Outbound Idocs for PO - PORDCR1 remain in status 30 (Ready for dispatch)

[Former Member]

Hi All,

We are using PORDCR1 Idoc to send POs from ECC to SNC. After saving the PO, an Idoc is trigerred but it remains in status "30" - ( IDoc ready for dispatch (ALE service) ) inspite of having the Output Mode in Partner Profile as "Transfer Idoc immediately". The Idoc gets sent only after manually processing it using BD87.

My queries are:

1. Should we run the program "RSEOUT00" even for the above Partner Profile setting ?

2. If so how to ensure the Idocs are triggered immediately after the PO is saved / changed in ECC?

Regards,

Bharath

[Former Member]

Hi Bharath

Check the condition record for vendor in MN05 and see if you have maintained settings as 4 i.e. Send immediately under data/time column.

Thanks

Pravin

[former_member501124]

Procedure to Create STO While creating Material Document in MIGO through Outputype using IDOC

Message Type: PORDCR1

Basic type PORDCR103

FM IDOC_INPUT_PORDCR1.

Process Code: Z******

Create Custom Process code in WE41 and WE42 for both Inbound and Outbound using BUS2012 IDOC_INPUT_PORDCR1 and Object type BUS2012

Create Partner Profile and update the Basic Type , Message Type  Custom Process code in both Inbound and Outbound.

Maintain Message control with Message type and Process code for Outbound Partner to trigger the output type from MIGO.

Assign FM IDOC_INPUT_PORDCR1 , Basic Type PORDCR103, Message type PORDCR1 and object type BUS2012 in WE57.

Define input method for inbound function module in BD51.

Goto NACE T-Code and Select ME(Inventory Management) and click on Output Types.

Select Z*** output type and click on Processing routines and provide program name Z****** and Form Routine EDI_PROCESSING.

Create Program Z***** which is assigned in NACE in SE38.

Use form FORM edi_processing USING rc us_screen to call EDI Processing.

Fetch data from MSEG based on MBLNR eq nast-objky+0(10) and mjahr = nast-objky+10(4) and zeile = nast-objky+14(4).

Populate IDOC data lt_idoc_data.

  Call FM IDOC_INBOUND_WRITE_TO_DB to create IDOC

  Call FM IDOC_START_INBOUND to process the IDOC.

[Former Member]

Hi Bharath

Is this case only with this idoc type or with every idoc?

Can you please check your XI port settings, ask XI/PI guy to clear the XI cache and do some tests using meta data.

Regards

Vinod

[Former Member]

Hi Vinod,

This is the case for the 2 outbound Idocs from ECC to SNC for which settings have been maintained to send them immediately:

1. PORDCR1

2. STPOD

I have asked my PI team to check the PI port / PI cache. Will keep the thread updated if theres any resolution.

Regards,

Bharath