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
|
public Messages.MessagesBuilder type_2(@Nullable String type_2)
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.
type_2
- public Messages.MessagesBuilder id(@Nullable String id)
Original property from the Odata EDM: Id
id
- public Messages.MessagesBuilder number(@Nullable String number)
Original property from the Odata EDM: Number
number
- public Messages.MessagesBuilder message(@Nullable String message)
Original property from the Odata EDM: Message
message
- public Messages.MessagesBuilder logNo(@Nullable String logNo)
Original property from the Odata EDM: LogNo
logNo
- public Messages.MessagesBuilder logMsgNo(@Nullable String logMsgNo)
Original property from the Odata EDM: LogMsgNo
(Not necessarily the chronological order.)
logMsgNo
- public Messages.MessagesBuilder messageV1(@Nullable String messageV1)
Original property from the Odata EDM: MessageV1
messageV1
- public Messages.MessagesBuilder messageV2(@Nullable String messageV2)
Original property from the Odata EDM: MessageV2
messageV2
- public Messages.MessagesBuilder messageV3(@Nullable String messageV3)
Original property from the Odata EDM: MessageV3
messageV3
- public Messages.MessagesBuilder messageV4(@Nullable String messageV4)
Original property from the Odata EDM: MessageV4
messageV4
- public Messages.MessagesBuilder parameter(@Nullable String parameter)
Original property from the Odata EDM: Parameter
parameter
- public Messages.MessagesBuilder row(@Nullable Integer row)
Original property from the Odata EDM: Row
row
- public Messages.MessagesBuilder field(@Nullable String field)
Original property from the Odata EDM: Field
field
- public Messages.MessagesBuilder system(@Nullable String system)
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.
system
- public Messages build()
Copyright © 2019 SAP SE. All rights reserved.