Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Using BTE for FBL*N tcode in Background processing

Former Member
0 Likes
1,241

Dear All...

I have a problem when utilize BTE FDM_AR_INTERFACE_00001650 to add some field in FBL*N tcode..

The problem arise when we execute transaction in background processing.
IF the BTE is active when we retrieve the data from background processing using SM37 (from spool) several field are blank .. even some field which are not the one that the BTE processed.. .

we already tried to create new layout for background processing but the field still come up blank..

But if we execute the report in online processing (not background) the same field are filled with data..

Since the data is too many if we go for online processing the system will gives time_out dump message so we have to execute it in background..

This condition only happens when the BTE is active... if we disabled the BTE in FIBF.. the results seems normal..

I've attached the result from online processing and background processing ...

why this condition happens ?

what should we do to fix this problem.. ??

any usefull information will be rewarded..

note : we have to enabled BTE because there's some extra fields that required in the report..

thank you,

Sasmito


1 ACCEPTED SOLUTION
Read only

RaymondGiuseppi
Active Contributor
0 Likes
881

For performance problem, look at BAdI FI_ITEMS_CH_DATA which can replace good old BTE 0000165, this BAdI receives the whole internal table when the BTE is called item per item, so a better optimization is possible.

For background processing, insure field catalog is correct and report width (check print parameters) is sufficient for the used ALV variant.

Regards,

Raymond

2 REPLIES 2
Read only

RaymondGiuseppi
Active Contributor
0 Likes
882

For performance problem, look at BAdI FI_ITEMS_CH_DATA which can replace good old BTE 0000165, this BAdI receives the whole internal table when the BTE is called item per item, so a better optimization is possible.

For background processing, insure field catalog is correct and report width (check print parameters) is sufficient for the used ALV variant.

Regards,

Raymond

Read only

0 Likes
881

Dear Raymond

thanks for your respons..

I've tested this BAdI and it seems solve the differences betweeen online and background processing..

but since the code from BTE are not migrate to BAdI yet.. so i can't confirm that it behaves similar to the BAdI..

i will update here soon..

thank you,

Sasmito