SLSRPT Inbound or Outbound idoc ?

is SLSRPT inbound idoc or outbound idoc and what is the Process code used ?
Thanks
Praveen chindam.

Hi Praveen,
Welcome to sdn.
This function allows you to receive and process the following types of partner transmissions in CRM:
·        Resale Report u2013 (ANSI X12; EDI 867, Message Type SLSRPT)
it is an inbound idoc.
see this link
http://repository.edifice.org/migs/slsrpt3/compare.htm
thanks
trinadh

Similar Messages

  • Puprose of inbound and outbound idocs

    plz help me
    what is inbound and outbound idoc ? its purpose
      inbound and outbound idoc steps
    thnaks

    Hi Mahesh,
    Please check this link
    what is the need of ALE/ IDOC
    what is idoc.
    IDOC creation
    inbound  idoc creation
    Best regards,
    raam

  • Degugging Inbound and Outbound idocs

    Hi friends,
    Can any one help me in debugging Inbound and outbound IDocs?
    1.I found the inbound FM using Tcode we19,clicked the inbound FM button and called it in the debugging mode.
      While debugging the Inbound FM iam nt able to figure out the actual problem.Is there any way to reach out the exact problem?
    2.How to find out the outbound Idoc FM and debug it?
    Your help is appreciated.
    Thanks in Advance.

    Hi,
    Inbound or Outbound IDoc processing FM can be found iin partner profiles(WE20).
    for Outbound: WE20 --> choose partner type --> Outbound parameters --> choose message type --> Message control Tab --> Double click on Process code to get the FM assigned.
    for inbound: WE20 --> choose partner type --> Inbound parameters --> choose message type --> inbound options --> Double click on Process code to get the FM assigned.
    For debugging, use Tcode WE15 for outbound, But before that u need to set the output type dispatch time as 1 (Send with periodically scheduled Job). Go to Output type assignment screen --> assign the output type --> choose further processing --> Set Dispatch time as 1 --> Save.
    Note: U need to keep the break point in the Outbound FM or exit if any before going to WE15 to debug from that point.
    Hope it helps,
    SG.

  • Scheduling inbound and outbound idoc  processing

    Hi everybody.
    I ´d ike to know which is the best way to schecule the outbound and inbound idoc process.
    Nowadays we are using this:
    INBOUND PROCESSING
    - In WE20 the idocs are checked with "Trigger with a background program".
    - The program RBDAPP01 is scheduled with a job to trigger the process of the inbound idocs.
    OUTBOUND PROCESSING
    - The program RBDMIDOC is scheduled to create the idocs than have been created with change pointers.
    - The program RSEOUT00 is scheduled with a job to trigger the process of the outbound idocs.
    Is there any better option to improve de perfomance????
    Edited by: Christian  Abad Chico on Nov 13, 2009 10:09 AM

    Any answer

  • Inbound and outbound Idoc for shipment

    Hi all,
    I woul need to configure an Idoc type both in outbound and in inbound for a shipment document.
    For the outbound process I'm trying to use the Idoc:
    message type SHPMNT_TNDR
    basic type SHPMNT04
    Is it right from your point of view?
    I don't know which Idoc type I've to use for the inbound process considering that I've to use it in order to add, on an existing shipment document, the stages distances.
    Could someone of you help me!!
    Thanks,
    A

    Hi,
    thank you for the previous answer.
    Really the inbound Idoc should change an existing shipment document in some field.
    I'm trying to build this Idoc type with the WE19 t-code but if I try to elaborate the Idoc I'm not able to process it succesfully (i'll obtain status 51 - message: "Idoc can not be processed without error").
    I'm inserting in this Idoc with WE19 the TKNUM (document number), the field E1EDT18-QUALF=CHA (that should be mean change), E1EDT18-PARAM=1 (IDoc fields are only copied if they are empty) and few some other information like the forwarding agent.
    Do someone have a suggestion for me in order to create this Idoc, in order to test it and change some fields in my shipment document?
    Thanks!!

  • Outbound IDoc Error: Status Code 37  'Sender Port' is invalid

    Hi
    I have an Error when the Outbound IDoc is triggered.
    It shows that 'Sender Port in Control Record is invalid'.
    Status Code: 37.
    I know that there are some issues with the Sender Port Definition.
    Please help me out to solve this problem using some checkpoints at each and every step.
    Reward Points Assured.
    Regards,
    Baburaj

    Hi Baburaj Manickam
    Good
    Follow this simple procedure
    1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
    -  Create File Port (WE21) for outbound file.
    -  Maintain Distribution Model (BD64) for sender ->receiver system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s). 
    _  Then you can FTP the file(s) to receiver system.
    2) Upload the flat file as an IDOC on the inbound sytem
    which is Client2(RECIEVER).
    -  Create File Port (WE21) for inbound file.
    -  Maintain Distribution Model (BD64) for receiver -> sender system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RSEINB00 to upload IDoc MATMAS file(s). 
    INBOUND IDOC PROCESSING:
    Firstly attach your idoc to a process code.
    In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
    Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
    1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
    2. Set Function Modules as Inbound: - Transaction BD51
    3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
    4. Create process codes : Transaction WE42, and link the z-function module.
    5. Create partner profile: transaction WE20 and attach the message type and process code.
    6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
    Try the Trasaction WE19 for testing your inbound and outbound IDOCs
    Good Luck and Reward me for the same
    Thanks
    Ashok.N

  • IDoc to XI u0096 Outbound IDoc

    hi Experts,
    Please let me know how to post IDOC to XI in R/3 Sender System?
    Please help
    Sourabh

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

  • Outbound idoc for RFQ

    Hi,
    can you tell me Outbound idoc for RFQ, Inbound idoc for Quotation and PO

    P786809 wrote:>
    > Hi,
    > can you tell me Outbound idoc for RFQ, Inbound idoc for Quotation and PO
    Hi,
    This is the idoc type..
    ORD_ID01  - Req.for quot./quotation/purchaseorder/order change
    Message Type for               IDOCTYP    
    QUOTES  -ORD_ID01   
    REQOTE  -ORD_ID01   
    REQOTE is the outbound idoc will trigger for RFQ
    QUOTES and REQOTE will trigger for Inbound idoc for RFQ
    ORDCHG,ORDERS,ORDRSP,PORDCR will trigger for PO inbound and Outbound idoc
    Regards,
    Prabhudas

  • Creation of Inbound Idoc for the Outbound Idoc in same client

    Hi,
    My requirement:
    Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
    It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
    I found there is a field for function module in WE21,can this be used to get the requirement done.
    Please suggest.
    Regards,
    Amar

    Example of a program that create and post an inbound idoc....maybe that will help you:
    report  zzinbound_idoc.
    data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
    data: g_edidd like edi_dd40 occurs 0 with header line.
    data: g_e1bpache09 like e1bpache09.
    parameter: mode type c default 'A'.
    refresh: g_idoc_control_record, g_edidd.
    clear:   g_idoc_control_record, g_edidd.
    *-Build Control Record -*
    g_idoc_control_record-mestyp  = 'ACC_DOCUMENT'.   "Message type
    g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
    g_idoc_control_record-direct  = '2'.              "Direction
    * Receiver
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
        g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-rcvprt = 'LS'.             "Partner type
    g_idoc_control_record-rcvpfc = ''.               "Partner function
    * Sender
    g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-sndprt = 'LS'.             "Partner type
    g_idoc_control_record-sndpfc = ''.               "Partner function
    g_idoc_control_record-refmes = 'Customer clearing'.
    append g_idoc_control_record.
    *-Build Idoc Segments -*
    *---E1KOMG
    clear g_edidd.
    clear g_e1bpache09.
    g_edidd-segnam               = 'E1BPACHE09'.
    g_edidd-segnum               = 1.
    move g_e1bpache09 to g_edidd-sdata.
    append g_edidd.
    *-Create idoc -*
    *-Syncronous
    if mode = 'S'.
      call function 'IDOC_INBOUND_SINGLE'
        exporting
          pi_idoc_control_rec_40              = g_idoc_control_record
    *     PI_DO_COMMIT                        = 'X'
    *   IMPORTING
    *     PE_IDOC_NUMBER                      =
    *     PE_ERROR_PRIOR_TO_APPLICATION       =
        tables
          pt_idoc_data_records_40             = g_edidd
        exceptions
          idoc_not_saved                      = 1
          others                              = 2.
      if sy-subrc <> 0.
        message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      endif.
    *-Asynchronus
    else.
      call function 'IDOC_INBOUND_ASYNCHRONOUS'
        in background task as separate unit
        tables
          idoc_control_rec_40 = g_idoc_control_record
          idoc_data_rec_40    = g_edidd.
      commit work.
    endif.
    write: / 'Well done!'.

  • Need IDOC inbound and outbound programs

    hi,
    i am new to xi.
    i want IDOCs , inbound and outbound / function module  programs for    PURCHASE ORDER
    and GOODS RECEIPT.
    ex:  BD10 for material master (matmas01).
    thanks and regards
    v ijender

    for purchase order.
    ORDERS / ORDERS04
    ORDCHG / ORDERS04
    ORDRSP / ORDERS04
    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.
    and also check the below link
    http://www.erpgenie.com/sapedi/message_types_masterdata.htm
    regards
    kummari

  • IDOC Inbound and Outbound

    Please let me know How to handle IDOC inbound and Outbound preferably with example. I am new to it.

    hi,
    your question is very broad,
    start reading continue from there...
    <a href="http://help.sap.com/saphelp_46c/helpdata/en/19/3cf334c20ccc52e10000009b38f83b/frameset.htm">Doc Interface: EDI Application Scenarios (BC-SRV-EDI)</a>
    <a href="http://help.sap.com/saphelp_46c/helpdata/en/dc/6b8a4943d711d1893e0000e8323c4f/frameset.htm">IDoc Interface / Electronic Data Interchange (BC-SRV-EDI)</a>
    An example:
    inter company invoiceing:
    the SD invoice has an output type (INVOICE01) that sends an Idoc that creates the mm invoice (invoice verification)
    for more data see the links above
    good luck

  • Relating outbound idoc to inbound idoc to create a document

    We have a requirement to relate the outbound idoc to inbound idoc , transfer the data and create a document.
    Kindly let me know the tcode / configuration steps of how can we relate the idocs.
    Thanks,
    Nalini S.

    Hi Juan,
    Check the IDOC: WMATGRP01. Hope it will be helpful for you.
    BR,
    Lokeswari.

  • Trigger an outbound idoc to sender system after inbound idoc has status 53

    Hi all,
    We have two different partners (say A and B)which send inbound idoc to ECC of same message type WMMBXY. This updates goods movement. The partner A collects the idocs(WE20 partner profile setting) and partner B trigger's immediately. Now our requirement is after successful processing of idocs (satus 53) we need to send another type of idocs to the sender regarding the updation/ changes occured in ECC.
    Since partner A collects the idocs how can we check that it reaches 53 status and send the outbound idoc to A.
    Kindly help me in solving this issue.
    Thanks,
    Aravind

    Create a new process code WMMB to ZMMB & assign a FM ZL_IDOC_INPUT_WMMBXY
    & call the standard FM L_IDOC_INPUT_WMMBXY , check the status or any error other wise create a new IDOC using
    Master_IDOC_CREATE, hope the solution works for you

  • Sending And Receiving IDOC (Inbound or Outbound) from Oracle To R/3

    Hi everyone,
    I am still new in XI development and i'm still confused even I have collect many information from SDN. Sometimes, when you got a lot information, instead of helping it's confused you _
    My specification like this :
    - There is XI between Oracle System and R/3
    - In my functional design, i have given information about message type and basic type from IDOC
    - I have given information about what BAPI that must be used to process IDOC
    Anyone know how me to handle inbound and outbound for this specification (step by step) from setting XI,IDOC and Processing Code ? Thank you
    Best Regards,
    Satria

    Hi everyone,
    I am still new in XI development and i'm still confused even I have collect many information from SDN. Sometimes, when you got a lot information, instead of helping it's confused you _
    My specification like this :
    - There is XI between Oracle System and R/3
    - In my functional design, i have given information about message type and basic type from IDOC
    - I have given information about what BAPI that must be used to process IDOC
    Anyone know how me to handle inbound and outbound for this specification (step by step) from setting XI,IDOC and Processing Code ? Thank you
    Best Regards,
    Satria

  • Why does an Inbound IDoc no change and differs from an Outbound IDoc no?

    Hi Experts,
    This seems to be a basic question..! But can someone kindly clarify why an IDoc number gets changed when sent from one R/3 system to another R/3 system and how does this happen???
    i.e., whenever an IDoc was triggered from R/3 system A to R/3 system B through XI/PI, the Inbound IDoc number (in system B) differs from the Outbound IDoc number (in system A)... Why does this happen and how???
    Thanks in advance!
    Br,
    G@nesh

    Hi Ganesh,
    The IDOC numbers are always Unique,
    IDOC can be generated in SAP system as a result of internal testing (WE19), or
    can be posted from a non sap system (say PI).
    So every time a new IDOC comes, it is assigned a new number to avoid confusion and also this plays a
    critical role in the  end to end testing and validation.
    If you look at the control record of the IDOC you can see a element called DOCNUM. this stores to actual IDOC number.
    from PI side you can  use IDX5 and in ECC  We02/05 to notice the idoc numbers.
    Regards,
    Srinivas

Maybe you are looking for