Ansicht
Dokumentation

GFD_BADI_06 - BAdI: Save Form Details to Backend

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

This business add- in is used to save the relationship of the form designed by the administrator with any backend object which is specific to an application.

Standard Settings

Importing Parameters

IV_FORM_ID,,,,,,Type,,GFDID

IV_FORM_VERSION,,,,Type,,GFDNUM

IV_OBJECT_ID,,,,,,Type,,GFDID

IV_OPERATION,,,,,,Type,,GFDNAME

Exporting Parameters

EV_FORMID,,,,Type,,GFDID

EV_FORMVERSION,,Type,,GFDNUM

ET_OBJECTID,,,,Type,,GFDID_T

Filter parameters

Context Id is the filter parameter which has to be passed to this BAdI.

Only perform this activity if the following conditions are satisfied:

",,The SAP standard processes do not cover your requirements.

",,You have an in-depth knowledge of the ABAP programming language.

",,BAdI implementations are code extensions and therefore apply across clients. If you have a multiclient system, you must define how the customer enhancement is to be used within the implementation for each client using the system variable SY-MANDT.

Note: BAdIs without multiple usages can have several implementations. However, only one of these implementations may be active at any one time.

",,You must also make sure that instance creation for the implementing class (Properties tab page) is declared as Public and not as Private, Protected, or Abstract. Otherwise, unwanted short dumps may occur during runtime.

For more information on BAdIs, see SAP Library at help.sap.com -> SAP Netweaver 7.0 library -> SAP NetWeaver by Key Capability -> Application Platform by Key capability -> ABAP Technology -> ABAP Workbench -> Changing the SAP Standard (BC) -> Classic BAdIs.

You can also access this documentation from the initial BAdI Builder screen by choosing Help -> Application Help.

When you execute the activity in Customizing, a dialog box appears in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

1. Enter a name for the BAdI implementation in the Implementation field, and choose Create.

2. The screen for creating BAdI implementations is displayed.

3. Enter a short text for the implementation.

4. From the tab index, choose Interface.

5. The Name of Implemented Class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

6. Save your entries, and assign the implementation to a development class.

7. Place the cursor on the method, and double-click to enter method processing.

8. Enter the code for the implementation between the statements method ~ and endmethod.

9. Save and implement your code. Return to the Edit Implementation screen.

10. Save the entries.

Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

11. Choose Activate.

The code you stored in the method will be run when the application program is executed.

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 3605 Date: 20240523 Time: 190117     sap01-206 ( 60 ms )