IDX2 Metadata

Hi,
In IDX2 we can add a Idoc metadata, In the same wise how can add metadata for a RFC. Help me friends.
Thanks
Hari

hi hari,
            idoc only we can add meta data, in RFC we dont need to add meta data, just we import the rfc under imported objects.
   regards,
   ganesh.

Similar Messages

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

IDX2 Metadata Error Message no.000 File to Idoc senario

Hello Experts,
I am trying to load metadata in IDX2 manually. But it fails and comes out with message Message no.000
I have crossed checked my RFC Destination (SM59) the connection test is successful. The port on IDX1 is created
Similarly the RFC Destination on CRM system is created too. Why is it that my metadata load is giving this message?
Also I created and end to end scenario in XI system for File to Idoc. The file is scheduled in queue for process. The receiver determination has hot started in pipe line process.
To check these when i went to idx2 there is not metadata. hence i tried to load the meta data ... am i searching in right direction?

Yet again like the post in this thread
IDX2 Meta data import fails. I::000 error.
I have been stupid not to check the user on R/3 i spelled the user wrong
Thanks for your support guys

JDBC to IDOC Error

Hi Guys
On my Scenario Jdbc to Idoc (Asynch) I am using FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01
as a Receiver Interface, now when testing on the sxmb_moni I get two flags the Black and While and the Red the one the is Back and While shows that the Sender is my JDBC Adapter which is right
but now the Red flag show that the Sender is IDoc(FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01) is also Sender of which I used it as a Receiver Interface, I dont know how to stop this IDoc Adapter not to send but to receiver.
Basical my scenario is meant to create an IDoc but is is not doing it when going to TCode WE02/WE05 I get message : "No IDocs selected"
Thanks
Yonela

Hi
I don't have any conditions, to Send and Receive, by the way I went to TCode IDX5 my Outbnd is right but Inbound thats where I get the below error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error
I have done these:
SM59- To Create RFC Destinations
WE21- To Create IDoc Ports
SALE- To Create Logical System
WE20- To Create Partner Profiles
IDX1- Port Maintenance in IDoc Adapter
IDX2- Metadata Overview for IDoc
On the ID I created the the IDoc Receiver:
RFC Destinatin: IDOC_RECEIVER
Interface Version: SAP Release 4.0 or Higher
Port: SAPPI1
SAP Release: 701
What could be the problem
Thanks,
Yonela

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
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.
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,
AshwinM

Trouble shooting File to Idoc scenario: wrong Idoc structure in target

Hi All,
             I am working in an file to idoc scenario. Now the scenario is running but the idoc I am sending from SAP XI is not matching with one received in SAP R/3 system. This is not a new scenario. The scenario was already existing. I have done structural changes in Idoc structure and re-imported it in SAP XI. When the iodoc reaches SAP R/3 system I check its structure and data content. 4 of its fields are missing all 4 were newly added fields. Data from some fields are getting merged into one field within Idoc. data from one field is moving onto other fields in target. I have refreshed the metadata using IDX2 transcation within SAP XI but still getting same result.

Hi All,
I am able to see the changed idoc structure in IR. I have also tried cache refresh. I am trying to explain my problem once again with example.
Source Idoc in XI
      fieldname                            data
       f1                                       d1
       f2                                       d2
       f3                                       d33
       f4                                       d4
       f5                                       d5
Idoc structure received in SAP R/3 system. I am seeing through we02 transcation, inbound idoc
      fieldname                            data
       f1                                       d1
       f2                                       d2
       f4                                       d33d4
I have tried cache refresh, IDx2 metadata refresh, but no improvement of the situation.

Extension does not exist : File - XI - IDOC

Hello,
I have an IDOC MATMAS03 with an extension, so called
MATMASA03.ZMATMASX
IDX2 - metadata upload done more than once ! OK
mapping from file to IDOC: test ok (Name of Interface ZMATX.MATMAS03.ZMATMASX)
config: test of communication from file system to R/3 with IDOC payload: OK
Process running results in an error:
Attribute IDOC Metadata, Extension ZMATMASX does not exist.
System is running on SP14!
Does anybody here have experience with extensions in IDOCs or knows about this problem?
Lot of thanks for any help!
regards
Dirk

Hi Dirk,
you can also have a look at idoc receiver channel
PORT: SAPXXX
is this the same port that you have your idoc metadata
downloaded in IDX2 ?
worth to check I guess
Regards,
michal

Simple IDoc to IDoc scenario with SAP PI

Hi!
I would like to implement a very simple IDoc_to_IDoc scenario.
i have two clients in SAP ECC 6.0 and would like to send/receive IDoc (e.g. material) with SAP PI.
Can some one please give exact the technical steps(tcodes, action in XI Tools) to realize this issue?
Any helpful information/documentation/SDN blogs will be very appreciated.
Thom

hi,
Communication Channels:
1) No Sender Channel is required as we are using IDOC.
2) CC_OUT_IDOC_MATMAS05 [Send the data from Xi to CGNSAP01].
Transaction Codes Used:
SM59- To Create RFC Destinations
WE21- To Create IDoc Ports
SALE- To Create Logical System
WE20- To Create Partner Profiles
BD64- Display Distribution Model
WE19- To Trigger an IDoc
IDX1- Port Maintenance in IDoc Adapter
IDX2- Metadata Overview for IDoc Adapter
Regards.

How to configure the Integration Server Settins?

Hi,
I am doing a scenario like Idoc 2 File, I am passing parameter of Adapter Engine is a Integration Server, and when we generate a Idoc and send to XI system using TC: WE19. XI System is not picked the Idoc, and when i am checking RWB the Adapter Framework. Please Guide me how to configure the Integration Server setting.
Regards
Mohan

Hi,
did you checked the ur IDOC outbound status?
also check IDX5, whether it has reached XI system.
plz do check all ur settings:
1. Create RFC destination to XI in SM59 transaction
2. Create a port in we21
3. Create partner profile we20
4. we05- Idocs monitoring
XI Settings:
1. Create RFC destination to XI in SM59 transaction
2. Idx1 Port maintenance
3. Idx2 - Metadata maintenance
4. Idx5 All Idoc inbound and outbound messages
regards
Message was edited by:
Vijaya Lakshmi MV

Idoc to Idco scenario

Hi Experts,
   I need help from you all as i struck in idoc to idoc scenario.
i need to send the idoc from source system(R/3) to target system SAP(APO).
Please guide me what all the steps to be followed.
i need to send the same idoc to target.

hi,
[Re: IDOC to IDOC Scenario;
also a sample scenario wid steps as follows :
Description:
In this scenario we are sending an IDOC from an R/3 system to the IDOC in other R/3 system through XI.
XI Details:
Integration Builder: Design
Component Name : SAPNW of sapnw
Namespace             : urn: idoc2idoc
Integration Builder: Configuration
Scenario Name     :   IDoc2IDoc
Business System   : SAP01 (Cgnsap 01 System)
                                   SSI (Cgnsap 13 System)
Communication Channels:
1) No Sender Channel is required as we are using IDOC.
2) CC_OUT_IDOC_MATMAS05 [Send the data from Xi to CGNSAP01].
Transaction Codes Used:
SM59- To Create RFC Destinations
WE21- To Create IDoc Ports
SALE- To Create Logical System
WE20- To Create Partner Profiles
BD64- Display Distribution Model
WE19- To Trigger an IDoc
IDX1- Port Maintenance in IDoc Adapter
IDX2- Metadata Overview for IDoc Adapter
Processing Steps:
Source Side Configuration: CGNSAP13 (SAP R/3)
IDOC used: MATMAS.MATMAS05
Using Transaction Code WE19 we can see the structure of IDOC (MATMAS05), which we are using
Go to Transaction Code WE19 and enter the name of IDOC in Basic Type and execute
Click on the Segment data and then a screen will come in which the data of IDOC is entered
Creation of RFC Destination:
1. Create RFC Destination: To create a RFC destination use transaction SM59.
The RFC destination is created to provide IDOC a route from SAP system to XI server. Thus once the IDOC is initiated will reach to this destination for further transformations.
2. Create a RFC Destination XI_IDOC2IDOC with Target Host: Cgnsap 32(XI System) and select the connection type as 3(Connection to R/3 System).
The following screen will come once you will click on Create for new RFC destination.
Give a name to your RFC destination.
The Target Host field will be your XI server like cgnsap32.
All the other fields are dependent on the target host.
Save this and your RFC will be created.
Go to Logon/Security tab and fill the details for the Cgnsap32 system as shown below
Creation of IDOC PORT:
3. Create Port: To create a port uses the transaction WE21. We need a port to send the IDOC to the intended RFC destination.
Create a new Transactional RFC.
Give the port name.
Select the RFC destination for this port.
Save the data.
Creation of Logical System:
4.       Now Go to Transaction Code SALE and create Logical System.
Sending and Receiving Systems->Logical Systems->Define Logical System
Click on New Entries and fill the relevant details as show below
b) As we will save it a new window will pop up, in this click on Create and then it will ask you to create a New Request. Just give description of the request and save it, else everything is self-generated.
c) Hence the Logical System is created.
Create another RFC Destination with Target host as cgnsap13. Also create a port and logical system as above using the RFC Destination. This is used as a sender to trigger the IDOC from cgnsap13.
Creation of Partner Profile:
Partner Profiles: Now we will create Partner Profiles by using transaction WE20. These partner profiles are created to identify our logical system uniquely, as we know that there can be n number of logical system in a Business System.
In the Partner No field enter the name of the logical system created.
Enter the Partner Type as LS (logical system).
The type and Lang field will be same.
In the Agent field select the business system from which you are sending the IDOC.
In the Message Type Field include the IDOC.
Save all the data.
Creation of Distribution Model:
Go to Transaction Code BD64 and create Distribution Model.
Click on create model view, window will popup as shown below.
Enter the short text and the technical name as required.
Once the model view is created, click on Add message type. A window pops up as shown below. Enter the details of the model view, sender logical system name (for cgnsap13 in this case) and the receiver logical system name. (Logical system created in cgnsap13 for sending to XI server)
XI SIDE CONFIGURATION: CGNSAP32 (XI SYSTEM)
Creation of RFC Destination:
1. Go to Transaction Code SM59 and select R/3 Connections and click on CREATE.
2. Create a RFC Destination RFC_IODCTOIODC with Target Host: Cgnsap 01(R/3 System) and select the connection type as 3(Connection to R/3 System).
Creation of IDOC PORT:
3. Go to Transaction Code IDX1 and create an IDoc Port PORT_01 (Transactional RFC) and map it with the RFC destination (RFC_IDOCTOIDOC).
4. Go to Transaction Code IDX2, Click on Create and enter the details of IDoc Type and Source Port.
Target Side Configuration: CGNSAP01 (SAP R/3)
Creation of Logical System:
4.       Now Go to Transaction Code SALE and create Logical System.
Sending and Receiving Systems->Logical Systems->Define Logical System.
Click on New Entries and fill the relevant details as show below
b) As we will save it a new window will pop up, in this click on Create and then it will ask you to create a New Request. Just give description of the request and save it , else everything is self generated.
c) Hence the Logical System is created.
Creation of Partner Profile:
Partner Profiles: Now we will create Partner Profiles by using transaction WE20. These partner profiles are created to identify our logical system uniquely, as we know that there can be n number of logical system in a Business System.
In the Partner No field enter the name of the logical system created.
Enter the Partner Type as LS (logical system).
The type and Lang field will be same.
Now add Inbound parameters.
In this screen, enter the Message type and the Process Code for u2018MATMASu2019 and save it.
Now go to   XI (http://cgnsap32:50000/rep), click on Integration Repository for Design.
Go to SLD by clicking on the u2018System Landscape Directoryu2019 in the above screen
Click on Business Landscape and check for the Business Systems, which have the required Technical systems (cgnsap01, cgnsap13 in this case) and the required clients (800 of cgnsap01 and 800 of cgnsap13).
We create a business system if the required business systems do not exist
Creation of Business System:
Click on New Business System and the following screen will appear.
Enter the name of the Business System and click next.
Select the type of the business system in this case its Web AS ABAP.
Select the Technical System for the Business System.
Select the required client.
Select the Business system role and related integration server and click Finish to complete the creation of the business system.
Design: Integration Repository
1. Create a Namespace under component SATYAM_SAPXI_IDOC.
2. Import the IDOC by using Import Wizard in the Imported Object in the Design time.
3. Create a Message Mapping and drag IDOC Structure into Source Message and Target Message panes. Map the mandatory fields of the input and output IDoc structure. Save and activate the message mapping.
4. Create an Interface Mapping for the IDoc.
CONFIGURATION TIME:
SCENARIO: Create a scenario in which all the objects will be created.
Scenario Name: SAP_XI_IDOCTOIDOC
Business System Name: SAP01 (for cgnsap01), SSI (for cgnsap13)
As we are going to send IDOC from the system so no Sender Channel is required.
SENDER AGREEMENT: No Sender Agreement is required.
Communication Channel:
Select IDOC Adapter and provide the details as shown below.
RECEIVER DETERMINATION: In receiver determination, we have to specify the Service and Receiver details.
INTERFACE DETERMINATION: Specify the service, interface and Inbound and outbound interfaces.
RECEIVER AGREEMENT:
Provide the sender service, receiver service and Receiver Communication Channel here.
In the Header Mapping, select the Sender Service as the receiving R/3 Business system
       (SAP 01 in this case).
Testing :
To test all the configuration of IDOC which you have done follow this test procedure:
Use transaction we19 for IDOC Processing.
Give your IDOC and execute it.
c)       Then enter values in IDOC and save it.
d)       Check the values in the XI System using SXMB_MONI Transaction Code.
Regards.
Siddhesh
Edited by: Siddhesh Naik on Nov 3, 2008 10:06 AM

Client Dependent or Client Indipendent

Hi All,
Could you plz tell me, XI Scenarios are Client Dependent or Client Independent ?
Is there any T.Code Creation for every scenario like ABAP ?
Who run these scenarios in Production system ? And how they are know this scenario for this purpose ?
( Based on Namespace or any thing )
Thanks & Regards
Murali
Edited by: Murali Dusi on Jun 26, 2008 9:49 AM
Edited by: Murali Dusi on Jun 26, 2008 9:53 AM

Xi s not same as R3..
Its a middle ware .. even XI system has a R3 (ABAP stack) other than JAVA(Integration Builder)
common Tcoded used in XI are:
SXMB_IFR
Start Integration Builder
SXMB_MONI
Integration Engine Monitoring
SXMB_ADM
Integration Engine Administration
SXMB_MONI_BPE
Business Process Engine Monitoring
SXI_CACHE
XI Directory Cache
SPROXY
ABAP Proxy Generation
IDX1
Port Maintenance in IDOC
IDX2
Metadata display in IDOC
IDX5
IDOC Adapter Monitoring
SLDCHECK
Test SLD Connection
RZ70
SLD Administration
SLDAPICUST
Maintain SLD Access Data
SM59
RFC Destination
ALRTCATDEF
Define Alert Category
ALRTDISP
Display Alerts
SU01
User Maintenance
SXI_SUPPORT
Test all the Repository and Directory Objects
SMICM
ICM administration and monitoring
SMQ1
Outbound Queue monitoring
SMQ2
Inbound Queue monitoring
SWELS
Switch event trace On/Off

New MDC, XI Issue

Hi,
2 things:
1)
I am trying to connect a first IDES client to the MDS for checking Extraction capabilities. I was following instructions ConfigGuide Harmonization+Central MDM, page 23 and fell about some pain-points.
I downloaded MDM Content on the XI as described and imported Design Objects in the xi-repository. I've got a Software Component MDM 3.00, which is based upon some other basic stuff and I created an own component based upon MDM 3.00 (usage dependency, install. time)
When importing my new component, which I want to use for the IDES, I get the MDM-stuff under Subdirectory Bascic Objects (German: Basis-Objekte). The config guide tells, I shall create the namespace - http://sap.com/xi/CMDM - under my own component, where i shall copy (later on), stuff from the mdm component like mappings. I can't do that, because then I get the message: same namespace - where did i go wrong?
2)
Concerning customizing on the MDS:
under ID-Mapping -- make XI File Settings -- there table: Key-Mapping-Framework... what to put there? what is a keymapping factory class?
2a)
customizing - Extraction Object:
when setting up process chain for inbound extraction I get the message: "No extraction objects exist for master data client IDES" - I suppose I get those by Replication of Metadata, but before that, I have to have my XI-scenario going, right ?
thanx for input,
matthias kasig

Hi Markus,
you're right, some expert gave me some valueable clues.
Now I re-opened the topic as my third question is not solved completly (but I have a clue, in which direction to search)...
I also wanted to post the answers here, too, but I didn't find the time last friday. But now I shall deliver:
for 1)
the config guide is wrong concerning the namespace issue... you definitely have to chose another namespace than http://sap.com/xi/CMDM...
concerning 2)
the table "Key-Mapping-Framework" requires a simple entry which has to consist out of the MDS-Host like "myMDMhost" - strange, that I really could not find a hint in the corresponding config guides. I really hate, that there is always such a veil on serious matters and a simple example-entry could have helped a lot... well, why make things easy - it's SAP...
anyway - having the entry you can export the keymapping-xi-files, which you need to import as zip-archive on the xi
for 2a) I am still hanging here, but due to ALE-IDoc problems, as for any reasons I don't get my Replication of Metadata done - but this again due to the fact that the Metadata of the MDS-Request-IDoc sent, won't show up in transaction IDX2 (Metadata-Overview for IDoc Adapter) - though I can import the data manually.
So if somebody knows the exact ALE settings on XI and MDS - then thanks for a hint.
Greetings,
Matthias Kasig
Message was edited by: matthias kasig

File to IDOC Scenario Not able get Metadata (IDX2)

Hi,
I am doing File to IDOC scenario. I have done all configurations in IR and in ID. But it is throwing error like ATTRIBUTE_IDOC_METADATA-Basic type ZOIDOC does not exist.
Where as my custom idoc is a not exit in metadata (IDX2). Also I am trying to reload same manually but I am not able to reload it. I have all required configuration in SAP R/3 side like partner profile.
I would appreciate yours inputs.

Hi Sunil,
You are saying that you are unable to load the Metadata even manually.
There could be a problem with the RFC destination defined within the IDX1 port. So first test the RFC destination using SM59.
Also ensure that you have used the right naming conventions for the PORTS and RFC destinations as below:
<SID>CL<ClientNo> e.g DXXCL055 where DXX is the SID and 055 is the Client No.
Rgds
RC

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 " <b>No RFC destination is maintained for the port</b> ".
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

IDX2 Metadata

Similar Messages

Maybe you are looking for