Copy Setups Between Instances of Order Management
Copy your setup from one instance of Order Management into another instance during the lifecycle of your Order Management deployment. For example, migrate your setup from a test environment to a production environment.
-
Use the Manage Configuration Packages page in the Setup and Maintenance work area to export and import a configuration package.
-
Learn about the list of business rules that the copy migrates. For details, see Migrate Business Rules in Order Management.
-
Learn about the approval rules you can migrate. For details, see Migrate Approval Rules Between Instances of Order Management.
-
You can use WebLogic Scripting Tool (
WLST
) commands to move order orchestration rules. Order Management stores order orchestration rules in the Metadata Services (MDS) Repository. You can also use data collection and interface tables to import your setup and your transaction data. For details, go to Implementing Common Features for Oracle SCM, then see the chapter that describes import and export. -
The migration adds hold codes that you set up in the source instance to hold codes that exist in the target instance. If the same hold codes exist in the source and target, then the holds in the source replace the holds in the target.
-
The migration doesn't migrate holds that apply a credit check hold or release a credit check hold.
-
The migration migrates only your set ups. It doesn't migrate transactional data, such as sales orders.
-
Don't modify the orchestration process name, task name in an orchestration process step, or the status rule set name in either environment. Modifying the name might prevent Order Management from updating references to other data in the orchestration process. For details, see:
-
If you created an order management extension, then prepare it before you migrate. For details, see Overview of Creating Order Management Extensions.
-
If you migrate from a production environment to a test environment, and if your migration includes an orchestration process that's currently in progress, then the sales order that references the process will become stuck. It isn't possible to recover the stuck order.
-
The migration migrates only your set ups. It doesn't migrate transactional data, such as sales orders.
Summary of the Steps
-
Export your setup.
-
Import your setup.
-
Deploy flexfields.
Export Your Setup
Export your setup from the source instance of Order Management.
-
Make sure the source instance and the target instance are at the same release level.
-
Sign into the source instance of Order Management with administrative privileges.
-
Go to the Setup and Maintenance work area.
-
On the Setup page, click Tasks > Manage Configuration Packages.
-
On the Manage Configuration Packages page, click Actions > Create.
-
On the Enter Basic Information page, set the values, then click Next.
Attribute
Value
Name
Select the name of the implementation project that defines the source instance.
Export
Setup task list and setup data
-
On the Select Objects for Export page, accept default values, then click Next.
The Select Objects for Export page comes predefined to select the objects that the export needs to support most instances of Order Management. For details, see Copy Setups Between Instances of Order Management.
-
On the Schedule and Notifications page, accept the default value, click Submit, then, in the Warning dialog, click Yes.
Attribute
Value
Run
As soon as possible
-
On the Manage Configuration Packages page, examine results in the elements, then sign out.
Element
Description
Export Setup Data button
Export a configuration package after you create it. The export identifies setup data according to the export definition and adds it to the configuration package.
Export a configuration package more than one time. Each export creates a different configuration package version that you can manage individually.
Download Latest Version
Download the most recent version of the configuration page.
Export and Import Processes area
Get details of the export or import for each configuration package.
Status
Examine the process status for each implementation project.
Click the status to get details about each step of the export or import process.
Download
Download a version so you can use it during an export or import.
Setup Data Report
View or download a report that contains the setup data exported to the configuration package, including the business objects processed and details about errors that happened.
Import Your Setup
Import your setup into the target instance of Order Management.
-
Sign into the target instance of Order Management with administrative privileges.
-
Go to the Setup and Maintenance work area.
-
On the Setup page, click Tasks > Manage Configuration Packages.
-
On the Manage Configuration Packages page, in the search results, click the row that contains the configuration package you must update.
-
In the Export and Import Processes area, click Import Setup Data.
-
On the Enter Basic Information page, accept default values, then click Next.
-
On the Select Pauses for External Import page, click Submit.
The import process.
-
Adds setup data that doesn't already exist in the target configuration package. It adds setup data from the source configuration package into the target configuration package.
-
Updates setup data that already exists in the target package with modifications from the source package.
-
Doesn't delete existing setup.
-
Doesn't modify setup that exists in the target instance but not in the source instance.
-
-
Restart the server that hosts the target instance.
Deploy Flexfields
You must deploy each flexfield that you import.
Get details about:
-
How to handle objects that aren't flexfields after the import, go to Implementing Common Features for Oracle SCM, then see the chapter that describes import and export.
-
Flexfields, see Set Up Extensible Flexfields in Order Management.
Deploy flexfields.
-
In the Setup and Maintenance work area, go to the task.
-
Offering: Order Management
-
Functional Area: Orders
-
Task: Manage Order Extensible Flexfields
-
-
On the Manage Order Extensible Flexfields page, identify each flexfield where the deployment status isn't Deployed, then deploy it.
-
Repeat steps 1 and 2 on each of these pages, as necessary.
-
Manage Item Revision Descriptive Flexfields
-
Manage Units of Measure Descriptive Flexfields
-
Manage Item Descriptive Flexfields
-
Manage Item Revision Descriptive Flexfields
-
Manage Item Relationship Descriptive Flexfields
-
Manage Trading Partner Item Descriptive Flexfields
-
Manage Catalog Descriptive Flexfields
-
Manage Category Descriptive Flexfields
-
Manage Source System Descriptive Flexfields
-
Manage Order Descriptive Flexfields
-
Manage Pricing Descriptive Flexfields
-
-
Sign into Oracle Enterprise Manager.
For details about Oracle Enterprise Manager, see https://www.oracle.com/technetwork/oem/enterprise-manager/overview/index.html.
-
In the navigation tree, select SOA Infrastructure, then click UpdateSOAMDS.
-
On the UpdateSOAMDS page, set the values.
Attribute
Description
Operation
Set to updateDuring.
Value
This Value attribute resides in a row in the
Input Arguments
area, in Tree View. The value for Name in the row is*payload
, and the Type is duration.Specify the time frame that has elapsed since the last time you deployed the flexfields. Use this format.
PXMYD
where
-
X. Number of months that have elapsed.
-
Y. Number of days that have elapsed.
For example, if one month and one day have elapsed since the last time you deployed flexfields, then use this format.
P1M1D
You can specify only the month, only the days, or months and days.
-
-
Run the UpdateSOAMDS composite to synchronize SOA (Service Oriented Architecture) with flexfields in Order Management.
-
Go to the Scheduled Processes work area.
-
On the Scheduled Processes page, click Schedule New Process, then run the Publish Extensible Flexfield Attributes scheduled process.