Bitcoin as Reporting Currency Users of our dab:AnalyticSuite (formerly known as dab:FastForwards) know and appreciate the functionality of the "ReportingCurrency" or the conversion of all relevant currency amounts into a group currency. We use SAP® internal exchange rates and we even allow you to choose between the exchange rate on a specific key date and the exchange rate that was recorded at the time of the document. This results in much greater flexibility when working with the analysis results, especially if you often work with e.g. cross-company-code comparisons with foreign currency transactions.
In this blog post we talk about the question whether vendor bank account data was changed (often). We explain we it is important to get an overview about such changes, and what special aspects come into play when talking about data out of SAP®.
Actually "The Trip to Panama" would have been a better header, but the news desks of the broadcasters beat us to it. Although of course the children's book by Janosch, with the tiny tiger and little bear, has nothing to do with the affair revolving around the letterbox or shell companies of the Panamanian law firm. But the title is just so catchy.
Which topics can be covered by data analytics at all? Why is it worthwhile for example to analyze „Credit Limit Changes“ or „One time accounts (Conto pro Diverse)“? What are the risks that can be identified when performing certain analytics?
In this article, I will describe the topic “Partial Payments” in SAP® Accounts Receivable. We often receive the following questions: “How do we post a partial payment in SAP®?” “Which amount is cleared?” “Is the customer invoice open or cleared after a partial payment?” “Which clearing logic do we have?” Using an example, I will explain how you could manage a partial payment in SAP®.