IDOC Acks not working

Hi All,
I have spent hours searching SDN for this specific problem, and can see some similar threads but none with a successful answer, so I will ask again.
I have the following scenario:
R/3 system sending an IDOC to XI, then XI mapping that to a custom XML message and sending it via the HTTP Adapter to an external business partner.
We have no issues with the above and get a chequered flag in SXMB_MONI.
But we want an Acknowledgement of that transmission to go back to the initiating IDOC in the R/3 system and update the status. e.g. If there was a HTTP comms failure and the message ended up in error in SXMB_MONI then we want that status sent back as an Acknowledgement to the original IDOC so that the R/3 system is aware of the failure.
We can see that XI tries to send the Ack back, but in SXMB_MONI in the "Ack Status" column there is an error associated with the Ack which says either "Acknowledgement not possible" or "Acknowledgement contains system errors". When we look into the error message contained within the Acknowledgement it says:
Unable to convert the sender service XXXXX to an ALE logical system
The Sender Service listed in the error message is the original Receiver Service which passed on the HTTP message to the 3rd party receiver. But in this case it is the sender because it is trying to send an Ack back to the R/3 system that is now the Reveiver. Note that it is a Business Service (not in SLD), it is NOT a Business System.
My question is - where is XI looking for an ALE Logical System name? My Business Service is not in the SLD (doesn't need to be, it's a 3rd party external system and I can send to it fine). I even tried populating the Adapter Specific Identifers for this Business Service with the IDOC Logical System name and R/3 System ID and Client, but that did nothing becasue this isn't using the IDOC Adapter, it's using the HTTP Adapter.
And note that we have SXMB_ADM param RUNTIME-ACK_SYSTEM_FAILURE = 1.
And please dont post a bunch of links, I've looked at every message in SDN that refers to the above. Please only reply if you can type the exact answer and it refers to the Acks only.
Thanks,
Brendan.

Hi,
Open(Double click) the Receiver Business service in ID and goto Change mode
goto Adapter Specific Identifiers---just give the LS name as HTTP and click on Apply and save Activate.
Do SXI_Cache also
Now try to post the Idoc Again from R/3
Regards
Seshagiri

Similar Messages

IDOC is not working

Hi,
We have 2 company codes and for the intercompany trade we are using IDOC to send invoices between the companies - it works perfect. Now we have added a third company code and the IDOC functionality does not work for intercompany trade involving the new company. All about pricing, requirements, PO, delivery etc. works without problems but the IDOC process does not start when we create the invoice - so i don't even have error to trace. I have created OBCA, OBCB, OBCD and OBCE and of course WE20.
A tip for the missing link will be really appreciated - thanks in advance
yu

With reference to this issue, please review note 106142 which has good
information on this behaviour.
Transaction OBCA is not really a customizing function since the table
as the partner numbers in the key, and these are master data, at
east in case of vendors (partner type LI). Thus, table T076B should not
ransport relevant. But there's been a couple of bugs in the lower
releases (note 106142) and they're fixed in release 4.70 and higher.
Similarly the tables like T076S as well as view V_T076S depend on master
data (like vendor master data), the standard settings of these tables
do not implicate transport requests.
Within note 106142 incorrect table settings in lower releases were
corrected to avoid the transport of these tables.
If you nevertheless want to transport changes of these tables you have
to undo the change of the recording routine in transaction se54.
For these tables change it back to Standard Recording Routine and save
the changes. Please do NOT generate the view.
But please keep in mind that this setting represents a modification
and possible problems due to this setting are not supported by SAP.
tr. SE54 ->
Table/View: T076M
select the radio-button 'Generated objects' ->
select the button 'Create/change' ->
frame 'Dialog data transport details' ->
'Recording routing' -> please, select option 'Standard recording
routing' and save your settings.
PLEASE, DO NOT REGENERATE THE VIEW !!!!
Further details which may be helpful:
You have to change
the view T076M for the transaction OBCD
the view V_T076S for the transaction OBCE,
the view V_T076K for the transaction OBCC,
the view V_T076B for the transaction OBCA,
the view V_T076I for the transaction OBCB.
Please also review the SAP notes.
356483     Customizing: Current settings in the test system
135028     Transfer IMG activity to current setting
106142     EDI: Customizing tables T076B, T076I,...
Regards
Vijayesh V V

Multiple IDOCs pattern not working

Hello, When I tried Multiple IDOC to single file pattern, it is not working as expected. Everytime when a idoc reaches XI, it is going to a seperate BPM queue and not collecting the IDOCs, any idea??

Yes, I have refered. I have done exaclty the same thing as in SAP Pattern for collecting multiple idocs to single file. Everything is working fine in BPM too. But the problem is whenever the idoc hits XI, it is going to a seperate BPM queue instead of a same queue. So single message for each BPM and BPM waits for 3 minutes (mentioned in BPM) and times out. But my need is all the IDOCs should come to a single BPM queue and BPM needs to collect all the IDOCs and send it as a single file.

WE20 - Pack size not working/IDOC packaging not working - PI 7.1

Hi all,
My requirement is to collect idocs and send to PI at one point of time in a day.
I kept Pack.Size = 100 in partner profile (WE20), in PI 7.1 - Sender Communication channel I assigned the same value 100 to pack size.
Now the problem is when I create more than 10 idocs and trigger manually by rseout00. for example
15 idocs are pushed to PI by executing RSEOUT00. In PI when I check IDX5 or SXMB_MONI, 2 message ID's are generated one with 10 idocs and the other with 5 idocs.
It works fine meaning creates only one message id if the total count of IDOC's are 10 or <10.
Any ideas/suggestions appreciated.
Thanks,
Krishna

Yes Prateek,
In Sender Communication channel - IDOC package size is assigned as '100' and only 10 idocs are collecting for one message id.
I checked the assignment and it was correct. I changed the description, saved and activated Sender agreement & Sender Communication Channel.
No luck.
Regards,
Krishna

Idoc Filtering not working

Hi All,
Requirement is to send an idoc to XI only if it satisfies the filter condition. Currently, the idoc is getting triggered even if the filter conditions are not satisfied. However the segment with the relevant filter fields does not appear in the idoc.
The config is complete in BD59, BD64, BD52 (for change pointers).
Does the filter in BD64 work at the idoc level or segment level? If at segment level, then what is the way to stop the idoc from getting triggered if it does not satisfy the filter conditions?
Thanks,
Shivali

hi
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
regards
ravish
<b>plz dont forget to reward points if helpful</b>

User eixt for modifying inbound idoc (delins) not working

hi all,
Inbound IDoc DELINS.DELFOR02 is sent from customer to vendor to create forecast delivery schedule lines (VA32). E1EDP16-WMENG has the delivery quantity and it is mapped to VBEP-WMENG.
I need modify E1EDP16-WMENG accordingly (based on some business rules) and this change should also be reflected to VBEP_WMENG.
I tried to modify the idoc_data in user exits: EXIT_SAPLVED4_002, userexit_zuordnen_idocs. During debug, I can see the idoc is modified, but the final forecast delivery is not updated (VA33).
Anyone can help?
Thanks!
Regards
Hui

Hi Sandip,
Inside userexit_zuordnen_idocs, i updated the table idoc_data_1 (I changed the delivery quantities of the schedule lines), but it dosen't work. In Va33, the delivery quantities are not changed.
Any other input?
Thanks!
Regards,
Hui

File to IDOC scenario not working

I have configured a file to idoc scenario and kept the XMl file in a shared location on XI server.
I have also created and checked the communication channels correctly.
Once Everything is done my xml file does not get picked up at all. Also the SXMB_MONI does not show any messages for my service.
How do I find out what is the error ??

Hi Kapil,
Just check the File path that was in shared location once and the file name is properly mentioned or not..
And also one thing after activating all IR and ID just goto SXI_CACHE and press <b>F6</b> to update cache refresh
And also in RWB --> Message Monitoring --> Adapter monitoring --> check the status of the sender
Regards,
Sridhar

IDOC Scenario Not Working

Dear All,
Yesterday I deleted the entry from SMQR transaction, I have SOAP->RFC->SOAP scenario it is working fine, but SOAP->XI->IDOC scenario is giving me the error , Please let me know how do I solve this issue.
Thanks in advance.
Raghavendra

Hi Ragava,
are u expecting the IDOC acknowledgments as RFC responds if so try to follow this links it may help you
setting up Audit Response.
Configuration Tips for a Business Service/Integration Process to send back ALE audit IDOC
Just set this parameter in SXMB_ADM >integration engine configuration>specific configuration--> choose RUNTIME --> ACK_SYSTEM_FAILURE.
It will send a acknowledgment in SXMB_MONI
regards,
Kishore

Notifications from IDoc processing not working right

I am having a problem where the IDoc error notifications are appearing in everyone's inboxes. I followed the instructions in SAP notes 44416 & 116610. If the tasks are set as general tasks, they go to everyone. If they are not general tasks, they go to no one. I checked the rule resolution for the tasks and they are resolving to the proper organization unit. Any ideas?

The changes only apply to new errors.

IDoc filter not working

Hi,
I've created a filter on my reduced message type from MATMAS in BD64. I'm filtering based on Plant (WERKS). But it isn't working... It sends out all plants using my message type. Is there some step that I've missed out???
-Vartika

Hi,
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for detail information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Hope this will help.
Regards,
Ferry Lianto

RBDAPP01 - First IDoc the CMOD works all subsequent ones don't..

Hi All
I have an interesting issue with RBDAPP01, I have developed a CMOD in Include ZXVEDU04 to block duplicate orders based on the cust PO number and to convert the quantity coming in if certain Units of measure are specified by the trading partners.
When I test this with a single IDoc in WE19 everything works as expected.
If however I process multiple IDocs using RBDAPP01- the first IDoc is processed successfully, but ALL of the subsequent IDocs do not work correctly...
The user exit is being called for all IDocs as there is other code in the exit that is working for all of the IDocs and not just the first..
Has anyone come across this problem before?
Your views on this would be greatly appreciated..
Many Thanks.

The issue was with a static variable that was not being re-initialised when each Idoc was processed, hence the reason why it worked for one and not for multiple IDocs.
Please note therefore that SAPLVEDA does not initialise its variables for each IDoc that is processed.

IDoc string field to JDBC date field - Not working

Hello everyone,
Once again I must ask you something that is keeping me..
I had a interface type RFC ASync to JDBC SQL Server, it was working fine. Then, I was asked to change to a type iDoc ASync to JDBC SQL Server.
At first, it was not a problem, just manual work. But them, I am getting an error.
In the RFC, I had a date field, that was directly related to the date field on the JDBC destination, so the mapping was pretty much straight forward. The SQL INSERT command was working fine on this cenario.
Now, in iDoc, this field was automatically converted to a string, and somehow, PI is not understanding that string has to be mapped to a date field in the JDBC.
Is there any 'workaround' for me to do this?
Thanks!
Ricardo Sancio Lóra
Brazil

The issue here is that somehow, the same SQL insert command that was working, does not work anymore.
This is the SQL command took from RWB log monitor:
INSERT INTO aniversariantes_sap (matricula, nome, nascimento, unidade) VALUES (00000070, 'Ricardo Lora', '19851216', 00000000)
If I run this query on my DB it works.
But, in PI, it's not, here is the error:
Could not execute statement for table/stored proc. "aniversariantes_sap" (structure "ANIVERSARIANTES_SAP") due to com.microsoft.sqlserver.jdbc.SQLServerException: Syntax error converting datetime from character string.
I´ve tried cast() and convert() using mapping 'habilities', but also, does not work. Work if I run in the DB, but not if PI runs it.
Wierd..
Ricardo

RBDMANI2 for IDOCs in error not working in Background..

Dear All,
    We have an ALE-IDOC scenario in which our IDOC gets posted in the destination system with status 51 as per business reqt. We schedule a job in the background using program RBDMANI2 which is used to manually reprocess IDOCS in error.
    This background job was working fine in the 4,7 R/3 Server, but we have upgarded the receiving system to ECC 6.0. Now the problem is dat when we try to reprocess the IDOC using this job, the IDOC are not processing further.. It ideally is supposed to do further processing as per the code writen.
We tried debugging the code(RBDMANI2) in background. But, its not helping.
Kindly advise.
Regards,
Santosh Reddy.

On primary research I found that there is a call to this FM 'SAPGUI_PROGRESS_INDICATOR' .
In that FM see line 12.
IF SY-BATCH <> SPACE.
          EXIT.    "do nothing in batch
       ENDIF.
May be this is the cause of your error.
Rhea.

Multiple occurence not working for extended idocs

hai friends
iam doing file to idoc senario in that multiple occurence is not working for Z segments.
it is extented idoc .
in taht multilpe segments are not creating only one segment is creating
what is the problem
pls help me
with regards
srikanth vipparla

Hi Srikanth,
You should map the node of the target side(the one which you want to occur multple times) to the node of the source side based upon which the target side node has to occur multiple times. For example lets say our source and target side structures are like this:
<Source>
              <Element1>
              <Element2>
              <Element3>
</Source>
<Target>
              <Element1>
              <Element2>
              <Element3>
</Target>
Now if you want Target to occur n times if Source node occurs n times, you should map Target node to the Source node. Even in case you want that Element1 of target side should occur as many times as many times you have Element1 of Source side, you should do the same.
Thanks and Regards,
Sanjeev.
PS: Reward points if helpful.

Inter-Company Billing via idoc FI & MM Not Working in Tandem

Hi,
Difficult choice where to post this as it crosses so many disciplines...hope there is someone who can help.
My problem is this:
We have an inter-company situation configured in our system, one company code supplies stock to another, the receiving company code is billed via an idoc and a FI doc is posted. This is all well and good, it works fine as a PO is involved and it is using the MM variant of EDI processing.
Now we wish to also use Cross Company Selling - this is where NO po is involved, simply the plant in the different company code satisfies the sales order.
All works up to the point of the EDI posting. It is set to work with the FI variant but the idoc does not process due to the error message: Enter document number from number range 51 for year 2009.
I understand what the message means: in the MM scenario the FI doc is created using the MM doc no for the vendor invoice receipt.
In the cross company sale FI scenario, there is no MM vendor invoice receipt so FI can't get it's doc No.
What am I missing?
Should I be creating a different FI doc in this process - maybe one that automatically assigns a No?
If so how does the EDI process decide which doc to create?
Any help gratefully received.
Regards
Guy

Hi Guy,
What i understood is that you are trying to clear manually. I suggest you to create a BDC from F-30 transaction which clears intercompany Billing Invoice (from the selling plant) and post an Debit on account of the other company plant.
Thanks
Rajjanikanth

IDOC Acks not working

Similar Messages

Maybe you are looking for