Follow these steps to activate the archiving information structure:
Archiving in SAP are executed using transaction SARA t-code.
When i started to join the implementation team for archiving project, there were several important SAP notes we used such as Note no 70547 - Data Archiving: General Information, SAP Note 157944 – Archiving Object-Specific Information and SAP Note 430886 – Archiving in SAP ERP
I come accross this question during my project last time in SAP erp archiving and In SAP, how do I archive financial documents?
The Object: FI DOCUMNT (For archiving FI Documents) in the SARA tcode. Select the Customize button but more analysis required
Object: FI DOCUMNT for archiving FI documents (For archive FI Documents) Choose the Write Option. Put a name for the version and click keep it.
Object: FI DOCUMNT is now used to remove the documents. Select Delete.
The above only helps if you know the fundamental about archiving in SAP , We had integration team who help in this activity.
I notice whenever when archive are being scoped, important tables needs to be identified and when i was searching the below table it was interesting as i could and had gotten it from Early watch alerts documents and also by some guru's in some forums long time ago and can't really remember now.
But In SAP, how can I get a list of tables?
Using the t-code SE16, press f4 on the table name, then click on info system and type * in the table name. I don't have access to SAP right now, however I believe the table DD02T has a list of all the tables. Look at the table with SE16.
These are the SAP Material Management tables
My review of the some of the important note that i took when performing S/4hana migration, below is just brief but there are more to it which you should refer to the SAP guide.
What is SAP's 4HANA migration cockpit, and how does it work?
The SAP S/4HANA migration cockpit makes it easier to move corporate data from one system to another. Migration objects are used by the SAP S/4HANA migration cockpit to identify and transmit important data. A migration object explains how to transfer data from SAP S/4HANA to a specified business object.
The SAP S/4HANA Migration Cockpit aids in the data migration process from SAP/non-SAP systems to SAP S/4HANA using preset migration objects. The source and target structures, as well as relationships and mapping information, are all detailed in the migration object.
SAP Migration Cockpit (SMC) is a new tool from SAP that is integrated into both cloud and on-premises versions of SAP S/4 HANA. It's designed to help with data transformation and loading into SAP S/4 HANA.
The process of shifting data from one system to another is known as data migration. While this may appear to be a simple task, it necessitates a change in storage as well as a database or application. Any data migration will include at least the transform and load steps in the extract/transform/load (ETL) process.
How long does it take to migrate SAP?
depends roughly 10 to 15 months or more depending on type and size
Moving from traditional SAP systems to SAP S/4HANA should take between 10 and 15 months, according to SAP.
Often we think about how SAP Fiori are being license throughout the use of various SAP products. Well for instance Solution Manager has fiori access, SAP Marketing has Fiori access, SAP One Launchpad in SAP Public domain as Fiori user interface.
Now coming to straight to the facts:
It took me a while to understand how the license works and for my environment i managed to find it out but for the rest of component software which uses fiori it might be packaged differently. You may want to check with your SAP contract or account manager.
SAP Fiori is included as part of SAP Gateway license in general that comes along when a customer sign up SAP Netweaver products.
However not only that Fiori access are also bundled in different ways maybe you need to explore with super admin access in SAP one launch pad on LIC tab to see how SAP fiori intergrated and to which product.
Quick information on how to check our SAP product in use license entitlement.
Enter the License Utilization Information Application (LUI) either through SAP ONE Support Launchpad or directly to gain an overview of your company's current licence consumption and licence entitlement.
How do I get to LUI?
The LUI application is currently only accessible to Super Admins.
In order for each S User to have access to the LUI application, the firm Super Amdin must assign the following profiles to them in the SAP One Support Launchpad:
Using Access Licenses in the Cloud
Use of on-premises access licences
Is there really SAP IS-RETAIL Installation software - This is just to give you bit understanding on how it works and where to get the installation files.
Because IS-Retail is an industry solution built on top of an ERP solution, there is no specialised guide. As a result, you must install SAP ERP using the requested release. Check out the SAP ERP installation guide.
You must enable IS-Retail in the switch framework after installing SAP ERP; see "SAP Note 1075202 - FAQ: Setting the Retail Switch" for more information.
When our company decided to move to S/4HANA, I was tasked with preparing our custom ABAP code for the transition. This post walks through how I used the Custom Code Migration Worklist (CCMSIDB) and the Simplification Database to identify, analyze, and remediate legacy code.
Subtopics & Answers:
What is CCMSIDB and why it matters in S/4HANA conversion It’s the engine behind SAP’s Custom Code Migration Worklist, comparing your codebase against the Simplification Database to flag incompatible objects.
Setting up the Simplification Database in NetWeaver 7.5
I downloaded the ZIP file from SAP Marketplace and imported it using SYCM_UPLOAD_SIMPLIFIC_INFO.
Running the Custom Code Analyzer and importing results
I used SYCM_UPLOAD_REPOSITORY_INFO to feed in our code references and usage data.
Interpreting the Worklist output The ALV-style report showed which objects were obsolete, modified, or required attention — with direct links to SAP Notes.
Remediation strategy and collaboration with developers We prioritized high-impact objects and used ATC checks to validate fixes.
Lessons learned from using CCMSIDB It saved us weeks of manual analysis and gave us confidence in our migration readiness.
