sapnote_0000402989

7/29/2019 sapnote_0000402989

http://slidepdf.com/reader/full/sapnote0000402989 1/3

07.03.2013 of 3

SAP Note 402989 - Lockbox error FA308 INPUT_PRUEFEN 1

Note Language: English Version: 1 Validity: Valid Since 13.08.2001

Summary

Symptom The user receives the error message FA 308 INPUT_PRUEFEN 1when importing lockbox BAI or BAI2 file, or during batch input ofthe bank file into the R/3 system.

Additional key wordsFLB2; lockbox, RFEBLB00, FA308, INPUT_PRUFEN 1

Cause and prerequisitesThe error is raised by routines that create Payment advice (AVIK, AVIP,

AVIR) from the data presented. Error is generally due to configuration,

bank file content errors, duplicated bank file data or repeated check

numbers. It is also possible to incorrectly construct or manipulate advice

data in the user exits of the bank fileinterpretation.

Solution1. Verify the bank source data conforms to the format for BAI or BAI2

(Bank Administration Institute). The formats differ in their

level of information detail.

2. Verify user has authorization to import the file, or create

input for automatic insert of customer bank details. These are

generally objects FEBB-BUK,F-FEBC-BUK, or F_BKPF_BUP.

Use Transaction SU53.

3. For a BAI format file, the cause of error FA308 may be 'blank'

or all zero invoice numbers. This may cause the system to think

there are fewer records than specified in the record type. A

"blank" invoice number is expected to be the end of the check.

If there is another record type 4, the insert sequence for AVIP

is corrupted. The invoices on the BAI file must match the number

of invoices per record in to be the end of the check. Using BAI

format, on record type 4, every every field for a document number

must be filled in, prior to the next type 4 record.

4. Lockbox program only processes certain data from the record types

1, 5, 6 & 4. All record types must conform to the input structures

maintained within the system that can be seen in the data

dictionary as structures with names FLB2*, FLB0*.

5. To prevent duplicate load and posting of a file, a lockbox

file will be rejected and error out if imported with the

identical time, date, or check numbers.

In a test system, before re-importing, it is advised you

change the File creation date, lockbox batch number,

check numbers, and invoice numbers every time you run

the lockbox file. Otherwise, payments will be identified

as being already cleared and the payments will be placed'on account'.

7/29/2019 sapnote_0000402989


07.03.2013 of 3


6. Delete a failed lockbox shortkey (KUKEY) from Bank data memory. See

Note 15759 and Program RFEBKA96. Note the caution instructions.

7. A BAI record format may be incorrect. Verify the BAI import

record format in transaction OBAY (no record length in BAI2)

Document length 10

Record No. of document numbers

Record 6 [3] (read by structure FLB06)

(A record 6 is considered 'one check')

Record 4 [6] (read by structure FLB04)

(Use as many #4 records as required)

The SAP standard lockbox processing looks at each #6

record as an 'individual check'. If the import file puts the

#4 records after several #6 records, then they will be misread.

8. Check CMOD to see if both user-exits are activated.

Structure AVIK may be passed to a user-exit. Test by

"de-activating" the user exits to verify the standard SAP programworks correctly. Review that data initialization occurs properly

in all called exit programs.

9. Check to see that bank account data is properly configured

in FI12 after upgrade or change. (see Note 98098)

10.Debug error message FA308: It may be useful to set a breakpoint

in the program RFEBLB20 at the point just prior to advice

creation (search for customer function_001) but after

the user-exit execution.

Inspect the data (AVIK, AVIP, AVIR) for proper ordering in

their respective key structures. Inspect the existing advice

in the same amount for the same customer. Performing the same

reasonable content test in existing external processes might

create them in error. Item numbers must be sequential without

gaps in sequencing, not duplicated, and probably presented in

sorted reordering.

11. Use Test Tool RFEBLBT2 via SE38 to check the formatting of

sample BAI/BAI2 file.

Header DataRelease Status: Released for Customer

Released on: 12.07.2001 22:00:00

Master Language: English

Priority: Recommendations/additional info

Category: Help for error analysis

Primary Component: FI-BL-PT-US US-bank statement/lockbox

The Note is release-independent

7/29/2019 sapnote_0000402989


07.03.2013 of 3


Related Notes

Number Short Text

98098 House bank data (table BNKA) transport via FI12

15759 Deleting account statements and check deposit lists

sapnote_0000402989

Documents