SAP OIB_PI_EXPORT_ITABS_TO_OIB_MM Function Module for Export the passed internal tables to SAPLOIB_MM
OIB_PI_EXPORT_ITABS_TO_OIB_MM is a standard oib pi export itabs to oib mm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export the passed internal tables to SAPLOIB_MM 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 oib pi export itabs to oib mm FM, simply by entering the name OIB_PI_EXPORT_ITABS_TO_OIB_MM into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIB_MM
Program Name: SAPLOIB_MM
Main Program: SAPLOIB_MM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIB_PI_EXPORT_ITABS_TO_OIB_MM 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 'OIB_PI_EXPORT_ITABS_TO_OIB_MM'"Export the passed internal tables to SAPLOIB_MM.
TABLES
OIB_IS1INT = "Physical Inventory Conversion Parameter Appendix
OIB_IS2INT = "Appendix: Physical Inventory - Additional Quantities
TABLES Parameters details for OIB_PI_EXPORT_ITABS_TO_OIB_MM
OIB_IS1INT - Physical Inventory Conversion Parameter Appendix
Data type: ISEGO1Optional: No
Call by Reference: Yes
OIB_IS2INT - Appendix: Physical Inventory - Additional Quantities
Data type: ISEGO2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIB_PI_EXPORT_ITABS_TO_OIB_MM 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_oib_is1int | TYPE STANDARD TABLE OF ISEGO1, " | |||
| lt_oib_is2int | TYPE STANDARD TABLE OF ISEGO2. " |
|   CALL FUNCTION 'OIB_PI_EXPORT_ITABS_TO_OIB_MM' "Export the passed internal tables to SAPLOIB_MM |
| TABLES | ||
| OIB_IS1INT | = lt_oib_is1int | |
| OIB_IS2INT | = lt_oib_is2int | |
| . " OIB_PI_EXPORT_ITABS_TO_OIB_MM | ||
ABAP code using 7.40 inline data declarations to call FM OIB_PI_EXPORT_ITABS_TO_OIB_MM
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