\n\u2022 Holistic Optimization, Planning, and Scheduling<\/strong>. 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.
\n\u2022 Finite Capacity Planning and Scheduling<\/strong>. Oracle ASCP generates feasible supply chain plans that consider both resource and material constraints.
\n\u2022 Optimization<\/strong>. Users can easily configure Oracle ASCP to optimize specific business criteria. No programming is necessary to access Oracle ASCP’s powerful mathematical optimization capabilities.
\n\u2022 Backward Compatibility<\/strong>. Oracle ASCP’s component architecture allow it to be deployed against any combination of Oracle 11 and Oracle 11i transaction systems.
\n\u2022 Workflow-Driven Exception Messaging<\/strong>. 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.
\n\u2022 Global Accessibility<\/strong>. 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.
\n\u2022 Integrated Planning and Execution<\/strong>. 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.
\n\u2022 Simulation Capability<\/strong>. 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\u2019s Workbench. Unlimited numbers of scenarios can be simulated and compared using online planning, copy plans, and exceptions.
\nObjective
\n<\/u><\/strong>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.<\/p>\n
Assumption \/ Pre implementation requirements 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.<\/p>\n Both source and destination database instances must be on the same major release of the Oracle database;<\/p>\n We are going to do a two machine ASCP implementation.<\/p>\n The basic requirement for both the machines is that of Oracle 11i E Business Suit.<\/p>\n Source System also called as \u201cERP System\u201d and \u201cTransaction System\u201d. Both the Oracle Applications 11i E-Business Suite are on release 11.5.10.2. If these patches have any prerequisite patches, you will have to apply all the prerequisite patches before applying the main patches.<\/p>\n 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.<\/p>\n 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 \u201cAPPS\u201d user.<\/p>\n SET LINESIZE 120 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\u2019t require applying this patch.<\/p>\n 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.<\/p>\n Do the required pre install steps before applying each patch and then after applying do the post-installation steps. 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.<\/p>\n Sr. No. Patch Note Required (Y\/N) Pre-requisites Hence the sequence of applying the patches is as follows<\/strong>: Patch the Destination (ASCP) system 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.<\/p>\n Sr. No. Patch Note Required (Y\/N) Pre-requisites ILOG Libraries and Executables 1. Log in to each concurrent processing server node as the owner of the Applications file system.<\/p>\n 2. If the $SHT_TOP\/lib\/ilog\/5.1 directory already exists, backup any files or directories that it contains.<\/p>\n 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.<\/p>\n 4. Change directories to $SHT_TOP\/lib\/ilog\/5.1\/SUN_OS5.<\/p>\n 5. Copy the library files from the current directory to the $SHT_TOP\/lib\/ilog\/5.1 directory. 6. Use AD Administration to relink these executables [Under DB Node]:<\/p>\n i. Oracle Constraint Based Option (MSO): MSONEW 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.<\/p>\n 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).<\/p>\n Create Database link as follows<\/strong>: APPS-TRNS1.USA.COM>select INSTANCE_NAME, HOST_NAME from v$instance;<\/p>\n INSTANCE_NAME HOST_NAME APPS-TRNS1.USA.COM>show user APPS-TRNS1.USA.COM>ed 1 create database link coe2 Database link created.<\/p>\n APPS-TRNS1.USA.COM>select INSTANCE_NAME, HOST_NAME from v$instance@coe2;<\/p>\n INSTANCE_NAME HOST_NAME APPS-TRNS1.USA.COM>select count(*) from fnd_user@coe2;<\/p>\n COUNT(*) APPS-TRNS1.USA.COM><\/p>\n Note the database link name created on this source \/ ERP system Oracle database for connecting planning \/ destination server Oracle database.<\/p>\n Create database link on Destination system to Source system<\/strong> Create Database link as follows:<\/p>\n create database link APPS-COE2.USA.COM>select INSTANCE_NAME, HOST_NAME from v$instance;<\/p>\n INSTANCE_NAME HOST_NAME APPS-COE2.USA.COM>show user 1 create database link trns1 Database link created.<\/p>\n APPS-COE2.USA.COM>select INSTANCE_NAME, HOST_NAME from v$instance@trns1 INSTANCE_NAME HOST_NAME APPS-COE2.USA.COM>select count(*) from fnd_user@trns1;<\/p>\n COUNT(*) APPS-COE2.USA.COM><\/p>\n Note the database link name created on this planning \/ destination Oracle Database server for connecting to source \/ ERP system Oracle database. Responsibility Name : Advanced Supply Chain Planner This responsibility is used to run the concurrent program Refresh Snapshot during all data collection runs.<\/p>\n Warning: The responsibility name must match as \u201cAdvanced Supply Chain Planner\u201d exactly. 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.<\/p>\n \u2022 MSO: Penalty cost factor for late demands (Organization) flexfield attribute Create APS partition on the Source System Place cursor in the name column, Click the plus sign (Green +) on the toolbar to create a “New” column. Switch responsibility to “Advanced supply chain planner”. In the \u201cFind Requests\u201d screen click on the \u201cSubmit a New Request\u201d \uf0e8 \u201cSingle Request\u201d. Launch the Create Planning Flexfield Report Create the Global Order Promising flexfilds. Set up source data Prepare the Target System Logged in to the Target (ASCP) System and choose \u201cAdvanced Planning Administrator\u201d.
\n<\/u><\/strong>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.<\/p>\n
\nDestination System also called as \u201cASCP System\u201d and Planning System\u201d.<\/p>\n
\nPatching the Source System (ERP System) and the Destination (ASCP system)
\nTask By: Apps DBA
\n<\/u><\/strong>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.<\/p>\n
\nCOLUMN APPLICATION_SHORT_NAME FORMAT A20
\nSELECT
\nBUG_ID, APPLICATION_SHORT_NAME, BUG_NUMBER, CREATION_DATE, ARU_RELEASE_NAME
\nFROM AD_BUGS
\nWHERE BUG_NUMBER LIKE ‘%&BUG_NUMBER%’
\nORDER BY 4<\/p>\n
\nPatch the Source System (ERP System)
\n<\/strong>The following patches are required to be applied on the Source system:
\n1. 4185358
\n2. 2700001
\n3. 3551142
\n4. 4183434
\n5. 4240365
\n6. 4039921
\n7. 4392144
\n8. 4366346
\n9. 4863176<\/p>\n
\n<\/strong>1. 4185358 Y None for 11.5.10.2
\n2. 2700001 N NR for 11.5.10.2
\n3. 3551142 Y None
\n4. 4183434 N NR for 11.5.10.2
\n5. 4240365 278055.1 Y None for 11.5.10.2
\n6. 4039921 N NR for 11.5.10.2
\n7. 4392144 278055.1 Y None for 11.5.10.2
\n8. 4366346 278055.1 Y 3629717
\n9. 3629717 Y None for 11.5.10.2
\n10. 4863176 Y None for 11.5.10.2<\/p>\n
\n1. 4185358
\n2. 3551142
\n3. 4240365
\n4. 4392144
\n5. 3629717
\n6. 4366346
\n7. 4863176<\/p>\n
\n<\/strong>The following patches are required to be applied on the Destination system:
\n1. 4185358
\n2. 4231863
\n3. 4210584
\n4. 4359934
\n5. 4392144
\n6. 4366346
\n7. 4392231
\n8. 4039921
\n9. 4523322<\/p>\n
\n1. 4185358 278055.1 Y None for 11.5.10.2
\n2. 4231863 278055.1 Y 4185358
\n3. 4210584 Y None
\n4. 4359934 278055.1 Y 4185358
\n5. 4392144 278055.1 Y None for 11.5.10.2
\n6. 4366346 278055.1 Y 3629717
\n7. 3629717 Y None
\n8. 4392231 Y None
\n9. 4039921 N NR for 11.5.10.2
\n10. 4523322 278055.1, 278052.1 Y 4392231, (4863176 on Source Side),
\n11. 4297568 Y None
\nHence the sequence of applying the patches is as follows:
\n<\/strong>1. 4185358
\n2. 4231863
\n3. 4210584
\n4. 4359934
\n5. 4392144
\n6. 3629717
\n7. 4366346
\n8. 4392231
\n9. 4039921
\n10. 4523322
\n11. 4297568<\/p>\n
\n<\/strong>The patch 4297568 is for \u201cILOG Libraries and Executables\u201d. Apply this patch only if you are using 11.5.10.2.<\/p>\n
\nOn UNIX Sun Solaris, the files are
\ni. libconcert.a
\nii. libcplex.a
\niii. libhybrid.a
\niv. libilocplex.a
\nv. libschedule.a
\nvi. libsolver.a<\/p>\n
\nii. Oracle Inventory Optimization (MSR): MSRNEW
\niii. Oracle Manufacturing Scheduling (WPS): WPCWFS
\niv. Oracle Work in Process (WIP): WICDOL, WICMEX, WICMLX
\nCreate Database link
\nTask By: Apps DBA
\nCreate database link on Source system to Destination system
\nA 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.<\/p>\n
\ncreate database link
\nconnect to APPS identified by
\nusing \u2018\u2019;<\/p>\n
\n—————- ———————————————————–
\nTRNS1 indsapp001<\/p>\n
\nUSER is “APPS”<\/p>\n
\nWrote file afiedt.buf<\/p>\n
\n2 connect to apps identified by *****
\n3* using ‘coe2’
\nAPPS-TRNS1.USA.COM>\/<\/p>\n
\n—————- ———————————————————–
\nCOE2 indapp002<\/p>\n
\n———-
\n101<\/p>\n
\nFirst 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).<\/p>\n
\nconnect to APPS identified by
\nusing \u2018\u2019;<\/p>\n
\n—————- ———————————————————–
\nCOE2 indsapp002<\/p>\n
\nUSER is “APPS”
\nAPPS-COE2.USA.COM>ed
\nWrote file afiedt.buf<\/p>\n
\n2 connect to apps identified by ****
\n3* using ‘trns1’
\nAPPS-COE2.USA.COM>\/<\/p>\n
\n2 ;<\/p>\n
\n—————- ———————————————————–
\nTRNS1 indapp001<\/p>\n
\n———-
\n100<\/p>\n
\nPrepare the Source System
\n<\/u>Create an Advanced Supply Chain Planner responsibility
\nTask By: Apps DBA<\/strong>
\nYou must create a responsibility in the source (ERP) instance that conforms to the specifications.<\/p>\n
\nApplication : Oracle Manufacturing
\nDescription : Used for running ASCP Report
\nMenu : SCP_TOP_4.0
\nData Group Name : Standard
\nApplication : Manufacturing
\nRequest Group : All SCP Reports
\nApplication : Oracle Master Scheduling\/MRP
\nResponsibility key :<\/p>\n![](\"https:\/\/onlineappsdba.com\/wp-content\/uploads\/2008\/06\/sc1.bmp\")
<\/a><\/p>\n
\nCheck Profile Option Name
\nTask By: Apps DBA and Functional Consultant<\/p>\n
\n\u2022 MSO: Penalty cost factor for exceeding material capacity (Organization) flexfield
\n\u2022 MSO: Penalty cost factor for exceeding resource capacity (Organization) flexfield
\n\u2022 MSO: Penalty cost factor for exceeding transportation capacity (Organization)
\n\u2022 MSO: Penalty cost factor for exceeding resource capacity (Resource) flexfield
\n\u2022 MSO: Penalty cost factor for exceeding transportation capacity flexfield attribute
\n\u2022 MSO: Penalty cost factor for late forecasts
\n\u2022 MSO: Penalty cost factor for late sales orders<\/p>\n
\nTask By: Apps DBA<\/strong>
\nLogin to Oracle Applications 11i Source System.
\nSelect \u201cSystem Administrator\u201d responsibility.
\nNavigate to Security \uf0e8 Responsibility \uf0e8 Request
\nEnter in the query mode in the \u201cRequest Group\u201d screen and query for \u201cAll MSC Reports\u201d .<\/p>\n<\/a><\/p>\n
\nIn the name column select “CREATE APS PARTITIONS” (Make sure to select the correct one) and the Save the record.<\/p>\n
\nNavigate to Other \uf0e8 Request<\/p>\n<\/a><\/p>\n
\nSelect \u201cCreate APS Partitions\u201d request and submit it.
\nCheck for the successful completion of this request.<\/p>\n
\nTask By: Functional Consultant<\/strong>
\nLaunch 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.
\nMatter<\/p>\n
\nTask By: Functional Consultant<\/strong>
\n[Not required this step in 11.5.10 and above]<\/p>\n
\nTask By: Functional Consultant
\n<\/strong>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.
\n[Not required this step in 11.5.10 and above]
\nSet System Profile Values
\nTask By: Functional Consultant<\/strong>
\nIf Global Order Promising is going to be utilized, the following two additional profile options must be set.
\nMRP:ATP Database Link: [Database Link Name on the Source System for the Target System]
\nINV: External ATP : [None]<\/p>\n
\n<\/u>Define the source instance to be collected from
\nTask By: Apps DBA<\/strong>
\nThe 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.<\/p>\n
\nNavigate to Admin \uf0e8 Instances. The Application Instances window appears.
\nInsert record for the Source (ERP) system as follows:
\nInstance Code : Give a new name for the Instance Code (uniquely identified).
\nInstance Type : Select \u201cDiscrete\u201d (consult Functional Consultant).
\nVersion : 11i (default, for 11i E Business Suite).
\nFrom Source to APS : Database Link created on the Source System for Target System Database.
\nFrom APS to Source : Database Link created on the Target System for Source System Database.
\nCheck \u201cEnable Flag\u201d, \u201cAllow ATP\u201d and \u201cAllow Release\u201d.
\nGMT Difference : \u201c-8\u201d (this is Application location specific, consult Functional consultant).
\nCurrency : USA (this is Application location specific, consult Functional consultant).
\nAssignment Set : (Kept this blank unless advised by Functional Consultant).<\/p>\n