Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

EXIT_SAPLAIB5_001 -

EXIT_SAPLAIB5_001 -

ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

EXIT_SAPLAIB5_001

Using a Group Currency

For BW Reporting and SEM-BPS planning across controlling areas in Corporate Investment Management, you can introduce a group currency.

You specify the group currency, and the exchange rate type for possible currency translations, in function module EXIT_SAPLAIB5_001.

Update of InfoCube 0IMFA_1 in BW

The DataSources supply values from R/3 in controlling area currency and in object currency. The distinction between the two is made in the InfoObject 0CURTYPE. When InfoCube 0IMFA_1 is updated from the DataSources, and the currency is the same as the group currency, the system updates the values in controlling area currency or object currency as group currency (0CURTYPE = 30). If the group currency is identical to neither the controlling area currency nor the object currency, then the controlling area currency is translated into the group currency.

Pushback of values from SEM-BPS to R/3

When values are pushed back from SEM-BPS to the R/3 Systems, and the currency for the pushback is neither the controlling area currency nor the object currency of the R/3 object, then the system translates the group currency back into the controlling area currency.

Special Considerations when Using Group Currency

Before transaction data can be loaded to InfoCube 0IMFA_1, the master data of all posted InfoObjects has to be loaded into BW. You also have to make sure that there is no limitation to a given currency type in the InfoPackages for the DataSources

The key date for the currency translation is determined for each transferred record by the following sequence of InfoObjects:

0FISCPER
0FISCYEAR
0APPR_YEAR

The system always uses the first calendar day of the given period for the currency translation. If one of these InfoObjects is not in the DataSource, or its value is blank or 0, then the system uses the next InfoObject in the sequence. If the system cannot determine a key date using this logic, then the currency translation is made using the current date.

Programming EXIT_SAPLAIB5_001

You copy the sample coding in INCLUDE LXAIBF02 as a reference for programming EXIT_SAPLAIB5_001. Make the necessary settings for the group currency using the export parameters of the function module:

ED_GROUP_CURRENCY (mandatory setting)

You use this parameter to specify the group currency.

ED_RATE_TYPE (mandatory setting)

This parameter determines the exchange rate type for the currency translation.

EFLG_NO_INSERT_COA_CURT (optional)

If this flag is set, the values in controlling area currency are not transferred to the InfoCube.

EFLG_NO_INSERT_OBJ_CURT (optional)

If this flag is set, the values in object area currency are not transferred to the InfoCube.

EFLG_ALWAYS_CONV_FROM_COA_CURR (optional)

If this flag is set, the system always translates from the controlling area currency into the group currency. Values in the object currency do not have to be loaded using the DataSources. In addition, the master data of the posted InfoObjects is not read in order to determine the object currency.






General Data in Customer Master   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3519 Date: 20211201 Time: 011324     sap01-206 ( 70 ms )