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

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

Error while creating sales order thru IDoc

Hi,
While using FM IDOC_WRITE_AND_START_INBOUND, I am getting an error 'Customer not found with DUNS number from IDoc' and the application document is nor posted. I am passing valid customers in the ship to party and sold to party segments but still getting this error.
Please advice.
Regards,
Rajesh

Hi All,
Can anybody give me some resolution for the above posted issue!
Thanks in advance.
Thanks,
Deep.

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

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 with network/project

Dear All,
we are getting the following message while creating a sales order with assembly processing with network/project system .
The standard Network used as a reference contains assignments to a standard WBS. However you have maintained WBS assignments manually.which assignment should be used?
manually maint pre-defined
reward points are assured for valuable help.
thanking you
Best regards,
R.Srinivasan

Dear Murali,
Thankyou very much for your reply.We have checked for these things which you have mentioned.
ie
Assignment of Standard WBS in the Standard network and WBS Assignment of Operastional network.We are still getting this error.
Kindly let me know What are the other possibilities for this error.
Thanking you,
Best regards,
R.Srinivasan

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

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.

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?

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

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

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

Similar Messages

Maybe you are looking for