MRP Area. Number of the MRP area for which material requirements planning should be carried out separately. Maximum length: 10.
Plant. Key uniquely identifying a plant. Maximum length: 4.
Independent Requirements Pointer. Maximum length: 12.
Indicator: Version Active. This selection determines whether the version is active, that is, relevant to MRP. Maximum length: 1.
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.
Requirements type. The requirements type determines the planning strategy to be used for a particular requirement. Maximum length: 4.
Version Number for Independent Requirements. Alphanumeric description of a demand program, also known as the (demand) version number. The version number is used for organizational purposes for the creation and further use of the demand program.Versions can be set to active and inactive. Only active versions are included in the planning run.Using the version compare function, you can compare various versions of a demand program with each other.With the version number various planned independent requirements can be indicated according to their origin. For example, whether the demand program results from SOP or from the material forecast.You can also create versions for long-term planning. Maximum length: 2.
Material Number. Alphanumeric key uniquely identifying the material. Maximum length: 40.
Requirements Plan. Key which can be given to create and to identify one or more planned independent requirements. The requirements plan number is used as a criterion for selection. Maximum length: 10.
Indicates that the Requirement Plan is external.
Requirement Segment. Indicates additional information about the type of requirement. You can freely define which requirement segments are satisfied by which stock segments using segmentation strategies in the transaction Segmentation Strategy Maintenance . Customer 1 accepts quality 1 and 2 while customer 2 accepts only quality 1. This results in 2 different requirement segments which can be assigned to different stock segments. Maximum length: 40.
One-to-many navigation property to the PlannedIndepRqmtItem entity.
All fields selector.
Static representation of the mrpArea property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plndIndepRqmtInternalId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plndIndepRqmtIsActive property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plndIndepRqmtLastChgdDateTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plndIndepRqmtType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plndIndepRqmtVersion property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the product property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the requirementPlan property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the requirementPlanIsExternal property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the requirementSegment property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the one-to-many navigation property toPlndIndepRqmtItem for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the PlannedIndepRqmt entity.
Default url path for the according service.
Technical entity name for PlannedIndepRqmt.
All key fields of the PlannedIndepRqmt entity.
Mapping of all key field names to the respective static field property PlannedIndepRqmt.
Technical service name for PlannedIndepRqmt.
Returns an entity builder to construct instances PlannedIndepRqmt.
A builder that constructs instances of entity type PlannedIndepRqmt.
Returns a selectable object that allows the selection of custom field in a get request for the entity PlannedIndepRqmt.
Name of the custom field to select
A builder that constructs instances of entity type PlannedIndepRqmt.
Returns a request builder to construct requests for operations on the PlannedIndepRqmt entity type.
A PlannedIndepRqmt request builder.
This class represents the entity "PlannedIndepRqmt" of service "API_PLND_INDEP_RQMT_SRV". This service is part of the following communication scenarios: Production Planning Integration (SAP_COM_0104). See https://api.sap.com/api/API_PLND_INDEP_RQMT_SRV for more information.