cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

ODP Extractor issue - Missing fields when importing into Data services

Former Member
0 Likes
2,527

Hi guys,

I'm importing some extractors into data services but I'm facing a big issue, which is only certain fields are imported. For example, using 0ASSET_TEXT.

This is the extract structure in ECC:

The datasource has been enabled in table ROOSATTR, and table ROOSFIELD looks like this:

When I import it from data services designer, this is what I get:

So, key1, key2 and key3, which in this case are chart to accounts, asset number, etc, are simply missing.

Any ideas?

Thanks

Accepted Solutions (0)

Answers (4)

Answers (4)

Mageshwaran_Subramanian
Active Contributor
0 Likes

Hi kt_sap_001,

What is the original data type of the missing fields?

I suspect the source contains the data types that are not supported in Data Services.

https://apps.support.sap.com/sap/support/knowledge/preview/en/1598268

Former Member
0 Likes

I created a custom copy of the datsource, enabled it as ODP using program RODPS_OS_EXPOSE, and it works:

So what am I missing that causes the standard ones not to work?

Former Member
0 Likes

https://launchpad.support.sap.com/#/notes/2321909

Seems to me generic text extractors using structures ROTEXT* should work unless you have added custom fields, which I haven't.

So still no solution.

Former Member
0 Likes

I'm coming to the conclusion that text extractors that have this "dynamic" structure (with generic "key1" "key2" "key3" type-fields) will simply not work. I'm saying this because none of these text extractors are ODP enabled by SAP, you need to manually add them to table ROOSATTR so it does not sound like a casual coincidence.

Anyway, if any of you have any ideas, please let me know.