Welcome to Release 12.2 of the Oracle Application Integration Architecture Oracle Value Chain Planning Integration Base Pack Implementation Guide.
See Related Information Sources for more Oracle Applications product information.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
This chapter discusses the batch integration process between JDE E1 or PeopleSoft and Value Chain Planning and includes details about:
This chapter describes how implementers can address common scenarios with the VCP Base Pack integration.
Note: This chapter does not pertain to PeopleSoft users.
Note: This chapter does not pertain to PeopleSoft users.
This chapter provides an overview of Demantra integration and discusses how to:
Note: This chapter does not pertain to JDE EnterpriseOne users.
This chapter discusses configuration steps that must be completed before using Oracle Demantra with this integration. The steps include:
Set up database directories
Run concurrent programs
Update profiles
Add additional Demantra levels (optional)
To facilitate the integration, certain one-time setup steps and configurations must be performed to the Oracle EBS planning server.
Additional Information: For additional information, see the Oracle Value Chain Planning Implementation Guide.
This chapter discusses setting up the ODI web service for Global Order Promising.
User-maintained data is data that is needed for planning purposes but is not available in the ERP extracts. In releases prior to 12.2.5.1, user-maintained data was managed using a spreadsheet. Staring with the 12.2.5.1 release this data is maintained using the Manage Integration Parameters user interface.
This chapter provides information about accessing and running JD Edwards EnterpriseOne or PeopleSoft collections. PeopleSoft users are restricted to those relating to Demantra Demand Management and have their own menu containing this restricted set of options.
This chapter assumes that the JDE or PeopleSoft extracts have been performed or are part of a pre-process script. The import processes is run separately or as part of a post-process.
This section details possible VCP Base Pack Integration failure points.
The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the Oracle E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.
Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle E-Business Suite data unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an Oracle E-Business Suite form can update many tables at once. But when you modify Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite automatically checks that your changes are valid. Oracle E-Business Suite also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.