SAP for Automotive Discussions
Connect with fellow SAP users in discussions to troubleshoot challenges, share best practices, and fuel each other's success. Join a conversation or start your own.
cancel
Showing results for 
Search instead for 
Did you mean: 

un updated and displyed field in /dbm/vm

kaus_desh
Contributor
0 Kudos
355

Hi

when we enter in to vehicle master /dbm/vm, we use to get a data tabs on LH side.

there is a TAB called VEHICLE GENRAL DATA in that ....there are 3 field entries

techinical field name - functional names as under

PDDATU- production date

PSDATU- planned dely date

CDDATE- Confirm delivery date

i want to use those fields how can i get it activated ? these are under display mode though we select VEHICLE EDIT function( action QMOD).

Kaustubh

1 ACCEPTED SOLUTION

Former Member
0 Kudos
237

Hello,

Following Fields in the vehicle master : General DATA are in display mode.

PDDATU- production date

PSDATU- planned dely date

CDDATE- Confirm delivery date

As per SAP these fields are getting updated in vehicle master from different VMS actions ( Processes).

It is not advisable to Open up these fields if you are not using these VMS actions ( Processes).

If requirement for these fields you can add separate additional fields.

Sanjeev Dhavan

View solution in original post

3 REPLIES 3

Former Member
0 Kudos
238

Hello,

Following Fields in the vehicle master : General DATA are in display mode.

PDDATU- production date

PSDATU- planned dely date

CDDATE- Confirm delivery date

As per SAP these fields are getting updated in vehicle master from different VMS actions ( Processes).

It is not advisable to Open up these fields if you are not using these VMS actions ( Processes).

If requirement for these fields you can add separate additional fields.

Sanjeev Dhavan

Former Member
0 Kudos
237

Hi Kaustubh,

all three fields are originally VMS fields. They're currently not actively used in DBM.

In VMS, the production date can be e. g. set using the vehicle creation action CREA (which is not used by DBM). You could enhance or create a DBM action in a way that you can also set the production date via DBM actions.

Refer to the SAP note on the DBM vehicle action enhancement concept for details about how to do that.

The planned delivery date is never set explicitely by a user. It's implicetely determined based on customizing made in transaction OVELO11.There you can define the remaining delivery time for the vehicle based on an action executed. See documentation about vehicle action matrix customizing for details.

I think in VMS there's also a BAdI which can be used to influence the determination of the planned delivery date.

By the way, in a similar way as the planned delivery date, you can also let vehicle actions set the location of a vehicle based on customizing settings in OVELO11.

Regarding the confirmed delivery date, I think (I'm not sure) that there's also functionality in the VMS area which can determine it and that therefore the confirmed delivery date (similar to the planned delivery date) should not be entered explicitely).

Kind regards,

Steffen

kaus_desh
Contributor
0 Kudos
237

thanks for the answer