IDOC Status 03, but some fields are missing in SEGMENT

[Former Member]

Dear All,

Outbound Idoc Processd successfully with status 03, basic type (INVOIC02). But in output file some fields are missing in one segment.

How to find missing fields, and how to debug this. I tried by putting break point in FM IDOC_OUTPUT_INVOIC, but debugger is not getting trigger.

Please help how to check missing fields.

Thanks,

Venky.

[Former Member]

Hi Venkat,

From what I see is the FM IDOC_OUTPUT_INVOIC is a standard FM. So if the fields be missing due to this FM, then it might be the case with other idocs as well. A standard FM cannot be responsible for missing fields of the idocs .

There must be some custom ABAP object in the way of the IDocs transaction which is removing those fields.

My suggestion to you will be to please throw more light on what happens when the Idoc flows from its sender to the receiver, or if possible you can figure out a custom object which is involved during the transaction of the idoc and then set up a breakpoint to analyze what has happened.

Kind Regards,

Souvik

[Former Member]

Venkat,

Generally when a field in the idoc does not have value, that field is removed from the segment. If all the fields in a segment do not have any values, the entire segment is removed. If this segment is mandatory then a error message is raised.

If the idoc is generated thru an output from invoice, then you need to turn on update debugging as all outputs are processed as updates (after commit is executed). Once update debugging is triggered, you can then add your break point and the system should stop the execution at the break point.

V.

[Former Member]

Hi Thanks for your inputs,

This IDOC is generating file in Application server, I have checked in WE19, all fields are coming in the segments. But in Application server some fields are missing in one segment.

How to check and where to check, how some fields are missing? please help.

Thanks,

Venky.

[TanmayVerma]

Hi Venkat,

If the fields in idoc do not have values then they do not appear in the IDOC. Also the idoc may be getting generated during an update task and hence you might need to activate update debugging to debug the FM.

Steps to activate update debugging:

1. Open debugger and go to 'Settings' option in menu bar. ( You can activate debugger for any other program ).
2. Select the 'Update Debugging ' option and Save settings.
3. Now go to FM IDOC_OUTPUT_INVOIC and put a break point.
4. Proceed normally to generate your IDOC. As soon as an update task is triggered a new window will ope for debug. Press F8 to move to your break point.

~Tanmay.

[Former Member]

Venkat,

Normally in the application server you will not see the entire file. If you use the option list->save/send->file, the entire file will not get downloaded correctly. AL11 in only a snap shot of the file.

If you are following the above process, this might be your problem. Instead use the transaction CG3Y to download the file and then check if it matches the IDOC.

V.