Oracle Advance Supply Chain Planning (ASCP) Learning

Oracle ASCP Learning

Introduction

Oracle Advanced Supply Chain Planning (ASCP) is a comprehensive, Internet-based planning solution that decides when and where supplies (for example, inventory, purchase orders and work orders) should be deployed within an extended supply chain. This is the supply planning function.

The key capabilities of Oracle ASCP are:

• Holistic Optimization, Planning, and Scheduling. Oracle ASCP can plan all supply chain facilities simultaneously. Short-term detailed scheduling and long-term aggregate planning are supported within a single plan. This single plan also supports multiple manufacturing methods, including discrete, flow, project, and process manufacturing.

• Finite Capacity Planning and Scheduling. Oracle ASCP generates feasible supply chain plans that consider both resource and material constraints.

• Optimization. Users can easily configure Oracle ASCP to optimize specific business criteria. No programming is necessary to access Oracle ASCP‘s powerful mathematical optimization capabilities.

• Backward Compatibility. Oracle ASCP‘s component architecture allows it to be deployed against any combination of Oracle 11 and Oracle 11i transaction systems.

• Workflow-Driven Exception Messaging. Oracle ASCP‘s exception messages alert planners to critical issues across the extended supply chain. Workflows that drive these exceptions route data to and feedback from trading partners as required, thus effectively involving them in the supply chain planning process.

• Global Accessibility. Oracle ASCP‘s database-centric architecture stores plan data in a central planning server database. These data are accessible from Oracle Advanced Supply Chain Planning anywhere via a simple browser. It is possible for multiple planners to simultaneously access data from a single plan.

• Integrated Planning and Execution. Oracle ASCP‘s Advanced Planner Workbench user interface not only displays plan results, but also allows planners to execute planning recommendations. Planners do not have to move to the transaction system to perform plan execution.

• Simulation Capability. Oracle ASCP allows many types of changes to supply, demand, plan options, and resource profiles to simulate changing business conditions. You can generate a plan considering all the changes that have been entered via the Planner‘s Workbench. Unlimited numbers of scenarios can be simulated and compared using online planning, copy plans, and exceptions.

Setup Flowchart

Setup Steps for the Source Instance

1. Install the source instance patch

Before beginning the functional setup of the source instance(s), a patch must be applied that will create several new concurrent programs, Flexfields, profile options, and database objects on the source database. The patch that is required is determined by the versions of the application and database on the source instance. When successfully applied, the patch should create the Create Planning Flexfields, Create Global ATP Flexfields, and Refresh Snapshot programs under the All SCP Reports Request group.

2. Create a database link pointing to the planning server.

Note: Before beginning the installation of the source patch, count all (if any) invalid database objects. If after the patch is installed there are more invalid objects than before, there was a problem with the patch application.

A database link must be established on the source instance that points to the destination (planning) instance. This database link will be referenced in a newly created profile option, MRP: ATP Database Link.

3. Create an Advanced Supply Chain Planner responsibility. You must create a responsibility in the source instance with the name 'Advanced Supply Chain Planner'. The responsibility name must match Advanced Supply Chain Planner exactly. During the data collection process which runs on the destination server, the Refresh Snapshot program is launched automatically in the source from this responsibility. The refresh snapshot process will not complete properly if the responsibility name is not correct.

The Create Planning Flexfields concurrent program creates new segment definitions in existing descriptive Flexfields to hold data that may be required for constrained and/or optimized planning. The program also populates profile values with the value corresponding to the descriptive Flexfields attribute number for each attribute (planning parameter) created.

4. Launch the Create Planning Flexfields report from the newly created Advanced Supply Chain Planner responsibility. The parameters that must be set for the report are the attributes that you wish to utilize for the new Flexfields definitions. The list of values for each parameter lists only the available attributes in the subject descriptive Flexfields. After submitting the program, eleven additional processes should be spawned. These jobs are compiling the descriptive Flexfields views. Check that the profile values corresponding to each Flexfields attribute were populated with the correct attribute number. Some profile values may retain the value of unassigned after the Create Planning Flexfields program completed. You must change any unassigned profiles to the attribute number corresponding to the Flexfields attribute where the new segment was defined.

5. Create the Global Order Promising Flexfields.

The Create Global ATP Flexfields is very similar to the Create Planning Flexfields program. It creates new Flexfields segments to hold global ATP data at the item, BOM, routing, and resource levels. The same process, including warnings and suggestions, applies for the Create Global ATP Flexfields program. 

6. Set up source data with BOMs, resources, routings, supplier data, Flexfields, purchasing information, item masters, Oracle BIS targets, and any other data required by your plans.

7. Set profile values.

If Global Order Promising is going to be utilized, the following two additional profile options must be set. The MRP: ATP Database Link profile option must be set with the database link. The profile value is the name of the database link that resides on the source and points to the destination. There is no validation on this profile value. If Global Order Promising is not utilized, this need not be set.

The INV: External ATP profile must be set to Global ATP. This is a choice from the list of values. If Global ATP is not utilized, this need not be set. 

8.Defining the planning parameters

9.Define forecast sets

10.Define MDS Names

11.Define planning exception Sets5.Start Planning manager

12. Execute the Refresh Snapshot concurrent program.

The Refresh Snapshot process must be run on the source. This concurrent program is available in the Advanced Supply Chain Planner responsibility created earlier. The process has no parameters to be set at run time. Verify that the process completes without error

Setup Steps for the Destination Instance 

1. Install the destination instance patches. 

2. Create a database link pointing to each source. These links will be needed when defining instances later in this setup procedure. 

3. Define the source instances to be collected from. The define instances setup establishes the means of communication between the source and destination instances. It also specifies the organizations in the source database for which data will be pulled. 

4. From the Navigator, choose Setup > Instances. Do not access this form while the collections process is running; it locks a table that the collections process needs to complete successfully. The Application Instances window appears. Enter each of the Application instances for which you would like the Planning Server to plan. Complete the fields and flags in the Application Instances window as shown in the table below. Enter the organizations on each of the instances from which to collect the Planning data and plan for on the Planning Server by clicking Organizations. The Organizations window appears. Select the organizations for an instance. Be sure to select the master organization.

1. Item Setup 

Item Planning Attribute(s)	Functional Area	Description
Make or Buy	General Planning	This item attribute determines how the item is planned. The
		planning process looks at the Make or Buy item attribute to
		determine whether to generate component requirements.
		The attribute can have a value of Make or Buy and is
		directly related to the Process Execution Enabled and
		Purchasable	item attributes.
		When implementing orders via the Planner Workbench,
		the make e or buy attribute is used as the default for the type
		of planned order you can implement, either purchased or
		manufactured.
Planner	General Planning	Planners manually review, adjust, and release orders as
		needed by the shop floor/Planning department. Assign Item
		Level Planner for each item that is under MRP Planned. To
		release planned orders from the Planner work bench,
		Planner is required to be defined and assigned. A single
		planner may handle both purchasing and production supply
		scheduling. Planners may also be responsible for levelling
		production, scheduling efficient batch sizes, and keeping
		stock balances to a minimum
Inventory Planning Method	General Planning	A Same Item cannot be in both MRP Planned and in
		General Planned. Hence Not Planned to be chosen for all
		MRP Planned Items
Planning Method	MPS/MPP Planned	All FG items having independent demand should be
		defined as MPS/MPP Planned Items so that they can be
		placed in the forecasts and sales orders. All dependent
		demand items (components) should be defined as MRP
		Planned Items so that Purchase requisitions can be
		generated for such items from the work bench
Forecast Control	MPS/MPP Planned	Consume and derive option is chosen to consume all
		forecasts for independent demand item whose forecasts
		are consumed during sales order issue and shipments and
		the forecast is updated.
Purchasable	Purchasing	This item attribute allows you to establish whether the item
		can be placed on purchase orders or requisitions. Items will
		be available	as Purchase Requisitions while releasing
		planned orders from Planner work bench. Enter List Price
		for all raw materials and packaging items
Stockable	Inventory	Enables you to store the item in an asset subinventory.
		Used while Net Subinventory during Planning Net
		Requirement	calculations
Customer Orders Enabled	Order Management	Enables you to place the item on a sales
		Order. It creates demand for all Items that are placed on
		the Sales Orders. This is required while setting planning
		parameters

2. Forecast Set

Create Forecast Set and assign items in Forecast set.

3. Sourcing Rule and Assignment Set

4. Creating Supply Chain plans in Oracle ASCP

Oracle ASCP can generate planned orders for an entire supply chain within a single multi-organization supply chain plan. There are three types of plans Production Plan, Manufacturing plan and Master plan. Each plan creates time phased planned orders that satisfy independent and dependent demand while seeking to respect material constrains.

Sourcing rules determine the movement of materials throughout your supply chain; these include items that you buy from your suppliers and make at your manufacturing organizations. Sourcing rules and bills of distribution both specify date-effective sourcing strategies, combining replenishment sources with split allocation percentages and rankings.

Pre-requisites for running a Supply Chain Plan

• Each planned organization must be set up on the source instance.
• Collection programs must be directed to collect data from the transactional instance of each planned organization
• Items to be planned must be enabled in each organization that can produce (or distribute) the item. During item setup, items can be enabled in all organizations or only in specific organization. 
• Formula and Recipe for each planned item must exist or be enabled in each organization that is planned centrally
•  Suppliers and sourcing rules must be enabled in all relevant organizations.

Navigate to the Advance Supply Chain Planner responsibility and add a new manufacturing plan in the plan Name and Plan Type.

• Planned Items: Only those items should be considered that are planned.
• Material Scheduling Method: This will order the material as per the start date and as per order date.
• End Item Substitution Set: Using this option we can run a simulation for proper substitution.
• Assignment Set: This contains the rules for material flow.
• Item Simulation Set: Attach the Item Simulation set to plan.
• Schedule By: We can schedule the plan on the basis of sales order line using arrival date, shipping date, promise arrival and promise shipping date, and so on.
• Calculate Key Performance Indicators: To calculate the KPIs we will check this option.
• Lot for Lot: For creation of a separate supply for each demand and to avoid multiple supplies for multiple demands.
• Enable Pegging: Advance Supply Chain Planning gives you a graphical view of the demand of an item if we check this checkbox. The pegging engine pegs demand to supply.

Aggregation tab

Now we will move to the Aggregation tab, which holds the information related to plan date and buckets.

The main options in this tab are:

• Plan Start Date: Displays the date on which you run the plan and by default it will pick the system date.
• Plan End Date: This date is as per the defined bucket of your organization.

5. Run Data Collections

To run data collections from oracle source systems , which includes item data, Stock details and demand includes sales order data etc before releasing planned orders. The collection data can be viewed from view collection data for the further analysis

The first program, Planning Data Pull, copies information from the source instance into the APS staging tables on the planning server. For example, it ensures that items with the same names that are collected from different source instances will be assigned the same internal IDs (recognized as the same item).

The second program, Planning ODS Load, copies information from the APS staging tables into the operation data store on the planning server, where it becomes available for use during planning.

There are three collection methods:

I. The Complete Refresh method clears all transaction data for all business entities from the planning server (for the source instance being collected), then copies over information about the userselected entities. This method can be time consuming.

II. The Targeted Refresh method clears transaction data for only the user-selected business entities from the planning server, and then copies the entity information over from the transaction instance. Information about unselected entities remains intact g targeted refresh for entity Trading partners, also collect entity Calendarsand PJM

III. The Net Change Refresh method copies only incremental changes to business entities to the planning server (and is thus faster), but is supported mainly for demand and supply business entities only.

6. Release Planned Orders

The Planning Detail Report provides a simple and consolidated report that shows the output of the advanced supply chain planning process. For a given Supply Chain Plan, the report includes the relevant details about items, gross requirements, scheduled receipts, planned orders and exceptions in separate worksheet

• From the Planner Workbench Navigator, Expand the Tree by clicking Plans > Plan Name XYZ >

Current> Late Sales orders and Forecasts > Past Due forecast > Organization Code > Item

Advanced Supply Chain Planning > Submit Requests > Planning detail Report