Reference Schema loader for Transaction Input Property

[former_member265052]

Hello,

I am trying to use XML Schema to define input structure of a BLS transaction, I have two issues with it.

Firstly. I do not get drill down Tree structure of the XML input parameter in an action block's link editor,

Secondly, If I add a reference document drill down comes, but there is an issue with that, when I close and open the transaction I get this error

I am not sure What I am missing here. Has anyone come across this issue?

Can we assign a reference schema document to an Incomming Parameter?

I have configured the transaction as given below.

1. I have specified an input parameter as XML type and linked it to a XSD file

2. The XSD File

<s:schema attributeFormDefault="unqualified" elementFormDefault="qualified"

  xmlns:s="http://www.w3.org/2001/XMLSchema"

            targetNamespace="http://www.sap.com/xMII">

  <s:element name="Request">

    <s:complexType>

      <s:sequence>

        <s:element type="s:string" name="MaterialNumber"/>

        <s:element type="s:string" name="Plant"/>

        <s:element name="TestList" minOccurs="1" maxOccurs="unbounded">

          <s:complexType>

            <s:sequence>

              <s:element type="s:string" name="Param"/>

            </s:sequence>

          </s:complexType>

        </s:element>

      </s:sequence>

    </s:complexType>

  </s:element>

</s:schema>

3. Created a reference Schema loader Action and configured it to refer the same XSD as above.

4. Assigned the Reference schema loader's XMLcontent to "Input"  property of transaction.

[salvatore_castro · Accepted solution]

I followed your steps and it worked fine for me; I have 14.0 SP5 Patch6

Sam

[former_member265052 · Accepted solution]

Hello Sam,

Thank you for the reply,

unfortunately, It still does'nt work for me.

I have 14.0 SP4 Patch 1 (08.01.2014).

Do you think an upgrade will help?

Also, why does below popup come when I close and open the transaction.

[salvatore_castro · Accepted solution]

Seems like it as I have the newer version (14.0 SP5 Patch 6) deployed and it works...I don't have your version anywhere or I would try it out to verify.

Sam