SAP for Public Sector Discussions
Foster conversations about citizen engagement, resource optimization, and service delivery improvements in the public sector using SAP.
cancel
Showing results for 
Search instead for 
Did you mean: 

Payment selection or commitment carryforward locked

0 Kudos

Hi experts. We have 7 companies working in the same productive system. We are getting this message "Payment selection or commitment carryforward locked .." when two companies are trying to execute FMF0 at the same time. I need your advice, how can I handle this situation. I tried to schedule FMF0 execution for every company, but their are complaining with this solution.

Regards,

Ruth

1 REPLY 1

mar_novalbos
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Ruth

There is the option to use parallel processing in FMJ2 which helps to improve performance. Also there is a flag to decide whether or not the documents should be locked.

However, generally FMJ2 should not be ran by several users at the same

time. Even if the documents lock is not selected, you are still using

S200 and therefore a general lock on the payment selection is

performed, despite of what's selected concerning to locks at document

level. This is for data protection.

So, at this stage we could suggest the following:

- Do not have several users running FMJ2 at the same time. Normally

mass transactions are intended to be ran by one user.

- Define parallel processing and schedule background executions,

in order to optimize user's times. I suggest to use job starting

conditions in order to have one job started after the previous one

is finished.

If your business process definitely cannot be changed, there would

be an option to deactivate the lock on S200 but I have to aware you

that it'll be a modification and therefore falls out of the SAP Support

Scope. If you definitely decide to implement a modification, you may contact SAP Support.

Reason and Prerequisites for the existing lock:

The commitment carryforward sets the same program lock as the payment

selection (FMF0, RFMS200). This is necessary since a simultaneously

executing the payment selection and the commitment carryforward would

result in data inconsistencies. Since payment selection can also update

cross FM area payments, the lock is set for an entire client.

Therefore it is not possible to start the payment selection in parallel

modes.

I hope this information will help you

Kind regards

Mar