Skip to main content

Hello everyone,

 

I’m using an augmented attribute  “Sendout y/n” which is based on this record identifier: EORD → Material || Plant || Supplier. 

This attribute is used within a dashboard and can be manually set for the default value “no” to “yes”.  In the case a user changes this combination: 

Material: 123456, Plant: XY, Supplier: SupplierA → 123456XYSupplierA → Sendout (Augmented Attribute): Yes, I can then use this attribute for a connected AF.

 

Let’s say the SAP EORD table data changes → orderbook changes the record identifier would now be: 

Material: 123456, Plant: XY, Supplier: SupplierB → what would now happen? Would the combination 123456XYSupplierB be on Sendout: Yes? Or would the augmented attribute as it is based on the MATNR, WERKS, LIFNR know that the identifier itself changed and be by default No again?

 

When changes occur I would need the combination 123456XYSupplierB to have the augmented attribute with: No by default. 

I’m assuming that this will be the case, however, I’m not 100% sure. Can someone confirm?

 

Thanks and best regards,

Julia Bauer

 

 

Hi Julia,


The augmented attribute should be having a default value as NO because your identifier itself is changing.
There’s no record for the old identifier so new one should pick default value whatever you have set.

 

Regards,

Lokesh Tuteja

Hello ​@Lokesh Tuteja , I just tested this and it unfortunately did not work as expected. Meaning even if the supplier changes, the flag will still be “Yes”. How could I solve this alternatively?

 

Best regards,
Julia Bauer

Hi Julia,

Thanks for reaching out—that's a really interesting use case.

You are correct in your assumption. The augmented attribute is tied to the unique identifier created from Material + Plant + Supplier. When any of these values change, a completely new augmented attribute is created.

So, in your example, the system would treat 123456XYSupplierB as a brand new record. Since this new record doesn't have a value set for "Sendout" yet, it will automatically be assigned the default value, which is "No". The "Yes" setting on the old record (...SupplierA) will not carry over.

Happy to jump on a call to discuss this further if that helps.

Kind regards,
Jan

​@jan.mölic  - Hello Jan, thanks for reaching out. Unfortunately I cannot confirm this assumption. I have changed the order book supplier within SAP and then reloaded the data in Celonis and the materia was still tied to the augmented attribute with “yes”. If you’d be open for a call, that would be I think the most efficient way to clarify this behavior. Thanks! BR Julia

From my experience with augmented attributes in Celonis, the behavior you’re describing is correct: the attribute is tied to the specific record identifier. So if your EORD table changes—e.g., the supplier changes from SupplierA to SupplierB—the new combination (123456XYSupplierB) will not inherit the previous manual value. By default, the augmented attribute for this new identifier should be set to No until someone updates it manually.

This is a good example of how augmented attributes behave like dynamic variables in a workflow: they track data combinations rather than static records. When building applications or dashboards that depend on these attributes, it’s important to account for these changes so your logic and connected analyses always reflect the current underlying data.

You could also implement checks or automation to reset attributes when new identifiers appear, which can help maintain consistency in your dashboards and connected AFs.

Reply


Community Code of Conduct