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

Function ICH_MWO_PPN_INSERT 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 'ICH_MWO_PPN_INSERT'"ICH_MWO_PPN_INSERT.
EXPORTING
IS_MWO_PPN_CONTROL = "ManufactoringWorkOrderProductionProgress control
EXCEPTIONS
ENTRY_ALREADY_EXISTS = 1 INSERT_FAILED = 2
IMPORTING Parameters details for ICH_MWO_PPN_INSERT
IS_MWO_PPN_CONTROL - ManufactoringWorkOrderProductionProgress control
Data type: ICH_S_MWO_PPN_CONTROLOptional: No
Call by Reference: Yes
EXCEPTIONS details
ENTRY_ALREADY_EXISTS - Entry already exists
Data type:Optional: No
Call by Reference: Yes
INSERT_FAILED - Insert Failed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICH_MWO_PPN_INSERT 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_mwo_ppn_control | TYPE ICH_S_MWO_PPN_CONTROL, " | |||
| lv_entry_already_exists | TYPE ICH_S_MWO_PPN_CONTROL, " | |||
| lv_insert_failed | TYPE ICH_S_MWO_PPN_CONTROL. " |
|   CALL FUNCTION 'ICH_MWO_PPN_INSERT' "ICH_MWO_PPN_INSERT |
| EXPORTING | ||
| IS_MWO_PPN_CONTROL | = lv_is_mwo_ppn_control | |
| EXCEPTIONS | ||
| ENTRY_ALREADY_EXISTS = 1 | ||
| INSERT_FAILED = 2 | ||
| . " ICH_MWO_PPN_INSERT | ||
ABAP code using 7.40 inline data declarations to call FM ICH_MWO_PPN_INSERT
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