Skip to Content

My Experience in dealing with inconsistent number range issue

I am sharing my experience in dealing with many inconsistent issues, number range issues,
express document/update fails.

Sometimes user may come across a temporary or inconsistent short dump while executing a process step or a particular transaction.

These inconsistent issues impact completion of activity (can be test /support/implementation activity)

Below method supports to analyze such issues at an earlier stage &resolve the issue wherever possible at users end itself.

~ Detailed analysis of short dumps or runtime errors using transaction ‘ST22’ helps
in understanding & resolving the root cause of the issue by highlighting
problem triggering code line, tables & fields.

~ Based on the information available on short dump trigger point, user can navigate to the
relevant tables & find the reason for inconsistency.

~ If available, perform necessary customizing settings to rectify the issue.

There are two kind of inconsistent issues I have seen:

  1. Issues which triggers dumps in ST22
  2. Issues without triggering dump in ST22

Example: where dump is triggered in ST22


Delivery number not being updated at table level

In given example, user is trying to create a delivery in transaction ‘VL01NO’.
After entering all necessary data when user saves the delivery document,   a delivery number is assigned based on
number range configuration & a success message appears with delivery
number.

/wp-content/uploads/2014/01/vl01no_367725.png

/wp-content/uploads/2014/01/del_367726.png

  However, in this particular example, on exiting the transaction a ‘Express information’ message appears with information “Update was terminated” which indicates that though a delivery number has been assigned to earlier transaction still the delivery doesn’t exist & the database is not updated with delivery information.

/wp-content/uploads/2014/01/express_367764.png

To analyze the issue, click on Inbox button, which navigates you to Business Workplace Inbox.  Look up the latest document with subject ‘Update was terminated’ & check the details relevant to update termination.

SWU3.png

For detail analysis of the issue, run transaction ST22, select today’s dump & search
appropriate dump based on user name. Go to the Source code Extract:

/wp-content/uploads/2014/01/st22_367775.png

As highlighted, choose the code line which triggered short dump. In this example,
the problem is occurring at the insert statement. You can discuss this with
your abaper too from here.

Based on the table information at problem triggering statement, check table VBPA, which stores the value with sales document number & partner function. In data browser, check the table entries for sales documents as highlighted.

VBPA.png

The delivery document number which was assigned in earlier transaction & following
numbers are already available in database. This indicates, there was a duplicate insert happening in this transaction at database leading to generate a short dump/update termination message.

This clearly directs to the root cause of issue to be a customization issue having a wrong
number range customizing set up for the delivery document. Based on delivery type customizing, choose appropriate number range & update the number range status to most latest available number.

SDDoc.png

After correcting number range customizing for delivery, repeat steps for delivery
creation with same data. User will be able to create delivery documents successfully;
the delivery number will be updated in table VBPA.

DWE.png

The new Delivery has been created & saved in the table.

Final vBPA.png

Example 2: when there is no dump in ST22

Change Pointer ID already Exist

In given example, user is trying to create a MPO (material Planning Object) in transaction ‘/ISDFPS/MPO’. After entering all necessary data when users save the document and exit the transaction. The termination pop up appears.

/wp-content/uploads/2014/01/mpo_367787.png

/wp-content/uploads/2014/01/express_367764.png

User does not find a log in ST22 as there is no short dump generated. In this case user
should check the SM21 (System logs).Double click on the system log and check the details for fail.

/wp-content/uploads/2014/01/sm21_367789.png

Navigate to transaction SM13 for more details

To find out the details of update termination, check SM13 (Update Requests)

/wp-content/uploads/2014/01/sm13_367794.png

/wp-content/uploads/2014/01/upd_367795.png

/wp-content/uploads/2014/01/changept_367799.png

Solution to correct this:  after searching with “Material_Write _Document” update fail, I
found a note: 1700295 which solved the issue.

Check the Number range for change pointers in transaction BDCP

The reason for update termination: Write Operation is failed. We can search with these search terms for Notes.

Similar sort of issue was occurring in transaction VK11 & it’s been solved in following discussion

http://scn.sap.com/thread/3278000          

  

40 Comments
You must be Logged on to comment or reply to a post.