FI to COPA Value fields Currency translation

Hello All,
We are having the following situation.
1) The company code currency is RUB
2) Operating concern currency is EUR.
3) Second local currency as EUR.
we are using a customised program to run the settlement. This program calls the KE21 transaction and creates the settlement line items.
The program passes the amount in the document currency to Ke21 transaction and the transaction inturn does the currency conversion to operating concern currency EUR.
The issue is that because of this there are some differences in the Amount in FI and Amount in CO-PA in EUR currency because the RUB exchange rate is volatile.
The userexit COPA0004 will give control only to the exchange rate type that can be defined.
Please let us know whether there is any user exit or any other way to have a control on the date of the currency conversion.
We tried sending the Second local currency,in this case the amount in EUR(Operating concern) is correct but the amount in the company code currency-RUB in COPA (Ke23)is not matching with the FI amount.
Hence our assumption is that if we can have a control on the date of the conversion then the FI and COPA amounts will match.
Please let us know incase the above requirement can be achived in any other way.
Thanks in Advance.
Regards
Pavan M

You should be able to achieve this by implementing the COPA valuation enhancement. Enhancement COPA0002, EXIT_SAPLKEAB_001 can be used to populate value fields. To use the exit you first must assign an exit number to your valuation strategy (t-code KE4U), which you then use in the exit. You can find documentation for the enhancement there as well.
thanks,

Similar Messages

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should 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.
Hope it helps

COPA value field not getting complete SD condition value

Hi Gurus,
I find a strange issue when a billing document is transferred to COPA (well basically, after a billing document is released to accounting, all the controlling docs and COPA docs are generated). The issue is, I have a SD pricing condition which has been assigned to COPA value field. I also have the transfer +/- sign checked on this value field. Now consider the following 2 scenarios:
Scenario 1: In VKOA, two different G/l accounts have been assigned to the corresponding pricing condition account key. These 2 G/L accounts have been defined as cost elements with category '12' (its related to sales deduct). and fall under the same cost element group. When a billing doc is posted to accounting and hence to COPA, I see that there is no value in the value field and the corresponding condition type. Then I ran a simulation using KE4ST and found that I have two lines with the same pricing condition type and value field but one carries a positive value and the other one carries a negative value. Then I came to a conclusion that may be these two lines are netting out and hence there is no value being posted on the value field.
Scenario 2: In VKOA, I have assigned two different G/L accounts which fall under different cost element group and one is defined as category 12 and the other as category 1. This time I see that only 1 line of value field is brought into COPA corresponding to the pricing condition and hence I see a value in COPA value field. But business doesn't want to go with scenario 2 as they don't want to use two cost elements in different cost element group. Also one is sales deduct and the other is primary cost/ cost reducing revenue. So there is a balance getting accumulated in the primary cost/cost reducing revenue element.
How do I resolve this issue to post a value to the COPA value field using scenario 1? I have also tried to uncheck the transfer +/- sign but I am unable to even release a billing doc to accounting as it is giving me a error message,: "correct the value field assignment for the condition type".
Please help me !!
Regards,
Sony

Version of SAP?

COPA - Value Field - Assignment to a G/L account

Dear All,
Could anyone kindly let us know what the relationship between the COPA value fields and G/L.???
(We do not use Sales and Distrubution module in our company)
Thank you Very much
Gayani
Moderator: Please, search SDN

Hi,
The configuration part looks to be ok !! But just check the G/L account you have mentioned, the second one which does get booked, see if it configured in a way to accept the value returned by the condition.
Check in the order item conditions, the value returned by the z condition not getting booked.
Hope it helps.
Thanks & Regards
Sadhu Kishore

SD- conditions to be mapped to COPA value field data in BI

Hi Experts,
I have a req where in I have to map condition level Sales order data to some COPA value fields. Currently for one Sale order item there are multiple conditions that means multiple line items. But when I try to find the COPA value field for the same same (Sales order, Sales order item ) key I get only one line item.
This has to be done for BI integration, but needs to be done at the source system level.
So my questions are,
1) How can we get the condition level data from COPA? Is it possible to fetch the data at that granularity?
2) Is it possible to integrate SD & COPA data on condition level i.e. at Sales order, sales order item & condition level.

Hi,
In KEA0, Data structure tab click on pencil button (change view).
Then click on -> change
Now you will be able to select new value fields
Rememeber, after changing click on save, activate and then back button. system will ask for regeneration, click ok.
Regards
Raghu

Fixed & Variable Cost flow to COPA Value fields

Hi All,
I am using the Fixed & Variable Cost option that has to flow to COPA (under which mechanism it will flow to COPA Value fields).
as structure based sample from OKTZ to KE4R
OKTZ
KE4R
01
10
Raw Material
3
Sum of Fixed & Var
ROHST
Raw Material Cost
01
20
Power
1
Fixed Amt
VVPOW
Power
01
30
Labour
1
Fixed Amt
VVLAB
Labour
02
10
Raw Material
3
Sum of Fixed & Var
ROHST
Raw Material Cost
02
20
Power
2
Var Amt
VVPOW
Power
02
30
Labour
2
Var Amt
VVLAB
Labour
While I run Std cost estimate it will show me "Power & Labour" -as per KP26 Fixed & Variable
Power
Fixed Cost
15
Variable Cost
8
Labour
Fixed Cost
10
Variable Cost
5
How it ditribute to COPA Value Fields the below amounts

Any replies ...........pls

How to create substituion for COPA value fields?

Hi,
In OBBH i cannot find a destination field for copa value fields. The destination fields are always from SAP standard tables like BKPF and so on.
In this case how can i create a substitution to assign values to COPA value fields?

Hi,
I can see only the following entries in my OBBH user exit, so what is difference between COPA0002 and these :-
SCO10
SGJF1
SGJA1
SGJA2
SGJA3

COPA Value Field +/- Error while releasing Billing Document for Return orde

Hi,
We have done Sale Order - PGI - Delivery and Billing for Quantity 10 and the customer returned 10 Qty due to some problem.
When i am doing the return process billing, I am getting the below error...
9000000892 000000 Check value field assignment for condition SGL1*
When condition "OR01" (application "V") was transferred to the value field "ERLOS" in operating concern "OR01" in
Profitability Analysis, the following became apparent:
o   The condition can take both positive and negative
    values
o   The flag "Transfer values with +/- signs" has not be
    set in Customizing for value field assignment.
Inconsistencies in the data could occur as a consequence.
Can any body help me on this issue
Is there any consequences if i activate +/- sign in KE4I for the above value field Please suggest me
Thanks
KC

Hi Kischow
You shud tick the +/- indicator only if
1. any One condition type repeats in the pricing procedure and can have +ve and -ve values
2. Two cond types in pricing procedures are assigned to same Value Field and the cond types can have +ve and -ve values
In COPA, all values are transferred as absolute values without + or - sign, with some exceptions ofcourse....
So, if you dont check + / - indicator in the cases mentioned above, say, +100 and -80 will be transferred as 100and 80 and the result will be 180 instead of 20
Regards
Ajay M

New COPA Value field not populating in BW

We created a NEW value field (VV0056) in SAP COPA that is NOT pulling manual journal entries into BW (document types AB and SA). All other value fields are pulling in all document types and balance to SAP u2013 itu2019s this new one that is not. We do not have any restrictions on selection of data coming into BW.
The manual journal entry is in our CE1* table in R/3.
We are still 3.x data loading in our BW 7 system.
Any ideas on what to look for? Your input is greatly appreciated.
Renee Mercede

Hi Renee
The new fields that has been added must be either in the COPA table or the corresponding datasource.
If it is added in the table
1) You need to enhance the corresponding datasource with a z-field that wiill represent the field added in the table.
2) This field will have to be populated through an ABAP routine.
3) Check the populated field values in RSA3.
4) Replicate the datasource in BW.
5) Create infoobject for the enhanced field.
6) Add infoobject in the corresponding BW data targets.
7) Change transformations / UR's - TR's.
8) Extract data.
If it is added in the datasource - which means you know from which base table this field needs to be populated.
Carry out steps (2) to (8) from above.
Cheers
Umesh

Having problems when adding new Curency value field + currency field.

I need to add a new Currency field (CURR, length 15, 2 decimal places) plus the Currency field itself to a view.
I'm really struggerling. I have looked at the existing SAP fields in the Component workbench and I have to admit I can not see how a field is linked/related to the currency itself. Is this link established purlely at the disctionary level?.
Has anyone added their own Z field value and Z currency field before. I can create both fields and display them, but what I can not work out is how I related them within the component workbench, or is this done from the dictionary?.
Any help would be greatly appreciated.
I should have been able to look at an existing SAP example and work out how it's done, but so far I can not see/determine how this is achieved, even though someone has mentioned that it's controlled via the GET_I_field method. Looking at this method I was expecting to see some mention of both the Currency value field and the Currency field. But as I don't see these confusion reigns.
Jason

That's correct, but am I right in thinking that you can't actually create the currency key field itself?.
I am aware that currency value fields can be created which reference a currency key field, but can see nothing that allows me to create a currency key field to be referenced.
I hope that makes sense.
Also, I have amended the structure, changing my value fields from Decimal 15,2 to Currency 15,2 and have created a new currency key field in the structure and referenced this from the Currency value field.
Witin the Component/view/context node I can see this new currency key field, but it appears as STRUCT.fieldlabel whereas my currency value field appears in the context node as EXT.fieldlabel, because it was created in the AET.
My problem is that when attempting to add the currency key field onto the screen I don't have it to select from within the list of structures/attributes. All the others attributes in the context node seem to be there, except the new currency key field/attribute.
The attribute has a SET_fieldlabel, GET_fieldlabel, GET_M_Fieldlabel and a GET_I_Fieldlabel, which I believe is all that should be required.
Does anyone know what my problem could be?.
Jason

Transport COPA Value fields

Hello Experts,
I have the scenario wherein we need to change the description of certain value fields & transport it to test & production system. I know this can be done via KE3I in which we can transport the entire operating concern but my interest lies in whether there are any potential impacts on production system in which there is already transaction data? Does this function transport the entire customization tables of COPA ? If transported to live environment, any impacts?
These questions are only to those COPA experts who have transported operating concerns for live systems containg transaction data.
Regards,
Amol

Hi
I am interested to know why you are looking for this change if want to change for reporting purpose you can change in BW from where we are getting the reports .
when you regenerate Operating concern, the old data needs to be dropped and reloaded again
which is a mamoth task and not advisable by SAP as well ,as dropping data and reloading the same their is no validation cycle for the same
Thanks
Deepak

COPA value field not updated in KE24

In VF03, I can see condition type ZV02 (discount), amount 10 USD, condition class: A(Discount) calculation type (quantity), account key Z02, in Ke4I, I already assigned ZV02 to value field VV101, but in KE24 line item, VV101 is empty, Why VV101 is empty, how to resolve, thanks

Thanks all, but all above solutions doesn't work, our CMOD only have copa00001 and copa00002, it regarding the characterstic derivation, but i'm talking value field, KEKF, no error, KE4S actual run, but result same
what's wrong with COPA, in KE24, I can see revenue, stock value, quantity, value field updated, but discount is not.
accounting document is posted, discount GL 30000010 has posting. why PA empty?

Cost Elements and COPA Value Fields

Hi All,
Should all the cost elements created in CO be assigned to value fields in Costing Based COPA?
I am a bit confused . . .
Regards,
Ravi Kumar

Hi ravi,
Basically fist you understood, how the values are flowing into the CO-PA. ie When ever billing document generated co-pa document generates automatically. based on your condition type and account keys.
While defining pricing procedure, they mapped the conditon type against releavant account key.
Based on the releavant account key they assigned releavant cost element under VKOA.
Against these condtion types they assgined value filed under KE4I in co-pa.
This is the way system will capture cost elemetns under copa. KIndly revert in case any issue.
Regards
Maruthi.

No postings to COPA value field

Hey All
Its kind of weird situation. I have to do some manual JE for month end clost to a Cat 11 GL. This GL is mapped to go a certain Value field... VV13. Now when i post the document in fb50 i enter the chars material, plant, customer and material acct assignment grp. When i enter these and save the COPA document gets posted but nothing shows up in VF vv13.
I post second document with chars material, plant, customer only and it posts COPA document with values in the value field VV13. Can anyone help me on this
Thanks
Ankur

It was due to a user exit for certain VF's . Closing the issue. Thanks!

COPA Value Fields maximum limit

Hi,
I read that there is a limit on the number of value fields that you can have in an Operating Concern, which is 120. There is an OSS Note (160892) that describes how you can extend this number to more than 120, however SAP puts a disclaimer that it is not responsible for any problems that result from implementing the note.
Has anyone used this note to extend the value field limit? Alternatively, does anyone know of any other method of creating more than 120 value fields in an Operating Concern?
Thanks

Hi,
I have also faced same situation earlier. Luckily, at that time, the Client agreed to abide by the SAP's suggestion. I think that it is not advisable to pooh pooh the SAP's advice. Kindly shows this OSS note to your employer and put the responsibility on them if something goes wrong. Then you can take up the adventure.I think that nobody on earth can go against the advice of SAP.
Cheers, Thanks.

FI to COPA Value fields Currency translation

Similar Messages

Maybe you are looking for