1. Implementing Order Management
  2. Import and Export Your Processing Constraints

Import and Export Your Processing Constraints

We recommend that you test your processing constraints in a test environment. In this topic, learn how you can import and export processing constraints between environments, such as between your test environment and your production environment.

In this example, assume you must constrain the ORDER_ENTRY_SPECIALIST role from updating the Carrier attribute on a sales order but exclude the ORDER_MANAGER role from this constraint. You need this because updating the carrier might affect your operating costs, so you must limit these changes to the ORDER_MANAGER role.

Assume you created the CARRIER_UPDATE_NOT_ALLOWED constraint at some earlier point, and now must modify it. Here are its current values.

Attribute

Value

Constraint Name

CARRIER_UPDATE_NOT_ALLOWED

Constraint Entity

Order Fulfillment Line

Constraint Operation

Update

Attribute Name

Carrier

This topic uses predefined job roles. You must create your own job roles, depending on your security requirements. For details, see Privileges That You Need to Implement Order Management.

Export Your Processing Constraints

  1. Go to the Setup and Maintenance work area, then select the Order Management offering.

  2. In the Functional Areas list, click the row that says Orders.

  3. In the Orders area, click View > Columns, then add a check mark to the Actions option.

  4. In the Search Tasks window, search for Manage Processing Constraints.

  5. In the Task list, in the row that has Manage Processing Constraints in the Task column, click Actions > Export to CSV File > Create New.

  6. On the Export Setup Data to CSV File page, click Submit, then, in the Confirmation dialog, note the value of the process name, such as Manage Processing Constraints_20210212_062347_662.

  7. On the Setup page, in the row that has Manage Processing Constraints in the Task column, click Actions > Export to CSV File, then notice the status that displays.

    If the status says Processing, then wait for it to finish. If the status says Ready for Download, then click Ready for Download.

  8. On the Export Setup Data to CSV File Results page, click Actions > Download > CSV File Package.

  9. In the dialog that displays, select the option to save as a file, then click OK.

  10. Use your browser to access the download location. It depends on your browser. For example, in Firefox, click the down arrow on the top banner.

  11. Notice that the download creates a single zip file that contains several csv files. Extract these files to a folder of your choice.

Modify Your Processing Constraints

  1. Edit the ORA_DOO_CONSTRAINT_ASSIGN.csv file to assign roles to the constraint.

    Attribute

    Value

    ORA_DOO_CONSTRAINT_SETUP.ConstraintName

    CARRIER_UPDATE_NOT_ALLOWED

    RoleCommonName

    ORDER_ENTRY_SPECIALIST

  2. Edit the ORA_DOO_CONSTRAINT_EXCLUSION.csv file to exclude roles from the constraint.

    Attribute

    Value

    ORA_DOO_CONSTRAINT_SETUP.ConstraintName

    sru_shippingmeth

    RoleCommonName

    ORDER_MANAGER

  3. Save your changes to the zip file.

Import Your Processing Constraints

  1. On the Setup Order Management page, In the Search Tasks window, search for Manage Processing Constraints.

  2. In the Task list, in the row that has Manage Processing Constraints in the Task column, click Actions > Import from CSV File > Create New.

  3. On the Import Setup Data to CSV File page, browse to the zip file you modified, then click Submit.

  4. On the Setup page, in the row that has Manage Processing Constraints in the Task column, click Actions > Import from CSV File, then notice the status that displays.

  5. Wait for the status to change from Importing Setup Data to Ready for Data Validation.

  6. Click the Ready for Data Validation status.

  7. On the Import Setup Data from CSV File Results page, verify the value.

    Attribute

    Value

    Status

    Completed Successfully

  8. Expand the Business Objects area, then click the arrow in the Go to Task column.

  9. On the Manage Processing Constraints page, verify that you can see the role you added.

Note

  • The export doesn't export predefined processing constraints. It only exports constraints that you create. So, if the Predefined option on the Manage Processing Constraints page contains a check mark, then you can't modify any part of the constraint.

  • The Manage Processing Constraints task in the Setup and Maintenance work area manages the relationships for you, such as between the constraint, conditions, rule set, record set, and so on. If you import or export, then you must manage these relationships manually in the csv files.

  • Import and export the entire package of csv files as a single zip file. This will help maintain relationships between files. Don't import and export individual csv files or a subset of them.

  • Only import data that exists in Oracle Applications. For example, if you import a role named MY_ROLE, then make sure MY_ROLE exists in Oracle Applications and that its active. If necessary, use the Security Console to add the role and make it active, or don't include the role in your import file. If you include the role, then make sure it matches the value of the RoleCommonName attribute from the Security Console.

Descriptions of the Files

Here are the files that the package contains.

File

Description

ASM_SETUP_CSV_METADATA.xml

Contains the metadata for the virtual object that the download creates. You must not modify this file.

DOO_CHANGE_CONSTRAINT_DEF.csv

Contains all the record sets that you create or reference from your constraints.

ORA_DOO_CONSTRAINT_ASSIGN.csv

Creates a relationship between each constraint on the Constraints tab and the roles in the Constrained Roles area of the Constraints tab.

ORA_DOO_CONSTRAINT_CONDITION.csv

Creates a relationship between each constraint on the Constraints tab of the Manage Processing Constraints page, such as Constraint Name, and data on the Conditions tab, such as Group Number, Message, Enabled, and so on.

ORA_DOO_CONSTRAINT_EXCLUSION.csv

Creates a relationship between each constraint on the Constraints tab and the roles in the Excluded Roles area of the Constraints tab.

ORA_DOO_CONSTRAINT_RECORD_SET_COLUMN.csv

Contains a record set that you use for a conditional constraint.

ORA_DOO_CONSTRAINT_SETUP.csv

Contains details for each constraint from the Constraints tab of the Manage Processing Constraints page, such as the Constraint Name, Constrained Operation, Enabled, On Operation Action, Applicable Roles, and so on.

It also contains other attributes that you can't set on the Manage Processing Constraints page, such as the effective dates.

The csv file contains these columns but the Manage Processing Constraints page doesn't. Remove these columns from the .csv file.

ORA_DOO_CONSTRAINT_VALIDATION_TEMPLATE.csv

Creates a relationship between the constraints and the validation rule sets.

Contains details from the Validation Rule Sets tab of the Manage Processing Constraints page, such as the Short Name, Validation Type, and so on.

ORA_DOO_CONSTRAINT_VALIDATION_TEMPLATE_COLUMN.csv

Creates a relationship between constraints on the Constraints tab and data in the Details area of the Validation Rule Sets tab, such as Attribute Name, Validation Operation, and Value String.

Related Topics