About proxies and IDOC

Hi all,
Can any one explain me or give me a lnk to blog on how do we merge more than two IDOC to one file.
And also blogs,good links about proxies (ABAP).
Cheers,
Karthick

Hi,
check this links
XI: Debug your inbound ABAP Proxy implementation ---Debug your inbound ABAP Proxy implementation
Choose the Right Adapter to integrate with SAP systems
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1387--- [original link is broken] [original link is broken] [original link is broken] Client Proxy
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1457--- [original link is broken] [original link is broken] [original link is broken] Server Proxy
ABAP Proxy Runtime
Programming with Client and Server Proxies
Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure
Various multi-mappings and Optimizing their Implementation in Integration Processes (BPM) in XI.
IDOCs (Multiple Types) Collection in BPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2034Regards [original link is broken] [original link is broken] [original link is broken]
regards
vasu

Similar Messages

About LSMW and Idoc

Hi Guys
I am new to LSMW and IDoc or BAPI method. Can anyone email me some step by step docs. Pls dont send me other methods, I knew it already! Thx in advance!
Kun Bao

LSMW
http://www.sap-img.com/sap-data-migration.htm
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-17643ed1d6d658821_glossary/L#Word-17643ed1d6d658821_glossary
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
BAPI
www.planetsap.com/LIST_ALL_BAPIs.htm
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Regards,
Santosh

Proxies and idocs/configuration

in the configuration of idocs from the sender and proxies we need not do sender communication channel(adapter config ) and sender agreement then wat do we have to mention for the sender service column in receiver agreement and determination ?.do we have to create dummy commu channel for the sender

Hi,
Just thought of giving you these How to links. You might find this useful.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Regards,
P.Venkat

About ale and idocs

hi all
i was asked in an interview when we will go for creation of an idoc.pls provide me some real time situaution when we use these idocs

HI,
IAM GIVING A DOCUMENT WHICH HELPS YOU TO UNDERSTAND THE PROCESS OF IDOCS BEING SENT BETWEEN TWO SYSTEMS AND IT COULD HELP YOU IF U GO FOR INTERVIEWS.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User:      MMUSER200 (This is the logon for dist.)
Client :      200
Password:      MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG100.
Receiver as      LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG200.
Receiver as      LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as      Mechanical Engineering
Material Type as           Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time:   WE07.

Proxies vs IDocs

Hi all,
how to decide between Proxies and IDocs when it comes to data transfer from one system to other?
What are the various factors on which the above decision depends?
Thanks in advance.

Yes but you have to check in the inbound system for IDOC status.
In Proxy you can get it instantly in sending system & then you can have error handling logic or triggering mail to the user.
Data Size & efficiency: I don't find much difference.
Implementing proxy is complex as compared to IDOC.
I had implemented both proxy & IDOC in a single program based on the requirements.
If you could tell me your requirements, I could help you better.
Thanks,
Sharath

I tried downloading Final Cut ProX but my computer said that "this computer cant download Final Cut ProX" and i dont know why?

i tried downloading Final Cut ProX but my computer said that "this computer cant download Final Cut ProX" and i dont know why?

Is your iMac still really on OS X 10.2 Jaguar?
Could you supply more accurate info about your Mac.
What Mac do you have?
To find out info about your system,
Click on the Apple symbol in the upper left of the OS X main menu bar. A drop down menu appears.
Click About this Mac. A smaller popup window appears. This gives you basic info like what version of OS X your iMac is running, the speed of your iMac's CPU and how much RAM is installed.
Click on the button that says More Info.
A larger window appears giving you a complete overview of your iMac's hardware specs.
Highlight all of this info and copy/paste all of this into another reply to this post, editing out your iMac's serial number before actually posting the reply.
This will tell us everything about your iMac so we may begin to help with your iMac issues.
Final Cut Pro X System Requirements.
OS X v10.9.2 or later
4GB of RAM (8GB recommended for 4K)
OpenCL-capable graphics cardor Intel HD Graphics 3000 or later
256MB of VRAM (1GB recommended for 4K)
3.5GB of disk space

Difference between BAPI and IDocs

hello all
what is difference between BAPI and IDocs

Hi,
BAPI
One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
Some of the BAPIs are better documented and easier to use than others. You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
BAPIs probably have better performance since they don't do the screen flow processing.
In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
Regards,
Bhaskar

What is the difference beween idoc package and idoc collection

Hi friends,
    i am unable to understand difference betwen Idoc package and Idoc cillection.
    Please give me clear clarification.
Thanks and regards
Bhanu

Hi Bhanu,
Apart from the replies above, in case you're looking for an answer from ECC perspective, here are some inputs: (ECC is considered as sender here)
1. IDoc Collection:
   This will collect the IDocs and will not immediately send it to the target system after they are created. Program RSEOUT00 can be later scheduled for these collected IDocs to deliver them to the target. You can treat this as a park and process approach which proves useful in several business scenarios.
This standard link gives more insight:
SAP Library - IDoc Interface/ALE
2. IDoc Packaging:
    This defines the number of IDocs to be packed and sent in 1 RFC call (tRFC). If you set is as 20, then 20 IDocs will be sent in 1 tRFC request. This doesn't connote whether the IDocs will be triggered immediately or later, this just talks about the bundling of IDocs per RFC call.
Hope this helps.
Regards,
Abhishek

Proxies and use of proxies in XI

hi all,
Can anybody help me this
what is proxies and how it will be helpfull in XI.
regards
manoj kumar

Hi Manoj,
You can get details about Proxies here..
http://help.sap.com/saphelp_nw04/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/content.htm
Also, the below links are helpful too...
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
Hope this helps..
Please let me know if you need any more details...
Kiran..

About RFC and BAPI

Hello Masters,
What Makes the exact difference between RFC and BAPIs. Both can perfom same thing. BAPI uses the RFCs only. Then how can it justify?
Thank you

RFC:
RFC --- > Function module and general will be used to make call to function
sending the function (XI has RFC adapter)
BAPI:
BAPI ---> Other version of RFC (Objected oriented) mostly we will use for Sync
calls (Mostly in XI using proxies we will call BAPI's)
Refer these links for more details:
http://sapabap.iespana.es/sapabap/sap/faq/ale_idocs_bapi.htm
http://www.sap-img.com/fu033.htm
BAPI Vs IDOC - in detail
http://searchsap.techtarget.com/tip/1,289483,sid21_gci824860,00.html
/thread/127699 [original link is broken]
IDOC,RFC,BAPI
Re: When and Why we use BAPI, RFC and IDOC.. in XI
Diff... between ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify
idoc and bapi
Difference among IDOCS,BAPI,RFC?
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
Differences Between RFC & BAPIS
RFC Vs BAPI
For more details:
refer this thread.
What are idocs, BAPI, RFC?
BAPI is nothing but the Business process programing interface which are standard and stable and these are store in the business object repository.
Standardized programming interface that enables external applications to access business processes and data in an SAP System
RFC is the remote function call which is used to call the function remotely which may be in same system or ather system
its also used communication between SAP systems , between SAP systems ,external systems.
idoc and bapi
Difference among IDOCS,BAPI,RFC?
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
Differences Between RFC & BAPIS
RFC Vs BAPI
http://www.sap-img.com/abap/ale-bapi.htm
RFC means remote function call,
these are the function modules which can help u to access across the sap and from sap to third party front end,
BAPI means Business application programing interface which is the RFC enable function module and uses in OOPS concept.
RFC ,IDoc and BAPI
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
This is a short description of BAPI and RFC
BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.
RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system.

Concept Question about EDI and Error Processing

Hello All,
This is a concept question, I was wondering how others would approach this scenario.
Let's take this scenario. In EDI often the transmission for a purchase order comes in with an invalid material number. Normal error processing is for the EDI team to research the issue (find the correct matnr), edit the idoc and reprocess the Idoc. I would like to move that type of error processing out of the hands of the EDI folks and into the hands of the business users.
How would they correct the material number? It has to be more intuitive than editing an IDoc, it has to be an easy and intuitive user interface. This process has to also work for many types of EDI transmissions both inbound and outbound.
There would be many ways to handle this: create a report with an editable grid that would change the idoc during input and create the order with the corrections, convert the idoc to xml and use simple transformations, use an xsl report...etc. You get the point.
How would you approach this? Before I start the design I want to make sure I've given all the options due consideration...all options, webdynpro, transformations, regex, you name it...all is available, except there is no XI.
Personally I'm leaning towards an editable grid and processing buttons that would post the idoc in background...but I do that type of thing all the time and I may be in a rut and neglecting better design options.
Thanks for your input,
Greg

Paul: So it runs the transaction silently in BDC format, until the error occurs, then opens up in dialogue to allow the user to change the invalid material, and then continue on with processing.
This works when the processing function module uses BDC. But even then I think this is possibly nice from user perspective, but a nightmare from auditing perspective. I.e. correct me if I'm wrong, but I'm pretty sure there's no log indicating that the user changed the material number. Thus for anybody comparing the IDoc contents against the posted document (including change history) there's no trail that shows this change. Of course you can assume that this is what must have happened, but I personally prefer if I can track in the system what happened and have proof for that.
Reddy:
<ol>
<li>it can be run daily basis, which should select all idocs which are in status 51 with message number (..related to wrong material number). report output should inlcude :idoc number-wrong mat no- space for new material to be entered by business against wrong 1. And there should be one button for RUN.</li>
<li>After RUN, the material number should be changed to new 1 in segments and idocs should be reprocessed.</li>
<li>repeat the run until business enter right mat num.</li>
</ol>
Design seems to limited to me (takes care only of one error message). Might work if that's the main pain point and this is the only one the user is dealing with. Otherwise I'd expect pretty soon they start complaining about having to use different tools for the possible errors. I'd keep the report more general, but allow this special form of processing only for a given error message (otherwise it's a normal re-process as triggered for example via BD87).
Also, I assume that when you talk of changing the IDoc you mean that you actually keep an original copy around (like SAP does when you edit an IDoc). Often this is required from an auditing perspective. I'm not sure why you wouldn't want to check the material number before trying to process the IDoc to avoid wasting system resources (but maybe I misunderstood the step).
Anyhow, in theory you could also achieve all of this via workflow. You can add custom columns to the work item overview in the inbox, only issue here is that it doesn't scale well (so issues with larger volumes).

ALE, EDI and IDOCS

Hi
I am learning some stuff on ALE,EDI and IDOCS... are there any good sites which gives clear step by step procedure for the above.
Thanks in Advance.
Sudhi

Hi Sudhi
You can find details on SAP courses from your country's sap.com site. You can find links from http://www.sap.com/contactsap/countries/index.aspx .
Also some Education Partners of SAP give courses. Some info about these will also be there...
Regards...
*--Serdar

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

Regarding rfc and idoc sender

hi
   can any one provide me with some scenarios having
idoc and rfc as senders.

Hi
To Configure the RFC to FILE scenario ,Proceed as Follows
a.       Create an RFC Destination to XI in transaction code (SM59)
b.       Create new destination of type T (TCP/IP)
c.       Make sure you select Registered Server Program option before writing your program ID
d.       Write you program ID (remember it's case-sensitive)
e.       In the gateway host and gateway service write the values of your Application system - business system (not the XI server)
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         The namespace is ur:rfctofile
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System IS :sapfox
4.2)     Client IS :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number: 00
4.5)     User name:developer
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC and RFC node. Click on this node and select the   Idoc or Rfc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the   Rfc and Idoc will be available into XI as Message types. So no need to create any Rfc or Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is. dt_file
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Message type.You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Rfc .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Rfc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
    Since the Sender is 'RFC', Specify the following Parameters
         For the adapter type , use the F4 help and select RFC.
         Specify Sender since the adapter will be sending messages to XI
         Specify the following parameters.
         Transport Protocol: RFC
         Message Protocol:   RFC(RFC XML )
         Adapter Engine: Integration Server
         Adapter status: Active
         RFC Server Parameter:
         Application Server(Gateway):172.25.5.7
         Application Server Service(Gateway Service): sapgw00
         Program Id: Id of Registered server program ( it is case sensititve)
         And the adapter is configured. Save it
          Since the Receiver is File , Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml files produce by XI need to be converted to text files)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:Test
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server:172.25.5.240
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select create new button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in SAP R/3 towards other system
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> Distribute to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         Your NameSpace is urn:idoctofile
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System :sapfox
4.2)     Client :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number:00
4.5)     User name: developer
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC node. Click on this node and select the   Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is :dt_file
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
     Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
          For the Receiver, Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:Test
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server: 172.25.5.240
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
plz rewards points
vikas

PPT on ALE and IDOC

Hi,
Any body can send me the ppt on ale and idoc .
great thanks in advance .
Regarding
kumar

Hi Anil,
The best way is to read the book ALE,IDOC... by Aravind nagpal,
Just read this you will get a clear idea about these.
The ppts will cover only the basic part,but i find this book as very useful when you do the coding or checking for soem settings.
Regards,
Sasi

About proxies and IDOC

Similar Messages

Maybe you are looking for