FM derivation rule - ??? client copy

Hi Expert,
I have encountered a strange problem on FM derviation rule (TCODE FMDERIVE). I tried to client copy a "gold copy" client to a seperate client using using SAP_ALL but found that all the details derviation rule were missing.... I tried in my different server and found the same problem. It seems that derviation rule would not be copied by "client copy"
I tried to recopy the configure. I search the orginal request but found that it was a Workbench request. By my knowledge, workbench request should be cross client...
Any other have the same situation? how can i fixed the probelm? Should i use scc1 to transport the request?

Hi
I do not know which version of EA-PS you are using .
when we were trying for funds managment we came to know that If the version is EA-PS 2.00 or higher you will find 9 rules in FMRULS and for balance you will find finction module for which you have to go to FMDERIVE - Create and from Create step select function module it will show the function modules availables which will derive the target fields based on default source fields.
If the answer is helpful kindly assign points.
Thanks & Regards
Mahesh

Similar Messages

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).

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

KE21N with reference - copy old copa records without applying new derivation rule

Dear all,
does anyone have a clue how to make this:
We would like to copy some old COPA line items but face the problem that doing KE21N with a reference document the old derivation is overwritten in the moment the document is saved.
Is there any possibility to copy the old document and also the old derivations?
Thank you a lot
Kind regards
Birgit Seeger

Hi Birgit
The only way I can think of is to enter the char values as you want directly in ke21n. You may Need to temporarily change your derivation rules to not derive the char values if the same is already filled
Just click on the magnifying lens icon beside the Target field inside your derivation rule and you change setting
Br. Ajay M

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.

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

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

Client copy error in test mode

Dear all,
I am doing a client copy in test mode. Following log is generated. Please tell me solution for it.
    Log File:
devdemo\sapmnt\trans\log\CC000007.RBD
Client copy from 25.08.2008 15:43:29
System ID............................ RBD
Target client........................ 120
R/3 Release.......................... 700
Basis Support Package...............SAPKB70012
Host................................. devdemo
Start in background............. .....
User................................. SAP*
Parameter
Source destination......................PRD_300
Source system.........................PRD
Client in source system..............300
Users in source system..............RBASIS
Basis Support Package...............SAPKB70012
Copier profile:.......................SAP_ALL
Table selection
Customizing data .....................X
With application data................ X
Initialize and recreate......... X
         / |   Change documents are not copied                                                                                |
Test mode (without database update).. X
    3S3T |   Start analysis of system 15:43:29                                                                                |
/GC1/CC_EXIT_CLIENT_DELETION executed         0(        0) entries copied
Exit program /GC1/CC_EXIT_CLIENT_DELETION successfully executed 15:43:44
Table /SAPCND/CONDINDX is deleted, not copied
Table /SAPCND/CONDREF is deleted, not copied
Table /SAPCND/CONDRECS is deleted, not copied
/SAPCND/CC_EXCLUDE_TABLES executed         3(        0) entries copied
Exit program /SAPCND/CC_EXCLUDE_TABLES successfully executed 15:43:44
Unknown message with
/SAPCND/CC_GROUP_WS_AA executed         0(        0) entries copied
Runtime              0 seconds
Exit program /SAPCND/CC_GROUP_WS_AA successfully executed 15:43:45
ADDR_CLIENTCOPY_SELECT_TABLES executed        26(        0) entries copied
Runtime              1 seconds
Exit program ADDR_CLIENTCOPY_SELECT_TABLES successfully executed 15:43:47
EFG_FORM_CC_EXIT_BEFORE executed         0(        0) entries copied
Runtime              0 seconds
Exit program EFG_FORM_CC_EXIT_BEFORE successfully executed 15:43:48
Start of deletion methods for client 120
Start the deletion method for object FINB-TR-DERIVATION
End of deletion method of object FINB-TR-DERIVATION
Start the deletion method for object UCM003
End of deletion method of object UCM003
Start the deletion method for object /EACC/ARCHIVING
End of deletion method of object /EACC/ARCHIVING
Start the deletion method for object /EACC/JOURNALCC
End of deletion method of object /EACC/JOURNALCC
Start the deletion method for object /EACC/DERIVATION-1
End of deletion method of object /EACC/DERIVATION-1
Start the deletion method for object FINB-PERSIST
End of deletion method of object FINB-PERSIST
Start the deletion method for object FINB_GENERATOR
Deletion log for client 120, application 10
0 objects registered for deletion
No errors found in simulation mode
Deletion log for client 120, application EA
0 objects registered for deletion
No errors found in simulation mode
Deletion log for client 120, application UG
0 objects registered for deletion
No errors found in simulation mode
End of deletion method of object FINB_GENERATOR
Start the deletion method for object FINB_SBU_DUMMY
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area AS deleted on server devdemo
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area AS deleted on server devdemo_RBD_00
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area XP deleted on server devdemo
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area XP deleted on server devdemo_RBD_00
Buffer FINB_S_KF_CHARS_BUFFER_KEY, area HA deleted on server devdemo
Buffer FINB_S_KF_CHARS_BUFFER_KEY, area HA deleted on server devdemo_RBD_00
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area GN deleted on server devdemo
Buffer FINB_S_SBU_BUFFER_HASH_KEY, area GN deleted on server devdemo_RBD_00
End of deletion method of object FINB_SBU_DUMMY
FINB_TR_CC_EXIT executed         0(        0) entries copied
Runtime              1 seconds
Exit program FINB_TR_CC_EXIT successfully executed 15:43:50
TPM_TRG_CCEXIT_REMOTE executed         0(        0) entries copied
Runtime              0 seconds
Exit program TPM_TRG_CCEXIT_REMOTE successfully executed 15:43:56
CLIENTCOPY_SELECT_TEXTTAB executed         3(        0) entries copied
Runtime              0 seconds
Exit program CLIENTCOPY_SELECT_TEXTTAB successfully executed 15:43:56
Table KX9RABA0000108 is deleted, not copied
Table TABADRH is deleted, not copied
Table TABADRS is deleted, not copied
Table TABADRSF is deleted, not copied
Table TABADRST is deleted, not copied
Table UCF001C is deleted, not copied
Table UCF001G is deleted, not copied
Table UCF001T is deleted, not copied
Table UCF0020 is deleted, not copied
Table UCF0021 is deleted, not copied
Table UCF0022 is deleted, not copied
Table UCF0023 is deleted, not copied
Table UCF002C is deleted, not copied
Table UCF002T is deleted, not copied
Table UCF0032 is deleted, not copied
Table UCF003C is deleted, not copied
Table UCF003G is deleted, not copied
Table UCF003T is deleted, not copied
Table UCF0040 is deleted, not copied
Table UCF0041 is deleted, not copied
Table UCF0042 is deleted, not copied
Table UCF0043 is deleted, not copied
Table UCF004C is deleted, not copied
Table UCF004T is deleted, not copied
Table UCF1000 is deleted, not copied
Table UCF1001 is deleted, not copied
Table UCF1002 is deleted, not copied
Table UCF2300 is deleted, not copied
Table UCF2301 is deleted, not copied
Table UCF2310 is deleted, not copied
Table UCF2311 is deleted, not copied
Table UCF3000 is deleted, not copied
Table UCF3001 is deleted, not copied
Table UCF3010 is deleted, not copied
Table UCF4000 is deleted, not copied
Table UCF4001 is deleted, not copied
Table UCF4002 is deleted, not copied
Table UCF5000 is deleted, not copied
Table UCF5001 is deleted, not copied
Table UCF5002 is deleted, not copied
Table UCF5010 is deleted, not copied
Table UCF600C is deleted, not copied
Table UCF6010 is deleted, not copied
Table UCF6020 is deleted, not copied
Table UCF6030 is deleted, not copied
Table UCF6050 is deleted, not copied
Table UCF6100 is deleted, not copied
Table UCF6110 is deleted, not copied
Table UCF6120 is deleted, not copied
Table UCF6130 is deleted, not copied
Table UCF6140 is deleted, not copied
Table UCF6150 is deleted, not copied
Table UCF6160 is deleted, not copied
Table UCF6170 is deleted, not copied
Table UCF6180 is deleted, not copied
Table UCF6200 is deleted, not copied
Table UCF620C is deleted, not copied
Table UCF620T is deleted, not copied
Table UCF6210 is deleted, not copied
Table UCF6300 is deleted, not copied
Table UCF6310 is deleted, not copied
Table UCF7100 is deleted, not copied
Table UCF7101 is deleted, not copied
Table UCF7102 is deleted, not copied
Table UCF7110 is deleted, not copied
Table UCF7300 is deleted, not copied
Table UCF7400 is deleted, not copied
Table UCF7410 is deleted, not copied
Table UCF7500 is deleted, not copied
Table UCF900C is deleted, not copied
Table UCF9010 is deleted, not copied
Table UCFE01T is deleted, not copied
Table UCFE020 is deleted, not copied
Table UCFE02T is deleted, not copied
Table UCFE03G is deleted, not copied
Table UCFE03T is deleted, not copied
Table UCFE04G is deleted, not copied
Table UCFE04T is deleted, not copied
Table UCFE050 is deleted, not copied
Table UCFE05G is deleted, not copied
Table UCFE05T is deleted, not copied
Table UCFE060 is deleted, not copied
Table UCFE06G is deleted, not copied
Table UCFE06T is deleted, not copied
Table UCFE070 is deleted, not copied
Table UCFE080 is deleted, not copied
Table UCFE081 is deleted, not copied
Table UCFI00C is deleted, not copied
Table UCFI10T is deleted, not copied
Table UCFI200 is deleted, not copied
Table UCFI210 is deleted, not copied
Table UCFT000 is deleted, not copied
Table UCFT001 is deleted, not copied
Table UCFT002 is deleted, not copied
Table UCFV000 is deleted, not copied
Table UCFV200 is deleted, not copied
Table UCFV201 is deleted, not copied
Table UCFV202 is deleted, not copied
Table UCFV20G is deleted, not copied
Table UCFV21G is deleted, not copied
Table UCFV21T is deleted, not copied
Table UCFV220 is deleted, not copied
Table UCFV22T is deleted, not copied
Table UCI1101 is deleted, not copied
Table UCI1201 is deleted, not copied
Table UCI2100 is deleted, not copied
Table UCL2011 is deleted, not copied
Table UCL201G is deleted, not copied
Table UCL201T is deleted, not copied
Table UCM0010 is deleted, not copied
Table UCM0011 is deleted, not copied
Table UCM0012 is deleted, not copied
Table UCM0013 is deleted, not copied
Table UCM0014 is deleted, not copied
Table UCM0015 is deleted, not copied
Table UCM0016 is deleted, not copied
Table UCM001T is deleted, not copied
Table UCM002C is deleted, not copied
Table UCM002T is deleted, not copied
Table UCM0030 is deleted, not copied
Table UCM0031 is deleted, not copied
Table UCM0032 is deleted, not copied
Table UCM0033 is deleted, not copied
Table UCM003C is deleted, not copied
Table UCM003T is deleted, not copied
Table UCM1000 is deleted, not copied
Table UCM1001 is deleted, not copied
Table UCM100G is deleted, not copied
Table UCM100T is deleted, not copied
Table UCM600C is deleted, not copied
Table UCM600T is deleted, not copied
Table UCMA100 is deleted, not copied
Table UCMA101 is deleted, not copied
Table UCMA10C is deleted, not copied
Table UCMA10T is deleted, not copied
Table UCMI100 is deleted, not copied
Table UCMI10C is deleted, not copied
Table UCMI10T is deleted, not copied
Table UCMI200 is deleted, not copied
Table UCMI210 is deleted, not copied
Table UCMI220 is deleted, not copied
Table UCMT010 is deleted, not copied
Table UCMT01C is deleted, not copied
Table UCMT01T is deleted, not copied
Table UCMT100 is deleted, not copied
Table UCMT10C is deleted, not copied
Table UCMT10T is deleted, not copied
Table UCMV01T is deleted, not copied
Table UCRX01C is deleted, not copied
Table UCRX02G is deleted, not copied
Table UCS0100 is deleted, not copied
Table UCS0102 is deleted, not copied
Table UCS0103 is deleted, not copied
Table UCS0104 is deleted, not copied
Table UCS0105 is deleted, not copied
Table UCS0106 is deleted, not copied
Table UCS0107 is deleted, not copied
Table UCS0108 is deleted, not copied
Table UCS010T is deleted, not copied
Table UCS0110 is deleted, not copied
Table UCS01A0 is deleted, not copied
Table UCS01A1 is deleted, not copied
Table UCS01A2 is deleted, not copied
Table UCS01A3 is deleted, not copied
Table UCS020T is deleted, not copied
Table UCT100G is deleted, not copied
Table UCT100T is deleted, not copied
Table UCT101C is deleted, not copied
Table UCT101T is deleted, not copied
Table UCT2001 is deleted, not copied
Table UCT200G is deleted, not copied
Table UCT200T is deleted, not copied
Table UCT2010 is deleted, not copied
Table UCT2011 is deleted, not copied
Table UCT2012 is deleted, not copied
Table UCT2013 is deleted, not copied
Table UCT2014 is deleted, not copied
Table UCT2015 is deleted, not copied
Table UCT2016 is deleted, not copied
Table UCT3000 is deleted, not copied
Table UCT300G is deleted, not copied
Table UCT4000 is deleted, not copied
Table UCT400G is deleted, not copied
Table UCT8000 is deleted, not copied
Table UCT800G is deleted, not copied
Table UCT8010 is deleted, not copied
Table UCT8011 is deleted, not copied
Table UCT8012 is deleted, not copied
Table UCT8013 is deleted, not copied
Table UCT8014 is deleted, not copied
Table UCT8015 is deleted, not copied
Table UCT8016 is deleted, not copied
Table UCT801G is deleted, not copied
Table UCT801T is deleted, not copied
Table /ISDFPS/CS_EXLST is convertible to the RFC system, field missing locally
Table /ISDFPS/CS_EXLST is deleted, not copied
Table AD01DLI is convertible to the RFC system, field missing locally
Table AD01DLI is deleted, not copied
Table ADRC is convertible to the RFC system, field missing locally
Table ADRC is deleted, not copied
Table AFFW is convertible to the RFC system, field missing locally
Table AFFW is deleted, not copied
Table AFIH is convertible to the RFC system, field missing locally
Table AFIH is deleted, not copied
Table AFKO is convertible to the RFC system, field missing locally
Table AFKO is deleted, not copied
Table AFPO is convertible to the RFC system, field missing locally
Table AFPO is deleted, not copied
Table AFRU is convertible to the RFC system, field missing locally
Table AFRU is deleted, not copied
Table AFRV is convertible to the RFC system, field missing locally
Table AFRV is deleted, not copied
Table AFVC is convertible to the RFC system, field missing locally
Table AFVC is deleted, not copied
Table ASMD is convertible to the RFC system, field missing locally
Table ASMD is deleted, not copied
Table AUFK is convertible to the RFC system, field missing locally
Table AUFK is deleted, not copied
Table AUFM is convertible to the RFC system, field missing locally
Table AUFM is deleted, not copied
Table CEZP is convertible to the RFC system, field missing locally
Table CEZP is deleted, not copied
Table CHVW is convertible to the RFC system, field missing locally
Table CHVW is deleted, not copied
Table CHVW_INC is convertible to the RFC system, field missing locally
Table CHVW_INC is deleted, not copied
Table CKIS is convertible to the RFC system, field missing locally
Table CKIS is deleted, not copied
Table CPZP is convertible to the RFC system, field missing locally
Table CPZP is deleted, not copied
Table CRFH is convertible to the RFC system, field missing locally
Table CRFH is deleted, not copied
Table EBAN is convertible to the RFC system, field missing locally
Table EBAN is deleted, not copied
Table EKBE is convertible to the RFC system, field missing locally
Table EKBE is deleted, not copied
Table EKBEH is convertible to the RFC system, field missing locally
Table EKBEH is deleted, not copied
Table EKEK is convertible to the RFC system, field missing locally
Table EKEK is deleted, not copied
Table EKES is convertible to the RFC system, field missing locally
Table EKES is deleted, not copied
Table EKET is convertible to the RFC system, field missing locally
Table EKET is deleted, not copied
Table EKKO is convertible to the RFC system, field missing locally
Table EKKO is deleted, not copied
Table EKPO is convertible to the RFC system, field missing locally
Table EKPO is deleted, not copied
Table EKRS is convertible to the RFC system, field missing locally
Table EKRS is deleted, not copied
Table EQBS is convertible to the RFC system, field missing locally
Table EQBS is deleted, not copied
Table EQUI is convertible to the RFC system, field missing locally
Table EQUI is deleted, not copied
Table EQUZ is convertible to the RFC system, field m

Well.. those don't look like errors to me... depending on what copy profile you use SAP chooses what tables to copy and what tables to delete... so basically is just letting you know which tables are not to be copied across...
Read
http://help.sap.com/saphelp_nw04s/helpdata/en/99/0a2a8e7e2511d2a6250000e82deaaa/content.htm
Regards
Juan

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

FM derivation rule

Hi Gurus,
We are using 4.6c version and In our client we have more than 10 company codes and controlling Area,
five of the company code have FM module in use but everyone sharing only one derivation rule, Is possible
to have different derivation rule e,g Company Code wise derivation rule & Strategies.
Please suggest.
BK

I don't see its possible to create a set of derivation rules at the company code level but if they are getting crossed between different users in different company codes you can always include the specific company code(s) as a condition in the derivation rules to help keep them organized and controlled.

Derivation Rule Tables

My users have created some transparent tables using the derivation rules in the Grants Management module. I need to read these tables in a Z program. The issue is, when the rule is run in each client the table name is generated by the system and varies from client to client. Does anyone know of a way to get these table names dynamically either from a function module or another table?
Thank you,
Becky

Hi,
Is there any solution to the above problem. I am also facing the same problem, as to how to get the derivation rules tables.
Thanks in advance,
Lalitha

How to delete derivation rule - COPA (KEA5)

Hi All,
Could you please inform me how to delete derivation rule(COPA_KOSTL) in KEA5 transaction code ? when we try to delete the system displaying the following message :
Message No K6430
Diagnosis
you are trying to delete a field delivered by SAP, although you are in the customer name range
System Response
You can delete the field, but must assume that the field will reappear in the next put.
Procedure
We are dealing with a currency - you can delete the field.
We added this field to Operating concern and now we want to delete this field.
Awaiting your valuable replied.
Thanks in advance
Srinivasa Chary

Hi,
In KEA5 did you copied the fixed characterisitics and created your own user Characterisirics. It is better not to copy the standard fields with table Since both will have same feature if you rename to another Desciption text.
Regards,
Sreekanth

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

FM derivation rule - ??? client copy

Similar Messages

Maybe you are looking for