Data Lake Setup in Optiva

In this section, you will use criteria to limit which tables will be sent to the Data Lake for the symbol using detail codes.

At least 1 Detail Code, 1 Status, and 1 Class must be selected in Symbol form > Data Lake tab in order to send over Table Schema and Data to the Data Lake.

Note: For a Label Content object, you can retrieve the parameter values for all row tags from the TP detail code, as the TPVAL detail code will not be used to send parameter values for row tags to the Data Lake.

A primary key is required for all tables sent to the Data Lake which means all extended tables must have a primary key if the MATRIX (Extension Tables) detail code is selected. If there is an extension table without a key, an error will be generated when you click the Setup Data Lake button. To fix this, edit the extension table and add a primary key. See the Infor PLM for Process Application Configuration Guide for more on extension tables.

You can also limit which objects are sent by selecting statuses and classes (where they apply).

Data Lake integration is supported by the following symbols: Workflows in Progress, Enumerated List, Formula, Item, Project, Specification, Symbol, Company, Ingredient Statement, Label Content, Test, Sample, and Test Order.

For the Company symbol, you can select the class None when companies with no class selected must be sent to the Data Lake. This is for both the initial data load and when data is edited.

Select the Data Lake tab for a symbol.
Select detail codes, statuses and classes to send to Data Lake. Click Save.
Click Setup Data Lake to send the table schema for this symbol to the Data Catalog without using the Inbox Listener. Now if a schema changes (for example, new columns, extension fields,extension table, fields in validation codes), the Data Catalog is automatically updated.
The Setup Data Lake button transforms into the Data Lake Send Data button once the table schema is successfully sent to the catalog. Click Data Lake Send Data to send the objects that meet the Data Lake criteria for the symbol to the Data Lake outbox.

Note: Once the initial data load is completed, an object of this symbol type is saved or deleted and it meets the Data Lake criteria, the complete set of all detail codes for the object will be sent to the Data Lake. It is important that the choices made for limiting criteria, detail, status and class, are chosen carefully. They can be edited after the initial data push but will only affect data sent in the future. For example, if the ITEM symbol was set up with statuses 300=Mfg Approved for Data Lake criteria, then all items are pushed to the Data Lake and then the ITEM symbol is edited again and 200=Pilot Approved is added to the Data Lake criteria, the all pilot approved ITEMS are not sent to the Data Lake, only the ones that are saved going forward.
It may be necessary to resend all the initial data for a symbol if there are any issues with the initial send, or if there is a reason to change the criteria for the data. To do this, use the Data Lake Resend Data button.

Note: This must only be done after the same data is purged from the Data Lake to avoid duplicate data. See the Infor ION Desk Data Lake Purge documentation for more information.