Condition VPRS value in operating concern currency.

Hi,
We've encountered the following problem. I was wondering if anyone of you had a similar one and how did you go about it:
1. We've defined second local currency for our company codes = currency type 30 = USD
2. CO-PA stores both company code currency = currency type 10 and op. concern currency B0=USD
3. When we post goods issue to a customer, COGS is posted in FI in both currencies 10 and 30.
4. Then when we run billing COGS condition VPRS is transfered to CO-PA in company code currency and operating concern currency. The value in company code currency is equal to the value during goods issue posting, however the value in operating concern currency (B0=USD) is calculated using the current exchange rate type 'M'. As a result VPRS value in CO-PA in B0=USD is not the same as the value of COGS in FI for currency type 30=USD (as the exchange rate is different during billing).
It makes it impossible to reconcile COGS between FI and CO-PA in USD.
For direct posting to CO-PA from MM and FI, SAP provides notes 604936 and 1066394 which solve the issue if B0=30. However those notes do not provide solution for billing documents and VPRS.
We were advised that this problem can be solved using CO-PA enhacement COPA0005.
Have you ever done it? Any tips on codeing this user exit? Any sample code?
Regards,
SZ

Hi,
Currency options in operating concern enables you to view the data in copa. Activation or deactivation of the additional currencies here wont impact base data from any documents.
If u r business doesnt have the profit center valuation or group valuation u can deactivate other currencies.
Regards
Sudhakar Reddy

Similar Messages

Company code and operating concern currency in COPA

Dear experts,
I have one controlling area and one operating concern for indian and foreign entitiy with INR as currency for controlling area and one operating concern.
but outside india i have sgd as company code currency.
So i ticked company code currency in operating concern.so while posting revenue in billing .system store in company code as well as operating concern currency.
But all my expenses for outside india entity will store(cost center) in company code currency 'SGD' and controlling area currency 'INR'.
while doing copa assesssment cycle- whether system will store data in copa table in SGD and INR or only INR as operating concern currency.
i need report on operating concern currency as well as company code currency.
regards
Raman Rana

Hi,
If you have ticked 'company code ccy' in KEA0 then all COPA postings (including COPA assessments) will happen in both currencies i.e. company code ccy and operating concern ccy.
regards
Waman

Account based copa - operating concern currency significance

Hello All,
we have implemented Account based copa and the operating concern currency in EUR.
no other fields in KEAo is activated like the company code currency and other fields.
the company code currency and the controlling area currency is SEK (Swedish Kroner)
sap note 69384 specifies that For account based PA, the operating concern currency is unimportant.
when we are trying to post a FI document, it is not asking for conversion from SEK to EUR
i tried posting to cost center and it got posted without asking for the conversion rate from SEK to EUR.
but when we are trying to post a controlling document(Account based COPA), it is asking for a converision rate from SEK to EUR.
can some one please clarify on why the conversion rate is required for account based copa.
Kind regards
SAP student

Hi
As far as posting to cost center is concerned, it is concerned with your controlling area.. It has nothing to do with your op concern.. Since your comp code and contr area currency is same, it does not ask for exchange rate
But the moment you post into COPA, where in you have specified another currency EUR, it asks for a conversion reason being your comp code currency is not same as EUR...
Even though op concern currency not reqd for account based COPA, but since you have specified it as EUR, it wud ask for a conversion rate
Hope this clarifies
Ajay M

ZXKKEU03 delivers wrong values in company code currency

Hello,
it is requested to transfer the value of a SD-condition (tables A004 + KONP) to a COPA value field with the help of the exit ZXKKEU03. Although the SD condition value is already in company code currency the system converts the value from operating concern currency into company code currency. An attempt to revert the conversion within ZXKKEU03 fails due to less decimal places (2) in ZXKKEU03 than in the SAP standard programs.
Does anybody have an idea how to solve this problem?
Many thanks in advance,
regards,
Martin

Hi Eric,
my message refers to that part of the source code within ZXKKEU03:
SELECT SINGLE * FROM VBKD INTO W_VBKD
                   WHERE VBELN = LINE_ITEM_7000-KAUFN
                     AND POSNR = '000000'.
                       Z_DATUM = W_VBKD-PRSDT.
     SELECT * FROM A912                          "Price acc. Price list
           WHERE KAPPL       =   'V'
           AND    KSCHL       =   'PR00'       "Gross turnover
           AND    VKORG       =   LINE_ITEM_7000-VKORG
           AND    VTWEG       =   LINE_ITEM_7000-VTWEG
           AND    SPART       =   LINE_ITEM_7000-WWVSP
           AND    MATNR       =   LINE_ITEM_7000-ARTNR
           AND    DATBI      >=   Z_DATUM
           AND    DATAB      <=   Z_DATUM.
    IF SY-SUBRC = 0.
      SELECT * FROM KONP INTO W_KONP
               WHERE KNUMH    = A912-KNUMH
               AND    KAPPL    = A912-KAPPL
               AND    LOEVM_KO =   ' '
               AND    KSCHL    = A912-KSCHL.
               EXIT.
      ENDSELECT.
      IF SY-SUBRC = 0.
          LINE_ITEM_7000-VV104 = W_KONP-KBETR * LINE_ITEM_7000-VV005 /
                                 W_KONP-KPEIN.
      ENDIF.
    ENDIF.
    ENDSELECT.
    IF LINE_ITEM_7000-VV104 = ' '.
    SELECT * FROM A004                           "Price acc..Price list
           WHERE KAPPL       =   'V'
           AND    KSCHL       =   'PR00'          "Gross turnover
           AND    VKORG       =   LINE_ITEM_7000-VKORG
           AND    VTWEG       =   LINE_ITEM_7000-VTWEG
           AND    MATNR       =   LINE_ITEM_7000-ARTNR
           AND    DATBI      >=   Z_DATUM
           AND    DATAB      <=   Z_DATUM.
    IF SY-SUBRC = 0.
      SELECT * FROM KONP INTO W_KONP
               WHERE KNUMH    = A004-KNUMH
               AND    KAPPL    = A004-KAPPL
               AND    LOEVM_KO =   ' '
               AND    KSCHL    = A004-KSCHL.
               EXIT.
      ENDSELECT.
      IF SY-SUBRC = 0.
          LINE_ITEM_7000-VV104 = W_KONP-KBETR * LINE_ITEM_7000-VV005 /
                                 W_KONP-KPEIN.
      ENDIF.
    ENDIF.
    ENDSELECT.
    ENDIF.
    IF LINE_ITEM_7000-FRWAE NE 'EUR'.
    IF SY-SUBRC = 0.
    SELECT * FROM TCURR INTO CORRESPONDING FIELDS OF TABLE I_TCURR
           WHERE KURST      = 'M'
           AND   FCURR      = LINE_ITEM_7000-FRWAE
           AND   TCURR      = 'EUR'.
    IF SY-SUBRC = 0.
      SORT I_TCURR ASCENDING BY GDATU.
      LOOP AT I_TCURR INTO W_TCURR.
           Z_UKURS = W_TCURR-UKURS.
           LINE_ITEM_7000-VV104 = LINE_ITEM_7000-VV104 * Z_UKURS.
           EXIT.
      ENDLOOP.
    ENDIF.
    ENDIF.
    ENDIF.
Regards,
Martin

Change the currency of Operating Concern COPA

Hi,
In my SAP environment there are 4 controlling areas. Only one of them is assigned to Operating concern. The remaining 3 have COPA inactive.
I would like to extend the existing operating concern to remaining 3 controlling areas, but before I do that I need to change the Operating concern currency as the one currently set is only relevant for only one controlling area and company code which is GBP. I need to change it to group currency - USD.
When I use F1 help on currency field in Operating Concern settings in configuration, I get information that 'once data has been posted, however, a change in the operating concern currency would cause the existing data to be interpreted as if it were posted in the new currency (for example: USD 1000.00 in old currency -> DEM 1000.00 in new currency).'
Even though we have transactional data posted in that operating concern , it is not being used by any department and we are quite happy to have existing data interpreted in USD instead of GBP. No reports are being generated in COPA currently so it will not be an issue for us. We want new data to be proper and constistent.
When I try to change the currency in operating concern config, the field is greyed out. I believe there is more complex workaround for that, but the only note I found on this is 651142 which says that SAP provides different tools to reorganize operating concern. But no further details are included.
If anybody managed to change operating concern currency, please help me with that.
Regards,
Karol

Hi Karol
I read the note given by you.. It asks you to contact the SAP for SLO Service (System Landscape Optimization )
This is a chargeable service by SAP... In case you decide to go ahead with this, do share your experience with us
Create an OSS msg and give ref of this note... I would suggest to go with SAP service and not with any one else's experiences... The tools that SAP is talking about are available only with SAP..
You may try to archive the existing data from COPA tables and then see if the currency field opens up for editing.. Am not sure about it..
Regards
Ajay M

Operating concern for two company code with different currency

Hi,
We are merging two company code into one SAP server.
We decide to use on chart of account, and to use one operating concern.
For company code A: the currency is CNY, for company code B: the currency is TWD. The operating concern currency is:CNY.
So i need to in KEA0(maintain operating concern) active company code currency, right?
So every posting in company code B will be posted in TWD and CNY to COPA same item, right?
In KE30 report, where to add characters: Currency type that i can show company code B report in TWD?
Thanks.

Dear David,
Yes. If you have different compancy codes within one controlling area, you have to maintain currency type with 10-Company code currecny and while maintaining the operating concern also you have to choose the company code currency only. Then only you will get the reports with respect of your company code currecny level. This will be basing on your company code-sales organisation, plants and other charcters assignment basis in your configuration.
All the best,
Dharma Rao. Yekula.

Value in Index-based currency in COPA report

Dear all,
I activate COPA with both accounting-based and Costing-based, I found that In Costing-based only Operating concern currency and company code currency display ,and in account-based we have 3 currency: transaction currency, company code currency and operating concern currency.
In FI config OB22 for commany code, we add Index-based currency and hard currency.
Is there any way to get and view value in Index-based currency in COPA report (accounting-based or costing based) ?
Thank you very much,
Dat Lam

Hi Dat Lam,
I am sorry to tell you that Index based currency can not be used in CO-PA in any form. This is not designed in the application.
Best Regards,
Abhisek

More than one country assign to one operating concern

Dear Experts,
I have created one controlling area for dubai entity and one operating concern for dubai.
now i am planning for country roll out so i have 10 countries for roll-out and all countries head office belong to dubai.
so i am planning to maintain USD as controlling area currency as well as operating concern currency along with company code currency tick in operating concern and assign all other countries to dubai operating concern and dubai controlling area.
Becoz management want to see reporting in USD as well as company code currency.
but reporting in CO comes under controlling area currency and most of the CO transaction reflects in controlling area currency like assessment and allocation where system takes controlling area currency by default .
any other point i am missing? and also how to see all CO reports in company code currency and how to do assessment in company code currency as well.?
your help will be highly appreciated.
regards
RK

Hi
All CO reports are visible in both currencies i.e. Contr area and Comp Code currency.. Just select company code currency in RPC0 for Cost centers and RPO0 for Order related reports
After executing Allocation, you can use the menu options and choose a layout for Displaying in OBJECT CURRENCY which means Comp Code currency
While calculating activity prices, you need to click on the settings Tab and tick the check box "Iterate amounts independently"
You can adopt single contr area provided all companies have same Fiscal Year and Chart of Accounts...
If any of the company has a different FYV, its better to have a separate contr area for them. Though using new GL you can have single contr area in that case also - My personal exp says its better to have separtae in that case
br, Ajay M

Info about a new value field in a live operating concern

Hi Team,
I'm working on 4.7 system.
I have a live Operating Concern with 120 value fields in "Active" Status.
Some of them never have been posted until now. I need a new "Quantity type" value field, but I can't create another one because I already have 120.
In addition, the value fields that have not been used until now are "Amount type" ones.
Is it possible to delete or modify one of these value files and create another "Quantity type" one, considering that Operating Concern is productive? And how can I do it? What kind of problems could I have?
Best Regards,
Gio

Hi Gio,
Good evening and greetings,
Please go through the SAP Note No.21207 on Deleting a Characteristic / Value Field from an active Operating Concern. This should clarify your questions.
Please reward points if the note is of some use to you.
Thanking you,
With kindest regards
Ramesh Padmanabhan

Maintaining operating concern after adding new value field

Hello,
I added a new value field to our live operating concern,maintained the data structure throguh KEA0(Maintain operating concern).The changes are transported from Development to Quality,Changes were reflected in Q system.After testing in Q system transports were pushed to production system.The new value field is added to the operating concern. When i check the log for KEA0 in production system it displayed one message like:
Field VV088 was added to the reference structure
Message no. KE782.You probably either changed the operating concern or SAP-EIS aspect, and added the field VV099 to the definition.
The added a CO-PA value field:
In this case, the field is added to the definition or the summarization levels. This invalidates all existing levels. Consequently, you need to activate them again and fill them with data.
In production system maintaining operating concenr or KEAO is only in display mode.Is it needed to regenerate the operating concern once again in production, how to do it. Is the message talking about the KEDV summarization levels.?
thanks
rahul

Hi,
No no ....KEDV is nothing to do here....that is creation of summarization in CO-PA.
Since you added new value field you necessarily have to Regenerate the operating concern...
Use Tcode KEA0...go to Environment tab...there the status of Cross client part and client specific part both will be in RED....now just click on the Cross client (candle button)...now the system would regenerate the operating concern...once it is over do the same for the client specific...
Beware when you do regenerate the operating concern no body can enter any transaction in that server since it is cross client table ...hence better do it after business hours.
Hope this helps!
Running KEDU with rebuild is relevant only when you already have created summarization and called up the same in the CO-PA report "options" tab. If you did not created the summarization you are nothing to do with KEDU.
Next: The new value field has to be transported to PRD and hence even in PRD we have to do the regeneration manually.
Regards,
Velumani
Message was edited by: Velumani Arunachalam
Message was edited by: Velumani Arunachalam

Adding new value fields to an existing and productive operating concern

Hi,
I would like to have 5 new value fields active in 4 out of 6 operating concerns that I am working with.
Is it correct that I could do this one of the following ways:
1. Use a value field that exists already in an operating concern and rename it?
In this case is it necessary to regenerate the operating concern?
Do I transport the change ?
2. Create an entirely new value field, and assign it to the operating concern?
Is it necessary to regenerate the operating concerns in question?
Do I transport the change?
3. Select a value field that is currently in the system but is not assigned to any operating concern eg some kind of SAP delivered value field? How do I assign it to the op con? Do I need to re gen the op con?
Which way is the best or is there a 4th option?
Thanks for your help in adviance
Regards
Aisling

Hi,
This note is a catalogue of notes of consulting notes where SAP tell you steps, reports to use and son . If you read them (these notes and related notes) you have the steps, guides, reports that you must use. Better advice. Try a solution with all steps in mind and check it in a quality enviroment. As you know there a lot of things in CO-PA concern (you have your own tables, with your own fields, your reports as KE2Rxxxx, and so on), your secondary indexes, etc.. , the best is try the solution in your Quality Enviroment (a quasi-clone of your production enviroment) and check the results (create SO, invoices, after modifications to check possible problems,...).
Regards,
Eduardo
pd: I forgot. If the size of tables (CE4xxxx, CE1XXXX, ...check them with DB02) are so big, get the opinion of a Basis Consultant. Surely in the before note there notes about this issue.
Edited by: Eduardo Hinojosa on Apr 23, 2010 2:41 PM

Add value field to existing/ productive operating concern

Dear All,
I need to create a new value field and add it to an existing operating concern, which is already in use (there is already transaction data in the live system).
In my opinion I have to do the following steps:
1. Create new value field (KEA6).
2. Add value field to operating concern (KEA0).
3. Activate operating concern (KEA0).
4. Transport operating concern (KE3I).
Is that strategy ok?
Is it ok, to transport an operating concern, when the system is already "live" and there is transaction data in the system?
Thanks for your answers,
Regards,
Michael

Hi,
first create new value field in KEA6. then take those new Value field in your operating concern Data Structure in t-code KEA0. Then generate the operating Concern.
Regards,
Sreekanth

Impact of adding new value fields in ongoing operating concern.

Hi All,
Want to know the steps of adding new value fields in the existing operating concern in COPA?
What is the overall impact of addition of New Value fields in the running Operating Concern?
How do we test the addition of new value fields?
Is the addition of New Value fields to the running Operating Concern advisable?
Your support and advice is highly anticipated and appreciated.
Thanks & Regards
9819528669

HI,
please search in SCN forum before you post:
Re: Adding a ValueField to an existing Operating Concern?
Best regards, Christian

Add value field to operating concern

Hello,
I have created a new value field VV955 and want to add it to my operating concern in transaction KEA6.
I go into change mode for all value fields for my operating concern and add a new line with my value field. When I hit the save button, it says "Field VV955 exists as Val. fld in field catalog -> choose another name".
Also when I go into change mode in KEA0 where you can drag value fields from left to the right, the value field is blue which means I cannot assign it to my operating concern.
Any suggestions?
Thanks
Anne

Hi,
While creating value field it will only consider long text. Inoperating concern Data structure in KEA0 you can assgin value field it will display in blue first, when you select to data structure you can see value field and save the value field.
Regards,
Sreekanth

Remove Value Field from Operating Concern

Hi all,
I created a new value field in DEV and assigned it to the corresponding Operating Concern.
Now, after some discussions, it is not necessary this value field.
I want to "un-assign" from the Operating Concern they use.
No data is being posted to this value field and nothing has been transported to QA yet.
Is this possible? Any ideas?
Thanks and Regards,
Flower.

I guess you can delete the value field as it was not transported to QA and PRD.
Here is some information given by SAP.
Deleting characteristics/value fields from an operating concern
You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.
Depending on the fields that were deleted, the following tables need to be converted (where xxxx = operating concern):
Characteristics: CE1xxxx, CE2xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Amount fields: CE1xxxx, CE2xxxx and CE3xxxx
Quantity fields: CE1xxxx, CE2xxxx, CE3xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Before deleting fields from an operating concern with a large data volume (more that 10 000 records in a table), you should refer to the section "The Database Utility" in the ABAP dictionary documentation. This section describes the database conversion process.
For database systems that do not require conversion (such as DB2 for AS/400, Informix, MSSQL), it can still take a considerable amount of time for the operating concern to be activated.
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. 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.
If you want to transport the operating concern into a different system, see the section "Notes on transport"
Note
Hope this helps
Thanks,
Reddy
Edited by: reddy sap on Sep 11, 2009 6:58 PM
Edited by: reddy sap on Sep 11, 2009 7:00 PM

Condition VPRS value in operating concern currency.

Similar Messages

Maybe you are looking for