Error in Fiori Create Sales Order

Hi All,
    After completing all the mandatory configuration for Create Sales Order Fiori App.
    I have created a Sales Rep with pernr , & Assigned the Sales Rep (ER) to Customer
    While executing the App I am getting the following message
No customer found for this user. Map using the business partner function
--58F5F155A7D0A16767A749B7E4BB03E30
Content-Type: application/http
Content-Length: 635
content-transfer-encoding: binary
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 529
dataserviceversion: 1.0
{"error":{"code":"SY/530","message":{"lang":"en","value":"No customer found for this user. Map using the business partner function."},"innererror":{"transactionid":"5397B701746C0C80E1008000AA74252D","timestamp":"","Error_Resolution":{"SAP_Transaction":"","SAP_Note":""},"errordetails":[{"code":"SRA017_SO_MSG/102","message":"No customer found for this user. Map using the business partner function.","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"","propertyref":"","severity":"error"}]}}}
--58F5F155A7D0A16767A749B7E4BB03E30--
Any idea how to resolve this issue
Rgds,
Ranjith
Tags edited by: Michael Appleby

Hi Ranjith,
Please double check you have configured required settings.
App Implementation: Create Sales Orders - SAP Fiori Apps - SAP Library
Regards, Masa
SAP Customer Experience Group - CEG

Similar Messages

Error throwing while creating sales order

Dear all,
While on sales order creation,We have entered order type,sales organization,distribution channel,divison,
on entering sold to party,presssing enter,error is throwing as
No customer master record exists for sold-to party
actually customer master record is already created,
We need to extend the sales area then only system is allowing to create sales order,
Is there is any setting missing in configuration ?
Thanks
Jeyakanthan

hi,
can be done in two ways
1, only for the paticular customer
goto XD01 and extend the customer by entering new sales area above
and the already exisisting sales area in the reference
2,common distribution channel and common division(this is for all the customer created in that particular sales area)
IMG>sales and distribution>master data
regards
senya

Error coming while creating sales order Thru' Assembly processing.u00A0

Hi,
I am working on assembly processing. when i am creating sales order if order qty when i am giving more then 999 means if i given 1000 kg it giving an error like the exection factor in the network is reduced to 1000 to 1 kg and confimed as 1 kg only and system is giving msg *Change not accepted (execution factor in network too large)* where i have tomodify this .
In above context i would like to brief you that i can't extend quantity more then 999(Three alfabet).
All suggestions will be apreciated with good points.
Regards,
Vishal Kr. Sharma

Hi vishal
Check in MMR the following settings :
1) Base unit of measure
2) sales unit
3) Strategy group maintained in MMR ->MRP 3 view
4) Availability check(sales/general plant view in MMR ) and MRP type (MRP1 view in MMR) has been maintained or not.
5) Check the fields maintained in the MRP 3 view.
Regards
Srinath

Sap Fiori - Create Sales Order in Offline

Hello,
It is possible to use SAP Fiori for creating Sales Order in Offline mode?
Thank you,

Hi Michely,
It is possible if you convert your Fiori web app to a hybrid app. You have to create a Cordova based hybrid app and use offline Kapsel plugins that comes with SAP Mobile Platform (Getting Started with Kapsel - Offline OData))
Out of the box Fiori doesn't have offline features, we are expecting it in the future.
Regards,Midhun
SAP Technology RIG

Error occurd while creating sales order, plz help

while i am creating a sales order, i got a error like this, version 0 is not defined for the fiscal year 2008. when i press error msg it shows like this The version 0 is not defined in controlling area 1000 for the fiscal year 2008.
You have to maintain the fiscal year-dependent version parameters for all actual versions for which multiple valuation is updated.
System Response
The version 0 cannot be used for fiscal year 2008.
Procedure
Maintain the fiscal year-dependent version parameters for the version 0.
Execute function

Hi
Maintaining Versions
Transactioncode
SPRO
Choose SAP Reference IMG.
Choose Controlling -> General Controlling -> Organization.
Choose for Maintain Versions.
http://help.sap.com/saphelp_46c/helpdata/en/03/fb58b00d9611d3b65e0000e82d962e/content.htm
Regards
Jitesh Mehta

Error in while creating sales order

HI
Gyanendra i have one error
No customer master record exists for sold to party.
plz explan how i ll do this with path .

Hi,
As I understood your issue, You came across this message then you try to enter a customer number in the Sold to party filed of VA01 sales order creation screen.
Reason why you got this error is there is no such sold to party available from the number you entered there.
You can check it by doing below steps.
Go to XD02 transaction
Enter the same number you enter in the VA01
Press "Customer Sales area's" button
Then system will through a error saying "Customer not exists"
If you able to see a customer go in to that and check the Account group of his by clicking below menu.
Extras -> Administrative Data
If it's not equal to "Sold to Party" then you can get same error in the VA01 as well.
In that case create a new customer from XD01 transaction
Come back to VA01 and try with that new customer.
You should be able to create the sales order now.
If you don't want to create a new customer just press F4 key in the Sold to Party field and get an existing customer.
Best regards,
Anupa

An error occured while creating sales order "Enter sold-to in R/3"

when creating a sales order using CRM even though we have passed Sold-to ship-to bill-to using partner table we are getting an error Enter Sold-to in R/3

Hi
I think you have both Variant configuration and BOM.
Pls ensure the following.
1. BOM masterdata is maintained for the variants
2. Variant configuration is configured correctly
Configuration profile is created for the material
Knowledge base object and run time version are available
3. Maintain materials as not relevant for delivery or dont give delivery quantity as 0
Once you are sure that these are in proper shape, you can start creating order. The problem wont come.
Reward points if it helps you.

SAP Fiori Error - Create Sales Order app doesn't run after Google Chrome updates

Hi,
I have a problem with the create sales order app (ui5_sd_so_cr).
Everything works fine until Google Chrome browser updates to version 34.0.1847.116 m .
The create sales order application has an error when i try to checkout the cart.
This error is in the SalesOrderCreatePriceAndAvailabilityCheck.controller.js and SalesOrderCartDetails.js in this function:
l.oSOCartModel.refreshSecurityToken(function (a, b) {
        l.oSOCartModel.create("/SalesOrders", m, null, function (c, d) {
            com.sap.kelley.salesordercreate.utils.ModelUtils.updateCartModelFromSimulationResponse(d);
            oSObusyIndicator.close();
        }, function (g) {
            oSObusyIndicator.close();
            var d = g.response.body;
            var f = jQuery.parseXML(d);
            var e = f.getElementsByTagName("message")[0].childNodes[0].nodeValue;
            var c = new sap.m.Dialog({
                title: sap.ca.common.uilib.message.AlertMessageBoxType.ERROR.title,
                content: [new sap.m.Label({
                    text: e
                leftButton: new sap.m.Button({
                    text: l.oBundle.getProperty("XBUT_OK"),
                    tap: function () {
                        if (j) {
                            l._onNavigateBack();
                        c.close();
            c.addStyleClass("sapSOC-SingleButtonDialog");
            c.open();
    }, function (a) {
        oSObusyIndicator.close();
        var b = new sap.m.Dialog({
            title: sap.ca.common.uilib.message.AlertMessageBoxType.ERROR.title,
            content: [new sap.m.Label({
                text: sap.ui.getCore()
                    .getModel("i18n")
                    .getProperty("ERROR_REFRESH_SECURITY_TOKEN")
            leftButton: new sap.m.Button({
                text: l.oBundle.getProperty("XBUT_OK"),
                tap: function () {
                    if (j) {
                        l._onNavigateBack();
                    b.close();
        b.addStyleClass("sapSOC-SingleButtonDialog");
        b.open();
    }, false);
The error is in the line 07. Cannot read property 'body' of undefined
Variable g is undefined.
I tested the application with other browsers (IE, Firefox, Safari) and everything works perfectly. Only Chrome has this kind of problem.
UISRA
UISRA017
100
0002
SAPK-10002INUISRA017
HTML5 Create Order
System
SAP_BASIS
731
0007
SAPKB73107
SAP Basis Component
GW_CORE
200
0006
SAPK-20006INGWCORE
SAP GW CORE 200
IW_BEP
200
0007
SAPK-20007INIWBEP
Backend Event Provider
UI5 version 1.16.4
It 'happened to someone else?
How can I fix the problem?
Thank you for your help.
Regards,
Nicola

Few things you can try,
Upgrade your UI5 library version. Latest is 1.18
Implement release notes :
1948368 - Fiori Create Sales Order Wave 1 Common Library Fixes
1947789 - Fiori Create Sales Order Wave 1 Fixes
Check if these can be applied or go with UI library update.
1939288 - Hotfix 1.16.5 for UI AddOn SP06 SC: UI2_SRVC
Regards,
Tejas

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

Issue in creating sales order using BAPI's...?

Hi Guru's,
i had generated the sales order using the BAPI..but could please guide me how to declare the data declaratin same fields as globally and how to move internal table and how to append ....
thanks in advance...
REPORT z_bapi_salesorder_create.
Sales document type
PARAMETERS: p_auart TYPE auart OBLIGATORY.
Sales organization
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
Distribution channel
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
Division.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
Sold-to
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
Ship-to
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
Material
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
Quantity.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
Plant
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    EXPORTING
      sales_header_in     = header
      sales_header_inx    = headerx
    IMPORTING
      salesdocument_ex    = v_vbeln
    TABLES
      return              = return
      sales_items_in      = item
      sales_items_inx     = itemx
      sales_schedules_in = lt_schedules_in
      sales_schedules_inx = lt_schedules_inx
      sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
   COMMIT WORK AND WAIT.
     call FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

*& Report ZAREPAS30
REPORT zarepas30.
DATA : gs_vbeln                   TYPE vbak-vbeln,
       gs_order_header_in         TYPE bapisdhd1,
       gs_order_header_inx        TYPE bapisdhd1x,
       gt_order_items_in          TYPE STANDARD TABLE OF bapisditm,
       gwa_itab1                  TYPE bapisditm,
       gt_order_items_inx         TYPE STANDARD TABLE OF bapisditmx,
       gwa_itab2                  TYPE bapisditmx,
       gt_order_partners          TYPE STANDARD TABLE OF bapiparnr,
       gwa_itab3                  TYPE bapiparnr,
       gt_return                  TYPE STANDARD TABLE OF bapiret2,
       gwa_itab4                  TYPE bapiret2.
Sales document type
PARAMETERS: p_auart TYPE auart OBLIGATORY.
Sales organization
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
Distribution channel
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
Division.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
Requested Delivery Date
PARAMETERS: p_edatu TYPE edatu OBLIGATORY.
Sold-to
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
Ship-to
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
Material
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
Quantity.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
Plant
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
gs_order_header_in-doc_type = p_auart.
gs_order_header_inx-doc_type = 'X'.
Sales organization
gs_order_header_in-sales_org = p_vkorg.
gs_order_header_inx-sales_org = 'X'.
Distribution channel
gs_order_header_in-distr_chan = p_vtweg.
gs_order_header_inx-distr_chan = 'X'.
Division
gs_order_header_in-division = p_spart.
gs_order_header_inx-division = 'X'.
Reguested Delivery Date
gs_order_header_in-req_date_h = p_edatu.
gs_order_header_inx-req_date_h = 'X'.
gs_order_header_inx-updateflag = 'I'.
Partner data
Sold to
gwa_itab3-partn_role = 'AG'.
gwa_itab3-partn_numb = p_sold.
APPEND gwa_itab3 TO gt_order_partners .
ship to
gwa_itab3-partn_role = 'WE'.
gwa_itab3-partn_numb = p_ship.
APPEND gwa_itab3 TO gt_order_partners .
ITEM DATA
gwa_itab2-updateflag = 'I'.
Line item number.
gwa_itab1-itm_number = '000010'.
gwa_itab2-itm_number = 'X'.
Material
gwa_itab1-material = p_matnr.
gwa_itab2-material = 'X'.
Plant
gwa_itab1-plant    = p_plant.
gwa_itab2-plant   = 'X'.
Quantity
gwa_itab1-target_qty = p_menge.
gwa_itab2-target_qty = 'X'.
APPEND gwa_itab1 TO gt_order_items_in.
APPEND gwa_itab2 TO gt_order_items_inx.
Line item number.
gwa_itab1-itm_number = '000020'.
gwa_itab2-itm_number = 'X'.
Material
gwa_itab1-material = p_matnr.
gwa_itab2-material = 'X'.
Plant
gwa_itab1-plant    = p_plant.
gwa_itab2-plant   = 'X'.
Quantity
gwa_itab1-target_qty = p_menge.
gwa_itab2-target_qty = 'X'.
APPEND gwa_itab1 TO gt_order_items_in.
APPEND gwa_itab2 TO gt_order_items_inx.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
    order_header_in               = gs_order_header_in
    ORDER_HEADER_INX              = gs_order_header_inx
IMPORTING
    SALESDOCUMENT                 = gs_vbeln
tables
    RETURN                        = gt_return
    ORDER_ITEMS_IN                = gt_order_items_in
    ORDER_ITEMS_INX               = gt_order_items_inx
    order_partners                = gt_order_partners.
Check the return table.
LOOP AT gt_return into gwa_itab4 WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error occured while creating sales order '.
ELSE.
Commit the work.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', gs_vbeln, ' created'.
ENDIF.

User Exit to check whether chapter id for Material and Plant combination is maintained while creating sales order

Hello all,
my requirement is, system should give error message while creating sales order, if chapter ID is not maintained for a material and plant combination.
please suggest the user exit.

Hi
CASE 1 : All Plants are excisable.
In Material master , Foreign Trade data tab- mentioned Control code field mandatory. ( i.e nothing but Chapter ID)
CASE 2 : Few Plants are excisable
In the Case 2 you need to go for Enhancement
Program Name : MV45AFZB
User Exit: USEREXIT_CHECK_VBAP ( Item Level Check )
By using above user exit you write a logic with the help of ABAPer
Plant and Chapter ID combination table : J_1IMTCHID

Order cannot be placed using "Create sales order" fiori app

We have setup "create sales order" fiori app and tried to place a order. We encountered with the error saying "In the context of Data Services an unknown internal server error occured" whilst clicking "Checkout" button.
We looked up Error log and found the detailed error "Invalid format (return table): Row Number 1, Property Name 'SalesOrderSimulation', Property Value". Full error log xml is as follows,
<?xml version="1.0" ?>
- <ERROR_CONTEXT>
<ERROR_INFO>Invalid format (return table): Row Number 1, Property Name 'SalesOrderSimulation', Property Value ''</ERROR_INFO>
- <ERROR_RESOLUTION>
<SAP_NOTE>See SAP Note 1797736 for error analysis</SAP_NOTE>
<LINK_TO_SAP_NOTE>https://service.sap.com/sap/support/notes/1797736</LINK_TO_SAP_NOTE>
</ERROR_RESOLUTION>
<_-IWCOR_-CX_DS_INTERNAL_ERROR />
- <_-IWCOR_-CX_DS_EP_ENTITY_ERROR>
<INDEX>1</INDEX>
<PROPERTY>SalesOrderSimulation</PROPERTY>
</_-IWCOR_-CX_DS_EP_ENTITY_ERROR>
- <_-IWCOR_-CX_DS_EP_PROPERTY_ERROR>
<PROPERTY>SalesOrderSimulation</PROPERTY>
<VALUE />
<TYPE>\TYPE=STRING</TYPE>
<OFFSET>0</OFFSET>
</_-IWCOR_-CX_DS_EP_PROPERTY_ERROR>
- <CX_PARAMETER_INVALID_TYPE>
<TYPE>\TYPE=STRING</TYPE>
</CX_PARAMETER_INVALID_TYPE>
- <SERVICE_INFO>
<NAMESPACE>/SAP/</NAMESPACE>
<SERVICE_NAME>***Hide_due_to_secure_log_level***</SERVICE_NAME>
<VERSION>0001</VERSION>
<SYSTEM_ALIAS>LOCAL</SYSTEM_ALIAS>
<DESTINATION>NONE</DESTINATION>
</SERVICE_INFO>
- <SYSTEM_INFO>
<REQUEST_URI>/sap/opu/odata/sap/***Hide_due_to_secure_log_level***</REQUEST_URI>
<REMOTE_ADDRESS>xxx.xx.x.xx</REMOTE_ADDRESS>
<APPLICATION_SERVER>eccdev_ECD_10</APPLICATION_SERVER>
<HUB_VERSION_INFO>System ECD/200, NW Release 7.40, SAP_GWFND SP10, Internal GWFND Version 011</HUB_VERSION_INFO>
</SYSTEM_INFO>
</ERROR_CONTEXT>
Please look at the screenshot for more details on request.
Do you have any idea how to fix this bug or do we have a mistake in our configuration?
Thanks for any hints.

Have you been able to solve this issue without resorting to a core mod described by Gopichand above? In our system the notes referenced by Masa in another post are not applicable because of the SP-level of the components involved. We've got:
SAP_GWFND
740
0010
SAP Gateway Foundation 7.40
SAP_UI
740
0011
User Interface Technology 7.40
SRA017
600
0006
Create Purchase Order OData Integration
UIEAAP01
100
0005
UI for ERP Central Applications
UIX01CA1
100
0004
UI for Cross-Applications
UIX01EAP
100
0005
UI for ERP Central Applications
Based on the fact that the error seems to be caused by the mismatching types of the SalesOrderSimulation property, the component at fault is SRA017 or possibly the GWFND component itself. In another system we're on SRA017 SP5 and SAP_GWFND SP9 and the app works without an issue. Since both those SP's are 1 level lower, it further confirms that it must be SRA017 SP6 or SAP_GWFND SP10 that cause the issue.
I have not been able to find any recent OSS notes that would address the issue and will be opening an OSS incident for it. If you happen to already have a solution, then please let me know. If not, I'll provide an update once I've heard from OSS folks.
Lukasz

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

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 in Fiori Create Sales Order

Similar Messages

Maybe you are looking for