E9.1 R3483 ending in error some times

[jigarmehta]

Dear All,

Facing a wierd issue of R3483 ending in error sometimes ..

Initially our planning months were set to 11 , for some days it worked fine but then it started ending in error in scheduler. Then we changed the planning months to 5 now and it was working fine till now but this is a stop gap solution we would need R3483 to plan for atleast next 10-12 months

To give you a back ground we have 3 manufacturing branch plants and IBR is setup accordingly for Demand Branch and Supply Branches.. Now in due course one of the MFG branch is going to get close and hence i changed the STKT for items in that Branch plant as Obsolete assuming MRP will not consider those items.
Our MRP runs in scheduler based on Planning codes , DO i need to change the planning codes (not to consider) as well for that Branch plant which is going to get close and also expire the IBR ??

On checking found that R3483 creates zombies in back ground and ends in error (Any work around or permanent solution for this

Any help would be appreciated if we need to look at a certain table for data size or anything since I am more into S&D profile and this pertains to MFG.

Using JD Edwards 9.1 Tools Release 9.2.1

 

[Larry_Jones]

First thing I would check is are your Calendars defined far out enough? Are they ending in 2021?
Second is have you customized any of the MRP/MPS UBEs, BSFNs, Data Structures?
Third is has anyone committed the cardinal sin of modifying a standard data dictionary item? (changed size or data type)

 

[Larry_Jones]

Do you run R30601 - Bill of Material Structural Analysis - on a regular basis to check for Loops in your BOM Structure?

 

[Jde_Bala]

First thing I would check is are your Calendars defined far out enough? Are they ending in 2021?
Second is have you customized any of the MRP/MPS UBEs, BSFNs, Data Structures?
Third is has anyone committed the cardinal sin of modifying a standard data dictionary item? (changed size or data type)

Yes Larry. I would also suggest to update calendar for all BU up to 2025. If the shifts are defined, adding calendar for shifts as well may not throe error.

 

[jigarmehta]

First thing I would check is are your Calendars defined far out enough? Are they ending in 2021?
Second is have you customized any of the MRP/MPS UBEs, BSFNs, Data Structures?
Third is has anyone committed the cardinal sin of modifying a standard data dictionary item? (changed size or data type)

Hi Larry,

There is nothing done with respect to customizing MRP or any of the BSFN ..neither any standard DD items change

The calendar is currently setup for Mfg Branch plant till 2024 but as read in Oracle document that it should be atleast 5 years in future.....So will try setting up the same till 2027 or so...

Need one suggestion that should both Supply and Demand Branch plant be set @ 5 years in future or only Mfg branch plant to be set for 5 years in future ..

 

[jigarmehta]

Yes Larry. I would also suggest to update calendar for all BU up to 2025. If the shifts are defined, adding calendar for shifts as well may not throe error.

Thanks.....Will try to setup the calendar till 2027 and observe.....the problem is that the issue is not consistent enough as the report goes in error only some times...and hence was trying to explore the possibilities...

 

[Craig_Potter]

Does the PDF report show any error?

 

[jigarmehta]

Does the PDF report show any error?

Hi Craig,

The report does not show any error and only the mesage "Generation successfull"...
But as mentioned above have setup the Shop floor calendar till 2027 now and it seems to be working now for at least 8-9 months in future which initially went into error for 4 months also.......However we would like to take have the messages till at least a year or so but managing so far till 9 months in future...

 

[Craig_Potter]

Hi Craig,

The report does not show any error and only the mesage "Generation successfull"...
But as mentioned above have setup the Shop floor calendar till 2027 now and it seems to be working now for at least 8-9 months in future which initially went into error for 4 months also.......However we would like to take have the messages till at least a year or so but managing so far till 9 months in future...

Perhaps change the horizon out to a year again to trigger the "error" and lets see what the error is.

Does the job end with status E?
If yes....Is there a PDF? What does it say? Is there a jde.log, what does it say? Are there any work centre errors?
If no.... what is the error?

 

[jigarmehta]

Perhaps change the horizon out to a year again to trigger the "error" and lets see what the error is.

Does the job end with status E?
If yes....Is there a PDF? What does it say? Is there a jde.log, what does it say? Are there any work centre errors?
If no.... what is the error?

Hi Craig,

Have gone to that level of jde.log and since it is working now for 9 months and management is OK with it for now , so do not wish to attend this for now as have couple of urgent things on hand to finish...

Have well noted down your comments and will explore the same in future along with Mfg consultant since my profile being into S&D the knowledge is limited...
Thanks for the support.