TABLE AND JOINS FUSION

➢ journals interface TABLE

GL_INTERFACE inter,
GL_LEDGERS ledger,
GL_ACCESS_SETS Acc
JOINS
inter.LEDGER_ID = ledger.LEDGER_ID
ledger.IMPLICIT_ACCESS_SET_ID = acc.ACCESS_SET_ID

Parameters
(NVL(null,:P_GROUP_ID) is null OR inter.GROUP_ID IN (:P_GROUP_ID))

➢ Descriptive Flexfield TABLE (DFF) Journals_DFF_Structure_Extract_Report

fnd_vs_value_sets v1,
fnd_df_segments_b v2,
fnd_df_segments_tl v3
JOINS
v1.VALUE_SET_ID = v2.VALUE_SET_ID
v2.DESCRIPTIVE_FLEXFIELD_CODE = v3.DESCRIPTIVE_FLEXFIELD_CODE
v2.SEGMENT_CODE = v3.SEGMENT_CODE

➢ Chart of Account Structure and Its Related Objects TABLE

fnd_vs_value_sets vs,
FND_KF_SEGMENTS_VL b,
FND_KF_STRUCTURES_TL ta,
FND_KF_STRUCTURES_B tb,
FND_KF_LABELED_SEGMENTS tc,
FND_KF_SEGMENT_LABELS_TL td,
FND_KF_STR_INSTANCES_VL ts,
GL_LEDGERS gl
JOINS
ta.structure_code = tb.structure_code
tb.structure_id = tc.structure_id (+)
tc.segment_label_code = td.segment_label_code(+)
b.STRUCTURE_ID = tb.structure_id
b.segment_code = tc.segment_code(+)
b.DEFAULT_VALUE_SET_ID= vs.value_set_id
tb.structure_id = ts.structure_id
ts.STRUCTURE_INSTANCE_NUMBER = gl.chart_of_accounts_id

➢ auto post criteria TABLE

GL_AUTOMATIC_POSTING_OPTIONS auto,
GL_AUTOMATIC_POSTING_SETS set1,
GL_LEDGERS led,
GL_JE_CATEGORIES Category,
GL_JE_SOURCES Source
JOINS
auto.AUTOPOST_SET_ID = set1.AUTOPOST_SET_ID
led.LEDGER_ID = auto.LEDGER_ID
auto.JE_CATEGORY_NAME = Category.JE_CATEGORY_NAME
 TABLE AND JOINS FUSION

auto.JE_SOURCE_NAME = Source.JE_SOURCE_NAME

➢ delete journals TABLE

GL_INTERFACE inter,
GL_ACCESS_SETS Asets,
GL_LEDGERS ledger,
GL_JE_SOURCES Source
JOINS
inter.LEDGER_ID = ledger.LEDGER_ID
ledger.IMPLICIT_ACCESS_SET_ID = Asets.ACCESS_SET_ID
inter.USER_JE_SOURCE_NAME = Source.USER_JE_SOURCE_NAME

➢ INVOICE TABLE
AP_INVOICE_ALL header,
AP_INVOICE_LINE_ALL line,
AP_TERMS_TL Terms,
AP_PAYMENT_SCHEDULES_ALL Schedules
JOINS
Header. INVIOCE_ID = line.INVIOCE_ID
Header.TERMS_ID = Terms.TERMS_ID
Line. INVIOCE_ID = schedules. INVIOCE_ID

➢ Supplier/vender/ party name

POZ_SUPPLIERS supplier,
HZ_PARTIES party,
POZ_SUPPLIER_SITES_ALL_M Site
JOINS
Party.PARTY_ID=Supplier.PARTY_ID
Site.VENDOR_ID= supplier.VENDOR_ID

➢ GL code or charge Account / Business Unit Table -

GL_CODE_COMBINATIONS CODE,
HR_ALL_ORGANIZATION_UNITS ORBUSINESS,
HR OPERATING UNITS OPBUSINESS
JOINS -
CODE.CODE_COMBINATION_ID = DISTRIBUTION.CODE_COMBINATION_ID
[Link] BU_ID = ORBUSINESS.ORGANIZATION_ID
HEADER REQ_BU_ID = OPBUSINESS.ORGANIZATION_ID

Project detail what we do and work flow

• Oracle financials cloud Interface data table schema for data integration.
• Creation of a custom BI publisher report to extract or get the details which is going to use in further
integrations.
• REST/SOAP API to call the above report from middleware platform (Mulesoft) and provide the response as
XML data.

Soap Api to move data into interface table →

then we run report from SOAP Api to validate the data into interface table →
 TABLE AND JOINS FUSION

when data is validated from interface table then we schedule ESS Job to move
data from interface to main table →
After submitting an ESS Job will get a request id for the same →
after getting a request id in response payload we trigger get Ess job request id
Api to get the status for the same →
if we get previous Api response in error or warning →
then we trigger another Api to download the log file or if we get response as a
succussed then we skip this step →
After moving data from interface to main table then we schedule an Ess
job to post our journal entry →
before submitting this request we have to get the id for the same →
to get an Autopost criteria set id we have to run the auto criteria set report
through soap Api →
after getting an Autopost id we go ahead and trigger Autopost request through
soap

EXPECTED RESULTS
• The process will be triggered from Brex.
• The BI Report would capture Journal Import data and extract it in the XML format.
• Web Service will be launched from Mulesoft to run the report and extract the data.
• Call web Services using Mule Soft to insert data into Journal Import Interface table.
• Call web Services using Mule Soft to execute standard Journal Import Program.
• Call web Services using Mule Soft to check the status of ESS Job submitted for Journal Import.

Mail bursting parameters

SELECT trx_number KEY,
'XXmulti Lang' TEMPLATE,
'en-us' LOCALE,
'PDF' OUTPUT_FORMAT,
'EMAIL' DEL_CHANNEL,
'ravireddy2632@[Link]' parameter1,
'ravireddy263@[Link]' parameter2,
'testmail@[Link]' parameter3,
'Ar Invoice'|| trx_number parameter4,
'Please Find the attached Invoice.
Thanks & Regards,
XXabc Company' parameter5,
'true' parameter6,
'donotreply@[Link]' parameter7
FROM (
select
distinct b.trx_number
from ra_customer_trx_lines_all a,
 TABLE AND JOINS FUSION

ra_customer_trx_all b
where a.customer_trx_id= b.customer_trx_id
and a.customer_trx_id in (1002,1))

• KEY is the Delivery key and must match the Deliver By element. The bursting engine uses the key to link delivery criteria
to a specific section of the burst data.

TEMPLATE - is the name of the Layout to apply. Note that the value is the Layout name (for example, 'Customer Invoice'), not the
template file name (for example, [Link]

Email PARAMETER1: Email address

PARAMETER2: cc
PARAMETER3: From
PARAMETER4: Subject
PARAMETER5: Message body
PARAMETER6: Attachment value ('true' or 'false'). If your output format is PDF, you must set this parameter
to "true" to attach the PDF to the e-mail.
PARAMETER7: Reply-To
PARAMETER8: Bcc
(PARAMETER 9-10 are not used)