cancel
Showing results for 
Search instead for 
Did you mean: 

PS:: CJ606 Error While Creating Coding Mask/Project Coding Key (PrjID)

09-25-2026 4:05 PM
rombase Explorer
34 views 2 comments
0 Likes
SAP Managed Tags
Subscribe

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.

rombase_0-1790345043222.png

 

Thank you.

0 Likes

Accepted Solutions (0)

Answers (2)

Answers (2)

Shubham_Srivastava1
Product and Topic Expert
Product and Topic Expert
0 Likes

 

  • 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

 

Shubham_Srivastava1
Product and Topic Expert
Product and Topic Expert
0 Likes

Review SAP Notes 482427, 1650931, 453280, and 520944 in full via SAP for Me (support.sap.com). Note 1650931 and 482427 directly address your CJ606 scenario. Note 453280 provides the renaming reports (ZZADJUSTTCJED, ZZADJUSTPOSID) needed if you proceed with retiring mask V.