Hierarchy
⤷ CA-GTF-TS-PPM (Application Component) Batch-Oriented Parallel Processing of Mass Data
⤷ BANK_PP_JOBCTRL (Package) Parallel Processing and Job Control
IMG Activity
ID | _PPM_RUN_HISTORY_BD | BAdI: Create History of Mass Run Data |
Transaction Code | S_ABA_72000155 | (empty) |
Created on | 20030911 | |
Customizing Attributes | _PPM_RUN_HISTORY_BD | BAdI: Create History of Mass Run Data |
Customizing Activity | _PPM_RUN_HISTORY_BD | BAdI: Create History of Mass Run Data |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BANK_PP_RUN_HISTORY |
Use
This Business Add-In (BAdI) is used in the Batch-Oriented Parallel Processing of Mass Data (CA-GTF-TS-PPM) component.
Using this BAdI you can create a history of the relevant control data of a mass run. This includes the call-up parameters, number of starts of a run or the current processing status.
The BAdI does not affect the application or other IMG activities as it used exclusively for transferring control data for creating a history.
The BAdI methods are called at different times during the process flow of the mass run (see the description of the methods).
Requirements
Standard settings
In the standard system delivered, the BAdI is active. There is no default coding.
The Business Add-In can be used more than once. All active implementations are called up and executed.
The Business Add-In is not filter-independent.
Activities
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
See also
Methods
Create history of header data of a mass run
Create history of infos for executing a mass run
Status transition within a level
Initialize history for mass run
Interfaces
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030911 |
SAP Release Created in | 640 |