cancel
Showing results for 
Search instead for 
Did you mean: 

Force publication status SUCCESS for canonical item

0 Kudos

Hi there,

consider the follwing short datahub example. I have 3 CanonicalProducts with say productIDs 1, 2 and 3 that originate from ERP. I now have a new custom canonical type to reflect a relation between the products, i.e. product #1 consists of #2 and #3. In that case, I would have 2 of those custom canonical items, one for the relation of #2 to #1 and one for the relation of #3 to #1. These canonical relation items might for example be generated by a BOMMAT idoc. Now consider the following fact: products #1 and #2 are of a specific type X and #3 is of type Y (the type might for instance reflect the ERP field MTART). Finally consider the requirement, that only products of type X should be replicated to hybris, and if there is a relation from one product to another product with type different to X, also do not replicate the relation to hybris.

My first idea was to filter idocs on ERP side, s.t. materials with type not equal to X are not send to the datahub at all. In that case I had the problem, that the datahub threw errors, when it was trying to replicate the relation from #3 to #1 since product #3 could not be found (obvious).

My next idea was to send the #3 product to the datahub, but filter out the publication of products with type Y and also filter out the replication of relations containing products of type Y using a publication handler. This is working quite well except of one thing, which is not too good. The filtered out canonical items get a publication status of IGNORED, which leads to the fact, that the datahub tries to publish these items over and over again. And the more of these items sum up in the datahub, the more impact it will have on performance. For that reason, I was wondering, if there is a possibility, to force set the status to SUCCESS, even if the item was not published to Hybris. Actually it might make sense, to introduce a new status like IRRELEVANT , which means not published, but don't try again?

Any suggestions for this issue?

Thanks

Simon

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Simon,

We have had similar requests before. We are currently working a new feature that will provide you the ability to prevent canonical items from being published based on a filter criteria and / or set the canonical publication status to either IGNORED or SUCCESS. We didn't want to add new status since it creates quite a testing burden.

If you want a different status than the default resulting from your custom handler, you will need explicitly set it within the custom handler.

Product Owner, Data Hub

Answers (0)