public class ChangeMstrObMgReDocInfoRecd extends VdmEntity<ChangeMstrObMgReDocInfoRecd>
Modifier and Type | Class and Description |
---|---|
static class |
ChangeMstrObMgReDocInfoRecd.ChangeMstrObMgReDocInfoRecdBuilder |
Modifier and Type | Field and Description |
---|---|
static ChangeMstrObMgReDocInfoRecdSelectable |
ALL_FIELDS
Selector for all available fields of ChangeMstrObMgReDocInfoRecd.
|
static ChangeMstrObMgReDocInfoRecdField<Boolean> |
ASSIGN_ALTERNATIVE_DATE_AC
Use with available fluent helpers to apply the AssignAlternativeDate_ac field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
CHANGE_NUMBER
Use with available fluent helpers to apply the ChangeNumber field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<Double> |
CHANGE_NUMBER_LAST_CHGD_DATE_TIME
Use with available fluent helpers to apply the ChangeNumberLastChgdDateTime field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
CHG_NMBR_ALTERNATIVE_DATE_ID
Use with available fluent helpers to apply the ChgNmbrAlternativeDateID field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
DOCUMENT_INFO_RECORD
Use with available fluent helpers to apply the DocumentInfoRecord field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
DOCUMENT_PART
Use with available fluent helpers to apply the DocumentPart field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
DOCUMENT_TYPE
Use with available fluent helpers to apply the DocumentType field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
DOCUMENT_VERSION
Use with available fluent helpers to apply the DocumentVersion field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
OBJ_MGMT_RECD_CREATED_BY
Use with available fluent helpers to apply the ObjMgmtRecdCreatedBy field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<Calendar> |
OBJ_MGMT_RECD_CREATION_DATE
Use with available fluent helpers to apply the ObjMgmtRecdCreationDate field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
OBJ_MGMT_RECD_DESCRIPTION
Use with available fluent helpers to apply the ObjMgmtRecdDescription field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<UUID> |
OBJ_MGMT_RECD_ITEM_UUID
Use with available fluent helpers to apply the ObjMgmtRecdItemUUID field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<Calendar> |
OBJ_MGMT_RECD_LAST_CHANGED_AT
Use with available fluent helpers to apply the ObjMgmtRecdLastChangedAt field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
OBJ_MGMT_RECD_LAST_CHANGED_BY
Use with available fluent helpers to apply the ObjMgmtRecdLastChangedBy field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
OBJ_MGMT_RECD_OBJ_IS_LOCKED_FOR_CHG
Use with available fluent helpers to apply the ObjMgmtRecdObjIsLockedForChg field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
OBJ_MGMT_RECD_OBJ_IS_PLANNED
Use with available fluent helpers to apply the ObjMgmtRecdObjIsPlanned field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<Calendar> |
OBJ_MGMT_RECD_OBJ_LAST_CHANGED_AT
Use with available fluent helpers to apply the ObjMgmtRecdObjLastChangedAt field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
OBJ_MGMT_RECD_OBJ_LAST_CHANGED_BY
Use with available fluent helpers to apply the ObjMgmtRecdObjLastChangedBy field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
OBJ_MGMT_RECD_OBJ_REVISION_LEVEL
Use with available fluent helpers to apply the ObjMgmtRecdObjRevisionLevel field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<String> |
SAP_OBJECT_TECHNICAL_ID
Use with available fluent helpers to apply the SAPObjectTechnicalID field to query operations.
|
static ChangeMstrObMgReDocInfoRecdField<Boolean> |
UNASSIGN_ALTERNATIVE_DATE_AC
Use with available fluent helpers to apply the UnassignAlternativeDate_ac field to query operations.
|
Constructor and Description |
---|
ChangeMstrObMgReDocInfoRecd() |
ChangeMstrObMgReDocInfoRecd(Boolean assignAlternativeDate_ac,
Boolean unassignAlternativeDate_ac,
String changeNumber,
String documentType,
String documentInfoRecord,
String documentPart,
String documentVersion,
String chgNmbrAlternativeDateID,
String sAPObjectTechnicalID,
String objMgmtRecdDescription,
UUID objMgmtRecdItemUUID,
Calendar objMgmtRecdLastChangedAt,
String objMgmtRecdLastChangedBy,
Calendar objMgmtRecdCreationDate,
String objMgmtRecdCreatedBy,
Calendar objMgmtRecdObjLastChangedAt,
String objMgmtRecdObjLastChangedBy,
String objMgmtRecdObjIsLockedForChg,
String objMgmtRecdObjIsPlanned,
String objMgmtRecdObjRevisionLevel,
Double changeNumberLastChgdDateTime,
ErpConfigContext erpConfigContext) |
Modifier and Type | Method and Description |
---|---|
static ChangeMstrObMgReDocInfoRecd.ChangeMstrObMgReDocInfoRecdBuilder |
builder() |
boolean |
equals(Object o) |
static <T> ChangeMstrObMgReDocInfoRecdField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
Boolean |
getAssignAlternativeDate_ac()
Constraints: none
|
String |
getChangeNumber()
(Key Field) Constraints: Not nullable, Maximum length: 12 If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:
The system determines the validity conditions
The conditions that the change is effective under can be defined in the change master record as follows:
Changes with a date validity (valid-from date)
Changes with parameter effectivity (for example: serial no. effectivity)
Log of the changes made
Documentation of the changes
Assignment of a revision level to a change state of a material or document
Release of changes for the different areas in the company
|
Double |
getChangeNumberLastChgdDateTime()
Constraints: Not nullable
|
String |
getChgNmbrAlternativeDateID()
Constraints: Not nullable, Maximum length: 18
|
String |
getDocumentInfoRecord()
(Key Field) Constraints: Not nullable, Maximum length: 25
|
String |
getDocumentPart()
(Key Field) Constraints: Not nullable, Maximum length: 3 Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
|
String |
getDocumentType()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
String |
getDocumentVersion()
(Key Field) Constraints: Not nullable, Maximum length: 2 A new version is assigned after the original files have been edited in the following processing situations:
The new processing status varies from the original in a certain way (for example, text change sin a text file).
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
String |
getObjMgmtRecdCreatedBy()
Constraints: Not nullable, Maximum length: 12
|
Calendar |
getObjMgmtRecdCreationDate()
Constraints: Not nullable, Precision: 0
|
String |
getObjMgmtRecdDescription()
Constraints: Not nullable, Maximum length: 40 You can enter or edit a long text by choosing the Object longtext function in the Extras menu.
|
UUID |
getObjMgmtRecdItemUUID()
Constraints: none
|
Calendar |
getObjMgmtRecdLastChangedAt()
Constraints: Not nullable, Precision: 0
|
String |
getObjMgmtRecdLastChangedBy()
Constraints: Not nullable, Maximum length: 12
|
String |
getObjMgmtRecdObjIsLockedForChg()
Constraints: Not nullable, Maximum length: 1
|
String |
getObjMgmtRecdObjIsPlanned()
Constraints: Not nullable, Maximum length: 1 no master record yet exists for this object and
no changes have been entered for the object with this change number
|
Calendar |
getObjMgmtRecdObjLastChangedAt()
Constraints: Not nullable, Precision: 0
|
String |
getObjMgmtRecdObjLastChangedBy()
Constraints: Not nullable, Maximum length: 12
|
String |
getObjMgmtRecdObjRevisionLevel()
Constraints: Not nullable, Maximum length: 2 You can assign a revision level when you make a change with reference to a change number with a particular valid-from date.
|
String |
getSAPObjectTechnicalID()
Constraints: Not nullable, Maximum length: 90
|
Class<ChangeMstrObMgReDocInfoRecd> |
getType() |
Boolean |
getUnassignAlternativeDate_ac()
Constraints: none
|
int |
hashCode() |
void |
setAssignAlternativeDate_ac(Boolean assignAlternativeDate_ac)
Constraints: none
|
void |
setChangeNumber(String changeNumber)
(Key Field) Constraints: Not nullable, Maximum length: 12 If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:
The system determines the validity conditions
The conditions that the change is effective under can be defined in the change master record as follows:
Changes with a date validity (valid-from date)
Changes with parameter effectivity (for example: serial no. effectivity)
Log of the changes made
Documentation of the changes
Assignment of a revision level to a change state of a material or document
Release of changes for the different areas in the company
|
void |
setChangeNumberLastChgdDateTime(Double changeNumberLastChgdDateTime)
Constraints: Not nullable
|
void |
setChgNmbrAlternativeDateID(String chgNmbrAlternativeDateID)
Constraints: Not nullable, Maximum length: 18
|
void |
setDocumentInfoRecord(String documentInfoRecord)
(Key Field) Constraints: Not nullable, Maximum length: 25
|
void |
setDocumentPart(String documentPart)
(Key Field) Constraints: Not nullable, Maximum length: 3 Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
|
void |
setDocumentType(String documentType)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
void |
setDocumentVersion(String documentVersion)
(Key Field) Constraints: Not nullable, Maximum length: 2 A new version is assigned after the original files have been edited in the following processing situations:
The new processing status varies from the original in a certain way (for example, text change sin a text file).
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setObjMgmtRecdCreatedBy(String objMgmtRecdCreatedBy)
Constraints: Not nullable, Maximum length: 12
|
void |
setObjMgmtRecdCreationDate(Calendar objMgmtRecdCreationDate)
Constraints: Not nullable, Precision: 0
|
void |
setObjMgmtRecdDescription(String objMgmtRecdDescription)
Constraints: Not nullable, Maximum length: 40 You can enter or edit a long text by choosing the Object longtext function in the Extras menu.
|
void |
setObjMgmtRecdItemUUID(UUID objMgmtRecdItemUUID)
Constraints: none
|
void |
setObjMgmtRecdLastChangedAt(Calendar objMgmtRecdLastChangedAt)
Constraints: Not nullable, Precision: 0
|
void |
setObjMgmtRecdLastChangedBy(String objMgmtRecdLastChangedBy)
Constraints: Not nullable, Maximum length: 12
|
void |
setObjMgmtRecdObjIsLockedForChg(String objMgmtRecdObjIsLockedForChg)
Constraints: Not nullable, Maximum length: 1
|
void |
setObjMgmtRecdObjIsPlanned(String objMgmtRecdObjIsPlanned)
Constraints: Not nullable, Maximum length: 1 no master record yet exists for this object and
no changes have been entered for the object with this change number
|
void |
setObjMgmtRecdObjLastChangedAt(Calendar objMgmtRecdObjLastChangedAt)
Constraints: Not nullable, Precision: 0
|
void |
setObjMgmtRecdObjLastChangedBy(String objMgmtRecdObjLastChangedBy)
Constraints: Not nullable, Maximum length: 12
|
void |
setObjMgmtRecdObjRevisionLevel(String objMgmtRecdObjRevisionLevel)
Constraints: Not nullable, Maximum length: 2 You can assign a revision level when you make a change with reference to a change number with a particular valid-from date.
|
void |
setSAPObjectTechnicalID(String sAPObjectTechnicalID)
Constraints: Not nullable, Maximum length: 90
|
void |
setUnassignAlternativeDate_ac(Boolean unassignAlternativeDate_ac)
Constraints: none
|
String |
toString() |
getVersionIdentifier, setVersionIdentifier
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField
public static final ChangeMstrObMgReDocInfoRecdSelectable ALL_FIELDS
public static final ChangeMstrObMgReDocInfoRecdField<Boolean> ASSIGN_ALTERNATIVE_DATE_AC
public static final ChangeMstrObMgReDocInfoRecdField<Boolean> UNASSIGN_ALTERNATIVE_DATE_AC
public static final ChangeMstrObMgReDocInfoRecdField<String> CHANGE_NUMBER
public static final ChangeMstrObMgReDocInfoRecdField<String> DOCUMENT_TYPE
public static final ChangeMstrObMgReDocInfoRecdField<String> DOCUMENT_INFO_RECORD
public static final ChangeMstrObMgReDocInfoRecdField<String> DOCUMENT_PART
public static final ChangeMstrObMgReDocInfoRecdField<String> DOCUMENT_VERSION
public static final ChangeMstrObMgReDocInfoRecdField<String> CHG_NMBR_ALTERNATIVE_DATE_ID
public static final ChangeMstrObMgReDocInfoRecdField<String> SAP_OBJECT_TECHNICAL_ID
public static final ChangeMstrObMgReDocInfoRecdField<String> OBJ_MGMT_RECD_DESCRIPTION
public static final ChangeMstrObMgReDocInfoRecdField<UUID> OBJ_MGMT_RECD_ITEM_UUID
public static final ChangeMstrObMgReDocInfoRecdField<Calendar> OBJ_MGMT_RECD_LAST_CHANGED_AT
public static final ChangeMstrObMgReDocInfoRecdField<String> OBJ_MGMT_RECD_LAST_CHANGED_BY
public static final ChangeMstrObMgReDocInfoRecdField<Calendar> OBJ_MGMT_RECD_CREATION_DATE
public static final ChangeMstrObMgReDocInfoRecdField<String> OBJ_MGMT_RECD_CREATED_BY
public static final ChangeMstrObMgReDocInfoRecdField<Calendar> OBJ_MGMT_RECD_OBJ_LAST_CHANGED_AT
public static final ChangeMstrObMgReDocInfoRecdField<String> OBJ_MGMT_RECD_OBJ_LAST_CHANGED_BY
public static final ChangeMstrObMgReDocInfoRecdField<String> OBJ_MGMT_RECD_OBJ_IS_LOCKED_FOR_CHG
public static final ChangeMstrObMgReDocInfoRecdField<String> OBJ_MGMT_RECD_OBJ_IS_PLANNED
public static final ChangeMstrObMgReDocInfoRecdField<String> OBJ_MGMT_RECD_OBJ_REVISION_LEVEL
public static final ChangeMstrObMgReDocInfoRecdField<Double> CHANGE_NUMBER_LAST_CHGD_DATE_TIME
public ChangeMstrObMgReDocInfoRecd()
public ChangeMstrObMgReDocInfoRecd(@Nullable Boolean assignAlternativeDate_ac, @Nullable Boolean unassignAlternativeDate_ac, @Nullable String changeNumber, @Nullable String documentType, @Nullable String documentInfoRecord, @Nullable String documentPart, @Nullable String documentVersion, @Nullable String chgNmbrAlternativeDateID, @Nullable String sAPObjectTechnicalID, @Nullable String objMgmtRecdDescription, @Nullable UUID objMgmtRecdItemUUID, @Nullable Calendar objMgmtRecdLastChangedAt, @Nullable String objMgmtRecdLastChangedBy, @Nullable Calendar objMgmtRecdCreationDate, @Nullable String objMgmtRecdCreatedBy, @Nullable Calendar objMgmtRecdObjLastChangedAt, @Nullable String objMgmtRecdObjLastChangedBy, @Nullable String objMgmtRecdObjIsLockedForChg, @Nullable String objMgmtRecdObjIsPlanned, @Nullable String objMgmtRecdObjRevisionLevel, @Nullable Double changeNumberLastChgdDateTime, @Nullable ErpConfigContext erpConfigContext)
public Class<ChangeMstrObMgReDocInfoRecd> getType()
getType
in class VdmObject<ChangeMstrObMgReDocInfoRecd>
public static <T> ChangeMstrObMgReDocInfoRecdField<T> field(String fieldName, Class<T> fieldType)
fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.public static ChangeMstrObMgReDocInfoRecd.ChangeMstrObMgReDocInfoRecdBuilder builder()
@Nullable public Boolean getAssignAlternativeDate_ac()
@Nullable public Boolean getUnassignAlternativeDate_ac()
@Nullable public String getChangeNumber()
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal: The system determines the validity conditions The conditions that the change is effective under can be defined in the change master record as follows: Changes with a date validity (valid-from date) Changes with parameter effectivity (for example: serial no. effectivity) Log of the changes made Documentation of the changes Assignment of a revision level to a change state of a material or document Release of changes for the different areas in the company
@Nullable public String getDocumentType()
@Nullable public String getDocumentInfoRecord()
@Nullable public String getDocumentPart()
Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
@Nullable public String getDocumentVersion()
A new version is assigned after the original files have been edited in the following processing situations: The new processing status varies from the original in a certain way (for example, text change sin a text file). You want the original processing status to remain the same (for example, documentation of project progress).
@Nullable public String getChgNmbrAlternativeDateID()
@Nullable public String getSAPObjectTechnicalID()
@Nullable public String getObjMgmtRecdDescription()
You can enter or edit a long text by choosing the Object longtext function in the Extras menu.
@Nullable public UUID getObjMgmtRecdItemUUID()
@Nullable public Calendar getObjMgmtRecdLastChangedAt()
@Nullable public String getObjMgmtRecdLastChangedBy()
@Nullable public Calendar getObjMgmtRecdCreationDate()
@Nullable public String getObjMgmtRecdCreatedBy()
@Nullable public Calendar getObjMgmtRecdObjLastChangedAt()
@Nullable public String getObjMgmtRecdObjLastChangedBy()
@Nullable public String getObjMgmtRecdObjIsLockedForChg()
@Nullable public String getObjMgmtRecdObjIsPlanned()
no master record yet exists for this object and no changes have been entered for the object with this change number
@Nullable public String getObjMgmtRecdObjRevisionLevel()
You can assign a revision level when you make a change with reference to a change number with a particular valid-from date. To do this, proceed as follows: Change a Material You can assign a revision level directly during processing in the material master record or in the material BOM header. Change a Document With documents, you can control whether a revision level is assigned, according to the document type. In this case you define a document status and set the release indicator for it. As soon as you process a document of this type, with reference to a change number and set this status for the first time, the revision level is assigned automatically. To enable you to enter a revision level, you first have to define it. To do this choose Logistics -> Central functions -> Engineering change management and then the menu path Revision level -> Material rev. level or Document rev. level. In the Setup control data section you can define how you want the assignment to be made.
@Nullable public Double getChangeNumberLastChgdDateTime()
@Nullable public ErpConfigContext getErpConfigContext()
public void setAssignAlternativeDate_ac(@Nullable Boolean assignAlternativeDate_ac)
assignAlternativeDate_ac
- public void setUnassignAlternativeDate_ac(@Nullable Boolean unassignAlternativeDate_ac)
unassignAlternativeDate_ac
- public void setChangeNumber(@Nullable String changeNumber)
If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal: The system determines the validity conditions The conditions that the change is effective under can be defined in the change master record as follows: Changes with a date validity (valid-from date) Changes with parameter effectivity (for example: serial no. effectivity) Log of the changes made Documentation of the changes Assignment of a revision level to a change state of a material or document Release of changes for the different areas in the company
changeNumber
- public void setDocumentType(@Nullable String documentType)
documentType
- public void setDocumentInfoRecord(@Nullable String documentInfoRecord)
documentInfoRecord
- public void setDocumentPart(@Nullable String documentPart)
Design departments, for example, can use document parts to divide up large documents such as design drawings into pages.
documentPart
- public void setDocumentVersion(@Nullable String documentVersion)
A new version is assigned after the original files have been edited in the following processing situations: The new processing status varies from the original in a certain way (for example, text change sin a text file). You want the original processing status to remain the same (for example, documentation of project progress).
documentVersion
- public void setChgNmbrAlternativeDateID(@Nullable String chgNmbrAlternativeDateID)
chgNmbrAlternativeDateID
- public void setSAPObjectTechnicalID(@Nullable String sAPObjectTechnicalID)
sAPObjectTechnicalID
- public void setObjMgmtRecdDescription(@Nullable String objMgmtRecdDescription)
You can enter or edit a long text by choosing the Object longtext function in the Extras menu.
objMgmtRecdDescription
- public void setObjMgmtRecdItemUUID(@Nullable UUID objMgmtRecdItemUUID)
objMgmtRecdItemUUID
- public void setObjMgmtRecdLastChangedAt(@Nullable Calendar objMgmtRecdLastChangedAt)
objMgmtRecdLastChangedAt
- public void setObjMgmtRecdLastChangedBy(@Nullable String objMgmtRecdLastChangedBy)
objMgmtRecdLastChangedBy
- public void setObjMgmtRecdCreationDate(@Nullable Calendar objMgmtRecdCreationDate)
objMgmtRecdCreationDate
- public void setObjMgmtRecdCreatedBy(@Nullable String objMgmtRecdCreatedBy)
objMgmtRecdCreatedBy
- public void setObjMgmtRecdObjLastChangedAt(@Nullable Calendar objMgmtRecdObjLastChangedAt)
objMgmtRecdObjLastChangedAt
- public void setObjMgmtRecdObjLastChangedBy(@Nullable String objMgmtRecdObjLastChangedBy)
objMgmtRecdObjLastChangedBy
- public void setObjMgmtRecdObjIsLockedForChg(@Nullable String objMgmtRecdObjIsLockedForChg)
objMgmtRecdObjIsLockedForChg
- public void setObjMgmtRecdObjIsPlanned(@Nullable String objMgmtRecdObjIsPlanned)
no master record yet exists for this object and no changes have been entered for the object with this change number
objMgmtRecdObjIsPlanned
- public void setObjMgmtRecdObjRevisionLevel(@Nullable String objMgmtRecdObjRevisionLevel)
You can assign a revision level when you make a change with reference to a change number with a particular valid-from date. To do this, proceed as follows: Change a Material You can assign a revision level directly during processing in the material master record or in the material BOM header. Change a Document With documents, you can control whether a revision level is assigned, according to the document type. In this case you define a document status and set the release indicator for it. As soon as you process a document of this type, with reference to a change number and set this status for the first time, the revision level is assigned automatically. To enable you to enter a revision level, you first have to define it. To do this choose Logistics -> Central functions -> Engineering change management and then the menu path Revision level -> Material rev. level or Document rev. level. In the Setup control data section you can define how you want the assignment to be made.
objMgmtRecdObjRevisionLevel
- public void setChangeNumberLastChgdDateTime(@Nullable Double changeNumberLastChgdDateTime)
changeNumberLastChgdDateTime
- public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext
- public String toString()
toString
in class VdmObject<ChangeMstrObMgReDocInfoRecd>
public boolean equals(Object o)
equals
in class VdmObject<ChangeMstrObMgReDocInfoRecd>
public int hashCode()
hashCode
in class VdmObject<ChangeMstrObMgReDocInfoRecd>
Copyright © 2018 SAP SE. All rights reserved.