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 Master Schedule Service
 
Receive Master Schedule Service
This service is in the WmOAMFG1227 package and has the following fully-qualified service name: masterScheduling1227.intoOA.masterSchedule:receiveMasterSchedule.
This service imports master schedules.
The Planning Manager scans for rows with PROCESS_STATUS = 2. These records are then validated according to the rules in the Implementation manuals. If they are successfully processed, then the PROCESS_STATUS is set to 5. If they contain a validation error, then PROCESS_STATUS is set to 4, and the ERROR_MESSAGE is populated appropriately. The records with PROCESS_STATUS = 5 will remain in the interface table for the number of days specified by the profile option MRP:Interface Table History Days.
The Master Schedule Interface Load Program performs the processing. The Planning Manager periodically checks the Master Schedule Interface tables to determine new rows for processing.
Since the Planning Manager runs in asynchronous mode, this transaction does not execute concurrent processes.
Database Scripts
This service does not use database scripts.
Supporting Transaction Definitions
This service was built from the configured services defined in the following transaction definitions:
*setMasterScheduleTxn1227.txp
*MasterScheduleTxn1227.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 master schedules:
*specifyDefaultSettings specifies the default parameter settings required for service execution. You should change these settings accordingly.
*bizDocMapping maps the incoming business document structure to the required Oracle Applications data structures (the interface tables).
*getOrgId is a common utility and 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 corresponding to the ORGANIZATION_NAME.
*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.
*getInventoryItemId returns the INVENTORY_ITEM_ID corresponding to the supplied ITEM_CODE and the ORGANIZATION_NAME. This service is a transformer in bizDocMapping.
*convertToDateObject returns the outDate as a date object corresponding to the supplied inDate, which is in text format. This service is a transformer in bizDocMapping.
*setMoveTransactionTxn 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 Open Move Interface.
*getLineId is a transformer for mapping the data into the interface table data structure. It takes LINE_CODE as input, and queries Oracle Applications database to find the line ID.
*getProjectId is a transformer for mapping the business document to the interface table data structure. It takes the project name as input, and returns the project ID by querying Oracle Applications database.
*getTaskId gets the task ID from Oracle Applications database. It takes the task name and organization name as input, and finds the matching task ID.
*setMasterScheduleTxn 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 Master Schedule.
For more details on receive transactions, see Overview of Receive Service Transaction Processing.
Business Document Structure
This service uses the business document masterScheduleBizDoc. Its structure is as follows:
*MRP_SCHEDULE
MRP_SCHEDULE (Maps to MRP_SCHEDULE_INTERFACE)
Field Name
Maps to Column
Description
ITEM_NUMBER
ITEM_NUMBER
Segmented item number.
ORGANIZATION_
NAME
ORGANIZATION_
ID
Required. Derived from
ORG_ORGANIZATION_
DEFINITIONS.
INVENTORY_ITEM
INVENTORY_
ITEM_ID
Required. Derived from
MTL_SYSTEM_ITEMS_B_KFV.
SCHEDULE_
DESIGNATOR
SCHEDULE_
DESIGNATOR
Required. Master schedule identifier.
SCHEDULE_DATE
SCHEDULE_
DATE
Required.
RATE_END_DATE
RATE_END_
DATE
SCHEDULE_
QUANTITY
SCHEDULE_
QUANTITY
Required.
SCHEDULE_
COMMENTS
SCHEDULE_
COMMENTS
WORKDAY_
CONTROL
WORKDAY_
CONTROL
Indicates the action that the Master Schedule Interface Load takes if a schedule date is not a valid workday. Use:
*1 for Reject (default).
*2 for Shift forward,
*3 for Shift backward.
If WORKDAY_CONTROL is set to Null, the Master Schedule Interface Load program assumes the default value.
TRANSACTION_ID
TRANSACTION_
ID
Required for replacement items; it must match a record in MRP_SCHEDULE_DATES table.
SOURCE_CODE
SOURCE_
CODE
Required. Identifies external source.
SOURCE_LINE_ID
SOURCE_LINE_
ID
Required. External Source Line Identifier.
PROJECT_NAME
PROJECT_ID
Derives PROJECT_ID from PA_PROJECTS_ALL table.
TASK_NUMBER
TASK_ID
Derives Task ID from PA_TASKS table.
LINE_CODE
LINE_ID
Derives LINE_ID from WIP_LINES table.