Skip to Content
avatar image
Gary King

BDC issue when using with CALL TRANSACTION against ME11 (Purchase Information Record)

Feb 15, 2018 at 09:48 AM | 70 Views | Last edit Feb 15, 2018 at 09:50 AM 2 rev.

Hi, I'm using a BDC recording and actioning it, not via SM35 but using a CALL TRANSACTION against transaction ME11 (PIR). This works fine in most cases, but every now and then we hit an issue. The issue is that for most Vendor/Material/Purchasing Org (we don't use plant) there could be one, or more, Condition types. Normally there is just one (PB00) but sometimes we are shown a pop-up screen requesting to know which of the three condition types to use. What I need to know before I use the BDC recording is what condition types are avaailable, based on the Vendor/Material and Purchasing Org fields being used. If I know this in advance I can craft the recording to work without issue, either allowing for this popup sub-screen, or not.

Does anyone know a table or FM that can be used to find out this information before the BDC is then used?.

ABAP Development
MM Purchasing | SRM Purchase Order | abap
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Jürgen Lins
    Feb 15, 2018 at 10:14 AM

    Start from A018 table and then find the corresponding records in KONH, KONP and KONM

    I used to load the prices separately, my ABAP skills are not that elaborated to do what you are planning to do

    see my blog https://blogs.sap.com/2013/12/26/difficulties-in-price-condition-load-for-purchasing-info-records-with-conda-idoc-method/

    Add comment
    10|10000 characters needed characters exceeded