Given System “A” with BRM and PDC and System “B” with BRM and PDC, following is the process for moving new or changed pricing data from system A to system B.
1. Load new/changed BRM configuration objects from BRM A to BRM B, in particular, the following objects that are mastered in BRM:
a. Provisioning Tagsb. GLIDs
c. Tax Codes
d. Tax Supplier
e. Events
f. Service
g. Account
2. Follow this step if you have made any name changes in PDC for these objects. If no name changes have been made, you can skip this step and go directly to Step 3. Export the Event attribute spec, Customer attribute spec, Product (aka Service) attribute spec and Profile attribute spec [if using ECE] from PDC A.
ImportExportPricing -export -config EVENT_ATTRIBUTE_SPEC
ImportExportPricing -export -config CUSTOMER_ATTRIBUTE_SPEC
ImportExportPricing -export -config PRODUCT_ATTRIBUTE_SPEC
ImportExportPricing -export –config PROFILE_ATTRIBUTE_SPEC [Applicable for ECE only]
These commands will generate 3 export files. (4 if ECE is used)
Import the exported attribute specs into PDC B
a. The internal IDs for the objects should not be changed.
b. Make sure that the transformation engines are running in so that the xref tables are updated.
c. Follow the same order as export.
ImportExportPricing -import -config export_config_attributes.xml
3. Start SyncPDC
If the Event, Service, and Account objects have already been moved from PDC A to PDC B (steps 2 and 3), this will only sync the other 4 objects from BRM because SyncPDC will know that the Event, Service, and Account objects have already been sync’ed.
4. Move configuration objects mastered in PDC.
a. Export configuration objects: This export should NOT include the objects mastered in BRM which have already been moved in steps 1-4.
ImportExportPricing -export -config <TYPE>
Types are: GEO_ZONE_MODEL, STANDARD_ZONE_MODEL, ZONE_MAP, ZONE_RESULT_CONFIGURATION, RUM_CONFIGURATION, ATTRIBUTE_SPEC_MAP, BALANCE_ELEMENT, HOLIDAY_CALENDAR, CUSTOM_ANALYZER_RULE[Applicable for ECE only]
Invoke these commands up to 9 times, generating as many export files.
b. Import configuration objects into PDC B. Observe the following ordering when importing:
- Import the service event map (AttributeSpecMap) last
- Load ZONE_RESULT_CONFIGURATION before both GEO_ZONE_MODEL and STANDARD_ZONE_MODEL
ImportExportPricing -import -config <exported file name>
5. Move pricing objects.
a. Export all pricing from PDC A
ImportExportPricing -export -pricing
This creates a file called: export_pricing.xml
b. Import all pricing into PDC B
ImportExportPricing -import -pricing <exported file name>
