SAP OIJP_PLANNING_MC Function Module for IS-OIL TSW - Planning proposal routine MC (Max. inventory with calendar)
OIJP_PLANNING_MC is a standard oijp planning mc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-OIL TSW - Planning proposal routine MC (Max. inventory with calendar) 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 oijp planning mc FM, simply by entering the name OIJP_PLANNING_MC into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJP
Program Name: SAPLOIJP
Main Program: SAPLOIJP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function OIJP_PLANNING_MC 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 'OIJP_PLANNING_MC'"IS-OIL TSW - Planning proposal routine MC (Max. inventory with calendar).
EXPORTING
I_PTYPEFLAG = "Planning functionality : Supply Chain Definition
T_OIJLOCMAT_WA = "Workarea of Loc. Rundown/Planning material table
T_OIJTSMAT_WA = "Workarea of TS Rundown/Planning material table
TABLES
T_OIJDOPL_TAB = "Internal demand object planning table
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLOIJP_001 OIL-TSW: Customer exit for customer specific inventory planning
EXIT_SAPLOIJP_002 OIL-TSW: Customer exit for dynamic safety stock calculation logic
IMPORTING Parameters details for OIJP_PLANNING_MC
I_PTYPEFLAG - Planning functionality : Supply Chain Definition
Data type: OIJPLSEQ-D_TYPEFLAGOptional: No
Call by Reference: No ( called with pass by value option)
T_OIJLOCMAT_WA - Workarea of Loc. Rundown/Planning material table
Data type: OIJLOCMATOptional: No
Call by Reference: No ( called with pass by value option)
T_OIJTSMAT_WA - Workarea of TS Rundown/Planning material table
Data type: OIJTSMATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OIJP_PLANNING_MC
T_OIJDOPL_TAB - Internal demand object planning table
Data type: ROIJDOPLOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIJP_PLANNING_MC 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_i_ptypeflag | TYPE OIJPLSEQ-D_TYPEFLAG, " | |||
lt_t_oijdopl_tab | TYPE STANDARD TABLE OF ROIJDOPL, " | |||
lv_t_oijlocmat_wa | TYPE OIJLOCMAT, " | |||
lv_t_oijtsmat_wa | TYPE OIJTSMAT. " |
  CALL FUNCTION 'OIJP_PLANNING_MC' "IS-OIL TSW - Planning proposal routine MC (Max. inventory with calendar) |
EXPORTING | ||
I_PTYPEFLAG | = lv_i_ptypeflag | |
T_OIJLOCMAT_WA | = lv_t_oijlocmat_wa | |
T_OIJTSMAT_WA | = lv_t_oijtsmat_wa | |
TABLES | ||
T_OIJDOPL_TAB | = lt_t_oijdopl_tab | |
. " OIJP_PLANNING_MC |
ABAP code using 7.40 inline data declarations to call FM OIJP_PLANNING_MC
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."SELECT single D_TYPEFLAG FROM OIJPLSEQ INTO @DATA(ld_i_ptypeflag). | ||||
Search for further information about these or an SAP related objects