Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
AP-MD-BF-TFW (Application Component) Templates⤷
BTFW (Package) Template Framework
IMG Activity
| ID | TFW_TEMPLATE_UPDATE | Registration of Changes to (Mini-) Templates |
| Transaction Code | S_PAB_09000025 | (empty) |
| Created on | 20050225 | |
| Customizing Attributes | TFW_TEMPLATE_UPDATE | Register Changes to (Mini-) Templates |
| Customizing Activity | TFW_TEMPLATE_UPDATE | Register Changes to (Mini-) Templates |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | TFW_TEMPLATE_UPDATE |
Use
This Business Add-In (BAdI) is used in the component Template Framework. It provides you with information about which changes to the assignment of a mini-template to a template have been carried out, or which mini-templates have been changed. In your implementation you can trigger other activities for your application objects affected by the change. This could, for example, be a distribution of the change to subsequent systems.
The template framework provides the transparent table TFW_DX_MINITP and the BAdI TFW_DISTRIBUTE for this purpose. The table TFW_DX_MINITP can include the keys of the application objects that are affected by changes to the mini-template or to the mini-template assignment.
The methods of the BAdI are used:
- You change a mini-template in Customizing of the template framework, or change the assignment of a mini-template to a template.
- If a mini-template is changed and the mini-template type of the mini-template in question has the category 'reference'.
- If the assignment of a mini-template to a template is changed and the template type of the template in question has the category 'only reference possible'.
- It must be a case of changes that affect the users of the mini-template or template. In the following situations the methods would not be called:
- If the description of a mini-template or template is changed
- If a new mini-template or template is added
The BAdIs TFW_READ, TFW_DISTRIBUTE, TFW_MINITP, TFW_MINITP_DEL_CHECK, TFW_SHOW_WHERE_USED, TFW_TEMPLATE, TFW_TEMPLATE_UPDATE and TFW_TP01_DEL_CHECK are available to the application objects of the template framework that facilitate the usage of template and/or mini-templates.
The BAdIs TFW_MINITP, TFW_MINITP_DEL_CHECK, TFW_TEMPLATE, TFW_TEMPLATE_UPDATE, TFW_TP01_DEL_CHECK and TFW_SHOW_WHERE_USED should be implemented because they are used during the maintenance of templates and mini-templates in the template framework.
The BAdIs TFW_READ and TFW_DISTRIBUTE do not necessarily have to be implemented. Their methods are not called from out of the template framework. However they are useful if you need to determine the currently valid data (BAdI TFW_READ) for an application object to which a template or mini-template is assigned; or if you want to distribute the changes that result from changes to templates or mini-templates on the application objects, to connected systems (BAdI TFW_DISTRIBUTE).
Requirements
Standard settings
The BAdI is filter-dependent. The filter criterion is the template framework application object.
The BAdI is reusable.
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.
Because the BAdI is filter-dependent, you must enter a filter value for your implementation. Choose you template framework application object as the filter value.
Example
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | TFW_TEMPLATE_UPDATE | 0 | PAB0000027 | Templates |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20050225 |
| SAP Release Created in | 700 |
