Multiple Output Rows from a single Input Row

-
Question Received: How do we use the CC&B Conversion Mapping tools to create several rows in a staging table for one row in a source input table? For example, if we have an account with one service in the legacy system, this may be represented by several service agreements in CC&B. We create one CI_ACCT row for the Legacy System Account. We then need to create several CI_SA rows under it.
In some cases we will know the specific details of each row that must be created with a specific type of service eg water usage, drainage.
In other cases we may have an unknown number of rows to create.


Answer: The option of creating multiple input rows in CC&B for a single source row is accomplished by specifying multiple mapping sources (relating to the same input table). I am not sure that I understand how you could have an 'unknown' number of transactions to create, there has to be a business or conversion rule that specifies what records of defined types are required. this will drive the number of mapping sources and the associated column mapping rules for each.

Comments

Post a Comment

Popular posts from this blog

Database Upgrades and their impact on Conversion

-
Hint: It appears that the current strategy in relation to application of Single Fixes and Service Packs no longer supports application of these scripts against a staging schema (at least as part of CC&B 2.x.x). As a result it is recommended that you drop and rebuild the Conversion schema from the Production instance once this has been upgraded with the latest patch-sets. We have also noted that application of these single fixes may require a redelivery of all custom java code from the development environment, since the java compilation is not performed as part of the patch install process (unlike the Cobol implementation process).
Read more

Embedding web-based external applications within the framework.

-
Image
My current project contained a requirement to embed an external application within the the CC&B framework and initiate calls to this application supplying a number of context elements to ensure that the correct information is displayed. The client also requested that the application be 'skinned' to maintain the CC&B look-and-feel. This is how we implemented it.. Defined a number of Business Object to manage retrieval of data from some of the base CC&B objects in a flattened format (ie. Characteristics mapped to descriptive elements, unused fields not defined, etc). Defined a UI map which forms the canvas for 'painting' the application within our framework. A Query Zone to ensure that the required data associated with the Context Zones are retrieved (using Zone type F1-DE-QUERY). A Business Service to wrap the call to the Query Zone into a usable service. A Script to initiate the call to the Business Service with the associated Context Identifiers (fr...
Read more

Bundle Corrections.

-
We have identified an issue with the use of bundling and UI Maps, whereby the resulting Bundle was wrapping the UI Map in a set of CDATA tags, but only after it had already removed all formatting from the source records, resulting in corruption of the UI Map HTML fragments. This has now been corrected by implementing Single Fix 8228025 on FW/CC&B 2.2.0. If you are using the Bundling subsystem in your implementation, I strongly recommend that you implement this patch.
Read more