| Overview of purchase schedule handling |  |
| A purchase schedule is a timetable of planned supply of materials. Purchase schedules support long-term purchasing with frequent deliveries and are usually backed by a purchase contract. All requirements for the same item, buy-from business partner, ship-from business partner, purchase office, and warehouse are stored in one schedule. Purchase schedules are used instead of standard purchase orders in cases where full visibility and time phasing of material requirement information is required. So, purchase schedules provide a more detailed way to specify the delivery dates/times per item. The following types of purchase schedules exist: Push schedule A list of time-phased requirements, generated by a central planning system, such as ERP LN Enterprise Planning or ERP LN Project that is sent to the purchase business partner. Push schedules contain both a forecast for the longer term and actual orders for the short term. A push schedule is also called a non-referenced schedule. Pull forecast schedule A list of time-phased planned requirements, generated by ERP LN Enterprise Planning, that is sent to the purchase business partner. Pull forecast schedules are only used for forecasting purposes. To actually order the items, a pull call-off schedule must be generated with the same schedule number as the pull forecast schedule. Like a push schedule, a pull forecast schedule is also a non-referenced schedule. Pull call-off schedule A list of time-phased specific requirements of purchased items, triggered from Assembly Control, Shop Floor Control, or ERP LN Warehouse Management (KANBAN, Time-phased order point). A pull call-off schedule is a referenced schedule. Purchase schedule master data Before you can carry out the purchase schedule procedure, you must define the purchase master data. For details, refer to: Purchase item data Purchase organizational data Before you can create a purchase schedule, you must also: Select the Purchase Schedule in Use check box for the item in the Item - General (tcibd0101s000) session and select a purchase schedule type in the Schedule Type field, which can be of the type push or pull. Set up a segment set by: Creating segments in the Schedule Segments (tdipu0115m000) session. Creating a segment set in the Schedule Segment Sets (tdipu0113m000) session. Adding the segments to the segment set in the Segment Set - Segments (tdipu0114m000) session. Create patterns in the Patterns (tcccp0690m000) session. Define the following parameters: The fields on the Schedules tab of the Purchase Contract Parameters (tdpur0100m300) session. The Number Group for Purchase Orders field in the Purchase Order Parameters (tdpur0100m400) session. The purchase schedule related parameters that apply for an item and business partner combination in the Purchase Contract Line Logistic Data (tdpur3102m000)/ Items - Purchase Business Partner (tdipu0110m000) sessions. Refer also to Purchase schedule release types. Store delivery patterns by warehouse, buy-from business partner/ship-from business partner and item in the Delivery Patterns by Warehouse / BP / Item (tdipu0124m000) session. Based on the combinations in this session, planned delivery moments can be generated in the Generate Planned Delivery Moments (tdipu0225m000) session. Generate planned delivery moments in the Generate Planned Delivery Moments (tdipu0225m000) session to determine when an item can be delivered. The dates returned, listed in the Planned Delivery Moments (Shipment Based) (tdipu0125m000) and the Planned Delivery Moments (Delivery Based) (tdipu0126m000) session, are used by Enterprise Planning for lead time offsetting. Purchase schedule procedure The purchase schedule procedure consists of a number of steps for each schedule type. Push schedules The following steps are or must be completed in the push schedule procedure: To generate a schedule header and lines. To regenerate schedule lines. To generate a purchase release (line) To approve the purchase release line. To print the purchase release. To insert authorizations. To insert receipt details. To insert cumulatives. To reset the cumulatives and authorizations To update history and turnover data. For more information, refer to Push schedules. Pull forecast schedules Based on the parameters and triggers, the following steps are completed in the pull forecast schedule procedure: To generate a schedule header and lines. To regenerate schedule lines. To generate a purchase release. To approve the purchase release. To print the purchase release. To insert authorizations. To generate a pull call-off schedule. For more information, refer to Pull forecast schedules. Pull call-off schedules Based on the parameters and triggers, the following steps are completed automatically in the pull call-off schedule procedure: To generate a schedule header. To generate schedule lines To generate a purchase release. To print the purchase release. To insert receipt details. To insert cumulatives. To reset the cumulatives and authorizations. To update history and turnover data. For more information, refer to Pull call-off schedules. To link a contract to a purchase schedule If a purchase schedule contains an external business partner, it is always based on a contract (line). As a result, you must define the logistic data that is required for the purchase schedule in the Purchase Contract Line Logistic Data (tdpur3102m000) session. If you only do business with internal business partners, you need not define a contract. ERP LN then retrieves the logistic data for the schedule from the Items - Purchase Business Partner (tdipu0110m000) session. ERP LN automatically links a normal contract to the purchase schedule. However, instead, you can link a special contract to the purchase schedule. To unlink the normal contract and link a special contract to the purchase schedule, click Change Contract in the Purchase Schedules (tdpur3110m000) session. As a result, the Selected Purchase Contract Lines (tdpur3512s000) session starts from which you can select a special contract. However, you can only replace the normal contract by a special contract as long as no receipts are booked yet for the purchase schedule. If receipts are already booked, you must terminate the existing purchase schedule and create a new purchase schedule in the Terminate Purchase Schedule (tdpur3210m100) session. Now, you can link a special contract to the newly created purchase schedule. When ERP LN links a contract to the purchase schedule, the schedule header is loaded with the default values of the linked contract. Specific addresses, as well as contract terms and prices and discounts, are adopted on the schedule level. For non-referenced schedules, ERP LN uses the Generation Date in the Purchase Schedules (tdpur3110m000) session to determine which purchase contract price revision must be used from the Purchase Contract Price Revisions (tdpur3103m000) session to retrieve prices and discounts. For referenced schedules, ERP LN uses the Purchase Price Date Type field in the Pricing Parameters (tdpcg0100m000) session, which can be set to Order Date, System Date, or Delivery Date to determine which purchase contract price revision must be used. Related topics Purchase item data Purchase organizational data Purchase schedule release types Push schedules Pull forecast schedules Pull call-off schedules Purchase contracts |