Derivation Rule - Workbench Transport

We are trying to create derivation rule through transaction KEDR without any values. After creating derivation rule, it is creating workbench transport request eventhough K9RE* table is client dependent.
We have different transport routes/groups for customizing and workbench. SAP Layer is assinged to workbench transport group with one another Z* layer.
When we are trying to create request it is creating workbench transport request eventhough it is client dependent. It is using KEG0 package which is assinged to SAP layer.
Workbench transport are not going to all clients and we have to move request manually to other clients.
What should we do for changing this behaviour?
Thanks,
Miral.

With detailed explanation:
I thing previous post with was not detailed enough. Please see below.
We have created two different transport group for differentiating
customizing and workbench transport request.
ZECD layer is assigned to /CUST/ group where as ZWBK and SAP layer is
assinged to /WRKB/ group.
We are moving all client independent transports (assigned to /WRKB/
group) to only 1 client in other systems.
While creating derivation rule through transaction KEDR, it is not
allowing us to assing /CUST/ group eventhough config is client dependent.
It is using package KEG0 which is assinged to SAP layer and SAP layer isassinged to /WRKB/ group in our configuration.
The Derivation rule config is client dependent eventhough it is creatingworkbench request. We would like to know why it is creating workbench
request instead of customizing request.
Thanks,
Miral.

Similar Messages

DERIVATION RULE VALUE TRANSPORTING

Hi,
Is it possible to transport the values of a particular derivation rule from one server to another? currently derivation rules are updated in "PRD" and we have created a copy of PRD with some changes now we would like to transport the rule values maintained in old PRD to its new copy.. is it possib to do so. if yes then what are the steps involved?
Regards,

Hi Faizan,
Please check these SAP notes:
1661776 - How to transport Derivation Strategy – Best Practice
1231815 - Predefined FMDERIVE tables are renamed during transport/CC
1019327 - FMDERIVE and the new FINBASIS transportation tool
Regards
Javed

Transport Problem - for KEDR Derivation rule

We are trying to create derivation rule through transaction KEDR without any values. After creating derivation rule, it is creating workbench transport request eventhough K9RE* table is client dependent.
We have different transport routes/groups for customizing and workbench. SAP Layer is assinged to workbench transport group with one another Z* layer.
When we are trying to create request it is creating workbench transport request eventhough it is client dependent. It is using KEG0 package which is assinged to SAP layer.
Workbench transport are not going to all clients and we have to move request manually to other clients.
What should we do for changing this behaviour?
Thanks,
Miral.

With detailed explanation:
I thing previous post with was not detailed enough. Please see below.
We have created two different transport group for differentiating
customizing and workbench transport request.
ZECD layer is assigned to /CUST/ group where as ZWBK and SAP layer is
assinged to /WRKB/ group.
We are moving all client independent transports (assigned to /WRKB/
group) to only 1 client in other systems.
While creating derivation rule through transaction KEDR, it is not
allowing us to assing /CUST/ group eventhough config is client dependent.
It is using package KEG0 which is assinged to SAP layer and SAP layer isassinged to /WRKB/ group in our configuration.
The Derivation rule config is client dependent eventhough it is creatingworkbench request. We would like to know why it is creating workbench
request instead of customizing request.
Thanks,
Miral.

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

How to copy copa derivation rules ( maintain rule value)

Hi All,
Can anyone help how to copy the copa derivation rules with maintain rule value from production to quality.

Hello,
Export and import of copa derivation rule is not possible.
usually Transports are moved from quality to production as per best policy.
Production to quality happens at the time of quality refresh.
in case of high importance please get in touch with Basis team.
Regards
Lavanya

Derivation Rule Problem After A Client Copy

Hello,
Has anyone ever encountered a problem with derivation rules after a client copy is performed? After a client copy, we have "some" FM and GM derivation rules (not all of them) that have to be manually copied from the source to the target client (line by line by line by line). I'm thinking that there has to be a way to prevent this since some rules are fine after the clent copy. Your input would be greatly appreciated.
Will

I believe that we have resoved our issue. For the derivation rule values that would never copy, we re-created these again starting in DEV and transported the derivation rules throughout the entire landscape (QAS and PRD). Evidently some derivation rules (and the related values stored in the tables) were created directly in Production. During a client copy the values in the tables for the derivation rules that were created directly in our Production environment would not copy to our QAS environment. Those rules were stored in a table named FMFMOAPRD1000122. Note that PRD is in the table name. After re-creating the rule and transporting it through the landscape, the table was named FMFMOADEV1000152 (for example).

Derivation Rule in report painter

I want Product describtion along with Product number. in a report. I have created a derivation rule through KEDR. and coppied the product describtionin the rule. Now how to use this derivation rule in the report.

Harish,
There is no need to define seprate derivation rule as product description is readily available in COPA tables.
Just select product description characterstics for available list while designing report.If report already exists then go to change mode and make nessesary changes.
Please call me for any more inputs.
Ashok

Maintain Derivation Rules - TCode : GGB1

Hi friends
What is the importance of Maintain Derivation Rules (TCode : GGB1) with respect to Profit center accounting. Is it a compulsory step in configuration or not?
At our client we are implementing the ECC 6.0 with new GL activation. In this case what is the importance of this "Derivation Rules".
Thanks in advance.
Regards
Kiran

Hi,
GGB1 is used for substitution maintenance. It's certainly not manadatory. Only if you have some functional requirement for subsitution, you should use this transaction.
Regards,
Eli

Error while defining derivation rules in FMDERIVE

We are currently on ECC6. While defining Funds Mgmt .... activated the derivation rules in FMRULES. But when I try to define the derivation rules in FMDERIVE .. I get the following error: Syntax error in program "RFMDERIVE003 ".
Error in the ABAP Application Program
The current ABAP program "SAPMABADR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RFMDERIVE003 " in include
"RFMDERIVE003 " in
line 32:
"The Dictionary structure or table "FMDERIVE003" is either not active o"
"r does not exist."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP* "
Error in the ABAP Application Program
The current ABAP program "SAPMABADR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
How can the same be rectified. Kindly help.
Thanx
Shivaji

Hi,
Check the OSS note Note 644974 - Syntax error in program RFMXPR47. Looks like table FMDERIVE is missing.
Regards,
Sanjay

"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 COPA

Hi
kindly explain me the derivation rules possible ways of derivation in COPA
based on costing based.

Hi,
Please check the following link:
https://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/4c38ee4a0111d1894c0000e829fbbd/content.htm
Regards,
Pavan Kumar Arvapally

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

Derivation Rule In FM

Hello Sappers
Can any body explain derivation rule in FM and what are the steps involved.Actually i want to understand what is meant by deriving fund center and commitment item.
Thanks.

You may find the information below somewhat helpful as we have about 13 FM derivation rules in our system that we use to minimize data entry and prevent user keying errors.
http://help.sap.com/saphelp_erp2004/helpdata/en/77/05f06a9b6711d496d90000e835339d/frameset.htm

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

Derivation Rule - Workbench Transport

Similar Messages

Maybe you are looking for