| Item - Purchase Business Partner (tdipu0110m000) |  |
| Use this session to view, enter, or maintain business partner specific information that is related to a specific purchased item. This session contains the default logistic data of a purchase business partner, required for a purchase contract, purchase schedule, or purchase order. Note For internal business partners, schedule information can be derived from the current session. For external business partners, purchase schedules are always based on a purchase contract line and schedule information is derived from the Purchase Contract Line Logistic Data (tdpur3102m000) session. Related topics Purchase item data Overview of purchase order handling Purchase contracts Overview of purchase schedule handling Business partner selection based on unit effectivity
Fields | Description
Item Group | Group of items with similar characteristics. Each item belongs to a particular item group. The item group is used in combination with the item type to set up item defaults.
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. 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) Note In the Item - General (tcibd0101s000) session, you can define whether orders are issued for an item according to a purchase schedule, and you can define a purchase schedule type, based on which the orders are generated. If no purchase schedule is in use for the item, you can still manually insert the item into a purchase push schedule. Related topics Push schedules
Buy-from Business Partner | The business partner from whom you order goods or services; this usually represents a supplier's sales department. The definition includes the default price and discount agreements, purchase-order defaults, delivery terms, and the related ship-from and invoice-from business partner. Default value When generating a purchase order, the searching logic ERP LN uses to retrieve a buy-from business partner is as follows: From the Buy-from Business Partner field in the Items - Purchase (tdipu0101m000) session. From the Buy-from Business Partner in the Items - Purchase Business Partner (tdipu0110m000) session that is: Set to Single Source in the Items - Purchase Business Partner (tdipu0110m000) session. Linked to an Item in the Items - Purchase Business Partner (tdipu0110m000) session. From the Buy-from Business Partner in the Items - Purchase Business Partner (tdipu0110m000) session that is: Set to Preferred in the Preferred field of the Items - Purchase Business Partner (tdipu0110m000) session. Linked to an Item in the Items - Purchase Business Partner (tdipu0110m000) session. From the Buy-from Business Partner in the Items - Purchase Business Partner (tdipu0110m000) session that is: Set to Single Source in the Items - Purchase Business Partner (tdipu0110m000) session. Linked to an Item Group in the Items - Purchase Business Partner (tdipu0110m000) session. From the Buy-from Business Partner in the Items - Purchase Business Partner (tdipu0110m000) session that is: Set to Preferred in the Preferred field of the Items - Purchase Business Partner (tdipu0110m000) session. Linked to an Item Group in the Items - Purchase Business Partner (tdipu0110m000) session. Note When a purchase order is generated by Enterprise Planning, ERP LN skips step one.
Ship-from Business Partner | The business partner that ships the ordered goods to your organization. This usually represents a supplier's distribution center or warehouse. The definition includes the default warehouse at which you want to receive the goods and if you want to inspect the goods, the carrier that takes care of the transport, and the related buy-from business partner.
Effective Date | The first day on which a record or a setting is valid. The effective date often includes the effective time.
Expiry Date | The last day on which a record is valid. If you do not specify an expiry time, the validity expires at the end of the expiry date, at 24:00 hours.
Item - Buy-from BP status | The status of the item - purchase business partner combination. Allowed values Item - Purchase Business Partner Status
Blocking Reason | The code that can be linked to the item - purchase business partner combination to describe the reason for blocking.
Preferred | Use this field to indicate whether the business partner is preferred or fixed for the item. Note When generating orders, ERP LN first searches for fixed purchase business partners and then for preferred purchase business partners by the purchase business partners' priority, as defined in the Priority field of the current session. If you set the current field to Single Source, and the single source purchase business partner is not valid at the moment of planned delivery, or cannot deliver the required demand, ERP LN tries to fulfill the demand with planned production orders or planned distribution orders, following the strategy that you defined for the plan item. If you set the current field to Preferred, and none of the buy-from business partners is valid at the moment of planned delivery, or cannot deliver the required demand, ERP LN generates a planned purchase order for an empty purchase business partner. Allowed values Possible Values Related topics Allocation rule: historic percentage
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.
Area | The code of the (commercial) area in which the buy-from business partner is established. Note The code of the area is for example used as sorting criteria for statistics.
Self-Billing | If this check box is selected, you pay an invoice to the purchase business partner without receiving an invoice for the item. As a result the invoice for the item is self-billed by your company. Related topics Self billing
Invoice after | You can indicate when a self billed invoice can be generated. Inspection Self bills can be generated after the goods are inspected and approved. Receipt Self bills can be generated after the goods are received or consumed. Related topics Self billing
Self Billing Date Type | If the Self-Billing check box is selected, use this field to define on which date the self-billing payments are based. Either the receipt date or the shipping date can be used as the invoice date on self-billed invoices. Related topics Self billing
Self Billing Method | If the Self-Billing check box is selected, you must select a self-billing method, which determines how self-billing is carried out. The self-billing method determines, among other things, the criteria for composing the invoice, the invoicing interval, the output medium, and so on. Related topics Self billing
Item Purchase Text (Internal) | If this check box is selected, a text is added for internal purposes only.
Item Purchase Text | If this check box is selected, a text is added that is printed on external documents.
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 1 (= highest priority) to 999 (= lowest priority). Related topics To use priorities Sourcing
Sourcing Percentage | A percentage used to calculate how orders are divided among suppliers. Related topics To use sourcing percentages Sourcing
Standard Configuration | If this check box is selected, the item - purchase business partner combination is valid unless it has exceptions attached that define the combination as not valid. If this check box is selected, and the purchase order has no effectivity unit linked to it, the purchase business partner is considered as valid. If this check box is cleared, Enterprise Planning considers the item - purchase business partner combination as not valid, unless it has exceptions attached that define the combination as valid for the effectivity unit of the purchase order. Note This check box is used to: Determine whether an item - purchase business partner combination is valid or not. However, the standard configuration can be overruled by exceptions. Retrieve valid business partners to return them to Enterprise Planning during the approved business partner selection process of order planning. During this process, Enterprise Planning communicates the effectivity unit from the Sales Order Lines (tdsls4101m000) session or the Sales Quotation Lines (tdsls1501m000) session to Purchase Control (PUR). PUR then uses this check box to determine which purchase business partners are valid for the item and can be returned to Enterprise Planning. Check the validity of the item - purchase business partner combination when you manually insert a purchase order line to which an effectivity unit is linked in the Purchase Order Lines (tdpur4101m000) session. Default value By default, ERP LN selects this check box if no exceptions are attached to this item - purchase business partner combination. However, you can manually select or clear this check box. Related topics Business partner selection based on unit effectivity Unit effectivity in Enterprise Planning
Exceptions present | If this check box is selected, the item - purchase business partner combination has exceptions attached that can overrule the standard configuration settings. Note This check box is used to: Retrieve valid business partners to return them to Enterprise Planning during the approved business partner selection process of order planning. During this process, Enterprise Planning communicates the effectivity unit that is entered in the Sales Order Lines (tdsls4101m000), or the Sales Quotation Lines (tdsls1501m000) to Purchase Control (PUR). PUR then uses this check box to determine which purchase business partners are valid for the item and can be returned to Enterprise Planning. Check the validity of the item - purchase business partner combination when you manually insert a purchase order line to which an effectivity unit is linked in the Purchase Order Lines (tdpur4101m000) session. Default value ERP LN selects this check box if exceptions are linked to this item - purchase business partner combination in the Exceptions (tcuef0105m000) session. Related topics Business partner selection based on unit effectivity Unit effectivity in Enterprise Planning Overview of unit effectivity
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 Warehousing. As a result, the quantities received are checked by Purchase Control and not by Warehousing. Related topics Push schedules Pull call-off schedules Blanket warehousing orders
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 Warehousing. As a result, the quantities received are checked by Purchase Control and not by Warehousing. Related topics Push schedules Pull call-off schedules Blanket warehousing orders
Receipt Quantity Tolerance (-) | The percentage that the received quantity may be less than the ordered quantity. Default value ERP LN retrieves the default value from the Quantity Tolerance (-) field of the Items - Purchase (tdipu0101m000) session. 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 Warehousing. As a result, the quantities received are checked by Purchase Control and not by Warehousing. Related topics Push schedules Pull call-off schedules Blanket warehousing orders
Receipt Quantity Tolerance (+) | The percentage that the received quantity is allowed to be more than the ordered quantity. Default value ERP LN retrieves the default value from the Quantity Tolerance (+) field of the Items - Purchase (tdipu0101m000) session. 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. 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. Related topics Push schedules Pull call-off schedules Blanket warehousing orders
Hard Stop on Quantity | The way in which ERP LN must react to a receipt that does not meet the quantity tolerances. Note This field is defaulted to the Hard Stop on Quantity field of the Inbound Order Lines (whinh2110m000) session, when: A purchase order is released to warehousing in the Release Purchase Orders to Warehousing (tdpur4246m000) session. A pull call-off schedule line is converted to a warehousing order when generating the schedule line in the Purchase Schedule - Lines (tdpur3111m000) session. Allowed values Possible values Related topics Push schedules Pull call-off schedules
Hard Stop on Date | The way in which ERP LN must react to a receipt that does not meet the time tolerances. Note This field is defaulted to the Hard Stop on Time field of the Inbound Order Lines (whinh2110m000) session, when: A purchase order is released to warehousing in the Release Purchase Orders to Warehousing (tdpur4246m000) session. A pull call-off schedule line is converted to a warehousing order when generating the schedule line in the Purchase Schedule - Lines (tdpur3111m000) session. Allowed values Possible values Related topics Push schedules Pull call-off schedules
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. Related topics Default purchase office
Manufacturer | The default manufacturer for the item - business partner combination. Note If the item is an MPN item, which you can define in the MPN Item field of the Items - Purchase (tdipu0101m000) session, this field is empty and disabled. Related topics To set up and use multiple manufacturer items
Inspection | If this check box is selected, actual deliveries must be inspected. Related topics To inspect scheduled items
Consigned | If this check box is selected, the item on the purchase schedule is consignment inventory. Note If you want to link the payment for a consumption of consignment inventory directly to the replenishment schedule, do not select this check box. Related topics Consignment in Sales and Procurement
For Commingling | If this check box is selected, and the Commingling for check box is also selected for the relevant origin in the Purchase Order Parameters (tdpur0100m400) session, you can commingle a purchase order line for the item and buy-from business partner. Related topics Overview of purchase order commingling To commingle purchase orders
Order Quantity Increment | The order quantity increment expressed in the inventory unit. Note This field cannot have the value 0. Related topics Order quantity settings
Minimum Order Quantity | The minimum order quantity expressed in the inventory unit. Related topics Order quantity settings
Maximum Order Quantity | The maximum order quantity expressed in the inventory unit. Related topics Order quantity settings
Fixed Order Quantity | The fixed order quantity expressed in the inventory unit. If an item's order method is Fixed Order Quantity, which you can define in the Order Method field of the Item - Ordering (tcibd2100s000) session, the value of the session's Fixed Order Quantity field is defaulted to the current field. If item ordering data is not present, the default value is 1. Note The value of this field must be a multiple of the Order Quantity Increment field. The value of this field must lie between the values of the Minimum Order Quantity and Maximum Order Quantity fields. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Fixed order quantity. Related topics Order quantity settings
Economic Order Quantity | The economic order quantity expressed in the inventory unit. Note If the order method is Economic Order Quantity, the economic order quantity is the most favourable quantity for planned purchase orders. This order method is defined in the Item - Ordering (tcibd2100s000) session. Related topics Order quantity settings
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. If purchase schedules are automatically generated by Enterprise Planning for an internal business partner, this field is only used in the purchase business partner selection process. Enterprise Planning uses this field, together with the Safety Time field and the Supply Time field, to assign a priority to purchase business partners 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 Processing 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. If purchase schedules are automatically generated by Enterprise Planning for an internal business partner, this field is only used in the purchase business partner selection process. Enterprise Planning uses this field, together with the Internal Processing Time field and the Supply Time field, to assign a priority to purchase business partners 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 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. If purchase schedules are automatically generated by Enterprise Planning for an internal business partner, this field is only used in the purchase business partner selection process. Enterprise Planning uses this field, together with the Internal Processing Time field and the Safety Time field, to assign a priority to purchase business partners who can deliver the required item. Note If you want to retrieve the supply time from an affiliated supplying company, use the Update Supply Times in Item - Purchase Business Partner (tdipu0210m100) session, which you can start from the appropriate menu of the current session. 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.
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 only visible if the Use Full Supply Time check box is selected in the Purchase Parameters (tdpur0100m000) session. If you want to retrieve the full supply time from an affiliated supplying company, use the Update Supply Times in Item - Purchase Business Partner (tdipu0210m100) session, which you can start from the appropriate menu of the current session. Related topics To calculate purchase item lead time
Full Supply Time | The unit in which the full supply time is expressed. Note This field is only visible if the Use Full Supply Time check box is selected in the Purchase Parameters (tdpur0100m000) session.
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 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 plans 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 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. If you want to recalculate the calculated lead time for a range of items/business partners, use the Update Calculated Lead Time in Item Purchase - BP (tdipu0210m000) session, which you can start from the appropriate menu of the current session. Related topics To calculate purchase item lead time Purchase lead time calculation
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 only visible 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, ERP LN (re)calculates the calculated full lead time. If you want to recalculate the calculated full lead time for a range of items/business partners, run the Update Calculated Lead Time in Item Purchase - BP (tdipu0210m000) session with the Update Calculated Full Lead Time check box selected, which you can start from the appropriate menu of the current session. Related topics To calculate purchase item lead time
Inbound Lead Time | The time interval between the arrival of the items and the actual storage in the warehouse. Default value This field is defaulted from the Inbound Lead Time field of the Warehouse - Item (whwmd2110s000) session. In this session, this field is displayed for information purposes only.
Inbound Lead Time | The unit in which the inbound lead time is expressed. Default value This field is defaulted from the Warehouse - Item (whwmd2110s000) session.
Lead Time Horizon (Days) | 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. 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
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. Note Sequence Shipping Schedule Only can only be selected if the Preferred field is set to Single Source and the schedule is a pull schedule. Allowed values Schedule Release Detail Related topics Purchase schedule release types To use segment sets
Communication Channel | The way in which purchase releases must be communicated to the business partner. Related topics Purchase releases
Package Definition | The package definition for the item or item group. Related topics Packaging levels
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 purchase business partner 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 purchase business partner, a purchase release receives the status Sent. Related topics Purchase releases
Schedule Type | The type of purchase schedule, which can be push schedule or pull schedule. Default value This value is retrieved from the Item - General (tcibd0101s000) session. Related topics Purchase schedule release types Push schedules Pull forecast schedules Pull call-off schedules
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 gets 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 Possible Values Related topics Authorizations To reset authorizations
Transaction Time Fence | This field indicates for which purchase schedule lines inventory transactions must be logged in the Warehouse Orders module of Warehousing, 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
Segment Set for Material Release | The segment set that is related to a 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 ( pull schedules ). If the value of the Release Type field is Shipping Schedule Only or Sequence Shipping Schedule Only, you cannot enter a segment set in this field. Default value The Segment Set for Material Release from the Purchase Contract Parameters (tdpur0100m300) session. Related topics To use segment sets
Segment Set for Shipping Schedule | The segment set that is related to a 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 value of the Release Type field is Material Release, you cannot enter a segment set in this field. Default value The Segment Set for Shipping Schedule from the Purchase Contract Parameters (tdpur0100m300) session. 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 ( pull schedules ). If the value of the Release Type field is Shipping Schedule Only or Sequence Shipping Schedule Only, you cannot enter an issue pattern in this field. Default value The Issue Pattern for Material Release from the Purchase Contract Parameters (tdpur0100m300) session. Related topics 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. Default value The Issue Pattern for Shipping Schedule from the Purchase Contract Parameters (tdpur0100m300) session. Related topics Overview of purchase schedule handling Purchase releases
Frozen Period for Increasing Qty | 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 for Decreasing Qty | 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
Generate Freight Orders from Purchase | If this check box is selected, freight orders must be generated for purchase orders that contain this item - purchase business partner combination. Default value The value of this check box is defaulted to the Generate Freight Orders from Purchase check box in the Purchase Order Lines (tdpur4101m000) session and the Purchase Order Line Details (tdpur4101m200), but can be overwritten in these sessions. Related topics Integration Freight Order Control and Purchase Control
Generate Order for Unexpected Warehouse Receipt | If this check box is selected, and a warehouse receipt has no corresponding inbound order, ERP LN automatically creates a purchase order against which the items are received for the purchase business partner. ERP LN automatically: Approves and releases the generated purchase order to Warehousing. Links the unexpected receipt line to the inbound order line and confirms it. Note You cannot select this check box if the Release to Warehouse check box is cleared for the item in the Items - Purchase (tdipu0101m000) session. Related topics Vendor managed inventory Configured items on purchase schedules
Shipment or Delivery Based | Use this field to define on what date and time (schedule) requirements are based. 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 This field is defaulted to the Shipment/Delivery Based field of the Purchase Schedules (tdpur3110m000) session. However, you can change its value in the Purchase Schedules (tdpur3110m000) session.
Supplier Capacity | The ship-from business partner capacity expressed in the inventory unit. Note Enterprise Planning uses this field when generating planned orders for a purchase business partner. Related topics To compute purchase order quantities
Order Quantity Multiple | The unit of measure in which the inventory of an item is recorded, such as piece, kilogram, box of 12, or meter. The inventory unit is also used as the base unit in measure conversions, especially for conversions that concern the order unit and the price unit on a purchase order or a sales order. These conversions always use the inventory unit as the base unit. An inventory unit therefore applies to all item types, also to item types that cannot be kept in stock.
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. Note Enterprise Planning uses this field when generating planned orders for a purchase business partner. 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 purchase business partner can only deliver a maximum number of 120 pieces a week.
Capacity Time Unit | The time unit in which the ship-from business partner capacity is expressed.
Commands | Description
Calculate | Calculates the Calculated Lead Time (Days).
Calculate | Calculates the Calculated Full Lead Time (Days).
Update Calculated Lead Time in Item - Purchase BP | Starts the Update Calculated Lead Time in Item Purchase - BP (tdipu0210m000) session in which you can recalculate the calculated (full) lead time for a range of items/business partners.
Update Supply Times in Item - Purchase Business Partner | Starts the Update Calculated Lead Time in Item Purchase - BP (tdipu0210m000) session, in which you can retrieve the (full) supply time from an affiliated supplying company.
Exceptions | Starts the Exceptions (tcuef0105m000) session, in which you can define unit effective purchase business partners.
Nett Prices per Buy-from Business Partner | Starts the Net Prices per Buy-from Business Partner (tdipu0110m100) session.
Approved Business Partners | Only displays the approved item - purchase business partner combinations.