Hierarchy
⤷ IS-A-VMS (Application Component) Vehicle Management System
⤷ ISAUTO_VLC (Package) Vehicle Management System (VMS)
IMG Activity
ID | VLC_BW_INTEGRATOR | BAdI: Vehicle Management System: SAP BW Integration |
Transaction Code | S_ALI_97000046 | (empty) |
Created on | 20040318 | |
Customizing Attributes | VLC_BW_INTEGRATOR | BAdI: Vehicle Management System: SAP BW Integration |
Customizing Activity | VLC_BW_INTEGRATOR | BAdI: Vehicle Management System: SAP BW Integration |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | VLC_BW_INTEGRATOR |
Use
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.
Requirements
You have set up a data transfer for SAP BW 3.5 or a higher release.
Standard settings
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.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
See also:
BAdI methods
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_BW_INTEGRATOR | 0 | KA50000029 | Vehicle Management System |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20040318 |
SAP Release Created in | 500 |