topic Re: SAP note problem in Application Development and Automation Discussions

SAP note problem

Former Member — Mon, 31 Jan 2011 12:27:36 GMT

Hello,

While implemeting SAP note , we found that the transport request contains other release correction instructions(for the same note) also like current version is 4.7 has changes for 6.20 release as well. This is a released request so cannot modify its contents.

Note changes are only for a program but when basis tried to import to another client in development got data dictionary errors referring to release 620 but there has been no changes to any data dictionary objects.

So can we ignore the other correction instructions and transport request to quality or how should we implement this note now.

Thanks in advance.

Best Regards

Abhilash

Re: SAP note problem

Former Member — Mon, 31 Jan 2011 12:33:22 GMT

Hi Abhilash,

4.7 is your SAP Application release and 6.20 seems to be your SAP Basis Release.

Make sure, what your SAP Basis Release is! Call "System"->"Status" and press the magnifier. Check Release of component SAP_BASIS. If it is 620, then you can't ignore the errors!

Regards,

Klaus

Re: SAP note problem

Former Member — Mon, 31 Jan 2011 13:27:29 GMT

Hi Klaus Babl ,

Thank you for the reply .

My current SAP version is 470 basis release is 620

Note had correction instructions for versions 470 500 600 and 602 . Note has changes for 1 program.

Error obtained while performing client copy using scc3 in development is on version 620 refrring to some data

dictionary objects.

This note is in fully implemenetd status in snote but still got errors while performing client copy. Note belongs to

higher package but there are no other required notes mentioned in the document.

Since this note is in full implemented status thought of transporting to quality , but got error while performing client copy so can this note be transported or what should be the approach. Any ideas appreciated.

Thank you.

Best Regards,

Abhilash

Re: SAP note problem

Former Member — Tue, 01 Feb 2011 05:56:56 GMT

Hi Abhilash,

I'm not sure to understand you right.

If this program has only corrections for 1 program, then you shouldn't import the transport in several clients. All workbench objects are not client dependent, there is only one client indeoendent version in your whole system. Did you get any error implementing this SAP note in your development system? Didi you get any error to import the transport request into the first client of your quality system?

If you say yes, this could have many reasons, e.g.:

- a missing manual action that must be done before installing this note with SNOTE

- a missing manual action of a previous note in note install chain

- a missing note SAP forgot to mark as predecessor note for your note to install

and more.

If you get an error only importing your transport to further clients then your SAP workbench has got the note once correctly and there may be no problem!

If you have more questions, please tell us the number of the SAP note!

Regards,

Klaus

Re: SAP note problem

Former Member — Tue, 01 Feb 2011 06:23:18 GMT

Hi,

You can consider to revert back the Notes, if you do not want to move to Quality & production

becouse not mooving will save the QA and PD but DV will be effected.

Regards

Bikas

Re: SAP note problem

Former Member — Tue, 01 Feb 2011 07:29:27 GMT

Hi Klaus,

I also thought about the same that if there is only 1 program then since it is not client dependent should we do client copy to other

clients. (This was a process followed by basis to move to all clients and when they got this error they stopped)But in case if we do a client copy also will it return this kind of errors related to data dictionary objects? So as a precaution we have not transported the same to quality. Once confirmed that it is safe will transport to quality.

Note being tried is 1085116 .

Thank you.

Best Regards,

Abhilash

Re: SAP note problem

Former Member — Tue, 01 Feb 2011 13:17:54 GMT

Hi Abhilash,

this looks like a simple SNOTE update of report RPRAPAFO. Do not copy this to other clients of your development system. If there was no error in SNOTE during implementation you can import it once to your quality system (only one client!). Import should work with highest error code 4. If a higher error occurs, then you have to check the reason.

Regards,

Klaus

Re: SAP note problem

Former Member — Wed, 02 Feb 2011 04:41:35 GMT

Hi,

If there is any Walkthru client in the Development system, Please try to move the transport (after releasing the task) to Walkthru via SCC1 or Manual Transport method and test if everything is fine as expected. If the Note/transport logs are looking fine without any issues. Then there is no problem without the note. If the note is applied successfully and still there is same issue, It is better to open a SAP message to look into the problem and suggest according.

Re: SAP note problem

former_member631876 — Tue, 24 Sep 2019 10:43:50 GMT

is there any sap notes without valid releases section ? is there any note relevant for any system ? thank you