Function Module to Generate Outbound IDOC for Sales Documents

Hello Experts,
Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents.  Some of the fm's I have come across are the following:
IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
Points will be given for any help provided.
Thanks in advance.

Hi Nagaraj,
I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order.  For everyone's reference here is the code:
form process_data.
  DATA v_idoc       TYPE edidc-docnum.
  DATA i_edidd      TYPE TABLE OF edidd.
  DATA wa_idoc_ctrl TYPE edidc.
  LOOP AT i_nast INTO wa_nast.
    CLEAR i_msgs[].
    CALL FUNCTION 'WFMC_PROTOCOL_GET'
      EXPORTING
        cps_nast        = wa_nast
      tables
        messages        = i_msgs
     EXCEPTIONS
       NOT_FOUND       = 1
       OTHERS          = 2.
    LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
*--- Check first if there is an IDOC
      IF wa_msgs-msgv1 IS INITIAL.
        CONTINUE.
      ENDIF.
      v_idoc = wa_msgs-msgv1.
      CLEAR i_edidd[].
      CLEAR wa_idoc_ctrl.
      CALL FUNCTION 'IDOC_READ_COMPLETELY'
        EXPORTING
          document_number                = v_idoc
        IMPORTING
          IDOC_CONTROL                   = wa_idoc_ctrl
*         NUMBER_OF_DATA_RECORDS         =
*         NUMBER_OF_STATUS_RECORDS       =
        TABLES
*         INT_EDIDS                      =
          INT_EDIDD                      = i_edidd
        EXCEPTIONS
*         DOCUMENT_NOT_EXIST             = 1
*         DOCUMENT_NUMBER_INVALID        = 2
          OTHERS                         = 3.
      CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
        EXPORTING
          object                              = wa_nast
          control_record_in                   = wa_idoc_ctrl
*       IMPORTING
*         OBJECT_TYPE                         =
*         CONTROL_RECORD_OUT                  =
        tables
          int_edidd                           = i_edidd
*       EXCEPTIONS
*         ERROR_MESSAGE_RECEIVED              = 1
*         DATA_NOT_RELEVANT_FOR_SENDING       = 2
*         OTHERS                              = 3
      IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      COMMIT WORK.
    ENDLOOP.
  ENDLOOP.

Similar Messages

  • Function Module to create Outbound IDoc

    I have created a segment (ZSEGPRO), basic type (ZIDOCPRO) and message type (ZMSGPRO) to create a custom IDoc. Now I have to write a Function Module to create Outbound IDoc.
    I want to know what will be in Import, Export, Changing, Tables, Exceptions and Source code of that function module. The fields used in the segment ZSEGPRO is given below:
    Fld NameSource Data Elmn     Description
    PRODUCT MARA MATNR     Material number
    TEXT     MAKT     MAKTX     Material description
    PRN     MARA     YYBCEZNDR     Print Field
    Additional information: Export parameter will be BAPIRETURN for holding error message(if any).
    These Function Module need not require to be RFC enabled.

    Hi ,
    Refer these:
    There are two main reasons
    1) Make sure you call COMMIT WORK after the MASTER_IDOC_DISTRIBUTE
    http://help.sap.com/saphelp_nw04/helpdata/en/78/21783151ce11d189570000e829fbbd/content.htm
    2) The rest of the setting of the ALE IDoc might not have been done
    http://help.sap.com/saphelp_46c/helpdata/en/78/2177c951ce11d189570000e829fbbd/frameset.htm
    You can use the Area Menu WEDI and do the rest of the settings.
    ALE Quick Start guide and ALE Programming Guides for your reference
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    Recent discussion which could be helpful,
    About WE21, BD64, sm59
    Regards
    Shiva Kumar

  • Is it possible to generate outbound idocs for FI invoices? How?

    Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

    Dear Gabriel
    Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
    As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
    So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP.  However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
    thanks
    G. Lakshmipathi

  • Generate outbound idoc for Customer Master

    Hi Developers,
    I have requirement to generate outbound IDOC for Customer Master Data. I need to send customer master data through an Outbound IDOC. Can we generate an outbound DEBMAS06 idoc? Can someone help me finding a solution to this problem?
    Thanks in advance for helping.
    Regards,
    Gajendra

    Hi,
    If you have done all the required settings (logical system, partner profiles, distribution model), then either transaction BD10 / BD14 will help you generate the IDOC.
    If you want to send the idocs automatically, then you will to configure some program.
    Unlike transaction data, Master data IDOCS are not triggered immediately, you will have to do the required configuration in SPRO.
    Transaction SPRO
    SAP Customizing Implementation Guide -->
    SAP Web application Server --> Application Link Enabling --> Modeling and Implementing Business Processes -->
    Master Data distribution --> Replication of Modified Data --> Creating IDOCS from Change Pointers
    Take a look at this thread.
    Re: automatic Idoc outbound
    Regards,
    Ravi
    Note : Please mark the helpful answers
    Message was edited by: Ravikumar Allampallam

  • Add segment to outbound Idoc for Sales order

    HI experts,
    I need to add segment E1EDP02 under Existing segment E1EDP01 for outbound IDOC for Sales order. FM" IDOC_OUTPUT_ORDRSP".
    I have used the Exit : "EXIT_SAPLVEDC_003" for the FM "IDOC_OUTPUT_ORDRSP"  in the include of the Exit   i wrote my code also for adding segment and activate it.
    But when i am trying to debug the code it's not working
    So please guide me how to debug it
    I have followed below steps to Debug.
    1. In VA02 i have repeat the output.
    2. Put the breakpoint in the Exit include program .
    3. put the Breakpoint in ALE processing Routine in RSNASTED program also
    4. Trigger the program RSNAST00 by giving the  Parameter value of SALES ORDER number and execute.
    But not working
    And i need to know whether i have used the Correct EXIT or not.In that case how to identify the correct exit's
    Thanks In advance

    Hi,
    I hope you have to add your segments through WE30 first for your IDOC type.
    Cheers,
    Raja.D

  • Outbound idoc for sales order

    Hi,
    can any one guide me in orders  Message Control Configuration..
    I am trying to acheive the outbound idoc upon sales order creation through output type.

    CHeck these threads.
    Idoc Sales Order Creation .
    Re-open EDI - ORDCHG for outbound sales order

  • IDoc For Sales Document

    Hi All,
    I have a requirement to create IDOC for sales order that should have all data related to SO document flow (History). Using output determination, I am able to create IDOC but the history is not populated in the IDOC.
    I did not see any message type for SO history, Is it possible to create an IDOC for sending sales order history.
    Thanks in advance/

    Yes, you could create a absolutely new IDOC type for the SO history or using a custmized IDOC which only added some new field into the current IDOC type.
    If the structure you need is very different with the current exist IDOC type, you can choose to create a former solution.
    Import a new type IDOC, you need to do the structure defination for it, and create a process function and process code to the system which receive it and handle it.  And of course, you need to fill the IDOC and send it by yourself in ABAP code, using e.g. FM MASTER_IDOC_DISTRIBUTE.
    Hope it will be helpful

  • How to create outbound IDOC for Accounting document type RV

    Hello All,
    We have a requirement to create a downpayment request for a customer. We have copied the FAZ billing type and created a ZFAZ. For this the accounting document type generated is RV. This RV is a statistical document and does not contain any debits and credit entries. It is just to inform the customer to pay. We have to generate an IDOC for the same. I have configured FIDCC1 standard FI message type for this in ALE. But it does not seem to work.
    Does anyone have any inputs on this ? May be RV does not use the message type FIDCC1 ? Anything in relation to RV or downpaymnts, please let me know..
    Appreciate your responses.
    Thanks
    SH.

    Hello Alpesh,
    I tried adding breakpoints to the following userexits and many other places where they occur..but while creating billing doc FAZ nor while generating accounting document RV they were triggered.
    I have created a distribution model and created the partner profile with outbound for basic type INVOIC02 for message type INVOIC . What do you say?
    Just a note that this is an outbound process and i cannot use process codes.
    - EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
    - EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
    Thanks
    Smitha
    Edited by: Smitha H on Jul 25, 2008 7:56 AM

  • Outbound IDOC for sales order: message type, function module ?

    Hi all,
    is there a possibility to send out sales order data with an outbound IDOC (like sending an purchase order out with ORDERS.ORDERS05)
    I've looked in WE20, for application V1 there are process codes like SD01, SD04, ... but the function modules behind are no existing on our system (release 500)
    can anybody give me an little hint?
    Thank you very much
    best regards Hans

    Hi George,
    for every process code there is a function module attached you can see in WE41(t-code)..
    double click on the Process code you will able to see the Function Module attached to Process code..
    and also you can check it out in WE57 (t-code) link between the Function module and Message type and Idoc type..
    Process code      SD01                                               
    Description       ORDRSP: Order acknowledgment, ORD_ID01 (SD_ORDRSP) 
    Function module   SD_EDI_ORDRSP_ORD_ID01                             
    Process code      SD04                                               
    Description       DESADV: Shipping notif. with DES_ID01 (SD_DESADV)  
    Function module   SD_EDI_DESADV_DES_ID01    
    regards,
    Prabhudas

  • How to generate Outbound idoc for Material Reservation

    Hi Experts,
    I want to send outbound IDoc when a material reservation is created with tcode MB21.
    I have been working on this issue and finding the solution in SCN for a week...
    I found some messages similar to this but I could not find out the correct way how to do that.
    At this moment, I configured BD64/WE20 referring the following topic which seems to be feasible solution but could not find any outbound IDocs created, unfortunately.
    Implement ALE_RESERVATION_CREATE
    I appreciate if someone can help me how to create outbound IDoc with MB21 or advice some possibility of missing configuration or steps.
    Best Regards,
    Kenji

    Hi;
    Have been able to find the solution to create the IDoc MRESCR after entering a reservation? 
    I am in the same situation and I do not see the IDoc output in the BD87. 
    It would be nice if you share the solution.
    Thanks in advance

  • Creating outbound IDOC for EDI

    HI All,
    I have to create an IDOC for EDI. Can anyone tell be the function module to create an IDOC for EDI. I know MASTER_IDOC_DESTRIBUTE, but it is only used for ALE.
    Can anyone help me in this.
    Thanks.
    Shweta

    Dudes:
    It sounds to me like all of you guys need some training and some understanding of the basics.
    MASTER_IDOC_DESTRIBUTE is called by the standard IDoc interface after an IDoc has been built and is ready to be kicked out the door. It provides all the services needed to write the idoc to the database and send it out through the partner profile and file or tRFC port. It's used both for ALE and EDI IDocs.
    I cover the processing flow extensively in my new book from SAP Press "Architecting EDI with SAP IDocs". The book is available from:
    http://www.sappress.com/product.cfm?account=&product=H3003
    I also cover these topics in my IT Toolbox blog at:
    http://it.toolbox.com/blogs/ehadzipetros
    And my SDN blog at:
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417600)ID1280983950DB11991735787968519403End?blog=/pub/u/252038725
    Good luck. ejh,

  • IDoc outbound function module to generate Purchase order PORDCH IDoc

    Hi all,
    Can anyone help me with the outbound function module to generate PORDCH IDoc

    instead of that you can use the Below For PO's.
    Message Type : ORDCHG
    Process Code  : ME11
    Function : IDOC_OUTPUT_ORDCHG

  • Outbound IDOCs for Functional Location

    Hi experts
    We are planning to use IDOCs for interfacing SAP and Legacy system using XI.
    THis will be an outbound interface  as we will be updating the legacy system with SAP.Therefore I am looking for a standard outbound  IDOC for functional location.
    So far I have not found one. Can you advise the outbound IDOC for Functional location ?
    Another question I have , I have found some IDOC's but they are not released , Is there a way to release the IDOC's, what needs to be done for this.
    Many Thanks
    Regards
    Gaurav

    Hi Vinod,
    This is the case for the 2 outbound Idocs from ECC to SNC for which settings have been maintained to send them immediately:
    1. PORDCR1
    2. STPOD
    I have asked my PI team to check the PI port / PI cache. Will keep the thread updated if theres any resolution.
    Regards,
    Bharath

  • Trying to change Inbound IDOC to Outbound IDOC for testing....

    Hi Friends,
    I am trying to do the following
    1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
    2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
    3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
    4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
    HELP!! Rewards

    Hi Friend,
            The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
    Use
    You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an “empty” IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
    You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
    Activities
    ·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
    You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the “file“ type. The default file is the inbound file entered there.
    ·        You generate the IDoc using .
    The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
    ·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
    You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
    ·        Click on the white fields to change data in the segments.
    In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
    In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
    ·        The additional procedure depends on whether you want to test inbound or outbound processing.
    Test: Outbound Processing from MC
    Use
    Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
    Prerequisites
    You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
    ·        Customer or vendor records
    ·        Material records
    ·        Info records
    ·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as “messages” from the respective application.
    The appropriate file ports and partner profiles must exist in the IDoc Interface.
    Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to “1” (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
    Activities
    Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
    Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to “Collect IDocs” in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode “Collect IDocs” in live operation.
    Activities
    You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
    You can decide whether the output mode is set to “Start subsystem” or “Do not start subsystem” in the partner profile. This defines whether the external (sub) system processes the IDocs further.
    Use
    This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to “File”.
    Prerequisites
    A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are “credited” to the relevant IDoc in the form of status records in the SAP System.
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
    Test: Inbound Processing: Modified Outbound File
    Use
    This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to “File”.
    Prerequisites
    You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type “File” must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
    Standard inbound processing is then triggered;
    ·        Reading the modified file
    ·        Generating the IDoc(s) in the SAP System
    ·        Processing in the application
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
    Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
    The recipient in this case is the SAP System. The port is used for identification purposes:
    ·        SAP (for example RSMITH
    Test: Inbound Processing: Original Inbound File
    Use
    This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
    Prerequisites
    You require a correct inbound file. In this case, correct means that the:
    ·        Sender and recipient in the control record are correct
    ·        Direction in the control record is set to 2 (inbound)
    ·        Client in the control record and data records are correct or empty
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
    The file is deleted after being read successfully!
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
    ·        Inbound port
    ·        Name and directory of the file
    These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
    Thanks

  • Urgent: Creating ALE IDOC for SALES ORDER

    hi
    please tell me <b>step by step procedure to create ALE IDOC for SALES ORDER?</b>
    reward for sure
    regards
    ravish

    Hi,
         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 !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
    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
    Regards

Maybe you are looking for

  • Transfer structure not active after runing RS_TRANSTRU_ACTIVATE_ALL

    Hi BW Experts, we are having a migration and just after migration we are finding the the transfer structure is not active. Hence in order to activate the same we ran <b>RS_TRANSTRU_ACTIVATE_ALL</b> program but still in the job log finding some proble

  • Treo Pro No Vibration on any setting

    About a week ago my Treo Pro stopped vibrating entirely.The phone will not vibrate when the switch is set to silent, or with ringer on, or for text messages, or during the phone boot up. When it's set to ringer the sound notification works properly.

  • Can we input range of values in the Function Module CONVERSION_EXIT_MATN1_I

    Hi all, Can we in put range of values in the FM 'CONVERSION_EXIT_MATN1_INPUT' Like If I am inputting s_matnr which takes range of material number based on selection screen input. CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'    EXPORTING      INPUT    

  • View *all* databases in oracle 8i

    Hello all, Is there a statement/command which i can type to view ALL the databases in the oracle8i database. I am having a certain problem with an application which is using the database, only i am not aware which database it is using!! I do have dba

  • CHEQUE PRINT OUT

    HELLO GURUS HOW CAN WE TAKE CHEQUE PRINTOUT FOR GENERAL EXPENSES PAYMENT LIKE TELEPHONE EXPENSES FOR INDIVIDUAL EMPLOYEE WHILE WE ARE USING VENDORS PAYMENT THROUGH CHECK PRINTED BY SYSTEM. WHAT IS REQUIRED TO DO? PLEASE SUGGEST. THANKS & REGARDS. Mod