SAP Function Modules

FAA_READ_NEWGL_LEDGER_SCENARIO SAP Function module







FAA_READ_NEWGL_LEDGER_SCENARIO is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FAA_READ_NEWGL_LEDGER_SCENARIO into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: AA_BAS_CUS_READ
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FAA_READ_NEWGL_LEDGER_SCENARIO - FAA READ NEWGL LEDGER SCENARIO





CALL FUNCTION 'FAA_READ_NEWGL_LEDGER_SCENARIO' "
  EXPORTING
    i_orgunit =                 " bukrs         Company Code
*   i_area =                    " afabe_d       Valuation Area
*   i_scenario_type =           " char1
*   i_buffer_refresh =          " boolean
  IMPORTING
    ed_newgl_active =           " boolean
    ed_glflex_mig_active =      " boolean
    ed_leading_ledger =         " rldnr
    ed_scenario_active =        " boolean
    et_scenarios =              " aacus_t_scenarios
  EXCEPTIONS
    NEWGL_NOT_ACTIVE = 1        "
    WRONG_PARAMETERS = 2        "
    ERROR_READING_ORGUNIT = 3   "
    ERROR_IN_NEWGL_SETUP = 4    "
    .  "  FAA_READ_NEWGL_LEDGER_SCENARIO

ABAP code example for Function Module FAA_READ_NEWGL_LEDGER_SCENARIO





The ABAP code below is a full code listing to execute function module FAA_READ_NEWGL_LEDGER_SCENARIO including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ed_newgl_active  TYPE BOOLEAN ,
ld_ed_glflex_mig_active  TYPE BOOLEAN ,
ld_ed_leading_ledger  TYPE RLDNR ,
ld_ed_scenario_active  TYPE BOOLEAN ,
ld_et_scenarios  TYPE AACUS_T_SCENARIOS .

DATA(ld_i_orgunit) = 'Check type of data required'.
DATA(ld_i_area) = 'Check type of data required'.
DATA(ld_i_scenario_type) = 'Check type of data required'.
DATA(ld_i_buffer_refresh) = 'Check type of data required'. . CALL FUNCTION 'FAA_READ_NEWGL_LEDGER_SCENARIO' EXPORTING i_orgunit = ld_i_orgunit * i_area = ld_i_area * i_scenario_type = ld_i_scenario_type * i_buffer_refresh = ld_i_buffer_refresh IMPORTING ed_newgl_active = ld_ed_newgl_active ed_glflex_mig_active = ld_ed_glflex_mig_active ed_leading_ledger = ld_ed_leading_ledger ed_scenario_active = ld_ed_scenario_active et_scenarios = ld_et_scenarios EXCEPTIONS NEWGL_NOT_ACTIVE = 1 WRONG_PARAMETERS = 2 ERROR_READING_ORGUNIT = 3 ERROR_IN_NEWGL_SETUP = 4 . " FAA_READ_NEWGL_LEDGER_SCENARIO
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_ed_newgl_active  TYPE BOOLEAN ,
ld_i_orgunit  TYPE BUKRS ,
ld_ed_glflex_mig_active  TYPE BOOLEAN ,
ld_i_area  TYPE AFABE_D ,
ld_ed_leading_ledger  TYPE RLDNR ,
ld_i_scenario_type  TYPE CHAR1 ,
ld_ed_scenario_active  TYPE BOOLEAN ,
ld_i_buffer_refresh  TYPE BOOLEAN ,
ld_et_scenarios  TYPE AACUS_T_SCENARIOS .

ld_i_orgunit = 'Check type of data required'.
ld_i_area = 'Check type of data required'.
ld_i_scenario_type = 'Check type of data required'.
ld_i_buffer_refresh = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FAA_READ_NEWGL_LEDGER_SCENARIO or its description.