Error during manuel entry/Change of condition.

Dear friends,
while I am trying to create standard customer order(VA01), I have faced an error message as: Item 00001:Error during manuel entry/Change of condition.
Can anyone tell me solution?
Thanks in advance.

Hi,
Goto to V/08 for your pricing procedure, check for the condition type if it is mandatory condition and / or if it is manual condition.
In V/06, select condition type and check the value for Manual entry field
Hope you get some inputs
regards,
Sagar

Similar Messages

Adhoc Query : Error during selection; check the selection conditions

Hi
We have a report set-up and which we want to run using our adhoc query report tcode S_PH0_48000513
The report, has a few different selection criteria in it to look at all action IT screen data in the system for ee's in specific personnel areas. There is also a criteria to allow us to paste in specific employee numbers we are interested in. The issue I am facing is that over about 3000 ids, the system automatically returns me a message when I click on the Output button to run the report which states:
Error during selection; check the selection conditions
Message no. PAIS206
I am not sure why this is happening. The selection criteria are fine and the other day I ran the report and I experienced no issues. The report ran successfully. Now though, if I try and paste in all the ids I am interested in (about 8000) I get this message straightaway.
Can anything be done to overcome this issue?
Any advice would be much appreciated.
Nicola

Hi
The message in full is:
Error during selection; check the selection conditions
Message no. PAIS206
Diagnosis
A runtime error occurred during dynamic selection.
System response
The runtime error will be caught; no short dump will be created. This error should not occur as a rule. However, very large select statements may trigger the runtime error SAPSQL_STMNT_TOO_LARGE or DBIF_RSQL_INVALID_RSQL. There is no way to prevent this happening. In this case, the error can only be caught.
Procedure
Check the selection conditions to see whether the error was caused because the option "Import from text file" included too many objects in the "Multiple selection" dialog. If this is so, you must limit the number of individual values.

Prepayment functionalitygives an error during Order Entry

Hi all,
We have oracle applications Suite - 11i (11.5.10.2) .
At time of prepayment during Order Entry form, we are getting following error.
_"Function not available to this responsibility. Change responsibilities or contact your system administrator" ._
Following is the Navigation Path :
Sales Order Entry > Query with existing SO > Others TAB > Select ACTIONS button > Select PAYMENTS option .
Thanks
Sanjay

Sanjay,
This is because the Function that is invoked when you select the Payments Action from Sales Order Screen has not been granted to your responsibility. The best way is to check the ONT_SUPER_USER menu in application Developer (this is the menu that is used by order Management super user), and see what all functions are there (manily the ones without prompts like 'Sales Orders: Print Payment Receipt'). ANd then compare the same with the menu that your responsibility is using (System Adminsitrator >> Security >> Responsibilities). I think you should get your answer. Please let me know.

Abab error during service entry sheet

dear experts
during service entry sheet the below error dump message is came.
pls any one solver porblem.
document # generated but which is not meet our oringla no range also its not save and terminated.
Update was terminated
System ID....   NEP
Client.......   900
User.....   mmusr
Transaction..   ML81N
Update key...   62B9FADE4AA3F18C8457001F29CC32A8
Generated....   06.01.2010, 14:49:32
Completed....   06.01.2010, 14:49:32
Error Info...   ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC

Check ST22 for abap dump. It looks program try to insert duplicate record. If there is an enhancement in standard tcode debug it. If not ask it to SAP via OSS.

Getting Account-Determination related Error during Service Entry Approval

Dear Sir,
We have created a Service Order (Purchase Order) with Account-Assignment Category as "Q" and Item-Category as "D" . The In the Purchase Order , Account assignment given was a WBS Element and appropriate GL for expense booking was also mentioned .
Subsequently , we did Service Entry (ML81n) .
Now during the approval of Service Entry Sheet , we are getting following error...
"Account determination for entry 9000 KBS 0001 not possible" .
We request to kindly guide us as what steps need to be followed to resolve this error . We will be highly greatful for the given kind help pl .
With Regards
Sania

HI
.1. In OBYC, check the Account Determination check box is not ticked. This means the account determination is not done from OBYC. It is done as per the account assignment entered in PO. 2. Check OMJJ go to OMJJ and enter teh movement type 101and go to Account geouping folder and click on it
all the line which has KBS in TEKey check the Check acc *** check box than you will not get this error.
3.Goto OBYC double click KBS and enter your valuation grouping code and assign to the G/L accounts and save

Account determination error during service entry for service PO

Dear Experts,
This about service PO. I created PO # 4501517101 & wanted to perform service entry via t/code ML81N. But I'm getting error "147 Account determination for entry OP01 FR1 OP01 not possible"
Appreciate if could anyone assist me on this issue. TQ.
rgds,
nantha

Please correct the assignment in OBYC and also in this error itself u can see one icon of proceed.If you will click on Proceed, then it will take u in to OBYC, where u have to do the corrections.

Error during transport-Structure change at field level (convert table /BIC)

Hi,
I am trying to transport from DEV to Test when I encountered this error.
The tables are both consistent when I checked with SE14.
Start of the after-import method RS_CUBE_AFTER_IMPORT for object type(s) CUBE (Activation Mode)
Error/warning in dict. activator, detailed log > Detail
Structure change at field level (convert table /BIC/DZCRUSDI026)
Table /BIC/DZCRUSDI026 could not be activated
Return code..............: 8
Following tables must be converted
DDIC Object TABL /BIC/DZCRUSDI026 has not been activated
Error when activating InfoCube ZCRUSDI02
Error/warning in dict. activator, detailed log > Detail
Structure change at field level (convert table /BIC/DZCRUSDI023)
Structure change at field level (convert table /BIC/FZCRUSDI02)
Table /BIC/DZCRUSDI023 could not be activated
Table /BIC/FZCRUSDI02 could not be activated
Return code..............: 8
Following tables must be converted
DDIC Object TABL /BIC/DZCRUSDI023 has not been activated
Error when resetting InfoCube ZCRUSDI02 to the active version
How do I resolve this
thanks

Hi,
There are no Inactive objects in the cube in DEV system. Also must of the changes I made in Test are already in the cube in TEST But the cube is not active.
SAP proposed that the cube be activated manually but is not a good procedure to activate in TEST system.
Error when resetting InfoCube ZCRUSDI02 to the active version
Message no. RSO410
Diagnosis
Errors arose when activating InfoCube ZCRUSDI02. An active version already existed before the activation.
System Response
InfoCube ZCRUSDI02 could not be reset to the old active version. Since the generated objects no longer correspond to the old active version, they were reset to inactive.
Procedure
The old active version of InfoCube ZCRUSDI02 can no longer be used. Remove the cause of the activation error and activate InfoCube ZCRUSDI02 anew.
thanks

Developer Mode Error during journal entry

Hi I am getting this error while entering a new journal.
Develope mode error
an oracle apps coding standards v iolation was encountered please report this probem to oracle support
fddfu.lc register_form-flex() fucntion detected a flexfield attached to a form field whose length is less than the maximum concat value lenght 700
please change the length of the field
Block : HEADER
Field : ORIGINATING_BAL_SEG_VALUE
Length : 25

Is this a base form or a custom form ? If it is a base form, pl disable any personalizations you may have on this form, and turn off all CUSTOM.pll code - then see if the error still occurs. If it does, pl open an SR with Oracle Support.
HTH
Srini Chavali

Error during activation of change list

I want to activate my changes in the change list of the intergration configuration. After activation I receive the error message:
unerwarteter Fehler bei Nachrichtenverarbeitung:
javax.transaction.HeuristicMixedException:
com.sap.engine.ts.exceptions.BaseHeuristicMixedException: One or more
XAResources were not commited because of Exception in the second commit
phase.
at com.sap.engine.services.ts.jta.impl.TransationImpl.commit
(TransactionImpl.java:451)

Hey Gregor,
This link talks about the status of change lists:-
http://help.sap.com/saphelp_nw04/helpdata/en/f6/719a2172f74b67b150612a7cd3b7df/frameset.htm
and this one shows how to organize change lists:-
http://help.sap.com/saphelp_nw04/helpdata/en/ab/3adb41083f6024e10000000a1550b0/content.htm
I hope they are helpful.
Regards
Sushumna

Error during Material type change

Hi,
We are trying to change a material type from being a purchased raw material to a manufactured semifinished part using MMAM tcode and getting following error.
The Purchase Order displayed is already received & invoice complete.
Error****************************
Purchase orders exist
The two material types have either different quantity/value updating or a different account category reference.
PO number      Item
P048019        00140
Could you please let me know how to overcome this error..?
Thanks & Regards,
Samay

Samay, I hate to be the bearer of bad news, but the only way to change the material type on a material is if the material has no links. No Purhase Orders against it, no reservations against it, no inventory, etc, etc. The material needs to be "Clean" to change the material type. If it is a fairly old material, this may be a huge task, which is why I suggested just to create a new material and go with that. You would need to do some major clean up to get the material to a state which would allow you to change the material type. I guess you could start by removing the item from the PO which you mentioned earlier. This is only the begining though.
Regards,
Rich Heilman

Error During Proxy client changing

Hi All,
I have a Webservice to Proxy synchronous scenario.
The scenario is working for client 210 of SAP system but it is giving an error for 260 of SAP system when i changed the client in CC and test the scenario.
The error says in the moni "INTERNAL">SYSTEM_NOT_CONFIGURED_AS_XMB".
Can some body help me what changes we have to do for different clients of the system.
Helpful answers will be rewarded points.
Thank & Regards,
RK

HI,
You need to do the configuration in 260 of SAP system. Run transaction SXMB_ADM and then navigate as mention blow.
Integration Engine Configuration ---> Under Role of Business System enter "Application System".
Under Corresponding Integ. Server, enter the rfc destination "dest://xxx" .
To know the rfc destination, goto SM59 and check the connection type 'H', here you will find the RFC destination, just copy it from here.
You can find all the info in this blog step no 2 under "Configuration Business system as local Integration Engine".
How do you activate ABAP Proxies?
Regards,
Sarvesh

Error during MIGO-Error during maint. of delivery costs in master condition

Hi
We are getting error as below during MIGO against a PO with doc type NB:
"Error during maint. of delivery costs in master conditions, Delivery cost conditions in different validity periods not identical"
What might be cause??
Thanks
Maruthi

Check the delivery conditions in condition tab of PO.
Try to check if there are any delivery condition records mainatined.
I think the problem is mostly due to overlapping validity period. Try to change the validity period for the same.

Error during creation of entry sheet via BAPI

Hi all,
I have a problem with that bapi and that user exit. I can create a entry sheet with the bapi BAPI_ENTRYSHEET_CREATE and get it accepted using the flag BAPIESSRC-ACCEPTANCE of the header.
But if i use the enhancement SRVEDIT in order to do a custom validation i get the following error during the creation of the entry sheet: "E SE 214 Error during update".
Even if i don't do anything in the user exit (only activate it) i still get the message "Error during update". Anybody knows if there is a problem with that user exit? should i do something specific to use that user exit (it doesn't exist any documentation for the user)
Anybody has solved the issue? Anyone knows another user exit to use in the moment of save the changes of the entry sheet?
Many thanks in advance
Aaron

Hi John,
Some of the structures you have to fill for the IDOC belongs to a referencing ...X structure. For example structure BAPI1022_FEGLG002 and BAPI1022_FEGLG002X.
When you fill the capitalization dat (BAPI1022_FEGLG002-CAP_DATE = '19981231') it's necessary to fill the corresponding field (BAPI1022_FEGLG002X-CAP_DATE = 'X') to specify that the content of the field should be transferred to the fixed asset. Otherwise it'll be not transferred and you'll get an error message instead.
Regards Bernhard

Lower limit can only be changed during initial entry, Message no. NR651

Hi Experts,
As per the number ranges limit values defined in the system for the planned orders, there is a need to increase the number ranges.
System is not allowing us to change the limit values of the Planned orders in MD91 and showing the Message no. NR651.
We have also searched for the available threads in SCN and other sites, but didn't find the root cuase link for this error.
System message:
Lower limit can only be changed during initial entry
Message no. NR651
Diagnosis
You have tried to change the lower limit of an interval which has a non-initial number status.
System Response
The change was not executed.
Please guide us how can we increase the number ranges for planned orders.
Thanks in advance.

Hi,
You can create a new number range or change in transaction OMi2 or in MD91.
Assign the 02 by clicking number range in OMi2
or in transaction OPPQ click on number range & select the 02.
Do the changes as described and analyse the results. Ensure that while testing no body is creating the planned orders.
Regards,
Narresh

Solman_admin password changes results in errors during managed system setup

Hello all,
I am trying to get Solman 4.0 EHP 1 to work, but get numberous problems.
Currently I have 6 messages at SAP, but no solution yet.
Situation:
Solman 4.0
SAP_BASIS     701     0003
SAP_ABA     701     0003
ST-PI     2008_1_700     0000
PI_BASIS     701     0003
SAP_BW     701     0003
CRMUIF     500     0001
SAP_AP     700     0014
BBPCRM     500     0013
CPRXRPM     400     0014
BI_CONT     704     0002
ST     400     0019
ST-A/PI     01L_CRM570     0000
ST-ICO     150_700     0016
ST-SER     701_2008_2     0002
So, it is uptodate.
The problem:
Changing the solman_admin password results in errors during connecting a managed system.
In the inital setup the solman_admin is created with a pasword.
After the basic setup I setup some managed systems.
In the meantime I had to change the password of solman_admin
I am logged in with solman_admin and do solman_setup to setup the managed system.
During the setup a process tries to logon back to the solman using solman_admin and the incorrect password.
This is the logging:
Step SSO Details
Found SID for SSO ACL entry : MSD
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (823 bytes)
A failure occured while connecting to ABAP stack on localhost sys=70 client=300 user=SOLMAN_ADMIN
!! Exception : Password logon no longer possible - too many failed attempts
A failure occured while importing ABAP SSO ticket certificate in ABAP stack
!! Exception : java.lang.NullPointerException
Java SSO ticket certificate of MSD was imported in ABAP PSE of kswv024.mob.local (client 300)
The Java SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=MSD LoginTicketClient=000)
Anyone else has this problem?
gr
Sander

Just for clarification it's Solman 7.0 EHP1 correct?
Also you may want to unlock the following user:
localhost sys=70 client=300 user=SOLMAN_ADMIN
Then if you navigate (in solution manager) to TCode solman_workcenter -> "Root Cause Analysis" tab ->"Agent Administration" menu item on the left -> "Applications Configuration" tab -> under the Agent Applications - Configuration menu on the left select "com.sap.smd.agent.application.global.configuration" -> Change the "Scope" drop down in the frame to the right to the SMD agent that you are using for "localhost sys=70 client=300" -> Click the "edit" button to the right of the Scope drop down box -> now find the entry below that lists "SOLMAN_ADMIN" as the user and find the corresponding password entry and update it with the new password that you changed it to -> click save and try the managed setup again.
Hope this helps, please let me know and we can go from there.

Error during manuel entry/Change of condition.

Similar Messages

Maybe you are looking for