IDoc Meta Data Problem

Hello i am getting the following error not clear of what might be the cause.
<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with <Client> Requested parameter does not exist FM NLS_GET_LANGU_CP_TAB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:Add
itionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with <clinet> Requested parameter does not exist FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please suggest

Hi,
I am just replying that..
Just go to Tcode SM59 in XI system and then go to RFC connections and then check for the RFC destinations created for the R/3 system. And then click on that will lead into different screen. Then click on Test Connection tab. If it is successfully connecting to R/3 system, then RFC destination is correct.
http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042638488911d189490000e829fbbd/frameset.htm
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Hope this helps..
Regards,
Moorthy

Similar Messages

IDOC meta data

Hi All,
I am trying a file-idoc scenario. I have imported the IDOC in IR and done with the mappings. I have created a RFC destination to R/3 server of type 3. Also I have created a port in IDX1 with the created RFC destination.
In IDX2 I cant find the meta data for my imported IDOC. Should I do it manually? If so how?
Thanks & Regards,
Jai Shankar.

Re: Importing Metadate from IDES 4.7 into Integration Server Rep
Re: IDoc Meta Data Problem
Have a look into these !!!

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
Rajeev

Hi,
actually it was authorization problem which I noticed when I checked the short dump in ECC.
anyways thanks for the reply.
Regards
Rajeev

Unable to delete IDoc meta data

Hi,
When I'm trying to load the IDoc meta data from IDX2 it is telling first delete the old one and then reload. But, the problem is we are unable to see the already existing IDoc meta data.
Can some one suggest how to see meta data all the loaded IDocs.
Regards,
Jeevan.

Hi Jeevan,
You may be checking for the IDoc meta data in the wrong port.
Make sure that you are looking in the correct port.
>>Can some one suggest how to see meta data all the loaded IDocs.
1. In IDX2 expand the Port that you are trying to import the IDoc.
2. Locate the IDoc type in that port and hit Delete.
Thanks
SaNv...
Edited by: Sãnthosh Kûmãr V on Oct 23, 2008 11:20 AM

Loading IDOC meta data into Xi not working

Hello,
I'm trying to load IDOC meta data using trx IDX2 but the program is not able to recognize the port "SAPRD1_222" I previously defined in trx IDX1.
Any ideas, what Im missing here?
Ruud

Ruud,
Pls take a look of this thread:
Re: Importing Metadate from IDES 4.7 into Integration Server Rep

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

IDoc Meta data Error at XI server

hai all,
I triggered IDoc from R/3 System and after observing XI server, it shows the following Adapter Meta data Error .RFC destination and ports are correct. Please can any one comment on this.
<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thank u.

Hi Nani,
go to transaction IDX2 and try to download
the metadata manually to see if there are
any errors over there
you can also find the same approach
(loading, reloading and comparing metadata) in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

IDoc meta data load problem in IDX2

I have been trying to load meta deta for some idocs and am getting message 'Basic type <idoc_type> is unknown'. Interesting to note is that I could load ECMMAS01 idoc type but other idoc types like MATMAS01 ..04, ORDERS01 ...04, DOCUMENT_LOAD01 ... and many others that I tried, I got the same message. The config has been done in IDX1 and IDX2 (that's how I got the ECMMAS01 in).
There is an OSS note '0000751839 IDoc Adapter: Basic type 'XYZ' is unknown. ' It seems we are already on that patch level. Can't verify if the note has been really applied or not for authorization issues for now. The note also mentions about a workaround to set the category level to '0' (i.e. blank) in the Integration server configuration. But that doesn't seem to help either.
Anyone else had this problem and resolved it?
Harshad

Problem stands resolved. I realized that the RFC destination in XI for the R/3 system had a problem. What still is not answered is how come I was able to import ECMMAS01?!?! One explanation could be that the RFC connection was ok then. Don't know, but I am happy that it works now.

Doubt about idoc meta data

hi this is seshagiri. i have one doubt while in sending idoc to xi server in the idoc to file scenario, can we do with out configuring metadata in idx2.
if can we do means wat is the procedure.
please clarify me
thans & regards
giri

Hi Sesha giri,
    If you are dealing with Idoc to File Scenario...you need to create
1) RFC Destination in R/3 pointing to XI.
2) Ports in R/3.
3) PartnerProfiles
   we need to send idoc from R/3...so we have to do ALE configuration.
   Please see the below link for more details.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Hope I am clear.
Please let me know if you have any queries...!
Thanks and Regards,
Chandu

Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

Hi,
I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
Thanks in advance.
Best Regards.
Alex

Hi Aamir,
The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
Thanks anyway.
Alex

Meta Data issue

Hi,
When I'm trying to load the IDoc meta data from IDX2 it is telling first delete the old one and then reload. But, the problem is we are unable to see the already existing IDoc meta data.
Can some one suggest how to see meta data all the loaded IDocs.
Regards,
Anitha.

Hi,
Try answers from this link
Re: How to refresh metadata in XI for IDOC
Thanks!

IDOC ADAPTER Issue, some meta data loads, some doesn't

Hey all,
I just started trying to setup the IDOC adapter connection between our R/3 system and our XI system. I decided to try and pull in some meta data via IDX2 to start. The weird thing is that I get some IDOC structures successfully, but not others. I think it has to do with some requirnments that I am missing on the R/3 side. For instance, outside of setting up the RFC connection, creating the tRFC port and the partner profile for the Logical system what else is needed. Do I have to assign the basic type to the outbound partner profile to access it? Do I have to actually create IDOCS for the basic type? Just curious. Here are the details of what I have done so far. A lot of this I pulled from other peoples postings here on the forum, I think I am just missing a few steps!
Our current configuration is as follows:
SAP R/3 Enterprise to post IDOCs to XI .
- R/3 Configuration:
logical system created: DXICLNT200
we20 : Partner Type LS: partner number: DXICLNT200.
we21 : IDOC Ports: Transactional RFC: Port name: DXICLNT200. IDOC record type SAP Release 4.x. RFC Destination : DXICLNT200
sm59 : create RFC destination : DXICLNT200. Target host: the XI box. Logon security: Client 200. XIAPPLUSER. PASSWORD (for XIAPPLUSER). Testing the connection works.
- XIHOST Configuration:
sm59 : created RFC destination to DDSCLNT210. Gateway options used, NO Client or User specified, are these needed, if so, is there a particular user to use.
Test connection works.
IDX1 : Created Port - DDSCLNT210. client 210. RFC destination DDSCLNT210.
IDX2 : Able to load metadata for IDoc Type CHRMAS01, of port DDSCLNT210. NOT ABLE TO IMPORT CREMAS03 or MATMAS03!
Any help is greatly apprciated!
Thanks,
Chris

There was a problem in the RFC connection, the target host was not populated correctly. All meta data can now be pulled.
However, I am curious about where the meta data for CHRMAS and CLSMAS came from. the RFC connection was NOT working, so where could it have pulled this information from????

The meta data for the IDoc type "LOIPRO01" is unavailable

Hello,
i'm trying to send idocs via rfc from SAP ERP ECC 6.0 to SAP MII 12.06, but we always get errors like:
The meta data for the IDOC type LOIPRO01 is unavailable
I've checked the parameters on MII side of the IDOC Listener:
Servername MII_JCI33
server Properties
gwhost H33-I0.rz.k-plus-s.net
gwserv sapgw02
progid MII_JCI33
trace 1
params
snc_myname
snc_qop
snc_lib
unicode 1
max_startup_delay
Client Properties
client 303
user RFC-I33
alias_user
passwd
lang en
sysnr 02
ashost h33-i0.rz.k-plus-s.net
mshost H33-I0.rz.k-plus-s.net
gwhost H33-I0.rz.k-plus-s.net
gwserv sapgw02
r3name H33
group
tpname MII_JCI33
tphost H33-I0.rz.k-plus-s.net
type 3
trace 1
codepage 1
There is no saprouter between ERP and MII as in the thread from Christoph Mertins in November 2008. The user rfc-i33 on the ERP has SAP_ALL permissions.
Has anyone an idea ?
Kind Regards,
Thomas Strecker

Thomas,
There is a link for a basic IDoc installation that may help.
[IDocListener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
One other issue that has occurred to cause problems is registering the program in Visual Administrator. If you registered the ProgID in Visual Administrator, there will now be two ProgIDs registered (MII does self registration with the RFC Destination upon starting the server). Delete the registration in VA, if you did it.
If there are other error messages available, please post them.
Good luck,
Mike
I also just remembered, if you have two ProgIDs that are the same, running on two separate MII instances, you may run into a problem. Not sure it will have the same symptoms or error messages, but something else to check with (especially when migrating from dev to prod).
Edited by: Michael Appleby on Feb 10, 2009 5:02 PM

Problem in loading meta data !!!!

Hi,
While creating metadata in IDX2, I am getting communication error 'Error when opening an RFC connection' .
I have created port SAP<SYSTEM ID> and client no & giving rfc des of sap system in idx1 . and while loading meta data i an getting above error .
I able to load meta data if i use other (non sap ) port eg abc and usng rfc des of sap system . but idocs are not reaching xi
What are the steps we should do for loading metadata by using sap port i.e client .
Please help me solve this problem
Thanks,
Sridhar

HI
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
PLZ REWARDS POINTS
VIKAS

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 "Error: I::000" 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

IDoc Meta Data Problem

Similar Messages

Maybe you are looking for