Error in Creating sales order

Hi guys
while creating a Sales order i have encountered a
problem.when i entered the following informations
i got the following error
Transaction code:VA01
order type : OR
salesOrg   : JNOS
Distbchannl: XC
Division   : FD
Salesoffice:JS00
Salesgroup : JAG
after entering all the iformation i got the following error
Error:Order type 'OR' has not been defined in Sales area <'JNOS','XC','FD'>
note- I was using tese infom before and i have created
many salesorder.now tis error is coming!
Regards
Jino

hi,
go to spro-sales and distributionsalessalesdocumentssales document header---assign sales area to sales document types
check if that assignment is made properly

Similar Messages

  • 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 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 creating Sales Order Through BAPI

    Hi Friends,
      i am creating a RFC where i have to create sales order .
    I am using bapi
    BAPI_SALESORDER_CREATEFROMDAT2
    for same and entering values to it.
    I got the following return messages:
    S V4                   233 SALES_HEADER_IN has been processed successfully
    S V4                   233 SALES_ITEM_IN has been processed successfully
    S V1                   311 BDN Order 3112800903 has been saved
    But when I go to transaction VA03 and enter the number i get the following error:
    SD document 3112800903 is not in the database or has been archived
    Can any one know how to resolve this error.I am also using BAPI_TRANSACTION_COMMIT with wait = 'X'.
    Regards,
    Santosh Alle

    Hi,
    Try to check the return message once.
    SD document 3112800903 is not in the database or has been archived
    You will get this message if the sales document is deleted from the database .The BAPI   'BAPI_SALESORDER_CHANGE'  is used to delete salesorder.Check whether anyone has deleted it
    Also, sometimes it may take few seconds to update the sales order in the database when using BAPI. Check the transaction after some time.
    Regards,
    Lakshman.
    Edited by: Lakshman N on May 14, 2010 7:43 AM

  • Error while creating sales order in ECC 6.0

    Hi All,
    I am creating sales order through VA01.
    Error comes As "Repairs processing with cost management only for the main item"
    The material which i am using is finished goods.

    Dear Akilesh,
         Just check whether the material - in MM - material type whether the Qty and value update has been ticked.
    What order type you are using and what is the item category you are using?
    Kindly let me know that also
    Regards,
    Sudhir

  • Error while creating sales order with ref using SD_SALESDOCUMENT_CREATE

    Hi
    I am creating sales order with reference using function module SD_SALESDOCUMENT_CREATE , while creating i am getting error
    Document doesn't have document category even thougth i am passing document category in header as well as item lavel.
    In VBUK table there is no value for VGTYP.
    Can you please help me how to resolve it.
    Thanks & regards
    kiran

    Problem resolved by passing   REFDOC_CAT in the FM along with  SD_DOC_CAT.
    Thanks

  • Error while creating sales order using SD_SALESDOCUMENT_CREATE

    Hello All,
    We are using to  SD_SALESDOCUMENT_CREATE function module to create sales order it is working fine for single material.
    When we try to create sales order with multiple matearials we ended up with the following errors
    SALES_HEADER_IN has been processed successfully
    000000
    VBAKKOM
    Internal error in communication between configuration and sales doc.CONFIGURATION_PROCESSING
    000000
    CONFIGURATION_PROCESSING
    Error in SALES_ITEM_IN 000010
    000000
    VBAPKOM
    Internal error in communication between configuration and sales doc.CONFIGURATION_PROCESSING
    000000
    CONFIGURATION_PROCESSING
    Error in SALES_ITEM_IN 000020
    000000
    VBAPKOM
    SALES_ITEM_IN has been processed successfully
    000000
    VBAPKOM
    Could any one help me out to resolve this issue.
    Thanks in advance....
    Cheers,
    Harsha

    Hello,
    Looking at BAPI errors. It looks like you are trying to create sales order with variant configuration.
    Check Below SAP Note.
    900380 - Configurable items in the SD process (idocs & bapis)
    Regards,
    Sameer

  • 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

  • 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 IN CREATING SALES ORDER,USING IDOC TYPE ORDERS05

    I am using exit to write my code for creating sales order of IDOC Type ORDERS05 and order type ZDRX.
    IF I proceess the Idoc in background each time error message comes
    FIELD kuwev-kunnr(ship to party)is not an input field.
    but if i run in foreground in debugging mode,sales order is getting created..
    please suggest something.

    If thats not working..
    try BAPI_SALESORDER_CREATEFROMDAT2
    If BAPI is not working. try creating a bdc for the same if there's not error on trying from VA01

  • Error in Creating Sales Order Using BAPI_SALESORDER_CREATEFROMDAT2

    Hi Everyone,
    We have a requirement to create sales order from flat file using BAPI. Everything was working well until we encounter a customer with credit control limit setup.
    Using the partners table for BAPi, the sold to customer is enter at header level, and we have this requirement to add the payer at item level. This is where the error is occuring. Upon debugging, I found out that the customer has a credit limit setup at FD33, and has a record found in KNKK, which is giving the error "Credit limit customer differs from credit limit customer in header".
    However, duting manual creation of sales order via VA01, this error is not encountered.
    Any ideas or suggesstions on how we can move forward with SO creation using BAPI with customers where credit management is setup?
    Thanks,
    Louisse

    If thats not working..
    try BAPI_SALESORDER_CREATEFROMDAT2
    If BAPI is not working. try creating a bdc for the same if there's not error on trying from VA01

  • 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". ."
    |    " "

  • Getting error when creat sales order and Stock Posting

    Hi
    I have created enterprise structure, xd01, mm01, ovkk but I count't post stock.
    When create sales order getting error is that
    1.This material is not defined for sales area 1000, 10, 00.
    And if i use this T.Code MB1C,
    2. Parameters for plant 1000 not maintained in Inventory Mgt.,
    *3. Unit *** is not created in language EN.*
    Thanks in advance

    Dear selvi sankaran
    1)  Compare the sales organization, distribution channel and division of customer and material.  In your case, either of that should have been created differently.  Maintain the same sales area and retry
    2)  Go to omi8 and maintain the required parameters to your plant
    3)  Go to Material Master, select "Additional data" and click on "Descriptions".  There maintain "EN" under language.
    thanks
    G. Lakshmipathi

  • Getting Error when creating sales order

    Hello expert,
    When i ma creating sales order In productive environment, not getting any error.
    While creating sales order in Quality system The Error is"Order Type ZSOS has not defined in sales area 0201,02.00.
    I checked customizing and both the system Quality and Productive system having following configuration and that is identical.
    Combine sales Org
    Sales Org                              Ref Sales org
    0201                                        Blank
    Combine Distribution Channel
    Sales Org                 D.Channel            Ref dist Channel
    0201                            02                            02
    Combine Division
    Sales org             Division            Ref Divison
    0201                      10                      00
    Assign permitted order type to he sales areas.
    Ref Sales org         Ref Distribution              Ref Division   Sales doc type
    0201                        02                                   00                     ZSOS
    Please can anyone assist me where we are missing.
    Regards
    Ajit jaiswal

    Hi Ajit,
    you have to make these assignments in img
    Combine sales organizations(ova0)
    Combine distribution channels(ovam)
    Combine divisions(ovan)
    Assign sales order types permitted for sales areas(ovaz)
    after these assignments the mentionwed error will be resolved
    Revert if helpful
    Mohit Singh

  • Dump Error when creating sales order

    Dear Friends,
    When I am creating sales order after entering order quantity field value in item table giving dump error.
    INCLUDE LV03VF0B.
    INCLUDE LV03VFB4 inside below code trigger error.
    PERFORM VVBBD_AUFBAUEN USING WA_AVBBD
                                        WA_AVBBD-APOMOBILE
                                        DA_SUBRC
                                        DA_UPDKZ
                                        DA_VVBBD_TABIX
                                        0.

    Hello Praveen,
    checked this program in other systems.
    The weird thing in your code is the final parameter 0, it should not be there.
    The call should be:
    PERFORM VVBBD_AUFBAUEN USING WA_AVBBD
                                        WA_AVBBD-APOMOBILE
                                        DA_SUBRC
                                        DA_UPDKZ
                                        DA_VVBBD_TABIX.
    Hope it helps.

Maybe you are looking for