The scope COPA Netback, iCare, exchange rate queries they are not an application but they are queries based in SAP CO module and exchange rate information in SAP. They have been create in WBP in the context of PQ1 Decommissioning project. |
For these queries the access is provided based on the BW menu and it's done via Service one. |
Target Users: BW COPA Netback query (Core Query) => SodaAsh GBU Controllers. |
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 14.08.2023 | Inês Vilares | Initial draft |
|
In the context of our business operations, these 2 queries are based on the Profit and Loss scope, so to understand in more detail this part please check in the respective functional documentation. Regarding the COPA Netback process, the purpose is to utilize the same framework as our Profit and Loss scope to generate reports on the GBU SodaAsh side. The primary objective here is to reallocate sales made by trading entities by Solvay, identifying Solvay customers, and ensuring the accuracy of customer information. The ultimate aim is to maintain the cleanest and most accurate data possible. For this process, they make use of our COPA information, and on their side they use the Dataiku tool to manipulate this data, ultimately generating a file referred to as 'COPAG' containing the necessary information. The file will offer a substantial amount of data that has been meticulously processed by Dataiku to ensure that they are working with the most precise and accurate data for their specific objectives. This approach was necessitated by the fact that our initial queries from the Profit and Loss side did not fully meet the requirement of providing the cleanest data pertaining to the costs associated with SodaAsh. Furthermore, it enables the analysis for specific cases as in the United States concerning the payment of royalties to certain companies that own lands, where a percentage of the Netback is associated with trona mineral (comprising 65% SodaAsh and 35% bicarbonate). For the iCare (to be checked) |
The exchange rates are a critical concept in SAP especially in the context of multinational businesses or organizations that conduct transactions in multiple currencies. SAP provides robust functionality for managing exchange rates, and here's an overview of how exchange rates work within the SAP system: Exchange Rate Types: SAP allows you to define multiple exchange rate types to accommodate various scenarios. Exchange rate types are categorized based on their use, such as buying rates, selling rates, or average rates. Common exchange rate types in SAP include "M" (average), "B" (bank buying), and "G" (group buying). Exchange Rate Sources: SAP supports different sources for obtaining exchange rates, including manual entry, automatic update from external sources, or user-defined calculation methods. Exchange rates can be maintained in the system's tables or retrieved from external systems. Currency Types: SAP supports various currency types, such as local currency, group currency, and parallel currencies. These currency types allow you to represent financial data in multiple currencies simultaneously. Exchange Rate Tables: Exchange rates in SAP are stored in exchange rate tables (e.g., TCURR) that capture rates for different currency pairs, rate types, and validity periods. You can maintain these rates manually or use interfaces to update rates automatically. Currency Conversion: Currency conversion in SAP involves converting financial transactions from one currency to another based on defined exchange rates. This process allows you to report financial data in a consistent currency, even when transactions occur in different currencies. Exchange Rate Determination: SAP determines which exchange rate to use based on factors like the transaction currency, local currency, exchange rate type, and validity date. The system selects the appropriate rate for currency conversion automatically. Document Currency: In SAP, each financial document is typically recorded in a document currency. The document currency is the currency in which the transaction is originally recorded, and exchange rate conversion may be necessary to report it in other currencies. Parallel Currencies: SAP allows you to define and maintain parallel currencies, enabling you to report financial data in multiple currencies simultaneously. This is valuable for internal and external financial reporting requirements. Currency Translation: SAP enables the translation of financial statements and balances from one currency to another, helping multinational organizations prepare consolidated financial reports in a common currency. Automatic Currency Conversion: SAP can automatically perform currency conversion during data entry, reporting, and posting, ensuring that financial data remains consistent across different currencies. Exchange Rate Differences: SAP also handles exchange rate differences that may arise due to fluctuations in exchange rates between transaction dates and settlement dates. These differences are recorded as accounting entries. Exchange Rate Update: SAP allows for periodic updates of exchange rates to reflect real-world fluctuations. You can define update frequencies and methods for currency exchange rates. In summary, exchange rates in SAP are a fundamental component of managing financial transactions in a global business environment. SAP provides comprehensive tools and functionality to define, maintain, and use exchange rates, ensuring accurate and consistent currency conversion and financial reporting across various currencies. For solvay this will always depend on the scope for each company to have this definition for exchange rates. We also have a dedicated wiki Exchange rates explaining all the available exchange rates in WBP, currencies, frequency, among other informations to be aligned with the information from SAP and BFC side. |
For this scope we will describe the queries since we don't have workbooks.
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| BW - BFC YTD Exchange Rate Monthly (Core Query) | The reports contains the information about exchange rate types and currency types for the calendar day range as per the selected criteria. | Mandatory fields:
Optional:
| NA | BW_QRY_DAFICE01_0002 |
| BW COPA Netback query (Core Query) | This report has been adapted to provide the required information and formatting for the GBU SodaAsh team's use in generating their final report. It includes specific data from the Profit and Loss (P&L) dataset, sharing similar characteristics. | Mandatory fields:
Optional:
| NA | BW_QRY_MVCOPA01_NETBACK_0001 |
| BW ICARE Query | Ask Charlotte | Mandatory fields:
Optional:
| NA | BW_QRY_MVCOPA01_0016 |
This section will approach the concepts/definitions that will be used in all the reports and required to understand the data from the reports.
Could be specific fields, closing activities, additional information to work and understand the reports.
| Domain | Finance |
|---|---|
| Application | NA since it's only queries |
| Provider | MVCOPA01 and DAFICE01 (for exchange rate) |
In this section we will approach each query:
|
This query contains the information about all the exchange rates types, the existent currencies (from ->to) and the exchange rate used depending on the selected month. In here the users can check which currency and value were used to a specific month for other calculations in other queries in BW.
As mentioned in the business process ssection we have more detail information about all the exchange rates regarding the frequency, source, loads, etc.
As already mentioned this is a specific query for the requirements on GBU SodaAsh side.
In the technical documentation we have more detail information regarding the source of each key figure/measures designed for this query. For the characteristics that can be used in the reports they are similar from the P&L structure.
US special case: to be checked.
5.6 Scalability
5.7 Compatibility
5.8 Availability
5.9 Refresh of the Data
COPA and iCare queries:
Exchange rate query: