We are facing a problem which is happening just after migrating SAP DS version 4.0 SP 3 to 4.1 SP3
While testing the jobs just migrated, we noticed that SOME of the Query Transforms where JOINS are implemented, got corrupted or something weird is going on.
It must be said that this error does not show in every JOIN definition. We have made a very extensive and complex development so we didn’t check every JOIN definition made in our repositories but we noticed this issue appears when an IDOC-like structure (NRDM) gets involved in a JOIN :
Case 1:
After migration, the left table disappears from the Left column in the Join pairs panel:
Left table in this case, is a structure contained in a Nested Relational Data Model , called Transform_Art.E1BPE1VARKEY
If we try to “re-assign” this NRDM structure in the Left column, it actually seems like if it was available for selection
, and indeed, it can be selected
As a matter of fact, when doing so, the FROM clause gets automatically completed, placing the correct Join Condition specified in the original query.
However, if we open the Smart Editor, the Transform_Art.E1BPE1VARKEY structure does not shows eligible for selection in the Data Panel
A member of such structure, Transform_Art.E1BPE1VARKEY.MATERIAL, appears mapped on the right panel though.
The weird thing is that, even if we go ahead and save this repository definition, it takes too long to complete the save process. And when we come back to this JOIN definition, it seems like no changes were made.
Case 2: In other cases, the whole JOIN spec disappears at all and only the FROM clause remains with information. If we try to re assign the Left and Right operators, and then try to save this change, the change gets not reflected.
If we choose to Validate the object, no Warning nor Error Messages come up.
However, when we run the Job, it seems like it is taking too long to complete (we think of a Cartesian Product occurring or so)
In the document Upgrade Guide SAP BusinessObjects Data Services 4.1 Support Package 1 (14.1.1.0) we noticed there is a list of things happening during the upgrade process
6.3.9 Joins in the Query transform
Data Services now supports ANSI/SQL92 joins in the Query transform. In the Query editor, the OUTER JOIN tab has been removed and the functionality in the FROM tab has been extended to enable you to specify all join types in one location and to more accurately define restrictions. Additionally, join rank and cache can now be set directly in the FROM tab of the Query editor.
During upgrade
During upgrade, the following actions occur:
• The Query transform ATL and XML are automatically upgraded during the repository upgrade.
• Inner join queries are not affected. Inner joins previously specified in the WHERE clause will remain the same.
• Left outer joins are moved from the OUTER JOIN tab to the FROM tab.
However, we are not using LEFT Joins
We had a series of functional repositories used for sending information between our Legacy System and SAP ECC 6 server both ways:
- From Legacy to SAP ECC 6: Jobs implementing the generation of IDOCS (ARTMAS, CONDA, INFREC) based on the Legacy System information
- From SAP ECC6 to the Legacy System: Reading SAP ECC tables and for downloading data into local files
INSFRAESTRUCTURE:
Operative System: Windows Server 2008 R2 Standard
System Type: 64 bits
Processor: Intel Xeon @ 2.7 GH (2 processors)
Installed RAM: 20 GB
Repository Database: SQL Server 2008 R2
SAP BO SOFTWARE INSTALLED BEFORE MIGRATION
SAP BO Information Platform Services 4.0 SP 4
SAP BO Data Services 4.0 SP3
SAP BO Data Services Designer 4.0 SP3
SAP BO SOFTWARE INSTALLED AFTER MIGRATION
SAP BO Information Platform Services 4.0 SP 6
SAP BO Data Services 4.1 SP3
SAP BO Data Services Designer 4.1 SP3
The Software Upgrade and the Repository Migration processes did not show any evident error.
Any advise will be greatly appreciated.
Regards
----------------------------------------------------------------------------------------------------------------------------------------------------------
UPDATE
We have opened a support ticket with SAP, and SAP experts have suggested us to apply Patch 1 for SAP DS 4.1 SP3.
Since Patch 1 does not exist any longer (even in the Archived installers), SAP then, suggested us to go for Patch 2.
The issue was addressed initialy on Patch 1 with the following issue ID:
ADAPT01721490
If the column name has an invalid character, the Query validation of join conditions between columns of nested schema fails, and joins disappear after saving. This issue has been fixed in this release.
See SAP Note 2026786
http://sap-note.com/2026786.htm
We just installed the Patch.
There's no need to do anything else to the repositories.
We are testing at this very moment (August 28,2014) in order to know if Patch 2 for SAP DS 4.1 SP3 works for us.
We will let you know.
Regards