Metadata EDISDEF not maintained - Idoc adapter error

hi,
In our scenario, SenderParty->XI->R/3, we are using custom idoc to post into R/3. The idoc adapter throws an error, Metadata EDISDEF for port SAPXXX, IDoc type ZKAGXXX and CIM type not maintained, but when i use standard idoc, i don't get this error. We even applied oss note 837595 to fix authorization issue, but it didn't help.
Any ideas or suggestions.
Thanks
Pandari

One LAST suggestion. Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS). Try authorization group 'SS' (without quotes). So:
Object: S_TABU_DIS
Activity: 03
Auth. Group: SS
I recall now that a customer recently had this issue and (for them), this helped.
Jin

Similar Messages

Basic Idoc Adapter Error - XI 3.0

Hi,
I am new to XI so excuse me if this is a basic question.
The scenario we have is File -> XI -> IDOC
When the message is processed into the IDOC Adapter I am getting the following error :
Control record must start with tag EDI_DC40 not E1LFA1M
Don't really understand this one as in the message mapping this segment on the target IDOC is disabled. It was my understanding that this segment is automatically filled by the IDOC Adapter.
Is there something I need to change in the Idoc Adapter to get this to happen ?
Kind regards
colin.

It is not a basic question, but it seems to be a common problem.
Check in your IDOC receiver channel, if the checkbox "Apply Control Record Values from Payload" is marked. If so, uncheck it. That should help.
Regards
Stefan

IDOC Adapter error while load balancing

Folks,
I am facing an issue when I am switching on Load balancing button in RFC destination while sending IDOC in sender system . The sender system shows this error in SM58
IDoc adapter inbound channel: Error Error when rea
Thanks,
Manish

Hi Manish...
This is from F1 on Traget host field in SM59..Check part in bold..
Name of target host
 Name of the target host as displayed by the UNIX command 'hostname'.
 If you are using load balancing, the target host must be the host name
 of the message server of the SAP System. This is defined in the profile
 parameter 'rdisp/mshost' of the target system. If you have any further
 questions, consult your system administrator. 
 You can specify host names as
 - Normal host names
 - Host names in DNS format (if DNS available)
 - IP addresses
 - SAProuter names (in the form /H/.../S/.../H/.../S/... )
Notes
 If you enter the host name (for example, hs0311) as the target host in
 an RFC destination, its IP address is stored internally in the database
 table RFCDES (destination administration). This speeds up the RFC
 connection initiation, since the host name does not need to be converted
 into its IP address.
 However, problems occur if the IP address of the target host changes.
 For this reason, you must adjust the RFC destinations if the IP address
 of the target host changes.
 If you specify the host name as a SAProuter name (/H/hs0311 instead of
 hs0311), it is not converted into its correspondidng IP address.
 Instead, it is stored in its SAProuter form in table RFCDES.

Material not maintained by purchasing : error in purchase requisition

Dear Experts ,
I have created a new material of material type ZSPR where the purchasing view is already extended. I can see
the purchasing view after selecting the plant in the material master. But when trying to add the line item in
Purchase requisition for this material ,then i am getting message "Material xxxxxxxxxxxx not maintained by
purchasing".
when I go the material master & click on the purchasing view , message in bottom is shown with tick in green
round background "No plant-specific data exists"
I have created hundreds of materials in past 10 days , but this problem comes only for 3 to 4 materials.
Kindly advise how to resolve.
Thanks in advance.
Regards,
Anil Shanbhag

Hi Anil,
Good day.
This problem occurs because there is no purchasing view plant specific i.e. you may be extended the purchasing view for some other plant.
1. Go to MM01.
2. Select Purchasing view.
3. Enter appropriate plant.
4. Enter relevant data & save.
If this doesn't help revert back.
Regards
Anil

IDoc Adapter error / oss note 856266

Hi all,
Has anyone else run into and successfully fixed the error described in oss note 856266? We ran into exactly this issue. Found the note by searching on the error message, downloaded and applied the correction instructions, all the while feeling pleased it was such an easy fix...
Nothing changed whatever though after the correction instructions were implemented. So either we did something dumb or the fix is not working for our system. Just wondered if anyone had similar experiences?
We are on Win2k/SQLServer/SP13
Cheers,
Chris

One LAST suggestion. Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS). Try authorization group 'SS' (without quotes). So:
Object: S_TABU_DIS
Activity: 03
Auth. Group: SS
I recall now that a customer recently had this issue and (for them), this helped.
Jin

IDOC Adapter Error

Hi All,
My scenario is JDBC to IDOC, where I am fetching data from Database and posting an IDOC in SAP. My ALE Configuration is correct. I have done the following steps:
In XI:
1. Created RFC destination to connect to ECC system
2. Created Port in IDX1
3. Imported Meta-data in IDX2
In ECC:
1. Defined Logical system
2. Partner Profile settings.
Still, I am getting the below error, not sure why is this occuring...
<?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_INV_RCV_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anyone help me out with what could be the cause of the error.
Thanks in advance.
Regards,
Amit

Hi Amit,
check this link
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
OR Check the receiver IDOC setting in my posting on Wiki
for File to IDOC scenario are u missing something
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
copy and paste complete link in URL or click here
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC& then Part3
Sachin
Message was edited by:
Sachin Dhingra

IDOC Adapter error"ATTRIBUTE_INV_SND_SERV'

I am doing small example like Using HTTP Client to submit Order Response XML from my browser and Converting Order Response XML file to an order response IDOC of type ORDERS05 idoc. I have developed all the necessary objects in Integartion Repository & Integration Directory and posted the Order Response XML file through HTTP client.
I am getting the error message(in SXMB_MONI)like "Unable to convert sender service OrderResponse to an ALE logical system".
Appritiate, if some one help me On this .
Thanks
Sudha

For the business sytem you have to mention the adapter specific identifiers in the Integration Directory.
Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
Maintain Logical System name and System ID and Client number.
Check the following blog.
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
regards
Shravan

XI- CRM through IDOC adapter - error in outbound status of XI

I have set of messages created today, each of which have 10,000 records as well as same no. of idocs as outbound in XI.
only few messages have status 'messages processed' adn lot of messages are in staus 'Message Recorded (Commit follows)' and 'System Error (Restart Possible)'.
So only the expected idocs are not coming in CRM. But i see the idocs XI. i clicked on IDOC in outbound column of SXMB_MONI.
how can i restart the same message and get the idocs into CRM.
THanks for your help in advance.
Regards,
Jilan Bhasha

hi Agasthuri Doss,
Do you mean to Restart the message?
i tried restarting the message, then prompted with the below message.
Do you want to retain the trace level for the
selected messages (with errors) for the restart
or increase it (maximum level)?
i click on Retain, then the below error appears.
'You cannot restart XML message
E79C4320576611DBBAB10003BAD9E360 with this
status/type'.
Thanks & Regards,
Jilan Bhasha

IDOC Adapter error / ATTRIBUTE_WRONG_INTF

Hi at all,
I have a problem regarding a interface sending IDOCs ( messagetype HRMD_A ) from one R/3 to another R/3 system via XI.
I have created a new Message Interface which has the Message Type of the imported IDOC typ ( HRMD_A06 ).
When the system tries to process the inbound IDOC I get the following message :

- <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_WRONG_INTF</SAP:Code>
<SAP:P1>MI_HR_A_Cas</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_HR_A_Cas</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Where can the problem be located ??
Why can't the IDOC interface be interpreted ?
I hope somebody can give me an advise.
Thanks
Florian

Hi Florian,
my solution:
Create a simple BPM which will handle your situation
BPM:
reveicer step -> check step -> (transformation one or two ) -> send step
in bpm you can use as many message interfaces (abstract idoc ) as you want
Regards,
michal
Message was edited by: Michal Krawczyk

Port Settings for IDoc Adapter

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

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

Shipping data not maintained in Plant.

Dear all,
While creating PO "shipping data not maintained in Plant" error comes.Please look into below issue.
Thanks and Regards,
Baiju

If it is Stock transfer PO, then your config is incomplete. You need to set it in below config path
spro>MM>purchasing>purchase order->setup stock transport order--->define shipping data for the plant.
Here you need to do for sending plant. You need to enter customer data and sales org data along with shipping point.
Regards
Antony

Error: Metadata EDISDEF for port SAPEC1, IDoc typ

I am getting following error in my File-2-IDOC scenario.
Could anyone please help me out?
Error: Metadata EDISDEF for port SAPEC1, IDoc typ
CREMAS04 and CIM type not maintained
I defined RFC Destination and Port properly..
Did I miss out anything.
Thanks in advance for the help.
Venu

Hi,
A few checks to be done,
1. GO to the RFC destination 9in SM59 and see if the Remote Log on and Test COnnectiivyt to the R# system works.
2. Go to IDX2 and deleted the exisitng Metadata and import the same meta data manually. IS the import succesful?
3. Check if you have entered valid POrt value and RFC destintion in IDOC adapter.
Regards,
Bhavesh

Error when Loading Metadata for IDOC Adapter

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

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

"error no:58" partner profile not maintained in idoc.

Hi to all,
i am new member to this site already searched forums for solution.
can anyone help us out to solve the following error while simulating inbound idoc.Error:58 " partner profile not maintained"
we tried with msg type CREMAS and DEBMAS.created partner profiles,rfc connection as procedural but same error results.
also give some useful links to process idocs.
we want ur valuable suggestions,thanks in advance.
regards
vinoth

Hi,
link for inbound idocs is given below
[http://help.sap.com/saphelp_46c/helpdata/en/78/2174b051ce11d189570000e829fbbd/content.htm|http://help.sap.com/saphelp_46c/helpdata/en/78/2174b051ce11d189570000e829fbbd/content.htm]
[http://sapdocs.info/sap/abap/idoc-useful-notes/http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli|http://sapdocs.info/sap/abap/idoc-useful-notes/http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli]
[http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-ii/|http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-ii/]
[http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-iii/|http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-iii/]
Please check in the receiver side if the partner profile is configured correctly.
Go through the link below in order to maintain partner profile.
[http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/content.htm]

Error Valuation & is not maintained for material & in IDOC

Hi Experts!
I'm currently having a difficult problem here.
This is an idoc issue. The scenario is: An idoc is created from WEB and an error appears "Valuation & is not maintained for material &" in SAP. But when we reporcess again usign the same data through WE19 everything seems to be okay. The status is green. Do you have any idea regarding this?
The error must not appear because the material that is being process is a non-stock material which does not need valuation.
I hope somebody can help me on this.
Thanks in advance!

Hi,
Please see that error ME124 ir raised because view "plant stock /
storage location stock" is not maintained in material master for plant.
if the material is not available in stock then no delivery and no
transfer is possible. It is not possible for non-stock
materials to make an stock transfer.
If you are using ME21* to create stock transfer order,
Please make sure the view "plant stock / storage location stock"
have maintained for the relevant plant in the material master
record.
Please also make sure the quantity flag have switched on in Ta OMS2
for both the delivery and receiving plant for the material type
that you are using. Otherwise, the error message ME 124 will be
issued.
But if you get the error error ME124 only for a vendor is the
assignment in Vendor Master (MK03) to plant. This assignment is
used in case of STO, in which plant must be assigned to vendor.
In order to not get the error, please remove plant in the
following path:
XK03 > Extras > Add. purchasing Data > Plant assignment.
BR
Nadia Orlandi

Metadata EDISDEF not maintained - Idoc adapter error

Similar Messages

Maybe you are looking for