Header

Contains fulfillment transaction request header information.

Group

Contains fulfillment transaction request group level information. One request can contain one or more groups.

Detail

Contains fulfillment transaction request detail level information within a group.

LLS

Contains picking location, lot ID, serial ID, and staged-date information, plus staged date information.

Group Level

Fulfillment requests consist of one or more groups. When creating the fulfillment request, you define the group. In its simplest form, the group level is an order and a detail level is a specific order line. However, flexibility exists to define a group as being just about any selection criteria used within the fulfillment system. Examples of a group include an order number, load ID, carrier ID, pick batch ID, or shipping container ID.

It is important to note that when you define information at the group level, all demand lines meeting that selection criteria are processed. For example, if you want to ship all demand lines on a 1000 line order, then all you need to do is to create a group level containing that order number. If you want to exclude order lines or you want to process partial quantities on order lines, then you would add detail level entries to the fulfillment request only for those specific order lines in which you have exceptions. All other order lines are processed completely.

Information overriding specific fields on the demand lines being processed can also be entered at the group level. For example, on a shipping request you may want to assign a specific pro-number. By entering this information at the group level, all demand lines processed within this group are assigned that pro-number.

Note. Override information can be entered at the group level on fulfillment engine EIPs and the Fulfillment Workbench only. When using the run control requests process pages to initiate fulfillment requests, the override information applies to the full request.

Detail Level

The detail level enables you to further refine the group level selection by providing exceptions to demand lines within the group level definition. This level usually contains demand line level information; however, all group level selection criteria is available at the detail level. This flexibility enables you to define exceptions for individual demand lines or for groups of demand lines. The detail level can be used to:

• Include

  Enter individual demand lines or groups of demand lines at the detail level to add additional demand lines to the fulfillment request. For example, if you wanted to ship a full load ID but add an additional order at the last minute, you could enter the load ID at the group level and then enter the added order number at the detail level. This would allow the full shipment to be shipped under the same ship ID, and any override information entered at the group level would be applied to the added demand lines entered at the detail level.

• Exclude

  Enter individual demand lines or groups of demand lines to be excluded from the selection criteria entered at the group level. For example, if the group level is defined as a particular load ID, then the detail level can be used to exclude a specific order in that load. Demand lines being excluded at the detail level must exist within the selection criteria entered at the group level. Exclude is not a valid option when you are create new materials stock request demand lines.

• Process partial quantities

  Enter exceptions to process partial quantities on demand lines. For example, if order MSR0000100 is being shipped, but order line number 55 is being shipped short, then you would create a group level containing order number MSR0000100, and then add a detail level for line 55 containing the quantity that actually shipped on that line.

Note. When entering exceptions referencing a specific demand line, the quantity and UOM provided at the detail level is used in place of the values that currently exist in the system for that demand line. The exception to this rule is when using the "exclude" option. Demand lines being excluded are always excluded completely, so the quantity and UOM fields are never used in this situation.

Note. A detail level entry is referencing a specific demand line if one of four combinations of selection criteria is entered. The four combinations are the full demand key, pick batch ID and pick batch line number, external reference ID and external reference line number, and the TMS reference ID and TMS reference line number.

Note. When the selection criteria is processing a group of demand lines, then the open order quantity on the demand lines in the demand tables is used when processing the demand lines. Fulfillment requests that define group information at the detail level are rejected if values are entered in the quantity and UOM fields.

LLS

The LLS entry is used to further identify instructions on how a transaction should be processed. Information such as material storage locations, lot ID, serial ID, staged dates, and storage containers are carried at this level.

Note. Transactions shipping from an unfulfilled or releasable state that reference items under lot, serial, or staged date control must provide LLS level information.

Transaction Based Run Requests

When using transaction based fulfillment requests, each request is assigned a control ID that is tracked and controlled so that there is a history of the work being performed. If errors are found, the transaction request is rejected and users follow up by either reprocessing the transaction request after the error is fixed or by canceling the request. A series of staging tables and error handling pages are in place to manage this process.

A fulfillment transaction request could be used when:

• Fulfillment transaction requests are fed from external systems.

• Higher volume shipping operations use the Fulfillment Workbench to generate shipping transaction requests.

  The Fulfillment Workbench can be configured for simple data entry of an order number at a shipping station. The order number is entered or scanned from a bar code label, and the transaction request is generated. From that point on, the transaction request is tracked to ensure that it is processed successfully. Shipping station personnel can immediately continue their work processing the next shipment, knowing that the system will provide an audit trail of the work performed on each transaction request.

• Processing large orders.

  When processing large orders, a transaction request can be used to enable processing in a background mode, freeing you up to work on the next transaction request. Because all fulfillment transaction requests are tracked in the staging tables, control is provided to ensure that all requests are processed successfully.

• Multiple group levels must be processed.

  You can use a transaction request when processing multiple group levels because the run control request allows processing of only a single group level.

• Exceptions must be entered.

  You can use a transaction request when entering exceptions because the run control request does not allow entry of detail level information.

Run Control Based Run Requests

When using run control based fulfillment requests, the transaction request record is created and passed on to PeopleSoft Process Scheduler. PeopleSoft Process Scheduler initiates the fulfillment engine and processes the data. If any errors are found, the appropriate error message is sent to the message log and can be viewed from the process monitor. When initiating the fulfillment engine from a run control request, you can enter only group level information. Only a single group can be processed at any one time.

A run control fulfillment request could be used when:

• Processing work on a scheduled basis from PeopleSoft Process Scheduler.

  For example, if you must run reservations processing each night for a full business unit, then you can set up a reservations run control request using the Reserve Materials Process page. The request would be scheduled to run at the appropriate time each night using PeopleSoft Process Scheduler.

• Handling a low volume of fulfillment requests, where tracking and control of requests can be managed by viewing the process monitor.

• Processing large orders.

  When processing large orders, you can use the run control request to enable processing of the demand lines in a background mode. This frees you up to do other work.

BCT_CTL

Contains control information identifying request source and status.

BCT_DTL

Contains fulfillment request transaction header information.

INV_FUL_GRP_EC

Contains fulfillment request group level information.

INV_FUL_DTL_EC

Contains fulfillment request detail level information. This record could contain demand line level information or data to be excluded from the request (for example, at the group level you could have defined a carrier, and then at the detail level you could enter a specific order number to exclude).

INV_FUL_LLS_EC

Contains picking location, lot ID, and serial ID information.

TSE_BCT_FLD

Contains any errors encountered when processing the fulfillment transaction request.

0360

Create Stock Request

The Inventory_Create_Stock_Request EIP from external systems.

0361

Reserve

The Fulfillment Workbench and the Inventory_Reservation EIP from external systems.

0363

Picking Feedback

The Fulfillment Workbench (action of Pick Confirm) and the Inventory_Pick_Confirm EIP from external systems.

0365

Front-end Ship

The Fulfillment Workbench and the Inventory_Front_End_Shipping EIP from external systems.

0366

Ship

The Fulfillment Workbench, Packing Session page, and Inventory_Shipping EIP from external systems.

Auto Schedule Processing

Select to immediately process the requests. The Fulfillment Requests process is launched when the requests are posted to the staging tables. This option is used when processing EIP messages and Fulfillment Workbench requests.

Release Additional Locks

Select to instruct the fulfillment engine to release any locks not identified by the first processing group of data determined at run time. If this option is cleared, then all fulfillment transaction requests and demand lines meeting those requests are soft locked until they are finished processing. When the locks are released using this option, both fulfillment transaction requests and demand lines that were not included in the initial processing group are released to be processed by concurrent fulfillment engine processes.

Perform Validation

Select to have the fulfillment engine validate data loaded into the demand table (IN_DEMAND) by external applications.

Log Errors Option

There are two options:

• Transaction Error Log: Transaction request errors are kept in the staging tables and set to a status of error.

  Use the Transaction Maintenance page to view and correct these requests for resubmitting to the fulfillment engine.

• Message Log: Transaction request errors should be logged to the message log and the status of those transactions changed to cancel.

  This prevents fulfillment transactions from ever being set to error status in the staging tables.

Allow Processing Overrides

Select to enable the user to override the Processing Level, Processing Count, Commit Level, and Commit Count fields where provided on the Fulfillment Workbench, fulfillment process pages, and external messages.

Processing Count

Enter the number of lines that can be processed together by the fulfillment engine; in other words, define the size of the processing group. The processing count is used to tune an inventory environment that is running into database contention issues. A processing group should be defined to be smaller than the large fulfillment transaction requests of your environment. If the Processing Count field is blank or zero, then all the data identified by the transaction request is included in one processing group.

A processing group breaks up the request into smaller chunks for processing, consequently reducing table locks and contention issues. For example, with a processing count of 500, the system processes rows in groups of 500. If the transaction request includes 1,050 rows of data, the system process the data in 3 processing groups, 2 groups of 500 rows, and 1 group of 50 rows at the end of the process.

Note. If the fulfillment engine receives a commit count greater than the specified processing count and the processing level is the same as the commit level, then the processing count is set to the commit count. Also, if the pass through level field is greater than the value specified in the Processing Level field, then the processing group is expanded to include all data at the pass through level.

Processing Level

Determines how the system counts rows to reach the number entered in the Processing Count field. For example, with a processing count of 500 and a processing level of Order, the process would create a processing group per every 500 order numbers. You can create processing groups based on:

• Request: The number of separate fulfillment transaction requests.

• Order: The number of separate orders (material stock requests and sales orders).

  The system reorganizes the demand lines by order number and then processes each group separately. This reorganization of the data rows before processing could change the processing results. For example, if insufficient supply exists to fulfill the demand, the Reserve Materials process could change the allocation of stock and even override demand prioritization rules.

• Line: The number of demand lines.

Note. When the Processing Count field is not blank or zero, the Processing Level must be greater than or equal to the Commit Level field.

Commit Count

Enter the number of lines that can be committed to the database together by the fulfillment engine; in other words, define the size of the commit group. The commit count is used to tune an inventory environment that is running into database contention issues. A commit group is a subset of the processing group; therefore, the Commit Count field should be the same as or smaller than the value in the Processing Count field. If the Commit Count field is blank or zero, then all the data rows identified in the processing group are committed to the database together.

A commit group should break up the processing group into smaller chunks for committing to the database. For example, if you use a processing count of 500 and a commit count of 100, the system breaks up the transaction request of 1,050 data rows into 3 processing groups: 2 groups of 500 rows and 1 group of 50 rows. Each processing group is then broken up into commit groups of 100 rows each. The first 2 processing groups are divided into 5 commit groups each and the last processing group of 50 rows is 1 commit group. The system then commits the data to the database using 11 commit groups in total.

Note. If the fulfillment engine receives a pass through level field that is greater than the value specified in the Commit Level field, then the commit group is expanded to include all data at the pass through level.

Commit Level

Determines how the system counts rows to reach the number entered in the Commit Count field. For example, with a commit count of 100 and a commit level of Item, the system issues a commit to the database for every 100 item IDs. You can issue commits based on:

• Request: The number of separate fulfillment transaction requests processed.

• Order: The number of separate orders (material stock requests and sales orders) processed.

• Line: The number of demand lines processed.

• Item: The number of item IDs processed.

Note. When the Commit Count field is not blank or zero, the commit level must be less than or equal to the processing level.

Allow Pass-through Overrides

Select to enable the user to override the pass through level on the Fulfillment Workbench, fulfillment process pages, and the fulfillment engine EIPs.

Pass-through Level

Provides the ability to pass good transactions through the system while holding up transactions that need additional review. On the request pages and on the transactions, the pass through level can have these values:

• Request: Any errors in the transaction request prevent the entire request from being processed

• Order: Any errors on any line in the order prevent the whole order from being processed.

• Line: Errors prevent only the line with the error from being processed.

From a processing standpoint, the pass through level must be less than or equal to the processing level and commit level. If the fulfillment engine receives a pass through level greater than the specified commit level or processing level, the commit group or processing group is expanded to include all data at the pass through level.

Note. The Reserve Materials process has restrictions based on lead times and item availability that determine whether demand lines are reserved. Demand lines that do not pass these restrictions are not considered errors for pass through purposes.

Note. For the Order Release Request process page and the Fulfillment Workbench, the Pass-through Level does not impact the picking portion of the process.

Allow State Overrides

Select to enable the user to override the from fulfillment status of the orders in the group. This applies to the Order Release Request process, Front-end Shipping Requests process, Shipping Requests process, and the fulfillment engine EIPs for front-end shipping and shipping.

Allow Auto-Processing Override

Select to enable the user to override the auto-processing option on process page, Fulfillment Workbench, or request transactions from an EIP.

Auto Processing Option

Select the auto processing option to move your orders downstream to the desired state. Options include:

• No Auto-Processing: Select to have the system only complete the process or action that you are initiating on the current page.

  No additional processing will be launched.

• Advance to Released: Select to automatically process the orders to the released state from the Reserve Materials process, Create/Update Stock Request component, the Fulfillment Workbench (when using the reserve action), and Inventory Reservation EIP.

  The parameters defined on the Auto Release Run Control are used to process the orders through the Order Release Request process. These parameters could release the orders further downstream based on the Auto-Processing Option field.

• Advance to Confirmed: Select to automatically process the orders to the picking confirmed state from the Order Release Request process page, Material Picking Feedback page, the Fulfillment Workbench (when using the pick confirm action), and the Pick Confirm EIP.

• Advance to Shipped: Select to automatically process the orders to the shipped state from the Order Release Request process page, Material Picking Feedback page, the Fulfillment Workbench (when using the pick confirm action), and the Pick Confirm EIP.

• Advance to Depleted: Select to automatically process the orders to the depleted state from the Order Release Request process page, Material Picking Feedback page, Picking Confirmation process, Front-end Shipping Request process, Shipping Request process, the Fulfillment Workbench (when using any action except reserve), and all of the fulfillment engine EIPs except reserve.

Auto Release User ID

Enter any user IDs that has created a run control for the Order Release Request process page.

Auto Release Run Control

Select any run control for the Order Release Request process page defined by the user entered in the Auto Release User ID field to the left. This run control contains the parameters to be used when auto-processing orders from an unfulfilled state to another downstream state. The Auto-Processing Option field on the Order Release Request determines how far downstream the orders will be sent.

To find the correct value for this field and the Auto Release User ID field, the system first looks for a value on:

1. The current run control. If these fields are blank, then the system looks to:

2. The Auto-Processing Options tab of the Setup Fulfillment-Fulfillment Task Options page. If these fields are blank, then the system looks to:

3. The Setup Fulfillment page. If these fields are blank, then the system looks to:

4. The Auto-Processing Options tab of the Fulfillment Engine Options page. If these fields are blank, then no auto release is done.

Auto Process at Save

Select this check box to launch the auto-processing option when the online page is saved. The online pages include Create/Update Stock Request component, Material Picking Feedback page, Express Issue page, and the Shipping/Issues page.

Complete Flag

Choose a Complete Flag option to automatically performing picking functionality on demand lines that have no previous picking activity reported against them. The LLS segment and the override location are applied prior to implementing the complete flag logic. Using the Complete Flag, the line can be moved to different sub-states within the Released state, or, with auto-processing, moved downstream to the shipped or depleted states. The complete flag is used for run control pages, fulfillment engine transaction requests, the Fulfillment Workbench, and the Inventory Picking EIP. The Complete Flag options are:

• No Action: Takes no action on demand lines that have no previous picking activity reported against them.

• Complete Pick- Dft Ship Loc: Uses the default shipping location as the pick location for demand lines that do not already have the Confirm Flag set.

  The default shipping location is stored at both the business unit and business unit/item levels.

• Complete Pick- Leave Alone: With this option any lines within the selection criteria that do not have the Confirm Flag set are left alone.

  The Confirm Flag is not set on these demand lines.

• Complete Pick- Zero Quantity: Sets the zero picked flag for every line within the selection criteria if they do not already have the Confirm Flag set. Also removes and deallocates any current allocations.

• Pick Batch Complete: Removes every line within the selection criteria from the pick batch ID if they do not already have the Confirm Flag set.

• Pick Batch as Planned: Sets the Confirm Flag on any line that has had picking activity.

  In this situation picking activity is assumed to be satisfied if there are any allocations as well as if the demand line is a zero picked demand line. An error is generated for any lines that have not had any picking activity when using this option.

• Pick Line Complete: Removes the line from the pick batch ID if the Confirm Flag is not already set. It is only valid when referencing an individual pick/batch line at the group or detail level.

• Pick Line as Planned: Sets the Confirm Flag on any line that has had picking activity.

  In this situation picking activity is assumed to be satisfied if there are any allocations as well as if the demand line is a zero picked demand line. An error is generated for any lines that have not had any picking activity when using this option. This option is only valid when referencing a pick/batch line at the group or detail level.

Note. For fulfillment engine transaction requests, the level (header, group or detail) where the Complete Flag is located determines what level to apply the complete flag logic.

Allow Kit Re-Explode Overrides

Select to enable the user to override the default settings for the Execution Mode and the Kit Effective Date on the Kit Re-Explode process page.

Execution Mode

Choose the action to be performed by the Kit Re-Explode process. The option are:

• Report Only: Generates a listing the differences between the kit components on the order to the current product kit definition.

  This listing can be viewed on the Kit Re-Explode Results inquiry page.

• Report and Re-Explode: This option:

  • Generates a listing the differences between the kit components on the order to the current product kit definition to be viewed on the Kit Re-Explode Results inquiry page.

  • Changes the order to match the current product kit definition by adding or deleting demand lines containing kit components.

Kit Effective Date

Select the date of the component kit demand lines to be compared to the date range (effective date and obsolete date) on the Product Kit Summary page. The demand line dates are:

• Order Date

• Schedule Date

• Ship Early Date

• Today's Date

Auto Schedule Processing

Yes

Yes

Yes

Release Additional Locks

Yes

Yes

Perform Validation

Yes

Log Errors Option

Yes

Allow Processing Overrides

Yes

Yes

Yes

No

Processing Count

Yes

Yes

Yes

Yes

Processing Level

Yes

Yes

Yes

Yes

Commit Count

Yes

Yes

Yes

Yes

Commit Level

Yes

Yes

Yes

Yes

Allow Pass through Overrides

Yes

Yes

Yes

No

Pass through Level

Yes

Yes

Yes

Yes

Allow State Overrides

Yes

Yes

Yes

No

Allow Auto-Processing Override

Yes

Yes

Yes

No

Auto Processing Option

Yes

Yes

Yes

Yes

Auto Release User ID

No

Yes

Yes

No

Auto Release Run Control

No

Yes

Yes

Yes

Auto Process at Save

Yes

Yes

Yes

No

Allow Kit Re-Explode Overrides

Yes

Yes

Yes

Execution Mode

Yes

Yes

Yes

Yes

Kit Effective Date

Yes

Yes

Yes

Yes

Auto Schedule Processing

The system-defined value is No.

Release Additional Locks

The system-defined value is No.

Allow Processing Overrides

The system-defined value is No.

Processing Count

The system-defined value is zero.

Processing Level

The system-defined value is Line.

Commit Count

The system-defined value is zero.

Commit Level

The system-defined value is Line.

Allow Pass-through Overrides

The system-defined value is No.

Pass-through Level

The system-defined value is Demand Line for reserve transactions and Request for shipping transactions.

Allow State Overrides

The system-defined value is No. The following states are set:

• For reservations, the only from state is Unfulfilled.

• For Order Release, the default from state is Releasable.

• For Picking Confirmation, the default from state is Released.

• For front end shipping, the default from state is Unfulfilled and Releasable.

• For shipping, the default from state is Confirmed.

Allow Auto-Processing Override

The system-defined value is No.

Auto Processing Option

The system-defined value is No Auto-Processing.

Auto Process at Save

The system-defined value is No.

Fulfillment Engine Options

INV_FUL_DFLT

Set Up Financials/Supply Chain, Product Related, Inventory, Fulfillment Engine Options

Define the fulfillment engine processing options for the set ID level. This 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.

TableSet Control - Record Group

SET_CNTRL_TABLE1

PeopleTools, Utilities, Administration, Tableset Control, Record Group

Select the SetID for the record group, IN_17, Fulfillment Engine Options to link the fulfillment engine processing options for the set ID level to the business unit (set control value).

Setup Fulfillment-Fulfillment Tasks

OF_SETUP1_INV

Inventory, Fulfill Stock Orders, Fulfillment Rules, Setup Fulfillment, Fulfillment Tasks

Define fulfillment engine defaults at the business unit level.

Setup Fulfillment-Fulfillment Task Options

INV_FUL_DFLT_BU

Select the Fulfillment Task Options link on the Setup Fulfillment-Fulfillment Tasks page.

Define fulfillment engine processing options for the business unit level.

Page/Process and Transaction

Displays the type of interface that uses the processing options:

• Reserve Materials Process: Use this row to define the default processing options to be used by the Reserve Materials process page.

• Create/Update Stock Request: Use this row to define the default processing options to be used by the Create/Update Stock Request component.

• Order Release Request: Use this row to define the default processing options to be used by the Order Release Request process page.

• Undo Fulfillment Request: Use this row to define the default processing options to be used by the Undo Fulfillment Request process page.

• Picking: Use this row to define the default processing options to be used by the Inventory Picking process page under the SCM Integrations menu.

• Material Picking Feedback: Use this row to define the default processing options to be used by the Material Picking Feedback page.

• Picking Confirmation: Use this row to define the default processing options to be used by the Picking Confirmation process page.

• Front-end Shipping Requests: Use this row to define the default processing options to be used by the Front-end Shipping Requests process page.

• Express Issue: Use this row to define the default processing options to be used by the Express Issue page.

• Shipping Requests: Use this row to define the processing options to be used by the Shipping Requests process page.

• Shipping/Issues: Use this row to define the default processing options to be used by the Shipping/Issues component.

• Deplete On Hand Quantity: Use this row to define the default processing options to be used by the Deplete On Hand Quantity process page.

• Kit Re-Explode: Use this row to define the default processing options to be used by the Kit Re-Explode process page.

• Fulfillment Workbench and Request to Reserve: Use this row to define the default processing options for the Fulfillment Workbench page when using an action of Reserve to move an unfulfilled order to another state.

• Fulfillment Workbench and Request Picking Feedback: Use this row to define the default processing options for the Fulfillment Workbench page when using an action of Pick Confirm to move a released order downstream.

• Fulfillment Workbench and Request to Ship (front-end): Use this row to define the default processing options for the Fulfillment Workbench page when using an action of Front End Ship to move an unfulfilled or releasable order to shipped status.

• Fulfillment Workbench and Request to Ship: Use this row to define the default processing options for the Fulfillment Workbench page when using an action of Ship to move an unfulfilled, releasable, or released-pick confirmed order to shipped status.

• Transactions and Create Stock Request: Use this row to define the default processing options for fulfillment transaction requests posted by the EIP, Inventory_Create_Stock_Request.

• Transactions and Request to Reserve: Use this row to define the default processing options for fulfillment transaction requests posted by the EIP, Inventory_Reservation.

• Transactions and Request Picking Feedback: Use this row to define the default processing options for fulfillment transaction requests posted by the EIP, Inventory_Pick_Confirm.

• Transactions and Request to Ship (front-end): Use this row to define the default processing options for fulfillment transaction requests posted by the EIP, Inventory_Front_End_Shipping.

• Transactions and Request to Ship: Use this row to define the default processing options for fulfillment transaction requests posted by the EIP, Inventory_Shipping.

Allow State Overrides

Select to enable the user to select a different From State in the fulfillment transaction request.

Unfulfilled, Releasable, Released, Confirmed, Shipped, and Depleted

Select the from state (or starting fulfillment status) of the orders to be moved to another status by the fulfillment engine.

Group

When working with group level information, the quantity and UOM fields are not entered on the transaction. In this case, the quantity and UOM on the demand lines within the group are converted to the stocking UOM for picking purposes.

Detail

You can enter any valid UOM for the item. The quantity associated with this UOM is converted to the stocking UOM for picking. If you leave the UOM field blank, then the system uses the standard UOM for the item.

LLS

You can enter any valid UOM for the item. The quantity associated with this UOM is converted to the stocking UOM for picking. If you leave the UOM field blank, then the system uses the standard UOM.

Header

Contains fulfillment request transaction header information.

Group

Contains fulfillment request group level information.

Detail

Contains fulfillment request detail level information. This record could contain demand line level information or data to be excluded from the request (for example, at the group level you could have defined a carrier and then at the detail level you could enter a specific order number to exclude).

Loc/Lot/Ser (LLS)

Contains picking location, lot ID, and serial ID information. This level applies only to the front-end shipping and shipping EIPs.

INVENTORY_CREATE_STOCK_REQUEST

Inbound

Asynchronous

InventoryCreateStockRequest

No

Third-party system

INVENTORY_RESERVATION

Inbound

Asynchronous

InventoryReservation

No

Third-party system

INVENTORY_PICK_CONFIRM

Inbound

Asynchronous

InventoryPickConfirm

No

Third-party system

INVENTORY_FRONT_END_SHIPPING

Inbound

Asynchronous

InventoryFrontEndShipping

No

Third-party system

INVENTORY_SHIPPING

Inbound

Asynchronous

InventoryShipping

No

Third-party system

Template Maintenance - Definition

IN_TM_OPR_FLD

Inventory, Fulfill Stock Orders, Fulfillment Rules, Template Maintenance, Definition

Create or modify a template. Templates define what actions and fields appear to the user when using the Fulfillment Workbench or the Shortage Workbench.

Template Maintenance - Permissions

IN_TM_OPR_SEC

Inventory, Fulfill Stock Orders, Fulfillment Rules, Template Maintenance, Permissions

Identify the individuals who can access this template on the Fulfillment Workbench or the Shortage Workbench. Also, identify the individuals who will maintain this template.

Template Permissions Inquiry

IN_TM_OPR_INQ

Inventory, Fulfill Stock Orders, Fulfillment Rules, Template Permissions Inquiry

Inquire on the existing templates defined for a set ID, inventory business unit, user role, or user ID. This page displays all templates meeting the search criteria and identifies if the template is active, who maintains the template, and who can access the template.

Category

Enter categories to:

1. Define the actions that a user can perform on the Fulfillment Workbench. There are four categories, or actions, delivered with the template code FULFIL_WRKBENCH:

   • RESERVE: Enables the user to move an unfulfilled order to releasable state.

   • FRONTENDSHIP: Enables the user to move an unfulfilled order or releasable order to shipped state.

   • PICKCONF: Enables the user to move a released order to the shipped state.

   • SHIP: Enables the user to move an unfulfilled order, releasable order, or pick confirmed order to shipped state.

2. Define the pages that a user can access on the Shortage Workbench.

   There are three categories delivered with the template code SHORT_WRKBENCH:

   • DEMANDLINES: Enables the user to access the Demand Lines View of the Shortage Workbench.

   • DEMANDSUMMARY: Enables the user to access the Demand Summary View of the Shortage Workbench.

   • ITEMVIEW: Enables the user to access the Item View of the Shortage Workbench.

Click the Insert Row button to add more than one category to the same template.

Required

Identifies whether the Category field is required or not.

Default

Select one category to be the default category. When a user enters the Fulfillment Workbench using this template ID, this category is the default value in the action field. When a user enters the Shortage Workbench using this template ID, this category is the default view in the View By field.

Search By

For the Shortage Workbench, the only value available in this field is SEARCH.

For the Fulfillment Workbench, define the available options for each action in the Search By field. The subcategories determine how the user groups the demand data for processing. Click the Insert Row button to add more than one subcategory. There are two subcategories, or search by options, delivered with the template code FULFIL_WRKBENCH:

• GROUP: Select to define the fields available at the group level to search and retrieve demand data.

• DETAIL: Select to define the fields available at the detail level to search and retrieve demand data.

Required

Identifies whether the value in the Search By field is required or not.

Sort

Select to sort the search criteria fields in the scroll area by sequence number.

One Column

Select to have the Workbench display the search criteria fields in one column. This is the default setting,

Two Column

Select to have the Workbench display the search criteria fields in two column. The system initially assigns every other field to the second column; however, you can change this for the individual field using the Display column in the Scroll Area group box.

View Layout

Select to view how the Workbench will display to the user based on your current settings and fields chosen.

Insert Fields

Select to insert additional fields into the template. The new field is added just below the currently selected field or, if no field name is currently selected, at the bottom of the scroll area.

Delete Fields

Select to delete the currently selected field name from the scroll area. This will remove the field from the Workbench.

Seq Nbr (sort sequence number)

Identify the order that appears on the Workbench.

Required

Select to define a field as required to display on the Workbench. The template code defines certain fields as required. You can chose to make additional fields required. For a required field, the Delete Fields button is disabled.

Display

Choose to display this field in the first or second column in the Workbench layout.

Display Mode

Define the conditions for this search criteria field. Options are:

• Display: Field is display-only on the Workbench.

• Edittable: A value can be entered in this field on the Workbench.

• Hide: This field is hidden on the Workbench.

Default From and Default To

Use the Default From field to enter a default value to display on the Workbench. For fields defined to display as a check box, you can select to default the check box value to yes (selected) or no (unselected). If you want a range to display, use the Default From and Default To fields together. The range selects all values in the date range or alphanumeric sequence. The range option is valid only for specific fields based on the template code and cannot be used with check box type fields.

Demand Source

Select the PeopleSoft application source of the orders that the user of the Fulfillment or Shortage Workbench can view and change. For example, a customer service representative might be limited to sales orders from PeopleSoft Order Management.

Select by Date

Select the options to display in the Select By Date field on the Fulfillment or Shortage Workbench. The options are; Schedule Date, Order Date, Ship Early Date, and Orders Placed Today.

Filter Unfulfilled Lines

For the Shortage Workbench, select the options available in the Filter Unfulfilled Lines field. This field enables the user to limit their search to demand lines that have been processed by reservations, not processed by reservations, or both.

Display Unapproved

For the Shortage Workbench, select the option to display unapproved demand lines.

Use Lead Days

For the Shortage Workbench, select the options to display in the Use Lead Days field. This option determines how the fulfillment lead days are used in the search criteria.

Header Action

For the demand summary view of the Shortage Workbench, select the actions that a user can perform using the Header Action field.

Detail Action

For the Shortage Workbench, select the actions that a user can perform using the Detail Action field.

Line Action

For the Shortage Workbench, select the actions that a user can perform using the Line Action field.

Select Summary View

For the demand summary view of the Shortage Workbench, choose the options available to the user in the Select Summary View field: order summary, item summary, kit summary, or kit schedule.

Exclude

Set the display and default options for this check box on the Fulfillment Workbench to enable the user to define the selection criteria as exclusion criteria. This check box appears only on the Fulfillment Workbench if Detail is selected in the Search By field.

Select Unfulfilled, Select Releasable, and Select Confirmed

Set the display and default options for these check boxes on the Fulfillment Workbench to enable the user to search for orders with these specific fulfillment states. The Shortage Workbench also uses the Select Fulfillment and Select Releasable options.

BLANK

Create a blank line on the Fulfillment or Shortage Workbench. All display and default options are disabled.

Refresh on Action Completion

Enables the system to automatically refresh the data when you complete an action on the Shortage Workbench.

Control Reason Code Prompting

Enable the user of the Shortage Workbench to enter a reason code and comments for any action that causes a quantity decrease to a demand line's promised, reserved or allocated quantity. This feature can be required or optional.

Fulfillment Workbench

IN_FW_SELECTION

Inventory, Fulfill Stock Orders, Fulfillment Workbench

Create a request to move material stock orders and sales orders from one fulfillment state to another.

Fulfillment Queue

IN_FW_CART

Select the Fulfillment Queue link on the Fulfill Workbench page, the Orders page, or the Demand Lines page.

View the demand lines in the processing queue. These are the orders that will be processed by the Fulfillment Workbench request. You can add or delete individual lines and even delete the queue and start over.

Orders

IN_FW_ORDERPOOL

Select the Orders link on the Fulfill Workbench page, the Demand Lines page, or the Fulfillment Queue.

View all of the material stock orders and sales orders matching the search criteria on the Fulfillment Workbench. Also include or exclude specific orders.

Demand Lines

IN_FW_DEMANDLINES

Select the Demand Lines link on the Fulfill Workbench page, the Orders page, or the Fulfillment Queue.

View the demand lines of the material stock orders and sales orders selected by the selection criteria on the Fulfillment Workbench or the order number chosen on the Orders page, depending on how the page was accessed. You can use this page to include or exclude specific demand lines. You can also change the quantity to be reserved or promised (if you are using an Action of Reserve) or shipped (if you are using an Action of Front End Ship or Ship).

Location / Lot / Serial

IN_FW_DEMANDLOC

Select the Location / Lot / Serial link on the Demand Lines page.

Review demand location information for a specific request detail row. When shipping from an unfulfilled or releasable state, you can enter the exact picking location, lot ID, stage date, serial ID, or ship serial ID. You can also exclude a specific picking location, lot ID, and serial ID when shipping from a confirmed state or change the pick or ship quantity and UOM.

Fulfillment Queue Location / Lot / Serial

IN_FW_CART_LLS

Select the Location / Lot / Serial link on the Location / Lot / Serial tab of the Fulfillment Queue page.

Review demand location information for a specific request detail row. When shipping from an unfulfilled or releasable state, you can enter the exact picking location, lot ID, stage date, serial ID, or ship serial ID. You can also exclude a specific picking location, lot ID, and serial ID when shipping from a confirmed state or change the pick or ship quantity and UOM.

Picking/Shipping Overrides

IN_FW_SHP_DFT_1_SP

Select the Group Picking/Shipping Default link or the Ship Defaults link on most pages of the Fulfillment Workbench component.

Enter any picking and shipping override entries to be applied at the transaction request, group, detail, or LLS level.

Processing Defaults

IN_FW_PROC_DFLT_SP

Select the Process Default link on the Fulfill Workbench page.

Change processing defaults for this request.

Action

Identify the type of request:

• Reserve: Enables you to move an unfulfilled order to releasable state.

• Front-end Ship: Enables you to move an unfulfilled order or releasable order to shipped state.

• Pick Confirm: Enables you to move a released order to the pick confirm state.

• Ship: Enables you to move an unfulfilled order, releasable order, or pick confirmed order to shipped state.

Search By

Enter the level that you want to search for and process demand. The fields that appear on the Fulfillment Workbench component vary depending on the option that you select. Options are:

• Group: Select to display group level selection criteria to define a grouping of demand lines.

  The group selection information can be added to the fulfillment queue at the group level, or the group level information can be used to display details within that group by using the Orders or Demand Lines links.

• Detail: Select to display group or detail level selection criteria to define an individual demand line or a grouping of demand lines.

  The selection criteria can be added to the fulfillment queue at the detail level or the selection information can be used to display details within the group using the Demand Lines link.

Group ID

Enter a group identification code for the grouping of demand lines that you are creating on the transaction request. The group ID is assigned automatically using a sequential number starting with one. To create a new group, click the arrow button to the right of this field.

Exclude

Select to define the search criteria as exclusion criteria. This check box appears only if Detail is selected in the Search By field. Selection criteria entered are used to exclude demand data from the group. For example, if you want to ship all demand lines on a pick batch except line number 55, then enter the pick batch ID at the group level and add the group segment to the fulfillment queue. Next, bring up the detail selection information by entering Detail in the Search By field and selecting the Exclude check box. Then enter the pick batch ID and line 55. Add the detail segment to the fulfillment queue. Then click the Fulfillment Queue link to review the transaction request. Write the request to the staging tables when you click the Process button.

Note. If the Exclude check box is selected at the order or demand line level, then that order or demand line must exist in the selection criteria established at the group level. If it is not in the selection criteria, then the fulfillment engine rejects the transaction request.

Select Unfulfilled

Select this check box to include unfulfilled orders in the search results and request.

Select Releasable

Select this check box to include releasable orders in the search results and request. This check box appears only if you have selected an action of Front End Ship or Ship.

Select Released

Select this check box to include released orders in the search results and request. This check box appears only if you have selected the action of Ship.

Select Confirmed

Select this check box to include confirmed orders in the search results and request. This check box appears only if you have selected an action of Ship.

Group Picking/Shipping Default

Select to go to the Picking/Shipping Overrides page, where you can override the picking storage location and shipping parameters. The overrides entered through this link apply to all demand lines in the processing group.

Process

Select to process all the demand lines matching the entered search criteria, without viewing any details. The entered search criteria (request) is written to the staging tables to be processed by the fulfillment engine using the Fulfillment Requests process. If you have selected the Auto Schedule Processing check box 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.

Note. Because the Process button immediately adds the information to the staging tables, it is not available once you have added data to the fulfillment queue. Go to the fulfillment queue and click the Process button to write the transaction request to the staging tables.

Add to Queue

Select to add search criteria to the fulfillment queue to be processed later. You can view the search criteria on the Fulfillment Queue page. When an order or demand line is selected and added to the fulfillment queue using the Orders link or Demand Line link, then a group level entry is automatically created in the fulfillment queue if one was not previously added from the Fulfillment Workbench page. In this situation, the group level entry has no selection criteria. This is done to meet the fulfillment engine's requirement for all detail segments to belong to a group ID on the transaction request being processed.

Clear

Select to clear any search criteria fields that have been populated.

Empty Queue

Select to remove all demand lines from the request.

Fulfillment Queue

Select to go to the Fulfillment Queue page, where you can view and edit the details of the current search criteria added to this request.

Orders

Select to go to the Orders page, where you can view and select individual orders for processing.

Demand Lines

Select to go to the Demand Lines page, where you can view and select individual demand lines for processing.

Ship Defaults

Select to go to the Picking/Shipping Overrides page, where you can override the picking storage location and shipping parameters. The overrides entered through this link apply to all demand lines in the transaction request.

Process Default

Select to go to the Processing Defaults page, where you can alter the fulfillment engine processing options applied to this request.

Select All

Click to select all the Select check boxes for each row. Any rows with clear Exclude check boxes are enabled.

Select None

Click to clear all the Select check boxes for each row. Any rows with selected Exclude check boxes are cleared and disabled.

Exclude All

Click to select all the Exclude check boxes for each row. Any rows with cleared Select check boxes are selected.

Exclude None

Click to clear all the Exclude check boxes for each row.

Select

Check to include this order in the request.

Exclude

Select to define the search criteria as exclusion criteria. This check box appears only if Detail is selected in the Search By field. Selection criteria entered are used to exclude demand data from the group. For example, if you want to ship all the orders in a pick batch ID except order number 55, then enter the pick batch ID at the group level and add the group segment to the fulfillment queue. Next, bring up the detail selection information by entering Detail in the Search By field and selecting the Exclude check box. Then enter the pick batch ID and order number 55. Add the detail segment to the fulfillment queue. Then use the Fulfillment Queue link to review the transaction request and write it to the staging tables when you click the Process button.

Note. If the Exclude check box is selected at the order or demand line level, then that order or demand line must exist in the selection criteria established at the group level. If it is not in the selection criteria, then the fulfillment engine rejects the transaction request.

Demand Lines

Select to access the Demand Lines page, where you can view the demand lines associated with this order number.

Ship Defaults

Select to access the Picking/Shipping Overrides page where you can override the picking storage location and shipping parameters. The overrides entered through this link apply only to the order selected.

Complete Flag

Choose a Complete Flag option to automatically performing picking functionality on demand lines that have no previous picking activity reported against them.

Add to Queue

Select to add the order as a detailed-level segment in the fulfillment queue. You can view the demand lines on the Fulfillment Queue page. When an order is selected and added to the fulfillment queue, a group level entry is automatically created in the fulfillment queue if one was not previously added from the Fulfillment Workbench page. In this situation, the group level entry has no selection criteria. This is done to meet the fulfillment engine's requirement for all detail segments to belong to a group ID on the transaction request being processed.

Workbench

Select to go to the Fulfillment Workbench page.

Fulfillment Queue

Select to go to the Fulfillment Queue page, where you can view and edit the details of the current orders on this request.

Select All

Click to select all of the Select check boxes for each row. Any rows with disabled Exclude check boxes are enabled.

Select None

Click to clear all of the Select check boxes for each row. Any rows with Exclude selected are cleared and disabled.

Exclude All

Click to select all of the Exclude check boxes for each row. Any rows with Select check boxes cleared are selected.

Exclude None

Click to clear all the Exclude check boxes for each row.

Select

Select to include this demand line in the request.

Exclude

Select to exclude this demand line from the selection criteria entered at the group level.

Qty (quantity)

Enter an override quantity for this demand line. If you are using an action of Reserve on the Fulfillment Workbench page, then this value overrides the releasable quantity on the demand line. If you are using an action of Pick Confirm on the Fulfillment Workbench page, then this value overrides the released quantity on the demand line. If you are using an action of Front End Ship or Ship on the Fulfillment Workbench page, then this value overrides the shipped quantity on the demand line.

UOM (unit of measure)

Enter the UOM for the quantity field. The shipping UOM is used as the default for all actions but reserve, but you can override it with any valid UOM for the item. For the action of reserve, the ordering UOM is used as the default.

Location / Lot / Serial

Click this link to access the Fulfillment Queue Location / Lot / Serial page, where you can review and change information related to specific items picked and shipped for this detail row in the transaction request.

Fulfillment State

Displays the current fulfillment state for this demand line.

Requested Base

Displays the requested quantity in the base unit of measure.

Backorder Base

Displays the backordered quantity in the base unit of measure.

Std UOM

Displays the item's standard unit of measure.

Short Ship Opt

Select an option for short shipping this demand line. Options are:

• Return to Location Picked From: Return the unshipped quantity that was picked to the original picking location.

• Scrap the Undershipment: Scrap the unshipped quantity that was picked.

Complete Flag

Choose a Complete Flag option to automatically performing picking functionality on demand lines that have no previous picking activity reported against them. The LLS segment and the override location are applied prior to implementing the complete flag logic. Using the Complete Flag, the line can be moved to different sub-states within the Released state, or, with auto-processing, moved downstream to the shipped or depleted states.

• Complete Pick- Dft Ship Loc: Uses the default shipping location as the pick location for demand lines that do not already have the Confirm Flag set.

  The default shipping location is stored at both the business unit and business unit/item levels.

• Complete Pick- Leave Alone: With this option any lines within the selection criteria that do not have the Confirm Flag set are left alone.

  The Confirm Flag is not set on these demand lines.

• Complete Pick- Zero Quantity: Sets the zero picked flag for every line within the selection criteria if they do not already have the Confirm Flag set.

  Also removes and deallocates any current allocations.

• Pick Batch Complete: Removes every line within the selection criteria from the pick batch ID if they do not already have the Confirm Flag set.

• Pick Batch as Planned: Sets the Confirm Flag on any line that has had picking activity.

  In this situation, picking activity is assumed to be satisfied if there are any allocations as well as if the demand line is a zero picked demand line. An error is generated for any lines that have not had any picking activity when using this option.

• Pick Line Complete: Removes the line from the pick batch ID if the Confirm Flag is not already set.

  It is only valid when referencing an individual pick/batch line at the group or detail level.

• Pick Line as Planned: Sets the Confirm Flag on any line that has had picking activity.

  In this situation, picking activity is assumed to be satisfied if there are any allocations as well as if the demand line is a zero picked demand line. An error is generated for any lines that have not had any picking activity when using this option. This option is only valid when referencing a pick/batch line at the group or detail level.

• Use Defaults: Uses the default value defined in the Fulfillment Engine Options component (setID level) or the Setup Fulfillment-Fulfillment Task Options component (business unit level).

Product ID

Displays the product ID tied to the item ID on the demand line.

Kit ID

Displays the product kit ID if this demand line contains a kit component. This value is also a link to the Kit Display page.

See Viewing Product Kit Details.

Add to Queue

Select to add the demand lines matching the search criteria to the fulfillment queue to be processed later. You can view the demand lines on the Fulfillment Queue page. When a demand line is selected and added to the fulfillment queue, a group level entry is automatically created in the fulfillment queue if one was not previously added from the Fulfillment Workbench page. In this situation, the group level entry has no selection criteria. This is done to meet the fulfillment engine's requirement for all detail segments to belong to a group ID on the transaction request being processed.

Workbench

Select to go to the Fulfillment Workbench page.

Fulfillment Queue

Select to go to the Fulfillment Queue page, where you can view and edit the details on this request.

Orders

Select to go to the Orders page, where you can view the orders in the current search criteria.

Kit ID

Displays the product kit ID if this demand line contains a kit component. This value is also a link to the Kit Display page.

See Viewing Product Kit Details.

Serial ID

Review or enter a serial ID for this request detail row or demand line. If the item is defined as a ship serial controlled item then enter the ship serial ID here.

Qty

Review or change the picking or shipping quantity for this request detail row.

UOM (unit of measure)

Review or change the picking or shipping UOM for this request detail row.

Allocation

Displays the type of allocation on this demand line. The options are:

• Standard (default) Displays that the demand line has a standard allocation created when the line was moved to the Released state.

• Pre-alloc: Displays that the demand line has a pre-allocation created when the line was in the Unfulfilled or Releasable state.

  In addition, if you anticipate that you might need to return this line to the Unfulfilled or Releasable states, then you can tell the system to keep your current allocation if the line is moved upstream. Simply select the value of Pre-Alloc in the Allocation field. You can change this value on existing rows or any new rows that you add on this page.

• Lot Allocation: Displays that the demand line has been lot-allocated. For lot-allocated demand lines this value cannot be changed.

Excluded

Select to exclude a specific picking location, lot ID, or serial ID from this request detail row. This check box is available only when shipping from a confirmed state.

Area, Lev 1, Lev 2, Lev 3, and Lev 4

Review or enter a specific picking location for this request detail row.

Cntr ID and Staged Dt

Review or enter an internal container ID or staged date for this demand line.

Shipping Container ID

Review or enter a shipping container ID for this demand line.

Short Ship Opt

Select an option for short shipping this demand line. Options are:

• Ret to Pic: (default) Return the unshipped quantity that was picked to the original picking location.

• Scrap: Scrap the unshipped quantity that was picked.

Tracking Number

Review or enter a tracking number assigned to this shipment.

Substitute Item ID

Enter a substitute item ID if the original item is defined for substitutes. Item substitution is only allowed for the first LLS row. For subsequent rows of the same demand line, the substitute item is display-only.

Seq Nbr

Enter the sequence number. The sequence number is a unique identifier for rows with the LLS segment for each detail segment.

Request Header Level: Applies to the entire transaction request. Overrides are applied unless another override exists at a lower level.

• Select the Ship Defaults link on the Fulfillment Workbench page.

• Select the Ship Defaults link on the Fulfillment Queue page.

Group Level: Applies to the group. One request can contain one or more groups.

• Select the Group Picking/Shipping Default link on the Fulfillment Workbench page.

• Select the Group Picking/Shipping Default link on the Fulfillment Queue page.

• Select the Ship Defaults link on the Order page.

Detail Level: Applies to one detail level within a group. For example, one demand line in an order.

Select the Ship Defaults link under the Miscellaneous tab on the Demand Lines page.

LLS Level: Applies to one LLS within a detail. For example, as demand line might have multiple serial IDs.

Select the Ship Defaults link under the Lot/Location/Serial tab on the Fulfillment Queue page.

Freight Terms

Enter a freight terms code to override the default value. The freight terms code determines whether the buyer or the seller pays the freight.

Freight Action

Select one of the following freight options to request freight from an external third-party freight system:

• Best Way: The PeopleSoft system sends a best way request to the third-party provider system and the third-party provider returns only best way freight choices. Use the Best Way group box to choose the best way option. The best way options are least cost or by commit date.

• Use Specified Carrier: The PeopleSoft system sends a request with a specific carrier ID to the third-party provider system and the third-party provider returns only freight choices from the specified carrier.

• Carrier with Best Way: Select this option to enable the third-party freight system to return freight results when the carrier ID field is blank on a delivery that uses the Use Specified Carrier freight option. If the PeopleSoft system sends a delivery using the Use Specified Carrier freight option and the delivery does not have a carrier ID assigned to it, then the Best Way freight option is used.

Best Way

If you have selected Best Way or Carrier with Best Way in the Freight Action group box, then use this group box to choose your best way option:

• By Commit Date: The third-party freight system selects and returns the freight service that best matches the scheduled ship date.

• Least Cost: The third-party freight system selects and returns the freight service with the least cost.

Commit Freight for Billing

Select this check box to indicate that once the freight is applied and prorated to the individual orders, then the freight is ready to be picked up by PeopleSoft Billing and by PeopleSoft Cost Management.

Complete Delivery

Select this check box to set the status of the delivery to Complete Delivery when this workbench shipment is finished. The Complete Delivery status indicates all fulfillment steps for the delivery are complete and all demand lines in the delivery are ready to be depleted using the Deplete On Hand Qtys process. If the PeopleSoft Inventory business unit is using deliveries, the Deplete On Hand Qtys process only pick ups demand lines that are on a delivery with the Complete Delivery status.

Ship Cntr ID

Enter an override value for the shipping container ID.

Tracking Number

Enter an override value for the tracking number for this shipment. This field is only available if you have entered a Ship Cntr ID on this page.

Pro Number

Enter an override value for the pro number for this shipment.

Storage Location

Enter the material storage location to pick stock for shipment. This override is applied against all demand lines processed from an unfulfilled or releasable state that do not have picking locations identified at the Location/Lot/Serial segment of the transaction request. If a picking location is not entered on the request, then the fulfillment engine uses the picking location setup on the Setup Fulfillment component.

Short Ship Opt

Select an option for short shipping this demand line. Options are:

• Return to Location Picked From: Return the unshipped quantity that was picked to the original picking location.

• Scrap the Undershipment: Scrap the unshipped quantity that was picked.

Complete Flag

Choose an override Complete Flag option to automatically performing picking functionality on demand lines that have no previous picking activity reported against them. The LLS segment and the override location are applied prior to implementing the complete flag logic. Using the Complete Flag, the line can be moved to different sub-states within the Released state, or, with auto-processing, moved downstream to the shipped or depleted states. The Complete Flag options are:

• Complete Pick- Dft Ship Loc: Uses the default shipping location as the pick location for demand lines that do not already have the Confirm Flag set.

  The default shipping location is stored at both the business unit and business unit/item levels.

• Complete Pick- Leave Alone: With this option any lines within the selection criteria that do not have the Confirm Flag set are left alone.

  The Confirm Flag is not set on these demand lines.

• Complete Pick- Zero Quantity: Sets the zero picked flag for every line within the selection criteria if they do not already have the Confirm Flag set. Also removes and deallocates any current allocations.

• Pick Batch Complete: Removes every line within the selection criteria from the pick batch ID if they do not already have the Confirm Flag set.

• Pick Batch as Planned: Sets the Confirm Flag on any line that has had picking activity.

  In this situation picking activity is assumed to be satisfied if there are any allocations as well as if the demand line is a zero picked demand line. An error is generated for any lines that have not had any picking activity when using this option.

• Use Defaults: Uses the default option.

Defer Depletions

Select the value of Override to Yes or Override to No to change the value of the Defer Depletions field on each demand line included in the selection criteria. The defer depletions value is only applied when the line is being placed in the Shipped fulfillment state. The Defer Depletions override field is available in the Picking /Shipping Overrides page located a the header, group, and detail levels. Overrides at lower levels take precedent over settings at the higher levels; for example, an N at the detail level is used rather than a Y at the header level. For more information in the Defer Depletions feature, go to the "Shipping Inventory" chapter, "Delaying the Billing and Costing of Inventory Shipments" section.

See Delaying the Billing and Costing of Inventory Shipments.

Auto Schedule processing

Select this check box to immediately process this request when you click the Process button on the Fulfillment Workbench page or the Fulfillment Queue page. Requests are placed in staging tables and then immediately processed by the fulfillment engine using the Fulfillment Requests process.

Pass-through Level

An entry here enables error-free transactions to process through the system while holding back transactions that need additional review. This field is available only with a reservations transaction request. The options are:

• Request: Any errors prevent the entire request from being processed.

• Order: Errors prevent an order number from being processed but remaining orders on the request are processed.

  This option is available only on the fulfillment transaction requests for reserve materials processing.

• Line: Errors prevent only the order line from being processed.

  The remaining lines on the order are processed and the remaining orders on the request are processed. This option is only available on the fulfillment transaction requests for reserve materials processing.

Commit Count

(For reserve requests) Enter the number of lines that can be committed to the database together by the fulfillment engine; in other words, define the size of the commit group.

Commit Level

(For reserve requests) Select the level of commits based on the number of:

• Request: Counts the number of separate fulfillment transaction requests processed.

• Order: Counts the number of separate orders (material stock requests and sales orders) processed.

• Line: Counts the number of demand lines processed.

• Item: Counts the number of item IDs processed.

Auto-Processing Option

Select the auto processing option to move your orders downstream to the desired state. The options available depend on the action chosen on the Fulfill Workbench page. Options include:

• No Auto-Processing: Select to have the system only complete the process or action that you are initiating on the current page.

  No additional processing will be launched.

• Advance to Released: Select to automatically process the orders to the released state when using the reserve action.

  The parameters defined on the Auto Release Run Control are used to process the orders through the Order Release Request process. These parameters could release the orders further downstream.

• Advance to Confirmed: Select to automatically process the orders to the picking confirmed state when using the pick confirm action.

• Advance to Shipped: Select to automatically process the orders to the shipped state when using the pick confirm action.

• Advance to Depleted: Select to automatically process the orders to the depleted state when using any action except reserve.

Release Run Control

Select a run control for the Order Release Request process page. This run control contains the parameters to be used when auto-processing orders from an unfulfilled state to another downstream state. The Auto Processing Option field determines how far downstream the orders will be sent.

Group Picking/Shipping Default

Select this link to go to the Picking/Shipping Overrides page, where you can override the picking storage location and shipping parameters. The overrides entered through this link are applied at the group level.

Exclude

Under the Demand Key tab, select and enter information to identify demand that should be excluded from the request.

Quantity

Under the Demand Key tab, enter an override quantity for this demand. If you are using an action of Reserve on the Fulfillment Workbench page, then this value overrides the releasable quantity on the demand line. If you are using an action of Pick Confirm on the Fulfillment Workbench page, then this value overrides the released quantity on the demand line. If you are using an action of Front End Ship or Ship on the Fulfillment Workbench page, then this value overrides the shipped quantity on the demand line.

Unit of Measure

Under the Demand Key tab, enter the UOM for the quantity field. The standard UOM is used as the default, but you can override it with any valid UOM for the item.

Kit ID

Under the Reference tab, you can view or edit the product kit. If you entered a product kit ID (Parent Product ID field) in the selection criteria of the Fulfillment Workbench page and then clicked the Add to Queue button, then the Kit ID is displayed in this field.

Location / Lot / Serial

Under the Lot/Location/Serial tab, select this link to access the Fulfillment Queue Location / Lot / Serial page, where you can review and change information related to specific items picked and shipped for this detail row in the transaction request.

Ship Defaults

Under the Lot/Location/Serial tab, select this link to go to the Picking/Shipping Overrides page where you can override the picking storage location and shipping parameters. The overrides entered through this link apply to the detail level.

Short Ship Opt

Under the Lot/Location/Serial tab, select an option for short shipping this demand line. Options are:

• Return to Location Picked From: Return the unshipped quantity that was picked to the original picking location.

• Scrap the Undershipment: Scrap the unshipped quantity that was picked.

Process

Select to process all the demand lines matching the entered search criteria. The entered search criteria (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 or the Setup Fulfillment - Fulfillment Engine page, then the Fulfillment Requests process is launched when you click this button.

Empty Queue

Select to remove all demand lines from the request.

Workbench

Select to go to the Fulfillment Workbench page, where you can add additional selection criteria.

Ship Defaults

Select to go to the Picking/Shipping Overrides page, where you can override the picking storage location and shipping parameters. The overrides entered through this link apply to the entire transaction request.

Orders

Select to go to the Orders page, where you can view and select individual orders for processing.

Demand Lines

Select to go to the Demand Lines page, where you can view and select individual demand lines for processing.

Fulfillment Requests

BCT_INV_REQFUL

SCM Integrations, Process Transactions, Inventory, Fulfillment Requests

Process fulfillment transaction requests in the fulfillment staging tables against the material stock orders and sales orders located in the PeopleSoft Inventory demand tables. Based on the transaction code, these transaction requests can create new material stock requests, add freight charges to sales orders, or move an order from one fulfillment state to another downstream state, often skipping intermediate steps.

Processing Options

INV_PROCESS_SEC

Click the Processing Options link on the Fulfillment Requests page.

Review or change the fulfillment engine processing options used by the Fulfillment Requests process. Initially this page displays the current fulfillment engine options that are defined in your environment at the business unit level (in the Setup Fulfillment component) or at the set ID level (on the Fulfillment Engine Options page). The fields available on this page are determined by the selection of the Allow Processing Overrides check box in the fulfillment engine options.

Fulfillment Tasks Options

INV_FUL_DFLT_BU

Select the View Process Defaults link on the Fulfillment Requests page.

Review the fulfillment engine processing options defined in this run control for the Fulfillment Requests process.

Transaction Maintenance

BCT_CTL_UPD

SCM Integrations, Transaction Error Handling, Maintain Transactions, Transaction Maintenance

View all electronic transactions in the transaction log and access the detail pages that enable you to correct transaction errors.

Transaction

Select the name of the inbound EIP or leave this field blank to select all transactions within the business unit.

Status

Select a status to display only the transactions within this state. Leave this field blank to display transactions in all states. The options are:

• Complete

• Confirmed

• Error

• In Process

• Incomplete

• New

• Reprocess

Search

Click this button to display all transactions with the entered search criteria of business unit, transaction, and status.

EIP Control ID

Select this link to access the detail pages of the transaction where you can view or change the values on this incoming transaction. The fields displayed vary depending on the type of transaction.