To demonstrate how to use SAP S/4HANA’s BAPI ACC DOCUMENT POST to post to only freely defined currencies
What will this blog post teach you, exactly?
This blog post will help you comprehend.
- Using BAPI ACC DOCUMENT POST, posting directly in a freely specified currency is possible by setting the group currency and business code currency to zero.
- Bypassing the system-set exchange rate by posting sums in freely defined currencies. i.e. The user can input a manual amount in
- FD currency regardless of the established exchange rates. The term “FD currency” will henceforth refer to the freely defined currency.
- How to post using FD currency with an asset posting and the effect of fixed assets
Business Scenarios are among the application areas.
- During the month-end and year-end closure processes, pay any outstanding sums resulting from variations in exchange rates translated in freely defined currencies.
- Remove any discrepancies between freely defined currencies brought on by CO allocations.
- When performing cutover in a greenfield or brownfield implementation, use freely defined currencies and disregard exchange rates determined by the system.
- It is also feasible to post in Fixed Assets with Cutover (as seen in the case below), but it is more difficult.
Currency and ledgers
You can construct profit centres in those countries and post all the transactions that correspond to that country with the relevant profit centre if your company code includes branches in multiple countries but you don’t want to create those branches as distinct company codes in SAP S/4HANA. Due to the fact that transactions are occurring in several regions and using various currencies, we have created FD currencies to facilitate reporting and other comparisons.
The number of FD currencies needed will determine how many ledgers need to be created. We are able to assign 7 distinct FD currencies to each ledger. If you require more than seven FD currencies, you must define additional ledgers and assign the FD currencies as necessary. In our instance, 3 ledgers for Local GAAP and 3 ledgers for IFRS have been defined.
The first freely defined currency can only be set as a currency type 40 or 50 and always refers to BSEG currencies (Hard currency and Index based currency). Thus, you are limited to using seven extra currencies in a single ledger. Additional ledgers will need to be set up for the next seven currencies, and so on, if the business requirement is to have reporting in more than seven currencies. The creation of a ledger group and the attachment of all ledgers to it allows for the uniform posting of all ledgers. Since the asset posting will post to all ledgers related to the ledger group/accounting principle combination, fixed asset accounting will also only require one depreciation area for all of these ledgers in this manner.
The example given below shows the creation of six ledgers: 0L, I2, and I3 for IFRS accounting, and L1, L2, and L3 for local GAAP. These ledgers specify and assign a variety of money types.
Defined categories of currency
Definition of Ledgers
FD currencies assigned in each ledger
BAPI ACC DOCUMENT POST
The amount in Transaction Currency, Company Code Currency, and Group Currency will all be zero in this case as we are just passing the value to freely defined currencies.
A fundamental GL entry, as:
Dr. consulting service
In CURRENCYAMOUNT, we typically pass simply the items for each GL entry, but when we need to manually pass the FD currency for a branch, we need to duplicate the rows for each GL item and input the currency type and currency in order to prevent exchange rate gain/loss during cutover.
For this BAPI, the first two rows are those that we typically pass in any accounting entry.
The last two rows with the currency types “Z5” and “BOB” are identical to the first two rows.
The value in ACDOCA only got posted in the ledgers where the currency type “Z5” was declared, in our case, the ledgers I3 (IFRS) and L3 (Local GAAP), as you can see in the screenshot below.
As you can see in the screenshot below, only the FD currency BOB is present in ledger I3 and L3 of FB03, whereas the amounts for transaction currency, local currency, and group currency are all zero.
In this instance, we’ll pass the value to the Transaction Currency and a freely specified currency.
The BAPI’s inputs are identical to those in Case 1 with the exception of the amount passed in Rows 1 and 2.
Unlike example 1, where only two of the six ledgers were present, in ACDOCA all six ledgers are visible since the transaction currency value was posted in each ledger, whereas the FD currency value, BOB, was only put in ledgers I3 and L3.
The value in transaction currency, local currency, group currency, and the FD currency BOB that was passed from BAPI and was not calculated by SAP S/4HANA can all be seen in FB03.
Announcement in Fixed Assets
It is possible to publish documents to an asset with varying values in freely specified currencies. This is not directly achievable in any asset-related transactions, only with a custom software. The freely defined currency in the case below is PEN, but the business code currency is COP (Pesos) (Peruvian Sol). The acquisition value is 1,20,000 in COP and passed as 1,00,000 in PEN (without considering the exchange rate determined at the time of document posting)
- You can create a customised programme and an excel file that includes the freely defined currency fields in addition to the default GL posting template. You can add one or more FD currencies to the template depending on your business’ needs.
- The BAPI can be improved as previously demonstrated, and a unique transaction code can be added to the application.
- After the aforementioned is finished, you will be able to make adjustments in currencies that you want.
- A unique strategy will be required for fixed assets. The technical feasibility of this has been demonstrated in this paper, but the specifics will be detailed in a blog post later.