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

Similar Messages

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

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

Parsing error while working with BPM

My scenario is File-RFC. Getting the response back from RFC function module (Using BPM sync-Async Bridge).
In SXMB_MONI I am getting this following error:
"PARSING" - "GENERAL"
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: Expecting a tag to begin with '<' instead of '2', in "R><RETURN>2345678903"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
My Input file structure is :
<?xml version="1.0" encoding="UTF-8"?>
<ns6:MT_GetFlatFile xmlns:ns6="http://sap.com/xi/XI/GMPOC_SYNC_RFC">
<HEADER_DESCRIPTION>DESCRIPTIONDESCRIPTIONDESCRIPTIONDESCRIPTION</HEADER_DESCRIPTION>
<PROJ_ESTIM_NO>9875670980</PROJ_ESTIM_NO>
<VENDOR_NO>2345678903</VENDOR_NO>
</ns6:MT_GetFlatFile>
I have made a change in RFC and once again imported the same to XI. But still I am getting this error .
Kindly help me in solving this problem.
Thanks and Regards,
Chary

Hi,
get your original message source from SXMB_MONI
(right click - view source ) then paste your message to your message mapping (Test Tab) in the Integration Repository
test your mapping and check if it's ok
Regards,
michal

Error While working with 2 hierarchy

Hi Experts - While working with 2 hierarchy variable and 2 node variables my webi report not returing any data.
But in RSRT i got data... Where could be a problem.
Any Inputs.

Sure - Ingo. One more behaviour i checked.Sequence of fetching the obj. in Webi.
for example - i have node variables on gl account and cost center both.
if in webi first i fetch gl accnt and then cost center then node variable is working on the object which i fetch later , here its means it works on cost center. But As i select any node from GL all data go vanish...
Actually selection of one node at a time from either hierarchy is working but If i select two nodes from two diffrent hierarchy it always fails.
so if i select one node from cost center and one from GL not working.
Here is MDX when i select both the nodes from two hierarchy - which fails.
SELECT { [Measures].[4GW5A7EF38T3R9YP5WSPWMT0Z] } ON COLUMNS , NON EMPTY CROSSJOIN( { Descendants( [0GL_ACCOUNT ZPLA].[LEVEL00].MEMBERS, [0GL_ACCOUNT ZPLA].[LEVEL07], LEAVES) } , { Descendants( [0COSTCENTER 1000CC_LOBLAW].[LEVEL00].MEMBERS, [0COSTCENTER 1000CC_LOBLAW].[LEVEL06], LEAVES) } ) DIMENSION PROPERTIES MEMBER_CAPTION ON ROWS FROM [0CCA_M20/ZCCA_M20_Q0007] SAP VARIABLES [!V000001] INCLUDING [0GL_ACCOUNT ZPLA] [!V000002] INCLUDING [0GL_ACCOUNT ZPLA].[ZPLA 0HIER_NODE] [!V000003] INCLUDING [0COSTCENTER 1000CC_LOBLAW] [!V000004] INCLUDING [0COSTCENTER 1000CC_LOBLAW].[1000CC_LOBLAW 0HIER_NODE]
Here is a MDX which run sucessfully when i select one node from one hierarchy -
SELECT { [Measures].[4GW5A7EF38T3R9YP5WSPWMT0Z] } ON COLUMNS , NON EMPTY CROSSJOIN( { Descendants( [0GL_ACCOUNT ZPLA].[LEVEL00].MEMBERS, [0GL_ACCOUNT ZPLA].[LEVEL07], LEAVES) } , { Descendants( [0COSTCENTER 1000CC_LOBLAW].[LEVEL00].MEMBERS, [0COSTCENTER 1000CC_LOBLAW].[LEVEL06], LEAVES) } ) DIMENSION PROPERTIES MEMBER_CAPTION ON ROWS FROM [0CCA_M20/ZCCA_M20_Q0007] SAP VARIABLES [!V000001] INCLUDING [0GL_ACCOUNT ZPLA] [!V000003] INCLUDING [0COSTCENTER 1000CC_LOBLAW] [!V000004] INCLUDING [0COSTCENTER 1000CC_LOBLAW].[1000CC_LOBLAW 0HIER_NODE]

Limit errors while working with multiple connections

I'm currently evaluating SQL Developer and I'm looking particularly for functionnalities that permit to distinct clearly several connections, so as to avoid DBA errors when working with several connections in parallel.
Currently it seems that SQL Developer provide these features :
- folders organization in the explorer --> for example we can create one folder per environnement (DEV, ...).
- connection name --> each user can define its own name. These aliases are then shown in main window title and tabs when opening a connection.
These features ar quite limited when comparing with a tool like Toad, which permit to associate colors to connections (good feature!) or define custom fields. Moreover database user is not shown into the SQL Developer interface, unless we add it into the connection name...
Do you know if it is planned to improve these features in following SQL developer releases ?
Or,if not, would it be possible to develop rapidly a plugin that can provide it? (especially concerning connections colors)
Thanks.

OK I found a feature request that exactly corresponds to mine : [http://htmldb.oracle.com/pls/otn/f?p=42626:39:8190796679950913::NO::P39_ID:3881]
But this request is 2 years old and was apparently rejected. Can I submit again a similar request?
And do you know if it would be possible to add this feature by developing a custom plug-in?
I mean: do SQL Developer plug-in extension mechanism allow us to extend the "connection preferences" wizard, and GUI?
Thanks

OIM 11g error while creating users on screen

Hi All,
while creating the users in OIM on screen following error is thrown in the web console.
An error occurred while performing create user operation. An error occurred while executing the kernel event handler.
please find the OIM server logs below.
<Connection for pool "oimOperationsDB" closed.>
####<Sep 5, 2012 11:22:30 AM IST> <Info> <Health> <blr-idm-app01.wipro.com> <oim_server1> <weblogic.GCMonitor> <<anonymous>> <> <4c00c82b0a97856d:-1e040449:1399130671f:-8000-000000000000008f> <1346824350538> <BEA-310002> <16% of the total memory in the server is free>
<Connection for pool "mds-oim" closed.>
<Connection for pool "mds-owsm" closed.>
<Connection for pool "oimJMSStoreDS" closed.>
<Created "1" resources for pool "mds-owsm", out of which "1" are available and "0" are unavailable.>
<Created "1" resources for pool "mds-oim", out of which "1" are available and "0" are unavailable.>
Thanks,
Power.

You can increase the connection pool size for data source "oimOperationsDB" through Web-logic Admin console.
See if you still get error then the issue is not with connection pool .

Error while Adding field on Screen Variant

Hi SAP Gurus,
I want to add one field Trading partner in Fast entry screen.
I am getting below error message while adding one field Trading Partner in Screen Variant ES007(O7E6)
FIELD instruction for field BSEG-VBUND missing on template screen
Message no. F4171
Please let me know where do I have to maintain Trading partner field in template screen.
A quick response on this is highly appreciate.
Regards,
SATVIR SINGH
Edited by: Satvir S Digwa on Oct 6, 2010 12:41 PM

Hi
Go through the below link:
Re: Trading partner in Field Status Group
Rgds
Vani

Access denied errors while working with RoboHelp Explorer

We get strange errors sometimes when we're working with
RoboHelp Explorer. We recently upgraded to RoboHelp 6.0, and since
then, these errors started appearing.
When compiling a project, or saving, or even just browsing to
a new section in the existing Word files (using the RoboHelp
Explorer), this message appears "Saving could not be completed
because of a sharing violation error" (roughly translated from the
Swedish message "Det gick inte att slutföra Spara på
grund av ett filtillståndsfel (c:\...\Mallar\Robohelp.dot)").
When we log out and log in again, it works fine for a while,
but then the message reappears after a while.
Any ideas? The user in question is running this from a
Terminal Services server.

Welcome to the forum.
RH is designed to be installed on and run from the user's PC.
Indeed the licence requires that it is installed with the user's
logon and that the user has admin rights. See the topic about
installation on my site.
Ordinarily I would say the problem was to do with running it
from a Terminal Services Server as presumably those requirements
had not been met but it looks like you had it running OK before.
Thus I am a bit puzzled. Maybe something I have said will remind of
how you installed it before?
Also projects must normally be run from the user's local
drive. Network projects often give problems as RH was not designed
to work that way.
Does the OS language need to be set to English? Not sure if
that would be an issue.
Sorry I cannot give you anything specific and hope you are
able to resolve it.

Getting Login error while working with User Management

Hi,
I am new to EBS and learning to work with 'User Management'.
I have EBS 11i installed on XP.
I face following error message when try to open any screen in 'User Management' responsibility...
*'This type of function cant be performed without logging into E-Business Suite Home Page'....*
This error is strange for me because i login with SYSADMIN and then choose 'User Management' responsibility.
Thanks in advance for any helpful hint.
Regards,
Sohail.

Hi,
I face following error message when try to open any screen in 'User Management' responsibility...
*'This type of function cant be performed without logging into E-Business Suite Home Page'....*Please mention the navigation path to reproduce the issue.
Also, please check Apache log files for any errors.
This error is strange for me because i login with SYSADMIN and then choose 'User Management' responsibility.Please see (How to to Define an Application User That Has All The Priviledges in User Management Responsibility options As SYSADMIN User [ID 378262.1]).
Thanks,
Hussein

Few errors while working with Oracle 9i developer suite.

I am facing a few errors working with Oracle 9i developer suite.
1. while running forms we have to press "ctrl +F11" to execute a query.
is there any other way of executing a query where the user can do it at a click of button or so? and similarly some way of canceling a query?
2. how can we run parameterized reports thru a menu in forms?
3. i had run a query which fetched around 15 records which were populated in 10 text boxes. i cud scroll down to see the records, with the keys but was not able to scroll back up. how can this be avoided or some way thru which we can scroll?
4. can sessions be created in Oracle forms?
5. the security feature thru menu roles is not proving efficient. can some1 suggest some way of achieving this user access control?
hope some 1 can answer my queries soon

1) execute query in windows is F8, yours is unix. Change the resource-file. You find them in <forms-home>. fmrweb.res is the standard. Save a copy. Copy then the fmrpcweb.res into fmrweb.res. That's all.
2) start in the menu with an execute_trigger ('UN_MY_REPORT_CALL') a forms-level-trigger in your form. Then you can interact with your report-objects.
3) page down + up are the keys to scroll. maybe the solution is 1)
4) yeah, implicit with open_form (... new_session...) but what do you need ?
5) write your own mechanism. say first, which features do you need
Gerd

Error while working in MIGO screen.

Similar Messages

Maybe you are looking for