Table of contents
A planned order is a system-generated proposal created within Enterprise Resource Planning (ERP) systems—such as SAP—or Advanced Planning Systems (APS), to signal the anticipated need to manufacture or procure a specific quantity of a pharmaceutical product or raw material at a specific time.
Planned orders are typically generated automatically during Material Requirements Planning (MRP) runs, using real-time inputs such as sales forecasts, customer orders, and inventory levels. Planned orders help pharmaceutical companies efficiently balance supply with demand, align production schedules, and maintain regulatory compliance.
In a digitally integrated environment like MINT, the ERP system of a pharmaceutical manufacturer is continuously updated with demand data. During MRP runs, the system creates planned orders that represent short-term, actionable needs. These planned orders are then shared with Contract Manufacturing Organizations (CMOs) or suppliers via MINT, providing them with timely and specific requirements that support better planning, responsiveness, and coordination across the supply chain.
While planners can manually create planned orders, they are most often generated automatically. They serve as preliminary production or procurement instructions—not yet final commitments, but essential for forward planning. Once reviewed and approved, planned orders can be converted into production orders (for in-house manufacturing) or purchase orders (for external sourcing), enabling smooth execution of supply chain activities.
Planned order sharing provides suppliers with detailed, short-term procurement proposals based on actual Material Requirements Planning (MRP) runs. These proposals include precise quantities and delivery dates that are often directly tied to production or process orders, making them more actionable and reflective of immediate operational needs. In contrast, forecast sharing communicates broader, long-term demand expectations derived from historical data and market trends. Forecasts are less specific and inherently more flexible, serving as strategic guidance for long-term capacity planning rather than firm commitments. As a result, planned orders carry a higher level of urgency and reliability, whereas forecasts are best viewed as directional indicators of future demand.
Planned order (IDoc)
The planned order IDoc message sends production planning information between MAH and CMO via an IDoc basic type message.
Contact your TraceLink Services representative for more information about integrating with this message.
- Message Type: MPC_PLANNED_ORDER
- IDoc Format: LOIPLO.LOIPLO02
- Transform Names:
SAP_IDoc_LOIPLO-LOIPLO02_PlannedOrder_IB_V1
SAP_IDoc_LOIPLO-LOIPLO02_PlannedOrder_OB_V1
Guidelines | Input Element | Occurs | Length | Description | Example | |||||
|---|---|---|---|---|---|---|---|---|---|
| IDOC | 1…1 | - | Required. IDoc root. | - | |||||
| @BEGIN | 1…1 | 0/* | Required. Begin of message attribute. | 1 | |||||
| EDI_DC40 | 1…1 | - | Required. IDoc control record. | - | |||||
| @SEGMENT | 1…1 | 0/* | Required. Begin of segment attribute. | 1 | |||||
| TABNAM | 1…1 | 0/* | Required. IDoc table name. | EDI_DC40 | |||||
| MANDT | 0…1 | 0/3 | Required. Client. | 300 | |||||
| DOCNUM | 0…1 | 0/16 | Required. IDoc number. | 0000000000619827 | |||||
| STATUS | 0…1 | 0/2 | Current IDoc processing status. | 03 | |||||
| DIRECT | 1…1 | 0/* | Required. Direction. | 1 | |||||
| OUTMOD | 0…1 | 0/1 | Output mode. | 2 | |||||
| EXPRSS | 0…1 | 0/1 | Overriding in inbound processing. | - | |||||
| TEST | 0…1 | 0/1 | Test flag. | - | |||||
| IDOCTYP | 1…1 | 0/* | Required. IDoc basic type. | DELFOR | |||||
| CIMTYP | 0…1 | 0/* | Name of extension type. | - | |||||
| MESTYP | 0…1 | 0/30 | Required. Logical message type. | DELFOR02 | |||||
| MESCOD | 0…1 | 0/3 | Required. Logical message code. | - | |||||
| MESFCT | 0…1 | 0/3 | Logical message function. | - | |||||
| STD | 0…1 | 0/1 | EDI standard. | - | |||||
| STDVRS | 0…1 | 0/6 | Version of EDI standard. | - | |||||
| STDMES | 0…1 | 0/6 | EDI message type. | - | |||||
| SNDPOR | 1…1 | 0/10 | Required. Sender port (SAP System, EDI subsystem). | SAPD11 | |||||
| SNDPRT | 1…1 | 0/2 | Required. Partner type of sender. | LS | |||||
| SNDPFC | 0…1 | 0/2 | Partner function of sender. | - | |||||
| SNDPRN | 1…1 | 0/10 | Required. Partner number of sender. | ERPCLNT302 | |||||
| SNDSAD | 0…1 | 0/21 | Required. Sender address (SADR). | - | |||||
| SNDLAD | 0…1 | 0/70 | Logical address of sender mapping to fileSenderNumber. Require a value that concatenates party type with party identifier in party type format. | 0010136941923 | |||||
| RCVPOR | 1…1 | 0/10 | Required. SAP receiver port. | TRACELINK | |||||
| RCVPRT | 0…1 | 0/2 | Partner type of receiver. | LS | |||||
| RCVPFC | 0…1 | 0/2 | Partner function of receiver. | LS | |||||
| RCVPRN | 1…1 | 0/10 | Required. Partner number of receiver. | TRACELINK | |||||
| RCVSAD | 0…1 | 0/21 | Required. Receiver address (SADR). | - | |||||
| RCVLAD | 0…1 | 0/70 | Logical address of receiver. Required for TraceLink. Identifies the receiver of the IDoc for the TraceLink system's location ID. Must match the value that the IDoc sender has configured for their receiver partner in TraceLink. | 3333331013655 | |||||
| CREDAT | 0…1 | 0/8 | Required. Date IDoc was created in format YYYYMMDD. | 20230511 | |||||
| CRETIM | 0…1 | 6/6 | Time IDoc was created in format HHMMSS. | 161000 | |||||
| REFINT | 0…1 | 0/14 | Reference to interchange file. | - | |||||
| REFGRP | 0…1 | 0/14 | Reference to message group. | - | |||||
| REFMES | 0…1 | 0/14 | Reference to message. | - | |||||
| ARCKEY | 0…1 | 0/70 | EDI archive key. | - | |||||
| SERIAL | 0…1 | 0/20 | EDI/ALE: Serialization field. | - | |||||
| E1PLAFL | 1…1 | - | Required. IDoc header data for planned order. | - | |||||
| @SEGMENT | 1…1 | 0/* | Required. Begin of segment attribute. | 1 | |||||
| ABMNG | 0…1 | 0/14 | Reduced quantity in the planned order, indicates a decrease in the originally planned order quantity due to changes in demand, stock availability, or other factors. | 12 | |||||
| AUFFX | 0…1 | 0/1 | This indicator specifies whether the planned order is fixed, meaning the system will not alter the dates or lot sizes during subsequent planning runs. | X | |||||
| AVMNG | 0…1 | 0/14 | Fixed scrap quantity from production. | 2 | |||||
| BESKZ | 0…1 | 0/1 | Procurement Type, Indicator determines procurement type of the planed order material is procured.
| F | |||||
| DISPO | 0…1 | 0/3 | Number of the MRP controller or group of MRP controllers responsible for material planning for the material. | 011 | |||||
| EKORG | 0…1 | 0/4 | Purchasing Organization code, purchasing organization procures materials and services, negotiates conditions of purchase with vendors, and is responsible for such transactions. | 1000 | |||||
| GSBTR | 0…1 | 0/8 | Total commitment date after ATP check from warehouse for MRP. | 20240428 | |||||
| GLTRS | 0…1 | 0/8 | Scheduled production finish date. | 20240428 | |||||
| GLUZS | 0…1 | 0/6 | scheduled production finish time in hhmmss. | 010450 | |||||
| GSMNG | 0…1 | 0/14 | Required. Total output planned order quantity. | 12 | |||||
| GSTRS | 0…1 | 0/8 | Scheduled production start date. | 20240428 | |||||
| GSUZS | 0…1 | 0/6 | scheduled production finish time in hhmmss. | 010450 | |||||
| KAPFX | 0…1 | 0/1 | Indicates that the capacity requirements for the planned order are dispatched and won't be changed, including dates and quantities. Valid value is X | X | |||||
| KDAUF | 0…1 | 0/10 | Sales Order identifier number, uniquely identifies a specific sales order in the system. It is used to track and reference sales orders, with postprocessing possible only for non-valuated sales order stock. | 0000011732 | |||||
| KDPOS | 0…1 | 0/6 | Sales order Item number, Uniquely identifies an item within a sales order. | 00010 | |||||
| LGORT | 0…1 | 0/4 | Storage location number in the plant. | 0004 | |||||
| MATNR | 0…1 | 0/18 | Required. Planning material number for which planned order is created | 100-130 | |||||
| MDACC | 0…1 | 0/4 | Code of last carried out action for a planned order, such as check material availability or explode BOM..etc. | BEMA | |||||
| MDACD | 0…1 | 0/8 | Date of last carried our action. | 20240428 | |||||
| MDACH | 0…1 | 0/4 | Action control in planned order processing, defining the sequence of actions that can be performed on planned orders. | 01 | |||||
| MDPBV | 0…1 | 0/1 | This field indicates the availability status of the planned order. It confirms whether the materials, resources, or capacities required for the planned order are available at the time of planning. Valid values:
| 1 | |||||
| MEINS | 0…1 | 0/3 | Required. Planned order quantity unit of measure. | PCE | |||||
| PAART | 0…1 | 0/4 | Required. Planned order type. Valid values:
| NB | |||||
| PALTR | 0…1 | 0/8 | Explosion date, which is used to determine the valid Bill of Materials (BOM) or routing for a planned order, it helps to ensure that materials are planned correctly based on the current version of the BOM, considering changes in components, materials, or production processes over time. | 20161113 | |||||
| PEDTR | 0…1 | 0/8 | Planned order finish date, expected completion or delivery of the planned order quantity. | 20240428 | |||||
| PERTR | 0…1 | 0/8 | Date when planned order will be opened. | 20161113 | |||||
| PLNAL | 0…1 | 0/2 | Group counter identifier, counter and group uniquely identify the task list, with group counter SAP allows planners to manage related planned orders as a group, making it easier to assign common resources, materials, and work centers. | 02 | |||||
| PLNNR | 0…1 | 0/8 | Group counter identifier, counter and group uniquely identify the task list, with group counter SAP allows planners to manage related planned orders as a group, making it easier to assign common resources, materials, and work centers. | 000002 | |||||
| PLNTY | 0…1 | 0/1 | Identifier key, classifies task lists according to their functionality. Valid values:
| 0 | |||||
| PLNUM | 0…1 | 0/10 | Required. Planned Order identifier number, uniquely identifies a specific planned order for a material. | 0000038723 | |||||
| PLWRK | 0…1 | 0/4 | Required. Planning plant code where materials are required to build. | 0004 | |||||
| PSPEL | 0…1 | 0/24 | Required. work break down structure identifier is used to identify a element or task in case of order type is project order. | M/3500-42 | |||||
| PSTTR | 0…1 | 0/8 | Required. Planned order start date, Earliest date by when production of planned order quantity starts. | 20240428 | |||||
| PWWRK | 0…1 | 0/4 | Production plant number in which the order quantity of the internally produced material will be manufactured. | 0004 | |||||
| SERNR | 0…1 | 0/8 | The BOM explosion number links this explosion to the specific production series that is being used to fulfill the planned order. | 000012 | |||||
| SOBES | 0…1 | 0/1 | Required. Indicator determines the procurement type of the material and how the material is procured.
| 0 | |||||
| SOBKZ | 0…1 | 0/1 | Required. Identifying and managing materials that are not part of regular inventory but need to be tracked separately.
| O | |||||
| STLFX | 0…1 | 0/1 | Indicates whether the BOM is fixed and won't be re-exploded during another planning run. Valid values:
| X | |||||
| UMSKZ | 0…1 | 0/1 | Indicates whether the planned order can be converted into a production order, process order, or purchase requisition. Valid values
| X | |||||
| VERID | 0…1 | 0/4 | A key determines production techniques determines BOM explosion, task list type, group and counter for allocating tasks lists. | 1 | |||||
| VFMNG | 0…1 | 0/14 | Total committed planned order quantity. | 12 | |||||
| WEBAZ | 0…1 | 0/5 | Goods receipt processing time in days, - days required to check received goods and transferring to storage locations. | 1 | |||||
| STLAN | 0…1 | 0/1 | BOM Usage defines the area (e.g., engineering, design, or production) where a BOM can be applied. It sets indicators to determine the item’s configuration and its processing eligibility in specific areas like production. | 1 | |||||
| STLAT | 0…1 | 0/2 | Alternative BOM identifies a BOM within a BOM group, This allows flexibility in production, where an alternative BOM can be selected if the primary BOM is unavailable or requires adjustments. | 1 | |||||
| PLGRP | 0…1 | 0/2 | Production of a material controlling group, responsible for calculating capacity requirement during schedule run. | 101 | |||||
| E1RESBL | 0…9999 | - | Reservation or dependent requirements. | - | |||||
| @SEGMENT | 1…1 | 0/* | Required. Begin of segment attribute. | 1 | |||||
| BDMNG | 0…1 | 0/14 | Required. Base item quantity reserved for making a finished product. | 13 | |||||
| BDTER | 0…1 | 0/8 | Required. Date on which reserved quantity is required. | 20161113 | |||||
| BEIKZ | 0…1 | 0/1 | Material provision indicator that the item is subject to material provision, empty in this field means this component are provided as consumable materials for subcontractor
| K | |||||
| CHARG | 0…1 | 0/10 | Batch number of reserved item. | AR | |||||
| DBSKZ | 0…1 | 0/1 | This field indicates whether the material required for the planned order is to be directly procured (procured specifically for a customer or production order) or managed through stock procurement. Valid values:
| E | |||||
| ENMNG | 0…1 | 0/14 | Quantity already withdrawn from the required item quantity reserved for making a finished product. | 4 | |||||
| FMENG | 0…1 | 0/1 | Quantity fixed indicator - Indicates that the quantity of an item remains constant, regardless of changes in the related system or finished product quantity. Valid value is | X | |||||
| LGORT | 0…1 | 0/4 | Specifies the storage location for issuing components (backflush posting) or receiving produced materials (receipt posting) in planned or production orders. | 1212 | |||||
| MATNR | 0…1 | 0/18 | Required. Component bill of material item identifier used in the production of finished good. | 121212 | |||||
| MEINS | 0…1 | 0/14 | Required. Base unit for Measurement Code. Unit of entry UOM's include: Valid values
| EA | |||||
| SBTER | 0…1 | 0/8 | Date on which reserved quantity is required. | 20161113 | |||||
| SOBKZ | 0…1 | 0/1 | Identifying and managing materials that are not part of regular inventory but need to be tracked separately.
| O | |||||
| UPSKZ | 0…1 | 0/1 | Indicates BOM Item sub items. | X | |||||
| VMENG | 0…1 | 0/14 | Confirmed quantity for availability check would store the difference between the delivered and invoiced quantities, based on the purchase order quantity. | 4 | |||||
| WERKS | 0…1 | 0/4 | Planning plant code where materials are required to build. | 0004 | |||||
| POSNR | 0…1 | 0/4 | Required. Reserved material/component serial number. | 0010 | |||||
| RSNUM | 0…1 | 0/10 | Required. Reservation or dependent requirements alphanumeric identifier for each order, unique identification number assigned to a reservation for materials or goods. RSNUM field links RSEB and FLAP table in SAP. | 0010 | |||||
| RSPOS | 0…1 | 0/4 | Required. Specifies the number that uniquely identifies an item in a reservation or a dependent requirement. | 1 | |||||
| NOMNG | 0…1 | 0/15 | Required. Required base quantity. | 4 | |||||
| DUMPS | 0…1 | 0/1 | Phantom item indicator, specifies whether the item in question is a phantom assembly. | - | |||||
| AUFST | 0…1 | 0/2 | The BOM level and the path are only relevant for planning with phantom assemblies. | - | |||||
| AUFWG | 0…1 | 0/2 | The level and path together identify the exact position of a phantom assembly in a BOM | - | |||||
| POSTP | 0…1 | 0/1 | Classifies BOM items based on criteria like object reference (e.g., material or document) or stock status. It controls field selection, default values, and system activities for BOM maintenance. | 1 | |||||
| STLNR | 0…1 | 0/8 | Bill of material identifier number. | 0000038723 | |||||
| STLKN | 0…1 | 0/8 | Bill of material item node identifier number. | 0121 | |||||
| STPOZ | 0…1 | 0/8 | Internal counter, Identifies the activity posting. | 01 | |||||
| LGNUM | 0…1 | 0/3 | Warehouse Number/Warehouse Complex ,identifies physical warehouse structure within the Warehouse Management system. | 01 | |||||
| PRVBE | 0…1 | 0/10 | A shop floor interim storage area for materials, used in production, Kanban processing, and Warehouse Management. | 2 | |||||
| E1PLOPL | 0…9999 | - | Processes/operations for planned orders. | - | |||||
| @SEGMENT | 1…1 | 0/* | Required. Begin of segment attribute. | 1 | |||||
| VORNR | 0…1 | 0/4 | Required. Determines in which order the operations of a sequence are carried out. | 01 | |||||
| PVZNR | 0…1 | 0/4 | Identifies priror operation to this operation. | 01 | |||||
| ARBEI | 0…1 | 0/7 | Required. Amount of work involved in performing the activity. | 01 | |||||
| ARBEH | 0…1 | 0/3 | Work unit of measurement. Valid values
| 01 | |||||
| ARBID | 0…1 | 0/8 | Work center ID. | 01 | |||||
| DAUNO | 0…1 | 0/7 | Normal duration of the activity. | 01 | |||||
| DAUNE | 0…1 | 0/3 | Normal duration unit of measurement. Valid values
| 01 | |||||
| FSSAD | 0…1 | 0/8 | Earliest date when processing is finished and teardown can start. | 20161113 | |||||
| FSSAZ | 0…1 | 0/6 | Earliest time when planning operation is finished and teardown can start. | 131110 | |||||
| FSSBD | 0…1 | 0/8 | Earliest date when processing of the planning operation can begin. | 20161113 | |||||
| FSSBZ | 0…1 | 0/6 | Earliest time when processing of the planning operation can begin. | 131110 | |||||
| PLNFL | 0…1 | 0/6 | Sequence - A key which identifies a sequence of operations within a routing. | 01 | |||||
| SSSAD | 0…1 | 0/8 | Latest start date for the teardown of the operation. | 20161113 | |||||
| SSSAZ | 0…1 | 0/6 | Latest start time for the teardown of the operation. | 131110 | |||||
| SSSBD | 0…1 | 0/8 | Latest start date for the processing of the operation. | 20161113 | |||||
| SSSBZ | 0…1 | 0/6 | Latest start time for the processing of the operation. | 131110 | |||||
| VGW | 0…1 | 0/7 | Amount of work involved in performing the activity. | 01 | |||||
| VGE | 0…1 | 0/3 | Work unit of measurement. Valid values
| 01 | |||||
| STEUS | 0…1 | 0/4 | Determines which business transactions should be executed for the object that belongs to the task list or order. | PPO1 | |||||
| FLGAT | 0…1 | 0/1 | Sequence category , Indicates a standard sequence or a parallel sequence or an alternative sequence. | - | |||||
| LTXA1 | 0…1 | 0/40 | Operation short text description. | - | |||||
| E1KBEDL | 0…9999 | - | Capacity requirements for processes. | - | |||||
| @SEGMENT | 1…1 | 0/* | Required. Begin of segment attribute. | 1 | |||||
| BEDID | 0…1 | 0/12 | Required. ID of the capacity requirements record. | 10000005942 | |||||
| BEDZL | 0…1 | 0/8 | Required. Internal counter, Identifies the activity posting. | 1 | |||||
| CANUM | 0…1 | 0/4 | Required. Internal counter, Identifies the activity posting. | 513 | |||||
| BEDKZ | 0…1 | 0/1 | Remaining split record indicator. | X | |||||
| KABRREST | 0…1 | 0/22 | Indicates how much capacity is still required for the teardown phase of an operation. | 0 | |||||
| KABRSOLL | 0…1 | 0/22 | Specifies the planned or scheduled capacity needed for the teardown phase of an operation. | 1 | |||||
| KBEAREST | 0…1 | 0/22 | Indicates how much capacity is still required for the processing phase of an operation. | 0 | |||||
| KBEASOLL | 0…1 | 0/22 | Specifies the planned or scheduled capacity needed for the processing phase of an operation. | 1 | |||||
| KRUEREST | 0…1 | 0/22 | Indicates how much capacity is still required for the setup phase of an operation. | 0 | |||||
| KRUESOLL | 0…1 | 0/22 | Specifies the planned or scheduled capacity needed for the setup phase of an operation. | 1 | |||||
| KAPAR | 0…1 | 0/3 | Capacity category: In a planning order or production order, this field is populated to indicate which capacity category (e.g., machine, labor, etc.) is linked with a specific operation or activity in a work center. | 101 | |||||
| KAPID | 0…1 | 0/8 | Work center resource id where in capacity is required in production. | 101232 | |||||
| KEINH | 0…1 | 0/3 | Unit of measure for displaying capacity requirements. Valid values
| EA | |||||
| FSTAD | 0…1 | 0/8 | Earliest start date for the processing of the operation. | 20161113 | |||||
| FSTAU | 0…1 | 0/6 | Earliest start time for the processing of the operation. | 131110 | |||||
| FENDD | 0…1 | 0/8 | Earliest finish date for the processing of the operation. | 20161113 | |||||
| FENDU | 0…1 | 0/6 | Earliest finish time for the processing of the operation. | 131110 | |||||
| SPLIT | 0…1 | 0/3 | Split number. | 01 | |||||
| MGVRG | 0…1 | 0/15 | Required. Operation activity quantity that will be produced. | 4 | |||||
| MEINH | 0…1 | 0/3 | Required. Unit of measure for activity. Valid values
| EA | |||||
| E1PLUVL | 0…9999 | - | sub processes/ sub operations for planned orders. | - | |||||
| @SEGMENT | 1…1 | 0/* | Required. Begin of segment attribute. | 1 | |||||
| UVORN | 0…1 | 0/4 | Required. Sub operation identifier. | 01 | |||||
| ARBEI | 0…1 | 0/7 | Amount of work involved in performing the activity. | 01 | |||||
| ARBEH | 0…1 | 0/3 | Work unit of measurement. Valid values
| 01 | |||||
| ARBID | 0…1 | 0/8 | Work center ID. | 01 | |||||
| DAUNO | 0…1 | 0/7 | Normal duration of the activity. | 01 | |||||
| DAUNE | 0…1 | 0/3 | Normal duration unit of measurement. Valid values
| 01 | |||||
| FSSAD | 0…1 | 0/8 | Earliest date when processing is finished and teardown can start | 20161113 | |||||
| FSSAZ | 0…1 | 0/6 | Earliest time when planning operation is finished and teardown can start | 131110 | |||||
| PLNFL | 0…1 | 0/6 | Sequence - A key which identifies a sequence of operations within a routing. | 01 | |||||
| FSSBD | 0…1 | 0/8 | Earliest date when processing of the planning operation can begin. | 20161113 | |||||
| FSSBZ | 0…1 | 0/6 | Earliest time when processing of the planning operation can begin. | 131110 | |||||
| SSSAD | 0…1 | 0/8 | Latest start date for the teardown of the operation. | 20161113 | |||||
| SSSAZ | 0…1 | 0/6 | Latest start time for the teardown of the operation. | 131110 | |||||
| SSSBD | 0…1 | 0/8 | Latest start date for the processing of the operation. | 20161113 | |||||
| SSSBZ | 0…1 | 0/6 | Latest start time for the processing of the operation. | 131110 | |||||
| VGW | 0…1 | 0/7 | Amount of work involved in performing the activity. | 01 | |||||
| VGE | 0…1 | 0/3 | Work unit of measurement. Valid values
| 01 | |||||
| E1KBEUL | 0…9999 | - | Capacity requirements for sub processes or sub operations. | - | |||||
| @SEGMENT | 1…1 | 0/* | Required. Begin of segment attribute. | 1 | |||||
| BEDID | 0…1 | 0/12 | Required. ID of the capacity requirements record. | 10000005942 | |||||
| BEDZL | 0…1 | 0/8 | Required. Identifier for the activity posting. | 1 | |||||
| CANUM | 0…1 | 0/4 | Required. Counters for capacity requirements records various caps includes individual capacities. | 513 | |||||
| BEDKZ | 0…1 | 0/1 | Remaining split record indicator. | X | |||||
| KABRREST | 0…1 | 0/22 | Indicates how much capacity is still required for the teardown phase of an operation. | 0 | |||||
| KABRSOLL | 0…1 | 0/22 | Specifies the planned or scheduled capacity needed for the teardown phase of an operation. | 1 | |||||
| KBEAREST | 0…1 | 0/22 | Indicates how much capacity is still required for the processing phase of an operation. | 0 | |||||
| KBEASOLL | 0…1 | 0/22 | Specifies the planned or scheduled capacity needed for the processing phase of an operation. | 1 | |||||
| KRUEREST | 0…1 | 0/22 | Indicates how much capacity is still required for the setup phase of an operation. | 0 | |||||
| KRUESOLL | 0…1 | 0/22 | Specifies the planned or scheduled capacity needed for the setup phase of an operation. | 1 | |||||
| KAPAR | 0…1 | 0/3 | Capacity category: In a planning order or production order, this field is populated to indicate which capacity category (e.g., machine, labor, etc.) is linked with a specific operation or activity in a work center. | 101 | |||||
| KAPID | 0…1 | 0/8 | Work center resource id where in capacity is required in production. | 101232 | |||||
| KEINH | 0…1 | 0/3 | Unit of measure for displaying capacity requirements. Valid values
|
EA | |||||
Example <LOIPLO02>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>300</MANDT>
<DOCNUM>0000000000619827</DOCNUM>
<STATUS>03</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<TEST>s</TEST>
<EXPRSS/>
<IDOCTYP>LOIPLO02</IDOCTYP>
<CIMTYP/>
<MESTYP/>
<MESCOD>s4</MESCOD>
<MESFCT>s5</MESFCT>
<STD>s</STD>
<STDVRS>s7</STDVRS>
<STDMES>s8</STDMES>
<SNDPOR>SAPD11</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPFC>s1</SNDPFC>
<SNDPRN>ERPCLNT302</SNDPRN>
<SNDSAD/>
<SNDLAD>ERPCLNT302</SNDLAD>
<RCVPOR>TRACELINK</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPFC>LS</RCVPFC>
<RCVPRN>TRACELINK</RCVPRN>
<RCVSAD/>
<RCVLAD>3333331013655</RCVLAD>
<CREDAT>20250206</CREDAT>
<CRETIM>154510</CRETIM>
<REFINT>s17</REFINT>
<REFGRP>s18</REFGRP>
<REFMES>s19</REFMES>
<ARCKEY>s20</ARCKEY>
<SERIAL>s21</SERIAL>
</EDI_DC40>
<E1PLAFL SEGMENT="1">
<ABMNG>12</ABMNG>
<AUFFX>X</AUFFX>
<AUFNR/>
<AVMNG>2</AVMNG>
<BESKZ>F</BESKZ>
<DISPO>100</DISPO>
<EKORG>1000</EKORG>
<GSBTR>20240428</GSBTR>
<GLTRS>20240428</GLTRS>
<GLUZS>010450</GLUZS>
<GSMNG>12</GSMNG>
<GSTRS>20240428</GSTRS>
<GSUZS>010450</GSUZS>
<KAPFX>X</KAPFX>
<KDAUF>0000011732</KDAUF>
<KDPOS>00010</KDPOS>
<LGORT>0004</LGORT>
<MATNR>100-130</MATNR>
<MDACC>BEMA</MDACC>
<MDACD>20240429</MDACD>
<MDACH>01</MDACH>
<MDACT>s42</MDACT>
<MDPBV>1</MDPBV>
<MEINS>PCE</MEINS>
<PAART>NB</PAART>
<PALTR>20161113</PALTR>
<PEDTR>20250428</PEDTR>
<PERTR>20161113</PERTR>
<PLNAL>02</PLNAL>
<PLNNR>0002</PLNNR>
<PLNTY>2</PLNTY>
<PLNUM>0000038723</PLNUM>
<PLSCN/>
<PLWRK>0004</PLWRK>
<PSPEL>M/3500-42</PSPEL>
<PSTTR>20240428</PSTTR>
<PWWRK>0004</PWWRK>
<SEQNR>1</SEQNR>
<SERNR>000012</SERNR>
<SOBES>0</SOBES>
<SOBKZ>R</SOBKZ>
<STLFX>X</STLFX>
<UMSKZ>X</UMSKZ>
<VERID>1</VERID>
<VFMNG>12</VFMNG>
<WEBAZ>1</WEBAZ>
<STLAN>1</STLAN>
<STALT>1</STALT>
<PLGRP>101</PLGRP>
<E1PLOPL SEGMENT="1">
<VORNR>01</VORNR>
<PVZNR>01</PVZNR>
<ARBEH>BE</ARBEH>
<ARBEI>100</ARBEI>
<ARBID>01</ARBID>
<DAUNE>BX</DAUNE>
<DAUNO>100</DAUNO>
<FSEDD></FSEDD>
<FSEDZ></FSEDZ>
<FSAVD></FSAVD>
<FSAVZ></FSAVZ>
<FSSAD>20191116</FSSAD>
<FSSAZ>131310</FSSAZ>
<FSSBD>20200113</FSSBD>
<FSSBZ>121500</FSSBZ>
<PLNFL>01</PLNFL>
<SSSAD>20200505</SSSAD>
<SSSAZ>150015</SSSAZ>
<SSSBD>20200707</SSSBD>
<SSSBZ>150015</SSSBZ>
<VGE01>EA</VGE01>
<VGE02>EA</VGE02>
<VGE03>EA</VGE03>
<VGE04>EA</VGE04>
<VGE05>EA</VGE05>
<VGE06>EA</VGE06>
<VGW01>10</VGW01>
<VGW02>20</VGW02>
<VGW03>30</VGW03>
<VGW04>40</VGW04>
<VGW05>50</VGW05>
<VGW06>60</VGW06>
<STEUS>PPO1</STEUS>
<FLGAT>s</FLGAT>
<LTXA1>s97</LTXA1>
<E1PLUVL SEGMENT="1">
<UVORN>01</UVORN>
<ARBEH>GLL</ARBEH>
<ARBEI>01</ARBEI>
<ARBID>01</ARBID>
<DAUNE>GLL</DAUNE>
<DAUNO>01</DAUNO>
<FSEDD></FSEDD>
<FSEDZ></FSEDZ>
<FSAVD></FSAVD>
<FSAVZ></FSAVZ>
<FSSAD>20161113</FSSAD>
<FSSAZ>131110</FSSAZ>
<FSSBD>20161113</FSSBD>
<FSSBZ>131110</FSSBZ>
<PLNFL>01</PLNFL>
<SSSAD>20161113</SSSAD>
<SSSAZ>131110</SSSAZ>
<SSSBD>20161113</SSSBD>
<SSSBZ>131110</SSSBZ>
<VGE01>EA</VGE01>
<VGE02>EA</VGE02>
<VGE03>EA</VGE03>
<VGE04>EA</VGE04>
<VGE05>EA</VGE05>
<VGE06>EA</VGE06>
<VGW01>10</VGW01>
<VGW02>20</VGW02>
<VGW03>30</VGW03>
<VGW04>40</VGW04>
<VGW05>50</VGW05>
<VGW06>60</VGW06>
<E1KBEUL SEGMENT="1">
<BEDID>10000005942</BEDID>
<BEDZL>1</BEDZL>
<CANUM>513</CANUM>
<BEDKZ>X</BEDKZ>
<KABRREST>0</KABRREST>
<KABRSOLL>1</KABRSOLL>
<KAPAR>101</KAPAR>
<KAPID>101232</KAPID>
<KBEAREST>0</KBEAREST>
<KBEASOLL>1</KBEASOLL>
<KEINH>EA</KEINH>
<KRUEREST>0</KRUEREST>
<KRUESOLL>1</KRUESOLL>
</E1KBEUL>
</E1PLUVL>
<E1KBEDL SEGMENT="1">
<BEDID>10000005942</BEDID>
<BEDZL>1</BEDZL>
<CANUM>513</CANUM>
<BEDKZ>X</BEDKZ>
<KABRREST>0</KABRREST>
<KABRSOLL>1</KABRSOLL>
<KAPAR>101</KAPAR>
<KAPID>101232</KAPID>
<KBEAREST>0</KBEAREST>
<KBEASOLL>1</KBEASOLL>
<KEINH>EA</KEINH>
<KRUEREST>0</KRUEREST>
<KRUESOLL>1</KRUESOLL>
<ARBID></ARBID>
<FSTAD>20171113</FSTAD>
<FSTAU>154213</FSTAU>
<FENDD>20180513</FENDD>
<FENDU>131115</FENDU>
<SPLIT>01</SPLIT>
<MGVRG>40</MGVRG>
<MEINH>EA</MEINH>
</E1KBEDL>
</E1PLOPL>
<E1RESBL SEGMENT="1">
<AUSCH>20.12</AUSCH>
<AVOAU>20.12</AVOAU>
<BDART>AR</BDART>
<BDMNG>13</BDMNG>
<BDTER>20161113</BDTER>
<BEIKZ>K</BEIKZ>
<CHARG>0101</CHARG>
<DBSKZ>E</DBSKZ>
<ENMNG>4</ENMNG>
<FMENG>X</FMENG>
<LGORT>1212</LGORT>
<MATNR>121212</MATNR>
<MEINS>EA</MEINS>
<NETAU></NETAU>
<SBTER>20161113</SBTER>
<SCHGT>X</SCHGT>
<SOBKZ>O</SOBKZ>
<UPSKZ>X</UPSKZ>
<VERTI>X</VERTI>
<VMENG>4</VMENG>
<WERKS>0004</WERKS>
<SHKZG>X</SHKZG>
<POSNR>0010</POSNR>
<MATNR_EXTERNAL>121212</MATNR_EXTERNAL>
<MATNR_VERSION></MATNR_VERSION>
<MATNR_GUID></MATNR_GUID>
<RSNUM>0010</RSNUM>
<RSPOS>1</RSPOS>
<RSART></RSART>
<ALPOS></ALPOS>
<ALPGR></ALPGR>
<ALPRF></ALPRF>
<ALPOS></ALPOS>
<EWAHR></EWAHR>
<NOMNG>4</NOMNG>
<DUMPS></DUMPS>
<AUFST>s1</AUFST>
<AUFWG>s1</AUFWG>
<BAUST></BAUST>
<BAUWG></BAUWG>
<MRPOS></MRPOS>
<POSTP>1</POSTP>
<AFPOS></AFPOS>
<STLNR>00038723</STLNR>
<STLKN>0121</STLKN>
<STPOZ>01</STPOZ>
<ASQTY></ASQTY>
<MATNR_LONG></MATNR_LONG>
<LGNUM>01</LGNUM>
<PRVBE>2</PRVBE>
</E1RESBL>
</E1PLAFL>
</IDOC>
</LOIPLO02>
