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 Cycle Count Entry Service
 
Receive Cycle Count Entry Service
This service is in the WmOAMFG1227 package and has the following fully-qualified service name: inventory1227.intoOA.cycleCountEntry:receiveCycleCountEntry.
This service imports cycle count entries.
Database Scripts
This service uses the following database scripts:
Script
Description
wm_install_into_cyclecount.sql
Runs the scripts listed below, except the uninstall script.
wm_into_cyclecount_pkg.sql
Installs
WM_INV_CC_IMP_HANDLER_PKG.
WM_HANDLE_INV_CC,
which calls the
WM_CONC_REQUEST.
WM_REQUEST_SUBMIT
procedure to submit the Transaction Worker Process.
wm_into_cyclecount_seq.sql
Creates the following component:
*WM_CC_ENTRIES_INTERFACE_S, which creates the CC Entry Interface ID sequence
wm_drop_into_cyclecount.sql
Uninstalls all components created by wm_install_into_cyclecount.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:
*setCycleCountEntryTxn1227.txp
*CycleCountEntry1227.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 cycle count entries:
*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).
*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.
*getOASystemDateObject returns the Oracle Applications system date as a date object.
*pickSequence generates the current sequence number from the sequence WM_CC_ENTRIES_INTERFACE_S.
*getCycleCountHeaderId gets the CYCLE_COUNT_HEADER_ID for the respective CYCLE_COUNT_HEADER_NAME and ORGANIZATION_NAME.
*convertToDateObject converts the text date format into object date format. This is a transformer in the bizDocMapping.
*getOrgId is a transformer for mapping the business document IData structure to the interface table IData 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.
*getCostGroupId retrieves the COST_GROUP_ID for the entered item in the organization.
*getCodeCombinationId is a transformer for mapping the business document IData structure to the interface table IData structure. This is a general service to get CODE_COMBINATION_ID from GL_CODE_COMBINATIONS_KFV, given the CONCATENATED_SEGMENTS and SET_OF_BOOK_NAME.
*getInventoryItemId is a transformer for mapping the business document IData structure to the interface table IData structure. It takes ITEM_CODE and ORGANIZATION_NAME as input, and returns the INVENTORY_ITEM_ID.
*getLocatorId is a transformer for mapping the business document to the interface IData structure. This service takes the LOCATOR and ORGANIZATION_NAME as input parameters, and returns the INVENTORY_LOCATION_ID
*setCycleCountEntryTxn inserts data into the interface table. It takes data from the IData structure that results from the bizDocMapping service, and puts the data into the interface table in Oracle Applications for Cycle Count Entries Interface.
*importCycleCountEntry imports data into the production table from the interface table. It calls the service execCycleCountEntryConcProg to execute the corresponding concurrent program that inserts data into the production table.
*execCycleCountEntryConcProg invokes the stored procedure WM_INV_CC_IMP_HANDLER_PKG.WM_HANDLE_INV_CC. The procedure calls the corresponding concurrent subroutine to execute the data import process for Labor 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).
*checkCycleCountEntryImportStatus queries the MTL_CC_ENTRIES_INTERFACE table to find the number of erroneous rows for the passed CYCLE_COUNT_HEADER_NAME.
*getCycleCountEntryImport_ERR gets the error message that occurs during the data import of Cycle Count Entries for the specified CYCLE_COUNT_HEADER_NAME to the production table from interface table.
For more details on receive transactions, see Overview of Receive Service Transaction Processing.
Business Document Structure
This service uses the business document CycleCountEntryBizDoc. Its structure is as follows:
*MTL_CC_ENTRIES
MTL_CC_ENTRIES (Maps to MTL_CC_ENTRIES_INTERFACE)
Field Name
Maps to Column
Description
ORGANIZATION_NAME
ORGANIZATION_ID
Required. Derived from
ORGANIZATION_ID and
ORG_ORGANIZATION_
DEFINITIONS.
SET_OF_BOOK_NAME
Required.
ACTION_CODE
ACTION_CODE
Required. Indicates the ways to process the record to the API. Use:
*11 for Validate.
*12 for Create.
*13 for Simulate.
*14 for Process Data.
*15 for Create and Process.
CYCLE_COUNT_
HEADER_NAME
CYCLE_COUNT_
HEADER_ID
Required. Cycle count name derives CYCLE_COUNT_HEADER_ID from MTL_CYCLE_COUNT_HEADERS table.
COUNT_LIST_
SEQUENCE
COUNT_LIST_
SEQUENCE
Identifies an open count request for the specified cycle count. If an open count request matches the specified count sequence, then the default item and SKU information are used from the MTL_CYCLE_COUNT_ENTRIES table. Otherwise, the count request in the interface table is an unscheduled count, and the count sequence is inserted into the table with the remainder of the count request information. In this case, the item and SKU information are required.
INVENTORY_ITEM
INVENTORY_ITEM_ID
Derives the Inventory ITEM_ID from MTK_SYSTEM_ITEMS_B_KFV table for the organization.
REVISION
REVISION
Revision number if under revision control.
SUBINVENTORY
SUBINVENTORY
LOCATOR
LOCATOR_ID
Derives LOCATOR_ID from MTL_ITEM_LOCATIONS_KFV for the item.
LOT_NUMBER
LOT_NUMBER
Lot number of the item, if under lot control.
SERIAL_NUMBER
SERIAL_NUMBER
Serial number, if under serial number control.
PRIMARY_UOM_
QUANTITY
PRIMARY_UOM_
QUANTITY
Count of the item at the primary unit of measure.
COUNT_UOM
COUNT_UOM
Code of unit of measure count.
COUNT_QUANTITY
COUNT_QUANTITY
Quantity counted.
ADJUSTMENT_
ACCOUNT
ADJUSTMENT_ACCOUNT_
ID
Derives CODE_COMBINATION_ID from GL_CODE_COMBINATIONS_KFV for the given set of book name.
COUNT_DATE
COUNT_DATE
EMPLOYEE_FULL_NAME
EMPLOYEE_FULL_NAME
REFERENCE
REFERENCE
TRANSACTION_REASON
TRANSACTION_REASON
Reason for the cycle count entry.