Asset Lifecycle Management - PSFT (MOSC)

MOSC Banner

Is anyone else having performance issues with WM_CLOSE batch job to close work orders?

edited Aug 4, 2020 10:23AM in Asset Lifecycle Management - PSFT (MOSC) 7 commentsAnswered ✓

In Maintenance Management module, there is a batch job WM_CLOSE that is now running 2 - 3 hours.  We are on PTools 8.56.14, PUM 34.  Our IT department is trying to state that we have too many completed work orders where time sheets have not yet been submitted. This job is processing through the timesheets and all the work order lines associated to those time sheets increasing the run time.  We have 1452 time sheets which have 75K work order lines associated to them (yes, we are a big shop). 

1.  Is anyone else experiencing this performance issue?

     - if not, have you done something to improve performance?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

PSFT ALM Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center