cancel
Showing results for 
Search instead for 
Did you mean: 

0fi_gl_14 datasource not working

former_member196080
Participant
0 Kudos

Friends

0fi_gl_14 datasource is working fine in QA , I mean badi logic(custom logic reading multiple ECC tables) is giving correct results but not in production. Looks like data packets are different for same document number(belnr) hence BADi logic is unable to process correctly. But in QA its working fine. The same Belnr is in same datapacket in QA.

I tried replicating and activating datasource again but no luck.

What can be done one Belnr should remain in one datapacket passed to badi?

Any suggestions here?

Thanks

former_member196080
Participant
0 Kudos

Hi Debjit

It will change the packet size for all BW. But is there a way to change the packet size for only one datasource?

Thanks

DebjitSingha
Active Contributor
0 Kudos

Hi rubane.s,

If I am not mistaken changes are global in nature and impact all BW DS.

Hope this helps.
If you are satisfied with the answers, appreciate if you flag this as answered. This will help others find solutions quickly and search engine will direct them to your question.

Thanks,
Debjit

former_member196080
Participant
0 Kudos

Hi Debjit

We cant change packet size of all datasources we want to increase only for one DS. Is there a way?

I'm flagging your answer since I appreciate you're help anyways even if it solves or not its secondary..thank you

DebjitSingha
Active Contributor
0 Kudos

I am afraid changes are global.
Good luck!

mynynachau
Community Advocate
Community Advocate
0 Kudos

Hi rubane.s ,

Thanks for acknowledging other members for their help on your question. We've received a moderator alert that the flagged answer is not correct/helpful. However, answers should only be marked as accepted, if the answer was helpful for your original question. If you would like to show a "thank you" gesture, you might upvote the answer instead.

I have unflagged the accepted answer by you to avoid confusion. In case you disagree with this approach and want to confirm that the answer was indeed helpful and correct, please feel free to accept it again.

Best regards

SAP Community moderator

Accepted Solutions (0)

Answers (1)

Answers (1)

bhavinvyas
Active Contributor

Try to SORT with BELNR and other keyfields before you are reading the tables in BADI Method.

Thanks,

Bhavin

former_member196080
Participant
0 Kudos

Hi Bhavin, Its already sorted in Data method of BADI.

Question is how we can control behavior of data packets sent to BADI in C_T_Data? In QA its not an issue but in production the BELNR is coming in different data packets for example if BELNR has 32 lines 4 are coming in one data-packet and remaining 28 in others.

Anyway we can control this behaviour?

bhavinvyas
Active Contributor
0 Kudos

Recently we had similar issue, In QA it was working perfect but in prod. it was not. You can also try to change the default packet size of particular infopackage and test it. change it from 20000/10 to may be 1000/10. it will bring more no of lines in 1 data-packet but still issue will be there.

We have corrected the sorting in code to resolve the issue as we are using binary search while reading.

something like this,

select statement .......

If sy-subrc=0

Sort ......

endif.

Loop...

Read Table .... Binary Search.

Endloop...

former_member196080
Participant
0 Kudos

what was the excat before and after code ..if you can share that will help to understand