SAP IDOC_INPUT_SHIPMENT_CHANGE Function Module for NOTRANSL: IDoc -> BAPI: IDOC_INPUT_SHIPMENT_CHANGE









IDOC_INPUT_SHIPMENT_CHANGE is a standard idoc input shipment change 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: IDoc -> BAPI: IDOC_INPUT_SHIPMENT_CHANGE 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 idoc input shipment change FM, simply by entering the name IDOC_INPUT_SHIPMENT_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function IDOC_INPUT_SHIPMENT_CHANGE 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 'IDOC_INPUT_SHIPMENT_CHANGE'"NOTRANSL: IDoc -> BAPI: IDOC_INPUT_SHIPMENT_CHANGE
  EXPORTING
   INPUT_METHOD =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   MASS_PROCESSING =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

 IMPORTING
   WORKFLOW_RESULT =  "Value of Method
   APPLICATION_VARIABLE =  "Variable to be used by application as required
   IN_UPDATE_TASK =  "Flag: Application has triggered update task
   CALL_TRANSACTION_DONE =  "Flag: Application has actually performed call transaction

TABLES
   IDOC_CONTRL =  "Control Record (IDoc)
   IDOC_DATA =  "Data Record (IDoc)
   IDOC_STATUS =  "ALE IDoc Status (Subset of All IDoc Status Fields)
   RETURN_VARIABLES =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   SERIALIZATION_INFO =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
   WRONG_FUNCTION_CALLED = 1
.



IMPORTING Parameters details for IDOC_INPUT_SHIPMENT_CHANGE

INPUT_METHOD - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

MASS_PROCESSING - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXPORTING Parameters details for IDOC_INPUT_SHIPMENT_CHANGE

WORKFLOW_RESULT - Value of Method

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

APPLICATION_VARIABLE - Variable to be used by application as required

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

IN_UPDATE_TASK - Flag: Application has triggered update task

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

CALL_TRANSACTION_DONE - Flag: Application has actually performed call transaction

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

TABLES Parameters details for IDOC_INPUT_SHIPMENT_CHANGE

IDOC_CONTRL - Control Record (IDoc)

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

IDOC_DATA - Data Record (IDoc)

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

IDOC_STATUS - ALE IDoc Status (Subset of All IDoc Status Fields)

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

RETURN_VARIABLES - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

SERIALIZATION_INFO - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXCEPTIONS details

WRONG_FUNCTION_CALLED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IDOC_INPUT_SHIPMENT_CHANGE 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_idoc_contrl  TYPE STANDARD TABLE OF EDIDC, "   
lv_input_method  TYPE BDWFAP_PAR-INPUTMETHD, "   
lv_workflow_result  TYPE BDWF_PARAM-RESULT, "   
lv_wrong_function_called  TYPE BDWF_PARAM, "   
lt_idoc_data  TYPE STANDARD TABLE OF EDIDD, "   
lv_mass_processing  TYPE BDWFAP_PAR-MASS_PROC, "   
lv_application_variable  TYPE BDWF_PARAM-APPL_VAR, "   
lt_idoc_status  TYPE STANDARD TABLE OF BDIDOCSTAT, "   
lv_in_update_task  TYPE BDWFAP_PAR-UPDATETASK, "   
lt_return_variables  TYPE STANDARD TABLE OF BDWFRETVAR, "   
lv_call_transaction_done  TYPE BDWFAP_PAR-CALLTRANS, "   
lt_serialization_info  TYPE STANDARD TABLE OF BDI_SER. "   

  CALL FUNCTION 'IDOC_INPUT_SHIPMENT_CHANGE'  "NOTRANSL: IDoc -> BAPI: IDOC_INPUT_SHIPMENT_CHANGE
    EXPORTING
         INPUT_METHOD = lv_input_method
         MASS_PROCESSING = lv_mass_processing
    IMPORTING
         WORKFLOW_RESULT = lv_workflow_result
         APPLICATION_VARIABLE = lv_application_variable
         IN_UPDATE_TASK = lv_in_update_task
         CALL_TRANSACTION_DONE = lv_call_transaction_done
    TABLES
         IDOC_CONTRL = lt_idoc_contrl
         IDOC_DATA = lt_idoc_data
         IDOC_STATUS = lt_idoc_status
         RETURN_VARIABLES = lt_return_variables
         SERIALIZATION_INFO = lt_serialization_info
    EXCEPTIONS
        WRONG_FUNCTION_CALLED = 1
. " IDOC_INPUT_SHIPMENT_CHANGE




ABAP code using 7.40 inline data declarations to call FM IDOC_INPUT_SHIPMENT_CHANGE

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 INPUTMETHD FROM BDWFAP_PAR INTO @DATA(ld_input_method).
 
"SELECT single RESULT FROM BDWF_PARAM INTO @DATA(ld_workflow_result).
 
 
 
"SELECT single MASS_PROC FROM BDWFAP_PAR INTO @DATA(ld_mass_processing).
 
"SELECT single APPL_VAR FROM BDWF_PARAM INTO @DATA(ld_application_variable).
 
 
"SELECT single UPDATETASK FROM BDWFAP_PAR INTO @DATA(ld_in_update_task).
 
 
"SELECT single CALLTRANS FROM BDWFAP_PAR INTO @DATA(ld_call_transaction_done).
 
 


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!