R12:JL: How to Store UUID on Data that Is Interfaced Via GL Interface API? (Doc ID 2079346.1)

Last updated on DECEMBER 16, 2015

Applies to:

Oracle Financials for the Americas - Version 12.0.0 and later
Oracle Payables - Version 12.0.0 and later
Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.

Goal

Where to store the UUID in GL for Mexico Electronic Reporting on data that is interfaced via the GL interface API?

Since AR and AP are using the Global Attribute 1 to store the UUID, may the user assume that the same location (Global Attribute 1)
on the gl_je_lines table could be used to store any UUID data that is passed through the GL Interface API?

What about the transactions processed outside Oracle EBS and then interfaced to the GL (Payroll and travel and expense are examples)?


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms