Oracle Value Chain Planning (VCP) Instance Setup

VCP modules can be implemented on the same instance where other modules like Order Management, Purchasing, Field Service etc are implemented. But, the regular practice is to use a distributed system.
In a distributed environment we implement VCP on a separate instance (called the destination instance) and bring in the data required for VCP from another instance called the Source Instance.

VCP Instance setup steps

Create the source instance entry into VCP.
           A single VCP instance can plan for many source instances. Every source instance has a unique 'Instance Code' which we give as the entry while creating the 'Application Instances'.

   Functional Setup:
       Navigation - Service Supply Chain Administrator --> Admin --> Instances 

       Important Fields: 
       Instance Code         -- Unique Source Instance Code
        Version                   -- Version of Source Instance. (Ex: R12.1)
        From Source to APS  -- Database Link to get data from source to APS   
                                        (VCP is formerly called as APS -- Advanced Planning Suite)
        From APS to Source  -- Database Link to get data from APS to Source

  Below figure showing the Form for setting up Instance in VCP.

    Technical Details: 

    The entry made into the above form will get saved into the table

        

             MSC_APPS_INSTANCES

     Important columns:

     INSTANCE_CODE

     INSTANCE_ID

     A2M_DBLINK     -- Database Link to get data from source to VCP

     M2A_DBLINK     -- Database Link to get data from APS to Source

     SQL Query:

     SELECT instance_code, 

          instance_id,

          a2m_dblink,

          m2a_dblink

     FROM msc_apps_instances;