Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error BAPI_CONTRACT_CREATE ID 06 Number 76

Epena
Participant
0 Likes
787

Hello, I hace a problem with BAPI_CONTRACT_CREATE.

I created an outline agreement with reference to a purchase requisition not using the whole ammount. Then I try to create another outline agreement with reference to the same purchase requisition for the remaining amount, however, when trying to create the second one I get the following error:

ID: 06

Number: 076

Message: Materials of requisition & item & alr. ordered in full

However it's not true, the materials for the requisition being used is not ordered in full....

The BAPI throws the error on method COMPATIBILITY_CHECK (LCL_INDEX_CON), include: LMEREQSF01 when trying to validate the following:

* no reference to fully ordered PR

    l_eban = l_req->if_purchase_requisition_item~get_persistent_data( ). "1339645

    CHECK im_creqs-varkey(1) = '#'.                         "1346997

    IF l_eban-menge LE l_eban-bsmng OR

       l_eban-ebakz NE space OR

       l_eban-bsakz EQ 'R' AND

     ( l_eban-statu EQ 'K' OR

       l_eban-statu EQ 'L' ).

      re_success = mo_const->no.

      MESSAGE e076(06) WITH im_creqs-banfn im_creqs-bnfpo INTO gl_dummy.

      mmpur_message_forced sy-msgty sy-msgid sy-msgno

                           sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

    ENDIF.

  ENDMETHOD.                    "compatibility_check


The values for our variables are:


L_EBAN-MENGE = 100.000

L_EBAN-BSMNG = 0.00

L_EBAN-EBAKZ = ' '

L_EBAN-BSAKZ  = 'R'

L_EBAN-STATU = 'K'


KNTTP and PSTYP for both utline agreements (the one succesfully created and the one with error):


KNTTP = U

PSTYP = 8


I'd really appreciate your help!!!


Best Regards.

1 REPLY 1
Read only

DavidLY
Product and Topic Expert
Product and Topic Expert
0 Likes
569

Hello,

This issue is caused by SAP note:
1346997 implemented by support package

As per system design functionality is different for BAPI_CONTRACT_CHANGE

Please read information in SAP note 1346997.

Regards,

David