Authorization for RFCUSER for IDOC adapter

Hello,
who can tell me, which authorizations the RFC User must have I want to use for the IDOC adapter.
I have the problem, that I can not download the idoc definition into IDX2. Error: "No RFC authorisation..."
Is there a list of authorization this user MUST have.
best regards
Werner Magerl

Hi,
The thread speaks of the same issue.
User abcd has no RFC authorization for function group SYST
If it's of any help.
regards
Vijaya

Similar Messages

SA PI 7.1 EHP1 - Support for IDOC Adapter using AAE

Hi,
Can anyone confirm if the SAP PI 7.1 EHP1 supports the IDOC adapter in the AAE ?
Cheers
Colin.

Hi Colin,
I am workinngt on EHP1 PI7.1,but no support for IDoc Adapter in the AAE.
The new features added for IDoc adapter is IDoc packging and new conversion module added .
we have to wait till next release,but not sure...
Regards,
raj

QoS for IDOC adapter

Hi all ,
what are the QOS available for idoc adapter
Regards,
Tarang

Hi,
Check on this:
<i>The quality of service EOIO (Exactly Once In Order) must be specified in the message header.
The receiver system or the sender system must be based on SAP Web Application Server 6.40 or higher.
If this is not the case, the quality of service is automatically changed to EO for compatibility reasons and the message is processed accordingly.</i>
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
Regards
Vijaya

Empty payload for idoc adapter

Hello,
I have a file to idoc scenario with an xslt mapping. Normaly after the mapping the idoc looks like:
<wpwuw>-
<idoc>...</idoc>
<idoc>...</idoc>
</wpwuw>
Because of the business requirements in some cases the mapping should not generate an idoc. That means I have to create an empty payload.
The problem is that the idoc adapter creates an error for all kinds of empty messages.
a) empty payload
b) empty trading segment ( <wpwuw></wpwuw> )
c) empty idoc segment ( <wpwuw>-<idoc/>-</wpwuw> )
Any idea what I can do not to get an error from the idoc adapter ?
Regards Bernd

HI
instead of creating empty paylaod. Use conditional(enhanced for mapping & standard for condition on Xpath) receiver determination for this and dont generate IDOC for the specified conditions.
Thanks
Gaurav

Error when Loading Metadata for IDOC Adapter

Everybody,
I know this should be pretty straight forward and that there are a few posts about it. But following the Demo 3.0 guide and the posts I can't seem to load the data into the IDOC Adapter. I did every step in the guide and when I try to execute IDX2 for the source port I previously created I get the error "No RFC Destination is maintained for the port".
Following the guide I have my XI host
ID:ABC
Instance:01
Client:700
Executed IDX1 and got port SAPABC_107 with RFC Dest-ABC_107, which I defined previously with transaction sm59 and the test came back ok.
When I try to execute IDX2 I get the error message...
What am I missing ?????
Thanks!
Diego

Everything was setup before (by following the XI 3.0 Demo guide) here are the steps I did:
1. Setup an RFC R/3 Destination on my client 107 (American Airlines) to client 700 (my XI): ABC_700
2. Setup an RFC R/3 Destination on my client 700 to client 107: ABC_107
3. Setup the IDOC processing port "SAPABC" on client 107 with RFC Destination ABC_700.
4. Define partner type LS for logical system ABCCLNT105 (Airline Lufthansa)
5. Define partner type LS for logical system ABCCLNT700 (XI)
6. Specified the ALE distribution model in client 107.
7. Execute IDX1, I input the SAPABC port created in step 3, input the client number 107 and the RFC destination ABC_107 created in step 2 and save. The result is port SAPABC_107.
AND..!! where the error occurs:
8. Execute IDX2 input port SAPABC_107 and idoc type and get the error message "No RFC Destination is maintain for SAPABC_107"
Any ideas !?
Thanks
D
The client 107 represents the Airline American Airlines and has a R/3 RFC Destination to client 700, my XI. The same way my XI has an R/3 RFC Destination to client 107.

Port Settings for IDoc Adapter

Hi All,
Our scenario is like this ERP -> XI -> File. ERP sends IDoc to XI. I have a couple of questions.
1. In the control part of an IDoc, there's a sender partner number and sender port. What are they used for? As I understand, the partner and port represent the destination of the IDoc instead of the source. Why is there sender port and partner?
2. We need to maintain port using IDX1. Should I set the name of the port to be the same as the sender port of the IDoc?
3. I didn't configure the scenario and the IDoc sender adapter. If the ERP system sends IDoc to XI, can I find it in t-code IDX5?
Best Regards
Jerome

Hi Jerome,
1. Sender Partner and Port : The control record should have sender port and partner number. This will be used by the receiver system (i.e., XI system). Because, receiver system should know from which system this IDoc is coming using Sender Partner number. This partner number should be same as Logical system name in Sender Business system which is configured in SLD.
The sender port should be SAP<Sys-id of sender system>
and sender partner number should be <sys-id of sender>CLNT<client number of sender>
2. The port created in IDX1 will be used for importing IDoc's metadata in XI system from R/3. IDoc metadata is needed by IDoc adapter to convert incoming IDoc to IDoc-XML format.
It is mandatory to have same name for Port in IDX1 and sender port of the IDoc's control record.
3. I think the IDoc wont be listed in IDX5 if scenario and IDoc adapter are not configured. IDX5 displays inbound and outbound IDocs in the IDoc adapter.
Regards,
Uma

Required Enhancement Package for Idoc Adapter in Java

Hi experts,
I just would like to know which Enhancement Package I need for PI 7.1 when I want to have the Idoc adapter to be implemented in Java and not only in ABAP.
Thanks and regards.
Oliver Vöpel.

I talked to someone from the SAP development. They told me it will be realized in enhancement package 2 or 3.
Thanks and best regards.
Oliver Vöpel.

Meta data Overview for Idoc Adapter

Hi All,
When i am trying to create meta data overivew for Idoc adpater of my source port, i am gettign this error "<b>Error: I::000</b>" and surprising abt this error.Any clues on this.........:) what should i do to do this??
Thanks in Advance
Cheers
Veera

Hi All,
Once i have cross check RFC destination & Port and tried to load the meta data it was succesfully loded with out ant errors.The same port i have mention in Receivr Idoc adapter and tested the sceanrio File2Idoc.It is working fine.
I have solved the problem my own ( And the tricky thing is i have deleted and recreated RFC dest,Port from XI to R3).However what is the cause of this error??
Cheers
Veera

Sender Radio Button disabled for Idoc adapter

If u clearly observe .......
Whats the necessity or significance of not having a sender communication channel(sender side radio button is disabled) and sender agreement in scenarios pertaining to Idocs....

Hi Deepika,
Just think that IDOC adapter as a sender, that means, you are getting source file (IDOC) from R/3 (SAP) system definitely. And XI is also and SAP system. As both are SAP systems, we already have a way of establishing the connection between SAP systems, which is ALE configuration. Using which, you can easily transfer IDOC from R/3 to XI.
Also, you might know that IDOC and HTTP adapters reside on ABAP stack. When the R/3 and XI configuration settings are done, XI can receive the IDOC sent by R/3, directly to Integration Engine instead of Adapter Engine. If the file initially reaches to Adapter Engine, then the details about sender application are necessary, that means the Sender Agreement. But in this case, you don't even need the Sender Agreement.
I hope you understand why the IDOC sender button is disabled and sender agreement is not necessary.
Thank you.
Regards
Bhanu
Intelligroup.

Security Authorizations for IDOC

can anybody explai me following.
Roles and responsibility wrt the Security Authorizations the user should have to process the IDOCs at the receiving end and also the monitoring the IDOCs
Regards,
Rahul

Hi Shesha,
I presume you have the SAP Integration kit intalled and configured, and imported the BW roles in the CMC... you are also login with the SAP user account (User1, User2). This would be a base requirement to make this work.
In your OLAP universe, you need to set the connection properties of the connection to. Select Use Single Sign On when refreshing reports at view time to allow the user to benefit from SAP SSO.
You have currently used User1 for the connection and saved the universe with this user id, thus, when the connection is made to BW, it is User1 with its role permissions accessing the data, even if you are logged on as User2, User1 is being authenticated.
Hope this helps
Jacques

Adapter Module for receiver IDOC adapter?

Hi,
I have a scenario where i need to do some custom logging in the receiver adapters. For all receiver file adapters, i have written an adapter module which fulfills this custom requirement but how will i do this in the receiver IDOC adapter as its on the ABAP stack? I cannot write a java adapter module for this.
Is there anyway by which i can write a ABAP adapter mosule and deploy it in the IDOC adapter? Or any other way to achive it. the scenario is such that i need to do the logging before the idoc is posted into R/3 system by the idoc adapter.
Please advice.
Regards,
Yash

Hi Chirag,
Yes i have seen that the module tab is disabled for idoc adapter. I have a fin interface where i need to split a incoming file into an idoc and a file. For this purpose i need to log how many records are received by each adapter and the sum of the line items for audit perspose.
any othr way to do it apart from doing it in message mapping. The req is to do in the adapter engine.

Sender IDOC adapter for SAP 3.1H system & XI 7.0

We are on XI 7.0 and XI would receive a IDOC message from SAP 3.1H system.
I need to import IDOC's in imported objects in integration repository but I cannot see any IDOC under the IDOC node. I am able to see the RFC's. Do we need to do extra steps with SAP 3.1H version for IDOC adapter?
Thanks in advance for help!
Mrudula

Ahmad,
This thread is for sender RFC adapter. I am able to see the all the RFC's but not IDOC's from Integration repository for imported objects from SAP 3.1H version.
Thanks!
Mrudula

Load metadata for idoc

hi,
how to load metadata for idoc..
I hope IDX2 is for to check whether metadata is loaded or not..
thanks
guna

Hi,
use :
IDoc (Intermediate Document) metadata comprises structures for the corresponding IDoc types that are required by the IDoc adapter to convert these IDocs to IDoc XML format and the other way around.
Using an RFC connection, metadata of this type can be either called directly at runtime or loaded to the Integration Server beforehand.
The system containing the metadata is either the sender or receiver SAP system or, if the sender or receiver system is a subsystem, the SAP reference system where the metadata is saved.
You can display metadata that has already been loaded, or if you are upgrading the application system then you can delete the metadata and reload it.
Prerequisites
To access the metadata in the sender system, you must establish an RFC connection to this system using the port maintenance in the IDoc adapter.
Procedure
       1.      To find out what metadata has already been loaded, call the transaction Metadata Overview for IDoc Adapter (IDX2).
The system displays a screen with the directory of all systems connected with the IDoc adapter (including a description) for which metadata has already been loaded. Choose Port Maintenance in IDoc Adapter () to call the corresponding transaction and to create additional ports.
       2.      Expand the individual systems to display the IDoc types and clients including a description for each system. The system displays the metadata for each connected system for which metadata has already been loaded.
       3.      To apply the metadata structure loaded from a particular system to another system (for example, to an SAP reference system), select the link to the corresponding IDoc type and choose Copy ().
The system displays a dialog box in which you can copy the IDoc type description to another system (Target Port).
       4.      To delete metadata that has already been loaded, select the link to the corresponding IDoc type and choose Delete ().
The system asks you if you really want to delete the selected structure.
       5.      To delete the metadata structure, choose Yes.
       6.      To load additional metadata, choose Create ().
The system displays a dialog box where you can enter the IDoc Type including Extension and the system (Source Port).
       7.      Make the required entries and choose Continue.
The new structure is inserted in the tree structure as follows:
¡        If the structure originates from a system from which metadata has already been loaded, it is inserted below the structures already loaded from this system.
¡        If the structure originates from a system from which no metadata has already been loaded, it is inserted together with the system below the already listed systems.
       8.      To display details about a metadata structure that has already been loaded, choose the link to the corresponding IDoc type. To display this structure in detail, choose Display (). The system displays the structure in a hierarchy tree.
       9.      To display the corresponding system (port) and the basic type from the detailed display, choose Header Information ().
   10.      To display the segment versions of all segment types in the structure, choose All Segment Versions ().
   11.      Select a segment to display all its fields.
and also refer these article
http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
http://publib.boulder.ibm.com/infocenter/wtxdoc/v8r2m0/index.jsp?topic=/com.ibm.websphere.dtx.packsapxi.doc/tasks/t_pack_sapxi_Set_up_the_SAP_XI_System.htm
Regards,
Suryanarayana

IDoc Adapter - ATTRIBUTE_BE_NOT_SUPP Async processing

Hello,
I'm trying to establish IDoc communication. Here is the scenario that I need:
<XML Data> --- <SOAP> --> PI Server ( Map XML to IDoc XML) --- <IDoc> --> SAP Retail System
I have the following components set up:
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
2. Sender Agreement
3. Map from InXML to OutIDoc. OutIDoc - Message Interface - Inbound Asynchronous
4. Receiver Determination
5. Interface Determination
6. Receiver Agreement
7. Receiver IDoc Communication Channel
8. Business Service for all this
No Integration Scenario.
If I replace item 7 to the FTP for example, everything works just perfect - I send XML it gets Mapped to IDoc and in my FTP I have the IDoc file.
Now, I've asked SAP support specialist to establish communication from PI Server to Retail using IDoc. He send me parameters, which I used for IDoc Communication Channel:
RFC Destination: NX7CLNT800
Port: A000000022
SAP Release: 3 - this is I put myself
But when I run the whole system again, I'm getting the error:
IDOC_ADAPTER ATTRIBUTE_BE_NOT_SUPP - "Only asynchronous processing supported for IDoc adapter outbound processg"
This is very confusing because both my message interfaces are Asynchronous.
Can anyone tell me what I'm doing wrong and why I'm getting this error.
Thanks.

8. Business Service for all this
Should it not be Business System for IDOC.....for SOAP it will be Business Service
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
Check what is the QoS that is specified in the SOAP Channel.....if it is Best Effort then it will be a cause of the error......change it to Exactly Once (EO).
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 4, 2009 10:29 AM

ABAP Proxy or IDOC Adapter?

Hi all,
In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
1. Oracle ->PI ->SAP R/3
Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
2.VAN->PI->SAP R/3
VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver shall i go for IDOC Adpter or ABAP proxy?
3.SAP->PI->VAN
Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
Please suggest me which one is better in all the scenarios.
How to decide which is better for the above scenarios?
Thanks In advance
Venkatesh

>
venkatesh bs wrote:
> Hi all,
>
> In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
>
> 1. Oracle ->PI ->SAP R/3
> Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
>
> 2.VAN->PI->SAP R/3
>
> VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver shall i go for IDOC Adpter or ABAP proxy?
>
> 3.SAP->PI->VAN
> Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
> Please suggest me which one is better in all the scenarios.
> How to decide which is better for the above scenarios?
>
> Thanks In advance
>
> Venkatesh
Material Master - MATMAS
Invoice - INVOIC01
PO - ORDERS
wouldnt the above IDoc suit you?

Authorization for RFCUSER for IDOC adapter

Similar Messages

Maybe you are looking for