| Purchase Contract Line Logistic Data (tdpur3102m000) |  |
| Use this session to 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 in the Purchase Contract Lines (tdpur3101m000) session is selected. You can only change inactive purchase contract line logistic data. To activate the purchase contract line logistic data, choose Activate. The status is changed to Active. To deactivate the purchase contract line logistic data, choose De-activate. The status is changed to Free. Note All fields in this session are defaulted from the corresponding fields in the Items - Purchase Business Partner (tdipu0110m000) session. Related topics To set up contract line logistic data Purchase contracts Overview of purchase schedule handling
Fields | Description
Contract | Purchase contracts are used to register specific agreements with a buy-from business partner that concern the delivery of specific goods. A contract is comprised of: A purchase contract header with general business partner data, and optionally, a linked terms and conditions agreement. One or more purchase contract lines with price/discount agreements and quantity information that apply to an item or price group.
Position | The number of the purchase contract line
Purchase Office | A department in your organization that is responsible for buying the materials and services needed by your organization. You assign number groups to the purchase office. In this way, you can assign serial numbers to: Purchase orders Purchase schedules Requests for quotations Purchase contracts You can also define a default warehouse where goods ordered by the purchase office must be delivered.
Status | The status of the logistic record, which can be Free, or Active. You can assign a status to the logistic record by use of the following buttons: Activate. De-activate. You can only activate a contract line in the Purchase Contract Lines (tdpur3101m000) session if at least one logistic record is active for the contract line in the current session.
Item | In ERP LN, the raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, sold, and so on. An item can also represent a set of items handled as one (kit), or exist in multiple product variants (generic item). You can also define nonphysical items, which are not held in inventory but can be used to post costs or to invoice services to customers. Examples of nonphysical items: Cost items (for example, electricity) Service items Subcontracting services List items (menus/options)
Preferred | Use this field to indicate whether the business partner is preferred or fixed for the item. Allowed values Possible Values
Priority | An option that enables you to add a certain rating for suppliers. If the priority is defined, the item/supplier combinations are sorted according to descending priority. Allowed values The allowed values range from 0, which is the highest priority, to 999, which is the lowest priority. Related topics To use priorities Sourcing
Sourcing Percentage | A percentage used to calculate how orders are divided among suppliers. Note This parameter has no effect on the planning algorithms in Warehouse Management. Related topics Sourcing To use sourcing percentages
Freezing Time Increase | The number of days, calculated from the current date, for which you can no longer increase the quantity of required items. If the purchase schedule is Shipment Based, which you can define in the Shipment or Delivery Based field of the current session, frozen time limits are based on planned shipment dates. If the schedule is Delivery Based, frozen time limits are based on planned delivery dates. Related topics Constraints for generating non-referenced purchase schedule lines
Frozen Period (-) | The number of days, calculated from the current date, for which you can no longer reduce the quantity of required items. If the purchase schedule is Shipment Based, which you can define in the Shipment or Delivery Based field of the current session, frozen time limits are based on planned shipment dates. If the schedule is Delivery Based, frozen time limits are based on planned delivery dates. Related topics Constraints for generating non-referenced purchase schedule lines
Supplier Capacity | ship-from business partner capacity.
Capacity Time Unit | The time unit in which the ship-from business partner capacity is expressed.
Minimum Capacity Tolerance | The minimum percentage that can stay below ship-from business partner capacity.
Maximum Capacity Tolerance | The maximum percentage that can exceed ship-from business partner capacity. The maximum capacity tolerance is calculated as follows:
                                        Maximum Capacity Tolerance x 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 | An organization that provides transport services. You can link a default carrier to both ship-to and ship-from business partners. In addition, you can print sales and purchase orders on a packing list, sorted by carrier. For ordering and invoicing, you must define a carrier as a business partner.
Internal Processing Time | The time required between the recognition of needs and the release of the purchase order. Internal processing time includes document preparation and sourcing. Note If purchase schedules are automatically generated by Enterprise Planning, this field is only used in the supplier selection process. Enterprise Planning uses this field, together with the the Safety Time field and the Supply Time field, to assign a priority to suppliers who can deliver the required item. Related topics To calculate purchase item lead time To determine the planned receipt date Distribution lead time based on the supply calendar Overview of purchase schedule handling Push schedules Pull forecast schedules
Internal Proc. Time | The unit in which the internal processing time is expressed.
Safety Time | The time that you can add to the normal lead time to protect delivery of goods against fluctuations in the lead time so that an order can be completed before the order's real need date. Note If purchase schedules are automatically generated by Enterprise Planning, this field is only used in the supplier selection process. Enterprise Planning uses this field, together with the the Internal Processing Time field and the Supply Time field, to assign a priority to suppliers who can deliver the required item. Related topics To calculate purchase item lead time To determine the planned receipt date Distribution lead time based on the supply calendar Overview of purchase schedule handling Push schedules Pull forecast schedules
Safety Time | The unit in which the safety time is expressed.
Supply Time | The total time required to obtain a purchased item. This time includes order document preparation, sourcing, and supplier lead time. Note If purchase schedules are automatically generated by Enterprise Planning, this field is only used in the supplier selection process. Enterprise Planning uses this field, together with the the Internal Processing Time field and the Safety Time field, to assign a priority to suppliers who can deliver the required item. Related topics To calculate purchase item lead time To determine the planned receipt date Distribution lead time based on the supply calendar Overview of purchase schedule handling Push schedules Pull forecast schedules
Supply Time | The unit in which the supply time is expressed.
Lead Time Horizon | The number of days that, together with the current date/generation date, determines whether: ERP LN uses the calculated lead time to determine the planned receipt date. ERP 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. ERP LN determines the planned receipt date, taking into account the calendars that are related to the lead time components. ERP 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. Related topics To determine the planned receipt date To calculate purchase item lead time Purchase lead time calculation Distribution lead time based on the supply calendar
Transportation Time (Days) | The transportation time in days, which can be calculated in two ways. ERP LN retrieves the transportation time as follows: If Freight Management 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. ERP LN performs the following steps to retrieve the transportation time. If the route, the carrier, the origin, and the destination addresses are known, ERP LN first searches for route plan s and then for standard routes with matching routes, carriers, and addresses. If more than one matching route plan or standard route is found, ERP LN selects the route plan or standard route with a transport means group that matches the transport means group of the carrier. If ERP 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 ERP LN still finds more than one route plan, it selects the first one it encounters in the database. If Freight Management is not implemented, ERP 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. Related topics To calculate purchase item lead time To determine the planned receipt date Distribution lead time based on the supply calendar
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, ERP LN (re)calculates the calculated lead time. Related topics To calculate purchase item lead time Purchase lead time calculation
Inbound Lead Time | The time interval between the arrival of the items and the actual storage in the warehouse. In this session, this field is displayed for information purposes only.
Inbound Lead Time | The unit in which the inbound lead time is expressed.
Receipt Date Tolerance (+) | The number of days late that a supplier can make a delivery. In purchase scheduling, tolerances are only used for pull call-off schedules. Note For push schedules, you cannot use order tolerances. The reason for this is that receipts are made on blanket warehouse orders in Warehouse Management. As a result, the quantities received are checked by Purchase Control and not by Warehouse Management. Related topics Push schedules Pull call-off schedules Blanket warehousing orders
Receipt Date Tolerance (-) | The number of days early that a supplier can make a delivery. In purchase scheduling, tolerances are only used for pull call-off schedules. Note For push schedules, you cannot use order tolerances. The reason for this is that receipts are made on blanket warehouse orders in Warehouse Management. As a result, the quantities received are checked by Purchase Control and not by Warehouse Management. Related topics Push schedules Pull call-off schedules Blanket warehousing orders
Receipt Quantity Tolerance (+) | The maximum quantity that a supplier can deliver. The maximum quantity tolerance is expressed as a percentage of the ordered quantity. ERP LN uses the Receipt 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
Receipt 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. In purchase scheduling, tolerances are only used for pull call-off schedules. Note For push schedules, you cannot use order tolerances. The reason for this is that receipts are made on blanket warehouse orders in Warehouse Management. As a result, the quantities received are checked by Purchase Control and not by Warehouse Management. Related topics Push schedules Pull call-off schedules Blanket warehousing orders
Receipt Quantity Tolerance (-) | minimum quantity tolerance (-). ERP LN uses the Receipt 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
Receipt 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. In purchase scheduling, tolerances are only used for pull call-off schedules. Note For push schedules, you cannot use order tolerances. The reason for this is that receipts are made on blanket warehouse orders in Warehouse Management. As a result, the quantities received are checked by Purchase Control and not by Warehouse Management. Related topics Push schedules Pull call-off schedules Blanket warehousing orders
Release Type | Use this field to indicate what schedule release type is used, based on which an EDI message is sent. This message is indicated by the used schedule. Allowed values See Schedule Release Detail Related topics Purchase schedule release types To use segment sets
Transaction Time Fence | This field indicates for which purchase schedule lines inventory transactions must be logged in the Inventory Handling module of Warehouse Management, and financial transactions must be logged in the General Ledger module, and the Accounts Payable module 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 related to push schedules and not to pull schedules. Note Even if a purchase schedule line falls outside the FAB period, transactions are still logged for the schedule line as soon as 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 Possible Values Related topics To log transactions for purchase schedule lines
Communication Channel | The way in which purchase releases must be communicated to the business partner. Related topics Purchase releases
Release EDI Message Directly | If the value of the Communication Channel field is EDI, and If this check box is selected, EDI messages are prepared at the moment 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 in the Purchase Releases (tdpur3120m000) session is Scheduled. If the status is Preview, the messages are not sent until the status becomes Scheduled. At the moment Electronic Commerce sends the EDI messages to the supplier, a purchase release receives the status Sent. Related topics Purchase releases
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. If the value of the Release Type field is Shipping Schedule Only, you cannot enter a segment set in this field. Related topics pull schedules To use segment sets
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 value of the Release Type field is Material Release, you cannot enter a segment set in this field. Related topics To use segment sets
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. If the value of the Release Type field is Shipping Schedule Only, you cannot enter an issue pattern in this field. Related topics pull schedules Overview of purchase schedule handling To cluster purchase schedule lines Purchase releases
Issue Pattern for Shipping Schedule | The pattern used to determine the issue date for shipping schedule. 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 value of the Release Type field is Material Release, you cannot enter an issue pattern in this field. Related topics Overview of purchase schedule handling Purchase releases
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 as soon as: A purchase release receives the status Sent. The cumulatives are reset in the Reset Cumulatives (tdpur3230m000) session. Related topics Authorizations To reset authorizations Purchase releases
FAB Period | The time period during which the supplier is authorized to manufacture the goods required on a schedule, calculated from the schedule issue date on for push schedules, and from the current date on for pull forecast schedules. The fab period is expressed in a number of days. Example CUM start quantity: 10000 Schedule issue date/current date: 05.07.99 Fab period: 20 days
Issue/current date | Quantity
05.07.99 | 100
12.07.99 | 100
19.07.99 | 100
26.07.99 | 100
    Fab time fence   : 05.07.99 (+ 20 days) = 25.07.99.
    Fab authorization: 10000 + 100 + 100 + 100 = 10300.
Related topics Authorizations
RAW Period | The time period during which the supplier is authorized to procure the raw materials required on a schedule, calculated from the schedule issue date on for push schedules, and from the current date on for pull forecast schedules. The raw period is expressed in a number of days. Example CUM start quantity: 10000 Schedule issue date/current date: 05.07.99 Raw period: 20 days
Issue/current date | Quantity
--- | ---
05.07.99 | 100
12.07.99 | 100
19.07.99 | 100
26.07.99 | 100
    Raw time fence   : 05.07.99 (+ 20 days) = 25.07.99.
    Raw authorization: 10000 + 100 + 100 + 100 = 10300.
Related topics Authorizations
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 See Possible Values Related topics Authorizations To reset authorizations
Package Definition | The package definition for the item or item group. Related topics Packaging levels
Shipment or Delivery Based | Use this field to define on what date and time (schedule) requirements are based. You have the following options: Shipment Based: the (schedule) requirement is based on the date and time you pick the goods up at the ship-from business partner 's warehouse. As a result, time calculations are based on the planned shipment date. Delivery Based: the (schedule) requirement is based on the date and time you want the goods to be delivered at your warehouse by the business partner. As a result, time calculations are based on the planned delivery date. Note Although the value of this field is defaulted to the Shipment/Delivery Based field of the Purchase Schedules (tdpur3110m000) session, you can change the value of this field in the Purchase Schedules (tdpur3110m000) session.