SAP SD_REPAIRORDER_NODIALOG Function Module for NOTRANSL: Reparaturabwicklung: Hintergundverarbeitung

Search SAP Function Modules

SD_REPAIRORDER_NODIALOG is a standard sd repairorder nodialog 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: Reparaturabwicklung: Hintergundverarbeitung 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 repairorder nodialog FM, simply by entering the name SD_REPAIRORDER_NODIALOG into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_REPAIRORDER_NODIALOG 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_REPAIRORDER_NODIALOG'"NOTRANSL: Reparaturabwicklung: Hintergundverarbeitung
  EXPORTING
   I_CALL_ACTIVITY =  "
   I_STAGE =  "Repair procedure: Stage

 IMPORTING
   E_DATALOSS =  "Name of the dialog type

CHANGING
   C_HEADKOM =  "Repairs Processing: Header Communication Structure

TABLES
   T_ITEMKOM =  "Repairs Processing: Communication Structure for Items
   T_REPAKOM =  "Communic. Structure for Confirming Inspection Lot/SM Order
   T_SERIKOM =  "Repairs Processing: Communication Structure for Serial Nos.

EXCEPTIONS
   MANUALLY_ACTION = 1    NO_PROPOSAL = 2 

.

IMPORTING Parameters details for SD_REPAIRORDER_NODIALOG

I_CALL_ACTIVITY -

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

I_STAGE - Repair procedure: Stage

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

EXPORTING Parameters details for SD_REPAIRORDER_NODIALOG

E_DATALOSS - Name of the dialog type

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

CHANGING Parameters details for SD_REPAIRORDER_NODIALOG

C_HEADKOM - Repairs Processing: Header Communication Structure

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

TABLES Parameters details for SD_REPAIRORDER_NODIALOG

T_ITEMKOM - Repairs Processing: Communication Structure for Items

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

T_REPAKOM - Communic. Structure for Confirming Inspection Lot/SM Order

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

T_SERIKOM - Repairs Processing: Communication Structure for Serial Nos.

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

EXCEPTIONS details

MANUALLY_ACTION -

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

NO_PROPOSAL -

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

Copy and paste ABAP code example for SD_REPAIRORDER_NODIALOG 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.

ABAP code using 7.40 inline data declarations to call FM SD_REPAIRORDER_NODIALOG

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