no interface found

[Former Member]

What does this trace mean in Response Trace

<Trace level="1" type="T">no interface found</Trace>

<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>

<Trace level="1" type="T">Hence set action to DEL</Trace>

[Former Member · Accepted solution]

Hi,

That's not any error. That is just a information. are you facing any issue while testing your scenario?

Thanks

Amit

Reward points if suggestion is useful

[Former Member · Accepted solution]

hi amit...

i am not facing any problem.....i am not receiving a file at the receiver side....

i am doing a idoc to file scenario

[GabrielSagaya · Accepted solution]

In Business Service (ID) set adapter specific Identifier for the Sender IDoc (Logical System Name, R/3 Sender System ID and Client). This is Important for the receiver system to receive the IDoc from the Sender System and should be Identical with the Sender System

[Former Member · Accepted solution]

Hi,

where to fill these details Gabriel

Edited by: Harsha reddy on Jun 19, 2008 11:15 PM

[Former Member · Accepted solution]

Hi Harsha,

Open your Business Service/System in ID. Go to Menu Service -> Adpater-Specific Identifiers.

If you want to Edit it first go to Display/Edit mode and do the steps mentioned above.

Thanks

Amit

[Former Member · Accepted solution]

those are fine......

actually its a idoc to file scenario....

at first i got mapping error...solved it...

now it shows chkered flag form the sender........i dont see any flag at receiver side....

where to see if the error occured...

[Former Member · Accepted solution]

Hi,

In your message monitoring, there will be only one message displayed and if it is showing as checked it means there is no error in Integration Engine.

There can be some error in Adapter Engine before sending the File to Receiver System. You can see that in Runtime WorkBench -> Component Monitoring -> Adpater Engine -> Communication Channel Monitoring. Select your channel and see if there is any error in there ?

Thanks

Amit

Reward points if answer is useful

[Former Member · Accepted solution]

Hi Amit...u are right.....till now the communication channel was fine.....i dont know what heppen all of a sudden...when i see that CC in Communication channel monitoring...

it shows red....it is often happening with other adapters aswell....

here is the error it says

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '/102' too long (>1 for 3. column) - must stop', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '/102' too long (>1 for 3. column) - must stop', probably configuration error in file adapter (XML parser error)'

Edited by: Harsha reddy on Jun 19, 2008 11:29 PM

[Former Member · Accepted solution]

Hi,

Are you using FileContent Conversion in your File Receiver Channel. Please check the properties again. It is only causing the issue.

If it doesn't work try this using this parameter in your fcc.

fixedLengthTooShortHandling

check this url from sap help.

http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm

Thanks

Amit

Reward points if answer helps

[Former Member · Accepted solution]

Hi,

Hey are you using any FCC??

Thanks

Vikrath

[Former Member · Accepted solution]

yes i am

[Former Member · Accepted solution]

Here is my XSD.....can some one tell me ..how to write FCC

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="URN:COM.trys_LGCY_BS" targetNamespace="URN:COM.LGCY_BS">

<xsd:element name="HEALTHCARE" type="HEALTHCARE_INCT_DED" />

<xsd:complexType name="HEALTHCARE_INCT_DED">

<xsd:sequence>

<xsd:element name="HEADER">

<xsd:complexType>

<xsd:sequence>

<xsd:element name="RTYPE">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="3" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="RUNDT">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="8" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="SYSSRC">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="3" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="CUSTID">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:length value="3" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="SYSDST">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="4" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="RUNNO">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="9" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="EFFDT">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="8" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="HDESC">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="60" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="CUSTNO">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="4" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="FILLER01">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="48" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name="DETAILS" maxOccurs="unbounded">

<xsd:complexType>

<xsd:sequence>

<xsd:element name="RTYPE">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="3" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="PERID">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="9" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="FILLER02">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="16" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="FUNDSRC">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="1" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="TRANSTYP">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="2" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="TRANSAMOUNT">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="15" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="TRANSDESC">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="45" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="EFFDT">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="8" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="FILLER03">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="54" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name="TRAILER">

<xsd:complexType>

<xsd:sequence>

<xsd:element name="RTYPE">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="3" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="SYSSRC">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="3" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="SYSDST">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="4" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="LNTOTAL">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="13" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="RUNNO">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="9" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="DRTOTAL">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="19" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="CRTOTAL">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="19" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="TDESC">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="60" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="CUSTNO">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="4" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

<xsd:element name="FILLER04">

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:maxLength value="22" />

</xsd:restriction>

</xsd:simpleType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

[Former Member · Accepted solution]

Hi,

The issue is there only.

In reciver file adapter FCC parameters you would have mentioned one of the field length as 1 but the field size which is reaching the file adapter is more than 1. Please rectify it that and it will resolve your issue.

Thanks

Amit

[Former Member · Accepted solution]

Hi,

you can handle this by using this parameter in your fcc.

fixedLengthTooShortHandling

check this url from sap help.

http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm

Thanks

Vikranth

[Former Member · Accepted solution]

its fine Amit.....everything is perfect...at present i am testing my scenario....

initially it was working fine.....i dont think there would be a problem with FCC

[Former Member · Accepted solution]

oh thats gr8...

[Former Member · Accepted solution]

Hi,

Gr8!!. Please close the thread as answered once you are done and by rewarding points

Thanks

Amit

[Former Member · Accepted solution]

oops...i am sorry...i wanted to say it was fine.....spelling mistake....apologize for that...

it was working fine....all of a sudden.....i dont know what happen to that...

[Former Member · Accepted solution]

Hi,

Is your issue resolved or not? Can you send me your fcc configuration details and your target data after mapping from sxmb moni.

thanks

amit

[Former Member]

i see a system error in message monitoring...

[Former Member]

Hi,

check out the connectivity etc for Integration Server

Go to RWB>Component Monitoring>Test all the components.. Atleast Integration Server should be green or Yellow.

Also test the Cache Connetivity Test

Even you can check Message Monitoring in RWB...does it work?

Hope this can help u to find out the errors,

Thanks

Vikranth

[Former Member]

Hi,

Check these.

1.Check your interaface determination and receiver determnation.

2.compare the entries "service", "interface" and "namespace" of your interface determination with the entries at message monitoring SXMB_MONI. They are case sensitive.

Can you tell me what type of error are you getting in SMB_MONI

Thanks

Vikranth

[GabrielSagaya]

You have to define a Receiver Determination for the Sender & Interface and specify the Receiver there. Furthermore, you will need an Interface Determination to determine the interface of the outgoing email and the mapping that is required to transform the IDoc to this interface.

http://help.sap.com/saphelp_nw04/helpdata/en/19/8dba88b1db634f891622e909565f7a/frameset.htm