5.11.1 Features and Limitations of the Load Procedure

The LEDGER_STAT load utility is the only supported method for loading your ledger data into the LEDGER_STAT table. The LEDGER_STAT load utility offers the following features:

• You can load ledger data for one month or for a range of months.
• You can also load ledger data based on calendar as-of-dates.
• A month can be undone individually, using the Ledger Load Undo process. You can do this even though the month to be undone is included in a multiple-month load.
• You can update columns in existing LEDGER_STAT rows using either the additive or replacement functionality.
• You can bypass the upsert logic and insert all the rows from the load table using the INSERT_ONLY mode. This functionality can be used either for first-time loads or to reload for all months with each load.

Limitations

The following are the limitations.

• Load Table Rows Must Be Unique
• A restriction imposed by the use of bulk SQL (as opposed to row-by-row) processing is that all the rows in the load table(s) must be unique. This means that there is one row in the load table for one row in LEDGER_STAT. A unique index is created on each load table to enforce this uniqueness and provide acceptable performance.
• Defining Financial Elements in AMHM
• Occasionally, your load table may contain dimension member values for one or more dimensions that are not defined in AMHM. The LEDGER_STAT load procedure loads these rows anyway, except for the rows containing undefined or incompletely defined FINANCIAL_ELEM_ID values.
• Any new values for FINANCIAL_ELEM_ID must first be defined in AMHM before running the load. Specifically, the load procedure needs the AGGREGATE_ METHOD value for each FINANCIAL_ELEM_ID value so that the YTD columns in LEDGER_STAT can be computed using the appropriate method.