cond. rate(kbetr) in tcode me32k does not change using BAPI_CONTRACT_CHANGE

[amol_samte]

Hi expert,

I need ur help...

I have a task to change CONDITION RATE(KBETR) in t-code:- me32k, i am using BAPI_CONTRACT_CHANGE....

Providing test data :

PURCHASINGDOCUMENT aggremnt

ITEM_COND_VALIDITY :

ITEM_NO 04850

SERIAL_ID

PLANT

VALID_FROM 16.12.2010

VALID_TO 31.12.9999

ITEM_COND_VALIDITYX :

ITEM_NO 04850

SERIAL_ID

ITEM_NOX

SERIAL_IDX

PLANT

VALID_FROM X

VALID_TO X

ITEM_CONDITION:

ITEM_NO 04850

COND_VALUE 0.033000000

CURRENCY USD

COND_P_UNT 100

COND_UNIT EA

COND_TYPE PB00

ITEM_CONDITIONX:

'X' for inputed ITEM_CONDITION(hope u will get)

but here is problem CONDITION RATE(KBETR) is not changing. and having return msg in bapi like :

after BAPI COMMIT

S BAPI 002 Instance UTCMAG of object type PurchasingContract has been changed.

S 06 023 Quantity Contract UTCMAG changed

I ME 713 Item 04850 for purchasing document UTCMAG has deletion indicator L

W MEOUT 018 No message generated for output of purchasing document.

Is m going wrong way or any good suggestion

Thanks In Adavance

Amol

Edited by: Rob Burbank on Dec 14, 2011 4:36 PM

[JL23]

i general the messages you receive are saying that the update was made, and the other messages are info and warnng messages which will not stop updating.

however, I miss the sense in this scenario. Why would you like to update a price for a deleted item.

Undelete this item in ME32K, then try your BAPI again and see if it updates correctly.

[amol_samte]

Thanks Jürgen L for your early reply...

i used another item no. after that below msg shows..

E BAPI 003 Instance PurchasingContract of object type UTCMAG could not be changed

E MEOUT 105 Internal error: KONP-ID_KONH 1 KONP-KOPOS 00

Thanks,

Amol.

[JL23]

I guess you have to debug the include LMEKOF20

[amol_samte]

HI issue resolved...

only COND COUNT field missing thats why des error happend..

Thanks,

Amol

[Former Member]

Hi Amol Samte,

I having same issues as well, i followed what u mentioned but doesn't work.

And i encountered this BAPI will took long time to process even though only just for one item transaction.

Hope you can give me some suggestion on this.

Thanks and Regards,

Nicky.

[amol_samte]

hi Nickcy ,

sorry for late reply..

test using test data using filed condition count....

if further issue...reply this...

if it is taking much time then put in background jobs.. m also using bj...

Thanks

amol

Edited by: amol Samte on Feb 6, 2012 6:33 AM