SAP ABAP IMG Activity _ISPSFM_N_BCS_BADI01 (BAdI: Create User-Defined Fields in Budget Entry Document)
Hierarchy
EA-PS (Software Component) SAP Enterprise Extension Public Services
   PSM-FM-MD (Application Component) Master Data
     FMCC (Package) FIFM: Cash budget management customizing
IMG Activity
ID _ISPSFM_N_BCS_BADI01 BAdI: Create User-Defined Fields in Budget Entry Document  
Transaction Code S_ALN_01000569   (empty) 
Created on 20020115    
Customizing Attributes _ISPSFM_N_BCS_BADI01   BAdI: Create User-Defined Fields in Budget Entry Document 
Customizing Activity _ISPSFM_N_BCS_BADI01   BAdI: Create User-Defined Fields in Budget Entry Document 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FMBW_CUSTOMER    

Note:
The settings affected here are exclusively reserved for the use of the Budget Control System (BCS).

Title

Business Add-In: Customer specific fields in budgeting workbench (entry document)

Use

With this Business Add-In you can define a sub-screen for the input/output of your specific fields associated with an entry document.

It can only be implemented for Funds Management, component Budget Control System (BCS).

The methods of this BAdI are called in the PBO (Process Before Output) and PAI (Process After Input) of the screen that contains additional data.

Additionally, the method PRINT is called when the entry document is printed.

Standard settings

SAP does not deliver any implementations of this BAdI. Therefore in the standard release the BAdI is not active.

Activities

If you would like to have customer-specific fields for entry documents, you should first define the corresponding customer include (CI_FMBH).

Now implement this BAdI applying the following steps:

After calling up the IMG activity, 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. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    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.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    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.

  9. Choose Activate

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

Example

Define a sub-screen that contains customer-specific fields.

The method GET_DATA_FROM_SCREEN should be called in the PBO of your subscreen.

The method PUT_DATA_TO_SCREEN should be called in the PAI of your subscreen.

The method PRINT is called when the entry document is printed.

Assign the subscreen to the BAdI implementation.

Activate your BAdI implementation.

Requirements

The structure CI_FMBH (customer include for entry document) should be defined.

Recommendation

Only use character-like fields in the structure.

Further notes

Documentation for the BAdI method PUT_DATA_TO_SCREEN

Documentation for the BAdI method GET_DATA_FROM_SCREEN

Documentation for the BAdI method PRINT

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030707 
SAP Release Created in 110