Unable to extract data using datatable in Oracle EBS

[dvkc91 (Daniel Voon)]

I have encountered where the robot is unable to extract the datatable from Oracle EBS in this table when there are multiple rows as shown in the screenshot. It is only able to capture one row which is not correct. And also, there is another issue where it is unable to scroll down to capture other rows to datatable as well. Need assistance on how to resolve this issue, as I need to extract it out to perform mapping with a data value from my Excel and to instruct the robot to click which row to update the information as the requirement.

[prashant1603765 (Prashant Kumar)]

Hi @dvkc91

Pls check below link,

How to select a specific record from Oracle EBS application based on the value extracted from Excel?

Perfect here it is necessary to deeper inspect the [grafik] we mentioned: e.g. Col1 Col2 A 1 B 2 C 3 D 4 Scrollmode: 1 row, Segment Size: 2 At the begin we will see: A,1 B,2 B will have idx=2 When we scroll then we move 1 row forward and will get: B,2 C,3 B will have idx=1 after Scrolling As mentioned: there are many variations (depending on what was done by the Application Developer) and therefore the deeper analysis is needed on overall structures paging…

Happy Automation

[dvkc91 (Daniel Voon)]

But the main issue I encountered is that it is only extract one row. If extract records which has multiple rows and scrollable it will encounter the error I shown in the screenshot. I have tried numerous methods but have no idea to resolve it.

[Anil_G (Anil Gorthi)]

@dvkc91

Ebs screen behaves differently

Generally it is better to use idx in the selectors to get each row

So basically get a single cell check if value is not blank then get the data ..if blank end the loop..and once you scroll the idx resets so even that needs to be handled separately to get the data below the scroll

Cheers

[Jeroen_van_Loon]

The tables in the Java view of EBS are not recognised as tables from a UiPath perspective for the extraction wizard. Unfortunately, it is a matter of idx usage and scrolling as mentioned above.

Sometimes there is an alternative, where you can export a table to excel or csv. That would allow you to read the entire table by reading the exported file. Useful with large tables.

Things to look out for:

• idx parameters do not match the data rows, but the visible rows. If a grid has only 4 visible rows there is not an idx=5, ever, even when scrolling. Be sure to compensate for that.
• Not all data is always loaded immediately. If the EBS status bar lists ‘12 o ??? records found’ this is the case. So when looping and scrolling for extraction be sure to validate that to find your ‘end’ point.
• If you need to do data entry in a table, be sure to double check the selectors. Cells in edit mode might get different identifiers.

[dvkc91 (Daniel Voon)]

Would it be possible to guide me the detailed steps? I can provide the configuration from Oracle EBS.