importing XCBL-Standard as external definition

[Former Member]

Hello,

I have to import the XCBL-XML Standard 4.0 into SAP XI to use it for orderprocessing.

The import itself seemd to be no problem, all import and include connections are resolved.

Now my problem: I have no message that I can use in a messagetype or mapping.

This is the ordermanagement.xsd from the xcbl standard (I need the order):

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

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:core="rrn:org.xcbl:schemas/xcbl/v4_0/core/core.xsd" xmlns:dgs="http://www.w3.org/2000/09/xmldsig#" xmlns="rrn:org.xcbl:schemas/xcbl/v4_0/ordermanagement/v1_0/ordermanagement.xsd" targetNamespace="rrn:org.xcbl:schemas/xcbl/v4_0/ordermanagement/v1_0/ordermanagement.xsd" elementFormDefault="qualified">
	<xsd:import namespace="rrn:org.xcbl:schemas/xcbl/v4_0/core/core.xsd" schemaLocation="../../core/core.xsd" />
	<xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="../../externalschemas/xmldsig-core-schema.xsd" />
	<xsd:include schemaLocation="AccountAssignmentType.xsd" />
	<xsd:include schemaLocation="BaseItemDetailType.xsd" />
	<xsd:include schemaLocation="ChangeOrderDetailType.xsd" />
	<xsd:include schemaLocation="ChangeOrderHeaderType.xsd" />
	<xsd:include schemaLocation="ChangeOrderItemDetailType.xsd" />
	<xsd:include schemaLocation="ChangeOrderNumberType.xsd" />
	<xsd:include schemaLocation="ChangeOrderPackageDetailType.xsd" />
	<xsd:include schemaLocation="ChangeOrderSummaryType.xsd" />
	<xsd:include schemaLocation="ChangeOrderType.xsd" />
	<xsd:include schemaLocation="ContractAndSystemReferenceType.xsd" />
	<xsd:include schemaLocation="ItemDetailType.xsd" />
	<xsd:include schemaLocation="ItemStatusType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationActionCodeType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationActionType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationDetailReferencesType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationDetailType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationHeaderType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationItemDetailType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationPartyType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationResponseDetailType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationResponseHeaderType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationResponsePartyType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationResponseType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationTypeCodeType.xsd" />
	<xsd:include schemaLocation="OrderConfirmationTypeType.xsd" />
	<xsd:include schemaLocation="OrderDatesType.xsd" />
	<xsd:include schemaLocation="OrderDetailType.xsd" />
	<xsd:include schemaLocation="OrderHeaderType.xsd" />
	<xsd:include schemaLocation="OrderInvoiceMediumTypeCodeType.xsd" />
	<xsd:include schemaLocation="OrderNumberType.xsd" />
	<xsd:include schemaLocation="OrderPartyType.xsd" />
	<xsd:include schemaLocation="OrderReferencesType.xsd" />
	<xsd:include schemaLocation="OrderRequestHeaderType.xsd" />
	<xsd:include schemaLocation="OrderRequestNumberType.xsd" />
	<xsd:include schemaLocation="OrderRequestPartyType.xsd" />
	<xsd:include schemaLocation="OrderRequestType.xsd" />
	<xsd:include schemaLocation="OrderResponseDetailType.xsd" />
	<xsd:include schemaLocation="OrderResponseDocTypeCodeType.xsd" />
	<xsd:include schemaLocation="OrderResponseHeaderType.xsd" />
	<xsd:include schemaLocation="OrderResponseItemDetailType.xsd" />
	<xsd:include schemaLocation="OrderResponseNumberType.xsd" />
	<xsd:include schemaLocation="OrderResponsePackageDetailType.xsd" />
	<xsd:include schemaLocation="OrderResponseSummaryType.xsd" />
	<xsd:include schemaLocation="OrderResponseType.xsd" />
	<xsd:include schemaLocation="OrderStatusEventCodeType.xsd" />
	<xsd:include schemaLocation="OrderStatusItemType.xsd" />
	<xsd:include schemaLocation="OrderStatusReferenceType.xsd" />
	<xsd:include schemaLocation="OrderStatusRequestDetailType.xsd" />
	<xsd:include schemaLocation="OrderStatusRequestHeaderType.xsd" />
	<xsd:include schemaLocation="OrderStatusRequestType.xsd" />
	<xsd:include schemaLocation="OrderStatusResultDetailType.xsd" />
	<xsd:include schemaLocation="OrderStatusResultHeaderType.xsd" />
	<xsd:include schemaLocation="OrderStatusResultItemType.xsd" />
	<xsd:include schemaLocation="OrderStatusResultReferenceType.xsd" />
	<xsd:include schemaLocation="OrderStatusResultType.xsd" />
	<xsd:include schemaLocation="OrderSummaryType.xsd" />
	<xsd:include schemaLocation="OrderType.xsd" />
	<xsd:include schemaLocation="OriginalItemDetailWithChangesType.xsd" />
	<xsd:include schemaLocation="ResponseBaseItemDetailType.xsd" />
	<xsd:include schemaLocation="ResponseDeliveryDetailType.xsd" />
	<xsd:include schemaLocation="SplitQuantityType.xsd" />
	<xsd:element name="ChangeOrder" type="ChangeOrderType" />
	<xsd:element name="Order" type="OrderType" />
	<xsd:element name="OrderRequest" type="OrderRequestType" />
	<xsd:element name="OrderResponse" type="OrderResponseType" />
	<xsd:element name="OrderConfirmation" type="OrderConfirmationType" />
	<xsd:element name="OrderConfirmationResponse" type="OrderConfirmationResponseType" />
	<xsd:element name="OrderStatusRequest" type="OrderStatusRequestType" />
	<xsd:element name="OrderStatusResult" type="OrderStatusResultType" />
</xsd:schema>

Thanks for any advice

[Former Member]

Yes, I have found the problem and a workaround for it.

The XCBL-xsd uses multiple namespaces which causes problems in SAP.

I created a new xsd from an example file and deleted all namespaces from it except one - now it works.

Thank you for your advice anyway

[Former Member]

use this link ... this forum is - strange ....

http://img183.imageshack.us/img183/5262/externaldefinitionyp6.jpg

[Former Member]

Hi ,

Is your issue resolved ? If you can send me the XSD's I can check from my end also .

Regards,

Ganesh.

[Former Member]

Oh!

Sorry I misunderstood you

But I already filled all source-values with the correct names.

I uploded a picture of the current situation for better understanding.

The left screenshot shows the main-xsd the right the above mentioned xmldsig...

<a href="http://img183.imageshack.us/my.php?image=externaldefinitionyp6.jpg">[IMG]http://img183.imageshack.us/img183/5262/externaldefinitionyp6.th.jpg[/IMG]</a><a href="http://g.imageshack.us/thpix.php">[IMG]http://img183.imageshack.us/images/thpix.gif[/IMG]</a>

[Former Member]

I tried it out - it doesn't work.

Some of the xcbl-xsd have symbols in their names that can't be used in SAP like "-" so I am unable to name the objects like the source file.

Example:

This is from the main xsd

<xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="../../externalschemas/xmldsig-core-schema.xsd" />

I called this Object in SAP: EX_xmldsig_core_schema

I can't call it like the original name: xmldsig-core-schema.xsd

In the "External definitions" tab it looks like:

Source -

---

Name

../../externalschemas/xmldsig-core-schema.xsd -

---

EX_xmldsig_core_schema

Is there perhaps a limit for includes? I had to make over 100 objects to fill all external definitions. Some of them have includes again.

[Former Member]

Hi,

Original name should be used in the source field of the included XSD ; U can give any name to the XSD imported in IR .

That means in u r XSD : EX_xmldsig_core_schema enter the source field value as : xmldsig-core-schema.xsd which is there in the schemalocation of main XSD.

And it takes '-' in the source field value name.

Regards,

Ganesh.

[Former Member]

The references work fine. I can open all nested xsd from the main-xsd.

I named my components like "EX_OrderSummary" while the xsd-file name is "OrderSummaryType.xsd" could this be the problem?

I also chose "from all global elements" in the messages combo-box - do I perhaps need to select something else for the nested xsds?

[Former Member]

Hi,

Try Using the same name as there in the main XSD's schema location in the source field of included XSD.

And from All available global elements should not have any problem.

Regards,

Ganesh.

[Former Member]

Yes, I see them.

All external definitions have a source and are filled with a name from another external definition I included.

[Former Member]

Hi,

Check the names u mentioned in the source field in the included XSD's and those that are there in Main XSD match ;

Also check that when you double click on the link to the included XSD in External Refferences tab it opens the corresponding XSD.

Because this is the way to inlude the nested XSD's.

Regards,

Ganesh.

[Former Member]

The source values are already mentioned and recognized correctly by the main-xsd as well as further includes by the other files.

[Former Member]

Hi,

R u able to see link to the included XSD's in the external refference tab of the Main XSD?

Regards,

Ganesh.

[Former Member]

Hi,

It seems it is not able to indentify the included XSD's , in u r XSD's which are working as a include mention the source value which is there in the schemalocation of the main XSD.

Regards,

Ganesh.