IDoc to IDoc through ALE

hello experts !! could u plz give me some idea or step by step help for creating IDoc to IDoc data transfer through ALE.
My scenarion is like the following:
there will be two client in two R/3 system..(Sending and receiving)....
in sending system i want to insert data in a particular table....
that data will be automatically updated in receiving system..
plz help meeeeeeee
thanks...
points will be rewarded.......

Hi Soumya,
Follow the process as below
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
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards,
Satish

Similar Messages

  • Regarding an error when an idoc is transferred through ALE

    hi guys,
    i have designed a custom message type and sent an idoc from server 1 to server 2 ( receiver system ) <b>using ALE</b>, idoc is transferred fine but data in idoc is not sent to receiver system i mean, there is no data in idoc.
    i received an error saying: idoc transferred with errors at inbound system.
    <b> it displays status 56 i.e EDI: partner profile not defined.</b>
    but partner profile and model view for both outbound and inbound system have been absolutely configered.
    can you plss help me with this.
    thanks very much
       pavan

    hi appana,
    thx for ur suggestion, actually outbound idoc is populated but problem is with inbound idoc - there is no data in it.
    what exactly do u mean by partner profile maintained for this idoc at inbound, actually i have created partner profile at inbound using we20 and assinged custom message type and process code ( functin module developed by me) to msgtype.
    can u be elaborative.
    thanks
    pavan.

  • Issues in employee replication from ECC to CRM through ALE/IDOC

    Hi,
    We are replicating the employees from ECC to CRM through ALE/IDOC.
    Some times for some employees, the Idoc status in CRM is  52(Application document not fully posted) in CRM (WE02 tcode)
    If I see the details its showing as " Identification Category BPCCOD is Not Assigned to Any Identification Type"
    What I need to do now to avoid this.
    Pl suggest
    Regards
    BABU.

    Hi Babu, I'm having the same error when I replicate my employes. I have define  BPCCOD in  spro - Cross-Application Components - SAP Business Partner - Business Partner - Basic Settings - Identification Numbers,  but this configuration does not resolve my problem.
    Could you resolve this problem?.
    Pls. let me know...
    Regards,
    George

  • Reverse HR/FI Posting through ALE/IDOC

    We had a scenario in which Payroll Run will happen in one instance & posting will happen in another instance through ALE/IDOC.
    Now we want to do the posting reversal though ALE/IDOC.
    There is no specific message type for HR/FI Posting Reversal
    Can anyone help on this?
    Regards,
    Ravi

    Ravi,
    What bharathi said is exactly correct Infact i was worked with HR/FI posting.
    Posting of payroll from HR to FI is our (HR job) but reverse posting is absolutly FI consultant job. Since before that we already estblished a link between G/L a/c's and Wagetypes.
    by creating symbolic accounts
    I suggest if you post this question in FI you will get more reply positvely
    Best Regards

  • Pass through scenario in SAP PI with no mapping for File to IDoc and Idoc to file scenarios

    Hi Experts,
    Can i have step by step process in SAP PI for pass through scenario with no mapping in case of file to Idoc and Idoc to file both cases please.
    What objects i can skip.
    My PI system is 7.3 dual stack.
    I have seen below blogs, still its confusing to me.
    When and how to create an scenario in SAP PI without mapping objects.
    Pass Through Scenario with no Mapping in PI 7.1
    Appreciate your help on this.
    Regards,
    Mohan.

    Hi Mohan
    In pass thru interface you don't need to create any ESR objects, only ID objects are required.
    Just Create a Receiver Determination and Receiver Agreement for your scenario (no need for Interface Det. and Sender Agreement).
    Specify the IDOC in the Sender Interface and namespace as urn:sap-com:document:sap:idoc:messages
    Or instead of creating objects manually, Run the wizard with Idoc name/namespace in sender/receiver interface
    Regards
    Osman

  • IDoc ready for dispatch (ALE service)

    Hello All,
    My IDoc gets generated with the status 30: IDoc ready for dispatch (ALE service).
    I want to trigger the IDoc automatically [status 03 (Data passed to port) and the signal light displayed to Green colour.]
    Also, I checked the partner profile (WE20). In the outbound parameters, I went to the appropriate message type & there the output mode is set to 2 (send immediately).
    Please let me know if there is any configuration setting that I need to check.
    Thanks & Regards,
    Saurabh Buksh

    Hello,
    could you please check whether there is any process or program that is locking the status of the idoc you are trying to process via BD87?
    Once I got the same error and I solved by just closing up a report (RC1_IDOC_SET_STATUS) that i was using in order to change the idoc status.
    Regards
    Antonio

  • Debugging customized function module when Idoc is triggered via ALE

    Hi,
    Whenever we save the billing document, an outbound idoc is triggered via ALE. The logic for the data to be included in the idoc is written in a customized function module.
    However we are making some changes and would like to include some more data in the idoc. But we find that when we put a breakpoint in the function module, on saving the billing document, the flow does not stop at the break point. We are 100% sure that the code in the function module gets executed based on the data in the idoc.
    How do we get into debug mode and break the flow in the function module so that we can debug in the function module?
    Any help would be greatly appreciated.
    Thanks in advance,
    Mick

    Hi Mick, this might be of some help 4 u.
    ALE IDOC
    Sending System(Outbound ALE Process)
    Tcode SALE - for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 - Create Model View
    Tcode BD82 - Generate partner Profiles & Create Ports
    Tcode BD64 - Distribute the Model view
    Message Type MATMAS
    Tcode BD10 - Send Material Data
    Tcode WE05 - Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE - for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 - Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 - Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 - Create Model View
    Tcode BD82 - Generate partner Profiles & Create Ports
    Tcode BD64 - Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE - for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 - Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 - Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 - Send Material Data
    Tcode WE05 - Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Change Pointers
    I know how to change the description of a material using ALE Change Pointers.
    I will give the following few steps
    1) Tcode BD61---> check the change pointers activated check box
    save and goback.
    2) Tcode BD50---> check the MATMAS check box save and comeback.
    3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
    4) Tcode BD52---> give message type : matmas press ok button.
    select all what ever you want and delete remaining fields.
    save & come back.
    5) 5) go to Tcode MM02 select one material and try to change the description and save it
    it will effects the target systems material desciption will also changes
    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
    give Message type : MATMAS and Executte
    ALE/IDOC Status Codes/Messages
    01 Error --> Idoc Added
    30 Error --> Idoc ready for dispatch(ALE Service)
    then goto SE38 --> Execute the Program RBDMIDOC
    29 Error --> ALE Service Layer
    then goto SE38 --> Execute the Program RSEOUT00
    03 Error --> Data Passed to Port ok
    then goto SE38 --> Execute the Program RBDMOIND
    12 Error --> Dispatch ok
    Inbound Status Codes
    50 Error --> It will go for ALE Service Layer
    56 Error --> Idoc with Errors added
    51 Error --> Application Document not posted
    65 Error --> Error in ALE Service Layer
    for 51 or 56 Errors do the following steps
    goto WE19 > give the IDOC Number and Execute>
    Press on Inbound function Module
    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
    cheers,
    Hema.

  • Outbound Idoc error handling through workflow

    Hi,
    I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
    How this task can be triggered when outbound idoc error occurs in the system?
    Kr,
    Vithalprasad
    Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

    Hi,
          Have a look
    Outbound IDoc Error Handling via Workflow
    Outbound idoc error handling through workflow

  • How can we identify idoc is generated from ale or edi

    hi friends,
    This is interview question asked in tcs,
    how can we identify idoc is generated from ALE or EDI.
    please give me reply if anybody knows
    thanks,
    hari priya

    Idoc created by ALE is a means of migrating DATA between SAP systems. You configure logical destinations, establish some migrating criteria and the system takes care of getting your data from point A to point B
    Where as Idoc created by EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
    EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
    Also refer to these lonks:
    www.sapgenie.com/sapedi/edi_sap_training.htm
    www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
    www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
    www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
    http://www.onestopsap.com/interview-Question/edi/
    IDocs act as data containers in an ALE scenario. They are just a format of storing application data and then transferred using ALE. Take a look at http://www.sapgenie.com/ale/why_ale.htm and http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc for further details on ALE.
    Check this link.
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
    http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
    Reward points if found helpful...
    Cheers,
    Chandra Sekhar.

  • How to tranfer IDOC and BAPI through LSMW

    Hi friends,
    I need documents regarding processing of IDOC and BAPi through LSMW,
    Thanks In advance,
    Regards,
    charan

    Hi
    LSMW-BAPI
    Step-by-Step Guide for using BAPI in LSMW
    Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
    Introduction:
    This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
    Pre-requisites:
    It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
    Step-by-Step Procedure:
    Details of the BAPI used in this scenario:
    Business Object: BUS2012
    Method: CreateFromData
    Details of Message Type and Basic IDoc Type:
    Message Type: PORDCR
    Basic IDoc Type: PORDCR02
    Let’s have a look at the BAPI first, before proceeding to the LSMW:
    1. Go to Transaction BAPI
    2. Click on Search Button
    3. Enter the value “BUS2012” and select “Obj.type(Technical Object Name”
    4. Press ENTER
    5. Following screen appears:
    6. On the left side of the screen, Expand the “PurchaseOrder”.
    7. Select “PurchaseOrder” and double-click on the same for details.
    Building LSMW using BAPI:
    1. Go to Transaction LSMW.
    2. Enter the Project, Subproject and Object information and click on CREATE.
    3. Enter the descriptions for Project, Subproject and Object.
    4. Now select Settings à IDoc Inbound Processing
    5. “IDoc Inbound Processing” screen appears. Enter the required details as shown below:
    6. Click on “Activate IDoc Inbound Processing”.
    7. Click on “Yes” when prompted for “Activate IDoc Inbound?”
    8. Hit on “Back” to return to the main screen.
    9. Click on Continue (F8). Following Screen appears:
    10. Select the Step 1 “Maintain Object Attributes” and select “Execute”.
    11. Select the radio button “Business Object Method” and enter the following details:
    Business Object: BUS2012
    Method: CreateFromData
    Hit ENTER
    12. Save and click on BACK button. Following information message is displayed.
    13. Now select step 2 “Maintain Source Structures” and click “Execute”.
    14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
    Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on “Create” again to create the child structure. Following popup appears:
    Select “Lower Level” and click on Continue. Enter the Item data structure name.
    Click Save and hit BACK button to go to the main screen.
    15. Select step 3 “Maintain Source Fields” and hit execute.
    16. Enter the fields as shown below:
    17. Click SAVE and return to main screen.
    18. Select step 4 “Maintain Structure Relations” and click Execute.
    Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
    Select HEADERDATA and hit ENTER
    Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
    Click Save and return to main screen.
    19. Select the step “Maintain Field Mapping and Conversion Rules” and click on execute. Maintain the Field Mapping as seen below:
    20. Select step 7 “Maintain Source Files” and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
    Save and return to main screen.
    21. Select the step “Assign Files” and click on Execute.
    Assign the file provided to the source structure. Here the same file is provided for both the structures.
    Save and return to the main screen.
    22. Select the step “Read Data” and click on Execute.
    Click on Execute.
    Return to the main screen.
    23. Select the step “Display read data” and click on execute.
    Click on the structure name to get the field level values.
    24. Return to main screen and now select “Convert Data”.
    25. Return to the main screen and select “Display Converted data”.
    26. Return to main screen and select “Start IDoc generation”.
    27. Now select the step “Start IDoc Processing” on the main screen.
    28. Return to main screen and click on “Create IDoc overview”. Here the data record and status records of the IDoc could be viewed
    It is given in screen shot.
    http://www.****************
    LSMW-IDOC
    see this and do accordingly
    http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
    Go through the steps
    Hi please go through the following steps for IDOC method
    Step 1. Run the transaction ( /nlsmw ) you will reach to the screen
    Here you have to specify
    Project : 060_BUS_TRANS
    Subproject : SERVICE_TICKET
    Object : SRV_TICKET_ZSVT
    click on the execute button .you will reach the screen :
    The screen shows the 15 steps to Run the lsmw
    Step 2) select the first step ( Maintain object attributes) and click the execute button.After clicking on the execute button you will reach at. the screen
    Here you have to specify ( MEssage type and basic type)
    click on the BACK button
    Step 3) select the 2nd step ( Maintain source structures) and click the execute button
    Here you have to specify the source structures.
    Step 4) Select the 3rd step ( Maintain source fields) and click on the execute button :
    Here you have to specify the fields present in the source structure
    Step 5) select the 4th step ( Maintain structure relationship ) and click on the execute button :
    Here you have to specify relationship between source and target structures
    Step 6) select the 5th step ( Maintain field mapping ) and click on the exécute button :
    Here you have to map the fields between source and target structure. Also you have to apply conversion rules here if any
    STEP 7) select the 6th step and click on the exécute button
    Here you can define any fixed value or user define routines
    Step 8) select the 7th step ( Specify files) and click on the exécute button :
    At This screen we have to specify the files for This we should be in change mode .So please click on the button shown in the above screen. After clicking on This button you will be in change mode and will be able to specify the files :
    Step 9) select the 8th step ( Assign files) and click on the exécute button
    For assigning files yoy should be in change mode do the same thing click on the button as shown in the above screen :
    Then assign the files to different structures.
    Step 10 ) select the 9th step ( Read Data) and click on the exécute button :
    After clicking on the exécute button you will reach to the screen
    Again click on the exécute button . After clicking on the exécute button you will reach to the next screen
    Here you will see data is read.
    Step 11) select the 10th step ( Display read data) and click on the exécute button :
    Here you can see your test data present in test files assign to source sturcture
    Step 12 ) select the 11th step ( Convert data) and click on the exécute button :
    After clicking on the exécute button you will reach to the screen
    Click on the exécute button as shown on the : After click on the exécute button you will reach to the next screen
    Data is converted
    Step 12th ( Display converted data is same as Display read data )
    Step 13 ) select the 13th step ( Start idoc generation) and click on the exécute
    button :
    At this step Idoc is generated using converted data
    Step 14) select the 14th step ( Start idoc processing ) and click on the exécute button :
    After clicking on the exécute button you will reach to the screen :
    And then click on the exécute button : After clicking on the exécute button you will reach to the final processive screen
    If data is processed correctly you will see ( 53 Status message with green sign)
    http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
    http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
    Reward points for useful Answers
    Regards
    Anji

  • Options to create IDOC in IDOC Flatfile

    Hi,
    we have requirement to process a fixed length file and map that structure to a standard IDOC and that IDOC has to be written out as IDOC flat file.I just want to get different opinions to see whether there are any other options other than using ABAP mapping like mentioned in that standard How to Guide IDOC XML to IDOC Flatfile.
    My scenario is  Fixed length file ->XI->IDOC Flatfile-->SAP(through File port with RSEINB00 Report)
    I know there is module available in PI7.1,but we are still in PI7.0 with SP18 and no plans to up grage yet.
    In the file I get single header,multiple details and single trailer records and I have to create multiple IDOCs(that many number of Detail Records) from a single file.So,I think I need to use BPM first to convert multiple IDOC to single IDOC and then use the ABAP mapping to convert IDOC XML to IDOC Flatfile.like two steps.
    so I am thinking to avoid BPM,ABAP mapping and to see different options to create an IDOC flat file and the receiving SAP system can read the IDOC flatfile using standard File port.Receiving SAP is is very low version(I think 3.0) which is not supporting IDOC adapter communication from XI.
    please suggest different options to get IDOC Flatfile or even directly sending IDOC  (with ALE connection) that has been created after the mapping from ffixed length flatfile to standard IDOC.
    Thank you in adavance.
    Babu

    > In the file I get single header,multiple details and single trailer records and I have to create multiple IDOCs(that many number of Detail Records) from a single file.So,I think I need to use BPM first to convert multiple IDOC to single IDOC
    Hi Babu,
      When PI reads the file from source system, it will read all the data into Single XML file and in message mapping just do 1:N mapping to create multiple IDOCs from single XML. You dont have to use BPM for this requirement.
    You wait for better solution from other for 2nd part of your requirement i.e IDOC-XML to IDOC Flat file conversion.
    Have a great day.
    Cheers,
    Jag

  • Organisational structure replication through ALE

    Hi Gurus,
    Can you guide me how to do organisational structure replications through ALE.
    The transaction to be used are BD21 .
    I have tried and i am not able to see any IDOCS in green colour without error.
    Can anybody explain me the process in detail.
    Kind Regards,
    Shruti

    Hi Shruti,
    Pease check this in Org,Replication /Org.Model
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f03e6f6c-8c16-2a10-1581-ed8812e2effe&overridelayout=true
    and take help from ur ABAP'r also.
    Thanks
    Swati

  • Transfer of inforecord condition types through ALE

    Hi,
    I want to know how to transfer Inforecord Condition Types other than PB00 through ALE.For condition type PB00,we can use msg type COND_A & t-code MEK3.Similarly, what are the corresponding values for other condition types like FRA1 etc.
    Thanks,
    Kaveri

    Hi,
    If we are loading the conditions by IDoc type COND_A, we do not give the transaction code, instead we specify the table (like KVEWE = 'A' & KOTABNR = '025' for the Inforecords with plant level conditions), We give the condition records to structure E1KONP with condition PB00 as first condition followed by other conditions ( example RA00, RA01) in sequence as per the condition schema mentioned.
    So you can load the FRA1 condition the same way, just feed the LSMW the condition record FRA1after PB00.
    Hope this helps.
    Best Regards, Murugesh

  • Incoming Invoice Parking through ALE

    Hello Gurus,
    We have a scenario in which we trigger a IDoc on saving of VF01 transaction( INVOIC01).
    We send this IDoc to the other SAP system.
    Here we have to park this Invoice through MIR7.
    Here the reference for parking Invoice is PO for Thirty Party Scenario and Delivery Note for GR based.
    This we need to to do through ALE.
    Please let me let know if we need any conversion rules and is it possible by using the said IDoc: INVOIC01.
    Also do we require to apply any SAP note.
    Thanks in Advance.
    Pavan

    Hi Pavan,
    If you want to park an EDI-invoice, you can use the note 501524.  
    Please review the online documentation at help.sap.com by following this                                
    path:                                                                               
    ->Materials Managament                                                                               
    ->Logistics Invoice Verification (MM-IV)                                                               
      ->Logistics Invoice Verification (MM-IV-LIV)                                                          
       ->Invoices Received via EDI (MM-IV)                                                                  
        ->Processing EDI Invoices                                                                           
    I hope this note can help you fruther
    best regards
    Erika

  • Doubt on IDOC TO  IDOC communication

    Hi Experts,
    I have a doubt on IDOC to IDOC communication:
    Plz clarify it
    1. what is the need of passing same IDOC from one system to other system through XI while communicating between two systems,it can be done by using ABAP also ?
    2.what is the advantage of passing like this through XI compared to ABAP?
                           Plz clarify good answers will be rewarded .
                                                                                    Regards,
                                                                                    Vinod.

    Hi,
    See when you are dealing with Only IDOC to IDOC Communication means there is no need of XI here.
    You can go with ALE also here.
    Situations to go to XI.
    1) when you have the Different field mappings
    2) When you are having the multiple receivers
    3) when you are dealing with Bundling & Transformations
    Reward Ponts If Helpful
    Regards
    Giri

Maybe you are looking for

  • Problem connecting to one website, tracert shows timeout at 7 & 8

    Hi all, So I am having issues connecting to one website. Everytime I run tracert it shows a similar timeout. I am not sure what is causing this. My web browsing otherwise is great. Just having issues with this one website. Below is a sample of tracer

  • Error Occurred While Processing Request

    Hi I am getting this message when attempting to open my website. Error Occurred While Processing Request Cannot find CFML template for custom tag header. ColdFusion attempted looking in the tree of installed custom tags but did not find a custom tag

  • Connect more than one computer to a time capsule volume?

    Hello. I am considering buying an old time capsule (500G, 2nd generation) as a little in-house server to store data that need to be accessible for more than one work station. Is it possible to connect more than one work station to one time capsule? T

  • How to download a report in CPS

    Hi , I need to download the report for the list oj jobs which was failed since last one month. Kinldy help me for this. Thanks, Ramkumar

  • Extend cutomer master data

    Dear All, what is the procedure to extend customer master data.i want to extend my customer master with distribution channel. Regards Ajit jaiswal