topic Re: Create manual dump in Application Development and Automation Discussions

Create manual dump

Former Member — Mon, 10 Oct 2011 12:05:27 GMT

Hello everyone,

I have the following isse. A customer has a problem that a Z-table sometimes doesn't get updated. Now I would like to save as much data as possible as soon as i discover this (select on table in different locations of the program).

So what I would ideally like is to manually create a "dump" and save that information. That way I have as much data as possible when investigating this problem.

I already thought of using the application log, but this only saves messages and nog variables, internal tables etc.

Do any of you have an idea ?

Thanks for your troubles <removed by moderator>

Dirk.

Edited by: Thomas Zloch on Oct 10, 2011 2:09 PM

Re: Create manual dump

ThomasZloch — Mon, 10 Oct 2011 12:07:57 GMT

You can try issuing a message of type X, which leads to a, you guessed it, MESSAGE_TYPE_X short dump.

Thomas

Re: Create manual dump

Former Member — Mon, 10 Oct 2011 12:09:23 GMT

a message with type A wont do the job?

or wait was it A or X? hmmm anyway try those two and report back if thats not enough.

Re: Create manual dump

Former Member — Mon, 10 Oct 2011 12:09:51 GMT

I thought of that idea, but that would trigger a real dump.

And that's not what I want.

Re: Create manual dump

Former Member — Mon, 10 Oct 2011 12:15:55 GMT

well, then you have not much chance using any predefined algorithm.

Seems you need to do it yourself.

What means:

- gather all information you need for your "dump" to get an idea what went wrong

- gather thrown error messages from system (sy-msgno, sy-msgv1, ...)

- store that in a protcol table of your own, or make a spool or whatever.

Re: Create manual dump

Former Member — Mon, 10 Oct 2011 12:25:24 GMT

Instead of forcing a dump on your conditions, make ue of ASSERT or LOG-POINT. This enables you to store information.

Go look it up.

edit. As of release 7.0 LOG-POINT should be used for this purpose.

Edited by: Maen Anachronos on Oct 10, 2011 2:25 PM

Re: Create manual dump

Former Member — Wed, 12 Oct 2011 08:27:35 GMT

I've looked into it but I'm not sure exactly how this all works. I have to experiment some more.

Just for the record: The customer uses this base:

SAP_BASIS 640 0027 SAPKB64027 SAP-Basis-component

So, I think I have to stick to ASSERT.

Re: Create manual dump

Former Member — Mon, 14 Nov 2011 15:37:07 GMT

OK.... I've tried the assert statement and although it's a nice idea, it's not exactly what I want.

I still have to declare the list of variables which I want in the logging. But a dump contains (almost) all variables.

Anyone else an idea ?