R12 Is there a Way to Minimize the Data Stored in XLA_AE_LINES for Project's Expenditure Items.
(Doc ID 2111747.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Project Costing - Version 12.2.3 and later
Information in this document applies to any platform.
The Subledger Accounting (SLA) option 'JLT Merge Matching Lines' is set to 'ALL' (see 'R12: FAQ on Transfer to GL in R12 (Doc ID 876190.1)' number 4), but this option only merges lines where the CCID is the same within one expenditure item. Is there an SLA merge option to merge lines across expenditure items?
Scenario: A million expenditures item per month are interfaced into projects. The expenditures go to GL in detail. Based upon auto accounting rules, each expenditure is generating 6+ DISTINCT lines in XLA_DISTRIBUTION_LINKS resulting in up to 12 million rows in XLA_DISTRIBUTION_LINKS, XLA_AE_LINES, GL_IMPORT_REFERENCES, and GL_JE_LINES. GL_JE_LINES can be summarized to greatly reduce the volume to less than 30 thousand rows per month, but it would be desirable to summarize GL_IMPORT_REFERENCES and XLA_AE_LINES to preserve disk space as well. Research indicates summarizing the records in these tables are handled by 'Merge matching lines', but this option does not help in this case as there is still an entity created in XLA for each expenditure and thus a header for each expenditure in XLA_AE_HEADERS. Is there a way to further merge this information?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|