Change Number. Number used to uniquely identify a change master record. If you make a change with reference to a change number, or create anobject with a change number, the following functions are at your disposal:The system determines the effectivity parametersThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date effectivity (valid from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation for the changesRevision level to indicate the change status of a material or documentChanges released for the different areas in the company. Maximum length: 12.
UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun). The UTC timestamp displays date and time according to UTC (Universal Coordinated Time). In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
Valid-From Date. Date, from which the change object (for example, document) change is effective with the corresponding change number. The system determines the date from the corresponding change master record. If the change object is not assigned to an alternative date, the date is then the valid-from date in the change header.
Alternative date external key. Key that uniquely identifies a valid-from date that differs from the valid-from date (change header). Maximum length: 18.
Objects Allocated.
All fields selector.
Static representation of the changeNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the changeNumberLastChgdDateTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the chgNmbrAlternativeDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the chgNmbrAlternativeDateId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the chgNmbrAltvDateIsAssignedToObj property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the ChangeMasterAltDate entity.
Default url path for the according service.
Technical entity name for ChangeMasterAltDate.
All key fields of the ChangeMasterAltDate entity.
Mapping of all key field names to the respective static field property ChangeMasterAltDate.
Technical service name for ChangeMasterAltDate.
Returns an entity builder to construct instances ChangeMasterAltDate.
A builder that constructs instances of entity type ChangeMasterAltDate.
Returns a selectable object that allows the selection of custom field in a get request for the entity ChangeMasterAltDate.
Name of the custom field to select
A builder that constructs instances of entity type ChangeMasterAltDate.
Returns a request builder to construct requests for operations on the ChangeMasterAltDate entity type.
A ChangeMasterAltDate request builder.
This class represents the entity "A_ChangeMasterAltDate" of service "API_CHANGEMASTER". This service is part of the following communication scenarios: Product Lifecycle Management - Master Data Integration (SAP_COM_0105). See https://api.sap.com/api/API_CHANGEMASTER;v=0002 for more information.