Recreating Idocs Manually

[Former Member]

Hi,

In R/3 purchase orders are being created in SAP using inbound idocs.

In production some line items of the Purchase Orders are having incorrect data, however the idocs are successfully posted.

To recreate the scenario, we would like to recreate the same idocs manually in the development system.

Would greatly appreciate if somebody could give me a step by step guide on how to recreate the idocs manually in development, as I am new to this technology.

Thanks and Regards,

Mick

[Former Member]

Hi,

In R/3 purchase orders are being created in SAP using inbound idocs.

In production some line items of the Purchase Orders are having incorrect data, however the idocs are successfully posted.

To recreate the scenario, we would like to recreate the same idocs manually in the development system.

Would greatly appreciate if somebody could give me a step by step guide on how to recreate the idocs manually in development, as I am new to this technology.

Thanks and Regards,

Mick

[Former Member]

You can use transaction WE19 for testing your IDOCs.

If you have an existing IDOC you can choose this radio button and then manually change the data on the following screen.

Or you can use radio button for Existing type and extension and then manually enter the data on the following screen.

[Former Member]

If your PO's are processed from a flat file you can obviously use the same source file for input in development. I expect this is not the case however.

Use Matt's suggestion of WE19, but set up the ALE configuration to allow sending your message type from production to development. This will require the following:

1. Logical system in production that represents development system. (BD54)

2. Maintain RFC destination pointing to development. (SM59)

3. Maintain tRFC port using RFC destination from 2. (WE21)

4. Maintain distribution model with production LS as source and development LS as destination. (BD64)

5. Maintain partner profile, type LS, for destination logical system. (WE20)

6. Enter existing IDoc in WE19 and maintain necessary fields in control record:

Recipient port, partner no, partner type

Sender port, partner no, partner type

Click the "Standard outbound processing" button to send.

[Former Member]

Thanks Michael. I am a little confused.

We want to recreate a scenario in development, which is taking place in production.

The scenario as I described earlier is that PO's are created in R/3 production from inbound IDocs. Some line items in the PO have wrong data, but the IDocs are successfully posted.

Now we want to recreate the same scenario in Development. So as suggested by you, do we need to make all the config changes in Production and development?

Or is there any other way to recreate the scenario in development.

[Former Member]

It might be easier for you to recreate the IDoc in development manually using WE19, depending on how much data is in the IDoc. If so, you shouldn't need to do any configuration as I expect the interface exists in development as well. If you use this method, you can use an existing DEV IDoc to determine how to populate the control record.

If the IDoc is too large, then you can use my suggestion from above. This will send the exact IDoc from production down to development. I forgot, you would need to set up the partner profile in development as well to allow ORDERS to be received from your production logical system.

[Former Member]

Hi Jayesh,

You have to configure only from which system you are getting the idocs. Since, you have to fill the control record as per your development system, you need that.

Other than control record, you can enter the same data from production system idoc to Development system IDOCs manually and then post it.

First check in WE20 T Code, if the message type is configured in Dev system.

shylesh

[Former Member]

Thanks to everyone for answering.

So in WE19 should I enter the basic type or an existing IDoc (I assume that what they mean by existing IDoc is we have to write an IDoc number)?

Remember the IDoc was posted in production and assume that the interface exists in development also.

[Former Member]

I would use WE19 simultaneously in PRD and DEV. In PRD, enter the IDoc number you would like to recreate in DEV. This will provide a reference. In DEV, enter the IDoc type. Click on a segment in both systems and start filling the DEV IDoc. When you populate the control record, you might want to open up a posted IDoc from DEV to verify the correct values.

[Former Member]

Hi Jayesh,

You can use transaction WE19 (Test tool for IDoc) to create IDoc manually.

Enter the corresponding message type and populate all segments (EDIDC and EDIDD) same as production IDoc. At the end you can process the inbound IDoc with start inbound button (using standard FM) or inbound function module button (using custom FM).

Hope this will help.

Regards,

Ferry Lianto

[Former Member]

Here we go :

WE19.

Cheers.

[Former Member]

Thanks to everybody for answering.

But can we recreate an idoc in development from an existing idoc in production?