Purchase Contract Line Logistic Detail Line (tdpur3102m100)
Use this session to view, enter, and maintain logistic agreements for a purchase contract line detail.
The purchase contract line logistic detail data provides default values to the purchase schedule that is linked to the purchase contract line detail.
You can only change logistic agreements with the Free status. A purchase contract line logistic detail line has the same status as its parent purchase contract line logistic data for which the status can be changed in the Purchase Contract Line Logistic Data (tdpur3102m000) session.
Field Information
- Contract
-
The number of the corporate purchase contract.
- Contract Status
-
The status of the logistic record, which can be Free, or Active.
Note: A purchase contract line logistic detail line has the same status as its parent purchase contract line logistic data for which the status can be changed in the Purchase Contract Line Logistic Data (tdpur3102m000) session. - Line
-
The number of the purchase contract line.
- Purchase Office
-
The logistic company of the purchase office, site, receiving site and warehouse.
- Purchase Office
-
The code of the purchase office.
Note:- You must specify this value, if the contract line is of the type Detail and the Use Corporate Purchase Contracts check box is cleared.
- This field is enabled, when the Purchase Office is set to a value other than zero.
- This value is defaulted for the specified logistic company.
- This value cannot be modified, if the contract line is of the type Detail.
- Purchase Office
-
purchase office
- Sequence
-
The number of the purchase contract line detail.
- Item
-
item
- Site
-
The code of the site.
- Date Tolerance (+)
-
delivery date tolerance (+)
Note: This tolerance is used for pull call-off schedules and the push schedules. - Date Tolerance (-)
-
delivery 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 Infor 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, Infor LN defaults this value from the Items - Purchase Business Partner (tdipu0110m000) session. If the value is not defined in this session, Infor 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 Infor 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, Infor LN defaults this value from the Items - Purchase Business Partner (tdipu0110m000) session. If the value is not defined in this session, Infor LN defaults this value from the related Total line.
- Carrier/LSP
-
carrier
- Internal Processing Time
-
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
-
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.
- Supply Time
-
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.
- 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. - Full Supply Time
-
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. - 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.
- 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
-
inbound lead time
In this session, this field is displayed for information purposes only.
- Inbound Lead Time Unit
-
The unit in which the inbound lead time is expressed.
- 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.
- Issue Pattern for Material Release
-
The pattern used to determine the issue date for material releases.
- 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 in the Purchase Contract Line Logistic Data (tdpur3102m000), you cannot enter an issue pattern in this field.
- Schedule Type
-
The type of purchase schedule, which is always push schedule in this session.
- 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.
- Freezing Time Increase
-
frozen zone+
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 (-)
-
frozen zone-
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. - Package Definition
-
The package definition for the item.