What authorization required to post idoc from XI via RFC?

Hi all,
I need to post idoc to SAP R/3 system from XI. I have done all the steps correctly. While creating RFC in XI system to connect to the R/3 system, intially I gave my R/3 username and password and tested teh connection. Everything was working fine but when I actually ran the scenario, IDOC was not getting posted in the R/3. But there was no error anywhere.
fianlly after debugging I fould it might be the issue of authorization the the R/3 user i used in the RFC. I then assigned SAP_ALL authorization to my user and posted the iodc again and it started working fine.
Can anyone please tell me what are th exact authorizations/role i need to assign to the r/3 used to use it in RFC and successfully posting the idoc? I dont want to use SAP_ALL authorization in my production environemnt.
Please help.
Regards,
Yash

Hi,
Even i had faced this problem. Whenever I tried to send IDOCs, i used to get an error in SM58, " No authorization to send IDOC of type DEBMDM".
When i got SAP_ALL it worked. However I raised a note with SAP asking for an alternative and this is the reply gave me.
You can get good information on this topic in your online help files.
The following is taken from the document "General Security Measures
(ALE)":
Use the transaction SALE to maintain the ALE configuration, to include setting up the distribution model and setting up ALE user authorizations and profiles. Note the following:
- Be restrictive when assigning the ALE authorizations.
The authorization profile B_ALE_ALL contains the following
authorization objects that are needed for ALE:
Authorizations for ALE
Authorization Description
B_ALE_CGRP ALE Customizing Distribution: Group Activities
B_ALE_LSYS ALE/EDI: Maintaining logical systems
B_ALE_MAST ALE/EDI: Distributing master data
B_ALE_MODL ALE/EDI: Maintaining customer distribution model
B_ALE_RECV ALE/EDI: Receiving IDocs via RFC
B_ALE_REDU ALE/EDI: Generating messages (ex. reduction)
S_PROGRAM ABAP: Program run checks
S_TABU_DIS Table Maintenance (using standard tools such as SM30)
Protect external users and passwords.
For example, for a non-SAP system to send IDocs to a SAP System using transactional RFC, it must also send a SAP user ID and password.
In most cases, the user and password are stored outside of the SAP System. Make sure that this information is not accessible to external systems or programs. (How you can do this is dependent on the system that you have; therefore, you need to refer to the documentation for the system where the information is stored.)
However, I feel assigining the profile S_IDOC_ALL should also be enough. Just try and see.
Regards,
Merrilly

Similar Messages

Help Required to post IDOC from R/3 to XI

Hello,
I need help to post IDOC from R/3 to XI
My XI System --- E11 on client 001
My R/3 System -- IXS on client 812
In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 )
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS )
While Posting data from R/3
Recipient Port --- A00020
Recipient Partner No -- RECE
Recipient Partner Type --- LS
Sender Port --- SAPB6M
Sender Partner Number -- B6MTEST
Sender Partner Type --- LS
I am getting error " Could not post IDOC to R/3".
Please let me know where are my setting are incorrect
Regards

In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 ) ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS ) ( Not require in SAP XI)
chenage the PORT NAME IN R/3 it should work.

What authorization required to deploy module from NWDS 7.1

Hi Experts,
Need to deploy custom adapter module from NWDS 7.1 to PI server, Please help me to know exact access/authorization role required one developer to publish the module.
I have gone through many blogs and thread but not able to find exact administrator role which help to deploy the custom module on PI server.
Error I am getting in NWDS 7.1, while deploying module:
Could not establish connection to AS Java on [<server detail>]. Authentication did not succeed. Wrong or missing security credentials (password) for principal [PIUSER], or the specified principal has no permissions to perform JNDI related operations.
Regards
Raghav
Edited by: RaghavTiwari on Feb 4, 2012 8:25 AM

Hi Raghav,
Check this [SAP Help link|http://help.sap.com/saphelp_nw73ehp1/helpdata/en/43/1e1bbc5d9206fde10000000a422035/frameset.htm] for User Roles for Adapter and Module Development.
Regards,
Raghu_Vamsee.

Posting idocs from R/3 to xi

dear all,
i want to do one scenario of posting INVOIC idocs from R/3 to XI. I have gone thru some of the blogs posted in SDN but didn't find any step by step guide for doing it.
Can anybody send me the link or sme document for the above said scenario.
Warm regards,
N.Jain

Sent/Receive IDOC:
you need to do the following:
In XI
SM59 - R3 connection pointing to R3
IDX1 - define the port with the above dest.
In R3
SM59 - R3 connection pointing to XI
WE21 - define the port with the above dest.
WE20 - Partner profile type outbound/Inbound
Further ref:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
ALE configuration for pushing idocs from SAP to XI -
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
For a IDOC -> File, ref:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

While Posting IDOC from XI to R/3 Message Type needs to be changed

We are doing mapping IN XI. For one condition we want Message Type to be ORDERS and for one condition we want Message Type to be ORDERSCHG
when posting IDOC from XI to R/3.
Pls revert anybody asap.
Regards

Hi,
>>>>It means I need to create two Interface Mappings for the same message mapping and then I can use the Interface Determination . Am I right.
no, you need two message mapping
and two interface mappings
file - orders.orders05
file - ordrchg.order05
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

How to post idoc from r/3 to xi

hi experts i have one doubt abt posting idoc from r/3 to xi
how to post
for vendor master idoc
for sales order idoc
for purchase order idoc
for delivery idoc
is there any inbuilt posting prgms r there or we have to write the prms.
please clear me
regards
babu

to add more...
Befor posting IDOCS into XI..we need to do ALE SETTINGS...as fallows..
ALE settings.
SAP XI1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
and coming to the posting, u can go with WE19

JCO RFC Provider: "Bean not found" when calling EJB from ABAP via RFC

Hello,
I'm having trouble calling an EJB in a CE 7.1 system from ABAP via RFC. I'm trying to use the JCO RFC Provider service, which mean that I want to expose an EJB so that it can be called via Remote Function Call.
I have documented everything, including the code and the deployment descriptors I wrote, in this thread in the CE forum: Jco RFC Provider: Bean not found
If there's any chance you can help, please do me a favour and look into the problem.
Thanks a lot!
Thorsten

Hi Vladimir,
Thank you very much, your help was immensely valuable.
I just had to add the function declaration to the Home Component interface, everything else was correct, and now it works.
Cheers,
Thorsten

Authorization error in posting IDoc

Hi,
I have completed configuration of File to IDoc scenario. When File adapter has picked up the file from FTP server, the message is processed with outbound error.
To find out the error occured at the outbound side, I ran the transaction 'SM58' which explained that XIAFUSER does not have authorizations to post the IDoc to destination system. Can somebody provide what authorizations should be given to this user to facilitate the processing of message.
In another instance the same error has resulted but notifying the different user. This time WF-BATCH does not have authorizations to post the IDoc to destination system.
As per my understanding there should be some system configuration where you have an option of specifying the user for posting IDocs to destination system.
Please confirm whether my understanding is correct and also let me know the where it is done?
Regards,
Suraj

Hi Suraj,
The user id which you are using in your RFC destination will be of your target system to login. This user id should be having all SAP_ALL authorizations attached into their profile.
Pls do try with the help of your basis by assigning this profile to your WF-BATCH user.
Cheers
JK

"An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX

Hi all,
While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58
Only a particular Idoc type is having this issue.
Below are the checks done before posting this query:
1. Pushed other Idocs from the SAP ECC to PI and all were getting exchanged successfully.
2. Reloaded the meta data in PI for the particular Idoc type in issue.
3. Checked the RFC destinations in SAP ECC, RFC connection test is also working fine.
4. Unicode option enabled in the SAP ECC RFC destination pointing to PI-AEX
5. Restarted the inboundRA service in PI AEX.
Is there anything still missing. What could be root cause of this issue.
If anyone has encountered it before, pleases share the resolution.
Thank you
Younus

Hi Amit,
Thanks for the reply. Log viewer doesn't provide much help on the error.
The error desc says
"JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_58, connectionId=5-ip address|sapgw20|XI_IDOC_DEFAULT_SID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: An IDocException occurred"
regards,
Younus

How to post Idocs FROM BW to R/3?

Hi,
what I need to do is:
1. read a cube.
2. create an Idoc from the record I read.
3. post the idoc back to R/3.
Do you know how can I send the Idoc directly to R/3 FROM BW?
Thanks,
Itay

Hi Andrzej,
I created the following fm in R/3 to be called from BW:
FUNCTION z_read_table.
""local Interface:
*" IMPORTING
*" VALUE(IP_TABNAME) TYPE TABNAME
*" EXPORTING
*" VALUE(EP_TAB) TYPE ZBP0_TAB
DATA: it_table TYPE REF TO data,
 l_line TYPE zbp0_struc.
FIELD-SYMBOLS: <it_tab> TYPE STANDARD TABLE,
 <ls_tab> TYPE ANY.
create internal table
CREATE DATA it_table
 TYPE STANDARD TABLE OF (ip_tabname).
ASSIGN it_table->* TO <it_tab>.
read data
SELECT * INTO TABLE <it_tab> FROM (ip_tabname).
assign data
LOOP AT <it_tab> ASSIGNING <ls_tab>.
 CALL FUNCTION 'SO_STRUCT_TO_CHAR'
 EXPORTING
 ip_struct = <ls_tab>
 IMPORTING
 ep_string = l_line.
 APPEND l_line TO ep_tab.
ENDLOOP.
ENDFUNCTION.
In BW I am calling it with
CALL FUNCTION Z_READ_TABLE destination 'DEST'
IMPORTING ip_tabname = 'ZTABLE'
EXPORTING ep_tab = itab.
Hope this helps!
regards
Siggi

Posting IDOC from MQ

Hi,
I have a scenario in which I have to Post an IDOC from MQ (MQ to IDOC scenario).
I am getting an error in the communication channel :
Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: java.lang.Exception: ERROR converting document line no. 1 according to structure Header:java.lang.Exception: Consistency error: field(s) missing - specify lastFieldsOptional parameter to allow this; nested exception caused by: java.lang.Exception: ERROR converting document line no. 1 according to structure Header:java.lang.Exception: Consistency error: field(s) missing - specify lastFieldsOptional parameter to allow this
What is the solution to this problem?
Thanks,
Vikas

It seems you are using Content conversion on Sender JMS adapter side.
Some fields must be missing in your Source file.
You need to specify the lastFieldsOptional parameter in Content Conversion.

Posting IDOCs from Proxies.

I would like to know if there is a way to post an SAP inbound IDOC from a proxy?
have any of you worked on such scenarios? If so what are the steps involved?
Thank You
Arvind R

Hi Arvind,
I am not sure why do you want to do that but if you are able to generate IDOC headers using the data in the proxy, yes, then you can send/post an IDOC using proxy.
Award if helpful,
Sarath.

Problems with posting iDocs from MDM in SAP R3

Hi,
I am an MDM consultant, with limited knowledge about SAP R3.
We send material master data from MDM, via PI to R3 using iDocs.
We are having problems with posting MATMAS, and it seems the problems are with updating already existing materials.
In BD87 we get the following warnings:
The field MARA-ERVOE is not ready for input and was therefore not initialized
The field MARA-ERVOL is not ready for input and was therefore not initialized
The field MARA-FERTH is not ready for input and was therefore not initialized
The field MARA-KZGVH is not ready for input and was therefore not initialized
The field MARA-XCHPF is not ready for input and was therefore not initialized
With the last message being:
No changes made
I have checked the MDM syndicator, and none of these idoc-fields are linked to the MDM repository.
So they are syndicated blank.
If we try to resend the material, it is again stopped and in BD87 I see the same messages.
Please help me understanding how to solve these issues.
Thanks,
Thomas

Hi,
Please refer the below threads which talks about the similar problem
http://scn.sap.com/thread/3180116
http://scn.sap.com/thread/1374222
Generally the basic view of the material to be created first. Then the sales, purchasing and other views to be created.
There are few fields in the other views which gets values from the basic data view.
Regards,
Antony

Post Idoc from SAP to Thirdparty using XI

Dear Friends,
My requirement is sending the Idoc from SAP to Thirdparty system,but Thirdparty system also receive the Idoc format only.
so IDoc to Idoc scenario but SAP to Thirdparty system it is possible or not.
please tell me how ?
Regards,
Shalini Shah

You can use SAP Business Connector(BC) to convert IDOC to IDOC-XML at the third party legacy system.
With Business Connector see the below links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://www.erpgenie.com/mysap/bus_connector.htm
WAS - Business Connector
business connector documentation
SAP Business Connector
Business connector
Will Business Connector 4.6 be affected by new Daylight savings changes
Business connector
More info on XI can be found at https://service.sap.com/xi
and webAS on http://help.sap.com/saphelp_nw04/helpdata/en/f3/e20f3adfd0a706e10000000a114084/frameset.htm
Check this also-
http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/1bd5c2a85b11d6b28500508b5d5211/frameset.htm

Error when posting Idocs From XI to SAP by Partner Profile

Hi all.
i have a problem. all my inbound IDocs in R3 use PP(Partner Profile) LS_XID.
but i need to send IDoc MATMAS by a diferent PP (LS_MATERIALS).
So, i added a new BS in transaction BD54.
In transaction BD64 re-desing the Distribution Model as follow
SL_130 (R3 DES)
> LS_MATERIALS (XI)
|> MATMAS.
In transaction WE20 define the new PP LS_MATERIAL. In inbound table add the MATMAS IDoc. Later imust delete de MATMAS IDoc from LS_XID list. same as transaction BD64.
My problem is when send the MATMAS to R3. it is still using PP SL_XID, so IDoc get status 56 (EDI: Partner Profile Inbound not Available) in R3.
Why?? Any IDea??
Thanks & Regards
Rodrigo.

Hi,
Please check the Logical system,Business system, configurations ,please see the below links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
Regards
Chilla..

What authorization required to post idoc from XI via RFC?

Similar Messages

Maybe you are looking for