Kontakt

Ansicht
Dokumentation

TFW_SHOW_WHERE_USED - Output: Where-Used List for Mini-Templates and Templates

TFW_SHOW_WHERE_USED - Output: Where-Used List for Mini-Templates and Templates

General Data in Customer Master   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the component Template Framework (AP-MD-BF-TFW). It is used when changes to mini-templates, templates or the assignment of mini-templates to templates are carried out in template framework Customizing. Using the methods of the BAdIs TFW_MINITP and TFW_TEMPLATE, you can determine which application objects the changes would affect. The result of this where-used list is transferred in the method CALL_WHERE_USED_POPUP. In your BAdI implementation it is expected that you visualize the result of the where-used list, and confirm any rejection of a user's changes that he may have caused himself. The template framework provides the function module TFW_WHERE_USED_POPUP for visualizing the where-used list. You can use this function module if you wish to, but it is not mandatory.

The methods of the BAdI are used:

  • If the mini-template type of the mini-template that is being changed has the category reference.
  • If the template type of the template that is being deleted has the category only reference possible.
  • If the template type of a template has the category only reference possible, and the assignment of a mini-template to this template is being changed
  • In the case of changes that affect the users of the mini-template or template. In the following situations, the methods would not be called up:
  • If the description of a mini-template or mini-template is changed

  • If a 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, with the template framework application object being the filter criterion.

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 as the filter value your template framework application object.

Methods

Transfer of Where-Used List for Display in Popup






CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5595 Date: 20240523 Time: 182552     sap01-206 ( 96 ms )