BPM - IDOC System Acknowledgements from R/3

Hi My scenario is File-XI/BPM-R/3(Idocs).
In Integration process, we configured 'system ack' in Send Step which sends Idocs to R/3 system.
BPM Process stays in 'STARTED' state forever though XI received acknowledgement ( in SXMB_MONI, on the main screen ACk Status is in '?'mark meaning its still waiting for Acknowledgement. But the moment you click on the message Ack status becomes 'Ack received' and BPM ends".
This seems to be a bug.
How can the Acknowledement staus changes the moment you clike on the message?. Does anyone have same issue?. Any suggestion will be appreciated. we are on PI7.0 sps6.0 environment.
we donot want to deal with ALEUPD..so please do not suggest to config ALEUPD.

HI,
see the below
The Business Process Engine supports Acknowledgments when sending asynchronously as follows:
Acknowledgment------     Processing of Send Step
Receiver system does not support requested acknowledgments ---     Send step completed successfully
Positive acknowledgment----
     Send step completed successfully
Permanent negative acknowledgment------     Send step triggers system error for which you can define a specific exception handling.
Temporary (transient) negative acknowledgment-------     Send step continues to wait because the temporary acknowledgment can still change to a permanent or negative acknowledgment. This can occur in the IDoc environment in particular, for example, when a user intervenes.
Exception or error handling within the integration process is not possible. However, using message monitoring you can determine whether the acknowledgment is temporary or not.
Acknowledgment with multiple receivers     A message sent from a send step can have multiple receivers. In this case, the system duplicates the message accordingly. Acknowledgments returned from the respective receivers are ignored and the send step continues to wait.
If multiple receivers are possible and you want to evaluate the individual acknowledgments, you must define the integration process accordingly. To do this, determine the receivers in a receiver determination step and send the message to the individual receivers in a loop.
For more information about acknowledgments, in particular how they are used in the adapter environment,
Note: see SAP Note 837285.
Regards
Chilla

Similar Messages

How to get rid of system acknowledgements in JDBC adapter

Hi,
I've set up a receiver JDBC adapter.
It works good, but sends back acknowledgements which i dont want
On help.sap.com i found: "....If you want to prevent a synchronous system acknowledgement from being sent back, even if the sender requests it, set XI.AckFinal=false....."
In the channel configuration i'm on tab "parameters" >> tab "advanced" and i checked the box "advanced".
I get "additional parameters" screen
There is a box where i can fill name and value for parameters.
If i put:
name = XI.AckFinal
value = false,
i still get the acknowledgements from the database.
What must i do to get rid of the acknowledgements?
Thx.
Robert

Hi Srinivas,
I think you are referring to the tab "module"
What i am referring to is the tab "parameters" , etc etc.
I dont think i would need an additional module to get rid of the system acknowledgements.
Thx.

XI acknowledge from BPM

HI Experts,
Trying to make acknowledge from XI to R/3 through BPM but get error message Unable to convert the sender service <BPM_Process> to an ALE logical. The XI process flow is from SAP with Idoc to XI BPM and to JDBC. Have check setting in Adapter specific identifier which has logical system. Could experts have same experience before, please advice?
Thanks in advance.
Katjun

Hey,
Have you maintained all the ALE setting from R/3 to XI > and the Port on Idoc Adapter IDX1 >? Once try to specify Adapter Specific identifier to the bpm process .
Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*

System Acknowledgement IDOC - XI - File

Hi all,
Is it possible to receive a system aknowledgement from the fileadapter when a message (IDoc) has passed trough the adapter engine, without using BPM.
Not a application aknowledgement! but a system aknowledgement!
When I try I get the following message in the IDoc monitor: "aknowledgement not possible".
And guys, please do not post one billion links. I have gone through them all, and they don't give me the answer.
Thanks

IDOC outbound from R/3
SNDPRN - R3SNDR
RCVPRN - FILERCVR (assume with these parameters idoc is coming to PI)
IDOC Business system should have adapter specific identifier as - R3SNDR
File Business system should have - FILERCVR
While generating ALEAUDO1 it will have from PI
SNDPRN - FILERCVR
RCVPRN - R3SNDR
SO in R/3 you should have partner profile FILERCVR with inbound processing for ALEAUD
Hope its clear
Rajesh

Acknowledgement from receiver file Adapter with out BPM

Hi Gurus,
I am trying to get Acknowledgement from Receiver file Adapter with out Using BPM.
Here is the scenario. I am sending files from different Sender Adapters. There is only one target that is File Adapter. After each successfull and failure transaction I need an Acknowledgement that needs to trigger another receiver adapter and send the the file name and timestamp to that file.
Hope this is a complicated scenario. Please help me.
Thanks,
Kevin

from sap note 821267
6. Acknowledgements
    * Q: Does the File Adapter support acknowledgements?
    * A: You need to distinguish system acknowledgements (indicating that a message has been received by the target system) and application acknowledgements (indicating that the message has been successfully processed by the application on the receiver side).
           The receiver of an XI message will only send an acknowledgement back to the sender if the sender has requested one. However, the File Adapter has no functionality that relies on the receipt of an acknowledgement, so it never requests one.
           On the other hand, if a File Adapter Receiver receives a request to send an acknowledgement, it will do so for a system acknowledgement request. Application acknowledgements are not supported at all as the File Receiver has no way to determine if the written file has been correctly processed by the back-end application, which is what a positive application acknowledgement would imply.
this means that your requirement is ideally not possible without a BPM

How to send application acknowledgement from R/3 system

Hi guys,
How to send application acknowledgement from R/3 system. Ex. we have post one IDoc and check user validations. Suppose date is wrong that means indicate earlier or wrong date but date format is correct. In this situation we need send one acknowledment to sender.
How to find the solution? pls tell anyone.
Regards
Vijay

Hi Vijay,
Plz do perform the following steps:
1) In the Integration Server, call transaction SE38
2) Run program IDX_ALEREQUEST to process IDocs with message type ALEAUD as XI request
message.
3) Now Enter Sender Port, Sender Client,Partner Number, Partner Type, and Partner Rol
4) In Integration Directory, configure the routing of interface
5) Call transaction SXMB_MONI to display the XI message.
Also,
Further in IDX5 as well you will find entry for IDoc ALEAUD.ALEAUD01
Please go through the link
1)Succesful IDOC acknowledgements from ECC
2)https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
3)https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
After you triggered the IDoc by e.g. tcode: WPMA and IDoc reached FILE system, FILE receiver CC actually is only able to send acknowledgment types SystemErrorAck and AckNotSupported.
This is because:
- IDoc sender adapter requests the following acknowledgments:
SystemAckRequested="false"
SystemErrorAckRequested="true"
ApplicationAckRequested="true"
ApplicationErrorAckRequested="true"
- File receiver adapter that run on the Adapter Engine support system acknowledgments and system error acknowledgments if they are requested by the sender. These acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed.
If you havent suppressed acknowledgments for IDocs WP_PLU in IDX_NOALE in XI then you will get:
SystemErrorAck when message has not reached the FILE system
AckNotSupported for all others acknowledgement types
QQ) Will this IDOC Ack applicable for this scenario???
Rather not, since FILE adapter does not support any other acknowledgements then system and IDoc adapter does not request other acknowledgements then application + SystemErrorAckRequested.
In sender system your IDoc will be always in status 39 (instead of 03), when acknowledgement is turned on.
This is because:
For SystemErrorAck the corresponding ALEAUD status is 56
For AckNotSupported the corresponding ALEAUD status is 50
Both inbound 56 and 50 statuses end up in 39 for your outbound IDoc in sender system.
Q1) Will this ALEAUD Idoc contains any Message from File System????
In both cases, it will result in status 39 - IDoc is in the target system. So it does not matter.
Q2) Basically what Information will contain this IDOC Ack.
Idoc number from sender system and status 56 or 50 depends on acknowledgement type.
Q3) Do we receive any Info from the Target File System , if we implement this Ack concept??
Nothing useful.
Remember that File Receiver has no way to determine if the written file has been correctly processed by the back-end application. However, if your FILE application can read your WP_PLU message and after successful processing is able to generate any kind of message then you can acknowledge the communications but you will not be able to link original message with the acknowledgement request message.
To do that you need to configure just normal scenario (that will be your new acknowledgement scenario) FILE -> XI -> R/3. Your FILE service will send ALEUAUD Idoc to R/3 system. Your FILE application must take care to generate proper ALEAUD XML message. In order to treat ALEAUD as a request message (not standard acknowledgement) you need to run IDX_ALEREQUEST in SE38 on XI.
Q1) It means if the Idoc not reached to Target File system means we can able to get the System Error Ack to Sender SAP R/3 System. Am i Right????
Supposed you have turned off acks on XI (tcode: se38, IDX_NOALE) for your sender port/client:
You have sent the IDoc and the last status is "03 - Data passed to port OK"
You don't know whether it was even delivered to XI ...
Supposed you have turned on acks on XI (tcode: se38, IDX_NOALE) for your sender port/client.
1)
You send and IDoc and it has been delivered successfully to FILE system.
Adapter Engine creates acknowledgement type: AckNotSupported
In XI you can see Ack Status: AckRequestNotSupported (Acknowledgement not possible). Category: permanent.
XI will send ALEAUD IDoc to R/3 system: status "50 - IDoc is added"
The IDoc status in sender will be "39 - IDoc is in receiving system (ALE service)".
2)
You send and IDoc and it has not been delivered successfully to FILE system. e.g. FILE server is down.
Adapter Engine creates acknowledgement type: SystemErrorAck
In XI you can see Ack Status: Error (Acknowledgement contains system errors). Category: transient.
XI will send ALEAUD IDoc to R/3 system: status "56 - IDoc with errors is added"
The IDoc status in sender will be "39 - IDoc is in receiving system (ALE service)".
So status 39 means only that IDoc reached XI, but you don't know whether it was delivered to FILE system or not.
Q2) And one more thing is Even though we are dealing with the IDOCFile OR FileIDOC we can able to get the ACk of Type System Error Ack only. Am I Right?????
No, "Sender adapters of the Adapter Engine do not request any acknowledgements."
Q3) So the same case( Which we disscused for IDOCFile) is Applicable for FileIDOC also????
No.
Can we able to get the System Error Ack, if the File is not reached to SAP R/3( Target here)
No.
Q4) If Yes to Q3 means,Where this System Error Ack will be seen in File System side???
Do we need to do any extra settings to receive these System Error Ack at File system side??
Not relevant.
Regards,
Vinod.

IDOC with extension from external ECC system

Hello experts.
I have a scenario where I need to receive an IDOC with extenstion from an external system.
how can I define the xsd of that IDOC in my PI system?
will I need to receive an xsd file from the external system and import it as an external defenition?
how is it done? (this 3rd party doesn't have a PI system, so they can't export XSD like me)
another option is to build a similar IDOC with extenstion in our SLD, and import it into the PI system... but it seems a bit problematic.
I'll be happy to hear suggestions from people who had to implement a similar scenario.
thanks,
Imanuel Rahamim.

Hi,
Three questions:
1. how your external system will send to you the data: by an Idoc-XML file ? or by directly an IDoc (so with an ALE config) ?
if it's ALE config, then you should have also a connexion to this Ext. ECC system, for instance to return back an acknowledgment. And so, if you have a connexion, you can import this IDoc into PI.
If it's a file, they have to provide to you an XSD file, that you can use as External Def, and create a Service Interface. So it will be not really like an IDoc, but like all other message which look like an idoc.
2. with this ext. ECC system, do you have a logon connexion ?
if yes, you can import this IDoc into PI.
3. Do you have to send the same IDoc to your own ECC system ?
if yes, that means the extension has to be developped in also in your own ECC. In that case, you will be able to import it PI and use it for source and target.
> how is it done? (this 3rd party doesn't have a PI system, so they can't export XSD like me)
you can find on SDN, some program to generate an XSD from a DDIC table/structure, but for complete IDoc, I don't know.
Anyway, if it's really an ECC system, the better way to exchange data, it's to do an ALE config from their system to your PI, and no issue to import the IDoc def in PI.
regards.
Mickael

IDOC to and from eternal system

Hi All,
I've following scenario:
Sender SAP R/3 system is sendind IDOC of type say A to XI system, XI system is mapping IDOC of type A to say IDOC B, then finally XI is sending IDOC B to receiver SAP R/3 system [External system}
Note: Reverse scenario is also there in which we are receiving IDoc from external r/3 system and mapping it to different IDOC in XI then sending to SAP System.
Development done so far:
ID:
I've imported IDOC A in XI. SInce I didn't had authoriztion to import IDOC B from target so I asked client to provide XSD od IDOC B.
I created one inbound message interface using IDOC B XSD and also completed the mapping part using same XSD.
IR:
I've created one IDOC receiver communcation channel for external system. I completed the configuration
ALE:
I've created on RFC destination of type 3 to connect external SAP system. I created port in IDX1 for IDOC communcaition.
Problem:
When I am sending IDoc to exxternal sap system then message is getting failed in moni. IDoc adapter is not accepting the message interface creted based on IDoc XSD.
I believe I need to import IDoc meta data from target system for IDOC B. since in XI i didn't imported IDOC instead I used IDO XSD.
it may be the reason.
Please help me to solve the problem

HI Experts,
I am doing testing of my scenario.
As I've described the scenario in my last post. I am sending a IDoc A from my sender system and traslating it to IDoc B in XI, then sending it to the external SAP system (SAP 4.6). Basically IDOC XI IDC scenario but with the slightly change of converting one idoc to other.
During test:
I received following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Trace:
<Trace level="1" type="T">Parse XML-BODY</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPLSD</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
I've created one idoc port in XI named 'SAPLSD' inside I've used RFC destination to the target system. During runtime metadata is not loaded in IDX2.
When I tried importing metadata manually, i received the following error
"No RFC destination is maintained for the port"
is there any particular naming i should use for idx port and for rfc destination??
what could be the problem?? ....
Q. is it because of the RFC destination is not OK or
Q. the I do not have proper authoirsation to import metadata from LES system or
Q. Since target system is SAP 4.6 system.... is it could be the problem? [Unicode]
Please suggest

IDOC Message coming from R/3 system to XI , but waits in Qeue

IDOC Message coming from R/3 system to XI , but waits in Qeue
XI doesn't send the message FTP receiver.In XI sxmb_moni the "c" column contains green flags that mean "message scheduled on outbound side".
In smq1 It writes "SYSFAIL" means "Password logon no longer possible - too many faile"
But I use "anonymus" in FTP adapter. Which password is this, which component is related with this error.
How can I do?
thanks

Hi Cemil,
it may be that the FTP server where you want to send your output file does not accept anonymous connections.........so just get the username and password of that FTP server, which has access to do FTP to that machine, for doing ftp to that machine, then your output msg will be FTP to your target FTP server........
Thanks,
Rajeev Gupta

Succesful IDOC acknowledgements from ECC

Dear MDM gurus,
What is the best way to handle acknowledgements from ECC (INTO MDM) for inbound IDOCS from MDM (MDM->XI->ECC).
We want it such that when an IDOC gets posted into ECC succesfully,it should send an acknowledgement signal back to MDM saying that IDOC was received properly.
Thanks.

HI Mugdha,
I have a concern on the Acknowledgement (ALEAUD) Idoc. I have implemented this scenario wherein DEBMAS IDoc is posted from MDM -PI - ECC and ECC sends back the acknowldgement using ALEAUD Idoc.
However, in PI (SXMB_MONI) there is no separate message entry created for this acknowledgment. The ALEAUD acknowldgement message details is attached to the original DEBMAS message which was triggered from MDM - PI - ECC. Due to this, PI interface created is not able to read the acknowledgement message and process it to post/dump the target file onto the MDM Port.
I tried triggering and ALEAUD Idoc manually using PI - RWB which generated a separate message for ALEAUD Idoc in sxmb_moni and then my target file was created in MDM (But this is just a manual way of testing the PI interface).
Can you advice on how this concern can be dealt with?
Thanks in advance,
Elizabeth.

PO acknowledgement from vendor in system

Hi gurus,
PLease let me know the procedure for getting acknowledge from vendor for PO...
Once po created , how to get acknowledge and what are settings required for the same.. how to use that option..
plesae explain..
thanks in advance

Vendor Acknowledgment can be used with Confirmations Concept
After Receiving PO, Vendor will notify you acknowledgment through mail/phone/ some other source.
Then, in ME22N, In the Item Details, Confirmations Tab (BELOW),
You Acknowledge the materials,...
Then only system will allow you to do GR in MIGO.
You have to activate Confirmations In SPRO,and Vendor Master data
Edited by: Anand K on May 1, 2008 3:17 PM

IDOC to JDBC:System Acknowledgment

Hi,
We have a scenario IDOC-PI-JDBC. We are using PI7.31 single stack.
We need to get the System acknowledgement, and we want to update the status of the IDOC accordingly(error/successful) once its processed.
-Is it possible in IDOC to JDBC flow?
-As per my understanding in IDoc sender channel we should check the acknowledgement option. Other than this do we need to do any other setting to get the system acknowledgement?
-Does JDBC receiver adapter by default sends the system acknowledgement ?
- Can we get the acknowledgement if we have multiple receivers?
Please help with info.
Thanks,
Tina

Hi,
JDBC by default is synchronous. Just create the inbound service interface as synchronous and test, you will find the response. you build the response ICO based on the structure. Even if it insert/delete/update statements, JDBC will return the number of success records. Check the help documentation on JDBC.
As IDOC is asynchronous, you can not do it directly. but you can achieve this using request response bean.
--Naresh

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

IDOC - XI(BPM) - IDOC

Hi,
Does anybody has a documentation regarding how to set up an IDOC - XI - IDOC scenario using a BPM. Coz' currently I have an error from BPM - IDOC as the error "Unable to convert the sender service SC_PO_idoc2idoc to an ALE logical system". SC_PO_idoc2idoc is my BPM.
Thanks
Zubair

I've done all the necessary however still giving me the same problem, one thing I realize our XI box is currently running on SP10 this could be the problem so we've decide to upgrade it to SP11.
1. we have sp10 and the problem doesn't exist
Integration Directory and just happened that same Logical system has been used by another system then it would raised an error to my BPM saying "Check Result for Object SC_PO_idoc2idoc Logical system M01CLNT200 already exists in service | BS_JOBSKL_200" when I'm trying to SAVE the changes to my BPM.
2. but if you have 2 different systems why are you using the same name? they must be different as they represent 2 different systems
Is this a bugs in SP10 as well, do you face any problem like this before. Because if this is an issue then it will be a disaster if we have many interface coming into XI and need to be send to one same BS which the logical system is unique.
3. Like you wrote "logical system is unique" so you can't have two business systems with the same logical system name
This means that "to be send to one same BS which the logical system is unique" can be easily achived - don't worry.
regards,
michal

IDoc Transport Acknowledge doesn't return to PI 7.0 automatically

Hi all,
I realized an Integration scenario in which PI 7.0 generates custom IDocs messages (like MBGMCR) and send them to a SAP system (4.6 C). In particular there are the scenario steps:
1. BPM -> IDoc msg
2. IDoc msg transport ACK -> BPM
3. BPM -> JDBC updating
When SAP receive IDocs must send back to PI the related Transport Acknoledgement in order to complete the Integration Scenario with JDBC updating.
So I observe that, if I don't refresh IDoc messages on SXMB_MONI, the Transport ACK doesn't return back from SAP to PI and the BPM remains pending.
Any ideas?
Thanks in advance,
GB

Hi Gaurav,
could you please tell me which are these parameters:
- partner number (for the receiver)
- partner type (for the receiver)
- partner role (for the receiver)
In my scenario PI 7.0 sends IDocs to R/3 so the receiver (written in the point 3 of the link you sent me) should be R/3.
It's right?
I'm unable to find the Parner Role. In which transaction can I found it?
Thanks,
GB

BPM - IDOC System Acknowledgements from R/3

Similar Messages

Maybe you are looking for