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!

Work order transaction import

Status
Not open for further replies.

nettom

Technical User
Oct 16, 2006
2
US
Hi All,

I'm trying to import workorder material transactions into a batch. All seems to work fine except the material costs which, I think should be calculated by the system are all 0.00 when I look in the batch after importing. Any idea what I am doing wrong? Valuation for inventory items is set to Standard.





CONFIGURATION INFORMATION
-------------------------------------------------------------------------------------------------------------
FILE NAME: WO.TRNSENT W/O TRANSACTION ENTRY
IMPORT FILE: c:\m200cs\ASF_IMPORT\WOTAMAT.DBF
FILE TYPE: DBASE

INSERT ALL REQUIRED FIELDS DURING SETUP: Y
HEADER INFORMATION INCLUDED IN DETAIL LINES: N
PASSWORD: NO

DATA ITEMS
-------------------------------------------------------------------------------------------------------------
ITEM ITEM NAME FG TYPE OPERATION COLUMN IMPORT MASK SUB-STRING
-------------------------------------------------------------------------------------------------------------
00001 TRANS_NUMBER H ACCOUNT REPLACE 00001 ####### No
00002 BATCH_NUMBER H ACCOUNT ASSIGN 00019 No
00003 TRANS_TYPE H STRING ASSIGN 2 No
00004 WORK_ORDER LE ZERO-FILL REPLACE 00002 Start: 1 Len: 7 No
00005 WORK_CENTER LG ACCOUNT ASSIGN FABM No
00006 ISSUE_ITEM_NUM L2 STRING REPLACE 00003 Start: 1 Len: 15 No
00007 OP_CODE LG ACCOUNT ASSIGN 0001 No
00008 ITEM_TYPE LK STRING ASSIGN 1 No
00009 COMPL_UM LK STRING FILE ASSIGN IM.ITEM:STANDARD_UM No
00010 PARENT_UOM LK STRING FILE ASSIGN IM.ITEM:STANDARD_UM No
00011 ISSUE_UM L2 STRING REPLACE 00004 Start: 1 Len: 4 No
00012 COMPL_WHSE L8 ACCOUNT ASSIGN 000 No
00013 STOCK_COST_METH L8 STRING ASSIGN 1 No
00014 ISSUE_WHSE L2 ACCOUNT ASSIGN 000 No
00015 ISSUE_COST_METH L2 STRING ASSIGN 1 No
00016 COMPL_WHSE LA ZERO-FILL ASSIGN 000 No
00017 SOWO_COST_METHD LA STRING ASSIGN 1 No
00018 LINE_TYPE L STRING ASSIGN 2 No
00019 ISSUE_QTY L2 NUMBER REPLACE 00006 No
00020 CREW_ENTRY H YES/NO ASSIGN N No
00021 TRANS_DATE H DATE RUN-TIME ASSN Runtime: 03/23/07 No
00022 STEP_NUMBER LF ZERO-FILL ASSIGN 0000 No
00023 DIST_COMPLETE L2 YES/NO ASSIGN Y No
00024 UNIT_COST LJ NUMBER FILE ASSIGN IM.ITEM:STANDARD_COST No
00025 SUB_MATERIAL L2 YES/NO ASSIGN N No
00026 TRANS_UM_CONV LJ NUMBER REPLACE 00005 No

RECORD SELECTION
-------------------------------------------------------------------------------------------------------------
ITEM TYPE DESCRIPTION COLUMN START LENGTH RELATION VALUE
-------------------------------------------------------------------------------------------------------------
00001 2 Material Issue 00005 00001 00001 = 1
00002 H Header Record 00001 00001 00001 = 47

VALIDATION RECORDS
-------------------------------------------------------------------------------------------------------------
ITEM FIELD METHOD SKIP FILE/STRING/EXPRESSION
-------------------------------------------------------------------------------------------------------------
00001 TRANS_TYPE STRING N 12345678
00002 CREW_NUMBER FILE Y WO.CREW
00003 EMPLOYEE_NUMBER FILE Y WO.PRODEMP
00004 CREW_ENTRY UPPERCASE N YN
00005 LOT_SER_EXIST UPPERCASE Y YN
00006 WORK_ORDER FILE N WO.MASTER
00007 COMPL_TO_CODE STRING N 1234
00008 SUB_STEP_PREFIX UPPERCASE Y 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ
00009 COMPL_UM_SCRAP EXPRESSION N WOS$(13,4)<>DIM(4)
00010 WORK_CENTER FILE N WO.WORKCTR
00011 ISSUE_ITEM_NUM FILE N IM.ITEM
00012 OP_CODE FILE N WO.OPCODE
00013 ITEM_TYPE STRING N 12
00014 COMPL_UM EXPRESSION N WOS$(30,4)<>DIM(4)
00015 PARENT_UOM EXPRESSION N WOS$(34,4)<>DIM(4)
00016 ISSUE_UM EXPRESSION N WOS$(37,4)<>DIM(4)
 
I was not able to make it do this either. I had my source document application scan IM1 for the standard cost and added it to my CSV.

ChaZ

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
Have you tried posting? Note that in the TRSG for that file it has this entry. Issue Unit Cost (Calc @ Pre-Update). This means that when you get ready to update the program calculates the cost. I would try posting in a test company and see what happens.
 
Hi Louie,

Thanks for the replies. Am working on importing journal transactions right now, will go back to material issue transaction project after this is done. Will keep you posted on progress.

Cheers

 
It is also entirely possible that with manual entry there is programming in the background that calculates the unit cost. VI imports directly into the files which means that any background programming will not run and the unit cost will not be calculated. The only way you will know which theory is correct is to post in a test company.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top