OPM Product Development supports the acquisition of electronic signatures on electronic records. Electronic documentation replaces paper with a seamless interface of business activities that improves manufacturing throughput and enhances the overall quality of operations in the enterprise. The following provides information for online and deferred events that are e-record and e-signature enabled in the OPM Product Development application. A brief discussion of each event is provided. Refer to the Oracle E-Records Implementation Guide for details on setting up the events and approvals.
The following table lists the events that are e-record and e-signature enabled for OPM Product Development:
| Event | Online or Deferred |
|---|---|
| Operation Status Change Approval | Deferred |
| Routing Status Change Approval | Deferred |
| Formula Status Change Approval | Deferred |
| Recipe Status Change Approval | Deferred |
| Validity Rule Status Change Approval | Deferred |
| Formulation Specification Status Change Approval | Deferred |
| Item Substitution Status Change Approval | Deferred |
When the status of an operation is changed, the e-signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them their e-signature must be entered before the status of the operation is changed to the requested status.
The Change Status window in Product Development starts the signature capturing process whenever an operation status change is requested. This replaces the existing operation approval workflow.
When the status of a routing is changed the e-signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them their e-signature must be entered before the status of the routing is changed to the requested status.
When the status of a formula is changed the e-signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them their e-signature must be entered before the status of the formula is changed to the requested status.
When the status of a recipe is changed the e-signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them their e-signature must be entered before the status of the recipe is changed to the requested status.
When the status of a validity rule is changed the e-signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them their e-signature must be entered before the status of the validity rule is changed to the requested status.
When the status of a formulation specification is changed the e-signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them their e-signature must be entered before the status of the formulation specification is changed to the requested status.
When the status of an item substitution is changed the e-signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them their e-signature must be entered before the status of the item substitution is changed to the requested status.
Find the following information in the Oracle E-Records Implementation Guide:
Events
Event Key
Subscriptions
From the XML Gateway, using the existing Event and Event Key, derive the XML Map, Subscription Data, and Metadata.
Set up the capturing of e-signatures and e-records for the following seeded statuses and any other customized statuses:
Approved for Laboratory Use
Approved for General Use
On Hold
Frozen
Obsolete/Archived
| Name | Display Name | Description | Status | Owner Name | Owner Tag |
|---|---|---|---|---|---|
| oracle.apps.gmd.operation.sts | GMD ERES Operation Status Change Approval | This event is raised when the status of an operation is being changed. | Enabled | Product Development | GMD |
| oracle.apps.gmd.routing.sts | GMD ERES Routing Status Change Approval | This event is raised when the status of a routing is being changed. | Enabled | Product Development | GMD |
| oracle.apps.gmd.formula.sts | GMD ERES Formula Status Change Approval | This event is raised when the status of a formula is being changed. | Enabled | Product Development | GMD |
| oracle.apps.gmd.recipe.sts | GMD ERES Recipe Status Change Approval | This event is raised when the status of a recipe is being changed. | Enabled | Product Development | GMD |
| oracle.apps.gmd.validity.sts | GMD ERES Recipe Validity Rule Status Change Approval | This event is raised when the status of a validity rule is being changed. | Enabled | Product Development | GMD |
| oracle.apps.gmd.auto.recipe | GMD ERES Recipe Generation | This event is raised when a recipe is generated. | Enabled | Product Development | GMD |
| oracle.apps.gmd.formspec.sts | GMD ERES Formulation Specification Status Change Approval | This event is raised when the status of a formulation specification is being changed. | Enabled | Product Development | GMD |
| oracle.apps.gmd.itemsub.sts | GMD ERES Item Substitution Status Change Approval | This event is raised when the status of an item substitution is being changed. | Enabled | Product Development | GMD |
| Event Name | Event Key | User Event Key |
|---|---|---|
| oracle.apps.gmd.operation.sts | Oprn_id | Gmd_operations_vl.oprn_no - Gmd_operations_vl.oprn_vers |
| oracle.apps.gmd.routing.sts | Routing_id | Fm_rout_dtl.Routing_no - fm_rout_dtl.routing_vers |
| oracle.apps.gmd.formula.sts | Formula_id | Fm_form_mst.formula_no, - fm_form_mst.formuls_vers |
| oracle.apps.gmd.recipe.sts | Recipe_id | Gmd_eres_recipes_vw.recipe_no - gmd_eres_recipes_vw.recipe_version |
| oracle.apps.gmd.validity.sts | Recipe_validity_rule_id | Gmd_recipe_validity_rules.recipe_id - Gmd_recipe_validity_rules.recipe_use - Gmd_recipe_validity_rules.orgn_code - Gmd_recipe_validity_rules.item_id |
| oracle.apps.gmd.auto.recipe | Formula_id | fm_form_mst_b.formula_no - fm_form_mst_b.formula_vers |
| oracle.apps.gmd.formspec.sts | N/A | N/A |
| oracle.apps.gmd.itemsub.sts | N/A | N/A |
The system is HM001 for all subscriptions.
| Source Type | Event Filter | Phase | Status | Rule Data | Rule Function | Parameters | Priority |
|---|---|---|---|---|---|---|---|
| Local | oracle.apps.gmd.operation.sts | 0 | Disabled | Key | EDR_RULE.ESIGN_RULE | EDR_XML_MAP_CODE = 'oracle.apps.gmd.operation_sts'; EDR_AME_TRANSACTION_TYPE = 'oracle.apps.gmd.operation_sts'; | Normal |
| Local | oracle.apps.gmd.routing.sts | 0 | Disabled | Key | EDR_RULE.ESIGN_RULE | EDR_XML_MAP_CODE = 'oracle.apps.gmd.routing_sts'; EDR_AME_TRANSACTION_TYPE = 'oracle.apps.gmd.routing_sts'; | Normal |
| Local | oracle.apps.gmd.formula.sts | 0 | Disabled | Key | EDR_RULE.ESIGN_RULE | EDR_XML_MAP_CODE = 'oracle.apps.gmd.formula_sts'; EDR_AME_TRANSACTION_TYPE = 'oracle.apps.gmd.formula_sts'; | Normal |
| Local | oracle.apps.gmd.recipe.sts | 0 | Disabled | Key | EDR_RULE.ESIGN_RULE | EDR_XML_MAP_CODE = 'oracle.apps.gmd.recipe_sts'; EDR_AME_TRANSACTION_TYPE = 'oracle.apps.gmd.recipe_sts'; | Normal |
| Local | oracle.apps.gmd.validity.sts | 0 | Disabled | Key | EDR_RULE.ESIGN_RULE | EDR_XML_MAP_CODE = 'oracle.apps.gmd.validity_sts'; EDR_AME_TRANSACTION_TYPE = 'oracle.apps.gmd.validity_sts'; | Normal |
| Local | oracle.apps.gmd.auto.recipe | 0 | Enabled | Key | EDR_RULE.ESIGN_RULE | EDR_XML_MAP_CODE = 'oracle.apps.gmd.auto.recipe'; EDR_AME_TRANSACTION_TYPE = 'oracle.apps.gmd.auto.recipe'; | Normal |
| Local | oracle.apps.gmd.formspec.sts | 0 | Enabled | Key | EDR_PSIG_RULE.PSIG_RULE | N/A | Normal |
| Local | oracle.apps.gmd.itemsub.sts | 0 | Enabled | Key | EDR_PSIG_RULE.PSIG_RULE | N/A | Normal |
| Oracle Application | Transaction Type ID | Transaction Type Description | Line Item Id Query String |
|---|---|---|---|
| Oracle Process Manufacturing Product Development | oracle.apps.gmd.operation.sts | GMD ERES Operation Status Change Approval | N/A |
| Oracle Process Manufacturing Product Development | oracle.apps.gmd.routing.sts | GMD ERES Routing Status Change Approval | N/A |
| Oracle Process Manufacturing Product Development | oracle.apps.gmd.formula.sts | GMD ERES Formula Status Change Approval | N/A |
| Oracle Process Manufacturing Product Development | oracle.apps.gmd.recipe.sts | GMD ERES Recipe Status Change Approval | N/A |
| Oracle Process Manufacturing Product Development | oracle.apps.gmd.validity.sts | GMD ERES Recipe Validity Rule Status Change Approval | N/A |
| Oracle Process Manufacturing Product Development | oracle.apps.gmd.recipe.generation | GMD ERES Recipe Generation | N/A |
| Oracle Process Manufacturing Product Development | oracle.apps.gmd.formspec.sts | GMD ERES Formulation Specification Status Change Approval | N/A |
| Oracle Process Manufacturing Product Development | oracle.apps.gmd.itemsub.sts | GMD ERES Item Substitution Status Change Approval | N/A |
The rules basing the status on Approved For Laboratory Use and Approved For General Use are seeded.
As part of the implementation, complete these activities. The following mandatory and nonmandatory attributes must be added for all transaction types. Substitute the values shown with appropriate transaction specific values or data:
| Name | Attribute Type | Description | Static Usage | Usage |
|---|---|---|---|---|
| ALLOW_DELETING_RULE_GENERATED_APPROVERS | boolean | Whether to let the calling application (or its end users) delete approvers generated by the rules. | Yes | False |
| ALLOW_REQUESTOR_APPROVAL | boolean | Whether to allow requestors to approve their own transactions (when the rules do so). | Yes | False |
| AT_LEAST_ONE_RULE_MUST_APPLY | boolean | Whether to require that at least one rule apply to each transaction. | Yes | False |
| EFFECTIVE_RULE_DATE | date | The date that determines which rules are active. | Yes | (blank) |
| TRANSACTION_DATE | date | Date transaction occurred. | No | Select ame_util.versionDateToString(CREATION_DATE) from gme_batch_header where batch_id=:transactionId |
| TRANSACTION_GROUP_ID | number | Business-group ID in which transaction occurred. | Yes | (blank) |
| TRANSACTION_ORG_ID | number | Org ID in which transaction occurred. | Yes | (blank) |
| TRANSACTION_REQUESTOR_PERSON_ID | number | Person ID of person initiating transaction. | Yes | (blank) |
| TRANSACTION_REQUESTOR_USER_ID | number | User ID of person initiating transaction. | No | Select Last_updated_by from gme_batch_header where batch_id=:transactionId |
| TRANSACTION_SET_OF_BOOKS_ID | number | Set of books ID in which transaction occurred. | No | (blank) |
| USE_RESTRICTIVE_LINE_ITEM_EVALUATION | boolean | Whether to require that the same line item satisfy all line-item conditions in a given rule. | Yes | False |
| WORKFLOW_ITEM_KEY | string | The transaction's workflow item key. | No | (blank) |
| WORKFLOW_ITEM_TYPE | string | The transaction's Workflow item type. | No | (blank) |
| ALLOW_DELETING_RULE_GENERATED_APPROVERS | boolean | Whether to let the calling application (or its end users) delete approvers generated by the rules. | Yes | False |