Idoc - DTD file - schema

Hi,
In my outbound idoc scenario, i have to send idoc in XML format with schema.
I don't know what schema is, if it's XSD file or other.
My answers is:
1) What is it schema (or XSD) file? I have to send always or just one first time?
2) the DTD file which i can set in WE21 for XML port is the same thing? If not, which differents?
Thanks lot.
Matteo Vernile.

Hi,
1) What is it schema (or XSD) file? I have to send always or just one first time?
schema is a definition of xml. It is metadata which describes what can be inside xml. You can find xsd in this transaction: WE60
2) the DTD file which i can set in WE21 for XML port is the same thing? If not, which differents?
DTD is another definition type but it's not the same as xsd.
/wg

Similar Messages

Where to find dtd file name/schema for a certain XML Gateway interface

Hi folks,
For a certain XML Gateway interface, in which DB table can I find the dtd file name and dtd schema that this interface use?
Now I can find its map name.
Thanks.

Hello!
I found the answer myself now.
The XLST files are part of the static web content of the MI project Visiprise.
In the SAP MII workbench go to the project Visiprise
Then under the tab Web the static contecnt can be found under the folder WEB/XSLT/..

Flex Config File DTDs or Schemas

I am writing a basic application to test Flex integration
with Java objects, and after solving a bunch of deployment errors,
I am happy to say I am finding no errors on deployment anymore. The
application, however, still doesn't work because of what must be
some undescribed configuration error.
I have been unable to find any DTDs or schemas that pertain
to any of the following files:
flex-config.xml
data-management-config.xml
flex-webtier-config.xml
remoting-config.xml
services-config.xml
mxml-manifest.xml
Putting aside my disappointment that I need all these files
for a Flex-Java application that couldn't get any simpler, I would
appreciate any insight into these files.
Thanks.

Ok, I solved it by myself
I need to add the following codes when calling the Compiler
API
Configuration conf = application.getDefaultConfiguration();
conf.setToken("flexlib", "path to the frameworks")
applicaiton.setConfiguration(conf);
Then it solved the problem

How to generate .DTD file from IDOC?

Dear All,
On behalf of my colleague,
How to generate .DTD file from IDOC? I want to generate this file for importing into the WebMethod Tool. Please share relevant content regarding the same.
IDOC name is: BOMMAT01
Let me know if you need any other information.
Regards,
JK

Hi Jitendra,
When PI receives idoc from ECC it will be in xml format.
Are you telling that you want to convert this xml to .dtd file?
check this for converting xml into .dtd file.
How to convert XML file into DTD or XSD
could you please explain about what you are doing in this requirement?
After importing into WebMethod what is the next action?
do they want to send the file to PI?

Error during variable substitution: idoc to file

Hi Friends,
I have a got a issue which is Idoc to file scenario.
Iam getting the following error.
Attempt to process file failed with com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: date_processing
Could you please tell me waht could be the reason for the same?
as per my analysis, I observed that the field date_processing has been declared

Hi Sandeep ,
If the variable date_processing refers to an element in XML schema, Please check if you have added the prefix payload: to the information under Reference.
The reference then comprises a pseudo path description in the form of a comma-separated list with the schema namea,na,nameb,nb,....
Where namea,nameb,... corresponds to the element name and na,nb,... corresponds to the occurrence of the element name at the respective level in the document.
The description begins at the root of the document and ends at the respective element.
Also please check
Re: Variable substitution
Regards,
Jyoti

Idoc to file problem with DynamicConfiguration

HI SAP Guru's
I have a iDoc to File scenario and the output file requirement is bit tricky.
output file should be xx_Region_iDoc Number_YYYYMMDDHHMMSS
I been through couple of blogs but non of them mentioned about the iDoc all of them showed the about the FileName in FileAdapter.
I believe it is only possibly via Dynamic configuration.
I need to extract E1EDKA1/LAND1, DOCNUM from Source IDoc Structure and then concat it with Date and generate the output file name.
I cannot even get the iDoc Number i.e. DOCNUM via Dynamic Configuration.
I was trying this method but it didn't work.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/IDoc","DOCNUM");
String ourSourceFileName = conf.get(key);
return ourSourceFileName;
Can somebody please let me know how to achieve this and how?

Hi Rodrigo,
I have done the UDF with 3 inputs and mapped it with header of Target side and now would like to know about the setting in File Adapter.
1. Could tell me what do I need to write in "File Name Scheme" , I am using *.xml , is it right?
2. I also check the Use Adapter Specific Message Attributes,
Fail if Adapter-Specific Message Attributes Missing
FileName
Could you please tell me is there anything else I need to do because I have been through couple of blogs and all of them mentioned about File but not about the IDoc.
DynamicConfigurationKey key = DynamicConfigurationKey.create(u201Chttp://sap.com/xi/XI/System/Fileu201D,u201CFileNameu201D);
Except you who mentioned this
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/IDoc",fileName);
I am bit confused about the FileName because there is no FileName in IDoc;
I found these information in IDoc Dynamic Configuration
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPDGE</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">DGE008</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">A000000012</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">CITIPHMX</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">B</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">PAYEXT</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">PEXR2002</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP">ZPEXR2002</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/Message/30" name="CALLER_CODEPAGE">4102</SAP:Record>
</SAP:DynamicConfiguration>
Please comment.

Error in IDoc to file scenario

Hi Experts,
I am working on IDoc to File scenario.IDoc is sccessfully reached XI.In SXMB_MONI it is showing error in request mapping.Error is
<?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="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please suggest me in this issue.
Thanks,
Bhuvan.

Check this link:
http://help.sap.com/saphelp_nw70/helpdata/EN/bb/ad1c3d2b058c4ce10000000a114084/
You might want to refer to the SAP NOTE: 316877
Regards,
Ravi

Idoc-to-File Scenario ATTRIBUTE_INV_SND_SERV Error

Hi All,
I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an 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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>FILE_BC</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
Thanks,
Geetha

Thanks everybody! It has got fixed. I just requested No acknowledgements.
Geetha
Edited by: Geetha on Nov 11, 2009 5:45 PM

Getting Receiver Agreement issue in IDOC to File scenario

Hi Gurus,
 Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
Error Message:
No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
Error Category : Outbounding
Error ID : CO_TXT_OUTBINDING_NOT_FOUND
My IR design:
Sender:
 Interface : VEND_IDOC_OUT_MI
 Message Type : CREMDM.CREMDM04
Receiver:
 Interface : VEND_FILE_IN_MI
 Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
My ID Config:
1. Sender / Outbound Message: Service Type --> Business System
 Service ---> SAPERP
 Interface--> VEND_IDOC_OUT_MI
 Adapter Type : IDOC
2. Receiver / Inbound Message: Service Type --> Business Service
 Service --> IDOC2FileReceiver
 Interface ---> VEND_FILE_IN_MI
 Adapter Type--> File
3. In Sender Agreement : Specified the Sender Communication Channel
 VEND_IDOC_OUT_Channel
4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
Can anyone help me identifying what's going wrong. I'm very new to XI and basically this is the first assignment I'm working on.
Regards,
Subhadip

Hi Babu,
 In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
Please find the XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
 <xsd:complexType name="VEND_FILE_DT">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 8f584d80456311dccd680018fe79f69b
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb0390c11dc843000188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Code
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb4390c11dc84e800188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor name4
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb5390c11dcbe3400188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor City
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb6390c11dc896100188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor PO Box
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0335fd11dc9e9600188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor House No & Street
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0435fd11dc98b000188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Postal Code
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0535fd11dc870500188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Country
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 7ca8d600403b11dcc9bd00188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Tax Number 1
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7040e611dcce4300188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Telephone number
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7140e611dc8f3900188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 VAT Registration Number
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7240e611dccef700188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Account Number of Vendor or Creditor
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7340e611dcb3bc00188bd09370
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>

AckRequestNotSupported error in IDoc to file scenario

Hi,
I have a scenario from IDoc to file adatper, when i try to run this scenario, every thing is ok except there is a error in message monitor.
This error is regarding the Acknowledgment("Acknowledgment not possible"), But the ALEAUD IDoc have been sent to the orignal sender (IDoc side) with the empty content except the Header segment such as sender name, receiver name etc.
And when i tracted the detail information in message monitor, i got the following error information.
*<SAP:Status>AckRequestNotSupported</SAP:Status>*
*<SAP:Category>permanent</SAP:Category>*
I also went through some weblog and artical, i didn't got the solution.
If some body also have this error?
thanks & Best regards
Rocky
Following is My acknowledgment error information: FYI
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1" applicationAckNotSupported="true" applicationErrorAckNotSupported="true">
<SAP:Status>AckRequestNotSupported</SAP:Status>
<SAP:Category>permanent</SAP:Category>
</SAP:Ack>
Outbound Acknowledgment content:
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>030</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000036022</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPO01</SAP:SNDPOR>
<SAP:SNDPRN>A01CLNT030</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPO05</SAP:RCVPOR>
<SAP:RCVPRN>A05CLNT231</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY />
</SAP:IDocOutbound>

Hi Rocky,
Check the below links of setting up of ALEAUDUT RESPONSE:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Check this document on handling IDOC acknowledgements. This might give you some idea.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Please check the above two links if u have missed anything in setting up the acknowledgement.Let me know if u need furthur information
Thanks,
Bhargav.
Note:Award points if found useful.

Idoc 2 File Scenario

Hi Experts,
I am doing Idoc to file scenario (bypass).
I got below error in sxmb_moni. Plz tell me what might be the proble?
Unable to convert the sender service BS1_SENDER to an ALE logical system

Hi Moorthy,
I am explaining my total scenari here.....
Its Bypass, Idoc to file.
I am sending idoc-xml as it is to receiver as file-xml.
I am not doing any IR objects.
I have configured ID (RD, ID & RA) objects.
I have used Idoc name(i.e Orders.Orders05) as Inbound & Outbound Interfaces.
But in SXMB_MONI, the error was showing as
<?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>
Please provide the solution.
Thanks in advance.

Error Resource not Found in SXMB_MONI while doing IDoc to File Scenario

Hi Experts,
I am doing IDoc to File Scenario and I am facing Following Error in SXMB_MONI,
<?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>Application</SAP:Category>
<SAP:Code area="MAPPING">RESOURCE_NOT_FOUND</SAP:Code>
<SAP:P1>193c0e01-bd37-11dd-850c-d879ac131b1f</SAP:P1>
<SAP:P2>http://clarityPOC</SAP:P2>
<SAP:P3>com/sap/xi/tf/_MM_Timesheets_iDocToFile_.class</SAP:P3>
<SAP:P4>-1</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have tested the same file in test tab of mapping, execution of mapping is successful there.
Regards,
Nitin Patil
Edited by: Nitin Patil on Dec 5, 2008 7:09 AM

Hi Dharmveer I have done the cache refresh ID in XI Data Cache Refresh using link
http://sapnbipoc:50000/rep/support/admin/index.html
but still same error persisting
and in Integration Builder> Environment>Cache Status Overview >Problem tab
following error (initial part of the error pasted) is shown
Thrown:
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Adapter Engine af.npi.sapnbipoc not found in SLD
 at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:56)
 at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:41)
 at com.sap.aii.ib.server.abapcache.logons.IR_LogonData.<init>(IR_LogonData.java:26)
Regards,
Nitin Patil

IDOC-BPM-FILE scenario ERRORS

Hi gurus,
I am trying to send IORDER01(pm order) from an R/3 system to a file, which works fine.
but when i try to use some business logic like if order type = 'PM01' then only i have to write to the file, using ccBPM, it fails...
this is my first BPM scenario and am having trouble....have read lot of blogs etc...can u please tell me where i am going wrong...
I have a data type DT_FILE for writing to the file.
I have interfaces:
si_oa_iorder(outbound asynchronous interface for file)
si_aa_iorder(abstract asynchronous interface for idoc)
si_aa_file( abstract asynchronous interface for file)
si_ia_file (inbound asynchronous interface for file)
I have message mapping MM_IORDER2FILE mapping IDoc to flat file structure
I have operation mapping OM_IORDER2FILE where I have mapped si_aa_iorder and si_aa_file
(( Is this right? are both abstract interfaces to be mapped? or do i need to create more mappings like si_oa_iorder to si_aa_iorder etc? please clarify...))
My IP is very simple with just a 'recv step' having container element of type si_aa_iorder and 'send step' having container element of type si_aa_file to start with..i haven't yet put the switch control etc...even such simple IP fails....
I have created Configuration objects like
Business System for file receiver
Business component for Idoc sender with adapter specific details set
Communication channels for Idoc and file adapters
No sender agreement as it is Idoc communication
Receiver agreement between the Integration Process(IP_IORDER2FILE) and the file server
2 Receiver determinations between BC_idoc_send to IP and other from IP to FileRecv system
2 interface determinations , one from si_oa_iorder of BC_idoc_send to IP and other from si_aa_file of IP to file recv system.
This is my setup and this fails....
My question is..is my message mapping and operation mappings correct? and can u see any obvious blunders i am doing?
please bear in mind that with same interfaces and sending and recv components, it runs fine without BPM....so please look at the BPM bit of mappings/config that i might have missed and please advice asap..
Thanks in advance and i am sure there would be lot of gurus for whome it is just a peanut...so please reply...
Regards
Jhansi

Hello,
I am trying to implement one pi scenario :
File -> file adapter -> ccBPM -> soap receiver adapter -> web service request -> web service response -> ccBPM -> output file adapter.
The web service that I call works file from wsnavigator. I have created all the design and configuration objects
needed for the scenario.
I place a file with following contents:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
 <pns:GetSetNameWS xmlns:pns="urn:file2soap2fileWSVi">
 <pns:name1>ajeet</pns:name1>
 <pns:name2>phadnis</pns:name2>
 </pns:GetSetNameWS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When I look at the process monitor I get this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists. Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists. No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have no clue about this error. Can you help me with this ?
If yes I can send you more details, if you liked 
Hoping to get help from you,
Cheers,
Ajeet Phadnis

Idoc to File scenario using Party

Hi All,
I have to configure Idoc to File scenario .This file needs to be posted in EDI Subsystem .My receiver partner type is LI.That means i need to use Party here.So please let me know the step by step solution to do this.Specially i want to know the configuration in Party Identifier and Receiver Communication channel Identifiers.
How the control record values from idoc are transferred to EDI File structure and how will XI identify one of the many customers to post the file.
All valuable suggestions will be rewarded the points.
Please send me the documents for such scenario with screen shots.

Hi,
Let me see if I had you requirement correct.
When the Idoc is sent from R3, sender partner type is LS and Receiver Partner Type is LI.
If yes,
1. Create a Party in ID.
2. The Agency , Scheme and Identifier will have values,
Agency --> Receiver Business System name or Business Service Name to be used for File.
Scheme --> ALE#LI
Identiier --> Value of the RCVPRN field in the idoc control Record. Basically the Receiver Partner Name.
All the Configuration In ID will use this Party as the Receiver Party and the corresponding Service asthe Receiver service.
No need for a sender party as sender partner is LS.
Regards
Bhavesh

XML Validation using custom DTD file

Well, I thought that my problem is about to be a trivial one, but now, I don't think so. I have to develop XML-based protocol over HTTP. XML Document doesn't contain any reference to DTD, but I have some DTDs. I want to validate my XML messages in real time and I want to find some library that allows to do something like that:
SomeXmlValidatingParser s = new SomeXmlValidatingParser(InputStream dtdFileStream);
for(;;)
 InputStream is = message.recive();
 DocumentObject = s.parseAndValidate(is);
}So, the issue is to pass my custom DTD file (it is already loaded to memory) into validating parser.
So, which library have such functionality? And if there are some, could you be so kind to advice some of them?

Well, I've just realized that JDK 1.5 has standard way to validate XMLs using XSD schemas. Ok. But look at the sample
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
 schemaLocation="http://www.w3.org/2001/xml.xsd" />
<xs:element name="birthdate">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="month" type="xs:string" />
 <xs:element name="day" type="xs:int" />
 <xs:element name="year" type="xs:int" />
 </xs:sequence>
 </xs:complexType>
</xs:element>
</xs:schema>Every time I process this schema, it goes to w3c.org... And I wonder if it cause some problems if I delete
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
 schemaLocation="http://www.w3.org/2001/xml.xsd" />

Idoc - DTD file - schema

Similar Messages

Maybe you are looking for