PS:: CJ606 Error While Creating Coding Mask/Project C...

[#1]

Hello Experts,

We are working on a Bluefield migration project and need to migrate SAP PS coding mask configuration from an independent development system (let's say Y) to our ED S/4HANA landscape.

Currently, coding mask starting with prj ID 'V' already exists in our landscape, and there are active projects in QA and Production that use this coding mask.

In system Y, coding masks (PrjID) such as VA0SA, VA0SB, etc. exist.

While trying to manually create coding mask VA0SA in the ED system, SAP raises the following error: CJ606 - Entry V already exists

Based on SAP Note 482427 and SAP standard behavior, this seems to be because V is a prefix of VA0SA. My understanding is that SAP does not allow the creation of a coding mask when an existing coding mask is a prefix of the new one.

Since there are active projects in QA and Production that use coding mask V, deleting this coding mask is not an option.

Questions:

1. Has anyone successfully introduced coding masks such as VA0SA in a landscape where coding mask V already exists and is being used by active projects?
2. Is there any SAP-supported migration approach for this scenario?
3. Can coding mask V be retired while still preserving the ability to maintain existing projects?
4. Are there any SAP Notes, best practices, or Bluefield migration recommendations for handling such coding mask conflicts?
5. Is there any supported workaround other than redesigning the coding mask structure?

Any insights or experiences would be greatly appreciated.

Thank you.

[Shubham_Srivastava1]

• Identify all projects and WBS elements in DEV, QA, and Production that reference PrjID V using transaction CJ20N and table PROJ (via SE16).
• Run report ZZADJUSTPOSID (from Note 453280) in test mode to evaluate whether existing V-based project numbers can be consistently realigned. 
• Consider whether the V projects can be archived or closed before the migration window, which would allow standard deletion of the mask in OPSJ per Note 1650931

[rombase]

here are a few active projects in Production using the "V" coding mask that will remain open beyond the migration window, with some projects expected to continue until 2030. One option considered was changing the Project ID prefix from "V" to another value and then deleting the "V" coding mask. However, there are two key constraints: It needs to be verified whether SAP allows mass changes to Project IDs for existing saved projects. If feasible, a custom program would likely be required. The ZZADJUSTPOSID program can be used to adjust coding masks for inconsistent data; however, in this case the project data is consistent, so the program does not allow the change. Therefore, an alternative workaround or enhancement would need to be explored. It is also not yet confirmed whether SAP supports this type of change for active projects. Existing WBS references in PRs, POs, Sales Orders, and other transactions would be impacted and may require updates. Account assignments may need to be reassigned to the new WBS elements, and a detailed impact assessment would be required to identify the effect on open commitments, reporting, interfaces, and related business processes. However, since only around 10 projects in Production are currently using this coding mask, the scope of change is relatively small, making the required updates comparatively easier to manage. that's what I am thinking right now.

[Shubham_Srivastava1]

This looks a feasible approach @rombase