PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 12/28/2018 2:33 PM by  Ragu Raghavan
IC500 - Please HELP if you can!
 11 Replies
Sort:
You are not authorized to post a reply.
Author Messages
TBonney
Private
Private
Veteran Member
(625 points)
Veteran Member
Posts:267


Send Message:

--
12/28/2018 10:03 AM

    I have reviewed the file layout document for IC500, along with any KB articles I cold find and been going back and forth on an incident on Infor Xtreme. However, I can not get the IC500 job to process an inbound file properly without errorring out.

     

    I believe it is strictly the result of the headers being improperly named because the file layout document indicates the field names to contain spaces, hyphens, mixed case fields, upper case fields, etc., which I have never seen before and do not believe to be correctly documented.

    I've also never experienced an interface job like this one where you need to include both a header line and a detail line for each record (at least I think that is what is required).

    Has anyone else experienced this confusion with this job and, if so, are you willing to share your experience and provide some guidance on how to properly format the file and process the job/file successfully? Any help would be appreciated. Thanks in advance!

    Greg Moeller
    Private
    Private
    Veteran Member
    (4094 points)
    Veteran Member
    Posts:1460


    Send Message:

    --
    12/28/2018 10:27 AM
    Perhaps a known good/working input file will help you...

    Find one attached.

    Attachments
    Greg Moeller
    Private
    Private
    Veteran Member
    (4094 points)
    Veteran Member
    Posts:1460


    Send Message:

    --
    12/28/2018 10:29 AM
    I don't think you need to include the headers.....
    Greg Moeller
    Private
    Private
    Veteran Member
    (4094 points)
    Veteran Member
    Posts:1460


    Send Message:

    --
    12/28/2018 10:56 AM
    The header is actually defined in the item number field (pos 24-29) where if item = 000000 * header record
    Unless you are using the CSV input file... I don't have experience with that.
    Greg Moeller
    Private
    Private
    Veteran Member
    (4094 points)
    Veteran Member
    Posts:1460


    Send Message:

    --
    12/28/2018 10:57 AM
    line number not item (sorry)
    TBonney
    Private
    Private
    Veteran Member
    (625 points)
    Veteran Member
    Posts:267


    Send Message:

    --
    12/28/2018 12:06 PM

    Thanks so much for the information Greg. Apparently, I should have just started with the flat file approach instead of csv to begin with. Matching your fields to the file layout makes perfect sense. However, I do have one additional question if you don't mind...

    I see that you have LOC01 as the 'Location' for the first 9 records/rows and in the line 1 header record for that grouping, there is a single 'From or To Location' of 7012E identified. Then you have LOC02 as the 'Location' for the remaining 23 records/rows and, in the line 10 header record for that grouping, there is again only a single 'From or To Location' of 7031E identified. Which of these two locations would actually have the inventory decremented from it for the quantities being detailed within the line detail, LOC01/LOC02 or 7012E/7031E?

    I am asking this because the data I am being given from our materials management team appears to indicate that there can be multiple 'From or To Locations' within a single 'Location'? Therefore, I am trying to decipher how this would look in the designated file format.

    TBonney
    Private
    Private
    Veteran Member
    (625 points)
    Veteran Member
    Posts:267


    Send Message:

    --
    12/28/2018 12:41 PM

    Greg, also, do you need to manually build the workdef file? I created a job to run using the flat file option, but the workdef shows all filler for everything after the line # & Seq #? Total file size is 1000 like the sample you provided me with, but all of the fields are not defined in the workdef. (Screen shot attached)

     

    Attachments
    Greg Moeller
    Private
    Private
    Veteran Member
    (4094 points)
    Veteran Member
    Posts:1460


    Send Message:

    --
    12/28/2018 1:20 PM
    LOC01 is our Inventory Location. I'm not an end-user of this, but I believe the 7012E/7031E are the From or To locations...
    So to answer your main question, I believe that LOC01/LOC02 would be the ones decremented as that corresponds to our storeroom.
    Greg Moeller
    Private
    Private
    Veteran Member
    (4094 points)
    Veteran Member
    Posts:1460


    Send Message:

    --
    12/28/2018 1:22 PM
    From what I remember..... the fields that are on the sample input file that I shared, NEED to be populated with either a space, a zero, or whatever they are populated with... we try not to populate anything that doesn't need it here, so I'm thinking you'd need to populate them too.
    Greg Moeller
    Private
    Private
    Veteran Member
    (4094 points)
    Veteran Member
    Posts:1460


    Send Message:

    --
    12/28/2018 1:40 PM
    CSV files tend to be tricky.. esp with Lawson. Anytime you open them up in Excel MS in their infinite wisdom strips the leading zeros (which Lawson sometimes needs), and reformats things just a bit.. And heaven forbid if you ever save it without a backup copy.
    I've struggled with using CSV files with Lawson, so go right back to the flat files.
    Greg Moeller
    Private
    Private
    Veteran Member
    (4094 points)
    Veteran Member
    Posts:1460


    Send Message:

    --
    12/28/2018 2:09 PM
    No, we did not have to manually build the workdef file. Just took defaults.
    Ragu Raghavan
    Private
    Private
    Veteran Member
    (1260 points)
    Veteran Member
    Posts:438


    Send Message:

    --
    12/28/2018 2:33 PM
    If I understand TBonney's question, what constitutes filler 256, filler 105, filler 604 shown in workdef?
    You need to look at the file IC500WS, I think, depending on the rec-type, the record layout is defined in FIX-FFMST-REC, FAX-ICACTIVITY-REC, FCT-ICTRANS-REC, or FCD-ICTRANSDTL-REC
    You are not authorized to post a reply.