SAP K40C_MAP_EXTERNAL_TO_INTERNAL Function Module for









K40C_MAP_EXTERNAL_TO_INTERNAL is a standard k40c map external to internal SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 k40c map external to internal FM, simply by entering the name K40C_MAP_EXTERNAL_TO_INTERNAL into the relevant SAP transaction such as SE37 or SE38.

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



Function K40C_MAP_EXTERNAL_TO_INTERNAL 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 'K40C_MAP_EXTERNAL_TO_INTERNAL'"
  EXPORTING
   IS_DOC_HEADER =  "
*  ID_CO_TRANSAC = ' ' "CO business transaction
   ID_ACTIVITY =  "
*  ID_ERROR_PREFIX = ' ' "

 IMPORTING
   ES_DOC_HEADER =  "
   ES_DOC_HEADER_EXT =  "

TABLES
*  IT_DOC_ITEMS =  "
*  IT_SEND_CRITERIA =  "
*  IT_RECV_CRITERIA =  "
*  IT_CUST_FIELDS =  "Customer Fields
*  ET_DOC_ITEMS =  "
*  ET_EXT_PRICES =  "
*  ET_MESSAGES =  "Message Collector

EXCEPTIONS
   ERROR_DURING_MAPPING = 1
.



IMPORTING Parameters details for K40C_MAP_EXTERNAL_TO_INTERNAL

IS_DOC_HEADER -

Data type:
Optional: No
Call by Reference: Yes

ID_CO_TRANSAC - CO business transaction

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

ID_ACTIVITY -

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

ID_ERROR_PREFIX -

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

EXPORTING Parameters details for K40C_MAP_EXTERNAL_TO_INTERNAL

ES_DOC_HEADER -

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

ES_DOC_HEADER_EXT -

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

TABLES Parameters details for K40C_MAP_EXTERNAL_TO_INTERNAL

IT_DOC_ITEMS -

Data type:
Optional: Yes
Call by Reference: Yes

IT_SEND_CRITERIA -

Data type: BAPIACKECR
Optional: Yes
Call by Reference: Yes

IT_RECV_CRITERIA -

Data type: BAPIACKECR
Optional: Yes
Call by Reference: Yes

IT_CUST_FIELDS - Customer Fields

Data type: BAPIEXTC
Optional: Yes
Call by Reference: Yes

ET_DOC_ITEMS -

Data type: RK40C
Optional: Yes
Call by Reference: Yes

ET_EXT_PRICES -

Data type: COEXPRICES
Optional: Yes
Call by Reference: Yes

ET_MESSAGES - Message Collector

Data type: MESG
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ERROR_DURING_MAPPING - Error During Mapping

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for K40C_MAP_EXTERNAL_TO_INTERNAL 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:
lt_it_doc_items  TYPE STANDARD TABLE OF STRING, "   
lv_es_doc_header  TYPE COBK, "   
lv_is_doc_header  TYPE COBK, "   
lv_error_during_mapping  TYPE COBK, "   
lv_id_co_transac  TYPE CO_VORGANG, "   SPACE
lt_it_send_criteria  TYPE STANDARD TABLE OF BAPIACKECR, "   
lv_es_doc_header_ext  TYPE COHEADER_EXT, "   
lv_id_activity  TYPE C, "   
lt_it_recv_criteria  TYPE STANDARD TABLE OF BAPIACKECR, "   
lt_it_cust_fields  TYPE STANDARD TABLE OF BAPIEXTC, "   
lv_id_error_prefix  TYPE CHAR22, "   SPACE
lt_et_doc_items  TYPE STANDARD TABLE OF RK40C, "   
lt_et_ext_prices  TYPE STANDARD TABLE OF COEXPRICES, "   
lt_et_messages  TYPE STANDARD TABLE OF MESG. "   

  CALL FUNCTION 'K40C_MAP_EXTERNAL_TO_INTERNAL'  "
    EXPORTING
         IS_DOC_HEADER = lv_is_doc_header
         ID_CO_TRANSAC = lv_id_co_transac
         ID_ACTIVITY = lv_id_activity
         ID_ERROR_PREFIX = lv_id_error_prefix
    IMPORTING
         ES_DOC_HEADER = lv_es_doc_header
         ES_DOC_HEADER_EXT = lv_es_doc_header_ext
    TABLES
         IT_DOC_ITEMS = lt_it_doc_items
         IT_SEND_CRITERIA = lt_it_send_criteria
         IT_RECV_CRITERIA = lt_it_recv_criteria
         IT_CUST_FIELDS = lt_it_cust_fields
         ET_DOC_ITEMS = lt_et_doc_items
         ET_EXT_PRICES = lt_et_ext_prices
         ET_MESSAGES = lt_et_messages
    EXCEPTIONS
        ERROR_DURING_MAPPING = 1
. " K40C_MAP_EXTERNAL_TO_INTERNAL




ABAP code using 7.40 inline data declarations to call FM K40C_MAP_EXTERNAL_TO_INTERNAL

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_id_co_transac) = ' '.
 
 
 
 
 
 
DATA(ld_id_error_prefix) = ' '.
 
 
 
 


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!