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

Similar Messages

Pls send material for idocs in ECC 6.0

Pls send material for idocs in ECC6.0

Hi sitaram s ,
IDoc
- IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful

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

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

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.

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

Send Changes for IDOC ORDRSP

Hi Gurus
Can anyone help me in sending the changes for the IDOC for transactional data.
For Sales Order IDOC -- ORDRSP.
When newly sales order is created, all the sales order information should be sent. --This is not a problem.
When changes are done on the sales order -- Only the changes should be sent in the IDOC. I have activated the change pointers in BD50, BD51 for ORDRSP and in BD52 created the entries for ORDRSP.
but when i trigger the IDOC using the output type, i get to see all the data instead of only the changes.
Is there anything that i am missing???
Any help is really appreciated.
Thanks
Saritha

Hi Linda,
I have documentataion on ALE/IDOCs which may not be helpful to you. If u need that i can send u .
Instead i can help u out if u r facing any issue.
In our case: wen ever sales order is created /changed an idoc shud be genrated.
This can be done thru Message control.
Which involves customization from functional guys in NACE as well as Technical guy in Partner profile/port..
do let me know where ever u r not clear.
regards,
Naveen

Multiple customers in Sender Party for IDOC type KU

Hi All,
My scenario is IDOC to HTTP with sender IDOC Type KU.
We are using PO 7.4 and IDOC_AAE.
I have done the following settings.
Created a Sender Party and assigned a customer under party identifiers. (Also I can't add multiple values with same Agency and scheme it throws eror in PI)
For a single customer the end to end scenario is working fine.
But if I try to send the IDOC with other customer Number it fails as the entry is not maintained for that customer in Sender Party identifiers.
Also I can't afford to create a different party for each customer as there are hundreds of customers in the ECC Application system.
I also tried with value mapping but it won't worked.
Please suggest on this.
Regards,
Nitin...

Dear Nitin,
did you solve this problem? A am faced to it right now... ...
Regards,
Markus

Monitoring and sending alerts for IDocs

Hi ,
I have Idoc scenarios both outbound and inbound.
My requirement is that whenever an Idoc goes into error state an alert should be sent to a specified person automatically.
Please also let me know ways to reprocess Inbound and outbound Idocs.
Thanks

Hi,
Your question is mainly for ECC, than for PI...
but you can acheive it, for instance, by creating an abap program which checks the IDoc status, and send an email to a list of persons you determined for instance in a Ztable for each idoc (message type + idoc type + idoc extension). You can scheduled this program by creating a SAP job (tcode SM36).
Another way could be to add an abap enhancement in each idoc process (inbound / outbound) to check the status of this idoc and send an email. But...
Personally, I prefer the 1st solution, as the program is scheduled, you can group several idoc errors and send only one email (!). Keep in mind this case: among 1000 inbound idocs, 750 are in error, because of a bad or a missing data in the source system... What 's the result with the 2nd solution?... it's a spam of 750 emails to the emailbox of your employees (!!!. Not sure they will appreciate...
To retreat Idoc, you can use tcode BD87. Do not give this tcode to all employees, but only to some key users, to avoid that an employee retreat several idocs which are not in its scope (because he/she did not a godd selection in the selection screen) and which should be not be retreat now (exm due to a fiscel year).
regards
Mickael

Why we do not need sender agreement for Mail and SOAP adapter

Hi SDN,
I know, we do not need sender agreement for IDOC ,HTTP,XI adapters. As these three adapters will run in Integration engine of the abap stack.
In our scenario if sender is other than IDOC or HTTP or XI .
By Refering Sivamni's blog.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
message will be pickedup by communication channel with the help of sender agreement and prepare XI message header by performing cpa cache lookup. then message will go to module processor etc.
In our scenario if sender is IDOC or HTTP or XI .
As these 3 adapters are run in Integration engine.
Doubt 1:
how the integration engine will create the xi message header like sender interface sender system name etc...
Doubt 2:
I believe SOAP and mail adapter will run in adapter engine.but i came to know that we do not need sender agreement and sender comm channel for these two adapters too...then how the XI message header will create...
Please do correct me if i am wrong
and throw some light on the same..
Appreciate your help....
Regards,
Reehan.

Reehan,
Thanks for pointing me to that link. Guess I was wrong .,But,let me try to put to you why you need a sender agreement for a Sender SOAP Adapter,
1. In the sender SOAP adapter , the Sender Interface and the Interface Namespace as provided in the fields Default Interface Name and InterfaceNamespace. The Name of the Sender Service is provided in the WSDL when you ceate the WSDL in the Integration Directory. So, as all details are available in either the Sender SOAP adapter or in the WSDL url you do not need a Sender Agreement. It is not obligatory but you can always create the Sender Agreement.
2. For the mail adapter , if you select the option XIPAYLOAD, you will have the option to mention the Interface Name and Interface Namespace under XI Parameters and so in this case as once again the details provided in the sender agreement are available in the Sender Adapter itself the sender agreement is not needed for the mail adapter when you have select option XIPAYLOAD.
If you have selected XIALL then you need a sender agreement.
Regards
Bhavesh

Handling acknowledgement for sender idoc from multiple receivers

Hi,
Problem: Sender IDOC mapped to multiple FILE receivers. So sender system is SAP, receivers are BS_SYS1, BS_SYS2 and BS_SYS3. The partner profile for IDOC is set as BS_SYS. Due to this, I can enter BS_SYS in the Adapter-Specific Identifiers of one of the services say BS_SYS1. But all three will send acknowledgements and the ack messages for BS_SYS2 and BS_SYS3 error out in MONI due to
'Unable to convert sender service BS_SYS2 to an ALE logical system' and 'Unable to convert sender service BS_SYS3 to an ALE logical system'. How do I solve this since I am not able to set BS_SYS in all three services/adapter-specific identifiers box at the same time.
Anyone have this issue before? I am guessing one option is to create logical systems BS_SYS2 and BS_SYS3 in SAP and have the aleaud messages routed to these logical systems. But when there are say scores of receivers, it is a clumsy solution.
Thanks
JB

007,
nice to have here
You have alternatives:
1. Just use one business system with different inbound interfaces / receiver agreements / communication channels and conditions at interface determination
2. Create a Business Process which is doing the split. This could lead to some minus performance but you would be able to handle the acknowledgements in a senseful way (you get 3 ackn for one send msg)
Regards,
Udo

IDOC-Acknowledgement for Scenario IDOC_Sender to 3rd Party Filereceiver

Hello,
We have the following async scenario:
SAP-ISU (BS_OU9_300)=> IDOC-SenderAdapter => FileReceiverAdapter (BSV_EDSN).
We would like to receive an Acknowledgment (ALEAUDIT) back from XI to SAP-ISU (BS_OU9_300) when the fileadapter has written the file or if something goes wrong during the pipeline processing.
We went through the following HowToGuide: HowToHandle_Acknowledgements for IDOCs.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Unfortunately our scenario is not described there. Does anybody know, if our scenario is supported by ALEAUDIT?
The situation is as follows:
The ALEAUDIT is send back to SAP-ISU, but the segment fields are not filled correctly.
In E1ADHDR only the fields MESTYP and MESTYP_LEN are partly filled.
In E1STATE the field DOCNUM is not filled.
For my understanding the docnum should contain the idocnumber from the original idoc, for which the aleaudit is the confirmation. The process-code AUD1 (in partner profile for ALEAUD) then updates the status of the original IDOC.
Now my questions: (We are on PI 7.0 SP12)
1.     Is our scenario supported?
2.     If yes, why are the idoc fields are not filled correctly
3.             Is my understanding from the processing of the ALEAUD correct?
Regards Marlies

Yep what you have done makes perfect sense.
Am not sure why the Aleaduit does not contain the Docnum with the Source Idoc Number. I remember using Aleduits and they contained the Idoc Number in the DOcNum field.
Can you check the following,
1. Is there a logical system name associated with the Target Business Service/ System which is used against the file system.
2. If yes, is this what the partneprofile configuration in SAP R3 is done against for AleAduits?
Which SP are you on? If it is the latest patches, maybe a bug?
Regards
Bhavesh

Sending Acknowledgements in File to IDoc scenario

Hi,
I have configured File to IDoc scenario successfully. I would like to send acknowledgements whenever any error occurs. But, unfortunately I could not able to find IDX_NOALE report which is required for acknowledgement configuration. To my knowledge, this report is necessary.
Can anybody suggest workaround for this?
Regards,
Suraj Kumar

Hi Suraj,
Try these threads..
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Hope these help you out!
cheers,
Prashanth

Vendor Acknowledgment for PO using Inbound Idoc.

HI,
I have a scenario, where we send the PO to the supplier through Idoc, which is sucessfully recieved, when the supplier tries to send the acknowledgment for the PO through Idoc the Idoc fails with an error message "Confirmed price cannot be set in document conditions" - A condition type with condition category 'd' is not included among the document conditions. I am using message type as ORDRSP. Can any one please tell me where i would have gone wrong in the settings.
Regards
JJJ

Hi,
As per my assumption If the IDOC is recieved with the Error status.There shouldn't be any problem with settings.Please put the break point in the Inbound function module and test the IDOC in Tcode WE19 and try to find out from where the error is.
Please let me know if you require anything else.
Regards,
Sharath
Edited by: sharath Girmaji on Aug 29, 2008 7:58 PM

Sending Acknowledgements for IDOCs

Similar Messages

Maybe you are looking for