SPAU actions with grey notes

[Former Member]

Hello folks!

Guide me please,

There are many threads in SCN about grey notes, but nothing about one thing. Must i import requst with reseted notes, of course, from DEV to PRD system?

wbr,Albert

[Former Member]

Ok. How i will proceed grey notes in SPAU

1) Reset grey notes in SPAU

2) Compare notes in DEV and PRD systems

3) Notes, which exist in DEV and PRD i will import in PRD pre-dropped in DEV

[Lokeshchemiti]

Hi Albert,

As far as i remember , these Grey color notes are Obsolete in the system ,Which may be delivered with the upgrade or support package previously and is therefore obsolete now.Even system will pop up a message to reset.So,better to Reset .

Regards ,

Lokesh

[Matt_Fraser]

There will be no harm in resetting all the obsolete Notes that show up, and adding all such to the SPAU transport.

[Former Member]

Hi,

Normally Dev and Prod will not be in sync for client dependant/client independent objects as there must be lot of "work in progress" objects which are with different versions in both the systems.

If you have same version of objects then you can move them from Development otherwise best option is to move the objects from mock/QAS system which is exact copy of your production.

One simplest option (with zero issues) is to do SPAU/SPDD independently in each system so that these mismatches can be avoided completely.

Regards,

Nick Loy

[Former Member]

Thanks for response!

If i correctly understand you, In DEV system i reset notes in SPAU with grey status, next request with reseted notes i import in QAS, next in PRD system

[Former Member]

Hi,

It really depends on the situation, I suggest you to do the changes in QA (which is exact copy of Production where you did your mock upgrades) and then use same transport request for Production.

Regards,

Nick Loy

[Matt_Fraser]

The status of SAP-delivered code really should be in sync between DEV, QAS, and PRD, except for where you have applied Notes or Support Packs in DEV and not yet in the downstream systems.  You should not make the changes in QAS.  You were right the first time, reset the 'grey' Notes in SPAU in DEV and add those resets (along with all your other SPAU changes) to a transport request per the normal SPAU process, then let that transport request be imported automatically as part of your support pack queue in both QAS and PRD.  You need to do it this way in QAS to ensure that the import actually works correctly.  If you "do the changes" in QAS to import into PRD, then you haven't actually tested that PRD queue import anywhere.  This, also, is how DEV systems get badly out of sync.

The only reason to run SPAU again in QAS is to a) ensure that your transport took care of everything, or b) fix things that are out of sync with DEV because you've been doing it incorrectly in the past.

Regards,

Matt