SAP SD_SHIPMENT_STATUS_REGISTRATED Function Module for NOTRANSL: Funktionen bei Setzen des Status 'Registriert' im Transportkopf
SD_SHIPMENT_STATUS_REGISTRATED is a standard sd shipment status registrated 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: Funktionen bei Setzen des Status 'Registriert' im Transportkopf 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 status registrated FM, simply by entering the name SD_SHIPMENT_STATUS_REGISTRATED into the relevant SAP transaction such as SE37 or SE38.
Function Group: V56F
Program Name: SAPLV56F
Main Program: SAPLV56F
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SD_SHIPMENT_STATUS_REGISTRATED 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_STATUS_REGISTRATED'"NOTRANSL: Funktionen bei Setzen des Status 'Registriert' im Transportkopf.
EXPORTING
I_TVTK = "Transport Type
I_NEW_STATUS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_NEW_STATUS_DATE = "New Date
* I_NEW_STATUS_TIME = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* OPT_DIALOG = 'X' "DE-EN-LANG-SWITCH-NO-TRANSLATION
CHANGING
C_XVTTK_WA = "Shipment header
TABLES
C_XVTTK = "Shipment header
C_YVBPA = "Partner
C_XVBADR = "Addresses
C_YVBADR = "Addresses
I_XTRLK = "DE-EN-LANG-SWITCH-NO-TRANSLATION
I_XTRLP = "
C_YVTTK = "
C_XVTTP = "DE-EN-LANG-SWITCH-NO-TRANSLATION
C_YVTTP = "DE-EN-LANG-SWITCH-NO-TRANSLATION
C_XVTTS = "Stages
C_YVTTS = "Stages
C_XVTSP = "DE-EN-LANG-SWITCH-NO-TRANSLATION
C_YVTSP = "DE-EN-LANG-SWITCH-NO-TRANSLATION
C_XVBPA = "Partner
EXCEPTIONS
WRONG_SHIPMENT_TYPE = 1 TIME_INVALID = 2 DATE_INVALID = 3 FUNCTION_FAILED = 4
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_SAPLV56F_010 Shipment Processing: Copying Delivery Data to Shipment Document
EXIT_SAPLV56F_011 Shipment Processing: Activities for Setting a Status, Time 1
EXIT_SAPLV56F_012 Shipment Processing: Activities for Setting a Status, Time 2
IMPORTING Parameters details for SD_SHIPMENT_STATUS_REGISTRATED
I_TVTK - Transport Type
Data type: TVTKOptional: No
Call by Reference: No ( called with pass by value option)
I_NEW_STATUS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTTK-STREGOptional: No
Call by Reference: No ( called with pass by value option)
I_NEW_STATUS_DATE - New Date
Data type: VTTK-DAREGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NEW_STATUS_TIME - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTTK-UAREGOptional: Yes
Call by Reference: No ( called with pass by value option)
OPT_DIALOG - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: RV56A-SELKZDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SD_SHIPMENT_STATUS_REGISTRATED
C_XVTTK_WA - Shipment header
Data type: VTTKVBOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SD_SHIPMENT_STATUS_REGISTRATED
C_XVTTK - Shipment header
Data type: VTTKVBOptional: No
Call by Reference: No ( called with pass by value option)
C_YVBPA - Partner
Data type: VBPAVBOptional: No
Call by Reference: No ( called with pass by value option)
C_XVBADR - Addresses
Data type: SADRVBOptional: No
Call by Reference: No ( called with pass by value option)
C_YVBADR - Addresses
Data type: SADRVBOptional: No
Call by Reference: No ( called with pass by value option)
I_XTRLK - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTRLKOptional: No
Call by Reference: No ( called with pass by value option)
I_XTRLP -
Data type: VTRLPOptional: No
Call by Reference: No ( called with pass by value option)
C_YVTTK -
Data type: VTTKVBOptional: No
Call by Reference: No ( called with pass by value option)
C_XVTTP - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTTPVBOptional: No
Call by Reference: No ( called with pass by value option)
C_YVTTP - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTTPVBOptional: No
Call by Reference: No ( called with pass by value option)
C_XVTTS - Stages
Data type: VTTSVBOptional: No
Call by Reference: No ( called with pass by value option)
C_YVTTS - Stages
Data type: VTTSVBOptional: No
Call by Reference: No ( called with pass by value option)
C_XVTSP - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTSPVBOptional: No
Call by Reference: No ( called with pass by value option)
C_YVTSP - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTSPVBOptional: No
Call by Reference: No ( called with pass by value option)
C_XVBPA - Partner
Data type: VBPAVBOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_SHIPMENT_TYPE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TIME_INVALID - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATE_INVALID - Invalid date
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FUNCTION_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_SHIPMENT_STATUS_REGISTRATED 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_tvtk | TYPE TVTK, " | |||
lt_c_xvttk | TYPE STANDARD TABLE OF VTTKVB, " | |||
lv_c_xvttk_wa | TYPE VTTKVB, " | |||
lv_wrong_shipment_type | TYPE VTTKVB, " | |||
lt_c_yvbpa | TYPE STANDARD TABLE OF VBPAVB, " | |||
lt_c_xvbadr | TYPE STANDARD TABLE OF SADRVB, " | |||
lt_c_yvbadr | TYPE STANDARD TABLE OF SADRVB, " | |||
lt_i_xtrlk | TYPE STANDARD TABLE OF VTRLK, " | |||
lt_i_xtrlp | TYPE STANDARD TABLE OF VTRLP, " | |||
lt_c_yvttk | TYPE STANDARD TABLE OF VTTKVB, " | |||
lv_i_new_status | TYPE VTTK-STREG, " | |||
lv_time_invalid | TYPE VTTK, " | |||
lt_c_xvttp | TYPE STANDARD TABLE OF VTTPVB, " | |||
lv_date_invalid | TYPE VTTPVB, " | |||
lv_i_new_status_date | TYPE VTTK-DAREG, " | |||
lt_c_yvttp | TYPE STANDARD TABLE OF VTTPVB, " | |||
lv_function_failed | TYPE VTTPVB, " | |||
lv_i_new_status_time | TYPE VTTK-UAREG, " | |||
lt_c_xvtts | TYPE STANDARD TABLE OF VTTSVB, " | |||
lv_opt_dialog | TYPE RV56A-SELKZ, " 'X' | |||
lt_c_yvtts | TYPE STANDARD TABLE OF VTTSVB, " | |||
lt_c_xvtsp | TYPE STANDARD TABLE OF VTSPVB, " | |||
lt_c_yvtsp | TYPE STANDARD TABLE OF VTSPVB, " | |||
lt_c_xvbpa | TYPE STANDARD TABLE OF VBPAVB. " |
  CALL FUNCTION 'SD_SHIPMENT_STATUS_REGISTRATED' "NOTRANSL: Funktionen bei Setzen des Status 'Registriert' im Transportkopf |
EXPORTING | ||
I_TVTK | = lv_i_tvtk | |
I_NEW_STATUS | = lv_i_new_status | |
I_NEW_STATUS_DATE | = lv_i_new_status_date | |
I_NEW_STATUS_TIME | = lv_i_new_status_time | |
OPT_DIALOG | = lv_opt_dialog | |
CHANGING | ||
C_XVTTK_WA | = lv_c_xvttk_wa | |
TABLES | ||
C_XVTTK | = lt_c_xvttk | |
C_YVBPA | = lt_c_yvbpa | |
C_XVBADR | = lt_c_xvbadr | |
C_YVBADR | = lt_c_yvbadr | |
I_XTRLK | = lt_i_xtrlk | |
I_XTRLP | = lt_i_xtrlp | |
C_YVTTK | = lt_c_yvttk | |
C_XVTTP | = lt_c_xvttp | |
C_YVTTP | = lt_c_yvttp | |
C_XVTTS | = lt_c_xvtts | |
C_YVTTS | = lt_c_yvtts | |
C_XVTSP | = lt_c_xvtsp | |
C_YVTSP | = lt_c_yvtsp | |
C_XVBPA | = lt_c_xvbpa | |
EXCEPTIONS | ||
WRONG_SHIPMENT_TYPE = 1 | ||
TIME_INVALID = 2 | ||
DATE_INVALID = 3 | ||
FUNCTION_FAILED = 4 | ||
. " SD_SHIPMENT_STATUS_REGISTRATED |
ABAP code using 7.40 inline data declarations to call FM SD_SHIPMENT_STATUS_REGISTRATED
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 STREG FROM VTTK INTO @DATA(ld_i_new_status). | ||||
"SELECT single DAREG FROM VTTK INTO @DATA(ld_i_new_status_date). | ||||
"SELECT single UAREG FROM VTTK INTO @DATA(ld_i_new_status_time). | ||||
"SELECT single SELKZ FROM RV56A INTO @DATA(ld_opt_dialog). | ||||
DATA(ld_opt_dialog) | = 'X'. | |||
Search for further information about these or an SAP related objects