Ansicht
Dokumentation

OIJP_INTERIM_CHECK - IS-OIL TSW - Interim Check Routine

ROGBILLS - Synchronize billing plans   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Functionality

In the routines where either the optimum proposal date or the most inventory is proposed, there is little risk of interim dates having too little inventory. This then applies to:

• those routines that use re-order point planning where the inventory is checked for a level above the safety level and the proposal made on that date before the inventory position can become worse,

• those routines that maximize inventory on specified calendar dates in order to have the highest possible levels of inventory in the proposals

This does not mean that there is absolutely no risk of low inventory positions using these routines, only (1) that the routines make the best possible attempt to avoid them. Any proposals that are left are left because either (1) it is physically not possible to cover the demand issues or (2) previously scheduled batches are blocking planning proposals from being made at a sufficient level.

There are however two routines available for the user to specify planning in order to consider that do not necessarily satisfy the above statements. Specifically, these are the Target and Replacement planning types when used in conjunction with a planning calendar.

Because targets may be well below maximum levels, and the proposals are allowed only on calendar dates, the ability of planning using the normal routine to cover all the interim inventory positions is reduced.

For this reason, below is an extra routine that must be applied to these these two routines (TC and RC) only at the specified point. (Note that the spreadsheet examples in the text do not include consideration of this routine for clarity.)

1. Find lowest IBASE figure between BACK_DATE and RDATE (local). Record inventory and date in LMENG and LDATE respectively (local)

2. Calculate SAFETY - LMENG = SHORTFALL

3. If SHORTFALL > 0, carry on otherwise End.

4. Find previous DFLAG prior to LDATE
Record inventory and date in DMENG and DDATE (local)

5. Calculate MAXINV - DMENG - record value in P_DINV.

6. Calculate MAXINV - RMENG - record value in P_RINV.

7. Calculate lesser of P_DINV and P_RINV - record value in PLONG.
This is the most that can be allowed on the previous calendar date (DDATE).

8. Check SFLAG on DDATE. If marked, goto step 9. If not marked, goto step 12.

9. Increment proposal allowed.

10. Round SHORTFALL up to nearest INCLOT.

11. If PLONG greater than or equal to SHORTFALL, goto step 15. If not, routine END.

12. New batch proposal.

13. Round SHORTFALL up to nearest MINLOT + INCLOT.

14. If PLONG greater than or equal to SHORTFALL, goto step 15. if not, routine END.

15. Move SHORTFALL onto RMRP (and IBASE) on date DDATE.

16. Clear all local variables used in this routine.

If this routine results in a proposal being made and placed on RMRP, then the routine in which this takes place (TC or RC) will have a new new IBASE figure to that highlighted before the above (to be put in local variable RMENG). This will, however, still be the correct one to choose for the main routine and the main routine can continue provided the new value of IBASE at RDATE is captured. If no proposal is made above, then the main routine can continue as before.

When a proposal cannot be made by the above routine to cover interim inventory positions, then the worklist includes the proposal as a problem with the relevant reason code. Note that this routine, when successful, will result in some planning runs not being optimized according to the planning type and method chosen--however, planning also has a responsibility to cover the inventory across the whole planning horizon.

Example

Notes

Further information

Parameters

DATE_FROM
DATE_TO
INTERIM_OIJDOPL_TAB
I_INCLOT
I_MAXI
I_MAXINV
I_MAXLOT
I_MININV
I_MINLOT
I_SAFEINV

Exceptions

Function Group

OIJP

ROGBILLS - Synchronize billing plans   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4368 Date: 20240523 Time: 130740     sap01-206 ( 79 ms )