SAP CRM_ISUSVK_MAP_PV_TO_TABLE Function Module for Mapping Preisvereinbarung auf Bapicuval
CRM_ISUSVK_MAP_PV_TO_TABLE is a standard crm isusvk map pv to table SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mapping Preisvereinbarung auf Bapicuval processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for crm isusvk map pv to table FM, simply by entering the name CRM_ISUSVK_MAP_PV_TO_TABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_UPLOAD_ISU_CONTRACT
Program Name: SAPLCRM_UPLOAD_ISU_CONTRACT
Main Program: SAPLCRM_UPLOAD_ISU_CONTRACT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_ISUSVK_MAP_PV_TO_TABLE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CRM_ISUSVK_MAP_PV_TO_TABLE'"Mapping Preisvereinbarung auf Bapicuval.
EXPORTING
TX_PRICE_AGREEMENT = "GUID of a CRM Order Object
IMPORTING
TY_ECRM_PV_MAP = "Price Agreement
IMPORTING Parameters details for CRM_ISUSVK_MAP_PV_TO_TABLE
TX_PRICE_AGREEMENT - GUID of a CRM Order Object
Data type: /1CN/WORKING_SET_I_D_CRM_TOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_ISUSVK_MAP_PV_TO_TABLE
TY_ECRM_PV_MAP - Price Agreement
Data type: ECRM_PV_MAP_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_ISUSVK_MAP_PV_TO_TABLE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_ty_ecrm_pv_map | TYPE ECRM_PV_MAP_T, " | |||
lv_tx_price_agreement | TYPE /1CN/WORKING_SET_I_D_CRM_T. " |
  CALL FUNCTION 'CRM_ISUSVK_MAP_PV_TO_TABLE' "Mapping Preisvereinbarung auf Bapicuval |
EXPORTING | ||
TX_PRICE_AGREEMENT | = lv_tx_price_agreement | |
IMPORTING | ||
TY_ECRM_PV_MAP | = lv_ty_ecrm_pv_map | |
. " CRM_ISUSVK_MAP_PV_TO_TABLE |
ABAP code using 7.40 inline data declarations to call FM CRM_ISUSVK_MAP_PV_TO_TABLE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects