Setting customer as obsolete

[SauMaris]

Hi!

We have been utilizing a following process in our on-prem system v1709 SP01.

1) customer is deleted in SAP (ex-hybris) Commerce system

2) customer is received as "obsolete" in SAP Marketing system using a CUAN_IMPORT_SRV

3) set "obsolete" customers "cold" with CUAN_CE_IC_SET_COLD with a flag "Deleted in a Source System"

4) delete "cold" customers with CUAN_CE_IC_DELETE_COLD with a flag "Deleted in a Source System"

Import service used to mark whole customer as "obsolete", but now only a particular facet in marked as obsolete.

        {
            "EMailAddress": "email@example.com",
            "Id": "1-2-3-4",
            "IdOrigin": "SAP_HYBRIS_CONSUMER",
            "IsConsumer": true,
            "Obsolete": true,
            "Timestamp": "2018-11-29T11:30:41"
        }

We are frequently updating our system with latest SAP notes. Since when this has been changed? Is it a bug or requirements have changed?

How shall we mark the whole customer as obsolete with this call, if we don't have anything else in the remote system more than email address and id?

[SauMaris · Accepted solution]

Actually it seems to be a bug implemented with a note 2713065. As soon as I reversed the note implementation, all facets are being updated and root table as well.

[KunalBansal]

Dear Maris,

Could you first check if the note 2696905 is installed in your system?

Thank you.

Kunal

[SauMaris]

It is not about these reports (and, yes, note is applied), but about the Import service not setting "obsolete" flag in the root table, only for one particular facet in the facet table. In the odata call we pass "obsolete" at a customer level, not facet level, so it is unclear why it stopped working.