PDC ImportExport Charge Selector Validation Error For Big Input Xml Files (Doc ID 2796329.1)

Last updated on FEBRUARY 07, 2024

Applies to:

Goal

We have a situation when we export the config and pricing components from production environment and an attempt to import the output xml files fail on a test env.

The situation is as follows:

- there is already an old version of pricing in the test environment
- on production env some paths are removed from value maps
- when trying to import charges and charge selectors there are more than one changeset created due to split by 999 pricing objects
- the first changeset to be validated seems to contain only charges. Since the charges affect charge selectors a validation on the charge selectors is executed but the new definition of charge selectors are in the second changeset so it validates against the old versions containing paths in value maps that are no longer there - the changeset validation fails even though the input xml file contains both the charges and the new charge selectors versions. To me it seems that there should not be a validation of charge selectors vs value maps if only the charge is imported though hard to implement.
The second solution would be increasing the number of xml pricing objects in one set so there is no split - where can we do it? I couldn't find any place to set to a bigger number.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.