Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dear experts!
I have a question concerning the extraxt of the hierarchy 0FUNCT_LOC_HIER:
I'm using the Extractor Connector to load this data from the SAP (no BW).
Result of extracting data ist always:
0 lines fetched
0FUNCT_LOC_HIER << ExpandedLeaves 0 lines fetched
The log file "QvSAPExtr" contains "2016-01-20 15:22:08 Received: E1RSHND, Rows: 0, Total Rows: 0"
So I get no data for this. This is really strange because the "Server" log contains this:
2016-01-20 15:22:07 Requesting a new SAP Data job: 0FUNCT_LOC_HIER, Logical Sys: QVEXTRX999, ASHOST: 192.12.155.10, Id: 253
2016-01-20 15:22:07 Hierarchy: TPLH
2016-01-20 15:22:08 253 : Started job: REQU_QVEXTRX999_20160120152206
2016-01-20 15:22:08 Received: 0FUNCT_LOC_HIER, Id: 253, rows: 206, Total rows: 206
2016-01-20 15:22:11 rqState 9: Reported complete by SAP, id: 253
->so there is some Data...
I'm using the generated script:
HIERARCHY(NODEID,PARENTID,NODENAME,,NODENAME,HIERARCHY)
LOAD
NODEID,
INFOOBJECT,
NODENAME,
TLEVEL,
LINK,
PARENTID,
CHILDID,
NEXTID,
DATEFROM,
DATETO,
INTERVL;
SQL EXTRACTOR 0FUNCT_LOC_HIER
UPDMODE H // Hierarchy extractor
TFRMETHOD T // tRFC transfer method
HIERARCHY TPLH
HIERLANGUAGE German
HIERTABLE E1RSHND
LOGSYS QVEXTRX999
;
Can someone help me?
Thanks!
Hi Tomas,
Thanks. I think we will do connector update later this year.
IDoc is not possible because it is not allowed in DataSource ("only PSA"). May be we will switch this in source system an try the IDoc way later.
If there are news for this issue I will reply on this thread.
Meanwhile we extended the 0FUNCT_LOC_ATTR with the relevant hierarchy field TPLMA from the IFLOT table. This workaround works .
Regards,
Markus