R3190 running slow

Our R3190- Repost open work orders, normally runs in 1.5 hrs, but once in a while it runs for 4-5 hrs. Does anyone know of a reason this would happen?

Thanks

E810, SQL

The problem you have described is quite vague. You may need to do more analysis to discover the proble,.Some questions
1-Is the R3190 repost running on a scheduler? Are there other scheduled jobs running or in same queue?
2-When the R3190 runs for 4-5 hrs, has there been a significant change in work orders, e.g, MRP creating new work orders or sales orders driving new ones? Don't forget the R3190 is checking F4801, F3111,F41021 to update/clear commitments.
3-Check your processing options and data selection of R3190. You may need to narrow these down

R3190 intermittent long run times

skrishna said:

Our R3190- Repost open work orders, normally runs in 1.5 hrs, but once in a while it runs for 4-5 hrs. Does anyone know of a reason this would happen?

Thanks

E810, SQL

Click to expand...

Did you ever find out what was causing this? We are experiencing the same issue now.

Thank you.

Some findings that may be of help..................

Work Order Repost R3190 runs in an endless loop under the following conditions.
a) Item is a component in Warehouse for picking.
b) Two-phase pick process is enabled for the item in Warehouse profile.
c) When R3190 is run, Phase 2 of pick request is not confirmed (Status < 391).

This issue is addressed by Bug 19260627 - R3190 Infinite Loop For Two Phase Pick Request.

An infinite 'While' loop was detected in the code and involves NER N4600610 (F4602 Repost Warehouse Commitments).

I did see that SAR but ruled it out since we are not using warehouse commitments, and an infinite loop would imply that the job would not end without manual intervention.

However, most of the time our job runs in 5 minutes or under but once in a while can take up to 4-5 hours. We cannot establish a pattern for this.

Thank you.

Did you test a scenario whereby you adjusted parameters to only select a specific number of records? This will enable you to gain some intelligence as to a root cause.

Al - its random.

Inadvertent reopening of closed work orders might have happened resulting in more data being processed...just a guess but certainly possible!

Thanks

A few other points to checkoff.......................

Checklist

1. When running the UBE, you can use short item number in data selection.

2. Run R3190 after peak hours so that it does not compete with other UBE's.

3. Maintenance should include purging Work Order files (R4801P). The R3190 looks at every WO record out there in the table. As this table grows, its going to take additional time.
Refer to R4801P Purging Work Order Records Document 630413.1.

4. Create multiple versions of the program, giving distinct data selection values. These versions may then run concurrently.

5. Run Purge Locations (R4102P) to purge the locations which are no longer going to be used. Refer to E1: 40: R4102P and Tables Related per Processing Option Value Document 1125633.1 and E1: 41: Inventory Purge Programs (R4101P/R4102P) Document 1322000.1.

6. Regenerate the table Indexes of F41021, F4801 and F3111.