SAP CRM_BILLPLAN_GET_SPLIT_DATA Function Module for Get Data from IL for Value Split Display









CRM_BILLPLAN_GET_SPLIT_DATA is a standard crm billplan get split data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Data from IL for Value Split Display 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 billplan get split data FM, simply by entering the name CRM_BILLPLAN_GET_SPLIT_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM_BILLPLAN_IL
Program Name: SAPLCRM_BILLPLAN_IL
Main Program: SAPLCRM_BILLPLAN_IL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CRM_BILLPLAN_GET_SPLIT_DATA 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_BILLPLAN_GET_SPLIT_DATA'"Get Data from IL for Value Split Display
  EXPORTING
*  IV_USAGE = ' ' "Billing Plan Usage

 IMPORTING
   ES_1030_ENTRY_MODE =  "Input Mode for Value Split
   ES_1030_BILLPLAN_UI =  "Billing Plan Data
   ES_1030_PARTNER_FCT =  "Assign Billing Plan Type to Partner Functions
   ET_1030_SPLIT_UI =  "User Interface: Table of Billing Plan Dates
   ET_1030_BILLING_IT_UI =  "User Interface: Table of Billing Request Items
   ES_2030_ENTRY_MODE =  "Input Mode for Value Split
   ES_2030_BILLPLAN_UI =  "Billing Plan Data
   ET_2030_SPLIT_UI =  "User Interface: Table of Billing Plan Dates
   ET_2030_BILLING_IT_UI =  "User Interface: Table of Billing Request Items
.



IMPORTING Parameters details for CRM_BILLPLAN_GET_SPLIT_DATA

IV_USAGE - Billing Plan Usage

Data type: CRMT_BP_USAGE
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CRM_BILLPLAN_GET_SPLIT_DATA

ES_1030_ENTRY_MODE - Input Mode for Value Split

Data type: CRMT_VALUE_SPLIT_ENTRY_MODE_UI
Optional: No
Call by Reference: Yes

ES_1030_BILLPLAN_UI - Billing Plan Data

Data type: CRMT_1000_BILLPLAN_UI
Optional: No
Call by Reference: Yes

ES_1030_PARTNER_FCT - Assign Billing Plan Type to Partner Functions

Data type: CRMC_BILPT_PFCT
Optional: No
Call by Reference: Yes

ET_1030_SPLIT_UI - User Interface: Table of Billing Plan Dates

Data type: CRMT_1030_ALV_SPLIT_UI_TAB
Optional: No
Call by Reference: Yes

ET_1030_BILLING_IT_UI - User Interface: Table of Billing Request Items

Data type: CRMT_1000_BILLING_IT_UI_TAB
Optional: No
Call by Reference: Yes

ES_2030_ENTRY_MODE - Input Mode for Value Split

Data type: CRMT_2030_VSPLIT_ENTRY_MODE_UI
Optional: No
Call by Reference: Yes

ES_2030_BILLPLAN_UI - Billing Plan Data

Data type: CRMT_2000_BILLPLAN_UI
Optional: No
Call by Reference: Yes

ET_2030_SPLIT_UI - User Interface: Table of Billing Plan Dates

Data type: CRMT_1030_ALV_SPLIT_UI_TAB
Optional: No
Call by Reference: Yes

ET_2030_BILLING_IT_UI - User Interface: Table of Billing Request Items

Data type: CRMT_2000_BILLING_IT_UI_TAB
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CRM_BILLPLAN_GET_SPLIT_DATA 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_iv_usage  TYPE CRMT_BP_USAGE, "   SPACE
lv_es_1030_entry_mode  TYPE CRMT_VALUE_SPLIT_ENTRY_MODE_UI, "   
lv_es_1030_billplan_ui  TYPE CRMT_1000_BILLPLAN_UI, "   
lv_es_1030_partner_fct  TYPE CRMC_BILPT_PFCT, "   
lv_et_1030_split_ui  TYPE CRMT_1030_ALV_SPLIT_UI_TAB, "   
lv_et_1030_billing_it_ui  TYPE CRMT_1000_BILLING_IT_UI_TAB, "   
lv_es_2030_entry_mode  TYPE CRMT_2030_VSPLIT_ENTRY_MODE_UI, "   
lv_es_2030_billplan_ui  TYPE CRMT_2000_BILLPLAN_UI, "   
lv_et_2030_split_ui  TYPE CRMT_1030_ALV_SPLIT_UI_TAB, "   
lv_et_2030_billing_it_ui  TYPE CRMT_2000_BILLING_IT_UI_TAB. "   

  CALL FUNCTION 'CRM_BILLPLAN_GET_SPLIT_DATA'  "Get Data from IL for Value Split Display
    EXPORTING
         IV_USAGE = lv_iv_usage
    IMPORTING
         ES_1030_ENTRY_MODE = lv_es_1030_entry_mode
         ES_1030_BILLPLAN_UI = lv_es_1030_billplan_ui
         ES_1030_PARTNER_FCT = lv_es_1030_partner_fct
         ET_1030_SPLIT_UI = lv_et_1030_split_ui
         ET_1030_BILLING_IT_UI = lv_et_1030_billing_it_ui
         ES_2030_ENTRY_MODE = lv_es_2030_entry_mode
         ES_2030_BILLPLAN_UI = lv_es_2030_billplan_ui
         ET_2030_SPLIT_UI = lv_et_2030_split_ui
         ET_2030_BILLING_IT_UI = lv_et_2030_billing_it_ui
. " CRM_BILLPLAN_GET_SPLIT_DATA




ABAP code using 7.40 inline data declarations to call FM CRM_BILLPLAN_GET_SPLIT_DATA

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.

DATA(ld_iv_usage) = ' '.
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!