Ansicht
Dokumentation

GFD_BADI_21 - BADIs: Prefill form

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

This Business add-in (BAdI) is used in the Student Lifecycle Management (IS-HER-CM) component.

You can use this BAdI to prefill the application form based on the context ID either from the student file or from previous application forms, or from user registration details.

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.

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.

Changing Parameters

CT_PARAM_TAB TYPE ABAP_FUNC_PARMBIND_TAB (Table Type for Form Submission Field)

The fields which have to be prefilled will be updated with values by the above changing parameters.

Filter Parameters

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

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 Application Log Documentation   General Material Data  
This documentation is copyright by SAP AG.

Length: 3230 Date: 20240523 Time: 211619     sap01-206 ( 67 ms )