Fonction SAP BKK_PAYM_ITEM_DIALOG - Payment Item Dialog

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
I_ACTIVITY TBKKIDT-AKTYP C 2 Activity
I_DOCTYPE TBKKIDT-DOCTYPE C 2 X Document Type
I_ITEM_KEY BKKP_BKKIT_KEY 0 Payment Item Key
I_XDATE_POST TBKKIDT-XDATE_POST C 1 X 'X': Return Posting Allowed

Paramètre Reférence Type Long. Description
E_RC SYST-SUBRC I 4 (See Long Text)

Paramètre Reférence Long. Facultatif Description
T_BKKIT BKKIT 1215 X Payment Item(s)

Process flow description
Depending on the activity, initial screen 100 for entering adjustmentpostings (details: transaction type, bank area, account number) iscalled, or screen 200 for displaying, postprocessing posted or open PIor PI with status 'In Postprocessing'. The currentdata for the key supplied is read from table BKKIT and forwarded forfurther processing to a global structure (G_S_APIOUT). The table forthe corresponding payment notes is also made globally available. Whenyou have entered all the required fields on the initial screen, byconfirming with ENTER, you branch to screen 200. Before screen 200 iscalled, the system makes an authorization check and - if applicable -sets lock entries for the payment items that need postprocessing. Beforeentry, authorization is checked for the initial screen at the PAIevent. After dialog processing when the change has been made, thetable for PI and a return code that is entered after a functionality isexecuted 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 authorizationmodule is 'Edit'. All other activities (create, display, release) areforwarded 1:1. Individual functionalities are not subjected to anyspecial authorization check.

Functionalities
For further processing, depending on thetype of payment item, theprocess and the status, functionalities that arenot permitted for the PI in question are hidden.
The functions that need hiding are determined by function moduleBKK_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 theactivity and to the document type.
It is currently necessary to make this distinction because the firstdetermination version always permits all permitted functionalities,whereas for the second version, either no interface parameters areavailable (initial values for the first entry) or not allfunctionalities may be offered when special menu points are called(return, for example).

Field status
The field status is determined via the activity and the documenttype (function module BKK_PAYM_GET_FIELDSTAT).
Exceptions:

  • Special transaction 'Backdated Posting'

    • An indicator (TBKKIDT-XDATE_POST) shows that the posting date mustappear as required field.
    • Value date

      • Field status depends on the transaction type Customizing; for initialentry 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 thethe transaction type is relevant for checks, the fields are shown andthe 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

          Description
          rc 0 = displayed /no changes CON_RC_DIAL_DISP (IBKKCONP)
          rc 1 = changed CON_RC_DIAL_CHNG
          rc 2 = posted CON_RC_DIAL_POST
          rc 3 = posted with checkflags CON_RC_DIAL_FORCE
          rc 4 = preposted with errors CON_RC_DIAL_PREP
          rc 5 = deleted CON_RC_DIAL_DEL
          rc 6 = released CON_RC_DIAL_REL