This chapter covers the following topics:
Oracle Process Manufacturing Product Development delivers comprehensive and powerful tools that allow process manufacturers to manage the product life cycle from inception through production, accelerate innovation to market, and minimize costs. It also includes Oracle Process Manufacturing Quality Management, which helps process companies to achieve product consistency, enforce proactive quality assurance, streamline quality lab productivity, and assure customer and regulatory compliance.
This section provides information on the common prerequisites, profile options, and data setups required for executing the Oracle Process Manufacturing Product Development flows. Flow specific requirements are documented along with each flow in the subsequent sections.
The following are the prerequisites for executing the flows:
Lab and Inventory Organization are defined
Product development parameters are defined.
Finished goods template is available.
Default formula status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No – To disable E-signature Yes – To enable E-signature |
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| User | User Name | Process_ops |
| Password | welcome | |
| Responsibility | Responsibility Name | Formulator Inventory Super User (Process Operations) Oracle HRMS Process Engineer Oracle Process Manufacturing Process Planning Workflow Administrator Web Applications ERES Administrator Approvals Management Business Analyst |
| Item Template | Template | Process Item (with process manufacturing attributes enabled) |
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PRU - US Operations (Process Manufacturing) |
| Inventory Organization | PR1- Main Process Manufacturing LAB - Process organization |
|
| Recipe | Recipe | Recipe and Validity Rule |
| Organization Parameters: Query for ‘LAB’ | Laboratory | Enabled |
Resources are assets that are used to manufacture production batches, including production equipment and employee labor, and can be utilized in different organizations. The Manage Plant Resources flow creates resources for performing activities and operations in a manufacturing plant.
This section provides information on prerequisites, profile options, and data setups required to execute the Manage Plant Resources flow.
GMD_Process_Operations
The following are the prerequisites for executing this flow:
Unit of Measure Types is defined.
Unit of Measure is defined.
Cost Component Class is defined.
Not applicable.
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organizations | Organizations | PR1 |
Not applicable.
The Manage Process Parameters flow associates process parameters to a resource, at the resource level within an operation and a recipe, as well as at the production batch level.
This section provides information on prerequisites, profile options, and data setups required to execute the Manage Process Parameters flow.
GMD_Process_Parameters
The following is a prerequisite for executing this flow:
Units for process parameters are defined.
Not applicable.
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organizations | Organizations | PR1 |
| Test Units | Test Units | $ |
Not applicable.
Activities are actions performed during production. Activities are set up to divide a manufacturing process into logical breakpoints. The Manage Activities flow creates activities to be performed on the shop floor with the help of resources in order to manufacture the finished product.
GMD_Activities
This section provides information on prerequisites, profile options, and data setups required to execute the Manage Activities flow.
The following is a prerequisite for executing this flow:
Cost analysis codes are set up.
Not applicable.
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Analysis Code | Analysis Code | VAL |
Not applicable.
Operations are a combination of activities performed in a production batch and the resources used to perform those activities. The Manage Process Operation flow creates operations to perform different activities on the shop floor.
This section provides information on prerequisites, profile options, and data setups required to execute the Manage Process Operation flow.
GMD_Process_Operations
The following are the prerequisites for executing this flow:
Activities are created.
Resources are created.
Operation classes are created (Optional).
UOM are created.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organizations | Organizations | PR1 |
| Activity | Activity | BLENDING |
| Process Operation Classes | Process Operation Classes | BLND |
| Unit of Measure | Unit of Measure | KGM |
| Generic Resource | Generic Resource | 1-BLENDER |
| Plant Resource | Plant Resource | 1-BLENDER |
| Cost Component Class | Cost Component Class | 1-EQUIP |
| Cost Analysis Code | Cost Analysis Code | VAL |
Not applicable.
This flow creates a new version of a formula. Generally new versions of a formula are created when there are changes in the existing formula, in terms of quantity and ingredients used.
This section provides information on prerequisites, profile options, and data setups required to execute the Formula Version Control flow.
GMD_Formulator_Version_Control
None.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organizations | Organizations | PR1 |
Not applicable.
Formulas can be scaled up or down by input or by output:
If the formula input ingredients are scaled, a specific scaling factor is applied to all scalable ingredients. A calculated output scale factor is applied to all scalable outputs.
If the formula outputs are scaled, a factor is applied to all scalable outputs. A calculated input scale factor is applied to all scalable ingredients.
In order for this approach to be successful, it must be specified whether the quantities of each item in the formula are fixed or scalable.
The Formula Scaling flow scales the formula up or down as per requirement.
This section provides information on prerequisites, profile options, and data setups required to execute the Formula Scaling flow.
GMD_Formula_Scaling
The following are the prerequisites for executing this flow:
Setup ingredients and products with UOM conversion are defined based on Yield UOM and Mass UOM.
Formula classes are created (Optional).
Organization parameters are set (Optional).
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
| Organization | Organization | PR – Process Master |
Not applicable.
The Formula Inquiry Selection window is the starting point for Formula Inquiry queries. Using a selection range to narrow the search of formula information, a summary list of formulas can be displayed that fit the parameters specified. The inquiry delivers a Formula Inquiry Summary View window where parent level and intermediate level formula information is displayed.
This section provides information on prerequisites, profile options, and data setups required to execute the Formula Inquiry flow.
GMD_Prod_Dev_Formula_Inquiry
The following are the prerequisites for executing this flow:
Default Recipe Status is set to New.
Default Validity Rule Status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
The following predefined data must be used:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
| Organization | Organization | PR – Process Master |
Not applicable.
E-records are records that store data electronically and can be retrieved as and when required. Using e-records for transactions eliminates the need to maintain paper records.
The E-Record Setup for Process Execution Product Development flow creates the setup for e-record generation.
This section provides information on prerequisites, profile options, and data setups required to execute the E-Record Setup for Process Execution Product Development flow.
GMD_ERES_Setup
The following are the prerequisites for executing this flow:
Default Formula Status is set to New.
Default Operation Status is set to New.
Default Routing Status is set to New.
Default Recipe Status is set to New.
Default Validity Rule Status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
Recipe is automatically generated once the formula is generated as per the setup. The Recipe Generation window configures rules for the creation of a recipe and validity automatically when a formula is created.
The Auto Recipe Generation with E-Record (Default Status) flow generates the recipe automatically when a formula is created. The approver defined in Oracle Approvals Management (AME) must approve the recipe.
This section provides information on prerequisites, profile options, and data setups required to execute the Auto Recipe Generation with E-Record (Default Status) flow.
ERES_Through_Auto_Recipe_Generation_With_Default_Status
None.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | Yes |
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
This flow creates experimental items, lab formulas, and lab batches to create a production batch.
This section provides information on prerequisites, profile options, and data setups required to execute the Experimental Item Validation, New Product Development Setups, and Batch Execution flow.
Experimental_Item_Validation_NPD_Setups_And_Batch_Execution
None.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
Quality results serve as the basis for measuring actual material characteristics against expected quality records, and for assigning follow-up actions to be taken throughout the supply chain.
The Process Quality Results flow enters test results, assigns result evaluation and changes sample disposition status automatically.
This section provides information on prerequisites, profile options, and data setups required to execute the Process Quality Results flow.
Inventory_Convergence_Process_Quality_Results
The following are the prerequisites for executing the flow:
Default Formula Status is set to New.
Default Recipe Status is set to New.
Default Validity Rule Status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
AME rules must be disabled for transactions that do not require notifications. This flow disables all AME rules for various transaction types.
This section provides information on prerequisites, profile options, and data setups required to execute the Disable AME Rule Profiles flow.
OPM_Disable_Vision_AME_Rule_Profiles
None.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
A test helps determine a quality characteristic or attribute of an item or lot. A test method describes how a test is performed. A test method can refer to a test protocol or standard operating procedure.
The Manage Tests flow creates test setup, and updates tests as well as test methods.
This section provides information on prerequisites, profile options, and data setups required to execute the Manage Tests flow.
QM_Test_Setup
The following are the prerequisites for executing this flow:
Default Formula Status is set to New.
Default Recipe Status is set to New.
Default Validity Rule Status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
This flow defines unit of measure (UOM) conversions between units, creates an item sample, and enters results. After entering the results it changes the disposition, which is the status of a sample or sample group with respect to analysis. While the disposition is changed, a notification is sent to the approver defined in Oracle Approvals Management.
This section provides information on prerequisites, profile options, and data setups required to execute the Lot UOM Conversion flow.
Final_Lot_UOM_Conversions
The following are the prerequisites for executing this flow:
Default Formula Status is set to New.
Default Recipe Status is set to New.
Default Validity Rule Status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
This flow creates a purchase order and receives materials into the inventory without inspecting the goods being received.
This section provides information on prerequisites, profile options, and data setups required to execute the Direct Delivery of Material into Inventory Using Receipt Routing flow.
QC_Direct_Delivery_Auto_Sample_Checked
The following are the prerequisites for executing this flow:
Default Formula Status is set to New.
Default Recipe Status is set to New.
Default Validity Rule Status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
Specification identifies the target or ideal result of a quality control assay test performed on an item or lot. Assay codes and item attributes are combined to devise test specifications for items and lots.
The Create Specification and its Validity Rules creates a specification and the rules to test if a specification is valid.
This section provides information on prerequisites, profile options, and data setups required to execute the Create Specification and its Validity Rules flow.
Quality_Specifications_And_Validity_Rules
The following are the prerequisites for executing this flow:
Default Formula Status is set to New.
Default Recipe Status is set to New.
Default Validity Rule Status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |
The Specification Comparison flow compares two different specifications for the same item. Comparison takes place between tests and its results are entered.
This section provides information on prerequisites, profile options, and data setups required to execute the Specification Comparison flow.
Specification_Comparison
The following are the prerequisites for executing this flow:
Default Formula Status is set to New.
Default Recipe Status is set to New.
Default Validity Rule Status is set to New.
The following profile options must be set:
| Profile Option Name | Profile Option Value |
|---|---|
| EDR: E-records and E-signatures | No |
Not applicable.
The following data must be set up:
| Window Name | Field Name | Field Value |
|---|---|---|
| Organization | Organization | PR1 |