Product Interface: Pipe Delimited Method
- Samantha Menzynski
Use the Product Interface to load inventory information using data from external applications. Information you load using this interface adds to the data already stored in PENTA.
Data files you load must have Request Types assigned to the D Interface Type.
PENTA runs several high-level tests for integrity on the file and records. When you process the records, be sure to use the file name as the Batch Number. This is different from other PENTA Interface Types. In the Inventory Interface files, there is no Batch Number field. The file name itself becomes the Batch Number during processing.
After interfacing records, you can review and edit them in the Product Information window.
Product Restrictions
Do not use tildes (~) to denote null (empty) fields in this interface’s records. Instead, enter nothing (no space) between pipe delimiters.
Available Records
Product Distribution
You can have PENTA distribute the batch immediately after file transfer. This ensures that no one modifies the batch. To do this, set System Option 125 (“Mark Batch for Distribution”) to Y.
PENTA does not distribute a batch if System Option 125 is N.
The Interface Request Product Master table contains master data supplied by the external application that applies to inventory products as a whole. You enter this data in the Product Information window. PENTA uses the Product Id to ensure that each record is unique.
|
Field | Entry | Format | Description |
|---|---|---|---|---|
1 | Activity Code | Req | C! 1 | Required for all activity. Possible values are:
|
2 | Record Type | Req | C! 5 | The value should be PROD. |
3 | Product ID | Req | X | PENTA verifies this field is a unique entry in the PRODUCT table for new entries. |
4 | Description | Req | C 30 | Description of the product. |
5 | Barcode | Opt | C 128 | Physical barcode on the product. |
6 | Product Status | Req | C 1 | Status of the product. Possible values are A (active) or I (inactive). |
7 | Product Type | Req | C 4 | PENTA verifies this field exists in the PROD_TYPE table. |
8 | Product Class | Req | C 6 | PENTA verifies this field exists in the PROD_CLASS table. |
9 | Stocked Unit of Measure | Req | C 5 | PENTA verifies this field exists in the UNIT_OF_MEASURE table. |
10 | Pricing Factor | Opt | C 2 | PENTA verifies this field exists in the PRICING_FACTOR table. |
11 | Purchase Unit of Measure | Req | C 5 | PENTA verifies this field exists in the UNIT_OF_MEASURE table. |
12 | PUM | Req | N 4 | Antecedent for the Ratio PUM to UM. |
13 | UM | Req | N 4 | Consequent for the Ratio PUM to UM. |
14 | Taxable Product | Req | C! 1 | Indicates whether this is a taxable product. Possible values are Y (yes) or N (no). |
15 | Expense Product | Req | C! 1 | Indicates whether this is an expense product. Possible values are Y (yes) or N (no). |
16 | Warranty Period | Opt | N 3 | If you include Warranty Period, the Warranty Period Unit of Measure is required. |
17 | D/M/Y | Opt | C! 1 | Possible values are D (day(s)), M (month(s)), and Y (year(s)). If you include Warranty Period, Warranty Period Unit of Measure is required. |
18 | Scrap Factor Percent | Opt | 8,5 | The flat percentage PENTA applies to the product’s unit cost after you transfer the Product from inventory. |
19 | Cost Type Code | Opt | C! 4 | PENTA verifies this field exists in the COST_TYPE table, and is an active Cost Type. If you include Costcode, Cost Type Code is required. |
20 | Costcode | Opt | X | PENTA verifies this field exists in the COSTCODE table, and is an active Costcode. If you include Cost Type Code, Costcode is required. |
21 | Refrigerant | Req | C! 1 | Indicates whether this is a refrigerant product. Possible values are Y (yes) and N (no). |
Optional PROD Record Fields (place after Field 21)
Field | Format | Description |
DESCR_100 | C 100 | Extended description of the product. You can enter a value of up to 100 characters in this field. |
LEAD_TIME | I 3 | Lead time (days) for the product. Possible values are 0-999. |
Product Standard Costs Fields
The Interface Request Product Standard Cost table contains product cost data supplied by the external application that applies to inventory products by organizational unit. You enter this data in the Product Standard Costs window. PENTA uses the combination of Product ID and Balance Sheet Organizational Unit ID to ensure that each record is unique.
# | Field | Entry | Format | Description |
|---|---|---|---|---|
1 | Activity Code | Req | C! 1 | Required for all activity. Possible values are:
|
2 | Record Type | Req | C! 5 | The value should be PRODSTDCOST. |
3 | Product ID | Req | X | PENTA verifies this field is a unique entry in the PRODUCT table for new entries. |
4 | Balance Sheet OU ID | Req | X | PENTA verifies this field exists in the ORGANIZATION_UNIT table, and is an active Balance Sheet OU ID. |
5 | Effective Date | Req | D | Effective Date. |
6 | Sequence | Opt | C 10 | Sort Sequence Number. |
7 | Standard Cost | Req | F 12.3 | The Unit Cost. |