Ansicht
Dokumentation

DPVMS_BADI_MODEL - BAdI: Back-End Integration of Dealer Portal

CL_GUI_FRONTEND_SERVICES - Frontend Services   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Vehicle Management System (IS-A-DP-VMS) component.

You can use this BAdI to influence the way how the dealer portal for VMS accesses the VMS back-end functions. Every part of the user interface calls methods of this BAdI to retrieve the necessary data from VMS.

The dealer portal for VMS uses the MVC (model view controller) architecture. This BAdI represents the model.

For this BAdI, the CL_DEF_IM_DPVMS_BADI_MODEL fallback class is available. This class contains the dealer portal standard coding.

You can create implementations of this BAdI that overwrite single methods of the fallback class. You can reuse the standard functions where it covers your needs and overwrite it where you require different functions.

The BAdI provides the following methods:

• GET_COMP_WIND returns the specific component and window, which includes a layout for address and end customer (business partner) detail visualization.

• SEARCH_BUPA searches for end customers (business partners).

• GET_BUPA_DETAIL returns detail data for an end customer.

• CREATE_BUPA creates an end customer.

• CHANGE_BUPA changes the data of an end customer.

• DELETE_BUPA sets the deletion flag for an end customer.

• GET_ALL_FORMCNTRYS returns all country/region codes, which are defined in the Customizing activity Assign WD Components to Country/Region-Specific End Customer Address Formats.

• SEARCH_SDDOC searches for sales documents by sales document data.

• GET_OPERATION_PRICING returns a table of detailed condition entries including short texts. It can be called as follows:

• Simulation mode: Used when no document , but just configuration data (for example, vehicle) is passed.

• Reading mode: Used when exisiting documents are passed (for the fallback class, implementation it is only possible to simulate one item at the same time).

,,Additionally it can be retrieved either the item or the header pricing information for an exisiting document

• GET_SEARCH_CLASS determines the variant configuration class for a list of vehicle models. If the models do not have the same class assigned, no class is returned. In case the models have a common family class, the family class is returned. The method is used by the vehicle configuration search.

• GET_CLASS_CSTICS returns the list of characteristics and characteristic values for the provided class. The method is used by the vehicle configuration search.

• SEARCH_VEHICLE searches for vehicles by variant configuration and vehicle master data.

• GET_HISTORY returns the vehicle history for one vehicle.

• GET_MODEL_DATA returns the model list and the model hierarchy based on the VMS role assignment of the user.

• GET_DEST_CFG returns the start URL of the variant configuration UI. The fallback implementation returns the URL that is used to start the IPC.

• GET_NAVIGATION_DATA returns the navigation data, which is defined in the Customizing activity Define Screen Navigation.

• GET_ORG_ROLES returns the list of all organizational roles that are available for the user. The personalization screen uses this method to provide the user the possibility to choose one of these roles.

• GET_ORG_ROLE_LONGTEXTS determines the longtexts for the organizational role. The longtext is a concatenation of the data created for the organizational role in transaction VELORO.

• GET_ORG_ROLE_FOR_USER returns the organizational VMS role which is currently assigned to the user.

• GET_VALID_UACTIONS determines the list of user actions that can currently be executed for the list of operations in IT_VLCDIAVEHI.

• PREPARE_CONFIGURATION is called for setting all the parameters that are necessary to start the variant configurator user interface. The fallback implementation provides the parameters necessary for IPC.

• RETRIEVE_CONFIGURATION passes back the configuration that has been returned from the variant configuration UI. The fallback implementation provides the data returned from IPC.

• CREATE_CFG_DISPLAY_UI dynamically generates the display screen for the variant configuration of a vehicle or a sales document item. It generates labels, input fields etc. The variant configuration is for example displayed on the vehicle detail screen, the sales document detail screen, and various function screens like Change Sales Order.

• CREATE_CFG_SEARCH_UI dynamically generates the vehicle configuration search screen with labels and input fields for all characteristics of the model.

• GET_PERSONALIZATION reads the personalization data of the user.

• SET_PERSONALIZATION writes the personalization data of the user.

• GET_CFG_FROM_SHMO returns the variant configuration from the shared memory. The shared memory is used to pass vehicle configuration from the variant configuration UI to the function screens and to the vehicle search screen.

• CREATE_SHMO_FOR_CFG writes a variant configuration into the shared memory.

• DELETE_SHMO_CFG deletes a variant configuration from the shared memory.

• GET_OPERATION_DETAIL returns detailed vehicle and sales document data for a list of operations.

• PREPARE_FUNCTION is called when a function is started and executed before the function screen gets displayed. It executes the PREPARE function module to fill the function screen with data.

• EXECUTE_FUNCTION executes a VMS dealer portal function.

• GET_DDLIST_ENTRIES reads the possible values of dropdown lists. The fallback class provides value lists for a selection of data elements and the possibility to get a value list by specifying a table and a column name. Note that the fallback implemenation is not able to handle any dropdown list box

• GET_F4_HELP_ENTRIES is used by the RFC-enabled input helps to retrieve input help data from the back-end system.

• GET_APPLID_FOR_ORGROLE returns the power list application ID that is assigned to the organizational role. The method accesses the settings of Customizing activity Determine Work Overview.

• GET_ASSIGNMENTS is called for a list of operations and determines the vehicles that are eventually attached to sales documents and the sales documents that are eventually attached to vehicles. The table CT_OPERATION_KEYS may contain incomplete entries that may either come from the vehicle search (only VGUID) or from the sales document search (VBELN and POSNR). It then uses the VMS late order assignment function to determine the relations between vehicles and sales documents.

• GET_ORG_ROLE_DATA returns all data of an organizational role. Either the key of the role can be provided or the user name. In case of the user name, the user's current organizational role is read and its data is returned.

• GET_AKNOWLEDGE_CASES reads the VMS acknowledge table VLCAKN. It is used by the feeder class of the work overview that displays acknowledge cases.

• GET_RESERVATIONS returns all reservations that are currently valid for the user logged on and his organizational role.

• GET_TRANSFER_DATA returns the data from the VMS transfer table VLCVTRANSFER.

• GET_FPM_IDR_FUNCTN_TITLE returns the title text for the function screens, which is displayed in the identification region's title bar.

• GET_RFCDEST returns the RFC destination that is defined in Customizing activity Define Back-End RFC Destination and that should be used by the calls of this BADI that have to access the VMS back-end system.

• IS_UACTION checks if the provided user action is really defined in Customizing activity Define User Actions.

• DEQUEUE_SALES_DOC releases the lock that is set on a sales document for which a function has been executed.

• CHECK_OPDATA_VALIDITY checks if the data of the operation for which an user action is started is still valid, or if it has changed in the meantime because another user has executed an user action for the operation.

• GET_CONFIG reads the variant configuration data for a list of operations. It is used during the function PREPARE phase to read the data necessary for calling the variant configuration UI.

• GET_CONFIG_TEXT returns the long texts for characteristics and characteristic values.

• GET_FIELD_CATALOG_POWL_ALV allows to define field catalogs for work overview power lists.

• DEFINE_FIELD_CATALOG_ALV allows to define field catalogs for ALV lists.

• HANDLE_POWL_ALV_CELL_ACTION allows to react on events, which are triggered from the table cells of a power list. Possible event trigger can be UI elements like buttons and links.

• HANDLE_ALV_CELL_ACTION allows to react on events, which are triggered from the table cells of usual ALV lists. Possible event trigger can be UI elements like buttons and links.

• CHECK_PLM_VC_ACTIVE checks whether the characteristic value assignment screen should be used for configuration.

• GET_ADD_PARAMS_PLM_VC retrieves the context and properties table for the characteristic value assignment screen for configuration. These additional parameters are originally used by the external configurator application, but are reused for the characteristic value assignment screen.

• In the standard system, there is no activated BAdI implementation.

• The BAdI is designed for multiple use. All activated implementations are called and executed.

• The BAdI is not filter-dependent.

• For this BAdI, the default implementation class CL_DEF_IM_DPVMS_BADI_MODEL is available. If no customer-specific implementation is active, this default implementation class is called.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

TXBHW - Original Tax Base Amount in Local Currency   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 12455 Date: 20240523 Time: 180354     sap01-206 ( 217 ms )