SAP FOPC_ORM_TRANSFER Function Module for Transfer ORM
FOPC_ORM_TRANSFER is a standard fopc orm transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transfer ORM 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 fopc orm transfer FM, simply by entering the name FOPC_ORM_TRANSFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: FOPC_ORM
Program Name: SAPLFOPC_ORM
Main Program: SAPLFOPC_ORM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FOPC_ORM_TRANSFER 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 'FOPC_ORM_TRANSFER'"Transfer ORM.
EXPORTING
I_TIMEFRAME = "Timeframe
I_YEAR = "Year
* I_MODE = "
IMPORTING
ET_MESSAGES = "Return Table
TABLES
IT_ORGUNIT = "Organizational Units
IMPORTING Parameters details for FOPC_ORM_TRANSFER
I_TIMEFRAME - Timeframe
Data type: FOPC_TIMEFRAMEOptional: No
Call by Reference: Yes
I_YEAR - Year
Data type: FOPC_YEAROptional: No
Call by Reference: Yes
I_MODE -
Data type: COptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FOPC_ORM_TRANSFER
ET_MESSAGES - Return Table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
TABLES Parameters details for FOPC_ORM_TRANSFER
IT_ORGUNIT - Organizational Units
Data type: FOPC_T_ORGUNITOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FOPC_ORM_TRANSFER 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: | ||||
| lt_it_orgunit | TYPE STANDARD TABLE OF FOPC_T_ORGUNIT, " | |||
| lv_et_messages | TYPE BAPIRET2_T, " | |||
| lv_i_timeframe | TYPE FOPC_TIMEFRAME, " | |||
| lv_i_year | TYPE FOPC_YEAR, " | |||
| lv_i_mode | TYPE C. " |
|   CALL FUNCTION 'FOPC_ORM_TRANSFER' "Transfer ORM |
| EXPORTING | ||
| I_TIMEFRAME | = lv_i_timeframe | |
| I_YEAR | = lv_i_year | |
| I_MODE | = lv_i_mode | |
| IMPORTING | ||
| ET_MESSAGES | = lv_et_messages | |
| TABLES | ||
| IT_ORGUNIT | = lt_it_orgunit | |
| . " FOPC_ORM_TRANSFER | ||
ABAP code using 7.40 inline data declarations to call FM FOPC_ORM_TRANSFER
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