can any one pls explain how number range object transported from developemnet to quality and production.i hve a doupt if we work with particular no range obj in testing does it reflected in prod server.
Number range needs to be transported manually from one to other server. TR has to be generated manually.
Once u send the TR then only one no range will reflect as same in other server.
Number range needs to be transported manually from one to other server. TR has to be generated manually.
Once u send the TR then only one no range will reflect as same in other server.
We can do TR also if system is fresh and nothing is done.
You normally NEVER transport number ranges between servers/clients - these are transactional dependant to
a particular SAP Instance as everything is tied to specific transactions within that client - and never shall the twain meet.
In my last Implementation project we did transport the number ranges manually and it worked fine. Before any transaction we sent TRs and when all number ranges were there we started the tranx. And there was no problem everything is fine even after 8months
can u pls explain hw tr has to generate manually and also no.ranges transport in steps.for instance take example of vendor master no ranges.u help is highly needed.
when u are at number range then at top u will see interval in menu click at it then click transport, it will ask do u want to transport the material say yes. release the TR in se10 and then in stms import it in other server hope this can help you
Anand,
I'm surprised. Most of the dev and test environments
have a small subset of data - things like vendor
masters are different in size and end up with
different numbering. I've been on many
implementations and this is one area we did not
transport across the landscapes. Not sure what a TR
is - maybe they tweaked the current number used to map
to production before transport went - that is really
the only thing that would make sense to me.
Tom Florio
Tom,
I think am not able to explain well or u didnt get my point. For eg:
no range in client100 for PO is- 4500000000-4599999999
and i want same No range which i made in other client200
so instead of doing manually i sent Transport Request (TR). Similarly for
all customised TRs.
Hope you got my point.
anand
Anand,
Understood your point, but some of the range tables
also contain last number used - this needs to kept
clean between the clients as it will vary based on
number of transactions processed. Agree number range
itself is usually set same between clients.
No comments:
Post a Comment