R12: How To View Reporting Sequences For Subl edgerJournals?Goal1.You havedefined Sequencing- reportingfor bothsubledger and GL journal entry event GL periodclose.After closing the periodin GL,the Create Reporting Sequence Number program is automatically launched and completed normally but when checking the reporting sequence number for Subledger journals and GL journal entries only the reporting sequence numbersfor GL journal entries are shownandno reporting sequences for Subledger journals are available.How to view the reporting sequence created and assigned to subledger journals?SolutionThis is the intended functionality.For subledger journals you can see the reporting sequence in SLA level not in GL.For subledgerjournals GL cant transfer the reporting sequence. Only manual journals which are created in GL will get thereporting sequence. For subledger journalsyou can see the reporting sequence in SLA level only .If however a subledger journal is reversed user will not get a reporting sequence because the reversals do not populate the xla_seq_je_headers_gt table that gets the sequenceIn order to see the reporting sequences for subledger journals in SLA: Log in with your SLA responsibility; Check your setup according to Oracle Subledger Accounting Implementation Guide Release 12 Chapter 7 Reporting Sequence- page 7-4 Reporting Sequence Process Steps and following. Navigate to Subledger Journal Entries > Lines > make your query and see the transactions retrieved. In the Transaction information area note the + Show additional information : unhide the information; at this step you can see your accounting and reporting sequences numbers.Note: In order to have the assigned reporting sequences usedyou have to: Checkthe journal entry status of Final'; draft entries are not assigned a reporting sequence; Check that the transactionsare posted in GL; Check that the GL period has been closed and the automatically launched process Create Reporting Sequence Number has completed normally; At the time you check your SLA reporting sequencesnumbersthe period in GL has not been re-opened (the program erases the sequences that are assigned to the journal entries that belong to the reopened period).

R12 What are the Differences Between Accounting Sequencing and ReportingSequencing?The accounting sequence is assigned to Subledger Accounting journal entries at the time that the journal entry is completed. The sequence is assigned in the completion date order using the GL date as the date criterion for determining the sequence to be used.The reporting sequence is assigned to both Subledger Accounting journal entries and General Ledger journal entries when the General Ledger period is closed. This sequence is used by most of the legal reports required in some countries as the main sorting criterion to display the journal entries.Reporting sequence is optional.These two sequences are not mutually exclusive and can coexist in the same journal entry.Note: for more details-Oracle Financials Implementation Guide (Part No. B16386-01) contains aseparate chapter on Accounting and Reporting Sequencing;-Oracle Subledger Accounting Implementation Guide chapter on Reporting Sequencing;

Setup:1 Go to Setup > Financials > Sequences >.Assign2.Select your General Ledger3.Select Sequence Entity : Subledger Journal Entry4.Select Sequence Event : GL Period Close': for fiscal reporting during accounting period close./Accounting': for fiscal accounting of journal entries originating in the subledgers.5 .Select Sequence Entity : GL Journal Entry6. Select Sequence Event: GL Period Close': for fiscal reporting during accounting period close./Posting : for fiscal accounting of journal entries originating in the general ledger.

Impact of SLA on Journal Import in General Ledger Setups related to JournalImport1. Journal Import can be run in Summary or Detail mode.This can be set for each application, as per therequirement. By default this is set to Summarize by GLPeriod, but can be changed as per the requirement. Thesetup can be changed from: General Ledger responsibility Financials -> Accounting Setup Manager ->Accounting Setups Query for the Ledger being used Update Accounting Options Select update for Subledger Accounting Options Update Accounting Options for the Application Here there is an option General Ledger JournalEntry Summarization, which can be set tofollowing values:i. Summarize by GL Date (Journal Import willcreate summary journals based onAcccounting Date)ii. No Summarization (Journal Import willcreate journals in Detail mode)iii. Summarize by GL Period (Journal Importwill create summary journals based onPeriod to which the Accounting Date falls)Thus the option General Ledger Journal EntrySummarization will determine if the Import for theapplication is being done in Detail or Summary mode.2. Prior to Release 12, it was needed that the Journal Importshould be run in the same language as the language,which was used to transfer data to GL_INTERFACE. Though this is not much relevant now (the transfer andjournal import are triggered together); still Journal Importcan be made independent of the language. This can beachieved by running journal import using the Source andCategory Key.Generally the columns user_je_source_name anduser_je_category_name in gl_interface, correspond to thecolumns GL_JE_SOURCES.user_je_source_name andGL_JE_CATEGORIES.user_je_category_name respectively.These values change for the different language and thusmaking journal import language-dependent. Howeverwhile defining the sources (General Ledger Responsibility: Setup -> Journal -> Source), if the option Import UsingKey is selected, then import refers toGL_JE_SOURCES.je_source_key andGL_JE_CATEGORIES.je_category_key. These being theKey values are common across languages and hencejournal import becomes language independent.3. While running Journal Import from General Ledgerresponsibility, the LOV of Ledger appears provided thereis data in the table GL_INTERFACE for the ledger and theData Access Set attached to the responsibility has eitherFull or Read/Write access to the Ledger.Journal -> Import -> RunLOV for Ledger.In case a different Interface table is being used, the LOVwill check for the data in GL_INTERFACE_CONTROLinstead of GL_INTERFACE.4. Data Access Sets do apply to Journal Import too. To beable to import data, one should have either Full orRead/Write Access to the ledger and all the BalancingSegment Values for which data is populated inGL_INTERFACE.In case one does not have access to the Ledger at all, theLOV for Ledger will not appear in Journal -> Import ->Run screen and hence he will not be able to submitJournal Import.If there are multiple balancing segments in the data inGL_INTERFACE, and the responsibility has access to a fewand not to others, then you will be able to run JournalImport but it will complete in Warning and data will notbe imported. Error shown in the Journal Import Executionreport would be:EM29 : You do not have access to this ledger and accountcombination.

Impact of SLA on Journal Import in GeneralLedgerThe way Journal Import is triggered from the subledgers hasundergone a major change in Release 12. Execution of JournalImport from the Subledgers depends on the setting of the Profileoption SLA: Disable Journal Import.The profile option SLA: Disable Journal Import can be set onlyat the Site level and hence will be applicable to all thesubledgers/modules. The default value for this profile option isNo and this should NEVER be changed, unless suggested bySupport or Development. Setting this profile option to Yesbreaks the link between SLA and GL, so GL no longer knowswhich journals came from SLA. This may cause problems withinquiry and drilldown on these journals in the future. This optionis set to Yes only in cases where GL is on a separate instancethan SLA.

SLA: Disable Journal Import set to No.

Value No for this profile option indicates that Journal Importwill ALWAYS accompany the transfer of data from Subledger.Another main implication of this value is that, on failure ofJournal Import, the data will be rolled back to SLA tables andhence we will not have any data in GL_INTERFACE. Note thatfor this setting of the profile option, General Ledger will havevery little part to play, as any error in Journal Import will takethe data back to SLA tables and GL_INTERFACE will not haveany data in it. This will also mean that Journal -> Import -> Runand Journal -> Import -> Correct forms will not be used for theSubledger data as GL_INTERFACE will never have any data forthem. However, these forms will continue to be used for thedata, which is being transferred from some other sources such asLegacy or some user defined sources for which data is populatedin GL_INTERFACE table, and then Import is run in GeneralLedger.

Whenever data is transferred from the subledgers, the requestdoing so, will also trigger the Journal Import program. The nameof the program to transfer data to GL, will change as per thesubledger; we have explained the behavior below with respectto the Payables module. In Payables, there are three options fortransferring data to GL:

1. When Online Accounting is done for Payables transactions,there are three options available:a. Draftb. Finalc. Final PostFor any value of the profile option, Draft and Final optionswork in the same way i.e draft mode creates the SLA journalsin Draft mode which can be modified afterwards; Final modecreates SLA journals and the transaction can not be modifiedafter this. The SLA journal can then be transferred to GeneralLedger.Transfer of the journals created in Final Mode is doneusing Transfer to General Ledger concurrent request.However Final Post works differently for the two values ofthe Profile option. If profile option is set to No, then FinalPost creates the SLA journals in Final mode, transfers thedata to GL_INTERFACE, runs Journal Import and triggers theGeneral Ledger Posting program too.

2. When Accounting is done from Submit request form i.e byrunning the request Create Accounting, it gives thefollowing options:a. Mode: Draft or Finalb. Transfer to General Ledgerc. Post in General LedgerIf Transfer to General Ledger is selected as Yes, then thedata is transferred to GL_INTERFACE and immediately afterthat Journal Import request is also triggered. In case of anyerrors, the data is rolled back to SLA tables.

3. If Accounting is done in Final Mode and we are transferringthe data by running the request Transfer Journal Entries toGL request, it gives the option of Post in General Ledgerwhich refers to the Posting program in General Ledger.Thus there is no option for Journal Import as Journal Import willalways be triggered by the Transfer program.From points 1, 2 and 3, it is evident that Journal Import hasbecome an inbuilt part of the Transfer Journal Entries program ofSLA in Release 12. Thus when the profile option SLA: DisableJournal Import is set to No, GL_INTERFACE table will neverhave data for Subledgers.SLA: Disable Journal Import set to YesThis setting for the profile option indicates that the transferring ofdata from Subledgers will take place in the same manner as ithappens in Release 11i. However changing the value of theProfile option to Yes is strictly not suppported and shouldNEVER be used as this may lead to issues related to the linkingbetween SLA and GL journals. For this value of profile, theTransfer to GL programs of the subledgers, populates the data inGL_INTERFACE and then Import needs to be run manually fromGL. In case the subledger is providing the option of running thejournal import too along with the transfer to GL, then the requestwill fire the Journal Import also. However in case of a JournalImport error, the data will remain in GL_INTERFACE table.

Impact of SLA on Drilldown in GeneralLedgerDrilldownfunctionality enables users to navigate from a Journalin General Ledger to the Subledger Journal Entry in SLA andfrom there to the transaction which has resulted into that journal.To enable Journal drilldown from General Ledger, the ImportJournal References option should be enabled for the Source.This can be checked under General Ledger Responsibility atSetup -> Journal -> Sources -> Define.Only when this is enabled, the reference data is populated bySLA engine.The Drilldown in Release 12 is different from the prior releasesof the Application. R12 drilldown is Web based and not in theForms.

1- Navigation to perform Drilldown is the same as in Release 11i.Journals -> Enter -> Review JournalSelect the journal line and click on Lines Drilldown.2- Drilldown can also be performed from:Tools -> DrilldownAs mentioned above, Drilldown opens the Web Page instead ofForm.The SLA Page for Drilldown shows the following: GL Journal Line information Subledger Journal Line informationThere are two Options available on this SLA page: View Transaction View Journal EntryView Transaction will take us to the Subledger Transactionform.E.g for the current journal line, since the Source wasPayables, it opens Invoice Workbench.View Journal Entry will take to the Subledger Journal EntrydetailsView Journal Entry has three parts to it.1. Transaction Information2. Additional Information (this is hidden by default)3. Line DetailsApart from this there are some extra details shown at the top ofthe page, which is the header level information for the SubledgerTransaction.Some of the important fields in header part of the SubledgerTransaction Journal are: Ledger Name Journal Entry Status Balance Type GL DateThis is the Additional Information section of SubledgerTransaction Entry page.This section shows the details of Event General Ledger Sequences Application Accounting DefinitionNote that Event and Application Accounting Definition areimportant from SLA side. However, from GL perspective therelevant details are Period, Transfer to GL Date and Transfer toGL status.This is the last section, Lines of the Subledger Journal Entrypage.The important details in this section are: Code Combination Currency Entered Debits and Credits Accounted Debits and CreditsSelect the link Show for any of the lines to view additionaldetails for the transaction line

Profile Options related to Drilldown:

SLA: Enable Subledger Transaction Security in GLThis profile option controls whether the drilldown to SLA willenforce the transaction security of the application owning theTransaction. For example, if one drills down to Payables, he willonly be able to see Journals for transactions belonging tooperating units to which he has access (based on your MO:Security Profile.) Thus drilldown can be restricted to theOperating Units to which the responsibility has access. In casethe GL responsibility does not have access to a particularOperating Unit, the Drilldown will not show any data.

XLA_EVENTS:SELECT * FROM xla_events xe WHERE xe.application_id = 222AND xe.entity_id IN ( SELECT xte.entity_id FROM xla.xla_transaction_entities xteWHERE xte.application_id = 222 AND xte.entity_code = TRANSACTIONSAND xte.source_id_int_1 = 10066)XLA_AE_HEADERS:SELECT * FROM xla_ae_headers xahWHERE xah.application_id = 222 AND xah.entity_id IN ( SELECT xte.entity_idFROM xla.xla_transaction_entities xte WHERE xte.application_id = 222AND xte.entity_code = TRANSACTIONS AND xte.source_id_int_1 = 10066)XLA_AE_LINES:SELECT xal.* FROM xla_ae_lines xal, xla_ae_headers xahWHERE xal.application_id = xah.application_id AND xal.ae_header_id = xah.ae_header_idAND xah.application_id = 222 AND xah.entity_id IN (SELECT xte.entity_id FROM xla.xla_transaction_entities xteWHERE xte.application_id = 222 AND xte.entity_code = TRANSACTIONSAND xte.source_id_int_1 = 10066)XLA_DISTRIBUTION_LINES:SELECT xdl.* FROM xla_distribution_links xdl, xla_ae_headers xahWHERE xdl.application_id = xah.application_id AND xdl.ae_header_id = xah.ae_header_idAND xah.application_id = 222 AND xah.entity_id IN ( SELECT xte.entity_idFROM xla.xla_transaction_entities xte WHERE xte.application_id = 222AND xte.entity_code = TRANSACTIONS AND xte.source_id_int_1 = 10066);

9