Skip to Content
Technical Articles

lock dependent with foreign keys causes syntax errors as of 2105

The problem before the upgrade

With the upcoming upgrade to 2105 you might run into problems if the coding of your behavior definitions still contain the outdated syntax that uses foreign keys rather than using the new syntax that uses associations.

If you do not change your coding your application will stop to work.

As you can see in the screen shot below the statement

lock dependent ( field_in_cds_view = field_in_root_cds_view )

is currently already shown as a warning.

which states

The same can also be obtained if you run an ATC check on the package

Then you will obtain the following message:

The solution

Step 1 – Change the BDEF

You have to switch to the new coding (latest after the upgrade because than your code will stop to work).

lock dependent by _<name_of_association>

But this is not all …

Step 2 – Change the projection of the BDEF

In addition you have to edit the behavior definition projection because otherwise you will still get dumps.

When checking the behavior definition of the projection view you will find the following two warnings:

The association "_HOLIDAY" of the basis entity "ZFCALI_HOLIDAYTEXT_351" is missing in the behavior definition of projection entity "ZFCALC_HOLIDAYTEXT_351". 

This means that the "lock master" relation cannot be projected.

 

 

After adding the statement

use association _<name_of_associtation>

your RAP BO will continue to work as expected.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.