com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.purchaserequisition

Class Messages.MessagesBuilder

java.lang.Object

com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.purchaserequisition.Messages.MessagesBuilder

Enclosing class:

Messages

public static class Messages.MessagesBuilder
extends Object

Method Summary

Modifier and Type	Method and Description
Messages	build()
Messages.MessagesBuilder	field(String field) Constraints: Not nullable, Maximum length: 30
Messages.MessagesBuilder	id(String id) Constraints: Not nullable, Maximum length: 20
Messages.MessagesBuilder	logMsgNo(String logMsgNo) Constraints: Not nullable, Maximum length: 6
Messages.MessagesBuilder	logNo(String logNo) Constraints: Not nullable, Maximum length: 20
Messages.MessagesBuilder	message(String message) Constraints: Not nullable, Maximum length: 220
Messages.MessagesBuilder	messageV1(String messageV1) Constraints: Not nullable, Maximum length: 50
Messages.MessagesBuilder	messageV2(String messageV2) Constraints: Not nullable, Maximum length: 50
Messages.MessagesBuilder	messageV3(String messageV3) Constraints: Not nullable, Maximum length: 50
Messages.MessagesBuilder	messageV4(String messageV4) Constraints: Not nullable, Maximum length: 50
Messages.MessagesBuilder	number(String number) Constraints: Not nullable, Maximum length: 3
Messages.MessagesBuilder	parameter(String parameter) Constraints: Not nullable, Maximum length: 32
Messages.MessagesBuilder	row(Integer row) Constraints: Not nullable
Messages.MessagesBuilder	system(String system) Constraints: Not nullable, Maximum length: 10
String	toString()
Messages.MessagesBuilder	type_2(String type_2) Constraints: Not nullable, Maximum length: 1

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Method Detail

type_2

@Nonnull
public Messages.MessagesBuilder type_2(@Nullable
                                                String type_2)

Constraints: Not nullable, Maximum length: 1

Original property from the Odata EDM: Type

"S" for success messages"E" for error messages"W" for warnings"I" for information messagesDepending on the how a BAPI is implemented, if there is a termination message, a rollback can be executed in the database. All database changes since the last commit work command are cancelled. For further information see the documentation for the BAPI in question.

Parameters:

type_2 -

Returns:

this.

id

@Nonnull
public Messages.MessagesBuilder id(@Nullable
                                            String id)

Constraints: Not nullable, Maximum length: 20

Original property from the Odata EDM: Id

Parameters:

id -

Returns:

this.

number

@Nonnull
public Messages.MessagesBuilder number(@Nullable
                                                String number)

Constraints: Not nullable, Maximum length: 3

Original property from the Odata EDM: Number

Parameters:

number -

Returns:

this.

message

@Nonnull
public Messages.MessagesBuilder message(@Nullable
                                                 String message)

Constraints: Not nullable, Maximum length: 220

Original property from the Odata EDM: Message

Parameters:

message -

Returns:

this.

logNo

@Nonnull
public Messages.MessagesBuilder logNo(@Nullable
                                               String logNo)

Constraints: Not nullable, Maximum length: 20

Original property from the Odata EDM: LogNo

Parameters:

logNo -

Returns:

this.

logMsgNo

@Nonnull
public Messages.MessagesBuilder logMsgNo(@Nullable
                                                  String logMsgNo)

Constraints: Not nullable, Maximum length: 6

Original property from the Odata EDM: LogMsgNo

(Not necessarily the chronological order.)

Parameters:

logMsgNo -

Returns:

this.

messageV1

@Nonnull
public Messages.MessagesBuilder messageV1(@Nullable
                                                   String messageV1)

Constraints: Not nullable, Maximum length: 50

Original property from the Odata EDM: MessageV1

Parameters:

messageV1 -

Returns:

this.

messageV2

@Nonnull
public Messages.MessagesBuilder messageV2(@Nullable
                                                   String messageV2)

Constraints: Not nullable, Maximum length: 50

Original property from the Odata EDM: MessageV2

Parameters:

messageV2 -

Returns:

this.

messageV3

@Nonnull
public Messages.MessagesBuilder messageV3(@Nullable
                                                   String messageV3)

Constraints: Not nullable, Maximum length: 50

Original property from the Odata EDM: MessageV3

Parameters:

messageV3 -

Returns:

this.

messageV4

@Nonnull
public Messages.MessagesBuilder messageV4(@Nullable
                                                   String messageV4)

Constraints: Not nullable, Maximum length: 50

Original property from the Odata EDM: MessageV4

Parameters:

messageV4 -

Returns:

this.

parameter

@Nonnull
public Messages.MessagesBuilder parameter(@Nullable
                                                   String parameter)

Constraints: Not nullable, Maximum length: 32

Original property from the Odata EDM: Parameter

Parameters:

parameter -

Returns:

this.

row

@Nonnull
public Messages.MessagesBuilder row(@Nullable
                                             Integer row)

Constraints: Not nullable

Original property from the Odata EDM: Row

Parameters:

row -

Returns:

this.

field

@Nonnull
public Messages.MessagesBuilder field(@Nullable
                                               String field)

Constraints: Not nullable, Maximum length: 30

Original property from the Odata EDM: Field

Parameters:

field -

Returns:

this.

system

@Nonnull
public Messages.MessagesBuilder system(@Nullable
                                                String system)

Constraints: Not nullable, Maximum length: 10

Original property from the Odata EDM: System

The system names must have been defined.In SAP terms a client corresponds to a logical system. When you define a client, you can specify which logical system corresponds to the client.The logical system is important in the following SAP areas:ALE generally, where communication takes place between two or more logical systems.ALE distribution scenarios (for example, cost center accounting) where a system running a particular application is defined. Only in this system, for example, can master data be changed,Workflow objects: The object key always contains the logical system where the object is located.When you define the logical system keep in mind that:The logical system must be unique company-wide. No other system in the ALE system group can be used.The logical system must not be changed in the productive system, once a non-initial value has been specified. If a logical system with a non- initial value is changed afterwards, you may not be able to find documents in your own system. If the logical system specified in a document reference is not the same as your own system, the system assumes the document is located in a different system.

Parameters:

system -

Returns:

this.

build

@Nonnull
public Messages build()

toString

@Nonnull
public String toString()

Overrides:

toString in class Object