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

Similar Messages

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

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

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

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....

Error monitoring through workflow for idoc with message type ORDRSP

Hi All,
Through WE19 I am trying to post a failed idoc ie idoc in 51 status for message type ORDRSP to check whether the event IDOCORDRSP-INPUTERROROCCURED event is triggering or not. Though the idoc is going into 51 status and partner profile is maintained I cannot find this event in SWEL. I checked in fm IDOC_INPUT_ORDRSP fm and found that workflow_result is 99999.
Can anybody tell me why the event is not getting triggered for the message type ORDRSP or where do I debug to find out what is going wrong. IDOC_INPUT_ORDRSP fm is getting called from BUS2012 'S method confirmfromORDRSP which is very strange.So I am not getting where do I debug.
Regards
Suchandra

Hi All,
Solved it by my self.. To trigger the event we need to populate the EDIDC control record in WE19 and press standard inbound button 'not test by inbound fm) and then the inputerroroccured event will trigger...
Regards
Suchandra

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

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.

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

Error when executing the program RBDMIDOC with Message type HRMD_ABA

Hello All
I finished the integration between CRM and HR
Now I am able to replicate the employees and the organizations, but when I created a schedule job for the program RBDMIDOC and message type HRMD_ABA the system gives me warning and message: no data selected for distribution even if I try to run the program using SE38 I am getting the same error message
I already activated the message type using BD50 and activated the Change pointers using BD61
Regards
Jacopo Fransoice

us the program
RHALEINI

User has no authorization to send IDOCS of type

Hi Gurus,
I am sending an IDOC of type OILDEB02 from XI to R/3. I have done the configuration (we20, we21 etc). The message is processing successfully and not reaching the R/3.
When I checked in IDX5, after cclicking the 'transaction id', i see this message.
Caller: XIAFUSER
No authorization to send IDOCS of type OILDEB02.
Do we need to create the XI service users in the R/3 system?
I wanted to know what is missed in this configuration?
Thanks
Kalyan

Bhavesh,
I am using File to IDOC interface.
I have checked all the items you mentioned. Everything is working as expected.
<i>1. The rfc destination and port in the IDOC adapter are the valid ones you have created for the R3 system in Sm59 and IDX1 respectively
***THESE ARE VALID
2. Go to IDX2 and try to manually import the Idoc metadata. See if this is successful.
MANUAL IMPORT IS SUCCESSFUL
3. In the RC destination in Sm59, try a test connection and remote log on.
TEST CONNECTION AND REMOTE LOG ON WERE SUCCESSFUL.
4. Finally check if the user id has the roles mentioned in my porevious reply and if yes, things should work.
I didn't check this on. But there was no error regarding my user id.
</i>
After I run the interface, XI is showing the processing successful and the IDOC is not received at R/3.
When I checked in IDX5 in XI, after clicking the transaction id, the message is saying that -
Caller XIAFUSER
Function module: IDOC_INBOUND_ASYNCHRONOUS
Target system: R/3 SYSTEM RFC destination I have created in XI
Status text: No authorization to send IDocs with message type OILDEB
Any thoughts??
Thanks
Kalyan

Error during proxy processing An exception with the type CX_BBPX1_STD_MESSA

Hello,everyone!
My PI version is 7.11,SRM SUS version is 7.0,ECC version is 6.0 ,When I import XI SRM CONTEN,sending IDOC in ECC,there is a error some of the mesages:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX1_SUSPO_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Detialed error from SXMB_MONI,
Error in XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 0015111411 with type 'Vendor' I:R5:553 -'Different country' field contents deleted because identical to 'Country' E:BS:002 -"Create" is not allowed (SUS Purchase Order 7100076527 ) Program: CX_BBP_BD_ERROR===============CP; include: CX_BBP_BD_ERROR===============CM002; Line:
This issue only ocuured for partner 0015111411, but we tried with other partner ID and those messages are processed sucessfully and PO is created.
I have a doubt that, is there functionality in proxy to compare the country with partner in SRM system. Could please anyone help me one the same.
Regards,
Baskaran K

HI,
This is a standard proxy. I'm not sure how to debug the proxy with payload. Could you please tell me the steps.
We have one more error message
<FAULT_TEXT>Error in XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner XY91 with type 'Sold-to Party' E:BS:002 -"Create" is not allowed (SUS Purchase Order 7100076526 ) Program: CX_BBP_BD_ERROR===============CP; include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
Is there any table to check these details like Sold-to Part, Vendor etc in SRM system?
Regards,
Baskaran K

No authorization for this transaction with mvt type 101

Has anyone seen this error:
RFC BAPI Wrapper call:You have no authorization for this transaction inplant 1120
RFC BAPI Wrapper call:You have no authorization for this transaction with mvt. type 101
RFC BAPI Wrapper call:You have no authorization for this transaction inplant 1120
The strange thing is that when I assign user with a different Personnel Number and it works just fine. But when I switched back to his Personnel Number, then I get above error.
Even though I don't get any order list but I got all notifications and technical objects.
Also, this user has same roles with everyone else. While everyone is working fine this user is the only one that getting the error and no order download to PDA.
Regards,
Dai Ly

Hi,
please run ther getlist and getdetail handler in the backend directly for that user - most likely you will get a better failure message there.
Nevertheless - what Application yre you using? Is it MAM? If yes, check the SPRO setup for this particular user,
Regards,
Oliver

No authorization for this transaction with movement type 601

Dear All,
This is chandra i am getting this error in delivery level " No authorization for this transaction with movement type 601. If give the authorization for SAP ALL its working fine. If give the authorization for SAP SD T.Codes i am getting this error. Plz help me.
Thanks and regards
Chandra

Dear Chandra,
Check with -
T. Code: OMJJ
Select Movement Type: 601 and Double-Click: "Allowed Transaction" (From Left-hand side) .
Check whether the Transaction is allowed for Movement Type 601 or not
Note: if Transaction is not listed (i.e. not allowed) and you wanna allow this Transaction with Movement type 601, then -
Up-there, Tab: New Entry. Click on it.
Maintain entry as:
MovTy: 601
TCode: As reqd.
and Save.
Best Regards,
Amit

Outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON

Hi Friends
I am trying to pack outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON.
But IDOC has error Specification of destination HU missing.
Could you please help us to resolve the issue to Pack the outbound delivery with the IDOC.
Thanks
SR

HI Ian Kehoe
Sorry for delay in reply
Thanks you very much
I solved that problem .
Could you please advice test data for IDOC DELVRY06 packing hierarchy (multi level packing) to pack SAP outbound delivery.
Thanks
Ravi

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

Similar Messages

Maybe you are looking for