Purchase Contract Line Logistic Data (tdpur3102m000)
Use this session to view, enter, and maintain logistic agreements for a purchase contract line.
The purchase contract line logistic data provides default values to the purchase schedule that is linked to the purchase contract line.
You can only maintain purchase contract line logistic data if the Purchase Schedule in use check box is selected in the Purchase Contract Lines (tdpur3101m000) session.
To activate the purchase contract line logistic data, choose Activate. The Active check box is selected. To de-activate the purchase contract line logistic data, choose De-activate. The Active check box is cleared.
The fields in this session are defaulted from the corresponding fields in the Items - Purchase Business Partner (tdipu0110m000) session.
If the contract is a corporate purchase contract, many fields are disabled in this session. Logistic agreements are specified by purchase contract line detail in the Purchase Contract Line Logistic Detail Line (tdpur3102m100) session.
Field Information
- Contract
- Line
-
The number of the purchase contract line.
- Purchase Office
- Active
-
If this check box is selected, the logistic agreement is active.
If this check box is cleared, the logistic agreement is inactive. You can update the agreement.
You can activate a contract line in the Purchase Contract Lines (tdpur3101m000) session only if at least one logistic agreement is active for the contract line.
- Item
- Preferred
-
Use this field to indicate whether the business partner is preferred or fixed for the item.
Allowed values
- Single Source
-
Only one buy-from business partners can be fixed for this item.
- Preferred
-
One or several buy-from business partner can be preferred for this item.
- Priority
-
Allowed values
The allowed values range from 0, which is the highest priority, to 999, which is the lowest priority.
- Sourcing Percentage
-
Note: This parameter has no effect on the planning algorithms in Warehousing .
- Freezing Time Increase
-
If the purchase schedule is Shipment Based, which you can define in the Shipment or Receipt Based field of the current session, frozen time limits are based on planned shipment dates. If the schedule is Receipt Based, frozen time limits are based on planned receipt dates.
- Frozen Period (-)
-
If the purchase schedule is Shipment Based, which you can define in the Shipment or Receipt Based field of the current session, frozen time limits are based on planned shipment dates. If the schedule is Receipt Based, frozen time limits are based on planned receipt dates.
- Use Working Days for Frozen Period
-
If this check box is selected, only working days are used when calculating frozen periods.
If this check box is cleared, calendar days are used when calculating frozen periods.
Note:If this check box is selected, the specified number of working days is added to the current date. The working days are retrieved from the calendar that is linked to the ship-from business partner, the buy-from business partner, or the company.
If this check box is cleared, the specified number of calendar days is added to the current date.
When planning the dates, the availability type from the Procurement Parameters (tdpur0100m000) session is used.
- Delete Past Schedule Lines
-
This check box determines how to handle undelivered and redundant quantities on schedule lines with dates in the past.
If this check box is selected, the schedule lines are deleted by Enterprise Planning .
If this check box is cleared, planning messages are generated informing a planner to manually delete the schedule lines.
Note: This check box can be selected only if the Frozen Period for Decreasing Quantity is zero in the current session. - Supplier Capacity
- Capacity Time Unit
- Minimum Capacity Tolerance
- Maximum Capacity Tolerance
-
The maximum capacity tolerance is calculated as follows:
Maximum Capacity Tolerance * Supplier Capacity + Supplier Capacity
Example
- Supplier capacity: 100 pieces.
- Maximum capacity tolerance: 20 (percent).
- Capacity time unit: week.
Enterprise Planning takes into account that the supplier can only deliver a maximum number of 120 pieces a week.
- Carrier/LSP
- Internal Processing Time
-
Note: If purchase schedules are automatically generated by Enterprise Planning , this field is used in the supplier selection process. Enterprise Planning uses this field, together with the Safety Time and Supply Time fields, to assign a priority to suppliers who can deliver the required item.
- Unit for Internal Processing Time
-
The unit in which the internal processing time is expressed.
- Safety Time
-
Note: If purchase schedules are automatically generated by Enterprise Planning , this field is used in the supplier selection process. Enterprise Planning uses this field, together with the Internal Processing Time and Supply Time fields, to assign a priority to suppliers who can deliver the required item.
- Unit for Safety Time
-
The unit in which the safety time is expressed.
- Site
- The code of the site.Note: This field is displayed for the Contract Line types, Detail and Contract Line.
- Generate Supply Orders Automatically
- Indicates if the supply orders are created automatically after a
planning run. This check box is only visible if the Item is not specified with the Item Type, Product or Tool and the Purchase Schedule in use check box is selected in the Item - Purchase (tdipu0601m000) session.Note: This field is only enabled if the
- Subcontracting with Purchase Schedules check box is selected in the Purchase Schedule Parameters (tdpur0100m500) session.
- Subcontracting with Material Flow check box is selected in the Implemented Software Components (tccom0100s000) session.
- Warehouse Order Type for Supply Orders
- The type of warehouse order. This field is only enabled if
the
- Subcontracting with Material Flow check box is selected in the Implemented Software Components (tccom0100s000) session.
- Item is not specified with the Item Type, Product or Tool.
- warehouse order type is Transfer in the Warehousing Order Types (whinh0110m000) session.
- Time Frame for Combining Supply Orders
- Indicates the number of time units that are combined into a single
supply order.
- Subcontracting with Material Flow check box is selected in the Implemented Software Components (tccom0100s000) session.
- Item is not specified with the Item Type, Product or Tool.
- Time Frame Unit for Combining Supply Orders
-
The unit in which the Time Frame for Combining Supply Orders is measured.
Allowed values
- Days
- Hours
Note: This check box is only enabled if the- Subcontracting with Material Flow check box is selected in the Implemented Software Components (tccom0100s000) session.
- Item is not specified with the Item Type, Product or Tool.
- Supply Time
-
Note: If purchase schedules are automatically generated by Enterprise Planning , this field is used in the supplier selection process. Enterprise Planning uses this field, together with the Internal Processing Time and Safety Time fields, to assign a priority to suppliers who can deliver the required item.
- Unit for Supply Time
-
The unit in which the supply time is expressed.
- Full Supply Time
-
Note: This field is visible only if the Use Full Supply Time check box is selected in the Procurement Parameters (tdpur0100m000) session.
- Unit for Full Supply Time
-
The unit in which the full supply time is expressed.
Note: This field is visible only if the Use Full Supply Time check box is selected in the Procurement Parameters (tdpur0100m000) session. - Lead Time Horizon
-
The number of days that, together with the current date/generation date, determines whether:
- LN uses the calculated lead time to determine the planned receipt date. LN uses this calculation when the date for which the lead time is calculated, falls outside the lead time horizon. Planned dates are calculated using the value from the Calculated Lead Time (Days) field, which is derived from the company's calendar.
- LN determines the planned receipt date, taking into account the calendars that are related to the lead time components. LN uses this calculation when the date for which the lead time is calculated, lies between the current date and the lead time horizon. Planned dates are calculated using the individual lead time components with the components' respective calendars.
- Transportation Time (Days)
-
The transportation time in days, which can be calculated in two ways.
LN retrieves the transportation time as follows:
- If
Freight
is implemented, which you can define in the Implemented Software Components (tccom0500m000) session, calculation of the transportation time is based on carrier, and routes. Route plans and service levels are not known at this point in time.
LN performs the following steps to retrieve the transportation time.
- If the route, the carrier, the origin, and the destination addresses are known, LN first searches for route plans and then for standard routes with matching routes, carriers, and addresses.
- If more than one matching route plan or standard route is found, LN selects the route plan or standard route with a transport means group that matches the transport means group of the carrier.
- If LN still finds more than one route plan or standard route, route plans have priority over standard routes. If only standard routes are found, the standard route is selected following the settings of the Carrier/LSP Selection Criterion parameter in the Freight Planning Parameters (fmlbd0100m000) session.
- If LN still finds more than one route plan, it selects the first one it encounters in the database.
- If Freight is not implemented, LN takes the transportation time between the ship-from business partner's address and the receiving warehouse's address, based on a relevant distance table (if available) in the Distance Table by City (tccom4137s000) session or in the Distance Table by ZIP Code/Postal Code (tccom4138s000) session. From which of these two sessions the transportation time is retrieved, depends on the value of the Usage Distance Tables field in the COM Parameters (tccom0000s000) session.
- If
Freight
is implemented, which you can define in the Implemented Software Components (tccom0500m000) session, calculation of the transportation time is based on carrier, and routes. Route plans and service levels are not known at this point in time.
- Calculated Lead Time (Days)
-
The rough purchase item lead time expressed in days. The calculated lead time is only used to determine the planned receipt date of forecast demand for which no accurate determination of the planned receipt date is yet required.
The calculated lead time is based on the availability type and calendar template that are linked to the following fields:
- Supply Time
- Internal Processing Time
- Safety Time
- Transportation Time (Days)
Note: Each time you open or close the current session, LN (re)calculates the calculated lead time. - Calculated Full Lead Time (Days)
-
The rough purchase full item lead time expressed in days.
The calculated full lead time is based on the availability type and calendar template that are linked to the following fields:
- Full Supply Time
- Internal Processing Time
- Safety Time
- Transportation Time (Days)
Note:- This field is visible only if the Use Full Supply Time check box is selected in the Procurement Parameters (tdpur0100m000) session.
- Each time you open or close the current session, LN (re)calculates the calculated full lead time.
- Inbound Lead Time
-
In this session, this field is displayed for information purposes only.
- Inbound Lead Time
-
The unit in which the inbound lead time is expressed.
- Date Tolerance (+)
-
Note: This tolerance is used for pull call-off schedules and the push schedules.
- Date Tolerance (-)
-
Note: This tolerance is used for pull call-off schedules and the push schedules.
- Hard Stop on Date
-
Indicates the action performed by LN when the date tolerances are exceeded.
Allowed values
- No
-
You always can save the outbound advice, because LN ignores the set tolerances.
- Warn
-
You can save the outbound advice, but you receive a warning if the tolerances are not met.
- Block
-
You cannot save the outbound advice if the tolerances are not met.
Note:- This field is enabled only if the Active check box is cleared.
- For a Detail contract line, LN defaults this value from the Items - Purchase Business Partner (tdipu0110m000) session. If the value is not defined in this session, LN defaults this value from the related Total line.
- Quantity Tolerance (+)
-
maximum quantity tolerance (+)
LN uses the Quantity Tolerance (+) to determine the default value of the Maximum Quantity Tolerance field in the Warehousing Orders (whinh2100m000) session as follows:
Max. Quantity Tolerance = 100 + Quantity Tolerance (+)
EXAMPLE
Quantity Tolerance (-) = 10% Minimum Quantity Tolerance = 100% + 10% = 110% Ordered quantity 200 In this case you do not accept receipts with a quantity over 220.
Note:For push schedules, the tolerated over-receipt quantity is calculated as follows:
- If blanket warehouse orders are used, the ordered quantity of the entire schedule is used for the calculation.
- If receipts are made in Purchase Control , the ordered quantity of the schedule line yet to be received, is used for the calculation.
The receipt quantity that exceeds the ordered quantity is added to the last schedule line.
- Quantity Tolerance (-)
-
minimum quantity tolerance (-).
LN uses the Quantity Tolerance (-) to determine the default value of the Minimum Quantity Tolerance field in the Warehousing Orders (whinh2100m000) session as follows:
Minimum Quantity Tolerance = 100 - Quantity Tolerance (-)
EXAMPLE
Quantity Tolerance (-) = 10% Minimum Quantity Tolerance = 100% - 10% = 90% Ordered quantity 200 In this case you do not accept receipts with a quantity less than 180.
Note: This tolerance is used for pull call-off schedules and the push schedules. - Hard Stop on Quantity
-
Indicates the action performed by LN when the quantity tolerances are exceeded.
Allowed values
- No
-
You always can save the outbound advice, because LN ignores the set tolerances.
- Warn
-
You can save the outbound advice, but you receive a warning if the tolerances are not met.
- Block
-
You cannot save the outbound advice if the tolerances are not met.
Note:- This field is enabled only if the Active check box is cleared.
- For a Detail contract line, LN defaults this value from the Items - Purchase Business Partner (tdipu0110m000) session. If the value is not defined in this session, LN defaults this value from the related Total line.
- Use Material Release
-
If this check box is selected, you can send material releases with forecasting data.
- Use Material Release for Firm Requirements
-
If this check box is selected, you can send material releases that contain the actual order.
Note: You can only select this check box if the Use Material Release check box is also selected. - Use Shipping Schedule
-
If this check box is selected, you can send shipping schedules.
Note: You cannot select this check box if the Use Material Release for Firm Requirements check box is selected. - Use Sequence Shipping Schedule
-
If this check box is selected, you can send sequence shipping schedules.
Note: You cannot select this check box if the Use Material Release for Firm Requirements check box is selected. - Schedule Type
-
The type of purchase schedule, which can be push schedule or pull schedule.
- Update Direct Delivery Sales Schedule Automatically after Receipt
-
If this check box is selected, the sales schedule for direct delivery is updated automatically after the receipt of the purchased item.
- Transaction Time Fence
-
This field indicates for which purchase schedule lines inventory transactions must be logged in Warehouse Orders of Warehousing , and financial transactions must be logged in General Ledger and Accounts Payable of Financials .
Irrespective of the chosen parameter:
- Inventory transactions and financial transactions are always logged for pull call-off schedules.
- No transactions are logged for pull forecast schedules. As a result, this parameter is only applicable for push schedules and not for pull schedules.
Note: Even if a purchase schedule line is outside the FAB period, transactions are still logged for the schedule line when its requirement type becomes Firm.Performance aspects
The setting of this field could affect system performance and database growth. For more information, refer to Transaction time fence.
Allowed values
- All Lines
-
Transactions are logged for the entire schedule.
- Lines in the FAB Period
-
Transactions are logged for the FAB period.
- Lines in the Firm Period
-
Transactions are logged for the period authorized for shipment (firm period).
- Communication Channel
-
The way in which purchase releases must be communicated to the business partner.
- Release EDI Message Directly
-
If the Communication Channel field is set to EDI and this check box is selected, EDI messages are prepared when a purchase release receives the status Scheduled in the Purchase Releases (tdpur3120m000) session.
If this check box is cleared, you can prepare EDI messages by selecting the Prepare EDI messages check box in the Print Purchase Releases (tdpur3422m000) session.
Note:- Electronic Commerce can only send the generated EDI messages to the supplier if the status of the purchase release is Scheduled in the Purchase Releases (tdpur3120m000) session. If the status is Created, the messages are not sent until the status becomes Scheduled.
- When Electronic Commerce sends the EDI messages to the supplier, a purchase release receives the status Sent.
- Field for Last Shipment
-
The shipment related field in LN that is used in the Purchase Release (OUT) Business Object Document (BOD).
Allowed values
- Last Supplier's ASN
-
The latest advance shipment notice (ASN) received from the supplier is included in the BOD.
- Packing Slip
-
The packing slip linked to the latest receipt is included in the BOD.
- Last Shipment ID
-
The number of the latest shipment ID is included in the BOD.
- Segment Set for Material Release
-
The segment set used for material releases.
Note: A segment set for material release is only used in push schedules and pull forecast schedules. For pull call-off schedules, no segment sets are used. - Segment Set for Shipping Schedule
-
The segment set used for shipping schedules.
Note:- A segment set for shipping schedule is only used in push schedules. For pull schedules, this segment set is not used.
- If the Use Material Release for Firm Requirements check box is selected, you cannot enter a segment set in this field.
- Issue Pattern for Material Release
-
The pattern used to determine the issue date for material releases.
Note: An issue pattern for material release is only used in push schedules and pull forecast schedules. In case of pull call-off schedules, no issue patterns are used. - Description
-
The description of the issue pattern.
- Issue Pattern for Shipping Schedule
-
The pattern used to determine the issue date for shipping schedules.
Note:- An issue pattern for shipping schedule is only used in push schedules. In case of pull schedules, this issue pattern is not used.
- If the Use Material Release for Firm Requirements check box is selected, you cannot enter an issue pattern in this field.
- Authorizations
-
If this check box is selected, authorizations are used and calculated.
Authorizations for the schedule are updated in the FAB/RAW Authorizations (tdpur3534m000) session when:
- A purchase release receives the Sent status
- The cumulatives are reset in the Reset Cumulatives (tdpur3230m000) session
- FAB Period
-
- RAW Period
-
- Authorizations to be
-
This field indicates whether the high fab authorizations and high raw authorizations must be carried forward or reset when the cumulatives (CUMs) are reset in the Reset Cumulatives (tdpur3230m000) session.
Allowed values
- Carried Forward
-
The high FAB authorizations and high RAW authorizations are reduced by the reset quantity.
- Reset
-
The high FAB authorizations and high RAW authorizations are equalized to the FAB authorization and RAW authorization values.
- Package Definition
-
The package definition for the item.
- Shipment or Receipt Based
-
Specify on what date and time (schedule) requirements are based.
Note: The value of this field is defaulted to the Shipment/Receipt Based field of the Purchase Schedules (tdpur3110m000) session.Allowed values
- Shipment Based
-
The (schedule) requirements are based on the date and time you pick the goods up at the ship-from business partner 's warehouse (purchase) or on the date and time the goods must be shipped to the ship-to business partner (sales). As a result, time calculations are based on the planned shipment date.
- Receipt Based
-
The (schedule) requirement are based on the date and time you want the goods to be delivered at your warehouse by the business partner (purchase) or on the date and time your ship-to business partner needs the goods at the warehouse (sales). As a result, time calculations are based on the planned delivery date.