Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When a new client is built, configuration and its address data is included in that process. When using Gold Client to populate the application data in the new client, the best practice is to copy the application data, which includes address data, from the same source system used for the client build. This results in the configuration and address data being a match to the source system, typically Production. It also minimizes the risk of address master inconsistencies.
There are occasions when a customer wants to create a new client with configuration from one system and application data from another. An example of this is building a new client with configuration from Development and application data from Production. This may cause address master inconsistencies for the configured organizational units because the address number assigned in one system may not be the same across all systems.
If the client is built in this manner against best practice and address inconsistencies occur, there is a solution. The address data for each of the organizational units could be copied from the system in which the configuration was sourced. Organizational units with address data are:
Company Code (T001)
Plant (T001W)
Sales Organization (TVKO)
Shipping Point (TVST)
Transportation Scheduling Point (TTDS)
Sales Office (TVBUR)
All of those tables have field ADRNR (address) that can be used to find all related address data. To do this, go to ZGOLD – Configuration – Additional Tools – Create/Delete Data Type.
In field Table Name, use the multiple selection button to input the configuration tables and click Copy.
For Data Type Kind, select M for master data. The configuration tables are not master data, but we will link to the address master data. The fields for Child Table Name and Field Name can remain blank. Keep the default for Create Data Type selected and click Execute.
It will create a new data type for each configuration table.
Back out to the main Configuration screen and go to Data Framework – Data Echo.
Click Display All to see all data types and scroll to find the new ones. For each new data type, the linkage to the address master data should be added. Open the data type, double-click on Linkages, and in the Linkage window, switch to change mode. Add a new entry for data type CA - CENTRAL ADDRESS MANAGEMENT. Save it and double-click on it. In the Linkage Details window, add a new entry for relationship ADRC-ADDRNUMBER = ADRNR. Save it.
Repeat the addition of a linkage to data type CA – CENTRAL ADDRESS MANAGEMENT for all of the new organization unit data types created.
Back out to the main ZGOLD screen so the export can be created. Go to Data Snap. Enter one of the new data types and click Data Type Manager. Open it and double-click on Data Snap. Add the Data Snap selection criteria for the given organizational unit and save it.
Back out to the Data Snap screen and click Execute. Enter the selection criteria. To obtain address data for all organizational units, use an asterisk (*). Click Save as Scenario so it can be reused in the future.
Back out and repeat the Data Snap configuration and scenario creation for the remaining organizational unit data types.
On the main ZGOLD screen, go to Export Control. Find your master data ExportID or create a new one and click on it. Click Add Container, use the Data Type dropdown to find Z- T001 or enter it manually, and use the scenario drop-down to find the Data Snap scenario that was created. Save it. Add containers for other organizational unit data types and save it.
Export the data as you would any other data type. When importing, keep the default for Replace Duplicates selected even though likely the data does not already exist. This should allow the configuration to have its correct address data in the new client.
For further questions or if your organization has a different situation than those described, please open a support case (www.qlik.com/community-support-cases) to discuss further.
