SAP CRM_MAP_DIVISION Function Module for CRM Division in R/3 Sparte konvertieren
CRM_MAP_DIVISION is a standard crm map division SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CRM Division in R/3 Sparte konvertieren 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 map division FM, simply by entering the name CRM_MAP_DIVISION into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_OPPT_SD_FB
Program Name: SAPLCRM_OPPT_SD_FB
Main Program: SAPLCRM_OPPT_SD_FB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_MAP_DIVISION 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_MAP_DIVISION'"CRM Division in R/3 Sparte konvertieren.
EXPORTING
I_DIVISION = "Sparte
IMPORTING
E_SPART = "Sparte
EXCEPTIONS
NO_MAPPING_DEFINED = 1 R3_KEY_NOT_DEFINED = 2
IMPORTING Parameters details for CRM_MAP_DIVISION
I_DIVISION - Sparte
Data type: CRMT_DIVISIONOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_MAP_DIVISION
E_SPART - Sparte
Data type: SPARTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_MAPPING_DEFINED -
Data type:Optional: No
Call by Reference: Yes
R3_KEY_NOT_DEFINED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_MAP_DIVISION 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_e_spart | TYPE SPART, " | |||
| lv_i_division | TYPE CRMT_DIVISION, " | |||
| lv_no_mapping_defined | TYPE CRMT_DIVISION, " | |||
| lv_r3_key_not_defined | TYPE CRMT_DIVISION. " |
|   CALL FUNCTION 'CRM_MAP_DIVISION' "CRM Division in R/3 Sparte konvertieren |
| EXPORTING | ||
| I_DIVISION | = lv_i_division | |
| IMPORTING | ||
| E_SPART | = lv_e_spart | |
| EXCEPTIONS | ||
| NO_MAPPING_DEFINED = 1 | ||
| R3_KEY_NOT_DEFINED = 2 | ||
| . " CRM_MAP_DIVISION | ||
ABAP code using 7.40 inline data declarations to call FM CRM_MAP_DIVISION
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