Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

00412 - Anyone with a SLICK SPAU process during applic ation of Support Pa ckage(s)? 4.6C

00412 - Anyone with a SLICK SPAU process during applic ation of Support Pa ckage(s)? 4.6C

BAL Application Log Documentation   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Anyone with a SLICK SPAU process during applic ation of Support Pa ckage(s)? 4.6C

Doreen, we make this entirely a developers problem. We print the SPAU list,
hand it to the developers and they must handle it. This gives them a vested
interest in keeping records and documenting their changes.

Regards,
Kevin
Operations Manager
Robertsons (Pty) Ltd.
Durban
South Africa.
Tel: +27-31-3699803
Cell: 082 807 7530.


-----Original Message-----
From: Anderson, Doreen [mailto:dandersoZb...]
Sent: 18 January 2001 07:22
To: 'SAP AS/400 Discussion Group'
Subject: 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

To unsubscribe from this group, send an email to:
SAP on System i-unsubscribeZegroups.com



Durban Tours - Südafrika Safari

ABAP Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 2703 Date: 20230205 Time: 130055     sap01-206 ( 2 ms )