Kontakt

Ansicht
Dokumentation

VLC_BW_INTEGRATOR - BAdI: Vehicle Management System: SAP BW Integration

VLC_BW_INTEGRATOR - BAdI: Vehicle Management System: SAP BW Integration

General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the component Vehicle Management System (IS-A-VMS). This BAdI enables you to monitor the transfer of vehicles and links between vehicles and documents from the SAP DIMP Vehicle Management System (VMS) to the SAP Business Information Warehouse (SAP BW). With this BAdI you can transfer additional document links to SAP BW. You can exclude document links that are transferred in the standard to SAP BW.

The BAdI is called when you call the SAP BW extractor for the vehicle document links. In the standard, the extractor supports links between vehicles and the following documents:

  • Sales order
  • Order
  • Goods receipt
  • Goods issue
  • Incoming invoice
  • Outgoing invoice

You must implement the BAdI in the following cases:

  • You want to extract other document links that are created by SAP standard actions (for example, for the service order).
  • You have implemented some customer actions that create document links. You want to extract these document links.
  • If you do not need some of these document links for your business analyses you can remove them from the data transfer to SAP BW to improve performance.

You have set up a data transfer for SAP BW 3.5 or a higher release.

In the standard the BAdI is active. The default coding is executed automatically. The BAdI has a standard implementation, in which some of the standard document links are extracted. The standard implementation also uses the standard vehicle action document types.

The BAdI is not filter-dependent. The BAdI is not reusable.

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.

BAdI methods

Extract document links






BAL_S_LOG - Application Log: Log header data   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 4280 Date: 20240523 Time: 161710     sap01-206 ( 64 ms )