Kontakt

Ansicht
Dokumentation

LGE_SUBSCR_ACL - Add-In: Log Entry Subscreen

LGE_SUBSCR_ACL - Add-In: Log Entry Subscreen

General Data in Customer Master   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Implementing Business Add-In LGE_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.

To better understand all 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 will enable 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. These fields are
  • 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. (See below). On the database the last ,,five fields are represented by the Operation time and Cycles Measurement documents. (See definition of the ,,corresponding counters below.)

  • 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 details, see example implementation listed below.)
  • Create your own implementation of Business Add-In LGE_SUBSCR_ACL:
    In the Subscreens tab strip link the sub screen area defined in the Add-In with your subscreen that will enable maintaining your specific log entry data.

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.

Business Add-In implementation LGE_SUBSCR_EX; Subscreen 9999 in program SAPLDIACL_GUI_LGE_EX. From the Customizing screen, choose Execute -> LGE_SUBSCR_EX.

Interface

Log Entry Sub Screen






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

Length: 5435 Date: 20240523 Time: 220944     sap01-206 ( 91 ms )