Entering content frameFunction documentationEntering Lockbox Data per EDI (FI-BL-PT-LB) Locate the document in its SAP Library structure


Lockboxdata that you previously received from the house bank or from a lockbox provider via electronic data transfer can now be received per EDI. This data is then imported into the R/3 System automatically and can be subject to further processing - customer receivables are cleared with the incoming payments.



You must carry out this step before maintaining the partner profiles, since it is only when maintaining these profiles that you can select the EDI-compatible banks.

Proceed as follows:

a. In the Implementation Guide (IMG) choose Bank Accounting ® Bank Accounts ® Define House Banks.

b. Carry out the activity.

c. Enter a company code and choose Goto ® House banks.

d. Select the house bank you require (double-click).

e. Choose Goto ® DME.

f. Enter a partner number (the bank key for example).

You can branch to the partner profiles from this screen. For information on what you can define under partner profiles, refer to the section on IDocs.

For more information, refer to Customizing for Bank Accounting under Business Volume ® Payment Transactions ® Lockbox

Define Control Parameters

Define Posting Data

For more information on lockboxes, access the R/3 Library and choose Financial Accounting ® Bank Accounting ® Business Volume ® Lockbox.

Since ISO codes can be transferred using EDI, your Customizing entries for the conversion of SAP codes into ISO codes for currencies, units of measurement, and countries must be entered in full and contain no errors.

For more information, refer to Global Settings in the Implementation Guide (IMG) and the activities Set Countries, Check Currency Codes, Check Units of Measurement

IDoc interface

Make the following entries in the in-bound parameter profiles:



Message type


Logical message


Partner type


Process code



Immediate processing (for example)

Permitted processor

Organizational unit (an R/3 user for example)


Inbound processing

Lock box data is processed in three stages:

  1. The data is imported into the R/3 System and stored in bank data storage. The system evaluates your Customizing settings for the lockbox and adds this data (posting rules, company code, data on the house bank account and so on) to the lockbox data.
  2. To generate the postings for Accounts Receivable and Accounts Payable that result from the lockbox data, schedule report RFEBLB30.
  3. To postprocess lockbox data (checks) run transaction FLB1.

During postprocessing, you branch to processing payment advice notes, where you can change, supplement or delete clearing information.

Dealing with exceptions

In the event of an error, the system generates a workitem (the task FINSTA_ERROR is started) and determines the processor using the Structure link IDoc interface standard method


Ensure that you define an administrator who can be notified of errors automatically is defined for the Workflow basic data. To do so, on the R/3 System screen choose Tools ® SAP Business Workflow ® Development ® Definition tools ® Tasks/Task groups ® Change.

Modifying data using customer exits

When the system processes a type FINSTA01 IDoc, you can use the following customer exits to access the database (to read or to change data):

This function module is called up immediately prior to writing the lockbox data. For more information, see the documentation on function module EXIT_SAPLIEDP_201 in enhancement FEDI0005 (transaction CMOD).

You can access the dataset when writing individual segments to it.

To do so, define the segments for which a corresponding function module is to be called up by maintaining table "FEDICUS". Function module "202" is then called up for processing the segments defined in this table. For more information, see the documentation on function module EXIT_SAPLIEDP_202, enhancement FEDI0005.


Enhancement FEBLB001 for lockbox data is also triggered for inbound IDocs (report RFEBLB30 starts report RFEBLB20 which calls up the customer exits). It follows that you do not need to transfer any coding that may exist in this report to one of the customer exits of enhancement FEDI0005.



Leaving content frame