Regarding IDX2

Hii,
We Import the Required Idoc into the Integration Repository and we get the Idoc Structure. Then What is the need to specify the IDOC in IDX2.
Regards,
Varun

Hi,
This step (loading IDOC metadata in IDX2) is optional. When you start to send/receive your first IDOCS then XI will automatically load the metadata from the system.
So in fact you only have to make sure that the IDOC port you have defined in TRX IDX1 works propoerky and that your IDOC exists in the R/3 system.
In your IDX1 you pass the RFC Destination to connect to R/3, check the authorization for the user in that RFC destination. You can check for the authorization in SU01 of the R/3 box. In profiles tab check for the rights of the user, the user must not be having the relevant rights.
load metadata of IDoc using /nidx2
go thru these links...
http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/0e/d8fa40badbf56fe10000000a1550b0/content.htm
Also have look at this thread...
Re: IDoc meta data load problem in IDX2
Hope it helps
Surya

Similar Messages

Regarding IDX1,IDX2 and WE20

Hi Masters,
while doing file to idoc scenerio i have little bit of confusion ..
1) In idx1 we have to create a idoc port.. in case of port tab wht we have to give .. either we have to give logical system name of xi server or any other .. name ..
2) In idx2 we have to load the metadata .. here also we have to give source port .. so here also we have to give logical system name of xi server or any other name ..
3) In case of maintaining partner profile .. we have to give partner number.. so here also we have to give logical system name of xi server or other name ... this we have to do in r3 system ..
please help for doing this process ... if possible can u provide a step by step process for maintaining idx1,idx2 and we20...
Thanks in Advance,
jagannath.

Hi,
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
Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
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.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

With out using IDX2.....in file to idoc scenario

Hi Masters,
                   i have one doubt .. Can i send normal file from sender system to sap system in the form of idoc.. with out using IDX2...
if it is possible then plz explain me about the steps .. and also explain me wht is the actual use of IDX2 .. as wel as IDX1,,
if u say in IDX2 we have to load the metadata of the idoc .. then we already uploaded the structure of the idoc in XI system ... then why we are using again IDX2 to load the metadata. i have full confusion now .. plz explain me in details ..
          hoping for quick response ..
               Thanks in advance ,
                   jp.

Hi,
You can send an idoc to SAP system through XI without using IDX2. When u send an Idoc through XI, the metadata will be automatically loaded in Idx2.
IDX1 is used for creating a port in XI for Idoc. This port will be responsible for loading the metadata.
Also have a look at this:
Importance of IDX1
Regards,
Divija.

Regarding RFC connection in File to IDOC Scenario

Hi everyone,
I was configuring file to Idoc Scenario, i have made all the required configurations in SLD, IR and ID, in XI system and in R/3 System. i have created RFC connection from XI to R/3 system, and its working fine. i have created an Partner profile in WE20 with sender file system name with inbound parameters. But still i am getting error as EDI Partner Profile not defined in WE05- iDOC ADDED WITH ERRORS. Do we need to create an RFC connection from R/3 system to XI for file to Idoc Scenario
!!! Note: RFC connection from R/3 system to XI is not working, will this be a problem for file to idoc scenario. !!!
Regards,
Varun Reddy.K

Hi Varun
Follow these steps
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Regards,
Santosh

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

Regarding IDOC in XI

Dear All,
For scenario:
System A (RFC adapter) --> XI --> System B (IDOC adapter).
How should i configure for the partner profile?
1. In System A --> Logical System to System B, and put my message type as outbound.
2. In System B --> Logical System to System A, and put my message type as inbound.
3. or i need to configure in XI partner profile? Logical system A (outbound) and Logical system B (inbound).
Please clear my doubts.
Thanks,
Victor.

Hey,
   For RFC you do not need to make any entries in partner profile.
For IDOC(i.e) in system B create a partner profile as inbound.
Please refer to these steps if any issues.
teps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
regards,
     Milan

How to get rid of maintaining transaction IDX2

Hy everybody,
is there a way to get rid of maintaining transaction IDX2, when an IDoc structure changes?
Thanks a lot,
Thomas

I have done some investigations and found the part in the idx2 where the structure is deleted...
      delete from idxsload where port    eq i_idxsload-port
                           and   idoctyp eq i_idxsload-idoctyp
                           and   cimtyp eq i_idxsload-cimtyp.
      delete from idxidocsyn where port    eq i_idxsload-port
                             and   idoctyp eq i_idxsload-idoctyp
                             and   cimtyp eq i_idxsload-cimtyp.
Do you think it is crazy to write a program which uses this lines of code?
Regards,
Thomas

Need information regarding IDOC to JDBC Scenarios.

Hi,
Kindly help me with the pre-requisites inorder to start with a scenario of IDOC to JDBC and also the scenario of JDBC to IDOC.
Regards,
Sreedhar, Av

Hello Sreedhar,
While we working in JDBC or JMS Adapters we should deploy the Drivers..
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
To install JDBC driver follow the how to guide.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
Configuration of JDBC Adapter for SQL Server
JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
UserID and Password.
If the connection is not working find the correct port number.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
JDBC- X I - R/3 Scenario
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
2) While we working in IDOC Adapters we should do ALE Config of IDOC Settings .
Do these configurations in R/3 and in XI...
SAP XI
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 (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.
Here in IDOC to JDBC interface we need not to config sender Adapter..
1) The main usage of a sender adapter is to convert the input format into the XI supported XML format.
Once the conversion is completed the sender agreement appends the header with the sender details.
In case of these adapters we wont require sender agreement and sender communicationchannel for the
following reasons.
Sender agreement is associated with a namespace when we shoot an idoc frm r/3 if already contains its standard sap namespace. so those is need of sender agreement
The sender communication channel use is to identify the sending system and adapter, as the idoc header contains the details there is no need to sender.
These adapters resides on ABAP stack here the integration server takes care of IDOC/HTTP to XML conversion without requirement of adapter.
The business system that is sending the adapter has already been assigned to a techinical system which normally acts as an integration server...
IDOC to xi links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Hope this explanation is useful to u..
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on Jun 3, 2008 9:57 AM

Regarding partner profile

HI all
i am configuring an outbound partner profile for an outbound IDOC ,when i try to give the post processing:permitted agent,here i am getting this message NO ACTIVE PLAN VERSION EXISTS.
CAN ANYBODY HELP ME ON THIS
regards
kish

Hi,
Go trough this
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
 The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
 The Client must be the client number of the backend SAP system.
 Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
 Double-click on the business system in the Integration Directory.
 Switch to Edit mode.
 Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
 The RFC Destination is from step 3.1.
 The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
award points if find helpful

Problem while loading metadata in IDX2

Hi
I tried to load metadata in IDX2 .I passed the parameters IDOC TYPE and SOURCE PORT .when i asked to continue it is showing me the that " No RFC destination is maintained for the port ".
When I checked that particular port in IDX1 I am able to see that correct RFC destination is assigned to that port .
Please help me in this case.
With Regards
C Sivakumar.

hi.....siva
execute tcode SM59 and check the logical systems & their login details are correct not.
select REMOTE LOGON button.if ur details are correct then it displays that perticular screen.similarly u can test the reciever also.first u have to test the RFC Destination like this.Try it.
regards,
Naresh.K

IDX2 IDoc Metadata issue

Hello,
We have created an IDoc and imported it in our XI system,it worked fine.
Then we changed the length of a field and reimported this IDoc,deleted the metadata in IDX2 and it is fine in development system.
The metadata is exactly same as the latest version of IDoc.
However,when we imported the same in our test system,in IDX2, for metadata,we can see this changed field appears two times,one with the old length and other with the changed length.
What could be the reason for this?
Has anybody encountered this problem?Kindly let us know.
Thanks.
Regards,
Shweta

Hi Rajesh,
We tried to delete the metadata using transaction IDX2 a number of times but every time it gets created with twice occurence of this field.
Also,this is fine in dev system and test R/3 system.
Problem only exists in test XI system.
We tried transporting again as well,but no luck.
Here,new changes are being picked up but older changes are not removed ,so we can see both versions for this field.
Any other areas to check?
Thanks.
Regards,
Shweta

Idoc meta data does not come up in trx idx2

Hi there,
Im importing IDOC meta data into XI (using trx idx2) from a CRM 4.0 idoc basic type CRMXIF_PARTNER_SAVE_M02.
No idoc meta data is imported, instead the transaction is giving me back an information message: I::0000
When I click on the pop-up window, the description provided is only: "Message no.000"
Does anyone knows what this message really means?
SLD setup is ok, RFC connections are also ok, IDOC port seems also to be OK.
Any feedback is appreciated,
Rob.

Noriko,
this error is authorization related. There are a couple of function groups which are called in the target system and the user in the RFC Destination to the target system might not have sufficient authorization. Just look into transaction SU53 in the target and select the user used in the RFC destination. This should show you the failed authorization checks.
Also SAP Note 940313 some hints on what you can check for this error.
Regards
Christine

IDX2 Metadata Create Error Message l.000 File to Idoc senario

Dear All,
I got the error l:000 while creating meta data.I read all threads related to this error,but couldn't solve this.I have assigned roles SAP_XI_APPL_SERV_USER,SAP_XI_IS_SERV_USER on xi system,and tried to assign Profiles: SAP_ALL and SAP_NEW.but i couldn't see those profiles.
any help would be appreciated.Thanks in advance.
Regards
Vinay

Hi Vinay,
Please check whether you have created the IDX1 port correctly. It should use the sm59 destination pointing to the SAP Backend system (ECC/CRM). The user access to be used needs to be tested for authorizations. (Do as mentioned above)
Also remember, even if the metadata is not cached in IDX2, the interface should work if the user authorizations are correctly maintained in sm59 destinations and that is referred to in IDX1.
Once the first run is successful, the metadata is automatically cached in PI system (ABAP stack) in IDX2.
Regards,
Souvik

Regarding Error handling and customisation in RFC, Idocs and Proxy

Hi,
I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
Please let me know in detail if possible.
Regards,
Sampada

Hi ,
Check this blog to know when to use which adapter:
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
we use proxy in sap 6.0 version or higher.
Basically used for adapter less communication
& very high volume of data has to be transfered.
Step for Configuration fo IDOC in 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 (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.
Regards,
Vinod.

IDX2 doens't refresh IDoc structure

Hello everybody,
I have a problem with the IDX2. There is a Z IDoc which has changed. So I deleted the old entry in the IDX2 and load it again from the system. But the structure is not refreshed. I tryed to load it from another XI System (the development XI and not the quality XI) but from the same R/3 backend. And there the structure is refreshed. So it seems to be a problem of the XI and not the R/3 backend.
We are on NW04s SPS 13.
Did anybody know this problem and can help me.
Thanks

Hi,
Following two should solve your problem:
Goto IDX1 edit port and then save it again it will refresh connection b/w R/3 and XI.
Goto IDX2 delete metadata and import Idoc again.
You can also refer to note: 907957 (not sure as you are already on higher patch)
Regards,
Gourav
Reward points if it helps you

Regarding IDX2

Similar Messages

Maybe you are looking for