SAP DAUER_SAP_TO_PC Function Module for
DAUER_SAP_TO_PC is a standard dauer sap to pc 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 dauer sap to pc FM, simply by entering the name DAUER_SAP_TO_PC into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNISN
Program Name: SAPLCNISN
Main Program: SAPLCNISN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DAUER_SAP_TO_PC 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 'DAUER_SAP_TO_PC'".
EXPORTING
SAPDAUER = "
SAPEINHEIT = "Unit for the time interval between relationships
CHANGING
PCDAUER = "
PCEINHEIT = "
IMPORTING Parameters details for DAUER_SAP_TO_PC
SAPDAUER -
Data type: POptional: No
Call by Reference: Yes
SAPEINHEIT - Unit for the time interval between relationships
Data type: AFABR-ZEINHOptional: No
Call by Reference: Yes
CHANGING Parameters details for DAUER_SAP_TO_PC
PCDAUER -
Data type: COptional: No
Call by Reference: Yes
PCEINHEIT -
Data type: COptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DAUER_SAP_TO_PC 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_pcdauer | TYPE C, " | |||
| lv_sapdauer | TYPE P, " | |||
| lv_pceinheit | TYPE C, " | |||
| lv_sapeinheit | TYPE AFABR-ZEINH. " |
|   CALL FUNCTION 'DAUER_SAP_TO_PC' " |
| EXPORTING | ||
| SAPDAUER | = lv_sapdauer | |
| SAPEINHEIT | = lv_sapeinheit | |
| CHANGING | ||
| PCDAUER | = lv_pcdauer | |
| PCEINHEIT | = lv_pceinheit | |
| . " DAUER_SAP_TO_PC | ||
ABAP code using 7.40 inline data declarations to call FM DAUER_SAP_TO_PC
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 ZEINH FROM AFABR INTO @DATA(ld_sapeinheit). | ||||
Search for further information about these or an SAP related objects