Hello

I’m working on migration of IFS V8 to IFS Cloud 24.1.4 and I’m publishing custom attributes.
On InventoryPartInStock entity, I have a custom attribute which is a readonly.
For this, we use the following statement (adapted to the new db structure) :

SELECT
    pol.cf$_gross_weight_rw
FROM
    purchase_order_line_cfv pol
    INNER JOIN receipt_inv_location        ril ON pol.order_no = ril.source_ref1
                                               AND pol.line_no = ril.source_ref2
                                               AND pol.release_no = ril.source_ref3
    INNER JOIN inventory_part_in_stock    ipis ON ril.contract = ipis.contract
                                               AND ril.part_no = ipis.part_no
                                               AND ril.configuration_id = ipis.configuration_id
                                               AND ril.location_no = ipis.location_no
                                               AND ril.lot_batch_no = ipis.lot_batch_no
                                               AND ril.serial_no = ipis.serial_no
                                               AND ril.waiv_dev_rej_no = ipis.waiv_dev_rej_no
                                               AND ril.eng_chg_level = ipis.eng_chg_level
                                               AND ril.activity_seq = ipis.activity_seq
WHERE
        ipis.contract = :contract
    AND ipis.part_no = :part_no
    AND ipis.configuration_id = :configuration_id
    AND ipis.location_no = :location_no
    AND ipis.lot_batch_no = :lot_batch_no
    AND ipis.serial_no = :serial_no
    AND ipis.eng_chg_level = :eng_chg_level
    AND ipis.waiv_dev_rej_no = :waiv_dev_rej_no
    AND ipis.activity_seq = :activity_seq

And following request arguments : 

v.contract, v.part_no, v.configuration_id, v.location_no, v.lot_batch_no, v.serial_no, v.eng_chg_level, v.waiv_dev_rej_no, v.activity_seq

When validating the attribute before approval and entity synchronization, I got the following error :

The column configuration_id refered to in table t is not an approved persistent Custom Attribute.

The problem is, configuration_id is not a custom attribute, but a standard attribute of the table.
Seen on the view, and on db, the field is available and has data.

What I tried is to replace the sql statement to test the argument on dummy table :

SELECT :configuration_id FROM dual

The issue is still there, and I can’t figure out what is the problem to fix.
Removing the argument and the where clause, keeping the join on the field make the statement working.
But this is not the good solution, we need configuration_id as argument.