Ansicht
Dokumentation
00406 - Anyone with a SLICK SPAU process during application of Support Pa ckage(s)? 4.6C
BAL_S_LOG - Application Log: Log header data Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
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
rdisp/max_wprun_time - Maximum work process run time ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 1692 Date: 20240423 Time: 223144 sap01-206 ( 3 ms )
