Demand Pegging Relationships (tcibd4520m000)
Use this session to display the demand pegging relationships between combinations of Parent Business Object Type, Parent Business Object, and Parent Business Object Reference.
In this session, all business object combinations are displayed with the same specification (demand pegging data) as is linked to the parent business object combination from the header. The specification is displayed in the Allocated to group box.
On the appropriate menu, you can click
to only display purchase orders and production orders with the same specification as the parent business object combination from the header.Field Information
- Parent Business Object Type
-
The parent business object type for which the demand pegging relationships are displayed.
- Parent Business Object
-
The parent business object ID for which the demand pegging relationships are displayed.
- Parent Business Object Reference
-
The order or order line for which the demand pegging relationships are displayed.
- Sold-to Business Partner
-
The supply that fills the demand must have been allocated or hard pegged to the sold-to business partner displayed in this field.
LN uses this characteristic to find a matching supply for this demand.
- Business Object Type
-
The supply that fills the demand must have been allocated or hard pegged to the type of order displayed in this field.
LN uses this characteristic to find a matching supply for this demand.
Note:The following fields are always used in combination; together, they identify the relevant order or order line:
- Business Object Type
- Business Object
- Business Object Reference
Allowed values
- Service (Manual)
- Maintenance Sales Order
- Maintenance Sales (Manual)
- Maintenance Work Order
-
maintenance order
- Maintenance Work Order (Manual)
- Sales Order
- Sales Schedule
- Not Applicable
- Sales (Manual)
- Service Order
- Business Object
-
The supply that fills the demand must have been allocated or hard pegged to the order, or order line, displayed in this field.
LN uses this characteristic to find a matching supply for this demand.
Note:The following fields are always used in combination; together, they identify the relevant order or order line:
- Business Object Type
- Business Object
- Business Object Reference
- Business Object Reference
-
The supply that fills the demand must have been allocated or hard pegged to the order, or order line, displayed in this field.
LN uses this characteristic to find a matching supply for this demand.
Note:The following fields are always used in combination; together, they identify the relevant order or order line:
- Business Object Type
- Business Object
- Business Object Reference
- Reference
-
The supply that fills the demand must have been allocated or hard pegged to the reference code displayed in this field.
LN uses this characteristic to find a matching supply for this demand.
LN can use this field in two ways:
- If the Sold-to Business Partner field is filled, LN uses the Reference field to record a reference code defined by a customer.
- If the Sold-to Business Partner field is empty, LN uses the Reference field to record an internal reference.
You can use a reference code to keep a collection of parts linked together, even if they follow different routings, for example, if some of the parts are transported to a subcontractor to be returned later.
- Use Unallocated Inventory
-
If this check box is selected, unallocated inventory can be allocated and used to supply the demand order. First, allocated inventory is used, then unallocated inventory.
If this check box is cleared, only allocated inventory can be used.
- Parent Business Object Type
-
The object type with the same specification as the parent business object combination from the header.
Note:The following fields are always used in combination; together, they identify the relevant order or order line:
- Parent Business Object Type
- Parent Business Object
- Parent Business Object Reference
- Parent Business Object
-
The business object ID with the same specification as the parent business object combination from the header.
Note:The following fields are always used in combination; together, they identify the relevant order or order line:
- Parent Business Object Type
- Parent Business Object
- Parent Business Object Reference
- Parent Business Object Reference
-
The order or order line with the same specification as the parent business object combination from the header.
Note:The following fields are always used in combination; together, they identify the relevant order or order line:
- Parent Business Object Type
- Parent Business Object
- Parent Business Object Reference