IDoc - JDBC, acknowledgment not possible

Hi Guys.
I've this scenario, It makes a branch, to a BPM and to a JDBC. The problem is, i got an error at the JDBC acknowledgment response (Acknowledgment not possible)
                        IDOC
Branch
               BPM                 JDBC
          No errors              Acknowledgment
        in acknowledgment        not possible
This scenario was made by a external consultant, and i don't know where is the JDBC acknowledgment defined.
Does anyone know, where can i modified this and disable the acknowledgment response for the JDBC?
Thanks in advance.

HI,
Go to BPM and check the Send Step .. Is it has mode as acknowledgement etc ?
Also check is Exception Branch has been defined ?
to suppress the ack for Idoc -[page no 10 - entry in table IDXNOALE in XI system
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Regards,
Moorthy

Similar Messages

XI IDoc Acknowledgement - Acknowledgement not possible status

Hi Experts,
My scenario:
SAP IDOC - XI - jdbc (oracle)
Problem:
Getting the infamous "Acknowledgement not possible" status in SXI_MONI. I only need the transport acknowledgements back to SAP not the application acknowledgements. The messages themselves route fine from source to destination.

check if this blog helps you:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
From the blog:
The system acknowledgement sent by the file adapter is converted into an ALE audit message and sent
back to the sender SAP system by an IDOC ACK channel configured in XI(an IDOC receiver adapter).
For your info:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Edited by: abhishek salvi on May 15, 2009 10:48 AM

Acknowledgement not possible though the message was sent successfully

Hello Everyone,
I have the following scenario below.
Sender = R/3
Interface = IDoc - stored procedure
Receiver = JDBC Adapter
I need 2 kind of acknowledgements.
1. If the message got an mapping error in XI/PI we need to send "any kind of ack" back to the R/3 to inform the Team that something happens during the mapping.
I do get a ALEAUD success message when a IDOC is sent to PI .
2. If everything is ok and the message was sent to the MSSQL- I gett an error like "Acknowledgement not possible". AnywayIi don´t need a ack if mapping in XI/PI is successful as it is a asynchronous scenario.
I think it is trying to send back an ack because i have a receiver IDOC channel defined for the R/3 receiver.
How can I get rid of this Acknowledgement not possible information ?
Thank you ,
Teresa

chk this:
1) http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
2) To suppress ack maintain the entries in table IDXNOALE (DO not request ack)

Acknowledgement not possible

Hi Experts,
Scenario : IDOC to JMS
when i trigger the idoc the message successfully sent to Moni but, i need to get the symbol of still awaiting acknowledgement instead of that am getting Acknowledgement not possible.
Please suggest me how can i do that..
Thanks & Regards,
Y.Raj.

But, R/3 system should get an default acknowledgement right when it reaches to XI either it's JMS and vice versa and i could have seen some of the interfaces which is related to IDOC to JMS which gets an acknowledgement to R/3
Regards,
Y.Raj.
Edited by: YeswanthRaj Kumar on Oct 6, 2008 2:42 PM

SXMB_MONI - weird message "Acknowledgement not possible"

Hi All,
I Am working on an async scenario of:
ERP -> IDOC -> XI -> PlainHTTP -> 3RDPARTY
I have now got the original message doing all that I want it to, I create it in the ERP system, it goes through XI and ends up at the right place. But I had a few problems with Acknowledgements. First off I had the seemingly infamous "Unable to convert the sender service to an ALE logical system" error, but by searching through the forum and some useful weblogs (thanks Michal..) was able to sort this out (still find it far from obvious that a 3rd party system needs an LS..).
And now my ALE Ack is (seemingly) successfully going back into my ERP system and if I look with Transaction WE05 it says it was processed successfully (code 53, using process code AUD1), plus in the RWB the acknowledgement is shown as having been processed successfully, but SXMB_MONI still shows the icon and message "Acknowledgement not possible" in the list of XML messages, although when I look at the details there are no errors... it is weird and I am tempted to ignore it as it does not seem to be causing any issues but I would love to know why it still displays this message.. any ideas?
Many thanks,
Chris

Hey,
Thanks Udo, I kind of suspected that it was ignorable but it is always nice to see only green lights and clean messages in RWB... So I will move on.. but am still a little confused though, as to what it means to say that acknowledgements are not supported? I can see that an acknowledgment is being created, sent and accepted back into the Sender system (which suggests a certain level of support for acknowledgements..)
So does that mean there are further acks that could/should be sent but are not supported? The acknowledgment documentation I have found does not seem clear on this. Perhaps I am getting the Ack from the IS but not from the plain Http adapter??
Many thanks for your help,
Chris

Acknowledgment not possible

Hi all,
I am doing IDOc to Soap scenario. the scenario working perfectly and data is updatain in target side also. But in SXmb_moni its showing Ack status as "Acknowledgment not possible". What is the reason could you please explain me and how to rectify this...
waiting for you valuable information.
Regards,
Kum

Hi,
this should be helpful:
ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Regards
Patrick
Edited by: Patrick Koehnen on May 5, 2008 3:03 PM

Http to file scenario generate "Acknowledgement not possible"?

Hi.
On PI7.1 we built a http to file scenario and used the RWB "Test message" functionality to test the interface.
Now we get a "Acknowledgement not possible" in sxmb_moni. How can we switch this off.
thanks

Hi
while sending request use either EO or EOIO for Asynch.
EO and EOIO, processing occurs asynchronously and the client only receives a confirmation of receipt with HTTP status u2018200u2019.
Read this
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm

Acknowledgment not possible ..File adapter ..receiver side

Hi XI Friends
In my Simple IDOC to File Scenario...
i am getting successfull meessage in SXMB_MONI.but in sxmb_moni ,the acknowledgment status is not possible.
my inbound inteface is of file and asynchrounous type.
how can i get acknowledgment .
please guid me.
thanks and regards
Ram

Hi,
File adapter does not support Application Acknowledgements.
In your case, turn of the Acknowledgements, by adding the entry in the table <b>IDXNOALE</b> in XI for the Sender Port and idoc type. After this, the Acknowledgement column in MONI will be empty.
Regards,
Bhavesh

IDOC Negative acknowledge not triggering system Exception

Hi guys,
I've a send step in my BPM which sends an IDOC and waits for the application acknowledge. After watching several threads, and specially SAP Note 837285, we can read that:
"Permanent negative acknowledgements: If the BPE receives a
permanent negative system or application acknowledgment, the
asynchronous send step waiting for it triggers a system error for
which you can define an exception handling."
Well, in my send step I've placed a system exception for handling this negative acknowledges but eventough I'm getting the negative application acknowlege from R3 (in SXMB_MONI I get the ack figure with a red cross indicating 'Ackonwledgment contains applic. errors'), the BPE doesn't trigger the system exception. Instead it enters in my deadline branch after quite a long time, ending the process....
Can you guys give me a hand?

Hi Ravi,
What is happening is:
After the idoc reaches R3, the Send step begins waiting for the ALEAUD ack from R3. I've got a System Exception for handling negative acks and a deadline branch for communication errors during the sending step... Meanwhile, the negative ack reaches XI (I can see it on the SXMB_MONI of XI) but the send step still waits for the ack. Of course, after the timeframe which was set for the deadline branch, the bpm will be completed because it jumps to that branch.
I can't figure it out why isn't the BPM catching the negative acknowledges..... :S If the acknowledge is error-free, the send step catches it and proceeds to the next step....
Any ideas? suggestions....? crazy attempts....?
The only point possible is the acknowledge received not being a permanent negative ack but a transient negative ack.... How can I check this IMPORTANT point.... ?
Message was edited by:
Gonçalo Mouro Vaz

'Acknowledgement Not Possible' Error message

Iam doing IDOC-XI-File scenario .
Iam able to write file successfully. But It lookslike creating acknowledgement. Since there is no routing possible, Iam getting this error in SXMB_Moni. A looked at File adapter as well. I have no clue. Lookslike I might have setup something incorrectly.. Would some one help me?
Thanks

Hi Ram,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
However IDoc adapter is requesting application acks. Therefore you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20handle%20acknowledgments%20for%20idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Also refer the guide: "How To Handle Acknowledgments for IDoc"
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Regards,
Abhy
Message was edited by: Abhy Thomas

Message Transferred to Business Service, but acknowledgement not possible

I have an IDoc to Flat File scenario. Flat file communication channel is in a Receiver Agreement for a Business Service.
The message posts fine, but in the acknowledgement there is the familiar problem:
"Unable to convert the sender service BSE_XXXX to an ALE logical system"
I have checked that the Business System has an associated Logical System, and that the Header of the Receiver Agreement has the Sender Service and Receiver Service fields populated. Still I get this problem.
Any suggestions?
BR,
Tony.

hi,
u cant send acknowledgement through the file adapter.
if u r using bpm then only u can do it
plz rewards points
vikas

About IDoc to file scenarios, ack not possible

I almost work out this scenario except one error in XI, T-Code SXMB_MONI
Acknowledgment not possible
detail info is "Unable to convert the sender service FTP to an ALE logical system".
Because I create two business service for SAP ERP and FTP, no technical system in SLD.
Of course I assign the Logical system name to SAP ERP, and FTP has no Adapter specific identifiers.
It is not Ok to create another Logical system and partner profile for this.
Is there any expert can tell me what to do in this situation?
Thanks for any suggestion.

> detail info is "Unable to convert the sender service FTP to an ALE logical system".
>
> Because I create two business service for SAP ERP and FTP, no technical system in SLD.
> Of course I assign the Logical system name to SAP ERP, and FTP has no Adapter specific identifiers.
> It is not Ok to create another Logical system and partner profile for this.
> Is there any expert can tell me what to do in this situation?
>
you need to do HEADER MAPPING in Receiver Agreement. Just define the sender logical system there and your problem will be solved...

Scenario:SAP-XI-AS/400; Ack not possible and DB insert issues.

Hi,
I have a SAP-XI-AS/400 scenario and I have two issues with the same.
1. When I trigger an IDoc to the XI system, I get ack status(in SXMB_MONI) as: "Acknowledgement not possible". The message is : "Unable to convert the sender service to an ALE logical system"
2. While trying to do a DB insert I get the below Error and DB insert is not happening.
" Error Unable to execute statement for table or stored procedure. '<table_name>' (Structure 'Statement_<table_name>') due to java.sql.SQLException: [SQL7008] <table_name> in <lib> not valid for operation.
Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. '<table_name>' (structure 'Statement_<table_name>'): java.sql.SQLException: [SQL7008] <table_name> in <lib> not valid for operation.
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. '<table_name>' (structure 'Statement_<table_name>'): java.sql.SQLException: [SQL7008] <table_name> in <lib> not valid for operation.
Error Exception caught by adapter framework: null
Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. '<table_name>' (structure 'Statement_<table_name>'): java.sql.SQLException: [SQL7008] <table_name> in <lib> not valid for operation.. "
I have been using the same kind of query we use for other succesful dB inserts.
Can you please give me a solution and suggest possible reasons and workarounds?
Thank you
Best Regards,
Smitha

Smitha,
Go through this links....
Some Experts discussions..
Error while updating JDBD table
JDBC Error
Error when executing statement for table/stored proc DB2 - Data Truncation
Hope this info is useful to you..
Thanks,
Satya Kumar

ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5

Hi All,
I am trying to configure ALEAUD in SAP->XI->JDBC scenario for Idoc acknowledgment.
I did following config in SAP
WE21 create port for XI
WE20 create Partner type XIDLOGSYS1 LS , Inbound parameter ALEAUD.
In XI I delete all entries from IDXNOALE table.
But still I am not receiving any ALEAUD in D02 when, any IDOC posted from SAP to XI.
In SXMB_MONI I am able to see Ack status Acknowledgment not possible
Please guide how to get ALE AUD in SAP from XI.
Regards

Before I ask my questions, please note I do have a copy of the "How To Handle Acknowledgements for IDoc" How To Guide. I just need some clarification from the group.
Here are my questions:
1. XI will not send a positve acknowledgement/status to let the sender system know it made it to XI ok, correct?
2. The only status that XI itself will initiate will be if there is a techncial issue with XI, correct? (Granted the Receiver system could send a positive or negative status back to Sender System) I just want to make sure that XI will not send a status back to Sender System that equates to "Triggering EDI subsystem OK" (or something like that)
3. How does the status of an idoc get set to 12 from 03? Does that mean that I always have the program RBDMOIND configured when I am interfacing to XI in order to force the status from 03 to 12?
4. As a norm, are those who are using XI seeing a 12 status on the Sender System IDoc Status?
5. If a techical issue error occurs in XI, what specific error status will be sent back to the Sender System?(if at all) I am looking for an example status number of what to expect.
6. If we are doing SAP R/3 to a partners XI system directly and that partner does not have RBDSTATE configured on their SAP R/3 environment and there is nothing else on their XI system for ALEAUD processing, I am out of luck in determining if the IDoc actually made it to their XI system, correct?
7. The Configure Scenario 2 in the document How To Handle Acknowledgements for IDoc" How To Guide should allow us to determine "did the Idoc get to that Server" correct?
Thanks for any feedback on this,
Ian

Availability time plan for recevier JDBC adapater ( IDOC-JDBC)

Hi
I am doing IDOC-XI-JDBC ( insert) .
We can use availability time plan for sender communication channels ( eg: Sender JDBC ). So the channel is available for only the specified period ( for example : 9AM to 8PM)
Query :
1) Can we use the Availability time plan for Receiver channel ( JDBC )?
2) If Yes, when I activate the time from 9AM to 10 AM , Then after 10 AM if it gets any data, I am getting error in communication channel monitoring adapter level.
If I start the channel with in 5 min then the message processed succefully. But how much time the adapter retries sending message to JDBC. It is giving error at adapter level which it shoudn't.
How to use availability time plan for receiver channel??. Why the message is giving error at adapter level instead of waiting?? will the waiting message success even after 2 hr or more also??
Thanks
Murali

> {quote:ti> Query :
> 1) Can we use the Availability time plan for Receiver channel ( JDBC )?
>
Not Possible.
> 2) If Yes, when I activate the time from 9AM to 10 AM , Then after 10 AM if it gets any data, I am getting error in communication channel monitoring adapter level.
Better way to handle this requirement is, schedule back ground job in ECC to trigger IDoc at specific time interval.>
> If I start the channel with in 5 min then the message processed succefully. But how much time the adapter retries sending message to JDBC. It is giving error at adapter level which it shoudn't.
>
>
Suppose you have started Receiver communictaion channel , when ever Adapter engine receive the message then JDBC adapter
will deliver the message to Data base, if data base connection failed due to some reason like Network issue or Data base down, in this case Receiver adapter tries min 3 times to deliver data to Data base, after that it will give error message.
You can set number retries and time interface by your self.
> How to use availability time plan for receiver channel??. Why the message is giving error at adapter level instead of waiting?? will the waiting message success even after 2 hr or more also??
Check audit log ,and post the exception here, there could be number of reasons.
Regards,
Raj
Edited by: Raja Sekhar Reddy T on Apr 25, 2011 6:32 AM

IDoc - JDBC, acknowledgment not possible

Similar Messages

Maybe you are looking for