Solution : https://service.sap.com/sap/support/notes/104010 (SAP Service marketplace login required)
Summary :
SAP Note addresses issues and outlines solutions related to namespace usage in development objects within the ABAP Development Workbench. It specifies that as of Release 4.0, personal namespaces can be reserved, aiming to prevent naming conflicts when delivering developments to third parties. Issues such as object editors not recognizing namespace prefixes and error occurrences when prefixes are used are acknowledged due to certain object types not supporting namespaces and incomplete tool adjustments. The solution section suggests namespaces development concept limitations could be intentional or due to inadequate adaptation of development tools. Recommendations for naming conventions and supported object types are detailed, alongside instructions for handling specific exceptions and error scenarios in object type usage.
Key words :
release-independent restrictions number range objects, names permits mnemonic long names, r3tr fugr /abc/xyz, namespace offers sufficient space, license-checked namespace reservations, function modules conversion_exit_xxxxx_input/output, project management - transaction spro -, general text document class, central abap repository objects, customer conversion exits begin
Related Notes :
| 1316963 | SU21| Transport object SUSO must be registered |
| 951659 | Condition tables cannot be created in the object namespace |
| 912214 | No repair license for objects in /SAPCND/ namespace. |
| 560889 | Application log: Customer namespace |
| 431522 | CTS prefix namespace for workflow |
| 395083 | |
| 172753 | Restriction for developing test cases in namespace |
| 131208 | SAPscript: Namespace for layout sets |
| 89898 | Extending namespace in 4.0: Effects |
| 84282 | Development namespaces for customers and partners |
| 26171 | Possible entry values for command field ("OK-code") |
| 16466 | Customer name range for SAP objects |