Skip to Content
0

Funded program derivation not being derived correctly

May 10, 2017 at 09:45 AM

123

avatar image

Hi all,

I am deriving FM account elements using source fields GL and Plant to derive Commitment Item, Funds Center, Functional Area, Fund and Funded Program. This is for MM purchase requisitions. When i create a PR and trace the derivations, at the time of entering the PR, all objects are derived correctly and both GL and plant are filled up as source fields - Event is CHECKALL.

But when i check the document before posting, event changes to OPENITEM and GL account is no longer being filled up as a source field. Source field becomes only plant. The cause of that is Funded Program is no longer being derived and the system will issue a budget error.

Kindly assist.

Jordan.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Eli Klovski
May 10, 2017 at 11:26 AM
0

Hi,

Please, check if note 1330498 - FMDERIVE to re-derive values instead of reading from buffer

is implemented in your system.

Regards,

Eli

P.S. Also check this one:

1532905 - Buffer table not properly updated within FMDERIVE

Show 6 Share
10 |10000 characters needed characters left characters exceeded

Hi Eli,

I have implemented the changes to the function modules as required by the notes but the problem is still there.

Regards

Jordan

0

Do you have event field available in the trace? How can you distinguish between CHECKALL and OPENITEM?

Is note 1691314 equally implemented?

0

Hi Eli,

Sorry for the delayed response. The field Event is displayed in trace. This is where CHECKALL and OPENITEM are being displayed. At the time of entering the data in the PR, the even is displayed as CHECKALL. Here all the segments are derived correctly. But at the time of checking or posting the PR, the event field is displayed as OPENITEM. This is when the system doesnt derive the other segments.

Regards

Jordan

0

Well, you can make a workaround, putting the event into the rule and not overwriting already derived value.

Or simply define in a rule, that initial value cannot overwrite existing one.

0

Hi Eli,

Can you assist with an example? How do i put the event into the rule? I don't see event as an object definable into a rule.

Regards

Jordan

0

Just put this option in the rule

xnlld.png (3.0 kB)
0
Jordan Senior May 18, 2017 at 09:17 AM
0

Hi Eli,

Thanks for the prompt responses. After implementing your recommendation the system is still dropping the derivations. It still cant derive all objects at the time of posting. It only derives them at the time of entering the data.

Regards

Jordan

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Once derived, they shouldn't be erased if you set the rule in the way I showed.

Set a trace in FMDERIVE and check why the data is erased, i.e. which step is erasing it.

0