Incorrect XML format for outbound binding

Hi,
I am in the process of configuring a scenario where we are sending PO's from SRM to XI in XML format and later we want these PO's in XML format to be sent to a vendor. I am able to send the XML from SRM to XI, but I get the following error message (probably while sending the XML to the external application):
Incorrect XML format for outbound binding , , NO_TO_SERVICE_NAME, MI_Order_CreateOrChangeVendorView_In, urn:poscenario:srm:xi:vendor
Unable to find element OutboundBindingAttributes: Node DY1WebMethodsMI_Order_CreateOrChangeVendorView_Inurn:poscenario:srm:xi:vendor8f16f906899838c7a4b64634e8140706686c72620ed63ed28c12a634f905d0ce.
You help will be highly appreciated.
Regards,
Ravinder Masuta

Hi Tanja,
Now I tried to use the XI channel and I become the same problems. Maybe me configure of the "Receiver Agreement" is wrong.
sender-service      A1CLNT100
receiver-service    A2CLNT100
receiver-Interface: ORDERS.ORDERS05
namespace:          urn:sap-com:document:sap:idoc:messages
communication channel : IDOC
But without the IDOC-channel I become this error message:
OUTBOUND_BINDING_NOT_FOUND --- no Receiver Agreement found
Regards
Christoph

Similar Messages

Incorrect XML disply for ALERTCATEGORY error during deserialization data lo

Hi,
I am getting below error while executing first scenario in Quality enviornment, i have not defined and trasported any ALERTS.
Incorrect XML disply for ALERTCATEGORY error during deserialization data loss occured when converting 011136c23c9430359b57c0ef8949c630
this error stoping my interface executing...did anyone experienced this issue??
put some light on this.
many thanks,
Raj

Have you checked this SAP Note # 1394710 ?

XML format for Acrobat JavaScript

Hi,
This is my first posting to any Adobe forum, so please bear with me...
I'm interested in the XML format for Acrobat JavaScript. I'll be using an external editor (UltraEdit). When I do (in Acrobat 8) Advanced-->Document Processing-->Edit All JavaScripts, UltraEdit starts off with this:
//-----------------Do not edit the XML tags--------------------
Interesting, but not very useful. If I look at some existing PDF files containing JavaScript, I see things like:
//-----------------Do not edit the XML tags--------------------
//<Document-Level>
//<ACRO_source>DocOpen</ACRO_source>
//<ACRO_script>
/*********** belongs to: Document-Level:DocOpen ***********/
OK, this is better. In fact, if I look at enough existing PDF files containing JavaScript, I could probably figure out the XML format by myself, including the XML format of tags like <Page-Actions>, <AcroForm>, etc. However, it would be far easier to get the specification of the JavaScript XML format -- for example, what is the format of the text following the "belongs to:" string within the various types of XML tags?
I *presume* this is documented somewhere but I couldn't find it. If someone has the Acrobat JavaScript XML format specification, it would be greatly appreciated.
Thanks.
Dave
P.S. Another possible approach would be to create JavaScripts myself using Advanced-->Document Processing-->Document JavaScripts, and then see what XML is created based on the code I enter into the GUI, e.g. form code, functions, etc. This also seems somewhat inefficient, presuming again that the JavaScript XML format is already documented.

Thanks for the additional information.
I played with JavaScript some more, using my preferred editor, UltraEdit, which I attached to Acrobat. I thought I would be able to take a JavaScript program from one PDF file (source file) and do a copy & paste into another PDF file (destination file). While I can do the paste (again, via UltraEdit) into the destination file and can do an UltraEdit Save, when I go back into UltraEdit via Advanced --> Document Processing --> Edit All JavaScripts, the JavaScript I pasted from the source file to the destination file isn't there in the destination file.
From this, I concluded that I'll need to create the Document-level JavaScript and the form field Javascripts (e.g. a JavaScript triggered by a "Mouse Down" in a button) via the Acrobat GUI's. Acrobat doesn't seem to like it if I bypass the GUIs and just attempt to paste the code directly into the PDF file via an editor. By not using the GUI and just doing the cut & paste as I did, I'm probably missing some part of the code setup/creation process that Acrobat needs to know about.
This is why I originally asked about the syntax for the pseudo-XML, thinking I could just copy the pseudo-XML/JavaScript code from one PDF file to another, and then modify the code to reflect the needs of the destination PDF. Now I understand the need you mentioned to use the Acrobat GUIs to set up the initial XML/JavaScript structure.
Once I have the XML structure set up in the destination file (e.g. a JavaScript triggered by a "Mouse Down" in a button), I can obviously copy code snippets into that <AcroForm> sections, I just can't *create* the original "Mouse Down" <AcroForm> sections via the editor.
Another approach I could follow would be to make a copy of the original source file and change the name of the copy to the desired destination file name, and then start modifying the code in the new (destination) file -- presuming that's the easiest path to get the desired functionality created. This way, I wouldn't have to manually (via the Acrobat GUI) create all of the <Document-Level> and <AcroForm> sections.
Thanks for your (and others') help, let me know if I'm missing anything.
Dave

What is the XML format for Sub Agreements?

Hi,
We have requirement to automate loading Master Agreements and Sub Agreements into CLM from a non-SAP system.
Currently the data is loaded using CSV files, but Double Byte Char. is not supported in CSV file format.
I am trying to load using XML format and have be successful to load Master Agreement.
I need help with Sub Agreement XML Structure or a better alternative to load Sub Agreement metadata containing Double Byte Char.
Provided below is the Sub Agreement XML Structure. Please provide suggestions or guidance on this issue.
We are on 7.0 SP8 .
Thanks
Sai

Hi Prasad,
Thanks for your quick response.
I am able to load successfully Project and Master Agreement in XML format with metadata containing multibyte char.
Multibyte char is displayed on Project and Master Agreement Screen.
English , German, Chinese, Japanese, Korean, Spanish, French and Italian language packs are installed in Sourcing.
I am getting below error while importing XML for Sub Agreement.
Record 1. Warning: XML import could not process field: CONTRACT_UNIQUE_DOC_NAME
Facility=local4;sessionid=bR6bHsKNs_s_sA8ihHdOSyOASPCvRgEP3icA_SAP;tenantid=#ebay#;username=sguntaka;exception=java.lang.IllegalArgumentException: unsupported null bind parameter no. 0 found in statement SELECT OBJECTID, CONTEXTID, REVISION_COUNT, UNIQUE_DOC_NAME, DISPLAY_NAME, COLLN_METADATA, RESERVATION_LOCK, DOCUMENT_DESCRIPTION, CREATED_BY_USER_OBJECT_ID, CREATED_BY_USER_CLASS_ID, CREATED_BY_USER_OBJECT_NAME, MODIFIED_BY_USER_OBJECT_ID, MODIFIED_BY_USER_CLASS_ID, MODIFIED_BY_USER_OBJECT_NAME, EDIT_BY_USER_OBJECT_ID, EDIT_BY_USER_CLASS_ID, EDIT_BY_USER_OBJECT_NAME, CREATED_AT, MODIFIED_AT, EDIT_AT_DATETIME, INACTIVE, TRACK_CHANGES, COLLABORATION_POLICY, HAS_PUBLIC_DISC, IS_TEMPLATE, CANCELED_BY_USER_OBJECT_ID, CANCELED_BY_USER_CLASS_ID, CANCELED_BY_USER_OBJECT_NAME, DOC_OWNER_USER_OBJECT_ID, DOC_OWNER_USER_CLASS_ID, DOC_OWNER_USER_OBJECT_NAME, CLOSED_BY_USER_OBJECT_ID, CLOSED_BY_USER_CLASS_ID, CLOSED_BY_USER_OBJECT_NAME, CANCELED_AT, CLOSED_AT, TEMPLATE_OBJECT_ID, TEMPLATE_CLASS_ID, TEMPLATE_OBJECT_NAME, DOC_TYPE_OBJECT_ID, DOC_TYPE_CLASS_ID, DOC_TYPE_OBJECT_NAME, BASE_DATE_DATE, SCHEDULE_WORK_DAYS, BUSINESS_UNIT_OBJECT_ID, BUSINESS_UNIT_CLASS_ID, BUSINESS_UNIT_OBJECT_NAME, COMPANY_OBJECT_ID, COMPANY_CLASS_ID, COMPANY_OBJECT_NAME, ESTIMATED_CURRENCY, ESTIMATED_OBJECT_ID, ESTIMATED_PRICE, BUDGETED_CURRENCY, BUDGETED_OBJECT_ID, BUDGETED_PRICE, CURRENCY_OBJECT_ID, CURRENCY_CLASS_ID, CURRENCY_OBJECT_NAME, VENDOR_VISIBLE, DATE_TO_PUBLISH_DATE, LOCK_BASELINE, LI_PERIOD_TYPE_OBJECT_ID, LI_PERIOD_TYPE_CLASS_ID, LI_PERIOD_TYPE_OBJECT_NAME, CALC_METHOD, SPEC_ID_COUNT, ATTR_ID_COUNT, FORMULA_ID_COUNT, PURCHASING_ORG_OBJECT_ID, PURCHASING_ORG_CLASS_ID, PURCHASING_ORG_OBJECT_NAME, PURCHASING_GRP_OBJECT_ID, PURCHASING_GRP_CLASS_ID, PURCHASING_GRP_OBJECT_NAME, TRANSACTION_TYPE_OBJECT_ID, TRANSACTION_TYPE_CLASS_ID, TRANSACTION_TYPE_OBJECT_NAME, COMPANY_CODE_OBJECT_ID, COMPANY_CODE_CLASS_ID, COMPANY_CODE_OBJECT_NAME, INTEGRATED_TYPE, USE_ERP_VALIDATION, STORAGE_LOCATION, RECORD_SERIES, RETENTION_DATE_DATE, RETENTION_REMINDER_DATE_DATE, RETENTION_EVENT_OBJECT_ID, RETENTION_EVENT_CLASS_ID, RETENTION_EVENT_OBJECT_NAME, EFFECTIVE_DATE_DATE, EXPIRATION_DATE_DATE, TERMIN_NOTICE_LEAD_TIME, TERMIN_COMMU_DATE, PERPETUAL_TERM, AUTO_RENEWAL, EVENT_OBJECT_ID, EVENT_CLASS_ID, EVENT_OBJECT_NAME, RENEWAL_REMINDER_DATE, VENDOR_OBJECT_ID, VENDOR_CLASS_ID, VENDOR_OBJECT_NAME, CONTACT_OBJECT_ID, CONTACT_CLASS_ID, CONTACT_OBJECT_NAME, LOCATION_OBJECT_ID, LOCATION_CLASS_ID, LOCATION_OBJECT_NAME, PAYTERMS_OBJECT_ID, PAYTERMS_CLASS_ID, PAYTERMS_OBJECT_NAME, REPLENISHMENT_OBJECT_ID, REPLENISHMENT_CLASS_ID, REPLENISHMENT_OBJECT_NAME, VENDOR_ACCT_NUM, INT_CAT_OBJECT_ID, INT_CAT_CLASS_ID, INT_CAT_OBJECT_NAME, EXT_CAT_OBJECT_ID, EXT_CAT_CLASS_ID, EXT_CAT_OBJECT_NAME, EVALUATION_CRITERIA, NEXT_AUDIT_DATE, LAST_AUDIT_DATE, TOTAL_EXPECTED_CURRENCY, TOTAL_EXPECTED_OBJECT_ID, TOTAL_EXPECTED_PRICE, TOTAL_BUDGETED_CURRENCY, TOTAL_BUDGETED_OBJECT_ID, TOTAL_BUDGETED_PRICE, TOTAL_ACTUAL_CURRENCY, TOTAL_ACTUAL_OBJECT_ID, TOTAL_ACTUAL_PRICE, TOTAL_SAVINGS_CURRENCY, TOTAL_SAVINGS_OBJECT_ID, TOTAL_SAVINGS_PRICE, TOTAL_COST_SAVINGS_CURRENCY, TOTAL_COST_SAVINGS_OBJECT_ID, TOTAL_COST_SAVINGS_PRICE, TOTAL_COST_AVOIDANCE_CURRENCY, TOTAL_COST_AVOIDANCE_OBJECT_ID, TOTAL_COST_AVOIDANCE_PRICE, PERF_EVAL_CRITERIA, PERF_LAST_UPDATE_DATE, PERF_NEXT_UPDATE_DATE, BUYER_SEARCHABLE, VAL_PERIOD_TYPE_OBJECT_ID, VAL_PERIOD_TYPE_CLASS_ID, VAL_PERIOD_TYPE_OBJECT_NAME, INCLUDE_PART_NUMBER, TOTAL_ACTUAL_SPEND_CURRENCY, TOTAL_ACTUAL_SPEND_OBJECT_ID, TOTAL_ACTUAL_SPEND_PRICE, FORECAST_SPEND_CURRENCY, FORECAST_SPEND_OBJECT_ID, FORECAST_SPEND_PRICE, ACTUAL_LIMIT_PCT, FORECAST_LIMIT_PCT, LINEITEM_ID_CNT, LIMIT_VALUE_CURRENCY, LIMIT_VALUE_OBJECT_ID, LIMIT_VALUE_PRICE, MINIMUM_VALUE_CURRENCY, MINIMUM_VALUE_OBJECT_ID, MINIMUM_VALUE_PRICE, MINIMUM_DAYS_OFFSET, MARGIN_PRICING, DELETED_AT_DATETIME, DELETED_BY_OBJECT_ID, DELETED_BY_CLASS_ID, DELETED_BY_OBJECT_NAME, CTR_IS_DUET, HAS_DUET_ITEMS, WORD_ATTRIBUTES_TEXT_PREVIEW, WORD_ATTRIBUTES_TEXT_OBJECT_ID, WORD_ATTRIBUTES_TEXT_CLASS_ID, WORD_ATTRIBUTES_CHECKSUM, SENT_TO_ERP_DATETIME, STATUS_OBJECT_ID, STATUS_CLASS_ID, STATUS_OBJECT_NAME, LAST_SPEND_IMPORT_DATE, BUYER_SPECS_SUPPORT, VENDOR_SPECS_SUPPORT FROM clmuser.FCI_CONTRACT WHERE UNIQUE_DOC_NAME = ? AND CONTEXTID = ?;stacktrace=java.lang.IllegalArgumentException: unsupported null bind parameter no. 0 found in statement SELECT OBJECTID, CONTEXTID, REVISION_COUNT, UNIQUE_DOC_NAME, DISPLAY_NAME, COLLN_METADATA, RESERVATION_LOCK, DOCUMENT_DESCRIPTION, CREATED_BY_USER_OBJECT_ID, CREATED_BY_USER_CLASS_ID, CREATED_BY_USER_OBJECT_NAME, MODIFIED_BY_USER_OBJECT_ID, MODIFIED_BY_USER_CLASS_ID, MODIFIED_BY_USER_OBJECT_NAME, EDIT_BY_USER_OBJECT_ID, EDIT_BY_USER_CLASS_ID, EDIT_BY_USER_OBJECT_NAME, CREATED_AT, MODIFIED_AT, EDIT_AT_DATETIME, INACTIVE, TRACK_CHANGES, COLLABORATION_POLICY, HAS_PUBLIC_DISC, IS_TEMPLATE, CANCELED_BY_USER_OBJECT_ID, CANCELED_BY_USER_CLASS_ID, CANCELED_BY_USER_OBJECT_NAME, DOC_OWNER_USER_OBJECT_ID, DOC_OWNER_USER_CLASS_ID, DOC_OWNER_USER_OBJECT_NAME, CLOSED_BY_USER_OBJECT_ID, CLOSED_BY_USER_CLASS_ID, CLOSED_BY_USER_OBJECT_NAME, CANCELED_AT, CLOSED_AT, TEMPLATE_OBJECT_ID, TEMPLATE_CLASS_ID, TEMPLATE_OBJECT_NAME, DOC_TYPE_OBJECT_ID, DOC_TYPE_CLASS_ID, DOC_TYPE_OBJECT_NAME, BASE_DATE_DATE, SCHEDULE_WORK_DAYS, BUSINESS_UNIT_OBJECT_ID, BUSINESS_UNIT_CLASS_ID, BUSINESS_UNIT_OBJECT_NAME, COMPANY_OBJECT_ID, COMPANY_CLASS_ID, COMPANY_OBJECT_NAME, ESTIMATED_CURRENCY, ESTIMATED_OBJECT_ID, ESTIMATED_PRICE, BUDGETED_CURRENCY, BUDGETED_OBJECT_ID, BUDGETED_PRICE, CURRENCY_OBJECT_ID, CURRENCY_CLASS_ID, CURRENCY_OBJECT_NAME, VENDOR_VISIBLE, DATE_TO_PUBLISH_DATE, LOCK_BASELINE, LI_PERIOD_TYPE_OBJECT_ID, LI_PERIOD_TYPE_CLASS_ID, LI_PERIOD_TYPE_OBJECT_NAME, CALC_METHOD, SPEC_ID_COUNT, ATTR_ID_COUNT, FORMULA_ID_COUNT, PURCHASING_ORG_OBJECT_ID, PURCHASING_ORG_CLASS_ID, PURCHASING_ORG_OBJECT_NAME, PURCHASING_GRP_OBJECT_ID, PURCHASING_GRP_CLASS_ID, PURCHASING_GRP_OBJECT_NAME, TRANSACTION_TYPE_OBJECT_ID, TRANSACTION_TYPE_CLASS_ID, TRANSACTION_TYPE_OBJECT_NAME, COMPANY_CODE_OBJECT_ID, COMPANY_CODE_CLASS_ID, COMPANY_CODE_OBJECT_NAME, INTEGRATED_TYPE, USE_ERP_VALIDATION, STORAGE_LOCATION, RECORD_SERIES, RETENTION_DATE_DATE, RETENTION_REMINDER_DATE_DATE, RETENTION_EVENT_OBJECT_ID, RETENTION_EVENT_CLASS_ID, RETENTION_EVENT_OBJECT_NAME, EFFECTIVE_DATE_DATE, EXPIRATION_DATE_DATE, TERMIN_NOTICE_LEAD_TIME, TERMIN_COMMU_DATE, PERPETUAL_TERM, AUTO_RENEWAL, EVENT_OBJECT_ID, EVENT_CLASS_ID, EVENT_OBJECT_NAME, RENEWAL_REMINDER_DATE, VENDOR_OBJECT_ID, VENDOR_CLASS_ID, VENDOR_OBJECT_NAME, CONTACT_OBJECT_ID, CONTACT_CLASS_ID, CONTACT_OBJECT_NAME, LOCATION_OBJECT_ID, LOCATION_CLASS_ID, LOCATION_OBJECT_NAME, PAYTERMS_OBJECT_ID, PAYTERMS_CLASS_ID, PAYTERMS_OBJECT_NAME, REPLENISHMENT_OBJECT_ID, REPLENISHMENT_CLASS_ID, REPLENISHMENT_OBJECT_NAME, VENDOR_ACCT_NUM, INT_CAT_OBJECT_ID, INT_CAT_CLASS_ID, INT_CAT_OBJECT_NAME, EXT_CAT_OBJECT_ID, EXT_CAT_CLASS_ID, EXT_CAT_OBJECT_NAME, EVALUATION_CRITERIA, NEXT_AUDIT_DATE, LAST_AUDIT_DATE, TOTAL_EXPECTED_CURRENCY, TOTAL_EXPECTED_OBJECT_ID, TOTAL_EXPECTED_PRICE, TOTAL_BUDGETED_CURRENCY, TOTAL_BUDGETED_OBJECT_ID, TOTAL_BUDGETED_PRICE, TOTAL_ACTUAL_CURRENCY, TOTAL_ACTUAL_OBJECT_ID, TOTAL_ACTUAL_PRICE, TOTAL_SAVINGS_CURRENCY, TOTAL_SAVINGS_OBJECT_ID, TOTAL_SAVINGS_PRICE, TOTAL_COST_SAVINGS_CURRENCY, TOTAL_COST_SAVINGS_OBJECT_ID, TOTAL_COST_SAVINGS_PRICE, TOTAL_COST_AVOIDANCE_CURRENCY, TOTAL_COST_AVOIDANCE_OBJECT_ID, TOTAL_COST_AVOIDANCE_PRICE, PERF_EVAL_CRITERIA, PERF_LAST_UPDATE_DATE, PERF_NEXT_UPDATE_DATE, BUYER_SEARCHABLE, VAL_PERIOD_TYPE_OBJECT_ID, VAL_PERIOD_TYPE_CLASS_ID, VAL_PERIOD_TYPE_OBJECT_NAME, INCLUDE_PART_NUMBER, TOTAL_ACTUAL_SPEND_CURRENCY, TOTAL_ACTUAL_SPEND_OBJECT_ID, TOTAL_ACTUAL_SPEND_PRICE, FORECAST_SPEND_CURRENCY, FORECAST_SPEND_OBJECT_ID, FORECAST_SPEND_PRICE, ACTUAL_LIMIT_PCT, FORECAST_LIMIT_PCT, LINEITEM_ID_CNT, LIMIT_VALUE_CURRENCY, LIMIT_VALUE_OBJECT_ID, LIMIT_VALUE_PRICE, MINIMUM_VALUE_CURRENCY, MINIMUM_VALUE_OBJECT_ID, MINIMUM_VALUE_PRICE, MINIMUM_DAYS_OFFSET, MARGIN_PRICING, DELETED_AT_DATETIME, DELETED_BY_OBJECT_ID, DELETED_BY_CLASS_ID, DELETED_BY_OBJECT_NAME, CTR_IS_DUET, HAS_DUET_ITEMS, WORD_ATTRIBUTES_TEXT_PREVIEW, WORD_ATTRIBUTES_TEXT_OBJECT_ID, WORD_ATTRIBUTES_TEXT_CLASS_ID, WORD_ATTRIBUTES_CHECKSUM, SENT_TO_ERP_DATETIME, STATUS_OBJECT_ID, STATUS_CLASS_ID, STATUS_OBJECT_NAME, LAST_SPEND_IMPORT_DATE, BUYER_SPECS_SUPPORT, VENDOR_SPECS_SUPPORT FROM clmuser.FCI_CONTRACT WHERE UNIQUE_DOC_NAME = ? AND CONTEXTID = ?
at com.sap.odp.common.db.AbstractDb.findWhere(AbstractDb.java:5823)
at com.sap.odp.common.db.AbstractDb.findWhere(AbstractDb.java:5760)
at com.sap.eso.contracts.ContractHome.findUniqueByDocName(ContractHome.java:96)
at com.sap.eso.contracts.importer.processors.AgreementProcessor.createNewHook(AgreementProcessor.java:479)
at com.sap.odp.doc.importer.AbsDocImportProcessor.processRow(AbsDocImportProcessor.java:165)
at com.sap.odp.common.install.dataimport.csv.CsvFileProcessor.processRowInternal(CsvFileProcessor.java:1370)
at com.sap.odp.common.install.dataimport.csv.CsvFileProcessor.processFile(CsvFileProcessor.java:281)
at com.sap.odp.common.install.dataimport.xml.XmlImporter.importXmlObject(XmlImporter.java:249)
at com.sap.odp.common.install.dataimport.xml.XmlImportHandler.endElement(XmlImportHandler.java:155)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:176)
at com.sap.odp.common.install.dataimport.xml.ImportXmlReader.importObjects(ImportXmlReader.java:141)
at com.sap.odp.common.install.dataimport.xml.ImportXmlReader.parse(ImportXmlReader.java:84)
at com.sap.odp.common.install.dataimport.xml.ImportXmlReader.parse(ImportXmlReader.java:73)
at com.sap.odp.common.install.dataimport.xml.XmlImporter.go(XmlImporter.java:164)
at com.sap.odp.install.actions.ProcessXmlImportFile.executeHook(ProcessXmlImportFile.java:170)
at com.sap.odp.install.actions.InstallAction.execute(InstallAction.java:203)
at com.sap.odp.install.engine.ScriptedImportEngine.runSingleItem(ScriptedImportEngine.java:319)
at com.sap.odp.install.engine.XmlImportEngine.execute(XmlImportEngine.java:128)
at com.sap.odp.install.imports.ImportController$ImportRunner.execute(ImportController.java:302)
at com.sap.odp.install.imports.ImportController$ImportRunner.run(ImportController.java:212)
at java.lang.Thread.run(Thread.java:708)
Let me know if you need additional details.
Regards
Sai

XML format for input to BPEL process from client stub

Hi,
I have deployed SyncHelloWorld BPEL process as given in the tutorial in the BPEL Server. It is working fine. Now I am trying to invoke the process by creating a Java client stub . I created a stub using the Web-services wizard by specifying the WSDL of the BPEL. Now I want to know how to pass some string through XML document to the BPEL process.
I am using this code in the main method of the stub., but the value is not being passed to the BPEL nodes correctly. the output I am getting is "Hello "
and not "Hello XYZString". I think I am not able to form the XML document to pass as input correctly. Can anyone help.
Can anyone please help :
public static void main(String[] args)
try
SyncHelloWorldStub stub = new SyncHelloWorldStub();
// Add your own code here.
// Create an empty XML document
XMLDocument doc = new XMLDocument();
// Create an element
Element body = doc.createElementNS("http://xmlns.oracle.com/SyncHelloWorld", "SyncHelloWorldProcessRequest");
// Create the inner element
Element ip = doc.createElementNS("http://xmlns.oracle.com/SyncHelloWorld", "input");
// Create a text node
Text text = doc.createTextNode("input");
// Set the input parameter
text.setNodeValue("XYZString");
ip.appendChild(text);
body.appendChild(ip);
// Call the process. It returns a vector
Vector v = stub.process(body);
// Code to print the returned xml.
System.out.println("Received " + v.size() + " element");
Enumeration enum = v.elements();
// Walk through the vector and print out contents
while (enum.hasMoreElements())
Object o = enum.nextElement();
System.out.println("Returned a " + o.getClass().getName());
//If it is an element, print it out
if (o instanceof XMLElement)
XMLElement xml = (XMLElement)o;
xml.print(System.out);
else
System.out.println("Returned " + o.toString());
System.out.println("After executing : "+v.toString());
catch(Exception ex)
ex.printStackTrace();
This is the code for WSDL file for the BPEL process.
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="SyncHelloWorld" targetNamespace="http://xmlns.oracle.com/SyncHelloWorld" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/SyncHelloWorld" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:client="http://xmlns.oracle.com/SyncHelloWorld">
- <types>
- <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/SyncHelloWorld" xmlns="http://www.w3.org/2001/XMLSchema">
- <element name="SyncHelloWorldProcessRequest">
- <complexType>
- <sequence>
<element name="input" type="string" />
</sequence>
</complexType>
</element>
- <element name="SyncHelloWorldProcessResponse">
- <complexType>
- <sequence>
<element name="result" type="string" />
</sequence>
</complexType>
</element>
</schema>
</types>
- <message name="SyncHelloWorldRequestMessage">
<part name="payload" element="tns:SyncHelloWorldProcessRequest" />
</message>
- <message name="SyncHelloWorldResponseMessage">
<part name="payload" element="tns:SyncHelloWorldProcessResponse" />
</message>
- <portType name="SyncHelloWorld">
- <operation name="process">
<input message="tns:SyncHelloWorldRequestMessage" />
<output message="tns:SyncHelloWorldResponseMessage" />
</operation>
</portType>
- <binding name="SyncHelloWorldBinding" type="tns:SyncHelloWorld">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="process">
<soap:operation style="document" soapAction="process" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
</binding>
- <service name="SyncHelloWorld">
- <port name="SyncHelloWorldPort" binding="tns:SyncHelloWorldBinding">
<soap:address location="http://cisoidd001.corporate.ge.com:5843/orabpel/default/SyncHelloWorld/v2006_06_19__40924" />
</port>
</service>
- <plnk:partnerLinkType name="SyncHelloWorld">
- <plnk:role name="SyncHelloWorldProvider">
<plnk:portType name="tns:SyncHelloWorld" />
</plnk:role>
</plnk:partnerLinkType>
</definitions>
Also, while running the BPEL process from console, we can give the input as html or string. Can anyone give the me xml format of the input.
Any help would be highly appreciated.
Thanks,
Debojyoty

Your last question shows that you might have solved this by now.
The xml document you are composing in java might not exactly be the xml input bpel excepts. The way to compare is first initiate a process by posting an html message, using the initiate tab for your process in the BPEL console. Check the box "Save as default input" before you send the html request.
Then again do an initiate from the BPEL console and select "XML Source" instead of "HTML Form". You will see the xml message you just have sent as html.
You might also want to test your java program with one of the many free soap clients available on the internet.
HTH,
Ruerd
http://www.numericalexample.com

How to generate Campaign details in XML format for sending to downstream sy

Dear gurus,
we have a requirement to send the Campaign details from CRM to some Downstream system in the XML format through PI interfaces. We want to include the following campaign details in the structure.
<SAPTOAL DATE="03-MAR-2011" TIME="13:25pm">
      <CAMPAIGN>
            <ID></ID>
            <NAME></NAME>
            <RUNDATE></RUNDATE>
            <RUNTIME></RUNTIME>
            <STARTDATE></STARTDATE>
            <ENDDATE></ENDDATE>
            <RECORDCOUNT></RECORDCOUNT>
      </CAMPAIGN>
      <TARGETGROUP>
            <ID></ID>
            <NAME></NAME>
</TARGETGROUP>
      <BUSINESSPARTNERS>
            <BUSINESSPARTNER>
                  <ID>001</ID>
            <TARGETGROUPID></TARGETGROUPID>
            <FIRSTNAME></FIRSTNAME>
                  <LASTNAME></LASTNAME>
                  <TITLE></TITLE>
                  <SUFFIX></SUFFIX>
                  <EMAIL></EMAIL>
                  <REPFIRSTNAME></REPFIRSTNAME>
                  <REPLASTNAME></REPLASTNAME>
                  <REPPHONE></REPPHONE>
                  <REPSIGNATUREURL></REPSIGNATUREURL>
                  <REPPICTUREURL></REPPICTUREURL>
                  <REPEMAIL></REPEMAIL>
            </BUSINESSPARTNER>
            <BUSINESSPARTNER>
                  <ID>002</ID>
            <TARGETGROUPID></TARGETGROUPID>
                  <FIRSTNAME></FIRSTNAME>
                  <LASTNAME></LASTNAME>
                  <TITLE></TITLE>
                  <SUFFIX></SUFFIX>
                  <EMAIL></EMAIL>
                  <REPFIRSTNAME></REPFIRSTNAME>
                  <REPLASTNAME></REPLASTNAME>
                  <REPPHONE></REPPHONE>
                  <REPSIGNATUREURL></REPSIGNATUREURL>
                  <REPPICTUREURL></REPPICTUREURL>
                  <REPEMAIL></REPEMAIL>
            </BUSINESSPARTNER>
      </BUSINESSPARTNERS>
</SAPTOAL>
We have already tried the following things in SPRO.
CRM --> Marketing --> Marketing Planning and Campaign Management --> Campaign Execution --> Define File Export Variants
But with this we were not able to get the full XML structure, as required above. We got only this much.
<?xml version="1.0" encoding="utf-8" ?>
<DATA>
<ITEM>
   <Field_1>Test Email.</Field_1>
   <Field_2>Test Email.</Field_2>
   <Field_3>ABC Company.</Field_31>
</ITEM>
</DATA>
Any pointers or help on this will he greatly appreciated.rgrds,
Randhir Soni

Hi Prabhu,
The program SAPFPAYM generates the payment Medium on the basis of your configuration and background settings, this program does not bydefault give the output in the XML.
Varient creation for the PMW in T. Code OBPM4, use the same program, which i already done it, even without this it is not be possible to create any payment Medium.
Regards,
Rony

Output from Concurrent program in XML format for bytes greater than 32K

Hi,
I created a custom concurrent program where i send the generated XML data as an output to the program.
I have an XML template attached to the program, so the template picks up the xml output and converts it to a PDF.
so ultimately when i run the concurrent program, the output is a PDF file. This way it is easy for the user to just run a program and get a PDF file.
Now the generated XML data is from an oracle seeded program and it is a BLOB.
I am converting it to a CLOB so that i can write it to the output. if the CLOB doesnt exceed 32K bytes, i have no issues writing it to the output.
But since we cannot write more than 32K bytes, i an using a substr to write chunks of the CLOB for every 30,000 bytes.
since it is chunking at every 30,000 bytes the next 30,000 bytes are coming in the next line and XML publisher is throwing an error with invalid character.
Any idea how i can overcome this?
Either i write the whole 33000+ bytes in one line to the fnd output or try to remove the line breaks from the xml data.
Thanks in advance for anyone reading this!

>
> since it is chunking at every 30,000 bytes the next 30,000 bytes are coming in the next line and XML publisher is throwing an error with invalid character.
Any idea how i can overcome this?So I suppose you're using FND_FILE.PUT_LINE ?
Why not use FND_FILE.PUT instead, so that no new line is generated after each chunk ?
http://docs.oracle.com/cd/E18727_01/doc.121/e12897/T302934T458258.htm#I_fndfile

-info XML format for Compressor's command line interface?

Hi Everyone,
I've got a brand new copy of Final Cut Studio HD that I'm using for an encoding project. I'm trying to figure out how to use Compressor's command line interface. I want to give it a MPEG-2 file and a .scc (closed caption) file. I can see how to specify the source file, but I'm having trouble figuring out how to specify the SCC file. As best as I can understand, I'm going to need to use the -info <XML> option, but I haven't found any documentation for this. Can someone point me to the appropriate documentation?
Thanks!
- Kevin

I get an error when I do exactly what you suggested. My problem is not if the XSU is able to locate the xml file because I know it is able to parse it since it picks up an error in it such as if I make the "ROW" element "row" - ie small caps instead of big which is not recognised by XSU. I use the url of the xml file as specified when I open the xml file in internet explorer. The XSU does confirm it inserts the document successfully with my original command but the document simply doesn't get inserted into the table. Specifically, if anyone is to insert the xml file I have shown in Oracle, how would it be approached successfully?
Your help is very much appreciated.

CCM. Data upload SAP XML Format for CatalogueUpdateNotification

Hi everybody
Could anyone send me a SAP XML file example for CatalogueUpdateNotification?
My email [email protected]
Thanks in advance.
Raúl.

Hi Raul,
Sent.
Hope it will be useful.
and you can give me points.
BR
Dinesh

Help required on XML format for Sourcing system

Hi All,
We are Integrating PI with SAP Sourcing and Sourcing is expecting the XML in below structure.
XML Required by the target system:
<?xml version="1.0" encoding="UTF-8"?>
<sapesourcing defaultlanguage="" xsi:noNamespaceSchemaLocation="Locations.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <objects>
<object classname="">
            <fields>
Field1....n
            </fields>
        </object>
      </objects>
</sapesourcing>
I have converted the XML in to XSD and imported in to PI, but I have no idea how to Populate the tag as it required by Sourcing system
tag must be required by sourcing system is:
"<sapesourcing defaultlanguage="" xsi:noNamespaceSchemaLocation="Locations.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Mapping generates below tag :
<?xml version="1.0" encoding="UTF-8"?>
<sapesourcing defaultlanguage=""> ........
Regards,
Mani

Hi Mani,
Try to add the xml tag using XSLT mapping. Go through with the below link.
add Namespace in message mapping | SCN
Thanks,
Satish.

Exchange 2003 SMTP resolves to incorrect MX record for Outbound emails

Starting October 2007, we have encountered numerous incidents where users complaint that they can not send emails to randomly with Relayed Denied error.
First we thought the problem is with the receipient servers, but after reviewing the SMTP log intensively, I have noticed that the SMTP service on Exchange Server 2003 SP2 tries to send out emails to wrong IP Addresses (instead of sending out to listed IP of MX record, it tries to send to primary domain IP address).
To test further, we have changed the DNS server of the Exchange Server to public DNS service provided by the ISPs and still received same result.
If the user tries to send the email again (from the bounced back message), it some times goes through.
Has anyone know what the problem is?
Have checked the server configuration, DNS configuration, ran all updates, and yet still same result. Is one of the Microsoft Updates causing this issue?

Here is the official explanation i got from MS, sounds like it is doing what they expect it to do.
Problem Description
When Exchange 2003 sends e-mail to the Internet using DNS to resolve external domain names a DNS query is done for the remote domain's MX records. In the event that the initial MX query returns a "server failure", Exchange 2003 will fall back to a DNS A record query. If this query is, in turn, successful and there is an A record for the domain in question that happens to be listening on port 25, Exchange will make a connection to that server. However, if this server does not relay, or accept e-mail for the intended domain a NDR will be generated with a 5.7.1, or
5.5.0 error message.
There are several domains that have A records that point to IP addresses that accept connections on port 25, but do not relay for the same name space:
Eg: Mindspring.com; Earthlink.net
Resolution
Resolve the DNS resolution problems that are causing occasional MX record failures.
Examples:
1. The Exchange server has multiple default gateways set on a multi-homed server.
This is not a recommended configuration and can cause a number of unexpected network problems. If the internal DNS server the internal NIC points to cannot resolve external DNS queries, this problem can occur.
Action: remove the default gateway from one of the NICs.
This doesn’t applies to us, as we don’t use Internal DNS
2. If the Exchange server points to multiple DNS servers on TCP/IP properties, or on the SMTP Virtual Server properties, verify that each of these DNS servers will return MX records properly. If one of the DNS servers does not return DNS records consistently, rectify this problem.
Action: remove this DNS server from the external DNS tab.
Workaround:
Bypass DNS by creating a SMTP connector with address space of <domain.com> and forward to smart host as the IP address the MX/A points to.
Exchange Query Explained
1. If Exchange finds the MX record(s) for a remote domain (through DNS query) it will not fall back to an A record query in the event the MX record (more precisely, the A record the MX record points to) is temporarily not responding on port 25. Instead, Exchange will try another MX record if one exists. If no other MX records exist and none are responding on port 25, the queue will go into a retry state for this remote domain. When that retry state has expired, Exchange will again attempt to resolve MX records for this domain, and so on.
2. Exchange will fall back to an A record query for the remote domain in the event that no MX record can be found. This is not to say that the MX record does not exist - only that when Exchange issued a DNS query for the remote domain the DNS response was "server failure", which basically means no MX was found. So, the MX record may indeed exist, but Exchange simply could not find it through DNS resolution.
3. Exchange then queries the A record and this happens to return a result. If the A record is listening on port 25, but does not accept mail for <domain.com> then we will get the NDR with 550 5.7.1 unable to relay (or some variation of this NDR error code) when Exchange connects and attempts to send the e-mail.
So, the intermittent nature of the problem is caused by a failure to find the MX record and a success in finding A record. This can happen for a variety of reasons, but it boils down to flakey DNS resolution.
For example:
a. A bad DNS server listed as a forwader on the DNS server.
b. A bad DNS server on the TCP/IP properties.
c. A bad DNS server on the SMTP VS (external DNS servers)
d. Multiple default gateways on Exchange (ie. multiple NICs on different networks, each NIC having a default GW)
A netmon on Exchange will show the failed MX lookup and successful A record lookup; however, it may not be conclusive unless the "bad" DNS server is listed in the netmon trace. For example, if Exchange points to internal DNS server(s) for name resolution and these DNS servers service these DNS queries by Exchange, you may need a netmon on the DNS server(s) as well to determine which DNS server/Forwarder/etc is at fault.
Regards,
Shahul Hameed Dasthagir
Support Engineer | Enterprise Communications Support

Regarding Displaying of outbound Idocs in XML format

Hi every1
i want to display my IDocs in XML format. I am using T.Code WE34, after that.... what i have to do. Please let me know whole procedure, because in SAP Library I am getting information about only Inbound; and i want to know about outbound Idoc. please reply me its urgent.
Thanks
Anil Behera.

Hi,
Follow the procedure
IDOC to XML Convertion using ALE Interface
1) Send an outbound IDOC data(MATMAS) to a flat file(XML) on client1(SENDER).
Create File Port (WE21) of XML Type for outbound file.
Specify the Physical directory and file under the Outbound File tab
Maintain Distribution Model (BD64) for sender ->receiver system.
Create Partner Profile (WE20) for logical system.
You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
Create File Port (WE21) for inbound file.
Maintain Distribution Model (BD64) for receiver -> sender system.
Create Partner Profile (WE20) for logical system.
You can use this program RSEINB00 to upload IDoc MATMAS file(s).
A sample scenario for idoc generation
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
Now go to the physical directory and check your idoc converted as an XML File.
Regards,
Satish

Writting file in xml format

Hello guys,
I am just wondering if i can write to a text file in xml format:
For example if i want to save the following:
Avisha 00/06/2000
The text file should show:
<record>
<name>Avisha</name>
<DOB00/06/200</DOB>
</record>
I think i probably needs to use some sort of XML schema, i never done it before and i would appriciate your help.
Thanks,

corlettk wrote:
thomas.behr wrote:
Well, for simple cases, such as your example, just create an appropriate String and write that to your file.
For more complex cases, create a org.w3c.dom.Document (using DocumentBuilder and DocumentBuilderFactory), create the appropriate structure and use a javax.xml.transform.Transformer (created via TransformerFactory) to convert your Document from a DOMSource to StreamResult.I'm not a fan of the DOM solution... It's slow and very memory hungry... Goog for small datasets.
@OP If you can, I recommend using an XMLBinder (like [XML-Beans|http://xmlbeans.apache.org/] jusr for example) to both read and write all your XML.Errr, XMLBeans and the like will still be using DOM under the covers, so the memory issue is still as relevant as before. Happily, this turns out to be "not as much as you probably think" anyway. So the decision is a design one. Do you have schemas for this XML? You don't? Ah well, a binding framework's out of the question anyway. What are you doing with it? ("Processing it" isn't an answer). Where is it coming from? ("my codez" isn't an answer). What format need it be in? ("XML format" isn't an answer)
Building a DOM tree and serializing it isn't necessarily all that stupid an idea

Invalid xml error for raising events thro EM console

Hi,
I am using soa-suite 11g and was trying chapter 17 (EDN) from the book "Getting Started with Oracle SOA Suite 11g R1 – A Hands-On Tutorial".
I created an event and trying to consume it through a mediator and writing it to a file. I read that there is a provision to raise event through EM console. I tried that option and gave a sample xml payload. But it always errors out saying incorrect xml format.
I pasting below the xsd definition and the input payload. Can someone pls let me know if raising events thro em console works ?
PO.XSD
<?xml version= '1.0' encoding= 'UTF-8' ?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xmlns.oracle.com/ns/order"
xmlns:po="http://xmlns.oracle.com/ns/order" elementFormDefault="qualified">
<element name="PurchaseOrder" type="po:PurchaseOrderType"/>
<complexType name="PurchaseOrderType">
<sequence>
<element name="CustID" type="string"/>
<element name="ID" type="string"/>
<element name="productName" type="string" minOccurs="0"/>
<element name="itemType" type="string" minOccurs="0"/>
<element name="price" type="decimal" minOccurs="0"/>
<element name="quantity" type="decimal" minOccurs="0"/>
<element name="status" type="string" minOccurs="0"/>
<element name="ccType" type="string" minOccurs="0"/>
<element name="ccNumber" type="string" minOccurs="0"/>
</sequence>
</complexType>
</schema>
Input Payload
<PurchaseOrder xmlns="http://xmlns.oracle.com/ns/order">
<CustID>1111</CustID>
<ID>33412</ID>
<productName>Sony Bluray DVD Player</productName>
<itemType>Electronics</itemType>
<price>350</price>
<quantity>5</quantity>
<status>Initial</status>
<ccType>Mastercard</ccType>
<ccNumber>1234-1234-1234-1234</ccNumber>
</PurchaseOrder>
EDL
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<definitions xmlns="http://schemas.oracle.com/events/edl" targetNamespace="http://schemas.oracle.com/events/edl/POEvents">
<schema-import namespace="http://xmlns.oracle.com/ns/order" location="xsd/po.xsd"/>
<event-definition name="NewPO">
<content xmlns:ns0="http://xmlns.oracle.com/ns/order" element="ns0:PurchaseOrder"/>
</event-definition>
</definitions>
thanks in advance
Balaji

Error when raising on EM console
"Failed to publish the event. A common cause is to input incorrect XML syntax. Please view the log files for details."
Exception in the log
oracle.fabric.common.FabricException: Error enqueing event
at oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus.publishEvent(SAQBusinessEventBus.java:517)
at oracle.integration.platform.blocks.event.EDNFacadeImpl.testEventPublish(EDNFacadeImpl.java:394)
at oracle.soa.management.internal.ejb.impl.FacadeFinderBeanImpl.executeEDNMethod(FacadeFinderBeanImpl.java:1191)
at sun.reflect.GeneratedMethodAccessor940.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
at sun.reflect.GeneratedMethodAccessor863.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy241.executeEDNMethod(Unknown Source)
at oracle.soa.management.internal.ejb.impl.FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.executeEDNMethod(FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.java:1536)
at oracle.soa.management.internal.ejb.impl.FacadeFinderBean_4vacyo_FacadeFinderBeanImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus.inGlobalTrans(SAQBusinessEventBus.java:640)
at oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus.getConnection(SAQBusinessEventBus.java:1357)
at oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus.publishEvent(SAQBusinessEventBus.java:511)
at oracle.integration.platform.blocks.event.EDNFacadeImpl.testEventPublish(EDNFacadeImpl.java:394)
at oracle.soa.management.internal.ejb.impl.FacadeFinderBeanImpl.executeEDNMethod(FacadeFinderBeanImpl.java:1192)
at sun.reflect.GeneratedMethodAccessor940.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
at sun.reflect.GeneratedMethodAccessor863.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy241.executeEDNMethod(Unknown Source)
at oracle.soa.management.internal.ejb.impl.FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.executeEDNMethod(FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.java:1536)
at oracle.soa.management.internal.ejb.impl.FacadeFinderBean_4vacyo_FacadeFinderBeanImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:590)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:478)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:119)
... 2 more

Help in creation of XML file for IDOC postings

Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
Srini

Hello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto

Incorrect XML format for outbound binding

Similar Messages

Maybe you are looking for