Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-GTF-DOB (Application Component) Document Builder⤷
/IPRO/BASIS (Package) Tables, Structures, general Infrastruktur
IMG Activity
| ID | /IPRO/MGT_BADI_ELMNT | Start Editor |
| Transaction Code | /IPRO/67000017 | (empty) |
| Created on | 20040602 | |
| Customizing Attributes | /IPRO/MGT_BADI_ELMNT | Start Editor |
| Customizing Activity | /IPRO/ELMNT_DEF | Start Editor |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /IPRO/ELMNT_DEF |
Use
Implement this Business Add-In to define which application should be used to view or edit different type of clauses.
The Business Add-In consists of the method described below, which can be used instead of the standard algorithm.
LAUNCH_EDITOR
The following import parameters are provided:
- IV_FULLTEXT
Full text of the clause/element in the raw format. - IV_FORMAT
Format of the text (PDF, HTML). - IV_TITLE
Title of the clause/element to be displayed in the editor. - IV_MODE
Indicates whether the text is read-only ('V') or editable ('E'). The default value is 'E'. - CV_ENCODING
Encoding of the clause/element text. If you change the encoding inside the editor, the result is returned in this parameter.
The following export parameters must be provided by your coding:
- EV_CHANGED
Indicates whether the text has been changed or not in the editor. - EV_STRING
Changed full text of the clause/element in the raw format.
FORM_EDITOR
The following import parameters are provided:
CV_FORM
Form name of the standard form. This can be the name used in Adobe LiveCycle Designer or SmartForm, or any other form editor. If you create a new form, the result is returned in this parameter.
Requirements
Standard settings
By default, the Business Text Framework (BTF) editor control is used to view/edit clauses in HTML or HTM format, an HTML viewer to display texts in PDF format, and a PDF-based form for standard forms.
Activities
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 coding for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
7. Save and implement your coding. 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 coding you stored in the methods will be run when the application program is executed.
Example
Additional hints
For more information on using Business Add-Ins, see the SAP Library under Basis Components -> ABAP Workbench (BC-DWB) -> Changing the SAP Standard (BC) -> Business Add-Ins.
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 | 20070622 |
| SAP Release Created in | 100 |
