SAP SD_SHIPMENT_FCODE_CONTROL Function Module for NOTRANSL: Transportbearbeitung: Prüfung, ob FCODE erlaubt ist









SD_SHIPMENT_FCODE_CONTROL is a standard sd shipment fcode control 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: Transportbearbeitung: Prüfung, ob FCODE erlaubt ist 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 fcode control FM, simply by entering the name SD_SHIPMENT_FCODE_CONTROL into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_SHIPMENT_FCODE_CONTROL 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_FCODE_CONTROL'"NOTRANSL: Transportbearbeitung: Prüfung, ob FCODE erlaubt ist
  EXPORTING
   I_XVTTK =  "
*  I_XVTTS =  "
*  I_XVTTP =  "
   I_FCODE =  "
*  I_FIELDNAME =  "

TABLES
*  I_XVTTK_TAB =  "
*  I_XVTTP_TAB =  "Shipment Item for Logging
*  I_XTRLK_TAB =  "Delivery in Shipment: Header
*  I_XTRLP_TAB =  "Delivery in Shipment: Item
*  I_XVTTS_TAB =  "Stage of Shipment
*  I_XVTSP_TAB =  "Stage of Transport / Item: Logging
*  I_XVBPA_TAB =  "Reference structure for XVBPA/YVBPA

EXCEPTIONS
   NOT_ALLOWED = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV56B_001 Transportation Processing: Field Modification

IMPORTING Parameters details for SD_SHIPMENT_FCODE_CONTROL

I_XVTTK -

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

I_XVTTS -

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

I_XVTTP -

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

I_FCODE -

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

I_FIELDNAME -

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

TABLES Parameters details for SD_SHIPMENT_FCODE_CONTROL

I_XVTTK_TAB -

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

I_XVTTP_TAB - Shipment Item for Logging

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

I_XTRLK_TAB - Delivery in Shipment: Header

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

I_XTRLP_TAB - Delivery in Shipment: Item

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

I_XVTTS_TAB - Stage of Shipment

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

I_XVTSP_TAB - Stage of Transport / Item: Logging

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

I_XVBPA_TAB - Reference structure for XVBPA/YVBPA

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

EXCEPTIONS details

NOT_ALLOWED -

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

Copy and paste ABAP code example for SD_SHIPMENT_FCODE_CONTROL 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, "   
lt_i_xvttk_tab  TYPE STANDARD TABLE OF VTTKVB, "   
lv_not_allowed  TYPE VTTKVB, "   
lv_i_xvtts  TYPE VTTSVB, "   
lt_i_xvttp_tab  TYPE STANDARD TABLE OF VTTPVB, "   
lv_i_xvttp  TYPE VTTPVB, "   
lt_i_xtrlk_tab  TYPE STANDARD TABLE OF VTRLK, "   
lv_i_fcode  TYPE C, "   
lt_i_xtrlp_tab  TYPE STANDARD TABLE OF VTRLP, "   
lv_i_fieldname  TYPE C, "   
lt_i_xvtts_tab  TYPE STANDARD TABLE OF VTTSVB, "   
lt_i_xvtsp_tab  TYPE STANDARD TABLE OF VTSPVB, "   
lt_i_xvbpa_tab  TYPE STANDARD TABLE OF VBPAVB. "   

  CALL FUNCTION 'SD_SHIPMENT_FCODE_CONTROL'  "NOTRANSL: Transportbearbeitung: Prüfung, ob FCODE erlaubt ist
    EXPORTING
         I_XVTTK = lv_i_xvttk
         I_XVTTS = lv_i_xvtts
         I_XVTTP = lv_i_xvttp
         I_FCODE = lv_i_fcode
         I_FIELDNAME = lv_i_fieldname
    TABLES
         I_XVTTK_TAB = lt_i_xvttk_tab
         I_XVTTP_TAB = lt_i_xvttp_tab
         I_XTRLK_TAB = lt_i_xtrlk_tab
         I_XTRLP_TAB = lt_i_xtrlp_tab
         I_XVTTS_TAB = lt_i_xvtts_tab
         I_XVTSP_TAB = lt_i_xvtsp_tab
         I_XVBPA_TAB = lt_i_xvbpa_tab
    EXCEPTIONS
        NOT_ALLOWED = 1
. " SD_SHIPMENT_FCODE_CONTROL




ABAP code using 7.40 inline data declarations to call FM SD_SHIPMENT_FCODE_CONTROL

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!