Solved: FM table difference in Funds Management

zunaid_hingora2 · ‎06-04-2015

Hi,

This issue is in quality system for FM tables. Numbers of Tables are not matching with Production and Development system

In Quality, in se11, if we give *ECQ300* we have 2 tables as below.

FMFMOAECQ3000022

FMFMYCECQ3000024

In production in SE11. if we give *ECP300*in Database Table. Click on display. we have 8 tables as

below.

FMATGRECP3000001

FMATGRECP3000002

FMFMOAECP3000012

FMFMOAECP3000013

FMFMOAECP3000014

FMFMOAECP3000015

FMFMOAECP3000016

FMFMOAECP3000017

4 months back production system was copied to quality.

What would be the reason for this and how to solve this.

Regards

Zunaid

mar_novalbos · ‎06-09-2015

Hi Zunaid

Complementing Eli's anwer, let me share the outcome from Support:
There is also note 1675451 that delivers report 'RFFMCOMPARE_STRATEGY'. See its documentation:
This report enables the comparison of derivation strategy tables across clients via RFC.
The table names used in the rule type Derivation Rule (DRULE) are changed dynamically when the derivation strategy is transported via
the FIN_BASIS Transport Tool. The FIN_BASIS Transport Tool is used starting on release ECC 6.00. For older releases the standard transport tool was used and the tables for the rule type DRULE were not changed.

This report permits the evaluation of the rule type DRULE in detail using the tables in the logon and remote systems instead of assuming that the tables will have the same name in both systems. The result provides an overview of the evaluated rules and indicates when the rules are equivalent.

The name of the table may reflect the original system or the actual system where the table exists in. But from application point of view, the table name itself is actually not relevant. It does not have to be identical in all systems or correspond the system name.

So, there should be no problem in your case.

If you are addressing the derivation table names in your custom coding, this is not recommended. See note 1231815 as Eli suggested.

hope this helps. Feel free to share some other feedback you may have.

best regards

Mar

View solution in original post

iklovski · ‎06-04-2015

Hi,

Please, consult OSS note 1231815 - Predefined FMDERIVE tables are renamed during transport/CC

Regards,

Eli

mar_novalbos · ‎06-09-2015

Hi Zunaid

Complementing Eli's anwer, let me share the outcome from Support:
There is also note 1675451 that delivers report 'RFFMCOMPARE_STRATEGY'. See its documentation:
This report enables the comparison of derivation strategy tables across clients via RFC.
The table names used in the rule type Derivation Rule (DRULE) are changed dynamically when the derivation strategy is transported via
the FIN_BASIS Transport Tool. The FIN_BASIS Transport Tool is used starting on release ECC 6.00. For older releases the standard transport tool was used and the tables for the rule type DRULE were not changed.

This report permits the evaluation of the rule type DRULE in detail using the tables in the logon and remote systems instead of assuming that the tables will have the same name in both systems. The result provides an overview of the evaluated rules and indicates when the rules are equivalent.

The name of the table may reflect the original system or the actual system where the table exists in. But from application point of view, the table name itself is actually not relevant. It does not have to be identical in all systems or correspond the system name.

So, there should be no problem in your case.

If you are addressing the derivation table names in your custom coding, this is not recommended. See note 1231815 as Eli suggested.

hope this helps. Feel free to share some other feedback you may have.

best regards

Mar

zunaid_hingora2 · ‎06-09-2015

Hi Mar,

Brilliant. I agree with your above response. All tables are there in the system with different name.

Regards

Zunaid