SAP S/4 HANA 1709 – Part IV – Custom Business Transaction Types
Further to our previous post, we would like to let you know about a new feature introduced in 1709.
In the new release of SAP S/4HANA 1709 a new feature is introduced by SAP which is intended to help improve financial reporting. The feature contains new Custom Business Transactions. Lets see how it helps.
Custom Business Transaction Types
This feature enables us to improve the classification of journal entry items based on the type of business transaction that triggers a journal entry posting. This results in more detailed insights into the origin of financial KPIs. This feature has been implemented in the following ways:
- The SAP standard method of deriving business transaction types has been enhanced to provide more details for Financial Accounting transactions that have used business transaction type RFBU (FI Postings) in the past
- In addition, you can define and derive your own business transaction types
We can use the business transaction type to break down KPIs or amounts in analytics according to the types of business transactions that trigger journal entry postings. While sufficiently detailed business transaction types have been available for Logistics and Controlling, many Financial Accounting transactions have used business transaction type RFBU (FI Postings) in the past. In order to get at least some information about the origin of Financial Accounting data, you had to use the document type or the transaction code (at document header level) as a workaround.
Now, transaction types such as Incoming Payment, Outgoing Credit Memo, or Foreign Currency Valuation are also available for Financial Accounting transactions. In addition, you can create your own business transaction types if you don’t want to use the standard method of deriving the business transaction type.
The improved method only impacts journal entries that have been posted after the new business transaction type was introduced.
Business transaction type ACDOCA-BTTYPE was designed for reporting purposes. Please note that SAP will not guarantee the stability of BTTYPE values. Existing business transaction type values may be replaced by new values in the future.
If you need to create coding based on this business transaction type, you should use the transaction type for general ledger (ACDOCA-VORGN) instead, which is still filled with the standard SAP values (for example, RFBU) that were used before this enhancement and will remain stable
Define your own business transaction types using Customizing activity
Financial Accounting > Financial Accounting Global Settings > Document > Maintain Business Transaction Types
This new feature will help in custom reports where we will be able to identify the transaction based on business transaction type within FI Module. This feature may have impact on the existing custom reports. Hence, it will be important to identify the custom reports where this field was used and logic is defined based on RFBU.