Understanding Order Fulfillment Processing

This chapter provides overviews of:

Click to jump to parent topicThe Order Fulfillment Process

PeopleSoft Inventory is delivered with the ability to handle one-step order fulfillment or multi-step order fulfillment. There are many options to tailor the steps in PeopleSoft fulfillment to match your work environment. Orders can be fulfilled in one step, several steps, or any combination in between based on the complexity of your shipping operations. You can use different steps in different parts of your organization.

The following diagram illustrates the possible fulfillment steps that you might use in your environment.

Potential Fulfillment Steps

Click to jump to top of pageClick to jump to parent topicState of Order Demand Lines

PeopleSoft Inventory tracks order demand lines throughout the fulfillment process and displays fulfillment state information on multiple pages and components. Demand lines processed in PeopleSoft Inventory have one of these fulfillment states:

Pending

The line is either incomplete, invalid, or on hold. Lines in a Pending state are ignored by fulfillment processes.

Unfulfilled

The line has been entered. The demand line's quantity could be partially or fully soft-reserved, promised, or lot-allocated but the line has not been released downstream to the next order fulfillment step.

Releasable

The line is ready to be released to picking. The line can be soft-reserved, promised, lot-allocated, or simply set to the releasable state.

Released

The line has been associated with a pick batch ID and released for picking. The line can be allocated or remain soft-reserved, promised, lot-allocated, or simply released for picking.

Confirmed

The Picking Confirmation process has subtracted the quantity picked for the order line from quantity balances at the material storage location level and has staged the demand line for shipping. The business unit level available balance has been updated but the on-hand balance has not yet been decreased.

Shipped

The quantity shipped has been recorded for the line.

Depleted

The Deplete On Hand Qty (Depletion) process has subtracted the quantity shipped from quantity balances at the business unit level and has inserted the shipping transaction into the TRANSACTION_INV table for costing.

Canceled

The line has been canceled in PeopleSoft Order Management or PeopleSoft Inventory. Sales order lines must be canceled using the Order Entry Form component in PeopleSoft Order Management. After the fulfillment stage indicated on the Demand Change Configuration feature, it must also be canceled on the Cancel/Hold Stock Requests page in PeopleSoft Inventory. All unshipped non-sales orders must be canceled in the Cancel/Hold Stock Requests page.

Click to jump to top of pageClick to jump to parent topicFulfillment Steps

During implementation of PeopleSoft Inventory, you must tailor the steps in PeopleSoft fulfillment to match your work environment. The following fulfillment steps can be combined or eliminated based on the needs of your environment.

Reservation

The reservation processes complete three tasks:

Each task can be performed independently. For example, a reservation process might reserve available quantity to a demand line and still keep it in the unfulfilled state because it did not meet the criteria of the reservation rules to be set to the releasable state. In addition, a reservation process can simply release demand lines downstream with no type of reservation if the item is not defined for soft-reserve or promise or if the reservation and backorder rules instruct the process to release a shortage downstream. A demand line can stay in the unfulfilled state and be partially or fully soft-reserved or promised.

Reservations can be initiated several different ways:

See Understanding Inventory Reservations.

Order Release

This step is a process that releases demand lines for picking by moving the line from the releasable state to the released state. On the Order Release process, you can select the Create Allocations action to allocate stock for the demand line (push pick plan). An allocation means that quantity in a specific material storage location has been reserved for a particular demand line. You can also choose to not create an allocation, requesting that the Order Release process just make suggestions (pull pick plan) without allocating stock at the material storage location level. The default value for allocation can be defined at the inventory business unit level for all order release processes using the Setup Fulfillment-Order Release page. In addition, the Order Release process can generate:

Note. A material storage location’s on-hand quantity and reserved or allocated quantity are maintained on the PHYSICAL_INV record.

See Understanding the Picking Process.

See Monitoring Inventory Quantity Balances.

Picking Feedback

Once you have physically picked the stock, enter picking results. When you have released demand lines to picking with an allocation, then the system assumes that you picked from the material storage locations specified in the hard allocation. You must enter exceptions to the allocations on the pick batch ID before confirming the pick results. When you have released demand lines to picking without an allocation, then the system does not know where to pull the stock from. In this case, you must enter all the picking results with the material storage locations used. The picking results can be entered into PeopleSoft Inventory by using:

Once picking results have been entered, the demand lines are marked for confirmation.

Picking Confirmation

Once picking results have been entered, use the Picking Confirmation process to:

The Picking Confirmation process can be launched directly from the process page, a link on the Material Picking Feedback page, or by auto-processing.

Packing

After running the Picking Confirmation process and before shipping orders, you can pack stock into shipping containers. The PeopleSoft Inventory packing feature enables you to create multiple levels of shipping containers and to keep track of how each container is packed. Shipping container information is listed on packing lists, advanced shipping notices (ASN), and is stored for historical inquiry purposes.

You can also use the Shipping Request transaction or the Pick Confirm transaction to create shipping containers. In addition, you can create shipping containers earlier in the fulfillment process by using the electronic data collection shipping container transactions to create single-level containers during picking. The electronic data collection transactions enable you to convert storage containers into shipping containers for tracking purposes.

To pack stock into shipping containers, use:

Shipping

In the shipping business process, demand lines are moved from any previous fulfillment state to the shipped state. The process also includes assigning demand lines to a shipping ID, entering or changing shipping information, generating backorders, and creating the necessary shipping documents.

To move orders to the shipped state, you can use any of the following methods:

Depletion

The Deplete On Hand Quantity (Depletion) process completes the final step in order fulfillment by; reviewing all the demand lines that have been shipped, depleting the Inventory business unit for the shipped stock (that is, reducing the on-hand balance and removing the soft-reserve for shipped materials), creating the costing records in the transaction history table (TRANSACTION_INV), and changing the demand lines state to depleted. Once this process has been run, the demand lines cannot be unshipped. The Deplete On Hand Quantity process can be launched directly from the process page, the Shipping/Issues component, the Express Issues page, or by auto-processing.

See Also

Canceling or Holding Orders Within PeopleSoft Inventory

Monitoring Order Fulfillment Status

Picking Inventory

Placing Sales Orders on Hold

Promising and Reserving Inventory

Shipping Inventory

Click to jump to top of pageClick to jump to parent topicPre-Allocated Items

Pre-allocated items include:

Allocated Pegged Items

The Complete Putaway process can allocate the incoming supply to the corresponding outgoing demand. This is a hard allocation that reserves the incoming stock at the business unit item and material storage location levels (that is bin location) to the outgoing material stock request or sales order. The pre-allocation of pegged items is defined in the Pegging Item Setup page and the Pegging Setup page.

See Pegging Supply and Demand.

Lot-Allocated Items

For lot-controlled items, you can create a lot allocation. The lot allocation is created when a specific lot has been allocated to a particular demand line. Lot allocations reserve quantity at the business unit item, lot, and material storage location levels. You can allocate lots to orders using the:

Enable lot allocation by selecting the Allow Lot Allocation check box on the Inventory Definition-Business Unit Options page.

Note. The LOT_CONTROL_INV record provides a business unit view of lot quantities by summarizing quantity information for lot-controlled items recorded in the PHYSICAL_INV record.

The following diagram illustrates the possible fulfillment steps that you might use for a lot-allocated item.

Order Fulfillment Steps for Lot-Allocated Items

See Allocating Lots to Orders.

See Managing Item Lots.

See Understanding the Picking Process.

Click to jump to top of pageClick to jump to parent topicSoft-Reserved Items

A soft reservation means that part of the business unit's total available quantity for the item has been reserved for an order demand line and cannot be consumed by other orders staged for fulfillment processing. With soft reservations, you process only those orders for which you have sufficient onhand stock to fulfill. You can reserve items marked for soft-reservation processing using a reservations process.

To manage short-supply situations, you can require that soft-reserved items be reserved only online from the Shortage Workbench using the Reserve Online check box on the Setup Fulfillment-Reservation page or the Setup Item Fulfillment page.

Note. The business unit’s available quantity and reserved quantity are maintained on the BU_ITEMS_INV record.

Orders can be released directly from an unfulfilled state, bypassing the reservations process. Soft-reserved items released in this manner are treated as shortages by the Order Release process if sufficient inventory is not available at the business unit level. If the Order Release Shortage option allows the release of shortages then any available quantity is reserved and the order is released. If no shortages exist, then the full quantity is reserved and the order released.

The following diagram illustrates the possible fulfillment steps that you might use for a soft-reserved item.

Order Fulfillment Steps for Soft-Reserve Items

Click to jump to top of pageClick to jump to parent topicPromised items

A promised order line is a demand line for which a scheduled shipment date has been promised based on Available to Promise (ATP) calculations of future supply and demand. Quantity for promised items is not soft-reserved or allocated (subtracted from the business unit or material storage location’s available quantity) until the demand line has been allocated by the Order Release process or confirmed as picked by the Picking Confirmation process. You can promise items marked for ATP processing using a reservations process.

Orders can be released directly from an unfulfilled state, bypassing the reservations process. ATP items released in this manner are promised and released if inventory is available at the material storage location level. Normal ATP rules are not followed as this is considered an exception situation.

The following diagram illustrates the possible fulfillment steps that you might use for an ATP item.

Order Fulfillment Steps for ATP-Items

Click to jump to top of pageClick to jump to parent topicNon-Soft Reserve, Non-ATP Items

Items can be defined for no reserve, promise, or lot-allocation. Using this method, the system does not tie up available stock in the business unit until the picking stage. This is especially useful for items that are plentiful and rarely experience shortages.

Note. For non-soft reserve, non-ATP items, you have the option to skip the reservation process by adding the orders in the releasable state. Use the Non-Soft Reserved State field on the Setup Fulfillment page to choose this option.

The following diagram illustrates the possible fulfillment steps that you might use for non-soft reserve, non-ATP item.

Order Fulfillment Steps for Non-Soft Reserve, Non-ATP Items.

Click to jump to parent topicConfiguration of Order Fulfillment

Order fulfillment requirements differ from organization to organization. PeopleSoft Inventory provides a wide variety of fulfillment processing options, giving you the flexibility to design the methods that best fits your needs. These methods fall into two categories:

Direct and auto-processing can be used separately or combined enabling you to tailor one or more fulfillment flows to match your physical environments for shipping stock.

Direct Processing

The direct processing methods enable you to select demand lines from any fulfillment state and place them directly in the desired downstream state; bypassing the in-between fulfillment steps. For example, an unfulfilled order can be shipped in one step, using one process. This enables users to release orders and ship orders from any previous fulfillment state, eliminating the need to run prerequisite processes in order to print pick plans or to ship demand lines.

Direct processing is launched by all process pages, online pages, and EIPs except the picking confirmation processes and the Deplete On Hand Qty process. Some process pages, online pages, and EIPs send demand lines one step downstream while others can send demand lines down more than one step. For example, the Reserve Materials process page sends orders from the unfulfilled state to the releasable state, one step down. However, the Front End Shipping Request process page can send orders from the unfulfilled or releasable state to the shipped state.

Auto Processing

The auto processing methods enables you to combine and run multiple fulfillment steps together and the system enforces all the rules and restrictions of each fulfillment step included. Auto processing does not string together multiple programs in process-scheduled jobs; it is a fulfillment engine process.

This auto-processing methods differs from the direct processing methods in that the rules of each fulfillment step are enforced. For example, if you use auto-processing to send an order from the releasable state to the shipped state, then the system will enforce any picking rules, including not picking from any restricted stock quantities. However, if you use direct processing to move an order from the releasable state to the shipped state, then the system selects the stock quantities that you direct, regardless of the picking rules.

Configuration Options

In this section, we will review some of the order fulfillment configurations that could be used in your environment.

Click to jump to top of pageClick to jump to parent topicAuto-Processing Options

Auto-processing enables you to automate the system steps required to fulfill orders. If you have simple fulfillment requirements, you can streamline all of the steps. If the requirements are more complex, you can choose which steps to automate and which to control manually. Auto processing can be launched from several different process pages, online pages, and EIPs. The default structure for auto-processing can be defined at the business unit level using the Auto-Processing Options tab of the Setup Fulfillment-Fulfillment Engine Options page. If the business unit defaults are blank, then the system looks at the setID level using the Fulfillment Engine Options page. If enabled, the auto-processing option can also be changed for the individual process instance using the process page, online page, or EIP.

The options for auto-processing include:

Using the Auto Release Run Control

When you use the auto-processing option on the Reserve Materials process, Create/Update Stock Request component, the Fulfillment Workbench (when using the reserve action), and Inventory Reservation EIP, the demand lines can be processed passed the released state by defining a run control ID for the Order Release process in the Auto Release Run Control field located in the Fulfillment Engine Options components. The parameters defined on the Order Release run control are used to process the orders through the Order Release Request process. The run control ID could also release the orders further downstream based on the settings in the Auto-Processing Option field on the run control.

Examples of Auto-Processing Configurations

For example, to streamline the entire fulfillment process using auto-processing:

  1. Define the Order Release run control XYZ and select the Advance to Depleted option in the Auto-Processing Option field of this run control.

  2. Enter the XYZ run control ID in the Auto Release Run Control field located in the Reserve Materials Process row of the Setup Fulfillment-Fulfillment Engine Options page.

This setup tells to system to default the Reserve Materials process page to take demand lines from the unfulfilled state to the shipped state. When items are always stored in the same material storage location and you do not need to enter shipping information, you can use this method to streamline the entire fulfillment process, from reservations through depletion, and require little manual intervention. If you choose this fulfillment configuration, you must use create an allocation on the Order Release process page (push picking plan), and you cannot process any picking exceptions that may occur. This configuration is not recommended when processing lot, serial, ship serial, or staged date-controlled items; if you must enter pro numbers or miscellaneous charges; or if you must validate kits before shipment.

If you want to take streamline most of your fulfillment steps but you need to enter picking feedback exceptions, you can:

  1. Define the Order Release run control XYZ and select the No Auto-Processing option in the Auto-Processing Option field of this run control.

  2. For the Reserve Materials Process row of the Setup Fulfillment-Fulfillment Engine Options page, selectAdvance to Released for the Auto Processing Option field and enter the XYZ run control in the Auto Release Run Control field.

  3. For the Materials Picking Feedback or Picking Confirmation rows (or both) of the Setup Fulfillment-Fulfillment Engine Options page, selectAdvance to Shipped for the Auto Processing Option field.

The system then streamlines the reservations, picking, and shipping operations but permits you to enter picking exceptions. In addition, shipping information can be entered on the Material Picking Feedback page or the Picking Confirmation process page.

For more detailed shipping information, you can stop auto-processing in the confirmed state and then use the Shipping/Issues component or the fulfillment engine's shipping request process to enter shipping and picking information. Then use auto-processing to launch the Deplete On Hand Quantity process.

When you want to control the reservations and picking steps but the shipping requirements are simple, you can use auto-processing on the second portion of the fulfillment process. This enables you to use either a push or a pull picking plan and to enter picking exceptions.

Click to jump to top of pageClick to jump to parent topicExpress Fulfillment

Express issue processing is ideal for environments with small stockrooms and simple shipping needs; such as, a stock pickup window. With this direct processing method, you use the Express Issue component to enter the information required to get the requested stock to the customer or department. You can create internal orders, external orders, interunit transfers, and return-to-vendor orders from this component. Once the order is created and saved, the demand lines are placed in the shipped state. Using the auto-processing options for Express Fulfillment, you can then have the system launch the Deplete On Hand Quantity (Depletion) process at save time along with any direct invoicing process.

The following diagram illustrates the express fulfillment option:

Express Issue

This option is appropriate when you process only small volumes of stock and when you communicate directly with an internal department representative or customer while entering the order. Express issue entries cannot handle future shipment dates, kits, approval processing, loads, planned loss, backorders, or ad hoc requisitions. There is no logic built into express issue picking. You simply tell the system what items were picked from which material storage location. In addition, because you must request and ship the stock during a single session, you cannot use this method for existing orders or customer shipments.

See Also

Creating Online Orders Using Express Issue in PeopleSoft Inventory

Click to jump to top of pageClick to jump to parent topicMoving Orders to the Shipped State

These direct processing methods enable you to move demand lines to the shipped state, bypassing any fulfillment steps that are unnecessary in your environment.

Use the front-end shipping requests to move demand lines from an unfulfilled or releasable state to a shipped state. The shipping request can be launched by the:

The following diagram illustrates the front-end shipping options:

Front-End Shipping

Use the shipping requests to move demand lines from an unfulfilled, releasable, released, or confirmed state to a shipped state. The shipping request can be launched by the:

The following diagram illustrates the shipping request options:

Shipping Requests

Click to jump to top of pageClick to jump to parent topicLaunching Processes from Online Components

If you must process orders immediately, you can launch the downstream process when you save the following online components:

To use this feature, select the Auto Process Save check box for the component on the Setup Fulfillment-Fulfillment Engine Options page (business unit level). If the business unit level is blank, then the system looks to the Fulfillment Engine Options page at the setID level.

PeopleSoft recommends that you use caution in environments in which you save often during the transaction. The order information remains after the page is saved; any subsequent modifications to the order in the same session may result in online errors.

Note. You can also run each of these processes manually. Click the Reserve button on the Create/Update Stock Request-Stock Request Summary page to launch the Reserve Materials process, click the Run Picking Confirmation link on the Material Picking Feedback page to launch the Picking Confirmation process, or click the Run Process link in the Shipping/Issues component or the Deplete On Hand Qty link on the Express Issue component to launch the Deplete On Hand Qty (Depletion) process.

Click to jump to top of pageClick to jump to parent topicAuto Processing to Invoicing in PeopleSoft Billing

Intercompany transfers and sales orders originating in PeopleSoft Order Management often require the automatic creation of PeopleSoft Billing invoices to accompany the shipment. When you want to use auto-processing for such orders, you can take advantage of the Direct Invoicing with Auto-Ship multiprocess job (DIRAUTO) located in the Ship and Invoice process page. This job streamlines picking confirmation, shipping, and invoicing and prints some of the necessary shipping documentation. At the same time, it enables you to retain manual control of the reservations and picking steps and to enter picking exceptions.

PeopleSoft delivers the Direct Invoicing with Auto-Ship multiprocess job with these processes:

When you save the Ship and Invoice page, PeopleSoft Inventory creates a run control ID for the Picking Confirmation process and launches the multi-process job. The Picking Confirmation process then automatically calls the Deplete On Hand Qty (Depletion) process. The Deplete On Hand Qty (Depletion) process in turn creates run controls (using the same run control ID) for the Packing Slip, Shipping Notices, OM Billing Interface, InterUnit Transfers Bill Load, and invoicing processes.

Note. If the job terminates prematurely, you can manually run any remaining processes for which the system has created run controls.

See Also

Understanding the Direct Invoicing Jobs

Billing Orders

Click to jump to parent topicFulfillment Process Exceptions

In some cases, you must adjust orders after they have undergone some of the fulfillment steps. Situations that require such adjustments include removing stock from shipments after reserving, picking, confirming, or shipping the order lines. PeopleSoft Inventory enables you to enter exceptions at various points in the fulfillment process so that you can update your system when you physically manipulate orders.

Adjusting Order Lines in the Unfulfilled or Releasable States

When you must change demand lines that have been lot-allocated, soft reserved, or promised but not yet picked, you can use the Shortage Workbench to perform several actions, including:

Unpicking Order Lines

Unpicking refers to reversing the picked state of order lines that have been picked or pick confirmed but not shipped. Possible reasons for unpicking include: to reallocate material to higher-priority order lines, to update the records when a customer decreases the requested quantity or changes the items ordered, to pick substitute items, to change the material storage location from which stock was picked, or to correct errors made during picking feedback. You can unpick using the:

 

Unpicking is an umbrella term encompassing two similar procedures:

If stock has been placed into a shipping container or assigned to a shipping serial ID, you must release the association before unpicking the order line.

Unshipping Order Lines

Unshipping is the act of reversing the state of order lines that have been shipped but not depleted. You unship order lines using the Shipping/Issues component. To unship:

  1. Select the demand lines to unship.

  2. Select the Do not ship/Do not include option for the Ship Action field.

  3. Save the Shipping/Issues component.

Order lines that contain backordered quantities are eligible for unshipping, but if you later decide to reship such an order line, the quantity shipped still excludes the backordered quantity.

You cannot unship order lines once they have undergone the Deplete On Hand Qty (Depletion) process.

See Also

Running the Reserve Materials Process

Managing Stock Requests Online

Monitoring Inventory Quantity Balances

Packing Orders for Shipment

Click to jump to parent topicFulfillment Lead Times

PeopleSoft Inventory uses lead times to ensure accurate supply and demand projections and to control fulfillment processing. Some lead times, such as the average shipping lead time, are for informational purposes only and are discussed elsewhere.

Closure-Calendar Processing and Lead Days

The Closure Calendar page enables you to require closure-calendar validation and processing for shipping, receiving, and materials management activities in the business unit. If you have defined closure dates and selected the Use Closure Calendar check box on the Setup Fulfillment-Reservation page, the system ensures that only open business days are included in lead-time calculations by adding one day to the lead time for every day that the business unit is closed. For example, when calculating reservation lead days, PeopleSoft Inventory verifies that the date range does not include closed days; if it does, the system adds any closed days to the to date (today plus the number of reservation lead days). Therefore, the resulting lead time includes today plus the number of reservation lead days and closed days.

See Also

Calculating Historical Lead Time

Establishing Operation Closure Dates

Click to jump to top of pageClick to jump to parent topicReservation Lead Days

Reservation lead days represent the number of days required to reserve, pick, pack, and ship the majority of the items in the business unit. The value defined for the business unit (on the Setup Fulfillment-Reservation page) becomes the default for the item level; you can override it. The reservation lead days entered on the Setup Item Fulfillment page represent the number of days required to reserve, pick, pack, and ship a particular item.

The reservation lead days are used by the reservation processes to:

Note. Reservation processing can reserve or promise stock to a demand line. The decision to move the line from the unfulfilled state to the releasable state is made during reservation processing based on the reservation and backorder rules, not the lead days.

You can use the Update Unreserved Orders page or the Shortage Workbench to view orders that are not within the reservation lead days.

The reservation lead days can be overridden on the reservation request if the Allow Override of Lead Days check box is selected on the Setup Fulfillment-Reservation page. In addition, to prevent entry errors, the override value cannot create a scheduled shipment date that exceeds the current date plus the max lead days entered on the Setup Fulfillment-Reservation page. The override value is never used for ATP processing. ATP always uses the reservation lead days at the business unit or item level.

Note. When the business unit requires closure-calendar validation and processing for receiving activities as defined on the Closure Calendar page, and when the calculated schedule shipment date for the requisition falls on a closure date, the system selects the first valid future date for the schedule shipment date. Therefore, the reservation lead days include only open business days.

See Also

Setting Up Fulfillment at the Business Unit and Item Levels

Understanding Inventory Reservations

Click to jump to top of pageClick to jump to parent topicATP Lead Days

ATP lead days represent the number of days that the majority of the items in the business unit can be fully promised for shipment. The business unit value (defined on the on the Setup Fulfillment-Reservation page) becomes the default for a particular item on the Setup Item Fulfillment page. You can override this default.

ATP lead days should be greater than the reservation lead days. If the scheduled shipment date falls within the ATP lead days, the ATP function promises only the full quantity requested. If the scheduled shipment date falls within the reservation lead days, the system promises either the full or partial quantity requested.

Note. If the business unit requires closure-calendar validation and processing for shipping activities as defined on the Closure Calendar page, and if the number of ATP lead days includes closure dates, the system adds one day for every closed day to the number of reservation lead days to compare against the scheduled ship date. Therefore, the lead days include only open business days.

See Also

Understanding Inventory Reservations

Click to jump to top of pageClick to jump to parent topicPicking Lead Days and Minutes

Picking lead days and minutes represent the time required to process a demand line from the time that it is picked to the time that it is shipped. The business unit defaults (defined on the Setup Fulfillment-Order Release page) can be overridden on the Order Release process page. When selecting orders for inclusion in a pick batch ID, the system adds the picking lead days and minutes to today’s date and time and compares the result to the scheduled ship date.

Note. If the business unit requires closure-calendar validation and processing for shipping activities as defined on the Closure Calendar page, and if the picking lead days include closure dates, the system adds one day for every closed day to the picking lead time to compare against the scheduled ship date. Therefore, the lead days include only open business days. Times are not included in these calculations.

Click to jump to top of pageClick to jump to parent topicReplenishment Lead Days

Replenishment lead days, established for a business unit/item combination on the Define Business Unit Item - Inventory: Replenishment page, represent the average number of days from purchase order placement to stock receipt. The ad hoc and reorder point replenishment methods use these values. (Fixed bin replenishment does not use lead days.)

When creating ad hoc requisitions, the Reserve Materials process adds the replenishment lead days to the required-by date to determine the expected date for the item.

Note. When the business unit requires closure-calendar validation and processing for receiving activities as defined on the Closure Calendar page, and when the calculated required date for the requisition falls on a closure date, the system selects the first valid previous date for the required date. It then takes this new required date and adds the replenishment lead days to arrive at the expected date. Therefore, the lead days include only open business days. If this calculation encounters a closure date, the system selects the first valid future date for the expected date.

You set up business unit replenishment parameters on the Setup Replenishment page. These parameters become the defaults for the item level on the Define Business Unit Item - Inventory: Replenishment page.

When the system calculates replenishment lead times, the Calculate Replenishment Parameters process (IN_RPL_RPM) averages the delta between an item's purchase order date and its subsequent putaway date. The purchase order date is required for this calculation.

See Also

Understanding Inventory Reservations

Replenishing Inventory

Click to jump to top of pageClick to jump to parent topicShelf Life

Shelf life values are used in lot expiration calculations and, when added to the lot creation date, represent how long a lot is valid for fulfillment processing (expiration date = creation date + shelf life). You establish these parameters for an item on the Define Business Unit Item - Inventory: Shipping/Handling page.

See Also

Managing Item Lots

Click to jump to parent topicEIPs for Fulfillment Transactions

PeopleSoft provides generic EIPs to enable you to integrate with third-party systems. These systems might include electronic data collection systems, transportation management systems, warehouse management systems, vendor or customers systems, or other material management applications within your enterprise. The EIPs that support fulfillment transactions use Application Messaging publish and subscribe technology to exchange transactional data related to order processing between PeopleSoft and third-party systems. This section discusses how the EIPs packaged with PeopleSoft support fulfillment transactions and provide cross-references to related information.

See Also

PeopleSoft Enterprise Integration PeopleBook

Click to jump to top of pageClick to jump to parent topicOrder Fulfillment Engine EIPs

In an integrated environment, the order fulfillment engine EIPs enable a third-party system to send requests to PeopleSoft Inventory that efficiently move orders to the desired fulfillment state in one step. These EIPs are especially useful when dealing with a large number of orders. PeopleSoft application messages from external systems can be processed through the PeopleSoft Integration Broker. These messages can request to move material stock orders and sales orders from one fulfillment state to another. PeopleSoft delivers these asynchronous messages that enable you to post a message to the Integration Broker and receive a response indicating that the message has been received. For each active inbound asynchronous transaction defined in the system for the source node and message version, the Integration Broker generates a subscription contract and runs the appropriate subscription PeopleCode. These requests are then placed in staging tables and processed by the fulfillment engine using the Fulfillment Requests process. The delivered application messages are:

See Also

Processing Inbound Application Messages for the Fulfillment Engine

Click to jump to top of pageClick to jump to parent topicTransportation Management System EIPs

The transportation management system (TMS) EIPs enable PeopleSoft Inventory to integrate with a third-party TMSs in order to maximize space utilization of loads and thereby minimize the costs of shipping goods. The outbound TMS EIP (TMS Order Release EIP) sends demand information from material stock requests and sales orders to the TMS where optimal loads are determined. An inbound TMS EIP (TMS Load Notification EIP) then uploads into PeopleSoft Inventory the carriers, loads, and dates based on optimization rules that take place within the TMS. The TMS Load Notification EIP can be used as either an asynchronous inbound batch subscribe message or as a synchronous inbound message that receives load optimization data from a TMS.

Setting Up the TMS Order Release EIP

To use the TMS Order Release EIP:

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

Setting Up the TMS Load Notification EIP

To use the TMS Load Notification EIP:

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

See Also

PeopleSoft Integration Broker PeopleBook

PeopleSoft Enterprise Integration PeopleBook

Click to jump to top of pageClick to jump to parent topicInventory Picking EIP

The Inventory Picking message is an asynchronous inbound batch subscribe EIP that receives picking feedback data into PeopleSoft from an electronic data collection system. The data is stored in the transaction log using any one of three transaction codes: Pick Location (0301), Complete Pick Batch Line (0302), and Complete Pick Batch (0303).

See Also

Entering Picking Feedback Using an Electronic Data Collection System

Click to jump to top of pageClick to jump to parent topicShipping Order Release EIP

The Shipping Order Release message is an outbound asynchronous EIP that provides third-party systems with details of orders that have been released for picking and shipment. This EIP supports integrated implementations in which a third-party system is used to pick, pack, and ship orders. With this EIP, you can publish both XML-based application messages and flat files. The Shipping Order Release EIP meets X.12 EDI requirements of the 940 − Authority to Ship Customer Order transaction set.

See Also

Creating Shipping Order Release Messages

Click to jump to top of pageClick to jump to parent topicAdvanced Shipping Notice EIP

The Advanced Shipping Notice (ASN) message is an asynchronous outbound batch publish EIP used to notify your customers that a sales order has been shipped. This message is passed to an external system or to the PeopleSoft CRM Field Service and PeopleSoft CRM Order Capture applications. The Advanced Shipping Notice EIP meets X.12 EDI requirements of the 856-Shipping Notice/Manifest transaction set and is also used with warehouse management systems. An ASN message is generated when a sales order entered from PeopleSoft Order Management has been depleted in PeopleSoft Inventory. You can specify whether to generate the ASN for all sales order shipments in the business unit, sales orders belonging to a specific shipping ID, sales orders for a specific sold to customer, or sales orders for a specific ship to customer.

See Also

Creating Advanced Shipping Notices

Click to jump to top of pageClick to jump to parent topicInternal Location Expected Receipt EIP

The Internal Location Expected Receipt message is a asynchronous outbound EIP that sends notification of an expected receipt transaction when an internal material stock request is depleted. Internal material stock requests are created to fulfill demand from a material storage location within the PeopleSoft Inventory business unit. Typically, you use the Internal Location Expected Receipts EIP when integrating with third-party point-of-use (POU) supplier systems or surgical resource management systems that manage supplies stored in internal par locations. The third-party system can use the data contained in the transaction message to manage receiving and restocking activities at the destination location. The Internal Location Expected Receipts EIP can be used with surgical resource software and POU applications.

See Also

Creating Internal Location Expected Receipts

Click to jump to top of pageClick to jump to parent topicInterUnit Expected Receipt EIP

The InterUnit Expected Receipt message is an asynchronous batch publish EIP that notifies a third-party system that a PeopleSoft Inventory business unit has shipped an interunit transfer order. The Interunit Expected Receipt EIP meets X.12 EDI requirements of the 943 - Warehouse Stock Transfer Shipment Advice transaction set and is also used with warehouse management systems. Interunit transfer orders are created in PeopleSoft to move stock between PeopleSoft Inventory business units. Typically, you use the Interunit Expected Receipt EIP in integrated implementations in which a third-party system is controlling a PeopleSoft Inventory business unit. A message is generated when an interunit transfer order with a destination business unit that is under external warehouse control is depleted. The third-party system can use the information from the interunit expected receipt message to validate the receipt of goods when the shipment arrives at the destination warehouse.

See Also

Creating Interunit Expected Receipts

Click to jump to top of pageClick to jump to parent topicPurchase Order and InterUnit Transfer Information Business Interlink

The Purchase Order and InterUnit Transfer Information request/response business interlink (GETPOIUT and RF_GETPOIUT) provides a third-party or another PeopleSoft database information regarding purchase orders and interunit transfer orders based on the business unit and requisition ID sent in on the request. This business interlink (RF_GETPOIUT ) can be integrated with the PeopleSoft CRM Field Service database.

To set up a business interlink, use PeopleTools to: