Ansicht
Dokumentation

RFEBJP0X - Import Bank Statement: ZENGINKYO (Japan)

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.

Description

Program RFEBJP0X imports bank statements into the SAP system,and then generates batch input sessions for posting in G/L and subledger accounting.

There are two types of bank statements for ZENGINKYOU:

general account transaction information (Nyuu-Shukkin Torihiki Meisai)

credit memo transfer information (Furikomi Nyuukin Tsuchi)

Prerequisite is that the data to be imported has already been converted to the R/3 code page used.

By stating parameters, you can specify whether both sessions are generated in one run or whether only the session for G/L accounting is generated first. The batch input session names are generated by the program, in which case you can choose from two rules:

house bank ID and account ID (e.g. DREBA-GIRO)

house bank ID and bank statement number (e.g. DREBA-00115)

The session name for subledger accounting always begins with /.

Interpretation of the Note-to-Payee Fields

Japanese bank statements usually contain neither a document number nor a reference number. In the standard SAP system, you can include the following items in the note to payee:

the bank and branch name of the payer
Gaiyou ran, the user-defined information field for the bank

When the statement contains incoming payments, you can, by specifying the selection field (BELNR oder XBLNR), have the system search the note to payee lines for either document numbers or reference document numbers. Therefore, you can obtain the information you need to clear customer payments.

If you do not specify a selection field, the note to payee fields are not read by the system.

You can narrow the search for document numbers or reference document numbers by specifying a certain length for the selection field and the number range that belongs to it. This method (which also has the effect of speeding up the processing time) works as follows: values that are outside the specified length and specified number range are considered invalid by the program and consequently not used as clearing information.

If you want the note to payee fields to be interpreted in a special way (for example, if you are an insurance company), you can program an individual "user exit".

Requirements

The program checks whether the business transaction codes (external transactions) used by the bank were allocated to an internal transaction within the system configuration. This is necessary because the system posts to the G/L and subledger accounts by using the posting rules stored under an internal transaction.

For external transactions, the system uses the japanese ZNGINKYOU code.

If the program finds an external transaction not maintained in the corresponding table, it terminates after fully importing the bank statement, and outputs a list with the missing entries (error log).

You must maintain these missing entries so that the system can generate the posting transactions in the appropriate sessions. You then must restart the program, making sure you do not select the "import data" field this time, since the bank statement is already in the SAP System.

When the program is restarted, it searches the buffer for all line items not yet indicated as posted in the respective posting area. A line item is regarded as posted only if a posting is put into a session.

Output

The posting log provides information, separated according to posting area, on all postings put into the batch input session. The output also lists the external business transaction codes and the internal transactions which control posting.

The processing statistics show you

how many postings

were created per session

could not be created due to an error

for how many line items postings could not be created for each definition.

Program RFEKAPJ0 prints the bank statements.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up Addresses (Business Address Services)
This documentation is copyright by SAP AG.

Length: 4469 Date: 20240601 Time: 115324 sap01-206 ( 74 ms )