Vehicle IDoc

Definition

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 .

For more information, see the documentation for the SAP Web Application Server under Processing of IDocs .

Use

  • The inbound IDoc 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 Start of the navigation path Control Data Next navigation step Define External Status End of the navigation path ): 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.

    You can display inbound IDocs using the standard transactions WE02 or the VMS transaction VELOM Status Monitor for Vehicle IDoc .

  • The outbound IDoc is linked to VMS message control (see Customizing for VMS). As importer, you can send faxes, e-mails and IDocs containing the vehicle data to subordinate or superior sales organizations using action MSSO . The system then uses the plant and the action to find an organization channel and an external status in the above-named Customizing table and writes these to the IDoc. If the recipient of the IDoc also uses VMS, he/she can evaluate this data and process it automatically using the same Customizing table in his/her own VMS.

    Note Note

    You can use user parameter VELO_ORGCH to enter a default value for the organization channel for outbound IDocs.

    End of the note.

    You can display outbound IDocs using the standard transaction WE05.

    Caution Caution

    Outbound and inbound IDocs use the same Customizing table (transaction OVELO5) and read it once forwards and once backwards. Please ensure that the table only contains clear and precise entries. If the outbound IDoc finds ambiguous entries, the data is sent but it cannot be processed any further on the receiving side and a warning message appears.

    End of the caution.

Structure

The vehicle IDoc VEHCLE01 contains the following segments :

  • E1VLCK1 vehicle identification : required segment, number 1 (organization channel, external status, vehicle ID, internal/external vehicle number, vehicle identification number)

    • E1VLCK2 vehicle data : optional segment, number 1 (vehicle model, plant, storage location, vendor, customer, end customer, visibility, availability, address, production date, delivery date, vehicle use, sales campaign, gross list price, currency, vehicle search area, original ordering party, access authorization)

    • E1VLCC1 configuration data : optional segment, number 1

      E1VLCC2 instance data: optional segment, number n

      E1VLCC3 part of data: optional segment, number n

      E1VLCC4 characteristic value assignment: optional segment, number n

    • E1VLCA1 additional data : optional segment, number n (qualifier, qualifier characteristics)

  • E1EDS01 general totals segment : required segment, number 1

The fields Organization channel , External status and one of the vehicle numbers must be filled in segment E1VLCK1 for inbound IDocs and in segment E1VLCK2 the field Vehicle model (only for Create actions).

The inbound vehicle IDoc has message type VLCCPO Vehicle: purchase order confirmation/status tracking , the outbound vehicle IDoc has message type VLCVDT Vehicle detail data .

Example for an Inbound IDoc

As importer you receive a purchase order confirmation from manufacturer X that contains a small configuration change. The vehicle has, for example, a different colour from that specified in the purchase order. The external status is Purchase order confirmed with change . In Customizing you have assigned the action Change purchase order to the external status Purchase order confirmed with change and the organization channel XY. As soon as you confirm the configuration change, the system performs this action. The vehicle receives the internal status Purchase order confirmed and the purchase order is changed accordingly.