Error while working on 'Material Classification'

Hello Guys
I was working on creating a generic datasource using t-code CTBW (material classification technique). And i got the following error:
Object type is not a sheet type in the class type
Diagnosis
A class type with several object types can have several object
hierarchies. All characteristics for objects that are not end node
objects are usually multi-value.
System Response
Multi-value characteristics cannot be extracted.
How do i resolve this error?
Thanks.
Srini.

Any suggestions, guyz??

Similar Messages

Recieving ORA-01722 invalid number error while creating a materialized view

Hi,
I am receiving a ORA-01722 invalid number error while creating a materialized view. when run the select statement of the view i don't get any error, but when i use the same select statement to create a materialized view i receive this error. Could any please help in resolving this error. Here is the code i am using to create a materialized view.
CREATE MATERIALIZED VIEW MV_EBS_CH_CLOSED
REFRESH FORCE ON DEMAND
AS
SELECT DISTINCT kr.request_id, org.org_unit_name,
ebs_ch_ticket_type (kr.request_id) ticket_type,
DECODE
(kr.status_code,
'CLOSED_SUCCESS', kr.last_update_date,
'IN_PROGRESS', (SELECT MAX (start_time)
FROM ebs_ch_datastore ecd1
WHERE kr.request_id = ecd1.request_id
AND workflow_step_name =
'Final BA Review and Deployment Exit Criteria')
) closed_date,
substr(krhd.visible_parameter12,1,10) siebel_start_date,
kr.creation_date itg_start_date
FROM kcrt_requests kr,
kcrt_request_types krt,
kcrt_req_header_details krhd, kcrt_request_details krd1,
(SELECT koum.user_id user_id,
DECODE (koup.org_unit_name,
'IT Implementations', 'CHS - Service Management BA',
koup.org_unit_name
) org_unit_name
FROM krsc_org_unit_members koum, krsc_org_units koup
WHERE 1 = 1
AND 'Y' = koup.enabled_flag
AND koum.org_unit_id = koup.org_unit_id
AND EXISTS (
SELECT 'X'
FROM krsc_org_units kouc
WHERE koup.org_unit_id = kouc.org_unit_id
START WITH kouc.parent_org_unit_id =
ANY (SELECT org_unit_id
FROM krsc_org_units krsc_org_units1
WHERE 'Clearinghouse' =
org_unit_name)
CONNECT BY kouc.parent_org_unit_id =
PRIOR kouc.org_unit_id)
UNION
SELECT kou.manager_id user_id,
DECODE
(kou.org_unit_name,
'IT Implementations', 'CHS - Service Management BA',
kou.org_unit_name
) org_unit_name
FROM krsc_org_units kou
WHERE 'Y' = kou.enabled_flag
START WITH kou.parent_org_unit_id =
(SELECT org_unit_id
FROM krsc_org_units krsc_org_units2
WHERE 'Clearinghouse' = org_unit_name)
CONNECT BY kou.parent_org_unit_id = PRIOR kou.org_unit_id) org
WHERE krt.request_type_id = kr.request_type_id
AND krt.request_type_name IN ('Bug Fix', 'IT Enhancement')
and kr.REQUEST_ID = krd1.request_id
and krd1.batch_number = 1
AND kr.request_id = krhd.request_id
AND org.user_id in (krd1.parameter4, krd1.parameter5, krd1.parameter7)
AND ( 'CLOSED_SUCCESS' = kr.status_code
OR 'IN_PROGRESS' = kr.status_code
AND kr.request_id IN (
SELECT request_id
FROM (SELECT DISTINCT request_id,
MAX
(start_time)
closed_date
FROM ebs_ch_datastore
WHERE 'Final BA Review and Deployment Exit Criteria' =
workflow_step_name
GROUP BY request_id))
Thanks,
Shaik Mohiuddin

This error occurs when you try to create a materialized view , but if you run the sql the results are perfectly fine. Well it happend to me also and to fix this I made sure all the coulmns have the same data type which are used in joins or in where clause.
use
where
to_number(col1)=to_number(col2) and to_number(col3)=to_number(col4)
hope this helps..

Error while working samba through Windows XP+SP2

Subject: Error while working samba through Windows XP+SP2
Hi,
I have problem with SAMBA Server on SOLARIS 10.0 while browsing shares through MS Windows XP Pro + SP2.
Descriptions:
1) SAMBA Configuration:
#==== global settings ======
[global]
security = user
hosts allow = 192.168.9. 200.0.0. 127. 127.0.0.1
unix password sync = yes
remote announce = 200.0.0.255/Workgroup
192.168.9.255/workgroup
remote browse sync = 200.0.0.255 192.168.9.255
restrict anonymous = yes
root directory = %H
deadtime = 5
#==== shares ======
[homes]
comment = Directory for User: %U
browseable = no
writable = yes
[%U]
comment = Private Directory for User: %U, R.Host: %m
path = %H
valid users = %U
browseable = yes
read only = no
profile acls = yes
[temp]
comment = Temporary file space
path = /tmp
read only = no
public = yes
2) This configuration tested with MS Windows 2000 family and Windows XP Pro+SP2
When I'm going to browse server by windows family stations, server asked for username/password, after authentication on both clients (Win XP and Win 2000) the share list appears correctly. for browsing shares contents through windows 2000 I have no problem but when i want to browse shares contents with windows xp+sp2 error message appears with "Access denied." subject.
How can I solve this problem?
Any help would be greatly appreciate.
M.Chitsaz

UPDATE
i was able to connect and synced songs yesterday.
but when i tried it again today. i cant connect again.
i tried to disconnect and reconnect million times and i even dropped
my iPOD and now it has some scratch and i hate it.

JVM error while working on flex

Hi,
Getting following error while working on flex:
JVM terminated. Exit code=1
C:\Program Files\Adobe\Flex Builder 3\jre\bin\javaw.exe
-Xms128m
-Xmx512m
-XX:MaxPermSize=256m
-XX:PermSize=64m
-Djava.net.preferIPv4Stack=true
-jar C:\Program Files\Adobe\Flex Builder 3\startup.jar
-os win32
-ws win32
-arch x86
-launcher C:\Program Files\Adobe\Flex Builder 3\FlexBuilder.exe
-name FlexBuilder
-showsplash 600
-exitdata 520_54
-vm C:\Program Files\Adobe\Flex Builder 3\jre\bin\javaw.exe
-vmargs
-Xms128m
-Xmx512m
-XX:MaxPermSize=256m
-XX:PermSize=64m
-Djava.net.preferIPv4Stack=true
-jar C:\Program Files\Adobe\Flex Builder 3\startup.jar
Its terminated my flex builder without any notice.
Need help to resolve
Thanks

Hi :
I also used to get the same error , Use the below command it will solve ur issues.
export ANT_OPTS="-Xmx900m -XX:MaxPermSize=900m"
Thanks,
Staish

While working in Material Master, Before exporting to Excel need to know the count of listed items in SQVI Reporting

While working in Material Master, Before exporting to Excel need to know the count of listed items in SQVI Reporting

Major documentation is at https://service.sap.com/installmdm.
In the "Installation" section, you can find information about predefined object models (e.g. Product, Business Partner). For "Vendor" information, please check under "Previous Releases (ZIP Files) > MDM 5.5 (SP03) Installation Guides > SAP ERP-MDM Field Mapping and Check Tables.xls.

Error while cancelling the material document.

HI,
while cancellation of material document thru MIGO screen getting error
Deficit of PU IR quantity 20.000 EA
Message no. M7021
Diagnosis
Shortfall below the specified stock level or quantity amounting to 20.000 EA.
Diagnosis
Shortfall below the specified stock level or quantity amounting to 20.000 EA.
The invoice of material document has been process thru ERS.....so no way we can cancel the invoice.
waht is the exact process to cancel this document which furher use ERS for invoice verification.
thanks.....

Hi Ayaan,
You need to set the indicator against the movement type 102 under the following path :
SPRO>Materials Management>Inventory Management and Physical Inventory>Goods Receipt>For GR-Based IV, Reversal of GR Despite Invoice
Once set , try reversing the material document . This will work .
Regards
Ramesh Ch

Error while creating 2nd Material Receipt after reversal of 1st MR

Dear,
Facing an error while creating Material Receipt.
The gate entry of this material is 123456789.
The 1st MR was created on 10/02/2011 & no. was 12345 with Location ABC via Z T-code.
Under Quality this product was Rejected with Location XYZ.
Due to Material was Rejected in Quality this MR 12345 was reversed through MB01 which produced a Reversal number 67890.
Now the material is again on its original Location ABC.
Now when the user is again creating an MR on 17/03/2011 of this material present at ABC location via using Z T-code it is producing an error stating that M/R already processed against 123456789 gate entry.
We have done these several cases before also and there was no error shown when we created the 2nd MR for the same material after its reversal has been made.

Dear,
Problem solved.
The problem was in PO.
The person had unchecked the GR-basediv which caused the real trouble. The MR number was not appearing in MB03 & material was rejected in the QA11 so it was reversed through MB01.
When again the MR was being punched then it was stating that the "MR already processed for the Gate Entry."
PO was changed, Bill No. was changed by adding "A" & later deleting this "A" from Table level.

Error while creating a material using Bapi_material_savedata

Hi,
there is an error encountered while creating a material using BAPI_MATERIAL_SAVEDATA..
The Error description is " Material description is not transfered " even after supplying the Material description and other mandatory field information like industrial sector, material type ,basic view indicator,Base UOM,Base UOM ISO code.
Please let me know the solution, if you know.

Hi,
Please search the SCN for the answers
https://www.sdn.sap.com/irj/scn/advancedsearch?query=errorinBAPI_MATERIAL_SAVEDATA+&cat=sdn_all

Error while working in NetWeaver studio

Hi all,
While working in NetWeaver studio i am getting the following error.
"A SWT error has occured"
It is recommended to exit the workbench
Subsequent errors may happen and may terminate the workbench with out warning
See error log for more details
Exit Workspace "
Followed by Yes and No buttons
So the workbench is getting closed and interrupting my work.
Can anyone plz help me out
Regards
Padma N

Hi Padma,
There is one folder named .metadata it is in uour workspace.
1. Close your NWDS.
2. copy .metadata folder from your workspace to somewhere else.
3. delete .metadata folder from your workspace.
4. start your NWDS.
this process will start configuring your NWDS from initial level.

Error while working with OracleApps Adapter please help mee

<bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>1086</code>
</part><part name="summary"><summary>file:/F:/product/10.1.3.1/OracleAS_2/bpel/domains/test/tmp/.bpel_RepairOrder_1.0_4bac0e828ef344d37656722b167615db.tmp/CreateRepairOrder.wsdl [ CreateRepairOrder_ptt::CreateRepairOrder(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'CreateRepairOrder' failed due to: Error while trying to prepare and execute an API.
An error occurred while preparing and executing the APPS.XX_BPEL_CREATEREPAIRORDER.CSD_REPAIRS_PUB$CREATE_REPAIR API. Cause: java.sql.SQLException: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
[Caused by: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
; nested exception is:
     ORABPEL-11811
Error while trying to prepare and execute an API.
An error occurred while preparing and executing the APPS.XX_BPEL_CREATEREPAIRORDER.CSD_REPAIRS_PUB$CREATE_REPAIR API. Cause: java.sql.SQLException: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
[Caused by: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
Check to ensure that the API is defined in the database and that the parameters match the signature of the API. Contact oracle support if error is not fixable.
</summary>
</part><part name="detail"><detail>
Internal Exception: java.sql.SQLException: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
Error Code: 1086</detail>
</part></bindingFault>

create or replace
PACKAGE BODY CSD_REPAIRS_PUB as
/* $Header: csdpdrab.pls 120.12 2006/09/05 11:57:18 vparvath noship $ */
* This is the public interface for the Depot Repair API. It allows
* execution of various Depot Repair APIs.
* @rep:scope public
* @rep:product CSD
* @rep:displayname Depot Repair APIs
* @rep:lifecycle active
* @rep:category BUSINESS_ENTITY CSD_REPAIR_ORDER
-- Package name : CSD_REPAIRS_PUB
-- Purpose : This package contains the public APIs for creating
-- and updating repair orders.
-- History :
-- Version Date Name Description
-- 115.0 11/17/99 pkdas Created.
-- 115.1 12/18/99 pkdas
-- 115.2 01/04/00 pkdas
-- 115.3 02/09/00 pkdas Added p_REPAIR_LINE_ID as IN parameter in the
-- Create_Repairs procedure.
-- Added p_REPAIR_NUMBER as OUT parameter in the
-- Create_Repairs procedure.
-- 115.4 02/29/00 pkdas Changed the procedure name
-- Create_Repairs -> Create_Repair_Order
-- Update_Repairs -> Update_Repair_Order
-- Added p_validation_level to Create_Repair_Order and
-- Update_Repair_Order
-- NOTE :
G_PKG_NAME CONSTANT VARCHAR2(30) := 'CSD_REPAIRS_PUB';
G_FILE_NAME CONSTANT VARCHAR2(12) := 'csdpdrab.pls';
g_debug NUMBER := csd_gen_utility_pvt.g_debug_level;
* Create Repair Order
* @param P_Api_Version_Number api version number
* @param P_Init_Msg_List initial the message stack, default to false
* @param P_Commit to decide whether to commit the transaction or not, default to false
* @param p_validation_level validation level, default to full level
* @param p_repair_line_id repair line id is unique id
* @param P_REPLN_Rec repiar line record
* @param p_create_default_logistics flag to create logistics lines, default to N
* @param X_REPAIR_LINE_ID repair line id of the created repair order
* @param X_REPAIR_NUMBER repair number of the created repair order which display on Depot UI
* @param X_Return_Status return status
* @param X_Msg_Count return message count
* @param X_Msg_Data return message data
* @rep:scope public
* @rep:lifecycle active
* @rep:displayname Create Repair Order
PROCEDURE Create_Repair_Order(P_Api_Version_Number IN NUMBER,
P_Init_Msg_List IN VARCHAR2 := FND_API.G_FALSE,
P_Commit IN VARCHAR2 := FND_API.G_FALSE,
p_validation_level IN NUMBER := FND_API.G_VALID_LEVEL_FULL,
P_REPAIR_LINE_ID IN NUMBER := FND_API.G_MISS_NUM,
P_REPLN_Rec IN CSD_REPAIRS_PUB.REPLN_Rec_Type,
p_create_default_logistics IN VARCHAR2 := 'N',
X_REPAIR_LINE_ID OUT NOCOPY NUMBER,
X_REPAIR_NUMBER OUT NOCOPY VARCHAR2,
X_Return_Status OUT NOCOPY VARCHAR2,
X_Msg_Count OUT NOCOPY NUMBER,
X_Msg_Data OUT NOCOPY VARCHAR2) IS
l_api_name CONSTANT VARCHAR2(30) := 'Create_Repair_Order';
l_api_version_number CONSTANT NUMBER := 1.0;
BEGIN
-- Standard Start of API savepoint
SAVEPOINT CREATE_REPAIR_ORDER_PUB;
-- Standard call to check for call compatibility.
IF NOT FND_API.Compatible_API_Call(l_api_version_number,
p_api_version_number,
l_api_name,
G_PKG_NAME)
THEN
RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
END IF;
-- Initialize message list if p_init_msg_list is set to TRUE.
IF FND_API.to_Boolean(p_init_msg_list)
THEN
FND_MSG_PUB.initialize;
END IF;
-- Initialize API return status to success
x_return_status := FND_API.G_RET_STS_SUCCESS;
-- API body
CSD_REPAIRS_PVT.Create_Repair_Order(P_Api_Version_Number => 1.0,
P_Init_Msg_List => p_init_msg_list,
P_Commit => p_commit,
P_Validation_Level => p_validation_level,
P_REPAIR_LINE_ID => p_REPAIR_LINE_ID,
P_REPLN_Rec => p_REPLN_Rec,
X_REPAIR_LINE_ID => x_REPAIR_LINE_ID,
X_REPAIR_NUMBER => x_REPAIR_NUMBER,
X_Return_Status => x_return_status,
X_Msg_Count => x_msg_count,
X_Msg_Data => x_msg_data);
-- Check return status from the above procedure call
IF not (x_return_status = FND_API.G_RET_STS_SUCCESS)
then
ROLLBACK TO CREATE_REPAIR_ORDER_PUB;
return;
END IF;
IF (P_CREATE_DEFAULT_LOGISTICS = 'Y') THEN
CSD_LOGISTICS_PVT.Create_Default_Logistics
( p_api_version => P_Api_Version_Number,
p_commit => P_Commit,
p_init_msg_list => P_Init_Msg_List,
p_validation_level => p_validation_level,
p_repair_line_id => P_REPAIR_LINE_ID,
x_return_status => X_Return_Status,
x_msg_count => X_Msg_Count,
x_msg_data => X_Msg_Data
IF NOT(x_return_status = FND_API.G_RET_STS_SUCCESS) THEN
RAISE FND_API.G_EXC_ERROR;
END IF;
END IF;
-- End of API body.
-- Standard check for p_commit
IF FND_API.to_Boolean(p_commit)
THEN
COMMIT WORK;
END IF;
-- Standard call to get message count and if count is 1, get message info.
FND_MSG_PUB.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
EXCEPTION
WHEN FND_API.G_EXC_ERROR THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,-------------------------------line 144 error
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => FND_MSG_PUB.G_MSG_LVL_ERROR,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
WHEN FND_API.G_EXC_UNEXPECTED_ERROR THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => FND_MSG_PUB.G_MSG_LVL_UNEXP_ERROR,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
WHEN OTHERS THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => JTF_PLSQL_API.G_EXC_OTHERS,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
End Create_Repair_Order;
PROCEDURE Update_Repair_Order(P_Api_Version_Number IN NUMBER,
P_Init_Msg_List IN VARCHAR2 := FND_API.G_FALSE,
P_Commit IN VARCHAR2 := FND_API.G_FALSE,
p_validation_level IN NUMBER := FND_API.G_VALID_LEVEL_FULL,
p_REPAIR_LINE_ID IN NUMBER,
P_REPLN_Rec IN OUT NOCOPY CSD_REPAIRS_PUB.REPLN_Rec_Type,
X_Return_Status OUT NOCOPY VARCHAR2,
X_Msg_Count OUT NOCOPY NUMBER,
X_Msg_Data OUT NOCOPY VARCHAR2) IS
l_api_name CONSTANT VARCHAR2(30) := 'Update_Repair_Order';
l_api_version_number CONSTANT NUMBER := 1.0;
BEGIN
-- Standard Start of API savepoint
SAVEPOINT UPDATE_REPAIR_ORDER_PUB;
-- Standard call to check for call compatibility.
IF NOT FND_API.Compatible_API_Call(l_api_version_number,
p_api_version_number,
l_api_name,
G_PKG_NAME)
THEN
RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
END IF;
-- Initialize message list if p_init_msg_list is set to TRUE.
IF FND_API.to_Boolean(p_init_msg_list)
THEN
FND_MSG_PUB.initialize;
END IF;
-- Initialize API return status to SUCCESS
x_return_status := FND_API.G_RET_STS_SUCCESS;
-- API body
CSD_repairs_PVT.Update_Repair_Order(P_Api_Version_Number => 1.0,
P_Init_Msg_List => p_init_msg_list,
P_Commit => p_commit,
P_Validation_Level => p_validation_level,
p_REPAIR_LINE_ID => p_repair_line_id,
P_REPLN_Rec => p_REPLN_Rec,
X_Return_Status => x_return_status,
X_Msg_Count => x_msg_count,
X_Msg_Data => x_msg_data);
-- Check return status from the above procedure call
IF not (x_return_status = FND_API.G_RET_STS_SUCCESS)
then
ROLLBACK TO UPDATE_REPAIR_ORDER_PUB;
return;
END IF;
-- End of API body.
-- Standard check for p_commit
IF FND_API.to_Boolean(p_commit)
THEN
COMMIT WORK;
END IF;
-- Standard call to get message count and if count is 1, get message info.
FND_MSG_PUB.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
EXCEPTION
WHEN FND_API.G_EXC_ERROR THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => FND_MSG_PUB.G_MSG_LVL_ERROR,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
WHEN FND_API.G_EXC_UNEXPECTED_ERROR THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => FND_MSG_PUB.G_MSG_LVL_UNEXP_ERROR,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
WHEN OTHERS THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => JTF_PLSQL_API.G_EXC_OTHERS,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
End Update_Repair_Order;
-- R12 Development Begin
* Update Repair Order Status
* @param P_Api_Version api version number
* @param P_Commit to decide whether to commit the transaction or not, default to false
* @param P_Init_Msg_List initial the message stack, default to false
* @param X_Return_Status return status
* @param X_Msg_Count return message count
* @param X_Msg_Data return message data
* @param P_Repair_status_rec repair status attributes record.
* @param P_status_upd_control_rec repair status record control flags.
* @param X_OBJECT_VERSION_NUMBER
* @rep:scope public
* @rep:lifecycle active
* @rep:displayname Update Repair Order Status
PROCEDURE Update_Ro_Status(P_Api_Version IN NUMBER,
P_Commit IN VARCHAR2,
P_Init_Msg_List IN VARCHAR2,
X_Return_Status OUT NOCOPY VARCHAR2,
X_Msg_Count OUT NOCOPY NUMBER,
X_Msg_Data OUT NOCOPY VARCHAR2,
P_REPAIR_STATUS_Rec IN REPAIR_STATUS_REC_TYPE,
P_STATUS_UPD_CONTROL_REC IN STATUS_UPD_CONTROL_REC_TYPE,
X_OBJECT_VERSION_NUMBER OUT NOCOPY NUMBER) IS
l_api_name CONSTANT VARCHAR2(30) := 'Update_Ro_Status';
l_api_version_number CONSTANT NUMBER := 1.0;
     l_msg_data varchar2(2000);
     l_msg_index_out NUMBER;
BEGIN
-- Standard Start of API savepoint
SAVEPOINT UPDATE_RO_STATUS_PUB;
-- Initialize message list if p_init_msg_list is set to TRUE.
IF FND_API.to_Boolean(p_init_msg_list)
THEN
FND_MSG_PUB.initialize;
END IF;
-- Initialize API return status to success
x_return_status := FND_API.G_RET_STS_SUCCESS;
-- API body
CSD_REPAIRS_PVT.UPDATE_RO_STATUS(P_Api_Version => p_api_version,
P_Commit => p_commit,
P_Init_Msg_List => p_init_msg_list,
P_Validation_Level => FND_API.G_VALID_LEVEL_FULL,
X_Return_Status => x_return_status,
X_Msg_Count => x_msg_count,
X_Msg_Data => x_msg_data,
P_REPAIR_STATUS_REC => p_repair_status_rec,
P_STATUS_CONTROL_REC => p_status_upd_control_rec,
X_OBJECT_VERSION_NUMBER => x_object_Version_number);
-- Check return status from the above procedure call
IF not (x_return_status = FND_API.G_RET_STS_SUCCESS)
then
ROLLBACK TO UPDATE_RO_STATUS_PUB;
return;
END IF;
-- End of API body.
-- Standard check for p_commit
IF FND_API.to_Boolean(p_commit)
THEN
COMMIT WORK;
END IF;
-- Standard call to get message count and if count is 1, get message info.
FND_MSG_PUB.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
     if(x_msg_count > 1) then
          FOR l_index IN 1 .. x_msg_count
          LOOP
          fnd_msg_pub.get (p_msg_index => l_index,
                    p_encoded => fnd_api.g_false,
                    p_data => l_msg_data,
                    p_msg_index_out => l_msg_index_out
          x_msg_data := x_msg_data ||'['||l_msg_data||']';
          END LOOP;
     end if;
EXCEPTION
WHEN Fnd_Api.G_EXC_ERROR THEN
x_return_status := Fnd_Api.G_RET_STS_ERROR;
ROLLBACK TO UPDATE_RO_STATUS_PUB;
Fnd_Msg_Pub.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
IF (Fnd_Log.level_error >= Fnd_Log.g_current_runtime_level)
THEN
Fnd_Log.STRING(Fnd_Log.level_error,
'csd.plsql.CSD_REPAIRS_PUB.Update_ro_status',
'EXC_ERROR[' || x_msg_data || ']');
END IF;
     if(x_msg_count > 1) then
          FOR l_index IN 1 .. x_msg_count
          LOOP
          fnd_msg_pub.get (p_msg_index => l_index,
                    p_encoded => fnd_api.g_false,
                    p_data => l_msg_data,
                    p_msg_index_out => l_msg_index_out
          x_msg_data := x_msg_data ||'['||l_msg_data||']';
          END LOOP;
     end if;
WHEN Fnd_Api.G_EXC_UNEXPECTED_ERROR THEN
x_return_status := Fnd_Api.G_RET_STS_UNEXP_ERROR;
ROLLBACK TO UPDATE_RO_STATUS_PUB;
Fnd_Msg_Pub.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
IF (Fnd_Log.level_exception >= Fnd_Log.g_current_runtime_level)
THEN
Fnd_Log.STRING(Fnd_Log.level_exception,
'csd.plsql.CSD_REPAIRS_PUB.Update_ro_status',
'EXC_UNEXP_ERROR[' || x_msg_data || ']');
END IF;
     if(x_msg_count > 1) then
          FOR l_index IN 1 .. x_msg_count
          LOOP
          fnd_msg_pub.get (p_msg_index => l_index,
                    p_encoded => fnd_api.g_false,
                    p_data => l_msg_data,
                    p_msg_index_out => l_msg_index_out
          x_msg_data := x_msg_data ||'['||l_msg_data||']';
          END LOOP;
     end if;
WHEN OTHERS THEN
x_return_status := Fnd_Api.G_RET_STS_UNEXP_ERROR;
Rollback TO UPDATE_RO_STATUS_PUB;
IF Fnd_Msg_Pub.Check_Msg_Level(Fnd_Msg_Pub.G_MSG_LVL_UNEXP_ERROR)
THEN
Fnd_Msg_Pub.Add_Exc_Msg(G_PKG_NAME, l_api_name);
END IF;
Fnd_Msg_Pub.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
IF (Fnd_Log.level_exception >= Fnd_Log.g_current_runtime_level)
THEN
Fnd_Log.STRING(Fnd_Log.level_exception,
'csd.plsql.CSD_REPAIRS_PUB.Update_ro_status',
'SQL MEssage[' || SQLERRM || ']');
END IF;
     if(x_msg_count > 1) then
          FOR l_index IN 1 .. x_msg_count
          LOOP
          fnd_msg_pub.get (p_msg_index => l_index,
                    p_encoded => fnd_api.g_false,
                    p_data => l_msg_data,
                    p_msg_index_out => l_msg_index_out
          x_msg_data := x_msg_data ||'['||l_msg_data||']';
          END LOOP;
     end if;
End Update_ro_status;
-- R12 Development End
End CSD_REPAIRS_PUB;
Plzz checkout help me out

Error while cancelling the material document. MIGO

i am getting following error while cancelling material document
You cannot cancel GR, since inspection lot is already partly posted
Message no. QA046
Diagnosis
You are attempting to reverse a goods receipt although quantity postings have already been made from the inspection lot. This means that stock for the goods receipt has already been transferred and, for this reason, a cancelation of the document is no longer possible.
Procedure
Ensure that the postings in QM (within the usage decision transactions) are carried out.

hi,
You can't do cancellation here just because you have given some lot/qty to QI:
2 ways:
1. Don't do cancellation, make returns for the rest of the qty...
2. Take back the qty in the Unrestrcited stock back and then try to do cancellations...
Regards
Priyanka.P

Error while working and saving .PDF files from Illustrator CS 5.1

One of my partners has been facing issues while working with Adobe Illustrator PDF Files, especially while saving them. We've lost so many hours of work with these errors. We own an early 2009 iMac (MB418LL/A) running OS X Mountain Lion (10.8.5). You can see the specs in this link:
iMac "Core 2 Duo" 2.66 24-Inch (Early 2009) Specs (Early 2009, MB418LL/A, iMac9,1, A1225, 2267) @ EveryMac.com.
She works with vectors and images, most of the time. At the moment, working on a Letter sheet sized magazine. Any help would be appreciated. Thanks in advance.
This is the error shown: http://txs.io/Xnrb

Alvin,
Just to make sure: Where are you/is she saving?
Here it is always recommended to open/save AI documents from/to own harddisk, and to only copy from/to externals such as local server/whatever.
The reason is that with the latter, AI files tend to get corrupted sooner or later, so you may be lucky for a while but it hurts when your luck runs out.

Buffer table not up-to-date error while working with local SRM PO

Hi all,
We are working in SRM 7.0 with extended classic scenario.
I faced an issue while working with local SRM PO. Iam getting a dump while doing changes in SRM PO.
Dump says that "Buffer table not up-to-date". Please find the detail dump error below :
http://cscgsapndc34.nwk.amer.csc.com:8114/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
UNCAUGHT_EXCEPTION
Buffer table not up-to-date
Function: BBP_PD_ABORT of program SAPLBBP_PDH
Form: ABORT of program SAPLBBP_PDACC
Form: ACCOUNT_INTERNAL_SAVE of program SAPLBBP_PDACC
Function: BBP_ACCOUNT_INTERNAL_SAVE of program SAPLBBP_PDACC
Form: PROCDOC_INTERNAL_SAVE of program SAPLBBP_PD
Form: STATUS_SET_AND_INTERNAL_SAVE of program SAPLBBP_PD
Form: PROCDOC_UPDATE of program SAPLBBP_PD
Function: BBP_PROCDOC_UPDATE of program SAPLBBP_PD
Method: /SAPSRM/IF_PDO_UPDATE_BUFFER~SUBMIT of program /SAPSRM/CL_PDO_UPDATE_BUFF_PO=CP
Method: /SAPSRM/IF_PDO_BASE~SUBMIT_UPDATE of program /SAPSRM/CL_PDO_BASE===========CP
http://cscgsapndc34.nwk.amer.csc.com:8114/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
If anyone of you already came across this type of dump error can you please let me know what might be the possible reasons for the same . Request your kind help in this regard.
Thanks in advance.
Regards,
Kalyani

There could be many issues..
or some data issue.
can you recreate the same issue you can fix it.
it could only one incident so you should thoroghly check what piece of data is wrong.
what actions are you doing in the purchase order.
Note 1580496 - Purchase order Buffer table not upto date dump in change ver
Symptom
1.Create a change version on any Purchase order.
2. Edit quantity of any item
3. Dont press 'Enter key'
4. Clickk on Order button.
Application gves dump 'Buffer table not upto date'
but it is very difficult to say what is the issue. request your technical resource to look your dump.
if you recreate the issue half of the problem resolved.

Error while Change of material Type

Hi,
I have one material and the same material is present in our 3 company code and plant, the materila TYpe is HALB anf I want to change it to FG but while changing with MMAM first it was giving error that valuated stock is avalable then I have issue the material now my stock is zero but still it giving error that many PO exist and Porduction order exist, for the HALB valuation class is 2000 and for FG it is 3000,
How this probelm can be solve.
regards,
zafar

Hi,
While changing the Material Type, following points needs to be confirmed :-
1. There should be no stock against the materials. If there will be any stock against the materials, then u will have to nullify the stock for the materials.
2. There should be no open documents against the materials like PO, PR etc. In case if any open documents, same needs to be closed.
3. Also there should be no open reservation order against the materials.

Error while working in MIGO screen.

Dear Members,
I am encountering an error, while trying to receive goods in MIGO, Here are the list of screen shots regarding the error. Kindly assist me to correct the mistake to correctly make the MIGO.
Kindly let me know any supporting or configuration document, so i can check and correct the mistakes.
1.
2.
3.
4.
Kindly assist me on this asap.
Regards : Karthikeya

Hi,
The accounting entry at the time of MIGO is
Raw Mateial account dr
to GR/IR Clearing account
For Raw materials or inventory transaction key is BSX and GR/IR Clearing is WRX.once you please check the combition of (WSCA BSX US01) whether the G/L is assigned if not please assign.then relogon to the MIGO Screen then it will allow
Regards
Chakri

Error while working on 'Material Classification'

Similar Messages

Maybe you are looking for