Skip to Content
Technical Articles
Author's profile photo Sachin Balmiki

VMS upgrade S/4HANA 1610 to 1909

When vehicle creation is triggered using CREA action, system triggers creation of CUOBJ object which is holding the configuration object of the vehicle. Once vehicle is created a a vehicle record is created in the table VLCVEHICLE where inthe field CUOBJ gets updated with a number, this number is generated by the Number range object CU_INOB

In one of the recent customer upgrade from S/4HANA 1610 to 1909, it was observed that Sales order creation or at VELO transaction at the time of Creation of Vehicle below dump appears:


Standard method CL_CU_CONFIG_INSTANCE à create_new_cuobj has been modified in the new version to create internal object number (number range) while creating a vehicle. The number range that the new version looks for is “03” but there is no number range “03” in the number range definition for the object CU_INOB. Hence there was dump. The standard number range “01” provided occupies the whole available range (18 digits).

The same check is validated again when the configuration modification is done at the creation of the vehicle or creation of sales order at VA01.

You can also verify the number range data for the object in the table NRIV.

In order to fix this issue, please refer SAP note. 2610381 – Short dump during sales order creation

Go to transaction SNUM for object CU_INOB and maintain the interval exactly like this:

No. From No. To Number
01 000000000000000001 899899999999999999
02 899900000000000001 899999999999999999
03 999900000000000001 999999999999999999

Post updating the number range details, Please test creation of Vehicle from VELO transaction & also test creation of a sales order manually from VA01 with configurations to validate whether the issue is resolved or not.

Assigned Tags

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