MOGenV2 Table Map

MOGenV2 Table Map

The integration table (W7158MOGen2) is located in the Company Database.   Optional columns do not accept NULLs, so they need to be populated with a default value (empty string for strings, ‘19000101’ for dates, and 0 for all numeric or Boolean fields). Where the Notes have a list of “valid values” this applies only when providing information in that field—if it is not used it can be left as 0 (zero).

Col Name Updateable Notes
1 MONum NO MO Number is required

When creating new MOs if the MO Number is provided it must not exist in GP or it will be interpreted as an Update. Either generate your own unique MO Number, or use a unique number starting with a question mark, such as “?000011”. The question mark indicates to MOGenV2 that it should generate a new, unique MO Number. The MO Number will be assigned the next MO Number using the MO Doc Type setting on the MO Generator window (it uses either the GP Manufacturing “next MO number” or it uses WilloWare’s MO Doc Types in MFG PowerPack).

MO Number will be truncated at 30-characters and converted to upper case.
2 SEQNUMBR NO SEQNUMBR is required but may be zero.

Since an MO Number may be submitted multiple times to create the MO and then perform various updates, the SEQNUMBR should increment by one each time the MO is submitted.
3 ITEMNMBR NO Item Number is required when creating MOs.

The Item Number must exist in GP.

Item Number will be truncated at 30-characters and converted to upper case.
4 StartQty YES If provided, the value must be compatible with the Item Quantity Decimals setting of the Item Number.

If you submit a Start Qty change you should also set the RebuildPicklist and RescheduleMO flags.
5 EndQty YES End Qty is required when creating MOs.

If provided, the value must be compatible with the Item Quantity Decimals setting of the Item Number.

If you submit an End Qty change you should also set the RebuildPicklist and RescheduleMO flags.
6 STRTDATE YES Start Date is required when creating MOs using Forward Infinite scheduling.

If Start Date and End Date are provided, Start Date must be on or before Due Date.

If you submit a Start Date change you should also set the RebuildPicklist and RescheduleMO flags.
7 ENDDATE YES End Date is required when creating MOs using Backward Infinite scheduling.

If Start Date and End Date are provided, Start Date must be on or before Due Date.

If you submit an End Date change you should also set the RebuildPicklist and RescheduleMO flags.

End Date is called “Due Date” on the MO Entry window.
8 DrawFrom YES Site where raw materials are consumed from. If provided, it must exist as a Location Code in Dynamics GP.

If you submit a Draw From change you should also set the RebuildPicklist and RescheduleMO flags.

Draw From will be truncated at 10 characters and converted to upper case.
9 PostTo YES Site where the Finished Good is received into. If provided, it must exist as a Location Code in Dynamics GP and be valid for the finished good Item Number.

If you submit a Post To change you should also set the RebuildPicklist and RescheduleMO flags.

Draw From will be truncated at 10 characters and converted to upper case.
10 SchedPref YES Scheduling Preference can be used to drive the setting of the Schedule Method, Draw From and Post To sites. If provided it must exist in the Schedule Preference master in Dynamics GP. Submitting a SchedPref change will update SchedMtd, DrawFrom and PostTo on the MO. If any, or all, of these values are different than what is currently on the MO, you should also set the RebuildPicklist and RescheduleMO flags.

You should create a Default Scheduling Preference that has Draw From and Post To sites. This will ensure MOGen V2 can create new MOs using default setup information.
11 SchedMethod YES Valid Scheduling Method values are:

  1. Forward Infinite
  2. Backward Infinite

If you submit a SchedMtd change you should also set the RebuildPicklist and RescheduleMO flags.
12 RoutingName YES Routing Name must exist in the Routing Entry window for the finished good Item Number.

Routing Name will be truncated at 30 characters and converted to upper case.

If you submit a Routing Name change you should also set the RebuildPicklist and RescheduleMO flags.
13 BOMCat YES BOM Category and BOM Name must be used together. See BOM Name for details.

Valid BOM Categories are:

  1. MFG BOM
  2. ENG BOM
  3. ARCH BOM
  4. CONFIG BOM

BOM Cat is called “BOM Type” on the Bill of Materials Entry window but is the BOMCAT_I field in the MFG Tables.
14 BOMName YES Required if BOM Type is 3 or 4.

If you submit a BOMCat/BOMName change you should also set the RebuildPicklist and RescheduleMO flags.
15 DSCRIPTN YES Description will be truncated at 30 characters. Submitting a Description change will replace the existing MO Description.
16 MOStatus YES Valid MO Status values are:

  1. Quote
  2. Open
  3. Released
  4. Hold
  5. Canceled
  6. Complete
  7. Partially Received

New MOs can be created as Quote, Open or Released. The default MO Status is Open.

If you submit an MOStatus change you should also set the RebuildPicklist and RescheduleMO flags. If Manufacturing setup specifies that inventory should be allocated when MO Status is changed to Released, running RescheduleMO and RebuildPicklist will trigger creation of the Allocation transaction.

NOTE: there are a large number of rules regarding allowed changes of MO Status. Please read the MOGen V2-Updates section.
17 MOPriority YES Valid values are:

  1. High
  2. Medium
  3. Low

The default MO Priority is Medium.
18 SOPNUMBE NO SOPNumber, SOPType, Line Item Seq and Component Seq are required to create a MOP-SOP Link. The combination of fields must link to a valid SOP Line (SOP10200) that has a Backordered Quantity (for Order or Invoice) or the document is a Quote or Backorder.

SOP Number will be truncated at 20 characters and converted to upper case.

To create a MOP-SOP Link the MO must have available quantity to link, and you cannot link a quantity greater than the MO Quantity. MOGenV2 cannot break or change a link once it is created, but you can do so through the GP user interface.

See MOGenV2 – MOP_SOP Link for more information.
19 SOPTYPE NO See SOP Number.

Valid Values are:

  1. Quote
  2. Order
  3. Invoice
  4. Return
  5. Backorder
20 LNITMSEQ NO See SOP Number
21 CMPNTSEQ NO See SOP Number
22 UpdateExisting NO Valid values

0-False

1-True

See MOGenV2 – Updates for more information
23 RebuildPicklist NO Valid values

0-False

1-True

See MOGenV2 – Rebuild Picklist for more information
24 RescheduleMO NO Valid values

0-False

1-True

See MOGenV2 – Reschedule MO for more information
25 CreateChildMO NO Valid values

0-False

1-True

See MOGenV2 – Create Child MO for more information
26 Status NO Set to 0.

During processing, MOGenV2 will set the following values:

0 – Ready to process

1 – Has Errors

2 – Processed OK

99 – Processing

100 – Created MO

101 – Rescheduled

102 – Picklist Rebuilt
27 DEX_ROW_ID NO Auto-incrementing row number. Do NOT include this column in the INSERT statement adding records to this table.
28 TXTFIELD YES Up to 32000 characters of text can be provided in the Text Field. This will be APPENDED to the MO Note. When performing multiple updates over time, it can be useful to provide a short description of each update in the TextField. Each update will be appended to the existing note to create a log of changes on the MO.