|
Functionality
You can use this function module to import information about incomingchecks into the system. The data is supplied by a lockbox service or abank.
The bank account can usually be identified using the bank ID andaccount number. In the case of lockbox data, the terms "destination"(for bank ID) and origin (for account) are used.
In the case of lockbox, there is no need to enter the account balances..
Notes
The following authorization object is checked with activity 01(create):
o F_FEBB_BUK Company Code Bank Account
Checks
Lockbox data is stored in the SAP system accurate to the minute. Bankaccount data that applies to the same date and time as data alreadystored is rejected.
Messages are returned to the "Return" parameter. Refer to the parameterdocumentation for information on return codes and what they mean. Further information
For more information, read the "Lockbox" section of the SAP Library.
INCLUDE BAPI_ACCSTMT_CREATEFROMPREVDAYSTMT_KEY OBJECT DOKU ID FULANGUAGE EN
INCLUDE BAPI_ACCSTMT_CREATEFROMPREVDAYBANK_ACCOUNT OBJECT DOKU ID FU Description
Validity of lockbox data
Important fields
STMT_DATE Date of lockbox data
LOCKBOX_NO Lockbox number
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX
INCLUDE BAPI_ACCSTMT_CREATEFROMPREVDAYTESTRUN OBJECT DOKU ID FU
LANGUAGE EN
Description
Enhancement Description
Enhancement Description
Enhancement Description
Lockbox data - Invoice information
The structure is to be filled with information on the invoices paid.The most important specification is the invoice number.
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX
INCLUDE BAPI_TABLE OBJECT DOKU ID TX
Value range
Messages re authorization
Type ID Number Message
A 00 149 No authorization for object <(>&<)>
Messages re input checks
Type ID Number Message
A B1 547 No currency key found for ISO code
<(>&<)> in field <(>&<)>.
E B1 536 Currency amount <(>&<)> <(>&<)> in field<(>&<)> could not beconverted.
A BAPI4499 001 Data (lockbox) already exists:
<(>&<)> <(>&<)> <(>&<)> <(>&<)>
A BAPI4499 003 The bank statement(FEBVW) already
exists:<(>&<)> <(>&<)> <(>&<)> <(>&<)>
A BAPI4499 005 Bank statement date incorrect: <(>&<)>
A BAPI4499 007 No bank statement number could be
allocated
A BAPI4499 008 Unknown error occurred
S BAPI4499 009 Bank statement created: <(>&<)> <(>&<)><(>&<)> <(>&<)>
S BAPI4499 010 Test run completed successfully.
Statement:<(>&<)> <(>&<)> <(>&<)> <(>&<)>
W BAPI4499 011 No record written in cash management(Customizing).
S BAPI4499 012 Cash management memo record written.
ID: <(>&<)> Statement: <(>&<)> <(>&<)><(>&<)>
Messages re incorrect settings in Customizing
Type ID Number Message
E FB 759 Bank details <(>&<)> <(>&<)> not in tableT028B
E FB 915 Entry <(>&<)> <(>&<)> missing from tableT035D
E FB 882 No G/L account maintained for house
bank account <(>&<)> <(>&<)>
E FB 736 House bank table; no entry with
bank key <(>&<)> and account <(>&<)>
A FB 735 Inconsistency between house bank
account table and house bank table
A FB 755 Table T012 has no entry with bank key
<(>&<)>
E FV 141 Currency <(>&<)> not allowed in account
<(>&<)> / <(>&<)>.
E FB 858 No bank account found for currency:
<(>&<)> <(>&<)> <(>&<)>
E FB 859 No bank account found for currency:
<(>&<)> <(>&<)> <(>&<)>
E FB 755 Table T012 has no entry with bank key
<(>&<)>
E FB 865 External transaction for determining
posting rule is missing
E FB 866 No posting rule could be found for
external transaction <(>&<)> Description
This structure is designed to provide information on an incomingpayment (incoming check):
Important fields:
VALUE_DATE Value date (date on which the amount was debited/
credited)
TRAMOUNT/DB_CR_IND Amount (+/- sign)
TRANS_CODE Transaction type, in coded form
(examples; BAI code, BTC)
or
EXT_TRANS Transaction type ID (27 characters)
BANK_CHKNO Check number/reference number
|