Standard Receipts.

Direct Receipts for receive and deliver transactions.

Serial numbering.

Separate receive and deliver transactions.

Corrections.

Returns.

Movement statistics.

Dynamic locators.

Receipt against Internal Orders.

Receipt against Inter-Organization transfers.

Receipt against Drop Ship Orders.

Receipt against RMAs.

setRCVTxn.txp

RCVTransactions1227.txp

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

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

pickSequence generates the group ID from the customer sequence WM_RCV_GROUP_S.

bizDocMapping maps the incoming business document structure to the required Oracle Applications data structures, which is similar to the interface tables.

getVendorSiteId is a transformer for mapping the business document IData structure to the interface table IData structure. It takes ADDRESS_LINE1, ADDRESS_LINE2, ADDRESS_LINE3, CITY, STATE, ZIP, COUNTRY, VENDOR_NAME and ORG_NAME as the input parameters, queries the tables AP_SUPPLIER_SITES_ALL, AP_SUPPLIERS, and ORG_ORGANIZATION and gets the VENDOR_SITE_ID corresponding to the passed values.

getOrgId is a transformer for mapping the business document IData structure to the interface table structure. It takes ORGANIZATION_NAME as the input parameter, queries the table ORG_ORGANIZATION_DEFINITIONS and gets the ORGANIZATION_ID corresponding to the ORGANIZATION_NAME.

getLocationId-tf is a transformer for mapping the business document IData structure to the interface table IData structure. This is a general service to get the LOCATION_ID from HR_LOCATIONS, given ADDRESS_LINE_1, ADDRESS_LINE_2, ADDRESS_LINE_3, TOWN_OR_CITY, COUNTRY, POSTAL_CODE, REGION_1, and REGION_2.

getReasonId is a transformer for mapping the business document IData structure to the interface table IData structure. It takes REASON_NAME as the input parameter, queries the table MTL_TRANSACTION_REASONS, and gets the REASON_ID corresponding to the REASON_NAME.

setRCVTxn inserts data into the interface table. It extracts data form the IData structure that results in the bizDocMapping service, and puts the data into the interface table in Oracle Applications for Open Receiving.

importRCV imports data to the production table from the interface table. It then calls the services executeConcurrentProgram, checkRCVIntTabStatus, and setRCVTxn_ERR to execute the corresponding concurrent program that inserts data into the production table to generate the error/acknowledgement message. If the status of the execution is SUCCESS (returned by the service executeConcurrentProgram), 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 getRCVTxn_ERR to retrieve the errors. If no record is found, it comes out of the flow and indicates the success of the data import process. If the status of the execution is FAILED, it returns the appropriate error message and comes out of execution.

execRCVConcProg invokes the stored procedure WM_RECEIVING_IMP_HANDLER_PKG.WM_HANDLE_RECEIVING. This procedure then calls the corresponding concurrent subroutine to execute the data import process for Open Receiving into Oracle Applications. This service gives Status ID, Request ID, and Execution Status Message (for normal concurrent program completion), and a database Stored Procedure error message (if an exception occurs during the Stored Procedure execution).

checkRCVImportStatus checks the status of the execution by checking the Error Interface Table. If the query does not return any rows, it indicates 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.

getRCVTxn_ERR gets the error message that occurs during the data import to the production table from the interface table. Based on the parameter request ID, it scans table PO_INTERFACE_ERRORS to get the corresponding message matches to the request ID.

1.0. RCV_HEADERS

1.1. RCV_LINES