Solution : https://service.sap.com/sap/support/notes/16466 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the naming conventions for user-defined objects to avoid name conflicts with SAP namespace in upgrades. Customers should use prefixes 'Y' or 'Z' for custom objects. As of Release 4.0, name length limits for certain object types have been revised. Additionally, naming for third-party distribution involves prefix namespaces introduced in Release 4.0 and partner projects from Release 3.x. Adhering to these conventions is crucial during upgrades to prevent potential issues like overwrites of custom objects. Specific guidelines for various object types and their naming formats are detailed for enforcement from specific releases.
Key words :
0a table index sap table, -pool/cluster tables additional max, 1ascreen number sap prog, tables/fields/indices/structures, 0c user exit funct, module pool update task, module pool info type, upgrade overwrites customer objects, table field sap table, user exit funct
Related Notes :
| 757234 | Namespace/development license/corporate functions |
| 560889 | Application log: Customer namespace |
| 536613 | SAP name range enhancement for condition technique tables |
| 534720 | Converting customer-specific 9* code pages does not work |
| 454354 | Change document: Function module name is in SAP namespace |
| 395083 | |
| 334526 | SE54: Tables not recognized as customer objects |
| 319944 | CD: Object is in the SAP namespace |
| 212246 | T500L: Organization of country groupings in SAP standard |
| 105132 | Reserving namespaces |
| 104010 | Restrictions for development in namespaces |
| 84282 | Development namespaces for customers and partners |
| 44962 | Changes to SAP original objects in cust.sys. |
| 41474 | Customer namespace for conversion routines |
| 39524 | Development in the partner namespace: Preconditions |
| 38781 | Partner name space SAP objects |
| 20643 | |
| 3166 | Name range for customer-modified printer types |