Results 1 to 3 of 3

Thread: 40 char supplier invoice number

  1. #1

    40 char supplier invoice number

    We are working on a project to use a third party procurement system. This system will be sending data to JDE AP via an interface to create Vouchers. However, this third party system uses a 40 character Supplier Invoice Number, and JDE's field for Vendor Invoice Number is 25 characters.

    We are being asked to store this full 40 character value. We have even been asked to change the F0411 to increase the size of RPVINV, but will not be attempting that. Right now the idea is to store what will fit in the RPVINV, then store anything over 25 in a new field.

    Has anyone had a similar requirement. We would be very interested in how this was handled. Thanks for your assistance.

    We are on tools 9.1.4.7 apps 9.0.

  2. #2
    I think the only other fields you can put the remaining 15 characters are: VR01 (max 25) and URRF (max 15). If you split the invoice number like this, you need to make sure that the first 25 characters of the invoice# coming from the third party are unique (by supplier). Otherwise, it will not get into the system.

    Your other option is to use a tag table.
    Regards,

    Hari Sharma
    Aellius
    EnterpriseOne: Integration (.Net, Web Services) | Output Management | Monitoring

  3. #3
    Member
    Join Date
    Mar 2009
    Location
    Phoenix, AZ USA
    Posts
    58
    James, to add to Hari's suggestion: If you're comfortable enough with the coding required to implement a tag file, you could create an Invoice level tag file, essentially creating a parent table for the F0411 Supplier Ledger. The F0411 is really a denormalized table that includes both invoice and invoice line item columns. You could make this tag file joining on the Document Company, Document Type, and Document Number and add your extended invoice ID text column and whatever else that might be useful. You would probably need to create a corresponding Z file for this as well. Update the tag file right after the regular Z upload process successfully completes.
    Regards,
    Kim Schmidt

    - E1 9.1.4 ,TR 9.2.2 , iSeries, DB2
    - formerly Xe, 8.0, SQL Server, Oracle

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.