Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Visual Integrator Import missing fields

Status
Not open for further replies.

DougP

MIS
Dec 13, 1999
5,985
US
Creating an Import job for Work Order Transaction Material Issue Process.
When I test the job it shows success but most of the fields are missing. Of course nothing is imported because I missing something. I have seen other imports that show all the fields in testing and also don't require all the validation.
This is from the Data TAB and the Validation TAB.

Code:
00001  TRANS_NUMBER      H  ACCOUNT   NEXT                   #######
00002  TRANS_TYPE        H  STRING    ASSIGN                 3
00003  CREW_ENTRY        H  YES/NO    ASSIGN                 N
00004  WORK_ORDER        LE ZERO-FILL REPLACE       00004    Start: 1   Len: 7
00005  LINE_TYPE         L  STRING    ASSIGN                 3
00006  START_TIME        LP NUMBER    REPLACE       00006
00007  STOP_TIME         LP NUMBER    REPLACE       00009
00008  TRANS_DATE        H  DATE      REPLACE       00008    YY/MM/DD
00009  EMPL_CREW_DEPT    H  ZERO-FILL ASSIGN                 00
00010  EMPLOYEE_NUMBER   H  ACCOUNT   REPLACE       00003    #######
00011  STEP_NUMBER       LF ZERO-FILL REPLACE       00005    Start: 1   Len: 4
00012  NC_START_DATE     L3 DATE      REPLACE       00008    YY/MM/DD
00013  NC_STOP_DATE      L3 DATE      REPLACE       00008    YY/MM/DD
00014  STEP_COMPLETE     L3 YES/NO    ASSIGN                 Y
00015  LAB_QTY_COMPL     LP NUMBER    REPLACE       00014
00016  BATCH_NUMBER      H  ACCOUNT   RUN-TIME ASSN          Runtime: 00003
00017  TEMP01            H  NUMBER    CALCULATED
CALC EXP: 0
00018  WORK_CENTER       LG ACCOUNT   ASSIGN
CONDITION: {WO.TRNSENT:WORK_CENTER}=DIM(5)
00019  OP_CODE           LG ACCOUNT   ASSIGN
CONDITION: {WO.TRNSENT:OP_CODE}=DIM(5)

Code:
00001  TRANS_NUMBER                  EXPRESSION      N    WOR$(1,7)<>DIM(7)
00002  TRANS_TYPE                    STRING          N    12345678
00003  CREW_NUMBER                   FILE            Y    WO.CREW
00004  EMPLOYEE_NUMBER               FILE            Y    WO.PRODEMP
00005  CREW_ENTRY                    UPPERCASE       N    YN
00006  LOT_SER_EXIST                 UPPERCASE       Y    YN
00007  WORK_ORDER                    FILE            N    WO.MASTER
00008  COMPL_TO_CODE                 FILE            Y
00009  SUB_STEP_PREFIX               UPPERCASE       Y    0123456789ABCDEFGHIJKLMNOPQR
00010  COMPL_ITEM_NO                 FILE            N
00011  COMPL_UM                      EXPRESSION      N    WOS$(13,4)<>DIM(4)
00012  WORK_CENTER                   FILE            N    WO.WORKCTR
00013  ISSUE_ITEM_NUM                FILE            N    IM.ITEM
00014  OP_CODE                       FILE            N    WO.OPCODE
00015  ITEM_TYPE                     STRING          N    12
00016  COMPL_UM                      EXPRESSION      N    WOS$(30,4)<>DIM(4)
00017  PARENT_UOM                    EXPRESSION      N    WOS$(34,4)<>DIM(4)
00018  ISSUE_UM                      EXPRESSION      N    WOS$(37,4)<>DIM(4)
00019  COMPL_WHSE                    FILE            N    IM.WHSE
00020  COMPL_SO_NUMBER               FILE            N    SO.ORDER
00021  COMPL_WO_NUMBER               FILE            N    WO.MASTER
00022  STCK_PURCH_ACCT               FILE            Y    GL_Account
00023  STEP_COMPLETE                 UPPERCASE       Y    YN
00024  STOCK_COST_METH               STRING          N    123456
00025  ISSUE_WHSE                    FILE            N    IM.WHSE
00026  ISSUE_COST_METH               STRING          N    123456
00027  SUB_MATERIAL                  STRING          Y    YN
00028  ORIG_ITEM_NUM                 FILE            Y    IM.ITEM
00029  COMPL_WHSE                    FILE            N    IM.WHSE
00030  SOWO_PURCH_ACCT               FILE            Y    GL_Account
00031  SOWO_COST_METHD               STRING          N    123456
00032  SOWO_LOT_SER                  STRING          N
00033  VENDOR_DIV                    FILE            N    AP.DIV
00034  VENDOR_NUMBER                 FILE            N    AP.VENDOR
00035  ORIG_WHSE                     FILE            Y    IM.WHSE
00036  LINE_TYPE                     UPPERCASE       N    123456789ABCD
00037  USE_ALL_WIP                   UPPERCASE       Y    YN
00038  DIST_COMPLETE                 UPPERCASE       Y    YN
00039  START_TIME                    EXPRESSION      N    WOS[0]<24
00040  STOP_TIME                     EXPRESSION      N    WOS[1]<24
00041  TRANS_UM_CONV                 EXPRESSION      N    WOS[1]>0

DougP, MCP, A+
 
This may not be related, but all of my attemps to import to work order transactions via a csv failed. It worked when I switched to an odbc source from an access file, and I still don't know why. Maybe related?

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
The data is coming from a DOS barcode scanner which can only do ASCII files. I wish I could use Access.

DougP, MCP, A+
 
The ODBC thing may not be your problem, but to get around stuff like that, I built the access app to scan data, then launch the VI job, and shut down.

What version of mas are you using? I see you have run time assign for batch number, are you using batches in your set up in work order?

I have had tons of trouble getting vi jobs to work in a batch environment. Solution I usually come up with is to scan the set up file, see the next batch number, and use it, which creates the batch, rather than run time assign.

ChaZ

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top