How to use EBPP_LOG_DISP - Display of Log Categories

SAP Transaction Code - Details

• Transaction Code: EBPP_LOG_DISP

  Description: Display of Log Categories

  Release: S/4HANA and ECC 6

  Menu Path:

  • Accounting > Financial Supply Chain Management > Biller Direct > Customer Portal Administration > Display Customer Actions Logs

• • Program: REBPPEVENTLOG_DISPLAY

    Screen: 1000

    Authorization Object:

  • Development Package: EBPP_APAR

    Package Description:

    Parent Package: PI-WEB

  • Module/Component: FIN-FSCM-BD-AR

    Description: Accounts Receivable Accounting Process Integration

Smart SAP Assistant

• SAP Tcode: EBPP_LOG_DISP - Display of Log Categories

  
  Overview:
  The SAP transaction code EBPP_LOG_DISP is used to display log categories in the SAP system. This transaction code is used to view the log categories that are available in the system and to check the status of each log category. 
  
  Functionality: 
  The EBPP_LOG_DISP transaction code allows users to view the log categories that are available in the system. It also allows users to check the status of each log category, such as whether it is active or inactive. This transaction code can be used to troubleshoot any issues related to log categories in the system. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code EBPP_LOG_DISP into the command field. 
  2. The list of available log categories will be displayed. 
  3. Select a log category from the list and click on “Display” button. 
  4. The status of the selected log category will be displayed. 
  5. To activate or deactivate a log category, select it and click on “Activate” or “Deactivate” button respectively. 
  6. To save any changes made, click on “Save” button. 
  7. To exit, click on “Back” button or press F3 key on your keyboard. 
  
  Other Recommendations: 
  It is recommended that users should be familiar with the different log categories before using this transaction code, as it can help them troubleshoot any issues related to log categories more efficiently. Additionally, users should always save any changes made before exiting the transaction code, as this will ensure that all changes are properly saved in the system.