Derivation Rule For Fund Management

Dear All,
Where we can maintain derivation rule for fund management???
Mahendra
help.sap.com

Dear Mahendra,
Please follow following link for PSM-FM
http://help.sap.com/saphelp_pserv472/helpdata/EN/ba/43d43ab8029b66e10000000a114084/content.htm
and for FI-FM
http://help.sap.com/saphelp_pserv464/helpdata/EN/ba/43d43ab8029b66e10000000a114084/content.htm
Hope this solves your query
Regards
Saurabh
Edited by: Saurabh Khandelwal on Nov 23, 2011 3:05 PM

Similar Messages

Change in Derivation rule in fund managemet

Hi Gurus
If i change derivation rule for fund center to cost center in between of fiscal year. will it make any impact on existing PO.
please give me your valuable input.
Regards
Shiv

Hi Shiv,
If I understood you well you want to know if one assignment bettwen funds center and cost center change if the PO will be automatically updated to the new assignment or not.
The answer is no and you can find all the hints in the following note:
658163 Acct assignmnt change: Determinatn of new FM acct assignmnt
If you want that the PO will be changed to the new assignment, the note provides also some workarounds that will allow you to do this.
I hope it helps you
Best Regards,
Vanessa Barth.

Validation rule in Funds management.

Dear Friends,
We use commitment items to monitor the budgets with overall budget for budget type Payment budget
In some cases, users are posting some adjustment entries to transfer the consumed budget values from one commitment item to another.
Ex:
Original Entry: Expenses incurred 1000, So entry booked with PK40, 123456 (expense GL), amt 1000, and commitment item ABC.
So at a later stage they came to know that they have used a wrong commitment item for the above document.(Correct CI would have been DEF)
So they are posting an adjustment entry like
PK40 GL123456 amt 1000 CI DEF
PK50 GL123456 amt 1000 CI ABC
So when i check the funds management doc for the above doc, FM uses VALUE TYPE 66 to do the transfer postings to commitment items, since these documents are giving wrong impact on my CI overall balances report FMRP_RFFMTO31X - Overall Budget -> Totals Records .
For the debit commitment item, it is not adding that amount in invoice column of above report, but it is comsuming the budget. So there is a mismatch in my total record for the debited commitment item.
For the credti commitment item, it is not deducting that amount in invoice column of above report, but it is increasing the budget. So there is a mismatch in my total record for the credited commitment item.
(Ex: Total budget-invoices-open items = Available budget) This is not happening at all
So i tried to restrict these kind of postings with a validation in FM like
Prerequisite: BPJA_VALID-FIKRS = 'AE69' (AE69 is my FM area)
Check: BPJA_VALID-WRTTP < > '66'
Message: Error message.
And activated the same in SPRO->PSM->FMG->Budgeting and Avl Control (Former Budgeting)->Budgeting (Former Budgeting)->Validation rules->Activate Funds Management Validation----
But still i am able to post those kind of documents.
Is there any other workaround for this restriction or can only be restricted by a validation?
Please corret me if i am wrong in validation condition expressions.
Thanks,
Srinu

Hi,
Actually we are using a Z program, which is copied from standard program as said earlier.
In the z program, we made some conditions to treat value type 66 also as like 54.
Now we are getting our report as expected.
Thanks,
Srinu...

Automatic Business Area Derivation Rule for Vendor Line Item in MIRO

Hello Experts,
We trying to use Business Area concept for our client.
I have completed all configuration setting for the business are derivation like
1. Creation of Business Area
2. Assign Business area to Plant / Division (OMJ7)
3. Business area determination from sales area (TVTA)
4. Business Area by Sales Area
5. Checked Field Status Group for Customer and Vendor Reconciliation Account
It is working for for compelete sales process and in Procurement cylce it is picking business for MIGO transaction both the line items.
But
In MIRO (Purchase invoice posting) it is automatically taking Business area to the GR/IR line item and it not taking Business area for the vendor line item (automatically)
I comes know that there is a business area derivation rule for this to happen automatically.
Can you please propose the soulution for the automatic derivation of business in MIRO for vendor line item.
Regards,
Chalapathi

Hi,
I do mot think there is a BA derivation rule for MIRO.
The best you can do is:
1. Use a user exit or enhancement point for deriving the BA from the GR/IR line and populate that in the vendor line
or
2. You make BA as a mandatory field in the field status group for the vendor reconciliation account. This will then force the user update the BA. We use this option. This is so because at times, the vendor item may need a different business area than the GR/IR line.
Cheers.

BPC Retraction for Funds Management

hi guys,
is there any FM or programs that we can use to retract data from BPC back to ECC6 for Funds Management module

In my project, customer has same requirement. We retracted BPC data to FM module by:
Option1 - FMCYCOPI_BW is a standard function, but issue: it can't provide detail information if there's error happened.
(1) Download BPC data to a BW Cube. (This step is not mandatory)
(2) in FM, use TCODE FMCYCOPI_BW to extract BW query (on that Cube) and generate FM documents. // you need to do some configure in SPRO FM.
Option2 - you can capture error while creating FM documents.
Write ABAP codes to retract BPC data and generate FM Documents.

Derivation rule for value fied

can any one tel me how we define derivation rules for value fields. is it posible to put derivation and how it
will effect.
Thanks&Regards
Amar

Hi
In COPA Derivation rules you can only map characteristic.. i mean you can derive only Characteristic values not for Value fields.
Value fields are normally mapped with SD conditions or GL accounts.
If you want to manipulate or recalculate the values flowing into value fields you need to use enhancements.
In this step you can set up system enhancements which are not supported in the standard R/3 System. These so-called "standard enhancements" can be used in the following areas of Profitability Analysis as below.
Derivation of characteristic values        (COPA0001)
Valuation                                    (COPA0002)
Direct postings to profitability segments (COPA0003)
Currency translation                        (COPA0004)
Actual data update                          (COPA0005)
Hope this helps
Regards
Venkat

Derivation rule for budgeting

is it possible to have a derivation rule where we can define for budgeting purpose that if we are using a particular cost center we could use only a particular commitment code only.
viewers please leave your hints/remarks so that any help could be received

How to change fund managment period from existing (APRIL TO MARCH)    TO OCT TO SEPTEMBER.
WE ARE TRYING TO CHANGE THAT USING
                 public cector mgmt
                                 fund mgmnt govt
                                               basic setting
                                                         fiscal year setting
                                                                     define fiscal year setting
there we have                       v3 as    april to march and
                                           v9 as    oct to sept
originally we had assigned v3 to Financial year and   to fund mgmt period both.
             but now we want to assign v9 to fund mgmt period.
But system is not allowing us to do that. How can we achive it and what are the reasons for errors

Derivation rule for service agreement

Dear Gurus,
I have derivation rules between GL-commitment item and Cost center - Fund center. now when i create PR & standard PO for type "cost center" the system is working properly by derives fund center and commitment item automatically but when i create service agreement the system doesn't derive fund center and commitment item. If anyone have any suggestions, please let me know.

Are there any conditions to the derivation rule?
In my QA system, I was able to create a derivation rule GL=Committment item. It worked the first time I created a scheduling agreement using ME31L.
Then I went into the "conditon" tab of the derivation rule and entered business transaction=RMBA and RMBE (purchase requisition and purchase order respectively) and the derivation rule did not work when i created another scheduling agreement.
Other than some conditions exist or the target field attribute is needed to be set to overwrite. I am at a loss to what the problem could be.

Derivation rule for Product from Material Group

Dear All,
Is it possible derive product from Material Group. The scenario is as below.
We executed KE30 report (Classic Drill down) for Product, the we are able to see the profitability for different products, when we click on the list button (Find button) againist the product at the bottom we found not assigned, we selected that and we found there are some un assigned amounts (without product). when we see the line items for the same the line items are coming with out product ( product field is emply)
Another observation is we created profitability assessment cycle (KEU5) in which cost center is the sender and material group is the receiver. when we run this cycle system is not distibuting the costs to the products, in the sender and receiver its executed with zero values.
In derivation rule KEDR we gave the logic to derive product from material group.
please guide the way which we are following is correct or not. can we derive product from material group.
Thanks,
Siva Reddy.S

Hi
Yes you can derive using "Derivation" method in KEDR and maintain a mapping of Mat Grp to Product... But that is not the right way
You need to find out why some lines are posted w/o products.. They can be genuine cases....
Also for assessment, either specify the Product as receiver or run KE28 Top Down Dist in order to allocate values from Mat group to Products..... Deriving Product from Mat group does not seem to be the nice way
br, Ajay M

Derivation rule for commitment code

is it possible to have a derivation rule where we can define for budgeting purpose that if we are using a particular cost center we could use only a particular commitment code only.
viewers please leave your hints/remarks so that any help could be received
Edited by: ca sanjeev mehndiratta on Jan 12, 2009 6:59 AM

over

Deleting derivation rule for the existing characteristic in operating conce

Hi all
My customer has two characteristics" Billing Doc(VBELN)" and" Warranty status" in the development and testing client and not in the production now.
Option 1 : Is to delete them but as the data is already posted for the same in the test and development client,it is lot more complex( involves implementation of OSS notes-SAPNET note 21207) .
Option 2: If we decide to keep them for now:These two have a derivation rules too. So can we simply delete the derivation rules so that data will not get posted to them( So will not effect the PSG i.e ce4xxxx table in production once the same transport is moved to production). There are no dependencies on this derivation rule.
Option 3: Can we also remove them from segment level characteristics?
Please let me know pros and cons ?
I really appreciate your time and effort.
Thanks & Regards
Sri

Hi,
If the characteristics have not been transported to production then why don't you delete them in the dev/test system ? Here you can take the risk.
To delete characteristics or value fields, perform the following
activities:
1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor. You can access it by choosing Tools -> Analysis -> Check Customizing Settings (TA KECM).
You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.
4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.
If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during the conversion.
A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->Jobs.
Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application help while still in the above transaction.
12. Once you have activated all the tables in the operating concern, generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
regards
Waman

Copa derivation rule for customer group

Hi All,
I am currently facing an issue with Derivation rule and hope someone can help me on resolving this.I have created a COPA derivation rule which has field as
Source Field
company code
Plant
Target field
Distribution channel
Condition
customer group 3 = 18.
so ideally with this conbination the distribtion channel gets updated
for the sales order.
However the issue we are facing is that the rule is working for only 1st line item and not for the others. I have also kept setting as" overwrite values only if new values found"
e.g if we see the accounting doc of billing then
line item 1 customer: x
line item 2 SaLes GL: rule works fine and dist channel is updated.
line item 3 discount GL: rule does not work.
Have checked the derivation rule and it looks correct.
Can you kindly suggest solution to this.

Hi Ajay,
Thank you so much for your reply.Please note that the GL is a cost element but the category in system is 1 and not 12.However I would like understand as to why is this happening.why does the system picks up derviation rule for a Gross sales GL and not for Discount GL(Cost element).
The distribution channel gets updated for sales GL when i check the prof segment of the line item, however this is not the case with doscount GL.
I would like to understnad the implication before changing cost element category from 1 to 12 as it runs across system.
Kindly provide some more explaination.
thanks in advance.

COPA derivation rule for GL fields

we are using Transaction type (BSEG_BEWAR) to store additional information for our Sales reporting. During the GL entry this field is update. I have created Derivation rule in COPA using table look up. The table I am using is BSEG. I have characteristics defined for Transaction type- WWTTY.
when the table lookup is populated I get following fields in source as target :
BSEG -
> BUKRS                                COPA --> BUKRS
BSEG -
> BELNR                               COPA -
> BELNR
BSEG -
> GJAHR                              COPA ---> GJAHR
BSEG -
> BUZEI                               COPA -
> WWDOC ( This is custom defined in COPA)
Assignment of Target Fields:
BSEG ---> BEWAR                                COPA -
WWDOC
Still I am in seeing COPA getting updated with Transaction type value.
Need input to solve this issue.
Thanks in advance

Hi Ajay,
Thank you so much for your reply.Please note that the GL is a cost element but the category in system is 1 and not 12.However I would like understand as to why is this happening.why does the system picks up derviation rule for a Gross sales GL and not for Discount GL(Cost element).
The distribution channel gets updated for sales GL when i check the prof segment of the line item, however this is not the case with doscount GL.
I would like to understnad the implication before changing cost element category from 1 to 12 as it runs across system.
Kindly provide some more explaination.
thanks in advance.

Derivation Rule for Partner Function

Dear Experts
I have some questions about COPA derivation rule.
I attempted to input a number for remark by using the partner function u201Ccontactu201D field in biling table (KNVP-PANRN).
Itu2019s always occurred error while SD entered PGI after I configuring the derivation rules.
My derivation rules as following:
Source Fields
KNVP     KUNNR     >>CO-PA     KNDNR
KNVP     VKORG     >>CO-PA     VKORG
KNVP     VTWEG     >>CO-PA     VTWEG
KNVP     SPART     >>CO-PA     SPART
KNVP     PARVW     >>GLOBAL USERTEMP3 (use MOVE for constant=CP in last step)
KNVP     PARZA     >>GLOBAL USERTEMP4 (use MOVE for constant=000 in last step)
Target Fields
KNVP    PARNR >>CO-PA WW001
Seems probably have some problems.
Could Experts give me a hint?

Problem solved.
I just set my constant numbers wrong.

Goods Issue activity creation for Funds Management Actuals Budgeting

Hi All,
We have implemented the commitment budget (PR/PO/GRIR) process at our workplace, and now we need to budget the actual consumption too (Goods Issue)
While trying to assign a strategy, I find that in the Activity Group, there is no Goods Issue activity group, but there are groups like Purchase Orders, Purchase Requisitions, Actual Posting, Controlling Posting etc defined for group numbers like 20,30,40,60, etc.
Do we need to create one, before we start budgeting the actuals too through the Goods Issuing process ? In that case, for the derivation strategy for this Goods Issue process, what value type and CO business transaction needs to be given to map it ? The value types too are categorised like invoices, payments, funds block, funds reservation, etc and the CO business transactions are FICA, RMBA, RMWA, etc, but there is not Goods Issue Transaction type.
Regards,
Wy

Hi Eli,
Thanks for the inputs !!
I suppose you meant Goods Issue comes under Value Type "54", which is named Invoices.
I checked out for possible derivations in the AVC Activity Groups and found a CO Business Transaction RMWL - Possibly felt that there must be a derivation with this and value type 54 to get the correspoding activity 40 "Actual Posting" - I got a bit confused seeing a separate Goods Issue transaction type and thus felt that there might be a separate activity group too.
Regards,
Wy

Derivation Rule For Fund Management

Similar Messages

Maybe you are looking for