Background: ECO Print

Settings in Document Output Parameters Maintenance (TDOC) can be configured to generate an ECO order at the time it is sent out for sign off approval and again when the document is sent for implementation approval.

The lists selected for sign off and implementation approval are used in combination with the approval hierarchy established for engineering change orders. Basically you tie ECOs to functions and then you can change the relationship of the individual to the function quickly. You can manually create the ECOs as needed.

This topic has these subtopics:

Print or Reprint Engineering Change Orders
Process the Print Queue
The ECO Document

Print or Reprint Engineering Change Orders

It is recommended that the ECO document be set up to print through the Document Management System. While ECOs can be printed and reprinted directly from ECO Print (ECOP), they are sent to the Output device selected in the Runtime option; output devices, copies and other options selected in Document Output Parameters Maintenance (TDOC) are not considered.

Caution
When you reprint ECOs, be sure to enter Selection options to specify an ECO number or range or click List to enter non-sequential ECO numbers. If you do not, you will reprint all ECOs in the system.

Process the Print Queue

If you set up the Document Output Parameters Maintenance (TDOC) program to queue new and/or changed documents, use the Engineering Change Order Print Queue (ECOLPM) program to process or maintain the print queue. See Overview: Document Management System.

The ECO Document

The program prints this information for engineering change orders if data exists:

  • Engineering change order (ECO) number

  • Date the ECO was entered

  • Current status of the ECO

  • Title of the ECO

  • Current revision of the ECO

  • Project name associated with the ECO

  • Priority of the ECO

  • Date signoff approval is due to be completed

  • Date implementation approval is due to be completed

  • Any pre-approval received as a part of the ECO request process

  • Name of the user who is writing the ECO

  • Reason for the ECO

  • ECO's effectivity code

  • Compliance code assigned to the ECO

  • Change type code assigned to the ECO

  • Functions and users that are required for signoff approval/implementation approval

  • ECO costs

  • Any Misc costs

Each item included in the change is listed with the following information if data exists:

  • Old ECL level
  • New ECL level (wild card designator may be shown until the ECOP has been run)
  • Sequence
  • Item number
  • Item description
  • Item type
  • New material cost

Bill of material change details:

  • Parent item number
  • Parent description
  • Component action type (A=add, C=Change and D=Delete)
  • Component item number
  • Component item description
  • Part designator for the component
  • From qty: the original quantity per for the component
  • To qty: the changed quantity per for the component
  • Effective date for the component
  • Expiration date for the component
  • Component reference