Command Import

There is not ONE way to import Command Data - each situation is unique.

What you need to know before importing Command's Data

• There is NO data integrity.

• Expect sub tables, prices etc. to have records that do have matching main tables. (e.g. prices for customers that don't exist).

MS SQL hasn't had the "TRIM" statement for long, so most often you must select as: LTRIM(RTRIM((PRJP.PROJ_CODE)) JOB_PO_LOC, But in some cases, such as Oracle you only have trim and must select as: TRIM(PRJP.PROJ_CODE) JOB_PO_LOC,

• All fields must be trimmed - especially key fields. Expect both left and right padding on Customer and product codes.
• Field IDs are longer - especially Tax Authorities, sales people and classes.

• Keep a list of mappings when setting up the class type fields to use in case statements...

Here are some samples used in the past...
:Examples by Table
:Command Import: Hedger Work Notes
:Command Import: Rain MO Work Notes



Command Tables:

*ACCT: GL  Accounts
*ARTB: Aging
*CCON: Contact Connection
*COMP: Company
*CPRD: Customer Prices
*CTCT: Contact
*CUST: Customer Prices
*EMPL: Employee - Sales and Drivers
*ICAT: Item (Product) 
*ICST: Component Structure
*ILOC: Product by Location (Similar to Plant)
*IMST: Products
*IPRC: Prices - by Level (Group)
*LOCN: Locations (Similar to Plant)
*PLNT: Plant
*PRCC: Price Group
*PRJP: Project Prices
*PROJ: Project
*SANL: Customer Class
*TAXC: Tax (Similar to Keystone Tax Auth)
*TAXJ: Tax Structure
*TAXL: Tax Locality (not 1 to 1 with Keystone)
*TRMS: Terms
*TRUC: Trucks
*UOMS: Unit of Meausure
*USGE: Useage