Professional Documents
Culture Documents
1. Define organization
2. Setup Instance if the System is Decentralized
3. Run Data Collection
4. Assignment of responsibility
5. View Plan Options
How to Setup A New Organization So It Can Be Used In Advanced Supply Chain Planner
[ID 428640.1]
A: 1. Create a new organization and assign a 4/4/5 or 5/4/4 Calendar to the organization.
2. Create items and assigned to the new organization
3. Create Sourcing rules and assigned them.
4. Create Planning Parameters
-- NAV: Material Planner / Setup / Planning Parameters
5. Update the Instances / Organization region to enable the orgs for Data Collections
-- NAV: Advanced Planning Administrator / Admin / Instances - click on the Organizations
Tab and
add the organization to the list and enable for collections
6. Run Data Collection with a Complete Refresh
7. Assign the organization to the responsibilities that will need to use this organization:
-- NAV: Advanced Planning Administrator / Admin / Organization Security and assign the
correct
responsibilities
Search
Custom Search
Home
About Us
Book
Contact Us
Services
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;
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.
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.
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.
1. Log in to each concurrent processing server node as the owner of the Applications file
system.
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
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).
APPS-TRNS1.USA.COM>show user
USER is “APPS”
APPS-TRNS1.USA.COM>ed
Wrote file afiedt.buf
INSTANCE_NAME HOST_NAME
—————- ———————————————————–
COE2 indapp002
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.
INSTANCE_NAME HOST_NAME
—————- ———————————————————–
COE2 indsapp002
APPS-COE2.USA.COM>show user
USER is “APPS”
APPS-COE2.USA.COM>ed
Wrote file afiedt.buf
INSTANCE_NAME HOST_NAME
—————- ———————————————————–
TRNS1 indapp001
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.
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
“SingleIn the “Find Requests” screen click on the “Submit a New Request” 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
Logged in to the Target (ASCP) System and choose “Advanced Planning Administrator”.
Instances. The Application InstancesNavigate to Admin 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).
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.