In FMDERIVE does the "Overwrite w/New Value"...

[Former Member]

...button impact automatic Status Indicator on transactions.

Heres the situation. We had a major re-organization and I set up an LSMW to transfer asset value from assets linked to an old Cost Center to a new asset shell linked to a new Cost Center. This was done after the configuration was changed in FMDERIVE for the Internal Order/Funded Program fields where the Fnded Program field was set to Overwrite with New Value. This was done to accomodate the copy function in Purchase Orders and Purchase Requisitions when original order data changes from the time of origination to the time of realization.

It appears when we changed the configuration in FMDERIVE it stopped posting "Statistical" documents in FM and now everything is posting as real. Can someone explain if indeed that "Iverwriute New Value" button is somehow linked to the Statistical vs. Real button?

[Former Member · Accepted solution]

Hi Daniel,

The post with new value does not have that effect .

FMDERIVE is a interface tool between SAP modules and FM. Therrefore you have origin fields, and target fields. Now, when the target field is already filled, the system will not overwrite it, unless you flag it as overwrite w/ new value.

There are several reasons why your derivation strategy is deriving a statistical address, could you please check if your target commitment item is itself flagged as statistical in the master data?.

Cheers

[iklovski]

Hi,

The nature of the posting depends on two things:

a) attribute of the FM object (e.g. commitment item could be defined statistical and therefore all the postings on it would be statistical)

b) update profile or/and its modifications (OF37/OF39 transactions)

Regards,

Eli

[Former Member]

We finally discovered the problem. In our FMDERIVE table we have an assignement configured for all Asset transaction types to post to a Statistical Commitment Item. In our "Gold" client for some reason the "values" are blank for this assignment. When the transport for the Order/Funded Program rule were transported a pop up window requests, "Do you want to transport values?". This was answered YES. As a resulte the 18 values in the Quality and Production system in the Asset Transaction Type assignment were all wiped out. Evidently, our organization has a policy to update values manually in Quality & Production.

I disagree with this philosophy so we will be addressing the issue that the Table is not identical to what is in Production.

Thanks for your help.

Dan

[iklovski]

Hi Dan,

It's quite common to update derivation values directly in production. At least, in 85% of projects I took part in. The reason for this is simple: in DEV system there is not enough data to execute real test on the derivation strategy. The only thing you can do is to simulate...

Regards,

Eli

[Former Member]

Thanks Eli,

That does help me with the perspective on why we would not populate the values in the DEV coient.

Dan