Ansicht
Dokumentation
00416 - Anyone with a SLICK SPAU process during applic ation of Support Pa ckage(s)? 4.6C
Vendor Master (General Section) ABAP Short ReferenceThis documentation is copyright by SAP AG.
Anyone with a SLICK SPAU process during applic ation of Support Pa ckage(s)? 4.6C
Hi all,Furthermore it is a god way to "kick" the development org. to minimize what
they alter in SAP standard.
Regards
Klaus Lindegaard
> -----Oprindelig meddelelse-----
> Fra: Kevin Dowle [SMTP:kevin.dowleZr...]
> Sendt: 19. januar 2001 09:00
> Til: 'SAP on System iZegroups.com'
> Emne: RE: 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
>
>
>
>
> eGroups Sponsor
>
> Choose 3 DVDs for $0.49 each!Choose 3 DVDs for $0.49 each!
> <http://rd.consolut.net/M=168002.1291681.2888959.2/D=egroupmail/S=1700007389:
> N/A=564956/*http://www.columbiahouse.com/gateway?token=7415>
>
> <http://us.adserver.consolut.net/l?M=168002.1291681.2888959.2/D=egroupmail/S=
> 1700007389:N/A=564956/rand=359331767>
>
> To unsubscribe from this group, send an email to:
> SAP on System i-unsubscribeZegroups.com
>
>
>
Durban Tours - Südafrika Safari
Fill RESBD Structure from EBP Component Structure Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 4686 Date: 20240425 Time: 182744 sap01-206 ( 2 ms )
