SAP CACS_PR_UI_0100_GET_DATA Function Module for NOTRANSL: Daten für Subscreen 0100 holen

Search SAP Function Modules

CACS_PR_UI_0100_GET_DATA is a standard cacs pr ui 0100 get data 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: Daten für Subscreen 0100 holen 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 cacs pr ui 0100 get data FM, simply by entering the name CACS_PR_UI_0100_GET_DATA into the relevant SAP transaction such as SE37 or SE38.

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

Function CACS_PR_UI_0100_GET_DATA 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 'CACS_PR_UI_0100_GET_DATA'"NOTRANSL: Daten für Subscreen 0100 holen
 IMPORTING
   ED_BUSI_DATE =  "Effective Date
   ED_BUSI_TIME =  "
   ED_TECH_DATE =  "Technical Date
   ED_TECH_TIME =  "
   ED_BUSI_TSTMP =  "Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
   ED_TECH_TSTMP =  "Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)
   EB_BUSI_FLG =  "
   EB_TECH_FLG =  "

EXCEPTIONS
   ERROR_CONVERTING_UI_DATA = 1 

.

EXPORTING Parameters details for CACS_PR_UI_0100_GET_DATA

ED_BUSI_DATE - Effective Date

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

ED_BUSI_TIME -

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

ED_TECH_DATE - Technical Date

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

ED_TECH_TIME -

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

ED_BUSI_TSTMP - Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)

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

ED_TECH_TSTMP - Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)

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

EB_BUSI_FLG -

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

EB_TECH_FLG -

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

EXCEPTIONS details

ERROR_CONVERTING_UI_DATA -

Data type:
Optional: No
Call by Reference: Yes

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

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