Reg: ALE settings in SAP R3 system

Hai
           I am Kiran. I want to know complete details about ALE settings.
           Can any one send necessary documents regarding these settings.
Thanks
Kiran

Enter tcode WEDI and you will be able to see all the transaction codes that corresponds to ALE/Idocs.
Please follow the links,
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/whitepapers/ale.htm
http://www.sapgenie.com/ale/index.htm
http://www.sappoint.com/abap.html
http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEHR/CABFAALEHR_ALE_QS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/ECPCA/ECPCA_ALE_154.pdf
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
Check this link:
ALE
and this :
http://www.erpgenie.com/sap/ale/whitepaper.htm

Similar Messages

  • Idocs are not prosessing even after ALE settings in SAP XI and ECC

    Hi Experts!,
                     <b>I have a system which has SAP ECC and SAP XI 3.0 installed with 2 instances  on the same operating system. ( In MMC you can see ECC and XI under the same SAP console tree ).
    I have made many times all possible ALE settings between ECC and XI and I was unable to deliver the IDOC [ Idoc scenario- unable to get the IDOC in the receiver side (R3)]
    Could any one please let me know how to solve this issue.
    Useful answers will be rewarded.
    </b>
    Thanks in advance!,
    Sunil

    Hi Martens,
                    I appreciate your kind reply, error : Unable to convert ALE logical system.., this is the error message I am getting, while I do File to IDOC scenario. So what may be the wrong thing in this configuration, Have done ALE settings ( Log sys, assign log sys, partner profile, port and RFC connection from R3 to XI).
    So could you please let me know the solution.
    regards,
    Sunil

  • Setup of ALE Audit in SAP Receiver System

    Hello,
    for a scenario JDBC -> XI -> IDoc,  I have to setup ALE Audit in the receiver SAP sytem.
    I have followed the steps in the How-To-Guide (Handle acknowledgements for IDocs):
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    However I just want to have acknowledgements sent back to SAP XI for a specific type of IDoc (source coming from the database) and not all received IDocs as there are different sender systems sending IDocs (some of them via XI some of them directly).
    Is there a way to configure ALE Audit in a way ALEAUDITs are sent just for specific sender systems / IDoc types. I want to avoid that the SAP XI system receives ALEAUDIT for all inbound IDocs.

    Hey,
    This document describe how the handle audit the the sender and the receiver systems are SAP system, when one of the sides (sender/receiver) is not SAP system,
    than the configuration become much more complex.
    As of XI SP18, there are ways to control ALEAUD,
    for more information, read:
    http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393634373435%7d
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc

  • WE20, WE21 settings after SAP BW system copy

    Hi!
    I copied SAP BW system and have executed the following post installation settings:
    - BDLS (conversion of logical system names)
    - Program RS_BW_POST_MIGRATION
    When I go to tcode RSA1 on my new copied SAP BW system and try to reach source system I get the following error:
    BI unknown in source system
    BI IDoc type ZSBA004 is not the same as source system IDoc type
    The following errors occurred in the source system
    EDI: Partner profile not available
    +Entry in inbound table not found     +
    Entry in outbound table not found
    Question:
    Should I create new entries in tcode WE20, WE21?
    If yes, how (copy of existing one from SAP source BW system)
    Thank you!

    Hi!
    I face currently with the problem on my new SAP BW within RSA1 --> Source system --> Check:
    BI unknown in source system
    BI IDoc type ZSBA004 is not the same as source system IDoc type
    How can I solve this problem?
    The partner definition t-RFC as well are created...
    Thank you!

  • ALE settings in SAP R3

    Hi People
    In IDoc to File Scenario
    I need some info about R3 sys configurations step by step i know what is the procsess
    1st we have to create LS (Tcode : SALE)
    2nd we have to create RFC destination (TC : sm59)
    3rd we have to create PORT (TC : we21)
    4th we have to create PP (TC : we20)
    5th we have to create DISTRIBUTION MODEL (TC : bd64)
    i know this steps But i want step by step in that what we have ti give in LS , RFCDS, PORT, PP, DM 
    and how it process internally, what details we have to give in all configurations in  that above transactions
    regards
    shekar

    Hi,
    Follow below steps to create custom IDOC.
    1.Create segments through transaction WE31.
    2.Create IDoc Type through transaction WE30 by attaching created segments.
    3.Message type through transaction WE81.
    4.Link Idoc and message type in WE82 transaction.
    Check the transaction WEDI for ALE settings
    Check these links for more details on IDoc's:
    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
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
    Thanks
    Swarup

  • How to check the ALE settings in SAP

    Hello everybody,
    I have a question about ALE setups.
    Through ALE,a lot of data flows from one SAP system to another.Hence all these various SAP systems are maintained as logical systems and the appropriate RFC destinations are in place.
    1.Now,if I wish to disable some of these recipient SAP systems ,how to go about it?
    2.More importantly, I have a list SAP boxes(you can say,recipient logical systems),for which I need to check if they are still active or if they have already been disabled.
    Basically,my problem is that I have a number of SAP programs which have got variants maintained ,containing these SAP boxes as partner recipient numbers as part of their variant data.Now,these variants are used to run a lot of batch jobs and I need to verify whether these mentioned partner recipient numbers are still up and active or they have been disabled while the variants never got rectified.
    Please let me know as how this complete check can be made.
    If any clarification regarding the problem is required,please do not hesitate to ask.
    Regards
    Papri

    Hello Papri,
    See below a fast overview for Application Link Enabling settings to check:
    1- Are logical systems with which you want to exchange data defined ?
    If not, you cannot have a RFC connection to those systems.
    2- Do you have RFC R/3 connections for your logical systems  (SM59) ?
    If not, no transactional RFC port can be created for those RFC connections.
    3- Do you have a transactional RFC port for your RFC connections (WE21) ?
    If not, no parner profile can be generated for your parner type (Logical System).
    4- Do you have a distribution model between systems (BD64) ?
    If not, no data exchange via IDoc is possible as no partner profiles LS (WE20) are generated and no model view is distributed.
    So, according to your point:
    1- only one logical system can be reached by RFC connection. It is not possible for others,
    2- that's why you have partner profile not being active,
    3- so, RFC connection is no longer active for logical system is this situation.
    Just one thing regarding those sentences from your first post:
    >(...)
    > Basically,my problem is that I have a number of SAP programs which have got variants maintained ,containing these SAP boxes as partner recipient numbers as part of their variant data.
    >Now,these variants are used to run a lot of batch jobs and I need to verify whether these mentioned partner recipient numbers are still up and active or they have been disabled while the variants never got rectified.
    > (...)
    As those partners (logical systems) are not defined, you should have a DUMP for those jobs.
    It is not the case ?
    Regards.
    Laurent.

  • ALE settings in sapR3 system logical system

    Hi People
    IN IDoc to File scenario
    How to create Logical system(ALE settings) in SAP R3 system, i know little bit idea about that,  we have to 1st create LS name (for R3 sys & PI sys),   after that we have to assign that name's how to assign that,    PLS can u provide me to with screen shots (if possible) r any links 
    Regards
    shekar

    Hi,
    IDOC
    http://msdn2.microsoft.com/en-us/library/ms942196.aspx
    Idoc configuration Required~
    in R/3
    1) RFC destination pointing to XI
    2) WE20 Partner Profile entries
    in XI
    1) RFC destination pointing to R/3
    Go thru this -
    configuration steps for receiving idoc in xi from r/3
    Go thru these for Idoc to XI scenarios-
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    These will be the Configurations needed in your R3,
    1. SM 59 - Create an RFC destination for your XI .
    2. We21 -- Create a port for XI
    3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
    Configuration on XI
    1. IDX2 - Import IDOC metadata.
    For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
    In XI :
    Step 1 : In SALE Tcode :
    a)Create Logical systems for R/3 and XI.
    EG : (QZACLNT100) and (X7ACLNT100).
    b) Assign the logical system of XI to Client.(X7ACLNT100)
    Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
    Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
    Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
    In R/3 :
    Step 1:
    In SALE Tcode :
    a) Create Logical systems for R/3 and XI for
    b) Assign the logical system of R/3 to Client.(QZACLNT100)
    Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
    Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
    a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
    b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
    c)In Menu Bar EDIT->Generate Partner Profile.
    Click on that and press Execute .
    This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
    d) Click EDIT->MODEL VIEW->Distribute.
    This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
    This configuration shall surely help u out as it worked out for me.
    Configurations required for IDocs in R/3
    In your XI system, you need to do the following.
    1. Create a RFC destination to your R/3 system
    2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
    3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
    4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
    5. Import the business system and you can use it in your configuration scenario.
    Please also refer below links for details.
    Go thru this-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    SAP R3 ->Legacy system including master data using XI
    Regards,
    Phani

  • Initial Settings in SAP PI 7.3 after System Installation

    Hi,
    We are installing SAP PI 7.3 here. After media installation by BASIS team, what all other things an SAP PI consultant should maintain/configure(initially before start working on scenarios) ?
    Since I have worked on SAP PI scenarios where the SAP PI server was completely ready(set up). This is the 1st time I'm working on completely new SAP PI system.
    So please guide me at the earliest.
    Thanks,
    Amit Patil

    Hi All,
    This document explains more of "How to set up demo examples?"
    But I want to do initial settings in fresh SAP PI 7.31 system post-installation. Since I have not done this before at all, I need the help step by step.
    I am aware of what all things to be done in fresh SAP PI system like
    RFC connections between ECC-PI and CRM-PI,
    SLD connections between ECC-PI and CRM-PI,
    Maintain Integration and Application Systems in SLD,
    Checking Adapter & Integration Engine Status in PI,
    Etc.
    Please I need help desperately. -
    Thanks,
    Amit Patil
    Message was edited by: Moderator

  • Integrate the Org structure and employees SAP HR system to CRM via ALE

    Hi All,
    We want to integrate the organization structure and employees from mySAP HR system to mySAP CRM system. We are also aware that the same can be achieved through ALE Interface between both these systems.
    In addition to the HR Organization Structure from HR system, can we also bring over the Sales Organization Structure from R/3 using transaction CRMC_R3_ORG_GENERATE?
    1) Can someone , please let us the possible challenges which might occur when we download HR Org structure from SAP HR to SAP CRM.?
    2) What is the implication of maintaining an HR org structure and CRM Sales Org structure within the SAP CRM 52 system?
    3) Any _precautions) should we take before doing the download via ALE??
    Please get back, suitable points will be awarded.
    Regards
    Ritvij

    Hi Ritvij,
    Couple of things that spring to mind are:
    1) When you do the initial data load (PFAL) try to ensure that no one is amending the Org structure as Objects can be locked and therefore not transferred. (on one of our test loads the top level was locked and therfore all subsequent levels were just transfered and we didn't have a top level)
    2) Keep the 'forms of address' in CRM the same as the R/3 ones
    3) Keep the same Employee and Org Unit IDs but prefix with (for exmaple) EM and OU in CRM. (Through the HR integration config in CRM). This may also (apparantley) aid you if set up something like an Employee interaction centre in the future.
    I will update when other stuff springs to mind.
    Cheers
    Gaz

  • How to use ale/idocs in sap crm to transfer master and transactional data

    hi all,
    I am working on sap crm7.0 ehp1. I want to transfer my master and transactional data from crm development system to crm quality system here through idocs. I am aware of basic ale settings and successfully transfe the ztable data through idocs. But i am not able to find any proper step by step procedure for maste and transactional data in sap crm. Also sap ecc tcode NACE is not available here.
    pls help..
    regards,
    kavita chaudhary

    Kavita,
    In CRM, Exchange Interface (XIF) ALE/IDOC is available to transfer master and transaction data. You can go through the following link for set up.
    Basic Data exchange set up for ALE IDocs - Wiki - SCN Wiki
    You can extend the standard XIF IDOCs using Transaction BDFg as well.
    Thanks,
    Ravi

  • Set up for Extraction the data from SAP ECC system

    Hi!
    I would like to analyze the transaction and master data from SAP ECC system into SAP BI system.
    I have created the connection (entry for SAP ECC system) within SAP NetWeaver System.
    Unfortunately when I try to load the transaction data for Info source the process does not end successfully.
    There are no information within SM58 on source system.
    The ST22 does not contain some suitable information.
    Question:
    Which settings do I miss and how can solve my problem?
    (user authorization, etc.)
    Thank you very much!
    regards
    Holger

    Hi!
    many thanks for your reply.
    The error I get:
    Errors while sending packages from OLTP to BI
    Diagnosis
    No IDocs could be sent to BI using RFC.
    System Response
    There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
    Further analysis:
    Check the TRFC log.
    You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
    Error handling:
    If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source
    Can you please help me to identify the error?
    Thank you!

  • Doubt regarding  ALE SETTINGS in IDOC scenario.

    Hi Friends,
            I have some doubts regarding ALE settings for IDOC scenarios,  can anyone  please clarify my doubts.
    For exmaple take IDOC to FILE scenario
    The knowledge i got from SDN is --
    One need to do at the  R3 side is  --- RFC DESTINATION (SM59)  for the XI system.
                                                       --- TRFC PORT  for sending IDOC  to the  XI system
                                                       --- CREATING LOGICAL SYSTEM
                                                       --- CREATING PARTNER PROFILE 
                   at the XI side is  --- RFC  Destination ( For SAP sender system)
                                           --- CREATING  PORT  for receiving IDOC from the SAP sending system(IDX1).
    1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
    In IDOC to IDOC scenario-------
      2.  Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
      3.  If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
    y we r creating receiver communication channel in the case of FILE to IDOC scenario?
      4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                    FILE to IDOC scenario,                                                                               
    IDOC to IDOC scenario individually.
    Thanks in advance.
    Regards,
    Ramana.

    hi,
    1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
    it is a mandatory step in doing ALE configurations
    2. We create 1 RFC destination each in R3 and XI.
        R3 RFC destination points to Xi and
        XI RFC destination  points to R3
    3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
    4. ALE settings for all IDOC scenarios are same  as follows....
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 6)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    Xi
    IDx5(Idoc check)
    SU53(authorization check)
    Reward points if helpful
    Prashant

  • ALE settings in xi

    1) what are the ALE settings i have to maintain in R/3 system and XI in  Idoc 2 file scenario?(I know little bit RFC Destination, Port, Partner profile in R/3 system. is it required to maintain the port in XI also? )
    2) what is use of  Meta data ( IDX2 )? can we import it every time explicitly ?
    3) what are the ALE settings i have to maintain in R/3 system and XI in  File 2 Idoc scenario?
    4) should i create ports in both R/3 and XI systems?( idoc 2 file / file 2 idoc)

    Hey,
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 6)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    WE42 process code
    WE47 status info.
    reward points if useful.
    regards,
           Milan

  • SAP Source system creation in BI

    Hi Gurus,
    I am trying to create SAP source system in BI,  The trying to create ALE REMOTE user in both systems.
    What roles and profiles i need to assign to this user id. After creating user ids what steps i need to follow. Thanks.
    Best Regards,
    Suresh.

    Hi,
    To Create SAP Source System In BI:
    -Click on Source System tab in RSA1.
    -Then right click on the heading Source system and select Create.
    -Select the first option Automatic. Create SAP System and continue filling the other details.
    -This will create Source system automatically.
    When you enter background user's password, sap system user name is modifiable, but the the BI user.
    The background user of BI system, is defined in
    RSA1 => Settings => Global Settings
    <b>BW User ALE</b> field will have the name of the background user in BI.
    If you are using ALEREMOTE as background user, make sure the same is maintained as BW User ALE.
    regards,
    Pruthvi R
    Message was edited by:
            Pruthvi R

  • SAP File System Access - SLD Naming Convention/Suggestions

    I would like to access our ECC file system to pick up files we will use to create Idocs.   
    I'm wondering the best way to describe the file system access in the SLD.   
    I have a business system for the main client on the ECC  system (BS_ED1CLNT010) for example but the OS isn't client specific.    I could use this as the Business System in the scenario and define a file adapter that connects to the unix server.
    Any thoughts?

    Maybe I didn't frame my question properly.  
    In the ECC system we have multiple clients (20,30,40, etc).  If I am going to post an Idoc to a client in this system I need to define each as a business system in the SLD and import this to the Integration Directory.    So I would have BS_XXXCLNT010, BS_XXXCLNT020, etc, one for each client.   These all share the same Technical System.    If I want to post an Idoc to a client on the ECC system I have to define a Business System and interface to that and every client that will receive an Idoc. (as well as the ALE settings on the ECC)
    Each of these reside on the same SAP server (sap00001 for example) and there is a directory (/public for example)  on this server.     This isn't client specific.  
    I wish to pick up a file from the ECC file system and post a client on the ECC system (maybe different ones based on the data in the file).   
    I don't want to define the file adapter under BS_XXXCLNT020 since it isn't specifc to client 020 although that would work.  
    Do I create a new TS in the SLD as third party, stand alone java, and a BS for that?    TS_XXX_FILESYSTE (3rd party).  BS_XXX_FILESYSTEM for the TS?
    I'm really looking for clarity in the definition of the SLD.

Maybe you are looking for