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 Customer Item Service
 
Receive Customer Item Service
This service is in the WmOAMFG1227 package and has the following fully-qualified service name: inventory1227.intoOA.customerItem:receiveCustomerItem.
This service imports Customer Items into Oracle Inventory.
You can import Customer Items at any of the following levels: Customer-level, Address Category-level, or Address-level. The level is specified in the Item Definition Level column. An item imported at the Customer level is visible to all organizations. You can also import items with an inactive status.
While submitting the concurrent program Customer Item Import to load the Customer Item records from interface tables to production tables, you cannot restrict the processing to only those records uploaded by the IS flow instance. The program will process all unprocessed records that exist in the interface table at the time of execution. After executing the concurrent program, errors will be retrieved for all processed records that might not be uploaded by this IS flow instance.
Database Scripts
This service uses the following database scripts:
Script
Description
wm_install_into_custitem.sql
Runs the scripts listed below, except the uninstall script.
wm_into_custitem_pkg.sql
Installs
WM_INV_CTITEM_IMP_HANDLER_PKG.
WM_HANDLE_CUSTITEM,
which calls the
WM_CONC_REQUEST.
WM_REQUEST_SUBMIT
procedure to submit the Customer Item Import process.
The process in the Oracle Inventory module is Import Customer Items.
wm_drop_into_custitem.sql
Uninstalls the components created by wm_install_into_custitem.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:
*setCustomerItemTxn1227.txp
*CustomerItemTxn1227.txp
For information about using the transaction definition files to customize this service, see Transaction Definitions.
Flow Control
The receiveCustomerItem service uses the following flow operations to import customer items:
*specifyDefaultSettings specifies the default settings required for service execution.
*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).
*getOASystemDateObject returns the Oracle Applications system date as a date object.
*getOracleAppsUserId is a transformer for mapping the business document IData structure to the interface table IData structure. It takes ORACLE_APPS_USER_NAME as the input parameter from the business document, and queries the table FND_USER to get the USER_ID. The USER_ID information is required for insertion into the interface tables.
*setCustomerItemTxn 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 Customer Items.
*importCustomerItem imports data to the production table from the interface table. It calls the services execCustomerItemConcProg, checkCustomerItemImportStatus, and getCustomerItemImport_ERR to execute the corresponding concurrent program that inserts data into the production table, and to generate the error/acknowledgment message. If the status of the execution is SUCCESS (returned by the service execCustomerItemConcProg), it checks for rejected records. If records are found, it then indicates an error during import. In this case, this service calls getCustomerItemImport_ERR to retrieve the errors. If no records are 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.
*execCustomerItemConcProg invokes the stored procedure WM_INV_CTITEM_IMP_HANDLER_PKG.WM_HANDLE_CUSTITEM. This procedure calls the corresponding concurrent subroutine to execute the data import process for Customer Items 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 the Stored Procedure execution).
*checkCustomerItemImportStatus checks the status of the execution by checking the Interface Table for any rejected record. If the query does not return rows, it indicates successful import. If the query returns rows, it indicates that the concurrent program could not import data successfully in the production tables of Oracle Applications. The Interface table is not updated with the REQUEST_ID; there is no way to check errors corresponding to only the current bizDoc import. Therefore, the error document will show any old errors, as well.
*getCustomerItemImport_ERR gets the error message that occurs during the data import to the production table from interface table. It scans the MTL_CI_INTERFACE table to get the rejected records. The Interface table is not updated with the REQUEST_ID; there is no way to check errors corresponding to only the current bizDoc import. Therefore, the error document will show any old errors as well.
For more details on receive transactions, see Overview of Receive Service Transaction Processing.
Business Document Structure
This service uses the business document customerItemBizDoc. Its structure is as follows:
*CUST_ITEM
CUST_ITEM (Maps to MTL_CI_INTERFACE)
Field Name
Maps to Column
Description
PARTY_NAME
PARTY_NAME
CUSTOMER_CATEGORY_
CODE
CUSTOMER_
CATEGORY_CODE
ADDRESS1
ADDRESS1
ADDRESS2
ADDRESS2
ADDRESS3
ADDRESS3
ADDRESS4
ADDRESS4
CITY
CITY
STATE
STATE
COUNTY
COUNTY
COUNTRY
COUNTRY
POSTAL_CODE
POSTAL_CODE
CUSTOMER_ITEM_
NUMBER
CUSTOMER_
ITEM_NUMBER
Required.
ITEM_DEFINITION_
LEVEL
ITEM_DEFINITION_
LEVEL
If this is at the Address Category level, then Customer and Address Category are required. If this is at the Address level, then the complete address fields and the Customer field are required. Definition Level for the Customer Item. Use:
*1 for Customer
*2 for Address Category.
*3 for Address.
CUSTOMER_ITEM_
DESC
CUSTOMER_
ITEM_DESC
Description of the Customer Item defined above.
MODEL_CUSTOMER_
ITEM_NUMBER
MODEL_CUSTOMER_
ITEM_NUMBER
COMMODITY_CODE
COMMODITY_CODE
Commodity code as defined in Oracle Inventory.
MASTER_CONTAINER
MASTER_CONTAINER
Multi-segmented values for a container Item.
CONTAINER_ITEM_
ORG_NAME
CONTAINER_ITEM_
ORG_NAME
Organization name for the container item.
DETAIL_CONTAINER
DETAIL_CONTAINER
Detail container item name (flexfield concatenated segments).
MIN_FILL_PERCENTAGE
MIN_FILL_PERCENTAGE
Minimum fill percentage.
DEP_PLAN_
REQUIRED_FLAG
DEP_PLAN_
REQUIRED_FLAG
Flag to indicate whether departure planning is required for the Customer Item. Use:
*1 for Yes.
*2 for No.
DEP_PLAN_PRIOR_
BLD_FLAG
DEP_PLAN_
PRIOR_BLD_FLAG
Flag indicating if departure plan before build is required. Use:
*1 for Yes.
*2 for No.
INACTIVE_FLAG
INACTIVE_FLAG
Required. Use:
*1 for Yes.
*2 for No.
DEMAND_TOLERANCE_
POSITIVE
DEMAND_
TOLERANCE_
POSITIVE
Positive tolerance (high end) for customer item demand.
DEMAND_TOLERANCE_
NEGATIVE
DEMAND_
TOLERANCE_
NEGATIVE
Negative tolerance (low end) for customer item demand.