Debugging standard transaction MB1C - Queries

[Former Member]

Hi Experts,

SAP standard transaction MB1C is not updating the database table MSEG.

Please help me in finding the cause of this issue.

1. I have checked the ST22 for any errors - no errors logged.

2. How is the transaction insert entries into the trans. table MSEG. ( any update, modify queries)

3. How to debug the MB1C tx to find the issue..

When I post the documents, it says "Document #### posted". When I go and check the table.. I get "No table entries found".

Please provide me some ideas where is the problem.

[Former Member]

Hi Experts,

SAP standard transaction MB1C is not updating the database table MSEG.

Please help me in finding the cause of this issue.

1. I have checked the ST22 for any errors - no errors logged.

2. How is the transaction insert entries into the trans. table MSEG. ( any update, modify queries)

3. How to debug the MB1C tx to find the issue..

When I post the documents, it says "Document #### posted". When I go and check the table.. I get "No table entries found".

Please provide me some ideas where is the problem.

[Former Member]

Hi

As you said the posting is done and you get the message.

But check in the code the what kind of messages are maintained in the MSG table.

May be only the message of ERROR type are stored in the table not the SUCCESS type.

So check you code and find which type of message are stored in MSG table.

Thanks

Lalit Gupta

[Former Member]

Any more ideas??

Experts who have debugged the transaction previously, how is the data transferred from internal table to trans. table MSEG?

[Maciej_DomagaBa]

Are you sure there are no pending updates to perform ? (or crashed)

Check this in SM13.

regards

[Former Member]

I have checked SM13 and there are no entries.

[brad_bohn]

There's a number of ways to attack it and find the best place to start debugging. Have you checked the where-used list for the message in SE91 to find the codepoint(s) for the document creation? Use SE30 to view the call stack for the transaction and target the specific function that creates the document. Use ST05 to find the DB operations and their codepoints.

[Former Member]

Hi Brad,

Thanks for your input.. I used the message class technique and found the problem..

[Sandra_Rossi]

> SAP standard transaction MB1C is not updating the database table MSEG

I don't know MB1C, but if you use the normal transaction MB03 (?) to display the goods receipt (or whatever its name is), does it display normally? (ask the functional people if you don't know the transaction)

If yes, then maybe it's normal that MSEG is not filled (sorry if it makes some people howl). In that case, you should trace MB03 transaction via ST05 and other techniques (see Brad's answer) to check from which tables the data comes from.

If you can't see the goods receipt using any transaction, then it's probably a bug and you have to contact SAP support.