Excel – MO Header

Excel Map – MO Header

SHEET 1. The first row must have column headers. Data should begin in row 2.

Column	Description
(A) MONumber	May be blank when performing 1-Step receiving (a new MO is created on the fly) AND not importing data in the other sheets (i.e. Picklist). When blank, MORI will generate the next available MO Number. When importing additional data (i.e. Picklist), you must provide a value in this column so that the import can find matching records in each of the worksheets. To have the system generate the next available MO Number during the import, you can create a numbering scheme that begins with a question mark (?). For example: ?0001 ?0002 ?0003 and so on You would then use “?0001” as the MO Number in the other worksheets. When the import runs it will see “?0001” and generate the next GP MO Number, and records from the other worksheets will be brought in for “?0001” using the new MO Number. If the MO Receipt should be recorded against an existing MO, provide the MO Number and mark the Allow Receipts on Existing MOs box on MOGen. Do not use a numbering sequence that includes a dash “-“. Such as MO0123-16384. Since the MO Receipt Integration also uses a dash when performing partial receipts, an MO Number with a dash will prevent it from correctly identifying the “parent” MO.
(B) Sequence	If multiple receipts for an MO are going to be recorded, SEQUENCE1 should increment by 1 for each receipt. If only one receipt is created per MO, SEQUENCE1 may be zero or one. If 1-Step Receiving is being performed, MO Number and Sequence may be blank.
(C) Item Number	The Item Number produced. The Item Number must be an existing Dynamics GP Item Number, which has at minimum, a MFG BOM Header and Primary Routing. The Item Number must be Active. 30-character, upper-case string. Not required if posting a receipt for an existing MO.
(D) Quantity	The quantity of the Item Number produced. This will be the End Quantity for the MO. As is standard functionality within Dynamics GP, the Base UOM will be used when processing MO’s. The quantity must be compatible with the Item’s Quantity Decimals in GP. For example, if the item has zero quantity decimals, entering a Receipt Quantity of 1.25 will result in an error.
(E) SerLotNum	For non-serial/lot tracked items, leave this field blank. 20-character, upper-case string. If the MO Receipt produces one Lot Number or Serial Number, populate this field. For multiple lot numbers, create a separate MO Receipt record for each Lot Number received.
(F) LotAttrib1	May be populated for Lot Controlled items. Ignored for all other items. May be blank. 10-character string
(G) LotAttrib2	May be populated for Lot Controlled items. Ignored for all other items. May be blank. 10-character string
(H) LotAttrib3	May be populated for Lot Controlled items. Ignored for all other items. May be blank. 10-character string
(I) LotAttrib4	May be populated for Lot Controlled items. Ignored for all other items. May be blank. Date
(J) LotAttrib5	May be populated for Lot Controlled items. Ignored for all other items. May be blank. Date
(K) MFGDate	May be populated for Lot Controlled items. Ignored for all other items. May be blank. Date
(L) EXPDate	May be populated for Lot Controlled items. Ignored for all other items. May be blank. Date
(M) DATE1	Not used. May be blank. If provided, will populate W7158MOHdr.DATE1.
(N) TIME1	Not used. May be blank. If provided, will populate W7158MOHdr.TIME1. Must use this format (hh:mm:ss) 12:31:07
(O) LocationCode	The Post To site for the MO. This may be blank if the Default Scheduling Preference provides a Post To Site, or Scheduling Preference is provided in the spreadsheet and it provides a Post To Site. See Using MORI: Sites for more information.
(P) LastReceipt	Blank or 0 = False 1 = True If you are integrating the final receipt for an MO, and the total quantity received is less than the End Quantity on the MO, set the LastReceipt flag to 1. MORI will then post the receipt and close the MO (or Cancel it if there were several partial receipts). If the last receipt brings the total quantity received equal to (or greater than) the End Quantity, MORI will automatically Cancel the source MO. If you are going to Allocate inventory to the MO, or use Outsourcing, or perform WIP Data Collection, you may integrate one and only one receipt for the MO, and the LastReceipt flag must be set to 1 (true).
(Q) RoutingName	If blank, the Primary Routing is used.
(R) BOMCat	Allowed values Blank, 0 or 1 = MFG BOM 2 = ENG BOM 3 = ARCH BOM 4 = CONFIG BOM
(S) BOMName	Must be populated if BOMCat = 3 or 4
(T) SchedPref	If blank, the default Scheduling Preference is used. If a Scheduling Preference is provided, it provides the Draw From and Post To sites (this overrides the location code (LOCNCODE) provided above.
(U) BinNum	May be blank. Overrides the Material Receipts Bin from the Item Site Default Bins window. The Bin must be valid for the Post To Site. See LOCNCODE code for Post To Site rules.

Column

Description

(A)

MONumber

May be blank when performing 1-Step receiving (a new MO is created on the fly) AND not importing data in the other sheets (i.e. Picklist). When blank, MORI will generate the next available MO Number.

When importing additional data (i.e. Picklist), you must provide a value in this column so that the import can find matching records in each of the worksheets. To have the system generate the next available MO Number during the import, you can create a numbering scheme that begins with a question mark (?). For example:

?0001
?0002
?0003 and so on

You would then use “?0001” as the MO Number in the other worksheets. When the import runs it will see “?0001” and generate the next GP MO Number, and records from the other worksheets will be brought in for “?0001” using the new MO Number.

If the MO Receipt should be recorded against an existing MO, provide the MO Number and mark the Allow Receipts on Existing MOs box on MOGen.

Do not use a numbering sequence that includes a dash “-“. Such as MO0123-16384. Since the MO Receipt Integration also uses a dash when performing partial receipts, an MO Number with a dash will prevent it from correctly identifying the “parent” MO.

(B)

Sequence

If multiple receipts for an MO are going to be recorded, SEQUENCE1 should increment by 1 for each receipt. If only one receipt is created per MO, SEQUENCE1 may be zero or one.

If 1-Step Receiving is being performed, MO Number and Sequence may be blank.

(C)

Item Number

The Item Number produced. The Item Number must be an existing Dynamics GP Item Number, which has at minimum, a MFG BOM Header and Primary Routing. The Item Number must be Active.

30-character, upper-case string.

Not required if posting a receipt for an existing MO.

(D)

Quantity

The quantity of the Item Number produced. This will be the End Quantity for the MO. As is standard functionality within Dynamics GP, the Base UOM will be used when processing MO’s.

The quantity must be compatible with the Item’s Quantity Decimals in GP. For example, if the item has zero quantity decimals, entering a Receipt Quantity of 1.25 will result in an error.

(E)

SerLotNum

For non-serial/lot tracked items, leave this field blank.

20-character, upper-case string.

If the MO Receipt produces one Lot Number or Serial Number, populate this field.

For multiple lot numbers, create a separate MO Receipt record for each Lot Number received.

(F)

LotAttrib1