Ansicht
Dokumentation

LGETY_SUBSCR_ACL - Add-In: Log Entry Type Subscreen

LGETY_SUBSCR_ACL - Add-In: Log Entry Type Subscreen

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Implementing Business Add-In LGETY_SUBSCR_ACL is a prerequisite in order to be able to capture operational and defect information within the Logbook application. Operational information is stored in log entries, and defect information is stored in log notifications. The reason why SAP does not provide a standard solution for log entries is that operational data is very customer-specific, meaning that different customers will store different information in log entries.

After implementing the Business Add-In, you will be able to create log entries containing your specific operational data within Logbooks and log notifications with reference to log entries.

For better understanding of the steps listed here, refer to the example implementation listed in the Example section.

In the Data Dictionary create an append structure containing the fields for your specific operational data. Include this append structure into the DDIC Structure DIACL_LGE_S provided by SAP. This enables saving your specific log entry data in the database table DIACL_LOG_ENTRY as well as accessing the log entry data when using the Logbook application.

SAP provides standard log entry fields that you don't need to append. The fields are as follows:

  • Log entry short text
  • Log entry ID
  • Start and end date, start and end time of operation (4 fields)
  • Number of performed cycles per operation

These fields are available to you when defining the Log entry subscreen. In the database the last five fields are represented by the Operation time and Cycles Measurement documents.

  • In the Logbook Customizing transaction for defining the Counters to be updated by the Logbook application, define the counters for the two standard types Operation time and Cycles (transaction DIACLC2). These counters are used to store start and end date/time and number of performed cycles for each operation.
  • Based on the display structure DIACL_LGE_DS defined in the DDIC, create your specific log entry subscreen, enabling you to maintain your specific log entry data.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

For more information about the procedure, see the SAP Library under Enhancement Framework -> Business Add-Ins (BAdIs) -> BAdIs Concept -> Screen Enhancements.

When the application program is executed, the code you created is run through.

Business Add-In implementation LGETY_SUBSCR_EX; Subscreen 9999 in program SAPLDIACL_GUI_LGE_EX.

Interface

IF_EX_LGETY_SUBSCR_ACL






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

Length: 3760 Date: 20240523 Time: 194411     sap01-206 ( 135 ms )