Ansicht
Dokumentation
03865 - Hotpack Application Procedure
Fill RESBD Structure from EBP Component Structure ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
Hotpack Application Procedure
Zhihong,Just a small note: I usually don't confirm the HPs until the next
application. Remember, once confirmed it can't be undone (although I have
never undone HPs, I usually just fix any problems they cause).
Regards,
Mike D. Martin<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
email: <mailto:mmartinZs...>
-----Original Message-----
From: Zhihong Zhao [mailto:ZhaoZZd...]
Sent: Tuesday, November 13, 2001 2:04 PM
To: 'Mike Martin, IS-NA, AOSOLA'; Michael Power; Andrew Tilbrook
Cc: SAP - AS/400 List (E-mail)
Subject: RE: Hotpack Application Procedure
Mike:
Thank you for your response. We will follow the adjusted procedure:
1. Import HPs to DEV
2. When prompted make all SPAD/SPAU adjustments (reverting to SAP original;
adding to transport requests)
3. Release the request from step 2
4. Reapply all necessary notes (fallout from step 2; adding to trasp.
request)
5. Release request from step 4
6. Import the HPs to TST
7. Import request from step 2 to TST
8. Run SPAU/SPDD in TST and find all remaining objects.
9. In DEV, create a transport request, manually, that includes all objects
found in step 9
10.Import to TST and rerun SPAU/SPDD to ensure no remaining adjustments
needed
11.Confirm HPs to TST
12.Import request from step 4 to TST
13.Repeat steps 6-11 in PRD
Regards
Zhihong Zhao
SAP Basis Analyst
DairyFarmers - Project Enterprise
-----Original Message-----
From: Mike Martin, IS-NA, AOSOLA [mailto:MMartinZa...]
Sent: Wednesday, November 14, 2001 4:32 AM
To: 'Zhihong Zhao'; Mike Martin, IS-NA, AOSOLA
Cc: SAP - AS/400 List (E-mail)
Subject: RE: Hotpack Application Procedure
You are correct, you simply exit when prompted to perform SPAU and SPDD.
Then proceed with the transports. If you did do mods directly in the
subsequent systems, these would just be overwritten by the transport anyway.
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
email: <mailto:mmartinZs...>
-----Original Message-----
From: Zhihong Zhao [mailto:ZhaoZZd...]
Sent: Monday, November 12, 2001 9:15 PM
To: 'Mike Martin, IS-NA, AOSOLA'
Cc: SAP - AS/400 List (E-mail)
Subject: RE: Hotpack Application Procedure
Mike:
We are in the middle of hotpack apply project, and got a question regarding
the procedure applying hotpack to the second or third systems. In your
procedure, step 7 & 8 import transport from 2 & 4 into the target system. As
I know, when you apply hotpack, the spam will automatically direct you to
SPDD & SPAU. Did you just quit from this point and use the transports? I
feel I have to make adjustment directly in target system and then import the
transport from step 4. Does anyone have a better idea?
Regards
Zhihong Zhao
SAP Basis Analyst
DairyFarmers - Project Enterprise
-----Original Message-----
From: Mike Martin, IS-NA, AOSOLA [mailto:MMartinZa...]
Sent: Tuesday, October 30, 2001 5:09 AM
To: 'Sugg, Chris'
Cc: SAP - AS/400 List (E-mail)
Subject: RE: Hotpack Application Procedure
Hi Chris,
I think you're on the right track, however, I would avoid opening up TST for
changes.
I would follow these steps:
1. Import HPs to DEV
2. When prompted make all SPAD/SPAU adjustments (reverting to SAP original;
adding to transport requests)
3. Release the request from step 2
4. Reapply all necessary notes (fallout from step 2; adding to trasp.
request)
5. Release request from step 4
6. Import the HPs to TST
7. Import request from step 2 to TST
8. Import request from step 4 to TST
9. Run SPAU/SPDD in TST and find all remaining objects.
10.In DEV, create a transport request, manually, that includes all objects
found in step 9
11.Import to TST and rerun SPAU/SPDD to ensure no remaining adjustments
needed
12.Repeat steps 6-11 in PRD
Once you get all systems in sync with regards to repaired objects, etc.,
then this shouldn't be an issue upon the next HP updates. However, SAP
objects are currently inconsistent throughout your landscape probably due to
opening systems for changes in the past. I would highly recommend avoiding
this practice (for ABAP objects...for config, etc, it's OK/necessary).
Good luck, and if you have specific problems/questions, feel free to contact
me.
Regards,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...
-----Original Message-----
From: Sugg, Chris [ mailto:aacsuggZn... <mailto:aacsuggZn...> ]
Sent: Monday, October 29, 2001 7:21 AM
To: 'Mike Martin' (E-mail)
Subject: Hotpack Application Procedure
Hello Mike.
I picked up some information from the mailing list from you concerning
applying support packs and SPAU changes. We are in the middle of applying
HP's (we were at 13 and are now at 25 for DEV and TST). If you have a few
minutes, any thoughts/ideas would greatly be appreciated.
Currently, the steps that were taken were to first apply to DEV and in SPAU,
we reset objects to original, which created transports.
Then, we applied HP's to our TST system and of course SPAU found objects.
Some of the objects listed were also included in the DEV SPAU and some were
not.
My question is what steps do you think we should take from here? Our plans
were to change the system setting to allow us to change objects to original
in the TST system, then go to our DEV system and create a transport for the
objects that need notes reapplied and then transport them to TST.
Also, what problems do you foresee in our upgrade for PRD?
Any suggestions would be greatly appreciated,
thanks
Chris Sugg
SAP Basis Administrator
NACCO Materials Handling Group
1400 Sullivan Drive
Greenville, NC 27834-2011
AACSUGGZN...
Phone: (252) 695-1912
Fax #: (252) 931-0934
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
TXBHW - Original Tax Base Amount in Local Currency BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 8052 Date: 20240418 Time: 203341 sap01-206 ( 3 ms )
