Product Catalog deployment known facts and system behavior

General deployment facts

• Deploy Product Catalog as a standalone component for best performance results. For more information, see Product Recommendation.
• Product Catalog deployments are deployed at the product level.
  For example,
  If a product is configured in both the source and target, the rate plan differs, the rate plan charges are selected for deployment, and then the complete product payload is deployed. A validation checkpoint is available to stop creating the already available rate plans and rate plan charges to avoid duplications.
• Deploying a product catalog is a synchronous and asynchronous workflow. When you submit a comparison job between source and target, it is queued at the backend. At this stage, the job status is "Submitted." You can submit a maximum of 50 comparison jobs per environment.
• If the comparison job takes more than 30 minutes, it is canceled, and its status is displayed as "Canceled."
• The compared jobs are stored in the Deployment Manager for 24 hours from when they were completed. After that, the system auto-deletes them.
• Deployment Manager supports deploying 2800 products, 300 Rate Plans(for each per product), and 300 (for each per product) Rate Plan Charges. The system will pick the products, rate plans, and rate plan charges based on the last modified date.
• The current version of the Product Catalog does not support Product Features, Price Books, and Catalog Groups.
• Deployment Manager does not support migration of the following fields for the Product Catalog:
  • Prepaid Quantity
  • Prepaid Total Quantity
  • Prepaid UOM
• Deployment Manager does not support migration of Prepaid Dropdown fields for Product Rate Plans.
• Product Catalog has a validation that allows you to create products only when the difference between the SKU numbering varies by 2. If there are exceptions to this validation, the product is not created successfully in the target.

For example,

In this scenario, the recommendation is to deploy by selecting "Auto-Generating SKU" option.

• If the user selects the “All” button on the compare screen, all the products from the source tenant will be selected for deployment. The user will not be able to deselect any product. In such a case, the products will be disabled for selection on the compare screen.
• Configure the following revenue codes associated with RevPro manually:
  • Contract Asset
  • Contract Liability
  • Unbilled Receivables 
  • Adjustment Liability
  • Recognized Revenue
  • Adjustment Revenue
• The following Revenue fields can be deployed through API. See CRUD: Create a product rate plan charge, for more information.
  • Product Class
  • Product Family
  • Product Line
  • Allocation Eligible
  • POB Policy

Comparison and deployment scenarios

Known system behavior with natural keys or product number

• Always standardize the prefix for Product Number in source and target tenant. A difference in the configurations of prefixes in source and target will result in comparison being displayed as different every time.

• In the pre-deployment phase, the tenant is configured with a set of products, rate plans, and rate plan charges. Subsequently, during the post-deployment phase, newly introduced products, rate plans, and rate plan charges will be assigned incremental product numbers derived from the latest numbers already present in the target tenant. It is recommended to select auto-generate Product Number in this scenario. If not, the system will throw a validation error.

• When deploying products in the target tenant which does not have existing products, rate plans, rate plan charges, either the clone of Product Number or auto generate product number options may be selected for deployments.

• If deploying a newly configured product, rate plan or rate plan charge between tenants that have been already baselined accurately and up-to-date, the option of cloning product number from source to target may be selected.