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 Quality Collection Service
 
Receive Quality Collection Service
This service is in the WmOAMFG1227 package and has the following fully-qualified service name:
quality1227.intoOA.qualityCollection:receiveQualityCollection
This service adds new quality results to, or updates existing quality results in, the Oracle Applications Quality Data Repository.
Database Scripts
This service uses the following database scripts:
Script
Description
wm_install_into_qacollection.sql
Runs the scripts listed below, except the uninstall script.
wm_into_qacollection_pkg.sql
Installs
WM_QA_IMP_HANDLER_PKG.WM_HANDLE_QA,
which calls the
WM_CONC_REQUEST.WM_REQUEST_SUBMIT
procedure to submit the Quality Collection Import process.
The process in the QA module is Collection Import.
wm_drop_into_qacollection.sql
Uninstalls all components created by wm_install_into_qacollection.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:
*setQualityCollectionTxn1227.txp
*QualityCollectionTxn1227.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 add or update quality results:
*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.
*bizDocMapping maps the incoming business document structure to the required Oracle Applications data structures (the interface tables). In the process, it sets two flags (IS_INSERT and IS_UPDATE) to determine whether the incoming document contains Insert Transactions, Update Transactions, or both.
*getOrgIdAndCode is a transformer for mapping the business document IData structure to the interface table IData structure. It takes ORGANIZATION_NAME as the input parameter, and queries the table ORG_ORGANIZATION_DEFINITIONS to get the ORGANIZATION_ID and ORGANIZATION_CODE corresponding to the ORGANIZATION_NAME.
*getWIPEntityId is a transformer for mapping the business document that takes the WIP_ENTITY_NAME as input, and returns WIP_ENTITY_ID.
*insertTypeLookUp converts the incoming insert type to a value.
*getPOAgentId is a transformer that takes FULL_NAME as input, and returns the Agent ID by querying the database.
*checkInsertType checks the type of actions to import the data into the production table. There can be two modes of import: insert and update. This service checks the incoming data string for the mode, and sets the IS_INSERT or IS_UPDATE flag to Y for further use.
*importQualityCollection imports data to the production table from the interface table. Depending on the action type (Insert or Update), it calls the service execQualityCollectionConcProg with the appropriate parameters to execute the corresponding concurrent program that inserts data into the production table, and that generates the error/acknowledgement message. If the status of the execution is SUCCESS (returned by the service execQualityCollectionConcProg), it checks for records in the interface table. If records are found, it then indicates an error during import. In this case, this service calls getQualityCollectionImport_ERR to retrieve the errors. If records are not found, it comes out of the flow, indicating success of the data import process. If the status of the execution is FAILED, it comes out of execution.
Include one new parameter in ConcProgParams in Input/ Output section. Then in Branch for Insert and Update, this parameter needs to be mapped in the called service execQualityCollectionConcProg.
*execQualityCollectionConcProg invokes the stored procedure WM_QA_IMP_HANDLER_PKG.WM_HANDLE_QA. The procedure calls the corresponding concurrent subroutine to execute the data import process for Quality Collection into Oracle Applications. This service returns Status ID, Request ID, Execution Status Message (for concurrent program normal completion), and database Stored Procedure error message (if an exception occurs in Stored Procedure execution).
The transaction definition of this service needs to be imported and this service needs to be regenerated so as to include the new parameter P_GATHER_STATISTICS in the service.
*checkQualityCollectionImportStatus service checks the status of the execution by checking the Interface Table for any rejected record corresponding to the current request_id. If the query does not return any rows, it indicates successful import. If the query returns rows, it indicates that the concurrent program could not import data successfully in the Oracle Applications production tables.
*getQualityCollectionImport_ERR gets the error message that occurs during the data import into the production table from the interface table. Based on the parameter REQUEST_ID, it scans the tables QA_INTERFACE_ERRORS and QA_RESULTS_INTERFACE to get the corresponding message.
For more information on receive transactions, see Overview of Receive Service Transaction Processing.
Business Document Structure
This service uses the business document QualityCollectionBizDoc. Its structure is as follows:
*QA_COLLECTION
QA_COLLECTION (Maps to QA_RESULTS_INTERFACE)
Field Name
Maps to Column
Description
COLLECTION_ID
SOURCE_CODE
SOURCE_CODE
Source of quality data.
SOURCE_LINE_ID
SOURCE_LINE_ID
Detailed information about quality data.
ORGANIZATION_NAME
ORGANIZATION_CODE
Required. Derives the Organization
Code from
ORG_ORGANIZATION_
DEFINITIONS.
PLAN_NAME
PLAN_NAME
Required. Name of the collection plan as defined in Oracle Quality.
SPEC_NAME
SPEC_NAME
Quality specification name.
DEPARTMENT
DEPARTMENT
Code for the Bill of Materials Department.
RESOURCE_CODE
RESOURCE_CODE
QUANTITY
QUANTITY
ITEM
ITEM
Item number.
UOM
UOM
Unit of measure.
REVISION
REVISION
SUBINVENTORY
SUBINVENTORY
LOCATOR
LOCATOR
Locator of the item.
LOT_NUMBER
LOT_NUMBER
SERIAL_NUMBER
SERIAL_NUMBER
COMP_ITEM
COMP_ITEM
Component item number.
COMP_UOM
COMP_UOM
Component unit of measure.
COMP_REVISION
COMP_REVISION
Component revision.
COMP_SUBINVENTORY
COMP_SUBINVENTORY
Component subinventory.
COMP_LOCATOR
COMP_LOCATOR
Component locator.
COMP_LOT_NUMBER
COMP_LOT_NUMBER
Component lot number.
COMP_SERIAL_NUMBER
COMP_SERIAL_NUMBER
Component serial number.
WIP_ENTITY_NAME
WIP_ENTITY_ID
Derived from WIP_ENTITIES table.
JOB_NAME
JOB_NAME
PRODUCTION_LINE
PRODUCTION_LINE
TO_OP_SEQ_NUM
TO_OP_SEQ_NUMBER
To operating sequence number.
FROM_OP_SEQ_NUM
FROM_OP_SEQ_NUMBER
From operating sequence number.
VENDOR_NAME
VENDOR_NAME
Name of the supplier.
RECEIPT_NUM
RECEIPT_NUM
Receipt number.
PO_NUMBER
PO_NUMBER
Purchase order number.
PO_LINE_NUM
PO_LINE_NUM
Purchase order line number.
PO_SHIPMENT_NUM
PO_SHIPMENT_NUM
Purchase order shipment number.
PARTY_NAME
PARTY_NAME
SALES_ORDER
SALES_ORDER
Sales order number.
RMA_NUMBER
RMA_NUMBER
Return Material Authorization number.
CHARACTER1 through CHARACTER100
CHARACTER1 through CHARACTER100
A collection plan defined in Oracle Applications can have one or more of these planning-specific collection elements.
TO_DEPARTMENT
TO_DEPARTMENT
To Bill of Materials department.
PO_RELEASE_NUM
PO_RELEASE_NUM
Purchase order release number.
PROJECT_NUMBER
PROJECT_NUMBER
INSERT_TYPE
INSERT_TYPE
Use:
*Null to add records to repository.
*1 to Insert.
*2 to Update existing records.
MATCHING_ELEMENTS
MATCHING_ELEMENTS
A comma-separated list of column names. The data in these columns are used as search keys to find matching rows in collection import updates.
PO_AGENT_FULL_NAME
PO_AGENT_ID
Derives the agent ID from PO_AGENTS table.