As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
We purchased the IBI SAP HANA adapter. We are having an issue where we do a very simple join on a material number to another table with material number, same exact format. When the report is displayed all it returns are the materials that are exactly the full length of the material which is A18. if the material is not exactly 18 bytes the material is ignored. This is very frustrating...any ideas. We are in the middle of an SAP HANA upgrade are now dead in the water. Is there certain setting on the adapter or config files we need to modify? ThanksThis message has been edited. Last edited by: FP Mod Chuck,
You would think that would work, but I changed both masters to have a variable format on the join fields and still I get the same result. Thanks again for your response.
Are you indeed on 8.0.9, as your signature implies?
For our SAP ECC connector, we started out with 8.0.9, but had to upgrade to 8.1.03 (We're on Gen 827) because of show-stopper issues that were solved in later versions.
If you did not already do so, make sure to open a call with Tech Support. Even if they can't solve this for you right away (probably by means of an upgrade), they should at least be (made) aware of the issue.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
In the EDAPROF.PRF file there was a set command: " SQL SQLHANA SET VARCHAR OFF " The reason this was originally added was to remove all "V" variable length formats from the master files. The original masters pointing to SAP ECC 5 did not have variable length fields but apparently HANA (SAP ECC 6) requires the fields to be variable length. Once the material field was changed from a A18 to A18V format the join worked as expected.This message has been edited. Last edited by: MMcDonald,
Once we removed the " SQL SQLHANA SET VARCHAR OFF " In the EDAPROF.PRF file and recreated the HANA master with the variable length fields “V”, the join worked. The NEW issue is, the join ONLY works if you are joining from a HANA master to another table, they are not working if you join from (for example) a MSS SQL table to a HANA table.
Are the JOIN fields the same format in both databases? WebFOCUS is in my experience rather unwilling to coerce the format of one field to another - it does print a warning about non-matching JOIN field formats though.
In such cases, manually coercing the fields to the longest usually helps. However, that usually requires a DEFINE field WITH someotherfield and another WITH in the right-hand side of your JOIN - and therefore it pretty much defines in which order you can JOIN your tables.
Often we end up holding to a local file first.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Formats are identical. The adapter seems to be padding the field with either spaces or zeros when the value of the field is less the the actual format designated by the master file. I was on the phone all afternoon with IBI support and will continue to work with IBI this morning. There does not seem to be a quick solution fr this issue, like a set command in the edaprof for HANA. I will continue to update this case and hopefully we find a solution.