Table Map – Header
The integration table (W7158ImportHdr) is located in the Company Database. Optional columns do not accept NULLs, so they need to be populated with a default value.
Col | Name | Required | Notes |
1 | MONum | YES | MONum is the Key Field in this table so it must always be provided. See MO Numbering below for more details. |
2 | ITEMNMBR | YES | |
3 | QUANTITY | YES | |
4 | DUEDATE | YES | The date should be (but does not need to be) equal to, or after, the User Date. This field allows importing both DATE and TIME when used with Forward Infinite Scheduling. The MO Scheduler and Create MOs utilities can use “Start Time” if included in this field. |
5 | SchedPref | NO | A Scheduling Preference can be entered on the MOGen window. If present, it will be used when SchedPref is not provided in the import. MOGen will use the Default Scheduling Preference from MFG Setup if no other Scheduling Preference is provided. Default to empty string. |
6 | RoutingName | NO | If not provided, the Item’s Primary Routing will be used. Default to empty string. |
7 | BOMType | NO | If not provided the Item’s MFG BOM will be used. Default to zero. |
8 | BOMName | NO | If BOMType = 3 (ARCH BOM) or 4 (CONFIG BOM), a BOMName must be provided. Default to zero. |
9 | DSCRIPTN | NO | An MO Description can be provided on the MOGen window. If no Description is provided in the import, the MO Description from the MOGen window will be used. |
10 | NOTEINDX | NO | For internal use. Always set to zero. |
11 | Status | NO | 0 = New. Always set to zero
1 = Error 2 = Done 9999 = Being processed |
NOTE: The GP Manufacturing Bill of Materials window field labels do not match the SQL table columns for BOM Type and BOM Catetory. They are reversed. BOM Type on the window is BOMCAT_I in the table, and BOM Category on the window is BOMTYPE_I in the table.
W7158ImportHdr.BOMType corresponds to the User Interface BOM Type (i.e. MFG BOM, Config BOM, etc).
MO Numbering: MONum is a required field. Each row much have a unique MONum. The value provided in MONum will be used as the Manufacture Order Number in GP, so it must also be a unique value in the Manufacture Order Master (WO010032). The MONum cannot already exist in WO010032.
If the imported MONum begins with “?”, when MOGen creates an MO it will generate the next MO Number for you based on the settings on the MOGen window. So, it will create a Manufacture Order Number using either the default next number from Manufacturing, or WilloWare’s MO Document Types.
As long as the MONum begins with a “?”, MOGen will create the next MO Number for you.
If you are registered for MO Document Types in WilloWare’s MFG PowerPack, you can use MO Document Types with MOGen. The MO Document Types will appear in the MO Type drop-down list. If you do not have MO Document Type, the “Default” option will use Manufacturing’s next MO Number.
To have MOGen create an MO Number for you, the import table needs to have the MONum field populated with something, such a simple row number:
select ‘?’+ltrim(str(max(DEX_ROW_ID)+1)) FROM W7158ImportHdr (nolock)