Hierarchy 
    ⤷
⤷
  IMG Activity 
                            | ID | EASYDM_BADI_NEWNAME | BAdI: Rename File | 
| Transaction Code | S_E4E_66000025 | (empty) | 
| Created on | 20080107 | |
| Customizing Attributes | EASYDM_BADI_NEWNAME | BAdI: Rename File | 
| Customizing Activity | EASYDM_BADI_NEWNAME | BAdI: Rename File | 
  Document 
                            | Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. | 
| Document Name | EASYDMS_NEW_FILENAME | 
Use
When you implement the Business Add-In (BAdI) EASYDMS_NEW_FILENAME, you can rename the originals after check-in.
Requirements
Standard settings
- The BAdI is active in the standard system. The default code is executed automatically.
 - All texts are filled automatically and transferred to the BAdI to be changed.
 
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create. 
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
 - If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
 - Save your entries and assign the Add-In to a package.
 - To edit a method, double-click its name.
 - Enter your implementation code between the 
method <Interface Name>~<Name of Method>.andendmethod.statements. - Save and activate your code. Navigate back to the Change Implementation screen. 
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate. 
When the application program is executed, the code you created is run through. 
Example
METHOD if_ex_easydms_new_filename~rename_file.
DATA: ls_docfile TYPE bapi_doc_files2,
ls_doknr_extern TYPE filep.
LOOP AT docfile INTO ls_docfile.
WRITE: document_doknr TO ls_doknr_extern.
CONCATENATE ls_doknr_extern '_' ls_docfile-docfile
INTO ls_docfile-docfile.
MODIFY docfile FROM ls_docfile.
ENDLOOP.
ENDIF.
ENDMETHOD.
See also:
Methods:
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits | 
| 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 | 20080107 | 
| SAP Release Created in |