This blog is aimed to let you know how to solve the DMC error of “Not ready for processing” in the version SAP S/4HANA 2022 FPS0. Hope it will be helpful for you.
Since we adopt the transport concept of migration cockpit in our S/4 project, we create multiple migration cockpit projects and assign the selected standard objects in it, then via LTMOM to generate TR for the transport. So we call those migration cockpit projects as “transported project” in QAS or PRD.
Client modifiable only in Development system:
After we transport the transported projects into QAS, the transported project status changes into “Not ready for processing” from “imported” after the database connection setup.
All the button is grey, we can’t download or upload any load file from the first step, even the “prepare project” job doesn’t been generated and running.
We started the trouble shooting, and found the root caused. The assembly of the SAP S/4HANA 2022 FPS0 is incomplete regarding data migration objects. Here SAP recommends using Note Analyzer to implement the missing/latest notes, and SAP keeps updating the latest notes via Note Analyzer. So we need to check whether the latest notes missing in implementation or not by specific regular time.
Because we use SAP S/4HANA 2022 FPS0 and adopt data migration approach of staging table, here we only implement SAP Note Transport-Based Correction Instructions (TCI) of staging table.
Below are the steps of resolve error “Not ready for processing”:
Step 1 – Implement Important Corrections Note 3291483
Step 2 – Implement TCI Note 3291767
Step 3 – Implement SAP Note 3016862 to get the Note Analyzer
Step 4 – Implement multiple Notes extracted from Note Analyzer
Step 5 – Refer to Note 3094534 to check Stepuser existed with correct security or not in Job Repository (T-code /nsjobrepo)
After all relevant notes implemented and transported, the migration cockpit project status changed into “Ready for Processing”.