Hello everyone! We are back with yet another post on SAP. This time we will speak about the most spoke about topic “Conversion of SAP ECC to S/4 HANA” Conversion is a step by step process, majorly divided into various stages, or we can say milestones. To start with, let’s first try to understand the various phases that we have to go through during this process. Please note that we will speak about SAP S/4 HANA release 1709 in this post. Pre Conversion Checks Technical Migration (SUM – Software Update Manager) This activity is performed by our BASIS colleagues and is purely technical in nature Preparing Customizing Post Conversion Data Migration Post conversion Post Migration Activities Above activities are to be done at least three times as below: First Mock Run Second Mock Run Final Migration in Production System We will discuss about all of the above in detail in the coming posts. Till then thanks a lot.
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: Additional Details 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 […]
CO-PA Reset Value Fields We all have been looking into flow of values in CO-PA along with their mapping to Value Fields. The mapping helps us store values from various modules into CO-PA. This mapping helps us perform analysis and extract various reports. Going forward, it is important to understand that in every situation, we do not want the values to flow to CO-PA. Or in certain cases, we want only certain values flowing to CO-PA. Resetting Value/Quantity Fields helps in reconciling CO-PA with FI Sales Invoicing As an instance, if we consider Sales Invoicing, with regards to CO-PA mapping, we assign Sales Condition Types to CO-PA Value Fields using Transaction Code KE4I. But, if we look a little deeper, the sales condition types mapped by us to COPA Value Fields, are the same in majority of the billing types. This means for e.g. a Condition Type of MRP “ZMRP” is available in both the sales document types i.e. Normal Sales Invoice, Stock Transfer Invoice and Debit/Credit Note. Now this mapping will every time post value of MRP to COPA value field “VV101” during postings of Sales Invoice, Stock Transfer Invoice and Debit/Credit Notes. The above value pf “MRP” may not be […]
SAP S/4 HANA 1709 – Part IV – Effect on COGS Posting in FI After the previous post, in this part of the series of posts we will try to see the improvements in SAP S/4 HANA 1709 that have Effect on COGS Posting in FI. Splitting the Cost of Goods Sold 1709 has come up with some improvements in recording the cost component split of cost of goods sold in Financial Accounting (FI). Business Add-Ins for Splitting COGS Two Business Add-Ins (BAdIs) are now available for refining the Customizing activity Define Accounts for Splitting the Cost of Goods Sold: Additional Details FCO_COGS_SPLIT_RELEVANCE This BAdI allows you to override the standard COGS splitting logic. For example: FCO_COGS_SPLIT_BASIS With the SAP standard logic for splitting the cost of goods sold, the split must be based on either the unit cost estimate for the sales order item or the standard cost estimate for the material/plant combination. This BAdI enables you to use a different basis for the split. For example, you could use a past or future standard cost estimate or the actual cost estimate of the previous year. Additionally, if no basis for the split was found by the SAP standard […]
SAP S/4HANA 1709 – changes in CO-PA In the previous post, we had gone through some of the changes in various areas. But there is one specific change which impacts FI/CO guys as this change relates to CO-PA i.e. Profitability Analysis. Lets see what has changed and how it will affect us. Changes to Profitability Analysis in Controlling Module Storage and Numbering of Profitability Segments The way in which profitability segments are stored and numbered in the system has been modified. A separate type of profitability segment is now stored in table CE4XXXX_ACCT (XXXX denotes the operating concern). Just as with the profitability segments in table CE4XXXX, those in table CE4XXXX_ACCT assign a unique number to each combination of characteristic values. However, in table CE4XXXX_ACCT a new number is assigned for each new business process. Furthermore, characteristic summarization is not applied to this table. Additional Details Profitability segments contain a combination of characteristic values for a business process to be posted. Each of these combinations is assigned a unique number which is used throughout the system to transfer this information, for example from a billing document to Accounting. The assignment between profitability segment numbers and the corresponding characteristic values is […]
What’s New in SAP S/4HANA 1709? In our previous post, we have learnt about features of the newly introduced SAP S/4 Release 1709. In this post, we will try to look deeper into the new release and try to understand what this new release has in store for us. SAP S/4HANA 1709 has various new improvements introduced as listed below: Maintenance Operations New app “Report and Repair Malfunction” You can use this app to easily report that a technical object has a malfunction, plan the required repair work, as well as document and confirm the maintenance work when it’s done. Three tiles are provided for this app: The Report Malfunction tile for creating malfunction reports, the Manage Malfunction Reports tile that provides a list of malfunction reports that have already been created, and the Repair Malfunctions – My Job List tile that provides a list of all work items assigned to you or to your team. Environment, Health, and Safety Introduction of New Apps “Incidents – Detailed Analysis” With the Incidents – Detailed Analysis app, you can analyze incidents, near misses, and safety observations that have been recorded in incident management. You can use the app to: Incident Management Enhancements […]