Kontakt

Ansicht
Dokumentation

TFW_MINITP - Template Framework Mini-Template Usages

TFW_MINITP - Template Framework Mini-Template Usages

RFUMSV00 - Advance Return for Tax on Sales/Purchases   PERFORM Short Reference  
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) and is used to determine which application objects use a mini-template. Mini-templates can be assigned to an application object in different ways, depending on their mini-template type and the read method used. The application object, mini-template type and read method therefore constitute the filter criterion for the BAdI.

The methods of the BAdI are used:

  • If you want to change or delete a mini-template in Customizing of the template framework.
  • The mini-template type of the mini-template in question has the category "reference".
  • When the changes affect the users of the mini-template. In the following the methods are not called up:
  • If the description of a mini-template is changed

  • If a mini-template is added

Changes could affect all the application objects that reference the mini-template. The user is made aware of the consequence of his change in the popup, because mass changes can be triggered in this way.

Depending on the change carried out in the template framework Customizing, the method WHERE_USED_MINITP is called up by itself, or with the method NOT_USED_MINITP as well.

If a template is deleted, only the method WHERE_USED_MINITP is used. This is sufficient because the system does not allow a mini-templated to be deleted if it is still assigned to an application object.

If a mini-template is changed, the method NOT_USED_MINITP is also used. For the application objects, to which the mini-template is assigned directly, you should check whether changes to the mini-template data really affect the application object. This is not the case if own data is assigned to an application object.

In addition, the method WHERE_USED_TP of the BAdI TFW_TEMPLATE is used when a mini-template is changed. For more information, see the documentation of the BAdI TFW_TEMPLATE.

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 made up of:

  • Template framework application object
  • Mini-template type
  • Read method

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 your filter value the application object, the mini-template type and the read method for which you implement the methods.

Methods

Objects to Which a Mini-Template Is Directly Assigned

Objects Do Not Use Mini-Template, as Own Data Exists






Fill RESBD Structure from EBP Component Structure   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 6288 Date: 20240523 Time: 173356     sap01-206 ( 103 ms )