Hi Kay,
SAPnote #2029981 does not apply in your case as you are not using any Oracle hint with aliasing in your code.
It seems like SAP introduced a (new) client awareness in its DBSL as the join condition reflects that. I would guess that both tables (/gkv/cd01_bn_npo and /gkv/cd01_bn_nko) are client specific. This makes sense from a logical/application point of view, but can lead to execution plan changes, especially if more or different join conditions are applied (instead of restrictions).
>> But in SAPM i got a full-table-scan instead of index access via BNDTA_AGNR which is selectiv enough.
Only a FTS, that changed? Can you please post both execution plans in DBMS_XPLAN output.
Regards
Stefan