cancel
Showing results for 
Search instead for 
Did you mean: 

Datasource FM using BAPI_ALM_ORDER_GET_DETAIL not working

former_member242512
Participant
0 Kudos

Hi All

We have developed a datasource using a function module inside which it calls the BAPI '

BAPI_ALM_ORDER_GET_DETAIL' . The datasource works perfectly fine when executed through RSA3 tcode in SAP but when it is extracted through SQL team it is going in endless time and not providing them any records . Is there any issues using this BAPI ? Kindly assist.

Accepted Solutions (0)

Answers (3)

Answers (3)

paul_meehan
Advisor
Advisor
0 Kudos

Hi,

Should not be any problem with this BAPI. Check it independently using SE37 to verify your selection does return data.

-Paul

raymond_giuseppi
Active Contributor
0 Kudos

Did you check for authorization failure, during your RSA3 test did you extract only small volume of data, etc.

former_member242512
Participant
0 Kudos

Hello Raymond , Yes small amount of data is getting fetched so no authorization issue . The SQL people say it extracts only 300-400 records and don't go over that .

raymond_giuseppi
Active Contributor

How do they (SQL) extract the data, for example a BW system will execute multiple requests to extract data package after package until the extractor raise the no_more_data exception. Also you should check execution in source system (Did you free some memory between call of BAPI, damage caused by non sorted big internal table with wrong read statements can kill the performance concept)

" small amount of data is getting fetched so no authorization issue 

Volume of data and authorization check are not really linked... so why 'so'?

former_member242512
Participant
0 Kudos

Actaully this an SQL system outside SAP Box. They directly access our datasource created in SAP. I used below FM for refresh of buffers .Is there any FM thourgh which I should free up memory ? Kindly suggest.

CALL FUNCTION 'BUFFER_REFRESH_ALL'.

CALL FUNCTION 'BAPI_ALM_ORDER_GET_DETAIL'
EXPORTING

raymond_giuseppi
Active Contributor

First check on source system for actual problem, those were only assumptions, you have to look first in your system during call. Insure with the guys of the SQL system if they correctly call the extractors.

For memory release you could look at FM like ITOB_BUF_CLEANUP or CO_IH_BUFFER_REFRESH depending on your version of SAP. Or execute the BAPI thru a RFC call so in another LUW (force close with RFC_CONNECTION_CLOSE at end of each package if required)

NTeunckens
Active Contributor

Try FM "IBAPI_PROC_INIT_REQUEST" to clear Buffers before executing the BAPI ...

Former Member
0 Kudos

Hi Ujj,

This BAPI is connecting to component PM-WOC-MO ( Maintenance Orders ).

You could try to extend the tags with the component, I do not see any impoct from BW side at the moment.

Br, Andras