FMCT for Converting old FI document, FMUP067 error message showned

[former_member648681]

Dear Experts,

Hi!

When we were conducting FMCT to convert old FI document as we tried to get FM on-line, the program show error message FMUP 067 "Functional Area is used as an entity in the general ledger. Reassignment not possible".

The Function area is used in General Ledger accounting, however, it is not activated and configured not used in FM area.

Besides, when I tried to post a new FI document exactly the same as the one that cause the error message, It was fine and the FI and FM document were all posted in the system.(The old FI documents was posted in the current fiscal year and the FM BCS was activated in the year)

Could any one suggest how to solve the problem so that we could convert the old FI documents and import these documents into FM module?

Thank you very much indeed.

Yours,

Kelvin Niu

[Former Member]

Please refer to OSS Notes 1379542. Hope this may help you issue.

Thanks,

Eva

[former_member184992]

Hi Kelvin,

FMCT should reassign the account assignment IF New GL is active but no scenario or customer field has been assigned to any ledger.

If this is your case, then you need to implement note 1283321 and 1282605. This notes will avoid error FMUP067 if your business scenario fits the pre-requisites of the notes.

If the notes does not apply to your business scenario please let me know which one of the following is yours:

Please review in which of the following scenarios is your case fitting in order to verify if the error message is being correctly triggered by the reassignment programs:

Scenarios:

1. New GL is active but no scenario or customer field has been assigned to any ledger.

In this case reassignment is allowed and no error message should be sent

2. NewGL is active and FM account assignments are being used as splitting characteristics but they are not updated in NewGL (this means that the relevant scenario that contains this field or the relevant customer field has not been assigned to any ledger). In this case reassignment is allowed and no error message should be sent from the FM reassignment programs.

3. NewGL is active and FM account assignments are being used as splitting characteristics and are updated in the NewGL (the relevant scenario that contains this field or the relevant customer field has been assigned at least to one ledger). However the zero balancing flag has not been activated for these assignments. This implies that balance sheets are being created because the customer wants to do a reporting based on these FM assignments.

In this case reassignment is not allowed and the error message should be sent from the FM reassignment programs.

Please note that as soon as the scenario or customer field is assigned to one ledger, reassignment for this account assignment will not be possible in FM.

So it is important that only the scenarios or customer fields that are really necessary to fulfil the customer's reporting requirements are assigned to the ledger(s).

4. NewGL is active and FM account assignments are being used as splitting characteristics and are updated in the NewGL (the relevant scenario that contains this field or the relevant customer field has been assigned at least to one ledger). In addition, the zero balancing flag has been activated for these assignments. This implies that full balance sheets are being created based on these FM assignments.

In this case reassignment is not allowed and the error message should be sent from the FM reassignment programs.

Please note that as soon as the scenario or customer field is assigned to one ledger, reassignment for this account assignment will not be possible in FM.

So it is important that only the scenarios or customer fields that are really necessary to fulfil the customer's reporting requirements are assigned to the ledger(s).

Special Ledger:

5. Special Ledger is being used and "field movements" have been defined on FM characteristics. These FM characteristics don't have to be necessarily defined as splitting criteria within SL. In this case reassignment is not allowed and the error message should be sent from the FM reassignment programs.

-

---

Please kindly have a look at the notes 1282605 and 1283321. These notes explain better the risks in case you were not receiving FMUP067.

Currently, the logic of these programs don't change the specific NewGL tables, so if the change/reassignment of a value would only be done in BSEG and in the FM totals table, but not in the NewGL tables, the information wouldn't be consistent any more between them. That is why the error message is sent: to prevent the inconsistencies from being created.

So our recommendation is either to reverse and to repost the FI documents (after changing the derivation rule appropriately) or to post manual correction postings to the documents already posted.

I am really sorry that I can not give you a more positive answer.

Best Regards,

Vanessa.