Ansicht
Dokumentation
FINS_ACDOC_UTIL_SET_CURR_KEYS - Filling Currency Keys and Moving Amounts into ACDOCA
ABAP Short Reference TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Purpose
You use this report to update existing transactional data with the currency key for new additional currencies in a test system.
The reason for using this report is that there is no standard function available to introduce new currencies in a client that has already been used in a production environment. This means that if you assign a new currency type to a combination of company code and a ledger, your client’s settings become inconsistent as the existing transaction data do not contain this currency. This report enables you to get the client’s settings consistent from a technical point of view. From a business perspective, the amounts in the new currencies are not consistent as the report does not perform a currency conversion into the new target currency. The amount of the new currency will be set to zero in the existing journal.
If, however, the new currency key is identical with another configured currency for this particular combination of company code and ledger, no currency conversion is needed as all line items already contain the target currency. In this case the amount will be copied to the amount field of the new currency.
General Restrictions
The report can process currency types which are neither FI relevant nor CO relevant, that is currencies that are neither written into document table BSEG nor CO currency types.
If you assign a new currency type to a company code and a ledger and don’t update existing transactional data with this report, you can’t clear these documents or do partial payments.
Normally, the report does not fill the amount of the new currency. If the new currency type has a currency key that does not exist in the posted transactional data, only the currency key will be updated and the amount will be set to zero.
In the above mentioned exceptional case where the new currency key is identical with another currency key for this combination of ledger and company code, the report fills the amount of the new currency type, if possible, by copying it from the amount field of the already existing currency key. This amount can be different from the amount which would be calculated in the transaction, as the currency conversion settings (the exchange rate type, for example) might be different.
Table “Universal Journal Entry Line Items” (ACDOCA)
The currency key of the new currency type is filled into the existing entries of table ACDOCA.
The currency key is filled whether or not the amount can be filled.
The report analyzes the currency information in the existing ACDOCA entries and in the Customizing tables of the currency configuration. If the report finds an amount for a currency type which can be copied into the amount field of the new currency type, it copies the amount into this field.
Rules for finding the correct source amount field
If in the Customizing activity “Company Code Setting for the Ledger” (transaction FINSC_LEDGER) the “Real-Time Conversion” option is not active, the following rules apply:
- If the source currency type corresponds to the transaction currency (currency type “00”), the report can’t identify any source currency amount field and the amount field of the new currency type remains zero.
- If the direct source currency type has the same currency key as the currency key of the new currency type, the amount from that field is copied to the amount field of the new currency type.
- If the currency key of the direct source currency type is not identical with the currency key of the new currency type, the amount field of the new currency type remains zero
If the “Real-Time Conversion” option is active, the following rules apply:
-
The report determines the source currency type by analyzing other source currency types belonging to the given combination of ledger and company code.
If the currency key of the source currency type differs from the currency key of the new currency type, the report looks at the source currency type of the next source currency type in order to find the same currency key. If no suitable combination with the correct currency key can be found, the report moves on to the next source currency type until it finds the correct currency key. If this is not possible or if the source currency type is “00” (transaction currency), the search process continues with the next step. - If no currency type can be determined using the step above, copy the amount from the amount field of currency type 10 (company code currency), if it has the currency key of the new currency type.
- If still no currency type can be determined, copy the amount of one randomly determined currency type, for which real-time conversion is active and which has the currency key of the new currency type.
- If still no currency type can be determined, copy the amount of one randomly determined currency type, for which real-time conversion is not active and which has the currency key of the new currency type.
Limitations and Restrictions
The report is restricted to new currency types that are not FI relevant (meaning that they are not updated into table BSEG).
An amount of a new currency type that has been copied from another amount can be different from an amount that is calculated using currency conversion during transactional processing. This report only copies the amount from a source currency amount field without changing it. However, the transactional currency conversion considers the configuration attributes exchange rate type and translation date type specified in transaction “Define Settings for Ledgers and Currency Type” (FINSC_LEDGER).
Table “Splitting Information of Open Item Values” (FAGL_SPLINFO_VAL)
With the currency key of the new currency type, for each existing entry of a journal entry a new entry is inserted into table “Splitting Information of Open Item Values” (FAGL_SPLINFO_VAL).
The new entry always contains the currency key. If the amount can be filled, it is filled based on an existing entry.
The report analyzes the currency information in the existing FAGL_SPLINFO_VAL entries and in the Customizing tables of the currency configuration. If it finds an amount for a currency type which can be copied into the amount field of the new entry of the new currency type, it copies the amount into this field.
Rules for finding the correct source amount field
For table “Splitting Information of Open Item Values”, the same rules apply as for table “Universal Journal Entry Line Items” (ACDOCA) (see above).
Limitations
The same limitations and restrictions apply as for table “Universal Journal Entry Line Items” (ACDOCA) (see above).
Tables filled by the Foreign Currency Valuation (BSBW, FAGL_BSBW_HISTRY, FAGL_BSBW_HISTLG, and FAGL_BSBW_HST_BL)
With the currency key of the new currency type, for each existing entry of a journal entry a new entry is inserted into the foreign currency table (BSBW, FAGL_BSBW_HISTRY, FAGL_BSBW_HISTLG, and FAGL_BSBW_HST_BL).
A new entry is inserted if the amount can be filled based on an existing entry. If this is not possible, no new entry will be added. This behavior is different from the table Splitting Information of Open Item Values (FAGL_SPLINFO_VAL) (see above).
The report analyzes the currency information in the existing entries of the tables filled by the foreign currency valuation and in the Customizing tables of the currency configuration. If the report finds an amount for a currency type which can be copied into the amount field of the new entry of the new currency type, it copies the amount into this field.
Rules for finding the correct source amount field
The rules for finding the correct source amount fields for tables filled by the foreign currency valuation are different from the rule for the other tables handled by this report. The report has to follow the same rules as the foreign currency valuation run (transaction FAGL_FCV). This means that new entries are created only if the direct source currency type has the same currency key as the new currency type. Furthermore, the source currency type must not be identical with the transaction currency (currency type “00”).
Limitations
The report is restricted to new currency types which are not written into document table BSEG only.
An amount of a new currency type that was copied from another amount can differ from the amount that is calculated by currency conversion during the foreign currency valuation (transaction FAGL_FCV). The report only copies the amount from a source currency amount field without changing it. However, the foreign currency valuation considers the configuration attributes exchange rate type and translation date type specified in transaction “Define Settings for Ledgers and Currency Type” (FINSC_LEDGER).
Table “Realized foreign currency differences in additional currency” (BSE_CLR_RDIFF)
With the currency key of the new currency type, for each existing entry of a journal entry a new entry is inserted into table “Realized foreign currency differences in additional currency” (BSE_CLR_RDIFF).
A new entry is inserted if the amount can be filled based on an existing entry. If this is not possible, no new entry will be added. This behavior is different from table “Splitting Information of Open Item Values” (FAGL_SPLINFO_VAL) (see above).
Rules for finding the correct source amount field
For table “Realized foreign currency differences in additional currency”, the same rules apply as for table ”Universal Journal Entry Line Items” (ACDOCA) (see above).
Limitations
The report is restricted to new currency types which are not written into document table BSEG only.
An amount of a new currency type that was copied from another amount can differ from the amount which is calculated by currency conversion during the clearing process. The clearing process calculates the amounts in all local currencies based on the historic exchange rates of the cleared document. This report only copies the amount from a source currency amount field without changing it. Performing a currency conversion during the clearing process means using historic exchange rates. The historic exchange rates are based on the configuration attributes exchange rate type and translation date type specified in transaction “Define Settings for Ledgers and Currency Type” (FINSC_LEDGER). This means that there can be differences with regard to the amounts calculated during the transactional clearing process.
Prerequisites
Features
Selection
Standard Variants
Output
The report creates an application log (transaction SLG1) and shows the application log as an output list.
The application log contains the values of all selection parameters as well as the number of updates and inserts of each database table.
Activities
Example
General Material Data TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 12209 Date: 20240520 Time: 060336 sap01-206 ( 274 ms )
