Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-ADR (Application Component) Address Management/Business Address⤷
SZAD (Package) SAP Technology - Business Services: Address Management
IMG Activity
| ID | SIMG_ADDRESSES_SA01 | Maintain Address and Person Number Range |
| Transaction Code | S_BCE_68000285 | IMG Activity: SIMG_ADDRESSES_SA01 |
| Created on | 19981207 | |
| Customizing Attributes | SIMG_ADDRESSES_SA01 | Maintain address and person number range |
| Customizing Activity | SIMG_ADDRESSES_SA01 | Maintain address and person number range |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ADDRESSES_SA01 |
The addresses used in SAP applications are primarily stored in the tables of the Business Address Services (BAS). Addresses are identified by an internal number, assigned by the SAP number assignment.
The same number range is used for the Business Address Services tables from Release 4.0 (ADRC, ADRP, etc.) as for addresses in the tables SADR/SADRP in previous releases.
Example
Requirements
Standard settings
Number ranges "01" and "10" are delivered. Number range "10" is needed for some areas in SD and must not be changed.
Recommendation
You can change the number range "01" if required, but see the note under "Further notes".
You may not change the characteristic of the number range interval "01" to "external number assignment. The system does not support external number assignment for addresses.
Activities
To change the number range for Business Address Services, proceed as follows:
- Call the number range maintenance transaction by choosing "Execute".
- Choose Change interval.
- Maintain the interval values (from number, to number) for the number range "01".
(number range "10" must not be changed) - Save the entries.
Further notes
The following notes were valid until Release 4.5; from Release 4.6 the changed transport methods should resolve the problems mentioned. The organizational measures for separating number ranges are only needed for transports between 4.6 and 4.5 systems.
If you work in several systems or clients and want to transport address data - for instance with the organizational units in Customizing - note that inconsistencies can occur when transporting addresses:
Problem
The key for the address file is an internal number which is assigned sequentially per system and client. Problems can occur if the same number was assigned in the source system and in the target system for two different addresses. The address from the source system is then not inserted in the address file in the target system; the existing address in the target system (with the same internal number) is "changed", that is, it is overwritten with the data of the transported address and is no longer available.
Solution
See OSS note 25182.
Business Attributes
| ASAP Roadmap ID | 250 | Define Number Range and Basic Structures |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_ADDRESSES_SA01 | 0 | HLB0006316 | Address Management/Business Address |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| SNUM | T - Individual transaction object | SA01 | ADR_NUMRA | Maintain number ranges for central address management |
History
| Last changed by/on | SAP | 19990302 |
| SAP Release Created in |
