Symptom
For MDG HANA View Generation and Search, in case the system has HANA
as the primary database, no entry should be needed for the Database
connection name in the MDG Landscape Profile customizing. However,
currently the system always expects a connection name to be maintained
in this customizing. This note provides a fix for this issue.
Other Terms
Master Data Governance, MDG HANA View Generation, MDG HANA Search
Reason and Prerequisites
In cases where MDG is used with HANA in a side-by-side deployment
scenario, a secondary database connection name needs to be maintained in
the MDG Landscape profile customizing.
However, if HANA is the primary database, now it is not mandatory to maintain this customizing entry. If not maintained, then a default database connection will be used for HANA view generation and search. However, the user does have the option of maintaining a different database connection name in the Landscape Profile if he does not wish to use the default.
However, if HANA is the primary database, now it is not mandatory to maintain this customizing entry. If not maintained, then a default database connection will be used for HANA view generation and search. However, the user does have the option of maintaining a different database connection name in the Landscape Profile if he does not wish to use the default.
Solution
Implementing this note will allow the user to use the default
database connection name without maintaining an entry in the MDG
Landscape profile customizing, for cases where MDG is used with HANA as
the primary database.
Header Data
| Released On | 04.09.2014 12:07:30 |
| Release Status | Released for Customer |
| Component | CA-MDG-DQ-SD Search / Duplicate Check |
| Priority | Correction with medium priority |
| Category | Program error |
No comments:
Post a Comment