PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 12/27/2021 5:56 PM by  John Henley
AP03.1 data issues
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Chris Willhoite
Developer, Business Intelligence
Private
New Member
(1 points)
New Member
Posts:1


Send Message:

--
12/10/2021 6:20 PM
    Our AP team uses attributes on the vendors, and the data that displays in the AP03.1 screen does not match the data in the APVNMXVAL table. This is causing issues with integrations with other applications and reports. As a test I updated the data in AP03.1 and the database does not update. Is there another table that AP03.1 may be linked to or another reason that the data is not the same between Lawson and the database?
    Kat V
    Sr Supply Chain System Analyst
    South Broward Hospital District
    Veteran Member
    (2854 points)
    Veteran Member
    Posts:976


    Send Message:

    --
    12/27/2021 5:05 PM
    I don't have that issue - you do have to be on the APVNMXVAL table and as far as I can tell can only pull the attribute in by one Matrix Category - or you get multiple rows per vendor.

    But APVENMAST and APVNMXVAL joined on AP_OBJ_ID are where the values are for me.
    Carol S
    Senior Consultant
    Private
    Basic Member
    (28 points)
    Basic Member
    Posts:10


    Send Message:

    --
    12/27/2021 5:37 PM
    Chris is correct. You need the AP-OBJ-ID to link to APVNMXVAL. You can also get back multiple values depending on how many attributes you use on the vendor.
    You need to know both the name of the Attribute and also the range (if specified) of the attribute values you want to update.
    Attributes are created on MX10 and the values added to attributes could be limiting if they are set up that way.
    It would be easier to assist if you let us know what is missing in the APVNMXVAL table after you have done the interface.
    Carol Sanguinetti
    John Henley
    Private
    Private
    Senior Member
    (9848 points)
    Senior Member
    Posts:3300


    Send Message:

    --
    12/27/2021 5:56 PM
    Chris, don't laugh, but it just might be that you are entering into Lawson and it isn't showing up in the database because you're looking at the wrong database table... one suggestion is to double/triple check that you're actually looking at the correct database table, i.e. correct server, database name, schema, etc. It happens....
    Thanks for using the LawsonGuru.com forums!
    John
    You are not authorized to post a reply.