Creating CSV files
Multiple import interfaces use the Generic Table Import Interface. Each interface requires a specific CSV file. You must create each CSV file according to the CSV file’s field specifications.
Skill Import
The CSV file for the Skill Import Interface includes these field-column specifications:
Note: Fields with the asterisk symbol (*) are required.
Col. | Field Name | Type | Size/Format | Description |
---|---|---|---|---|
1 | STSKL_NAME* | VARCHAR | 40 | Skill name |
2 | STSKL_DESC | VARCHAR | 100 | Skill description |
3 | STSKLTYP_NAME* | VARCHAR | 40 | Skill type |
4 | STSKL_FLAG1-5 | VARCHAR | 1 | Skill flag fields, 1 through 5 |
5 | STSKL_UDF1-5 | VARCHAR | 40 | Skill UDF fields, 1 through 5 |
Note: The STSKLTYP_NAME (foreign key to the ST_SKILL table) gets
translated into an appropriate STSKLTYP_ID that the ST_SKILL table is expecting
as part of the import.
This text is an example of a CSV file for Skill Import:
Cashier, Store Cashier, Skill (skill name, skill description, skill type)
SO Budget Pay Cost Import
The CSV file for the SO Budget Pay Cost Import Interface includes this field-column specifications:
Note: Fields with the asterisk
symbol (*) are required.
Col. | Field Name | Type | Size/Format | Description |
---|---|---|---|---|
1 | SKDGRP_ID* | Number | 22 | Location ID of the location for which the budget is set |
2 | BDGPAY_DATE* | Date | 7 yyyyMMdd |
Date of the budget |
3 | BDGPAY_AMOUNT* | Number | 12 | Amount of the budget |
This text is an example of a CSV file for SO Budget Pay Cost Import:
1234, 06/22/2008, 1000.00 (skdgrp_id, bdgpay_date, bdgpay_amount)