Oracle EBS SLA Detailed

Source: Internet
Author: User

http://zhangzhongjie.iteye.com/blog/1977931

SLA overview

SLA: Sub-Ledger (Subledger Accounting), which is strongly publicized in R12, we generally think that the general Ledger is a summary of journal, but in the actual operation we will find that for Sub system journal, It is not simple to summarize in a single logic, such as the AP incoming to GL request, although there are a wealth of options to summarize, but for whether to summarize detail Journal, the financial staff's thinking angle is different from us, and can not be such a simple summary, For different invoice, you may expect to get a journal look that is not quite the same. Therefore, the new module of SLA is needed to deal with the Journal of these special properties. In fact, this module is not R12 unique, under 11i, we can see some form, DB object is XLA beginning, in fact, is Subledger Accounting.

SLA settings

Introduction to SLA common tables

The most common technical aspect of the SLA is the journal source traceability, which differs significantly from GL to SLA and 11i in the retroactive process, and is performed through the Gl_import_references table, which is je_batch_id,je_header_id,je_line _num is associated with GL, the table field gl_sl_link_id is associated with the row table (Xla_ae_lines) in the SLA, and several important tables in the SLA are as follows:

Xla_events:

The Xla_events table record all information related to a specific event. This table is created as a type Xla_array_event_type.

Xla_transaction_entities:

The table xla_transaction_entities contains information about Sub-ledger document or transactions.

Xla_ae_headers:

The Xla_ae_headers table stores subledger Journal entries. There is a one-to-many relationship between accounting events and journal entry headers.

Xla_ae_lines:

The Xla_ae_lines table stores the Subledger Journal entry LINES. There is a one-to-many relationship between Subledger Journal entry headers and Subledger Journal entry lines.

Xla_distribution_links:

The Xla_distribution_links table stores the link between transactions and Subledger Journal entry lines.

Association settings between SLAs and sub-modules

The gl_import_references.gl_sl_link_id field mentioned above is associated with the xla_ae_lines.gl_sl_link_id field in which the fields associated with the submodule are Xla_transaction_ In entities, the table has the following forms of fields:

Source Table Association Fields

Source_id_int_num

Source_id_char_num

(these two fields are used to associate with the source module, which is set in each sub-module)

Path:

Setup->accounting setup->subledger Accounting setup->accounting Methods builder->events->event Model

(Setup, ledger account settings, sub-ledger accounting settings, accounting method Builder, event model)

(Note: The path of each submodule is slightly different, roughly as above)

The following is an example of AR module shown below:

The entity code[entities code for this interface corresponds to the Entity_code field in the Xla_transaction_entities table, and each source indicates which module generated the sub-ledger. Click on the identifiers[sign] to enter the following interface: The entity table column[in this interface field] is the sub-module related source table field, Identifier column[labeled column] is the SLA xla_transaction_ The Entities table column, the SLA and the sub-modules of the connection is through the interface settings to complete.

Security Control Fields

Security_id_int_num

Security_id_char_num

These two fields are used for security validation, data masking, xla_transaction_entities is a table with VPD validation, and the policy functions used by each module are set by the following interface:

Path: setup->accounting setup->subledger Accounting setup->subledger Application

(Set up ledger account settings, sub-ledger accounting settings, sub-ledger application products)

(Note: The path of each submodule is slightly different, roughly as above)

Er diagram between SLA and each sub-module

1. SLA and Ap_invoice

2. SLA and Ap_payment

3. SLA and Ar_transactions

4. SLA and Ar_receipts

5. SLA and Ar_adjustment

6. SLA and Fa_transactions

7. SLA and Fa_depreciation

8. SLA and Pa_revenue

9. SLA and Pa_expenditures

SLA and Po_receive

One. SLA and Inv_transactions

SLA and Wip_transactions

Oracle EBS SLA Detailed

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.