Product Engineering - Engineering Change Management
Automated review of Engineering Change Orders
The Engineering Change Staging table is considered to be a "background" function as the records are processed by batch functions. Either directly following on the import or as separate batches run by the Job Queue.
The Engineering Change Request (ECR) is an important driver for the Engineering Change process. When the change is triggered by an ECR we know "where it is coming from" since source type and number are stored in the ECR.
When engineering responds with an ECO preferably the ECR is mentioned as reference which means the ECO can be handled as "pre-approved" since it is based on the Operations request.
When the ECR is not specified the "Get ECR Lines" action in the ECO allows the user to manually retrieve 1 or more ECR's being resolved by the ECO.
When the ECO is processed with the "Carryout Action" the linked ECR's are marked as "Processed" and the ECR Lifecycle status is set accordingly (ARCHIVE).
In this process the Engineering Change Staging shows a history of the imported records.
NOTE: To support the automated process a codeunit is provided which can be used in an Event Generator Activity in a Connectivity Studio Process: 11014979 N149 Create Eng. Change Order.
See also
Reference