Skip to Content
0

source list generation-Purchasing info record XXX flagged for deletion 06718

Mar 06, 2017 at 09:51 AM

65

avatar image
Former Member

Dears,

We are trying to generate a source list via ME05 but our job is getting cancelled after error 06718. We have set the message as warning message as per note 1896184 : OLME -> Environment Data-> Define Attributes of System Messages. But we are still getting blocked. message is being triggered in program LMEORF0P form LIEFERANT_PRUEFEN where message is hard coded.

Can you please help me understand why solution in note is not working. Grateful if anyone could let me know if there is any solution or archiving is the only solution. Thanks in advance

regards,

Karishma

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Jürgen L
Mar 06, 2017 at 10:26 AM
0

The OSS note is about purchase order creation, you are talking about source list creation

I understand the OSS note different than you. I understand that it is standard that SAP recognizes deleted info records, and if you want it differently then you shall set the message to error or you shall do a modification to the standard code.

Since you said you changed the message to warning, I have to conclude that it was earlier already different than SAP standard. And since it is now set to warning I can only assume that you have the modification in place which stops your system from working properly.

I tested the case in my system and I do not get any error message in ME05 if the info record is flagged for deletion.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Mar 06, 2017 at 11:20 AM
0

Dear Jurgen,

thanks for your reply. Sorry for this miscommunication. I meant that the message 06718 is customised as warning on our system. But despite this, we are getting blocked. We did not do any change.

regards,

Karishma

Share
10 |10000 characters needed characters left characters exceeded
Jürgen L
Mar 06, 2017 at 12:22 PM
0

I recommend to use transaction ANST to check if there is really no own coding stopping you and transaction PANKS to check if there are SAP notes for the given message

See the blogs for more detail: https://blogs.sap.com/2014/01/07/what-is-anstand-why-arent-you-using-it/

https://blogs.sap.com/2014/11/28/got-an-error-message-the-new-tool-panks-is-here-to-help-you/

Share
10 |10000 characters needed characters left characters exceeded