Purpose
The Budgetary Ledger (BL) Correction program is a tool or utility usedto correct BL documents, which may be incorrectly posted or not postedat all due to incorrect customizing in Funds Management (FM) and/orprogram errors in FM or BL. It corrects BL postings on a document level.The program can be run more than once for the same original document,such as

• Funds reservation documents


• Cost controlling (CO) documents


• Purchase requisitions (PRs)


• Purchase orders (POs)


• Sales order (SO) documents


• Goods receipts (GRs)


• Invoice receipts (IRs)


• Payments


• Budgeting documents (not in release IS-PS 4.62).

Here are a few scenarios in which you may need to run this program tocorrect your original document:

• It is missing a BL document.


• It already has a BL document, but it is incorrect.


• It may have additional unwanted BL documents.


• It may have a BL document, but the original document is NOT relevant to
the BL.

• You may have changed your BL configurations and you want these new
configuration settings to take effect on your BL postings of theoriginal document.

Integration
Program RFFMFG_BL_CORR reads FM data and creates a BL correction (FI-BL)document and its corresponding Special Purpose Ledger (FI-SL) documentby calling the Accounting interface. The generated BL correctiondocument will be attached to the original document, for example,purchase orders, sales orders, goods receipts, and so on, which you arecorrecting. For instance, while displaying a PO (transaction ME23N), goto menu option Environment >> AC commitment documents to see the list ofaccounting documents.
The BL Correction program uses your current configurations for the BLfor your normal online postings, for example, OFBL (for the former BL),to create a BL correction document. Note that the program createsBL correction documents by going through the accounting interface;however, only the FI-BL and FI-SL documents are created. This means thatFMDERIVE is not called by the program because we do not wish to post FMagain.

Prerequisites
Program RFFMFG_BL_CORR works on the assumption that your FM data isalready correct. If your FM data is not correct, correct it first beforerunning this program to generate correction postings.

Selection
The selection screen contains a tab-strip with three tabs, namely,General Attributes, Document Selection, and Additional Options.


• General Attributes

This tab allows you to enter overall selection criteria and postingparameters, along with other general parameters.

• Document Selection

This is where you enter ranges of document numbers for the selectioncriteria. Documents that can be processed by this program include budgetentries (not valid for release IS-PS 4.62), commitment postings (forexample, PR's and PO's, funds reservation documents, and so on), actualsdocuments (for example, GRs, IRs, vendor invoices, billing documents,payments, and so on), and CO documents. Be sure to select theappropriate checkbox(es) for the types of documents you would like toprocess. Note that actuals documents are the FI document numbers.For example, if you would like to run the program for an MM invoice, youwould have to enter the corresponding FI document number for theinvoice, not the MM document number.

• Additional Options

Payment Budget category (Ledger 9A)
Select this radio button if you update the BL with the payment budget.This is the case for most customers, so this button is selected bydefault. This option is not available for release IS-PS 4.62.
Commitment Budget category
Select this radio button if you update the BL with the commitmentbudget. Some customers, such as the Columbian and Spanish customers,update the BL with commitment budget. This option is not available forrelease IS-PS 4.62.
Correct FM entries for which no predecessor document is found in FM
Correct FM entries for which no successor document is found FM

Output
The screen shows an ALV report containing the status information. Somedetails:


• Lot status column

This first column shows the status of a lot. When the BL Data Explorerscreen appears, each lot has already been assigned a status - an initialsimulation for all lots. The following are different statuses you maysee and what they mean. Some statuses share the same icon, but havedifferent texts in the tool tips.
Error
This lot has an error, which may be caused by DB data. For example, oneerror may be caused by missing predecessor document information.
Correction posted
This status is set for a lot for which the program has posted a BLcorrection document(s). The status is set only in production run (updatemode).
Correction failed
This status is set for a lot for which the program attempted but failedto post a BL document. The status is set only in production run. Checkthe message log for any messages.
Simulation successful
The program sets this status for a lot that has been simulatedsuccessfully. You see this status only in test runs.
Simulation failed
The program sets this status for lots it has attempted but failed tosimulate in a test run. You see this status only in test runs. Check themessage log for any messages.
Not relevant to BL
This status is set when the system recognizes that a lot is not relevantto the BL and does not require any BL posting. You may see this statusin both production runs and test runs.
Already correct
This status indicates that a lot, which you would like to simulate orcorrect, already has the correct BL posting(s). This means that theprogram will not generate any BL posting(s) for this lot when aproduction run takes place.
Incorrect BL posting exists
The program sets this status for a lot that has existing BL documentsthat are incorrect and need correction. You may see this status in bothsimulation (test run) and correction posting (production run).
Required BL posting does not exist
A lot receives this status if it is relevant to the BL but missing a BLdocument.
BL posted in error
This status can only be set in simulation. It means that the program hasfound a BL document, which has been incorrectly posted.

• The lot number column

This lot number column normally would contain the FM transaction numbers(TRANR) found in DB tables FMIOI, FMIFIIT, and FMBH (for EA-PS 200 andhigher). However, for Cost Controlling (CO) documents, FM is not updatedwith the TRANR numbers. Hence, for CO documents, this column would showthe object key (AWKEY), which is composed of the reference documentnumber and reference organization.

• The reference document number column

This column contains the document, which you would like the program tocorrect. You can drill down to the reference document by double-clickingon the document number.

• The table name column

This column shows you from which DB tables the program has taken itsdata. For example, for a given purchase order, the program reads thedata from DB table FMIOI.

Activities


• Display current/delta BL items:

You can select a lot number and determine whether or not a delta existsby clicking the "Delta" button. A delta is defined as a differencebetween what the program thinks should have been posted (shown in the"NEW" window) given the current FM data and BL configuration and theoriginal existing BL postings (shown in the "ORIG" window). The differ
ence is then displayed in a third window named "DELTA". In other words,DELTA = NEW - ORIG.

• Display source FM items:

You can select a lot number and see the FM database entries by clickingthe "FM Items" button. A separate window appears, showing the FMentries.

• View message log:

This button is located next to the "Delta" button to the right of theALV application toolbar. Clicking this button shows you all the messages- information, warning, and error - you received since programexecution, including those you may receive for your online actions.