Ansicht
Dokumentation
00413 - Anyone with a SLICK SPAU process during application of Suppor t Pa ckage(s)? 4.6C
TXBHW - Original Tax Base Amount in Local Currency rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
Anyone with a SLICK SPAU process during application of Suppor t Pa ckage(s)? 4.6C
Hi Doreen,I agree, we have the same problems while applying support packages.
I apply the complete package and return to SAP standard without controlling
the
differences. We have a list where all the changed and modified objects where
listed.
At SPAU time it is fast and easy to control the changes and evtl. implement
the OSS-note again.
It would be cost too much time which i do not have, to control all the notes
included in
a support package. Sometimes this is poor, because SAP has implemented new
functions
which I do not know and running programs will now be not running.
It is impossible to test all the programs.
I would like to have a general note, which contains all the 'must'
instructions,
hints for new functions, advanced developments or in other words,
all informations needed to apply support packages fast and sure.
kind regards
Karl Grauer
Amphenol-Tuchel Electronics
August-Haeusser-Str. 10
DE 74080 Heilbronn
phone: +49 7131/929327
mailto:karl.grauerZa...
-----Ursprüngliche Nachricht-----
Von: Anderson, Doreen [mailto:DAndersoZb...]
Gesendet am: Donnerstag, 18. Januar 2001 18:22
An: 'SAP AS/400 Discussion Group'
Betreff: Anyone with a SLICK SPAU process during application of Support
Pa ckage(s)? 4.6C
Hi,
We're finding that it is taking more & more time to assess all the objects
which "appear" in SPAU during the application of a Support Package
One at a time; we bring up each source in SPAU; Version Management & Compare
We've been able to get the developers to annotate on the text for their
change request the note# that they are applying.
We then typically display the OSS Note & take a look at whether it was to be
included in the Support Package being applied at the time.
At that point, we "return to SAP standard" without really scrutinizing the
code differences on the compare screen.
If the change request does not contain any documentation/text; we then
review the code differences.
We are going to ask the developers to take it one step further & also
include the Support Package # in which the code changes are scheduled for
(if that information has also been included in the OSS note)
Does anyone have a more streamlined procedure? Do you push this
responsibility back to each individual developer?
Curious
ps. Our 4.6C DIA instance issue went away after scrapping it & reinstalling;
must of done something incorrectly 1st time
Durban Tours - Südafrika Safari
TXBHW - Original Tax Base Amount in Local Currency Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 3314 Date: 20240418 Time: 132840 sap01-206 ( 2 ms )
