| | Purchase Contract Line Logistic Data (tdpur3102m000)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. 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. 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 (central) price
agreements, logistic agreements, and quantity information that apply to an item
or price group.
- Purchase contract line details with logistic agreements and
quantity information that apply to an item or price group for a specific site
(warehouse) of a multisite corporation. Contract line details can exist only
for corporate purchase contracts.
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: 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 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. 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.
The following are 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. 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. Sourcing Percentage A percentage used to calculate how orders are divided among
suppliers. Note This parameter has no effect on the planning algorithms in Warehousing. Frozen Period (+) 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/Delivery 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 (-) 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/Delivery 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 selected, 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 selected, the specified number of
calendar days is added to the current date. When planning the dates, the availability type from the Purchase Parameters (tdpur0100m000) session is used. Capacity Time Unit The time unit in which the ship-from business partner capacity
is expressed. Min. Capacity Toler. The minimum percentage that can stay below ship-from business
partner capacity. Max. Capacity Toler. The maximum percentage that can exceed ship-from business
partner capacity. 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 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 Proc. 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 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. 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 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. Supply Time The total time required to obtain an item that is forecasted.
This time is used to calculate an item's order lead time, based on which a
company takes commitment decisions and executes capacity planning and order
management. Example For item A, the supplier communicated a supply
time of 50 days. This is in fact a reduced lead time and is only
possible because a three year forecast is sent to the supplier for this item.
If additional quantities are needed, which are not included in the forecast,
the supplier needs the full supply time, which is 300
days. 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. Full Supply Time The total time required to obtain an item that is not
forecasted. This time is used to calculate the full cumulative order lead time
for an item, which includes the cumulative lead time of purchased
parts. Example For item A, the supplier communicated a supply
time of 50 days. This is in fact a reduced lead time and is only
possible because a three year forecast is sent to the supplier for this item.
If additional quantities are needed, which are not included in the forecast,
the supplier needs the full supply time, which is 300
days. Note This field is visible only if the Use Full Supply Time check box is selected in the Purchase Parameters (tdpur0100m000) session. Full Supply Time Note This field is visible only if the Use Full Supply Time check box is selected in the Purchase 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 Calc. Lead Time 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 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 Priority Distance Tables field in the COM Parameters (tccom0000s000) session.
Calc. Lead Time 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 Proc. 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 Proc. Time
- Safety Time
- Transportation Time (Days)
Note - This field is visible only if the Use Full Supply Time check box is selected in the Purchase Parameters (tdpur0100m000) session.
- Each time you open or close the current session, LN (re)calculates the
calculated full lead time.
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. Del. 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 Warehousing. As a result, the quantities received are checked by Purchase Control and not
by Warehousing. Del. 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 Warehousing. As a result, the quantities received are checked by Purchase Control and not
by Warehousing. Qty. Tolerance (+) The maximum quantity that a supplier can deliver. The maximum
quantity tolerance is expressed as a percentage of the ordered quantity. 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 Warehousing. As a result, the quantities received are checked by Purchase Control and not
by Warehousing. Qty. Tolerance (-) 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 Warehousing. As a result, the quantities received are checked by Purchase Control and not
by Warehousing. 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 Note You cannot select this check box if the Use Material Release for Firm Requirements check box is
selected. Use Sequence Shipping Schedule Note You cannot select this check box if the Use Material Release for Firm Requirements check box is
selected. 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. Release EDI Message Directly If the value of the Communication Channel field is EDI and 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 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.
Segment Set for Material Release 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 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 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. Issue Pattern 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 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 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.
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.
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. | |