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.
i have to load a csv file from SAP (tab seperated) into WebFOCUS. The problem is that the structure is not a typical flat file structure. (Content by Columns) I will get the data in rows. In the first row are header informations, like user_id, e_mail, company, date, in the sond row are deaper informations on the contracts belonging to the company like order or contracts, currencies, materials. In the third to n rows are the actual orders with amounts, companys, savings. Each row has the contract_id as key field to connect the rows. I also know in which table (SQL-Server) i have to write the specific values. Has anybody an idea how such a load process shoud work??
Regards
Christian
WF Production Version: 7.7.02M WF Test Version: 7.7.02M Developer Studio: 7.7.02 HTML, EXL2K, FLEX, PDF,PPT
WF is very good at working with multi-record sequential files. Unfortunately, this does not apply to CSV format.
What a work mate of mine did very recently was create a master with one field that was as long as the longest potential record and treated the CSV as a true flat file. He then ran one query for each record type and saved the output in their own tables (using a series of where statements to identify the different record types). He then created one master for each record type to read only those records as CSVs.
This will only work if there is something in each record that can point to the parent record.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott