Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
This forum is where any logged-in member can create a knowledge article.
Recent Documents
-
Compare Infoproviders between BW HANA environments using Gold Client BW
Compare Infoproviders between BW HANA environments using Gold Client BW One of the most asked and key features of Gold client BW is to provide the use... Show MoreCompare Infoproviders between BW HANA environments using Gold Client BW
One of the most asked and key features of Gold client BW is to provide the users with a feature to Compare infoproviders between two BW HANA environments. This unique feature also list’s out the differences of the object between the two environments.
The function allows the comparison of various types of Infoproviders like Info Objects, Info Cubes, DSO and ADSO’s structures and properties between the current BW system and a target BW system.
Upon entering one or multiple Info Objects, Info Cubes, DSO’s or ADSO’s the function will compare the structure and properties of the same against the Info Objects, Info Cubes, DSO’s and ADSO’s in the target system specified by the user.
Example:
Source BW Environment = A4H(BWonHANA)
Target BW Environment = BW2(BW4HANA)
infoprovider to be compared between two BW environments = 0MATERIAL
Login to the source BW system which in this example is A4H and use the tcode ZGOLDBW for Gold Client BW
Click on Compare Info provider button under the Infoprovider Equalizer section as shown in the figure below
In the next screen we need to provide the details of the info provider which we would like to compare with the Target BW system. Below are the steps to be followed
Compare Info Provider for on your target system.
- Select InfoObject radio button from the Info Provider type
- Enter InfoObject(s) in the Info Provider Selection which in this case is 0MATERIAL
- Enter the RFC destination of the BW system the Info Object is being compared to – Which in this example is BW2
- Press the Execute button
Once the execute button is pressed the user will be asked to login to the target BW system which in this example is BW2
After logging in successfully, the system will compare the infoprovider between the two BW environments and will list out the differences of the infoprovider between the environments.
In the below example of 0MAERIAL we can see that the length, output length, number of attributes and the attributes which is missing or differ from the source BW system will be displayed.
Similar to 0MATERIAL the user’s will be able to compare the below different types of infoprovider between two BW HANA and BW Non-HANA environments
- Info Object
- Info Cube
- Data store Objects
- Advance Data store objects
Environment
-
How to check if Qlik Gold Client Transformation is Working ?
Intro Data Transformation functionality was introduced in Gold Client version 8.0. It allows the transformation of fields during the Export of data i... Show MoreIntro
Data Transformation functionality was introduced in Gold Client version 8.0. It allows the transformation of fields during the Export of data in Gold Client. This functionality is delivered with default configuration; however, users are provided the flexibility to define their own data transformation routines for any table and field.
Summary:
When using Qlik Gold Client, you are unsure if the transformation is working.
Here is a step by step to validate all the stages of transformation.
How To Make Sure Transformation is active:
1. Check that the rule(s) exist in /n/HTG/ZGOLD > Data Transform > Transformation Setup.
2. The configuration needs to be active and have a valid rule.
In this example, transformation rule BP01 (designed to transform Business Partner data) is scrambling BUT0CC-CCNUM (Payment Cards Number) and EKUN-SOC_SECURE (Social Insurance Number).
3. Transformation rules only add value if they are assigned to Data Echo and/or Client Construct data types.
This assignment is important because the data transformation will occur automatically during the export process but only for those data types which have a rule assigned.
To provide an example, transformation rule BP01 (designed to transform Business Partner data) could be assigned to Client Construct data type BUSINESS PARTNERS and/or to Data Echo data type CA - BUSINESS PARTNERS.
Users who initiate exports do not need to take any actions for transformation to occur because of this rule assignment.
4. During the Export, please make sure that the transformation rule(s) is/are being called. Go to the job monitor (SM37) of the main job and check the job log.
For more information, see the Data Transform User Guide found at:
Tags:
- Qlik Gold Client
- Transform data
- Scramble data
- Anonimization
- SAP
- S4HANA
Labels
Environment
- Qlik Gold Client 8.7
- SAP S4 HANA
- SAP ERP
-
Gold Client - transformation rule (Derived - Multiplier) PA**** Tables
Intro Data Transformation functionality was introduced in Gold Client version 8.0. It allows the transformation of fields during the Export of data i... Show MoreIntro
Data Transformation functionality was introduced in Gold Client version 8.0. It allows the transformation of fields during the Export of data in Gold Client. This functionality is delivered with default configuration; however, users are provided the flexibility to define their own data transformation routines for any table and field.
Summary:
When we have Derived transformation to multiply a value in PA**** tables, Gold Client allows to transform values based on a reference field (it can be the field itself) by applying a multiply factor.
Customizing table /HTG/NOPERNRSYNC plays a major role here, because this table allows the synchronization of each record in PA* tables by employee.
The table contains only two columns (Table name, Field name). This is field level customization, and all required fields should be maintained in customization. To maintain entries in this customizing table, please use transaction SM30.
- If the entry is not maintained in the customizing table /HTG/NOPERNRSYNC, Gold Client will transform all records related to a particular PERNR to the same value, and that is calculated from the first record of that PERNR.
- If the entry is maintained in the customizing table /HTG/NOPERNRSYNC, each record is calculated from its own original value.
Example:
- In PA0014 there are 4 records for PERNR “00070036” and each row contains a different value in BETRG Field.
- Create a Transformation rule for PA0014-BETRG field where field BETRG will be derived by its own field by a multiplication factor of 1.5x.
- Assign this rule to the corresponding data type in Default Rules
Scenario 1: Configuration Not Maintained
- SM30 ---> Table /HTG/NOPERNRSYNC - “Do not sync same-PERNR records for GC Transformation”
- Run Data Snap – Data type – HR - PERSONNEL MASTER
- Check Sizing Report
Scenario 2: Configuration Maintained
- SM30 ---> Table /HTG/NOPERNRSYNC - “Do not sync same-PERNR records for GC Transformation”
à Configuration for PA0014-BETRG - Run Data Snap – Data type HR - PERSONNEL MASTER
- Check Sizing Report
Note:
- In the first scenario (PA0014-BETRG is not maintained in the configuration table /HTG/NOPERNRSYNC). All rows contain the same value for field BETRG, and this value is calculated from the first-row original value (18 = 16 * 1.5) and replicated to all other lines.
- In the second scenario (PA0014-BETRG is maintained in the configuration table /HTG/NOPERNRSYNC). Each row is calculated from its own original value:
18 = 12 * 1.5
32.25 = 21.50 * 1.5
51.75 = 34.50 * 1.5
300 = 200 * 1.5
For more information, see the Data Transform User Guide found at:If you are unable to resolve the issue, freely submit a support case, and the Qlik Gold Client team will respond accordingly.
Tags:
- Qlik Gold Client
- Transformation
- SAP
- S4HANA
Labels
-
How to Use Timestamp field as a filter in Qlik Gold Client?
How to Use Timestamp field as a filter in Qlik Gold Client? In Qlik Gold Client version 8.7.3 and prior releases the following Timestamp issues... Show MoreHow to Use Timestamp field as a filter in Qlik Gold Client?
In Qlik Gold Client version 8.7.3 and prior releases the following Timestamp issues were reported:- Timestamp fields are populating (with minor discrepancies), but the number of records is not calculated. Number of records is displaying 0 (zero) in Export Control screen.
- Timestamp fields are populating with initial values, and the number of records is not calculated. Number of records is displaying 0 (zero) in Export Control screen.
- The timestamp value is also not correct:
Example: 1.12.2022 to 29.12.2022 should be calculated as 01.12.2022 00:00:00 to 29.12.2022 23:59:59.o but it is calculated as 30.11.2022 21:00:00 to 29.12.2022 20:59:59.
- Timestamp fields are unavailable as primary date fields in Data Framework.
If you are facing any of these issues, please upgrade to the latest version of Gold Client. All these fixes related to Timestamps were included in Gold Client 8.7.4 and later versions.Regarding Timestamp fields not being available as a primary date field (4) in Data Framework, a specific configuration needs to be added in Gold Client:1- Identify the corresponding domain for the field(s):For example, table SCMG_T_CASE_ATTR has 3 timestamp fields, all with the same domain:Field nameData ElementDomainCREATE_TIMESCMG_CREATE_TIMESCMG_TIMESTAMPCHANGE_TIMESCMG_CHANGE_TIMESCMG_TIMESTAMPCLOSING_TIMESCMG_CLOSING_TIMESCMG_TIMESTAMP2- Add the corresponding field domain(s) in the Gold Client Configuration:Gold Client > Configuration > Administration > Maintain Timestamp TypesDomain/Dtel/ConvExit: SCMG_TIMESTAMPTimSt/DM: TimestampActive:SaveAfter that, the Timestamp fields should be available in the search help of Primary Date Field in Gold Client’s Data Framework:If you are unable to resolve the issue, Please contact our Support.Tags:- Timestamp
- SAP
- Qlik Gold Client
Labels -
Copying SAP Flexible Workflows with Qlik Gold Client
SAP Flexible Workflow is a new concept introduced in SAP S/4HANA to simplify workflow configuration. community.sap.com -> Flexible Workflows If you ... Show MoreSAP Flexible Workflow is a new concept introduced in SAP S/4HANA to simplify workflow configuration. community.sap.com -> Flexible Workflows
If you have recently used Qlik Gold Client to copy SAP Flexible Workflows into your target client and there are some steps missing, the most likely root cause is that table SWF_FLEX_PROC has RAW fields and Gold Client can have trouble determining the full length of these fields.
Please check the instructions below:
Gold Client > Client Exporter > WORKFLOW FLEX TABLES
In this case, check the Gold Client Configuration before the export to ensure that the Table Compression Type for SWF_FLEX_PROC (or any other related table with RAW fields) is defined as New Compression.
Gold Client > Configuration > Data Copy Toolbox > Set Table Compression Type
If you cannot resolve the issue, freely submit a support case, and the Qlik Gold Client team will respond accordingly.
Note:
If Client Construct Data Type WORKFLOW FLEX TABLES doesn't exist, it can be included in the data model, adding all SWF_FLEX_* relevant tables.
Tags:
- Qlik Gold Client
- Flexible Workflow
- SAP
- S4HANA
Labels
Environment
- SAP S4 HANA
