Ansicht
Dokumentation

EXIT_SAPMF40K_001 -

rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.

Processing individual bank statement items after entry

Description

During manual bank statement entry, this function exit enables you

1. to set up your own checks of individual items in the bank statement,
2. to change entered values and
3. to transfer particular values that could not be entered.

Link to Standard Program

During each screen change, the function exit receives one after the other the lines displayed on the screen. The values -possibly changed- are returned to the program. To generate an error message, you can output it yourself or transfer a text string to the program which formats the string as an error message. When message type E (error) or W (warning) appears, the system highlights the corresponding screen line for postprocessing.

Structure of Transferred Data

The function exit imports the following data:

• I_BUKRS = company code

• I_HKONT = G/L bank account number

• I_DYKEY = name of the current layout variant

• I_WAERS = currency key

• I_KWBTR = the statement line amount (with sign)

• I_LINE = other statement line values:

• VGMAN = transaction entered

• VGINT = internal transaction derived from VGMAN

• KFMOD = account modification derived from VGMAN

• VALUT = value date of the statement line item

• and the account assignment fields that can be entered (compare structure RF40KI1).

• I_STATUS = line status (compare structure RF40KI3).

• SEL_TAB = table with selection values (for clearing open items):

• FNAME = name of the selection field

• FWERT = value of the selection field

• ZUOSL = allocation key (only necessary if items in several subledger accounts are to be cleared at the same time with one line item)

The function exit exports the following data:

• E_LINE = other values of the statement line (compare above)

• SEL_TAB = table with selection values (compare above)

• E_GRPNR = grouping for BI sessions (separate BI session generated per E_GRPNR)

• E_MESSTYPE = message type

• E_MESSAGE = message text

• E_UPDATE = indicator whether changes should be accepted

Note

Message type E (error) can only represent fields which can be directly entered on the entry screen. If, for example, several document numbers are entered using "Edit -> Value set", then you can only access the first document number. If message type E represents one of the other document numbers, there is nothing you can do.

Example

1. Checks

Checking whether entered customer numbers exist

To do this, the exit searches table "SEL_TAB" for lines with "SEL_TAB-FNAME" = 'FEBMKK-KUNNR'. A customer number is in field "SEL_TAB-FWERT". The exit can check whether this number exists in the SAP System. If the number does not exist, then the field "E_MESSAGE" is filled with the appropriate text, such as "customer abc does not exist", and the field "E_MESSTYPE" is filled with the required message type.

2. Value changes

Selecting other transaction for amounts greater than 10,000

If field "I_KWBTR" exceeds the amount 10,000, the exit refills the fields "E_LINE-VGMAN", "E_LINE-VGINT" and "E_LINE-KFMOD" ("E_UPDATE= 'X').

3. Filling the special field

Separating the batch input sessions according to accounting clerk

The exit determines the accounting clerk for each subledger in question and appropriately fills the field "E_GRPNR" ("E_UPDATE" = 'X').

The system then generates a separate batch input session for each grouping.

General Data in Customer Master   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4766 Date: 20240425 Time: 064932     sap01-206 ( 59 ms )