SAP Knowledge Base Article - Public

2774304 - You observe the following error when activating a web service - Recheck WSDL and upload it again: Object TTYP YABC Could Not be Activated->Check DDIC

Symptom

You have attempted to activate your custom web service in the cloud studio and it fails with the following errors.

            • Recheck WSDL and upload it again
            • object TTYP YABC could not be activated->check ddic
            • TTYP YABC1 Activated with errors for dependent objects (Details -> DDIC log)

(Where YABC and YABC1 are the solution namespaces.)

Environment

  • SAP Cloud for Customer
  • SAP Business ByDesign
  • SAP Cloud Application Studio

Reproducing the Issue

  1. Login to SDK.
  2. Open the relevant solution.
  3. Select the required Webservice, XYZ.WSID .
  4. Right click on the .wsid file and select the option Activate.
  5. Error appears in the pop-up.

Cause

The WSDL file contains some fields with the same name from both Original solution and Patch solution.

Resolution

You have to remove the duplicate fields for either the original or patch schema definitions.

To do this please follow these steps:

  1. Open your WSDL file in any open source wsdl editor. e.g. notepad++  etc.
  2. Find the this tag in the wsdl <wsdl:types>.
  3. In the wsdl types there are .xsd schemas which belong to each target namespace used in the webservice.

e.g.

<xsd: Schema targetNamepace ="http://123"> (http://123 represents any of the following namepaces).

    • http://sap.com/xi/SAPGlobal20/Global;
    • http://sap.com/xi/AP/Common/Global;
    • http://sap.com/xi/A1S/Global;
    • http://0050010927-one-off.sap.com/Y123_; (Y123 represents a PDI solution)

 The PDI solution namespaces will start with Y*.

e.g.

    • <xsd: Schema targetNamepace ="http://0050010927-one-off.sap.com/Y123"......>
    • <xsd: Schema targetNamepace ="http://0050010927-one-off.sap.com/YABC"......>  (Y123 represents the name of the original solution & YABC represents the name of the patch solution)

Since one of these solutions is the original and the other is the patch solution, some or all of the fields in two these schema definitions may have the same name, which causes the duplicate issue.

  1. Expand these structures to see the element information in each, an example of which is seen below;

e.g.

********************************************************************************************************************

<xsd:group name="Ext00163E6B75071EE980B3EB4F1F560955">

         <xsd:sequence>

                 <xsd:element name="BeneficiaryAddress2" minOccurs="0" form="qualified" type="xi11:Ext00163E3B22471ED881AD62347B0602B4"/>

        </xsd:sequence>

</xsd:group>

<xsd:attributeGroup name="Ext00163E6B75071EE980B3EB4F1F560955"/>

    •  Each field is declared inside a group with the  tag <XSD:GROUP Name> and also has attribute group with tag <XSD:ATTRIBUTEGROUP Name>
    •  The value of the group name and the attribute group name are the same

********************************************************************************************************************

  1.  Find which of these fields are present twice in the WSDL and comment out the duplicate fields from the solution namespace which is not needed.

i.e.

    • The element is present in both the original and patch solution schema definitions and you wish to comment it out of the original namespace schema definition.
  1. To do this comment out the whole element part

e.g.

********************************************************************************************************************

<xsd:group name="Ext00163E6B75071EE980B3EB4F1F560955">

         <xsd:sequence>

        Add comment here ->  //  <xsd:element name="BeneficiaryAddress2" minOccurs="0" form="qualified" type="xi11:Ext00163E3B22471ED881AD62347B0602B4"/>

        </xsd:sequence>

</xsd:group>

<xsd:attributeGroup name="Ext00163E6B75071EE980B3EB4F1F560955"/>

********************************************************************************************************************

  1.  Now search by the value of the group name i.e. "Ext00163E6B75071EE980B3EB4F1F560955"  from the example above.

You will find a reference to it (<xsd:group ref="...">)under the following tag structure:

e.g.

********************************************************************************************************************

<xsd:ComplexType name =..........

<xsd:sequence..........

<xsd:group ref="xi2:Ext00163E6B75071EE980B3EB4F1F560955"/>

********************************************************************************************************************

  1. Comment out this reference also:  // <xsd:group ref="xi2:Ext00163E6B75071EE980B3EB4F1F560955"/>
  2. Repeat these steps for all the fields which are duplicated.  
  3. After commenting out all duplicated fields (from one of the namespace schema definitions), save the WSDL and upload it again to the WSID file.
  4. Activate the WSID file.

 

Keywords

WSDL, Activate, Cloud Studio, Custom Web service, DDIC, TTYP, Activated, Check WSDL, Check DDIC, , KBA , AP-RC-BDS-WS , ByDesign Studio Web Services , Problem

Product

SAP Business ByDesign all versions ; SAP Cloud Applications Studio all versions ; SAP Cloud for Customer add-ins all versions