Hierarchy
⤷ IS-AD-LBK (Application Component) R/3 Log Book
⤷ DIACL_GUI_AD (Package) Logbook: presentation layer (A&D)
IMG Activity
ID | LGN_SUBSCR_ACL | Add-In: Log Notification Customer Subscreen |
Transaction Code | S_ALI_97000061 | (empty) |
Created on | 20040412 | |
Customizing Attributes | LGN_SUBSCR_ACL | Add-In: Log Notification Customer Subscreen |
Customizing Activity | LGN_SUBSCR_ACL | Add-In: Log Notification Customer Subscreen |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | LGN_SUBSCR_ACL |
Use
Implementing this BAdI enables you to enhance the standard log notification screen in Logbook. The defect information is stored in log notifications. The reason for providing this BAdI is since the defect information is customer specific and different customers store different information in log notifications.
After implementing the BAdI, you will be able to create log notifications containing your additional defect information.
Requirements
Standard settings
Activities
Following are the steps involved to create the BAdI implementation:
- Create your specific log notification subscreens to be able to maintain your specific log notification data.
- Create your own implementation of BAdI LGN_SUBSCR_ACL
In the Subscreens tab, for each of the different subscreen areas like LGN_TAB_SUBSC_AREA , NOTIF_SUBSCR_AREA , OPER_SUBSCR_AREA, COMP_SUBSCR_AREA, FAST_SUBSCR_AREA link your own subscreen areas (created in step 1) that enables you to maintain your specific log notification data in each of these subscreen areas.
- After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this BAdI have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the BAdI implementation and choose Create.
- The system displays the initial screen for creating BAdI implementations.
- On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, the system populates the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the BAdI to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the method
<Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
- Note: You can also create an implementation for a BAdI and not activate it until later. If you want to do this, do not perform the following step:
- Choose Activate.
- The code you created is run through, when the application program is executed.
See also
Interface : IF_EX_LGN_SUBSCR_ACL
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | LGN_SUBSCR_ACL | 0 | KA50002490 | R/3 Log Book |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20040412 |
SAP Release Created in | 500 |