The JE Posting Process

Use

The purpose of JE posting is to take a batch, validate it for consistency, and create FI documents and post those entries in various line item accounts needed for subsequent business processing.

JE Posting is a process that with a few exceptions runs behind the scenes (without user dialog) and is the heart of Journal Entry. It receives journal entry data (representing financial transactions) from the PRA modules (Valuation, Revenue Distribution, etc.), and summarizes them in batches and posts them to the PRA JE line item tables and to SAP FI. JE Posting is the link between the journal entries coming from PRA applications and the FI documents and JE line item table items that are created.

All application areas of PRA that create financial transactions call the Journal Entry system and use it. The sender (source) of the data is the various application areas of PRA (Revenue Distribution, Checkwrite, Check input, etc.).

The JE Posting Module is automatically called by the various PRA application areas. For example, whenever you create a Valuation, Revenue Distribution, Checkwrite, Check Input, Tax and Royalty, Owner Suspense, or Accounts Receivable document, the JE Posting Process is automatically triggered.

There is an exception to that, however – the JE stand alone Posting Mode. It is used to manually trigger JE Posting for ad hoc processing needs like manual journal entry and reject corrections. For more information on that area, see: Running JE Posting in Stand-Alone Mode (JE Posting Driver) .

The following is a graphical representation of the data flow for JE posting:

Whenever journal entries are posted, the data for each journal entry is posted to two separate tables: the JE General Ledger, and JE line item tables (one of the ten line item tables, based on what type of financial transaction is involved).

Features

JE Posting can handle three kinds of batches:

Batch

Description

Original posting

Original posting is the case when JE receives a batch number (a set of two or more JE records) to be posted for the first time.

Reject reprocessing

Reject reprocessing occurs when JE posted the original batches and some line item failed validation and was rejected. Those entries are stored in a JE table (Manual JE & Rejects Table) which is corrected through the Manual Journal entry screen. Once the problem has been fixed, it is sent again for posting through the stand-alone JE posting driver.

Write-off

Write-off processing happens when the user decides to discard the rejected line item instead of correcting the error.

The following functions are supported:

  • Validations are carried out on the journal entries (checks are carried out on the journal entries with respect to: master data, data integrity, and checks if the fields are filled).

  • Any errors in journal entries are written to an error table (Manual JE and Rejects Table). From there, you can use the Running JE Posting in Stand-Alone Mode (JE Posting Driver) to manually trigger JE Posting, after any corrections have been made via the Manual JE function.

  • The formatting of accepted journal entries for input into the JE subledgers and SAP FI ledgers

  • The updating of the A/R interface table with receivable line items

When the batch is accepted, the set of line items for the batch is summarized on a company code, accounting period, batch number, and account number and FI document line items are formatted and posted to FI through a BAPI call.

The ultimate function of the JE Post process is to post journal entries (summarized financial transactions) to line items accounts in JE (the line item tables) and to post to SAP FI. JE Posting helps you carry your financial transactions to financial statements in FI.

Each journal entry has two entries: a header and a line item. The header entry is posted to the PRA General Ledger, and the item is posted to a JE line item.

  • The system assigns a batch number to each batch.

  • Each process calls the JE post directly, thus eliminating the need for JE post batch jobs.

  • Reconciliation between postings in FI and batch number in PRA exists

  • JE reports (The Accepted Journal Entry Report, and the Rejected Journal Entry Report) can be executed at any time for any JE post run

  • A new JE post process can be run even if the previous post process failed

  • A BAPI is used as an interface to post to SAP FI.

  • A staging table (JEINTF) is used in the JE Post Process.

If a batch run fails, the system will roll back the work so that it does not post to FI and the subledgers.

Integration

FI customizing affects JE Posting.