POVENITEM error when using the PO536 upload

Sort:
You are not authorized to post a reply.
Author
Messages
Arnold Layne
New Member
Posts: 1
New Member
    Hi everyone,

    I get the below error when I try loading a vendor contract price list via the PO536.  I've isolated the issue.  It has to do with the MFG CODE field in the P0536 upload.  When I try to populate the 4 character MFG CODE I get the below error.  When I strip off the code - the file loads just fine.  Does anyone have some advice on how I can get the MFG Code to populate the IC11, PO13, & PO25.6 via the PO536 upload.  Many thanks.


    User Name: u0y6ap00 Job Name: GORE Queue Name: POQUE
    BEGIN: Job Submitted: Tue Sep 2 12:21:47 2014

    Step 1: PO536 Started. . . . . .: Tue Sep 2 12:21:47 2014
    Token Command. . . . . .: /law/c0y6da/lawson/dev901/obj/PO536.gnt
    Executable Command . . .: /law/c0y6da/gen/bin/lacobrts lacobrts /law/c0y6da/lawson/dev901/obj/PO536.gnt dev901 u0y6ap00 GORE 1
    Process ID . . . . . . .: 1343664
    Program Messages:
    ** Creating .prt and .dtl files
    Processing PO536 (Vendor Price Agreement Load)
    **** File Attributes Set For File: IMPORT ****
    File Path Name was taken from the Work File Name
    File Options were taken from JOBSTEPWRK Record
    File PathName: /law/c0y6da/lawson/dev901/work/WLGORE.csv
    File Options:
    HasHeader = No
    XltHeader = No
    FldSep ->,<-
    DateFmt =CCYYMMDD
    DateSep ->/<-
    TimeSep ->:<-
    DecimalSep ->.<-
    ThouSep -> <-
    QuoteChar ->"<-
    FileTerm = None
    LineTerm = Hex 0D0A
    **** End of File Attributes For File: IMPORT ****
    Checkpoint Import Agreement
    Checkpoint Import Lines
    PO KEYS = MIG /0000/IC/
    PO KEYS = MIG /0000/IC/
    File DEV901/POITEMVEN.
    tsStoreDBRec error is Key change not allowed (32).

    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member
      If it helps - I've gotten "Key change is not allowed" on PO13 when I'm trying to change a value to something that doesn't match the PO25 header.
      You are not authorized to post a reply.