How You Capture E-Records and E-Signatures for Manufacturing Work Order Approval in Deferred Mode
You can enable the ability to capture electronic signatures and generate electronic records for work order creation, and work order update.
The Electronic Records and Electronic Signatures process for work order is initiated when the work order is put in Released status (or a custom status associated to Released status) for the first time through the user interface.
The approval process is initiated in deferred mode. Note that when the work order is put in Pending Approval status, and you can't edit it. The work order will be in view only mode.
After the approval flow is complete, and if the E-Record is approved, the work order is put in Released status (or the custom status). If the E-Record was rejected, the work order is put in the original status (this could be Unreleased or on hold or any custom status associated with these statuses).
The manufacturing work order e-record contains the following information as applicable in the work order:
-
Work order header and details
-
Transactional item attributes if it is a configured product
-
Preassigned product lot and serial details
-
Project details
-
Operation details, including operation items, operation outputs, operation resources, operation item substitutes, and documents
-
Material reservations
-
Production exceptions
-
Attachment details
You can search and retrieve electronic records in the electronic records work area using multiple search criteria like the contents of the report title, the transaction type, organization, signed date, and status. The electronic records are stored in secured document repository and cannot be modified or deleted. Oracle E-Signatures and E-Records store both the approved and rejected records.
Using a deferred approval process with notifications, the work order is held in a Pending Approval status until the approvals are obtained. Depending upon the outcome of the approval, the work order is saved in the Approved status or rolled back to the previous status. The status change history captures the change from and to Pending approval status.
Here are a few considerations for you when you capture E-Records and E-Signatures for a manufacturing work order release in deferred mode:
- You can configure different approval rules based on the work method.
- You can submit a work order for approval when the initially changing to a user-defined status that is associated with the system status of Released.
- You can't update a work order in Pending Approval status through the UI, File Based Data Import (FBDI), or REST. You must wait for the approval process to complete as approved or rejected before making further changes.
- You can't create work orders in the Released status through the UI if e-records and e-signatures are enabled for the organization. However, you can create work orders in the Released status through FBDI and REST.
- You can't submit a work order that has been previously released for e-record and e-signature approval again. Instead, you can enable audit trail to track work order changes.
- You can't release and pick a work order in a single action when e-records and e-signatures is enabled. Instead, you can release a work order and submit it for approval before picking materials.
-
You can't release a work order for e-record and e-signature approval through FBDI, REST, the Material Availability Assignments page, and the Edit Production Exception page.
- You can't prevent changes to material reservations for work orders in Pending Approval status. However, you can manually coordinate when material reservation changes in Inventory need to be implemented for the affected work order before initiating the e-record and e-signature approval process.
- You can't configure the suppression of the e-signature approval based on specific conditions. However, you can configure an automatic, conditional approval based on approval rules.