Need Help : Native SQL ABAP dump “DBIF_DSQL2_SQL_ERROR” on procedure “APS_ORDER_CHANGE”.

[Former Member]

Hi All,

We are facing an issue and want to check if you have seen it in past and can help us in resolving it. Any input will be greatly appreciated.

Issue:
While executing product heuristic on few product/location combinations in product view, we encounter native SQL ABAP dump “DBIF_DSQL2_SQL_ERROR” on
procedure “APS_ORDER_CHANGE”.

We were debugging for one particular product/location combination, this combination has 2 planned orders, and the Internal order number of these planned orders are
given as input to this procedure “APS_ORDER_CHANGE”. These 2 internal order numbers are the only inputs given to this procedure.

When we try to delete those planned orders we again encounter same ABAP dump. There are many product/location having the same issue.

We also checked variable duration maintained on the PPM of this product/location, and was fine.

For more deatils : Please check the attached document of downloaded ABAP Dump.

Thanks and Regards,

Pritesh Jain

[tiago_furlanetto]

Hi Pritesh.

What liveCache version/build/patch are you on? What is the database error text shown in this dump?

If it is exactly the one below

Database error text........: "POS(1) Work rolled back: tExcept 30730 in

APS_ORDER_CHAN"

You can try running report SLCA_EMERGENCY_SWITCH, then turning off the option "Verify that all input table records have been read" and saving the results. If that solves the issue, you can use this as a workaround until the next time you upgrade your liveCache build.

To get a clear root cause, you may need to create an OSS incident under BC-DB-LCA component providing a reproducible example.

Regards,

Tiago

[Former Member]

Hi Pritesh

I have not encountered this specific error but would suggest to do a Livecache consistency check (/SAPAPO/OM17) as a first step. You can find more on this on http://scn.sap.com/thread/429219.

You may also like to check OSS note 1596873 if that is applicable in your scenario.

Thanks,

Prasun