Exchahge rate type in case of import

All SAP Gurus,
While doing Goods Receipt against a PO (for imports), which exchange rate is picked up by the system?
From where system picks up which exchange rate to be used?
Regards,

Hi  Rajan
Exchange rate is picked form the Exchange table maintained by FI. Use Txn code OB08 and find out the exchange rate for the date or week or month you wish to know the details. This tabkle is common and used for all the transactional activities.
Regards

Similar Messages

  • 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
    Siva

    Hi,
    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

  • COPA0004 Change in Exch.rate type

    Hi,
    We’ve a costing based CO-PA in our instance which is shared by other co.codes in our environment. Now, with new business requirement, we
    may have to use a separate exchange rate type for CO-PA than M. We’re trying to achieve this with exit COPA0004. We’ve also read the note 429517 on Currency translation billing document -> CO-PA to understand the value flow to COPA.
    Please note that we don’t want to affect current exch.rate settings of existing co.codes which is ‘M’. However, for a new co.code we want
    to move values to COPA with ‘P’ exchange rate.  
    Question-
    Is it possible to achieve it through user exit COPA0004 to default exchange rate in COPA based on company code? Or is it a blanket change
    for all co.codes if we change the rate from ‘M’ to ‘P’. 
    We’re evaluating the solution before implementing in system.  
    Thanks,
    Nirav

    Hello Nirav,
    planning version settings in CO-PA do only affect planning data!
    Conversion with actual data will always be done with rate type 'M'.
    Enhancement COPA0004 offers however a possibility to use different
    rate type in case of actual data.
    Function module EXIT_SAPLKECU_001 can be used to change the exchange
    rate type for currency translation when actual data is processed in
    Profitability Analysis. By default, the system always translates the
    values using the exchange rate type "M". You can change this type
    (export parameter E_KURST) for a specific operating concern (import
    parameter I_ERKRS). The import parameters I_CURRENCY_FROM and
    I_CURRENCY_TO contain the currency key of the currencies involved in the
    translation.
    You can only change the exchange rate type for translating actual
    values! For planning, you specify the exchange rate type in Customizing
    when you define your plan versions.
    Best regards,
    Ronghua Fan

  • Use of Diff. Exchage Rate Types in Diff. Scenarios (Import /Export/Other)

    Suppose maintained following Rates against USD in OB08 -
    B (Bank Selling Rate) - 46
    M (Avg. Rate) - 45
    G (Bank Buying Rate) -44
    Which Exchange Rate Types are used in case of following -
    In case of Import -
    In PO
    In GRN
    In MIRO
    In Case of Export -
    In SO
    In Billing Document
    In Sales Accounting Document
    In Excise Accounting Document
    Also in case of following -
    At the time of Receipt
    At the time of Payment
    At the time of Revaluation of Open Items of Customer 
    At the time of Revaluation of Open Items of Vendor
    At the time of Clearing of Advance against Vendor Invoice in F-44
    Please guide in this regard...
    Thanks & Regards...
    Ameya

    Hi,
    Where ever an accounting document is created there a document type will be used for the postings and in that document type we will be assigniong like which exchange rate has to be used for which document type.
    Hence the system will identify from the document type where the accounting documents are generated.
    But in case of PO & SO it will be determined from the material master as per the exchange rate assifnment.
    Regards
    Shaik Javeed

  • Goods Receipt Rate (GRN) Rate in case of Import

    Hi,
    I would like to know which rate should system pick at the time of making goods receipt note (GRN) in case of import material.
    E.g. If an Indian Company is importing material from USA in august when $ rate to INR is 50, and
    if material received in septmber when $ rate is 45. then
    at the time of GRN what exchange rate should system pick.
    thanks in anticipation

    HI
    Its depends on the Purchase order , in delivery/Invoice tab you can find the check box with Exchange rate Fixed , if it is selected then during GRN it will pick what ever you maintained in the PO, and if it is not selected then it will pick from the customization tables which will be maintained by Finance department.

  • Archived case in ISU not allowing to change rate type

    Hi,
    There is one case where rate type is changed after 'move in' during data conversion. Move in rdg and code '17' (rate type change) rdg were entered.Date of 'move in' and 'rate type change' is same.
    Custoemr was getting billed for so many years.
    Few months back they do archiving of their meter reading data.
    Now when they are trying to change rate type again with current date, system is giving an error asking for initial code 17 reading which is in archived period.
    If we try to enter that reading in t code EC30, then it says the mr date is in already billed period.
    Whether anyone knows how to resolve this issue? Is it because of archiving?
    Regards,
    Reymond

    Hi,
    You can only change notification type for created notifications that are of type "General" (Notification category-05). If it is not general then you can not change in IQS22 (or other change notification transactions).
    -Paul

  • Mass update exchange rate type (not rate) in open sales orders

    Hi all,
    Our requirement is to update the exchange rate type at sales order header (VBAK-KURST) for all open sales orders with a new type created. (Z001). This field does not appear in MASS transaction for sales orders despite being present in the structure MASSSDHEAD.
    This field cannot be located even in VA02 transaction (I am not sure if standard SAP masks or shows this field at header; I also can't find any transaction variants assigned).
    Can anyone suggest how this field can be updated for sales orders either individually or in mass mode.
    Regards,
    KC
    SAP SD

    You are correct in indicating that Exchange rate type field  is not seen in Header data of sales order. I checked screen layouts for various screens for sales order data and this field is not suppressed. The only reason could be that this field is not used in sales order screens
    If you are interested, you could also check in the following way
    1.  Go to SE11, enter database table as VBAK
    2. Once inside data dictionary table, click where used list button, select programs and screens and execute
    3. click continue (don't select background)
    4. now you would have list of programs and screens, this table is used
    5.  now start another session and go to transaction SE51
    6. indicate program name as SAPMV45A and screen numbers as listed in step 4. you can check all screen numbers to see whether Exchange rate type field is listed in sales order layout.
    7. Of particular interest would be screen number 4311 as this contains  Financial accounting data & 4303 Billing data
    8. you can check screen layout for screen 4311 & 4303. you would see Exchange rate type field is not indicated.
    9. in case you could find this field in any screen, you could ask your ABAP consultant to add this field in the layout screen.
    Hope this answers your question

  • Exch.Rate Type for Determining the Proposed Rate

    Dears,
    I defined, in the document type to be used for Goods Receipt, the field T003-KURST (Exch.Rate Type for Determining the Proposed Rate) equal to u2018Pu2019: exchange rate type used also for standard translation for cost planning.
    Then, I created a Purchase Order using a vendor in foreign currency, and in the header section within tab u2018Delivery/Invoiceu2019 in field "Exchange Rate" I filled in the exchange rate valid at the moment of the Purchase Order creation and I also put the flag in the indicator "Fixing of Exchange Rate".
    Afterwards, I posted  the Goods Receipt against the Purchase Order created at the previous step.
    My expectations were to find in FI accounting:
    - 1 line item for stock increase (transaction BSX) valuated using the exchange rate defined in the document type in field T003-KURST;
    - 1 line item for GR/IR increase (transaction WRX) valuated using the exchange rate defined in the Purchase Order and indicated as fixed;
    - 1 line item for difference (transaction PRD) between stock and GR/IR.
    but when I checked the accounting document, these my expectations were not met, because:
    - the line item for stock increase (transaction BSX) has not been valuated using the exchange rate defined in the document type in field T003-KURST, but a differet exchange rate that I didnu2019t find defined for this couple of currencies;
    - the line for GR/IR increase (transaction WRX) has been valuated as expected using the exchange rate defined in the Purchase Order and indicated as fixed;
    - the line item for difference (transaction PRD) between stock and GR/IR has been created.
    The help (F1) for field T003-KURST, show the following indication:
    Exch.Rate Type for Determining the Proposed Rate
        Rate type under which the proposed rate is defined for foreign currency documents.
    Use
        If no exchange rate is specified in the document header when entering documents in foreign currencies, the system will automatically select a rate from the currency translation rate table.  The system then converts all amounts in the document's line items using this exchange rate.
        The system uses the average rate as a default value as long as no other exchange rate type is entered here.
    Based on this message, my expectation is that all documentu2019s line items have to be converted at the exchange rate type defined in field T003-KURST. And in the case mentioned above, the line for stock (BSX) should be converted at exchange rate type defined in field T003-KURST.
    While, correctly, the line for GR/IR (WRX) has been converted at the exchanged rate fixed in the purchase order.
    Can you please let me know how can be fixed the problem for the line related to the stock allowing the conversion using the exchange rate type defined in field T003-KURST?
    Thanks and Regards,
    Jody

    Hello Jody,
    kindly consider the information contained under the attached note:
    191927 - Posting logic: GR for foreign currency PO.
    As stated in it:
    Postings to the material stock account (BSX):
    In order to be able to determine the value of the stock posting, the
    valuation methods which exist in the material master in local currency
    (standard price, total value of stock) must be converted into document
    currency. This translation is thus carried out on the posting date with
    the exchange rate type that is assigned to the FI document type used,
    that is, independent from the exchange rate defined in the purchase
    order!
    If no exchange rate type is assigned to an FI document type, the system
    uses exchange rate type M.
    Please, check in your system the settings stored in the customizing
    transaction OBF4 for the document type WE (Goods receipt). If the field
    'Exch.Rate Type for foreign currency documents' is empty, the exchange
    rate type M is used.
    The fixed conversion rate in the purchase order refers to the valuation
    approach in the purchase order and, therefore, to the costs for the
    purchased material. Therefore, the posting amount to the GR/IR clearing
    account (WRX) is converted according to the fixed conversion rate in the
    purchase order header.
    On the other side the fixed conversion rate in the purchase order is not
    designed for converting the posting values to the material stock account
    (BSX). This conversion reflects the situation of the valuation of the
    material stock and is therefore designed to be independent of the
    conversion rate defined in the purchase order. This is what note 191927
    outlines.
    In the note 191927 you will also locate relevant information about the
    postings to the KDM key:
    Exchange rate differences (KDM):
    As of Release 4.0A, exchange rate differences (KDM) can be posted to a
    separate account. The exchange rate differences result from the
    difference of the clearing value on the GR/IR clearing account (WRX) in
    document currency that is translated to the current exchange rate stored
    in the system in local currency from the clearing value in local
    currency that is determined with the conversion factor from the purchase
    order or the invoices.
    The offsetting entry for the exchange rate differences is settled with
    the price difference.
    (Price difference = GR/IR amount - stock value - exchange rate
    difference)
    KDM is only posted during the GR if the flag T169P-XPLCU is initial,
    therefore, KDM postings will not occur during incoming invoices.
    This is determined in the IMG path:
    Materials Management
    -> Logistics Invoice Verification
       -> Incoming Invoice
          -> Configure How Exchange Rate Differences Are Treated
    Here, you have the following options per Company Code:
    .- The exchange rate differences will be calculated from the difference
       between the exchange rate at the time of the goods receipt and the
       exchange rate at the time of the invoice receipt.
    .- The exchange rate differences will be calculated from the difference
       between the exchange rate at the time of the invoice receipt and an
       assumed exchange rate that is valid for a specific amount of time,
       such as a year or a season.
    .- No exchange rate differences will be calculated. Instead, differences
       from exchange rate variations will be considered as price differences
       and posted to a price difference account.
    The field T001A-CURDT for the company code will determine which date is
    relevant to calculate the exchange rate difference.
    This is set under the IMG path:
    Financial Accounting
    -> Financial Accounting Global Settings
       -> Company Code
          -> Multiple Currencies
             -> Define Additional Local Currencies
    So, finally, the value for KDM calculates as difference between
    GR/IR amount in local currency - GR/IR amount in foreign
    currency*exchange rate.
    I hope this information can be of help.
    cheers
    ray

  • Exchange rate type P is replaced with M

    Hi,
    We are using CATS for time booking and the process is as follows:
    1) CAT2 -> Hours booked.. Lets assume: 9 HRs
    2) CATS_APPR_LITE - > Time sheet approval -> Approved 9 Hrs
    3) CAT9 -> CATS data transfer to cost object(PM order) -> During this transaction, system does calculate the amount needs to be tranferred based on price maintained in KP26 and hours booked. Lets say KP26 price is $100. That means controlling document will be generated for amount $900.
    Note - As per system configuration, exchange rate type will always be P whenever CATS posting will happen and controlling document gets generated. That means, currency conversion will take place based on the exchange rates maintained for type P.
    So as per business requirement, we have done an enhancement to the existing CATS process:
    Price is manually determined at the time of CAT2 and same will be considered till the controlling document is generated. So, no price determination during CAT9. Therefore the strategy says it is a manual determiination of price and the Exchange rate type is determined as "M" and thats an issue because we do want to pass manual price but we want Exchange rate type as "P" as well.
    Is there any way out or settings availabe in SAP or any user exit or an enhancement to achieve this functionality?
    Thanks,
    Aby

    Hi Aby,
    I believe these notes contain good information for this case:
    1073979 (which I think is already in your system and therefore this behavior).
    and
    691613 (which explains the strategies)
    Also, please check the entry you have defined in the transaction OKEV.
    There, the system will make the translation depending on the
    exchange rate defined.
    I hope this helps. 
    Regards,
    Lucas

  • Exchange Rate Type default different from M for a company code

    Dear SAP guru,
    Would you shed some light on this?
    How would we be able to default/assign a different exchange rate type from M at a company code level?
    I have a company code - finance company - that every foreign currenty transaction needs to be translated using different exchange rate type (i.e. daily hedge rate) than other operating companies.
    The OB22 screen makes it appear as M rate is specificied as 1st currency in company code, but grayed out and not able to change.
    Please help me with your expertise on this.
    Kind regards
    taro

    Hi,
    ExRateType is hardcoded in
    Main Program     SAPL0F03
    Source code of   L0F03I01
    *------- Daten zur ersten Hauswährung -
      rfcu4-curtp = '10'.
      rfcu4-bwer1 = '0'.                                        "AT 23039
      rfcu4-kurst = 'M'.               <<<<<
      rfcu4-cursr = '1'.
      rfcu4-curdt = '3'.
    The reason why the assignment of exchange rate type M to the first company code currency is a historical reason. A lot of coding within the SAP system is directly developed under the prerequisite that the exchange rate type for the first company code currency is M.
    As you described you want to setup several company codes in one client that all have the same first company code currency but should use different exchange rates. To solve that issue there are 2 ways available:
    The first way is that you use the functionality to assign an exchange rate type to a document type. That would mean a lot of work because in that case you would have to define all document types seperatly for
    every company code.
    The second possible solution is that you use different names for the fist company code currency.
    That means for example that you name the first company code currency in company code 0001 USD and in company code 0002 US1. So you can use different exchange rates for the same currency.because in that examle USD and US1 are only different names for the same currency. Using this approach you can have different exchange rates for different companies with the same company code currency by setting only different names even though the exchange rate type M is fix asigend to the first company code currency.
    Best Regards,
    Gladys xing

  • Exchange Rate Type not working during plan assessment in T Code KSUB

    Hello Experts
    We had different exchange rate types created for different plan versions. We had Exchange Rate Type Z1 for Plan Version 01.
    We had maintained the same in Planning settings for the fiscal year 2011.
    We had created a new plan assessment cycle with version 1.
    Now when we execute assessment cycle it is not using the exchange rate from 01/01/2011. Instead it is selecting the rate from 01/01/2010.
    Is there something wrong when we copied fiscal year 2011 from 2010 for version 01.
    Request your inputs and help on this.
    Thanks
    Satya Alapati

    Hi Ajay
    Thanks for the information.
    We had not maintained the value date for any of our versions since we keep changing the rates for every period and wish to have the system pick the latest rate for the period.
    It has been the case in earlier years also.
    Thanks
    Satya

  • Sequence of condition types in MIRO for import P.O

    Hi!
    In case of import P.O. scenario, while capturing customs duties in MIRO, the sequence of condition types is not as defined in P.O. ( no GR bassed IV, MIRO before MIGO).
    For example, sequence defined in P.O :
                                                               1. Basic duty
                                                               2. CVD
                                                               3. Spl. Addl. Cess
                                                               4. E.Cess on CVD
                                                               5. S&H E.Cess on CVD
                                                               6. Customs E.Cess   etc...
    While capturing the customs duties in MIRO, after entering the P.O. no, the system should propose the same sequence of condition types as defined above (i.e., P.O). But it is proposing in the following sequence.
                                                               1. S&H E.Cess on CVD
                                                               2. Basic duty
                                                               3. E.Cess on CVD
                                                               4. CVD
                                                               5. Customs E.Cess
                                                               6. Spl. Addl. Cess
    The sequence of condtion types defined in pricing procedure is also same as shown in P.O.
    Can any one suggest the reason for this issue. Your valid suggestions will be highly appriciated.
    Thanks & Regards
    Gopi Chand.

    Hi VS!
    Thanks for the reply.
    Actually I have already verified the pricing procedure for this concern and it was not maintained like that. For every condition type, different step with counter zero was mentioned.
    10 - 0 - BCD
    20 - 0 - CVD
    30 - 0 - Ecess on CVD etc..
    Even then the problem is coming.
    Can you please suggest any other solution.
    Thanks & Regards,
    Gopi Chand.

  • Alternate Exchange Rate Type Not Picked while converting from Document Currency to Group Currency

    Hello Gurus,
    We have setup an alternate Exchange Rate type MNB for rate M for the postings happening in Hungary. Local currency is HUF. Group currency is USD.
    If the document currency is, lets say, EUR, latest MNB rate is correctly picked up (EUR to HUF) and postings are correctly converted into local currency (HUF).
    Although, for the same document, when a group currency is being calculated (EUR to USD), exchange rate type M is being picked up. Same happens if  document currency is HUF. Even then, the conversion is based on exchange rate type M.
    Is this a normal SAP behavior? How to prevent/correct this? This is also throwing off balances when we check in FAGLB03 or BSEG values in local and group currencies. In OB22, we have local currency1 and local currency 2 setup with exchange rate type M and we may not want to make any changes there as it is setup at global level.
    Do we need to run any valuations after the fact? if so, how?
    Thank you for your inputs in advance.
    Regards,
    Sagar

    Hi,
    You mentioned that "in OB22, we have local currency1 and local currency 2 setup with exchange rate type M". Then, I'm wondering how MNB is picked up for the first local curr. conversion to HUF? It should be 'M' instead. There must be some settings in your instance for such behavior. Can you check that?
    Actually, Group Curr. conversion happens with the rate defined for 2nd Loc.Curr.in OB22 which is 'M' in your case. Therefore, all the transactions are converted with M instead of MNB.
    Since you can't change OB22 per global co.policy, the exch.rate defined in OBA7 will overrule OB22. However, you've to make sure it's set up for all doc.types which are affected and posted in different curr. than HUF.
    As a workaround, another thought would be to maintain the same conversion rate for both exch.rate types MNB & M, for eg. HUF > USD rate is the same both exch.rate type MNB & M. This way, you ensure all transactions are posted with correct exch.rate irrespective of whatever rate type is used.
    From business, & global org. perspective, I'm sure they are sending the 'M' exch.rates to all their sister concerns monthly, so they would like to consolidate results as per standard rate in their system. Then, why ,as a local company, would you like to fiddle with standard process? It's a management decision, please run them through again before going ahead.
    Thanks,
    Nirav

  • Exchange Rate Type upon PO/PR

    Hi Experts,
    Is there a config to default exchange rate type upon PO/PR creation? I was told that by default it will read type 'M' and I'll be the happiest man if it can link to type 'M'.
    In my case, it reads from other type i.e. '2004'. Thus, I was wondering how does it reads and is it based on configuration? Thanks in advance.

    I suggest you to check global company code(mentioned in po/pr) setting
    for exchange rates  in spro financial accounting ??.
    Whether new po's / pr's were created from existing or old documents ?
    Edited by: Jeyakanthan A on Dec 4, 2011 1:33 AM

  • Selling Exchange rate type is not picking while billing

    Hi,
    We have maintained Exchange rate type B for selling and the same was assigned in customer master as well as the RV document type. While raising sale order system is picking the B rate from OB08 table, but at the time of billing system is taking the M rate. Where do i set a control to pickup only B rate? Can anybody help me on this.
    govind.

    Hi,
    Ideally at the time of billing, exchange rate type is picked up from the document type (RV in your case). However if the rate is picked up for standard exchange rate type, check if there is user exit being called for exchange rate type.
    Thanks,
    Aman

Maybe you are looking for

  • Problems in migration to Ecc 6.0

    Good Morning, Working with ECC 6.0 SAP version we have problems with the DMS likns to customer objects. The standar objects like EQUI are saved in the system but not the customer objects, like project definition. I have debugging the customer program

  • Xfa.host.messageBox or app.alert not working some machines

    Hi, We've a PDF form with alert messages on a button click. We've written a function in a script object which is called on button click. This PDF is working fine on most of the machines but does not work few machines. On all machines, we have same ad

  • Nokia 2730c Is it upgradeable to any new S40 OS??

    New OS on X2,C2,C2-03 looks better. I want that look??? Anybody can help?

  • Oracle DB 10g XE Database Home Page login failure

    Hi, I've just successfully installed Oracle DB 10g XE on WIN2KPRO SP4. I can connect to the Oracle DB using Toad for Oracle. So the System user and password entered during setup work. However if I open the DB home page and try to log in with the same

  • Avoiding resizing after importing video files

    Hello, I'd like to keep the video files I import from my hard in their original size format to avoid quality loss, however I'm unable to locate an option that prevents iMovie from resizing them automatically. Does such an option exist? If it's imposs