ActionsPDF download from SAP Help Portal:http://help.sap.com/saphelp_di46c2/helpdata/EN/95/47c83abc3c1a54e10000000a114084/content.htm

Created on March 24, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SEand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and othercountries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 21

Table of content1 Actions1.1 Working with Actions1.2 Performing Actions in a Batch1.3 Make-to-Stock Scenario:1.4 Make-to-Order Scenario:1.5 Configurations1.5.1 Handling Configurations1.5.2 Actions and Configurations1.6 Creating Vehicles1.7 Procurement: Purchase Order1.8 Procurement: Incoming Invoice1.9 Sales: Reservation, Quotation, Reservation Request, Inquiry1.10 Sales: Sales Order1.11 Sales: Delivery1.12 Sales: Outgoing Invoice1.13 Goods Movements: Goods Issue, Goods Receipt1.14 Rework (Including Goods Movements)1.15 Processing Returns1.16 Trade-In and Used Vehicle Sales1.17 Service Processing1.18 Special VMS Actions1.19 Warranty Processing

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 21

1 Actions

UseActions are business transactions that represent the business processes involved in the handling of vehicles, for example, creating a vehicle,changing a vehicle, creating a purchase order and creating a sales order.

FeaturesActions can be classified as primary or secondary actions. The terms primary and secondary should not be regarded as higher or lower level, in other

words, they do not indicate a hierarchy. Whether the actions are primary or secondary depends on the individual business processes of the user. Possibledivisions are: procurement actions versus sales actions or logistical actions (actions that affect the vehicle itself) versus financial actions (actions that affectpayment transactions).

Actions affect the vehicle status. Primary actions affect the primary status, secondary actions the secondary status. Primary and secondary statusesexist in parallel and independently of one another. You can control which actions can follow on from one another and which change of status this causes under

Action Controls .There are the following types of actions:

Actions that do not change the vehicle status(for example: vehicle status quotation created , action change vehicle => vehicle status remains unchanged as quotation created ).

Actions that assign a new value to the vehicle status(for example, old vehicle status quotation created , action create sales order => new status sales order created ).

An inter-linking action is an action that comprises two or more linked elementary actions. The term elementary action means, in this case, the same asaction.

When the inter-linking action is started, all the other elementary actions contained in it are performed in the given order. The system processes eachelementary action as a complete action, including setting a new status and updating data.

The use of inter-linking actions is critical if both actions create business documents. If the second elementary action expects data on the databasethat is not written until the first action has been completed, the system cannot perform the inter-linking action.

A whole host of actions are delivered with the standard system. In Customizing, however, you can modify these actions or define your own actions.You can find further information in the IMG documentation Program Actions under Logistics Execution ® Vehicle Management System Enhancements.

1.1 Working with Actions

UseActions form the central functions in VMS. With the exception of actions for creating vehicles, they involve one or more vehicles that you have previously soughtand chosen (see also:Vehicle Search, Searching for Vehicles and Vehicle Overview and Vehicle Details).

FeaturesYou can control every action with authorizations (authorization object C_AUTO_VMS). So you can set up your VMS system so that you, as importer, are

allowed to perform all actions, but your dealer only the actions for the sales orders, inquiries/reservation requests. offers/reservations, assigning of endcustomer and hiding/displaying of vehicles.

You call an action by choosing it in the action list field in the upper screen area and confirming with . You can branch to actions that you have placed onpushbuttons (see below) directly by choosing the appropriate pushbutton. The tab page Action appears. If you have already found and chosen vehicles, theyare copied to the left-hand screen area. In the right-hand screen area you can make your entries for the chosen action.

If you have not chosen any vehicles yet, only actions for creating new vehicles are displayed in the action list field. If you have already chosen vehicles,you only see the actions that are possible in the current process. If the primary and secondary action control is not yet known, too many actions may bedisplayed.

The default settings dictate that only the actions that are allowed for all the selected vehicles are displayed. You can use the parameter nameVELO_ACTLISTBOX = X to define that all the actions are displayed that are allowed for at least one of the selected vehicles.

You can place up to four actions that you use most often on pushbuttons. These pushbuttons are then displayed in the uppermost screen area andalways at your disposal.

If you want to do this, enter one or more of the following parameters: VELO_ACT1, VELO_ACT2, VELO_ACT3 and VELO_ACT4 and assign an action toeach parameter as value. You can find the keys for the actions (for example, CREA for Create vehicle ) in Customizing for VMS (transaction OVELO1).

Actions refer to all the vehicles in the left-hand screen area of the tab page Action .

All actions are performed for all vehicles at the same time. You therefore only choose once. For some actions, however, you may need to assignspecific data to each vehicle, for example Assign end customer or Create inbound invoice . You can recognize these vehicles by the fact that the internalvehicle number is displayed in the right-hand screen area. Make the required entries for the first vehicle, then select the next vehicle in the left-handscreen area, make the entries for this vehicle and so on. When you have completed all the vehicles, choose once.

You can see whether the action has been performed successfully or not by the success indicator in the left screen area next to each vehicle and theappropriate message in the status line. You can find further information on any errors that may have occurred in the log . Choose Log.

Only the current VMS run is logged. As soon as you exit the transaction VELO, the log can no be displayed. You can use user parameter

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 21

VELO_ACTPROTOCOL = X to make settings to define that the log is written to the database. You can then call it with transaction VELOP03 or delete itwith transaction SLG2 (object VMS_ACTION). Saving the log is particularly useful for the test phase.

If you perform an action after you have called the log, the log is not updated automatically. Close the log and call it again.

The default setting dictates that all the actions (that create documents) create exactly one document with one item per vehicle. The quantity per item isalways 1. If, for example, you order 10 vehicles, one purchase order with 10 items is created.

Depending on certain settings in SD, you can create more than one document at the same time, but only for the action DELI Create delivery .

1.2 Performing Actions in a Batch

UseAs a system administrator for VMS, you can perform any actions you like in batch mode (in other words in a collective run) and schedule these runs for any timeyou like. You define with which parameters you want to perform the actions in parameter variants. You can define the number of vehicles for which you wish toperform the actions by using selection criteria.

The name of the batch program is RVLCSACREG.

Creating Parameter VariantsChoose the transaction VELOV ( Maintain Variants ).

The selection screen for choosing parameter variants appears (table VLCBATCHACT).

Choose directly if you want to display all existing parameter variants.

Limit your selection and then choose if you only want to display specific parameter variants, for example all parameter variants for a specific action.

A list appears that displays all the parameter variants that correspond to your selection criteria.

Choose to create a new parameter variant.A screen appears with the fields of all the existing action interfaces.

Choose an action. Enter a name for the parameter variant and define the further parameters with which you want to perform the action. These are then theparameters that you have to enter on the appropriate action interface when you start the actions from the Vehicle Manager.

Save your entries.

Performing Actions with Parameter Variants in Batch ModeChoose transaction VELOB ( Perform Actions in Batch ).

The Triggering of Action Supported by Report screen appears.Choose the desired action and a parameter variant for this action. The parameter variant is a required field.Limit the number of vehicles in the Vehicle Selection area of the screen to those for which you want to perform the action /exception: all actions that create

vehicles). Enter at least the plant.Select the field Trigger Action Directly if you want the action to be performed for all the vehicles that the system finds.

Deselect the field if you do not want the action to be performed for all the vehicles but rather only for some of the vehicles, which you want to define more precisely.Choose the status the vehicles for which the action is performed should have in the screen areas entitled Primary Sts and Secondary Sts .Start the batch job or schedule it.

Choose if you want to start the batch job immediately.

If you have selected the Trigger Action Directly field, a list containing error messages and success messages appears. These are either generalmessages or messages with reference to a vehicle and they give you a hint on how to continue processing.

If you have not selected the Trigger Action Directly field, a list appears with all the vehicles that the system has found. You can select your desiredvehicles in this list and start the action for these vehicles with Action . After this intermediary step, you then also receive a list with error andsuccess messages.

Choose Program ® Execute in background if you want to schedule the batch job.

The screen for entering print parameters appears. Enter the required data and choose . The screen for scheduling jobs appears. Enter when youwant the job to be executed and save your entries.

1.3 Make-to-Stock Scenario:

PurposeYou use this procedure if your dealers work with make-to-stock production or when you order vehicles for stock yourself.

Process FlowAs importer, you sit down with your manufacturer, analyze the sales figures for the last business period and decide on quotas for the individual vehicle models forthe new business period. This decision made, you create the number of vehicles agreed on as planned vehicles (no value assignment possible) in your system.You do not allow values to be assigned until you actually order the vehicles from the manufacturer. As soon as you receive a purchase order confirmation from themanufacturer via IDoc, you make the vehicles visible, in other words, offer them for sale to your dealers. Your dealers can now make reservations and requests forreservations or also create a sales order directly. As soon as a dealer has created a sales order, he/she hides the vehicle from display so that it can no longer be

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 21

seen by other dealers.

Goods movements and invoices complete the process. The process is complete when your dealer delivers the vehicle to the end customer and the salesregistration note with the license number has been returned to you.

Here is an example of this procedure. (V) signifies anInterlinking Action.

Sequence Action Description Who does this?

1 CRE1 Create planned vehicle (withoutvalues)

Importer

2 CMOD Change configuration of plannedvehicles

Importer

3 REAL + ORD1 Allow value assignment for vehicle andcreate purchase order (alternative tosteps 1-3 alsoORD2)

Importer

4 MORD Change purchase order Importer

5 CONF Confirm purchase order (action notcontained in the Customizing settingsdelivered)

OEM via EDI

6 SHOW Allow vehicle for search Importer

7 SHMT Confirm transit OEM via EDI

8 GORE Create goods receipt (also possiblelater in process)

Importer

9 INIV Create inbound invoice (also possiblelater in process)

Importer

10 RSVN Create reservation Dealer

11 CUOR + HIDE Create sales order and exclude vehiclefrom search

Dealer

12 CHCO Change sales order Dealer

13 BUPA Assign end customer Dealer

14 DELI Create delivery Importer

15 GOIS Create goods issue Importer

16 OUIV Create outbound invoice Importer

1.4 Make-to-Order Scenario:

PurposeYou use this procedure if your dealers work with make-to-order production and do not produce for stock.

Process FlowIn contrast to the make-to-stock scenario, you do not create the vehicle as importer. Your dealer does this with respect to a sales order. The vehicle createdtherefore has the configuration desired by the dealer or the end customer. As importer, you order the desired vehicle from the manufacturer. Larger dealers can, ifrequired, create the vehicle, purchase order and sales order at the same time in an inter-linking action. The manufacturer confirms the purchase order andproduces the desired vehicle. He/she updates the vehicle status using IDocs and informs you of the progress being made in production/delivery.

Goods movements and invoices complete the process. The process is complete when your dealer delivers the vehicle to the end customer and the salesregistration note with the license number has been returned to you.

Here is an example of this procedure. (V) signifies anInterlinking Action.

Sequence Action Description Who does this?

1 CRCO (V) or Create vehicle and sales order Dealer

1+4 O2CO (V) Create vehicle, purchase order andsales order

Dealer

2 CHCO Change sales order Dealer

3 BUPA Assign end customer Dealer

4 ORD1 Create purchase order Importer

5 MORD Change purchase order Importer

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 21

2+5 CCPO (V) Change sales order and purchaseorder

Dealer

6 CONF Confirm purchase order (action notcontained in the Customizing settingsdelivered)

OEM via EDI

7 SHMT Confirm transit OEM via EDI

8 GORE Create goods receipt (also possiblelater in process)

Importer

9 INIV Create inbound invoice (also possiblelater in process)

Importer

10 UORD Start rework (purchase order andtransfer posting)

Importer

11 UGRE Finish rework (goods receipt) Importer

12 DELI Create delivery Importer

13 GOIS Create goods issue Importer

14 OUIV Create outbound invoice Importer

1.5 Configurations

FeaturesThere are the following configurations in VMS:

Vehicle Configuration

The vehicle configuration is part of the vehicle data and is stored in the vehicle table. It is the only configuration that is relevant in the vehicle search. Thevehicle configuration is displayed with the vehicle details in transaction VELO .

You can save a customer configuration using actionSOCD. This is the configuration that contains the original configuration desired by the customer. When, in a make-to-stock scenario, a customer buys a vehicle forwhich the configuration does not completely fulfill his/her requirements, the configuration originally desired can be saved. Evaluations at a later date can thendetermine in how far the actual and target configurations differ.

Sales Order, Offer, Inquiry Configuration

You can display the sales order configuration with the standard transaction VA03, the offer configuration with VA23 and the inquiry configuration with VA13.

Purchase Order Configuration

You can display the purchase order configuration using transaction ME23.

Subcontracting Purchase Order Configuration

You can display the subcontracting purchase order configuration using the standard transaction ME23.

You can use the icon in the vehicle history to branch to the transactions named above.

1.5.1 Handling Configurations

FunctionalityThe sales order, purchase order and subcontracting purchase order configuration influence the vehicle configuration in such a way that the vehicle configuration inthe vehicle data mirrors the current physical configuration as far as possible.

There is the following priority:

1. Subcontracting Purchase Order Configuration2. Purchase Order Configuration3. Sales Order Configuration4. Planned Configuration (vehicle configuration before the documents are created)

A new or changes configuration only influences the configuration if there is no configuration that has a higher priority (further up in the above list). If, for example, apurchase order exists, a sales order configuration does not influence the vehicle configuration, but it does if there is no purchase order.

The inquiry configuration and the offer configuration are of no importance in the respect. The inquiry configuration is stored in an inquiry document butdoes not have any further control function. The offer configuration is stored in the offer document and serves as a template for the sales orderconfiguration.

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 21

Process FlowMake-to-Stock Scenario:

The vehicle configuration is at the beginning of the MTS scenario. As soon as the purchase order is created at the manufacturer, the configuration for thepurchase order becomes the vehicle configuration. As soon as a subcontracting purchase order is created for rework, the additional rework characteristicsare copied to the vehicle configuration. If no rework is required, the purchase order configuration and the sales order configuration are the same. At the end,the vehicle configuration shows what the vehicle really looks like.

Make-to-Order Scenario:

The vehicle configuration is at the beginning of the MTO scenario. As soon as the dealer creates the sales order, the configuration for the sales orderbecomes the vehicle configuration. As soon as the purchase order is created, its configuration is copied to the vehicle configuration. As soon as asubcontracting purchase order is created for rework, the additional rework characteristics are copied to the vehicle configuration. After rework, the vehicleconfiguration and the sales order configuration are the same. At the end, the vehicle configuration shows what the vehicle really looks like.

Notes

All actions for which configuring a vehicle and/or deleting configurations is possible have a setTemplate Configuration. You can change this template configuration using the BAdI VLC_PREPARE_ACTION (method PREPARE_FURTHER_ACTIONS).

The first elementary action always sets the template configuration for inter-linking actions.

You can split the configuration using the BAdI VLC_CONFIG_SPLITTER. Splitting is useful if you want to distinguish between global and localcharacteristics. The global characteristics (OEM-relevant characteristics) are the written to the purchase order and the local characteristics to thesubcontracting purchase order for rework.

1.5.2 Actions and Configurations Below you can find a list of all the actions which allow you a configuration to take place or which allow a configuration to be deleted. The template configurationis the configuration with which the action is called.

Action Description Template Configuration Vehicle Configuration Further Configurations

CREA/CRE1 Create vehicle (valuespossible)/create plannedvehicle (no values possible)

None A new vehicle configuration iscreated If you have notconfigured when you create thevehicle, the vehicleconfiguration is created butremains empty

CMOD Change configuration ofplanned vehicles

Vehicle Configuration Vehicle configuration ischanged

VDEL Delete vehicles withoutdocuments

Not necessary Vehicle configuration is deleted

ORD1 Create purchase order Vehicle Configuration Vehicle configuration ischanged

Purchase order configuration iscreated and copied to thevehicle configuration

MORD Change purchase order Purchase Order Configuration Vehicle configuration ischanged

Purchase order configuration ischanged If none exists yet, oneis created

DORD Delete order item Not necessary If a sales order exists, thesales order configuration iscopied to the vehicleconfiguration If not, the plannedconfiguration is reused

Purchase order configuration isdeleted

IQRY Create inquiry Vehicle Configuration Vehicle configuration is notchanged

Inquiry configuration is created

DEIQ Delete inquiry Not necessary Vehicle configuration is notchanged

Inquiry configuration is deleted

OFFE Create offer Vehicle Configuration Vehicle configuration is notchanged

Offer configuration is created

DEOF Delete offer Not necessary Vehicle configuration is notchanged

Offer configuration is deleted

CUOR Create sales order If exists, then offerconfiguration, otherwise vehicleconfiguration

The vehicle configuration isonly changed if no purchaseorder exists

The sales order configuration iscreated and copied to thevehicle configuration is nopurchase order exists

CHCO Change sales order Sales Order Configuration The vehicle configuration isonly changed if no purchaseorder exists

The existing sales orderconfiguration is changed

DECO Delete sales order Not necessary If purchase order exists, thevehicle configuration is notchanged If no purchase orderexists, the planned vehicleconfiguration is reused

Sales order configuration isdeleted

UORD Start rework (purchase orderand transfer posting)

If exists, then sales orderconfiguration, otherwise vehicle

Vehicle configuration ischanged

Subcontracting purchase orderconfiguration is created and

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 7 of 21

configuration copied to the vehicleconfiguration

UDOR Delete rework purchase orderand transfer posting

Not necessary Vehicle configuration isreverted to what it was beforerework If several rework step,the correct configuration canonly be reused for the correctrework step

Subcontracting purchase orderconfiguration is deleted

RETU Create return Sales Order Configuration Vehicle configuration is notchanged

Sales order configuration iscopied to the returns document

POEU Trade-in Vehicle Configuration Vehicle configuration ischanged

Purchase order configuration iscreated and copied to thevehicle configuration

SOEU Used vehicle sales: createorder

Vehicle Configuration Vehicle configuration is notchanged

A new sales order configurationis created

SOCD Save customer’s desiredconfiguration

Not necessary Vehicle configuration is notchanged

The configuration desired bycustomer is created, if onealready exists, it is changed

1.6 Creating Vehicles

Process

You can find further information in the Standard documentation under

Batch Management (LO-BM), especially Valuation for a Single Batch.

Actions

Action Description Prerequisites What does the action do? Notes

CRE1 Create planned vehicle(without values)

Configurable material,configuration profile, class

Creates vehicle without batchand valuation type The internalvehicle number is assigned

Vehicles must belong to thesame vehicle model and havethe same configuration

REAL Allow values for vehicle Planned vehicle Creates batch and valuationtype for vehicles that havealready been created withCRE1

CREA Create vehicle (with values) Configurable material,configuration profile, class

Creates vehicle with batch andvaluation type The internalvehicle number is assignedThe number of the batch andthe valuation type are identicalto the internal vehicle number

Vehicles must belong to thesame vehicle model and havethe same configurationOnly advisable if the vehicleis really to exist in this formsince the valuation type cannotbe deleted later

CMOD Change configuration ofplanned vehicles

Planned vehicle Changes configuration ofplanned vehicles

Only for planned vehiclessince the configurations cannotbe changed in purchase orderdocuments and sales orderdocuments

VDEL Delete vehicles withoutdocuments

There must be no equipmentand no document (purchaseorder, sales order etc.) for thevehicle

Deletes vehicle withoutdocuments If configurationsand batches exist for thevehicle, these are also deleted

Valuation types are not deletedwith this action.You can delete valuation typesindividually and manuallyusing transaction MM06.

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 8 of 21

RVAL Revaluate vehicle Vehicle that has already beenposted in goods receipt and ismanaged in stock with aquantity of 1

Changes the vehicle value inthe valuation segment of thematerial masterA price change document (LO)and an accounting document(FI) are created

This action is useful if costshave been incurred in theVMS process that have to beactivated (example: paymentof duty)

1.7 Procurement: Purchase Order

Process

You can find further information in the Standard documentation under

Purchase Orders (MM-PUR-PO).

Actions(V) signifies anInterlinking Action.

Action Description Prerequisites What does the action do? Notes

ORD1 Create purchase order Vehicle can be assignedvaluesCreditorPurchasing info. record

Creates a purchase order atmanufacturer for existingvehicles.

The complete configuration iswritten to the purchase order(by default).

ORD2(V)

Create vehicle and purchaseorder

CREA + ORD1

MORD Change purchase order Purchase orderGoods issue should not havebeen posted

Changes the configuration andthe delivery date of order itemsand performs pricing again.

The selected vehicles must bein the same purchase order;but not all vehicles in thepurchase order have to beselectedYou can only change theconfiguration and delivery dateparameters

DORD Delete order item Purchase orderGoods issue should not havebeen posted

Deletes purchase order items.

1.8 Procurement: Incoming Invoice

Process

Actions

Action Description Prerequisites What does the action do? Notes

INIV Create incoming invoice Purchase orderThe goods receipt must havebeen posted for goods-receipt-

Enters incoming invoiceCurrency and paymentconditions are taken from the

The action is used for incominginvoices for actions ORD1(create purchase order) and

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 9 of 21

related invoice verification purchase order or thepurchasing info. record

POEU (trade-in). and not forincoming invoices after rework.There can only be onepurchase order without anincoming invoice for a vehicleIf there is more than one, theincoming invoice for the newestpurchase order isautomatically postedIncoming invoices for one-timevendors are not possible withthis action.

IIVR Cancel incoming invoice Incoming invoice Creates cancellation documentfor incoming invoice

The incoming invoice can onlybe cancelled completely Allthe vehicles in the incominginvoice have to be selected

1.9 Sales: Reservation, Quotation, Reservation Request,Inquiry

Process

The reservation request can be used by yourself, as importer, and by your dealers. With this process, your dealers begin the sale of vehicles, which ends in asales order. As importer, you can use the process for assigning a set amount of vehicles to your individual dealers. At the start of the business period youagree with each of your dealers on how many vehicles of each model he/she wants to take. Then you create the vehicles and reserve them for each of yourdealers. By doing this, this dealer is entered in the vehicle data. Only this dealer may then create a sales order for such a vehicle.

Creating quotations and inquiries is optional in this process. It makes sense to work with quotations and inquiries if you:

want to use objects and documents from the standard SAP system (quotation and inquiry are standard objects, reservations and reservation requests areVMS objects)want to print documentswant to configure vehicles

The report REP_MAIN_QUEUE (transaction VELOR Update reservation queue ) deletes all expired reservations, reservation requests, quotations and inquiries.If a reservation is deleted (from the report or manually), it results in the next reservation request becoming a reservation. If the current date does not coincide withthe validity period of this reservation, the validity date is changed to include the current date and all the following reservations move accordingly in time too.

You can display the logs for this report with transaction VELOP02 and, for example, determine for which dealer a valid reservation exists. You canthen inform this dealer per e-mail, if necessary. You can delete the logs with transaction SLG2 (object VMS_RESV).

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 10 of 21

PrerequisitesYou have created vehicles but not yet entered any sales orders for these vehicles.

As soon as you create a sales order, reservations and reservation requests including the appropriate quotations and inquiries are deleted.

You have created master records in the customer master record for dealers to whom you want to sell vehicles (see also:Creating Vendors and Customers).

Actions(I) signifies anInterlinking Action.

Action Description Prerequisites What does the action do? Notes

RSVN Create reservation No sales order, no quotationand no reservation can exist forthe vehiclesPlant calendar (if you requireone when calculating thevalidity periods)

Reserves the vehicles for aspecific dealer and writes thedealer as customer in thevehicle data

The standard validity amountsto 3 working days from thecreation date You canimplement your own logicusing the BAdIVLC_RESERVATIONYou can display thereservation and the reservationrequests in transaction VELO(tab page Details , screenVehicle Data . PushbuttonReservations )

OFFE Create quotation Reservation for the samedealer

Creates a quotation for thedealer for which the reservationis also valid

RSOF

(I)

Create reservation andquotation

RSVN + OFFE

DERS Delete reservation ReservationsThe selected vehicles must bereserved for the same dealer

Deletes the reservation for thevehiclesIf no sales order exists, thedealer is deleted as customerform the vehicle data

DEOF Delete quotation Quotation Deletes the quotation Deletescustomer, end customer andconfirmed delivery date formthe vehicle master record

You can only delete an entiredocument and not onlyindividual items

DERO

(I)

Delete reservation andquotation

DERS + DEOF

RSVM Create request for reservation Creates a reservation requestfor the vehicle

You can display thereservation and the reservationrequests in transaction VELO(tab page Details , screenVehicle Data . PushbuttonReservations )

The validity period follows upthe last reservation orreservation requestThe standard validity amountsto 3 working days from thecreation date You canimplement your own logicusing the BAdIVLC_RESERVATION

IQRY Create inquiry Reservation request for thesame dealer

Creates an inquiry for thedealer for which the reservationrequest is also valid

RSIQ

(I)

Create reservation request andinquiry

RSVM + IQRY

DERQ Delete reservation request Reservation request Deletes the reservationrequests for the vehicles

DEIQ Delete inquiry Inquiry You can only delete an entiredocument and not onlyindividual items

DERI Delete reservation request and DERQ + DEIQ

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 11 of 21

(I)inquiry

1.10 Sales: Sales Order

Process

For more information, see the standard documentation

Sales Order.

Actions(I) signifies anInterlinking Action.

Action Description Prerequisites What does the action do? Notes

BUPA Assign end customer Assigns an end customer tothe vehicles You can alsocreate an end customer

An importer can display allend customers, a dealer canonly display his/her own , i.e.the ones he/she created Thisis controlled by entering thedealer as a customer in theOrganizational Role

CUOR Create sales order Customer master record fordealer

Creates sales order forvehicles and enters dealer towhich the vehicles are to besold and the vehicle usage inthe vehicle dataYou can also create andassign an end customerDeletes thereservation queue

This action cannot be used forreselling used vehicles withtheTrade-In process.

CHCO Change sales order Sales order Changes sales order If theconfiguration is changed,pricing is performed againYou can also create andassign an end customer

The selected vehicles must bein the same sales order; butnot all vehicles in the salesorder have to be selectedThe dealer as sold-to partycannot be changedThis action cannot be used forreselling used vehicles withtheTrade-In process.

DECO Delete sales order Sales order Deletes sales order with themost recent dateDeletes end customer anddealer (customer) from thevehicle data

You can only delete acomplete sales order, notindividual items

CRCO(I)

Create vehicle and sales order CREA + CUOR Only advisable in theMTO Scenario

O2CO(I)

Create vehicle, purchase orderand sales order

CREA + ORD1 + CUOR Only advisable in theMTO Scenario

CCPO(I)

Change sales order andpurchase order

CHCO + MORDFirst changes the sales order

Only advisable in theMTO Scenario

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 12 of 21

and then the purchase order

1.11 Sales: Delivery

Process

For more information, see the standard documentation

Delivery Processing.

Actions

Action Description Prerequisites What does the action do? Notes

DELI Create delivery Sales orderVehicle must be in importerstock

Creates delivery for sales orderwith the most recent date

You can split a sales order intodifferent deliveriesMore than one order can begrouped into a delivery ifspecific criteria have beenfulfilled For this to be the case,the appropriate field in thesales area data of thecustomer master record (tabpage for shipping) must havebeen selectedYou do not have to select allthe vehicles in a sales order

DEDE Delete delivery Delivery Deletes delivery for sales orderwith the most recent date

You can only delete acomplete delivery, notindividual items

1.12 Sales: Outgoing Invoice

Process

For more information, see the standard documentation

Billing.

Actions

Action Description Prerequisites What does the action do? Notes

OUIV Create outgoing invoice Sales order Bills the sales order with themost recent date

Outgoing invoices are onlypossible if related to salesorder, not related to deliveryMore than one order can begrouped into an outgoinginvoice if specific criteria havebeen fulfilled

OIVR Cancel outgoing invoice Outgoing invoice Cancels existing outgoinginvoice

You can only cancel an entiredocument and not onlyindividual items

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 13 of 21

1.13 Goods Movements: Goods Issue, Goods Receipt

Process

You can find further information in the standard documentation under

Goods Issue and Goods Receipt.

Actions

Action Description Prerequisites What does the action do? Notes

GORE Create goods receipt Purchase order Creates material document forthe goods receipt withreference to a purchase order

The action is used for goodsreceipts for actions ORD1(create purchase order) andPOEU (trade-in) and not forgoods receipts after rework.There can only be onepurchase order without goodsreceipt for a vehicle If there ismore than one, the goodsreceipt for the newestpurchase order isautomatically postedIt cannot be posted to the salesorder stock

GRER Cancel goods receipt Goods receipt Creates cancellation documentfor goods receipt

This action can cancel acomplete goods receipt orindividual document items

STOL Storage location posting Goods receiptVehicle cannot be inrepair/rework

Creates a material documentfor the transfer posting from onestorage location to another

This action can still beperformed after a delivery hasbeen created as long as nogoods issue has been postedfor this deliveryPosting across different plantsis not possible

GOIS Create goods issue Delivery Creates a material documentfor a goods issue

The storage location from whichthe goods issue can be postedcannot be changed after thedelivery has been createdGoods issue documents musthave a 1:1 relationship to thedelivery

GISR Cancel goods issue Goods issue Creates a cancellationdocument for the goods issue

This action only cancels acomplete documentIt can only be used for goodsissues that have been createdwith the action GOIS.

1.14 Rework (Including Goods Movements)

Process

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 14 of 21

The reworker is represented in the SAP system as a vendor in the role of a subcontractor. For more information, see the standard documentation

Subcontracting.Vehicles can be reworked more than once.

Processing rework is only possible using an external service provider.

The actions DORD, MORD, GORE, GRER, INIV and IIVR cannot be used in the rework process. You can only use four actions (listed below) inthe rework process.

PrerequisitesYou have defined which characteristics are to be reworked by which vendor.If only part of the configuration is to be assigned to a subcontractor order, you have implemented BAdI VLC_CONFIG_SPLITTER, which compares thepurchase order configuration with the sales order configuration. The differences between these two define the scope of the work to be done.

Actions

Action Description Prerequisites What does the action do? Notes

UORD Start rework (purchase orderand transfer posting)

Procurement processcompleted up to and includinggoods receiptReworker created as creditor inthe systemSubcontractor info. recordBill of material (if componentsto be provided are beingworked on) as super BOM withobject dependencies for theBOM explosion: the vehiclemust be a component in theBOM

Creates subcontractorpurchase order and transferposting for the vehicle in thesubcontractor stockThe BOM is exploded

The components to beprovided for the subcontractorpurchase order can only bedetermined by the BOMexplosionThe transfer posting of thesecomponents to thesubcontractor stock takesplace outside VMS (in thestandard transaction MB1B)There is only one entry in thehistory so you can only displaythe purchase order and not thetransfer postingYou can enter a default valuein the field Reworker with theuser parameterVELO_REWORKER

UDOR Delete rework purchase orderand transfer posting

The vehicle must be insubcontracting stock

Deletes the subcontractingpurchase order and creates acancellation document for thetransfer posting

UGRE Finish rework (goods receipt) The vehicle must be insubcontracting stock

Creates a goods receiptdocument with reference to thesubcontracting purchase order

The goods receipt is posted forall the components to beprovided in subcontractingpurchase order

UGRR Rework: cancel goods receipt Creates a cancellationdocument for the goods receiptfor the subcontractingpurchase order

1.15 Processing Returns

Process

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 15 of 21

A vehicle that is sold and then returned to stock is usually resold using the normal sales process for new vehicles (see also:Sales: Reservation, Quotation, Reservation Request, Inquiry and Sales: Sales Order). However, if the vehicle is classified as being a used vehicle, actions SPEUand SOEU from the Trade-In process succeed the actions displayed above when the vehicle is resold.For more information, see the standard documentation

Returns.

Actions

Action Description Prerequisites What does the action do? Notes

RETU Create return Sales order Creates return for a vehicle thathas already been sold

A return can only be createdwith reference to a sales orderand not with reference to anoutgoing invoiceYou do not have to select allthe vehicles in the sales orderYou have to define itemcategory, copy control and itemcategory determination

RELI Create returns delivery Return Creates returns delivery for areturn to register the arrival ofthe vehicle and to post thevehicle to stock

REGI Goods receipt for returnsdelivery

Returns delivery Posts goods receipt to theblocked stock returns

RECM Create credit memo for returns Return Creates a credit memo for thereturn

REUS Transfer vehicle from blockedstock returns to unrestricted-use stock

Vehicle in blocked stockreturns

Posts vehicle from blockedstock returns to unrestricted-use stock so that it can beresold

1.16 Trade-In and Used Vehicle Sales

Process

The normal VMS sales process with delivery, goodsmovements and outgoing invoice follows action SOEU.

Vehicles can be taken in part exchange/as a trade-in more than once.

You can find further information in the Standard documentation under

Purchase Orders (MM-PUR-PO).

If you trade-in using a one-time vendor, the inbound invoice cannot be posted with transaction INIV but only with the SAP standard transaction.

Actions(I) signifies anInterlinking Action.

Action Description Prerequisites What does the action do? Notes

CREA Create vehicle (with values) See:

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 16 of 21

CREA Create vehicle (with values) See:Creating VehiclesWhen you trade-in vehiclesthat you have already sold asan importer, you do not have toperform this action.

POEU Trade-in Vehicle Creates a normal purchaseorder for the vehiclesIn contrast to action ORD1, theprice and the vendor (also one-time vendor) have to beentered manually in theinterface

A purchasing info. recordshould not exist for thevendor/vendors.If a record does exist, youmust ensure (in the pricingprocedure) that the priceentered manually has priorityover and above the price in thepurchasing info. record.

GORE Create goods receipt See:Goods Movements: GI, GR

CRPU

(I)

Create and trade-in vehicle CREA + POEU This action can only beperformed for exactly onevehicle.

SPEU Used vehicle sales: determineprice

The vehicle has been returnedto the importer’s stock due totrade-ins or returns processing.

Overwrites the gross list pricein the vehicle data with theresell priceThe resale price is a manuallyfixed price that is independentof the configuration of thevehicle

SOEU Used vehicle sales: createorder

The vehicle has already beensold once and has beenreturned to stock by a trade-inprocess or returns processingResale price (action SPEU)

Creates a sales order for theused vehicle and can overwritethe entries for customer, endcustomer and vehicle usage

This action is a very simplifiedversion of action CUOR andnumerous restrictions apply:you cannot carry outReturns Processing for salesorders that have been createdusing action SOEU. Youcannot make reservations ifyou are using action SOEU.Sales orders that have beencreated with action SOEUcannot be changed with actionCHCO but they can be deletedwith action DECO.You should use a differentpricing procedure for pricingthan you use for action CUOR.Background: condition typeVA00 (variant price) iscontained in the pricingprocedure fin the case ofCUOR, in other words, theprices depend on theconfiguration during pricing(see also:Create Variant Conditions forPricing). You should not,however, use condition typeVA00 for action SOEU sincethe price is independent of theconfiguration here anddetermined manually usingaction SPEU. This resale priceis transferred as condition typePR00 by default. You candefine a different condition typefor the resale price in BAdIVLC_EXECUTE_ACTION,methodDATA_CHANGES_BEFORE_ACTION. You must then writethis condition type inVLCACTDATA_CS-KSCHA.If you want to be able to usedifferent pricing procedures forCUOR and SOEU, you shoulduse different document types.Both actions work withdocument type TA (standardorder) by default. You canchange the document type inBAdI

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 17 of 21

VLC_EXECUTE_ACTION,methodDATA_CHANGES_BEFORE_ACTION. You can enter thedocument type inVLCACTDATA_CS-AUART.

1.17 Service Processing

Process

There are two options for service processing:

Processing only with a service notification, in other words, without a service order. This is the quickest type of service processing if no costs that have to besettled are incurred.Processing with a service notification and a service order. This is sensible if you have to plan and calculate materials, resources and work forces. If nodetails are required for actions, measures, persons responsible etc., you can ignore the service notification and create a service order directly.

You can find further information in the standard documentation under

Service Object as Equipment, Service Notification, Service Order and Processing Services .

Actions(I) signifies anInterlinking Action.

Action Description Prerequisites What does the action do? Notes

CREQ Create equipment Vehicle Creates an equipment for avehicle and writes theequipment number in thevehicle data.

SMNO Process service notification Optional: equipment Creates a CS servicenotification with claim itemsand organizational data andallows you to change orcomplete existing servicenotifications. You can enter aseparate item with problem,affected object part, reason forclaim, actions and measuresfor rectifying the damage foreach claim.

If you enter the value X for userparameterVELO_SMNO_POPUP_MODE, you always branchdirectly to the screen forcreating a new servicenotification or, if a notificationalready exists, to the screenfor changing this notification.This is useful if youfundamentally do not want toallow more than one servicenotification.

SMOR Create service order Optional: service notification Creates a CS service orderwith operations. Items in theservice notification becomeoperations in the service order.You can propose plannedworking times for theoperations.The order can be releasedautomatically depending onwhich settings have beenmade in Customizing for CS.

If you enter the value X for userparameterVELO_SMOR_OPR_MODE,exactly one operation will becreated in the service order.The service notification itemsare not copied.

SMCO Confirm service order Service order Confirms actual working timeand used components to theservice order. Any number ofpartial confirmations possible.

External services cannot beconfirmed.

SMIO Create billing request forservice order

Service order Creates a billing request for aservice order. The billingrequest covers all confirmedcomponents and working times

The billing document has to becreated outside VMS (forexample, in collectiveprocessing).

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 18 of 21

for this service order for whichno billing request yet exists.

SMOC(I)

Create and confirm serviceorder

Optional: service notification SMOR + SMCO

1.18 Special VMS Actions

Process

Actions

Action Description Prerequisites What does the action do? Notes

SOCD Save customer’s desiredconfiguration

Saves additional configurationfor vehicle

This action serves above all tostore a desired configuration forthe vehicle which you can thenlater compare with the actualconfiguration

SMOD Change vehicle Defined values in VMSCustomizing for vehicle usage,vehicle search area andsharing levelDefined qualifiers inCustomizing and assignment toaction SMOD

Allows changes to vehicleattributes and qualifiers (seealso in VMS Customizingunder Enhancements ®Program Actions andEnhancements ® Define

Additional Data for Vehicles

Example for an action thatworks with additional data(filled by additional fields onthe initial screen) and withqualifiers (ALV list on entryscreen)You can program any numberof such actions that work withdifferent fields

CORR Correct status (without check) Internal action that, in contrastto the other actions, is notactually an action since it doesnot link to a primary orsecondary matrixIf you execute transactionVELOE ( EmergencyMonitoring ), which you canuse to change the vehiclestatus in case of an error, anentry is written to the vehiclehistory so that the statusconversion is logged Theaction CORR is written to thehistory

This action cannot be startedmanually using transactionVELO

HIDE Exclude vehicle from search Sets the vehicle attribute fromdisplayed to not displayedThe dealer usually performsthis action in theMTS Scenario as soon as hehas bought a vehicle so thatother dealers do not haveaccess to the vehicleDefault setting = vehicles notdisplayed

The actions HIDE and SHOWhave no effect in themselves –only in combination with one ofthe following twoimplementations:1. You can use the visibilitydependently of the VMS role(dealer, importer) as parameterwhen selecting vehicles fromthe database (BAdIVLC_SEARCH_ADAPTION)

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 19 of 21

SHOW Include vehicle in search Sets the vehicle tovisible/displayed in thevehicle attributes

VLC_SEARCH_ADAPTION)2. You can use the visibilityaccording to the selection inCategory Management (vehiclefilter) as parameter The secondoption has the disadvantagethat the performance is not asgood, since many vehicles areselected that are not neededlater

CAMP Assign sales campaign Values for sales campaign(transaction VELOC )

Sets the vehicle attributeSales campaign to a new

value

The point of this action is totrigger pricing again in thesales order (due to assignedsales campaign) There are twooptions:1. You can add the field as anobject characteristic to thevehicle configuration (see:Adding Object Characteristicsto the Configuration)2. You can use the options forflexible enhancements to SDpricing

LCTN Set vehicle location Values for vehicle location inCustomizing for VMS(transaction OVELO)

Sets the vehicle attributeVehicle location to a new

value and assigns the addressof the vehicle location to thevehicle

SHMT Confirm transit Example for an action that onlychanges the status and doesnot create any documents

Actions such as these, forexample Confirm purchaseorder can be defined inCustomizing

STWO Trigger Workflow event Organizational structureTasks

Only useful as part of an inter-linking actionTriggers the sending of e-mailswith Workflow items, theserefer to the actions with whichthe action STWO has beenlinked

MSSO Output messages VMS Customizing forMessages Determination

Outputs messages (possiblyas part of an inter-linkingaction)

You can display the sentmessages in transactionVELO (tab page Details ,screen Vehicle Data .Pushbutton )You can find further informationunder

Message/Output Control(CA-GTF-BS) and in thedocumentation for theappropriate VMS Customizingactivities.

ADDO Assign business documents Assigns documents to avehicle

You can display the storeddocuments in transactionVELO (tab page Details ,screen Vehicle Data .Pushbutton )You can find further informationunder

Business DocumentNavigator

1.19 Warranty Processing

Process

These three actions link the applications

Vehicle Management System (IS-A-VMS) and Warranty Processing (IS-A-WTY). They serve to create the master data ( Equipment, Master Warranty,

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 20 of 21

Measuring Points) that is necessary to carry out the Warranty Check in Warranty Processing, in other words, to check automatically whether a warranty stillexists for a specific vehicle or not.

Actions

Action Description Prerequisites What does the action do? Notes

CREQ Creates equipment for thevehicle

Vehicle Creates an equipment for avehicle and writes theequipment number in thevehicle data.

WRTY Assign master warranty Equipment for vehicle, masterwarranty, BAdI

Assigns a master warranty toequipment that has beencreated using action CREQ

MEAS Assign measuring points Equipment for vehicle,reference equipment, BAdI

Assigns measuring points tothe measurement positionsand warranty counters of thereference equipment forequipment that has beencreated using action CREQ

PUBLIC© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 21 of 21