Ansicht
Dokumentation

CRM_TFW_DISTRIBUTE - Distribution of Changes to (Mini-) Templates

CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the component Template Framework (AP-MD-BF-TFW) in report TFW_DX_TEMPLATE_CHANGES. The report is provided by the template framework for the distribution of changes that have occurred in the application objects due to changes made to mini-templates, or the assignment of mini-templates to templates. Since the BAdI is reusable, every required distribution can have its own implementation (Business Warehouse, Exchange Infrastructure, CRM Middleware, and so on).

In its interface, the BAdI anticipates the keys of the application objects affected by the changes, in the form of the table TFW_DX_MINITP. You can build this table, for example, in your implementation of the BAdI TFW_TEMPLATE_UPDATE.

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).

The BAdI is filter-dependent. The application object of the template framework constitutes the filter criterion.

The BAdI is reusable.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

Because of the filter-dependency of the des BAdI, you have to enter a filter value for your implementation. Choose your template framework application object as the filter value.

Methods

Distribute Changes Concerning the Object Instances

PERFORM Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 4572 Date: 20240523 Time: 155449     sap01-206 ( 97 ms )