Inventory Management - EBS (MOSC)

MOSC Banner

Inventory Transaction Worker programs are running in sequence

edited May 16, 2016 3:59PM in Inventory Management - EBS (MOSC) 3 commentsAnswered

Hi,

Given below scenario, can anyone please help me finding an optimal way to process Material Transaction Interface records?

We have legacy Warehouse Management application for receiving Items against PO and fulfilling Sales Order. This application is integrated with Oracle Inventory management all receiving, internal movements & adjustments, and Shipment transactions are interfaced to Oracle Inventory module. on daily basis we do receive thousands of transaction records in MTL_TRANSACTION_INTERFACE table. The situation we are facing very frequently when Material Transaction processing is taking muck longer time than in-flow of the data.

Let me explain one scenario: in one of our recent experience there were some 14K number of Interface records were in PENDING status (PROCESS_FLAG = 1). When Process Transaction Interface job is bounced (terminated and started), it allocated 28 Worker processes each allocated with Transaction Header ID for 500 records (Worker Rows set as 500 for "Material Transaction Manager"). Now these worker jobs are running in sequence and each job approximately taking 15-20 mins to complete. Overall spending some 7-8 Hours to completely processing 14K records. From performance standpoint this is not acceptable as per Business.

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center