FM DERIVER Custom field in Derivation Rule

Hi Experts,
I want to have a custom field while defining Derivation Rule in TCODE FMDERIVE, the field I require is Storage Location LGORT. Inorder to achieve this I have used Customer Include in structure FMDERIVE and inserted field LGORT.
Now the problem is that when I am defining my custom Derivation Rule using custom field Storage Location, the rule is not determined.
Could u please help me in this.
Thanks n Regards
Rohit

Hi
Go to
Spro -PSFM-FMG-Master Data-Allocation to account assignment from other components -select derivation steps
here u selct 3 option
cost center to commitment-item/fund ctr/fund function
then define account assignment derivation
here u define Derivation rule whcihever u define
here u find tables and field whichever u find
if nay query, revert back
Regards
Roobal

Similar Messages

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 CO-PA, number of target fields

Hi all,
is there a possibility to have more than 6 target fields in a CO-PA derivation rule or is the only way to handle more fields with a separate rule based on the same source field?
thanks for your help
kind regards
Adrian

Dear Adrian,
If you want to update more than 6 target field in one derivation step, as for I know is not possible but create a new derivation step with same source and additonal target fields, otherwise use exits.
Regards
Ravi

Derivation rule to determine customer tax classification in COPA

Hi Experts,
Please guide me to complete this assignment.
The requirement is to fetch the material tax classification and customer tax classificaion into COPA through derivation rule.
we can fetch material tax classification through table VBRP.
Please help me to derive customer tax classification( KNVI-TAXKD) through derivation.
Customer tax classification data is available in table KNVI.
But when you consider KNVI table through table lookup it is asking customer, country key and tax category. To define this derivation rule we need tax category values in COPA.
We can get customer and country key but not tax category.
How to bring tax category (KNVI-TATYP)
into COPA to define derivation rule to fetch customer tax classification( KNVI-TAXKD).
Please suggest me if any alternative solution to bring customer tax classification data into COPA.
Points will be assigned to usefull answer.
Thanks in advance.
Regards,
Amar.

HI,
The Tax related thing are balance sheet items . which can not be considered at CO-PA.
only revenue item will be considered at Co-pa.
Hope this is clear
With regards
krishna

COPA derivation rule :more than 6 target fields

Hi ,
As per client's requirement I need to include 10 target fields in a COPA derivation rule . Now after entering 6 , I can see rest of the rows are greyed out ; it looks like SAP does not allow more than 6 as target .
I tried to find out if such limitation is mentioned anywhere in SAP documentation but I could not find ; if anyone has any reference doc on that please let me know .
Secondly , how to meet the requirement ? I can break the same into 2 separate derivation , say 6 target & related rule value in the first and in just next step another 4 targets & rule value ; the source remains same in both the step .
OR any COPA user exit / enhancement will help me accommodate all 10 targets in a single step of derivation ? as far as my knowledge goes SAP provided COPA user exits (1 to 5) will not be helpful here .
Awaiting your help ...
Regards
Indranil Sen

Dear Indranil Sen,
As per my knowledge it is not possible to mention more than 6 source and target fields for a derivation rule.
Because for that program, SAP defines that (1+5) fields for that screen.
That is the reason you are getting the gray color after 6 entries
Yes we can increase that limit but for that we need the access key.
If you have access key authorization, you can increase the limit
Reasons in detail:
Screen filed what you are looking for is:
DYNP5400-SRC-NAME-FIELDNAME
There you can enter (1+5) entries only. enhancement for that field is difficult.
So you can opt for 2nd option as you said.
Let see Mr. Waman Shirwaicar's views on this issue.
Regards,
Pavan Kumar Arvapally

"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 Rule in PCA

Dear All,
we have an issue in profit center acccounting. Balance sheet account Vat input tax payable is picking dummy profit center instead of correct profit center. Basically we are doing the following steps. 1. Purchase order creation 2. Goods received via migo 3. invoice receipt via miro
At the time of miro posting, system is automatically created accounting document, with dummy profit center is assigned to Vat input tax payable account. For GR/IR clearing account right profit center is picking without any mistake.
Infact, Dummy profit center is assigned to this balance sheet account under tcode 3KEH.
Derivation rule is created for this balance sheet account along with plant condition to post to correct profit center under 3KEI . But system is taking only dummy profit center.
I have checked configuration and the following areas like Material master costing view, tax code areas, and account group but not find any mistake.
Please advice how to get correct profit center to this balance sheet account instead of dummy.

You have to do this with the Month end closing
TC
F.5D - Calculate
F.5E - Post
F.5F - Display Log
F.5G - Special Functions
This is the help from F.5D - Calculate
Short text
Calculate Balance Sheet Adjustment
Description
A balance sheet eadjustment distributes
receivables and payables in customer and vendor reconciliation accounts,
tax postings,
cash discount postings from the net method of posting vendor invoices as well as
valuated exchange rate differences in open items (this is a P&L item, but since receivables or payables increase or decrease depending on the valuation, a readjustment is also made for the exchange rate difference with a reverse +/- sign).
This process ensures the zero balance per business area necessary for creating business area balance sheets.
It consists of the following steps:
When posting a document, the system analyzes it to determine whether a balance sheet readjustment is necessary. If a readjustment is required, the system marks the document for readjustment.
Readjustments are calculated for the marked documents and stored in special tables.
This subfunction is described below.
The calculated readjustments are read and then distributed and posted in total to the appropriate accounts.
Fields Included in Readjustment
Readjustments are made for business areas if the function for business area balance sheets is activated in the company code in question. Readjustments are also made for trading partner business areas if the function for business area consolidation is activated.
If Profit Center Accounting is activated in the controlling area allocated to the company code, readjustments are made for profit centers as well as trading partner profit centers.
Note
The fields included in readjustment are determined when the original document is posted. Thus, the customizing settings for business areas and profit centers must be made prior to posting the first document. If these settings were not made, you can still mark posted documents for balance sheet readjustment by executing the subfunction for setting up the balance sheet readjustment (see below).
Basis for Distribution
The system uses the account assignments of the offsetting entries in the initial document to calculate the distribution. Offsetting entries are all G/L account items apart from tax items and cash discount items.
Readjustment is made only for those account assignments which were not specified during posting (their value is blank). If a value is entered in an account assignment field during posting, it is regarded as a correct entry and not changed by the readjustment.
Carrying Out the Distribution
Readjustments are transfer postings which create one or more account assignments (not blank) for the unspecified account assignments in original documents.
Scheduling the Program Run
You can run this program as often as you like.
Requirements
Account Determination
For each account, you can specify an adjustment account to post the readjustment to. Otherwise, the system posts the readjustment to the original account.
To distinguish readjustment postings from other postings, you should create separate adjustment accounts and have the readjustments posted to them.
Since reconciliation accounts cannot be posted to directly, you have to specify adjustment accounts for them.
Since readjustments are posted without tax, the accounts posted to cannot be relevant to tax.
Adjustment accounts are determined when calculating the distribution.
For more information on automatic postings, see the Implementation Guide.
Output
The log shows how many documents per company code the system calculated distributions for.
Note:
If valuation differences are noted in documents, the system always includes them in the calculation. When updating the allocation tables, it checks for whether or not calculations already exist for these documents.
If account determination is incomplete or maintained incorrectly, the system does not calculate any distributions for the affected documents. It lists both the queried entries and the affected documents.
To view the readjustment calculated for an individual document in Document Display, choose Environment -> B/S readjustment.
Additional Information
See the documentation for the other subfunctions:
Posting the distribution.
Displaying the logs of existing posting runs.
Reversing an incorrect posting run.
Redetermining the adjustment accounts if you changed the account determination or it was incomplete at the time of calculation.
Setting up balance sheet readjustment if you have already been productive with a release prior to 3.0.
Dependent functions
Readjustment must be carried out prior to creating a business area balance sheet.
Profit Center Accounting also requires the results of readjustments.

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

Profit centre derivation rule to derive profit centre based in Business plc

Hi,
We required "profit centre derivation rule to derive profit centre based in Business place + 9000 in such case were vendor & customers are involved and current profit center derivation logic doesnu2019t work."
For this we have mapped a substitution pertaining to all co. codes based on all the relevant posting keys for Vendor and Customer where in system will replace the profit center based on business place given in line item as Business Place + 9000. For happening this we have written a User Exit and attached the same with this substitution through t.code OBBH. Entire hting we mapped in our testing client.
But now the problem is whatever posting keys we have defined in our substitution are being used in normal payment and clearing also.
Eg : In payment document vendor is debited vide posting key No 25. where the profit centre is derived based on the invoice that gets selected.
In Normal Payment and clearing transactions, the profit centre is derived based on the profit center in offsetting line items (as per New GL Logic) currently.
Now our business requires that where ever the system is unable to derive a profit centre for vendor and customer (And giving the error " Balancing field profit center in line item 001 not filled") transactions, then at that time profit center for that line item should replace with logic Business Place + 9000 (here business place is the business place contained by that line item in which error is coming for profit center.).
How to map the same in the system through substitution / exit or any other method? Awaiting for your inputs pls. Thanks in advance.
Tapan

Still not answered.
Requesting to give some clue for the same.
Thanks & Regards,
Tapan

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.

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

Profit center derivation rule

HI
We need to maintain the profit center derivation rule in the delivery or billing document, i.e. if batch no starts as A- Profit center-1000, B -Profit center-2000. We have used some user exit in order and working fine. where as our client is interested to have same in delivery or billing document. Is there any user exits are available. The profit center should be determined as per batch no starts and not as maintained in the material master.
Regards.
Edited by: R Rao on Sep 22, 2008 4:03 PM

Please check this user exits available for VF01.
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX009 Billing doc. processing KIDONO (payment reference number)
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedure
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lists
V61A0001 Customer enhancement: Pricing
Also check this user exits as well.
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.

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

Table look up and derivation rule in COPA

Hi,
What is the difference between table look up and derivation rule in COPA. How do we inter rellate them in customizing.
Please clarify.
Thanks and Regards,
Ram
Moderator: Please, avoid asking basic questions

Hi ram,
Herewith i am giving you link i hope this will help full to you.
deleted
Method which is used in the derivation step.
You can choose from the following derivation types:
Derivation rule :
Derivation rules are "if-then" rules, in which you specify which combination's of characteristic values will yield which target characteristic values.
Table look-up :
Table look-ups let you determine characteristic values by having the system read them from any table. The source fields must correspond to the key of the table where you want the system to find the target value.
Thanks,
Anil

FM DERIVER Custom field in Derivation Rule

Similar Messages

Maybe you are looking for