Receive Replenishment Service

Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter 12.2.7 Predefined Transaction Services Documentation | Manufacturing Predefined Transaction Services | Receive Replenishment Service

This service is in the WmOAMFG1227 package and has the following fully-qualified service name: inventory1227.intoOA.replenishment:receiveReplenishment.

This service imports replenishment requests from external systems, such as barcode applications. These requests can be stock-take counts or requisition requests for subinventories where quantities are not tracked. It can also be used to process requisition requests generated by external applications for tracked subinventories.

Database Scripts

This service uses the following database scripts:

Script	Description
wm_install_into_replenish.sql	Runs the scripts listed below, except the uninstall script.
wm_into_replenish_pkg.sql	Installs WM_OPEN_REPLENISH_HANDLER_PKG. WM_HANDLE_OPEN_REPLENISH, which calls the WM_CONC_REQUEST. WM_REQUEST_SUBMIT procedure to submit the Replenishment Import process.
wm_drop_into_replenish.sql	Uninstalls all components created by wm_install_into_replenish.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 definitions:

setReplenishmentTxn1227.txp

ReplenishmentTxn1227.txp

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

Flow Control

This service uses the following flow steps to import replenishment requests:

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

specifyConcProgParams specifies the default settings required for concurrent program execution. You should change these settings accordingly.

bizDocMapping service maps the incoming business document structure to the required Oracle Applications data structures (the interface tables).

getLocationId is a transformer that transforms the LOCATION_CODE to its ID that is required and understood by Oracle Applications database.

getUOMCode is a transformer for mapping the incoming business document to the interface table structure. This service selects the Unit Of Measure (UOM) code from the given UNIT_OF_MEASURE string.

setReplenishmentTxn inserts data into the interface table. It extracts data from the IData structure that results from the bizDocMapping service, and puts the data into the interface table in Oracle Applications for Replenishment.

importReplenishment imports data to the production table from the interface table. It then calls the services execReplenishmentConcProg, checkReplenishmentImportStatus, and getReplenishmentImport_ERR to execute the corresponding concurrent program that inserts data into the production table, and to generate the error/acknowledgement message. If the status of the execution is SUCCESS (returned by the service execReplenishmentConcProg), it checks for the record having the returned request ID in the error interface table. If a record is found, it indicates an error during import. In this case, this service calls getReplenishmentImport_ERR to retrieve the errors. If no record is found, it comes out of the flow, indicating success of the data import process. If the status of the execution is FAILED, it presents an error message and stops execution.

execReplenishmentConcProg invokes the stored procedure WM_OPEN_REPLENISH_HANDLER_PKG.WM_HANDLE_OPEN_ REPLENISH, which calls the corresponding concurrent subroutine to execute the data import process for Replenishment into Oracle Applications. This service returns Status ID, Request ID, Execution Status Message (for normal concurrent program completion), and database Stored Procedure error message (if an exception occurs in Stored Procedure execution).

mapExecStatus captures the concurrent program execution status. If the status returned is SUCCESS, it checks whether the data has been uploaded into production database tables.

mapExecErrorStatus captures the concurrent program execution error message. If the status returned is FAILED, it maps relevant messages to dbErrorMsgRecordSet and concProgMsgRecordSet, and control returns to the calling flow service (receiveReplenishment).

checkReplenishmentImportStatus service checks the status of the execution by checking the Error Interface Table. If the query does not return rows, it indicates a successful import. If rows exist in the Error Interface table, it indicates that the concurrent program could not import data successfully in the production tables of Oracle Applications.

getReplenishmentImport_ERR gets the error message that occurs during the data import to the production table from interface table. Based on the parameter Count Name, it scans the tables MTL_REPLENISH_HEADERS_INT and MTL_REPLENISH_LINES_INT to get the corresponding message matches to the count name.

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

Business Document Structure

This service uses the business document ReplenishmentBizDoc. Its structure is as follows:

1.0. MTL_REPLENISH_HEADERS

1.1. MTL_REPLENISH_LINES

1.0 MTL_REPLENISH_HEADERS (Maps to MTL_REPLENISH_HEADERS_INT)

Field Name	Maps to Column	Description
REPLENISHMENT_ COUNT_NAME	REPLENISHMENT_ COUNT_ NAME	Required. Unique name for the replenishment count.
COUNT_DATE	COUNT_DATE	Required. Date when the count was performed.
ORGANIZATION_NAME	ORGANIZATION_ID	Required. Name of organization from which the Replenishment count originated. Use HR_ALL_ORGANIZATION_ UNITS.NAME to derive the ORGANIZATION_ID. See the commonOA1227.utils:getOrgId transformer.
SUBINVENTORY_CODE	SUBINVENTORY_ CODE	Required. Code of the subinventory that is the source of the replenishment count.
SUPPLY_CUTOFF_DATE	SUPPLY_ CUTOFF_DATE	Date after which the planned supply will not be considered in available quantity calculations. A null value indicates that you do not want to consider planned supply when performing replenishment calculations.
DELIVER_TO_ LOCATION_ADDRESS_1	DELIVERY_ LOCATION_ID	Location to which the replenishment should be delivered. If none is specified, the default delivery location for the organization from which the replenishment originated is the system default. Use HR_LOCATIONS to get the LOCATION_ID.
DELIVER_TO_ LOCATION_ADDRESS_2
DELIVER_TO_ LOCATION_ADDRESS_3
DELIVER_TO_ LOCATION_TOWN_OR_CITY
DELIVER_TO_ LOCATION_COUNTY
DELIVER_TO _LOCATION_STATE
DELIVER_TO_ LOCATION_POSTAL_CODE
DELIVER_TO_ LOCATION_COUNTRY

1.1 MTL_REPLENISH_LINES (Maps to MTL_REPLENISH_LINES_INT)

Field Name	Maps to Column	Description
ORGANIZATION_NAME	ORGANIZATION_ ID	Name of organization where the replenishment count originated. The line organization must be the same as that of the header. Use HR_ALL_ORGANIZATION_ UNITS.NAME to derive the ORGANIZATION_ID. See the commonOA1227.utils:getOrgId transformer.
ITEM_CODE	INVENTORY_ ITEM_ID	Required. Item to be replenished. Derives the Inventory Item ID using MTL_SYSTEM_ITEMS_B_KFV. CONCATENATED_SEGMENTS for the given ORGANIZATION_ID.
COUNT_TYPE_CODE	COUNT_TYPE_ CODE	Required. Enter the type of the replenishment count entry. Use: 1 for On-hand quantity. 2 for Order quantity. 3 for Order maximum.
COUNT_QUANTITY	COUNT_ QUANTITY	Required. The count quantity for the count type entered for the line. This column is not used when the count type is Order Maximum or Other Count Types.
REFERENCE	REFERENCE	Replenishment count reference information.
COUNT_UNIT_ OF_MEASURE	COUNT_ UOM_CODE	Required. Unit of measure code used for the count. This column is meaningful only when a value is entered in the COUNT_QUANTITY columns. Use MTL_UNITS_OF_MEASURE_TL. UNIT_OF_MEASURE to get the UOM_CODE in the user’s LANGUAGE.
PROJECT	TASK_ID	Use PA_TASKS.TASK_NAME and PA_PROJECTS_ALL.NAME to get the TASK_ID.
TASK