topic Re: ale configuration in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778229#M909115 <HTML><HEAD></HEAD><BODY><P>hi</P><P>good</P><P></P><P>check the below link, hope this will give you the complete idea about the ALE configuration.</P><P></P><P><A href="http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp" target="test_blank">http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp</A></P><P></P><P>thanks</P><P>mrutyun^</P></BODY></HTML> Wed, 07 May 2008 04:34:42 GMT Former Member 2008-05-07T04:34:42Z ale configuration https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778228#M909114 <HTML><HEAD></HEAD><BODY><P>I created ale configurations </P><P>successfully.<STRONG>But i do not know what</STRONG></P><P><STRONG>is the purpose of below steps.</STRONG></P><P></P><P>a) what is mean by RFC destination(sm59)?.</P><P></P><P>b) what is the purpose of RFC destination?</P><P></P><P>c)what is mean by port(we21)?</P><P></P><P>d) what is the purpose of port?</P><P></P><P>e) what is mean by partner </P><P>profile(we20)?</P><P></P><P>f)what is th purpose of partner profile?</P><P></P><P>kindly help me.</P></BODY></HTML> Wed, 07 May 2008 03:28:19 GMT https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778228#M909114 Former Member 2008-05-07T03:28:19Z Re: ale configuration https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778229#M909115 <HTML><HEAD></HEAD><BODY><P>hi</P><P>good</P><P></P><P>check the below link, hope this will give you the complete idea about the ALE configuration.</P><P></P><P><A href="http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp" target="test_blank">http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp</A></P><P></P><P>thanks</P><P>mrutyun^</P></BODY></HTML> Wed, 07 May 2008 04:34:42 GMT https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778229#M909115 Former Member 2008-05-07T04:34:42Z Re: ale configuration https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778230#M909116 <HTML><HEAD></HEAD><BODY><P>Hi Saritha Pyla,</P><P></P><P>Please check these links</P><P></P><P><STRONG>RFC Destinalion</STRONG></P><P><A href="http://help.sap.com/saphelp_nw04/helpdata/en/80/09680289c751429ab3b07ad2a61c10/content.htm" target="test_blank">http://help.sap.com/saphelp_nw04/helpdata/en/80/09680289c751429ab3b07ad2a61c10/content.htm</A></P><P><A href="http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm" target="test_blank">http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm</A></P><P></P><P></P><P><STRONG>PORTS</STRONG></P><P>IDoc data can be sent and received through a multitude of different media. In order to decouple the definition of the media characteristics from the application using it, the media is accessed via ports.</P><P></P><P>A port is a logical name for an input/output device. A program talks to a port which</P><P>is presented to it with a common standard interface. The port takes care of the</P><P>translation between the standard interface format and the device dependent format.</P><P></P><P>Communication media is defined via a port definition.</P><P></P><P>Instead of defining the communication path directly in the partner profile, a port</P><P>number is assigned. The port number then designates the actual medium. This</P><P>allows you to define the characteristics of a port individually and use that port in</P><P>multiple profiles. Changes in the port will then reflect automatically to all profiles without touching them.</P><P></P><P>Please check this link</P><P><A href="http://abapprogramming.blogspot.com/2008/01/data-ports-we21-in-idoc.html" target="test_blank">http://abapprogramming.blogspot.com/2008/01/data-ports-we21-in-idoc.html</A></P><P></P><P><STRONG>PARTNER PROFILE</STRONG></P><P></P><P>We must maintain the business partners with whom we communicate via IDocs, in Partner Profiles.</P><P>The Distribution Model is only applicable to ALE interfaces. When using the Distribution Model, the BD82 transaction will automatically update/create partner profile definitions and create RFC port definitions as needed. However, these definitions must be created or modified manually in situations such as:</P><P></P><P>---&gt; When you are not able to use the Distribution Model, you must manually create your partner profile definitions (WE20) and port definitions (WE21). Reference the SAP Online Library for additional information. </P><P>---&gt; When using the EDI file-based method of IDoc creation, you will need to manually create partner profiles. </P><P>---&gt; When modifying the Partner Profile parameters prior to production or to create partner profiles manually. </P><P></P><P>Please check this link</P><P>[Partner Profile|http://publib.boulder.ibm.com/infocenter/wtxdoc/v8r2m0/index.jsp?topic=/com.ibm.websphere.dtx.packsapr3.doc/tasks/t_pack_sapr3_5_Manually_Creating_Partner_Profiles_WE20.htm]</P><P></P><P>Hope this helps...</P><P></P><P>Best regards,</P><P>raam</P></BODY></HTML> Wed, 07 May 2008 04:36:32 GMT https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778230#M909116 Former Member 2008-05-07T04:36:32Z Re: ale configuration https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778231#M909117 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P>Read all these Steps:</P><P>Data Creation in Idoc</P><P></P><P>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 </P><P>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. </P><P></P><P>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. </P><P></P><P>IDoc is a intermediate document to exchange data between two SAP Systems.</P><P></P><P>*IDocs are structured ASCII files (or a virtual equivalent). </P><P>*Electronic Interchange Document</P><P>*They are the file format used by SAP R/3 to exchange data with foreign systems.</P><P>*Data Is transmitted in ASCII format, i.e. human readable form</P><P>*IDocs exchange messages</P><P>*IDocs are used like classical interface files</P><P></P><P>IDOC types are templates for specific message types depending on what is the business document, you want to exchange.</P><P></P><P>WE30 - you can create a IDOC type.</P><P>An IDOC with data, will have to be triggered by the application that is trying to send out the data.</P><P></P><P>FOr testing you can use WE19.</P><P></P><P>How to create idoc?</P><P>*WE30 - you can create a IDOC type</P><P></P><P>For more information in details on the same along with the examples can be viewed on:</P><P></P><P><A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404" target="test_blank">http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404</A></P><P></P><P><A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm" target="test_blank">http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm</A></P><P><A href="http://www.sappoint.com/presentation.html" target="test_blank">http://www.sappoint.com/presentation.html</A></P><P><A href="http://www.allsaplinks.com/idoc_search.html" target="test_blank">http://www.allsaplinks.com/idoc_search.html</A></P><P><A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank">http://www.sapgenie.com/sapedi/idoc_abap.htm</A></P><P><A href="http://www.erpgenie.com/sapedi/idoc_abap.htm" target="test_blank">http://www.erpgenie.com/sapedi/idoc_abap.htm</A></P><P></P><P></P><P>To Create Idoc we need to follow these steps:</P><P></P><P>Create Segment ( WE31)</P><P>Create Idoc Type ( WE30 )</P><P>Create Message Type ( WE81 )</P><P>Assign Idoc Type to Message Type ( WE82 )</P><P></P><P>Creating a Segment</P><P>Go to transaction code WE31</P><P>Enter the name for your segment type and click on the Create icon</P><P>Type the short text</P><P>Enter the variable names and data elements</P><P>Save it and go back</P><P>Go to Edit -&gt; Set Release</P><P>Follow steps to create more number of segments</P><P></P><P>Create IDOC Type</P><P>Go to transaction code WE30</P><P>Enter the Object Name, select Basic type and click Create icon</P><P>Select the create new option and enter a description for your basic IDOC type and press enter</P><P>Select the IDOC Name and click Create icon</P><P>The system prompts us to enter a segment type and its attributes</P><P>Choose the appropriate values and press Enter</P><P>The system transfers the name of the segment type to the IDOC editor.</P><P>Follow these steps to add more number of segments to Parent or as Parent-child relation</P><P>Save it and go back</P><P>Go to Edit -&gt; Set release</P><P></P><P>Create Message Type</P><P>Go to transaction code WE81</P><P>Change the details from Display mode to Change mode</P><P>After selection, the system will give this message &#147;The table is cross-client (see Help for further info)&#148;. Press Enter</P><P>Click New Entries to create new Message Type</P><P>Fill details</P><P>Save it and go back</P><P></P><P>Assign Message Type to IDoc Type</P><P>Go to transaction code WE82</P><P>Change the details from Display mode to Change mode</P><P>After selection, the system will give this message &#147;The table is cross-client (see Help for further info)&#148;. Press Enter.</P><P>Click New Entries to create new Message Type.</P><P>Fill details</P><P>Save it and go back</P><P></P><P>Check these out..</P><P><A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2402859"></A></P><P></P><P>Check below link. It will give the step by step procedure for IDOC creation.</P><P></P><P><A href="http://www.supinfo-projects.com/cn/2005/idocs_en/2/" target="test_blank">http://www.supinfo-projects.com/cn/2005/idocs_en/2/</A></P><P></P><P>ALE/ IDOC</P><P><A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank">http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm</A></P><P><A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank">http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc</A></P><P><A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank">http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419</A></P><P><A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank">http://www.netweaverguru.com/EDI/HTML/IDocBook.htm</A></P><P><A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank">http://www.sapgenie.com/sapedi/index.htm</A></P><P><A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank">http://www.sappoint.com/abap/ale.pdf</A></P><P><A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank">http://www.sappoint.com/abap/ale2.pdf</A></P><P><A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank">http://www.sapgenie.com/sapedi/idoc_abap.htm</A></P><P><A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank">http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm</A></P><P><A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank">http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm</A></P><P><A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank">http://www.allsaplinks.com/idoc_sample.html</A></P><P><A href="http://www.sappoint.com/abap.html" target="test_blank">http://www.sappoint.com/abap.html</A></P><P><A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank">http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm</A></P><P><A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank">http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc</A></P><P><A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank">http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419</A></P><P><A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank">http://www.netweaverguru.com/EDI/HTML/IDocBook.htm</A></P><P><A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank">http://www.sapgenie.com/sapedi/index.htm</A></P><P><A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank">http://www.allsaplinks.com/idoc_sample.html</A></P><P><A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs" target="test_blank">http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs</A></P><P></P><P>go trough these links.</P><P></P><P><A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank">http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm</A></P><P><A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank">http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc</A></P><P><A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank">http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419</A></P><P><A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank">http://www.netweaverguru.com/EDI/HTML/IDocBook.htm</A></P><P><A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank">http://www.sapgenie.com/sapedi/index.htm</A></P><P><A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank">http://www.sappoint.com/abap/ale.pdf</A></P><P><A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank">http://www.sappoint.com/abap/ale2.pdf</A></P><P><A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank">http://www.sapgenie.com/sapedi/idoc_abap.htm</A></P><P><A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank">http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm</A></P><P><A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank">http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm</A></P><P><A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank">http://www.allsaplinks.com/idoc_sample.html</A></P><P><A href="http://www.sappoint.com/abap.html" target="test_blank">http://www.sappoint.com/abap.html</A></P><P></P><P><A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank">http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm</A></P><P><A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank">http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc</A></P><P><A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank">http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419</A></P><P><A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank">http://www.netweaverguru.com/EDI/HTML/IDocBook.htm</A></P><P><A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank">http://www.sapgenie.com/sapedi/index.htm</A></P><P><A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank">http://www.allsaplinks.com/idoc_sample.html</A></P><P></P><P><A href="http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank">http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm</A></P><P></P><P>An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...</P><P></P><P>1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables. </P><P></P><P>2.IDOCs are independent of the sending and receiving systems.</P><P></P><P>3.IDOCs are independent of the direction of data exchange.</P><P></P><P>The two available process for IDOCs are</P><P></P><P>Outbound Process</P><P>Inbound Process</P><P></P><P>AND There are basically two types of IDOCs.</P><P>Basic IDOCs</P><P>Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.</P><P></P><P>Extended IDOCs</P><P>Extending the functionality by adding more segments to existing Basic IDOCs.</P><P></P><P>To Create Idoc we need to follow these steps:</P><P></P><P>Create Segment ( WE31)</P><P>Create Idoc Type ( WE30)</P><P>Create Message Type ( WE81)</P><P>Assign Idoc Type to Message Type ( WE82)</P><P></P><P>imp links</P><P></P><P><A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank">http://www.allsaplinks.com/idoc_sample.html</A></P><P><A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank">http://www.sapgenie.com/sapedi/idoc_abap.htm</A></P><P><A href="https://community.sap.com/www.sappoint.com" target="test_blank">www.sappoint.com</A></P><P>--here u can find the ppts and basic seetings for ALE</P><P><A href="http://sappoint.com/presentation.html" target="test_blank">http://sappoint.com/presentation.html</A></P><P></P><P><A href="https://community.sap.com/www.sapgenie.com" target="test_blank">www.sapgenie.com</A></P><P><A href="http://www.sapgenie.com/ale/index.htm" target="test_blank">http://www.sapgenie.com/ale/index.htm</A></P><P></P><P>WE30 - you can create a IDOC type.</P><P>An IDOC with data, will have to be triggered by the application that is trying to send out the data.</P><P>Try this..Hope this will help.</P><P></P><P></P><P>SAP ALE &amp; IDOC&lt;&lt;&lt;&lt; </P><P>Steps to configuration(Basis) &gt;&gt; </P><P>1. Create Logical System (LS) for each applicable ALE-enabled client </P><P>2. Link client to Logical System on the respective servers </P><P>3. Create background user, to be used by ALE(with authorizaton for ALE postings) </P><P>4. Create RFC Destinations(SM59) </P><P>5. Ports in Idoc processing(WE21) </P><P>6. Generate partner profiles for sending system </P><P></P><P>The functional configuration(Tcode: SALE) </P><P>&#149; Create a Customer Distribution Model (CDM); </P><P>&#149; Add appropriate message types and filters to the CDM; </P><P>&#149; Generate outbound partner profiles; </P><P>&#149; Distribute the CDM to the receiving systems; and </P><P>&#149; Generate inbound partner profiles on each of the clients. </P><P></P><P>Steps to customize a new IDoc &gt;&gt;&gt; </P><P>1. Define IDoc Segment (WE31) </P><P>2. Convert Segments into an IDoc type (WE30) </P><P>3. Create a Message Type (WE81) </P><P>4. Create valid Combination of Message &amp; IDoc type(WE82) </P><P>5. Define Processing Code(WE41 for OUT / WE42 for IN) </P><P>6. Define Partner Profile(WE20) </P><P></P><P>Important Transaction Codes: </P><P>SALE - IMG ALE Configuration root </P><P>WE20 - Manually maintain partner profiles </P><P>BD64 - Maintain customer distribution model </P><P>BD71 - Distribute customer distribution model </P><P>SM59 - Create RFC Destinations </P><P>BDM5 - Consistency check (Transaction scenarios) </P><P>BD82 - Generate Partner Profiles </P><P>BD61 - Activate Change Pointers - Globally </P><P>BD50 - Activate Change Pointer for Msg Type </P><P>BD52 - Activate change pointer per change.doc object </P><P>BD59 - Allocation object type -&gt; IDOC type </P><P>BD56 - Maintain IDOC Segment Filters </P><P>BD53 - Reduction of Message Types </P><P>BD21 - Select Change Pointer </P><P>BD87 - Status Monitor for ALE Messages </P><P>BDM5 - Consistency check (Transaction scenarios) </P><P>BD62 - Define rules </P><P>BD79 - Maintain rules </P><P>BD55 - Defining settings for IDoc conversion </P><P></P><P>WEDI - ALE IDoc Administration </P><P>WE21 - Ports in Idoc processing </P><P>WE60 - IDoc documentation </P><P>SARA - IDoc archiving (Object type IDOC) </P><P>WE47 - IDoc status maintenance </P><P>WE07 - IDoc statistics </P><P></P><P>BALE - ALE Distribution Administration </P><P>WE05 - IDoc overview </P><P>BD87 - Inbound IDoc reprocessing </P><P>BD88 - Outbound IDoc reprocessing </P><P>BDM2 - IDoc Trace </P><P>BDM7 - IDoc Audit Analysis </P><P>BD21 - Create IDocs from change pointers </P><P>SM58 - Schedule RFC Failures </P><P></P><P>Basic config for Distributed data: </P><P>BD64: Maintain a Distributed Model </P><P>BD82: Generate Partner Profile </P><P>BD64: Distribute the distribution Model </P><P></P><P>Programs </P><P>RBDMIDOC &#150; Creating IDoc Type from Change Pointers </P><P>RSEOUT00 &#150; Process all selected IDocs (EDI) </P><P>RBDAPP01 - Inbound Processing of IDocs Ready for Transfer </P><P>RSARFCEX - Execute Calls Not Yet Executed </P><P>RBDMOIND - Status Conversion with Successful tRFC Execution </P><P>RBDMANIN - Start error handling for non-posted IDocs </P><P>RBDSTATE - Send Audit Confirmations </P><P>FOr testing you can use WE19. </P><P> </P><P></P><P>There are two filtering in IDoc. </P><P></P><P>Segment Filtering:</P><P>Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.</P><P></P><P>Data Filtering:</P><P>Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.</P><P></P><P>Please check this link for more information. </P><P></P><P><A href="http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm" target="test_blank">http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm</A></P><P></P><P></P><P>Regards,</P><P>Shiva.</P></BODY></HTML> Wed, 07 May 2008 04:47:41 GMT https://community.sap.com/t5/application-development-and-automation-discussions/ale-configuration/m-p/3778231#M909117 Former Member 2008-05-07T04:47:41Z