18. Importer
Produmex Manufacturing is a legacy product and Boyum IT Solutions no longer sells new installations for it.
Produmex Manufacturing offers importers for the following:
- Manufacturing Operation
- Bill of Materials
- Production Order
The importer processes a CSV file and adds a valid element/document to the company database.
18.1. Using the importer
18.1.1. Create import file
Create the CSV file. For more information about the file structure please see:
- Bills of Materials: Bills of Materials import file
- Manufacturing Operations: Manufacturing Operations import file
- Production orders: Production order import file
18.1.2. Open importer
Open the importer via the following path: Tools > Produmex Manufacturing > Produmex Data Management >
- To import Bills of Materials, click on: Import Bills of Materials
- To import Manufacturing Operations, click on: Import Manufacturing Operations
- To import Production orders, click on: Import Production order
18.1.3. Specify parameters
On the parameters form click on the ’…’ button and browse the CSV file.
Specify the importing parameters.
Delimiter
Specify the separator character that was used on the CSV file on the Delimiter field. The default delimiter is ’,’.
Comment Token
A Comment Token can be defined. Every row that begins with the comment token will be skipped. By default the comment token is ’#’.
Please note: If you leave it empty, each line in the file will be processed.
Override existing
When importing a Bill of Materials or a Manufacturing operation, an additional ’Override existing’ checkbox will be displayed. This parameter determines what the importer does when the Bill of Materials/Manufacturing Operation already exists.
- If it is checked, the existing document is deleted and replaced with the new one from CSV file. If there are many BoMs/Manufacturing Operations for the same product in the file, the last valid one will be loaded.
- If it is not checked, the existing documents remain intact, an error message is generated for the one in CSV file. If there are many BoMs/Manufacturing Operations for the same product in the file, the first valid one will be loaded.
Please note: Whenever a production order is imported, a new production order is added. The importer will not override existing production orders.
18.1.4. Validate
Before staring the import, validate the CSV file.
Check the ‘Only validate’ box. If this box is checked, the document will only be validated but will not be imported to the company database. Click on the ‘Import’ button to start the validation.
For more information about the validation steps please see: Validation
The results of the validation will be displayed on the result form.
On the header the path to the import file and the importing parameters are displayed.
Elements/documents included in the selected import file will be divided into three tabs:
- Documents/elements proven to be valid are listed on the ‘Successfully loaded’ tab.
- Documents/elements proven to be invalid due format errors are listed on the ‘Format error’ tab.
- Documents/elements proven to be invalid due content errors are listed on the ‘Content error’ tab.
The number of the grid elements is displayed next to the tab title.
When importing Bill of Materials or Production orders, the Product Number is the item code of the main product. When importing Manufacturing operations, the Product Number is the item code of the validated manufacturing operation.
The Line Reference is the number of the source line in the CSV file.
On the Message field further information are displayed about the entry.
18.1.5. Import
After every line of the import file is proven to be valid, start the import. It is recommended to only start the import after every line of the import file is proven to be valid. Make sure that the ‘Only validation’ checkbox is not checked.
Set the import parameters as described above and click on the ‘Import’ button to start the import. Please note: The system will always validate the file before the import, regardless of whether it was validated before or not.
The results of the import will be displayed on the results form.
- When importing a Bill of Materials, a link to the imported Bill of Material is added to the Product Number field.
- When importing a Manufacturing Operation, a link to the imported Manufacturing Operation is added to the Product Number field.
- When importing a Production Order, a link to the Bill of Material of the main product is added on the Product Number field. An additional Document Number field is displayed. The document number and a link to the generated production order is displayed on the field. All generated production orders will be in ‘Planned’ status, and their type will be ‘Special’. The production order will always be created based on the imported data, regardless whether its main product has a production BoM or not.
18.2. File structure
Element names/codes are case sensitive.
18.2.1. Manufacturing operation
Download an example CSV file from here: Manufacturing operation importer file example
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Item Series | Numeric | If left empty, the value will be 'Manual'. | |
| 2 | Operation Code | ✔ | Text | The code of the operation. Please note: If it is the code of an existing operation, the following can happen: If the ‘override existing’ checkbox is checked, the operation will be overridden. If the override existing checkbox is not checked, a content error will be generated and the manufacturing operation will not be imported. |
| 3 | Operation Name | Text | ||
| 4 | Is Outsourceable | Y/N | N - No Y - Yes If left empty, the value will be 'N'. |
|
| 5 | Item Group | Number | The item group code. You can find the Item Group codes in the OITB table. If left empty, the system will use the item group set on the 'Item Group for Operation' field of the Master Data tab of the Produmex Manufacturing settings. | |
| 6 | Before Time | Number | Importer converts it to a base time using the Operation Time UoM from the row. | |
| 7 | Safety Time | Number | ||
| 8 | Setup Time | Number | ||
| 9 | Job Time | ✔ | Number | |
| 10 | Teardown Time | Number | ||
| 11 | After Time | Number | ||
| 12 | Time Base | Number | ||
| 13 | Operation Break | Integer between 0 and 5 | 0 - 3 - Allowed 1 - Denied 2 - Allowed WC 4 - Allowed NBP 5 - Allowed WCNBP If left empty, the value will be '3'. |
|
| 14 | Operation Time UoM | Text | The value must be a valid time code defined on the TimeUnits (BXPTIMEUNITS) user table.* | |
| 15 | Is parallel operation | Y/N | N - No Y - Yes If left empty, the value will be 'N'. |
|
| 16 | Max Parallel Operations | Integer | ||
| 17 | Allocation window | Number | The importer converts it to a base time using Allocation Window UoM from actual row. | |
| 18 | Allocation window UoM | Text | The value must be a valid time code defined on the TimeUnits (BXPTIMEUNITS) user table.* | |
| 19 | Min. Job Quantity | Number | ||
| 20 | Feature | ✔ | Text | Must be an existing work center feature. |
| 21 | Is Mandatory Work Center | N/Y | N - No Y - Yes If left empty, the value will be 'N'. |
|
| 22 | Preferred Work Center | Text | Must be an existing work center feature. If the ‘Is Mandatory Work Center’ value is Y, this field must be filled. |
* In order to use Produmex Manufacturing integrated with Produmex WMS. the UoM must exist in the Units of Measure - Setup (OUOM) standard SBO table as well.
If there is a value beyond 21th column, the row is invalid. A format error message is generated, and the manufacturing operation is not processed.
18.2.2. Bills of Materials
The first character of a row defines the row type and drives the processing of the row. If a comment token was defined, all rows beginning with the given character are skipped.
The following row types are supported:
- H - Header row
- I - Item row
- S - Supplier row
- R - Resource row
- T - Text row
Every other first character, except the comment token, generates an error message.
Download an example CSV file from here: Bills of Materials importer file example
Header row type
It represents the header of the Bill of Materials.
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Row type | ✔ | H | |
| 2 | Product No. | ✔ | Text | Item code of the product/sub-assembly. Must be a valid item code. |
| 3 | Planned Average Production Size | Number | ||
| 4 | Quantity | Number | If left empty, the value will be 1. | |
| 5 | Warehouse (To) | Text | Must be a valid code of a warehouse. | |
| 6 | Price List | Integer | Must be a valid code of a price list. | |
| 7 | Distribution Rule 1 | Text | The Distribution rule for Dimension 1. Must be a valid identifier of a distribution rule. | |
| 8 | Distribution Rule 2 | Text | The Distribution rule for Dimension 2. Must be a valid identifier of a distribution rule. | |
| 9 | Distribution Rule 3 | Text | The Distribution rule for Dimension 3. Must be a valid identifier of a distribution rule. | |
| 10 | Distribution Rule 4 | Text | The Distribution rule for Dimension 4. Must be a valid identifier of a distribution rule. | |
| 11 | Distribution Rule 5 | Text | The Distribution rule for Dimension 5. Must be a valid identifier of a distribution rule. | |
| 12 | Project | Text | Must be a valid identifier of a project. | |
| 13 | Calculation Base Quantity | Number | ||
| 14 | Custom Code | Text | ||
| 15 | Is Auto Roll | N/Y | N - No Y - Yes If left empty, the value will be 'N'. |
|
| 16 | Milestone type | Integer between 0 and 4 | 0 - 1 - Milestone 2 - Depends on Begin 3 - Depends on Every 4 - Depends on End If left empty, the value will be '0'. |
|
| 17 | Operation Granularity | Number | ||
| 18 | Recipe Version | Number | No validation | |
| 19 | Rejected Warehouse | Text | Must be a valid code of a warehouse. | |
| 20 | Timestamp | Text | No validation |
If there is a value beyond 20th column, the row is invalid. A format error message is generated, and BoM is not processed.
Item row type
It represents a row on the grid of the Bill of Materials. The BoM row type is defined by the row sub type (second column) in the import file.
The first 15 column is the same for every-sub type. If the sub type of the row is operation, operation specific information can be added on the 16-39 columns.
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Row type | ✔ | I | |
| 2 | Row sub-type | ✔ | Integer between 1 and 8 | 1 - Material 2 - Operation 3 - Unfinished Material 4 - Supplier Material 5 - By-Product 6 - Unfinished Product 7 - Cost 8 - Phantom |
| 3 | Item Code | ✔ | Text | Define an item with the given sub-type. Must be a valid item code. The row sub-type is not validated. |
| 4 | Quantity | ✔ | Number | This field should be empty for operations. The importer automatically calculates the quantity and updates this field with the calculated quantity. |
| 5 | Warehouse | Text | Must be a valid code of a warehouse. | |
| 6 | Issue Method | M/B | M - Manual B - Backflush If left empty, the value will be 'B'. |
|
| 7 | Milestone type | Integer between 0 and 4 | 0 - 1 - Milestone 2 - Depends on Begin 3 - Depends on Every 4 - Depends on End If left empty, the value will be '0'. |
|
| 8 | Price List | Integer | Must be a valid code of a price list. | |
| 9 | Comments | Text | ||
| 10 | Distribution Rule 1 | Text | The Distribution rule for Dimension 1. Must be a valid identifier of a distribution rule. | |
| 11 | Distribution Rule 2 | Text | The Distribution rule for Dimension 2. Must be a valid identifier of a distribution rule. | |
| 12 | Distribution Rule 3 | Text | The Distribution rule for Dimension 3. Must be a valid identifier of a distribution rule. | |
| 13 | Distribution Rule 4 | Text | The Distribution rule for Dimension 4. Must be a valid identifier of a distribution rule. | |
| 14 | Distribution Rule 5 | Text | The Distribution rule for Dimension 5. Must be a valid identifier of a distribution rule. | |
| 15 | WIP Account | Text | The internal reference of a WIP Account. The internal reference code can be found in the OACT.ACCTCODE field. | |
| 16 | Consignation Size | Number | ||
| 17 | Drawing Position Number | Integer | ||
| 18 | Profit Center | Text | ||
| 19 | Rejected Warehouse | Text | Must be a valid code of a warehouse. |
If the sub-type of the row is not operation, and there is a value beyond 19th column, the row is invalid. A format error message is generated, and BoM is not processed.
Operation row sub-type
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 20 | Before Time | Number | The importer converts it to a base time using the Operation Time UoM from actual row of CSV or from Manufacturing Operation. | |
| 21 | Safety Time | Number | ||
| 22 | Setup Time | Number | ||
| 23 | Job Time | Number | ||
| 24 | Teardown Time | Number | ||
| 25 | After Time | Number | ||
| 26 | Time Base | Number | ||
| 27 | Operation Break | Integer between 0 and 5 | 0 - 3 - Allowed 1 - Denied 2 - Allowed WC 4 - Allowed NBP 5 - Allowed WCNBP If left empty, the system will copy the value from the manufacturing operation. |
|
| 28 | Operation Time UoM | Text | The value must be a valid time code defined on the TimeUnits (BXPTIMEUNITS) user table.* | |
| 29 | Is parallel operation | N/Y | N - No Y - Yes If left empty, the system will copy the value from the manufacturing operation. |
|
| 30 | Is overlapping operation | N/Y | N - No Y - Yes If left empty, the system will copy the value from the manufacturing operation. |
|
| 31 | Max Parallel Operations | Integer | ||
| 32 | Overlapping Quantity | Number | ||
| 33 | Allocation Window | Number | The importer converts it to a base time using Allocation Window UoM from actual row of CSV or from Manufacturing Operation. | |
| 34 | Allocation Window UoM | Text | The value must be a valid time code defined on the TimeUnits (BXPTIMEUNITS) user table.* | |
| 35 | Min Job Quantity | Number | ||
| 36 | Feature | Text | Must be an existing work center feature. | |
| 37 | Is Mandatory Work Center | N/Y | N - No Y - Yes If left empty, the system will copy the value from the manufacturing operation. |
|
| 38 | Preferred Work Center | Text | Must be an existing Work Center which supports selected Work Center Feature (from CSV or from Manufacturing Operation) | |
| 39 | Outsourced | N/Y | N - No Y - Yes If left empty, the system will copy the value from the manufacturing operation. |
|
| 40 | In House Quantity | Number | ||
| 41 | Outsourcing Lead Time | Number | If the Outsourced flag is set to Y, the importer converts it to a base time using Outsourcing UoM from actual row of CSV or from Manufacturing Operation. If the Outsourced flag is set to N, this field must be empty. |
|
| 42 | Outsourcing UoM | Number | If the Outsourced flag is set to Y, the value must be a valid time code defined on the TimeUnits (BXPTIMEUNITS) user table.* If the Outsourced flag is set to N, this field must be empty. |
|
| 43 | Items per Outsourcing Unit | Number | If the Outsourced flag is set to N, this field must be empty. |
* In order to use Produmex Manufacturing integrated with Produmex WMS. the UoM must exist in the Units of Measure - Setup (OUOM) standard SBO table as well.
If the row is an operation row, and there is a value beyond 43th column, the row is invalid. A format error message is generated, and BoM is not processed.
Supplier row type
It represents information about outsourcing partners. It can follow only an operation row or another supplier row, otherwise a format error message is generated and BoM is not processed.
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Row type | ✔ | S | |
| 2 | Supplier Code | ✔ | Text | Must be a valid supplier code. |
| 3 | Planned Quantity | ✔ | Number |
If there is a value beyond 3rd column, the row is invalid. A format error message is generated, and BoM is not processed.
Resource row type
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Row type | ✔ | R | |
| 2 | Resource Code | ✔ | Text | Must be a valid resource code. |
| 3 | Quantity | ✔ | Number | |
| 4 | Warehouse | Text | Must be a valid code of a warehouse. | |
| 5 | Issue Method | M/B | M - Manual B - Backflush If left empty, the value wiil be 'B'. |
|
| 6 | Unit price | Number | ||
| 7 | Comments | Text | ||
| 8 | Distribution Rule 1 | Text | The Distribution rule for Dimension 1. Must be a valid identifier of a distribution rule. | |
| 9 | Distribution Rule 2 | Text | The Distribution rule for Dimension 2. Must be a valid identifier of a distribution rule. | |
| 10 | Distribution Rule 3 | Text | The Distribution rule for Dimension 3. Must be a valid identifier of a distribution rule. | |
| 11 | Distribution Rule 4 | Text | The Distribution rule for Dimension 4. Must be a valid identifier of a distribution rule. | |
| 12 | Distribution Rule 5 | Text | The Distribution rule for Dimension 5. Must be a valid identifier of a distribution rule. | |
| 13 | WIP Account | Text | The internal reference of a WIP Account. The internal reference code can be found in the OACT.ACCTCODE field. |
If there is a value beyond 13th column, the row is invalid. A format error message is generated, and the BoM is not processed.
Text row type
| No. | Name | Mandatory | Possible types/values |
|---|---|---|---|
| 1 | Row type | ✔ | T |
| 2 | Text | ✔ | Text |
If there is a value beyond 2th column, the row is invalid. A format error message is generated, and the production order is not processed.
18.2.3. Production order
The first character of a row defines the row type and drives the processing of the row. If a comment token was defined, all rows beginning with the given character are skipped.
The following row types are supported:
- H - Header row
- I - Item row
- S - Supplier row
- R - Resource row
- T - Text row
Every other first character, except the comment token, generates an error message.
Download an example CSV file from here: Production order importer file example
Header row type
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Row type | ✔ | H | |
| 2 | Product No. | ✔ | Text | Item code of the product/sub-assembly. Must be a valid item code. |
| 3 | Planned quantity | If left empty, the value will be 1. | ||
| 4 | Warehouse (To) | Text | Must be a valid code of a warehouse. | |
| 5 | Series | Integer | ||
| 6 | Due Date | Date | Format: YYYYMMDD. If left empty, the due date will be the current date. | |
| 7 | Sales Order | Text | Add the DocEntry of the sales order. | |
| 8 | Customer | Text | Must be an existing customer. | |
| 9 | Distribution Rule 1 | Text | The Distribution rule for Dimension 1. Must be a valid identifier of a distribution rule. | |
| 10 | Distribution Rule 2 | Text | The Distribution rule for Dimension 2. Must be a valid identifier of a distribution rule. | |
| 11 | Distribution Rule 3 | Text | The Distribution rule for Dimension 3. Must be a valid identifier of a distribution rule. | |
| 12 | Distribution Rule 4 | Text | The Distribution rule for Dimension 4. Must be a valid identifier of a distribution rule. | |
| 13 | Distribution Rule 5 | Text | The Distribution rule for Dimension 5. Must be a valid identifier of a distribution rule. | |
| 14 | Project | Text | Must be a valid identifier of a project. | |
| 15 | Allocation Strategy | ✔ | Integer between 0 and 3 | 0 - 1 - Back from due date 2 - Forward from earliest date 3 - Forward from preferred date |
| 16 | Due Time | Date | Format: hh:mm | |
| 17 | Milestone Type | Integer between 0 and 4 | 0 - 1 - Milestone 2 - Depends On Begin 3 - Depends On Every 4 - Depends On End |
|
| 18 | Operation Granularity | Number | ||
| 19 | Rejected warehouse | ✔ | Text | Must be a valid code of a warehouse. |
| 20 | Is Auto Roll | ✔ | N/Y | N - No Y - Yes |
| 21 | Force Reallocation | ✔ | N/Y | N - No Y - Yes |
| 22 | Custom Code | Text |
If there is a value beyond 22th column, the row is invalid. A format error message is generated, and the production order is not processed.
Item row type
Belongs to the production order defined by the previous header. The Row SubType determines the interpretation of the rest of the row.
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Row type | ✔ | I | |
| 2 | Row sub-type | ✔ | Integer between 1 and 8 | 1-Material 2-Operation 3-Unfinished Material 4-Supplier Material 5-By-Product 6-Unfinshed Product 7-Cost 8-Phantom |
| 3 | Item Code | ✔ | ||
| 4 | Quantity | ✔ | Number | This value will be saved as the Base quantity. The Planned quantity will be calculated based on the Base quantity and the Quantity on the header. Only mandatory for Material rows. |
| 5 | Warehouse | Text | Must be a valid code of a warehouse. | |
| 6 | Distribution Rule 1 | Text | The Distribution rule for Dimension 1. Must be a valid identifier of a distribution rule. | |
| 7 | Distribution Rule 2 | Text | The Distribution rule for Dimension 2. Must be a valid identifier of a distribution rule. | |
| 8 | Distribution Rule 3 | Text | The Distribution rule for Dimension 3. Must be a valid identifier of a distribution rule. | |
| 9 | Distribution Rule 4 | Text | The Distribution rule for Dimension 4. Must be a valid identifier of a distribution rule. | |
| 10 | Distribution Rule 5 | Text | The Distribution rule for Dimension 5. Must be a valid identifier of a distribution rule. | |
| 11 | WIP Account | Text | The internal reference of a WIP Account. The internal reference code can be found in the OACT.ACCTCODE field. | |
| 12 | Consignation Size | Number | ||
| 13 | Drawing Position Number | Integer | ||
| 14 | Due Date | Date | Format: YYYYMMDD. If left empty, the due date will be the current date. | |
| 15 | Due Time | Date | Format: hh:mm | |
| 16 | Manual Planning | ✔ | Y/N | N - No Y - Yes |
| 17 | Issue Method | ✔ | B/M | M - Manual B - Backflush Mandatory for materials only. If left empty for other row sub-types, the value wiil be 'B'. |
| 18 | Milestone Type | Integer between 0 and 4 | 0 - 1 - Milestone 2 - Depends On Begin 3 - Depends On Every 4 - Depends On End If left empty, the value will be '0'. |
|
| 19 | Profit Center | Text | ||
| 20 | Rejected Warehouse | Text | Must be a valid code of a warehouse. | |
| 21 | Comment | Text |
If the sub-type of the row is not operation, and there is a value beyond 21th column, the row is invalid. A format error message is generated, and the production order is not processed.
Operation row sub-type
If the row sub-type is operation, additional operation specific data can be imported as well.
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 22 | Before Time | Number | The importer converts it to a base time using the Operation Time UoM from actual row. | |
| 23 | Safety Time | Number | ||
| 24 | Setup Time | Number | ||
| 25 | Job Time | ✔ | Number | |
| 26 | Teardown Time | Number | ||
| 27 | After Time | Number | ||
| 28 | Time Base | Number | ||
| 29 | Operation Break | Integer between 0 and 5 | 0 - 3 - Allowed 1 - Denied 2 - Allowed WC 4 - Allowed NBP 5 - Allowed WCNBP If left empty, the value will be '3'. |
|
| 30 | Operation Time UoM | Text | The value must be a valid time code defined on the TimeUnits (BXPTIMEUNITS) user table.* | |
| 31 | Is parallel operation | N/Y | N - No Y - Yes If left empty, the value will be 'N'. |
|
| 32 | Is overlapping operation | N/Y | N - No Y - Yes If left empty, the value will be 'N'. |
|
| 33 | Max Parallel Operations | Integer | ||
| 34 | Overlapping Quantity | Number | ||
| 35 | Allocation Window | Number | The importer converts it to a base time using Allocation Window UoM from actual row. | |
| 36 | Allocation Window UoM | Text | The value must be a valid time code defined on the TimeUnits (BXPTIMEUNITS) user table.* | |
| 37 | Min Job Quantity | Number | ||
| 38 | Feature | ✔ | Text | Must be an existing work center feature. |
| 39 | Is Mandatory Work Center | N/Y | N - No Y - Yes If left empty, the system will copy the value from the manufacturing operation. |
|
| 40 | Preferred Work Center | Text | Must be an existing Work Center which supports selected Work Center Feature. | |
| 41 | Outsourced | N/Y | N - No Y - Yes If left empty, the system will copy the value from the manufacturing operation. |
|
| 42 | In House Quantity | Number | ||
| 43 | Outsourcing Lead Time | Number | If the Outsourced flag is set to Y, the importer converts it to a base time using Outsourcing UoM from actual row. If the Outsourced flag is set to N, this field must be empty. |
|
| 44 | Outsourcing UoM | Number | If the Outsourced flag is set to Y, the value must be a valid time code defined on the TimeUnits (BXPTIMEUNITS) user table.* If the Outsourced flag is set to N, this field must be empty. |
|
| 45 | Items per Outsourcing Unit | Number | If the Outsourced flag is set to N, this field must be empty. |
* In order to use Produmex Manufacturing integrated with Produmex WMS. the UoM must exist in the Units of Measure - Setup (OUOM) standard SBO table as well.
If the row is an operation row, and there is a value beyond 45th column, the row is invalid. A format error message is generated, and the production order is not processed.
Supplier row type
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Row type | ✔ | S | |
| 2 | Supplier Code | ✔ | Text | Must be a valid supplier code. |
| 3 | Planned Quantity | ✔ | Number |
If there is a value beyond 3th column, the row is invalid. A format error message is generated, and the production order is not processed.
Resource row type
Belongs to the previous operation. It can be used only after a row with Operation sub-type, otherwise a content error will be generated.
| No. | Name | Mandatory | Possible types/values | Description |
|---|---|---|---|---|
| 1 | Row type | ✔ | R | |
| 2 | Resource Code | ✔ | Text | Must be a valid resource code. |
| 3 | Quantity | ✔ | Number | |
| 4 | Warehouse | Text | Must be a valid code of a warehouse. | |
| 5 | Issue Method | M/B | M - Manual B - Backflush If left empty, the value wiil be 'B'. |
|
| 6 | Comment | Text | ||
| 7 | Distribution Rule 1 | Text | The Distribution rule for Dimension 1. Must be a valid identifier of a distribution rule. | |
| 8 | Distribution Rule 2 | Text | The Distribution rule for Dimension 2. Must be a valid identifier of a distribution rule. | |
| 9 | Distribution Rule 3 | Text | The Distribution rule for Dimension 3. Must be a valid identifier of a distribution rule. | |
| 10 | Distribution Rule 4 | Text | The Distribution rule for Dimension 4. Must be a valid identifier of a distribution rule. | |
| 11 | Distribution Rule 5 | Text | The Distribution rule for Dimension 5. Must be a valid identifier of a distribution rule. | |
| 12 | WIP Account | Text | The internal reference of a WIP Account. The internal reference code can be found in the OACT.ACCTCODE field. |
If there is a value beyond 12th column, the row is invalid. A format error message is generated, and the production order is not processed.
Text row type
| No. | Name | Mandatory | Possible types/values |
|---|---|---|---|
| 1 | Row type | ✔ | T |
| 2 | Text | ✔ | Text |
If there is a value beyond 2th column, the row is invalid. A format error message is generated, and the production order is not processed.
18.3. Validation
Before the import the system validates the import file. The validation is split into two phases.
18.3.1. Format validation
In the first phase the system checks the file for format errors.
Possible issues:
- Row type is not valid
- Row sub-type is not valid
- Mandatory field is not given
- Given value doesn’t match to the type of the field (for example alphabetical character in numeric field etc.)
- Surplus value is given
- Invalid row order (for example a header row follows another header row)
18.3.2. Content validation
In the second phase the document/element is validated with the company database in order to detect content errors.
Manufacturing Operations
Possible issues:
- Invalid value when range is defined (Operation Break)
- Code cannot be found in SAP Business One (Item Group Code, Feature, Work Center)
- Invalid UoM (Operation Times, Allocation Window)
- Mandatory value is missing:
- Mandatory Work Center is required, but Preferred Work Center is missing
Bills of Materials
Possible issues:
- Invalid value when range is defined (Issue Method, Milestone Type, Operation Break Type)
- Code cannot be found in SAP Business One (Item, Feature, Work Center, Supplier, Warehouse etc.)
- Invalid UoM (Operation Times, Allocation Window, Outsourcing)
- Rules of using Issue Method and Milestone Type are violated
- Required correspondences between rows are violated (unfinished product must precede unfinished material etc.)
- Work Center does not support the Work Center Feature
- Mandatory value is missing:
- Mandatory Work Center is required, but Preferred Work Center is missing
- Operation is marked as outsourced, but no valid supplier is given
- Operation is not marked as outsourced, but a supplier row is given
- Sum of planned quantities exceeds quantity in header
- SAP Business One validates the following: Distribution Rule, Distribution Rule Dimensions, Price List
Production Order
Possible issues:
- Invalid value when range is defined (Issue Method, Milestone Type, Operation Break Type)
- Code cannot be found in SAP Business One (Item, Feature, Work Center, Supplier, Warehouse, Sales order, etc.)
- Invalid UoM (Operation Times, Allocation Window, Outsourcing)
- Rules of using Issue Method and Milestone Type are violated
- Required correspondences between rows are violated (unfinished product must precede unfinished material etc.)
- Work Center does not support the Work Center Feature
- Mandatory value is missing:
- Mandatory Work Center is required, but Preferred Work Center is missing
- Operation is marked as outsourced, but no valid supplier is given
- Operation is not marked as outsourced, but a supplier row is given
- Sum of planned quantities exceeds quantity in header
- SAP Business One validates the following: Distribution Rule, Distribution Rule Dimensions, Price List, WIP Code, Project