public class Messages extends VdmComplex<Messages>
Original complex type name from the Odata EDM: Messages
Modifier and Type | Class and Description |
---|---|
static class |
Messages.MessagesBuilder |
changedOriginalFields
Constructor and Description |
---|
Messages() |
Messages(String type_2,
String id,
String number,
String message,
String logNo,
String logMsgNo,
String messageV1,
String messageV2,
String messageV3,
String messageV4,
String parameter,
Integer row,
String field,
String system) |
Modifier and Type | Method and Description |
---|---|
static Messages.MessagesBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getField()
Constraints: Not nullable, Maximum length: 30
|
String |
getId()
Constraints: Not nullable, Maximum length: 20
|
protected Map<String,Object> |
getKey() |
String |
getLogMsgNo()
Constraints: Not nullable, Maximum length: 6
|
String |
getLogNo()
Constraints: Not nullable, Maximum length: 20
|
String |
getMessage()
Constraints: Not nullable, Maximum length: 220
|
String |
getMessageV1()
Constraints: Not nullable, Maximum length: 50
|
String |
getMessageV2()
Constraints: Not nullable, Maximum length: 50
|
String |
getMessageV3()
Constraints: Not nullable, Maximum length: 50
|
String |
getMessageV4()
Constraints: Not nullable, Maximum length: 50
|
String |
getNumber()
Constraints: Not nullable, Maximum length: 3
|
String |
getParameter()
Constraints: Not nullable, Maximum length: 32
|
Integer |
getRow()
Constraints: Not nullable
|
String |
getSystem()
Constraints: Not nullable, Maximum length: 10
|
String |
getType_2()
Constraints: Not nullable, Maximum length: 1
|
Class<Messages> |
getType() |
int |
hashCode() |
void |
setField(String field)
Constraints: Not nullable, Maximum length: 30
|
void |
setId(String id)
Constraints: Not nullable, Maximum length: 20
|
void |
setLogMsgNo(String logMsgNo)
Constraints: Not nullable, Maximum length: 6
|
void |
setLogNo(String logNo)
Constraints: Not nullable, Maximum length: 20
|
void |
setMessage(String message)
Constraints: Not nullable, Maximum length: 220
|
void |
setMessageV1(String messageV1)
Constraints: Not nullable, Maximum length: 50
|
void |
setMessageV2(String messageV2)
Constraints: Not nullable, Maximum length: 50
|
void |
setMessageV3(String messageV3)
Constraints: Not nullable, Maximum length: 50
|
void |
setMessageV4(String messageV4)
Constraints: Not nullable, Maximum length: 50
|
void |
setNumber(String number)
Constraints: Not nullable, Maximum length: 3
|
void |
setParameter(String parameter)
Constraints: Not nullable, Maximum length: 32
|
void |
setRow(Integer row)
Constraints: Not nullable
|
void |
setSystem(String system)
Constraints: Not nullable, Maximum length: 10
|
void |
setType_2(String type_2)
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public Messages()
public Messages(@Nullable String type_2, @Nullable String id, @Nullable String number, @Nullable String message, @Nullable String logNo, @Nullable String logMsgNo, @Nullable String messageV1, @Nullable String messageV2, @Nullable String messageV3, @Nullable String messageV4, @Nullable String parameter, @Nullable Integer row, @Nullable String field, @Nullable String system)
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<Messages>
@Nonnull public static Messages.MessagesBuilder builder()
@Nullable public String getType_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.
@Nullable public String getId()
Original property from the Odata EDM: Id
@Nullable public String getNumber()
Original property from the Odata EDM: Number
@Nullable public String getMessage()
Original property from the Odata EDM: Message
@Nullable public String getLogNo()
Original property from the Odata EDM: LogNo
@Nullable public String getLogMsgNo()
Original property from the Odata EDM: LogMsgNo
(Not necessarily the chronological order.)
@Nullable public String getMessageV1()
Original property from the Odata EDM: MessageV1
@Nullable public String getMessageV2()
Original property from the Odata EDM: MessageV2
@Nullable public String getMessageV3()
Original property from the Odata EDM: MessageV3
@Nullable public String getMessageV4()
Original property from the Odata EDM: MessageV4
@Nullable public String getParameter()
Original property from the Odata EDM: Parameter
@Nullable public Integer getRow()
Original property from the Odata EDM: Row
@Nullable public String getField()
Original property from the Odata EDM: Field
@Nullable public String getSystem()
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.
public void setType_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 void setId(@Nullable String id)
Original property from the Odata EDM: Id
id
- public void setNumber(@Nullable String number)
Original property from the Odata EDM: Number
number
- public void setMessage(@Nullable String message)
Original property from the Odata EDM: Message
message
- public void setLogNo(@Nullable String logNo)
Original property from the Odata EDM: LogNo
logNo
- public void setLogMsgNo(@Nullable String logMsgNo)
Original property from the Odata EDM: LogMsgNo
(Not necessarily the chronological order.)
logMsgNo
- public void setMessageV1(@Nullable String messageV1)
Original property from the Odata EDM: MessageV1
messageV1
- public void setMessageV2(@Nullable String messageV2)
Original property from the Odata EDM: MessageV2
messageV2
- public void setMessageV3(@Nullable String messageV3)
Original property from the Odata EDM: MessageV3
messageV3
- public void setMessageV4(@Nullable String messageV4)
Original property from the Odata EDM: MessageV4
messageV4
- public void setParameter(@Nullable String parameter)
Original property from the Odata EDM: Parameter
parameter
- public void setRow(@Nullable Integer row)
Original property from the Odata EDM: Row
row
- public void setField(@Nullable String field)
Original property from the Odata EDM: Field
field
- public void setSystem(@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
- Copyright © 2020 SAP SE. All rights reserved.