PO Collab using PORDCR1 : Unable to trigger outbound Idoc on PO Change

[Former Member]

Hi All,

I have done the following config for sending PO's from ECC to PI:

a. Message Determination:

Application = EF

Output Type = BAPI

Program = BUS2012_ICH_R3

Form Routine = SEND_PORDCR1

Transmission Medium = 8 (Special Function)

Dispatch Time = 4 (Send Immediately)

Have maintained condition records for the desired vendors with Function == LS, Partner == Partner No. for SNC Logical system

b. Partner Profiles:

Maintained an outbound partner profile under SNC Logical System with the following details:

Message Type = PORDCR1

Receiver Port = PI Port

Basic Type = PORDCR102

Trasnfer Idoc Immediately == Yes

But I have not maintained any entries under Message Control

Error:

1. Able to successfully trigger Idocs for New POs created in ECC.

2. But there is no Idoc output when PO is changed / deleted.

3. For the Chnaged PO on clicking on Messages, can see an output entry after change but it is in the status "Not Processed"

Am I missing any addtional config for trigerring Idoc on PO Chnage / Deletion ?

Regards,

Bharath

[Former Member · Accepted solution]

Hi Bharath,

In Partner profile for IDoc PORDCR maintain message control with application EF,message type ZSNC,process code ME10 change check box checked.

Now check and confirm.

Regards,

Nikhil

[Former Member · Accepted solution]

Hi Nikhil,

I tried the following Message Control settings for Message Type - PORDCR1 / Partner - SNC Logical System:

a. Application = EF; Message Type = BAPI; Process Code = ME10 ; Change Indicator = Checked

b. Application = EF; Message Type = BAPI; Process Code = ME11 ; Change Indicator = Checked

c. Application = EF; Message Type = BAPI; Process Code = ABI_AIDN_OUT (the only option available in dropdown) ; Change Indicator = Checked

I tried chnaing an existing PO after saving each of this setting. There is not outbound Idoc that is getting trigerred.

Regards,

Bharath

[Former Member · Accepted solution]

Hi Bhart,

Maintain below setting in message control:

a. Application = EF; Message Type = BAPI; Process Code = ME10 ; Change Indicator = UnChecked

b. Application = EF; Message Type = BAPI; Process Code = ME11 ; Change Indicator = Checked

Regards,

Nikhil

[Former Member · Accepted solution]

Hi Nikhil,

Even after mainitaing the settings as mentione by you, the Idoc is n ot getting trigerred on Change.

Regards,

Bharath

[Former Member · Accepted solution]

Hi Bharath

Could you please check the following customizing for your message output

ERP system-spro-Material Management-Purchasing-Messages-Output Control-Message Types-Define Message type for Purchase Order-Fine Tuned Control: Purchase Order

Check whether there are two entries for your Condition type BAPI Operation 1 and 2

Please let me know, whether this works or not? Try to work with fresh data

Regards

Vinod

[Former Member · Accepted solution]

Hi Vinod,

The Purchase Order-Fine Tuned Control: Purchase Order settings have been maintained for both the Operations 1 & 2. But still the output is in the status "Not Processed".

I wanted to update another observation for Po changes. Under display Pur. Order ::Output, under general data section :

The Locked Indicator is checked. The fiueld help for it is:

Output Locked

Use

Purchasing documents can be subject to a release procedure: If documents have not been released, the relevant output has this blocking indicator and cannot be processed (for example, printed or sent electronically).

Regards,

Bharath

[Former Member · Accepted solution]

Hi Bharath

In ERP-SPRO-MM-PURCHASING-PURCHASE ORDER-RELEASE PROCEDURE FOR PURCHASE ORDERS-DEFINE RELEASE PROCEDURE FOR PURCHASE ORDERS- RELEASE STRATEGIES

If you know the strategy id please select the line and go for details

Here look for Classification push button, there you will find which orders are blocked. If this is a mandatory supervision done by any user go back two steps, go to work flow, find the agent id and ask the responsible guy to approve the change, then the output will flow

Else please do not maintain the criteria in classification

Hope this should solve the problem

Regards

Vinod

[Former Member · Accepted solution]

Hi Vinod,

Thanks for the reply. The issue was due to PO Release Procedures / Version Management. It got resolved.

Apparently we need not maintain any Message Control in Outbound Partner Profile to trigger both the New / Change Po idocs when we are using PORDCR1. Its taken care by the Special Function / Program settings in NACE.

Regards,

Bharath