Ansicht
Dokumentation
UPB_CI_PUSHBACK_IQ - Corporate IM: Pushback of Values to Appropriation Requests
Fill RESBD Structure from EBP Component Structure ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
Functionality
The function module UPB_CI_PUSHBACK_IQ is used to define a planning function of the type exit in SEM-BPS.
This planning function is used to transfer strategic plan values from an SEM planning area to appropriation requests in R/3. Here a division is possible according to investment/expense and different transaction R/3 Systems are possible as targets.
Plan values for any appropriation requests can be transferred into a version and for an approval year per run. A central currency translation and selections to individual fiscal years and according to investment/expense are supported.
(But up to release 4.6C appropriation requests cannot conduct any of the object currency deviating from the controlling area currency.)
Value Transfer Logic
Aggregation regarding Time
The total value in R/3 is considered as the total of
all annual values in SEM. The year 0000 contains - as is usual in BW Content - the value not distributed to years. In R/3 this is the difference from the total value and the total of the annual values.
Zero Values
Since no records are updated with the value zero in SEM-BPS, the system cannot decide between the following possible causes for technical reasons:
- An appropriation request is not in the selection area for the pushback.
- The value should be set to zero in all selected years.
Thus the value of an appropriation request cannot be set to zero in all selected years per pushback.
In this case in SEM-BPS use the smallest possible value as a replacement for the value zero, or set the value zero using the R/3 transaction.
Release Prerequisites
| System Involved | Release |
|---|---|
| Receiving R/3 System | as of release 4.5B and as of plug-in for BW PI2001.1 |
| BW System | as of release 2.1C |
Settings in R/3
The appropriation requests must have a variant assignment for the version and approval year to be transferred. This variant cannot be assigned to any other version. (Tip: In R/3 use the program RAIMAVCY to create new variants for the version of the pushback).
SAP recommends locking the planning versions used for the pushback from SEM in R/3 organizationally for manual planning.
The RFC user must have the necessary authorizations for transaction IMA2N.
Settings in SEM and SEM-BPS
Determining the Exchange Rate Type for the Currency Translation
The exchange rate type for currency translation is defined using the customer enhancement AIBW002. The enhancement is activated using the transaction CMOD. If the planning area is linked to an InfoCube in another BW System using an RFC connection, the enhancement is to be realized in the system of the InfoCube.
Demands on the Planning Level
The planning level for the pushback must contain the following InfoObjects:
| 0APPR_REQU | (The name can be changed per parameter.) |
| 0APPR_YEAR | |
| 0VTYPE | |
| 0VERSION | |
| 0FISCYEAR | |
| 0FISCVARNT | |
| 0CURRENCY | |
| 0AMOUNT | (The name can be changed per parameter.) |
Optionally 0FISCPER can be evaluated by the extractor as time characteristic for currency translation when it is planned according to periods.
Furthermore, planning by investment and expense can take place by using the InfoObject 0CAP_EXP. If the InfoObject 0CAP_EXP is not used, then the values are posted as investments in R/3.
Note:
All of these InfoObjects can only be used in the form delivered by SAP. Changing the type, length or compounding is not allowed.
In addition to that, the planning level can also contain other InfoObjects.
Definition of the Planning Function of the Type Exit
The planning function for pushback is defined as type "Exit function":
| Function Module | Usage |
|---|---|
| UPB_CI_PUSHBACK_INIT | Initialization of planning function |
| UPB_CI_PUSHBACK_IQ | Transferring the values to the R/3 System |
| Parameter Name | Data Element |
| LINOMAIQ | UPB_CI_FLG_APPR_REQU_LIST |
| PLANAREA | UPC_Y_AREA |
| R3SYSTEM | LOGSYSTEM |
| TESTMODE | ADMI_TEST |
| RATETYPE | KURST_CURR |
| REQIOBJN | UPB_CI_IOBJNM_APPR_REQU |
| KYFIOBJN | UPB_CI_IOBJNM_AMOUNT |
Fields to Be Changed
All fields must be transferred as "fields to be changed".
Selections in the Planning Package
Mandatory Selections
The planning package with which the pushback function is executed must deliver (together with the selections in the planning level) a unique selection for the values of the following InfoObjects:
| 0CURRENCY |
| 0VTYPE |
| 0VERSION |
| 0APPR_YEAR. |
Optionally a selection can be made according to years using 0FISCYEAR and investment/expense using 0CAP_EXP.
For Other Selections Note:
The total plan value of an appropriation request for a year must always be contained in the planning package. If instead you would restrict to a period, then in R/3 the total annual plan value would be posted as the value for the period.
Settings in the Parameter Group
Further settings are made in the parameter group of the pushback function.
| Mandatory Settings | |
|---|---|
| Planning Area | Single planning area with the values planned in SEM-BPS |
| Optional Settings | |
| Only display in acc. with app. req. | Output of appropriation requests without R/3 source system |
| Target system ID | Restriction of pushback to an R/3 System |
| Test run | Indicator: Test processing - no locking and writing in R/3 |
| Exchange rate type | Exhange rate type for currency translation |
| IObj. App.Req. | Name of InfoObject for the appropriation requests (default: 0APPR_REQU) |
| IObj. key figure | Name of InfoObject for the key figure (default: 0AMOUNT) |
