Item Supplier Plan (cpvmi0530m000)

Use this session to display an item-business-partner plan You can use this session to see how the planned inventory of an item that is supplied and planned by a particular supplier develops over time.

This session acts more or less like the Item Order Plan (cprrp0520m000) session with a filter that only displays the transactions related to the selected supplier.

If you start this session, LN first starts the Item Supplier Plan - Find (cpvmi0531s000) session, in which you select the some parameters for this session.

This session can display three types of item-business-partner plan, depending on the value of the VMI requirement type that you select when you start this session. The VMI requirement type can have the following values:

  • Actual and Planned Demand
    The item-business-partner plan is based upon the actual demand data and planned demand data that you generated in the order-planning process.
  • Calculated Forecast to Supplier
    The item-business-partner plan is based upon the demand data from the forecast that you have calculated in the most recent order-planning run. (This calculated forecast may or may not yet have been sent to your supplier).
  • Sent Forecast to Supplier
    The item-business-partner plan is based upon the demand data from the most recent revision of the forecast sent to your supplier. (After LN calculates the forecast, you can modify the forecast before you send the forecast to your customer).

 

Settings
Scenario

The identification of an overall planning solution.

Each scenario represents one overall planning solution, and involves particular settings for the planning of items and resources. You can use scenarios to analyze and compare various planning options and to find the best planning solution. For example, you can vary demand forecasts or sourcing strategies.

One of the scenarios is the actual scenario, which corresponds with the actual planning situation. You can only transfer planned orders and production plans from the actual scenario to the execution level of LN.

Plan Item

An item with the order system Planned.

The production, distribution, or purchase of these items is planned in Enterprise Planning based on the forecast or the actual demand.

You can plan these items by means of the following:

  • Master-based planning, which is similar to master production scheduling techniques.
  • Order-based planning, which is similar to material-requirements planning techniques.
  • A combination of master-based planning and order-based planning.

Plan items can be one of the following:

  • An actual manufactured or purchased item.
  • A product family.
  • A basic model, that is, a defined product variant of a generic item.

A group of similar plan items or families is called a product family. The items are aggregated to give a more general plan than the one devised for individual items. A code displayed by the item code's cluster segment shows that the plan item is a clustered item that is used for distribution planning.

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.

Requirement Type

The type and origin of the requirements on which LN can base an item supplier plan or an item customer plan in a vendor-managed-inventory situation. Depending on the requirement type, LN uses different demand data to calculate how much of an the item is planned to be available in each period.

The VMI requirement type can have the following values:

  • Calculated Forecast to Supplier
  • Sent Forecast to Supplier
  • Received Forecast from Customer
  • Calculated Confirmed Supply
  • Sent Confirmed Supply
  • Actual and Planned Demand
Planner ID

The planner that is responsible for planning this plan item.

Actual Stock

The current inventory of the plan item.

If the information about the actual stock is only available at the supplier that handles the supply planning for the plan item, this field displays the confirmed stock.

Confirmed Stock

The actual stock of a plan item in a VMI warehouse, as reported by the supplier to the customer.

In a vendor-managed-inventory situation, where the supplier is responsible for the supply planning of an item in a warehouse at the customer's site, the supplier keeps track of the inventory levels. In that case, the supplier informs the customer of the actual stock.

Confirmed Stock

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.

Delivery Moment

The pattern code that determines the delivery moments on which you supplier agreed to deliver the items. For example, you can specify that the goods must always be delivered on Wednesdays at 8:00 AM.

Note

This field displays the value of the Delivery Moments field in the Planning Terms and Conditions (tctrm1135m000) session. That field can be left empty.

If this field is empty, your supplier is free to choose any moment to deliver the requested goods.

If this field displays a pattern code, LN can shift the date of delivery backwards to match one of the agreed delivery moments in the delivery pattern.

Date

The date and time on which the items are supposed to be received in or issued from the warehouse.

The calculation of the date depends on the type of record:

Total Forecast

The sum of the confirmed part and the unconfirmed part of the demand.

Note

The basis on which LN calculates this field depends on the VMI requirement type for which you opened this item-business-partner plan.

Confirmed Forecast

The confirmed part of the demand.

Note

The basis on which LN calculates this field depends on the VMI requirement type for which you opened this item-business-partner plan.

Unconfirmed Forecast

The unconfirmed part of the demand.

Scheduled Receipts

The quantity of items that you expect to receive from your VMI supplier.

These scheduled receipts based on the following information:

Note

LN retrieves the scheduled receipt data from the Planned Inventory Transactions (whinp1500m000) session.

Confirmed Supply/Expected Supply

The quantity of item the supplier has confirmed or is expected to be delivered to the customer on the planned delivery date.

Planned Avail.(Total)

The expected inventory level that will be reached after this demand or supply and all preceding changes will have been realized, assuming that not only the confirmed forecast but also the unconfirmed forecast will lead to actual issues from the warehouse.

Planned Available(Confirmed To Supplier)

The expected inventory level that will be reached after this demand or supply and all preceding changes will have been realized, assuming that only the confirmed forecast will lead to actual issues from the warehouse.

ATP (ConfirmedTo Supplier)

The item quantity that is still available to be promised to a customer.

In LN, available-to-promise (ATP) is part of a larger extended framework of order promising techniques called capable-to-promise (CTP). If an item's ATP is insufficient, CTP goes beyond ATP in that it also considers the possibility of producing more than was initially planned.

In addition to the standard ATP functionality, LN also uses channel ATP. This term refers to the availability of an item for a certain sales channel, taking into account the sales limits for that channel.

For all other types of order promising functionality used in LN, the term CTP is used.

If the VMI requirement type is Actual and Planned Demand, LN calculates the ATP based on the confirmed actual demand and the planned demand.

If the VMI requirement type is Calculated Forecast to Supplier or Sent Forecast to Supplier, LN calculates the ATP based on the confirmed demand and the confirmed actual demand and the planned demand.

MininumTarget Inventory

The minimum inventory level that must be maintained.

If a minimum level was specified in the applicable terms and conditions agreement, that level must be maintained. Otherwise, the safety stock is applied as usual.

MaximumTarget Inventory

The maximum inventory level permitted.

If a maximum level was specified in the applicable terms and conditions agreement, that level must not be exceeded. Otherwise, no maximum is applied.

Planning
Time Fence

The value of the Time Fence field in the Items - Planning (cprpd1100m000) session.

Forecast Time Fence

The value of the Forecast Time Fence field in the Items - Planning (cprpd1100m000) session.

Order Horizon

The value of the Order Horizon field in the Items - Planning (cprpd1100m000) session.

ATP Horizon

The value of the CTP Horizon field in the Items - Planning (cprpd1100m000) session.

Net Change Date

The value of the Net Change Date field in the Items - Planning (cprpd1100m000) session.

Replenishment Based On

The value of the Replenishment Based On field in the Planning Terms and Conditions (tctrm1135m000) session.

Use Min-Max Inventory Levels

The value of the Use Min-Max Inventory Levels field in the Planning Terms and Conditions (tctrm1135m000) session.

Terms and Conditions
Effective Date

The value of the Effective Date field in the Planning Terms and Conditions (tctrm1135m000) session.

Expiry Date

The value of the Expiry Date field in the Planning Terms and Conditions (tctrm1135m000) session.

Send Forecast to Supplier

The value of the Send Forecast to Supplier field in the Planning Terms and Conditions (tctrm1135m000) session.

Use Confirmed Supply

The value of the Use Confirmed Supply field in the Planning Terms and Conditions (tctrm1135m000) session.

BP Forecast Horizon

The value of the Forecast Horizon field in the Planning Terms and Conditions (tctrm1135m000) session.

Frozen Zone +

The value of the Frozen Zone + field in the Planning Terms and Conditions (tctrm1135m000) session.

Frozen Zone -

The value of the Frozen Zone - field in the Planning Terms and Conditions (tctrm1135m000) session.

Confirmed Supply Time Fence

The value of the Confirm Supply Horizon field in the Planning Terms and Conditions (tctrm1135m000) session.

Detail
Order Type

The type of order displayed on this line.

Order Number

The order number that identifies the demand or the order.

Pos./Rev.

Further details to identify the supply or demand.

Demand

The quantity of the demand.

If this line represents a supply, this field displays zero (0).

Supply

The quantity of the supply.

If this line represents a demand, this field displays zero (0).

Planning Total Forecast

Planning Confirmed Forecast

Planning Unconfirmed Forecast

Consumed BPForecast

The part of the forecast that has already resulted in issues from the warehouse, after the forecast data was sent to the supplier.

The actual issues consume the forecast demand.

ConsumedConfirmed Supply

The part of the confirmed supply that has already resulted in receipts or planned receipts into the warehouse after the confirmed-supply data has been received from the supplier.

The receipts consume the confirmed supply.

Initial Hidden
Default Warehouse

The default warehouse of the plan item, defined in the Items - Planning (cprpd1100m000) session.

Plan Item

The ordered plan item.

Specification
Specification

If this check box is selected, a specification is present.

To display the specification, in the menu, click Specification.

Effectivity Unit

A means to control the validity of variations by effectivity units.

Unit effectivity enables you to model changes for the following entities:

  • Engineering bill of material
  • Production bill of material
  • Routing
  • Routing operations
  • Supplier selection
  • Sourcing strategies
Business Partner

If this record involves a supply, this field indicates the sold-to business partner to which this supply was allocated or demand pegged. If this record involves a demand, this field indicates the sold-to business partner to which the supply that can fill this demand must have been allocated or demand pegged.

LN uses this characteristic to match supply and demand.

Business Object Type

If this record involves a supply, this field indicates the type of order to which the inventory was allocated or the supply object was demand pegged, such as, Sales Order, or Service Order. If this record involves a demand, this field indicates the type of order to which the supply that can fill this demand must have been allocated or demand pegged.

LN uses this characteristic to match supply and demand.

Note

The following fields are always used in combination; together, they identify the relevant order or order line:

  • Business Object Type
  • Business Object
  • Business Object Reference
Business Object

If this record involves a supply, this field indicates the order, or order line, to which the inventory was allocated or the supply object was demand pegged, such as, Sales Order, or Service Order. If this record involves a demand, this field indicates the order, or order line, to which the supply that can fill this demand must have been allocated or demand pegged.

LN uses this characteristic to match supply and demand.

Note

The following fields are always used in combination; together, they identify the relevant order or order line:

  • Business Object Type
  • Business Object
  • Business Object Reference
Reference

If this record involves a supply, this field indicates the reference code to which the inventory was allocated or the supply object was demand pegged. If this record involves a demand, this field indicates the reference code to which the supply that can fill this demand must have been allocated or demand pegged.

LN uses this characteristic to find a matching supply for this demand.

LN uses the Reference field to record an internal reference.

You can use a reference code to keep a collection of parts linked together, even if they follow different routings, for example, if some of the parts are transported to a subcontractor to be returned later.

Use Unallocated Inventory

If this check box is selected, Enterprise Planning can use unallocated inventory to supply the demand. Enterprise Planning uses allocated inventory first. If there is not enough allocated inventory, Enterprise Planning also uses unallocated inventory.

If this check box is cleared, Enterprise Planning can use only allocated inventory to fill the demand.

Note

After this record has been created, the value of this field is kept unchanged, even if the terms and conditions change.