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          

  

To report this post you need to login first.

40 Comments

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

    1. Nisha Agrawal Post author

      Ya mozzaM, i completely agree . its very tricky to analyse such issues. every other day we  face such issues.But definitely by solving such issues, atleast my technical skills improved a lot. πŸ™‚ just  thought of sharing my tricks & experience on the topic.

      Thanks for reading.

      (0) 
      1. ' MoazzaM '

        This is a good aproach to learn ABAP and BASIS things along with SD. With this approach one can be a good techno functional consultant which is demand of almost every client these days. Keep up this spirit 😎

        Thank$

        (0) 
  1. Jyoti Prakash

    I simply rated the content, as it is a nicely drafted & the choice of topic to represent your experience. But, being a blog you can reduce the number pictures shared. Refer one of the older blog which can assist you in improving your Blogger experience.

    Blogging 101 in SDN and BPX

    Thanks.

    Best Wishes, JP

    (0) 
    1. Nisha Agrawal Post author

      Thanks JP Sir πŸ™‚ definitely i agree with you.Initially i thought of preparing a document and collected all the screenshots. But as its my experience, then changed it to blog.

      I will keep this in mind for my next post.

      Feedback  always helps.

      Thanks for reading πŸ™‚

      (0) 
  2. Srinu S

    Thanks Nisha for sharing the useful document which is very helpful for future reference for many. Keep sharing πŸ™‚

    Srinu.

    (0) 
  3. Nitin Jinagal

    I need to give sometime to this doc before I could understand it. Appears very valuable (everyone is saying) πŸ˜‰

    I have bookmarked it and I’d be able to comment only after I understand this 😐

    Thank you for sharing!!

    ntn

    (0) 
  4. Anandkumar KS

    Hi Nisha,

    Greetings for the day!!

    I would like to inform you that my first support issue was the “Number Range Issue”, were I found the errors in ST22 and I solved the same.

    But, recently I faced the same kind of number range issue but I can’t find the error in ST22.

    Then I did so many research and at last I found the solution and it took more than a normal time.

    Now, from your document I got SM22 t code and steps to find the this type of issues. I hope this document helps me to solve this type of issues in future.

    Thanks a lot.

    with best regards

    AKS

    (0) 
    1. Nisha Agrawal Post author

      Thanks AKS for reading & your time πŸ™‚ . I have done a lot of reasearch on these kind of inconsistent & temperory issues. After all this i planned to share my experience with all my SCN members.So they can save some amount of time  on such issues. I am happy to learn that you are going to use this information.

      Your feedback makes think “What Next”. Thanks a lot.

      Regards

      Nisha

      (0) 
  5. yuvaraj v

    Hi, Nisha

    I am new to SCN just gone through your post, it’s really helpful for me, because recently i faced this issue and unable to solve, handover to some one. If i could have find it earlier i can definitely  solved. it so helpful for me , i would really appreciate you for sharing your knowledge and time.

    Thanks

    Yuvaraj πŸ™‚

    (0) 
    1. Nisha Agrawal Post author

      Thanks Yuvraj πŸ™‚ . I am very happy to learn that this article is helpful for you.

      Certainly i will keep sharing my finding with all SCN members.

      Regards

      Nisha

      (0) 
  6. Ankush Khatri

    Hi Nisha,

    Thanks a lot for such useful information.

    The blog was quite informative. I used to face same issues during SP execution and had to create messages for the same(that too consulting).

    Now, at least i can figure out the real problem.

    Regards,

    Ankush

    (0) 
  7. Phanikumar Valiveti

    Hi nisha,

    Good informative doc.

    But the error (change pointer Id-Object name ALE_CP)—as per you got the error in VK11 mainatinence—is it so???

    Are you following any procedure in updating pricing master other than standard??

    Phanikumar

    (0) 
    1. Nisha Agrawal Post author

      Thanks PhaniKumar for your time & feedback πŸ™‚ .

      I was creating the condition records with std process only using VK11 .In fact , you can get this issue in any master or transaction data if there are number range inconsistency.

      This was just an example.

      Regards

      Nisha

      (0) 

Leave a Reply