cancel
Showing results for 
Search instead for 
Did you mean: 

Generic error while using create operation on MDM WebService

Former Member
0 Kudos

Hello

I´m trying to create a record on MDM using a standard MDM WebService operation createProducts

When I create a record with everything blank (but not the repository info), it creates perfectly:

<urn:createProducts>

<urn:products>

<urn1:ProductsCreate></urn1:ProductsCreate>

</urn:products>

<urn:reposInfo>

<urn2:dataLang>English </urn2:dataLang>

<urn2:repositoryName>MY_REPOSITORY</urn2:repositoryName>

<urn2:serverName>mdmserver</urn2:serverName>

</urn:reposInfo>

</urn:createProducts>

However, when I try to add the following code, it doesn´t work:

<urn:createProducts>

<urn:products>

<urn1:ProductsCreate>

<urn1:eClassClassification>

<urn1:displayValue>PDM TEST</urn1:displayValue>

<urn1:attributes>

<urn1:attribute>

<urn1:name>TEST1 TEST123</urn1:name>

</urn1:attribute>

<urn1:attributeValue>

<urn1:value>

<urn1:value>220,00 MM</urn1:value>

</urn1:value>

</urn1:attributeValue>

</urn1:attributes>

</urn1:eClassClassification>

</urn1:ProductsCreate>

</urn:products>

<urn:reposInfo>

<urn2:dataLang>English </urn2:dataLang>

<urn2:repositoryName>MY_REPOSITORY</urn2:repositoryName>

<urn2:serverName>mdmserver</urn2:serverName>

</urn:reposInfo>

</urn:createProducts>

I get the return:

<rpl:createProductsResponse xmlns:rpl="urn:MDMMateriaisVi">

<rpl:Response xmlns:pns="urn:com.sap.mdm.ws.beans">

<pns:ExecutionStatus>

<pns:status>Fault</pns:status>

<pns:description>Record creation unsuccessful, see the faults list</pns:description>

<pns:fault>

<pns:severity>Error</pns:severity>

<pns:id>repository_3001</pns:id>

<pns:text>Error executing Records Creation on repository MY_REPOSITORY, error code -5627883, caused by Server error (0xffaa2015)</pns:text>

</pns:fault>

</pns:ExecutionStatus>

</rpl:Response>

</rpl:createProductsResponse>

All atributes exists on MDM but I still get the error.

Any ideas ?

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

did you got the solution to this issue, as we are also getting the same error,