Source : http://www.oracleug.com/user-guide/master-schedulingmrpscp/supply-chain-planning

Oracle Advanced Planning Suite has a component architecture that separates the transaction data

and associated processing (for example, inventory receipts and order entry) in a source

instancefrom the planning calculations done in a destination instance. This allows planning

calculations to be done on a different physical machine

than the machine that performs transactions and results in better system response. It also allows

planning calculations (demand planning, inventory planning, supply planning and order promising) to

be applied simultaneously to information from across multiple source instances, which is useful when

transaction information for a global supply chain is spread across multiple instances. Oracle Demand

Planning also uses athird instance, anExpress database, to hold data while multidimensional

manipulation of demand data occurs.

The source can be any ERP system, but out-of-the-box integration to the Oracle Advanced Planning

Suite destination instance (planning server) exists in some cases but not in all cases.

Set up for Oracle Advanced Planning Suite consists of steps for the source, steps for the destination,

and steps for Express.

APS may be implemented in two possible configurations:

Centralized Planning

A centralized configuration implies that the ERP applications and APS share the same Oracle

instance on one server.

Decentralized Planning

A decentralized configuration implies that the ERP applications and APS are executing within two

separate Oracle instances, possibly on the same server.

Both configurations are supported using a consistent architecture with the sole distinction

being that the decentralized configuration requires the use of database links to pull data into

the MSC data store. 

APS nomenclature employs Source and Destination when speaking of the ERP transaction data

store and the planning data.  Data, at the source, is collected into the destination or

operational datastore (ODS) where planning activities occur. If a centralized configuration is

implemented, both the source and destination are operating within the same Oracle instance. 

In Oracle Advanced Planning, transaction processing and planning occur in separate database

instances, the source instance and the destination instance. If you deploy any Oracle Advanced

Planning module using this multi-instance configuration, please note the important restriction that

both source and destination database instances must be on the same major release of the Oracle

database; either both instances must be on Oracle 8i or both instances must be on Oracle 9i. The

configuration source on 8i with destination on 9i is not supported and the configuration source on 9i

with destination on 8i is not supported.

The following figure is a flowchart illustrating the source and destination setup steps.

Multti-Machine Implementation

For small implementations, source, destination, and Express can reside on the same machine and be

in the same instance.

For larger implementations where system throughput is more important, the various instances can be

deployed on separate machines. A two-machine deployment configuration is appropriate when the

size of the demand planning data is relatively small.

A three-machine deployment allows for the manipulation of high-dimensionality, large-scale demand

planning data to occur on a machine separate from the planning calculations done on the planning

server. The following figure illustrates this configuration.

The Advanced Supply Chain Planning concurrent manager may also be deployed on a separate

machine.

Setup Flowchart

 Implementing APS in centralized mode is only possible when collecting from an 11i source.A

centralized implementation does not require database links.  Since the planning flexfields are

included in 11i, submitting the concurrent process, Create Planning Flexfields is not required.  All

other setup discussed in this document are required.

This section describes the flows of information between the components of the Oracle Advanced

Planning Suite and provides an overview of how these components are to be used together in order to

accomplish several key business flows.

Topics covered in this section include the following:

APS Information Flows

The Demand-to-Make / Demand-to-Buy Business Flow

The Inquiry-to-Order Business Flow

APS Information Flows

The major information flows between the components of the Oracle Advanced Planning Suite and the

rest of Oracle Applications are shown in the figure below.

The Demand-to-Make / Demand-to-Buy Business Flow

The demand-to-make /demand-to-buy business flow begins with the establishment of independent

demands that will drive the activities of the supply chain. On the basis of sales history from Oracle

Order Management, Oracle Demand Planning generates statistical demand forecasts. After

adjustment by planners, these forecasts and

their variability as estimated by Oracle Demand Planning are then input into Oracle Inventory

Optimization.

Using user-supplied information about the variability of this forecast demand and the variability of

supplier lead-times, Oracle Inventory Optimization generates an optimal time-phased safety stock

plan.

Oracle Advanced Supply Chain Planning (hereafter, Oracle ASCP) considers three streams of

independent demand: the safety stock planned demand from Oracle Inventory Optimization, forecasts

from Oracle Demand Planning, and sales order demand from Oracle Order Management. Oracle

ASCP outputs a time-phased supply plan (planned orders) that can then be released directly to the

appropriate execution systems: Oracle Purchasing, Oracle Work in Process (for discrete

manufacturing), Oracle Process Manufacturing, Oracle Flow Manufacturing, Oracle Project

Manufacturing, or Oracle Shop Floor Management (for semiconductor manufacturing).

The Inquiry-to-Order Business Flow

The demand/supply picture output by Oracle ASCP serves as the basis for the order promising results

calculated by Oracle Global Order Promising. Oracle Global Order Promising can be called either

from a customer-facing order capture application such as a web store or from Oracle Order

Management.

In the inquiry-to-order business flow, an inquiry for a potential order is sent from Oracle Order

Management to Oracle Global Order Promising. The fulfillment date returned by Global Order

Promising, if later than the original request date, is populated as the new request date of the order.

This request date validation process is called scheduling. Once an order is successfully scheduled,

then it can be booked and made visible to Oracle ASCP for supply planning purposes.

Planning Cycle

This section describes an end-to-end planning flow that a planner might perform during the course of

a planning cycle. The flow demonstrates the key features of Oracle ASCP that a typical planner would

use in the course of their work. The general flow that occurs during a planning cycle is shown in the

figure below.

Setup Steps for the Source1. Install the source instance patchBefore 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 flexfield 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 flexfield definitions. The list of values for each parameter lists only the available attributes in the subject descriptive flexfield.

After submitting the program, eleven additional processes should be spawned. These jobs are compiling the descriptive flexfield views. Check that the profile values corresponding to each flexfield attribute were populated with the correct attribute number. Some profile values may retain the value of unassigned after the Create Planning Flexfield program completed. You must change any unassigned profiles to the attribute number corresponding to the flexfield 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 flexfield 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 Flexfield 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. 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

1. Install the destination instance patches.

2. Create a database link pointing to each source. These links will be needed when defining instances later on 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 a particular instance. Be sure to select the master organization.

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. Oracle ASCP

addresses the following key supply planning issues:

• How do I plan my supply chain in the least amount of time possible?

• How do I minimize the number of plans and iterations?

• How do I plan my entire supply chain?

• How do I involve my trading partners?

• How can I access my plan from anywhere?

• How do I keep improving my plans?

• How can I plan all manufacturing methods?

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 allow 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.

Objective

The objective of this document is to provide technical instructions of implementing a distributed multi

node Oracle Advanced Supply Chain Planning system on your existing Oracle Application 11i System.

Assumption / Pre implementation requirements

Oracle Advanced Planning Suite has component architecture that separates the transaction data and

associated processing (for example, inventory receipts and order entry) in a source instance from the

planning calculations done in a destination instance. This allows planning calculations to be done on a

different physical machine than the machine that performs transactions and results in better system

response. It also allows planning calculations (demand planning, inventory planning, supply planning

and order promising) to be applied simultaneously to information from across multiple source

instances, which is useful when transaction information for a global supply chain is spread across

multiple instances.

The source can be any ERP system, but out-of-the-box integration to the Oracle Advanced Planning

Suite destination instance (planning server) exists if the source is Oracle Applications Release 11.0 or

11i. The planning server is an 11i instance.

Both source and destination database instances must be on the same major release of the Oracle

database;

We are going to do a two machine ASCP implementation.

The basic requirement for both the machines is that of Oracle 11i E Business Suit.

Source System also called as “ERP System” and “Transaction System”.

Destination System also called as “ASCP System” and Planning System”.

Both the Oracle Applications 11i E-Business Suite are on release 11.5.10.2.

Patching the Source System (ERP System) and the Destination (ASCP system)

Task By: Apps DBA

Before beginning the functional setup of the source instance(s) and destination, the following patches

must be applied that will create several new concurrent programs, flexfields, profile options, and

database objects on the database.

If these patches have any prerequisite patches, you will have to apply all the prerequisite patches

before applying the main patches.

Note that these patches can be applied at the same time on both the systems. Also note that most of

the patches are to be applied on both the systems.

Note that we are using Oracle Applications 11.5.10.2 E Business suite and hence most of the patches

may not be required to be applied. To confirm this use the following sql script connected to the Oracle

Application Database as “APPS” user.

SET LINESIZE 120

COLUMN APPLICATION_SHORT_NAME FORMAT A20

SELECT

BUG_ID, APPLICATION_SHORT_NAME, BUG_NUMBER, CREATION_DATE, ARU_RELEASE_NAME

FROM AD_BUGS

WHERE BUG_NUMBER LIKE ‘%&BUG_NUMBER%’

ORDER BY 4

Pass the patch number when asked for the Bug Number and check whether the bug / patch exist in the

Oracle Application database. If the query returns row (showing the presence of the patch) then you

don’t require applying this patch.

Before applying patches please go through the readme files and associated notes (if present) for each

patch. Before beginning the installation of the source / destination patches, count all (if any) invalid

database objects. If after the patches are installed there are more invalid objects than before, there

was a problem with the patch application. First try to resolve them before going to next step.

Do the required pre install steps before applying each patch and then after applying do the post-

installation steps.

Patch the Source System (ERP System)

The following patches are required to be applied on the Source system:

1. 4185358

2. 2700001

3. 3551142

4. 4183434

5. 4240365

6. 4039921

7. 4392144

8. 4366346

9. 4863176

Prepare a work sheet to identify whether the patch is required to be applied on the Oracle Application

Source system using above given sql script and whether it requires any pre-requisite patches.

Sr. No. Patch Note Required (Y/N) Pre-requisites

1. 4185358 Y None for 11.5.10.2

2. 2700001 N NR for 11.5.10.2

3. 3551142 Y None

4. 4183434 N NR for 11.5.10.2

5. 4240365 278055.1 Y None for 11.5.10.2

6. 4039921 N NR for 11.5.10.2

7. 4392144 278055.1 Y None for 11.5.10.2

8. 4366346 278055.1 Y 3629717

9. 3629717 Y None for 11.5.10.2

10. 4863176 Y None for 11.5.10.2

Hence the sequence of applying the patches is as follows:

1. 4185358

2. 3551142

3. 4240365

4. 4392144

5. 3629717

6. 4366346

7. 4863176

Patch the Destination (ASCP) system

The following patches are required to be applied on the Destination system:

1. 4185358

2. 4231863

3. 4210584

4. 4359934

5. 4392144

6. 4366346

7. 4392231

8. 4039921

9. 4523322

Prepare a work sheet to identify whether the patch is required to be applied on the Oracle Application

Destination system using above given sql script and whether it requires any pre-requisite patches.

Sr. No. Patch Note Required (Y/N) Pre-requisites

1. 4185358 278055.1 Y None for 11.5.10.2

2. 4231863 278055.1 Y 4185358

3. 4210584 Y None

4. 4359934 278055.1 Y 4185358

5. 4392144 278055.1 Y None for 11.5.10.2

6. 4366346 278055.1 Y 3629717

7. 3629717 Y None

8. 4392231 Y None

9. 4039921 N NR for 11.5.10.2

10. 4523322 278055.1, 278052.1 Y 4392231, (4863176 on Source Side),

11. 4297568 Y None

Hence the sequence of applying the patches is as follows:

1. 4185358

2. 4231863

3. 4210584

4. 4359934

5. 4392144

6. 3629717

7. 4366346

8. 4392231

9. 4039921

10. 4523322

11. 4297568

ILOG Libraries and Executables

The patch 4297568 is for “ILOG Libraries and Executables”. Apply this patch only if you are using

11.5.10.2.

1. Log in to each concurrent processing server node as the owner of the Applications file system.

2. If the $SHT_TOP/lib/ilog/5.1 directory already exists, backup any files or directories that it contains.

3. Unzip the ilog51lib.zip file, located in the sht/lib directory of this patch, into the $SHT_TOP/lib

directory. This will create the ilog/5.1 subdirectory if it doesn’t already exist.

4. Change directories to $SHT_TOP/lib/ilog/5.1/SUN_OS5.

5. Copy the library files from the current directory to the $SHT_TOP/lib/ilog/5.1 directory.

On UNIX Sun Solaris, the files are

i. libconcert.a

ii. libcplex.a

iii. libhybrid.a

iv. libilocplex.a

v. libschedule.a

vi. libsolver.a

6. Use AD Administration to relink these executables [Under DB Node]:

i. Oracle Constraint Based Option (MSO): MSONEW

ii. Oracle Inventory Optimization (MSR): MSRNEW

iii. Oracle Manufacturing Scheduling (WPS): WPCWFS

iv. Oracle Work in Process (WIP): WICDOL, WICMEX, WICMLX

Create Database link

Task By: Apps DBA

Create database link on Source system to Destination system

A database link must be established on the source instance that points to the destination (11i

planning) instance. This database link will be referenced in a newly created profile option, MRP: ATP

Database Link, discussed in Step 7.

This database link will also be used, along with a database link established on the destination instance,

in setting up the instances on the planning server.

First make necessary entry of the Target / Destination instance Oracle Database in the tnsnames.ora

file of the Source Instance Oracle Database tier (TNS_ADMIN location).

Create Database link as follows:

create database link

connect to APPS identified by

using ‘’;

APPS-TRNS1.USA.COM>select INSTANCE_NAME, HOST_NAME from v$instance;

INSTANCE_NAME HOST_NAME

—————- ———————————————————–

TRNS1 indsapp001

APPS-TRNS1.USA.COM>show user

USER is “APPS”

APPS-TRNS1.USA.COM>ed

Wrote file afiedt.buf

1 create database link coe2

2 connect to apps identified by *****

3* using ‘coe2′

APPS-TRNS1.USA.COM>/

Database link created.

APPS-TRNS1.USA.COM>select INSTANCE_NAME, HOST_NAME from v$instance@coe2;

INSTANCE_NAME HOST_NAME

—————- ———————————————————–

COE2 indapp002

APPS-TRNS1.USA.COM>select count(*) from fnd_user@coe2;

COUNT(*)

———-

101

APPS-TRNS1.USA.COM>

Note the database link name created on this source / ERP system Oracle database for connecting

planning / destination server Oracle database.

Create database link on Destination system to Source system

First make necessary entry of the Source / Transaction instance Oracle Database in the tnsnames.ora

file of the Target / Planning Instance Oracle Database tier (TNS_ADMIN location).

Create Database link as follows:

create database link

connect to APPS identified by

using ‘’;

APPS-COE2.USA.COM>select INSTANCE_NAME, HOST_NAME from v$instance;

INSTANCE_NAME HOST_NAME

—————- ———————————————————–

COE2 indsapp002

APPS-COE2.USA.COM>show user

USER is “APPS”

APPS-COE2.USA.COM>ed

Wrote file afiedt.buf

1 create database link trns1

2 connect to apps identified by ****

3* using ‘trns1′

APPS-COE2.USA.COM>/

Database link created.

APPS-COE2.USA.COM>select INSTANCE_NAME, HOST_NAME from v$instance@trns1

2 ;

INSTANCE_NAME HOST_NAME

—————- ———————————————————–

TRNS1 indapp001

APPS-COE2.USA.COM>select count(*) from fnd_user@trns1;

COUNT(*)

———-

100

APPS-COE2.USA.COM>

Note the database link name created on this planning / destination Oracle Database server for

connecting to source / ERP system Oracle database.

Prepare the Source System

Create an Advanced Supply Chain Planner responsibility

Task By: Apps DBA

You must create a responsibility in the source (ERP) instance that conforms to the specifications.

Responsibility Name : Advanced Supply Chain Planner

Application : Oracle Manufacturing

Description : Used for running ASCP Report

Menu : SCP_TOP_4.0

Data Group Name : Standard

Application : Manufacturing

Request Group : All SCP Reports

Application : Oracle Master Scheduling/MRP

Responsibility key :

This responsibility is used to run the concurrent program Refresh Snapshot during all data collection

runs.

Warning: The responsibility name must match as “Advanced Supply Chain Planner” exactly.

Check Profile Option Name

Task By: Apps DBA and Functional Consultant

The Create Planning Flexfileds concurrent program creates new segment definitions in existing

descriptive flex fields to hold data that may be required for constrained and /or optimized planning.

The program will not populate profile values.

• MSO: Penalty cost factor for late demands (Organization) flexfield attribute

• MSO: Penalty cost factor for exceeding material capacity (Organization) flexfield

• MSO: Penalty cost factor for exceeding resource capacity (Organization) flexfield

• MSO: Penalty cost factor for exceeding transportation capacity (Organization)

• MSO: Penalty cost factor for exceeding resource capacity (Resource) flexfield

• MSO: Penalty cost factor for exceeding transportation capacity flexfield attribute

• MSO: Penalty cost factor for late forecasts

• MSO: Penalty cost factor for late sales orders

Create APS partition on the Source System

Task By: Apps DBA

Login to Oracle Applications 11i Source System.

Select “System Administrator” responsibility.

Navigate to Security Responsibility Request

Enter in the query mode in the “Request Group” screen and query for “All MSC Reports” .

Place cursor in the name column, Click the plus sign (Green +) on the toolbar to create a “New”

column.

In the name column select “CREATE APS PARTITIONS” (Make sure to select the correct one) and the

Save the record.

Switch responsibility to “Advanced supply chain planner”.

Navigate to Other Request

In the “Find Requests” screen click on the “Submit a New Request” “Single Request”.

Select “Create APS Partitions” request and submit it.

Check for the successful completion of this request.

Launch the Create Planning Flexfield Report

Task By: Functional Consultant

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 flexfield definitions. The list of values for each parameter lists only the available attributes

in the subject descriptive flexfield.

Matter

Create the Global Order Promising flexfilds.

Task By: Functional Consultant

[Not required this step in 11.5.10 and above]

Set up source data

Task By: Functional Consultant

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.

[Not required this step in 11.5.10 and above]

Set System Profile Values

Task By: Functional Consultant

If Global Order Promising is going to be utilized, the following two additional profile options must be

set.

MRP:ATP Database Link: [Database Link Name on the Source System for the Target System]

INV: External ATP : [None]

Prepare the Target System

Define the source instance to be collected from

Task By: Apps DBA

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.

Logged in to the Target (ASCP) System and choose “Advanced Planning Administrator”.

Navigate to Admin Instances. The Application Instances window appears.

Insert record for the Source (ERP) system as follows:

Instance Code : Give a new name for the Instance Code (uniquely identified).

Instance Type : Select “Discrete” (consult Functional Consultant).

Version : 11i (default, for 11i E Business Suite).

From Source to APS : Database Link created on the Source System for Target System Database.

From APS to Source : Database Link created on the Target System for Source System Database.

Check “Enable Flag”, “Allow ATP” and “Allow Release”.

GMT Difference : “-8” (this is Application location specific, consult Functional consultant).

Currency : USA (this is Application location specific, consult Functional consultant).

Assignment Set : (Kept this blank unless advised by Functional Consultant).

Save the record.

Enter the organizations on each of the instance from which to collect the Planning data and plan for on

the Planning Server by clicking Organization. For this click on the “Organizations” button.

The Organizations window appears.

Select the organizations for a particular instance. Be sure to select the master organization.

Close the Organization window.

Save the Instance Definition setup.

Final Setups and Refreshing Snapshots

Setups

Task By: Apps DBA

1. Make sure the responsible name on both source & destination are the same. Eg. “Advanced Supply

Chain Planner”.

2. Set Standard Manager to 15 [sysadmin Concurrent Manager Define] on both System and Target

Application system.

3. Set MRP Manager to 1 [sysadmin Concurrent Manager Define] on both System and Target

Application system.

4. Relink MSC,MRP module from adadmin on Target (ASCP) DB node.

5. Execute this request “Gather Schema Statistics” on Source (ERP) and Target (ASCP) node.

6. Set “MSC:Source Setup Required” to “Y” in Target (ASCP) System, set “N” in Source (ERP) System.

7. Run “Refresh Collection Snapshots” from Source (ERP) instance.

Execute the Refresh Snapshot concurrent program on the Source (ERP) System

Task By: Functional Consultant

The “Refresh Collection Snapshots” process must be run on the source (ERP) instance. 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.

References

Oracle Metalink.Notes

Note:226415.1: Oracle Advanced Planning and Scheduling Suite Release 11i Family Pack I About doc

Note:282678.1: About Oracle Advanced Supply Chain Planning in APS Family Pack I

Note:286852.1: Oracle Advanced Supply Chain Planning Release 11i Family Pack I About doc

Note:176030.1: APS Installation Checklist with Patchset G

Note:136734.1: Advanced Supply Chain Planning 11.5.3 Installation Checklist

Note:259322.1: About Oracle ASCP in the Oracle Supply Chain Management Family Pack J

Note:220304.1: Setting Up Instances For Data Collection Gives Partition Error ERR_GET_INSTANCES

Note:280052.1: Advanced Planning and Scheduling (APS) Implementation Notes & White Papers

Note:137293.1: How To Manage APS Partitions in the MSC Schema

Note:252108.1: How to Determine the Latest APS Rollup Patch Applied to the System

Note:209585.1: ASCP Planning Detail Report Installation and Configuration Instructions

Note:278055.1: Advanced Planning and Scheduling Requirements for 11.5.10 - Family Pack J

Note that the above mentioned notes were not necessarily used for ASCP Multi Node Installation, but

they were studied. The Note required by the patches applied above are listed in its respective column.

Popularity: 25% [?]

Share This

   

Readers who viewed this page, also viewed:

Once again about MWA/MCSA Mobile Web Application Tips Oracle Mobile Supply Chain Applications Step by Step build RAC : Part 1 : Install VMWare and Linux Collection of Queries/Scripts

31 users commented in " Oracle Advanced Supply Chain Planning (ASCP)multi node implementation "