Configuration created in wrong Namespace

[adnanmaqbool]

Dear All 

While implementing a Public Cloud Project , consultant from the background of On-Prem implementation created all configurations with Y Namespace. Usually configurations performed by customer, either during ABAP development or SPRO were starting from Z or Y or 9 namespace.

Later on, we found an SAP Note that 'Y' in public cloud is considered as SAP namespace.

Consultant has created following configuration with 'Y Namespace' and also moved it to QAS. Please confirm the impact and any possible solution or can we leave the configuration in 'Y namespace' as it is, as a lot of work has already completed in it.

• Factory Calendar
• Standard Value Key
• Work Center Responsible
• Routing planner group
• MRP Controller
• Special Procurement Types
• Order Type
• Production Scheduler & Profile

[Muzzamil_SD_Consultant]

if we want to delete the wrongly created cofirguration, deletion optioned is not available

[adnanmaqbool · Accepted solution]

Received below response of SAP against an OSS.

You can use ‘Y’ for some of the configurations like Configure Planner Group.

No negative impact is expected.

You can remain same configuration with Y* namespace on above SSCUI activities.