Automatic Delivery creation through VMS

[tariq_aziz]

Dear Automotive wizards,

We are using the Vehicle Management system for or automotive process as a distributor and retailer.

The sales order - delivery settings are NOT for automatic delivery creation. However, in some cases, the delivery is getting created aytomatically in the background.

Have done some introspection in thes 'some' cases and found that they pertain to our 'used care business'. Therein we are using only standard document typesand no changes have been done in their settings. But in some of those cases whenever a sales order is created from the VMS the R3 is also creating a delivery. This delivery doenst show in the vehicle history hence has to be dug out by looking in the dpcument flow for the sales order. The order / delivery setting are NOT for automatic creation.

Do advise how to go about resolving this unnecessary 'speed breaker' in the IS AUTO highway!

Thanks and regards,

Tariq

[Former Member]

Do you have a batch process creating deliveries in the background or using the delivery due list in dialog ?

Check the "created by" and "created on" fields in the delivery header (LIKP-ERNAM & LIKP-ERDAT, respectively) to try and assist in determining who / how the delivery was created.

Nigel Ross

[tariq_aziz]

Thanks for the pointers but I have explored that earlier and the info therein shows that the delivery was created by the same ID and at the same time when the order was created.

In fact the user is oblivious of the situation too since he/she is working in the VMS and from there they are supposed to move on to create the order after the delivery. But this delivery gets created by itself in the R3, and you would recall that the R3 docs dont get reflect and hence do not update the VMS vehicle status. thereby the vehile status is still as "sales order created" in VMS but the R3 has as "delivery created" there being a mismatch the VMS stops further processing.

By the above you woujld have also got to know that we dont have batch processing or anything like that, pure simple and manual creation of dlivery through the VMS.

The strangest thing is that it happens for only some of the times, and for only some of the users. I have tried comparing he roles for access but all have the same access. Would there be any settings for storage location specific in R3 for delivery creation? or likewise?

Thanks and regards,

[Former Member]

Do you have any user exits or enhancements that may be called during the saving of the sales order, which could be generating the delivery ?

Also - have you any specific code called after the processing of the VMS action ?

[tariq_aziz]

No dear, unfortunately none of those and thats where the big issue lies...cant identify the cause of the error.

Like I asked would it be anything with authorisation or storage location specifc? Do ponder on those lines, if possible.

Many thanks for the cooperation.

[former_member183879]

Hi Tariq,

May be you have a background job schedule somewhere mentioning the primary and secondary status as the precondition. Please check if any variants are available for VELOB transaction code. or some similar tcode made by your people. I am sure that there is a job, which schedules this automatic delivery based on some preconditions like statuses, qualifiers etc.

[tariq_aziz]

Thanks for the pointers but I have explored that earlier and the info therein shows that the delivery was created by the same ID and at the same time when the order was created.

In fact the user is oblivious of the situation too since he/she is working in the VMS and from there they are supposed to move on to create the order after the delivery. But this delivery gets created by itself in the R3, and you would recall that the R3 docs dont get reflect and hence do not update the VMS vehicle status. thereby the vehile status is still as "sales order created" in VMS but the R3 has as "delivery created" there being a mismatch the VMS stops further processing.

No, we dont have batch processing or anything like that, pure simple and manual creation of dlivery through the VMS.