SAP PLM_AUD_DS_SOFTSWITCH Function Module for
PLM_AUD_DS_SOFTSWITCH is a standard plm aud ds softswitch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 plm aud ds softswitch FM, simply by entering the name PLM_AUD_DS_SOFTSWITCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: PLM_AUDIT_DS
Program Name: SAPLPLM_AUDIT_DS
Main Program: SAPLPLM_AUDIT_DS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PLM_AUD_DS_SOFTSWITCH 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 'PLM_AUD_DS_SOFTSWITCH'".
EXPORTING
* IV_ASSESSMENT_CAT = "
IMPORTING
EV_SETTINGS_AVAILABLE = "
IMPORTING Parameters details for PLM_AUD_DS_SOFTSWITCH
IV_ASSESSMENT_CAT -
Data type: PLMT_TV_ASSESSMENT_CATOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PLM_AUD_DS_SOFTSWITCH
EV_SETTINGS_AVAILABLE -
Data type: XFELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PLM_AUD_DS_SOFTSWITCH 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_iv_assessment_cat | TYPE PLMT_TV_ASSESSMENT_CAT, " | |||
| lv_ev_settings_available | TYPE XFELD. " |
|   CALL FUNCTION 'PLM_AUD_DS_SOFTSWITCH' " |
| EXPORTING | ||
| IV_ASSESSMENT_CAT | = lv_iv_assessment_cat | |
| IMPORTING | ||
| EV_SETTINGS_AVAILABLE | = lv_ev_settings_available | |
| . " PLM_AUD_DS_SOFTSWITCH | ||
ABAP code using 7.40 inline data declarations to call FM PLM_AUD_DS_SOFTSWITCH
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