cancel
Showing results for 
Search instead for 
Did you mean: 

Release strategy is not triggering by creating and changing contract by Bapi

hassen02
Discoverer
0 Kudos

Hello SAP Community,

We are currently facing challenges with the creation and modification of contracts using BAPIs (specifically BAPI_CONTRACT_CREATE and BAPI_CONTRACT_CHANGE within a report program). The FRGGR, FRGSX, and FRGKE fields are not undergoing changes and remain in their initial state after the contract is created or modified so the release strategy is not triggering for those contracts by ME35K.

I have consulted SAP Note: https://me.sap.com/notes/0002868041.

My question is what kind of changes could we do in the specific report to changes FRGGR, FRGSX, and FRGKE fields so the release strategy can be triggered by ME35K ?

Thank you in advance.

Best regards.

Accepted Solutions (0)

Answers (2)

Answers (2)

hassen02
Discoverer
0 Kudos

Indeed, the release strategy is activated when a contract is manually created or modified in ME31K/ME32K. However, the issue arises when using BAPI_CONTRACT_CREATE and BAPI_CONTRACT_CHANGE for creation or modification. According to SAP Note 2868041, the problem is due to the active User Exit EXIT_SAPLEBND_002. In our scenario, this user exit is not active. Do you have any suggestions or recommendations?

thilakan_t
Participant
0 Kudos

Is the contract subject to release?

Is release strategy triggered when creating/changing the contract manually in ME31K/ME32K?

Check how it system is configured to trigger the release strategy. It usually triggers when there is a change in quantity or price.

SPRO -> Material Management -> Purchasing -> Contract -> Release Procedure for contract