BW 7.0 - Extraction of the FM derivation rule gl_account - commitment item

Hello,
I need to load in BW the FI-FM tables of the derivation rules between GL account and commitment item.
The particularity of these tables is that their name is client-dependant.
Example: the table name in development system is: totoDEV; in production system: totoPROD.
I created a specific datasource based on table SKA1 and added the commitment item in the extraction structure .
Now, I have to write the function EXIT_SAPLRSAP_002. I know I need to use a variable for the table name but I don't know how to do that, because I can not declare the production table in development system. I need some abap help!!
Great thanks in advance.
Jacques

Hi,
I can think of three possibilities for a solution.
1. Store the name of the required table in a config table and select at runtime
2. use an 'IF' or 'CASE' statement to deterimine which system you are currently in and then place the required varible within this statement.
3. Preferred solution: use a Field Symbol to assign the table at run-time, this way no errors will occur and your program will compile.
There are many examples of FIELD SYMBOLS on SDN and even the F1 help in SAP.
regards,
CH

Similar Messages

"Error occurred in derivation rule" & "No commitment item entered in item".

Unable to create Purchase Request (PR) and the following error message shows
"Error occurred in derivation rule. See Long Text"
Diagnosis
Fund From Commitment Item
No entry in a derivation rule was found for the specified source fields.
The derivation rule was set up that an error message appears when this happens.
The required derivation rule entry would need the following source fields:
Commitment Item
xxxxxxx
Procedure:
Create an entry in a derivation rule for these source field values. Make sure that entries exist for all the valid source field values. If the derivation should not always be carried out, you can also define rule so that no error message appears if a derivation rule entry does not exist.
Can any one help how to find out the root cause of the error and solve this issue
Regards,
GB

I was able to duplicate your error by creating the following.
I went to transaction FMDERIVE and created a derivation rule and named it "Fund From Commitment Item".
On the definition tab, I selected committment item (COMMIT_ITEM) for the source field and the target field selected (FUND).
The condition tab was left blank. NOTE: On the attribute tab I selected the option "Issue Error Warning If No Value Found).
I entered no rule values (F9) within the rule (for example such as commitment item XXXXXXX = fund YYYYY) and saved.
After creating this derivation rule, I get the same error message because there were no values in the derivation rule (the source commitment item used was not found in the rule).
If Fund is a field that is always keyed manually then I would not have such a derivation rule.
But you may have some exceptions (like we do) and in the case of exceptions you can populate the derivation rule with those exceptions... i.e. whenever commitment item XXXX is used then the fund should be equal to YYYY further using your conditions and attributes for your custom needs.

Derivation of wrong commitment item in ML81N

Dear all,
A material document is created in ML81N with expenses a/c Dr. & provision for expenses a/c Cr & the budget is cosumed with debit of the expenses.& also Cr of this provision for expenses.Because the system defaulting the committment item of the expenses which is different from the commitment item attached to the provision for expenses G/L.
I have enhanced the derivation rule in FMDERIVE with checking the business transaction,G/L & commitment item.Then switch on Trace. Then while saving/posting/checking transaction i can see business transaction and other details also.
Even then the same problem is exist.
Now can any one advice me how to proceed further.
Thanks
Shivaji

Hi Shivaji,
Please check the following hints:
1) First of all, we need to be sure that all existent correction notes are implemented in your system. Please check if the following notes are applied in your system (including manual steps):
1289547 FM account assignment incorrect in GR/IR clearing in service
1450965 FM account assignment incorrectly inherited from PO
1480503 FM account assignment for GL line overwritten in MIRO
1502874 Planned Delivery Costs are not updated during GR/IR postings
These notes correct wrong behaviours in include LFMCOBLF06 related to account assignment.
If the notes are not there (and valid to your release/package), please apply all in one test system and retest your issue.
2) Regarding inheriting the FM assignments, material po's can retrieve the FM account assignments from the FM tables. This insures that the current FM account assigments are always used.
However, in the case of Services, it is not possible to use the FM tables as it is not guaranteed that the correct Account assigment will be retrieved. So, the SES table ESKN is used instead. The ESKN record is created at the time the SES is created.
So, the Invoice should inherit from the GR. But, it is not possible to read the FM tables to get the account assignment.
3) Talking about your derivation rules (i believe you checked this already), please enter in the derivation rule -> Definition Tab, double click in the name of your Target Field (bottom part of the screen).
There you will find the fields:
( ) Do not overwrite if Fld Already Filled
( ) Overwrite with new value
( ) Overwrite with new value if new value is not empty.
I believe you should have marked the first option due to your business requirements described in this thread.
4) I believe you have set your derivation rule to derive commitment item with the function module FMDT_READ_MD_ACCOUNT_COMPANY "Read Account Master Data". For additional information, check note
839488.
5) You can also add Conditions to your Derivation step regarding commitment item to not perform the step when (VORGN = 'RMWE' AND KTOSL = 'WRX') OR (VORGN = 'RMRP' AND KTOSL = 'WRX'). To simplify the maintenance of this condition, the Temporary flag could be used instead. You can set this flag in a previous step using the attributes above and then use that in the Condition list.
I hope this helps. If nothing helped, let me know the content of table FM01X in your system and your current release/package.
Best Regards,
Vanessa.

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

No fund derived for stadistical commitment item: error F6804

Hello,
While posting a payment I face an exchange difference. The exchance difference account has an "stadistical commitment item" related in the GL master data.
While posting and following the fmderiver tracking I see that the account tries to get the line item related to the invoice but the due to fmderiver I overwrite that commitment item and I took the one (teh stadistical) from the GL master data.
Then, when it tries to save it I get error f6804 as the system says that it is not able to trigger the fund, but as it is stadistical it should not be mandatory, isn't it?
Please let me.
Regards

Hi,
Statistical nature of commitment item is relevant only for budget control. There will be no AVC applied to postings on statistical CI. It has no influence on the requirements of the system to introduce full FM assignment.
As for the fund, it matters only for the reporting: if it means something for you which fund to apply for these postings, then define a rule accordingly. Otherwise, pick any fund available.
Regards,
Eli

Reconstruction for FI doc after derivation rule change

Hi SAPers,
My client needs to change the derivation rule for year end. For PR and PO reconstruction, i understand that we can use RFFMRP34N and RFFMRP02N.
What is the procedure to reconstruct FI document to update FM based on latest FMDERIVE? If i understand correctly on the message, we need to delete old dataset (RFFMDL02) and then run RFFMRP20, then finish by executing BPINDX03. Is my understanding correctly or is there any other thing that i need to check?
Thanks a lot for replying.
EG

Hi Mar,
I might be wrong, but if i only execute FMN0, the accounting document from GR of PO still goes to the commitment item on PO. Below is the steps that i performed:
1. Post PR, PO, GR using commitment item X.
2. Change the derivation rule to commitment item Y.
3. Delete Actual data using (RFFMDLFI).
4. Run Supplementary Account Assignment using FMCN, and convert it. This updated the commitment item Y in the GR document.
5. Run S_ALR_87012637 - Totals Records for FI Documents to see whether FMCN updates FM, and i can see that the GR document that i deleted still missing in FM.
6. Run FMBV, but report FMRP_RFFMAV01X - Annual Budget still does not show changes, and the document is still missing.
6. Run FMN0, and put the document number.
7. Run S_ALR_87012637 - Totals Records for FI Documents again, and the GR document is updated
8. Run report FMRP_RFFMAV01X - Annual Budget, but apparently, even though the commitment item has changed to Y, it updates at commitment item X.
9. Run FMBV again to reconstruct the assignment, and no changes.
Then i tried another way.
1. I deleted PO commitment data (RFFMDLOI).
2. I and reconstruct PO again using FMN4N.
3. I run FMN0 using the GR document as reference.
4. I run report FMRP_RFFMAV01X - Annual Budget, and i can see that the assignment is correct.
Did i miss something, or this is what we should do if we have FM data from GR or Invoice?
Thanks a lot for the explanation.
CW

Error ocurred in the derivation rule

Hi Guys
I am trying to create a sales order. But having this error
(error ocurred in the derivation rule) Msg no. K/111
How do I fix this please.
Thanks

Hi
The error desciption means that the issue is in the derivation rules for the source fields.
No entry in a derivation rule was found for the specified source fields.
The derivation rule was set up so that an error message appears when this happens.The required derivation rule entry would need the missing source fields.
Please click on the error message which should give you the missing source fields list. Maintain configuration in tcode KEDE and KEDR for the these fields and save,
Let me know if there are any issues. Hope this helps.
Karthik

Replicating COPA derivation rules in BI

Hi All,
We have a requirement where we are creating an extractor and COPA derivation rules available in ECC needs to be replicated in BI. My doubts are-
1. Could this be directly achieved in BI, if yes then how would we maintain sync between the ECC derivation rules and the replicated ones in BI. If there is some update on these rules, how would the respective BI rules get updated?
2.Should this be handled during extraction in ECC itself. If yes, what is the best approach for this?
any pointers catering to the above questions and anything related to mapping derivation rules in BI would be a great help.
Thanks in advance for your help and time.
Regards,
Bansi.

Hi AMK,
As a protocol that is followed on this site, please do provide points in case the replies helped, this helps in motivating the people to keep posting for the queries and also helps in keeping the spirits of the team high.
Regards
Ashish

Derivation rule in COPA from BSEG

Hi experts,
My issue is to derivate a field (SEGMENT) from Table BSEG in COPA.
Unfortunatly my customer donu2019t use the standard customizing from the SEGMENT derivation rule, we donu2019t populate the field SEGMENT in the profit center master data.
Firstly, with a user exit (U903 - ZRGGBS000) which is trigger with substitution rule we populated the field SEGMENT in BSEG.
Now I created a new characteristic WWSEG and I canu2019t derive it in KEDR with table look up, can I have your advices please?
With an abaper, we tried to find a solution with the COPA0005 exit but he donu2019t find the logic to map the source field BSEG-SEGMENT and the target field COPA-WWSEG
Thanks
Kinds regards
Cédric

Hi Waman,
Thanks a lot for all and thanks to Dave.
But it doesn't work.
The segment in bseg-segment is filled when posting a FI document.
For reminder, the field BSEG-SEGMENT is firstly filled with a user exit.
We implemented the note 1135567, we created the program ZRFI_OSS_KEAK_SEGMENT adapting the code to our characteristic WWSEG, when we tested, in debug we drop in the Abap code but the structure COBL-SEGMENT is not filled, therefore the WWSEG is not filled.
Have you other idea to solve my issue ?
Best regards
Cédric

Error occurred in derivation rule

Dear All,
After saving the billing document, & it is not realesed to A/c. Document.My client came across the following error;
Error occurred in derivation rule. See long text
Message no. K/111
CO-PA Characteristic Derivation
Diagnosis
Step 0031 Category --> Item Category Dummy
No entry in a derivation rule was found for the specified source fields.
The derivation rule was set up so that an error message appears when this happens.
The required derivation rule entry would need the following source fields:
Customer
31970063
Procedure
Create an entry in a derivation rule for these source field values. Make sure that entries exist for all the valid source field values. If the derivation should not always be carried out, you can also define a derivation rule so that no error message appears if a derivation rule entry does not exist.
Maintain entries
Maintain derivation strategy
Waiting for the response.
Thanks & Regards,
SPT

Hi,
Check value fields assigned to each condition types and take a help of FICO consultant.
Use this link to understand what configuration steps need to be taken accross.
http://help.sap.com/saphelp_46c/helpdata/en/7a/4c38e14a0111d1894c0000e829fbbd/content.htm
Thanks,
Swamy H P

Derivation Rule

Dear All,
I have Issue with derivation rule, When we create billing doc and try to post this to accounting. Its is throwing up message
"Step 0031 Customer --> Intercompany Indicator
No entry in a derivation rule was found for the specified source fields.
The derivation rule was set up so that an error message appears when this happens.
The required derivation rule entry would need the following source fields:
Customer 1"
Could some pls tell me how to resolve this issue. Pls guide me through the whole process.
Thank you.

In Derivation rule there would be a mapping of each customer to an Intercompany indicator. Check Transaction KEDR. KEDE for the customer
Anand

Error occurred in derivation rule in SAP

Hi All
i am trying to post the document as well to create the new PR i am getting the below error messge as
'Error occurred in derivation rule. See long text
Message no. K/101
Diagnosis
: Fund From Commitment Item
No entry in a derivation rule was found for the specified source fields.
The derivation rule was set up so that an error message appears when this happens.
The required derivation rule entry would need the following source fields:
Commitment Item
350801
Procedure
Create an entry in a derivation rule for these source field values. Make sure that entries exist for all the valid source field values. If the derivation should not always be carried out, you can also define a derivation rule so that no error message appears if a derivation rule entry does not exist.

Hi Krishguna,
You need to check your derivation rule, T. Code: FMDERIVE for Fund then activate the trace, this will help you why fund is not deriving from commitment item, or tell us the detail of derivation for fund you have set.
Thanks
Javed

Derivation Rules Not Working for other company codes

Hi,
I have 5 Company codes and only for one FM was activated. now i want to activate FM for all 5 company codes. for which i have assigned the FM area to all 5 company codes. I have also assigned the derivation strategy to all 5 company codes as well. now when i post a transaction for any other company code derivation rules is not being process hence no commitment item or fund center is derived. however for the original company code for which FM was activated in the first derivation rule are working fine means system is deriving commitment item and fund center. can any one tell me why derivation rules are not working for other company codes? do i have to add Company code in source field of derivation strategy? could this be the reason? because in beginning there was no other company code so we did not included any company code field in the first place.
Regards,

Faizan,
Go to Funds Management Government> Actual and Commitment Update/Integration> Activate/Deactivate Funds Management.
In the screen create an entry for each Company Code and Funds Management Area combination.
Activate the AA Derivtn flag if you want the derivation to be called and the Update flag if you want to update commitments and actuals in FM.
Thanks
Shyam

FM derivation:Service no with commitment item

Hi All,
I have a requirement in FM that, there are several marketing related services are getting from vendors.. my client wants to control the budget against each Service No in the service Purchase Order.. i want to give the Service no= commitment item in the FM Derivation Rule... i have gone through the SDn. Com... some BADI/User Exit will resolve this issue... am not much familiar... i f u have already worked on the above scenario.. could you help me ..
Thank

Hi,
System will have error message once budget exceeded!
You have value for service budget and did you have message setting as error with message number with application for BP-629 and BP-603 in t.codes:OBA5 and OBMSG.
Regards,
Biju K

Derivation rule at asset retirement

Hii experts,
we have requirement of assets procurement through grants they receive. Funds of fund center got consumed at the asset acquisition but when i m triyng to retire/scrap assets... its giving an error for FI313 I.e
No funds center entered/derived in item 00001 (1000/2000000122/)
I came to know that we need to prepare some derivation rule of the retirement of assets to resolve the issue.. Please guide me as i am very new to grant management...
Regards,
Abhay

Dear Abhay,
Since you have created Asset Codes in Asset Master, you have to provide Asset Codes in Asset Retirement Derivation Rule, so that system can derive proper values as per your derivate rule. You have to maintain the following derivation rule for Asset Retirement:
Transaction Type (TT)+Asset Code (To-From)+Document Type(DT)=Target Commitment Item
Mention all the Asset Code number ranges maintained in the system, while Document Type AA will be used for TT 200 (Retirement without Revenue) and Document Type DR will be used for TT 210 (Retirement with Revenue). You can derive statistical or dummy commitment item (60 and 3) for processing of transaction.
Further, you can also add cost centre as source field to derive funds centre. Also make sure you keep the rule in the logical order, since it may affect the derivation of fields. Also check note 666322 to make use of trace feature to ensure proper derivation of values.
I hope this will resolve the issue.
Regards,
Amar Lal

BW 7.0 - Extraction of the FM derivation rule gl_account - commitment item

Similar Messages

Maybe you are looking for