Skip to Content

Generic BDC for VK13 & BAPI for VK12

Sep 27, 2017 at 10:09 AM


avatar image

The requirement is to create a Generic BDC for VK13 which can map the values from an initial selection screen to the condition information screen of VK13. BDC should halt at this screen.

The problem is each condition type has a different selection screen (Condition Information-VK13) causing the BDC to fail in mapping the screen fields. Though few fields are same, their positions are different and using fields from the table fails for select-options.

Also, need a BAPI(for VK12) to display the condition records for a condition type, update the valid to date in the condition record and display the records again.

Can anyone suggest some solution?

Thanks in advance.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

avatar image
Former Member Sep 27, 2017 at 11:02 AM

Hi Srinidhi,

For the BDC, the best idea might be to put some conditions on the BDC_DATA you're populating based upon the user entry if you know what each screen has and where they're positioned. You can ignore all CURSOR positions in the BDC data so things moving around isn't an issue, just the screen fields.

For VK12, - BAPI_PRICES_CONDITIONS, if that doesn't work you can use these - RV_CONDITION_COPY, RV_CONDITION_SAVE.

Show 3 Share
10 |10000 characters needed characters left characters exceeded

I have already ignored all cursor positions, but still the mapping is failing when there is a different screen for a condition type.

Former Member
Srinidhi N R

I think you're stuck to handling all the different variants when you're building up your BDC data then, there can't be that many different screens?


There can be many condition types, so recording for each one wouldn't be generic BDC right?