De-implementation SAP Note 1780941, 1773591 and 1813133

[Former Member]

Hi,

We have implemented three SAP Note 1780941, 1773591 and 1813133 for FI Module.

After implementing we have again De-implemented all above mentioned SAP notes due to some errors in Transport.

Now problem is when we are trying to re-implement it, we are getting an error message while creating the Objects mentioned in Manual pre-implementation Steps. For e.g. it is saying that ''Function group FIPAY_DD_PRENOTIF already exist'' (for SAP Note 1780941) .

When I am displaying the same Function Group, it is saying ''Function group FIPAY_DD_PRENOTIF does not exist''.

How to re-implement it.

Thanks for your help.

Regards,

Siddhi

[raymond_giuseppi]

Did you heck for inactive object after de-implementation of manual steps, and did you use the exact reverse order (than implementation) for de-implentation ?

Performing a check on transport request(s) used for de-implementation could be useful (as long as the request can not be released there is very few chance to be able to re-implement the notes)

Regards,

Raymond

[Former Member]

We have not use any order while reversing.. all we did is just De-implemented it using Snote transaction.

many Objects are now in inactive state.

[matt]

Did you de-implement the notes in the reverse order to which you implemented them via snote.

For each note, did you reverse the post implementation steps (if any), then de-implement the note via snote, then reverse the pre-implementation steps (if any)?

That is what Raymond means by "did you use the exact reverse order".

[raymond_giuseppi]

Not a very good idea, e.g. if a note has pre-implementation action 1, implementation, post-implementation action 2, you must reverse action 2, de-implement the note and reverse action 1, and if two notes were implemented, 1 then 2, you must de-implement those in the reverse order of the implementation, 2 then 1?

I never got this problem, as I dislike () return code 4 in transport, so one note, one TR (exception: if an actual great number of notes are implemented) and I release (after check) each note before implementing the next one.

You should consider raising an OSS message (http://service.sap.com/incident) as those three notes have both pre and post implementation steps, some steps are even execution of report/customizing (so how to reverse ?)

Regards,

Raymond

[Former Member]

I've got a scary possible solution for you (read as only try this if you have a very good understanding of the underlying components and are desparate):

We start with the assumption that your transport never made it to your production environment.  If it did, then all bets are off.

Go into Production.

Create a transport there that contains all of the objects (except the new FG) in the offending transport.

Release it.

In Development, transport it into development.

Now everything is back to original in development except the new FG.

Now in Development try to do a create of of the FG.

If that succeeds, do a delete of the FG.

In theory, everything is back to normal.

But again, this is something that I would advise for only the most experienced to do.

The smart play is to wait for OSS to fix it!

Neal

[Former Member]

I'd immediately get a problem report into OSS!  The order is/was critical.  The system may now be in a state that will require some serious expert oversight.

Neal