Conversion Table for Revisions (bcmtc1125m000)

Use this session to to determine which revisions from MANMAN/HP must be migrated to ERP LN 6.1. It is possible that in MANMAN/HP revisions are entered on a purchase order or work order that do not exist in the master data of MANMAN/HP. These revisions cannot be migrated to the purchase order or production order of ERP LN 6.1, because of problems with references. Instead these revisions are migrated as text. In this session you can determine which revisions will be migrated and which revisions will be added as text on the order.

Preparation

No preparation activities are needed for this session.

Execution

Always mandatory because otherwise no revisions will be migrated to ERP LN 6.1.

Process Logic

Each revision present on a work order (MANDB.OWOF) or a purchase order (PURDB.POFIL) will be loaded into this session. Also the revision from master data table RESDB.ECOREC will be loaded into this session.

When the option Determine Revisions to Migrate is started this session will check which revisions present on the work or purchase orders are also present in the RESDB.ECOREC file. If this is the case the flag Migrate will be set to Yes. The option Generate Text for not Migrated Revisions will create a text line in table bcmtt101 for each revision that is not present in the RESDB.ECOREC file.

Order Origin

The Origin of the Ordernumber in MANMAN/HP.

Allowed values

  • Purchase Orders
  • Work (Production) Orders
  • Revisions
MANMAN Order Number

Order Number of MANMAN/HP.

MANMAN Order Line Number

Order Line Number of MANMAN/HP.

Allowed values

This field is only allowed when the Order Origin is Purchase.

Engineering Item Revision

Engineering Item Revision.

Migrate

This field displays if the revision will be migrated on the order or not.

Allowed values

The allowed values are Yes or No.

Default value

The default value is set to No.