MCTE Overview

MCTE Integration Overview

Manufacturing Component Traction Entry (MCTE) Integration is a utility for integrating MCTE transactions which are recorded outside of Dynamics GP into the Dynamics GP Manufacturing module. Information for the MCTE transactions is provided through an integration into several SQL staging tables. MCTE can run unattended, automatically processing new transactions as they are added to the staging tables. Since MCTE runs as part of the Dynamics GP client, it requires a User License and GP Client dedicated to running the processor.

MCTE Integration can create and post ISSUE transactions. It can handle:

  • Multiple issues against a single manufacturing order
  • Multi-bins
  • Non-tracked, Lot-tracked, and Serial-tracked inventory
  • Auto-selecting bins, lots and serial numbers
  • Issuing from specific bins, lots and serial numbers

Using the MCTE requires developing a direct-to-table import from the external manufacturing/inventory system into the Integration Tables provided by MCTE.  See the following sections for details about each integration table.

MCTEHdr (W7158MCTEHdr)

There are just a few required fields in this table. A simple insert looks like this:

SEQUENCE1 is a line number. It does not link to any other data in Dynamics GP. It will increment by 1 for each new record added to the table. If you did multiple partial ISSUEs for MO0237, the SEQUENCE1 field would be 1, 2, 3, 4 and so on.

Note that MarkAll tells MCTE to issue everything on the Picklist. If MarkAll = 1 then do not use MCTEItems and MCTEItemDtl.

MCTEItems (W7158MCTEItems)

The minimum information required in the table is Item Number, Location Code (Issue From Site) and Quantity. A simple insert looks like this:

SEQUENCE1 is the same value as MCTEHdr.SEQUENCE1. SEQNUMBR is a Line Number for the MCTEItems table. If you are issuing multiple components on one Issue transaction, SEQNUMBR will increment by 1 for each additional line item.

A white rectangular object with black text AI-generated content may be incorrect.

This shows MCTEItems for two separate MCTE transactions (1 and 2). The second transaction has two lines (1 and 2) for ARM and CAP100.

MCTEItemDtl (W7158MCTEItemDtl)

If you are using multi-bins and/or serial/lot tracked inventory, and you are not auto-selecting inventory, you will need to populate MCTEItemDtl. All fields are required.

A screenshot of a computer AI-generated content may be incorrect.

The key fields on this table are SEQUENCE1, SEQNUMBR, BINNMBR and SERLTNUM.

For MCTE transaction 2, ARM is a non-tracked item and multi-bins is enabled, so a bin is must be provided. Since BINNMBR is a key field, if inventory is drawn from multiple bins they would all be listed here with SEQUENCE1 = 2 and SEQNUMBR = 1.

The second item (CAP100) is consuming two different Lot Numbers from the AUTOCREATE bin.

Data Validation

There are a number of data validations performed on the integration tables before the integration process begins. They are described in the following pages that provide details on the integration tables. All validations are performed and all errors are reported. If any error is detected the MCTEHdr.Status is set to 1. The entire MCTE transaction (i.e. the records for a single SEQUENCE1) is then not processed.

Errors are recorded in a note in SY03900. MCTEHdr.NOTEINDX links to SY03900.NOTEINDX.

You can also view the errors inside GP from the MOGen Error Log window (Transactions >> Manufacturing >> MOGen Error Log).