SAP PFO_RFC_IMPORT Function Module for NOTRANSL: Generischer Import von Daten für die BZO
PFO_RFC_IMPORT is a standard pfo rfc import 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: Generischer Import von Daten für die BZO 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 pfo rfc import FM, simply by entering the name PFO_RFC_IMPORT into the relevant SAP transaction such as SE37 or SE38.
Function Group: PFO_RFC_INTERFACE
Program Name: SAPLPFO_RFC_INTERFACE
Main Program: SAPLPFO_RFC_INTERFACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function PFO_RFC_IMPORT 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 'PFO_RFC_IMPORT'"NOTRANSL: Generischer Import von Daten für die BZO.
EXPORTING
* ID_UPDATE_TASK = "
* ID_MASS_PROC = "Mass Processing
* ID_SIM = "Simulation?
CHANGING
* CD_LOGHANDLE = "Application Log: Log Handle
TABLES
IT_IMPORTDATA = "Import Data
CT_OK = "Processed Successfully
CT_NOK = "
EXCEPTIONS
ASSIGN_ERROR = 1 LOG_ERROR = 2 DB_ERROR = 3 ENQUEUE_ERROR = 4 ARCHIVE_ACTIVE = 5
IMPORTING Parameters details for PFO_RFC_IMPORT
ID_UPDATE_TASK -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_MASS_PROC - Mass Processing
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_SIM - Simulation?
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for PFO_RFC_IMPORT
CD_LOGHANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PFO_RFC_IMPORT
IT_IMPORTDATA - Import Data
Data type: PFO_TI_RFC_IMPORT_STRUCTUREOptional: No
Call by Reference: Yes
CT_OK - Processed Successfully
Data type: PFO_TI_RFC_IMPORT_STRUCTUREOptional: No
Call by Reference: Yes
CT_NOK -
Data type: PFO_TI_RFC_IMPORT_STRUCTUREOptional: No
Call by Reference: Yes
EXCEPTIONS details
ASSIGN_ERROR -
Data type:Optional: No
Call by Reference: Yes
LOG_ERROR - Error in log
Data type:Optional: No
Call by Reference: Yes
DB_ERROR -
Data type:Optional: No
Call by Reference: Yes
ENQUEUE_ERROR - Error in lock management
Data type:Optional: No
Call by Reference: Yes
ARCHIVE_ACTIVE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PFO_RFC_IMPORT 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_assign_error | TYPE STRING, " | |||
| lv_cd_loghandle | TYPE BALLOGHNDL, " | |||
| lt_it_importdata | TYPE STANDARD TABLE OF PFO_TI_RFC_IMPORT_STRUCTURE, " | |||
| lv_id_update_task | TYPE FLAG, " | |||
| lt_ct_ok | TYPE STANDARD TABLE OF PFO_TI_RFC_IMPORT_STRUCTURE, " | |||
| lv_log_error | TYPE PFO_TI_RFC_IMPORT_STRUCTURE, " | |||
| lv_id_mass_proc | TYPE FLAG, " | |||
| lt_ct_nok | TYPE STANDARD TABLE OF PFO_TI_RFC_IMPORT_STRUCTURE, " | |||
| lv_id_sim | TYPE FLAG, " | |||
| lv_db_error | TYPE FLAG, " | |||
| lv_enqueue_error | TYPE FLAG, " | |||
| lv_archive_active | TYPE FLAG. " |
|   CALL FUNCTION 'PFO_RFC_IMPORT' "NOTRANSL: Generischer Import von Daten für die BZO |
| EXPORTING | ||
| ID_UPDATE_TASK | = lv_id_update_task | |
| ID_MASS_PROC | = lv_id_mass_proc | |
| ID_SIM | = lv_id_sim | |
| CHANGING | ||
| CD_LOGHANDLE | = lv_cd_loghandle | |
| TABLES | ||
| IT_IMPORTDATA | = lt_it_importdata | |
| CT_OK | = lt_ct_ok | |
| CT_NOK | = lt_ct_nok | |
| EXCEPTIONS | ||
| ASSIGN_ERROR = 1 | ||
| LOG_ERROR = 2 | ||
| DB_ERROR = 3 | ||
| ENQUEUE_ERROR = 4 | ||
| ARCHIVE_ACTIVE = 5 | ||
| . " PFO_RFC_IMPORT | ||
ABAP code using 7.40 inline data declarations to call FM PFO_RFC_IMPORT
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