ALE configuration in ECC and 4.7

Hello guys
Is there any difference in ALE configuration in ECC and 4.7??

Summarised step follows below...
ALE settings for IDOC
SAP XI
1) RFC Destination (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.
2) Create Port (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 (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Also read this blog <a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a>.
Do a SDN serch and you can get a lot more that this
~SaNv...

Similar Messages

  • ALE configuration Between HR and FI system

    Dear All,
    We have HR system on ECC6 and FI system on 4.x version,
    i have to do ALE configuration between these two systems , please guide me what bapi's , idocs and what background jobs i need to run on FI system or HR system
    please advise at the earliest.
    Regards,
    Najeeb ..

    http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAIS/CABFAIS.pdf

  • Synching configuration between ECC and GTS

    Is there any way we can automatically synch configuration (e.g.countries, regions) from ECC to GTS?
    Thanks in advance.

    Transaction SCU0 lets you compare configuration between systems, based on a number of ways of selecting the items to compare.
    I am not sure if it offers any way to build a transport of the differences, or remotely update the target system.  At least it lets you know what is different.
    Andrew

  • ALE Configuration error

    Hi,
    I did the ALE configuration in sending and recieving system like creating LS,Assigning LS to Client,Model View For Message type,ports and partner profiles.
    When i was trying to distribute the model view it is giving error:
    RFC Destination not configured or partner profiles not generated.
    I can remote logon from sender system to reciever system and vice versa.
    The partner profiles are created for the  LS Sender and reciever.
    So can any one help me on this issue.
    Thank you.

    Hi Mili,
    You do not need to generate partner profile during the ditribution model view process (BD64). You can add manually the partner profile via WE20 for inbound and outbound parameters. As long as distriburon model has been setup and distribute, you can continue the next step for example generating IDoc and so on.
    Sometimes, you may face an issue to generate partner profile from BD64 for some reason. I found by generating manually partner profile always quick, safe and stay away from any trouble shooting for an error.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Configuration related to PO colabration in ECC and SNC

    Hi
    Can anybody throw light configuration related to PO colabration in ECC and SNC.
    Regards
    Raj

    Hi Raj,
    Below link provide you SNC information about Integration ECCPISNC and functionality of SNC
    link http://help.sap.com/saphelp_snc70/helpdata/EN/b4/f20483605b0d4fa856354a986e900d/frameset.htm but if you want configuration document then Click on below link
    http://help.sap.com/bp_bblibrary/500/BBlibrary_start.htm
    A07_BB_ConfigGuide_EN_DE.doc (Kanban processing)
    S32_BB_ConfigGuide_EN_DE.doc (SCM setting)
    S34_BB_ConfigGuide_EN_DE.doc (Supplier)
    S55_BB_ConfigGuide_EN_DE.doc (Contract Manufacturing Procurement)
    hope this documents are useful.
    Thanks,
    Nikhil

  • PI: configuration for PO and Contracts creation on ECC

    Dear Gurues,
    My client is working with classic scenario with plan driven procurement on SRM 7 EHP1 and ECC 6 EHP5.
    From ECC EHP4 or higher landscape, classic PO will be created in the backend, from SRM only via XML. For this, PI system should be configured and SRM system connections and the SRM & ECC business systems have to be mentioned in the PI system.  So the use of PI is mandatory.
    Can you explain me which configuration shoudl I have to perform in SRM-ECC and PI?
    Thanks in advance.
    Martí

    I do not think anything is mandatory regarding the order. You can go ahead with PI 7.1 first and then EHP4 on ECC. But the otherway should also not be a problem.
    VJ

  • IDOC and ALE Configuration with cross application with SD

    Hi Sap Gurus,
    Please send me some document on IDOC and ALE Configuration with cross application with SD.
    Please send me the material on my mail id [email protected]
    Regards
    shekhar

    Dear Shekhar,
    concerning EDI concept in SD: the EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.
    If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every thime send a change to the existiong order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).
    So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOIC.
    That's all concerning the SD-EDI.
    Additional processes in SD, where EDI are used:
    1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS
    2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD
    3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT
    4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.
    It is all processes which are realized in the SD module via EDI.
    I hope this info helps.
    Kind regards,
    Akmal Vakhidov
    Development Support SAP, Walldorf/Germany

  • Configuration of EDI and ALE

    Hi,
    I am new to Idocs i would like to know the cofiguration settings for EDI and ALE from starting.I know abt creating partner profiles and the other stuff. I would like to know in detail. Please let me know.
    Thanks in Advance,
    Srikanth.N

    Hi
    Data Creation in 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.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    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
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    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
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    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...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Check these links.
    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
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    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/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Outbound:
    Step 1.  Application document is created when transaction is saved.
             2.  Message control is invoked.
             3.  Messages are processed by system.
             4.  Messages are Edited (if desired).
             5.  Output (ALE /  EDI) is checked
             6.  Validate against Message control record from Partner Profile
             7.  Application Document is saved.
             8.  Entry NAST table is created for every selected output program
                  along with Medium & Timing.
             9.  Check for Process Immediately .
                     If (yes)
                       Determine Processing Program from TNAPR Table.
                     ELSE
                       Execute RSNASTED Program.
           10.  Read Partner Profile to determine Process Code.
           11.  Process Code points to the Function Module & Invoked.
           12.  IDoc is generated. 
           13.  Check for ALE Request.
                        if (Yes)
                            Perform Filters, Conversions, Version Changes etc.
                        Else.
                            IDoc is stored in DATABASE.
    INBOUND:
    Step 1.  EDI Subsystem creates an IDoc file from EDI Messages
            2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
             3.  Data in Control Record is validate against the Partner                       Profile.
            4. IDoc is generated in Database and syntax check is                      carried out.
            5. IDoc file is deleted once file read.
            6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow. 
                       7.  Check for Process Immediately.
                   If NO
                     Execute RBDAPP01 Program
                   Else
                      Read Process Code from Partner Profile        
                           Process Code Points to  Function Module
                     Application Document Posted.     
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • ALE Configuration for PEXR2002 IDoc  and PAYEXT message type sending to XI

    Hi all,
              I need ALE Configuration for PEXR2002(Basic Type) IDoc , it's message type PAYEXT.
    I don't know ALE Configuration for sending data from SAP IDS to SAP XI.????
    I need ALE Configuration doc/pdf??
    Please give me some guidline for this..
    Regards,
    Umesh

    Umesh,
    I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI. 
    I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
    Any help or direction would be great.
    Thanks,
    Dave

  • Can we go with ALE configuration instead of receiver idoc adapter at target

    Hi Experts,
    Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI  to Target system instead of configuring receiver IDOC adapter at target side.

    Hi Raj
    Point 1:
    When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
    Point 2:
    When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
    i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
    Regards,
    Raj

  • ALE Configuration SO creation

    Dear Experts,
    I have ECC PO and as of now user creates manual sales order in other R/3 4.7 which is time consuming, less accurate and erroneous process. I got to know something on ALE configuration where user creates PO in ECC, automatically SO created in R/3. Basically, i have two separate server ECC and R/3. pl share ALE configuration steps of to create SO in other R/3 system from PO of ECC system. Pl also share any other processes to be followed to achieve automation of SO creation into other SAP system from PO.

    Hi,
    Check the transaction code VOE2 which suits your requirement to create the SO from PO with ALE
    In that transaction code you have to maintain the combination of Customer ,  vendor and sales area details
    After that set up the partner profiles in the transaction code WE20 with the Partner type LS  from ECC to R/3 with relevant message types and IDOC types
    Please let the Developer know these details and he would be able to  create the Partner profile
    revert back if you need further details
    regards,
    santosh

  • ALE configuration automatic SO creation

    ABAP Experts,
    I have ECC PO and as of now user creates manual sales order in other R/3 4.7 which is time consuming, less accurate and erroneous process. I got to know something on ALE configuration where user creates PO in ECC, automatically SO created in R/3. Basically, i have two separate server ECC and R/3. pl share ALE configuration steps of to create SO in other R/3 system from PO of ECC system. Pl also share any other process to be followed to achieve automation of SO creation from PO.
    Thks
    Moderator message: please search for available information/documentation before asking.
    Edited by: Thomas Zloch on Jan 4, 2011 2:35 PM

    Hi,
    Check the transaction code VOE2 which suits your requirement to create the SO from PO with ALE
    In that transaction code you have to maintain the combination of Customer ,  vendor and sales area details
    After that set up the partner profiles in the transaction code WE20 with the Partner type LS  from ECC to R/3 with relevant message types and IDOC types
    Please let the Developer know these details and he would be able to  create the Partner profile
    revert back if you need further details
    regards,
    santosh

  • ALE Configuration Needed

    Hi every one,
    I want steps involved in ale configuration.
    Lets take example two systems are Sysa and sysb
    Thank you

    hi
    CATSDB CUSTOM IDOC TRANSFERMATION BETWEEN 2 DIFFERENT APPLICATION SERVERS
    For this scenario Client 800 of application server SAPADM is the Sender and client 800 of application server SAP-REMOTE is the Receiver
    1. Creating Logical Systems
    o       Login using 800 client
    o       Go to T. Code SALE
    o       Expand Sending and Receiving Systems
    o       Expand Logical Systems
    o       Click on Define Logical System
    o       Click on New Entries
    o       Create CATSSENDER, ECC Logical Systems
    o       Save and come back
    o       Assign the CATSSENDER Logical System to client 800 of Application Server SAPADMAssign the ECC Logical System to client 800 of Application Server SAP-REMOTE
    2. Creating the RFCs
    o       Go to T. Code SM59
    o       Expand R/3 Connections
    o       Enter RFC Name as CATSSENDER
    o       Connection Type as 3
    o       Language as EN
    o       Client as 800
    o       User as SAPUSER
    o       Password as YESV13
    o       Target host as SAPADM
    o       Click on Remote logon button to test the RFC
    o       Enter RFC Name as ECC
    o       Connection Type as 3
    o       Language as EN
    o       Client as 800
    o       User as SAPUSER               
    o       Password as YESV123
    o       Target host as SAPADM                                                                               
    o       Click on Remote logon button to test the RFC
    3. Creating the Message Type
    o       Go to T. Code WE81
    o       Click on change, continue
    o       Click on New Entries button
    o       Give message type as ZCATSTIME and description
    o       Save and back
    4. Creating the Segment
    o       Go to T. Code WE31
    o       Give segment name as ZSEGMENTTIME
    o       Enter Short Text
    o       Enter the Field Name and Data Element in the text boxes
    o       Save, continue,
    o       Click on Edit -> Set Release
    5. Creating the Basic IDOC Object
    o       Go to T. code WE30
    o       Give obj. name as ZTIMEIDOC
    o       Click on create
    o       Select create new radio button, give description and continue
    o       Select the IDOC obj name and click on create button
    o       Enter the segment name which is create earlier
    o       Select the check box if you want to make the segment mandatory
    o       Enter 1 in minimum number 99999 in maximum number, continue
    o       Save and backo       Click on Edit -> Set Release
    6. Creating Customer Distribution Model
    o       Go to T. Code BD64
    o       Click on change and Create model view button
    o       Enter the short text and Technical name as CATSSENDER
    o       Select the model and click on Add Message Type Button
    o       Give the Sender as CATSSENDER,
    o       Receiver as ECC,
    o       Message Type as ZCATSTIME
    o       Select the model view & click on Environment -> Generate Partner Profiles
    o       Select Transfer IDOC Immediately and Trigger Immediately radio buttons
    o       Click on Execute
    o       You should get a list in green color which means it executed successfully.
    o       Back to main screen, select the model view
    o       Click Edit->Model view->Distribute
    o       Click on continueo     
    You should get a list saying model view is distributed successfully.
    7. Checking the Port
    o       Go to T. Code WE21
    o       Expand Transactional RFC
    o       Find the port from the list which is created using BD64 for ECC (Receiving system) RFC Destination.
    8. Checking the Partner Profiles.
    o       Go to T. Code WE20
    o       Expand Partner Type LS
    o       Select the Partner profile ECC
    o       Double click on Message Type ZCATSTIME in Outbound parmtrs.
    o       Check Receiver Port is assigned correctlyo     
    Check the Basic type as your Basic IDOC object.
    9. Assigning the Message Type to Basic IDOC Object
    o       Go to T. Code WE82
    o       Click on Change & continue, New Entries button
    o       Give the Message type as ZCATSTIME
    o       Give Basic Type as ZTIMEIDOC
    o       Release as 4.6C
    o       Save and back10. Creating Inbound Function Module (Posting Program)
    o       Go to T. Code SE37
    o       Create a function Module ZCATSDB_TIMESHEET_SURESH
    o       Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.   
    o       Import Parameters
              P_WORKDATE                    LIKE               CATSDB-WORKDATE
              P_COUNTER                        LIKE               CATSDB-COUNTER
              P_LSTAR                               LIKE               CATSDB-LSTAR
    o       Export Parameters
    o       Tables 
                 S_PERNR                      LIKE           ZCATSPERNR
    [PERNR is select option parameters in ZCUSTOMIDOC report program so that it should be passed to function module ZCATSDB_TIMESHEET_SURESH in tables section. And also in tables section we used ZCATSPERNR, which is a global structure, which contains four fields as
    Ø     SIGN
    Ø     OPTION
    Ø     LOW
    Ø     HIGH]
    o       Exceptions
    o       Source Code
    FUNCTION zcatsdb_timesheet_suresh.
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(P_WORKDATE) LIKE  CATSDB-WORKDATE
    *"     VALUE(P_COUNTER) LIKE  CATSDB-COUNTER
    *"     VALUE(P_LSTAR) LIKE  CATSDB-LSTAR
    *"  TABLES
    *"      S_PERNR STRUCTURE  ZCATSPERNR
      TABLES: catsdb, edidc, edidd. " using structures of catsdb, edidc, edidd
      CONSTANTS: c_doctyp TYPE edidc-idoctp VALUE 'ZTIMEIDOC',  " idoc type
                 c_segnam TYPE edidd-segnam VALUE 'ZSEGMENTTIME',   "segment type
                 c_mestyp TYPE edidc-mestyp VALUE 'ZCATSTIME'.   " message type
    *001 comment begin
         creating internal tables with out header lines for catsdb, edidc, edidd and also
    -           work areas
    *001 comment end
      DATA: it_edidc  TYPE edidc OCCURS 0,    "  control internal table with out header line
            it_edidd  TYPE edidd OCCURS 0, " data internal table with out header line
            wa_catsdb TYPE it_catsdb1,  " work area for it_catsdb internal table
            wa_edidc  TYPE edidc,  " work area for it_edidc internal table
            wa_edidd  TYPE edidd,  " work area for it_edidd internal table
            wa_zsegmenttime TYPE zsegmenttime, " work area for zsegment internal table
            v_occmax  TYPE idocsyn-occmax,
            v_nbseg   TYPE i.
      CLEAR wa_catsdb. " clears work area of catsdb
      CLEAR wa_edidc.  " clears edidc work area
    *002  comment begin
    Save the message type and the basic IDoc type in the control segment.
    *002 comment end
      MOVE c_mestyp TO wa_edidc-mestyp. " assigning custom message type to edidc workarea
      MOVE c_doctyp TO wa_edidc-idoctp. " assigning custom idoc type to edidc workarea
    *003 comment begin
    Retrieve the maximum number of segments in the basic IDoc type.
    *003 comment end
      SELECT MIN( occmax ) FROM idocsyn INTO v_occmax WHERE idoctyp EQ c_doctyp AND segtyp EQ c_segnam.
    *004 comment begin
    Save the whole CATSDB table content in the IT_ZCATSDB internal table.
    *004 comment end
      SELECT pernr workdate lstar counter FROM catsdb INTO CORRESPONDING FIELDS OF TABLE it_catsdb WHERE pernr IN s_pernr AND workdate EQ p_workdate.
    *005 comment begin
    Create a data segment for each line of IT_ZCATSDB.
    *005 comment end
      IF sy-subrc EQ 0.
        LOOP AT it_catsdb INTO wa_catsdb WHERE pernr IN s_pernr.
          MOVE-CORRESPONDING wa_catsdb TO wa_zsegmenttime.
          CLEAR wa_edidd.
          MOVE c_segnam TO wa_edidd-segnam.
          MOVE wa_zsegmenttime TO wa_edidd-sdata.
          APPEND wa_edidd TO it_edidd.
          CLEAR wa_catsdb.
          CLEAR wa_zsegmenttime.
        ENDLOOP.
      ELSE.
        MESSAGE 'NO DATA FOUND FOR GIVEN SELECTION' TYPE 'I'.
      ENDIF.
    *006 comment begin
    Count the number of data segments.
    *006 comment end
      DESCRIBE TABLE it_edidd LINES v_nbseg.
    *007 comment begin
    If the number of data segments exceeds the maximum allowed number,then display an error message.
    *007 comment end
      IF v_nbseg GT v_occmax.
        MESSAGE  'IDOC ERROR Message' TYPE 'E000'.
      ENDIF.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' " for creating an catsdb idoc
      EXPORTING
      master_idoc_control = wa_edidc
    OBJ_TYPE = ''
    CHNUM = ''
      TABLES
      communication_idoc_control = it_edidc
      master_idoc_data = it_edidd
      EXCEPTIONS
      error_in_idoc_control = 1
      error_writing_idoc_status = 2
      error_in_idoc_data = 3
      sending_logical_system_unknown = 4
      OTHERS = 5
       IF sy-subrc <> 0.
         MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
         WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
       ENDIF.
    ENDFUNCTION.
    Save, check and activate
    111. Assigning the Inbound Function Module to Basic Type & Message Type
    o       Go to T. Code WE57
    o       Click on change, continue, continue and New Entries Button
    o       Enter the Module as ZCATSDB_TIMESHEET_SURESH Type as "F"
    o       Basic Type as ZTIMEIDOC
    o       Message Type as ZCATSTIME
    o       Direction as 2
    o       Save and back
    Now Login in 800 client of Application Server SAP-REMOTE
    12. Assigning the Inbound Function Module in ALE Table
    o       Go to T. Code BD51
    o       Click on continue, New Entries button
    o       Give the Inbound Function Module ZCATSDB_TIMESHEET_SURESH
    o       Give Input t. as 0 (zero)
    o       Save and back13. Creating Process Code
    o       Go to T. Code WE42
    o       Click on Change, New Entries Button
    o       Give Process Code name as ZCATSDB, give Description & Save
    o       Select Processing with ALE Services Radio button
    o       Select Processing by Function Module Radio button
    o       Click the ALE Table (arrow Icon) in Identification
    o       Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS
    o       Give maximum number of repeats 0
    o       Save and back, back
    o       Select the process code from the list & click on Logical Messages Icon
    o       Give the Message Type as ZCATSTIME
    o       Save & Back, Save & Back, Save & Back
    14. Changing the Customer Distribution model in receiving system
    o       Go to T. Code BD64
    o       Click on change and Create model view button
    o       Enter the short text and Technical name as CATSECC
    o       Select the model view & click on Environment -> Generate Partner Profiles
    o       Select Transfer IDOC Immediately and Trigger Immediately radio buttonso       Click on Execute You should get a list in green color which means it executed successfully.15. Assigning the Process Code to Message Type in Receiving System
    o       Go to T. Code WE20
    o       Expand Partner Type LS
    o       Select the Partner Profile CATSSENDER
    o       Double click on Message Type ZCATSTIME in Inbound parmtrs.
    o       Give the Process Code as ZCATSDB
    o       Click on Trigger Immediately Radio button
    o       Save & Back
    Save & Back
    16. Creating the Selection Program (Outbound Program)
    -         Login in client 800.
    -         Go to T. Code SE38
    -         Create a Report Program as ZCUSTOMIDOC with the following code
    REPORT ZCUSTOMIDOC
           NO STANDARD PAGE HEADING.
    TABLES:catsdb. " using structure of cats db table
    *000 comment begin
         this selection screen contains one select option and one parameter
    *000 comment end
    SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS pernr FOR catsdb-pernr.
    PARAMETER: workdate LIKE catsdb-workdate,
              LSTAR like catsdb-LSTAR,
              COUNTER like catsdb-counter.
    SELECTION-SCREEN: END OF BLOCK b1 .
    DATA: wa_val TYPE i.
    wa_val = pernr-high - pernr-low.
    *001 comment begin
          calling custom function module
    *001 comment end
    CALL FUNCTION 'ZCATSDB_TIMESHEET_SURESH'
      EXPORTING
        p_workdate = workdate " passing workdate parameter
        p_LSTAR = LSTAR
        p_counter = counter
      TABLES
        s_pernr    = pernr. " passing pernr select option
    IF sy-subrc EQ 0.
      MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' pernr-low ' AND ' pernr-high .
    MESSAGE i000(zaluri) WITH   'IDOCS CREATED FOR EMPLOYEES BETWEEN' PERNR-LOW 'TO' PERNR-HIGH.
    gives information message if idocs are created for given  employees
    ELSE.
      MESSAGE e000(zaluri) WITH 'NO IDOCS CREATED FOR EMPLOYEES' pernr-low  'TO' pernr-high. " gives error message
    " if idoc is not created
    17. Transferring the CATSDB records from sender Application Server SAPADM   to  receiver Application Server SAP-REMOTE
    -         Execute Report Program ZCUSTOMIDOC
    -         Give the Range of PERSONNEL NO'S, Date, Activity Type, Counter to Transfer
    -         Give Message Type as ZCATSTIME
    -         Give Receiver Logical system as ECC
    -         Execute
    -         You should get the IDOC Number
    -         Take the IDOC Number and go to T. Code WE05 & Execute
    -         In Outbox you can see the IDOC Status
    -         Select the status record in left side window
    -         Double click on the Status record in right side window-         You can see the Control Record, Data Record and Status Records for that IDOC
    If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully
    18. SENDING IDOCS FROM APPLICATION SERVER SAPADM
    TO APPLICATION SERVER SAP-REMOTE USING WEDI
    -         Go to T. Code WEDI & execute or T. Code WE19
    -         Give idoc number it is generated recently
    -         Continue & double click on segment to view data in segment
    -         Click on EDIDC to give port, partner no, message type, partner
    type of receiver. [For sender no need to give any port no leave it as
    blank]
    -         Click on Standard Outbound Processing button and click continue
    -         You will get a message as idocs successfully transferred
    Now Login in Receiver 800 client
    -         Go to T. Code WE05 & Execute
    -         You can see the status record in left side window
    -         If the status no is 53 and color is green, it means the IDOC is posted to Application successfully.
    -         You can see the Log Information by double clicking on the status record in right side window.
    -         Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC
    -         Now go to T. Code SE16
    -         Give the table name CATSDB & press F7
    -         See the contents of the table
    -         The table is updated with the catsdb records transferred from 800 client with our selection program.
    reward if u find useful
    regards
    Nagesh.Paruchuri

  • ECC and SCM connection

    Hi folks,
    i would like to see ECC and SCM scenarios connected by CIF, how ever HU2(ECC) and HU8 (SCM) systems are not interconnected. let us know whom do we need to contact in this regard.
    Thanks in Advance ...

    Hi Amit,
    The ES (emphasis on Enterprise Service or Web Service) Workplace Systems are actually setup for customers or consultants to test drive SAP delivered Enterprise Services, so it stands to reason that integration between these systems would be using web services / SAP Enterprise services for the most part.
    Trying to contact someone to configure CIF / ALE integration between HU2 and HU8 is not going to work for you.
    Regards, Trevor

  • Single Transaction code for ALE Configuration

    Hi All,
    I want to Know is there any Single Transaction code for the ALE Configuration instead of going through SALE, WEDI t-code or with defining logical systems assigning them to clients, creating RFC and Distribution Model, generate partner function and..so on.
    Please let me know if there is any t-code through which i can do the ALE configuration in a single T-code.
    Thanking you in advance,
    Bhanu

    hi ars
    i got a task saying that message type is DESADV01 ,but u told that DESADV01
    is basic type,can i know the difference.
    regards
    sagar

Maybe you are looking for