Procedure for update ACS 5.4.0.46.0a with cumulutative patch in large deployment

Hi,
I try to find the info within the CCO website but fail.
All docs I found on the site is Upgrading for 5.3 to 5.4 or 5.4 to 5.5
In my case I would like just apply cumulutative patch to my existing 5.4 running deployment.
5.4.0.46.0a to 5.4.0.46.6
My main concern is I use a large deployment scenario with multiple secondary server and one log collector.
The upgrade procedure mention, de-register all server one by one and change the log collector to be a standalone primary server.
Which cause me more downtime, loss of some logs, ...
For applying patch (update not upgrade), I think I can just use the pacth procedure and leave the setup as it is as I don't upgrade or change the database structure.
Update each server whenever the role he as (secondary, primary, log collector) one by one by just issue the :"acs patch install" command.
Does anyone have a advise or a past experience about update large deployment setup.
Thanks for your help.
Steve

Hi Minakshi,
I perform the update before your post and I test without deregister all server.
So far, all was good.
I had no issue and the update tooks me very less time without following the full UPGRADE procedure.
The command had also a rollback for the update, so I take the risk.
This is certainly not the case for upgrade but update seems to easier.
Kind regards.
Steve

Similar Messages

Update my app. What is the correct procedure for updating an app/folio?

I designed a folio in Indesign CS6 and created an app of the folio in adobe dps and succesfully uploaded it to the app store. Now I want to update my app. What is the correct procedure for updating an app/folio?

no, just update your content and recreate the Single Edition App. Your certificate should still be valid so there is not need to recreate these.
... your App ID absolutely need to be the exact same one you used for the first version if you want to make sure this is an update.

How to write a procedure for update the table

Hi all
can any body please tell me how to write a procedure to update the table......
I have a table with about 10,000 records...........Now I have add a new column and I want to add values for that like
registration Code Creidits
13213 BBA
1232 MCS
I had add the creidit now i want to update the table.........the new value want to get by SQL like
Creidit = select creidit from othere_table...........
Hope u can understand my problem
Thanks in advance
Regards
Shayan
[email protected]

Please try the following --
update Program_reg a
set TotalCreidit = ( select tot_cr <Accroding to your logic>
                            from Program_reg b
                            where a.Registration = b.Registration
                            and    a.Enrollment = b.Enrollment
                            and    a.code = b.code
where a.Registration in ( select distinct Registration
                                    from Program_reg );
N.B.: Not Tested....
Regards.
Satyaki De.

Stored Procedure - for update of commit problem

HI all,
I am getting an ORA-01002 error when rnning my stored procedure. I understnad this is because i am "commiting" when using a "For update of". But I am not sure how to commit or rollback this transaction. The procedure is below.

oraCraft wrote:
Do you know any way I can clean the code?Depends what's wrong with it. If you are getting the message 'Sorry, this content is not allowed' then there is a word blocked by the forum software (like 'discount').
If it doesn't display at all, then it may be to do with HTML. For example, posting <tt><></tt> is tricky.

What is Procedure for OPC Sever to communicate LabVIEW 7.1 with PLC (Any Make)

we want to use OPC Sever to communicate LabVIEW 7.1 with PLC (Any Make).Can someone tell what is the procedure for the same and how to configure the OPC Server?

Hey Sugam,
Did you try to look into de Developer Zone in NI? Here are some Articles that could help you to get started:
1. Tools for Troubleshooting OPC Interface Problems:
http://zone.ni.com/devzone/conceptd.nsf/webmain/401CB3A4E216356286256BC7004B5831
2. Accessing Remote OPC Server Using DataSocket: http://zone.ni.com/devzone/conceptd.nsf/webmain/D5DC903EC6F9320A862569EE007FEC7D
3. Connecting LabVIEW to an OPC Server through a DataSocket Connection: http://zone.ni.com/devzone/conceptd.nsf/webmain/DF8C0A4BA2E2B22A86256A3700592BEA
In short, you have to make your OPC server to run in your machine (you have to look into the documentation from the other manufacturer), and be familiar with NI Server Explorer (article 1 above helps with that) and you have to access the tag with datasocket or Tags (LabVIEW DSC). If you had LabVIEW 8, we introduced the concept of variables and you could configure the variable to access this tag.
Hope this gives you an idea what to do.
Barp - Control and Simulation Group - LabVIEW R&D - National Instruments

Stored Procedure for updating dynamic columns in a table

I have a table with a lot of columns around 30ish
Now I want to create a stored procedure that will update a specific column to a new value.
I the @columname and @newvalue to be the parameters, and an addition @itemId for the WHERE clause so it will update that specific row/data only.
here's my Stored Procedure
USE [db]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[usp_UpdateData]
@itemID int,
@ColumnName varchar(50),
@newValue nvarchar(50)
AS
BEGIN
Update dbo.ProjectAllocation
Set @ColumnName = @newValue
Where itemID = @itemID END
When I pass the following
@ColumnName: UserName
@newValue: NewUserName
@itemID: 1
it doesnt update row with itemID = 1.
How can I do this?
----------------------- Sharepoint Newbie

Did you try my last post method. Its better to use parameterized approach.
Anyway, if you want to change your code,you may need to change as below.....
SET @sql = 'UPDATE dbo.table SET ' + @ColumnName + '=''' + @newValue + ''' WHERE [itemID] = ' + cast(@itemID as varchar(50));

Sequence and procedure for updating records

I USED THE FOLLOWING CODE TO UPDATE THE COLUMNS
CURRT_USER_ID,
uPDATED_BY,
UPDATED_DATE
cURRT_USER_IS = SELECT USER FROM DUAL;
UPDATED_BY = CTUT_ID ;
UPDATED_DATE = SYSDATE
pROCEDURE COMPILED FINE AND TRIGGER CREATED FINE
bUT WHEN I UPDATE IT IS NOT UPDATING THE COLUMNS
CREATE OR REPLACE PROCEDURE UPD_CONSTITUENT(
CURRT_USER_ID out varchar2,UPDATED_DATE out DATE,UPDATED_BY out varchar2,CTUT_ID OUT NUMBER)
IS
puser varchar2(20);
pdate date;
pby varchar2(20);
pid number;
x_seq exception;
pragma exception_init(x_seq, -8004);
BEGIN
SELECT USER,SYSDATE INTO puser,pdate from dual;
CURRT_USER_ID := puser;
UPDATED_DATE := Pdate;
UPDATED_BY := ctut_id;
EXCEPTION WHEN x_seq THEN
RAISE_APPLICATION_ERROR(-8004, 'MY_SEQ has run out of numbers!');
END UPD_CONSTITUENT;
CREATE TRIGGER TU_CONSTITUENT
BEFORE INSERT ON K_CONSTITUENT FOR EACH ROW
BEGIN
UPD_CONSTITUENT(:NEW.CURRT_USER_ID,:NEW.UPDATED_DATE,:NEW.UPDATED_BY,:NEW.CTUT_ID);
END TU_CONSTITUENT;

IT WORKED FOR ME
i GAVE INSERT INSTEAD OF UPDATE

Procedure for update

hi all. Can you tell me what's wrong with my procedure? I got error: encountered create while expected another..
create or replace procedure p1 is
BEGIN
create table Documents(documentID , Sum) as
(select InvoiceName , TotalPrice from Invoices
union all
select TransferName, Sum from Payments)
create table EntrySum(EntryNumber,Sum) as
(select EntryNumber,Sum
from Entries e left outer join Documents d
on e.Document=d.DocumentID)
Update Entries e
Set EntrySum=(select es.Sum
from EntrySum es
where e.EntryNumber=es.EntryNumber)
drop table Documents,EntrySum;
END

Let's backtrack here. Why are you creating temp tables? For what purpose? Note that Oracle's concurrency is based on MVCC - multi-version concurrency control.
In simplest terms - readers do not block other readers and writers. And writers do not block readers, and only block other writers when vying for the very same row.
The typical use of temp tables are to work around the problem of readers blocking writers and/or writers blocking readers. This issue does not exist in Oracle. Which then begs the question why use temp tables?
The next issue is why do you create temp tables dynamically? This is also how not to use objects in Oracle.
In Oracle you define a temp table once. The CREATE statement defines the structure of the temp table. This is stored in the data dictionary. Consider it like the definition of a class in o-o terms.
And like in o-o, you can at any time instantiate an actual temp table using this "class" definition. And like an o-o object, this temp table will be automatically destroyed when your client session terminates (like a garbage collector cleanup).
Each session can instantiate its own copy of a temp table. There is no need to create it dynamically. Worse, when doing it dynamically, you do not have thread (concurrent) safe code as the 2nd copy of the code will throw an error as the temp table definition already exist in the data dictionary.
Never mind the issues of having to use dynamic SQL to deal with that temp table in the code.
So again - what you are showing us in this thread consistently seems to be wrong. Being wrong is not a problem.. if you fix that which is wrong. But persisting with that which seems wrong, kinds of blur the border between ignorance (curable) and stupidity (non-curable). IMO.

When is SELECT FOR UPDATE used

DB version:10gR2
Since another thread of mine on this subject didn't go well, i am starting another thread.
When exactly is SELECT..FOR UPDATE statement used? With the exception of using SELECT...FOR UPDATE in CURSOR declaration, I've rarely seen SELECT ...FOR UPDATE being used explicitlyby PL/SQL gurus in our firm. Why didn't they use SELECT..FOR UPDATE(i mean a stand alone SELECT FOR UPDATE, <em>not as a part of Cursor</em>) to lock rows before UPDATE/DELETE/INSERT in their codes?
Edited by: M.Everett on Oct 20, 2008 12:00 PM
edited the initial post to let the users know that I am refering to a stand alone SELECT FOR UPDATE statement, not the part of a cursor

M.Everett wrote:
What i gather from various sources in the Internet:
1. SELECT FOR UPDATE is used mainly on CURSORs and very rarely used as a stand alone statement (if this is not the case you would have seen SELECT FOR UPDATE statements before every UPDATEs and DELETEs in PL/SQL codes)
2. Stand alone SELECT FOR UPDATEs are used mainly when dealing with CLOB, BLOB
Am i right in making these conclusions?1. This is probably a fair assumption.
2. Not really. SELECT FOR UPDATE is not a requirement when dealign with (C|B)LOBs.
SELECT FOR UPDATE allows an easy form of reference when you come to update rows in a cursor loop (although cursor loops should be rarely used), because rather than having to include a where condition on key columns you can just refer to the CURRENT ROW. Obviously, the main reason for using SFUs is the locking and this can become a requirement in some business environments where a user "picks up" a record to deal with and other users will then not see that record in their list or be able to select it for themselves.
;)

API/package/procedure/function for updating physical attributes in Org/Mast

I need some kind of procedure or function for updating the weight, volume, and dimensions in the organization and master items forms. We have almost 350,000 items and I want to update them in batch. Is there an API of some kind for this? I would do a simple update but I want to make sure there's no additional logic necessary (other tables that are updated during the process of updating those fields, etc).
Thanks!

here is for API's you need to check...
You can use Decimal & UOM Quantity API
These APIs are used to handle item decimal quantities:
Convert from one UOM to another
Validate quantities at input time
Validate quantities at display/output time
Quantity Comparison
Get UOM information
For your convenience, I am giving you the API as below:
/*===========================================================================+
| Copyright (c) 1999 Oracle Corporation |
| Redwood Shores, California, USA |
| All rights reserved. |
+===========================================================================*/
/*-----------------------------------------------------------------------+
|This package contains procedures relevent to item decimal quantity |
|processing. This package contains routines to: |
|(1)validate item quantities based on UOM and decimal precision rules |
|(2)validate whether the UOM controls and decimal precision rules |
| themselves are correct based on functionality planned. For reviewing|
| UOM and decimal quantity functional design details, please visit the|
| following URL: |
| "http//apps-us.oracle.com/inv/development/designs_120/ |
| decimal_precision/decimal_precision.html" |
|But here are a few basics to give background context: |
| |
| "Item Quantity" -- The item's quantity is described by the item |
| identifier, the unit of measure (e.g. grams, kilos, etc), and a |
| number value to indicate the amount in that unit of measure. |
| |
| "Unit of Measure" -- Units of measure belong to unit of measure |
| classes(e.g. weight, volume, length, etc). Each unit of measure class|
| has actual units of measure that belong to that class (e.g. the |
| weight class may have units of measures like, "grams", "kilos", etc).|
| |
| "UOM Conversion" --Users can set up conversion rates between UOMs in |
| them same UOM class, by defining conversions to the base UOM. These |
| are standard conversions. Item-level intra-class conversions may also|
| be defined. When doing intra-class conversions, item-level |
| intra-class conversions are used first if defined, and then standard |
| conversions are used. |
| Users can define inter-class conversions. Inter-class Conversions may|
| also be defined at the lot/sublot levels. For inter-class conversions|
| sublot, lot, and then item inter-class conversions will be used in |
| in order. If lot-lvel conversion is not defined, then item-level |
| conversion is used. A strict hierarchy is imposed. |
| |
| "TU" -- Trasactable Unit.A UOM may have a TU. This implies |
| that when transacting in this UOM, any item's quantities will be |
| forced to be integer multiples of this TU quantity. The TU may also |
| be declared at the item level. The TU quantity at the item level may |
| be different from the UOM level TU, and if defined, item level TU |
| takes precedance. |
| |
| "Decimal Precision"--Users have a choice of setting decimal precision|
| at the base UOM for each UOM class. All other UOMs in that class get |
| get their decimal precisions derived from the base UOM decimal |
| precision, the converison rate, and TUs, if they are |
| being used. |
| |
| |
| "Conversion Rate Tolerance" -- This is a tolerance that may be set |
| when conversion rate cannot be not strictly fixed. Example: |
| 1 Chicken = 2 pounds (plus or minus 0.7 pounds). This 0.7 pounds is |
| the conversion rate tolerance. Conversion rate tolerance is only |
| definable at inter-class UOM conversions, at item or lot/sublot level|
| |
| History |
| 04/08/99 Mansoor Jafri Created Package Spec |
| 04/26/99 Mansoor Jafri Updated with TU at 3 levels as |
| opposed to MTU at 2 and atomic at|
| UOM class level. |
| 04/29/99 Mansoor Jafri Updated document with lot/sublot |
| conversions. Also, removed |
| "atomic" as a separate control, |
| since this can |
| implemented as a TU at base UOM |
| level with an integer quantity. |
| 05/03/99 Mansoor Jafri Updated the package with sublot |
| level control. Also, changed name|
| of DTU to TU, so that it fits |
| better in the "process" market. |
| Also, conformed to BOI API stds. |
+-----------------------------------------------------------------------*/
SET VERIFY OFF
WHENEVER SQLERROR EXIT FAILURE ROLLBACK;
CREATE OR REPLACE PACKAGE inv_decimals_pub AS
/* $Header: INVDECPS.pls 118.3 99/05/03 18:12:27 mjafri noship $ */
/*--------------------------------------------------------------------------+
|Procedure validate_compare_quantities(..)
|Returns the quantity converted from the first UOM in the second UOM.
|If quantities in 2 UOMs are already available, then this procedure will
|compare and validate these quantities based on conversion rates
|and UOM and decimal qty controls. This procedure may be used to validate
|scenarios where quatities are entered in dual UOMs. We want to make sure
|quantities are valid based on conversion, TUs, and conversion
|rate tolerances.
|
|Procedure validate_and_compare(
|p_api_version_number IN NUMBER, -- version # of API
|p_init_msg_list IN VARCHAR2, -- whether to initialize list
|p_inventory_item_id IN NUMBER, -- inventory_item_id
|p_organization_id IN NUMBER, -- organization_id
|p_lot_control_code IN NUMBER, -- item's lot control code
|p_lot_number IN VARCHAR2, -- lot number
|p_sub_lot_control_code IN NUMBER, --sub lot control code
|p_sublot_number IN VARCHAR2, -- sublot number
|p_from_quantity IN NUMBER, -- qty in first UOM
|p_from_uom_code IN VARCHAR2, -- UOM of fisrt qty
|p_to_uom_code IN VARCHAR2, -- UOM of second qty
|p_to_quantity_to_check IN NUMBER, -- qty in second UOM
|x_resultant_to_quantity OUT NUMBER, -- calculated qty in second UOM
|x_comparison OUT NUMBER,--Possible values are 1,0,-1,-99
|x_msg_count OUT NUMBER, -- number of messages
|x_msg_data OUT VARCHAR2, -- populated,if msg count = 1
|x_return_status OUT VARCHAR2) -- return status
|
|Note: The comparisons are done in base UOM
| of the UOM class to which the first UOM belongs. x_comparison returns:
|-1 if from_quantity is less than to_quantity (A < B)
| 0 if from_quantity is equal to to_quantity (A = B)
| 1 if from_quantity is greater than to_quantity (A > B)
| -99 if the validations for the first/second quantity failed
| If the UOMs belong to different classes, then users can specify whether
| they want to use the effective interclass UOM conversion tolerance, say, T.
| CASE: p_use_interclass_tolerance = 1
| ------
| Q1 > Q2 if (Q1 - Q2) >= T
| Q1 = Q2 if ABS(Q1 - Q2) < T
| Q1 < Q2 if (Q1 - Q2 ) <= -T
|
|The output variable x_resultant_to_quantity will contain the converted
|quantity
|in the second UOM, using effective conversion rates.
|Usage: In a dual UOM scenario, this api will confirm whether quantities in
|the two UOMs are equal or not, based on x_comparison output variable.
+--------------------------------------------------------------------------*/
Procedure validate_compare_quantities(
p_api_version_number IN NUMBER,
p_init_msg_list IN VARCHAR2,
p_inventory_item_id IN NUMBER,
p_organization_id IN NUMBER,
p_lot_control_code IN NUMBER,
p_lot_number IN VARCHAR2,
p_sub_lot_control_code IN NUMBER,
p_sublot_number IN VARCHAR2,
p_from_quantity IN NUMBER,
p_from_uom_code IN VARCHAR2,
p_to_uom_code IN VARCHAR2,
p_to_quantity_to_check IN NUMBER,
x_resultant_to_quantity OUT NUMBER,
x_valid_conversion OUT NUMBER,
x_msg_count OUT NUMBER,
x_msg_data OUT VARCHAR2,
x_return_status OUT VARCHAR2);
/*--------------------------------------------------------------------------+
|Function convert_UOM(..) return NUMBER ;
|Returns the quantity converted from the first unit into the second unit.
|If conversion is not possible, return status is failure.
|Function convert(
|p_api_version_number IN NUMBER,
|p_init_msg_list IN VARCHAR2, -- whether to initialize list
|p_inventory_item_id IN NUMBER, -- inventory_item_id
|p_organization_id IN NUMBER, -- organization_id
|p_lot_control_code IN NUMBER, -- item's lot control code
|p_lot_number IN VARCHAR2, -- lot number
|p_sub_lot_control_code IN NUMBER,
|p_sublot_number IN VARCHAR2,
|p_from_quantity IN NUMBER, -- qty in first UOM
|p_from_uom_code IN VARCHAR2, -- UOM of fisrt qty
|p_to_uom_code IN VARCHAR2, -- UOM of second qty
|x_msg_count OUT NUMBER,
|x_msg_data OUT VARCHAR2,
|x_return_status OUT VARCHAR2)
| return NUMBER ;
|If there is an error, then -99 is returned.
|1) From_quantity must be an absolute value.
|2) From_quantity will be truncated to decimal precision in the from UOM, then
| converted to base UOM in the class,
|3) Then converted to base UOM of the
| to_UOM class,
|4) Then converted to the quantity in to_UOM,
|5) Then truncated to decimal precision of the to_UOM.
+--------------------------------------------------------------------------*/
Function convert_UOM(
p_api_version_number IN NUMBER,
p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
p_inventory_item_id IN NUMBER,
p_organization_id IN NUMBER,
p_lot_control_code IN NUMBER,
p_lot_number IN VARCHAR2,
p_sub_lot_control_code IN NUMBER,
p_sublot_number IN VARCHAR2,
p_from_quantity IN NUMBER,
p_from_uom_code IN VARCHAR2,
p_to_uom_code IN VARCHAR2,
x_msg_count OUT NUMBER,
x_msg_data OUT VARCHAR2,
x_return_status OUT VARCHAR2) return NUMBER ;
/*--------------------------------------------------------------------------+
| get_uom_properties(..)
| This procedure is used to interrogate the UOM.
| It returns:
| (1) decimal precision at the UOM level
| (2) TU, if defined, at the UOM level
| (3) Atomicity, if defined for the class that this UOM belongs to
| If some of the controls are not defined, null values are returned.
| if the UOM is not found, the return status indicates this.
| Procedure get_uom_properties(
| p_api_version_number IN NUMBER,
| p_init_msg_list IN VARCHAR2,
| p_uom_code IN VARCHAR2,
| x_decimal_precision OUT NUMBER,
| x_uom_TU OUT NUMBER,
| x_uom_class OUT VARCHAR2,
| x_msg_count OUT NUMBER,
| x_msg_data OUT VARCHAR2,
| x_return_status OUT VARCAHR2);
+--------------------------------------------------------------------------*/
Procedure get_uom_properties(
p_api_version_number IN NUMBER,
p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
p_uom_code IN VARCHAR2,
x_decimal_precision OUT NUMBER,
x_uom_TU OUT NUMBER,
x_uom_class OUT VARCHAR2,
x_msg_count OUT NUMBER,
x_msg_data OUT VARCHAR2,
x_return_status OUT VARCAHR2);
/*-------------------------------------------------------------------------+
| get_item_uom_properties(..)
| This procedure returns a specific item's primary UOM, TU, and tolerance
| Procedure get_item_uom_properties(
| p_api_version_number IN NUMBER,
| p_init_msg_list IN VARCHAR2,
| p_inventory_item_id IN NUMBER,
| p_organization_id IN NUMBER,
| p_lot_control_code IN NUMBER, -- item's lot control code
| p_lot_number IN VARCHAR2,
| p_sub_lot_control_code IN NUMBER,
| p_sublot_number IN VARCHAR2,
| x_primary_uom_code OUT VARCHAR2,
| x_uom_class OUT VARCHAR2,
| x_decimal_precision OUT NUMBER,
| x_item_TU OUT NUMBER,
| x_uom_TU OUT NUMBER,
| x_effective_TU OUT NUMBER,
| x_msg_count OUT NUMBER,
| x_msg_data OUT VARCHAR2,
| x_return_status OUT VARCHAR2 );
| If the item is not a valid one, then this is reflected through the
| return status.
+-------------------------------------------------------------------------*/
Procedure get_item_uom_properties(
p_api_version_number IN NUMBER,
p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
p_inventory_item_id IN NUMBER,
p_organization_id IN NUMBER,
p_lot_control_code IN NUMBER,
p_lot_number IN VARCHAR2,
p_sub_lot_control_code IN NUMBER,
p_sublot_number IN VARCHAR2,
x_primary_uom_code OUT VARCHAR2,
x_uom_class OUT VARCHAR2,
x_decimal_precision OUT NUMBER,
x_item_TU OUT NUMBER,
x_class_TU OUT NUMBER,
x_uom_TU OUT NUMBER,
x_effective_TU OUT NUMBER,
x_msg_count OUT NUMBER,
x_msg_data OUT VARCHAR2,
x_return_status OUT VARCHAR2 );
/*-------------------------------------------------------------------------+
| Procedure compare_quantities(..)
| Procedure compare_quantities(
| p_api_version_number IN NUMBER,
| p_init_msg_list IN VARCHAR2,
| p_inventory_item_id IN NUMBER,
| p_organization_id IN NUMBER,
| p_lot_control_code IN NUMBER,
| p_lot_number IN VARCHAR2,
| p_sub_lot_control_code IN NUMBER,
| p_sublot_number IN VARCHAR2,
| p_fisrt_qauantity IN NUMBER,
| p_first_uom IN VARCHAR2,
| p_second_quantity IN NUMBER,
| p_second_uom IN VARCHAR2,
| p_use_interclass_tolerance IN VARCHAR2, -- Yes = 1, 2 = No
| x_comaprison_result OUT NUMBER,
| x_msg_count OUT NUMBER,
| x_msg_data OUT VARCHAR2,
| x_return_status OUT VARCHAR2);
|
| This procedure compares the quantities A and B and returns result in the
| output variable x_comparison_result. The comparisons are done in base UOM
| of the UOM class to which the first UOM belongs:
|-1 if quantity A is less than quantity B (A < B)
| 0 if quantity A is equal to quantity B (A = B)
| 1 if quantity A is greater than quantity B (A > B)
| If the UOMs belong to different classes, then users can specify whether
| they want to use interclass UOM conversion tolerance, say, T.
| CASE: p_use_interclass_tolerance = 1
| ------
| Q1 > Q2 if (Q1 - Q2) >= T
| Q1 = Q2 if ABS(Q1 - Q2) < T
| Q1 < Q2 if (Q1 - Q2 ) <= -T
+------------------------------------------------------------------------*/
Procedure compare_quantities(
p_api_version_number IN NUMBER,
p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
p_inventory_item_id IN NUMBER,
p_organization_id IN NUMBER,
p_lot_control_code IN NUMBER,
p_lot_number IN VARCAHR2,
p_sub_lot_control_code IN NUMBER,
p_sublot_number IN VARCHAR2,
p_fisrt_qauantity IN NUMBER,
p_first_uom IN VARCHAR2,
p_second_quantity IN NUMBER,
p_second_uom IN VARCHAR2,
p_use_interclass_tolerance IN VARCHAR2,
x_comaprison_result OUT NUMBER,
x_msg_count OUT NUMBER,
x_msg_data OUT VARCHAR2,
x_return_status OUT VARCHAR2);
/*-----------------------------------------------------------------------+
| Procedure Validate_Quantity(
| p_api_version_number IN NUMBER,
| p_init_msg_list IN VARCHAR2,
| p_inventory_item_id IN NUMBER,
| p_organization_id IN NUMBER,
| p_lot_control_code IN NUMBER,
| p_lot_number IN VARCHAR2,
| p_sub_lot_control_code IN NUMBER,
| p_sublot_number IN VARCHAR2,
| p_input_quantity IN NUMBER,
| p_UOM_code IN VARCHAR2,
| x_msg_count OUT NUMBER,
| x_msg_data OUT VARCHAR2,
| x_return_status OUT VARCHAR2);
|
| Validates and returns the quantity in this manner (the caller does not need
| to adjust the result):
| 0. Truncate to and validate decimal precision
| 1. Validate quantity with respect to TU controls.
+-------------------------------------------------------------------------*/
Procedure Validate_Quantity(
p_api_version_number IN NUMBER,
p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
p_inventory_item_id IN NUMBER,
p_organization_id IN NUMBER,
p_lot_control_code IN NUMBER,
p_lot_number IN VARCAHR2,
p_sub_lot_control_code IN NUMBER,
p_sublot_number IN VARCHAR2,
p_input_quantity IN NUMBER,
p_UOM_code IN VARCHAR2,
x_msg_count OUT NUMBER,
x_msg_data OUT VARCHAR2,
x_return_status OUT VARCHAR2);
/*------------------------------------------------------------------------+
| Function Truncate_Quantity(
| p_api_version_number IN NUMBER,
| p_init_msg_list IN VARCHAR2,
| p_inventory_item_id IN NUMBER,
| p_organization_id IN NUMBER,
| p_lot_control_code IN NUMBER,
| p_lot_number IN VARCHAR2,
| p_sub_lot_control_code IN NUMBER,
| p_sublot_number IN VARCHAR2,
| p_input_quantity IN NUMBER,
| p_UOM_code IN VARCHAR2,
| x_msg_count OUT NUMBER,
| x_msg_data OUT VARCHAR2,
| x_return_status OUT VARCHAR2) return NUMBER;
|
| Truncates the quantity to decimal precision of the UOM.
| In case of error conditions, -99 is returned.
+------------------------------------------------------------------------*/
Function Truncate_Quantity(
p_api_version_number IN NUMBER,
p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
p_inventory_item_id IN NUMBER,
p_organization_id IN NUMBER,
p_lot_control_code IN NUMBER,
p_lot_number IN VARCHAR2,
p_sub_lot_control_code IN NUMBER,
p_sublot_number IN VARCHAR2,
p_input_quantity IN NUMBER,
p_UOM_code IN VARCHAR2,
x_msg_count OUT NUMBER,
x_msg_data OUT VARCHAR2,
x_return_status OUT VARCHAR2) return NUMBER;
* show errors package INV_DECIMALS_PUB
* SELECT to_date('SQLERROR') FROM user_errors
* WHERE name = 'INV_DECIMALS_PUB'
* AND type = 'PACKAGE';
commit;
exit;

I cannot execute an procedure in Java that is a "select ... for update" stt

I have a table with a column that has BLOB types. First I insert into that table with EMPTY_BLOB(). After I create a procedure as:
PROCEDURE file_content_select
        p_id IN NUMBER,
        p_file_content OUT BLOB
   IS
BEGIN
    SELECT f.file_content
    INTO p_file_content
    FROM files f
    WHERE f.id = p_id
    FOR UPDATE of f.file_content;
END; In my java program. I do that:
my query string:
query = ""
                    + "BEGIN FILE_CONTENT_SELECT ("
                    + id
                    + ",?); END;";and my execute query code:
callableStatement = connection.prepareCall(query);
callableStatement.registerOutParameter(1, OracleTypes.BLOB);
callableStatement.execute();
dataBlob = (BLOB) callableStatement.getObject(1);But, I seem to stop at
callableStatement.execute();where I'm wrong? Thanks for help me.

When you say, "locked" was already deselected, I take it that you mean the small icon at the bottom right of the Get Info window displayed an open lock picture.
Have you tried locking it, then unlocking it again? I expect you will be able to lock it by simply clicking on the open lock icon, but to unlock it again you will need to supply an Admin password.
Odd that DU didn't fix it. That would be my first thought also. Suggest trying it again, if you haven't already done so.
Speaking of DU, have you verified your HDD?
My Applications folder permissions read -
System          Read and Write
admin           Read and Write
everyone      Read only
Message was edited by: El Deanio

Suggested procedure for safe updating of Safari to v. 3.2

If your Safari keeps crashing, or if you are updating Safari (or just have):
N.B. Never delete Safari, never run it under Rosetta, don't use proxy settings.
(If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Safari 3.2 for download can be found here:
http://www.apple.com/safari/download/
Make sure you download the correct version for your system.
Also, observe the standard procedure for installing software: repair permissions and close all applications, install, then repair permissions again.)
Input Managers and other plug-ins from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari.
Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 used Safari 3.0.4 which was not a beta and which was updated to v.3.1.2, and now both Tiger and Leopard uses Safari 3.2. If Safari 3.2 is not the fastest browser you have ever used, then something is wrong!
(Trying to revert to a previous version of Safari can have repercussions, as Safari 3.x uses a completely different webkit on which other applications like iChat, Mail, Dashboard Widgets etc also rely, but if you really want to do this post back in a new thread for instructions on the safe way to do so.)
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Add-ons that have been frequently mentioned here, among others, for causing such problems are Piclens, Saft, AcidSearch and Pithhelmet. If you have them, trash them and go the developer's sites to see if new versions are available for Safari 3.2.
You should also ensure that you have downloaded and installed the correct version for your Mac of Security Updates up to 2008-007, which is required for Safari 3.2. Like all security updates, these require a restart and a permission repair. Note that 2008-007 is a combo update: if you have missed a couple of updates this one will suffice.
To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
• Hard Disk/Library/InputManagers
• Home/Library/InputManagers
especially prior to system updates and updates to Safari (they can always be added back one-by-one later).
Please do not respond to this post if you are having difficulties, or ask your questions in somebody else's thread, but start your own thread where your particular problem can get the full attention it deserves.

Bump.
Upgrading PithHelmet stopped my crashing.

Bios Update Procedure for Portege 7200CT

Is somebody out there have the proper procedure to update the bios of a Portege 7200CT without the docking station.
Toshiba has posted a procedure in its bulletin but it does not explain how to do the update without the docking station. As everybody knows that the Portege 7200CT has its floppy drive on the docking station and if we follow the Toshiba updating procedure we have to undock the laptop, so how can we proceed with the update if the update software calls for a floppy drive that is on default to drive A:
Hope somebody out there have something to share!!!

Hi,
My Portege 7200CT present bios version is 1.5 and the latest version that is available at Toshiba-USA website is 2.1. I have WinXP Pro SP2 on it and the problem is that the PCMCIA slot does not recognize or detect a PC Card or Cardbus that I plug on it.
I only need to know how to update the bios without the docking station. Or can I update the bios with docking station.
Thanks,

Can any one please send me an update trigger (pl/sql procedure) for ap tables(ap_suppliers,ap_supplier_site_all,and contacts)

Please send an query for update trigger for those tables .
     1: ap_suppliers
     2: ap_supplier_sites_all
     3: ap_supplier_contacts.
Thanks,
Chaitanya.

Hi,
Actually ID and Data are different names in my API. Here I mentioned like that.
Am using Oracle 10g version.
Yes I am going to get the multiple values using this Ref Cursor. The same ref cursor is used in another API of my package.
In this API, the user actually enters Application_id and data. API should insert/update the version_master table with the inputs. See application_id is the foriegn key for app_master table.
The requirement is whenever they enters application_id and data, if application_id already present in the version_master table, then the data should be updated and we should get a status flag for this using Out variable(i.e. using ref cursor only we are showing the status). if the application_id is not present in the version_master table, new record should be inserted. The sequence will generate the version_id for version_master table.
But the Merge statement is working fine for update and insert also. Problem is am unable to see the success or failure through ref cursor. I don't know how exactly I can use this.
If data is NULL the operation should be failed. i.e. I should get Failure status here. But am not getting this.
Please remove the comments here and then check. If I use the NVL2 function I was able to get the status flag, i.e. S or F.
OPEN resultset_o FOR
SELECT NVL2 (data, 'S', 'F')
FROM version_master
WHERE application_id = application_id_i;
1.How the value of data being not null will determine Success of the api and how null failure
2.If the above select statement goes in to exception when others how I will no the failure
I have to achieve the above scenarios.
Please advice me.

Windows Update for Cisco ACS appliance

Due to the recent security alert from Windows I wish to make sure my systems are updated, but the cisco ACS appiance (cisco 1113) runs a specialized version of win2k with console access disabled. Is there any way get the windows critical security updates, and do I need to?

If the patch is necessary on acs appliance then they will be releasing it soon.
As of now we can't apply any windows patch on appliance.

Procedure for update ACS 5.4.0.46.0a with cumulutative patch in large deployment

Similar Messages

Maybe you are looking for