Error:-Action Create Vehicle and Sales Order has not been executed

[Former Member]

Hi All,

In VELO i have selected action CRCO in that i am getting the following error.

Action Create Vehicle and Sales Order has not been executed

Message no. VELO033

Any assignment is missing????

Reg.

Amol

[Former Member]

Hi Amol,

it's a bit hard to say what went wrong based on the information provided.

As CRCO is an interlinked action, you might be able to tell which of the two actions involved failed: CREA or CUOR. If it's the first one, there's no vehicle at the end. If it's the second one, a vehicle is created but not sold. This narrows down the possibilities.

Can you please check the log? (button on the upper left side of the VELO transaction's screen)? This typically gives you a more detailed message when you double-click on an entry on the left side. Hopefully the log contains the answer to your question.

If not, I can't tell you as I don't know what was already set up in your system, what master data and customizing entries have been created, etc. Please have a look at the VMS online documentation for information about specifica actions and about information regarding how to set up VMS in general.

Do you have the required authorizations for the action? Is the vehicle matrix set up to allow the action (For the interlinked action as well as for the elementary actions)? Is matrix determination set up? Is the material (model) assigned to the role which is assigned to your user? etc.

Kind regards,

Steffen

[Former Member]

Hi Stefen,

We are doing CREA for the First time.Are we suppose to start with goods receipt in VMS? or MB1C???

or any other option.

Our Action Matrices is

Action control old status Action new status

ZA RFS CRCO RFD

ZA RFS CREA RFD

ZA RFS CUOR RFD

Reg,

Amol

[Former Member]

Hi Amol,

my recommondation to you is to first read the online documentation about VMS. There you can find information about how VMS works in general. It also contains process examples (read: sequences of actions), descriptions of actions and how to do the master data / customizing set up.

http://help.sap.com/saphelp_dimp50/helpdata/EN/91/88c43ace7a3b46e10000000a114084/frameset.htm

The first action you execute on a vehicle needs to be an action which actually creates the vehicle (There's a flag in action customizing which shows if an action is a vehicle creation action).

The goods receipt action doesn't create a vehicle. You're not supposed to use transactions like MB1C when working on VMS vehicle processes.

The action matrix set up you describe in your last post is not a good one ...

ZA RFS CRCO RFD

ZA RFS CREA RFD

ZA RFS CUOR RFD

This won't work because the new status set by CREA (RFD) isn't a possible old status for CUOR in your set up.

Also, when creating a new vehicle, there's no old status. Instead of the example above, use something like this ...

ZA - initial - CRCO - RFS

ZA - initial - CREA - RFS

ZA - RFS - CUOR - RFD

By the way, didn't you find any useful information in the vehicle action log (see my previous posting)?

Kind regards,

Steffen

[Former Member]

Hi Stiffen,

i have read the online help of VMS.

i have defined action control as

ZSEC CREA RFS

in OVELO11

still i am getting the error as no Action Control Found in Log.

Any assignment is missing?

any step before VELO is missing?

Reg.

Amol

[Former Member]

Hello,

check the settings in transaction VELOS.

Kind regards,

Steffen

[bcrao]

Hi Amol,

Is your problem solved?

[Former Member]

No,

i have made Action "ZSEC" as Primary Action, in this i have defined CREA Action.

But Still i am getting Error Log as No Action Control Found.

Reg.

Amol

[Former Member]

Hello,

as I mentioned above, please check your settings in transaction VELOS. This is the transaction which is used to determine the action controls (a. k. a. action matrices) for the vehicles. You need to make sure that for the master data / organizational data you're using, an appropriate record in VELOS exists.

In the documentation, you'll find a chapter about matrix determination via transaction VELOS. There're quite a few possibilities how to enter data in VELOS correctly. I can't explain all that here, so please have a look at the documentation.

The error message to which you refer to has a long text in which the data used for matrix determination is specified. This you can compare this with what you've set up in VELOS to see why it doesn't fit.

Kind regards,

Steffen

[bcrao · Accepted solution]

Hi Amol,

I am giving example of status creation and action matrix configuration.

MM01, MM02 are primary action matrix and SD01 is secondary action matrix

1. On the Change View u201CDefine Vehicle statusu201D: Overview screen, choose New Entries.

2. On the New Entries: Overview of Added Entries screen, make the following entries:

Veh.Status

(Vehicle Status) Descript.

(Description of Vehicle Status)

* Generic *

M* generic M*

P* generic P*

L040 Goods Received

L050 Vehicle at Rework

L060 Vehicle at Rework

L080 End Rework, Vehicle Available

L090 End Rework, Vehicle Available

L100 Goods Issued

L110 Goods Issued

L200 Vehicle at Dealer

L210 Vehicle at Dealer

M005 Vehicle Planned

M006 Vehicle Created

M010 Vehicle Purchased

M020 Inbound Invoice Created

M030 Goods Received

P120 PO confirmed by OEM

P130 Manufactured

P140 Shipped

P180 VIN Assigned

P200 Shipped to End Customer

P210 Arrived at End Customer

RS01 Vehicle Reserved

SD01 Customer Spec. Veh. Identified

SD05 Sales Order Created

SD10 Rework Ended

SD25 Goods Issued

SD30 Outbound Invoice Created

SD35 Delivery Created

W200 Master Warranty Assigned

W300 measure points assigned

W400 General Object Number Created

1.

Action Control Old Vehicle Status Action New Vehicle Status Check Entry

MM01 CREA M005

MM01 * HIDE *

MM01 * SHOW *

MM01 * MSSO *

MM01 L040 INIV M020

MM01 L100 ZEND L200

MM01 L200 GEOB W400

MM01 M005 CMOD M005

MM01 M005 ORD1 M010

MM01 M010 MORD M010

MM01 M010 ZPOC P120

MM01 M020 CUOR *

MM01 M020 GOIS L100

MM01 P120 ZCON P130

MM01 P130 SMOD P180

MM01 P180 GORE L040

MM01 P200 ZCUS P210

MM01 W200 ZSHI P200

MM01 W400 WYVH W200

2. Choose Save and Back.

3. Repeat the step 2-5 to make the following entries:

Action Control Old Vehicle Status Action New Vehicle Status Check Entry

MM02 CRCO M005

MM02 CREA M005

MM02 CUOR M005

MM02 L050 UGRE L080

MM02 L060 INIV L050

MM02 L060 UGRE L090

MM02 L080 GOIS L100

MM02 L090 GOIS L110

MM02 L090 INIV L080

MM02 L100 ZEND L200

MM02 L110 INIV L100

MM02 L110 ZEND L210

MM02 L210 INIV L200

MM02 M005 CUOR M005

MM02 M005 ORD1 M010

MM02 M010 CCPO M010

MM02 M010 MORD M010

MM02 M010 ZPOC P120

MM02 M020 UORD L050

MM02 M030 INIV M020

MM02 M030 UORD L060

MM02 P120 CCPO P120

MM02 P120 MORD P120

MM02 P120 ZCON P130

MM02 P130 CCPO P130

MM02 P130 MORD P130

MM02 P130 SHMT P140

MM02 P140 CCPO P140

MM02 P140 GORE M030

MM02 P140 MORD P140

SD01 CREA SD01

SD01 * SHOW *

SD01 * HIDE *

SD01 RS01 BUPA RS01

SD01 RS01 CUOR SD05

SD01 SD01 RSVN RS01

SD01 SD05 BUPA SD05

SD01 SD05 OUIV SD30

SD01 SD30 DELI SD35

SD01 SD35 GOIS SD25

SD02 CRCO SD05

SD02 CREA SD01

SD02 SD01 CUOR SD05

SD02 SD05 BUPA SD05

SD02 SD05 CCPO SD05

SD02 SD05 CHCO SD05

SD02 SD05 UGRE SD10

SD02 SD10 CHCO SD10

SD02 SD10 DELI SD35

SD02 SD25 OUIV SD30

SD02 SD35 GOIS SD25