cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Problem creating Message Interface from External Definition

Former Member

on ‎03-09-2010 1:26 PM

0 Kudos

Hi everybody.

Im having problems creating a Message Interface from an External Definition.

I´ve imported an xsd to create an external definition an the process is been OK.

The problem is that when I go to create the message interface I cant choose this external definition and this external definition lives in the same namespace.

Whats wrong with my external definition?

Thanks a lot...

Regards

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (11)

Answers (11)

Former Member
‎03-10-2010 11:34 AM
0 Kudos

If I paste it the message is shown like this:

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

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:docu="http://www.basis.ko.com/XML/2002/SchemaDocumentation" xmlns="http://www.basis.ko.com/XMLSchemas/CallingSequenceRequest/2.0" targetNamespace="http://www.basis.ko.com/XMLSchemas/CallingSequenceRequest/2.0" elementFormDefault="qualified" xsi:schemaLocation="http://www.w3.org/2001/XMLSchema XMLSchema.xsd">
	<xs:include schemaLocation="EffectiveDate_Type.xsd" />
	<xs:annotation>
		<xs:documentation>
			<docu:generalInformation>
			Requests a calling sequence defintion.
			</docu:generalInformation>
			<docu:documentRole>
			request
			</docu:documentRole>
			<docu:relatedDocument>
			CallingSequence
			</docu:relatedDocument>
			<docu:applicationContext>
			OM
			</docu:applicationContext>
			<docu:associatedFiles>
				<docu:fileName>
				OM06
				</docu:fileName>
			</docu:associatedFiles>
			<docu:associatedVersions>
				<docu:version>
				REL530
				</docu:version>
				<docu:version>
				PTF531
				</docu:version>
				<docu:version>
				SPCB531020
				</docu:version>
				<docu:version>
				PTF532
				</docu:version>
				<docu:version>
				SPCB532003
				</docu:version>
				<docu:version>
				SPCB532042
				</docu:version>
			</docu:associatedVersions>
		</xs:documentation>
	</xs:annotation>
	<xs:element name="CallingSequenceRequest" type="CallingSequenceRequest_Type" />
	<xs:complexType name="CallingSequenceRequest_Type">
		<xs:sequence>
			<xs:element name="OutletNumber">
				<xs:annotation>
					<xs:documentation>
						<docu:additionalFieldReference file="OM06" field="OUTNUM" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:positiveInteger">
						<xs:totalDigits value="13" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="CallingType">
				<xs:annotation>
					<xs:documentation>
						<docu:additionalFieldReference file="OM06" field="CALTYP" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="2" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="CallingIdentification" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:additionalFieldReference file="OM06" field="CALIDF" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="2" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="UserName" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:additionalComment>
						Requestor UserName, stored in EB14-USRNAM in case of a reserve request. Mandatory for update, reserve and unreserve requests.
						</docu:additionalComment>
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="30" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="UserID" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:additionalComment>
						Requestor UserID, stored in OM06-UPDUSR in case of an update request
						</docu:additionalComment>
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="10" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="ApprovalIndicator1" type="xs:boolean" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="APVIND1" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="ApprovalIndicator2" type="xs:boolean" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="APVIND2" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="ApprovalIndicator3" type="xs:boolean" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="APVIND3" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="ApprovalIndicator4" type="xs:boolean" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="APVIND4" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="ApprovalIndicator5" type="xs:boolean" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="APVIND5" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="EffectiveToDate" type="EffectiveDate_Type" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="EFTDAT" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="CallingLocation" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="CALLOC" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="4" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="CallingRoute" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="CALRTE" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="3" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="CallingSequence" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="CALSEQ" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:positiveInteger">
						<xs:totalDigits value="5" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="WeekDay" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="WEKDAY" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:positiveInteger">
						<xs:totalDigits value="2" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="CallingIndicator" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="CALIND" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="1" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="CallingCycle" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="CALCYC" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:nonNegativeInteger">
						<xs:totalDigits value="3" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="FirstCallDate" type="EffectiveDate_Type" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="CALDAT" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="SuppressionCycle" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="SPRCYC" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:nonNegativeInteger">
						<xs:totalDigits value="3" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="SeasonStartDate" type="EffectiveDate_Type" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="SESSTRDAT" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="SeasonEndDate" type="EffectiveDate_Type" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="SESENDDAT" />
					</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="MessageCode1" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="MSGCOD61" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="2" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="MessageCode2" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="MSGCOD62" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="2" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="MessageCode3" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="MSGCOD63" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="2" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="MessageCode4" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:fieldMapping file="OM06" field="MSGCOD64" />
					</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:maxLength value="2" />
					</xs:restriction>
				</xs:simpleType>
			</xs:element>
			<xs:element name="UserElements" minOccurs="0">
				<xs:annotation>
					<xs:documentation>
						<docu:additionalComment>
						Use this area to specify the format of the user data you want to capture.
						</docu:additionalComment>
						<docu:additionalFieldReference file="OM06" field="USRARE030A" />
						<docu:additionalFieldReference file="OM06" field="USRARE030B" />
						<docu:additionalFieldReference file="OM06" field="USRARE030C" />
						<docu:additionalFieldReference file="OM06" field="USRINT01" />
						<docu:additionalFieldReference file="OM06" field="USRDEC01" />
						<docu:additionalFieldReference file="OM06" field="USRDAT01" />
					</xs:documentation>
				</xs:annotation>
				<xs:complexType>
					<xs:sequence>
						<xs:any processContents="lax" />
					</xs:sequence>
				</xs:complexType>
			</xs:element>
		</xs:sequence>
		<xs:attribute name="function" use="required">
			<xs:simpleType>
				<xs:restriction base="xs:NMTOKEN">
					<xs:enumeration value="retrieve">
						<xs:annotation>
							<xs:documentation>
								<docu:valueInformation>
								Retrieves calling sequence information for a given outlet number, calling type and calling identification.
								</docu:valueInformation>
							</xs:documentation>
						</xs:annotation>
					</xs:enumeration>
					<xs:enumeration value="reserve">
						<xs:annotation>
							<xs:documentation>
								<docu:valueInformation>
								Reserves the calling sequence identified by the given outlet number, calling type and calling identification for update by the given user.
								</docu:valueInformation>
							</xs:documentation>
						</xs:annotation>
					</xs:enumeration>
					<xs:enumeration value="unreserve">
						<xs:annotation>
							<xs:documentation>
								<docu:valueInformation>
								Unreserves the calling sequence identified by the given outlet number, calling type and calling identification that was reserved for update by the given user.
								</docu:valueInformation>
							</xs:documentation>
						</xs:annotation>
					</xs:enumeration>
					<xs:enumeration value="update">
						<xs:annotation>
							<xs:documentation>
								<docu:valueInformation>
								Update the calling sequence identified by the given outlet number, calling type and calling identification with the given calling sequence detail information. The system allows an update only for calling sequences, that have been reserved for update by the given user. No separate reservation request is required when the autoReserve attribute is true.
								</docu:valueInformation>
							</xs:documentation>
						</xs:annotation>
					</xs:enumeration>
					<xs:enumeration value="create">
						<xs:annotation>
							<xs:documentation>
								<docu:valueInformation>
								Create a new calling sequence with the given calling sequence information.
								</docu:valueInformation>
							</xs:documentation>
						</xs:annotation>
					</xs:enumeration>
					<xs:enumeration value="delete">
						<xs:annotation>
							<xs:documentation>
								<docu:valueInformation>
								Deletes the calling sequence identified by the given outlet number, calling type and calling identification.
								</docu:valueInformation>
							</xs:documentation>
						</xs:annotation>
					</xs:enumeration>
				</xs:restriction>
			</xs:simpleType>
		</xs:attribute>
		<xs:attribute name="acceptAllWarnings" default="false">
			<xs:simpleType>
				<xs:restriction base="xs:boolean" />
			</xs:simpleType>
		</xs:attribute>
		<xs:attribute name="processingStatus" default="final">
			<xs:simpleType>
				<xs:restriction base="xs:NMTOKEN">
					<xs:enumeration value="final" />
					<xs:enumeration value="finalElseDraft" />
					<xs:enumeration value="draft" />
				</xs:restriction>
			</xs:simpleType>
		</xs:attribute>
		<xs:attribute name="languageCode" default="ENU">
			<xs:simpleType>
				<xs:restriction base="xs:string">
					<xs:maxLength value="3" />
				</xs:restriction>
			</xs:simpleType>
		</xs:attribute>
		<xs:attribute name="role" use="optional">
			<xs:simpleType>
				<xs:restriction base="xs:string">
					<xs:maxLength value="5" />
				</xs:restriction>
			</xs:simpleType>
		</xs:attribute>
		<xs:attribute name="responseEdition" use="optional">
			<xs:simpleType>
				<xs:restriction base="xs:string">
					<xs:maxLength value="256" />
				</xs:restriction>
			</xs:simpleType>
		</xs:attribute>
		<xs:attribute name="requestCorrelationID" use="optional">
			<xs:simpleType>
				<xs:restriction base="xs:string">
					<xs:maxLength value="256" />
				</xs:restriction>
			</xs:simpleType>
		</xs:attribute>
		<xs:attribute name="autoReserve" type="xs:boolean" default="false" />
	</xs:complexType>
</xs:schema>

Show replies
Show replies
Former Member
‎03-10-2010 10:42 AM
0 Kudos

Yes I´ve tried but it continues not working....

Im getting crazy.... jejej

Thanks....

Show replies
Show replies
Former Member
‎03-10-2010 10:14 AM
0 Kudos

Good morning.

If somebody can tell me his mail I could send him the xsd.

If I paste the message here is not shown correctly...

Thanks a lot.

Regards

Show replies
Show replies
sbuttler77
Active Participant
‎03-10-2010 10:25 AM
0 Kudos

have you tried to change your messages setting in your external definition from

"Do not extract" to "From all available Global Elements" or "From all unreferenced Global Elements"?

Former Member
‎03-10-2010 11:14 AM
0 Kudos

> If somebody can tell me his mail I could send him the xsd.

Sorry, but this is agains the SDN rules of engagements.

> If I paste the message here is not shown correctly...

What do you mean it is inot shown correctly...... just paste it as a code.

Former Member
‎03-09-2010 3:14 PM
0 Kudos

That´s ok, I know it but the problem is when I paste the xml schema definition I cant find a paser to show the xml message correctly...

Thanks!!!

Show replies
Show replies
Former Member
‎03-09-2010 2:34 PM
0 Kudos

how can I add the xsd????

Thanks a lot.

Edited by: Christian Abad Chico on Mar 9, 2010 3:38 PM

Show replies
Show replies
Former Member
‎03-09-2010 2:46 PM
0 Kudos

Chico,

Open your external definiton in IR and then you see the code in the bottom screen. copy and paste here so that somebody here can take a look and help you out.

Regards,

---Satish

Former Member
‎03-09-2010 2:16 PM
0 Kudos

Hi Chico,

Can you put your external definiton so that somebody can help you out here?

Regards,

---Satish

Show replies
Show replies
Former Member
‎03-09-2010 1:54 PM
0 Kudos

I know where I have the problem....

The tab Messages in the external definition is empty and It must be filled with the name and the namesapce...

Why is this tab MESSSAGES not filled in the external definition?

Regards and thank u so much!!!

Show replies
Show replies
Former Member
‎03-09-2010 2:02 PM
0 Kudos

So it is simply your external definition issue. Have you checked the issue by pressing the F7 button in your external definition?

Former Member
‎03-09-2010 1:50 PM
0 Kudos

It´s possible to create a message interface from external definition created from a xsd.... I´ve done it a lot of times....

I´ve created the external definition from xsd...

Regards

Show replies
Show replies
Former Member
‎03-09-2010 1:47 PM
0 Kudos

How did you import External Definition?.. Did you choose the Category as XSD?

Show replies
Show replies
stefan_grube
Active Contributor
‎03-09-2010 1:41 PM
0 Kudos

I think a can assign an external definition to message interface only for a WSDL type.

For xsd you have to create a message type first.

Show replies
Show replies
Former Member
‎03-09-2010 1:44 PM
0 Kudos

> I think a can assign an external definition to message interface only for a WSDL type.

> For xsd you have to create a message type first.

In my case (XI3.0) I have directly used the external definition into my message interface.

Former Member
‎03-09-2010 1:37 PM
0 Kudos

Try drag & drop method. I mean after creating the Message Interface just drag the external definition in the input message box and drop it.

Show replies
Show replies
Ask a Question