SAP CUAS_GET_CONFIG_FROM_IBARCHIVE Function Module for Read Confign Data from IBase Archive









CUAS_GET_CONFIG_FROM_IBARCHIVE is a standard cuas get config from ibarchive SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Confign Data from IBase Archive 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 cuas get config from ibarchive FM, simply by entering the name CUAS_GET_CONFIG_FROM_IBARCHIVE into the relevant SAP transaction such as SE37 or SE38.

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



Function CUAS_GET_CONFIG_FROM_IBARCHIVE 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 'CUAS_GET_CONFIG_FROM_IBARCHIVE'"Read Confign Data from IBase Archive
  EXPORTING
   INSTANCE =  "IB: Component (instance)
   ARCHIVE_HANDLE =  "Internal Tables, Current Row Index
*  BUSINESS_OBJECT =  "Business Object
*  DATE =  "Date and Time, Current (Application Server) Date
*  SHOW_MULTILEVEL_CONF = ' ' "Indicator
*  INVALID_POSSIBLE = ' ' "Indicator

EXCEPTIONS
   INTERNAL_ERROR = 1    INVALID_INSTANCE = 2    INVALID_INPUT = 3
.



IMPORTING Parameters details for CUAS_GET_CONFIG_FROM_IBARCHIVE

INSTANCE - IB: Component (instance)

Data type: IBINOWN-INSTANCE
Optional: No
Call by Reference: Yes

ARCHIVE_HANDLE - Internal Tables, Current Row Index

Data type: SY-TABIX
Optional: No
Call by Reference: Yes

BUSINESS_OBJECT - Business Object

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

DATE - Date and Time, Current (Application Server) Date

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

SHOW_MULTILEVEL_CONF - Indicator

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

INVALID_POSSIBLE - Indicator

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

EXCEPTIONS details

INTERNAL_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INVALID_INSTANCE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INVALID_INPUT - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CUAS_GET_CONFIG_FROM_IBARCHIVE 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_instance  TYPE IBINOWN-INSTANCE, "   
lv_internal_error  TYPE IBINOWN, "   
lv_archive_handle  TYPE SY-TABIX, "   
lv_invalid_instance  TYPE SY, "   
lv_invalid_input  TYPE SY, "   
lv_business_object  TYPE IBXX_BUSINESS_OBJECT, "   
lv_date  TYPE SY-DATUM, "   
lv_show_multilevel_conf  TYPE FLAG_X, "   SPACE
lv_invalid_possible  TYPE FLAG_X. "   SPACE

  CALL FUNCTION 'CUAS_GET_CONFIG_FROM_IBARCHIVE'  "Read Confign Data from IBase Archive
    EXPORTING
         INSTANCE = lv_instance
         ARCHIVE_HANDLE = lv_archive_handle
         BUSINESS_OBJECT = lv_business_object
         DATE = lv_date
         SHOW_MULTILEVEL_CONF = lv_show_multilevel_conf
         INVALID_POSSIBLE = lv_invalid_possible
    EXCEPTIONS
        INTERNAL_ERROR = 1
        INVALID_INSTANCE = 2
        INVALID_INPUT = 3
. " CUAS_GET_CONFIG_FROM_IBARCHIVE




ABAP code using 7.40 inline data declarations to call FM CUAS_GET_CONFIG_FROM_IBARCHIVE

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 INSTANCE FROM IBINOWN INTO @DATA(ld_instance).
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_archive_handle).
 
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_date).
 
DATA(ld_show_multilevel_conf) = ' '.
 
DATA(ld_invalid_possible) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!