SAP SD_SHIPMENT_HEADER_DESCRIPTION Function Module for NOTRANSL: Füllen der Bezeichnungen zum Transportkopf (dynamischen Teil fül









SD_SHIPMENT_HEADER_DESCRIPTION is a standard sd shipment header description SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Füllen der Bezeichnungen zum Transportkopf (dynamischen Teil fül 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 sd shipment header description FM, simply by entering the name SD_SHIPMENT_HEADER_DESCRIPTION into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_SHIPMENT_HEADER_DESCRIPTION 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 'SD_SHIPMENT_HEADER_DESCRIPTION'"NOTRANSL: Füllen der Bezeichnungen zum Transportkopf (dynamischen Teil fül
EXPORTING
I_XVTTK = "
* I_LANGU = SY-LANGU "Language
* I_ADRNR = "Address

CHANGING
* C_TXT_DOCUMENT_CAT = "
* C_ICON_SHIPPING_TYPE = "
* C_TXT_SHIP_TYP_PREL = "
* C_ICON_SHIP_TYP_PREL = "
* C_TXT_SHIP_TYP_SUBS = "
* C_ICON_SHIP_TYP_SUBS = "
* C_TXT_LEG_INDICATOR = "
* C_TXT_SHIPPING_COND = "Description of the shipping conditions
* C_TXT_ROUTE = "Description of Route
* C_TXT_CARRIER = "Description of Service Provider
* C_TXT_OVERALL_STATUS = "Overall Status Name
* C_TXT_PLANNING_POINT = "
* C_ICON_OVERALL_STATUS = "
* C_TXT_FREIGHT_COST_RELEVANCE = "
* C_TXT_FREIGHT_CALC_STATUS = "
* C_TXT_FREIGHT_SETT_STATUS = "
* C_TXT_OVRL_FREIGHT_CALC_STATUS = "
* C_TXT_OVRL_FREIGHT_SETT_STATUS = "
* C_TXT_SPECIAL_PROCESSING = "
* C_TXT_PRICING_PROCEDURE = "
* C_ROUTID = "
* C_TXT_STATUS_PLANNED = "
* C_TXT_SHIPMENT_TYPE = "
* C_TXT_STATUS_REGISTRATED = "
* C_TXT_STATUS_LOAD_START = "
* C_TXT_STATUS_LOAD_END = "
* C_TXT_STATUS_PROCESSING = "
* C_TXT_STATUS_SHIPM_START = "
* C_TXT_STATUS_SHIPM_END = "
* C_TXT_ADD_INFO_1 = "
* C_TXT_ADD_INFO_2 = "
* C_TXT_ADD_INFO_3 = "
* C_TXT_ADD_INFO_4 = "
* C_TXT_LEG_DET_TYPE = "
* C_TXT_CARRADDR = "
* C_TXT_ROUTE_STAGES = "
* C_TXT_PROCESSING_TYPE = "
* C_TXT_PROCESS_CONTROL = "
* C_TXT_SERVICE_LEVEL = "
* C_TXT_SHIPPING_TYPE = "Description of the Shipping Type
.



IMPORTING Parameters details for SD_SHIPMENT_HEADER_DESCRIPTION

I_XVTTK -

Data type: VTTKVB
Optional: No
Call by Reference: No ( called with pass by value option)

I_LANGU - Language

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ADRNR - Address

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for SD_SHIPMENT_HEADER_DESCRIPTION

C_TXT_DOCUMENT_CAT -

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

C_ICON_SHIPPING_TYPE -

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

C_TXT_SHIP_TYP_PREL -

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

C_ICON_SHIP_TYP_PREL -

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

C_TXT_SHIP_TYP_SUBS -

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

C_ICON_SHIP_TYP_SUBS -

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

C_TXT_LEG_INDICATOR -

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

C_TXT_SHIPPING_COND - Description of the shipping conditions

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

C_TXT_ROUTE - Description of Route

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

C_TXT_CARRIER - Description of Service Provider

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

C_TXT_OVERALL_STATUS - Overall Status Name

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

C_TXT_PLANNING_POINT -

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

C_ICON_OVERALL_STATUS -

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

C_TXT_FREIGHT_COST_RELEVANCE -

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

C_TXT_FREIGHT_CALC_STATUS -

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

C_TXT_FREIGHT_SETT_STATUS -

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

C_TXT_OVRL_FREIGHT_CALC_STATUS -

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

C_TXT_OVRL_FREIGHT_SETT_STATUS -

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

C_TXT_SPECIAL_PROCESSING -

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

C_TXT_PRICING_PROCEDURE -

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

C_ROUTID -

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

C_TXT_STATUS_PLANNED -

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

C_TXT_SHIPMENT_TYPE -

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

C_TXT_STATUS_REGISTRATED -

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

C_TXT_STATUS_LOAD_START -

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

C_TXT_STATUS_LOAD_END -

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

C_TXT_STATUS_PROCESSING -

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

C_TXT_STATUS_SHIPM_START -

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

C_TXT_STATUS_SHIPM_END -

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

C_TXT_ADD_INFO_1 -

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

C_TXT_ADD_INFO_2 -

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

C_TXT_ADD_INFO_3 -

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

C_TXT_ADD_INFO_4 -

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

C_TXT_LEG_DET_TYPE -

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

C_TXT_CARRADDR -

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

C_TXT_ROUTE_STAGES -

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

C_TXT_PROCESSING_TYPE -

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

C_TXT_PROCESS_CONTROL -

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

C_TXT_SERVICE_LEVEL -

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

C_TXT_SHIPPING_TYPE - Description of the Shipping Type

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

Copy and paste ABAP code example for SD_SHIPMENT_HEADER_DESCRIPTION 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_i_xvttk  TYPE VTTKVB, "   
lv_c_txt_document_cat  TYPE C, "   
lv_c_icon_shipping_type  TYPE C, "   
lv_c_txt_ship_typ_prel  TYPE C, "   
lv_c_icon_ship_typ_prel  TYPE C, "   
lv_c_txt_ship_typ_subs  TYPE C, "   
lv_c_icon_ship_typ_subs  TYPE C, "   
lv_c_txt_leg_indicator  TYPE C, "   
lv_c_txt_shipping_cond  TYPE C, "   
lv_c_txt_route  TYPE C, "   
lv_c_txt_carrier  TYPE C, "   
lv_c_txt_overall_status  TYPE C, "   
lv_i_langu  TYPE SY-LANGU, "   SY-LANGU
lv_c_txt_planning_point  TYPE C, "   
lv_c_icon_overall_status  TYPE C, "   
lv_c_txt_freight_cost_relevance  TYPE C, "   
lv_c_txt_freight_calc_status  TYPE C, "   
lv_c_txt_freight_sett_status  TYPE C, "   
lv_c_txt_ovrl_freight_calc_status  TYPE C, "   
lv_c_txt_ovrl_freight_sett_status  TYPE C, "   
lv_c_txt_special_processing  TYPE C, "   
lv_c_txt_pricing_procedure  TYPE C, "   
lv_c_routid  TYPE C, "   
lv_c_txt_status_planned  TYPE C, "   
lv_i_adrnr  TYPE C, "   
lv_c_txt_shipment_type  TYPE C, "   
lv_c_txt_status_registrated  TYPE C, "   
lv_c_txt_status_load_start  TYPE C, "   
lv_c_txt_status_load_end  TYPE C, "   
lv_c_txt_status_processing  TYPE C, "   
lv_c_txt_status_shipm_start  TYPE C, "   
lv_c_txt_status_shipm_end  TYPE C, "   
lv_c_txt_add_info_1  TYPE C, "   
lv_c_txt_add_info_2  TYPE C, "   
lv_c_txt_add_info_3  TYPE C, "   
lv_c_txt_add_info_4  TYPE C, "   
lv_c_txt_leg_det_type  TYPE C, "   
lv_c_txt_carraddr  TYPE C, "   
lv_c_txt_route_stages  TYPE C, "   
lv_c_txt_processing_type  TYPE C, "   
lv_c_txt_process_control  TYPE C, "   
lv_c_txt_service_level  TYPE C, "   
lv_c_txt_shipping_type  TYPE C. "   

  CALL FUNCTION 'SD_SHIPMENT_HEADER_DESCRIPTION'  "NOTRANSL: Füllen der Bezeichnungen zum Transportkopf (dynamischen Teil fül
    EXPORTING
         I_XVTTK = lv_i_xvttk
         I_LANGU = lv_i_langu
         I_ADRNR = lv_i_adrnr
    CHANGING
         C_TXT_DOCUMENT_CAT = lv_c_txt_document_cat
         C_ICON_SHIPPING_TYPE = lv_c_icon_shipping_type
         C_TXT_SHIP_TYP_PREL = lv_c_txt_ship_typ_prel
         C_ICON_SHIP_TYP_PREL = lv_c_icon_ship_typ_prel
         C_TXT_SHIP_TYP_SUBS = lv_c_txt_ship_typ_subs
         C_ICON_SHIP_TYP_SUBS = lv_c_icon_ship_typ_subs
         C_TXT_LEG_INDICATOR = lv_c_txt_leg_indicator
         C_TXT_SHIPPING_COND = lv_c_txt_shipping_cond
         C_TXT_ROUTE = lv_c_txt_route
         C_TXT_CARRIER = lv_c_txt_carrier
         C_TXT_OVERALL_STATUS = lv_c_txt_overall_status
         C_TXT_PLANNING_POINT = lv_c_txt_planning_point
         C_ICON_OVERALL_STATUS = lv_c_icon_overall_status
         C_TXT_FREIGHT_COST_RELEVANCE = lv_c_txt_freight_cost_relevance
         C_TXT_FREIGHT_CALC_STATUS = lv_c_txt_freight_calc_status
         C_TXT_FREIGHT_SETT_STATUS = lv_c_txt_freight_sett_status
         C_TXT_OVRL_FREIGHT_CALC_STATUS = lv_c_txt_ovrl_freight_calc_status
         C_TXT_OVRL_FREIGHT_SETT_STATUS = lv_c_txt_ovrl_freight_sett_status
         C_TXT_SPECIAL_PROCESSING = lv_c_txt_special_processing
         C_TXT_PRICING_PROCEDURE = lv_c_txt_pricing_procedure
         C_ROUTID = lv_c_routid
         C_TXT_STATUS_PLANNED = lv_c_txt_status_planned
         C_TXT_SHIPMENT_TYPE = lv_c_txt_shipment_type
         C_TXT_STATUS_REGISTRATED = lv_c_txt_status_registrated
         C_TXT_STATUS_LOAD_START = lv_c_txt_status_load_start
         C_TXT_STATUS_LOAD_END = lv_c_txt_status_load_end
         C_TXT_STATUS_PROCESSING = lv_c_txt_status_processing
         C_TXT_STATUS_SHIPM_START = lv_c_txt_status_shipm_start
         C_TXT_STATUS_SHIPM_END = lv_c_txt_status_shipm_end
         C_TXT_ADD_INFO_1 = lv_c_txt_add_info_1
         C_TXT_ADD_INFO_2 = lv_c_txt_add_info_2
         C_TXT_ADD_INFO_3 = lv_c_txt_add_info_3
         C_TXT_ADD_INFO_4 = lv_c_txt_add_info_4
         C_TXT_LEG_DET_TYPE = lv_c_txt_leg_det_type
         C_TXT_CARRADDR = lv_c_txt_carraddr
         C_TXT_ROUTE_STAGES = lv_c_txt_route_stages
         C_TXT_PROCESSING_TYPE = lv_c_txt_processing_type
         C_TXT_PROCESS_CONTROL = lv_c_txt_process_control
         C_TXT_SERVICE_LEVEL = lv_c_txt_service_level
         C_TXT_SHIPPING_TYPE = lv_c_txt_shipping_type
. " SD_SHIPMENT_HEADER_DESCRIPTION




ABAP code using 7.40 inline data declarations to call FM SD_SHIPMENT_HEADER_DESCRIPTION

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.

 
 
 
 
 
 
 
 
 
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_i_langu).
DATA(ld_i_langu) = SY-LANGU.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!