Use Of IDX2
Hi all,
While configuring ALE for Idoc scenarios, we are creating Metadata using Idx2 tcode.
But I don't know what is the use of that meta data exactly. We are anyway giving port and RFC destinations right.
Hi Pavani,
<b>Transaction: IDX2</b>
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.
check this link for detail:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Sachin
Similar Messages
-
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. -
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,
ShwetaHi 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 -
We can import the IDOC Meta Structure using the Transaction IDX2, if I import that in which place the Structure will be stored?
Whether this structure is used by all the SWCV?
Then what is the use of the Imported Objects, there also we have the IDOC importing facility?
Thanks.Hi Pete,
<b>Then what is the use of the Imported Objects, there also we have the IDOC importing facility?</b>
In IR the imported Objects provide the structure that we will use in Message mapping, message interfcae and other IR Objects.
check this link: http://help.sap.com/saphelp_nw2004s/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
<b>IDX2</b>
check my reply in this
Re: Use Of IDX2
Sachin -
IDX2 and it gives me I::000 error
Hi All,
I am trying to import metadata using the IDX2 and it gives me I::000 error. I have checked the authorizations for the user RFCUSER on R/3 and it has
SAP_ALL
SAP_NEW
I am not sure where can I check the log which can show me where could be the problem...
Kind Regards,
Praveen.Hi Praveen,
Check if these threads give you some inputs:
I::000 error in IDOC to IDOC scenario
::000 message no. SR053
Regards,
ravi -
Cannot find the Recv Logical system in Distribution Model
HI experts,
Im triying a Idoc to file scenario, the logical system for PI and R3 has been already created and assinged for the appropriate clients.
and i ve created the port from r3 using tcode we21 and in PI using idx1 and Idx2. The RFC destination also created for PI and R3 system.. when i created the distribution model using BD64 in R2. when i assigning message type i can give the source logical system and i cant find the Receiver logical system... Also in WE19 i cant find the receiver port (which i created in IDX1 and IDX2)..
Could u tell me how to solve this prob???
Regards
BalajiHii Ravi,
Thanks for your reply,
Yes i have created the port (RFC800) idx1 and give RFC destination which points the R3 system.
I have assigned the meta data to that port using tcode idx2.
And I have created port with port name "PORT800" in R3 using we21 and give the RFC destination which points the PI system
when im using the WE19... i gave source logical system as R3 Logical system and receiver logical system as PI Logical system.
now im getting error like "PORT RFC800 DOESNT EXIT IN THE THE TABLE OF PORT DISCRIPTIONS".
Regards,
Balaji
Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM
Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM -
How can I sync to the last read location between devices?
Dear forum,
I have a large pdf file in the cloud (Acrobat.com) which I read both on a laptop and on iPad. What is the proper way to sync beetween the two, so that I can pick up on one device where I left off on the other?
Thanks.Use transaction IDX2. The metadata must be deleted from the cache in IDX2, this can be done by selecting the appropriate system from the list, drilling down the affected IDOC type and chosing delete
The next time an IDOC is sent or received, the cache will be refreshed. -
Error while trying to change settings in SALE
Hi
I am trying to trigger Idocs from QAS, ECC to XI. There are some problems with the settings.
I went to SALE -.> Logical System --> Define Logical System and reach " Display Logical Systems OverView screen.
Here under the Logical Systems, I don't see the name of the Logical System for XI QAS. I think this entry should be there, then only I can enter it next to Partner number in WE20. Is my understanding correct?
But when I try to add the Logical System name of the XI to the list, I am NOT able to do it. I don't see any option to edit it. The Dispplay- Change option under Table View is greyed out.
How do I change it and add XI system to it?
RegardsHi,
You have to follow the below steps :
1. ask basis to provide the proper authorization, or let them do that.
2. once done provide the LS name of XI-QAS,
3. Go partner profile and provide your idoc type.
4. go to port and provide the port which will be followed..
5. configure the xi system, using the idx2, idx1 transaction.
7. replicate the structure in xi and configure your xi system.
8. trigger one idoc in ECC QAS and monitor the same in xi system.
Cheers,
jay -
R/3 to XI (Idoc to File): Do we need to maintain distribution model in R/3?
Hi All,
I have a very basic question regarding Distribution model.
My scenario is IDOC-->File ( SAP R/3 --> XI). So all I am trying to do is send the IDOC frrom R/3 to XI. ( Within XI I am going to do an FTP to the 3rd party file server)
I have created a distribution model, but was wondering if I really need to create one as message is going from R/3 to XI and not from R/3 to another R/3.
Please help let me know If I need to distribute this model to XI or to SAP production sytem or I do not need to duistribute at all for this scenario.
Thanks
ShirinHi,
if you create partner profiles and port via t.code.
i hope, it's not required to maintain Distribution model.
please check the below points.
Configuration Steps for Idoc to File Scenario.
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO, SETTINGS IN SAP-XI
STEP 1:ALE SETTINGS IN SAP-XI
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) ALE SETTINGS TO POST IDOC OUT OF SAP-R/3 ***********************************************************************
a) Create RFC Destination using T.code in SM59.
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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item u2018Generate Partner Profilesu2019
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> u2018Distributeu2019 to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
warm regards
mahesh. -
IDOC Configuration in XI Server
Hi,
i need to send idoc(MATMAS03) from R/3 server to XI server.
In XI server i've done the following configurations:
1. created a logical system for XI server and R/3 server
2. Created a RFC destination for R/3 server
3. Created a port for IDOC adapter using t-code IDX1.
4. Imported the metadata of MATMAS03 idoc into XI server using tcode IDX2.
Configuration done at R/3 server:
1. created a logical system for XI server and R/3 server
2. Created a RFC destination for XI server
3. Created a logical port for R/3 and XI server using t-code WE21.
4. Created partner profile for R/3 and XI server using t-code WE20 and maintained MATMAS in outbound parameter of both the partners.
Now i'm sending idoc from R/3 system using tcode WE19. In tcode WE02, the status of the idoc shown is "IDOC send to the receiving system/program.
But when i'm checking tcode WE02 in XI system, its not showing any inbound idoc.
Do i need to maintain partner profile in XI system also?
Any help will be highly appreciated.
Regards
ManpreetHello Manpreet,
Lets say ur R/3 System is D10 and XI is P10.
Configuration on R/3 Side.. sending system..
1.Create a Port SAPP10 with RFC dest to XI in R/3. WE21
2.Create a Logical System Type LS in R/3. WE20
This logical system is for XI so in you Integration server in SLD Logical System name should be same.
That will do for R/3.
Now for XI..
1. Call Transaction IDX1.
Create a port with name SAPD10 and an RFC dest to R/3.
Now go to WE19 in R/3 take a successful IDOC and display the same.
Doubble click on EDIDC and enter Sender/Receiver Port/Partner Number.
In your case..
Sender: SAPD10.
Partner: xxxxx
Receiver: SAPP10 created above
Partner: xxxxx created above
Partner Type: LS.
And start outbound processing.
Goto SM58 and check ur TRFC if no messages apper you are successful in sending the IDOC else correct and resend.
Let me know if you were successful..
Regards,
Sri. -
IDoc meta data not getting imported
Hello
I am trying to get IDoc meta-data using transaction IDX2. I have configued RFC destinations of type R3 in both the systems (ECC and XI). Also I have created port using transaction IDX1.
When tried to import MATMAS04 using the defined port it gives Information box displaying "I::000" and nothing happens. The information box does'nt contain any message.
Anybody faced this problem with IDoc?
Thanks in advance.
Regards
RajeevHi,
actually it was authorization problem which I noticed when I checked the short dump in ECC.
anyways thanks for the reply.
Regards
Rajeev -
Add new nodes to IDoc in IDoc-XML Schema Mapping with Java
Hello everyone, I'm not very sure if this is the right forum but I have a problem and I haven't being able to find the answer, my scenario is as follows:
-First of all our system characteristics: SAP ECC 6.0, SAP BASIS 700, PI BASIS 2005-1-700 and SAP APPL 600
-We are in Mexico and we are creating our own billing documents with digital signature and a digital certificate in XML format according to SAP Note 1303712 and all derived notes.
-Our actual schema is working fine: We generate our IDocs (one for SD and one for FI) in SAP and we send them to PI XI to be parsed by a JAVA program and then converted to XML.
Now we have the requirement to add new nodes (I might be wrong in the term, feel free to correct me) to the IDoc, it sounds very simple but I have only experience with ABAP and no experience with PI, also it's working only on our production landscape, so if I don't do it right it could be very dangerous.
I have already read the following notes that might help me: 1321680 and 1318342 but their configuration is just in the aplication server and don't mention anything about PI or the Java program.
So, if any one could provide me some kind of guide or important aspects that I should take care (like mapping, structures, etc) to enhance IDocs for this schema i would be very grateful.
I hope this post were clear enough, if it is not also feel free to ask me to clarify or provide more information.
Kind Regards
OmarHi Omar,
Since the structure of the IDoc is changing (adding a new node), you would need to do the following in PI:
1) Reimport the IDoc in ESR/IR of PI.
2) Change the mapping/transformation logic in the mapping parser defined. If it is a Java code, you would need to reimport it in the ESR/IR. Use link below to understand more on jave mapping.
http://wiki.sdn.sap.com/wiki/display/XI/BeginnersguidetoJavamappingusingDOMparserinSAPXI
3) Delete the IDoc cache using transaction IDX2, after the IDoc is reimported.
Regards,
Sanjeev. -
Inbound Idoc processing issues - Partner Profiles - error status 56
Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-DHi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM -
EDI: Sender port in control record is invalid
HI
EDI: Sender port in control record is invalid, this message i am getting in WE02 what is this pls tell me ASAP
regards
shekarHi,
Check the ALE setting...
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Regards,
Phani
Maybe you are looking for
-
INSTALLING AND USING NEW IPOD TOUCH
Cannot install and use IPOD touch on computer. Showing up as a camera and not accepting install. Have tried uninstalling previous versions of itunes and ipod downloads. Please advise. Would like to see this work today.
-
10.6.8- since update both Macpro and Mac Air very sluggish. How do i fix?
Both computers are sluggish- so I have to assume it was something with the update which I did at the same time. Web pages take very long to open and apps hang on launch. Anyone else? I tried Snow leopard cleaner and repair permissions.
-
Dear javafx coders I am a physics teacher in London and I am trying to learn JFX so that I can make animations for use in lessons. I don't know much about programming, but so far I have successfully managed to animate a circle which oscillates up and
-
Is it possible to change Item Category of BOM component
Hi, We are in the process of implementing Guided Structure Synchronization (GSS). GSS helps in Syncing Source BOM (Engineering BOM) to Target BOM(Manufacturing BOM). During the creation of EBOM, designer may not have complete information about the I
-
CrystalReportViewer in CR2008 - Parameter panel - apply button
Hi, I'm working on a .net desktop application, that uses CR embedded server as a reports engine. We just migrated from CRXIR2 embedded server to CR2008 Embedded server in our new release. We want to use the new functionality of dynamic parameters in