Are two Exchange Rate types possible in Controlling ?
Hi SAP Experts,
My Client wants Exchange rate type "P" for Planning/Budgeting only and Exchange rate type "M" for all other documents in controlling.
In versions for fiscal year 2011, Exchange rate type "P" was configured and all documents in Controlling have been posted with exchange ate type "P" till now. Now Client wants two different exchange rate types only for documents that get posted in controlling.
Is there any way to restrict exchange rate type "P" only for Planning/Budgeting and Exchange rate type "M" in other Controlling documents ?
Thanks in advance.
Best Regards,
K.S.K
Thank You very much Ajay Maheshwari. I have tested the scenario in our testing system and it worked fine. The system picked exchange rate type "M" in CO actual postings and exchange rate type "P" for CO planning, since "P" was maintained in versions for year 2011.
Thanks again for quick turnaround.
Best Regards,
K.S.K
Similar Messages
-
Pricing Exchange Rate Type in Copy Control VTFL
Hello,
We have Pricing Exchange Rate type in the Copy control from Delivery To billing ( VTFL) at item level.
This Exchange rate type is used for price determination in the billing document. there are several options available for this field.
A Copy from sales order
B Price exchange rate = Accouting rate
C Exchange rate determination according to billing date
D Exchange rate determination according to pricing date
E Exchange rate determination according to current date
F Exch.rate determination accord.to date of services rendered
Normally the Exchange Rate in the accounting document is determined based on the rate available in the system on the billing date.
now what is the difference between "B" and "C".
I could not find any change in the way it processed when i put B or when i put C .
Does any one know what is the impact on the system if we select B or C. In what scenarios we use "B" and in what scenarios we use "C"
Your answers are much appreciated.Hi,
what is the difference between "B" and "C".
B Price exchange rate = Accouting rate
This value is used to determine the EXCHANGE RATE based on the Rate maintain in the ACCOUNTING DOCUMENT TYPES in OBA7 Transaction code irrespective of what determined in the ORDER
C Exchange rate determination according to billing date
This value determines the EXCHANGE rate based on the Rates maintained in the Transaction code OB08 and get the values from the table TCURR based on the BILLING DOCUMENT DATE.
regards,
santosh -
One Conversion Type and two Exchange Rate Types in one report
I have Conversion Type called TEST. In this Conversion Type there is Exchange Rate Type D selected (D-daily). I have also Fixed Target Currency selected. And the report works perfectly fine....BUT.......there is also Exchange Rate Type M defined in the system (and it used for the exchange rate used last day of the month).
The question is: how to put both Exchange Rate Types into one Conversion Type so both types are used in the reports?Hi,
You can go for a variable exchange rate type.
Creating variable:
For this you have create a varible which can take diffrent exchange rate types.
Open query designer create a new dummy query in that search for infoprovider 0RTYPE.
It will have one dimension(name ->key) with 0RTYPE in it.
create a variable for 0RTYPE.
Save and close the query.
goto RSCUR -> give your translation type -> go to exchange rate tab -> choose Ex. Rate from var option -> give the variable you have created prviously for 0RTPYE.
Rest all same but just for completion...
Go to your query in which in u want to do cur conversion.
Double click on the key fig
Go to conversions tab-> select the conversion type u created in RSCUR.
When you run the query you can select the exchange rate type in the variable screen.
rgds,
Raghu -
Currency Conversion for Exchange rate type "AS02"
Hi Experts,
I am gonna post the most challenging problem (regarding currency conversion) I ever faced in my 1 year of BW Carrier.Kindly provide a solution.
There are three types of currency to be used in the query for Key Figure 0NET_VALUE (so total 3 Key Figures to be created)
1.Document currency (may be any currency)
2.Local Currency (must be EURO)
3.Global Currency (must be USD)
From Document currency to Local Currency(EURO) we are using Exchange rate Type "M" (in Conversion Type created in Trans RRC1) [There is no problem in this conversion]
Problem starts now--->
From Local Currency(EURO) to Global Currency(USD) we have to use Exchange rate type "AS02" (in conversion type to be created in RRC1)
but there is a Business requirement that currency rate should be as per the last day of the entered period;and this logic should work for the range of periods also.
Example :
we are executing query for the period 006/2006 (posting Period)
Last day of this period is 06/30/2006,
Currency rate would be as per 06/30/2006
And this currency rate should be same throughout the period 006/2006 in query
The example was for single period,but logic must be incorporated for the range of the periods.Hi..
There is no corresponding source key figure in the InfoSource for the target key figureof the InfoCube.
a. A source key figure of the same type can be assigned to the target key figure
(for example, sales revenue instead of sales quantity revenue).
If the currencies of both of the key figures are the same, no currency
translation can take place.
If the currencies are different, a translation can take place either using a
currency translation type or by simply assigning a currency.
The following table provides an overview of possible combinations with different
currencies in the source and target key figures:
if Source key figure currency is fixed , Target key figure currency is variable then Currency translation (CT) No CT
if Source key figure currency is fixed , Target key figure currency is fixed then Currency translation (CT) CT
if Source key figure currency is variable , Target key figure currency is fixed then Currency translation (CT) CT
if Source key figure currency is variable , Target key figure currency is variable then Currency translation (CT) CT or assignment
b. If there is no corresponding source key figure of the same type, then you have
to fill the key figure for the data target from a routine.
If the target key figure has a fixed currency, no currency translation is
carried out. This means that if translation is required, you have to execute
it in the routine.
If the target key figure has a variable currency, you also have to assign
a variable source currency to the routine. Using the F4 help you can
select a currency from the variable currencies in the communication
structure. You have two options:
You can select a variable currency and assign it.
You select a currency translation type and a currency into which you
wish to translate (To currency).
The To currency is, by default, the target currency if it is included in the
communication structure.
Creating a Routine for Currency Translation:
If you want to translate currencies in the update even though the currency translation is not
available for one of the above reasons, you can create a routine. Choose Routine, set the
Unit Calculation in the Routine and choose Create Routine. In the routine editor you get
the additional return parameter UNIT, the value of which is used to determine the target
1. save the query and it under role
see to it is in : Restricted and calculated key figures ---> properties of k.f
2. exeute the query
3. the currency translation --> by target currency usd choose OK
conversion type : MEANTODAY Fixed target currency current date (MT)
4. Go back to the query definition by chossing chage query ( global definiton)
5. in the context menu for % share sales vouume of incoming orders, choose properties --> formula collision --> result form this formula choose OK
Note that -
your should alos set the currency translation in the properties for the two key figures sales voule EUR , choose properties ---> currency conversion key : fixed target currency , currrent date ( MT) --> target currency : American Dollar . choose OK
<b>The translation key is a combination of different parameters that establish how the exchange rate for the translation is executed.
The parameters that determine the exchange rate are the source and the target currency, the exchange rate type and the time reference for the translation.</b>
The source currency is determined from the data record or dynamically from the master data of the specified InfoObject (currency attribute)
The target currency can either be fixed in the translation key or selected at the time of translation.
You can also use an InfoObject (currency attribute) to determine the target currency.
The exchange rate type distinguishes exchange rates that are valid in the same time frame next to each other, for example, the bid rate, ask rate or middle rate. The exchange rate types are stored and can be maintained in a central table (TCURV).
The time reference for the currency translation can be either fixed or variable
The fixed time reference can either be a fixed key date that is stored in the translation type, or be determined using the system date when executing the currency translation.
If the time reference is variable, then the point in time for the exchange rate determination comes from the value of a time characteristic (InfoObject). The reference can, for example, be the end or the start of a fiscal year or a calendar year, a period and a month or even to the exact day. It can also be determined using a customer-specific InfoObject (for example, trading day).
Currency translation in the BEx
When selecting a translation key with a fixed target currency this currency will be added automatically to the query definition
Also, you can use translation keys selecting their target currency at the time of translation. These can be applied in two different ways:
Selection of a specific target currency in the query definition (1)
Entry by variable (2)
Dynamic translation keys require input from the InfoCube !
InfoObject value will be read during query execution
Examples:
dynamic time reference (p.eg. 0CALDAY)
time characteristic
target currency determined by InfoObject (currency attribute)
characteristic which contains currency in its attribute table
the corresponding InfoObject has to be part of the InfoCube
1.Define the currency attribute in the InfoObject maintenance
The currency attribute has to be a unit InfoObject of type currency
The unit InfoObject must be an attribute of the characteristic
The currency attribute should be filled in the master data table of the corresponding InfoObject (manual maintenance or upload via InfoSource)
2.Enter the InfoObject in the translation key maintenance
Only InfoObjects with a currency attribute can be used in translation keys (p.eg. 0COMP_CODE)
At the time of currency translation the value for the source currency / target currency is then derived for every record from the master data table of the specified InfoObject
All values for a query are translated ad hoc (after having executed the query) using a translation key
Depending on the translation key a fixed target currency will be used for translation or you will be able to select the target currency
The ad hoc currency translation offers only restricted functionality (selection of translation key and target currency) compared to the currency translation in the query definition
Do not forget to create your translation keys before starting your work in the Business Explorer Analyzer
Example:
You load the following record to your InfoCube:
Company Code: 1000
Amount in Source Currency: 500,-
Source Currency: FRF
Target Currency: ?
In the Update rules, you are now using a translation key which derives the target currency from the InfoObject 0COMP_CODE. During the Update Process the target currency will then be read for Company Code 1000 from the master date table of 0COMP_CODE.
With the currency translation in the Business Explorer, the source currency can currently only be determined from the data record.
Only translation keys with a fixed exchange rate type can be used in the BEx
Translation keys with a dynamic time reference (from an InfoObject) can only be used in the query definition. It is not possible to fill the InfoObject by a variable !
Translation keys getting their target currency from a currency attribute can only be selected in the query definition
When getting the dynamic reference from an InfoObject (p.eg. 0CALDAY) the currency translation will apply to each record read from the database. That means it will use the date in this record for the currency translation.
When using a variable you will restrict the output of your query to a certain amount of data. For example, you would translate all invoices of March 11 with the translation date March 11
This means, the requirement show me all invoices in my cube in group currency, conversion date: 14.07.2001 could not be solved by a variable input for 0CALDAY
I hope this would help...
with regards,
hari -
Hello All,
Please expalin the on pricing exchange rate type in copy controls.
Copy from sales order
Price exchange rate = Accouting rate
Exchange rate determination according to billing date
Exchange rate determination according to pricing date
Exchange rate determination according to current date
Exch.rate determination accord.to date of services rendered
User will change the bill to party during billing based the bill to part currency will be determined at billing header.
But currency in sales order is INR and if user changes the bill to party(Foreign) currency in billing will be EURO
and user want to cancel the invoice cannot able to cancel because currency from sales order to billing is different.
How can we fix the issue. Can we use any of the above mentioned pricing exchange rate types to fix the issue.
Best regards,
rameshHi
See SAP Note 22781 - Exchange rate in accounting, exchange rate type, problem C. It explains how to work the data en table TVCPF (data mantained in tcode VTFA). I suggest to set a break point in this coding and debug it to undertand how it works.
I hope this helps you
REgards
Eduardo -
Exchange rate type for posting to Controlling
Hi
We are using Currency type as 20 in Controlling Area. We have several Company Codes and each have different currency.
While posting entry from FI to CO , the system always take exchange rate type as M.
Please let me know whether we can assign some other exchange rate type for actual transactions.
Thanks
Gaurav JainHi
Goto TCode OBA7 and select your document type (usually SA ) and enter in Field "Ex.rate type for forgn crncy docs" your required exchange type.
Cheers
Srinivas -
Is it possible to change the standard exchange rate type?
Hi all,
at the moment, standard setting is that exchange rate type M is associated with the local currency of my company code, is it possible to define a new exchange rate type and assign it to the standard local currency instead of M?
Thanks!
DuskoHi
All postings and Clearing happen thro the Exchange rate type M which is the standard setting and cannot be altered. However for valuation and other purposes, we can have our own types
Jayaram -
Foreign Exchange Rate Type - M and EURO
Hi All,
My customer is maintainng the M exchange rate type as
1 USD = 106 JPY
along with this they are maintiaing a extra Exchange rate Type EURO as
106 JPY = 1 USD
Comany Code Currency is JPY.
In the document Type level they are not maintaing any of the exchage rate type. Means system is picking default exchnage rate type. As we know M is the default exchange rate type.
So, now customer doesnt want to maintain the EURO exchange rate type.
So, i want to know
1. if customer not want to maintain the EURO exchange rate then it would give any impact on the working.
2.Is any realtion between to maintain the two exchnange rate type.
3. On a document level, can we know that by using which exchnage rate it was processed. whether its was processed from M or EURO. We want to know the Exchange rate type of each document.
4. In M Exchane rate type we have both Direct and Indirect Quotation for same currency pair. So in this case which qutation system would take for the document processing as default quotation for a exchange rate type M.
Looking for early response.
Sachin1. if customer not want to maintain the EURO exchange rate then it would give any impact on the working.
<There is no impact as long as this is not used by any other applications. For eg, In controlling, project system, budget, at FI document type level etc, we have option of choosing different exchange rate.
2.Is any realtion between to maintain the two exchnange rate type.
No relation
3. On a document level, can we know that by using which exchnage rate it was processed. whether its was processed from M or EURO. We want to know the Exchange rate type of each document.
< You can see this at Table level eg - BKPF. But at front end I dont think it is possible atleast upto 4.6C4. In M Exchane rate type we have both Direct and Indirect Quotation for same currency pair. So in this case which qutation system would take for the document processing as default quotation for a exchange rate type M.
<To my knowledge, System will not allow to maintain rates in both types. so question of option doesnt come> -
Exchange rate type for version - error message GP541 during confirmation
Hi FICO Experts,
I bumped into a problem during confirmation in CO15. (I would like to get the SFG by mvt 101 and consume the raw material by 261).
The error messase I get is:
Maintain the exchange rate type for version 000 in 2009
Message no. GP541
Diagnosis
You want to use plan version 000 with controlling area 1000 in fiscal year 2009.
You have not specified an exchange rate type for this plan version for fiscal year 2009. Since the update of all currencies in 2009 is active in the control indicators of the controlling area, currency conversions are possible and sometimes also needed.
It is therefore necessary to specify an exchange rate type for plan version 000 in year 2009.
System Response
The system will not accept your entry.
Procedure
1. Please maintain plan version 000 first using the function 'Change Plan Version', or
2. correct your typing error.
I'd like to ask you to please help to resolve this issue.
Thanks,
Csabago to Maintain Version at SPRO-Controlling-General Controlling-Organization->Maintan Version and do what ever it says. Provide Exchange rate type P or M would resolve your issue
-
Payment Program and Spot Exchange Rate Type
Hi Everyone,
When performing wire transfers in foreign currency, my company wants to be able to have the payment program, F110, be able to convert the payment to the vendor based on the bank's spot rate at that moment in time. I found that we can use exchange rate type "G", update the rate within OB08 prior to running F110, input the exchange rate type "G" within the Parameter section within "Exchange rate type" and process the payment program as normal.
My question is this: We have a few separate companies that would use this feature with the possibility of receiving different rates from their respective banks. How would this work if 2 companies had 2 separate exchange rates for the same conversion on the same day? I found that once you enter in an exchange rate for a conversion, you are stuck with that rate for that particular day, so the amount can not be over written with another rate to be used by the second company code. Is there a way around this or is there a different way to accomplish the converting of currencies at the payment program?
Thanks.
Pete
Edited by: Peter Zaborowski on Sep 26, 2008 2:35 PMHi Peter
Use two different exchange rate type for bank1 and bank1. Upload the exchange rate into the system. Select house bank and specified rate type during the payment run.
Regards
Srinivas -
Exchange Rate Type per Company Code
HI Experts,
In our system the conversion rates for EURX are maintained since there are several European companies working with the system.
Now we would like to use the same SAP-system for companies in China & Taiwan. In both countries there is an individual "official" exchange rate which does not equal the exchange rates stated from the German banks and thus fed into the system.
Is there any possibility to connect a company (code) with one particular exchange rate type? Since we are dealing with countries outside of the EU.
Thanks in Advance
SivaHi,
as you may have recognized, the assignment cannot be made on company code (or country) level, but only on currency level. In particular, this is table TCURF.
When (almost) all possible currency combinations (from-to) are redirected to rate type EURX, then this looks like standard SAP delivery settings that you can freely change according to your needs.
If you are not familiar with TCURF maintenance, however, you should be very careful here and test every change before importing it to the productive environment.
The basic idea that I have always followed for the same or similar requirements is that local rules for a particular rate type are always control the rates to be applied when converting from any foreign currency to the currency of the particular country.
If you are a China company and your local company code currency (curr.type 10) is CNY, then you have to make the following changes to table TCURF:
First, find out all the foreign (non-CNY) currencies that you are dealing with. This may include EUR, USD, and any other currency of the world.
Then, determine (or create) a new exchange rate type in table TCURV. This should be the rate type for your "own" rates. Let's name it rate type "L" (for Local rates). Note: you can use the standard M rate type as well, but it is more transparent if you define a separate one.
Then have a look into table TCURF and find the entries as follows:
Rate type: M
From-currency: all that you are using in your business (all non-CNY that you use)
To-Currency: CNY
Valid-from: find the recent entry for each combination
With all of these entries displayed, you will find that the alternate exchange rate type field (ABWCT) in these entries is set to EURX.
Now you want to create a new TCURF entry as follows:
Rate type: M
From: the same foreign currencies as above
To: CNY
Valid-from: a newer date than the last current entry
Alternate exchange rate type: L (your new rate type) - in case you want to use just M, then leave ABWCT empty.
If you are using the L type (which I recommend), then you have to add 2 new entries to TCURF for each foreign currency:
1.
Rate type: L
From: foreign curr
To: CNY
Valid-from: 1.1.1800 (yes!)
Ratio from and to: as you want, it should be the same as in the corresponding M entry, usually 1:1, but it depends
Alternate exchange rate type: leave it blank.
2.
Rate type: L
From: CNY
To: foreign curr.
Valid-from: 1.1.1800 (yes!)
Ratio from and to: as you want, it should be the same as in the corresponding M entry, usually 1:1, but it depends
Alternate exchange rate type: leave it blank.
Finally, in OB08, you have to maintain rates like
type L, foreign curr to CNY
You are done
What is happening is the following (example you post a document in USD in your China company code)
Doc.currency USD --> must be converted to your local currency CNY
First, the system looks the current ratios for the M entry:
M, USD to CNY, valid from: recent, 1:1 and ABWCT = L !!!! (the entry you have added before)
Then it checks the ratios for L:
L, USD to CNY, valid from 1.1.1800, 1:1, ABWCT = blank
Based on TCURF, the system will look for the current rate entered under rate type L, your local rate )
Now what if a USD-based company has to post something in CNY? No changes there as the TCURF settings were not touched. They should look like this:
M CNY to USD, alt.exch.rate type EURX (or blank)
If it is EURX, then the rates enterd under EURX rate type (once USd to EUR and then CNY toi EUR) are read and the cross-rate CNY to USD is calculated.
If it is blank, then the rate entered under rate type M is used.
In both cases, no change to your current process.
It works similar if the company code is EUR based.
The main idea is: redirect all M entries in TCURF where <anycurr> to CNY to the new rate type L, but leave all other TCURF entries untouched. Direction <any> to CNY are only relevant for the China company code, the rest of the world does not care about that conversion. They might be interested in conversions like CNY to <any>, like in the above example, CNY to USD, or CNY to EUR, but that could be their German or ECB rate, you do not have to care about.
<removed_by_moderator>
Csaba -
Using Diffrent Exchange rate Type for Payroll
Hi All experts,
We wish to use a different exchange rate type for Payroll currency conversion. As we all know that the Payroll driver uses the currency coversion rate M and is hardcoded in the standard Programmes.
Now please suggest me whether it is possible in any means to use different currency conversion rate for Payroll?
Also we have explored the Global payroll, but the same has been not yet released for all customers, can I use it as it provides with the option of choosing exchange rate type on a particular date and have standard excahnge protection IT.
Awaiting guidance from u all....
Thanks in advance
Regards
learnerHi,
No i want system to pick diffrent exchange rate so i want to change exchange rate type for 1st Local Currency.
But that area is greyed out. Is there any system setting where i can maintain diffrent Exchange rate type for 1st Local Currency instead of "M". or is there any other way out that system will pick up diffrent exchange rate.
Problem is that two entities are operating in different market having same local currency but conversion rate for Foreign currency will be diffrent e.g. Local Currency EUR Exchange rate between EUR -USD in France 1.20 and Exchange rate between EUR-USD in Germany 1.25.
Is there any wayout to deal with such situation.
Please suggest.
Regards,
Manish -
Exchange Rate Types Used In What Transactions
Hi Experts!
I was inquiring on if there is a way to see all exchange rate types ("M" and alternative exchange rate types), with respects to where they are used, posted, and most importantly, what all transactions use them. The exchange rate types we use are M (system), Z1 (custom), and 0011 (custom). Even if there is a SAP note, on this, that would be helpful too. Urgent! Thank you for your time!
WCHi Will,
Execute transaction code <b>OB07</b> to see all the exchange rate types within your system.
The following should help you to understand where they are used and which transactions used them.
In <b>planning</b>, exchange rate types are used to specify exchange rates used for different purposes at the same time in the system. Existing entries may not be deleted.
When exchange rate conversions take place between many different currencies, using a reference currency can simplify maintenance of exchange rates. For the exchange rate types concerned, you then only have to specify the exchange rates in relationship to the reference currency for all currencies. The SAP R/3 System then carries out all exchange rate conversions in two steps, using the reference currency.
As well as a <b>buying rate</b> "<b>G</b>", you can also maintain a <b>selling rate</b> "<b>B</b>".
The buying rate is that under which the average rate "<b>M</b>" is recorded.
When maintaining a buying rate, enter the appropriate currency type for the average rate. This reduces the amount of work required in the conversion table.
The selling rate is that under which the average selling rate is recorded.
The user need only maintain the conversions for the average rate. The conversion occurs by determining the average rate and then adding the difference between the rates to this rate.
If an entry for a currency conversion is missing, the indicator Invert ensures that the reversed currency relationship, should one exist, is available for the conversion.
<u><b>Standard settings</b></u>
The standard R/3 System includes exchange rate type <b>P</b> (standard translation for cost center accounting).
<u><b>Note</b></u>
When you create a controlling area, the SAP R/3 System creates version 000 automatically for 5 years. Rate type <b>P</b> is defaulted.
The R/3 System uses rate type <b>M</b> for currency conversion during postings and clearings of documents.
<u><b>Recommendation</b></u>
Before creating your own exchange rate types, check those offered by SAP and use them if appropriate.
I hope the above helps.
Do not forget to award the points please.
Regards,
Jacob -
Define exchange rate types according to ledgers
Hi Everyone,
I am facing a problem about the exchange rate types.
I want to set different exchange rate types for my leading ledger and local ledger.
for example, the leading ledger 0L is defined for IFRS with default exchange rate type M.
the local ledger LL is defined for our country China and i want to use own-defined exchange rate type say Y001.
is it possible realize like this in SAP.
thank you so much!
regards,
samsonHi, Samson:
I am not sure whether it make sense to have different exchange rate for same two currencies in different countries, for example, in China and US, exchange rates for RMB and USD are different in same situation, like buy-in...
Your question about exchange rate definition in Non-Leading Ledger - it is impossible to do that in Define and Activate Non-Leading Ledgers.
For the purpose of Ledger approach for parallel accounting, it is used to meet the reporting requirements basically, for example, IFRS or USGAAP or HGB, but not for exchange rate type...
If you get any surpurise information, please share with me. Thanks.
Best Regards, Lawrence -
KP98 - Differences because of exchange rate types
Hello,
I am using KP98 transaction to copy actual data to plan data.
I take CO area currency for example and the system copy the amount correctly in my CO area currency, but in object currency there is a difference because of the exchange rate types ( actual and budget exchange rate types are different)
Is it possible to copy the same amount in the two currencies?
Thanks a lotHi,
during copying the data in CO area currency are converted into local currency based on the ex.rate settings in the CO version definition, the local curr. data is not really copied.
If you have an ex. rate that is changed every period it should be possible to copy the first period (with the correct ex.rate settings in CO version definition), change the ex.rate setting, copy the next period, change the ex. rate setting again, copy again,...
Best regards, Christian
Maybe you are looking for
-
Is it time to upgrade to an imac
Hi.. I currently work on Logic 9 and kontakt 8 library and some other au instruments.. All of this is connected to a 2009 MacBook with 2gb ram. My only question to the experts is whether a ram upgrade would let me work full fledgedly or is it time fo
-
Purchase Order - How to call customised PO_COMMUNICATION_PVT package?
We need to add additional fields to the Standard Purchase Order that is produced by using View Document on the PO form. The only suggestions in the forum so far are to modify the PO_COMMUNICATION_PVT package or the PO%XML views. But the option of ove
-
How to solve crash problem when doing "package" with Indesign CS 5.5?
Hello everyone, I've been having trouble with Indesign CS 5.5 when I use the package tool. I work with indesign for a long time, create my document files, and when everything is done, finished, i go and do the Package. But at a certain point it crash
-
Hi All, I've read the other threads on this but not found one exactly like it. We are running Exchange 2010 SP3 Update 1. We recently sent out an internal email to a distribution that had a couple of dynamic DL's in it and a few regular DL's. A lot
-
How do I record music from a music cd to my MacBook Pro? Up until this morning I would get a pop up window that asked if I wanted to play or record the disc I just put in. That screen no longer appears - a disk starts to play. I can stop the auto