Statistics Currency Error while posting Sales Order (No: V1453)

Hi Sappers,
I am in process of making a company in SAP ERP SD - IDES, and while posting Sales Order, after I input Sold to Party, PO no, Del Plant and Incoterms and I press ENTER: The error comes up as:
Statistics: The currency from in INR for date 25.11.2011 could not be determined.
Kindly suggest a possible solution.
Thanks
Rahul Tikku

Hi,
Just go to "OBD2", select the Accounts group of your customer and "Double Click" on it, then "Double  cliick" on "Sales Data" > Further goto,  "Sales" and check if "Currency" field is suppressed. if so then change it to required or optional Entry. save and update you customer master in XD02. Then try your process.
Reagrds
DSR

Similar Messages

  • Error while processing sales order as factory calendar missing.

    "factory calendar missing or error in factory calendar".iam getting this error while processing sales order even though i have assigned it to shipping point and plant and sales org.

    Hi Malik, How are you? I'm sorry to trouble you,
                   Let me introduce, I'm Daniel, and I saw your fantastic asnwer in
    the topic "How to update Factory Calendar in SRM", and might I have the same
    problem. It's with the "factory calendar".
    In transaction va02 when I choose a Delivery Date, and I sent it to process, as
    a result in the "shipping tab" it calculated to the first item one date, and to
    the rest one date different.  I don't know What it happen?
    I debugged the program and I saw that to the first item use to calculate the
    date is the function  'APO_SCHEDULING', and to the rest item use
    'SD_SCHEDULING', and until here I come.
    How can I do to what the dates calculated are the same? or What would be the
    problem?
    I need the dates calculated are equal.
    I looked at it's using two "factory calendar" which are "J4" and "C2". Is this
    correct?
    Thanks In Advance,
    My best regards,

  • Error while create sales order

    Hi,
    Please help.
    I am facing error while create sales order.
    No item category available (Table T184 OR VERP  )
    Message no. V1320
    Diagnosis
    No item category could be determined for the combination OR VERP .
    System Response
    The system does not allow further processing of this item.
    Procedure
    Check the entries in table T184 by means of which item category determination is controlled.
    If you do not have the authorization to do this yourself, contact your system administrator.

    Hi,
    Check in spro whether Item categorygroup VERP is assigned to sales document type.if not assign.
    Path
    SPRO-SD-sales-sales douments-sales document item-assign item categories.

  • Error while posting sales f-22

    Error while posting sales F-22
    Cost center 1000/150020 is Blocked againest revenue postings on 03.11.2008

    Hi,
    In your document you have cost centre assigned on revenue line. You have to unlock it for posting revenues: go to KS02 - Control - and unlock the actual revenues flag.
    Regards,
    Eli

  • Commit error while transferring Sales order Document to GTS

    Hello,
    We faced a transfer error while transferring sales order document to GTS.
    When I debugged the code function /SAPSLL/API_6800_SYNCH is called. In this function, /SAPSLL/CUHD_MAINTAIN_SINGLE is called with parameter lv_no_commit = 'X'. When I checked why its value is 'X', I saw that if the RFC destination and the current system are the same, then lv_no_commit = 'X', (means if the R3 and the GTS are in the same server, same client.) In debug mode I set the value of lv_no_commit to space, and then it works. It creates the GTS document.
    We are also transferring billing documents and it works fine. When I checked what is the difference between transferring sales order document and transferring Billing document, I saw that in the transferring billing document there is another function is called /SAPSLL/API_6800_CSD_SYNCH, and it's calling parameters(in background, as seperate unit) are different from calling parameters of /SAPSLL/API_6800_SYNCH. You can see the difference below.
    For sales document transfer :
        CALL FUNCTION '/SAPSLL/API_6800_SYNCH'
          DESTINATION cs_transfer-rfc_dest
    For billing document transfer :
        CALL FUNCTION '/SAPSLL/API_6800_CSD_SYNCH'
          IN BACKGROUND TASK
          DESTINATION cs_transfer-rfc_dest
          AS SEPARATE UNIT
    So my question is, do you think is it a sap standard program error, or is there any suitable settings in the customizing or SM59 to fix this error?
    Thanks in advance
    Serhat
    Edited by: Serhat Dirihan on Jan 22, 2009 11:46 AM

    Dear Serhat,
    I don't think this is an RFC problem or an error. But you wrote:
    When I checked why its value is 'X', I saw that if the RFC destination and the current system are the same, then lv_no_commit = 'X', (means if the R3 and the GTS are in the same server, same client.)
    It is impossible to have GTS and R/3 on the same system and same client. At least the client should be different. So try to check why the call is performed like that.
    Balazs

  • Getting runtime error while doing sales order

    Hi,
    I am getting a runtime error while doing sales order.
    Error : SAPSQL_INVALID_FIELDNAME
    Kindly suggets....stuck up badly.
    cant do any transaction.
    Regards
    Kishan

    Hello,
    Check OSS Note#209847 and 310304
    Regards,
    Gauravjit.
    Reward points if the notes are helpful

  • Unable to block or throw credit limit message while posting Sales Order.

    Dear All,
    I hv created new customer and extended credit limit through FD32, assigned Risk Categeory and set the limit to 10,000/-.
    When i am posting Sale Order with 15,000 or more value, i am not getting any warning or error message while saving Sale Invoice. No block was set against delivery or billing in Sale Order.
    Kindly guide me, which step i am missing. FYI, customer dont hv any open item or credit exposure as of now becoz he was new customer.
    Regards,
    Venkat

    Option 1
    If your requirement is to go ahead with warning message and allow saving the sales document, maintain A in VOV8 for credit limit check.
    If you want to restrict creating sales order when credit limit exceeded maintain B in VOV8 for credit limit check.
    Option 2
    Now in OVA8 if you click on dynamic option. Make sure you satisfy these requirements
    The customer's credit exposure is split into a static part - open items, open billing, and delivery values - and a dynamic part, the open order value. The open order value includes all not yet or only partially delivered orders. The value is calculated based on the shipping date and the credit horizon you specify in the adjacent field. For the purposes of evaluating credit, you want the system to ignore all open orders that are due for delivery after the horizon date. The sum of the static and dynamic parts of the check may not exceed the credit limit.
    I would recommend with option 1, still if you want to go for option 2
    Then click on Static and make sure you also select open orders and open deliveries.
    This will happen if you select static
    The customer's credit exposure may not exceed the established credit limit. The credit exposure is the total combined value of the following:
    Open sales documents
    Open delivery documents
    Open billing documents
    Open items (accounts receivable)
    You can specify in the adjacent fields whether the system takes into account all open orders and all open deliveries.
    Regards
    Ravi.
    I am sorry i wont be able to add further input than this.
    Dont forget to reward points if you think it was successful

  • Run time error while creating sales order in VA01

    Dear all,
    In our develpment server(ecc 6.0),while creating sales order in VA01 for a sales area, when ever entering material number and quantity and press enter, it is giving error and taking to Runtime error long text showing syntax error in program RK2LSFOC
    application patch level for both production and development is same.
    can any one suggest the solution please
    Moderator message - Cross post locked
    Edited by: Rob Burbank on Jan 7, 2010 10:03 AM

    ths

  • Error while creating sales order

    while creating sales order for a particular plant there is error coming
    NO NUMBER RANGE FOR DOC TYPE ZOS1VXBAK-AUARTSILD
    PLANTXVBAK-VKBUR.
    Intailly I have check the no series we have internal no series for all plant,the 
    number series which start 195000001, only one plant the giving the above error, rest all plant it is as applicable above series.
    kindly guide me for the same.

    Hi Sanjay
    This is regarding number ranges defining and assigning tips which you can follow as below:
    Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for Sales Documents which are allowed for your New Sales Area.
    Number Ranges can be maintained Internally by the system, however it can be maintained externally also if you customize it accordingly.
    In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.
    Defining - The same can be reached through in IMG as : Sales & Distribution>Sales>Sales Document Header-->Define Number Ranges for Sales Documents.
    Here you provide the system a specific Number range as follows:
    Number range Key Start Number range End Number Range+Current Number
    For Example: If you want to propose the following Number Range
    *1     9000076000      9000076999      0
    The Current Number field will be kept zero as you are proposing new number range and no sales documents have been created on it , Obviously..
    *1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should not be there in the system as existing.
    If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in the system already, the system will throw a message that Interval already already exists. So choose a key that is unique, and which is not there in the system.
    Here , by making this , you are assigning a Key to a Number Range Series.
    All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order. For example: !1, ^A, BB,Z*,M2.........
    Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have already proposed as above.
    The Assigning Part is done as follows:
    The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in V0V8.
    This can also be reached in IMG by:
    Sales & Distribution>Sales>Sales Document Header-->Define Sales Document Types
    Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the Two Digit Number key in the Field- "Number range External Assignment"
    Besides this:
    If a new Shipping Point is created then Delivery Number ranges are required to be maintained.
    Similarly,
    If a new Plant is created then Billing Number Ranges are required to be maintained.
    Regards
    Naren

  • Error while raising sales order

    Hi all,
    I have created a make-to-order material with item category group and general item cetegory group 0001.
    While raising sales order for that material (make-to-order) item category TAK.
    I got a error stating that plant is not assigned to controlling area.
    can anyone help me out in this regards.

    hi pavan,
    pl check this on settlement rule :
    The settlement rule consists of the sender and the settlement distribution rule which includes the settlement receiving accounts, distribution factor, settlement type, and validity period. You can change the settlement rule manually.
    There are two possibilities for settling sales orders. You can either:
    Settle to a business segment
    In this case, the settlement rule is determined automatically. You can only use this method of settlement if CO-PA is activated.
    Settle to a general ledger account
    In this case, you enter the settlement rule and the general ledger account number manually in the sales order.
    To change the settlement rule, choose Edit ® Settlement rule.
    For more detailed information about settlements and especially about processing settlement rules, see the CO Cost Object Controlling documentation.
    Please consult your FI guy so that he can help you configure a settlement profile.
    regards
    sadhu kishore

  • Error while saving sales order

    Hi I am encountering below error message while saving sales order:
    Warehouse
    Specify export data in material master
    Then I go to material master to check foreign trade export tab, and I had maintained commodity code export group, country of origin and region of origin, what did I miss? Help.

    Hi,
    Check whether you have activated legal control data for the Sales Order type configuration in Foreign Trade.
    If the Order type is activated then the following error message can pop up unless you maintain in material master.
    See whether export legal control data is activated or not for the order type.
    In IMG Sales and Distribution>Foreign trade>Legal control section
    Regards,
    Saju.S

  • End of Valid Logistic Calender error while creating Sales Order

    Hi,
    While creating Sales order in VA01 the following error message comes for particular material code for a particular site only:
    24.01.2202 date comes after end of valid logistics calendar. (Please
    correct)
         Message no. 61062
    Can anyone suggest on the same.
    Regards
    Nilofer

    Hi,
    The input value given in Sales order is " Req Delivery date: 31.03.2012", but the error comes with the below date such as
    "24.01.2202 date comes after end of valid logistics calendar.(Please correct)"
    We also face one more error such as
    " Incorrect index structure for table XMVERF_POS/0000224110/000040 ".
    From where system is taking 24.01.2202 date?

  • Hi   error while creating  sales order

    hi
    i am getting 'not able to save' message while i am creating sales order.
    how should i proceed to know where is the problem???
    i tried debugging but it is taking lots of time, is there any other way i can know the reason for this error in standard code.
    there is no wrong data entry while creating sales order.
    i just want to know what are the ways to know where is the problem in the standard code.
    thanx
    rocky

    hi ,
    try too create a sales order after that check transaction code ST22 U WILL FIND AN SHORT DUMP  then check in the source code extract an pointer will be visible where the error is coming and it will also show the program name , please read the dump analysis care fully
    srinivas

  • Va01:errors during posting sales order

    Hi there,
    can anyone help me on the error log during posting sales order via va01? the checking of sales order is correct.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          2009.02.17 10:11:37
    Short dump has not been completely stored (too big)
    |Short text          |
    |    The current application triggered a termination with a short dump.  |
    |What happened?      |
    |    The current application program detected a situation which really   |
    |    should not occur. Therefore, a termination with a short dump was    |
    |    triggered on purpose by the key word MESSAGE (type X). |
    |What can you do?    |
    |    Note down which actions and inputs caused the error.   |
    |       |
    |       |
    |    To process the problem further, contact you SAP system |
    |    administrator.  |
    |       |
    |    Using Transaction ST22 for ABAP Dump Analysis, you can look         |
    |    at and manage termination messages, and you can also   |
    |    keep them for a long time.   |
    |Error analysis      |
    |    Short text of error message: |
    |    Maintain the current CRM release (table CRMPAROLTP)    |
    |       |
    |    Long text of error message:  |
    |     Diagnosis      |
    |         Various transfer errors occur when transferring SAP sales orders to         |
    |         CRM or there is no status update or the status update has errors            |
    |         when transferring from CRM to the SAP system. This is caused by an          |
    |         incorrect entry for the CRM release in the SAP table CRMPAROLTP, or         |
    |         no entry is maintained at all.       |
    |     System Response|
    |         To avoid data inconsistencies, this message causes a short dump.            |
    |     Procedure      |
    |         Maintain table CRMPAROLTP in your SAP system as is described in SAP         |
    |         Note 691710 and then repeat the process again.    |
    |     Procedure for System Administration      |
    |       |
    |    Technical information about the message:  |
    |    Message class....... "V3"    |
    |    Number.............. 302     |
    |    Variable 1.......... " "     |
    |    Variable 2.......... " "     |
    |    Variable 3.......... " "     |
    |    Variable 4.......... " "     |
    |How to correct the error         |
    |    Probably the only way to eliminate the error is to correct the program.          |
    |    -  |
    |       |
    |    If the error occures in a non-modified SAP program, you may be able to           |
    |    find an interim solution in an SAP Note.  |
    |    If you have access to SAP Notes, carry out a search with the following           |
    |    keywords:       |
    |       |
    |    "MESSAGE_TYPE_X" " "         |
    |    "SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"           |
    |    "BAPIDATEN_ERMITTELN"        |
    |       |
    |    If you cannot solve the problem yourself and want to send an error  |
    |    notification to SAP, include the following information:|
    |       |
    |    1. The description of the current problem (short dump) |
    |       |
    |       To save the description, choose "System->List->Save->Local File  |
    |    (Unconverted)". |
    |       |
    |    2. Corresponding system log  |
    |       |
    |       Display the system log by calling transaction SM21. |
    |       Restrict the time interval to 10 minutes before and five minutes |
    |    after the short dump. Then choose "System->List->Save->Local File   |
    |    (Unconverted)". |
    |       |
    |    3. If the problem occurs in a problem of your own or a modified SAP |
    |    program: The source code of the program   |
    |       In the editor, choose "Utilities->More |
    |    Utilities->Upload/Download->Download".    |
    |       |
    |    4. Details about the conditions under which the error occurred or which          |
    |    actions and input led to the error.       |
    |       |
    |User and Transaction|
    |    Client.............. 200     |
    |    User................ "SAMSON"|
    |    Language key........ "E"     |
    |    Transaction......... "VA01 " |
    |    Program............. "SAPMV45A"           |
    |    Screen.............. "SAPMV45A 4001"      |
    |    Screen line......... 65      |
    |Information on where terminated  |
    |    Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN".  |
    |    The main program was "SAPMV45A ".         |
    |       |
    |    In the source code you have the termination point in line 338       |
    |    of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".            |
    |Source Code Extract |
    |Line |SourceCde     |
    |  308|    else.     |
    |  309|*-----Nicht unterstu9EF7zt, Abbruch        |
    |  310|      message a301(v3).    |
    |  311|    endif.    |
    |  312|  endif.      |
    |  313| |
    |  314|*-Szenario A pru9EE4en        |
    |  315|  if lv_scenario_a   = 'A'.|
    |  316|    vbak-vbkla+2(1) = lv_scenario_a.    |
    |  317|  endif.      |
    |  318| |
    |  319|*-ermitteln CRM-Release    |
    |  320|  call function func_name  |
    |  321|        exporting          |
    |  322|            i_paraname = 'CRM_RELEASE'  |
    |  323|        importing          |
    |  324|            e_parval1  = lv_parval1.    |
    |  325|  lv_release_crm = lv_parval1+0(3).     |
    |  326| |
    |  327|* If lv_release_crm empty => X-message (correct download not possible)         |
    |  328|  if da_download_active = charx.        |
    |  329|    CALL FUNCTION 'CRM_CONNECTED'       |
    |  330|     IMPORTING|
    |  331|       CRM_CONNECTED       = lv_crm_connected        |
    |  332|     EXCEPTIONS            |
    |  333|       NO_CRMRFCPAR        = 1          |
    |  334|       OTHERS = 2          |
    |  335| .            |
    |  336|    IF sy-subrc = 0 and lv_release_crm = space and   |
    |  337|       lv_crm_connected = charx.        |
    |>>>>>|        message x302(v3).  |
    |  339|    ENDIF.    |
    |  340|   endif.     |
    |  341| |
    |  342|*-Fu9EEElen der View fu9EF5 das Ermitteln der Auftragstabellen          |
    |  343|  da_sales_view-partner    = charx.     |
    |  344|  da_sales_view-sdcond     = charx.     |
    |  345|  da_sales_view-sdcond_add = charx.     |
    |  346|  da_sales_view-contract   = charx.     |
    |  347|  da_sales_view-text       = charx.     |
    |  348|*-bei mehr als 1000 Belegflusssu92DEzen werden Daten nicht ermittelt |
    |  349|  if lv_tabix_vbfa < 1000. |
    |  350|    da_sales_view-flow     = charx.     |
    |  351|  endif.      |
    |  352|  da_sales_view-billplan   = charx.     |
    |  353|  da_sales_view-configure  = charx.     |
    |  354|  da_sales_view-credcard   = charx.     |
    |  355| |
    |  356|*-Im Standardszenario soll eine manuelle u818Ederung eines CRM Belegs|
    |  357|* (ab CRM Release 30A) nicht zuru9EDEk ins CRM gesendet werden. Das  |
    any responses will be awarded,
    regards,
    samson

    Hi,
    Maintain the current CRM release.
    The dump might have occurred when transferring SAP sales order to CRM.
    This has caused a error in SAP table CRMPAROLTP .
    Go to SE91 provide the message class & message number, then click where-used-list & select the program check box.It will show you the program name MV45AF0B_BAPIDATEN_ERMITTELN.
    Just check the program with the ABAPer.
    Hope this helps.
    Regds.......
    Sumit

  • Runtime error while creating sales order in VA01

    Dear all,
    In our develpment server(ecc 6.0),while creating sales order in VA01 for a sales area, when ever entering material number and quantity and press enter, it is giving error and taking to Runtime error long text showing syntax error in program RK2LSFOC
    application patch level for both production and development is same.
    can any one suggest the solution please

    Please note the error details
    Runtime Errors         SYNTAX_ERROR
    Date and Time          07.01.2010 17:43:06
    Short text
    Syntax error in program "RK2LSFOC ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLKEAK" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "RK2LSFOC " in include "RK2LSFOC
    " in
    line 128:
    "No component exists with the name "KWBRUM". ."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP* "
    Error in the ABAP Application Program
    The current ABAP program "SAPLKEAK" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "RK2LSFOC ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    The following syntax error was found in the program RK2LSFOC :
    "No component exists with the name "KWBRUM". ."
    |    " "

Maybe you are looking for