Invalid Subledger (XLA) Packages In Release 12.1.3

In this Document

APPLIES TO:

Oracle Cost Management - Version 12.1.3 and later

Oracle Purchasing - Version 12.1.3 and later

Oracle Subledger Accounting - Version 12.1.2 and later

Information in this document applies to any platform.

GOAL

User currently having the following Invalid Packages, the purpose of this document is to explain how the Package Names are generated and How can this situation be resolved.

Object Type	Status	Owner
XLA_00707_AAD_S_000018_PKG	INVALID	APPS
XLA_00707_AAD_S_000019_PKG	INVALID	APPS
XLA_00201_AAD_S_000005_BC_PKG	INVALID	APPS
XLA_00707_AAD_S_000005_PKG	INVALID	APPS
XLA_00201_AAD_S_000004_BC_PKG	INVALID	APPS
XLA_00707_AAD_S_000003_PKG	INVALID	APPS
XLA_00707_AAD_S_000002_PKG	INVALID	APPS

These Packages are Invalid and customer is unable to compile them manually. How can we resolve this situation?

SOLUTION

1.- Information about These Packages

These packages are functional Subledgers Packages created using some concurrent programs and dependent on the EBS Setup.

  Application Accounting Definitions (AAD) Validation concurrent program will recompile what is really needed for Create Accounting - Cost Management and the name of the package is dynamically created like this:

         XLA_<PROD ID>_AAD_S_000###_PKG

Where:

         <PROD ID> = Is the Product ID in E-business Suite, for example 707 is Cost Management, 200 is Payables, 201 is Purchasing, etc.

In order to find the corresponding product, customer can run $AD_TOP/sql/adutconf.sql and in the output adutconf.lst customer will be able to find the Product Name.

         <S_000###> = Is a sequence.

In order to validate these packages, there are functional steps to be completed like for example in document:

Doc
ID 1508902.1 XLA Invalid Objects In The Database After The upgrade to R12, Can this be Ignored?

For example, based upon the following invalids:

         XLA_00707_AAD_S_000006_PKG = Costing package

         XLA_00200_AAD_S_000012_PKG = Payables package

Run the "Application Accounting Definition Validation Report" and check the output to see if the packages used by the installed applications are compiled. If the output of the "Application Accounting Definition Validation Report" indicates that all the packages
are valid, then it is safe to ignore the invalid AAD objects that show up with the sql:

         select object_name, status from all_objects where status = 'INVALID';

2.- Solution

1. These are compiled Subledger (XLA) Packages, there is no need to have them valid unless the customer is using the corresponding Application Accounting Definition. Customer needs to Re-Validate the AAD that
customer is using, verify after the Validation Program from the User Interface the corresponding AAD is valid.

a. Please run the following

                  XLAABACR Validate Application Accounting Definitions. For Cost Management.

                  Responsibility= Cost management-SLA

                  Paramters:

                  Ledger = null

                  Uncompile Status Only = No (will make sure that the new imported file is validated for all event types not just the invalid events)

                  Application = Cost Management

                  Application Accounting Definition = NULL/ Definition name(ex:Cost Management)

                  Application Accounting definition owner = NULL/Oracle/ User

         b. Review and upload Application Accounting Definition Validation Report, all AADs (of type Oracle and User) attached to ACTIVE Ledgers and ACTIVE Applications must be re-validated.

2. The Invalid Objects can be confirmed via script CstCheck.sql, Please review Doc
ID 378348.1 Data Collection Scripts for Cost Management. (For R11 and R12). Then scroll down to the Invalid Objects.

3. Check if Federal Costing Application Accounting Definition is being used?

4. Check if the CSTCRACC Create Accounting - Cost Management complete successfully.

5. If customer is not using "Federal Costing Application Accounting Definition" and Create Accounting - Cost Management completes successfully. Customer can ignore those invalid Package
Body Objects. Or can even drop these objects.

REFERENCES

NOTE:1529977.1 - Invalid XLA objects

NOTE:300056.1 - Debug and Validate
Invalid Objects