Kontakt

Ansicht
Dokumentation

TFW_TEMPLATE_UPDATE - Registration of Changes to (Mini-) Templates

TFW_TEMPLATE_UPDATE - Registration of Changes to (Mini-) Templates

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

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

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

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 the BAdI is filter-dependent, you must enter a filter value for your implementation. Choose you template framework application object as the filter value.

Methods

Transfer Information about Changes to Templates






CPI1466 during Backup   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 5462 Date: 20240523 Time: 171228     sap01-206 ( 91 ms )