Receive Pick Confirm Service

Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter 12.2.7 Predefined Transaction Services Documentation | Order Management Predefined Transaction Services | Receive Pick Confirm Service

This service is in the WmOAOMG1227 package and has the following fully-qualified service name: orderManagement1227.intoOA.pickConfirm:receivePickConfirm.

This service imports pick confirmations on Move Order Line Detail records. The Oracle Applications Pick Confirm API will not process any unmatched Move Order Line records.

The data elements in the Pick Confirm business document is queries for matching Move Order Lines from Oracle Applications. One record in the business document may result in multiple Move Order Lines. Each Move Order Line will be Pick Confirmed. The data elements in the Move Order Lines should be the same as those in the Pick Confirm.

Database Scripts

This service uses the following database scripts:

Database Script	Description
wm_install_into_pickconfirm.sql	Runs the scripts listed below, except the uninstall script.
wm_into_pickconfirm_pkg.sql	Installs WM_PICKCONFIRM_HANDLER_PKG.WM_PICK_CONFIRM_API, which calls the WM_CONC_REQUEST.WM_REQUEST_SUBMIT procedure to submit the pick confirmation import process.
wm_drop_into_pickconfirm.sql	Uninstalls all components created by wm_install_into_pickconfirm.sql.

For more information about using database scripts, see Database Scripts.

Supporting Transaction Definitions

This service was built from the configured services defined in the following transaction definition:

pickConfirmTxn1227.txp

For information about using the transaction definition files to customize this service, see Transaction Definitions.

Flow Control

The main flow executes as follows:

specifyDefaultSettings specifies the default parameter settings required for service execution. You should change these settings accordingly.

bizDocMapping uses the incoming business data structure (PickConfirmBizDoc) to query matching Move Order Lines, loads them to IData structure (PickConfirmRecordSet) that are then required to be fed to Pick Confirm APIs. In the process, it also builds up another IData structure (PickConfirmResults), which holds records from the incoming business data structure that did not result in any Move Order Lines.

importPickConfirm loops over the PickConfirmRecordSet created in the bizDocMapping and invokes the execPickConfirmConcProg for each record to execute the Pick Confirm API. The success/failure of API is tracked in the PickConfirmResults IData structure.

execPickConfirmConcProg calls the underlying Pick Confirm API with the set of parameters from PickConfirmRecordSet, and returns the V_ERRMSG, V_STATUS and O_ERRORMSG to provide the status of the execution, with other attributes identifying the Move Order Line.

For more details about receive transactions, see Overview of Receive Service Transaction Processing.

Business Document Structure

This business document structure is PickConfirmBizDoc. Its structure is as follows:

PICK_CONFIRM

Field Name	Description
MOVE_ORDER_NUMBER
INVENTORY_ITEM_CODE
ITEM_REVISION_NUMBER
TRANSACTION_TYPE
MOVE_ORDER_TYPE_NAME
PROJECT_NAME
TASK_NAME
ORGANIZATION_NAME	Organization name from which the material transaction originates.
SOURCE_SUBINVENTORY	Subinventory code from which material transfer initiated.
SOURCE_LOCATOR	Subinventory locator identifier from which the material transaction takes place.
DESTINATION_SUBINVENTORY	Subinventory code to which material transfer initiated.
DESTINATION_LOCATOR	Subinventory locator identifier to which the material transaction takes place.
PICK_SLIP_NUMBER	Pick slip number for the Move Order line.
SALES_ORDER_NUM	Sales order number for the Move Order Line.
LOT_NUMBER	Source subinventory lot number.