issue with idoc

[Former Member]

Hello guyz ,

Before I ask this question can I say please do not block this question cause I run out of ideas and i have done enough search:(

sales order is created by idoc in production which got wrong delivery address in it.

Now I wanted to debug this in QA and see where was the problem.

This is not happening to all the cusotmers.

Could you please guide me

thnx

[Former Member]

Hello guyz ,

Before I ask this question can I say please do not block this question cause I run out of ideas and i have done enough search:(

sales order is created by idoc in production which got wrong delivery address in it.

Now I wanted to debug this in QA and see where was the problem.

This is not happening to all the cusotmers.

Could you please guide me

thnx

[Former Member]

Use Transaction WE19. You can start the processing function with debug option.

[Former Member]

I tried it but the thing is how to get the idoc from prod to qa?

Edited by: BrightSide on Oct 1, 2010 12:40 PM

[Former Member]

Search your transactions...there's a program to copy specific IDOC from instance to instance, but I cannot recall the name at the moment.

[Former Member]

Hi,

if you have the same master data in both production and QA, then you can use WE19. Instead of giving the IDoc number, you can give the message type / Basic type and Enhancement to execute the same. Give the values passed and build and debug.

Hope it helps.

Sujay

[Former Member]

Go to transaction WE19 in your PD system. Call up your IDoc.

Edit the Control Segment so that it will pass the Partner Profile on the target QA system.

Once you've edited the Control Segment in WE19, click the button marked Inbound file.

A pop-up dialog with a data entry field where you will enter a file and path name for the IDoc file on the SAP App Server.

Note the checkbox that asks if you want to start inbound processing immediately.

Make sure it is not checked otherwise as soon as your IDoc is saved to a file inbound IDoc processing will be triggered into PRODUCTION.

The IDoc file will be deleted and you'll have nothing to copy to your QA system.

Click the green checkmark when everything is correct and your IDoc will be written to a file to the App Server location you specified.

Logon to PD app server and copy the IDoc to your desktop.

Then logon to QA server and copy the IDoc from your desktop to a directory on the QA App Server.

Run WE16 in QA.

Enter the path and file name for the IDoc file and the File Port set up to bring it in. Make sure it matches the File Port used in the Partner Profile for your Partner and IDoc Message Type.

If the Control Segment values are correct, the IDoc will pass the Partner Profile and be written to the IDoc Database at Status 64, assuming your Partner Profile is set to Trigger by background program.

Even if the Partner Profile check fails, SAP will still write the IDoc to the IDoc Database with Status Code 56, IDoc with errors added.

You can still use the IDoc for testing in WE19 as long as you edit the Control Segment to match your Partner Profile.

Please make a test of Idoc copying from QA to dev system as I did it for QA TO DEV and this all I can rememeber from what I searched at that time .