Understanding This AppendixThis appendix provides real-life scenarios for using PeopleSoft Inventory, including:
Scenario 1: Use auto processing in demand fulfillment.
Scenario 2: Use direct processing in demand fulfillment.
Scenario 3: Use the Fulfillment Workbench to handle exceptions.
Understanding This AppendixThe scenarios in this appendix are examples of how to use some of the features within PeopleSoft Inventory. These real-life examples describe some of the intended uses of these features, enabling you to understand how these features might be applied to your own organization.
Note. The real-life scenarios described within this PeopleBook may not conform to the business rules and procedures within your organization. Do not construe these examples as consulting or implementation advice for your specific industry or your individual organization. You should adapt or disregard the information here based on the needs of your organization. Oracle does not guarantee that the information included here will work as intended within your environment.
Scenario 1: Using Auto Processing in Demand Fulfillment
The demand fulfillment features in PeopleSoft Inventory provide a wide variety of options, giving you the flexibility to design the methods that best fits your needs. This scenario uses an auto-ship example to illustrate the unit of work concept within the auto-processing method. Auto-processing is useful in environments where stock is readily available and the pick plans are predictable.
The auto-processing methods enable 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; auto processing is a single fulfillment engine process. The selection criteria in the first fulfillment step are used to build the unit of work (the demand lines selected). The purpose of the auto-processing feature is to process the same unit of work moving from the first step in the process to the last step requested.
Auto-Processing From the Unfulfilled State
If you are designing an auto-processing flow that starts with Unfulfilled demand lines and moves them through the Releasable state to the Released, Confirmed, Shipped, or Depleted states, then you must predefine an Order Release run control. Within the auto-processing flow, the order release step is the only fulfillment step where additional parameters are needed. The fulfillment engine uses some of the parameters on the predefined Order Release run control in order to have the necessary instructions to process the unit of work sent to it from the reservations process.
Selection of the Unit of Work
The selection criteria in the first fulfillment step are used to build the unit of work (the demand lines selected). In the following example, the selection criteria on the Reserve Materials run control are used to build the unit of work since it is the first step in auto-process flow. Any selection criteria entered on the Order Release Request run control are ignored. If a demand line fails to be advanced to the Releasable state by the Reserve Materials process, then it is not part of the unit of work passed to the Order Release process. For example, if the Reserve Materials process selects 50 order lines and was able to move 45 lines to the Releasable fulfillment state, then the Order Release process would try to process the same 45 lines and place them in theShipped fulfillment state using information from the predefined Order Release run control.
If you want the fulfillment engine to use separate selection criteria for each process, then you should not use auto processing. Instead, you can define a PeopleSoft job with two processes in it: Reserve Materials and Order Release Request. Create a run control ID with the same name for both of these processes. The Order Release Request run control should have all the selection criteria required at order release time. In this scenario, the reservations process runs and completes, moving the requested demand lines to a Releasable state. Next, the Order Release process starts up from the beginning and selects only the demand lines that meet the Order Release selection criteria. Since there are two separate selection criteria, the processes would not have the same unit of work. The Order Release process could include the same or different demand lines than the reservations process; it might pick up more or less lines.
Step-by-Step Procedures to Auto ShipTo process the same set of demand lines (unit of work) from the Unfulfilled state to the Shipped state using auto processing, complete the following setup steps:
Define an Order Release run control for auto-processing to the Shipped fulfillment state.
Define a Reserve Materials run control for auto-processing to the Releasable fulfillment state and then pick up the Order Release run control to take the demand lines to the Shipped fulfillment state.
Once you have completed this setup, use the following steps to ship stock:
Run the Reserve Materials process using the predefined run control. This process instance uses auto-processing to move Unfulfilled demand lines to the Shipped state and yet still requires the lines to meet the rules and restrictions of each fulfillment step.
Use the picking plan generated by the Order Release process to physically pick the stock from the material storage locations used by the system. If stock is picked from a different material storage location than what is named on the picking plan, then use the Undo Fulfillment Request process to return the demand line to the Released state where you can alter the picking location and then process the demand line again to the Shipped state.
Generate any shipping documents needed. If necessary, these documents can be produced when the demand lines are in the Unfulfilled state.
Run the Deplete On Hand Quantity (Depletion) process to complete the final step in order fulfillment by depleting the PeopleSoft Inventory business unit for the shipped stock and marking the demand lines as depleted.
In this scenario, we are reviewing one method of using auto processing. This example does not represent all possible methods. For more information about the direct processing and auto processing methods, see the "Understanding Order Fulfillment Processing" chapter.
See Configuration of Order Fulfillment.
Defining the Order Release Run ControlAccess the Order Release Request process page (Inventory, Fulfill Stock Orders, Picking, Order Release Request):
On the Order Release Request page, define a new run control to be used for auto processing (auto-ship). We name this run control AUTO_SHIP and give it the following settings:
The Action field uses the option of Create Allocations, Make Suggestions, or Release Only.
The Auto Process field uses the option, Advance to Shipped.
The Auto Pick check box is selected.
The Output Options group box is used to select picking output. We select the Picking Plan check box to generate a pick plan report listing the material storage locations to be picked.
The Locations Selected By group box can be used to determine the manner in which the Order Release process suggests material storage locations from which to pick stock.
The Additional Options link can be used to define picking plan options and bar code information.
The File Overrides link can be used to review or change the file directory and file name for the picking extract file, item usage labels, or carton labels.
The fulfillment engine does not use any selection criteria defined on this run control, including:
The Selection Criteria group box.
The Date/Time Selection group box.
The Select Orders section at the bottom of the run control.
Define the Reserve Materials Run ControlAccess the Reserve Materials process page (Inventory, Fulfill Stock Orders, Stock Requests, Reserve Materials Process) :
On the Reserve Materials page, define a new run control that uses auto-processing. In this scenario, use the auto-ship method to select Unfulfilled demand lines and move them to the Released state where the Order Release process selects the lines and moves them to the Shipped state. We name this run control AUTO_SHIP and complete the following information:
Enter the selection criteria for the unit of work.
The selection is based on the search criteria entered on the fields from Business Unit to Product ID. In the page shot above, we have selected demand lines in the inventory business unit of US010 with a scheduled shipment date between September 1st and 5th of 2009 that use the carrier ID FAST.
In the Auto Release Option field, select an option to advance the demand lines to the Released state.
In the page shot above, we have chosen the field value of Advanced to Released. In this case, we must also enter a value in the Release Run Control field.
We could have chosen the field value of Use Auto-Processing Default for the Auto Release Option field. If we had chosen this option, then the system would use the default options for the Reserve Materials process defined under the Auto-Processing Options tab of the Setup Fulfillment-Fulfillment Task Options page (business unit level) or the Fulfillment Engine Options page (setID level).
In the Release Run Control field, select an Order Release run control that you have defined for this auto-processing flow.
In this example, we enter AUTO_SHIP, the Order Release run control defined in the first step. We have chosen the field value of Advanced to Released in the Auto Release Option field, therefore; we must enter a predefined run control for the Order Release process. This run control contains the parameters to be used when auto-processing orders after the Reserve Materials process.
Scenario 2: Using Direct Processing in Demand Fulfillment
In this scenario, we review one way to use the Front-End Shipping process to quick ship stock. This is just one example of how to use Front-End Shipping to solve your demand fulfillment needs. When using this scenario, think of procedures in your stock locations that could use part or all of this example.
The Front End Shipping Requests process (IN_FUL_SHF) submit requests to the fulfillment engine to move the demand lines of a material stock request or sales order from the Unfulfilled and Releasable states to the Shipped state. This process is a direct processing method that places demand lines directly in the Shipped state; bypassing any picking rules. If auto-processing is enabled, the Front-End Shipping process could then move the demand lines further downstream to the Depleted state. For more information about the direct processing and auto processing methods, see the "Understanding Order Fulfillment Processing" chapter.
See Configuration of Order Fulfillment.
In this scenario, we assume the following conditions exist in the inventory location:
Items are not always in stock.
The multi-step fulfillment process is too detailed and unnecessary for this inventory location. A two-step process in PeopleSoft Inventory is needed; move the orders to the Releasable state (usually reserving stock at this time) and then ship after the physical picking.
Warehouse personnel manually pick the stock without using a picking plan.
This shipping method should not allow personnel to ship demand lines from the Unfulfilled state; only demand lines in the Releasable state should be processed.
Another method of shipment, such as the Fulfillment Workbench, is used to handle exceptions.
Step-by-Step Procedures for Front-End ShippingIn this quick ship scenario, the step up steps are:
Restrict the Front-End Shipping Requests page to demand lines in the Releasable state.
Define the run control ID for Front-End Shipping.
Once you have completed this setup, use the following steps to ship stock:
Run the Reserve Materials process or online reservations to reserve stock for each order. Each demand line that is successfully reserved is move from the Unfulfilled state to the Releasable state.
Physically pick the stock without using a pick plan.
Use the predefined run control to launch the Front-End Shipping process. This moves the demand lines from the Releasable state to the Shipped state. If desired, you can move the demand lines into the Depleted state by using auto-processing.
Generate any shipping documents needed. If necessary, these documents can be produced earlier in the fulfillment cycle.
If not using auto-processing, run the Deplete On Hand Quantity (Depletion) process to complete the final step in order fulfillment by depleting the PeopleSoft Inventory business unit for the shipped stock and marking the demand lines as depleted.
Restricting the Front-End Shipping Requests to the Releasable StateIn this example, the orders are always shipped from a Releasable state and we do not want the users to be able to select demand lines in the Unfulfilled state. This enables users to work with their procedures without being concerned about erroneously shipping orders that are not available for shipment. For the Front-End Shipping Request page, we need to set the correct From State and prevent state overrides using either the:
Setup Fulfillment - Fulfillment Engine Options: From States page
The settings are applied at the inventory business unit level.
Fulfillment Engine Options: From States page.
The settings are applied at the SetID level to apply to multiple inventory locations. This page is only used by the system when there are no default settings defined at the inventory business unit level.
Defining Settings for one Inventory Business Unit
Access the Setup Fulfillment - Fulfillment Engine Options: From States page (Inventory, Fulfill Stock Orders, Fulfillment Rules, Setup Fulfillment, Fulfillment Tasks. Select the Fulfillment Task Options link and then select the From States tab.)
The settings on the Setup Fulfillment - Fulfillment Engine Options component are applied only to the inventory business unit identified at the top of the page.
For this scenario, we want to restrict the users of the Front-End Shipping Requests process page to demand lines within the Releasable fulfillment state. On the Setup Fulfillment - Fulfillment Engine Options: From States page, locate the row for the Front-end Shipping Requests and apply the following default settings:
Deselect the Allow State Overrides check box to prevent a user from changing fulfillment states on the Front-End Shipping Requests process page.
Deselect the Select Unfulfilled check box.
Select the Select Releasable check box.
When looking for the settings, the system looks first to the Setup Fulfillment - Fulfillment Engine Options component defined for the PeopleSoft Inventory business unit. If a default is not defined at this level for a particular option, then the system looks to the set ID level.
Defining Settings for Multiple Locations
Access the Fulfillment Engine Options: From States page (Set Up Financials/Supply Chain, Product Related, Inventory, Fulfillment Engine Options. Select the From States tab).
Use the Fulfillment Engine Options: From States page to apply the settings at the SetID level. This SetID is linked to one or more PeopleSoft Inventory business units on the TableSet Control - Record Group page using the record group, IN_17, Fulfillment Engine Options. The most specific default settings are used; therefore, the settings on this page are only used if there are no settings defined on the Setup Fulfillment - Fulfillment Engine Options: From States page (business unit level).
Locate the row for the Front-end Shipping Requests and apply the following default settings:
Deselect the Allow State Overrides check box.
Deselect the Select Unfulfilled check box.
Select the Select Releasable check box.
Defining the Run Control ID for Front-End ShippingAccess the Front-End Shipping Requests process page (Inventory, Fulfill Stock Orders, Shipping, Front-end Shipping Requests):
Define a new run control ID for the Front-End Shipping Requests process page. Users will enter the selection criteria from the Business Unit field to the Parent ID field. In the Override group box, notice that the From States are unavailable for change, the Select Unfulfilled check box is clear, and the Select Releasable check box is selected. These settings are derived from the Setup Fulfillment - Fulfillment Engine Options: From States page or the Fulfillment Engine Options: From States page.
In addition, you can use the Auto Process field to enable auto-processing from the Shipped state to the Depleted state. You can select :
Advance to Depleted: To enable auto-processing to the Depleted state for just this run control ID.
No Auto-Processing: To keep the demand lines in the Shipped state.
Use Auto-Processing Default: To use the default settings established on the Setup Fulfillment - Fulfillment Engine Options: Auto-Processing Options page (business unit level) or the Fulfillment Engine Options: Auto-Processing Options page (setID).
Scenario 3: Using the Fulfillment Workbench to Handle ExceptionsIn this scenario we look at some ways that the Fulfillment Workbench can be used to keep orders moving smoothly through demand fulfillment; including the ability to quickly:
Process large orders.
Fulfill backorders.
Exclude lines from a group.
Processing Large OrdersThe Fulfillment Workbench can be used to quickly process large orders without loading the data into the component's queue. For example, let us assume that the order MSR0000027 has 2,000 demand lines. We want to ship this order.
An authorized user can navigate to the Fulfillment Workbench page (Inventory, Fulfill Stock Orders, Fulfillment Workbench) and enter the following:
In the Action field, select the option Ship.
Enter the search criteria in the Selection Criteria group box to identify the large order. For this order we select the check boxes for the fulfillment states of the demand lines (Select Unfulfilled, Select Releasable, Select Released, Select Confirmed). We enter specific information in the Source, Source Bus Unit, and Order No fields in order to pick up just this order.
Click the Process button to write the transaction request to the staging tables. The transaction request can now be processed by the fulfillment engine using the Fulfillment Requests process. If you have selected automatic schedule processing on the Processing Defaults page of this workbench (use the Process Default link) or the Setup Fulfillment - Fulfillment Engine page, then the Fulfillment Requests process is launched when you click this button.
Use the Transaction Maintenance page (SCM Integrations, Transaction Error Handling, Maintain Transactions, Transaction Maintenance) or the Message Log to monitor the status of your transaction.
In order process this transaction. The system must have been properly setup. For more information on the setup of the Fulfillment Workbench, see the "Utilizing the Fulfillment Engine" chapter.
See Utilizing the Fulfillment Engine.
Fulfilling BackordersThe Fulfillment Workbench is a good vehicle to quickly process backordered demand lines when available stock arrives in the warehouse location. For example, let us assume there is one order with 10 lines. We originally used scenario 2 to process the order (see the above section: Scenario 2: Using Direct Processing in Demand Fulfillment). The Reserve Mateials process was run; 2 lines were backordered and 8 lines were moved to the Releasable state. We then used the Front-End Shipping process to move the 8 demand lines to the Shipped state. Right before we ship the 8 lines, we receive a shipment from our vendor that enables us to fulfill the 2 backordered lines. We want to ship the entire order together. Currently, 2 lines are backordered in the Unfulfilled state and 8 lines are on the shipping dock in the Shipped state.
An authorized user can go into the Fulfillment Workbench and create a transaction to take the 2 backordered demand lines, fulfill them with the stock from the inventory business unit and place the demand lines in the Shipped state. In the process, we can assign the same shipping ID as used on the 8 demand lines on the shipping dock.
Keep in mind that we need to reproduce any shipping documents that we might have printed for this shipment before we decided to add the 2 demand lines.
Once the new vendor shipment is received and putaway into the inventory business unit, we can use the Fulfillment Workbench to bring the 2 backordered lines to the Shipped state. First, an authorized user navigates to the Fulfillment Workbench page (Inventory, Fulfill Stock Orders, Fulfillment Workbench) and enters the following:
In the Action field, select the option Front End Ship.
Enter the search criteria in the Selection Criteria group box. For this order we select the Select Unfulfilled check box, and enter the correct values in the Source, Source Bus Unit, and Order No fields. Note that the Front End Ship launched by the Fulfillment Workbench can pick up Unfulfilled demand lines whereas the Front-End Shipping Requests process page can only pick up Releasable demand lines. This is possible because of the settings for the workbench are different from the process page.
Select the Demand Lines link to access the Demand Lines page of the workbench.
On the Demand Lines page of the Fulfillment Workbench, we can view all the lines of the order that meet our search criteria. On this page:
Select the demand lines using the Select check box on each demand line row.
Click the Add to Queue button.
Click the Fulfillment Queue link to access the Fulfillment Queue page of the workbench.
On the Fulfillment Queue page, we see both our demand lines that are currently backordered. Click the Ship Defaults link to access the Picking/Shipping Overrides page.
On this Picking/Shipping Overrides page, enter the Ship ID that was used for the other 8 demand lines of this order. Using this page, the Shipping ID override is applied to the entire transaction request. Click the OK button to return to the Fulfillment Queue page.
On the Fulfillment Queue page, click the Process button. The entered request is written to the staging tables to be processed by the fulfillment engine using the Fulfillment Requests process. If you have selected automatic schedule processing on the Processing Defaults page of this workbench or the Setup Fulfillment - Fulfillment Engine page, then the Fulfillment Requests process is launched when you click this button.
Excluding Lines From a GroupUse the Fulfillment Workbench to process a group while excluding part of that group. For example, let us assume that we want to ship all the orders within a particular load ID except one demand line. The group level is defined as a particular load ID (in this case, the load ID 0000000002), the detail level can be used to exclude a specific order or line in that load (in this case, order MSR0000029, line 2). Any demand lines being excluded at the detail level must exist within the selection criteria entered at the group level.
Creating the Group
First, we would create the group. An authorized user can navigate to the Fulfillment Workbench page (Inventory, Fulfill Stock Orders, Fulfillment Workbench) and enter the following:
In the Action field, select the option Ship.
In the Search By field, select the option Group.
Enter the search criteria in the Selection Criteria group box to identify the group. For this group, we enter the load ID 0000000001 that contains 4 demand lines. All the demand lines are in the Released state, so we select the Select Released check box.
Click the Add to Queue button.
Click the Orders link or the Demand Lines link to view the data within the queue.
Excluding Part of the Group
We want to exclude one demand line in this Load ID from the shipment. Once the group is created, select the Demand Lines link to access the Demand Lines page of the workbench. To exclude line 3 of the MSR0000011:
Select the Exclude check box on the demand line row. This action also selects the Select check box.
Click the Add to Queue button to add the exception to the fulfillment queue.
Click the Fulfillment Queue link to access the Fulfillment Queue page.
You can also exclude an entire order using the Orders page of the workbench. If the order is very large, you will want to avoid loading the order into the Fulfillment Queue by using the Fulfillment Workbench page to create an exclusion using the Detail option of the Search By field.
Viewing the Fulfillment Queue
Click the Fulfillment Queue link to access the Fulfillment Queue page where you can view the group and detail levels. On the Fulfillment Queue page:
Notice that the Group ID 1 selection criteria are listing in the Fulfillment Queue Group section.
Notice that the Fulfillment Queue Detail section displays the excluded order line.
Click to Process button to write the transaction request to the staging tables to be processed by the Fulfillment Requests process.