SAP DMC_DXWB_INTEGRATION_SP Function Module for Sender-/Empfaengertyp vom DXWB einstellen

Search SAP Function Modules

DMC_DXWB_INTEGRATION_SP is a standard dmc dxwb integration sp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sender-/Empfaengertyp vom DXWB einstellen 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 dmc dxwb integration sp FM, simply by entering the name DMC_DXWB_INTEGRATION_SP into the relevant SAP transaction such as SE37 or SE38.

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

Function DMC_DXWB_INTEGRATION_SP 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 'DMC_DXWB_INTEGRATION_SP'"Sender-/Empfaengertyp vom DXWB einstellen
  EXPORTING
   IM_CONV_OBJ =  "Conversion object
*  IM_RCVPRN =  "Partner number of receiver
   IM_IDOCTYP =  "Basic Type
*  IM_CIMTYP =  "Enhancement
*  IM_RELEASED =  "Released in
*  IM_VERSION =  "Version of IDoc record types
*  IM_MESSAGETYP =  "Message type
*  IM_SNDPOR =  "Sender port (SAP System, external subsystem)
*  IM_SNDPRN =  "Partner number of sender
*  IM_RCVPOR =  "Receiver port

EXCEPTIONS
   SENDERTYPE_NOT_SET = 1    RECEIVERTYPE_NOT_SET = 2 

.

IMPORTING Parameters details for DMC_DXWB_INTEGRATION_SP

IM_CONV_OBJ - Conversion object

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

IM_RCVPRN - Partner number of receiver

Data type: EDI_DC40-RCVPRN
Optional: Yes
Call by Reference: Yes

IM_IDOCTYP - Basic Type

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

IM_CIMTYP - Enhancement

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

IM_RELEASED - Released in

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

IM_VERSION - Version of IDoc record types

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

IM_MESSAGETYP - Message type

Data type: EDI_DC40-MESTYP
Optional: Yes
Call by Reference: Yes

IM_SNDPOR - Sender port (SAP System, external subsystem)

Data type: EDI_DC40-SNDPOR
Optional: Yes
Call by Reference: Yes

IM_SNDPRN - Partner number of sender

Data type: EDI_DC40-SNDPRN
Optional: Yes
Call by Reference: Yes

IM_RCVPOR - Receiver port

Data type: EDI_DC40-RCVPOR
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

SENDERTYPE_NOT_SET - Sender type is not set.

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

RECEIVERTYPE_NOT_SET - Receiver type is not set.

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

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

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