on 12-12-2020 9:36 PM
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
Try to SORT with BELNR and other keyfields before you are reading the tables in BADI Method.
Thanks,
Bhavin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
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...
User | Count |
---|---|
75 | |
10 | |
10 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.