cancel
Showing results for 
Search instead for 
Did you mean: 

Demo Consumption System - OData - EPM problem: persisting THE product DATA has FAILED.

Former Member
0 Kudos

Hi all,

we're trying to insert a record into Products and receive the following error:

  • SEPM_BOR_MESSAGES/001 -  EPM problem: persisting THE product DATA has FAILED.
  • Error-Detail: /IWBEP/CX_EPM_BUSI_EXCEPTION - EPM problem: persisting THE product DATA has FAILED

Does anyone know what that means?!?!

This is the request we're sending:

POST https://sapes4.sapdevcenter.com/sap/opu/odata/IWBEP/GWDEMO/ProductCollection HTTP/1.1
Cookie: SAP_SESSIONID_ES4_800=<SessionId>;
X-CSRF-Token: <Csrf-Token>
Content-Type: application/json
Host: sapes4.sapdevcenter.com
Content-Length: 634
Expect: 100-continue

{
  "ProductName": "Internet Keyboard",
  "ChangedAt": "2016-03-07T21:30:00",
  "TaxTariffText": "Regular VAT",
  "ProductID": "MW-1000",
  "DimensionUnit": "CMT",
  "WeightUnitText": "Kilogram",
  "UnitPrice": "1600",
  "ProductKey": "005056A216B81EE5B996868F8876AC2F",
  "WeightMeasure": "0",
  "ProductWidth": "52000",
  "DimensionUnitText": "Centimeter",
  "SupplierID": "0100000029",
  "ProductDescription": "Corded Keyboard with special keys for Internet Usability, USB",
  "ProductCategory": "Keyboards",
  "TaxTariffCode": 1,
  "QuantityUnit": null,
  "ProductTypeCode": "PR",
  "SupplierName": "C.R.T.U."
}

Thanks!

Michaela

Accepted Solutions (0)

Answers (1)

Answers (1)

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

I tried POST for same uri , it works for me. Can you check with this payload?

payload:


<?xml version="1.0" encoding="UTF-8"?>

<entry xmlns="http://www.w3.org/2005/Atom" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">

    <content type="application/xml">

        <m:properties>

            <d:ProductName>Play1 Movie1</d:ProductName>

            <d:ChangedAt>2016-03-08T11:37:04.8240000</d:ChangedAt>

            <d:TaxTariffText>Regular VAT</d:TaxTariffText>

            <d:ProductID>AB-1002</d:ProductID>

            <d:DimensionUnit>CMT</d:DimensionUnit>

            <d:WeightUnitText>Kilogram</d:WeightUnitText>

            <d:UnitPrice>13000.00</d:UnitPrice>

            <d:ProductKey>005056A216B81EE5B9A4428455AE6C2F</d:ProductKey>

            <d:WeightMeasure>2400.000</d:WeightMeasure>

            <d:ProductWidth>37000.000</d:ProductWidth>

            <d:DimensionUnitText>Centimeter</d:DimensionUnitText>

            <d:SupplierID>0100000040</d:SupplierID>

            <d:ProductDescription>

CD-RW, DVD+R/RW, DVD-R/RW, MPEG 2 (Video-DVD), MPEG 4, VCD, SVCD, DivX, Xvid

</d:ProductDescription>

            <d:ProductCategory>Portable Players</d:ProductCategory>

            <d:TaxTariffCode>1</d:TaxTariffCode>

            <d:QuantityUnit>EA</d:QuantityUnit>

            <d:ProductTypeCode>PR</d:ProductTypeCode>

            <d:QuantityUnitText>Each</d:QuantityUnitText>

            <d:WeightUnitCode>KGM</d:WeightUnitCode>

            <d:SupplierName>Chemia A Technicznie Fabryka</d:SupplierName>

            <d:CurrencyCode>PLN</d:CurrencyCode>

            <d:ProductHeight>6000.000</d:ProductHeight>

            <d:CurrencyText>Polish Zloty (new)</d:CurrencyText>

            <d:ProductDepth>24000.000</d:ProductDepth>

            <d:SupplierGuid>005056A216B81EE5B996868F88330C2F</d:SupplierGuid>

        </m:properties>

</content>

</entry>

Regards,

JK

former_member188585
Participant
0 Kudos

Hello Jitendra,

I tried using your payload but getting below error

~Rahul

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

You should add an header:

content-type:application/xml

Regards,

JK

former_member188585
Participant
0 Kudos

Oops. Forgot to add. It worked now. Thanks!

~Rahul

Former Member
0 Kudos

Hi,

thanks for your response!

I tried with your workload and it worked.

Digging into the differences field by field, it turned out, that the QuantityUnit field is not allowed to be null although it is not marked with nullable=false in the metadata (and in OData nullable defaults to true if not specified, as far as I know).

Strange error message and bad that null is not allowed (how should one know?).

Anyway, your response helped me identifying the issue - thanks a lot!!!

Kind regards

Michaela