Posting IDOCs with partner type SP ?

We have to post IDOCs to SAP where the partner type is SP . How do we configure XI to achieve this ?
We are disabling the control record and so not looking at the option of hardcoding the EDI_DC record.
I understand we need to specify Alternate identifiers in IDOC channel and also choose header mapping in receiver agreement, however am not very clear on the steps.
Can neone help me with the steps.
Thanks
Saravana

I need values something like below to be in the control record of the IDOC and could not find a way of doing it
  <SNDPOR>PORT1</SNDPOR>
  <SNDPRT>SP</SNDPRT>
  <SNDPRN>ServiceProvider1</SNDPRN>
  <RCVPOR>SAPS32</RCVPOR>
  <RCVPRT>SP</RCVPRT>
  <RCVPRN>ServiceProvider2</RCVPRN>
By default , the SNDPRT & RCVPRT carry the constant "LS"(i still do not get y this is enforced by the IDOC adapter). Our sender system is a FTP server & receiever is SAP system. We have the Business Systems defined as service without party.
I tried hardcoding the values in EDI_DC40 in message mapping, but the IDOC adapter removes(!!) it and creates its own header(inspite of the chk box being unchecked or checked!!?? in the communication channel configuration)
Christoph , i could not make out much out of the thread u ve pointed to.
Thanks
Saravana

Similar Messages

  • Issue: "No Authorization to send Idocs with message type Orders" - IDX5

    Hi All,
       I am working on a File to IDoc(Orders.Orders05) scenario. The sender is PI Server and the receiver is the SAP ISR system. A technical system has been created in PI SLD for the ISR system and a Business system is added to that. The logical system created in ISR system using Tcode BD54 is added to the business system in PI. A new RFC destination is created in PI system to connect to the ISR system.
      On the ISR system Partner profile is created using TCode we20 with the same logical system name already created using Tcode BD54.
    When sxi_monitor is executed on the PI system, It shows checked flag on the Inbound side and Red flag on the Outbound side. And when idx5 is executed, it shows the new Idoc number and when it is double clicked, it shows the Status Text as
    "No Authorization to send IDocs with message type Orders".
    All authorizations have been provided on the Sender side.
    Please let me know if any authorization need to be provided on the ISR system or Is this an error on any settings.
    Thanks in Advance.
    Stalin S.

    Hi,
    Check this Thread which deals with the Authorization Issue
    RFC Adapter
    And also check this how to check whether u have sufficient authorization to send the Idocs or not
    To test the Authorization check
    Double click the RFC Destination that u have created in XI towards R/3 in SM59
    Select UtilitiesTestAuthorization test
    By this you can come to know whether your user is having the propper authorization or not
    REgards
    Seshagiri

  • Creation of IDOC with message type INVOIC01

    Hi All,
    I am trying to create a new IDOC with message type INVOIC01.
    When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
    However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
    The client wants me to create IDOCs with basic type INVOIC01.
    Can anyone please help?
    Thanks in advance.
    regards
    Nagarajan

    Hi Nagaraj!
    I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
    Thank You,
    Natalija

  • RFC error "No authorization to send IDOCs with message type ..."

    Hi all,
    I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
    I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
    I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
    Any suggestions?
    Regards,
    Liesel

    Hi Liesel,
    The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
    Please check if the user id/Password that you have given has all the authorization.
    Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
    There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
    Regards,
    Abhy Thomas

  • Error : No authorization to send IDocs with message type MATMAS

    Hi All,
    My scenario is FILE-XI-IDOC.
    I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
    When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
    Do I need to give any authorizations on XI side or on R/3 side?
    If so, what is the authorization required?
    I could not find the note :837595.

    <i>You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
    This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
    Solution
    In transaction PFCG, extend the role of the logon user by adding the following authorizations:
    Authorization object S_RFC
          Field name RFC_TYPE value FUGR
          Field name RFC_NAME value EDIMEXT, SDTX
          Field name ACTVT    value 16
    Authorization object S_IDOCDEFT
          Field name ACTVT  value 03
          Field name EDI_CIM value ' '
          Field name EDI_DOC value TXTRAW01
          Field name EDI_TCD value WE30
    Authorization object S_CTS_ADMI
          Field name CTS_ADMFCT  value TABL
    Authorization object S_TABU_DIS
          Field name ACTVT      value 03
          Field name DICBERCLS  value</i>
    from the note mentioned above.
    Regards
    Bhavesh

  • Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

    Hello All,
    I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
    Br,
    Sri

    Hi !
    Becaus alle this happens in beckgound, things are a bit difficult but solvable....
    What you should do is a "Authority trace" ... as follows....:
      - Go to the ST01
      - Mark "Authorisation Check"
      - Swich the trace on for your Workflow user
      - Execute the Workflow until the error uccurs
      - Go back to the ST01
      - Press the "Analyze" button and see what error occurs
    Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
    Regards
    rainer
    Some Reward poins would be nice if that helped....

  • No authorization to send IDocs with message type R

    I'm in the process of installing some business content for a 3.5 prototype.  When trying to load some master data I get the following error in the transactional RFC in the source system.
    "No authorization to send IDocs with message type R"
    Any clues to what may be causing this?
    Any help appreciated.
    thanks
    Mike

    Hi Michael,
    the suggestion for SAP_ALL was just for testing purposes in order to see whether it works then. If security is an issue you should reduce the authorization to the ones really needed (see note).
    Another security option is to make the background user a system user and not a dialog user.
    Regards, Klaus

  • Wrong Partner Type in IDoc with message type REMADV

    Dear all,
       We have created 2 IDocs, one for outbound (first in one company code) and one for inbound (receiving company code) with transaction F110 (message type REMADV, Idoc basic type PEXR2001). However, for the first outbound IDoc we have created, we have the wrong Partner type (we would like it to get type KU (customer)) LS (Logic system).
    Does anyone know how to change the partner type from the Idoc generationg?
    Many thanks,
    Ronny

    Hi,
    Welcome to SDN.
    Please delete the exisiting outbound partner profile (WE20) for message type REMADV which under partner type LS (Logical System) and setup new outbound partner profile for partner type KU (Customer).
    Regards,
    Ferry Lianto

  • Idoc Scenario Partner type not LS

    Hi experts ,
    we have gone through  https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a&overridelayout=true for idoc scenario where idoc partner type is not a logical system .Now we are working on case2 scenario in above document.we have some confusion in the configurations at R/3 side.Can somebody explain the step by step configuration at R/3 side.
    Thanks.

    Hi Mark,
    For your requirement you, create partner profile for LS with following steps :
    Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
    Message Type      : INVOIC
    Under Outbound Option u2013 Tab
    Receiver Port      : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
    Pack Size           : 1
    Transfer IDoc Immediately (Select)
    Basic Type           : INVOIC02
    Cancel Processing After Syntax Error (Select)
    Under Message Control - Tab
    Application           : V3
    Message Type      : RD00
    Process Code           : SD09
    Hope, your problem will get resolve.
    Regards..
    Imran

  • Outbound INVOIC idoc to partner type LS

    Hello,
    We are trying to issue outbound invoices( Message type INVOIC / basic type INVOIC02)  to a 3rd party who will be doing the billing on our behalf.  We are trying to issue an ALE output type to a LS (logical system) partner type and we are receiving a message B1131, that says that partner type LS cannot be used here, only KU and LI partner types allowed.
    We can create the idocs if we setup our partner as a KU customer.  However, given that we are sending these to a 3rd party system, it seems that we should be using LS.  Does anybody know if there is some configuration where we can choose to be able to send an idoc of message type INVOIC to a partner type LS - logical system?
    Thanks in advance.
    Mark Monroe

    Hi Mark,
    For your requirement you, create partner profile for LS with following steps :
    Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
    Message Type      : INVOIC
    Under Outbound Option u2013 Tab
    Receiver Port      : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
    Pack Size           : 1
    Transfer IDoc Immediately (Select)
    Basic Type           : INVOIC02
    Cancel Processing After Syntax Error (Select)
    Under Message Control - Tab
    Application           : V3
    Message Type      : RD00
    Process Code           : SD09
    Hope, your problem will get resolve.
    Regards..
    Imran

  • Idoc with message type

    i need an example how to use the message type in IDOC

    Hi Manohar,
    This is custom IDoc prgm.Award points if useful
    IDocs Standalone program
    This Prgm will upload data in flat file into internal table and sends that data to inbound system
    REPORT  ZMMMC9403_UPLOAD_MATERIAL_IDOC.
    *1.Create parameters/select-options for input data. i.e., empno, message type, logical system.
    parameters :    p_mestyp like edmsg-msgtyp default 'zmsgkk',
                          p_logsys like tbdlst-logsys obligatory.
    *2.Create Data objects for control record, data record and database table.
    data : c_segment like edidd-segnam value 'ZKSEGTYPE',        "Data record (IDoc)-Segment type
             c_idoctp like edidc-idoctp value 'ZKIDOC'.        "Control record (IDoc)-Basic type
    data : begin of itab occurs 0,
              zsno   like zkiran-zsno,
              zsname like zkiran-zsname,
           end of itab.
    data : w_itab like itab.
    data : s_segment like zksegtype.
    data : i_edidd like edidd occurs 0 with header line.
    data : i_control_record like edidc.
    data : i_comm_idoc like edidc occurs 0 with header line.
    *3.     Select the data from flatfile/corresponding tables into internal table for a defined condition.
    *select single zsno zsname from zemp into corresponding fields of it_zemp where empno = p_empno.
    call function 'GUI_UPLOAD'               "since the data is coming from flatfile, GUI_UPLOAD is used
      exporting
        filename                      = 'C:\DATA.TXT'
        FILETYPE                      = 'ASC'
        HAS_FIELD_SEPARATOR           = 'X'
      tables
        data_tab                      = itab.
    *4.     create control record into internal table.
    i_control_record-mestyp = p_mestyp.         "Message Type
    i_control_record-idoctp = c_idoctp.         "Basic type
    i_control_record-rcvprt = 'LS'.             "Partner Type of Receiver
    i_control_record-rcvprn = p_logsys.         "Partner Number of Recipient
    *5.     create data record into internal table.
    *i_edidd-segnam =   c_segment.
    loop at itab into w_itab.
    s_segment-zsno =    w_itab-zsno.                     "Application Data
    s_segment-zsname =    w_itab-zsname.
    i_edidd-sdata = s_segment.
    i_edidd-segnam = c_segment.
    append i_edidd.
    endloop.
    *6.     Process ALE Service Layer using the function module  MASTER_IDOC_DISTRIBUTE.  It returns the corresponding IDoc No.s.
    call function 'MASTER_IDOC_DISTRIBUTE'
      exporting
        master_idoc_control            = i_control_record
      tables
        communication_idoc_control     = i_comm_idoc
        master_idoc_data               = i_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.
    *7.     Display Communication IDocs.
    loop at i_comm_idoc.
      write : / 'Communication IDoc No. is : ', i_comm_idoc-docnum.
    endloop.
    *8.     Commit Work.
    commit work.

  • Storage location is not updated after posting GR with Mvt type 107(Valuated GR blocked stock)

    Hi experts,
    Before posting GR through Movement type 107 (valuated GR blocked stock) we can see the storage location field in MIGO screen and able to enter value into this field. But after posting GR when we retrieve the material document we are finding that the field (storage location) is blank, i.e. it's not updated at all. When we check the stock in MMBE we find that no quantity is updated for valuated GR blocked stock.
    We want the storage location to be updated while posting GR with 107 Mvt type.
    Any idea Please?
    Points assured.
    Thanks
    Amitava

    SAP describes it in help.sap.com: Since the material is not to be added to the inventory yet, do not enter a storage location.
    If you require a storage location, then I assume that your design does not match with the design of SAP, you are using a function to solve a gap which is not foreseen by SAP for this case.
    Especially the 107 is usually representing stock which is still in transfer but you are already the legal owner and have to show the value of those goods in your books.

  • Posting Idocs with different users

    Hi folks,
    I have a simple scenario, File -> PI (7.0) -> ECC (Idoc)
    I would like to know if there is a way to post the Idocs with different users, for example, in the source file a field contains the user that has to post the Idoc, so I'd like to map that user as the one that posted the Idoc.
    Is it possible?
    Thanks in advance!
    Juan

    Thanx Ivan, but you mean Outbound Idocs, or Inbound Idocs?
    Prateek, the issue here is that this is a part of a whole process where are involved many handhelds.
    With this handhelds, first there is an authentication of the users (via RFC) to see if that user has permission or not, and after that, if successful, when PI posts the data fetched from the handheld, they want to know the user that posted that info in ECC (IDOCS); supposing that it was the same user that did the validation before.
    regards,
                 Juan

  • Trigger WBS idoc with basic type PROJECT01 when ever saved

    Hi
    I have requirement where idoc has to trigger each time the field value is changing to replicate changes to master data through a new document. And also only WBS elements with Project Type = 'TS' (Time tracking level). I am new to Idocs. Please hlp me how to do this. I have to use PROJECT01 idoc type.
    Regards,
    Lohitha

    Hi,
    Please refer to the below thread. Hope it helps.
    Triggering workflow upon idoc fail
    Regards,
    Sridhar

  • Transfer posting printout with trasns type WA

    Hi
    Issue: printout for Transaferposting with trans type WA with MB1B for 301 mvmnt with error message "The system could not create any outputs".
    what i did was, i set the printer configuarion for inventory management output for transposting in SPRO. with customization table B517,B518,B519,B520 with diffrent options a srequested by business, for the able table i maintained a new access seequnce.i was able to take the printout sucesffully in DEV system.
    Business was accepeted to  move the changes to Quality system. when i transports into QUALITy, the transport was displayed woth error message as "Table TMC1, entry B517,B518,B519,B520 table missed,". due to this transport, in qualkity system dump occured when doing MIGO transcation.
    when we check the dump, it states that table B517,B518 tablel etccc.
    due to this i deleted the tables in an access seequence, i moved the transport to qulity system. now NO dumps are displaying when doing MIGO transcations.
    In this situtaion, how will i move changes to quality system??
    my action points:
    1. i cretaed a new tables B521,B522,B523,B524 with copy of B517,B518,B519,B520 and  move dto quality system.
    2. i cretaed a new access seequnce for tables B521,B522,B523,B524 (Note:Old access seequcne was deleted and B517,B518,B519,B520 tables were deleted) .
    3. when i check the scenario for MB1B with 301 movement in DEV system, out put is not triggring . why??
    message displayed as  "The system could not create any outputs"..
    Question to you:
    how should we correct my mistake??
    Regards,
    Pabbati Obulesu

    Hi,
       Please ensure that the condition record for the output types has been maintained in the Dev as well as QAS system in MN21 transaction. Maintain the same and test again.
    Regards,
    AKPT

Maybe you are looking for