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