cannot create a Abap proxy

[Former Member]

Hi gurus,

today i tried to generate a abap proxy (in sproxy) without success. My Data Type has a deep structure and more than 200 field. Is there a restriction in this purpose? I wait over 10 minutes whether a dump - nothing happened.

Can anyone assist me?

Thank you

PM

[iaki_vila · Accepted solution]

Hi Peter,

You should wait and to check the exception in the case that this one appear, in this way it will be easier to catch the real problem. Meanwhile, you could check your PI outbound schema, if there is any problem with its tags. In this note you could revise the restrictions:  Note 944029 - XML schema supported by ABAP proxy generation

Regards.

[markangelo_dihiansan]

Hello Peter,

My Data Type has a deep structure and more than 200 field. Is there a restriction in this purpose? I wait over 10 minutes whether a dump - nothing happened.

We had a similar issue, except that the proxy structures were already generated in modules. The problem is when testing it using sproxy (f8), it is giving a SAVE_STYLESHEET_FAILED error in moni.

Upon checking the dump, it appears that the ABAP Control blocks became full (16384 blocks). Also checking using STRANS says we have 151000 lines of code. The solution was to make the proxy structure smaller by re-encoding the sap-generated datatype into a modular one imported as an external definition e.g (just an example)

From:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://namespace" targetNamespace="http://namespace">
   <xsd:element name="MT_Test" type="DT_Test" />
   <xsd:complexType name="DT_Test">
      <xsd:sequence>
         <xsd:element name="Row" minOccurs="0" maxOccurs="unbounded">
            <xsd:complexType>
               <xsd:sequence>
                  <xsd:element name="FirstName" type="xsd:string" />
                  <xsd:element name="LastName" type="xsd:string" />
               </xsd:sequence>
            </xsd:complexType>
         </xsd:element>
      </xsd:sequence>
   </xsd:complexType>
</xsd:schema>

To:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://namespace" targetNamespace="http://namespace">
   <xsd:complexType name="rowType">
      <xsd:sequence>
         <xsd:element name="FirstName" type="xsd:string" minOccurs="1" />
         <xsd:element name="LatName" type="xsd:string" maxOccurs="1" />
      </xsd:sequence>
   </xsd:complexType>
   <xsd:complexType name="TestType">
      <xsd:sequence>
         <xsd:element name="Row" type="rowType" minOccurs="0" maxOccurs="unbounded" />
      </xsd:sequence>
   </xsd:complexType>
   <xsd:element name="MT_Test" type="TestType" />
</xsd:schema>

After doing the re-encoding, we regenerated the proxy and then lines of code in STRANS became 6000.

Hope this helps,

Mark

[Former Member]

Hi Peter,

you can generate the elements separately, starting with the deeper and maybe less complex data types working up to the more complex ones. This is to eliminate the possibility that it is a performance or connection problem.

If your data type is really that deep and complex, maybe you should think about splitting it in PI. In my opinion huge data types are not very practical. They're not reusable and harder to maintain.

Regards,

Jörg

[naveen_chichili]

Hi Peter,

Check if your RFC connectivity is corking correctly. If the connectivity is fine then it might take some time to generate abap proxy.

Thanks,

Naveen

[ambrish_mishra]

Hi Peter,

a deep nested structure and 200 fields should not be an issue in proxy activation. It might take time. However you can check if the connection test is working and run other checks like RFC destinations related to proxy etc.

Let it run and see how much time it takes. Did you stop the transaction ?

Ambrish