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: 

Error FMCF108 in FMJ2 - Year-End Closing: Carryforward of Open Item

Former Member
0 Kudos

Hi Experts,

I'm using PSM BCS (Budget Control System)

1. I have defined a ''Derivation Strategy for Reassignment''

2. then, Assign Strategy for Reassignment to FM Area

3. I executed FMJ2 transaction to value type 51 (Purchase Orders), but the system shows the message: Reassignment of account assignment element Commitment Item not possible

The Define Account Assignment Derivation is not compatible with the Define Derivation Strategy for Reassignment. The value Z_GASTOS was determined for document no. 4100000008, the reassignment strategy for account assignment element Commitment Item. However, this was overwritten with value SUMINIS_Y_ART_FERRETERIA through the account assignment derivation of Funds Management.

We have SAP ECC 6.0 SAP_BASIS SAPKB70107

Thanks in advance.

José Luis

Edited by: José Luis Rodríguez on Oct 4, 2011 6:01 PM

1 ACCEPTED SOLUTION

mar_novalbos
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Jose Luis,

Normally FMCF108 long text describes the reason of the problem , as the strategy for reassignment needs to be compatible with the account assignment derivation.

During reassignment using the standard reassignment tools or when performing reassignment during the commitment carry forward process, message FMCF-108 ('Reassignment of account assignment element % not

possible.') may occur. This message is received for example when the Purchase Order line item has an account assignment category that does not allow changes to the account assignment based on its current state.

In most cases, this message is raised PROPERLY. If the user cannot make the change manually with the PO Change transaction (ME22N), then the fields will NOT be able to be changed automatically with the reassignment tool (FMCT) or with the CCF transactions (FMJ2).

There are several possible solutions to the problem:

1. Update the account assignment category to allow changes when follow

on documents have been created. Set field 'Acct.assign.changeable'

in the account assignment category to 'X'.

2. Update the field status settings for the account assignment

categories so that they are an optional entry (instead of being

hidden or display only).

In some situations, a combination of the two steps above may need to be implemented to successfully prevent the error.

Hope this will help you

Kind regards

Mar

View solution in original post

1 REPLY 1

mar_novalbos
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Jose Luis,

Normally FMCF108 long text describes the reason of the problem , as the strategy for reassignment needs to be compatible with the account assignment derivation.

During reassignment using the standard reassignment tools or when performing reassignment during the commitment carry forward process, message FMCF-108 ('Reassignment of account assignment element % not

possible.') may occur. This message is received for example when the Purchase Order line item has an account assignment category that does not allow changes to the account assignment based on its current state.

In most cases, this message is raised PROPERLY. If the user cannot make the change manually with the PO Change transaction (ME22N), then the fields will NOT be able to be changed automatically with the reassignment tool (FMCT) or with the CCF transactions (FMJ2).

There are several possible solutions to the problem:

1. Update the account assignment category to allow changes when follow

on documents have been created. Set field 'Acct.assign.changeable'

in the account assignment category to 'X'.

2. Update the field status settings for the account assignment

categories so that they are an optional entry (instead of being

hidden or display only).

In some situations, a combination of the two steps above may need to be implemented to successfully prevent the error.

Hope this will help you

Kind regards

Mar