Running the Journal Post Engines

This section provides an overview of instrument-level posting and lists the pages used to run the journal post engines.

Note: To do instrument-level profitability reporting from the PF_Ledger, make sure that you use only 18 characters to uniquely identify each instrument ID; that is, use only 18 of the available 20 characters in FI_INSTRUMENT_ID. The reason is that when the PF_EDIT program is run prior to posting data to PF_Ledger, it checks that each of these instrument IDs is found in the PF_OBJ_TBL, which can only handle field sizes up to 18 characters.

Pages Used to Run the Journal Post Engines

Page Name	Definition Name	Navigation	Usage
FI Journal Post	RUN_FI_POST	select Financial Services Industries, then select Analysis and Processing, then select Journal Post Engines, then select FI Journal Post Click the Run Engines link. Then click the FI Journal Post link in the Journal Post Engines menu.	Post instrument data from FI_JRNL_F00 to FI_ILDGR_F00.
FI Batch Selection	FI_POST_BATCH	select Financial Services Industries, then select Analysis and Processing, then select Journal Post Engines, then select FI Journal Post, then select FI Batch Selection Click the Run Engines link. Then click the FI Journal Post link in the Journal Post Engines menu.	Select by batch ID the instrument data to post from FI_JRNL_F00 to FI_ILDGR_F00.
Run FI Unpost	RUN_FI_UNP	select Financial Services Industries, then select Analysis and Processing, then select Journal Post Engines, then select FI Journal Unpost, then select Run FI Unpost Click the Run Engines link. Then click the FI Journal Unpost link in the Journal Post Engines menu.	Unpost data by batch ID from FI_ILDGR_F00.
FI Journal Unpost - Batch Selection	FI_UNPOST_BATCH	select Financial Services Industries, then select Analysis and Processing, then select Journal Post Engines, then select FI Journal Unpost, then select Batch Selection Click the Run Engines link. Then click the FI Journal Unpost link in the Journal Post Engines menu.	Select by batch ID the instrument data to unpost from FI_ILDGR_F00.
Journal Cleanup	RUN_FI_DELB	select Financial Services Industries, then select Analysis and Processing, then select Journal Post Engines, then select FI Journal Cleanup, then select Journal Cleanup Click the Run Engines link. Then click the FI Journal Cleanup link in the Journal Post Engines menu.	Delete data from FI_IJRNL_F00 by batch ID according to the parameters that you select. You can only delete batches that are not posted. Once posted, the batch cannot be deleted.
FI Journal Cleanup - Batch Selection	FI_DELETE_BATCH	select Financial Services Industries, then select Analysis and Processing, then select Journal Post Engines, then select FI Journal Cleanup, then select Batch Selection Click the Run Engines link. Then click the FI Journal Cleanup link in the Journal Post Engines menu.	Select by batch ID the unposted instrument data to delete from FI_IJRNL_F00.

Understanding Instrument-Level Posting

You have the option of posting the results of the enriched engines to the Instrument-Level Ledger (FI_POST). You can also unpost (FI_UNPOST) data previously posted to FI_ILDGR_R00. Additionally, you can delete groups of journals (batches) from the journal table (FI_DELBATCH).

The instrument-level posting process provides a mechanism to aggregate and store financial data associated with a specific instrument. This process is one means that an institution might choose to store and ultimately report on product profitability. Another alternative is posting profitability results at a more summarized level in the PF_LEDGER_F00 table. The key difference between these two approaches is that instrument-level posting stores data in a more detailed ledger table (FI_ILDGR_F00). This table includes the FI_INSTRUMENT_ID as an additional key.

Instrument-level posting is similar to summary-level posting (as discussed in detail in the PeopleSoft Enterprise Performance Management Fundamentals 9.1 Product Documentation). Both require you to populate a journal table, then run a job that summarizes and inserts or updates a target ledger table. If data exists in the target table with the same dimensions (for example, Account, Department ID, Fiscal Year, Accounting Period, and so forth), it is added to the existing ledger rows.

Instrument-level processing differs from summary-level posting in that there is no edit process included. This means that the process does not check for invalid dimensions or out-of-balance conditions. Taking this approach can avoid lengthy processing times for what is normally a high volume set of tables. It is the responsibility of the implementation team to assure that the dimensions and amounts are valid.

You can choose which process (or combination of processes) to employ. Here are some guidelines:

Instrument-level posting generally implies a longer processing cycle due to the detailed instrument volumes.
In addition to other required fields, instrument-level posting requires you to associate an instrument ID and account with every row of data.

This is sometimes difficult to achieve.

Both processes require competency with the use of data manager or other tools, when creating appropriate data in the journal tables.