Regarding baseline date

i want to show the base line date is unchangeble.how can i do that , for the base line date where can i supress.one of our friends told me regarding baseline date, you can supress by selecting FSG, or validations and parameter ID.
but i have tried the above scenarios , it is not showing  any field in account groups,postingkeys and field status groups. and in the validations also it is not showing any baseline date. and in the parameter id it is not showing any parameter id for the baselind date.if i supress user cannot change that date.
please help me

Reddy,
Follow the menu path for validation
Spro-FA-GLA-Business Transactions-General Ledger posing-make check and document settings-validation for accounting documents.
In this you can select line items and in prerequisite step you can select Baseline Date, which is in almost down in the column, give the baseline date table and give the condition as you require.  Make active callup point.
i hope it will work.
If it is useful award points.
sd/-
Sreenivasulu.P

Similar Messages

  • Regarding MIRO baseline date in payment tab

    Hi All,
    T-code: MIRO
    Input invoice date: 'xxxxxxxxxx', posting date:  'xxxxxxxxxx', PO# 'xxxxxxxxxx' and then press ENTER
    After pressing ENTER, can you do some coding to the user exit or field exit whatever in order to populate the GR date (i.e.  'xxxxxxxxxx') in baseline date field but WITHOUT pressing the "Payment" tab?
    Here i am using 4.6c version...
    please help me...

    hi,
    check these xits.
    Transaction Code - MIRO                     Enter Invoice
    Enhancement/ Business Add-in            Description
    Enhancement
    LMR1M001                                User exits in Logistics Invoice Verification
    LMR1M002                                Account grouping for GR/IR account maintenance
    LMR1M004                                Logistics Invoice Verification: item text for follow-on docs
    LMR1M005                                Logistics Inv. Verification: Release Parked Doc. for Posting
    MRMN0001                                Message output and creation: Logistics Invoice Verification
      Business Add-in
    INVOICE_UPDATE                          Business Add-In: Logistics Invoice Verification

  • Baseline Date Issue

    Dear Experts,
    I am facing a peculiar problem. In the payment terms configuration i have mentioned Posting Date as the baseline date. The invoice is created in our company when the goods are dispatched. At this point only the invoice is made and accounting/release to accounting is not done. Later, when the Bill of Lading comes back to us the accounting document is created. Now the system is expected to take the later (accounting) date as the baseline date but it is taking the invoice creation date as the baseline date. Please suggest a solution.
    Warm Regards,
    Mukesh

    In export sales, this situation would be there predominently, where the Billing Date and Bill of Lading date differs and client insists that actual sales should be considered only based on Bill of Lading Date.
    Since you already set the Posting Block as per your original post, whenever user tries to release the billing document via VF02, you can populate two fields
    Bill of Lading Number and
    Bill of Lading Date
    via Function Module EXIT_SAPLV60B_001 in include ZXVVFU01 and whatever date user is keying in, that should be your posting date.  This means, irrespective of your billing date, actual FI postings (sales) will happen only based on the date whatever user enters.   If need, you can also add couple of more fields depending upon clients' requirement.
    G. Lakshmipathi

  • Payment terms - Baseline date calculation.

    Hi
    In payment terms configuration, we have option "No Default" for determining Base line date.
    If we have payment terms with above configuration.......
    In Fi, Baseline field will be blank while posing Customer Invoice, in which case We can enter baseline date manually. However If Invoice is generated from SD-billing document, we dont have any field "Baseline date" while posting billing doc. In such case how system determines Baseline date. When I checked few billing documents, Baseline date is defaulted with BIlling date even "No default" option is selected.
    Is there any configuration in SD that prompts this action. or is it always billing date is defaulted ?
    Please clarify

    Hi !! Madhu,
    There is a way, but not exactly what u require! You can check while maintaining the condition records in t.code VK12, observe the last two columns available, one is called a 'Fixed Value date' & the other is called 'Add Val Days'.
    If you make any entry in the field 'Fixed Value date' this will be the date from which the payment terms start taking effects. Or if you make an entry in Add Val Days' in this case the payment terms start taking effect from billing date + the no. of days mentioned in this column.
    You cannot make a entry in both 'fixed value date' & 'Add Val date'  fields at one time.
    Give your feedback if this has worked for you.
    Regards,
    PATHIK

  • Debit memo(DR doc type) baseline date exceding the payment term days

    Hi All
    For debit memo I am facing a issue where my baseline date for a customer is showing more then the days specified in his(customer's) payment terms.
    sales document category is DR and order is created for some customer xyz and payment terms of that customer is showing 0% UP TO 15 DAYS. But when I check it in FBL5n the Net due dt for that order is showing 180 + 15 = 195days.
    What can be the reason, is it due to some enhancement or some routine or what , I am not able to figure out from where these days are coming for. I have checked MV45AFZZ , RV60AFZA and other exit s, I couldnt find any code which shows these added 180 days..
    Guide me in finding out the source ot this, <removed by moderator>.
    Thanks in Advance
    Regards
    Amit
    Edited by: Thomas Zloch on Sep 30, 2011 3:46 PM

    HI,
    You may need to check the copy control settings between the debit memo request and sales document in transaction code VTAA.
    Select the target document type and source document type, and click on the details (header level). Check the routine that is assigned for the field copying requirements for transfering business data.
    The routine assigned may be copying the base line date from the source document. You may need to assign other routine or you may need to develop your own routine to resolve your issue.
    Regards,

  • Baseline date in Accounting document changed after creation of Invoice List

    Hi all,
    1) User Requirement:-
    Creation of Invoice document(using VF01), Transfer u201CGoods Issue Dateu201D to FI accounting as a Baseline date instead of Invoice creation date.
    To meet the above requirement I did enhancement name: SDVFX008 user exit: EXIT_SAPLV60B_008.
    Its working fine and transfered goods issue date to Accounting(as baseline date) insted of  invoice date.
    2) Problem:-
    After Creation of Invoice List (VF21) system again overwriting baseline date iwith invoice list date.
    Does anyone know how to Stop overwriting baseline date in accounting while creation of invoice list.
    Thanks & Regards
    Sudheer

    Hi Valerie,
    do you recall the User Exit?
    Thanks

  • BaseLine date different from Terms Of Payment Date

    Hi,
    My client posted 3 documents dated 23.12.2009,17.12.2009,14.12.2009  respectively. The terms of payment has been set to accept document date as default for the baseline date. This means that the baseline dates for the  documents should be same as 23.12.2009,17.12.2009,14.12.2009  respectively. However, the system has set 31.12.2009 as baseline dates for all MIRO documents. I have already checked Terms Of Payment  ,Vendor Master and the posted documents.
    Can anyone please provide any clues to this problem?
    Thanks In Advance
    Regards,
    Payal Saxena

    Hi Payal
    Request you to check settings for PT in OBB8
    Also, refer to this thread - Baseline date in payment terms_reply the question for FI experts
    If the problem still persists, you will require a user exit.
    Rgds,
    Zub

  • User exit / substiution /  badi for changing baseline date

    Dear Experts ,
                           I have a requirement to change the base line date of residual document created in F-28 / F-32 to the base line date of original document getting partially cleared .
    I have explored the option of substitution but it doesnt work as field ZBLDT is not available for substitution there .
    Please let me know any BADI / Exit which can perform this change of baseline date .
    thanks in advance

    Hi Milind,
    Following are the user-exits for F-32 :
    RFAVIS01            Customer Exit for Changing Payment Advice Segment Text
    RFEPOS00            Line item display: Checking of selection conditions
    RFKORIEX            Automatic correspondence
    SAPLF051            Workflow for FI (pre-capture, release for payment)
    F050S001            FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002            FIDCC1: Change IDoc/do not send
    F050S003            FIDCC2: Change IDoc/do not send
    F050S004            FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
    F050S005            FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
    F050S006            FI Outgoing IDoc: Reset Clearing in FI Document
    F050S007            FIDCCH Outbound: Influence on IDoc for Document Change
    F180A001            Balance Sheet Adjustment
    FARC0002            Additional Checks for Archiving MM Vendor Master Data
    I hope this will help you.
    Regards,
    Nitin.

  • Baseline Date as the Document Date

    Hi,
    I have a query on Payment Terms which we maintain in the Posting Parameters->Postings Tab page in RE-FX Lease Out Contract.
    I maintain a payment term for 10 days in the RE-FX Contract.
    I have maintained a Condition which is due on 1st of every month with a monthly frequency.
    When i simulate the contract for planned Cash Flow, it shows me the conditions which are due to be posted on 1st of every month. Now, here is a scenario wherein I am unable to post the conditions through Periodic Posting (RERAPP) on 1st and i eventually carry out the Posting on 16th of that month. Hence I maintain Document Date and Posting date in the T Code RERAPP (Periodic Posting) as 16th of that month.
    Now when i open the Customer Line Items in FBL5N, i find that the Document Date and Posting date to be 16th whereas the Baseline date to be 1st of that month. This makes the calculation of Due Date totally wrong since the system takes 1st of that month as Baseline Date and adds Payment Term days (10 days) to it and shows 11th of that month as the Net due date (which instead should have been 26th of that month.
    I tried changing the definition of Baseline Date in the Payment Terms definition to Document Date but it still did not bring the desired effect.
    Pankaj

    Hi,
    I face similar problem but not involving TRM.
    I've payment term set-up in OBB8 and stating default baseline date = document date.
    But in FBL5N system is always retrieving posting date as baseline date. Is there any other setting prevailing over payment term definition?
    Regards,
    Baptiste

  • Baseline date for payment due date.

    Hi,
    In FB60 and Miro, Baseline date for calculating due date for payment is taken as default as document date, as per setting in payment terms. But I want to take this date as date of GR/SE. Can we do this. I also want to make it gray and dont want user to change it. Please suggest how to do it.

    Hi
    go through the link answered by me.
    Re: Substitution - Baseline Date to be replaced by the Goods Receipt date
    the Goods receipt date can be defaulted as Baseline Date.
    tell your ABAP consultant to check the BADI and do the necessary.
    regards
    venkat

  • How to get default baseline date in a payment terms

    Hi,
    We have around 160 payment terms used in our system. We want to get the default baseline date for all these payment terms. Going to each individual payment terms and getting the default baseline date is a cumbersome job.
    Is there any easy way to get the default baseline date for each of the payment terms, like from any table or anything else. I have tried table T052. But it does not have default baseline date.
    Please help.
    Regards
    B.Mohanty

    Hello Bibhu,
    default baseline date is a customizing setting in paymentterms. That's the only way.
    I have no idea why TC lsmw is recommended, definetely the wrong way.
    Best regards
      Horst

  • Posting date as Baseline Date in Residual item

    Hello,
    While clearing a document with Residual Clearing method through F-28 system is automatically proposing end of the month as Baseline Date for the residual item (newly created item for the balance amount), whereas we want it to be the posting/document date but not the monthend as proposed by the system. Eventhough we have selected the option for default baseline date as posting date/document date in Payment Terms, system is proposing monthend date as baseline date for the residual item. I have set payment terms in customer master record as 0001 (immediate payment).
    Because of the settings made for default baseline date in payment terms (SPRO/AR-AP) system is proposing document date as baseline date for new documents being posted, but we are facing problem only in case of residual items (new item created for the balance amount while doing residual clearing).
    Please let me know the procedure to change the settings, so that posting/document date will become default baseline date for the newly created open item while doing residual clearing.
    Thanks in Advance

    Hi,
    Try to take a look the setting of the following transaction,
    IMG> FA> AR & AP> Business Transactions> Incoming Payments> Manual Incoming Payments> Define Tolerances
    See what has been set for payment term for Residual Items.
    Regards,

  • BADI MRM_PAYMENT_TERMS - Baseline date

    Hi All,
    The requirment I have is to automatically populate the Baseline date based on the GR posting date and Invoice posting date.
    While creation of the Invoice in MIRO,
           1) If the GR posting date is greater than the Invoice posting date then the Baseline date should be populated with the GR posting date.
           2) If the Invoice posting date is greater than the GR posting date then the Baseline date date should be populated with the Invoice posting date.
    This logic I have implemented in  the BADI MRM_PAYMENT_TERMS which works as expected.
    But the standard calculation of 'DUE ON' date, Payment terms, Cash discount days are not performing according to the standard functionality and these values do not get displayed.
    Why is this getting affected?
    Also, please suggest if there is any other way to achieve this requirement without any deviation from the standard functionality.
    Below is the code that I have implemented in the BADI.
    *----Defining the structure for work area for EKBE table data fetch
      TYPES: BEGIN OF TY_EKBE,
              EBELN  TYPE  EBELN,
              EBELP  TYPE  EBELP,
              BELNR  TYPE  MBLNR,
              BEWTP  TYPE  BEWTP,
              BWART  TYPE  BWART,
              BUDAT  TYPE  BUDAT,
             END OF TY_EKBE.
    *----Defining the work areas
      DATA: WA_EKBE  TYPE                   TY_EKBE,          "Work area for History per Purchasing Document table
            WA_DRSEG TYPE LINE OF           MMCR_TDRSEG.      "Work area for Invoice doc items
    *----Checking if the Company code is IBTG
      IF I_RBKPV-BUKRS = 'IBTG'.
    *----Selecting data from EKBE table to fetch the latest GR posting date
        SELECT EBELN
               EBELP
               BELNR
               BEWTP
               BWART
               BUDAT
        INTO WA_EKBE
        FROM EKBE
        FOR ALL ENTRIES IN TI_DRSEG
        WHERE EBELN = TI_DRSEG-EBELN
        AND   BEWTP = 'E'
        AND   BWART = '101'.
        ENDSELECT.
    *----Looping at Invoice Doc. Items table into its work area
        LOOP AT TI_DRSEG INTO WA_DRSEG.
          IF WA_EKBE-BUDAT > WA_DRSEG-BUDAT.                 "If GR posting date is greater than invoice date
            E_ZFBDT = WA_EKBE-BUDAT.                         "Assigning the GR date to Baseline date
          ELSEIF WA_EKBE-BUDAT < WA_DRSEG-BUDAT.             "If Invoice date is greater than GR date
            E_ZFBDT = WA_DRSEG-BUDAT.                        "Assigning the Invoice date to Baseline date
          ELSEIF WA_EKBE-BUDAT = WA_DRSEG-BUDAT.             "If Invoice date is Equal to GR date
            E_ZFBDT = WA_DRSEG-BUDAT.                        "Assigning the Invoice date to Baseline date
          ENDIF.
        ENDLOOP.
      ENDIF.

    Hi,
    if you go to se18 and display badi MRM_PAYMENT_TERMS,
    in "Interface" tab if you double click on "Example implementation class"  CL_EXM_IM_MRM_PAYMENT_TERMS
    and then in class interface CL_EXM_IM_MRM_PAYMENT_TERMS, if you display the code of IF_EX_MRM_PAYMENT_TERMS~PAYMENT_TERMS_SET you will find three examples:
    METHOD if_ex_mrm_payment_terms~payment_terms_set .
    *--- fill all export-parameter ----------------------------------------*
      e_zfbdt = i_rbkpv-zfbdt.
      e_zbd1t = i_rbkpv-zbd1t.
      e_zbd1p = i_rbkpv-zbd1p.
      e_zbd2t = i_rbkpv-zbd2t.
      e_zbd2p = i_rbkpv-zbd2p.
      e_zbd3t = i_rbkpv-zbd3t.
      e_zlspr = i_rbkpv-zlspr.
    *** Example 1: Setting ZFBDT depending on goods receive
      DATA: h_drseg TYPE mmcr_drseg,
            h_budat TYPE mmcr_ekbe-budat.
      TYPES: BEGIN OF x_datum ,
               budat LIKE h_budat,
             END OF x_datum.
      TYPES: BEGIN OF x_ekbe_gelesen,
               ebeln TYPE ekbe-ebeln,
               ebelp TYPE mmcr_ekbe-ebelp,
             END OF x_ekbe_gelesen.
      DATA: h_ekbe_gelesen  TYPE STANDARD TABLE OF x_ekbe_gelesen,
            h1_ekbe_gelesen TYPE x_ekbe_gelesen.
      DATA: h_datum TYPE STANDARD TABLE OF x_datum,
            h1_datum TYPE x_datum,
            h_ebeln LIKE h_drseg-ebeln,
            h_ebelp LIKE h_drseg-ebelp.
      LOOP AT ti_drseg INTO h_drseg WHERE selkz = 'X'.
        SELECT budat FROM ekbe INTO h_budat WHERE
             ebeln = h_drseg-ebeln  AND
             ebelp = h_drseg-ebelp  AND
             lfbnr = h_drseg-lfbnr  AND
             lfgja = h_drseg-lfgja  AND
             lfpos = h_drseg-lfpos  AND
             vgabe = '1'.
          IF sy-subrc EQ 0.
            MOVE h_budat TO h1_datum-budat.
            APPEND h1_datum TO h_datum.
          ENDIF.
        ENDSELECT.
      ENDLOOP.
      SORT h_datum DESCENDING.
      READ TABLE h_datum INDEX 1 INTO e_zfbdt.
    *** Example 2: calculate best payment terms based on manual settings
      DATA: h2_drseg TYPE mmcr_drseg,
            h2_zbd1p TYPE mrm_rbkpv-zbd1p,
            h2_zbd1t TYPE mrm_rbkpv-zbd1t,
            h2_zbd2p TYPE mrm_rbkpv-zbd2p,
            h2_zbd2t TYPE mrm_rbkpv-zbd2t,
            h2_zbd3t TYPE mrm_rbkpv-zbd3t,
            h21_zbd1p TYPE mrm_rbkpv-zbd1p,
            h21_zbd1t TYPE mrm_rbkpv-zbd1t,
            h21_zbd2p TYPE mrm_rbkpv-zbd2p,
            h21_zbd2t TYPE mrm_rbkpv-zbd2t,
            h21_zbd3t TYPE mrm_rbkpv-zbd3t.
      LOOP AT ti_drseg INTO h2_drseg WHERE selkz = 'X'.
        SELECT zbd1p zbd1t zbd2p zbd2t zbd3t
          FROM ekko
          INTO (h2_zbd1p, h2_zbd1t, h2_zbd2p, h2_zbd2t, h2_zbd3t)
          WHERE ebeln = h2_drseg-ebeln.
          IF sy-subrc EQ 0.
            IF h2_zbd1p GT h21_zbd1p.
              MOVE h2_zbd1p TO h21_zbd1p.
              MOVE h2_zbd1t TO h21_zbd1t.
              MOVE h2_zbd2p TO h21_zbd2p.
              MOVE h2_zbd2t TO h21_zbd2t.
              MOVE h2_zbd3t TO h21_zbd3t.
            ENDIF.
          ENDIF.
        ENDSELECT.
      ENDLOOP.
      IF h21_zbd1p GT i_rbkpv-zbd1p.
        MOVE h21_zbd1p TO e_zbd1p.
        MOVE h21_zbd1t TO e_zbd1t.
        MOVE h21_zbd2p TO e_zbd2p.
        MOVE h21_zbd2t TO e_zbd2t.
        MOVE h21_zbd3t TO e_zbd3t.
      ENDIF.
    *** Example 3: Setting ZLSPR depending on currency
      CONSTANTS: c_zlspr_r VALUE 'R',
                 c_waers_itl TYPE waers VALUE 'ITL'.
      IF i_rbkpv-waers = c_waers_itl.
        MOVE c_zlspr_r TO e_zlspr.
      ENDIF.
    ENDMETHOD.
    your case is similar to the first example.
    Best regards.

  • Invoice verification Invoice date,Posting date and Baseline Date

    Hi Sap Gurus
    Pls Tell Me in detail what Dates should be entered at MIRO transaction,
    Invoice date,Posting date and Baseline Date
    i presumed that the date on the Invoice slip will be Invoice date,
    But in the Invoice the Date is very long back, say a month Older,
    the month of Posting as Posting date, but any posting Date made in MIRO will be Paid after 2 or 3 months so in this case what should be the Posting date.
    at Base line date in the present company Senario the Discount on Vendor payment is literally valid for all the time , say
    In Invoice if the condition is 10% discount if paid in 30 days is given.
    but in actual sense the Vendor is paid 10% less even if he is paid after 4 or 6 months also, so in this case what should be the Entry in Baseline date
    another senario is the vendor has sent only one Invoice for 2 POs how can this be accomadated in SAP
    Pls suggest its Urgent,
    Age may have a Bar, But Points No Bar
    Thanks and Regards
    Sathish

    Hi
    LIV is nothing but You are getting Invoice from the Vendor for your PO   and GR.....and you are checking the Invoice for Price, Qty,Amount etc. by refering the PO  and posting the Invoice...
    Invoice Date : 
               The date of Vendor' Invoice...ie) Date at which the vendor Raised the invoice for his supply against your PO...
    Posting Date :
       The Date at which you actually Verifying Vendor's Invoice and doing the Posting...
    base line date :
        Generally the Posting Date...
    The Imp. of Baseline date is for eg)
    If in the Payment Terms if some conditions are maintained like say
    10% Discount for Payment With in 30 days, if
    PO created on 01.11.2007.
    GR done at 10.11.2007.
    Invoice slip Received at 30.11.2007 but having the Date on it as 20.11.2007...
    So as per your terms you will get 10% Discount if you make the payment on or  20.12.07....
    Here if you keep  inv. Date: 20.11.2007  and Posting Date : 30.11.2007  and Baseline Date as  30.11.2007 ( you cannot maintain baseline date earlier than  Posting date)....even though as per terms the you are  eligible for discount if you make the payment on or before 20.11.2007.....as per the system you are still eligible to get the Discount if you make payment on or 30.12.2007( since you have maintained baseline date as 30.11.2007)...
    this way Baseline date is Importane...
    Generally we use to maintain always Posting Date as Baseline date....
    It is advantageous..
    Reward if useful
    regards
    S.Baskaran

  • Problem with baseline date of Credit memo

    Hello all
    The issue is like this: if I am posting a credit memo using TCode- FV75 then then the baseline date is picked automatically as the document date but if I use TCode: FV70 then the baseline date is not picked.
    Can anyone please tell as what is causing this issue :
    Thanks in advance.
    Regards.

    Dear all,
    A credit Memo without an Invoice Reference is always due on the
    Baseline Date (the Exceptions to this are Credit Memos which have an
    explicitly-stated Value Date)" > this Logic was introduced starting
    from Release 3.1I.
    Summary:
    1. Credit Memo with Invoice Reference have the same Terms of Payment
       and Baseline Date as the Invoice.
    2. For the Credit Memo without Reference to an Invoice, there are 2
       methods available for choosing the due Date :
    a) The Due Date for Net Payment (RFPOS-FAEDT) is identical to the
       Baseline Date for Payment (BSEG-ZFBDT). The Period for Net Term or
       the Term of Payment is not taken into Account. This is the Default.
    b) Or the Credit Memo is due based on the Payment Terms. For this,
       you must enter the Indicator "V" in the Credit Memo Field BSEG-REBZG
       "Invoice Ref", in addition to the specified Payment Method.
       You can modify this Field for the Credit Memos already posted.
       => the above Details are documented in the Help F1 behind the
       "Invoice Ref" Field.
    Manual filling of the Field can take place during the Entry of the
    Credit Memo, or in a Document Change Transaction:
    Run transaction FB02 to call up the Credit Memos. Drill down
    to Customer Line Item. Here, you should be able to see the Field
    "Invoice ref.' (BSEG-REBZG). Place a 'V' in this Field. With this,
    the Credit Memo is due based on the Payment Terms.
    I hope this helps.
    Mauri

Maybe you are looking for

  • SCCM Task Sequence no longer installs SCCM Client

    I am using SCCM 2007 R3 with SP2 and MDT 2010 My task sequences were all working fine until one of the other SCCM admins "Synced all sites" by transferring the site settings of one site to all the other sites.  How this broke OSD I don't know. At thi

  • CC Desktop is hosed

    OS: Windows 7 Professional SP1 (32-bit) Late last week CC was working well: PS installed paid and several additional apps installed for free trial. Earlier this evening after restarting my system a pop-up appeared indicating an update was available f

  • HT4589 How can I share a video shot at 60 fps.  Quick time error 0 and 50 occur for  DVD

    Change camera settings to 60 fps and now program will not share to DVD.  Getting quicktime error 0 for DVD and error 50 on master file.  Seems Quicktime cannot handle 60 fps. Is there a way I can solve this problem?  Camera setting will go back to 30

  • Sharepoint Hosting Vanity URL and ADFS 3.0

    Friends, i'm sure you got my question from the subject of this topic. to clarify this we are in progress of deploying a hosted model of sharepoint 2013 with vanity urls and i'm trying to integrate SP 2013 with adfs 3.0 we are planning to use vanity u

  • My Mac X10.5.8 PCG5. Can't open Firefox 4 'not supported on this architecture' why not?

    When I tried to open Firefox 4 a dialogue box opened stating "Can't open the application Firefox because it is not supported on this architecture"