BAPI_CONTRACT_CHANGE

[Former Member]

when we call FM BAPI_PO_RELEASE and immediately afterwards call FM
BAPI_CONTRACT_CHANGE (in test sequence for example) the current
PO_REL_COD is reset.  This occurs only in contracts, not in POs.

If the FMs are not called immediately one after the other (for example in two separate test sequences and not in one), then this error does not occur.

anyone can help me to find solution

asher

[Former Member]

Did you use BAPI_TRANSACTION_COMMIT? if use, then write WAIT UP TO 2 SECONDS after FM BAPI_PO_CHANGE. you wont get this type of error.

[Former Member]

Hi Ravi

I did use BAPI_TRANSACTION_COMMIT and i wait up to 5 seconds after FM BAPI_PO_CHANGE.

its still not working

Asher

[moshenaveh]

Hi Asher,

It was brought to my attention that your question is more relevant for the SRM space, therefore I moved it over there.

Regards,

Moshe

[Former Member]

Hi Moshe

My problem is not SRM problem

i call this FMs in T-code SE37

and this problem relevant to contract not for PO

Regards

Asher