shearerj
Reputable Poster
Hi All, looked through the list and didn't find any hits on this topic. Most conversations are about which UBEs should go to single and multi-threaded queues, but that is not my area of concern.
I am looking for feedback on the best practice queue design for a multi-billion dollar company with multiple divisions running in a single instance of JDE. There are no shared services between divisions. Each division runs their own GL, payroll, billing, etc. Three approaches are on the table:
1. Split each division to their own dedicated queues sharing between divisions only when there are single-threaded constraints (i.e. a QBatchXX per division).
2. Split each functional area to their own dedicated queues (i.e. QFinance, QPayroll, etc).
3. Both split by division and by functional area (i.e. QFinanceXX per division, QPayrollXX per division, etc).
Any feedback is appreciated.
I am looking for feedback on the best practice queue design for a multi-billion dollar company with multiple divisions running in a single instance of JDE. There are no shared services between divisions. Each division runs their own GL, payroll, billing, etc. Three approaches are on the table:
1. Split each division to their own dedicated queues sharing between divisions only when there are single-threaded constraints (i.e. a QBatchXX per division).
2. Split each functional area to their own dedicated queues (i.e. QFinance, QPayroll, etc).
3. Both split by division and by functional area (i.e. QFinanceXX per division, QPayrollXX per division, etc).
Any feedback is appreciated.