Professional Documents
Culture Documents
Release Info Note Automatic Account Determ S4 Hana 1908
Release Info Note Automatic Account Determ S4 Hana 1908
Symptom
This is the collective SAP Note for the Fiori app Automatic Account Determination for S/4 HANA Cloud 1908
release. This note provides references to related notes and information about specific limitations. This note is
subject to change. Make sure to check it on regular basis.
Other Terms
• You can ONLY use this app to configure your account assignments.
In other words, you cannot use the app to configure anything irrelevant to accounts.
• You can ONLY use this app after you have activated SAP content.
After activation, SAP content will be written into the configuration tables. And only then, can you use this
app to change the settings according to your business needs. The changes will be written into both
database and SAP content.
• Only in your Q (Test) system, can you use this app to maintain the account assignments.
That is because changing account assignments is very critical. The changes must be tested first before
being transported into P system.
• Starting from 1902, you will have the app in read-only mode in P system.
Starting from 1902, you can open this app in your P system and check whether your latest changes have
been transported from your Q system. Important to know that the app is read-only in P system. You
cannot make any change there.
• Assign your user to business role ‘SAP_BR_BPC_EXPERT' and log into the Launchpad with your
user.
• Hit ‘Manage Your Solution’, and in the coming page make sure you are in the right phase. In Q
system, it shall be ‘Realize’ phase, and in P system it shall be 'Deploy' or 'Run' phase.
• Hit ‘Configure Your Solution’, and in the next page, find the app with the following search conditions:
• Application Area: Finance
• Sub Application Area: General Ledger.
• With the search conditions above, you will get a list of Configuration Items. Choose the line with '
Chart of Accounts' in Item Name. You will get a list of 'Configuration Steps'. Find the line with
SSCUI ID 100297. That is the right app.
• Alternatively, it will be much easier for you to find the app by entering 100297 directly into the search
box at the beginning of 'Configure Your Solution' page.
• Hit the button 'Configure' on the end of this line to get the app launched.
Please note the following functional restrictions when you implement this app.
1. This app is designed for desktop only. Tablet or smart phone is not supported.
2. You can export data into your Excel sheet in the review page of this app. Click on the 'Share' button in the
footer bar. And you will get a menu item called 'Export to MS Excel'. Hit that item and you can get your data
exported. (Please be aware that you are only able to export data which you have got in the search result in
the previous page.)
3. Starting from 1902, the app is available in read-only mode in P system. You will find it much easier to
check if your changes have been transported to P or not. Just enter the same search criteria as you do in Q
system, and then you can check the settings in Step 3. You can go to the review page and export data into
an Excel file too.
4. Starting from 1908, if a business partner is being blocked, it cannot be entered in (and only in)
customer-owned condition tables in SD area.
5. In current release, the app supports the following G/L account assignments. (*) items are new or
adjusted in since last release.
• Controlling
• Cost Center Accounting
• Assign Intercompany Clearing Accounts for Actual Postings
transaction keys:
• B03: Flat-rate Individual Value Adjustment
• RKK: Provisions/Recs/Payables: Adjust. Acct
• ZKB: Provisions/Recs/Payables: Discount Exp.
• ZKK: Provisions/Recs/Payables: Discount Tfr.
• Integrate with HR Postings (transaction group HRI), including transaction keys:
• HRA: HR postings, technical accounts
• HRC: HR postings, expense accounts
• HRF: HR postings, financial accounts
• HRD: HR customer postings
• HRK: HR vendor postings
• Prepare Automatic Postings for Foreign Currency Valuation (transaction group FWA), including
transaction keys:
○ KDB: Exch. Rate Diff. using Exch. Rate Key
○ KDF: Exchange Rate Difference for Open Items
○ KDW: Payment Difference for Alternative Currency
○ RDF: Internal Currencies Rounding Differences
• Prepare Intercompany Transactions (transaction group VRB), including transaction keys:
○ BUV: (Clearing between Company Codes)
• Transfer and Sort Receivables and Payables, including transaction groups:
○ BI2 (Receivables/Payables Sorting)
○ BI3 (Changed Reconciliation Accounts)
• Define Accounts for Payment Transactions (transaction group SKN), including transaction keys:
• SKE: Cash discount received
• SKT: Cash discount expenses
• SKV: Cash discount clearing (net method)
• VSK: Lost cash discount (net procedure)
• ZDI: Payment differences by reason
• Define Accounts for Tax Clearing, (transaction group ANZ), including transaction keys:
• MVA: Output Tax Clearing for Down Payment
• VVA: Input Tax Clearing for Down Payment
Technical Limitations:
It is important to know that this app is built on SAP content and its packaging framework. Technical limitations
from SAP content and its packaging framework are reflected in the app too.
The app is built only on new packaging framework, which is used by all WEBGUI SSCUIs. This new
framework has got rid of some limitations in previous BCO framework, for example:
1. For Sales & Distribution area, the pre-delivered SAP content only covers standard condition tables
delivered by SAP in Cloud environment. In other words, SAP content does not cover any of the following
cases:
2. The principle above is applicable to all configurations based on SAP content. In the backend transaction
code '/n/SMB/BBI' (Solution Builder), tables not being supported by SAP content will not be linked to any
content data, or cannot be found at all.
3. Any data that is not defined in SAP content will be rejected by SAP packaging framework. Those error
messages will be populated through the app.
• It is not allowed to change the posting keys or rules for a transaction key.
• It is not allowed to delete any existing record.
• Sometimes, there will be a latency in seconds when you save your changes.
As described above, those technical limitations are from SAP content framework. If they are critical to your
business processes, you can raise customer incidents to content framework team directly. Here are how-tos:
All these limitations from SAP packaging framework are reflected not only in Automatic Account
Determination app, but also in any other native SSCUI (non-Fiori) from SET content.
One typical example is 'Company Code Master Data', which can be found in the following way:
• In the page ‘Configure Your Solution’, enter '100135' into the search box and press ENTER.
• In the 'Configuration Items', hit the line 'Company Codes'.
• Find a configuration entry with SSCUI ID 100135 in the next page, and click on the 'Configure'
button.
You can always check whether an issue occurs also in one of the native SSCUIs. If it is case, it is an
issue from content framework.
In addition, if you have saved you changes in Q system successfully, but you cannot find it in our read-
only app in P system , it must be a transport issue from content framework.
If it is an issue from the app, please create an incident with the component FI-FIO-GL.
Otherwise, please create a customer incident for the component SV-CLD-SSC directly, better with an
example in one of native SSCUIs to ensure the response time of the ticket.
In case of general Q2P issues, please create an incident for the component SV-CLD-FRM-APP.
Solution
For general information regarding S/4 HANA Finance for S/4 HANA Cloud 1908, please refer to the reference
notes for more details.