Transporting addresses can be an issue. You have to understand
the structure of addresses to understand why.
Address Number Ranges
Addresses for various
entities (such as plants, customers etc) are stored in a generic
address table with a pointer to the entry in the table. |
|
|
EG: a plant 8001 may have
address record (for detailed address information) of 4009. Transaction
SE16 on table T001W
The actual detailed address
is then stored in table ADRC with that key along with all the other
addresses.
Transaction
SE16 on table ADRC
When you first set up the
SAP systems, one could (if one remembers and of course it does not
always happen!), adjust the number ranges in DEV, TST and PRD, so
that if one adds addresses (by creating new plants) in DEV and
transports, then they do not overwrite the addresses for customers
and vendors that have
been created.
See Note:
25182 which advises (amongst other things) to ensure that the number
ranges do not overlap.
|
|
Check the status of number range 01
Transaction SNRO on object ADRNR
If there is an overlap, then you need arrange that the interval do
not overlap. It is not
possible to change the lower limits BUT one can change the status so that
the next address number allocated will start from status + 1.
Write the status down for each system:
|
Number
|
Status
|
|
PRD
|
23 393
|
|
TST
|
23 133
|
|
DEV
|
4 000
|
|
In
this case any transports from DEV with new address numbers lower
than 23 393 would overwrite in TEST and Prod and you would find
customers and plants sharing the same address record!
|
Fix the situation
Anticipate
the biggest range of address you may need – multiply by a factor 10 and
then create non-overlapping ranges for each
system as follows:
Change the upper limits
Transaction SNRO on ADRNR, then
click on “intervals”
Change the Status
Transaction SNRO on ADRNR, then
click on “status”
At
the end of this process you should have practically non-overlapping ranges
something like the following:
|
Number
|
From number
|
To number
|
Status
|
|
PRD
|
0000000001
|
3999999
|
3000000
|
|
TST
|
0000000001
|
2999999
|
2000000
|
|
DEV
|
0000000001
|
1999999
|
1000000
|
|
With
this method, any transports from DEV for new plants will go into a
range above any existing addresses but below TST and PRD ranges.
IE there will be no overlaps for any new stuff, any existing
records should be ok. Each
of these ranges allows for 1,000,000 addresses in Production to be
created before hitting the overlap problem again.
|
|
Notes
You will receive a warning
message when you try to create plants using OX10.
If the situation has been
rectified as described above, it should be quite safe to answer the
questions as indicated and continue with the definition and
subsequent transport.
Alternatively
|
|
|
Express thanks for SAP Scene information - buy your next
SAP book through our SAP Books page
