Ansicht
Dokumentation
EXIT_SAPMGPLV_010 -
BAL Application Log Documentation Vendor Master (General Section)This documentation is copyright by SAP AG.
Functionality
Customer exit allowing changes to plan data selected by transaction KP97 (Copy Planning) and KP98 (Copy Actual to Plan). In this way, the customer can enhance the standard R/3 System to some extent.
Interface Description of the Module
The interface consists of three parameters, I_PARX, I_CURSW, and T_KPLV1.
The first two parameters supply useful additional information; the third deals with the actual changing of plan data in table parameter T_KPLV1.
- The field I_PARX holds the relevant control parameters for the transaction and the copying transaction:
| Field Name | Description |
|---|---|
| FLG_MODUS | Indicator: Type of Copying |
| P: Copy Planning (KP97) | |
| A: Copy Actual to Plan (KP98) | |
| KOKRS | Controlling Area |
| VRGNG | Planning Transaction |
| FLG_TEST | Indicator: Test Run |
| X: Test Run | |
| : Real Procesing Run | |
| FLG_UPDATE | Indicator |
| X: Reset and Overwrite Data | |
| : No Changes to Data | |
| SGJAHR | Reference: Fiscal Year |
| SPERAB | Reference: First Period |
| SPERBI | Reference: Last Period |
| SVERSN | Reference: Version |
| TGJAHR | Target: Fiscal Year |
| TPERAB | Target: First Period |
| TPERBI | Target: Last Period |
| TVERSN | Target: Version |
- Parameter I_CURSW stores the leading currency. This currency serves as the basis for translation (such as for object currency).
T: Transaction Currency
C: Controlling Area Currency
- Table T_KPLV1 holds the plan and actual records read and refers to structure RKPLV1
in DDIC. This holds exact descriptions of the individual fields. Please note that all changes in this table can be passed to the planning interface and can be posted there.
Example
To demonstrate access and handling, include LXPLVF01 for transaction KP98 (Copy Actual to Plan) has sample program code for the following functions:
- Collect given cost elements in a single cost element (routine Costelements_Collect).
- Estimate the average of a period interval for other given periods (routine Periods_Extrapolate).
The program code includes explanatory commentary as well.
Routine Costelements_Collect
The routine in planning for a given fiscal year gathers multiple cost elements in actual as plan cost elements using the following table:
| Actual | Plan | |
|---|---|---|
| 416400 | 416999 | |
| 416500 | 416999 | |
| 420000 | 420999 | |
| 421000 | 420999 | |
| 422000 | 420999 | |
| 430000 | 430000 |
Routine Periods_Extrapolate
You want to estimate data for periods 10 through 12.
To do so, you calculate averages for each cost element based on periods 1 through 9. Afterwards, the R/3 System deletes the value fields from periods 1 through 9 and distributes the average values onto 10 through 12.
Notes
In the following example, the abbreviations in the pointed brackets represent your own entries.
To test the sample code above, create cost center
Create cost element group CE_KOAGRP1 in the Cost and Revenue Element Accounting component (CO-OM-CEL). Attach groups
| Group | Values |
|---|---|
| 416400 | |
| 416500 | |
| 420000 | |
| 421000 | |
| 422000 | |
| 430000 |
For each group, choose Extras -> Report info... to create representative values. For
Start KP98 with cost center
Further information
For more information, see the commentary in the program code for the example.
BAL_S_LOG - Application Log: Log header data ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 6727 Date: 20240424 Time: 035154 sap01-206 ( 58 ms )
