SAP CS_BOM_CALL_DIALOG_RFC Function Module for NOTRANSL: Aufruf Stücklistendialog als Remote Funktion Call

Search SAP Function Modules

CS_BOM_CALL_DIALOG_RFC is a standard cs bom call dialog rfc 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: Aufruf Stücklistendialog als Remote Funktion Call 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 cs bom call dialog rfc FM, simply by entering the name CS_BOM_CALL_DIALOG_RFC into the relevant SAP transaction such as SE37 or SE38.

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

Function CS_BOM_CALL_DIALOG_RFC 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 'CS_BOM_CALL_DIALOG_RFC'"NOTRANSL: Aufruf Stücklistendialog als Remote Funktion Call
  EXPORTING
   BOM_HEADER =  "BOM header table
*  OKCODE = ' ' "OKCODE, after data transfer
*  ECSIN =  "BOM interface
*  FLG_NO_WARNING = ' ' "

 IMPORTING
   FLG_UPD =  "
   ABICSK =  "

TABLES
   ITEM =  "Table of item data

EXCEPTIONS
   CMODE_ERROR = 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_SAPLCSDI_001 PCSD0001: BOM - User exit
EXIT_SAPLCSDI_002 PCSD0002: BOM Item - Customer Fields to Customer Program
EXIT_SAPLCSDI_003 PCSD0002: BOM item - Customer Field to SAP Program
EXIT_SAPLCSDI_004 PCSD0003: BOM header - Customer Field to Customer Program
EXIT_SAPLCSDI_005 PCSD0003: BOM header - Customer Field to SAP Program
EXIT_SAPLCSDI_006 PCSD0005: Additional Component Checks for Material Items
EXIT_SAPLCSDI_007 PCSD0007: Check STKOB after change

IMPORTING Parameters details for CS_BOM_CALL_DIALOG_RFC

BOM_HEADER - BOM header table

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

OKCODE - OKCODE, after data transfer

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

ECSIN - BOM interface

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

FLG_NO_WARNING -

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CS_BOM_CALL_DIALOG_RFC

FLG_UPD -

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

ABICSK -

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

TABLES Parameters details for CS_BOM_CALL_DIALOG_RFC

ITEM - Table of item data

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

EXCEPTIONS details

CMODE_ERROR - ECSIN-CMODE could not be interpreted

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

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

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