Bath Input for VBO2 transaction

[Former Member]

Hello everyone,

I'm programming a BI for transaction VBO2, changing rebate agreements from conditions in a file.

It's working right.

My problem is that when the rebate agreement is more than 1000 conditions and I

introduce material settlement, the BI does not placed correctly in the first box empty. It works OK for less than 1000

records, using the command P++, going to the bottom of page and charge the

materials back, but for more than 1000 conditions, SAP doesn't recognize the P+ or the

P++ to scroll and stays in first position.

Does anyone have any idea?

Thank you very much!

[Former Member]

Hello everyone,

I'm programming a BI for transaction VBO2, changing rebate agreements from conditions in a file.

It's working right.

My problem is that when the rebate agreement is more than 1000 conditions and I

introduce material settlement, the BI does not placed correctly in the first box empty. It works OK for less than 1000

records, using the command P++, going to the bottom of page and charge the

materials back, but for more than 1000 conditions, SAP doesn't recognize the P+ or the

P++ to scroll and stays in first position.

Does anyone have any idea?

Thank you very much!

[vinod_vemuru2]

Hi,

Welcome to SCN!!!

Conditions are handled in table control. As per my understanding, Limitation from SAP in table control is 999 records (Rows). But do you really have a practical scenario where a Rebate has more than 1000 condition rows!?

Thanks,

Vinod.

[Former Member]

thanks for your welcome

Yes, I have an scenario that with more than 1000 rows. Incredible, isn't it?

I've heard about 999 rows limit, but hope there is a solution.

Thank you so much!

[Sandra_Rossi]

> Conditions are handled in table control. As per my understanding, Limitation from SAP in table control is 999 records (Rows).

No !!! (I did a test with a simple custom program)

There are maybe limits in functional modules (for example I know there's a limit of 1000 items in FI documents because the BSEG-BUZEI key field is only 3 digits), but there's no limit with table control technology (or if there's one, I think it would be a timeout!)

[Former Member]

Hello,

When I try to fill more than 1000 rows from VBO2 transaction it works correctly and can add more material rows, but it doesn't work using a Batch Input session. So I think the problem is BI session, but I don't know if it's a VBO2+BI problem or it occurs in other BI sessions with Table control completions.

I'm trying to explain it in the best way I can, writing a bad English. If you need, I can rewrite it.

Thanks!!!

[Sandra_Rossi]

Hi Javier,

No doubt that we clearly understand what you say. As I said, my test shows that batch input supports 1000+ lines without problem. So, for me, the issue is clearly with VBO2 + BI.

Unfortunately, I can't test on my system as we don't use VBO2.

Could you tell me what dynpro (please indicate the subscreen if any, not the main dynpro) contains the concerned table control so that I have a look at its scrolling logic?

Did you try to record and run the batch input with the screen "default size"? (though I don't see why it would better work; for more information, see Note 11788 - Batch input, variable step loop or table control)

Finally, if you don't get any other solution, I recommend you to contact SAP support to report the "VBO2 + BI scrolling bug".

sandra

[Former Member]

Hi Sandra,

The Dynpro's number is 0411 and belongs to SAPMV13A programm.

Now, I'm going to read the note that indicates me.

Thank you!

[Sandra_Rossi]

Thx. First thing I see in the dynpro, it's not a table control, it's a step loop. I investigate...

[Sandra_Rossi]

1) I did a little test on step loops, they also support more than 1000 lines without problem.

2) I had a look at dynpro SAPMV13A 0401, but unfortunately, reading the code is very complex as everything is generic.

I could do little customizing to make VBO2 work, so that to test it.

Your issue is explained and solved in [note 320839 No scrolling in material for settlement in batch|http://service.sap.com/sap/support/notes/320839]

[Former Member]

I apologize for beeing out these days.

I read the sap note that you posted and it helped me a lot.

Finally, we use SICH OK_CODE to force vbo2 cursor for placing it in the correct field. By this way, I don't need to use scroll ok_code because when I tyi to record the registry usig SICH a pop-up advise appears and let me place the cursor in the correct field.

Thank you very much!!!