SAP CRM_GET_CROSS_DOCKING_DATA Function Module for makes ECC-RFC call and fills table which is used for display









CRM_GET_CROSS_DOCKING_DATA is a standard crm get cross docking 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 makes ECC-RFC call and fills table which is used for 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 get cross docking data FM, simply by entering the name CRM_GET_CROSS_DOCKING_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_GET_CROSS_DOCKING_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_GET_CROSS_DOCKING_DATA'"makes ECC-RFC call and fills table which is used for display
  EXPORTING
   IV_LOG_SYSTEM =  "Logisches System
*  IV_DOCUMENT_NO =  "Belegfluss: Belegnummer
*  IV_ITEM_NUMBER =  "Positionsnummer im Beleg
*  IV_TCD_NUMBER =  "Transport-Cross-Docking-Prozessnummer
*  IV_TCD_ITEM_NUMBER =  "Positionsnummer des Vertriebsbeleges

 IMPORTING
   ET_CD_DOCFLOW =  "Daten zur Anzeige des Transportation Cross Docking Belegflus
   ET_CD_DELIVERY_DATE =  "Letzes Lieferdatum pro Transport-Cross-Docking Prozess

EXCEPTIONS
   LOG_SYSTEM_INVALID = 1    SYSTEM_FAILURE = 2    COMMUNICATION_FAILURE = 3
.



IMPORTING Parameters details for CRM_GET_CROSS_DOCKING_DATA

IV_LOG_SYSTEM - Logisches System

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

IV_DOCUMENT_NO - Belegfluss: Belegnummer

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

IV_ITEM_NUMBER - Positionsnummer im Beleg

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

IV_TCD_NUMBER - Transport-Cross-Docking-Prozessnummer

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

IV_TCD_ITEM_NUMBER - Positionsnummer des Vertriebsbeleges

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

EXPORTING Parameters details for CRM_GET_CROSS_DOCKING_DATA

ET_CD_DOCFLOW - Daten zur Anzeige des Transportation Cross Docking Belegflus

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

ET_CD_DELIVERY_DATE - Letzes Lieferdatum pro Transport-Cross-Docking Prozess

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

EXCEPTIONS details

LOG_SYSTEM_INVALID -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CRM_GET_CROSS_DOCKING_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_et_cd_docflow  TYPE CRMT_3000_ALV_TCD_INFO_TAB, "   
lv_iv_log_system  TYPE CRMT_LOGSYS, "   
lv_log_system_invalid  TYPE CRMT_LOGSYS, "   
lv_iv_document_no  TYPE CRMT_OBJECT_ID, "   
lv_system_failure  TYPE CRMT_OBJECT_ID, "   
lv_et_cd_delivery_date  TYPE CRMT_CD_DELIVERY_DATE_TAB, "   
lv_iv_item_number  TYPE CRMT_POSNO, "   
lv_communication_failure  TYPE CRMT_POSNO, "   
lv_iv_tcd_number  TYPE CRMT_CD_PROCESS, "   
lv_iv_tcd_item_number  TYPE CRMT_POSNO. "   

  CALL FUNCTION 'CRM_GET_CROSS_DOCKING_DATA'  "makes ECC-RFC call and fills table which is used for display
    EXPORTING
         IV_LOG_SYSTEM = lv_iv_log_system
         IV_DOCUMENT_NO = lv_iv_document_no
         IV_ITEM_NUMBER = lv_iv_item_number
         IV_TCD_NUMBER = lv_iv_tcd_number
         IV_TCD_ITEM_NUMBER = lv_iv_tcd_item_number
    IMPORTING
         ET_CD_DOCFLOW = lv_et_cd_docflow
         ET_CD_DELIVERY_DATE = lv_et_cd_delivery_date
    EXCEPTIONS
        LOG_SYSTEM_INVALID = 1
        SYSTEM_FAILURE = 2
        COMMUNICATION_FAILURE = 3
. " CRM_GET_CROSS_DOCKING_DATA




ABAP code using 7.40 inline data declarations to call FM CRM_GET_CROSS_DOCKING_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.

 
 
 
 
 
 
 
 
 
 


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!