Fonction SAP BKK_BKKA_ACCOUNT_MAINTAIN - Maintain Account in Dialog

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
I_ACCNT BKK40-ACNUM_INT C 10 Internal Account Number
I_AKTYP TBZ0K-AKTYP C 2 Activity Category
I_APPLI TBZ0A-APPLI C 4 X Calling Application
I_BKKRS BKK40-BKKRS C 4 Bank Area
I_OTITL TBZ1T-OTITL C 25 X Screen Header (Object Part)
I_SICHT_START TBZ3E-SICHT C 6 SPACE X View of First Data Screen
I_VARNR TBZ3-VARNR C 6 X Screen Sequence Variant
I_XINIT IBKK50-CHAR1 C 1 SPACE X Indicator: Display Initial Screen?
I_XSAVE IBKK50-XSAVE C 1 'X' X Indicator: Account Saves Automatically?
I_XUPDTASK BOOLE-BOOLE C 1 'X' X Indicator: Use Update to Save

Paramètre Reférence Type Long. Description
E_RC SYST-SUBRC I 4 Return Code
E_STATE IBKK50-CHAR1 C 1 Return Status: How Was Maintenance Exited?
E_STATE_FCODE IBKK50-CHAR1 C 1 Exit Maintenance: With Which Function?

Value range
0 No errors occurred.
1 Account does not exist.

Description
This parameter informs you how the maintenance screenwas exited. It is only useful to evaluate this parameterif the initial screens are not displayed(parameter I_XINIT = SPACE). Otherwise, several partners can bemaintained within a function module call-up. In this case, the status ofthe last account to be maintained is returned.

Value range
1 Data has been saved/transferred, there were changes.
2 Data has been saved/transferred, no changes.
3 Maintenance screen exited without saving/transferring(functions Cancel, End, ...).

Description
The E_STATE_FCODE parameter returns the function that was used to exitthe maintenance screen.
It is only useful to evaluate this parameter if the initial screens arenot displayed (parameter I_XINIT = SPACE). Otherwise, several objectinstancescan be maintained within a function module call-up. In this case,the function of the last object instance to be maintained is returned.

Value range
1 Save/transfer
2 Back
3 Cancel
4 End
5 Other

Meaning
This parameter determines the activity that is used to call up themaintenance screen.

Range

  • 01 = Create

  • 02 = Change

  • 03 = Display

    • Description
    If a calling application is transferred, the system only displays theentries that are assigned to the calling application in the selectionfor role categories and role category groupings. Otherwise, allrole categories and role category groupings are displayed for selection.

    Description
    The title appears in the title bar at the top of the screen. You canprovide the object-dependent part of the title here.
    The object-dependent part of the title is determined at runtime. Thereare various possible scenarios for this:

    • The application object uses role categories from the business partner
      • control.
      If a title is provided when the function module is called, this title isused.
      If this is not the case, and exactly one role category or role categorygrouping is maintained, the title stored for this is used.
      If this is not the case either, the title of the application object isused.
      • The application object does not use role categories from the business
        • partner control.
        If a title is provided when the function module is called, this title isused.
        If this is not the case, the title of the application object is used.

        Description
        The I_SICHT_START parameter specifies the data screen that must becalled up first. After exiting the initial screen, the BDT determinesthe data screen that belongs to the view, and calls it up.
        In the cases below, the first data screen is called first:

        • The I_SICHT_START parameter is initial.

        • The transferred view is not used on any of the data screens in the main
          • screen sequence.
          • All fields for the screen in question are hidden.

            • Description
            The screen sequence variantspecifies which screens appear in which sequencewhen scrolling with the Previous Screen and Next Screenfunctions.
            The program determines the screen sequence variant at runtime,differentiating between the following cases:

            • Application object uses role categories from BP control

              • If a screen sequence variant is supplied when the function module iscalled, this variant is used.
              If this is not the case, and there is exactly one role category or onerole category grouping maintained, any screen sequence variant storedfor this is used.
              If this is not the case either, the standard screen sequence variant isused.
              • Application object does not use role categories from BP control

                • If a screen sequence variant is supplied when the function module iscalled, this variant is used.
                If this is not the case, the standard screen sequence variant is used.

                Description
                This indicator specifies whether the initial screen is displayed duringprocessing.

                Value range
                SPACE ,,= the initial screen runs as a dark screen and is only displayedif there are errors.
                X,,,,= the initial screen is displayed.

                Description
                This indicator determines the mode in which the processing is called.

                Value range
                SPACE ,,= Transfer mode (changes are only flagged and are not saved inthe database).
                X ,,,,= Save mode (changes are saved in the database with thesave function).

                Description
                This indicator determines whether data is written to the databasesynchronously or asynchronously.

                Value range
                SPACE = write data synchronously.
                X = write data asynchronously in an update task.