topic Re: OSS notes in Application Development and Automation Discussions

OSS notes

Former Member — Fri, 04 May 2007 14:29:35 GMT

Hi friends,

I have implemented a oss note, as per the instructions given to me, but in that

after implementing the oss note using transaction SNOTE, i am getting implimentation status as 'completed' and processing status is 'in process'.

Then how can i know that my oss notes is completed or what is the test conditions for this oss notes.

with regards,

sharma.

Re: OSS notes

Former Member — Fri, 04 May 2007 14:36:21 GMT

Hello Sharma,

You have to consider the status of the note: completed means that the note has been implemented.

Then you can classify this note after testing your program and everything works fine, ie the error has been corrected.

That's why it is "in process".

Regards,

Walter

please reward points for good answers

Re: OSS notes

Former Member — Fri, 04 May 2007 14:43:35 GMT

Hi walter,

Thanks a lot, I think u know my oss notes scenario. Then my main doubt is

how to test this oss notes. What do you mean my processing status is ' in processing'.

regards,

sharma.

Re: OSS notes

Former Member — Fri, 04 May 2007 14:50:28 GMT

If possible, check the correction mentioned in the snote are implemented in your system or not. If it is implemented then there is no problem in Snote implementation.

Re: OSS notes

Former Member — Mon, 07 May 2007 06:52:49 GMT

Symptom of the note:

Your system contains old deliveries that are closed from a business

perspective, but characterized as open by the system for a number of

different reasons. This has consequences for data archiving:

o Open deliveries cannot be archived because the overall processing

status "Completed" is an absolute requirement for deliveries to

be archived (see Note 138666).

o Open deliveries also affect whether or not sales orders can be

archived because these orders can only be archived once they are

completed as subsequent documents for related deliveries. Just

one open delivery in the document flow can prevent archiving of a

scheduling agreement covering a large number of subsequent

deliveries.

You should check if it is still the case after the note implementation.

Regards,

Walter