Kontakt

Ansicht
Dokumentation

BADI_SD_FUNCTION_ACT - Define Additional Checks for Activating SD Functions

BADI_SD_FUNCTION_ACT - Define Additional Checks for Activating SD Functions

ABAP Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Sales and Distribution application for Revenue Recognition.
In the Customizing activity Activate SD Functions you can enable Customizing for Revenue Recognition and make the appropriate settings.

So that only a restricted user group can carry out this activity, this BAdI executes authorization checks. This way, you can prevent activation information from being changed or created.

The BAdI provides the following methods:

  • CHECK_CHANGING_AUTHORITY - Check Change/Create Authorization
If you make an implementation for this method and authorization is withdrawn, the user can only carry out this activity for revenue recognition in display mode.
  • CHECK_FIELD_CHANGING_AUTHORITY- Check Change/Create Authorization on Field Level
If you make an implementation for this method and authorization is withdrawn, certain data in the Customizing activity cannot be changed.
The following fields are provided for this authorization check:
  • V_TVNFACTC-RRACT: Revenue Recognition Customizing

There is no additional authorization check in the standard system. As long as you do not create an implementation, every user who is authorized to change Customizing settings can make settings for revenue recognition.

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.

The standard system has an example implementation for the BAdI. This implementation is stored in the example class CL_BADI_SD_FUNCTION_ACTIVATION. For more information, see the documentation for the example implementation.






RFUMSV00 - Advance Return for Tax on Sales/Purchases   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3949 Date: 20240523 Time: 232626     sap01-206 ( 54 ms )