gATP - APO: Message number 999999 reached. Log is full

[rodrigoluiz_hoffman]

Hello Folks!

While trying to generate deliveries through transactions VL10A either via job or manually, I'm having this error for the related document on V_SA. It seems it's somehow related to gATP checks, because some of the related documents are fully droped to 0, even though there is enough inventory to confirm them (the sales order related to it is usually fully confirmed).

Does anybody know how this message gets generated, and how it impacts the gATP confirmations?

We are still investigating the problem, but if anyone has already gone through it, could you please share with us what may be happening?

Thanks in advance!

[Former Member · Accepted solution]

Rodrigo,

I have never seen this message appear, but a quick bit of research shows that the message number is BL 252 (on the SCM side), and it is invoked when the application log is full.

Basis or 'someone' is normally responsible for setting up maintenance jobs that periodically delete unneeded log entries. Or, since no-one in your shop seems to be actually reading the logs, you could consider turning logging off. If this is the log that I think it is, you can manually log onto SCM and execute SLG2 (delete expired logs) to make some space for new messages.

Here are a few docs about general maintenance for SCM. If your Basis guys haven't seen these, print 'em up and give copies to them for their birthdays.

http://service.sap.com/~sapidb/011000358700002213412003E

http://service.sap.com/~sapidb/011000358700000715082008E

http://service.sap.com/~sapidb/011000358700007382642002E

http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000785742007E

Since I have never seen a log overflow, I can't say if this is affecting your problem. Delete the obsolete logs entries and retry.

Best Regards,

DB49