Using Vendor Managed Inventory

This chapter provides an overview of vendor managed inventory (VMI), an overview of VMI integration points, and discusses how to:

• Set up vendor managed inventory.

• Perform vendor managed inventory processes.

• Create VMI messages.

• Create billing-only sales orders.

• Perform inquiries for VMI transactions.

Understanding Vendor Managed Inventory

Vendor managed inventory is a supply chain management strategy in which a vendor manages goods that are located in a customer's warehouse. The goods can be consigned or non-consigned stock. The consigned stock is owned by the vendor until the customer consumes it, and the non-consigned stock is owned by the customer when the customer receives it.

As the vendor, you will create a Vendor Managed Inventory (VMI) business unit, which represents your customer's inventory. This business unit will have storage locations that contain items and item quantities. Storage location in the VMI business unit correspond to Ship-To locations for a customer. These items and item quantities in the storage locations will match the item quantities at the customer site.

You can implement this strategy across the enterprise by integrating functions in PeopleSoft Inventory, Cost Management, Order Management, and Billing.

These terms are often used with VMI:

This diagram illustrates the vendor managed inventory process for consigned items:

VMI consigned item process flow

This diagram illustrates the vendor managed inventory process for non-consigned items:

VMI non-consigned item process flow

An individual in your organization is typically assigned to the customer and referred to as the VMI manager. The VMI manager works with the customer and agrees upon which items and item quantities to stock at the customer site. This information is entered into your enterprise system for the VMI business unit, in the VMI Replenishment menu.

On a periodic basis, which is agreed upon between the VMI manager and the customer, the customer sends messages to notify the VMI manager of item activity and to synchronize item quantities. Transactions are written to the transaction table (TRANSACTION_INV), and item quantities are updated in the VMI business unit.

When consumption transactions are reported for consigned goods, those transaction quantities are eligible for billing to the customer. The Create Billing-Only Orders (IN_BILL_VMI) process creates a bill-only sales order for those transaction quantities, which is used to create an invoice to send to the customer.

The VMI manager initiates the replenishment process to determine if quantity is needed at the customer site. If quantity is needed:

• The replenishment process creates an interunit material stock request (MSR) for consigned items.

• The replenishment process creates a sales order for non-consigned items.

  The items on these sales orders go through the standard fulfillment and billing process.

The fulfillment process is used to ship the items to the customer. During the Deplete On Hand Quantity Requests process the auto-putaway process may be initiated and updates item quantities in the VMI business unit. Alternatively, customers can report the receipt of goods when they arrive at the customers' facility.

The customer can return consigned or non-consigned items:

• If the customer returns a consigned item, the VMI manager creates an return material authorization (RMA) from the source inventory business unit to the supplying inventory business unit.

• If the customer returns a non-consigned item, the PeopleSoft Order Management RMA form is used.

Understanding VMI Integration Points

Integration points are a large part of the VMI business process. PeopleSoft provides integration points to receive messages from customers, and to send messages to customers.

Inbound Messages

The inbound messages create a corresponding transaction code that is written to the transaction table (TRANSACTION_INV). These messages include:

Outbound Messages

The InterUnit Expected Receipt integration point can be used to notify the customer of expected receipts and shipments.

See Also

Creating VMI Messages

EIPs for Fulfillment Transactions

Processing Electronic Data Interchange Transactions in PeopleSoft Inventory

Managing PeopleSoft Supply Chain Management Integration Points

Creating Interunit Expected Receipts

Enterprise PeopleTools 8.46 PeopleBook:Integration Broker

Setting Up Vendor Managed Inventory

When setting up your system to manage stock at a customer location, you must:

1. Set up security for the VMI manager.

2. Define items by setID.

3. Create a VMI business unit.

4. Setup Ship To VMI options for the customer.

5. Set up Sold To options for the customer.

6. Define items for a VMI business unit.

7. Create storage locations for the VMI business unit.

8. Setup VMI Replenishment parameters.

Setting Up VMI Replenishment Parameters

VMI replenishment parameters can be set up at these levels:

• The customer ship-to level.

• The VMI business unit level.

• The VMI business unit and item combination level.

• The VMI business unit, item, and customer ship to level.

Replenishment parameters default from different places. They may be defined at the customer ship-to and item combination level. If they are not, this table illustrates the manner in which they will default:

Pages Used to Set Up Vendor Managed Inventory

Setting Up Security

Access the User Profiles component and add the VMI manager role to the user.

Defining Items by SetID

To define items for VMI usage, access the Define Item-General: Common page. In the Item Type group box, make sure that the Non-Owned Item and the Consigned Purchase check boxes are not selected.

See Also

Defining General Item Information

Creating a VMI Business Unit

To create a VMI business unit that represents your customer site, access the Business Unit Definition page. Select the VMI Stock check box to indicate that this business unit is vendor managed.

Note. The VMI business unit must have the same general ledger business unit as the supplying inventory business unit.

See Also

Defining PeopleSoft Inventory Business Unit Attributes

Setting Up Customer Ship To VMI Options

To indicate that a customer ID is a VMI managed location, use the Customer Information (CUSTOMER_GENERAL) component. Use the Customer Ship To (CUSTOMER_SHIPTO_CI) component interface to load data into the tables for this component.

Use the Customer Ship To Options page to indicate that the customer accepts partial scheduled and partial orders so that the VMI manager can examine back ordered quantities.

Access the VMI Options page.

VMI Options

Customer Order Defaults

Customer Item Tracking

Select to indicate that lot, serial, container, and staged date information is maintained at the customer site. If selected, all transactions received from the customer will contain the item detail. If not selected, transactions received from the customer will not contain the item detail, and the items are depleted by using FIFO logic.

The options can not be updated if there is inventory on-hand or in-transit to the ship-to customer.

If any of the four customer item tracking options are selected, they are not grayed-out when you save. Instead, they are grayed-out the next time you access the page.

Replenishment Parameters

Indicate specific replenishment parameters that are used to calculate replenishment requests for VMI.

See Defining Replenishment Options.

Setting Up Customer Sold To VMI Options

To set up customer sold to VMI options, use the Customer Information (CUSTOMER_GENERAL) component. Use the Customer Sold To (CUSTOMER_SOLDTO_CI) component interface to load data into the tables for this component.

Access the Sold To Options page.

VMI Order Consolidation	Select the option that determines how sales order requests, that are generated during the VMI Replenishment process, is grouped. None: Select to instruct the VMI Replenishment process to generate a separate sales order for every replenishment request. Ship To Customer: Select to instruct the VMI Replenishment process to combine all replenishment requests for the same ship to customer on the same sales order or material stock request. Sold To Customer: Select to instruct the VMI Replenishment process to combine replenishment requests for the same sold to customer on the same sales order. This applies only to sales orders for non-consigned customers.
Receipt Verification	Select to indicate that the customer wishes to verify the receipt of items. If selected, the customer acknowledges the receipt of goods at their site. Shipments will appear as being in-transit until the receipt verification is received. If not selected, the customer does not acknowledge receipt, and the auto-putaway process is used to update on hand quantities for the VMI business unit.
Order Verification	Select to indicate that all sales orders created for this customer go on VMI hold. This provides the VMI manager to review the order before releasing it from hold.

See Also

Maintaining General Customer Information

Defining Items for a VMI Business Unit

To define items for a VMI business unit, access the Define Business Unit Item-General: Common page. Add a cost element. The Non-Owned Item and Consigned Purchase options are not enabled.

See Also

Defining Basic Business Unit Item Attributes

Creating Storage Locations for the VMI Business Unit

To create storage location for the VMI business unit, access the Material Storage Locations page.

Click the VMI Ship To link to access the VMI Ship To page.

Enter the VMI Order Management business unit, the VMI Ship To Customer identification code, the VMI Sold to Customer identification code, the Reorder Quantity Option, and the Desired Stock-In Probability.

Multiple customer ship to locations can be managed in one VMI business unit because the customer is associated to a material storage location. Therefore you can set up multiple MSLs within a VMI business unit; each MSL representing a customer site. If the customer site stores consigned and non-consigned items, you will need to create two storage locations and two customer ship-to values.

On the Material Storage Locations page, the Nettable, Non-Owned and WIP fields are not enabled. The Non-Owned field appears by default from the Goods Consigned at Customer option on the Customer: Ship To-VMI Options page.

Setting up Replenishment for Customer Ship-To

To set up VMI replenishment parameters for a customer ship-to, access the Customer Ship To - VMI Options page.

See Setting Up Customer Ship To VMI Options.

Using the BU Replenishment Page

To set up business unit replenishment attributes, use the BU Replenishment component.

Access the BU Replenishment page:

Reorder Quantity Option

Select how the VMI items are replenished for the VMI business unit. Options are EOQ, Min/Max, and Static Reorder Qty.

See Defining Replenishment Options.

Using the BU Item Replenishment Page

To set up VMI replenishment parameters at the VMI business unit-item combination level, use the VMI Replenish BU/Item Setup component.

Access the BU Item Replenishment page:

All values on this page override setup on the BU Replenishment page.

See Defining Replenishment Options.

Using the Ship To / Item Replenishment Page

To set up VMI replenishment parameters at the VMI business unit-item-customer ship to combination level, use the Ship-To / Item Replenishment component.

Access the Ship-To / Item Replenishment page:

Replenish Lead (Days)

This value represents the average number of days from the placement of a sales order or an MSR, to the receipt of the stock. It defaults from the BU Item Replenishment page.

The VMI Order Management business unit determines the setID that is used when selecting the Ship To Customer.

The Source Business Unit appears by default from the Customer Ship To setup page.

All values on this page, override setup on the BU Replenishment page and the BU Item Replenishment page.

See Also

Defining Replenishment Options

Performing Vendor Managed Inventory Processes

This section provides an overview of VMI processes and discusses how to replenish VMI.

Understanding VMI Processes

This section discusses VMI Processes, and which transactions cannot be performed.

VMI processes include:

• The fulfillment process.

• The receiving process.

• The consumption process.

• The return process.

• The physical and cycle count process.

• The message process.

The Fulfillment Process

The fulfillment process will process the sales order and the interunit MSR in the source inventory business unit as normal.

When a non-consigned item is reserved, the inventory business unit can send an order acknowledge message (855 EDI) to the customer. This message provides order information and can be used to receive non-consigned items. After the reservation process completes, the VMI manager can review shortages and backorders for consigned and non-consigned items.

When a sales order for a non-consigned item is shipped and depleted, the system performs these tasks:

• An interunit ID is assigned to the demand line

• A VMI shipment transaction (037) is written to the transaction table (TRANSACTION_INV) for the inventory business unit. For non-consigned items, this shipment transaction represents the revenue recognition.

• The interunit expected receipt EDI message can be sent to the customer, which contains the interunit ID.

• When the Deplete On Hand Quantity process runs for the inventory business unit, the auto-putaway process can be initiated to update the item quantities in the VMI business unit.

• The order management billing process (OMBILL) selects demand lines for invoicing and sends it to PeopleSoft Billing in order to create an invoice for the customer.

Note. Interunit orders that are created from sales order cannot be canceled by using the Cancel InterUnit Transfers page. Instead, you must receive the interunit order, then create a return material authorization against the order, and then receive the RMA.

When an interunit MSR for a consigned item is shipped and depleted, the system performs these tasks:

• An interunit ID is assigned to the demand line.

• An interunit transfer shipment transaction (031) is written to the transaction table (TRANSACTION_INV) for the inventory business unit. PeopleSoft Cost Management credits the inventory account and debits the cost of goods sold account.

• An interunit expected receipt EDI message can be sent to the customer, which contains the interunit ID.

• When the Deplete On Hand Quantity process runs for the inventory business unit, the auto-putaway process can be initiated to update the item quantities in the VMI business unit.

Note. Items cannot be pegged in a VMI business unit.

The Receiving Process

The customer has the option of providing receipt confirmation for consigned goods.

If the customer provides receipt feedback, they use the interunit receipt IP. With this message, the customer provides lot, serial, and container information, if being used, for all items received.

If the customer does not provide receipt feedback, the auto-putaway process is initiated from the Deplete On-Hand Quantity process. When the auto-putaway process runs for the VMI business unit, an interunit transfer receipt transaction (022) is written to the transaction table (TRANSACTION_INV) for the VMI business unit. The Putaway process will allow items from an owned location (from the inventory business unit) to be placed into a non-owned location, if the destination business unit is a VMI business unit.

The Goods Consigned at Customer check box on the VMI Options page indicates whether a customer who is receiving non-consigned items will report lot IDs, serial IDs, and staged dates on consumption transactions. If you elect to not reports these inventory identifiers, the items are removed from inventory of a FIFO basis.

• For lot controlled items, consumption occurs in the order of lot creation date.

• For serial controlled items, consumption occurs in the order of serial ID.

• For staged date controlled items, consumption occurs in the order of the date.

The Consumption Process

The customer communicates consumption one of two ways:

• The customer sends the item balance message to update on-hand quantities in the VMI business unit. The item balance in the message is compared to the item balance in the VMI business unit.

  • If the item balance is higher than the VMI business unit balance, a User Adjustment (050) transaction is created.

  • If the item balance is lower than the VMI business unit balance, a VMI Consumption (038) transaction is created.

• The customer sends a point of sale message or adjustment transaction to the VMI business unit, which creates a VMI Consumption (038) transaction.

All transactions are written to the transaction table (TRANSACTION_INV). The Create VMI Billing-Only Order process (IN_VMI_BILL) reads the transaction table and creates a billing-only sales order for all 038 transactions. A billing-only flag is located on the sales order header. The order management business unit is determined by associating it with the customer. The bill-only sales order creates an invoice in the billing business unit that is associated with the order management business unit, which is sent to the customer for the items consumed.

The quantity on-hand is reduced in the VMI business unit when the transaction is processed.

When a non-consigned item is consumed at the customer site, only the quantity on-hand in the VMI business unit is updated.

The Return Process

The customer can return consigned items and non-consigned items to the supplying inventory business unit.

If the item is non-consigned, the VMI manager creates a PeopleSoft Order Management return material authorization (RMA) from the VMI business unit, to track the return of the item. The VMI manager also performs an inventory adjustment, which creates a User Adjust (050) transaction in TRANSACTION_INV.

If the item is consigned, the VMI manager creates a PeopleSoft Inventory return material authorization (RMA) for an external customer in the source business unit, to track the shipment and depletion of the item. The customer sends an adjustment transaction message, with an adjust type of A (VMI Return), which creates an adjustment transaction that is not eligible for billing. The adjustment message initiates the Deplete On Hand Quantity process, which depletes the quantity for the VMI business unit. The source business unit can receive against the RMA.

See Performing Interunit and Intercompany Transfers.

The Physical and Cycle Counting Process

The VMI manager can perform physical and cycle counts at the customer site on a periodic basis for auditing purposes. The VMI manager can then perform the Physical or Cycle Count process on your enterprise system. Negative adjustments will use a VMI Consumption (038) transaction code. If a consigned item has a negative adjustment, the transaction will be eligible for the Create VMI Billing-Only Orders process.

The Message Process

Inbound messages are sent to your enterprise system, from the customer, in order to keep item quantities in sync. Outbound messages are sent to the customer in order to notify the customer of expected receipts.

Asynchronous messages are used to receive item balance, point of sale, receipt, and adjustment information from VMI customers. Process the transaction by using the appropriate inventory transaction, which can be found from the SCM Integrations menu:

• Quantity Adjustment (INPVIADJ) process.

• InterUnit Receiving (INPJIURV) process.

• VMI Quantity On Hand EIP (VMI_QOH_EIP) process.

If lot, serial, container, or staged date information is on the message and maintained in the VMI business unit, it is stored as received. When goods are not consigned in the inventory location, inventory decreases can be sent to the system through messaging without lot or serial number. The message process removes items from VMI inventory on a FIFO basis. If the FIFO logic is applied, the message is set to an error status if the transaction quantity is going to cause the inventory balance to be negative.

Note. When both receipt and balance information is received from a customer, procedures should be established to ensure that transactions are processed in the proper order.

See Processing Electronic Data Interchange Transactions in PeopleSoft Inventory.

See EIPs for Fulfillment Transactions.

Inventory Transactions That Cannot and Should Not be Performed

These transactions are not allowed with a VMI business unit:

• Bin-to-bin transfers within a VMI business unit.

• InterCompany and Inter general ledger express orders from a VMI business unit or to a VMI business unit.

• A VMI business unit cannot be part of a distribution network.

• A VMI business unit cannot be part of the procurement setup.

These transactions can be performed, but a warning is received:

• Interunit transfers to a VMI business unit for non-consigned items.

  The movement of non-consigned items is typically performed by creating a sales order. If items are moved using an interunit transfer, there is no automatic mechanism to bill for the items.

• Express issue of items from a VMI business unit.

  Movement of items in a VMI business unit represents movement from a customer's inventory. In the case of consigned items, this results in a depletion for which the customer may be billed.

Replenishing VMI

To replenish VMI at the customer site, the VMI manager uses the VMI Replenishment component.

The VMI replenishment process creates a sales order in the order management business unit if the item is not consigned. The non-consigned item sales order has a source code of VMI. When the sales order is shipped, the VMI customer is billed for the items.

The replenishment process creates an interunit MSR in the inventory business unit if the item is consigned. When the interunit MSR is shipped, the VMI business unit is not billed for the items.

The VMI manager can review replenishment quantities and make adjustments prior to creating replenishment requisitions if needed.

The VMI manager has the option to run the Replenishment process and allow the system to immediately generate sales orders and MSRs. Or, the VMI manager can review replenishment requests, remove suggested requests, and then allow the system to generate sales orders and MSRs based on the adjustments.

Follow these steps to replenish VMI:

1. Run the Calculate VMI Replenishment Parameters process. (Optional)

2. Review replenishment parameters and make adjustments if necessary.

3. Run the VMI Replenishment process to create replenishment requests.

4. Review suggested replenishment requests. (Optional)

5. Process reviewed requests.

6. Continue the VMI Replenishment process.

Pages Used to Replenish VMI

Running The Calculate VMI Replenishment Parameters Process

Access the Calculate VMI Replenishment Parameters page.

The Calculate VMI Replenishment Parameters process runs similar to the Calculate Replenishment Parameters process with these exceptions:

• The replenishment lead-time is manually entered or can be calculated for the Calculate VMI Replenishment Parameters process.

• When calculating EOQ for non-consigned items, if there is no cost for an item in the VMI business unit, the process will use the item cost in the source business unit.

• It only updates the fields at the ship-to and item level.

Running The VMI Replenishment Process

Access the Process VMI Replenishment page.

The VMI Replenishment (IN_VMI_RPLN) process runs similar to the Replenishment process with these exceptions:

• On-hand quantity is determine at the location level in the VMI business unit.

• On-order quantity is the sum of sales and interunit orders for the ship-to and item combination for the source business unit.

Reviewing Suggested Replenishment Requests

Access the Review Replenishment Requests page.

The review replenishment requests page is used to review and delete suggested replenishment orders. Suggested orders that are not deleted, will be used to create MSRs and Sales Order after saving the page and then selecting the Process Reviewed Requests option on the Process VMI Replenishment page.

Creating VMI Messages

This section discusses VMI EIPs and how to:

• Set up VMI messages.

• Enter quantity adjustments to VMI stock.

• Publish the Interunit Expected Receipts message.

Understanding VMI Enterprise Integration Points

VMI inventory is on hand at a customer location. You and your customers can communicate inventory levels and inventory movement by using enterprise integration point messages. Four messages support VMI:

• VMI On Hand Quantity - inbound communication of inventory quantities that are on hand at the customer site.

• VMI Inventory Adjustment - inbound communication of inventory transactions at the customer site.

• VMI Interunit Receipt - inbound communication of goods received by the customer.

• VMI Expected Receipt - outbound communication of goods shipped to the customer.

Maintaining Inventory Balance Messages

You can receive updates to customer inventory quantities using EIP messages. There are two messages that support bringing inventory quantities into the PeopleSoft system. Both messages are inbound asynchronous messages that can be mapped to the X.12 852 Product Activity transaction.

• The VMI Inventory Adjustment message is used to bring adjustment transactions into the system.

  The adjustment can be an increase, a decrease, a scrap adjustment, or a return of VMI Goods. Adjustment data is stored in the transaction log using the 0910 transaction code.

• The VMI Quantity On Hand Message is used to bring inventory balances into the PeopleSoft system.

  When an inventory balance is received, the quantity in the message is compared to the on hand inventory already existing in inventory, and an inventory adjustment is made to synchronize the balances. Balance data is stored in the transaction log using the 0900 transaction code.

Transaction details can be entered manually on the VMI QOH and Inventory Adjust (BCT_INV_VMI_QOH) page or can be created using the EIP’s. When you save the transaction, PeopleSoft Inventory inserts the information into the transaction log. You then run the VMI Quantity On Hand process (VMI_QOH_EIP), which retrieves data from the transaction log and processes the transaction. Use the Transaction Maintenance (BCT_CTL_UPD) component to correct the errors and resubmit the transaction.

The message processing capabilities described below apply to both the VMI Quantity on Hand and the VMI Inventory Adjustment messages:

• Users may send in either the VMI OM Business Unit and Ship To Customer ID or the inventory location. Since these map one to one, the location can be determined if it is not included on the message.

• Users may send in either the Product ID or the Item ID. If product ID is sent in, the message processing will get the item ID from the customer, the VMI Business Unit or from the PROD_ITEM table.

• If goods are lot-, serial-, or staged date controlled and the customer is a consigned customer, the inventory control information must be included on the message.

• If goods are lot-, serial-, or staged date controlled and the customer is a non-consigned customer, the inventory control information must be included on the message when an increase to inventory is being done.

• If goods are lot-, serial-, or staged date controlled and the customer is a non-consigned customer, the inventory control information need not be included on the message if a decrease to inventory is being done. The message processing will remove goods from inventory on a FIFO basis, using lot birthdate, serial ID, or staged date to determine the oldest goods on hand. The FIFO processing cannot be used to drive inventory negative. The message will be set to Error status when this occurs.

Receiving VMI Interunit Messages

Inventory balances in the VMI business unit can also be updated using the VMI Interunit Receipt EIP. VMI Interunit transfer orders are created in the PeopleSoft system to move stock between the source inventory business unit and the VMI business unit. The VMI Interunit Receipt message updates inventory quantities that are received by the VMI customer. The VMI Interunit Receipt EIP is an asynchronous batch-subscribe message.

Processing VMI Interunit Expected Receipt Messages

The VMI Interunit Expected Receipt message is an asynchronous batch publish EIP that notifies the customers system that an inventory business unit has shipped an interunit transfer order. The VMI Interunit Expected Receipt EIP meets X.12 EDI requirements of the 943 - Warehouse Stock Transfer Shipment Advice transaction set and can be used with warehouse management systems. VMI Interunit transfer orders are created in the PeopleSoft system to move stock between the source inventory business unit and the VMI business unit.

The VMI Interunit Receipt message provides one option for notifying VMI customers that inventory has been shipped. You can use the Interunit Expected Receipt EIP in integrated implementations where a third-party system is controlling an inventory business unit. A message is generated when an interunit transfer order that has a destination business unit that is under external warehouse control is depleted. The third-party system uses the information from the interunit expected receipt message to validate the receipt of goods when the shipment arrives at the destination warehouse.

Pages Used to Enter and Process VMI Messages

Setting Up VMI Messages

To use the VMI Quantity On Hand message setup in PeopleTools:

• Activate the VMI_QUANTITY_ON_HAND message.

• Activate the message subscription properties.

• Setup an inbound asynchronous transaction defining the VMI_QUANTITY_ON_HAND message on each node that can send the message to the system.

• Verify the INVENTORY_VMI_QOH message channel is in Run mode.

To use the VMI Inventory Adjustment message setup in PeopleTools:

• Activate the VMI_INVENTORY_ADJUSTMENT message.

• Activate the message subscription properties.

• Setup an inbound asynchronous transaction defining the VMI_INVENTORY_ADJUSTMENT message on each node that can send the message to the system.

• Verify the INVENTORY_VMI_QOH message channel is in Run mode.

To use the VMI Interunit Receipt message setup in PeopleTools:

• Activate the VMI_INTERUNIT_RECEIPT message.

• Activate the message subscription properties.

• Setup an inbound asynchronous transaction defining the VMI_INTERUNIT_RECEIPT message on each node that can send the message to the system.

• Verify the VMI_INTERUNIT_RECEIPT message channel is in Run mode.

To use the VMI Interunit Expected Receipt message:

• Setup in PeopleTools:

  • Activate the VMI_EXPECTED_RECEIPT message.

    If using message chunking, set up the OnRouteSend PeopleCode Event on the message.

  • Setup an outbound asynchronous transaction defining the VMI_EXPECTED_RECEIPT message on each node that will receive the transaction.

    This step is required only if an XML message is being generated. This step can be omitted if the batch publish rule is set up to post to a flat file.

  • Verify the VMI_EXPECTED_RECEIPT message channel is in Run mode.

• Setup Enterprise Components:

  • Activate the VMI_EXPECTED_RECEIPT batch publish rule.

    Specify the appropriate output for the message (XML-based message or flat file). If you want to use message chunking select a Chunking Rule ID for the batch publish rule.

  • Setup the chunking rule mapping definitions if message chunking is to be used

• Setup at the Application Level - select the Use External Warehouse Control check box on the Inventory Definition-Business Unit Options page.

Note. The setup instructions above assume that the message environment has been set up in PeopleSoft Integration Broker.

See Also

Enterprise PeopleTools 8.46 PeopleBook:Integration Broker

Entering Quantity Adjustments to VMI Stock

Access the Inventory Adjustment page.

Note. The business unit’s default display options determine how many storage location levels appear when you access this page. If you are entering a storage location that requires additional levels, enter the storage area, then refresh the page to display the remaining levels for that area.

Note. The business unit defaults that you established on the Inventory Display Options page determine whether lot, serial, staged date, and configuration fields appear when you access this page. Any fields for which the default is Yes always appear. Any fields for which the default is No appear when you save or refresh the page, and only if they apply to the item in question.

Publish the Interunit Expected Receipts Message

Access the Interunit Expected Receipts page.

Creating Billing-Only Sales Orders

After consigned items are consumed, the transaction table (TRANSACTION_INV) is updated. To create an invoice for the consumed items, the Create Billing-Only Sales Order (IN_VMI_BILL) process must be initiated.

Page Used to Create Billing-Only Sales Orders

Performing Inquiries for VMI Transactions

This section discusses how to view VMI transactions:

Page Used to Perform Inquiries for VMI Transactions

Viewing InterUnit Status

Use the Review VMI Shipment Info page to view the status of MSRs and sales orders that are used to transfer stock to a VMI customer.

The destination business unit field must be a VMI business unit.