12-26-2019 11:38 AM - edited 02-04-2024 12:09 AM
Hi
A customer S/4HANA Cloud MTE is asking their partner for migration of historical data (10 years ) to their new S4HC MTE system.
i know this is not recommended approach
i want help in getting any documentation that explains is this is possible in MTE? and if this is not advisable and why?
to help explain to the customer why this is not a recommended approach
Many thanks
Marise
Hi Marise,
I suppose, from a mere technical perspective it would be possible and it might even be supported through the general SAP support agreements and through database extension/addition provisions customers can purchase for their MTE if needed be.
The question is more, what's the purpose here? Why would this customer want to have 10 years worth of legacy data, many of which may not have any operational value whatsoever, in their operational cloud ERP system? What is the business value they are trying to get out of these data? There may be multiple answers to that question.
If they are trying to analyze those data, e.g. with machine learning, or otherwise, they may be better off with a data lake, or with structured storage solutions which are mostly decoupled from business operations.
If the purpose was more oriented towards compliance and audit capabilities, nearline storage, offline storage, and archiving systems may be more appropriate and cost conscious. SAP HANA, while being quite efficient in data storage, is meant for "hot" in-memory computing for live or near real-time operations and analytics, and comparatively expensive. Near-line or offline storage and archiving solutions are much less expensive, but upon data request may need some time to automatically (nearline) or manually trigger re-loading of data to the processing units.
SAP may have some dedicated services available for such nearline or offline/archiving use cases. I'd be happy to help you inquire on those, if you like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm working on that, Marise. For now I learned, with Sandra's help, the regular data migration is the way to go for customers to get their historic data in. Now they would want to distinguish in hot and cold data: In S/4HANA on premise, "data aging" is available as a Business Function which needs to be switched on in the switch framework. I'm currently trying to find out if this data aging function is also available in the cloud essentials. Please stay tuned.
In the meantime, I'm posting here the business and use case considerations behind this partner request:
• Why does the customer need historical data in their system? For what purpose (legal reporting, balance sheet comparison, create some predictive analysis, …..):
They need Historical data for Legal reporting , Controlling Authority , balance sheet comparison , P&L analysis
• What data is needed for each use case (high level at this point):
General Ledger Accounts ( Transactions data – Trial balance , etc.. )
Accounts Payables ( Transactions data – Vendor aging – Vendor payment history – Open and close invoices each period – list of vendor advance , etc… )
Accounts Receivables ( Transactions data – Customer aging – Customer payment history – Open and close invoices each period – list of Customer advance , etc… )
Asset Accounting ( Asset transaction – Acquisition – Retirement – Disposal – Sales with value – Scraping – Asset history sheet – Asset depreciation– etc …)
Bank and Cash management ( Bank balances periodically – bank transactions in details to vendors / to employees / from customers / to and from others – etc ..)
Property Management ( Leasing contract details – Custom deposit – Revenue for each unit – Expenses for each unit - Profitabily for each unit – etc.. )
Human Resources ( Employees data center – History change for each employee – Employee benefits in monthly basis – employee deduction – Employee business travel- etc ..)
The main point for business now, after Go-Live they will shut down Oracle and they need all transaction data and balances for all the above submodules available in SAP
Here are some further insights I was able to gather from our subject matter experts:
- If customers have legal reasons to keep data accessible for audits, it is very likely that they also have a need to ensure that access is limited to a very restricted number of people, and that data cannot technically be modified. Data Aging does not help you block / limit data access; or technically ensure immutability of data. This requirement is typically covered by data archiving. And generally, archived data can be accessed for typical auditing purposes, single item access. It cannot be used reasonably in reporting contexts – however, that is also not realistic with data aging.
- It is not possible to migrate/move data directly into “aging historical data” – it first needs to be loaded regularly into the system and might then be aged. Best practice would be, however, to archive any data not required for regular system operations before a migration to S/4HANA.
So overall, for the direct request, Data Aging is not a solution, neither technically nor strategically.
Many Thanks Andreas And Sandra
both answers are very helpful and the links are very useful
Based on below i will take it up with the customer
HAPPY NEW YEAR 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi marisesfeir , we're facing the same issue you mentioned and the answer andreas.muno gave is really interesting and complete. Just wondering if you have investigated about the last part of his answer "SAP may have some dedicated services available for such nearline or offline/archiving use cases."
Thanks!
additional information:
Migration on SAP Help Portal has very rich content: https://help.sap.com/viewer/d5699934e7004d048c4801b552f3b013/1911.500/en-US
Quarter migration newsletter Direct Link: https://www.sap.com/documents/2019/11/706de8c5-737d-0010-87a3-c30de2ffd8ff.html
All Migration related Newsletters are also available via SAP Help Portal: https://help.sap.com/S4_CE_DM → News → Data Migration Content Newsletter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
fully agree with all the previous comments from Andreas.
For MTE , below links for data migration KBA's, where you find what has been our point of view and guidelines for historical migration - only finance historical balances.
There are technical restrictions as well why we don't enable a full historical migration.
https://launchpad.support.sap.com/#/notes/2538700 - Collective SAP Note and FAQ for SAP S/4HANA Migration Cockpit (Cloud)
https://launchpad.support.sap.com/#/notes/2587192 - Migration of historical balances to SAP S/4HANA and SAP S/4HANA Cloud
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
6 | |
5 | |
5 | |
5 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.