Vehicle Status???

Hi.
What kind of Vehicle Statuses can be define???
Does that mean statuses like In Warehouse, To Customer, or Shipped but not invoiced,to Shipyard?
or anything else? As per Action will the status get changed???
Can anybody tell me Basic cycle in VMS with T codes? (Like in SD OR-DEL-INV)
am i suppose to use T codes VA01,VL01N& VF01 OR everything is done in VELO???
Reg,
Amol

VELO uses actions to perform these things.
The actions is set up in config (SPRO) .
The SAP Standard actions is as follows;
OFFE (Create Qoutation)
CUOR (Create Sales Order)
DELI (Create Delivery)
GOIS (Create Goods Issue)
OUIV (Create Outgoing Invoice)
Hope this helps
Kind Regards

Similar Messages

Available vehicle status

Is there any standard setting of the shipment, where if I trigger shipment start button, system automatically trigger the vehicle status from available vehicle to vehicle movement is in progress.
Currently we have manually status of the vehicle, and want system automatically set the status plus if vehicle is in movement than the same vehicles sould not be assign to any other shipment, till it will be avaialable.
Regards,
Imran

ok. let's try:
the availability of a vehicle is changed by a VMS action that is executed.
This is caused by action matrix configuration in the VMS:
IMG -> logistics execution -> VMS -> control data -> define action controls ...
Here, select an action matrix (right side), and then click twice on the field "availability, locations and planned delivery" (left side).
or use transaction OVELO11
Screenshot of an example is attached to this post.
See also the online help:
http://help.sap.com/saphelp_dimp50/helpdata/EN/91/88c43ace7a3b46e10000000a114084/frameset.htm
Note: when definining the action matrices for the availability, make sure that the availability is not unforeseen overwritten by other actions. The best way is to define the availibility only by one matrix, as long as the actions of assigned matrices to the vehicle model don't interfere with each other in regards to the availability.
Hope this helps. Let me know if you need further help.
Best, Ute

Vehicle Status at Shipment

Dear Gurus,
In LE we are not utilzing trip planning, just assign vehicle and driver on the shipment, I just required is there any standard functionality
where I can set a status of the vehicle, like if i press shipment start button on shipment vehicle change its status, now if i again assign the same vehicle to another shipment it will give us the message that vehicle is not available or any related message.
I only see the automatically PGI and billing functionality, like if i press shipment start system in back groud will process PGI.
Also suggest where i can maintain vehicle related status if it is a part of sd, or integrated with PM module.
Looking for the gurus response.

VELO uses actions to perform these things.
The actions is set up in config (SPRO) .
The SAP Standard actions is as follows;
OFFE (Create Qoutation)
CUOR (Create Sales Order)
DELI (Create Delivery)
GOIS (Create Goods Issue)
OUIV (Create Outgoing Invoice)
Hope this helps
Kind Regards

Vehicle availability status doubts

Dear sir,
Here they are using customized tcode to see the vehicle status(i.e if it is green-vehicle available,if it red-vehicle is breakdown).we could not able to find that in which table they have status information.
Now customer required management level report to see month wise vehicle available status.
how to take each day wise vehicle status-please let me know how to process
I have tried in JCDS table its not showing exactly day wise staus
Regards
Rajasekaran

Rajasekaran,
This query is technical centered. As you told this is a Z report, the traffic light status field comes from the logic in the program. This might be coded in a way that the code finds the User status/Sy Status of the Equipment (tables JEST, TJ02T/TJ30T etc) the depending upon that it assigns the green, red traffic light signal to a Zfield of the internal table. If this is the logic, you need to develop a program for management level report using the above tables (also EQUI). So this is an ABAPer's job.
KJogeswaraRao

How to create a vehicle in VELO

Hi;
I am new to VMS and trying to figure it. In our SAP DEV system, I have done the following:
1. Created a configuration profile
2. Created a material master record for a model car in MM01.
3. Tried to build an action matrix.
4. Defined Vehicle Status
5. Defined Vehicle Usage
I think I have done everything that I need to do. In VELO, my model car shows up on the FIND tab. I am trying to create a car but since I have no cars in the system to choose from I can't get it work.
Which tab do I use to create a car? I would like to create a "USED Vehicle" - action CRUV but right now I would be happy to create any car.
When on the "ACTION" tab, there are no actions available.
It seems like VELO is used to work with cars returned from the search, but I need to create a car master record. Can anybody help?
Also, if anyone has a program that accepts a file as input to create a car that they would be willing to share that would be helpful as well.
Thanks
Stephen

Hi Ganesh;
Thank you for the response. I finally figured out that I needed to turn on the flag creaact in table cvlc03 to get the execute button to appear on the "ACTION" tab.
You turn on this flag in spro --> Logistics Execution --> Vehicle Management System --> Enhancements --> Define Technical Details for Actions
This was hard to find. I haven't found any documentation that has told me to do this.
Now I have error message XCM scenario VEHICLEMAN DEFAULT not found. I have to figure this out.
Another question. We are an auction site for the selling of used cars. We don't actually own the cars but facilitate the selling of them for the car dealer. I am trying to use SAP to manage the "inventory" of cars as we have to keep track of them in our SAP system. We receive cars into a security parking lots and release the cars from the lot once the buyer has paid for the car.
Do you think I should use VMS or DBM? We need to keep track of some of the details of the car (i.e year, make, model, engine size, mileage, color). We do not need any purchase orders or any manufacturing.
Thanks
Stephen

Shipment - Vehicle master record

Hello
i know that in order to mantain the material master record for a vehicle is necessary to use packging material belonging to the category of means of trasport.
We need to use the means of transport in shipment and we have to pack all the deliveries items into that packagin material representing the vehicle.
I have the following question about this process:
1) Is it possibile to define the license plate number in material master record so it's copied automatically in the handling unit that is generated in shipment when i do the packing in the vehicle? Where, according to SAP standard is supposed to enter the plate number of vehicle?
2) Is it possibile to define vehicle status in material master record (damaged, unavailable, etc...) in order to block that vehicle/material packaging in shipment?
I know that some of the features above are part of yard management, but do you think is possbile to do the same only with sd-transportation module?
Thank you very much for your attenetion.
Regards,
A.

Thank you for your answer.
For the question two i mean a block in material master for packaging material like the one used for blocking the insertion of a specific material in sales order, delivery, etc... This block for the vehicle should prevent me by using the vehicle for the shipment (because it's damaged etc...).
My packaging material is not managed on stock basis.
Thank you very much for your attention.
Regards,
A.

TD Shipment Status Could Not be Reversed

Hi,
I've completely confirmed the TD Shipment with status 6, whenI realized that there was a little wrong number in the outbound delivery (delivery order). So, to make correction in the delivery order, I reversed both the delivery confirmation (O4H1) and loading confirmation (O4G1). It should be status 2 now, but the TD shipment is still status 5.
Then I checked with t-code O4F3, I found the documents status is still 3 and the vehicles status is still 5. Is there any t-code to reverse the documents status and vehicles status? This case is rare, and I've never found such case before.
Thanks in advance.
Edited by: alharo on May 27, 2011 3:41 AM

Hi,
First of all, you may use the tcode S_SO6_65000796 to check the inconsistency in the bulk shipment.
If the above does not help to sort out your issue, then you could consider using the tcode S_SO6_65000798 to carry out the release of the shipment through an emergency report. Thereafter you would need to carry out the material document reversal manually.
Importantly, kindly read through and understand the program documentation before running the above mentioned report. You should also execute in TEST mode prior to actual execution. It is also better to simulate the above mentioned scenario in sandbox and carry out this release before executing in the Production system.
Please note this is only an emergency report.
Path you may find this additional tools are: Logistics --> Add-On: Administration and Tools --> Transportation & Distribution
Hope the above helps.
Thanks.

Automatic Delivery creation through VMS

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

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,

VMS functionalities

Hi,
I need VMS fuctionalities in following Business process
Q 1- How to track/see the stock of the dealer using SAP VMS?? Is it possible to do so??
Q 2- What are the Standard reports available in SAP VMS?
Q 3- Transfer of Vehicle from Dealer A to Dealer B without any cancellation of documents even if the whole SD process is complete between the NSC and The Dealer A?
Thanks
chidambaram

Hi Chidambaram,
for being able to solve Q1, in my opinion the dealers need to access the VMS system. I assume you use dealer portal (or maybe the dealers have access to VELO directly?).
As VMS is typically installed at the importer and only the importer is normally modelled with one or several plants, the vehicles are not in the MM stock any more as soon as to create the goods issue in order to ship the vehicle to a dealer.
Depending on your requirements, it might be sufficient that you assume that from this point on (action GOIS was executed) you consider the vehicle being in the dealers stock. If you require to know hen the vehicle physically arrives at the dealer's lot, you probably need to introduce an action which is executed by either the dealer or the transportation agent when the vehicle arrives at the dealer's.
Similarily, I think you would require the dealer to execute a status change action when the vehicle is removed from the dealer's stock.
I'm not sure what your requirements look like in detail but this might be sufficient to be able to derive which vehicles are in which dealers stock. You would be able to figure this out by combining the vehicle status with the customer number of the vehicle as selection criteria in e. g. a report or the vehicle search.
Maybe there're other solution approaches possible which might fit better to your particular requirements but what I described above is a relatively simple possibility which might be sufficient.
Kind regards,
Steffen

Check Entry in Action Matrix

Sap documentation about this field is very poor, does anybody know what it is for?
Definition
Controls whether the status of an entry in the Action Matrix is to be checked or not.
Use
If you select this field, the system checks whether a required status has already been achieved. The status value and status time remain unchanged.
If somebody has an example to share, it will be great

Hi Jose,
The significance of Check entry in Action Matrix is:
In Action control matrix we are defining Old Vehicle Status and New Vehicle Status for that action.
So after performing action if New Vehicle status is required then Check entry field should be blank else check entry field should be X.
For Example:
In Vehicle create action New Vehicle status is required in this case check entry field is required BLANK.
In Change Configuration of Planned Vehicles action new vehicle status not required hence check entry field is required X.
Regards,
Arpit

Using IDOC VEHCLE01

Hi all,
Does any one know how to use this idoc?
I am tryng to use message type VLCCPO.
Thanks,
Naama.

The vehicle IDoc VEHCLE01 is part of VMS. It serves to transfer
vehicle data between manufacturer and importer or between
different sales organizations. It can be an inbound or an
outbound IDoc
inbound vehicle IDoc has message type VLCCPO
outbound vehicle IDoc has message type VLCVDT
· The inbound IDoc (VLCCPO )serves mainly as a communication
means between the manufacturer and yourself as importer.
The manufacturer can confirm your vehicle order via the IDoc
and update the vehicle status (in production, in transit etc.)
regularly with current production data. To do this, VMS
evaluates the Customizing table for transaction OVELO5 under
Control Data ® Define External Status): it finds an action
and a plant for the organization channel and the external
status. As soon as the system performs this action, the
vehicle is set to the internal status stored in the
appropriate action matrix
The outbound IDoc is linked to VMS message control As importer, you can send faxes,
e-mails and IDocs containing the vehicle data to subordinate or superior sales organizations
using action MSSO
Please do the idoc processing a normal idocs using we02 , we19 and bd87
, we can see the status in VELOM
REWARD SOME POINTS IF IT HELPS

Vms - actions

hi,
In VELO, we have done the follwoing actions succesfully
1) CREA (vehile creation)
2) ORD1 (create PO)
However, while trying to perform GORE (Goods Receipt)sytem is giving error saying that action cannot be executed for these vehicles . And the log says Read Conguration.
Did I miss any settings. Pls help.
Regards,
Student
Edited by: STUDENT on Jul 31, 2009 3:06 AM

Hi Student,
it's a bit hard to say for sure what causes the problem without knowing more details but to me it seems quite likely that the vehicle's current status doesn't allow the execution of the action you selected. The fact that action GORE isn't offered when you're on the action tab indicates so.
What I write here is based on this assumption.
You need to check the primary and secondary status of your vehicle in the vehicle details. Then in customizing (transaction OVELO1), check if action GORE is relevant for the primary status, the secondary status or both. In standard, the action is only relevant for the primary status.
You then can check, again in customizing (transaction OVELO11), what are the possible actions for the vehicle and what status is required for action GORE.
In order to be able to execute an action, the action needs to be part of the matrix relevent for the vehicle (in this case, the matrix used as primary matrix, see transaction VELOS, needs to contain action GORE). The old status of in the matrix for action GORE needs to be the same as the current vehicle status.
I hope most of this isn't new to you as this is the "core" of the VMS concept. In order to work with VMS, you need to be familiar with this concept.
Here're links to the documentation, just in case: http://help.sap.com/saphelp_dimp50/helpdata/EN/95/47c83abc3c1a54e10000000a114084/frameset.htm
http://help.sap.com/saphelp_dimp50/helpdata/EN/a1/6dc33ac037b41de10000000a11402f/frameset.htm
As I said, I'm not sure if my interpretation of what causes your problem is correct but what I've described above seems likely to me.
Kind regards,
Steffen

What is velo transaction

hi
what is velo transaction. i am not getting this transaction in my system. what would be the reason

Hi .
U R VELO     Transaction Will Come Under Following Scenario.
Vehicle
Definition
A vehicle is a business object (BUS1200) in the SAP system.
A vehicle is the result of using a create action in VMS to create a vehicle for a vehicle model. It is therefore, an instance of a vehicle model, in other words, an individual object. A configuration is always created for a vehicle; the characteristics in the configuration may have not yet had any values assigned to them, partly have had values assigned or have had all values assigned. You can identify the vehicle by its vehicle number and define it further using a batch, valuation type and, where appropriate, an equipment number.
Use
The vehicle is a central object in the Vehicle Management System. Vehicle searches and actions for the business processes involved always relate to at least one vehicle. The only exception is the function Assignment of Vehicles to Sales Documents, which does not start from the vehicle but from the sales document.
Structure
Assigning Values
When you create a vehicle it receives an internal vehicle number. This number is the also the batch number and the valuation type number. Each vehicle, therefore, has its own batch and valuation type. You can display valuated stock using transaction MMBE Stock Overview.
You are recommended to use valuation for a single batch with VMS. The valuation of sales order stock is not supported by VMS.
Create a purchasing info. record manually for each vendor. Leave the field Valuation type under Purchasing organization 1 empty. Do not use the Customizing setting (Customizing for Materials Management) under Purchasing ® Environment Data ® Define Default Values for Buyers, indicator InfoUpdate Purchase order), which defines that a purchasing info. record is created automatically when a purchase order is created. The field Valuation Type is filled when this Customizing setting has been made. This leads to problems when you want to create vehicles.
You can find further information in the documentation for Logistics General under Batch Management (LO-BM), especially Valuation for a Single Batch.
Vehicle Data
A vehicle is characterized by its vehicle data (vehicle master, see table VLCVEHICLE). The following belong to the vehicle data:
GUID
Global Unique Identifier. A 22-character technical key assigned by the system when the importer creates the vehicle.
This key is unique and therefore also differentiates between vehicles that have been created in different systems. The GUID serves only internal technical control purposes and does not appear on the interface.
Internal vehicle number
An identification number from an internal number range. It is assigned by the system when the importer creates the vehicle.
The vehicle number is created independently of the vehicle identification number (VIN).
External vehicle number
Identification number assigned by the manufacturer (for example, production number, vehicle number)
Vehicle identification number (VIN)
17-character number that identifies a vehicle and is created when the vehicle is assembled, for example, during the assembly process in the manufacturers production system.
The VIN is an international standard.
Batch (only for vehicles that can be assigned values)
A vehicle represents exactly one batch. The batch number is the same as the internal vehicle number (see above).
Valuation type (only for vehicles that can be assigned values)
Each vehicle has a valuation type (Valuation for a Single Batch). The valuation type number is the same as the internal vehicle number (see above).
Plant
Location, organizational unit of importer
Storage location
Actual storage location of the finished vehicle in the importers plant
Vehicle Model
Basic type of a vehicle that can be varied.
Vehicle models are created as configurable materials in the SAP system.
A vehicle model can be a general vehicle type or a vehicle type for which specific characteristic values have been predefined using object dependencies.
Configuration
Characteristics and assigned characteristic values (for example: color: blue; special features: radio, air conditioning).
Primary Action Control, primary status + date + time, secondary action control, secondary status + date + time
The action control defines (in an action matrix) which actions can follow one another when dealing with vehicles and which vehicle status change is connected with this.
Example: a vehicle that the importer has ordered from the manufacturer receives the status Ordered. After the manufacturer has confirmed the purchase order, in other words has performed the action Confirm purchase order, the status changes automatically to Purchase order confirmed.
You can distinguish between primary and secondary action controls, depending on the process that is being represents by the action control. The primary action control usually represents the procurement process (ordering the vehicle from the manufacturer) and the secondary action control the sales process (sale of the vehicle to the dealer). However, a subdivision into a logistics and a financial process is also possible.
Availability status
Status that displays whether the vehicle is available for sale (for example: Not released, Available, Reserved, Sold).
The status changes automatically depending on the action you perform.
The availability status can remain the same for a series of different vehicle statuses. Example: a vehicle that receives the statuses Vehicle created, Vehicle ordered, Purchase order confirmed and Transit confirmed retains the availability status Not released.
The availability status is only for information purposes and has no controlling effect.
Address
Address (from central address management) where the vehicle is to be found.
This address can be the address of a vendor, customer, end customer or of any other location defined in Customizing for VMS.
Production date (time stamp)
Date on which the vehicle is produced.
The importer enters the planned production date that he has agreed on with the manufacturer in the appropriate field when the vehicle is created or the vehicle data is changed. The manufacturer updates this date regularly during the production process using data transfer per external interface. The production date thus changes from being a planned date to being an actual production date.
This time stamp contains data on the construction year and month, which are required for the trade-in.
Planned delivery date (time stamp)
Date on which the vehicle is planned to arrive at the dealer/end customer.
The system determines this date automatically from the appropriate Customizing settings.
Gross list price + currency
Price that results from the vehicle configuration.
This price is independent of business partner-specific discounts.
The gross list price changes if the vehicle configuration is changed later.
You must create an organizational role with the key GROS (see: Calculating the Gross List Price Using Organizational Roles) if you want the system to be able to calculate the gross list price.
Vehicle usage
Planned usage for the vehicle, for example, use as end customer vehicle, in fleet sales, as demonstration car and so on.
This data can be used to help you prioritize cars when processing purchase orders and can be transferred to the manufacturer.
Sales campaign
Campaign for a specific length of time for the sale of a specific vehicle model or configuration at a reduced price. You can assign a sales campaign to a vehicle using the action CAMP.
Examples: sale of old models for which the new model is already on the market, sale of old stock with unusual configurations etc.
You can trigger special pricing functions in the sales documents of vehicles that belong to a sales campaign. There are two options:
·        You can add the field as an object characteristic to the vehicle configuration (see: Adding Object Characteristic to Configuration)
·        You can use the options for flexible enhancements to SD pricing
Visibility
Indicator in the vehicle table that can be used to influence whether a vehicle can be seen by dealers during the vehicle search or not.
This indicator is controlled by the actions SHOW and HIDE.
There are two options for removing a vehicle form the hit list of the vehicle search:
·        You can use the visibility dependently of the Organization Role as parameter when selecting vehicles from the database (BAdI VLC_SEARCH_ADAPTION)
Example: a VMS user at the importers can display all the vehicles but a VMS user at the dealers can only display the vehicles that are visible for all the dealers and additionally all the vehicles (also not visible) for which he/she has created a sales order/offer or for which, for example, he/she has been assigned as customer during the reservation process.
·        You can use the visibility according to the selection in Category Management as parameter. This second option has the disadvantage that the performance is not as good, since many vehicles are selected that are then filtered out later.
Customer
Business partner to whom the vehicle is sold.
This is usually the dealer. It may, however, also be an end customer, for example, a car rental/hire company that wants to buy an entire fleet of cars from the importer, or an employee of the importer who wants to buy a vehicle directly from the importer.
You can manage one-time customers, for example the employees of the importer, using a CpD one-time/suspense account in the customer master record.
End customer
End customer for the vehicle.
The data for the end customer are stored in the functions for business partner management. You can assign an end customer by using action BUPA or by using the function End Customer, which is available in several actions.
Dealers can create end customer data; this end customer data is then assigned to the appropriate dealer and can only be viewed by him/her.
Vendor
Business partner from whom the vehicle is procured.
This is usually the manufacturer (OEM). In cases where there is multi-level procurement, it may be an intermediate vendor, for example a distribution center.
When a used vehicle is being exchanged for cash, the vendor can also be, for example, a rent-a car company or any other person. Such a business partner may also be managed at the same time as a customer in the system.
You can manage one-time vendors, for example the previous owner when exchanging a vehicle for cash, using a CpD one-time/suspense account in the customer master record.
Vehicle Search Area
Geographical or organizational area in which vehicles are made available and searched for.
This area defines the outermost limit within which a vehicle search can take place. You can assign a vehicle search area using action SMOD.
A vehicle search area can include more than one sales organization.
Each vehicle can only belong to exactly one vehicle search area.
You can define rules for the vehicle search and search areas in Category Management and thus represent a uniform policy. Prerequisite: all the vehicles within one vehicle search area are technically compatible and allowed in every other geographical region.
Sharing Level
In a scenario in which more than one dealer, SD organization etc. can access the same vehicle stock (defined by the vehicle search area), you can increase or decrease the availability of a vehicle for other dealers, sales organizations etc. by using the sharing level.
The sharing level is used as a parameter in Category Management.
Created by
System user who created the vehicle.
Registration date
Counter/meter reading + unit
You can display this vehicle data. Choose transaction VELO (Vehicle Manager), perform a vehicle search, choose a vehicle and then choose the tab page Detail.
The vehicle data is the result of actions that have been performed for a vehicle. The data is enhanced and updated continuously. Example: the following data is entered and determined on creating a vehicle: internal vehicle number, plant, vehicle model, configuration, primary action control, primary status, availability status, gross list price and, where appropriate, production date and vendor. When the purchase order is created, this data is completed with entries for the vendor and the location.
Most of the vehicle data is also available as a parameter for the vehicle search.
You can define further vehicle data according to your requirements. To do this, choose Customizing for the Vehicle Management System (VMS) ® Enhancements ® Define Additional Data for Vehicle (transaction OVELO4). If you are dealing with qualifiers in the additional table, you can display the data separately (transaction VELO, tab page Detail, screen Vehicle Data, function Addnl Data). If you are dealing with vehicle attributes in the vehicle table, they are displayed as fields in the lists of the vehicle overview and the vehicle details. You can find further information under Programming Your Own Actions.
You can enter and store documents for each vehicle (action ADDO Assign documents) and display them (transaction VELO, tab page Detail, screen Vehicle Data, pushbutton Documents). You can find further information under Business Document Navigator

Implement badi for vms isolate action

Dear expert,
I am developing the VMS(vehicle management system) action which is set as "isolate" action.
I use badi for isolate action to perform execution logic (like update ztable and populate some value to VMS table).
but the problem is, the history of vehicle, status of vehicle and green light at navigation pannel is not updated even the message display successful.
Do I need to put some FM call after execute logic within this isolate badi?
Can some give me some sample?
Thank a lot.
Regards,
Boonsom

Hi Tim,
You can execute a method call in Action definition.
This method call is a badi implementation.
Badi: EXEC_METHODCALL_PPF
In this method call you can trigger your external interface.
Steps:
1) Implement badi EXEC_METHODCALL_PPF to create you method implementation from which you will trigger your external interface
2) Create an action definition in Action profile, in third level configuration for action profile, specifiy Method Call and assign the badi implemented method here.
3) Schedule the action condition.
Thats all.
Test the Scenario.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

Vehicle stuck in Yard Management - Is there a way to change the HU Status?

Hi Everyone,
I'm trying to remove a vehicle that's stuck in Yard Management (under a warehouse) but I had no luck so far. The problem is that the Handling Unit was set to deleted and I haven't been able to change its status through HU02 or even using HUMO. The system status right now is DLTD. When I try to delete the vehicle in YM, it says that I can't because of the status that's in right now.
Is there a way to change the system status back to 'PLND' for example?
Also, if I could find a way to set the user status, would it prevail over the system status?
If more information is needed, I'll gladly provide it.
Thanks everyone!

Hi Petr,
Thanks for replying.
I tried using this transaction but I don't think it's implemented in my company's SAP version.
I think I found what the problem is. In VEKP, the status field (VEKP-STATUS) is set to '0001' (Planned) instead of 0060 (Deleted). But if I display it using tcode HUMO, it shows up as 'DLTD'. Maybe the issue is that both status are not in sync with each other and that's why I can't remove the vehicle from Yard Management.

Vehicle Status???

Similar Messages

Maybe you are looking for