Oracle ASCP

How to configure High

speed manufacturing
routings in Oracle
Applications for ASCP

An AVATA White Paper

By Aravind Gajjela
December 2015

AVATA | www.avata.com page | 1

 Table of Contents
1 Introduction ................................................................................................................................. 3
1.1 Objective ........................................................................................................................................ 3
1.2 Business Needs .............................................................................................................................. 3
1.3 Business Impact ............................................................................................................................. 3
2 Technical Overview....................................................................................................................... 4
2.1 Solution Concept ............................................................................................................................ 4

AVATA | www.avata.com page | 2

 Introduction

1.1 Objective
This document is intended to give VCP consultants an overview of how to configure high speed
manufacturing routings in Oracle Applications to enable accurate planning in ASCP.

1.2 Business Needs

Oracle ASCP engine solves routing usage rates only up to 6 decimals. If client has high speed
manufacturing rates higher than 6 decimals, then ASCP overstates supply and gives a wrong
indication to the supply planning
Issue causes:
i. Impacts day to day planning cycles
ii. Incorrect picture to master schedulers
iii. Impacts raw material planning
iv. Impacts safety stock planning

This key issue most of the times drives consultants to customize the solution either in source ERP
systems or changing plan output with huge bolt on applications

This white paper helps consultants to resolve the issue using standard functionality using collections
hook. This has been blessed from Oracle through an SR

This solution has been successfully tested using Oracle Applications 12.2.2 using legacy collections
integrated with JD Edwards

This solution also works best using Oracle EBS integrated with Oracle ASCP using the same
approach. All of the below screen shots are from Oracle Applications 12.1.3

1.3 Business Impact

i. Any source ERP systems cannot change the routings due to this engine issue in ASCP
ii. Changing routing rates in source ERP systems have a significant impact on manufacturing
work orders/scheduling, line rates analysis, rough cut capacity planning
iii. Impact of changing routings is a bigger issue than ASCP engine solves
iv. Example:
a. Routing usage rates are 0.00000654 each/hour
b. Oracle VCP engine rounds this rate to 0.000007 each/hour

v. In this scenario, routings cannot be changed to a smaller time unit, due to rate becoming smaller than
an hour

AVATA | www.avata.com page | 3

 Technical Overview

1.4 Solution Concept

i. Oracle EBS routing allows usage rate to six decimals .000007 instead of actual usage rate
0.00000654 – this is just for illustration
ii. As Oracle routing allows only six decimals, there is no other option available to increase the
precision to ten decimals

AVATA | www.avata.com page | 4

 iii. Collected data also rounds the usage rate to six decimals

iv. Utilize routing quantity in msc_routings table to populate the quantity multiplier, so as to
reduce the number of decimals

v. Update resource_usage in msc_operation_resources to a multiple less than or equal to six

decimals

vi. With the above example to achieve the usage rate to 0.00000654 (eight decimals) it may be a
good idea to use routing_quantity as 1000 and resource_usage rate as 0.00654
vii. ASCP engine considers the usage rate with routing_quantity multiples and derives the
capacity in the constrained plans

AVATA | www.avata.com page | 5

 viii. This white paper is not intended to derive the results from ASCP plan output, as the plan
output depends on the plan options and profiles configuration and varies from client to client
ix. This little piece of custom code can be triggered in the collections hook to update the above
tables
x. There is no way to show routing_quantity in the front end using Oracle forms in ASCP
xi. After updates to msc_routings and msc_operation_resources

xii. Oracle ASCP plan output doesn’t change and reads the correct usage rate more than six
decimals with this approach, below Oracle ASCP constrained plan shows the usage rate
0.00000654/hour to 0.392392000/min correctly as needed

AVATA | www.avata.com page | 6

 Disclaimer:
Please test and follow Oracle configurations document as per your client requirements before enabling
this solution in Production environments

AVATA Inc.

Copyright 2015, AVATA. All rights reserved.

This document is provided for information

purposes only and contents are subject to
change without notice.

AVATA | www.avata.com page | 7