Segmentation with Agreements - Attribute "Product ID" or "Product Category" with no Data

[former_member355106]

Hi All,

we have loaded with OData Service API_MKT_AGREEMENT_SRV Agreements into yM Cloud (Release 1808). The Odata Call looks like this:

The product exists in yM and has a product category assigned. We can use the segmentation and we find the customer that is assigned to this agreement.

The problem is, that the product ID and the category for this agreement term is empty as can be seen here:

When doing a OData Call to call the current agreements on the other side, the product ID is shown:

[Kunal_Bansal · Accepted solution]

Dear Oliver,

Please follow the help document once again:

• https://help.sap.com/viewer/9775a1fb912c487b961bd59cd6179c3a/1805.500/en-US/96e08ba20f5f4dc1b3fce433...
• https://help.sap.com/viewer/9775a1fb912c487b961bd59cd6179c3a/1805.500/en-US/ef61a9b667c84404bee37775...

Best Regards,

Kunal

[former_member355106 · Accepted solution]

Dear Kunnal,

after two days of trying still the product ID is not becoming visible in Segmentation. The attributes we use to show the product of an agreement are:

The agreements are loaded normally and we also add the Marketing Area and other information without any problem.

Our OData Load is currently like this here:

Content-Length: ###
Sap-Cuan-SourceSystemId: C4C
Sap-Cuan-SourceSystemType: EXT
Sap-Cuan-SequenceId: SEQUENCE_ID_1236
Sap-Cuan-RequestTimestamp: 20180404141617.0000001
Sap-Cuan-ExternalReferenceId: REFERENCE_ID_1237
Sap-Cuan-StagingAreaRequestModeSynchronous: false

{"MKT_AgreementOrigin":"1",
"MKT_AgreementExternalID":"2100000006_Z0000003",
"MKT_AgreementType":"1",
"MKT_MarketingArea":"MASPXX",
"MKT_AgreementIsCanceled":false,
"MKT_AgrmtCancellationReason":"",
"ContactID":"2100000006","ContactOrigin":"SAP_C4C_BUPA",
"OriginDataLastChgUTCDateTime":"/Date({{$timestamp}}000)/",
"MKT_AgreementStartDateTime":"/Date(1491315187000)/","MKT_AgreementEndDateTime":"/Date(1649081587000)/"
}

--changeset_77162fcd-b8da-41ac-a9f8-9357efbbd621
Content-Type: application/http
Content-Transfer-Encoding: binary

PATCH AgreementTerms(MKT_AgreementOrigin='1',MKT_AgreementExternalID='2100000006_Z0000003',MKT_AgrmtTermsStartDateTime=datetimeoffset'2012-01-01T00%3A00%3A00Z',MKT_AgrmtTermsEndDateTime=datetimeoffset'2022-12-31T00%3A00%3A00Z') HTTP/1.1
Content-Type:  application/json
Content-Length: ###
Sap-Cuan-SourceSystemId: C4C
Sap-Cuan-SourceSystemType: EXT
Sap-Cuan-SequenceId: SEQUENCE_ID_1236
Sap-Cuan-RequestTimestamp: 2017-04-04T22:47:01
Sap-Cuan-ExternalReferenceId: REFERENCE_ID_1236

{"MKT_AgreementStatus":"A",
"MKT_AgreementRenewalType":"3",
"ProductOrigin":"SAP_C4C_PRODUCT",
"ProductID":"Z0000003",
"MKT_AgrmtCanclnConditions":"",
"MKT_AgrmtCanclnDcsnToDateTime":"9999-01-01T00:00:00Z",
"MKT_AgrmtProlngnDcsnFromDteTme":"2019-01-01T00:00:00Z",
"MKT_AgreementPaymentFrequency":"6",
"MKT_AgrmtPaymentIsInAdvance":false,
"OriginDataLastChgUTCDateTime":"/Date({{$timestamp}}000)/"
}

--changeset_77162fcd-b8da-41ac-a9f8-9357efbbd621--

--batch--

Any more hints what could be wrong?

[Kunal_Bansal · Accepted solution]

Dear Oliver,

We will need to check into your system directly, do you have an existing open incident?

If not, please create one and I will have a look into it.

Best Regards,

Kunal

[former_member355106 · Accepted solution]

Thank you very much. Incident is 423468/2018.

[Kunal_Bansal · Accepted solution]

I see our developer is already working on it, give us sometime to get back to you with a solution.

[former_member355106 · Accepted solution]

Problem was an Error in SAP Standard Coding which was fixed via Incident.