A2A - IDoc - IDoc scenario Use of XI

In an A2A - IDoc -IDoc scenario, is the use of XI justified?
-Naveen.

Hi,
SAP is recommending to use XI to avoid point-to-point connection between two SAP systems like R/3 and SRM etc..
Also if you are planning to incorporate a 3 layer architecture (Presentation-- Integration and Database), then you can go for XI.
Refer thisSAP to SAP integration need XI?
Regards
Suraj

Similar Messages

IDoc acknowledgement scenario using ALEAUD01 IDoc type

Hi All,
I have a query, regarding IDoc acknowledgement scenario using ALEAUD01 IDoc type as mentioned below.
In a scenario where we configure and send ALEAUD01 to sender as acknowledgement of the IDoc’s received, is there any way how do we make sure that IDoc’s received by target SAP system has sent the acknowledgement successfully. Would there be any key information in the ALEAUD01 IDoc, which refers to the IDoc/data sent?
Thanks
Rajendra

I needed 24 seconds to know the answer
I took the word ALEAUD01 into Google and added site:help.sap.com in the search field
Among the first 10 results was one with the subject
Acknowledgment Messages
one click to open and skimming through the text ....
And opening one of the other hits in Google told me even which field is having this info

File -- IDOC scenario using XI 3.0

Hi
I tried out a simple flat file to IDOC scenario using XI as the middleware and tried to post documents of type CREMAS03 on the backend R/3 system.
Now, I see that there is an IDOC number generated in the XI layer by the IDOC adapter. This IDOC number is seen under <SAP:DOCNUM>XXXXXXXXXX</SAP:DOCNUM>in the
Response-->IDOCOUTBOUND section of the pipeline in SXMB_MONI
According to SAP documentation :
To enable you to select IDocs in the target system later on, the system transfers the message GUID and the IDoc number in the ARCKEY field of the IDoc control record.
Now, I do find the XI msgid given as arckey in the control record of the Inbound in the target R/3 backend system. But I cannot find the XI IDOC number being cross referenced in the control record of the IDOC in the R/3 backend.
1.Is there a way to cross reference the IDOC number in XI with the IDOC number in the R/3 backend ( we have two different IDOC numbers, right ) i.e a IDOC number to IDOC number cross referencing in this File-->IDOC inbound into the R/3 system scenario involving XI
2. In the XI box, do we get as a part of async.reponse from the R3 system, the IDOC number that is created within the R3 system ? This would serve directly as a cross reference. Or do we have to indirectly query EDIDC table in the R/3 backend with the arckey value = msgid in XI - to retrieve the IDOC number created in the R3 backend ?
Thank you in advance for your time.

Hi,
Pls look into following link about Acknowledgement.
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
Pls note that , you can't get/receive the Acknowledgement for Sender File Adapter. Because File System acts as an Async system. But you can get the Idoc response and you can write it into another file. For this you need to use BPM.
Hope this helps..
Regards,
Moorthy

File to IDOC Scenario using BPM

Hi Experts,
    I am working on file-Bapi-Idoc scenario using BPM.
    I have two conditions
1. If the Sonumber is populated then need trigger an Bapi_change
2.If the Sonumber is not populated from the file then need to trigger a Bapi_Createfromdat to create the sales order and receive the salesorder number as response from Bapi
and the response of these BAPIs should be validated whether the Bapi is successful or not.
If it is successful message then need to trigger IDOC or else should throw an alert message.
let me know the steps involved in this scenario.
can i send alert message to other email IDs or can i send it to only XI admin?
Please let me know u r inputs.
Thanks in advance
Praveen

Hey,
You need to have a BPM for this.
BPM design.
Recieve step(abstract asynchronous) for file structure
Switch Case(condition whether sonumber is populated or not)
if populated
Branch 1(of switch)
    transforamtion step:- mapping between File and Bapi_Change(Request structure)
Send step(abstract syncronous) To send the BAPI_change
Branch 2(of switch)
transformation step:-mapping between file and BApi_Create
Send step(abstract synchronous) To send the BAPI_Create
Block step(which will include the Switch step)
    trigger an Execption in case of an error(in any of the two branches) through the block
    The Exception will trigger an alert.
Now after the Block step there will be a transformation step(which will have the mapping between RFC response and Idoc)
Next is the send step(abstract asynchronous) for the idoc
In case if there is no exception the Idoc will be triggered or the exception branch will trigger the alert
rewards points if useful
regards,
      Milan

ALE IDOC to XML IDOC scenario using XML port

Hi,
I am working on ALE IDOC to XML IDOC scenario using XML port . The requirement is to place a XML IDOC on the application server using ALE IDOC scenario ( output type is created in NACE which is ALE enabled ).
Can anybody help me on the steps.
Regards
Kumar
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 8, 2011 6:01 PM

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

File to Idoc Scenario using third party systems

hi,
Working with a File to Idoc Scenario. Been able to successfully define everything in IR / ID. However when I go to BD87 (reciever system) and see the status of Idoc processed - getting the error code 51 "Function Module Not Allowed: <Function Name>" . What could be the reason for this???
Have defined partner profiles in WE20 of type LS and also specified an inbound paramter in the post processing tab for partner profile. Are there any other settings I need to take care of to avoid getting that error.

Hi
I am giving u all the steps whioch are required for
File to IDoc Scenario
SM59- Create RFC destination
IDX1- Create a IDXPORT in idx1
IDX2-3. Import metadata of IDocs in idx2
Bus. service adapter specific Identifiers-->Logical sys name
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
SE16-Table name->LFA1 to check vendor has been created
Check have u followed all the steps.
Regards
Arpit Seth

Help on EDI to IDOC scenario using seeburger

Hi,
Anyone plzz explain me edi 850 to idoc orders05 scenario. at the same time how generated idoc will creat salesorder.
Thanks,
Seenu.

Hi,
You can see some basics about this integration in this blog:
/people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
You need to get the 850 xsd and import it in IR. Then map your xsd to order05 idoc. Then to test first seeburger adapters need to be deployed. Now you need to configure your classifier and then the splitter if you have multiple 850s within one transmission. Then finally the BIC module to convert edi to xml. Then once you have your xml you need to do your message mapping with the idoc and send to sap.
Once you install the seeburger adapters in your landscape you will have the documents for each of these ones. Go through them and configure.
Regards,
---Satish

Logical System in IDOC-XI scenario

Hi,
I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No. 2) Logical System.
my questions are
a) Are we use Logical System in B to B scenario ?
b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
Thanks and Regards
Mahesh.

Hay Kumar,
Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
Have a Good One,
Uri Lifshitz.

Issue in IDOC-File Scenario

Hallo Everybody,
In one of the requirements,for the interface design which involves IDOC-FILE scenario we have a req as:-
Multiple IDOCs would be sent from SAP R/3 to SAP XI. Each IDOC can have 0-4 segments and for each segment a file needs to created.
The files needs to be FTPed to a location, only if all the IDOCs have been processed successfully.
Requirement:
1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
2) We need to send a notification from XI, in case any IDOC processing fails.
3) How do we check in XI, if all the IDOCs have been processed successfully.
Please suggest me with some good stategies to resolve this issue.
Appreciations and Rewards in line.
Regards,
Younus

Hi
Are you planning to use BPM as it suits your requirement.
To collect the idocs in small bunches refer
Collecting IDocs without using BPM
1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
BPM will allow you to wait for the time all IDOC are processed
2) We need to send a notification from XI, in case any IDOC processing fails.
BPM exception handling will allow this functionality even to the exact field you want to send notification
3) How do we check in XI, if all the IDOCs have been processed successfully.
Set Acknowledgment for IDOC's
refer
Posting multiple IDocs with Acknowledgement
Thanks
Gaurav

IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Soap -- XI -- IDOC/RFC scenario

Hello,
I have a jsp page that working in tomcat server.
I want to send values from jsp page to xi to r/3. I think it will have
soap-- xi -- IDOC/RFC scenario
Pls send me pdf /doc to implemet it
Regards

Hi,
Please Refer the Following Links
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Regards
Khanna

IDoc Collection Scenario (IDoc to Mail Interface)

Hi,
I am configuring IDoc to Mail Scenario using BPM.
I gone through following link for develop the scenario. I am still unable to complete the scenario.
Collect Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
I have done following steps in my configuration. Please correct my steps if i am wrong.
Source is Outbound Invoice IDoc (SAP System).
Target is Inbound EDI 810 format send as a email(Mail System).
1. Create an Abstract Interface for Invoice IDoc(MI_IDoc_ABS)
2. Create a Message Interface for EDI 810 for Inbound(MI_EDI810_IN)
3. Create an Abstract Interface for EDI 810(MI_EDI810_ABS)
4. Message Mapping between Outbound IDoc and Abstract Invoice IDoc. I did this as per one of the above link. but did not understand the importance of this. On Message tab of Message Mapping, it shows the occurance as 1 for both source and target. I did not see the mention of this mapping in the BPM. Not sure if this was required?(MM_IDoc_ABS)
5. Message mapping between Abstract Invoice IDoc to Abstract EDI 810. On the message tab of message mapping, occurance of Source message is changed to 0-unbounded and occurance of target is kept as 1.(MM_EDI810_ABS)
6. Define Interface Mapping for above mappings
a) IM_IDoc_ABS - Outbound Invoice IDoc + MI_IDoc_ABS
MM_IDoc_ABS
b) IM_EDI810_ABS - MI_IDoc_ABS + MI_EDI810_ABS
MM_EDI810_ABS
7. Create a BPM in Integration process. Define 3 Containers namely
a) collectIDoc - Abstract Interface - MI_IDoc_ABS
b) collectIDocList - Abstract Interface - MI_IDoc_ABS(Multiline)
c) targetFile - Abstract Interface - MI_EDI810_ABS
8. Create a Block and define a infinite while loop with Block. Condition to be defined as (1=1)
9. Define a deadline block withing Block with duration = 5minutes
10. Define a Correlation in Correlation editor as SNDPOR as a ID.
11. Define a recieve step inside infinite while loop with following properties
Message = collectIDoc
Start Process = Checked
Use Correlation = Correlation
Activate Correlation = Correlation
Correlation
SNDPOR = collectIDoc./INVOIC02/IDOC/EDI_DC40/SNDPOR
12. Define Container operation next to recieve step. properties are
Target = collectIDocList
Operation = Append
expression = collectIDoc
13. Outside the block, there is Transformation Step with following properties
Interface Mapping = IM_EDI810_ABS
Source message = collectIDocList
Target message = targetFile
Acknowledgement = None
Reciever From = Send Context
Now the next step is to define Communication Channel and Receiver determination, Interface determination in the Integration Directory.
I don't know, how to go further on these steps.
In addition, could you please validate my above steps.
I appreciate your help.
Thanks,
Gowri

Hi Bhavesh,
Thanks for the directions and help. I appreciate your help. I understand the steps but i am unable to implement it.
I have few more questions on above answer.
a) Do i have to create Sender Agreement?
b) Do i have to import bmp process in Integration Process in Integration Directory?
The steps that i carried out in Integration Directory.
1. Create a Scenario EDI810_Scenario
2. Create a party called EDI810_Party and EDI810_Service.
3. In EDI810_Service, Receiver tab has interfaces defined. MI_EDI_IN and MI_IDoc_ABS. In sender tab, it is INVOIC.INVOICE02 (IDoc) and MI_EDI810_ABS.
4. Define a receiver communication channel CC_EDI810_Receiver(RFC).
5. Business System for SAP is defined in Service without Party.
6. Defined Sender communication channel CC_IDoc_Sender(IDoc)
7. Create Interface Determination (First)
Properties are
Sender Service : SAP Business System
Sender Interface : INVOIC.INVOICE02 (IDoc)
Sender Namespace : IDoc namespace
Receiver Party : EDI810_Party
Receiver Service : EDI810_Service
Configured Inbound Interface is
MI_IDoc_ABS and IM_IDoc_ABS
8. Create Interface Determination Determination (Second)
Properties are
Sender Service : BPM_IP (Bpm process is imported in Integratio directory)
Sender Interface : MI_EDI810_ABS
Receiver Party : EDI810_Party
Receiver Service : EDI810_Service
Configured Inbound Interface is
MI_EDI_IN. I do not see IM_EDI_ABS in the list. How do i get that.
What step did i miss?
Thanks,
Gowri

IDoc - File Scenario

Dear SDN,
We have to develop something like this:
An IDoc is generated from an ABAP Business System. Using content based routing conditions the IDoc must be sent to different FTP servers. The problem is that the IDoc must be written in its "native plain" format, not in XML format.
Any ideas?

hi Gustavo,
2 ways
1. https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
2. send the idoc from R3 in native IDOC (file port) and just tranport it via XI
both ways will produce native IDOC:)
for file ports you can check out my book
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

ALE & IDOC Example Scenarios

Hi all,
I'm trying to learn ALE & IDOC. I'm looking for example program for practicing.
I gone through arvind nagpal book and other documentations. I know the theoretical part, but i'm desperately looking for some example programs.
I've searched in google and SDN, but didnt find any example programs.
or else.
Can someone explain me briefly, what is the role of technical consultant in ALE&IDOC scenario?. Whether it may
creating the logical systems.
creating partner profiles
creating RFC destinations
etc etc....
Thanks in advance.
Edited by: Mr A on Feb 2, 2010 9:41 PM

Hi,
Based on the business requirements, you may need to do the following actions:
1) Extending standard Idocs.
2) Complete custom idoc scenario
3) Enhancing standard Idoc population programs using exits.
4) Creating custom segments
5) Creating partner profiles
etc

IDOC to XML using HTTP

Hi Friends,
Is there any possibilities to Convert IDOCs as XML using HTTP Adapter in SAP PI?
Because in my Scenario i need to send Idocs from ECC to Red Prariie using SAP PI.
Also is it there any possibilities using FTPS?
Please help me.
Thanks.

Hi PIstarter,
Sure this is possible. Just treat the IDoc like any other Service Interface that you use in the HTTP Receiver Adapter. You can even use the no-mapping approach if no additional processing is required by PI.
Hope this helps,
Greg

A2A - IDoc - IDoc scenario Use of XI

Similar Messages

Maybe you are looking for