Ansicht
Dokumentation

OIJP_PLANNING_RC - IS-OIL TSW - Planning proposal routine RC (Rep. inventory with calendar)

OIJP_PLANNING_RC - IS-OIL TSW - Planning proposal routine RC (Rep. inventory with calendar)

TXBHW - Original Tax Base Amount in Local Currency   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This routine attempts to make proposals for the demand object to match as closely as possible the issues for the object on the dates defined within the planning calendar.

Once the internal tables have been filled by the pre-routine process and calculations, only columns RMRP and IMRP should be empty at this stage. (IMRP may contain values from previous runs however).

The steps to follow for the demand object are:

1. Check that planning run flag (PLANFLAG) is not set.

2. Set variable Back_Date as day 0 or refresh Back_Date

3. Determine the highest inventory figure in column IBASE on calendar date (where DFLAG set) since Back_Date.
Sort on column IBASE for records with DFLAG set, record the value of date (RDATE) to identify inventory (RMENG)

4. Perform INTERIM CHECK ROUTINE.

5. Calculate MAXINV - RMENG = PMAX (local)
This is the maximum that can be proposed on date RDATE.

6. Find previous SFLAG marked prior to RDATE.
Record inventory SMENG (local) - this is the desired proposal quantity to replace.
Record date SDATE (local)

7. Calculate SMENG - RMENG = PREP

8. Calculate the lesser of PMAX and PREP - put result in PRES.

9. Check that PRES is greater than or equal to 0,5 * INCLOT - this ensures that we have at least the minimum space for a proposal. If check OK, carry on. If check fails, goto step 17.

10. Check RDATE record for an SFLAG setting > if marked, step 11. If not marked, step 13.

11. Incremental proposal to be made.

12. Calculate the incremental batch size for the proposal - PRES * * INCLOT / INCLOT, round to the nearest INCLOT (e.g. req. 17, INCLOT 10, 17 * 10 / 10 = 17, round to the nearest 10 gives 20).
Record value in PMRP (local variable).
If PMRP is greater than PMAX, PMRP = PMRP - INCLOT.
If resulting PMRP is less than or equal to zero, skip to step 17. ElseSkip to step 16.

13. New batch proposal to be made.

14. Is PRES greater then or equal to minimum batch size (MINLOT) ? If If yes, step 15 If no, skip to step 17.

15. Calculate the batch size for this proposal PRES - MINLOT = remainder, then remainder * INCLOT / INCLOT, round to the nearest INCLOT , gives partial result, then MINLOT + partial result gives proposal (e.g. requirement 42, MINLOT 25, INCLOT 10 > > remainder = 42 - 25 = 17 >> >> partial result as before in step 6. = 10, then proposal = 25 + 10 = 35).
Record this value in PMRP.
If PMRP is greater than PMAX, PMRP = PMRP - INCLOT.
If resulting PMRP is less than MININV, skip to step 17. Else goto step 16.

16. Place PMRP in RMRP on the RDATE, refresh values in IBASE.
Set SFLAG as marked on RDATE (as dates help to work out "issues" between batches).

17. Set BACK_DATE = RDATE.

18. Check BACK_DATE is equal to or less than END_DATE. If yes, loop around from step 3. If not, then End.

END.

This routine is then looped around (steps 3 to 18) until the whole planning horizon has been covered, when one of the back_date versus END_DATE checks fails.

This is then the routine for planning using replacement type and the re-order point method.

At the end of the planning routine, the values in RMRP should be be added to the values in BASE, and then both columns returned to OIJRD for the demand object, thereby overwriting the pervious values.

Example

Notes

Further information





Parameters

I_PTYPEFLAG
T_OIJDOPL_TAB
T_OIJLOCMAT_WA
T_OIJTSMAT_WA

Exceptions

Function Group

OIJP

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Material Data  
This documentation is copyright by SAP AG.

Length: 3919 Date: 20240523 Time: 141305     sap01-206 ( 58 ms )