Ansicht
Dokumentation

BKK_PAYM_ITEM_DIALOG - Payment Item Dialog

PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Dialog call-up for entering or postprocessing payment items (PI)

Process flow description

Depending on the activity, initial screen 100 for entering adjustment postings (details: transaction type, bank area, account number) is called, or screen 200 for displaying, postprocessing posted or open PI or PI with status 'In Postprocessing'. The current data for the key supplied is read from table BKKIT and forwarded for further processing to a global structure (G_S_APIOUT). The table for the corresponding payment notes is also made globally available. When you have entered all the required fields on the initial screen, by confirming with ENTER, you branch to screen 200. Before screen 200 is called, the system makes an authorization check and - if applicable - sets lock entries for the payment items that need postprocessing. Before entry, authorization is checked for the initial screen at the PAI event. After dialog processing when the change has been made, the table for PI and a return code that is entered after a functionality is executed are returned. Any locks that were set on the PIs are lifted.

Authorization check

For all activities below menu point 'Payment Item->Edit', the only activity forwarded to the authorization module is 'Edit'. All other activities (create, display, release) are forwarded 1:1. Individual functionalities are not subjected to any special authorization check.

Functionalities

For further processing, depending on the type of payment item, the process and the status, functionalities that are not permitted for the PI in question are hidden.

The functions that need hiding are determined by function module BKK_PAYM_ITEM_EXCL_FUNCTIONS, provided the call was made with the 'General Edit'(CON_ACTIVITY_ALL) or 'Edit' (CON_ACTIVITY_CHANGE) activity.

For all other activities (initial entry, display, reverse, return, release), a function variant is assigned to the activity and to the document type.

It is currently necessary to make this distinction because the first determination version always permits all permitted functionalities, whereas for the second version, either no interface parameters are available (initial values for the first entry) or not all functionalities may be offered when special menu points are called (return, for example).

Field status

The field status is determined via the activity and the document type (function module BKK_PAYM_GET_FIELDSTAT).

Exceptions:

• Special transaction 'Backdated Posting'
  An indicator (TBKKIDT-XDATE_POST) shows that the posting date must appear as required field.

• Value date
  Field status depends on the transaction type Customizing; for initial entry and editing (only if PI status is 'In Postprocessing' and 'Control').

• Check number, position type
  Field status also depends on the transaction type Customizing. If the the transaction type is relevant for checks, the fields are shown and the payment notes are hidden.

• Edit PI with status 'Posted' or 'Posted (Open Item)'.
  All fields are only displayed.

Glossary

Activities = Menu points such as edit generally, release

Functionalities = Post, force post, check, reverse and so on

Parameters

E_RC
I_ACTIVITY
I_DOCTYPE
I_FLG_PPO
I_ITEM_KEY
I_XDATE_POST
T_BKKIT

Exceptions

Function Group

FBII

TXBHW - Original Tax Base Amount in Local Currency   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4159 Date: 20240523 Time: 180741     sap01-206 ( 80 ms )