Turn of acknowledgment for IDoc - XI - BAPI Scenario

Hi,
i have a smal BPM where i am sending an IDoc from an
3rd PArty System -> XI (making some mappings) -> SAP
everything works fine, but in the end i get a Errormessage in the
MessageMonitoring on my runtimeWorkbench.
the error occure when XI try to send an acknowledgeMessage
back to my 3rd Party System.
I there a way to turn the request for Acknowledgement of?
Thanks 4 help,
Benjamin

Hi,
on my 3reParty System i am generating an IDoc,
an send it to an Abstract Asynchronus
Messageinterface on my XI IntegrationServer.
This works fine.
Also the synchron BAPI-Call to the SAP system works.
But in the end after all is done the XI system
try to send an acknoledge back to the 3rd PartySystem.
How can i turn off this acknoledgement?
I think i must turn it off in the beginning. this means i must turn it off on my initial IDoc-call.
but how can i do this?
thanks
Benjamin

Similar Messages

Acknowledgement for Idoc To File Scenario

Hi Experts,
My scenario is idoc to file and if the file is successfully delivered at destination then i need an acknowledgement saying that the file was received successfully.
How to achieve this. Can any body send me the scenario with screen shots.
Your help will be greatly appreciated.
Thanks & Regards,
Venkat

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Sending Acknowledgements for IDOCs

I have reviewed the document "How To... Handle Acknowledgements for IDOC" and "Configuration Tips for a Business Service/Integration Process to Send Back ALE Audit IDOC". These don't seem to work for the situation I have.
We have two R3 systems sending IDOCs to XI, one located in the US and one in Germany. The above documentation (from what I can tell) expects you to only have one R3 system. For example, when setting up the Adapter-Specific Identifiers, there is only one spot to enter in the Logical System or R3 System ID.
Is there a way to set up IDOC Acknowledgements if you have more than one R3 system that can be sending IDOCs?

Hi Larry,
for each R/3 create one business system service. Depending of the control data in your idoc (you can examine the sender R/3 system in the IDOc header data) create different receiving systems.
Regards Mario

Setup for IDoc-XI-File scenario

Hi All,
Please provide info where can I find, step by step documentation for the basic setup on R/3 and XI areas, before start developing IDoc-XI-File or File-XI-IDoc scenarios.
Thank you,
Sree

Hi,
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
File -> IDOC ->
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
(It concentrates on XSLT mapping but also gives an idea about the configuration part. Do go thru that, it might help you.)
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope I have answered your query.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

Error in Operation Mapping for Idoc to File Scenario

Hi Experts,
I am doing Idoc to File Scenario for Timesheet IDoc "HRSM_C" and following step are through,
Sender agreement --> Receiver Determination --> Interface Determination
got stuck in Operation mapping, it sahows error
"Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1"
Also not all the fields of IDoc HRSM_C are transferred to the XI server as I am unable to see all the fields in xml file using transaction idx5, as I suppose the reason behind may be there are no values in those fields.
Please suggest how to resove the issue and transfer all the fields from R3 to XI in Idoc eventhough it doesn't contain any value.

Hi
Refresh CPA cache using user PIDIRUSER.
Look Note 951318 for Mapping Cache Refresh.

Error in TRFC for IDoc to File scenario while sending IDoc

Hi,
Configured of 'IDoc to file' scenario is completed. Executed a stand alone program to post IDocs to XXI system using a RFC destination with required previleges.
Outbound IDoc has status successful, but it is blocked in the source system and can be viewed in TCode: SM58 (Transaction RFC). The error status is set as ':00'.
When I tried menu item 'Edit>>Execute LUW', I got the status message as 'Function module does not exist or EXCEPTION raised'.
For your information, User used in RFC destination is communication user with SAP_ALL profile(in XXI system).
Can anybody help me out in resoving the error?
Regards,
Suraj Kumar

Hi,
Thanks for your reply.
It is successfully tested and FYI as the user specified in RFC Destination is a communication user in destination system (XI), it does not have remote logon.
Hope I am clear.
Please let me know, if you need any further information.
Regards,
Suraj

Questions to a Mapping for IDOC-to-File Scenario

Hi all,
I want do develop a Message-Mapping for an IDOC-to-File Scenario. A SAP System sends an IDOC to the XI-System and the XI-System should make a mapping an send a XML-File to a FTP-Server. The Strukture of the target message is very easy:
<xdoc>
 <Invoice>
 @purno
 <HeaderInfo>
 <invno/>
 <shipdate/>
 <extvalue/>
 </HeaderInfo>
 <DetailInfo>
 <LineItem>
 @lineno
 <vpartno/>
 <descrip/>
 <qtyord/>
 <cost/>
 <vendmemo/>
 </LineItem>
 </DetailInfo>
 </Invoice>
</xdoc>
The source message is an IDOC. This IDOC can contain one or more positions (E1EDP01). Those different positions should be mapped into different LineItem's (see target structure) -> so in the target file one or more LineItems can appear.
Is it possible to implement this process with a common message-mapping or have I to implement a business process?
Thanks
with best regards
Christopher

Hi Christopher,
Is it possible to implement this process with a common message-mapping or have I to implement a business process? - This thing is possible with common message mapping......you dont need business proces for it.......in msg mapping after taking the source IDOC and target xml struc, map the E1EDP01 field to LineItem field.......just check the occurance of these nodes.....it should be 0..unbounded.........so as many E1EDP01 nodes will be there in idoc, that many LineItem nodes in target will be created.......
Thanks,
Rajeev Gupta

Do we need a sender channel for IDOC to file scenario.

Hi,
Do we need a sender channel in IDOC to FILE scenario.
Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
What is the reason for this?
Regards,
Younus

Younus,
to add more...
From WAS(Web Application Server) 6.20 and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
And it has got ABAP and JAVA engine in it.
It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.

The SAP Web AS 6.10 did not have a Java engine.
and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
Hope i cleared ur point...
Cheers,
Raghavesh
Message was edited by:
Raghavesh Reddy

Acknowledgement for R/3 - XI scenario (IDOC)

I am sending MATMAS04 idoc to XI and I need to get the acknowledgement back.. I am following the steps as in this weblog,
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Do I need to go to R/3 and update BD54 with the logical system name, that we attach to the business service? (I am not doing that currently).. I just put a logical system name (not same as business service name), creating receiver agreement to send from business service back to R/3
i am getting 'acknowledgement not possible ' icon.. but when i look at the details, no error flag is raised and the acknowledgement idoc is not created..
Am I missing something?

check this
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe

Error is Receiver AS2 adaptor used for Idoc to AS2 scenario

Hello Experts,
   I am doing Idoc to AS2 B2B scenario where I am getting below error message in runtime workbench comm channel monitoring.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..
Sending failed.
Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 10/16/09 9:06 AM >> Description: AS2 Adapter failure Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321)
AS2 Adapter failure
Processing task
Sending called.
Message processing started
Basis has already configured the AS2 Server with Certificates and provided me the below details for receiver agreement and those are put in Receiver agreement.
AS2 sender Configuration:
Authentication certificate à TRUSTEDAS2certAS2_datapool
AS2 Receiver Configuration:
Decryption Key à TRUSTEDAS2certXXXenterprise2008
Signing Key à TRUSTEDAS2certXXXenterprise2008
XXX is my receiver partner
For the Receiver party XXX I have maintained the Identifier as given below
*Agency----
Scheme-------Name*
http://sap.com/xi/XI--XIParty--
XXX
Seeburger----
AS2ID----
XXX_AS2ID
There is no need for sender agreement for Sender IDoc but still I tried to created R3 as sender party and R3 Business system, used it for the scenario and created sender agreement for sender Idoc but received same error message in Runtime workbench.
R2 system sender party is also set with identifier with AS2 ID.
MDN mode is set to no MDN in the receiver AS2 communication channel.
Please suggest me if something is missing or wrong in the configuration.
Thanks in advance.
Vinit

Hi Larry,
   The solution was very simple.
It was problem with the basic understanding of system and configuration.
Idoc is send sent by R3 ERP system and target is Partner Party. As ERP system is Business system and not the party w.r.t XI/PI terminology, we are not supposed to use Sender party as Sender ERP system but just use Business system as sender without any sender party. So in this way PI system could recognize that the data is coming from R3 system which is nothing but PI Business system.
Now question comes where to user the Serder Party which was defined with AS2 ID? So answer is in the receiver determination we have to mention the Sender party and sender service in the header mapping part (Also mention receiver party and service).
So in my case problem was with sernder party. I mentioned sender party in all receiver determination, Interface determination, Sender Agreement and receiver agreement where only sender service ie sender system was required. And as I configured my scenario without sender party it worked because PI could recognize the sender R3 system and AS2 ID was recognized form the Header mapping of Receiver Agreement.
Kindly let me know if it works and if you require snap shots of my configuration then I can send you the same.
Regards,
Vinit

ALEAUD Acknowledgement for Idocs in XI 3.0

Hi,
I need to know if it's possible to update the status of the original Idoc (sender Idoc) with the status of the new Idoc generated into XI 3.0 once it is saved and executed correctly in receiver (receiver Idoc).
Is this scenario configured automaticaly or is it necessary to create the interface for this Idoc type explicitly?.
The problem is if XI is able to update the status of the original Idoc in the sender R/3 system when the receiver save another Idoc changed and mapped through XI.
If is it possible, what is necessary to do in XI to prepare this?
In the backends side is it enough with add the Idoc Type ALEAUD in Partner Profile (Inbound in one way and outbound in the other?
Thank You

Hi Luis,
the post is a little bit old, and maybe you already have the answer, if not take a look at this guide https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
That should contain everything you need.
With Business Connector I used to send SYSTAT01 from BC back to sender R/3 and it did update the original IDoc status. I don't think this message is natively supported with XI, but I guess you can achieve the same result with aleaud.
Cheers
Alex

Unable to convert sender service for IDoc to SOAP Scenario

Hi,
I tried to find the solution my way and by using the search function but without any success. I have the folowing scenario:
SYS(my sap system) => IDoc => PI (Process Integration) => SOAP => XML
When i send the IDoc to the PI System and open SXI_Moni the folowing error is shown:
"Unable to convert the sender service receiver_service to an ALE logical system"
I read about Adapter Specific Identifies so i go to ID->Service without partner->Business System->MyBusinessSystem(SYS) then in Menü on Services and checked Adapter Specific Identifies. They are like maintained in SLD.
Next is a Cache refresh i tried a full one but no impact
Then i tried a header mapping in receiver agreement. I mapped there the receiver party to the definied receiver party and the receiver_service to the service.
I have no idea
Thanks for help, be sure that helpful answers will be awarded
regards
Matthias
P.S. What causes this error ? For my opinion ALE has already done all neccesary things (The Idoc is in PI System and the data is available in mesaage payload) so why didn't the pi map it and send it via Soap?

Hi Matthias
>>I dont know if its helpful but in SLD are only the system of our landscape so i have no entry for the external Party.
Party information is generally not required to be maintained in SLD
>>Adapter Specific Identifies
What is the value you have given for sender Business system->adapter specific identifier. Is it the same as the partner profile name in sender SAPECC. if not try making them same.
Regards
Suraj

Character Encoding for IDOC to JMS scenario with foreign characters

Dear Experts,
The scenario is desribed as follows:
Issue Description:
There is an IDOC which is created after extracting data from different countries (but only one country at a time). So, for instance first time the data is picked in Greek and Latin and corresponding IDOC is created and sent to PI, the next time plain English and sent to PI and next Chinese and so on. As of now every time this IDOC reaches PI ,it comes with UTF-8 character encoding as seen in the IDOC XML.
I am converting this IDOC XML into single string flat file (currently taking the default encoding UTF-8) and sending it to receiver JMS Queue (MQ Series). Now when this data is picked up from the end recepient from the corresponding queue in MQ Series, they see ? wherever there is a Greek/latin characters (may be because that should be having a different encoding like ISO-8859_7). This is causing issues at their end.
My Understanding
SAP system should trigger the IDOC with the right code page i.e if the IDOC is sent with Greek/Latin code page should be ISO-8859_7, if this same IDOC is sent with Chinese characters the corresponding code page else UTF-8 or default code page.
Once this is sent correctly from SAP, Java Mapping should have to use the correct code page when righting the bytes to outputstream and then we would also need to set the right code page as JMS Header before putting the message in the JMS queue so that receiver can interpret it.
Queries:
1. Is my approach for the scenario correct, if not please guide me to the right approach.
2. Does SAP support different code page being picked for the same IDOC based on different data set. If so how is it achieved.
3. What is the JMS Header property to set the right code page. I think there should be some JMS Header defined by MQ Series for Character Encoding which I should be setting correctly) I find that there is a property to set the CCSID in JMS Receiver Adapter but that only refers to Non-ASCII names and doesn't refer to the payload content.
I would appreciate if anybody can give me pointers on how to resolve this issue.
Thanks,
Pratik

Hi Pratik,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
This link might help.
regards
Anupam

Error in SXMB_MONI for Idoc to File Scenario (missing of field plant

Hi SapAll.
here i have got a tricky situation where in a Idoc(Matmas.Matmas05) to file Interface thorugh XI there is an error message raising in sxmb_moni.
to get the conclusion for this error i just copied the message from Sxmb_moni and tried with Message mapping in Design by just pasting there,after all this process iam getting the error message as below
Cannot produce target element /MT_FCI_MATERIAL/fcidataimport/objects/object/extensions/collection[3]/row/fields/PLANTEXT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
When i go the mapping program it is defined as
if Matmas.matmas05WERKS(sender) exists then map werks to plant tex(reciver MType)t else map constant with(null value) to reciever(MType).
and the important thing is the here the occurance of field plant text is 1.1.
so iam not sure on why the error was raised in message mapping as every thing is fine.
can any body help in slolving this.
regards.
Varma

if Matmas.matmas05WERKS(sender) exists then map werks to plant tex(reciver MType)t else map constant with(null value) to reciever(MType).
When WERKS's is absent the IF doesn't have a value and hence the whole context gets suppressed which returns the error. What you have configured would work fine if WERKS is there but with no value. Here the case is a bit different. WERKS itself is not coming. Your logic doesn't handle that. Hope you got what I intend to convey.
Correct me if I am wrong but the logic is you need to pass WERKS value to PLANTTEXT if value comes else map a blank constant...right??
If so, why not just use mapWithDefault
WERKS -> mapWithDefault(blank contant) -> PLANTTEXT
This way if WERKS comes teh value would be passed, if comes with blank value blank value would eb passed if doesn't come atall, even then a blank value would be passed.
Regards
Soumen...

Defining a port /RFC Destination on XI for IDOC to File scenario

When defining a port on XI, what is the client number I am supposed to use to receive the IDOC from R3 to XI. I am assuming that I am supposed to use R3 client number to define the port in XI. Is this correct ?
Please explain this !!!
Also I am assuming the same procedure to define a RFC destination in XI. I am using the IP address of R3 client to define the RFC destination in XI to point to R3. Is this correct ?

hi satya
u may refer to the doc attached for more insight on the ports
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660</a>

Turn of acknowledgment for IDoc - XI - BAPI Scenario

Similar Messages

Maybe you are looking for