This chapter covers the following topics:
Activities are actions performed during production through API.
PLSQL
Create_Activity_PLSQL
Not Applicable
Not Applicable
Not Applicable
Not Applicable
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Create_Activity | Create Activities | GMD_ACTIVITIES_PUB_INSERT_ACTIVITY | GMD_ACTIVITIES_PUB_INSERT_ACTIVITY | GMD_ACTIVITIES_PUB_INSERT_ACTIVITY_Main |
Verification | - | VERIFICATION_COMPONENT |
This flow creates Test through API
PLSQL
Create_Test_PLSQL
Rerun parameter should be NUMERIC.
The following profile options must be set:
Profile | Value |
---|---|
EDR: E-records and E-signatures | No |
Not Applicable
The following data must be set up:
Interface | Field Name | Field Value |
---|---|---|
Organization | Organization | PR1 |
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Create_Test | Create Tests | GMD_QC_TESTS_PUB_CREATE_TESTS | GMD_QC_TESTS_PUB_CREATE_TESTS | GMD_QC_TESTS_PUB_CREATE_TESTS_Main |
Verification | - | VERIFICATION_COMPONENT |
This flow creates Formula through API.
PLSQL
Create_Formula_PLSQL
Formula Security is OFF
UOM Conversions are defined for all items
Rerun parameter should be NUMERIC.
The following profile option must be set:
Profile | Value |
---|---|
EDR: E-records and E-signatures | No |
Not Applicable
The following data must be set up:
Interface | Field Name | Field Value |
---|---|---|
Organization | Organization | PR1 |
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Create_Formula | Create Formula | GMD_FORMULA_PUB_INSERT_FORMULA | GMD_FORMULA_PUB_INSERT_FORMULA | GMD_FORMULA_PUB_INSERT_FORMULA_Main |
Verification | - | VERIFICATION_COMPONENT |
Create Resource actions performed during production through API.
PLSQL
Create_Resource_PLSQL
Cost component class and UOM
Not Applicable
The following predefined data must be used:
Transaction | Field Name | Field Value |
---|---|---|
User | User Name | Process_ops |
Not Applicable
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Create_Resource | Create Resource | GMP_RESOURCES_PUB_INSERT_RESOURCES | GMP_RESOURCES_PUB_INSERT_RESOURCES | GMP_RESOURCES_PUB_INSERT_RESOURCES_Main |
Verification | - | VERIFICATION_COMPONENT |
This flow creates and releases Multiple Batches through API.
PLSQL
Create_Release_Batch_PLSQL
Formula, Routing, and Recipe setup
The following profile option must be set:
Profile | Value |
---|---|
EDR: E-records and E-signatures | No |
Not Applicable
The following data must be set up:
Interface | Field Name | Field Value |
---|---|---|
User | User Name | Process_ops/welcome |
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Create_Batch | Create Batch | GME_API_PUB_CREATE_BATCH | GME_API_PUB_CREATE_BATCH | GME_API_PUB_CREATE_BATCH_Main |
Release_Batch | Release Batch | GME_API_PUB_RELEASE_BATCH | GME_API_PUB_RELEASE_BATCH | GME_API_PUB_RELEASE_BATCH_Main |
Verification | - | VERIFICATION_COMPONENT |
This flow creates batch through UI and releases Batch through API.
Mixed
Form_Batch_Release_PLSQL
Formula, Routing, and Recipe setup
The following profile option must be set:
Profile | Value |
---|---|
EDR: E-records and E-signatures | No |
Not Applicable
The following data must be set up:
Interface | Field Name | Field Value |
---|---|---|
User | User Name | Process_ops/welcome |
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Create_Batch | UI Components: Fnd_Batches_New Batch Create_Batch | |||
Release_Batch | Release Batch | GME_API_PUB_RELEASE_BATCH | GME_API_PUB_RELEASE_BATCH | GME_API_PUB_RELEASE_BATCH_Main |
Verify_Batch_Status_Exit | - | UI Components: Find_Batches Verify_Batch_Status |
This flow creates batch through open interface in Oracle Process Manufacturing Execution. These flows uses single data in creation and create a batch.
Open Interface
Create_Batch_OI
Availability of Recipe and Opened Inventory Period
The following profile option must be set:
Profile | Value |
---|---|
EDR: E-records and E-signatures | No |
The following predefined data must be used:
Entity | Field Name | Field Value |
---|---|---|
User | User Name | Process_ops/welcome |
Not Applicable
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Create_Batch | This scenario creates batch through Recipe, Product Output | Batch_Import_Open_Interface_GMEBTIMP | Batch_Import_Open_Interface_GMEBTIMP | Batch_Import_Open_Interface_GMEBTIMP |
Verification | - | VERIFICATION_COMPONENT |
Perform action on batch through open interface in Oracle Process Manufacturing Execution. These flows use single data in creation and create and perform action on a batch.
Open Interface
Batch_Action_OI
Availability of Batch number with status pending(1) and opened inventory period
The following profile option must be set:
Profile | Value |
---|---|
EDR: E-records and E-signatures | No |
The following predefined data must be used:
Entity | Field Name | Field Value |
---|---|---|
User | User Name | Process_ops/welcome |
Not Applicable
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Batch_Action_Interface | Performs action on Batch e.g., Release, Cancel | Batch_Actions_Import_Manager_GMEBACTM | Batch_Actions_Import_Manager_GMEBACTM | Batch_Actions_Import_Manager_GMEBACTM |
Verification | - | SELECT VERIFICATION_COMPONENT |
Creates and Updates Item Cost and Resource Cost for Oracle Process Manufacturing Financials. This flow uses single data in creation and update of Item Cost and Resource cost lines.
PLSQL
OPM_GMF_Item_Cost_Resource_Cost_PLSQL
Availability of Current and Open OPM Calendar and Period
Not Applicable
The following predefined data must be used:
Entity | Field Name | Field Value |
---|---|---|
User | User Name | Process_ops/welcome |
Not Applicable
Following are the details of the scenarios in the flow:
Scenario | Objective | Artifact Method | Component Set | Main Component |
---|---|---|---|---|
Create_Item_Cost | This scenario creates an Item Cost in OPM enabled organizations for a given OPM Calendar and Period combination | GMF_ITEMCOST_PUB_CREATE_ITEM_COST | GMF_ITEMCOST_PUB_CREATE_ITEM_COST | GMF_ITEMCOST_PUB_CREATE_ITEM_COST_Main |
Update_Item_Cost | This scenario updates existing Item Cost in OPM enabled organizations for a given OPM Calendar and Period combination | GMF_ITEMCOST_PUB_UPDATE_ITEM_COST | GMF_ITEMCOST_PUB_UPDATE_ITEM_COST | GMF_ITEMCOST_PUB_UPDATE_ITEM_COST_Main |
Create_Resource_Cost | This scenario creates a Resource Cost in OPM enabled organizations for a given OPM Calendar and Period combination | GMF_RESOURCECOST_PUB_CREATE_RESOURCE_COST | GMF_RESOURCECOST_PUB_CREATE_RESOURCE_COST | GMF_RESOURCECOST_PUB_CREATE_RESOURCE_COST_Main |
Update_Resource_Cost | This scenario updates existing Resource Cost in OPM enabled organizations for a given OPM Calendar and Period combination | GMF_RESOURCECOST_PUB_UPDATE_RESOURCE_COST | GMF_RESOURCECOST_PUB_UPDATE_RESOURCE_COST | GMF_RESOURCECOST_PUB_UPDATE_RESOURCE_COST_Main |
Verification | - | VERIFICATION_COMPONENT |