Financial Services Accounting Hub Seed Data

Financial Services Accounting Hub Seed Data Overview

The Financial Services Accounting Hub provides the following types of seed data:

• Subledger application setups

  For these setups, FNDLOAD technology imports and exports the data between the database tables and the ldt data file directly.

  See: Financial Services Accounting Hub Setups

• Post-Accounting programs

  Subledger applications, such as Oracle Payables, support programs that transfer transaction data between subledgers based on the accounting generated by the transaction date. Users define Post-Accounting programs to distinguish journal lines for processing based on the accounting class associated with the journal entry line.

  See: Post-Accounting Programs, Oracle Subledger Accounting Implementation Guide

• Application accounting definitions and journal entry setups

  The Financial Services Accounting Hub provides the Application Accounting Definitions Loader (AAD Loader) to transfer setups between the database and the ldt file.

  See: Application Accounting Definitions (AAD) Loader Overview

Subledger Application Setups

The subledger application setups are the data created by the subledger applications to enable subledger accounting functionality. These setups establish the framework for building application accounting definitions. The setups include the following objects:

• Subledger applications registered with the Financial Services Accounting Hub

• Event model

• Process categories

• Accounting event class options

• Sources

• Source assignments

• Accounting attribute assignments

• Custom sources

Specifications

FNDLOAD exports and imports the subledger accounting setups between the database and ldt file. Use the xlamseed.lct control file for this purpose.

Export

To export the subledger application setups from a database to an ldt data file, use the following command:

FNDLOAD <username>/<password>[@connect] 0 Y DOWNLOAD xlaemseed.lct <datafile> XLA_SUBLEDGERS APPLICATION_ID=<application id>

Parameter	Description
Application ID	Application internal identifier

Import

To import the subledger application setups from an ldt data file to the database, use the following command:

FNDLOAD <username>/<password>[@connect] 0 Y UPLOAD xlaemseed.lct <datafile>

FNDLOAD inserts and updates the subledger application setups in the database; however, no existing data is deleted from the database.

See: Subledger Application Clean-up Script

Subledger Application Setups Examples

Export Example

For Oracle Receivables to export the subledger application setups from the database to the ldt data file ARXLASD.LDT, run the following:

FNDLOAD scott/tiger 0 Y DOWNLOAD xlaemseed.lct ARXLASD.ldt XLA_SUBLEDGERS APPLICATION_ID=222

Import Example

For Receivables to import the subledger application setups from the ldt data file ARXLASD.LDT to the database, run the following:

FNDLOAD scott/tiger 0 Y UPLOAD xlaemseed.lct ARXLASD.ldt

Subledger Application Setups Clean-up Script

The following script deletes the subledger application setups from the database. Once the data is deleted it is not recoverable unless the data was exported to an ldt data file.

Note: It is not necessary to run this script before running the import process. Run this script only if data must be removed from the database.

XLA_AAD_LOADER_UTIL_PVT.purge_subledger_seed Parameters

Parameter	Description	Data Type	Type
P_API_VERSION	API version. The value should be 1.0	NUMBER	IN
X_RETURN_STATUS	API return status. Possible values are: FND_API.G_RET_STATUS_SUCCESS - completed successfully FND_API.G_RET_STS_ERROR - completed unsuccessfully FND_API.G_RET_STS_UNEXP_ERROR - completed with unexpected error	VARCHAR2(1)	OUT
P_APPLICATIONS_ID	Internal identifier application	INTEGER	IN

Example

DECLARE

x_return_status VARCHAR2(1) ;

BEGIN

XLA_AAD_LOADER_UTIL_PVT.purge_subledger_seed
(p_api_version        => 1.0
,x_return_status      => x_return_status
,p_application_id     => <application id>) ;

END;