SAP ABAP IMG Activity VLC_HISTORY_CALL_TRA (BAdI: Display Documents from Vehicle History)
Hierarchy
ECC-DIMP (Software Component) DIMP
   IS-A-VMS (Application Component) Vehicle Management System
     ISAUTO_VLC (Package) Vehicle Management System (VMS)
IMG Activity
ID VLC_HISTORY_CALL_TRA BAdI: Display Documents from Vehicle History  
Transaction Code S_KA5_12001310   (empty) 
Created on 20021129    
Customizing Attributes VLC_HISTORY_CALL_TRA   BAdI: Display Documents 
Customizing Activity VLC_HISTORY_CALL_TRA   BAdI: Display Documents 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name VLC_HISTORY_CALL_TRA    

Use

This business add-in (BAdI) is used in the Vehicle Management System (IS-A-VMS) component.

The Vehicle Management System (VMS) is used to execute actions on vehicles. For each action executed, a vehicle receives an entry in the history. Some of the actions cause documents like purchase orders or sales orders to be created. You can then see the documents created by clicking on the corresponding history entry in the vehicle detailed display.

You go from the VMS history display to the transaction displaying the created documents via CALL TRANSACTION.

Data is prepared for CALL TRANSACTION and given to the user in function module VELO04_READ_TRANSCALLDATA.

You can also write customer-specific actions for VMS. History entries will also be generated for these actions. If customer actions cause documents to be created, for which display transactions exist, it is a good idea to be able to jump from VMS history into these display transactions.

The BAdI VLC_HISTORY_CALL_TRA allows you to provide data for such actions needed by the CALL TRANSACTION. This makes it possible for documents generated by customer actions to be displayed when the corresponding history entry is clicked upon.

For more information see the interface documentation.

The BAdI has the method PREPARE_CALL_TRANSACTION_DATA with the following parameters:

  • VGUID_IV: Vehicle GUID (Globally Unique IDentifier)
  • TSTAMP_IV: Long time stamp
  • ACTDOCTYPE_IV: Type of document created by action
  • ACTION_IV: Action, which created the document
  • TCODE_EV: Transaction for displaying the document
  • BDC_ET: Table for batch input to go to transactions
  • VLCHISTORY_BORLINK_CS: Data used to link between BOR type and vehicle GUID for the vehicle history

Requirements

Standard settings

This BAdI does not have a default implementation.

Activities

Procedure for BAdI Implementation

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG VLC_HISTORY_CALL_TRA 0 KA50000029 Vehicle Management System 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20021219 
SAP Release Created in 471