© 2009 Oracle Corporation – Proprietary and Confidential

1
 AR TO SLA DATA FLOW
Upcoming Receivables Community Live
Day, Date, 2004
Wednesday, Webcasts:
time p.m.
February 17,ET
2009
February 24, 2009: How to Use Receipts Application
11:30 EST Programming Interfaces (APIs) to Create and Apply
Teleconference Access: Receipts
North America: xxxx
Teleconference Access:
International:
North America:xxxx
Password: Advisor
+1-877-664-9143 March 3, 2009: Using Trading Community Architecture
(TCA) Application Programming Interfaces (APIs) for
Customer Data Creation
International:
+1-706-634 - 8961
Conference ID: 82198765 Do you have any requests for future Receivables
Advisor Webcast Events? Please email your
For upcoming Oracle Advisor suggestions to ARNEWS_US@oracle.com, subject:
Webcasts, see Note Topics of Interest.
398884.1, Oracle Advisor
Webcast Schedule.

© 2009 Oracle Corporation – Proprietary and Confidential

2
 Agenda
• Presentation – approximately 45 minutes
• Q&A Session – approximately 15 minutes
• Please hold all questions to the end of the session.
• To ask a question, move your cursor to the top of the screen and select the
‘bubble’ icon next to the moderator’s name.

• A dialog box will open. Enter your question and select “Send.”

• During the Q&A session your question will be read and an answer will
follow.

© 2009 Oracle Corporation – Proprietary and Confidential

3
 ATTENTION – AUDIO INFORMATION

If you encounter any audio issues, please call

InterCall (Audio Conferencing) and mute your
phone.

North America: +1-877-664-9143

International: +1-706-634 - 8961
Conference ID: 82198765

We would like to encourage attendees with sufficient

Internet bandwidth to listen through VoiceStreaming.

Thank you.

© 2009 Oracle Corporation – Proprietary and Confidential

4
 Safe Harbor Statement

The following is intended to outline our general

product direction. It is intended for information
purposes only, and may not be incorporated into
any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decision. The
development, release, and timing of any features
or functionality described for Oracle’s products
remains at the sole discretion of Oracle.

© 2009 Oracle Corporation – Proprietary and Confidential

5
 <Insert Picture Here>

AR to SLA Data Flow

José Manuel Martínez-Conde Abril
Senior Principal Support Engineer
 Program Agenda

• Enter Transaction in AR <Insert Picture Here>

• Complete Transaction
• Create Accounting in Draft Mode
• Create Accounting in Final Mode
• Transfer Journal Entries to GL
• Journal Import

© 2009 Oracle Corporation – Proprietary and Confidential

7
 <Insert Picture Here>

Enter Transaction

© 2009 Oracle Corporation – Proprietary and Confidential

8
 Enter Transaction
• A new event is created in xla_events with:
event_status_code = ‘I’
process_status_code = ‘U’

• The xla_transaction_entities table is populated

• The event_id field is populated in the distributions table

SELECT *
FROM XLA_EVENTS xe
WHERE xe.application_id = 222
AND xe.entity_id IN ( SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id );

© 2009 Oracle Corporation – Proprietary and Confidential

9
 Enter Transaction

© 2009 Oracle Corporation – Proprietary and Confidential

10
 Enter Transaction

© 2009 Oracle Corporation – Proprietary and Confidential

11
 <Insert Picture Here>

Complete Transaction

© 2009 Oracle Corporation – Proprietary and Confidential

12
 Complete Transaction

• Xla_events.event_status_code changes from ‘I’ to ‘U’

• Ra_customer_trx.complete_flag is set to ‘Y’

© 2009 Oracle Corporation – Proprietary and Confidential

13
 Complete Transaction

© 2009 Oracle Corporation – Proprietary and Confidential

14
 <Insert Picture Here>

Create Accounting in
Draft Mode

© 2009 Oracle Corporation – Proprietary and Confidential

15
 Create Draft Accounting
• xla_events.process_status_code is set to ‘D’

• Journal is created in xla_ae_headers and

xla_ae_lines

• xla_ae_headers. gl_transfer_status_code = ‘N’

• xla_ae_headers. gl_transfer_date is null

• xla_ae_headers. accounting_entry_status_code = ‘D’

• xla_distribution_links is populated

© 2009 Oracle Corporation – Proprietary and Confidential

16
 Create Draft Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

17
 Create Draft Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

18
 Create Draft Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

19
 Create Draft Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

20
 <Insert Picture Here>

Create Accounting in
Final Mode

© 2009 Oracle Corporation – Proprietary and Confidential

21
 Create Accounting in Final Mode
• xla_events.event_status_code and
process_status_code are set to ‘P’

• xla_ae_headers.ae_header_id changes

• xla_ae_headers & xla_ae_lines.

accounting_entry_status_code is set to ‘F’

• xla_ae_lines.gl_sl_link_id is set

• xla_ae_lines.control_balance_flag is set

© 2009 Oracle Corporation – Proprietary and Confidential

22
 Create Accounting in Final Mode
• XLABABUP module: ‘Subledger Accounting Balances
Update’ is launched

• xla_control_balances is updated at this stage

• xla_distribution_links is linked to the new

ae_header_id

• Transaction is marked as posted in AR

© 2009 Oracle Corporation – Proprietary and Confidential

23
 Create Final Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

24
 Create Final Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

25
 Create Final Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

26
 Create Final Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

27
 Create Final Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

28
 Create Final Accounting

© 2009 Oracle Corporation – Proprietary and Confidential

29
 <Insert Picture Here>

Transfer Journal Entries

to GL

© 2009 Oracle Corporation – Proprietary and Confidential

30
 Transfer Journal Entries to GL
• xla_ae_headers.gl_transfer_status_code is set to ‘Y’

• xla_ae_headers.gl_transfer_date is populated

• xla_ae_headers.group_id is assigned a value

• gl_interface is populated (or xla_glt_<group_id)

• If the SLA: Disable Journal Import Profile Option = ‘No’,

then journals go to xla_glt_<group_id>.

• Nothing happens in the xla_events, xla_ae_lines,

xla_distribution_links, or xla_control_balances tables.

© 2009 Oracle Corporation – Proprietary and Confidential

31
 Transfer Journal Entries to GL

© 2009 Oracle Corporation – Proprietary and Confidential

32
 Transfer Journal Entries to GL

© 2009 Oracle Corporation – Proprietary and Confidential

33
 Transfer Journal Entries to GL

© 2009 Oracle Corporation – Proprietary and Confidential

34
 <Insert Picture Here>

Import Journals

© 2009 Oracle Corporation – Proprietary and Confidential

35
 Journal Import

• Journals are moved from GL_interface /xla_glt

<group_id> to:

• GL_JE_batches

• GL_import_references

• GL_JE_headers

• GL_JE_lines

© 2009 Oracle Corporation – Proprietary and Confidential

36
 Journal Import

© 2009 Oracle Corporation – Proprietary and Confidential

37
 Journal Import

© 2009 Oracle Corporation – Proprietary and Confidential

38
 Journal Import

© 2009 Oracle Corporation – Proprietary and Confidential

39
 Journal Import

© 2009 Oracle Corporation – Proprietary and Confidential

40
 <Insert Picture Here>

Appendix

© 2009 Oracle Corporation – Proprietary and Confidential

41
 <Insert Picture Here>

Useful Queries Using

Customer_trx_id as Input
Parameter

© 2009 Oracle Corporation – Proprietary and Confidential

42
 USEFUL QUERIES

All results from the following queries (exceptions below)

can be found by running the Transaction Data
Diagnostic Script from the Oracle Diagnostics
Responsibility.

Information from the xla_transaction_entities and

xla_control_balances is not available via the
Transaction Data Diagnostic.

© 2009 Oracle Corporation – Proprietary and Confidential

43
 XLA_TRANSACTION_ENTITIES

SELECT *
FROM XLA.XLA_TRANSACTION_ENTITIES
WHERE application_id = 222
AND entity_code = 'TRANSACTIONS'
AND source_id_int_1 = &customer_trx_id );

© 2009 Oracle Corporation – Proprietary and Confidential

44
 XLA_EVENTS

SELECT *
FROM XLA_EVENTS xe
WHERE xe.application_id = 222
AND xe.entity_id IN
( SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id );

© 2009 Oracle Corporation – Proprietary and Confidential

45
 XLA_AE_HEADERS
SELECT *
FROM XLA_AE_HEADERS xah
WHERE xah.application_id = 222
AND xah.entity_id IN
(SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id);

© 2009 Oracle Corporation – Proprietary and Confidential

46
 XLA_AE_LINES
SELECT xal*
FROM XLA_AE_LINES xal, XLA_AE_HEADERS xah
WHERE xal.application_id = xah.application_id
AND xal.ae_header_id = xah.ae_header_id
AND xah.application_id = 222
AND xah.entity_id IN
(SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id);

© 2009 Oracle Corporation – Proprietary and Confidential

47
 XLA_DISTRIBUTION_LINKS
SELECT xdl.*
FROM XLA_DISTRIBUTION_LINKS xdl, XLA_AE_HEADERS xah
WHERE xdl.application_id = xah.application_id
AND xdl.ae_header_id = xah.ae_header_id
AND xah.application_id = 222
AND xah.entity_id IN
(SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id);

© 2009 Oracle Corporation – Proprietary and Confidential

48
 XLA_CONTROL_BALANCES

select *
from xla_control_balances
where code_combination_id = 12833
and application_id = 222
and ledger_id = 1
and period_name = ‘Feb-09’

© 2009 Oracle Corporation – Proprietary and Confidential

49
 GL_INTERFACE
SELECT distinct gi.*
FROM GL_INTERFACE gi, XLA_AE_LINES xal,XLA_AE_HEADERS xah
WHERE gi.gl_sl_link_id = xal.gl_sl_link_id
AND gi.gl_sl_link_table = xal.gl_sl_link_table
AND xal.application_id = xah.application_id
AND xal.ae_header_id = xah.ae_header_id
AND xah.application_id = 222
AND xah.entity_id IN
(SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id );

© 2009 Oracle Corporation – Proprietary and Confidential

50
 GL_JE_BATCHES
SELECT distinct gjb.*
FROM GL_JE_BATCHES gjb, GL_IMPORT_REFERENCES gir,
XLA_AE_LINES xal, XLA_AE_HEADERS xah
WHERE gjb.je_batch_id = gir.je_batch_id
AND gir.gl_sl_link_id = xal.gl_sl_link_id
AND gir.gl_sl_link_table = xal.gl_sl_link_table
AND xal.application_id = xah.application_id
AND xal.ae_header_id = xah.ae_header_id
AND xah.application_id = 222
AND xah.entity_id IN (SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id);

© 2009 Oracle Corporation – Proprietary and Confidential

51
 GL_IMPORT_REFERENCES
SELECT distinct gir.*
FROM GL_IMPORT_REFERENCES gir, XLA_AE_LINES xal,
XLA_AE_HEADERS xah
WHERE gir.gl_sl_link_id = xal.gl_sl_link_id
AND gir.gl_sl_link_table = xal.gl_sl_link_table
AND xal.application_id = xah.application_id
AND xal.ae_header_id = xah.ae_header_id
AND xah.application_id = 222
AND xah.entity_id IN (SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id);

© 2009 Oracle Corporation – Proprietary and Confidential

52
 GL_JE_HEADERS
SELECT distinct gjh.*
FROM GL_JE_HEADERS gjh, GL_IMPORT_REFERENCES gir,
XLA_AE_LINES xal, XLA_AE_HEADERS xah
WHERE gjh.je_header_id = gir.je_header_id
AND gir.gl_sl_link_id = xal.gl_sl_link_id
AND gir.gl_sl_link_table = xal.gl_sl_link_table
AND xal.application_id = xah.application_id
AND xal.ae_header_id = xah.ae_header_id
AND xah.application_id = 222
AND xah.entity_id IN (SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id);

© 2009 Oracle Corporation – Proprietary and Confidential

53
 GL_JE_LINES
SELECT distinct gjl.*
FROM GL_JE_LINES gjl, GL_IMPORT_REFERENCES gir,
XLA_AE_LINES xal, XLA_AE_HEADERS xah
WHERE gjl.je_header_id = gir.je_header_id
AND gjl.je_line_num = gir.je_line_num
AND gir.gl_sl_link_id = xal.gl_sl_link_id
AND gir.gl_sl_link_table = xal.gl_sl_link_table
AND xal.application_id = xah.application_id
AND xal.ae_header_id = xah.ae_header_id
AND xah.application_id = 222
AND xah.entity_id IN (SELECT xte.entity_id
FROM XLA.XLA_TRANSACTION_ENTITIES xte
WHERE xte.application_id = 222
AND xte.entity_code = 'TRANSACTIONS'
AND xte.source_id_int_1 = &customer_trx_id);

© 2009 Oracle Corporation – Proprietary and Confidential

54
 For More Information
Please refer to the eTRM at http://etrm.oracle.com/ for more details on
all Oracle tables.
The recorded version of this webcast will be available with the next 24
hours and can be downloaded from the Advisor Webcast Archive,
Note 740297.1.

Follow up questions from this morning:

1. How can we use the xla_glt_<group_id> table to debug if it is
temporary? The information in the xla_glt_<group_id> will only be
deleted once the journal import is successful, therefore, you would
only use this information to debug if the journal import failed.
2. If a summary report is selected when running Create Accounting, is
there a way to see a detailed report for the session at a later time?
You will be able to run the process in detail, but it will not affect the
transactions already processed and marked as posted in
xla_events, and ra_cust_trx_line_gl_dist_all.

© 2009 Oracle Corporation – Proprietary and Confidential

55
 Questions
• To ask a question, move your cursor to the top of the screen
and select the ‘bubble’ icon next to the moderator’s name.
• A dialog box will open. Enter your question and select
“Send.”

• Do you have any requests for future Receivables Advisor

Webcast Events? Please email your suggestions to
ARNEWS_US@oracle.com, subject: Topics of Interest.

© 2009 Oracle Corporation – Proprietary and Confidential

56
© 2009 Oracle Corporation – Proprietary and Confidential
57
 THANK YOU

© 2009 Oracle Corporation – Proprietary and Confidential

58