Ansicht
Dokumentation
02278 - When do you import into production?
General Data in Customer Master SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
When do you import into production?
Jim,our customer has locations all within one timezone, so at least we have not
a problem with online activities around the clock. There is a timeframe of
relatively low system activity between 6:00 pm and 8:00 pm, when most of the
users are already gone but the nightly batch jobs are not yet started.
Over the day we often have 10+ transports to import into PRD. It depends on
the quality of our developer's work as well as the sometimes urgently needs
of our customer. Anyway, we have built those rules for PRD transports:
1. Only a few guys from development are allowed to request transports
2. Transports are exclusively done by basis team
3. If the transport is uncritical (just changing a clitch), it is
imported whenever ready. In case of problems, the guys of development are at
work and can fix it.
4. If it's a more critical transport (changes on heavily used objects
or the slight chance of possible crashes etc.), it is done at 6:00 pm with a
scheduled batch job. The developer who has requested the transport has to
make sure he is available either at the office or remote at home. One of us
basis guys checks the transport joblog (normally remote from home). In case
of success he's going to have a drink, else he alarms the waiting developer.
5. If the transport is really hot, it is scheduled for the next
maintenance weekend.
Hope, it helps a little
Regards
Franz Lehnardt
AS/400 & R/3 Basis Administration
EGG IT Services GmbH
Eschborn, Germany
-----Ursprüngliche Nachricht-----
Von: Jim Doll [SMTP:JDOLLZp...]
Gesendet am: Donnerstag, 7. Juni 2001 21:49
An: sap400Zm...
Betreff: When do you import into production?
We're trying to find the best time to import into our 4.6C
production system, running on V4R5 OS/400. I think SAP's official position
is "run them when the system isn't busy", but we don't HAVE a non-busy time.
We recently had a case where we imported a user exit, and the SAP
system didn't like having it changed while it was in use--we fought
shortdumps for quite a while before it calmed down.
Originally, we imported during the evening, but at that time, most
of support (ABAP, config folks, and BASIS) had gone home. So we changed it
to noon, thinking that the system was a little less busy, but support folks
still here. But we've got order entry people going during that time, as
well as warehouse people.
We back up our system using MIMIX and an H/A box during the week; we
take production down and run a local save-while-active on it Saturday
morning. But Saturday morning transports have the same problem as evenings:
nobody is available to fix problems potentially caused by transports.
Any recommendations?
Jim Doll, Perrigo BASISist
Durban Tours - Südafrika Safari
Fill RESBD Structure from EBP Component Structure General Material Data
This documentation is copyright by SAP AG.
Length: 3539 Date: 20240520 Time: 181434 sap01-206 ( 4 ms )
