General Description Setting up RPCFG.TXT for Maximum Iterations
Resource Planning can handle infinite time phased bill explosions.
It also handles roll ups of planned orders through multiple distribution center levels.
Sometimes there are errors in the bill or the vendor consolidation center.
For instance Bill A points to Bill B and Bill B points to Bill A.
or Center 11 points to center 18 which points to 1 which points to 11.
These data/logic errors create infinite loops.
For this reason one should always set Maximum Iterrations in RPCFG.TXT.

Procedure	Setting up RPCFG.TXT for Maximum Iterations
1.	*MAXIMUM ITERATIONS*1*@ meansThere are no BOM's and No Consolidation Centers.
2.	*MAXIMUM ITERATIONS*2*@ means There are either single level BOM's or Consolidation Centers.
3a.	*MAXIMUM ITERATIONS*N*@ meansThere are BOM's and Consoilidation Centers
3b.	In this case your administrator should follow this procedure to get the setting.
3c.	*MAXIMUM ITERATIONS*0*@ Let's the software calculate the number of iterations.
3d.	*CREATE MYDEBUG FILE*1*@ creates mydeb1.txt mydeb2.txt etc. for each iteration.
3e	The administrator should look at the mydeb1.txt , mydeb2.txt etc. and set :
3f	*MAXIMUM ITERATIONS*N* where N is the last time mydebN.txt changed content.
3g.	Then the administrator removes *CREATE MYDEBUG FILE*1*@ from the RPCFG.txt file.
3h.	The computer could do this automatically but it is safer to have
3i	an administrator set the value to evaluate whether the extra iterations are data errors.
3j.	*MAXIMUM ITERATIONS*0*@ should never be running in production on the server
3k.	nor on the client computer.