cancel
Showing results for 
Search instead for 
Did you mean: 

Amount in Group Currency must be filled - File Upload migration FI Historical Balances

regysm21
Active Participant
0 Kudos

Hi Experts,

we are trying to upload the FI historical balances using the File Upload in S4 and I am getting the following error because the group currency column values are not filled:

Amount in Group Currency must be filled

In the file upload, there is not mandatory to fill the group currency/amount fields. Also in the mappings of LTMOM I removed the mappings, but still getting the same error.

Can you please give me a hint, how is it possible to migrate without uploading the group currency but only the transaction and company code currency?

Thank you and best regards,

Regys

regysm21
Active Participant
0 Kudos

Hi Experts,

do you have a suggestion on this please? I debugged it and saw the error, however I cannot deactivate that code. Is there any alternative, perhaps in customising that can be done so that they get automatically generated?

Thank you!

Accepted Solutions (1)

Accepted Solutions (1)

FrankFinkbohner
Advisor
Advisor

Hi Regys

what release are you using?

The object above is a custom object that contains also additional fields in Sender and Receiver that are not within the original object. Do you get the error message with the original object?

Which API are you using custom API or FINS_MIG_HIST_BAL_UPLOAD. The original FM does not contain the fields Functional Area and the other following fields.

The error message "Amount in Group Currency must be filled" is probably FINS_MIG_HIST_BAL 012 that is called in CHECK_DATA of cals CL_FINS_MIG_HIST_BALANCE. The error message is thrown if ACDOCA-KSL "Amount in Global Currency" is empty.

If you don't fill the groupcur it will be derived via customizing and ksl is filled with amt_groupcur.

If ksl is empty you will always get that error message.

**Empty amt_groupcur
IF ls_input_acdoca-ksl IS INITIAL.
MESSAGE e012(fins_mig_hist_bal) INTO ls_message-message.

Have you checked the documentation of the original object?

FI - Historical balance | SAP Help Portal

  • Currency and amount:

    • All currency amount fields in the migration template are mandatory. The amounts will not be derived automatically.

    • Transaction/document currency is mandatory. Local/company code currency and group currency are optional and will be derived automatically by the customizing settings maintained in system. An error message will be displayed if those currencies are filled in the template but don’t match the customizing settings.

    • Recommendation: provide all currency information via the template to ensure the provided amounts match to the related currencies. Otherwise, inconsistencies might be migrated.

Please check with the original object if you get the same error. If yes you may open ticket on component FI to ask for assistance here, why error message is coming up.

BR

Frank

regysm21
Active Participant
0 Kudos

Hi Frank, thanks a lot for the reply.

We are using release S4/HANA 2021 SP 02.

Yes this is a z-copy of the standard migration object and I added there also some more fields that were required by business. The error however is the same as in this custom object and also in the standard object (tested there too).

Yes, I read the documentation and there is saying that is optional and could be derived from customizing, which I assume it is in place as we do not have such issues with other migration objects ( FI G/L Account Balances and open line/items and also FI AR open items/AP open items. There the group currency also get automatically calculated by the system using the actual customizing.)

Do you have any suggestion what specifically in customizing must be in place so that it derives the group currency from there?

Thank you in advance,

Regys

P.S: We also opened a ticket.

FrankFinkbohner
Advisor
Advisor
0 Kudos

Hi Regys,

The amounts are all mandatory (1st sentence of the mapping instruction above)

"All currency amount fields in the migration template are mandatory. The amounts will not be derived automatically."

Only the currency is optional and will be derived automatically if not set but group amount must always be filled.

So, you cannot leave the group amount empty, If you check the method MOVE_DATA in the same class as CHECK_DATA you will see that

CALL METHOD cl_fins_mig_delta_common=>get_curr

is called to fill the currencies and then ls_curr-hwae2 is used to fill the groupcur if not filled.

The logic here is very complex. I don't know the customizing settings that needs to be place here to get it collected, The colleagues from FIN may tell you this via the ticket. But you definetly need to maintain the amounts of all currencies (CC, Transaction and Group).

Best

Frank

regysm21
Active Participant
0 Kudos

Thank you very much Frank for the reply. It seemed exactly that the group currency amount is mandatory but the currency of it not. I was just confused from the statements in the SAP Help documentation below:

  • All currency amount fields in the migration template are mandatory. The amounts will not be derived automatically.

  • Transaction/document currency is mandatory. Local/company code currency and group currency are optional and will be derived automatically by the customizing settings maintained in system. An error message will be displayed if those currencies are filled in the template but don’t match the customizing settings.

I uploaded the file only with the amount in the group currency and without the currency itself and it was simulated without issues.

Best regards,

Regys

Answers (2)

Answers (2)

Sybille
Product and Topic Expert
Product and Topic Expert

Hi Regys Mene,

please open an SAP incident in component: CA-LT-MC.

Best regards,

Sybille Lackermeier, SAP S/4HANA migration cockpit Product Management

FrankFinkbohner
Advisor
Advisor
0 Kudos

Hi Sybille,

the screenshot shows a custom object that is not identical with the delivered object.

Additional fields and modified mapping.

As you know, SAP will not give any consulting to custom objects.

Opening a ticket will therefore not solve the problem.

BR

Frank

Lakshmipathi
Active Contributor
0 Kudos

Have a look at this discussion where similar issue was discussed