cancel
Showing results for 
Search instead for 
Did you mean: 

Change Pointer ID already exists

nisha_sharma1
Active Contributor
0 Kudos

Hello All

We are getting an Express document  mentioning "Update terminated" in transaction VK11 while creating condition records for condition type PR00.

While seeing the details of express document : it says "Change pointer ID already exists".

This sort of issue is coming quite frequently. if anyone has faced such issue in past , please share the analysis & solution.

Regards

Nisha

Accepted Solutions (1)

Accepted Solutions (1)

jpfriends079
Active Contributor
0 Kudos

Hello Nisha,

For further details on termination error, kindly check corresponding dump in ST22,

There you can get is error message number and code error analysis, where this code inconsistence is happening.

For further assistance, can you provide the error number or share the dump.

Regards, JP

nisha_sharma1
Active Contributor
0 Kudos

Thanks JP for reply.

This express document is not generating any dump in ST22. I checked that as well.

But the update of FM:   RV_KONDITION_SICHERN_V13A is failing , found in system updates Sm13.

Regards

Nisha

jpfriends079
Active Contributor
0 Kudos

Thats nice!
This FM(RV_KONDITION_SICHERN_V13A) is used for validating the update based on new & existing values. You can refer few of the following SAP Notes (but, those are preetty older thread, still can provide some hints)

- Note 4336 - Update termination during condition maintenance

- Note 64822 - Performance problems for condition records

- Note 115993 - Update termination in sales pricing

- Note 190373 - Termination when saving condition records

Regards, JP

nisha_sharma1
Active Contributor

Thanks JP. There is no direct Note to correct this one.

Finally did a lot of analysis arround multiple tables and number ranges.

Steps to correct the issue:

1) Reset the number range for change pointers, which is leading to change pointer exists in TA: BDCP

2) Compare the highest number of conditiuon record in tables A000 -A999 and KONH,KONP,KONM

3) Reset the no range to highest no received in VN04.

this should solve the issue.

Regards

Nisha

Answers (0)