SAP OPEN_FI_PERFORM_01000820_E Function Module for NOTRANSL: Informationen zum CRM-Szenario









OPEN_FI_PERFORM_01000820_E is a standard open fi perform 01000820 e 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: Informationen zum CRM-Szenario 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 open fi perform 01000820 e FM, simply by entering the name OPEN_FI_PERFORM_01000820_E into the relevant SAP transaction such as SE37 or SE38.

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



Function OPEN_FI_PERFORM_01000820_E 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 'OPEN_FI_PERFORM_01000820_E'"NOTRANSL: Informationen zum CRM-Szenario
EXPORTING
IS_VBAK = "Sales Document Header
* IV_READ_FROM_DB = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION

IMPORTING
EV_SWITCH_OFF_SCHEDULING = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EV_SUPRESS_REQUIREMENTS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EV_LOGSYS_PREDECESSOR_REQ = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EV_OWN_LOGICAL_SYSTEM = "Separate Logical System
EV_SCENERIO_REQ_DLV = "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
OWN_LOGSYS_NOT_FOUND = 1 SD_ORDER_NOT_FOUND = 2 ERROR_OCCURED = 3
.



IMPORTING Parameters details for OPEN_FI_PERFORM_01000820_E

IS_VBAK - Sales Document Header

Data type: VBAK
Optional: No
Call by Reference: No ( called with pass by value option)

IV_READ_FROM_DB - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for OPEN_FI_PERFORM_01000820_E

EV_SWITCH_OFF_SCHEDULING - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EV_SUPRESS_REQUIREMENTS - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EV_LOGSYS_PREDECESSOR_REQ - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: T000-LOGSYS
Optional: No
Call by Reference: Yes

EV_OWN_LOGICAL_SYSTEM - Separate Logical System

Data type: T000-LOGSYS
Optional: No
Call by Reference: Yes

EV_SCENERIO_REQ_DLV - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXCEPTIONS details

OWN_LOGSYS_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

SD_ORDER_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ERROR_OCCURED - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OPEN_FI_PERFORM_01000820_E 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_is_vbak  TYPE VBAK, "   
lv_own_logsys_not_found  TYPE VBAK, "   
lv_ev_switch_off_scheduling  TYPE C, "   
lv_iv_read_from_db  TYPE C, "   SPACE
lv_sd_order_not_found  TYPE C, "   
lv_ev_supress_requirements  TYPE C, "   
lv_error_occured  TYPE C, "   
lv_ev_logsys_predecessor_req  TYPE T000-LOGSYS, "   
lv_ev_own_logical_system  TYPE T000-LOGSYS, "   
lv_ev_scenerio_req_dlv  TYPE C. "   

  CALL FUNCTION 'OPEN_FI_PERFORM_01000820_E'  "NOTRANSL: Informationen zum CRM-Szenario
    EXPORTING
         IS_VBAK = lv_is_vbak
         IV_READ_FROM_DB = lv_iv_read_from_db
    IMPORTING
         EV_SWITCH_OFF_SCHEDULING = lv_ev_switch_off_scheduling
         EV_SUPRESS_REQUIREMENTS = lv_ev_supress_requirements
         EV_LOGSYS_PREDECESSOR_REQ = lv_ev_logsys_predecessor_req
         EV_OWN_LOGICAL_SYSTEM = lv_ev_own_logical_system
         EV_SCENERIO_REQ_DLV = lv_ev_scenerio_req_dlv
    EXCEPTIONS
        OWN_LOGSYS_NOT_FOUND = 1
        SD_ORDER_NOT_FOUND = 2
        ERROR_OCCURED = 3
. " OPEN_FI_PERFORM_01000820_E




ABAP code using 7.40 inline data declarations to call FM OPEN_FI_PERFORM_01000820_E

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.

 
 
 
DATA(ld_iv_read_from_db) = ' '.
 
 
 
 
"SELECT single LOGSYS FROM T000 INTO @DATA(ld_ev_logsys_predecessor_req).
 
"SELECT single LOGSYS FROM T000 INTO @DATA(ld_ev_own_logical_system).
 
 


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!