Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_NSP (Package) CTS: Namespaces and Naming Conventions
Basic Data
| Data Element | NR_PROJECT |
| Short Description | Project Number for SAP Partner |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NR_PROJECT | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | RESP |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Project no |
| Medium | 20 | Proj.no. SAP partner |
| Long | 25 | Project no. SAP partner |
| Heading | 2 | PN |
Documentation
Definition
Up to Release 4.0, SAP partners have received exclusively reserved project name ranges in the SAP namespace to develop SAP enhancements and specific solutions (for example, industry solutions). These allow them to form object names during development according to an object-type-specific, fixed convention, which cannot be used by anyone else:
The object names J_nx* (Jnx* for short object names in Release 3.0, for example, transactions) could be formed (see Note 38781 in SAPNet - R/3 Frontend) for a two-character project ID nx (n = digit, x = letter). To do this, the project ID had to be entered in the tables RESP and RESPT and the SAP System configured as an SAP development system (not customer system).
Due to the introduction of new namespaces in Release 4.0, the RESP/RESPT entries in the namespace table V_TRNSPACE (display and maintenance using extended table maintenance) were used as logical namespaces /0SJnx/ and can now only be maintained using the namespace table.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
