Hierarchy
⤷ IS-AD-LBK (Application Component) R/3 Log Book
⤷ DIACL_APP_AD (Package) Logbook: application layer (A&D)
IMG Activity
ID | CNTR_DFLT_ACL | Add-In: Default Counter Update Values |
Transaction Code | S_KA5_12001396 | (empty) |
Created on | 20030109 | |
Customizing Attributes | CNTR_DFLT_ACL | Add-In: Default Counter Update Values |
Customizing Activity | CNTR_DFLT_ACL | Add-In: Default Counter Update Values |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CNTR_DFLT_ACL |
Use
Use this Business Add-In to set default values for counter udpates from the Logbook application.
Requirements
You have defined the counters to be updated via the Logbook application via Logbook Customizing transactions DIACLC1 and DIACLC2.
Standard settings
Activities
Implement method SET_CNTR_DFLT of interface IF_EX_CNTR_DFLT_ACL to set the counter update default values for the counters you made available for update via the Logbook application. For details, see the method documentation.
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In 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 implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated 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 Add-In 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 an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
Assume you have a technical asset (for example, an aircraft) for which you would like to track the fuel consumption. In that case you could make a field available in the log entry to capture the amount of fuel consumed per operation event. On creating the measurement documents for a log entry (updating the counters) your Business Add-In would then default the fuel counter update value with the value entered in the log entry.
See also:
Method
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 | CNTR_DFLT_ACL | 0 | KA50002490 | R/3 Log Book |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030109 |
SAP Release Created in | 471 |