Kontakt

Ansicht
Dokumentation

VLC_HISTORY_CALL_TRA - BAdI: Display Documents from Vehicle History

VLC_HISTORY_CALL_TRA - BAdI: Display Documents from Vehicle History

Fill RESBD Structure from EBP Component Structure   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

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

Procedure for BAdI Implementation






ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 2203 Date: 20240523 Time: 152255     sap01-206 ( 44 ms )