Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
Transferring asset hierarchy data between the root assets within Cognite poses a challenge due to a limitation within the Cognite Data Fusion (CDF) platform. However, this functionality is readily supported within SAP. In other words, while SAP facilitates the seamless movement of asset hierarchy data across various root assets, Cognite's CDF platform lacks this capability, presenting a constraint in data engineering management and pipeline failures. This limitation results in the real time failures as SAP changes are typically not in our control and business teams perform these changes periodically.
Moving asset hierarchy across root assets
API and SDKs
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Hi@Harsha , thanks for the feedback!
@Christian Flasshoff @Diego Antonino and team can advise further if you decide to go that route.
Is this something that you’re encountering with the Cognite SAP Extractor or a custom extraction method? If it’s the latter, it should be possible with a few extra lines of code to recreate an asset under a new root node based on the condition that the root is changing. I’m sure
However, in general we are not prioritizing features on the “classic” asset resource type at this time as the strategy is to move this to Data Modeling (DM). I will raise this with the team working on bringing Assets into DM to see if this same behavior is expected there.
This problem arises with the real-time APIs.
We write the data to Cognite APIs from S4 Hana to the CDF through SAP PO PI.
Changes occur in the asset hierarchy within SAP, which are beyond our control, affecting the root assets of CDF. Consequently, the interfaces encounter failures, indicating that data transfer across root assets in CDF is not possible.
Correct, we need the same functionality in Cognite, which does not require any additional programming, but is simply possible in the standard.
Anything else leads to unnecessary additional work and complication for each such case. As this is a standard functionality in SAP, it will be just as important and critical for other customers.
Hi@Harsha apologies for the slow response. I believe @Diego Antonino was following up with some procedures for how this can be implemented based on the API today.
As mentioned, it’s not something we are considering as an update at this time in the Assets API, as our primary focus is on getting Assets fully into Data Modeling, but we will keep this idea open as we can consider it at a later time as a feature on the Data Modeling version of Assets.