Error while creating condition record in qc15?

Hi all
I have selected QCA1 and selected material and customer and trying assign E22 but then getting an error " No released version found for specified selection E22"
kindly suggest me the solution on this
regards,
sanju

Hi Yogini,
I have crated a new profile , an created a condition record also with respect qca1 and assigned this profile.
how to make use of this profile further?
regards,
Sanjana

Similar Messages

Error while creating condition record

Hi
Am using 4.7 and creating condition record while saving condition record am getting error NO UPDATE SERVER FOUND FOR CONTEXT E, So am stuck up and do not know whom to contact is it error for BASIS? or related with SD kindly help.
Thanx

Hi Mukesh
As you are getting error NO UPDATE SERVER FOUND FOR CONTEXT E, while saving the condition record, kindly consult your BASIS consultants and ask them to check wheather the pricing related tables and structures have been copied and uploaded properly or not.
Regards
Srinath

Error while creating absence record in PA30 using 2001 infotype

Hi all,
iam getting an error while creating absence record for infotype 2001for LOP(unpaid)
error : No quota available for att./abs. 6000 for pers. no. 61000052 between 31.12.2009 and 31.12.2009
i have did
Create a absence type LOP
Determine Entry Screens and Time Constraint Classes
Define Counting Rules
Assign Counting Rules to Absence Types
Payroll: India>>Absences>Describe Absence Valuation Rules 01 Unpaid Leave
Group Absences for Absence Valuation>>Absence valuation rule>>F4 country grouping 40>> assign 01Unpaid Leave
please solve this

Actually I don't know how your system is configured.
However, the error you're receiving seems you have assigned the absence type to a quota type.
Please go to your counting rule and check whether Deduction rule - absence quotas - within entitlement field is filled.
If yes, get the deduction rule value and go to
SPRO Time man- Time data rec - Absences - Absence Cat - Abs counting - rules for counting (new) - deduction rules for abs quotas and check the quota type in here.
If there is a quota assignment in place, before creating an IT2001 you need to create a IT2006 for that specific time period.
Or, you need to delete the quota assignment via two config steps mentioned above.
Regards,
Dilek

Getting error while creating condition type in SPRO

Hi ,
can somebdy tell me why i am getting the following error while creating condition type in SPRO
No valid change license available for message /sapcnd/
and also while rule determination using condition type we are getting the following error.
system error:system cannot read the structure for table
reg
venkat

Hi Venkat,
Do you have the error number code!?
Regards,
Michel Bohn

Error while creating a record in a custom infotype

hi to all experts,
I have created a infotype with 3 screens . But one of the screen im getting this error while saving a record .The Required screen change cannot be made.

Im defining using the table pa9005 not the structure p9005
(is it the same)
Please help me ....
Edited by: mohammed abdul hai on Sep 18, 2009 8:20 AM

Use of Condition update while creating Condition Records

Hi Experts,
I have to maintain MRP for a product which will be applicable for only 1 particular order. after which system should pick up old MRP.
By using CONDITION UPDATE feature , i have tried to do it , but once maintained , its always picking new MRP for every order.
(If it being a record where only new price to be defaulted in one order and no need to create 2nd order , this is ok ., but not in my case)
Can any one suggest me how to go with this
Thanks in advance,
Jignesh

Hi,
This can be done using the CONDITION UPDATE
In the condition type check the CONDITION UPDATE AND SAVE IT
While creating the CONDITION RECORDS, maintain the values and click ont he ADDITIONAL DATA (F7) then maintain the value in the field MAXIMUM NUMBER OF ORDERS , PUT The sales order as 1.
Then try
Please revert if you need further details
thanks,
santosh

Error while uploading conditions records in MEK1

Hi All,
I have a code that updates condition records in MEK1 from an excel sheet. The no of records in an excel sheet can go up to 60 k records. If i try to upload 5000 records, the coditions records are saved successfully. But then, if I try to upload 10000 records i get a error saying " Condition blocked by user " . On debugging I found out that the user id is mine. That is, same id as the person who is trying to upload records. The transaction is not open in any window as well.
My question is, why do we encounter this error and is there any limit to number of records that can be uploaded at a time in MEK1?
Thanks in advance,
Sapna

Hi Rao,
For blocking you can commit in intevals or you can use wait command but it will take extra time but your records will update in one go,when a condition record is created,then after you try to update for same material or plant thats the reason its blocking,you can either use wait or adjust your excel files and avoid duplication of materials or whatever you are using in sequential manner.

Multiple (and quite too much) lines in konp while creating condition record

Hi,
i'm trying to create a webdypro application to maintain prices and conditions for materials.
Therefore I'm using the FM RV_CONDITION_COPY.
If I create a condition (i.e. with Condtype ZPR0) the FM creates many lines in KONP for every other condition maintained (Z***) in customizing. Any ideas ?
Is there perhaps another way to create conditions ?
The FM MUST be working dark !!!
Big Thanks

Hi
U can try to use the BAPI BAPI_PRICES_CONDITIONS
Max

Error while creating a quotation in SD

i am creating a quotation referring an inquiry of type ZINO and the quotation type is ZQTO. while saving the doc i am getting a error
Pricing error: Mandatory condition ZQOE is missing.
I am not able to fix it kindly help asap.
Nikhil

Hi Nikhil,
U check for which condition type U have created condition record in VK11.
Also check for the table while creating condition record (fields in condition table)
Check once while manually entering the value for the condition in sales order, If it works.....create condition record for the same combination in VK11.
Regards,
Praveen.

Getting ORA-20001: Address_Cannot_be_Primary error while creating US Global

Dear All,
I am getting ORA-20001: Address_Cannot_be_Primary error while creating address record of address type US global.
While analyzing the PYUPIP trace, I found the following piece of the code is causing issue:
File : /* $Header: peusaddlh.pkb 120.0.12010000.2 2010/05/08 09:10:25 lbodired noship $ */
Package : APPS.PER_US_ADD_LEG_HOOK.CREATE_US_ADDRESS
Code check :
IF (p_style <> 'US'
AND P_PRIMARY_FLAG = 'Y'
AND csr_emp_assign%FOUND) THEN
close csr_emp_assign;
hr_utility.set_message (800, 'Address_Cannot_be_Primary');
hr_utility.raise_error;
END IF;
It seems that while applying this check the case of the US Global address style is not taken care.
It has struck the address conversion, as all the records of my client has the address style US Global.
Please suggest how it will effect if for the time being I do following code changes in the seeded package(I know it is not recommened, but can not wait for the patch).
1. Comment the whole check
2. Replace the above code with the follwoing code :
IF (p_style not in ('US','US_GLB')
AND P_PRIMARY_FLAG = 'Y'
AND csr_emp_assign%FOUND) THEN
close csr_emp_assign;
hr_utility.set_message (800, 'Address_Cannot_be_Primary');
hr_utility.raise_error;
END IF;
Looking for the prompt reply.
regards
Devender Yadav

Dear All,
Oracle has supplied the patch 9902020 for the fix of the issue.
Now the payroll install check condition is also added in the check.
Code in the check is now like this :
IF (p_style <> 'US'
AND P_PRIMARY_FLAG = 'Y'
AND csr_emp_assign%FOUND
AND hr_general.chk_product_installed('801') = 'TRUE') THEN
close csr_emp_assign;
hr_utility.set_message (800, 'Address_Cannot_be_Primary');
hr_utility.raise_error;
END IF;
As my client has not installed the payroll, so the fix will work for us.
Thanks to all of you for your replies.
Regards
Devender Yadav

Error While Creating Date type condition query

Hi All,
I am getting following error while creating a multiple condition query.
ERROR:java.lang.IllegalArgumentException: Unexpected field type for D: java.lang.String
I am pasting the scrap of the code for review below.
pls note after removing the condition cond6; it works fine, and cond6 is for date type field.
for(int j=1;j<7;j++){
fd[j] =trd.getFieldDescriptor(arrayHeaderFieldNames[j]);
BasisFieldType bft1 = fd[j].getFieldType();
if (bft1 == BasisFieldType.C) {
filterOperator[j] = RelationalOperatorType.CONTAINS; }
else{
filterOperator[j] = RelationalOperatorType.EQUALS;
order[j] =queryFactory.createSortOrder(fd[j],true);
cond1 =queryFactory.createCondition(fd[1], filterOperator[1], values[0]);
cond2 =queryFactory.createCondition(fd[2], filterOperator[2], values[1]);
cond3 =queryFactory.createCondition(fd[3], filterOperator[3], values[2]);
cond4 =queryFactory.createCondition(fd[4], filterOperator[4], values[3]);
cond5 =queryFactory.createCondition(fd[5], filterOperator[5], values[4]);
cond6 =queryFactory.createCondition(fd[6], filterOperator[6], values[5]);
Condition cond = queryFactory.createCondition(new Condition[]{cond1,cond2,cond3,cond4,cond5,cond6},LogicalOperatorType.AND);
Please Help!
Thanks n regards,
Kapoorchand.

Hi,
well that problem is a long time back -. I only have in mind that the date I had to transfer to the quesry was in a "strange" format. Have a lock into the documentation for the date field - your date field is not recognised as a date field from the quesry engine and so this fails - but unfortunately I have no idea at the moment how I fixed it last time - how I converted my date field......
Sorry, thast I can not give you the real point - but I will have a lock into the old code - hopefully I find it soon.
Regards,
Oliver

ESS: Error while creating Family/Dependents record from portal

Hi All,
I'm getting a critical error while creating family members and dependents record from portal.
CRITICAL ERROR
"Type conflict in the ASSIGN statement in the program CL_HRPA_CONVERT_0021_US=======CP ., error key: RFC_ERROR_SYSTEM_FAILURE"
I checked the short dump in R/3 Side and searched for OSS note and didnt find any. I raised an OSS message.
If any had've already comeacross this, pls let me know.
System Details
EP 6.0 SP15
ESS Business Package BPERP4ESS0_0
ESS Support Package ESS10P_2-10002965, PCUIGP010P_1-20000568
Thanks
Karthik

Hello Karthik:
I'm getting the same error:
"critical error while creating family members and dependents record from portal.
Type conflict in the ASSIGN statement in the program CL_HRPA_CONVERT_0021_US=======CP ., error key: RFC_ERROR_SYSTEM_FAILURE"
Maybe you can help me solving this problem.
I appreciate your help.
Thanks in advance.

Error while creating table

Hi,
I am getting an error while creating a table,
create table cs_temp_xml_data as select rowid RW_ID, value(d).getClobVal() xml_value FROM cs_tmp_wcl_xml_data p,table(xmlsequence(extract(p.xml_data,'/records/record'))) d ;
Here cs_tmp_wcl_xml_data contains a data of 600 mb in oracle directory
ORA-04030: out of process memory when trying to allocate 4000 bytes (qmxlu subheap,qmemNextBuf:alloc)
Can anyone help me out regarding this error?

check out metalink doc: 543239.996
also bug 3436395.

Error while creating the DWH tables using DAC

Hi,
I am getting error while creating the DWH tables using DAC. I have created a ODBC DSN using merant driver with DAC repository DB credentials and the test connection is successful. And while creating the tables i gave the olap dw credentials and the DSN name which i created earlier. But it throws the error as below:
Please find the below mentioned error message
=====================================
STD OUTPUT
=====================================
CREATING SIEBEL DATABASE OBJECTS
F:\DAC\bifoundation\dac\UTILITIES\BIN\DDLIMP /I N /s N /u infdomain /p ******* /c DB_DAC /G "SSE_ROLE" /f F:\DAC\bifoundation\dac/conf/sqlgen/ctl-file/oracle_bi_dw.ctl /b "" /K "" /X "" /W N
Error while importing Siebel database schema.
=====================================
ERROR OUTPUT
=====================================
Siebel Enterprise Applications ODBC DDL Import Utility, Version 7.7 [18030] ENU
Copyright (c) 2001 Siebel Systems, Inc. All rights reserved.
This software is the property of Siebel Systems, Inc., 2207 Bridgepointe Parkway,
San Mateo, CA 94404.
User agrees that any use of this software is governed by: (1) the applicable
user limitations and other terms and conditions of the license agreement which
has been entered into with Siebel Systems or its authorized distributors; and
(2) the proprietary and restricted rights notices included in this software.
WARNING: THIS COMPUTER PROGRAM IS PROTECTED BY U.S. AND INTERNATIONAL LAW.
UNAUTHORIZED REPRODUCTION, DISTRIBUTION OR USE OF THIS PROGRAM, OR ANY PORTION
OF IT, MAY RESULT IN SEVERE CIVIL AND CRIMINAL PENALTIES, AND WILL BE
PROSECUTED TO THE MAXIMUM EXTENT POSSIBLE UNDER THE LAW.
If you have received this software in error, please notify Siebel Systems
immediately at (650) 295-5000.
F:\DAC\bifoundation\dac\UTILITIES\BIN\DDLIMP /I N /s N /u infdomain /p ***** /c DB_DAC /G SSE_ROLE /f F:\DAC\bifoundation\dac/conf/sqlgen/ctl-file/oracle_bi_dw.ctl /b /K /X /W N
Connecting to the database...
28000: [DataDirect][ODBC Oracle driver][Oracle]ORA-01017: invalid username/password; logon denied
Unable to connect to the database...
any help is appreciated.
Thanks,
RM

The fact that you are getting an "ORA-01017: invalid username/password; logon denied" message indicates that you are at least talking to the database.
The log shows that username "infdomain" is being used. Can you double check the username and password you have in DAC in a SQL*Plus/SQL Developer session?
Please mark if useful/helpful,
Andy.

Error while creating new projects using api

Hello,
I am having error while creating projects using standard api, PA_PROJECT_PUB.CREATE_PROJECTS. The error I am having is as follow.
Source template ID is invalid.
===
My code is as follow:
SET SERVEROUTPUT ON SIZE 1000000
SET VERIFY OFF
define no=&amg_number
DECLARE
-- Variables used to initialize the session
l_user_id NUMBER;
l_responsibility_id NUMBER;
cursor get_key_members is
select person_id, project_role_type, rownum
from pa_project_players
where project_id = 1;
-- Counter variables
a NUMBER := 0;
m NUMBER := 0;
-- Variables needed for API standard parameters
l_commit VARCHAR2(1) := 'F';
l_init_msg_list VARCHAR2(1) := 'T';
l_api_version_number NUMBER :=1.0;
l_return_status VARCHAR2(1);
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
-- Variables used specifically in error message retrieval
l_encoded VARCHAR2(1) := 'F';
l_data VARCHAR2(2000);
l_msg_index NUMBER;
l_msg_index_out NUMBER;
-- Variables needed for Oracle Project specific parameters
-- Input variables
l_pm_product_code VARCHAR2(30);
l_project_in pa_project_pub.project_in_rec_type;
l_key_members pa_project_pub.project_role_tbl_type;
l_class_categories pa_project_pub.class_category_tbl_type;
l_tasks_in pa_project_pub.task_in_tbl_type;
-- Record variables for loading table variables above
l_key_member_rec pa_project_pub.project_role_rec_type;
l_class_category_rec pa_project_pub.class_category_rec_type;
l_task_rec pa_project_pub.task_in_rec_type;
-- Output variables
l_workflow_started VARCHAR2(100);
l_project_out pa_project_pub.project_out_rec_type;
l_tasks_out pa_project_pub.task_out_tbl_type;
-- Exception to call messag handlers if API returns an error.
API_ERROR EXCEPTION;
BEGIN
-- Initialize the session with my user id and Projects, Vision Serves (USA0
-- responsibility:
select user_id into l_user_id
from fnd_user
where user_name = 'SSHAH';
select responsibility_id into l_responsibility_id
from fnd_responsibility_tl
where responsibility_name = 'Projects Implementation Superuser';
pa_interface_utils_pub.set_global_info(
p_api_version_number => l_api_version_number,
p_responsibility_id => l_responsibility_id,
p_user_id => l_user_id,
p_msg_count => l_msg_count,
p_msg_data => l_msg_data,
p_return_status => l_return_status);
if l_return_status != 'S' then
raise API_ERROR;
end if;
-- Provide values for input variables
-- L_PM_PRODUCT_CODE: These are stored in pa_lookups and can be defined
-- by the user. In this case we select a pre-defined one.
select lookup_code into l_pm_product_code
from pa_lookups
where lookup_type = 'PM_PRODUCT_CODE'
and meaning = 'Conversion';
-- L_PROJECT_IN: We have to provide values for all required elements
-- of this record (see p 5-13, 5-14 for the definition of the record).
-- Customers will normally select this information from some external
-- source
l_project_in.pm_project_reference := 'AGL-AMG Project &no';
l_project_in.project_name := 'AGL-AMG Project &no';
l_project_in.created_from_project_id := 1;
l_project_in.carrying_out_organization_id := 2864; /*Cons. West*/
l_project_in.project_status_code := 'UNAPPROVED';
l_project_in.start_date := '01-JAN-11';
l_project_in.completion_date := '31-DEC-11';
l_project_in.description := 'Trying Hard';
l_project_in.project_relationship_code := 'Primary';
-- L_KEY_MEMBERS: To load the key member table we load individual
-- key member records and assign them to the key member table. In
-- the example below I am selecting all of the key member setup
-- from an existing project with 4 key members ('EE-Proj-01'):
for km in get_key_members loop
-- Get the next record and load into key members record:
l_key_member_rec.person_id := km.person_id;
l_key_member_rec.project_role_type := km.project_role_type;
-- Assign this record to the table (array)
l_key_members(km.rownum) := l_key_member_rec;
end loop;
-- L_CLASS_CATEGORIES: commented out below should fix the error we get
-- because the template does not have an assigment for the mandatory class
-- 'BAS Test'
l_class_category_rec.class_category := 'Product';
l_class_category_rec.class_code := 'Non-classified';
-- Assign the record to the table (array)
l_class_categories(1) := l_class_category_rec;
-- L_TASKS_IN: We will load in a single task and a subtask providing only
-- the basic fields (see pp. 5-16,5-17,5-18 for the definition of
-- the task record)
l_task_rec.pm_task_reference := '1';
l_task_rec.pa_task_number := '1';
l_task_rec.task_name := 'Construction';
l_task_rec.pm_parent_task_reference := '' ;
l_task_rec.task_description := 'Plant function';
-- Assign the top task to the table.
l_taskS_in(1) := l_task_rec;
-- Assign values for the sub task
l_task_rec.pm_task_reference := '1.1';
l_task_rec.pa_task_number := '1.1';
l_task_rec.task_name := 'Brick laying';
l_task_rec.pm_parent_task_reference := '1' ;
l_task_rec.task_description := 'Plant building';
-- Assign the subtask to the task table.
l_tasks_in(2) := l_task_rec;
-- All inputs are assigned, so call the API:
pa_project_pub.create_project
(p_api_version_number => l_api_version_number,
p_commit => l_commit,
p_init_msg_list => l_init_msg_list,
p_msg_count => l_msg_count,
p_msg_data => l_msg_data,
p_return_status => l_return_status,
p_workflow_started => l_workflow_started,
p_pm_product_code => l_pm_product_code,
p_project_in => l_project_in,
p_project_out => l_project_out,
p_key_members => l_key_members,
p_class_categories => l_class_categories,
p_tasks_in => l_tasks_in,
p_tasks_out => l_tasks_out);
-- Check the return status, if it is not success, then raise message handling
-- exception.
IF l_return_status != 'S' THEN
dbms_output.put_line('Msg_count: '||to_char(l_msg_count));
dbms_output.put_line('Error: ret status: '||l_return_status);
RAISE API_ERROR;
END IF;
-- perform manual commit since p_commit was set to False.
COMMIT;
--HANDLE EXCEPTIONS
EXCEPTION
WHEN API_ERROR THEN
FOR i IN 1..l_msg_count LOOP
pa_interface_utils_pub.get_messages(
p_msg_count => l_msg_count,
p_encoded => l_encoded,
p_msg_index => i,
p_msg_data => l_msg_data,
p_data => l_data,
p_msg_index_out => l_msg_index_out);
dbms_output.put_line('ERROR: '||to_char(l_msg_index_out)||': '||l_data);
END LOOP;
rollback;
WHEN OTHERS THEN
dbms_output.put_line('Error: '||sqlerrm);
FOR i IN 1..l_msg_count LOOP
pa_interface_utils_pub.get_messages(
p_msg_count => l_msg_count,
p_encoded => l_encoded,
p_msg_index => i,
p_msg_data => l_msg_data,
p_data => l_data,
p_msg_index_out => l_msg_index_out);
dbms_output.put_line('ERROR: '||to_char(l_msg_index_out)||': '||l_data);
END LOOP;
rollback;
END;
===
Msg_count: 1
Error: ret status: E
ERROR: 1: Project: 'AGL-AMG Project 1123'
Source template ID is invalid.
PL/SQL procedure successfully completed.

I was using a custom Application, which had a id other then 275 (which belongs to Oracle projects)

Error while creating condition record in qc15?

Similar Messages

Maybe you are looking for