Modify functionality of "Update Opportunity Totals"

Hi all,
We are looking to modify the functionality of the button, "Update Opportunity Totals" in the Opportunities screen.
Can you share some pointers as to where can I find the flow, and modify the same to change the fields included maybe, and/or modify the calculations in effect ?
Best Regards

Hi,
what you can do is hide the standard button and instead insert a custom button with DOM manipulation (Global Web Applet in Action Bar with onload event). Afterwards you have to Query the Revenues (js query with sso) and update the opportunity (js insert)
Best Regards
SL

Similar Messages

Update Opportunity Totals button on Opprtunity Product Revenue line items

Hello,
In our application, the sales process is managed at the product revenue level. Each product line item goes through various stages and could be in the intiall state or get cancelled as well. I need to exclude these product revenue line items while updating the Revenue amount at the Opprtunity Header. With the <Update Opportunity Totals> button, the total is updated at the header irespective of the product reveneue status. I think I need to build a custome webservice to do that.
I need to find out if the <Update Opportunity Totals> button can be made read-only or removed based on roles and priveledges.
Thanks

Robin,
You can't turn off the button, but OOTB functionality can help you manage this. In our case, we created a workflow for the Revenue Record Type. The workflow watches for changes to the status of any Opty Revenue record, via the "Before modifed record saved" trigger event. When a user changes the status of an Opportunity Product Line Item to a specified value, "Lost" in our case, the workflow automatically updates the Quantity value at the line item to 0, and the Revenue and Expected Revenue values at the Opty Product Line Item level are calculated to be zero accordingly. When the user updates the totals at the Opty level, the totals inlcude only the records that have revenue associated with them at the Opty Prod Line Item level.
I assume your requirements are similar and the same approach could be used in your case.
Good Luck,
Thom

Update Opportunity Totals - trigger this action

Is there a way to trigger the Update Opportunity Totals action (so the user does not have to click on the button)?

Does anyone know if this functionality is available yet?
I have a customer that would like to know if there is a way to automate the clicking of the "Update Opportunity Totals" button everytime someone changes the product revenue record(s). Their issue is that if a user forgets to click the Update Opportunity Totals button after making a change that the Opportunity totals will be off.
Is there any work arounds for this?
Thanks.

Add logic behind 'Update Opportunity Totals' button in Oracle CRM On Demand

HI,
I need to add custom logic behind 'Update Opportunity Totals' button in Oracle CRM On Demand. Can anyone please let me know where can I implement this logic? Where can I find already implemented code of 'Update Opportunity Totals' button.
Thanks,
RM

Pl post this in a Siebel related forum
HTH
Srini

Disable the Update Opportunity Totals

Has anyone come up with a way of disabling the "Update Opportunity Totals" button on the Opportunity Page. Without going into detail, under certain circumstances, when our users click the button we come up with incorrect totals. This is due to our implmentation and how we populate the frequency & # of periods, not Oracle.
I looked into trying to add something in the in HTML Head Additions section of the custom web applet, that would disable just this button, but could not come up with anything.
The code that is executed when the button is selected is:
<div tabindex="5" onmouseover="toggleNavButton(this);" onkeypress="onButtonPress(this);" onmouseout="toggleNavButton(this);" class="buttonChildTitleBarTD" onclick="doNavigate('\/OnDemand\/user\/OpportunityDetail?OMTGT=RevenueList&OMCR0=1-19FGQ67&OpptyDetailForm.Id=1-19FGQ67&OMRET0=OpportunityDetail%3focTitle%3dDixie%2bPAS%26OMTGT%3dOpptyDetailForm%26OMTHD%3dOpportunityDetailNav%26ocEdit%3dY%26OpptyDetailForm.Id%3d1-19FGQ67%26OCTYPE%3d%26ocTitleField%3dName&OMCBO=Opportunity&OCTYPE=&OMTHD=UpdateTotals',true, this, null);" id="ProductRevenueChildListTB28508260*1"> Update Opportunity Totals </div>
Any thoughts?

You can't remove the Update opty total button but I had a similar issue, we capture revenue in 2 fields mthly and inital setup and it wouldn't use both and send it to the Opty total so we looked at redesigning it. I have 2 new currency fields and when a record is updated it divides the initial setup by # periods and adds that figure to the monthly figure and puts it in the currency field that displays in related items. The update Opty button then works with the correct numbers. Of course this goes in right after R16 because then I can remove the original Monthly revenue field off the related items section.
cheers
Alex

Update Opportunity Totals automatic ?

Hello,
Pls. is it possible somehow to automate the "click" on the Update Opportunity Totals button in the Opp. ? There is a tendency to forget the click... and the opp. value is not up to date...
Txs.
Antonio

Antonio, this is something that is being considered in a future CRM On Demand release.

Is there any method or function to update/modify an existing trip data?

Hey, ABAP gurus,
Is there any method or function to update/modify an existing trip (PR05) receipts data and cost distribution data?
Thanks in advance!
Fisher

Hi Fisher,
Please try HRTRV_IF_MODIFY_TRIP.
Regards,
Dilek

Sum child list items and update parent total using javascript

I have a SharePoint 2010 Parent/Child list setup using a lookup field to join both the lists, this is working well.
The Parent list contains requisition requests and the child list contains related item details. Each of the related child list items has a 'Line Item Total' field. I need to aggregate the Line Item Totals in the child list and place the result in a 'Requisition
Total' in the parent. So for any given parent record the sum of it's related child 'Line Item Totals' is reflected in the 'Requisition' total in the parent row.
I am struggling with the JavaScript code below. I am trying to aggregate Line Item Totals for a given Requisition#? Could someone please review and advise?
<script language="javascript" src="/Purchasing/Documents/jquery-1.8.2.js" type="text/javascript"></script>
<script language="javascript" src="/Purchasing/Documents/jquery.SPServices-2014.01.min.js" type="text/javascript"></script>
<script>
$(document).ready(function()
$('select[title=Requisition#]').children().attr('disabled',true);
$("input[title='Old Amount']").attr("readonly","true").css('background-color','#F6F6F6');
   // Retrieve the name of the selected parent item.
   var strParent=$("select[title$='Requisition#'] :selected").text();
splist li = web.lists["ReqDetails"]; // This is the child list
    spquery q = new spquery();
    q.Query= "<Where>" +
     "<And>" +
      "<Neq>" +
       "<FieldRef Name='ID'/><Value Type='Number'>0</Value>" +
      "</Neq>" +
      "<eq>" +
       "<FieldRef Name='LinkID'/><Value Type='Number'>ReqID</Value>" +
      "</eq>" +
     "<And>" +
    "</Where>" +
    "<OrderBy>" +
     "<FieldRef Name='LineItemTotal'/>" +
    "</OrderBy>"
    q.ViewFields = string.Concat("<FieldRef Name='LineItemTotal' />");
    q.ViewFieldsOnly = true; // Fetch only the data that we need
    splistitemcollection items = li.getitems(q);
    foreach(SPListItem item in items)
    sum += parseInt(item["LineItemTotal"], 10);
  alert(sum)
</script>
Rick Rofe

I do something similar for a PO Header/PO Detail set of lists. I use SPServices to pull the data.
I put this code in the child edit page - so any time any child is edited, the parent is updated. I get all children records and total them up (except for the item I'm displaying at the current time. I add that value in directly from the form itself.
<script type="text/javascript" src="/Javascript/JQuery/JQueryMin-1.11.1.js"></script>
<script src="/Javascript/JQuery/jquery.SPServices-2014.01.min.js"></script>
<script>var poNumber = '';
var poDetailID = '';
$(document).ready(function() { var queryStringVals = $().SPServices.SPGetQueryString();
poNumber = queryStringVals["PO"];
poDetailID = queryStringVals["ID"];
function PreSaveAction() {
// update the PO header with the total of all items + shipping + adjustments
var query = "<Query><Where><And><Eq><FieldRef Name='Title' /><Value Type='Text'>" + poNumber + "</Value></Eq><Neq><FieldRef Name='ID' /><Value Type='Counter'>" + poDetailID + "</Value></Neq></And></Where></Query>";
var viewFields = '<ViewFields><FieldRef Name="Total" />';
viewFields += '</ViewFields>';
var poTotal = 0.00;
$().SPServices({
operation: "GetListItems",
async: false,
listName: "PO Details",
webURL: "/po",
CAMLViewFields: viewFields,
CAMLQuery: query,
completefunc: function (xData, Status) {
//alert(xData.responseText);
$(xData.responseXML).SPFilterNode('z:row').each(function() {
if($(this).attr("ows_Total")) {
//alert($(this).attr("ows_Total"));
poTotal += Number(parseFloat($(this).attr("ows_Total").split(";#")[1],2).toFixed(2));
// add in this changed line (we skipped it above)
var qty = $('input[title="Quantity Ordered"]').val();
var price = $('input[title="Price"]').val().replace(',','');
var extend = Number(qty)*Number(price);
poTotal += extend;
//alert(poTotal);
// update the PO Header
$().SPServices({
operation: "UpdateListItems",
async: false,
listName: "Purchase Orders",
webURL: "/po",
ID: poID,
valuepairs: [["Total", poTotal]],
completefunc: function (xData, Status) {
//alert(xData.responseText);
$(xData.responseXML).SPFilterNode('z:row').each(function() {
return true;
Robin

In Update_Opportunity_Pre error while updating opportunity status

Hello,
We are encountering an error 'In Update_Opportunity_Pre' in the log when trying to update apportunity status to a closed status using Update Opportunity API. Has anyone encountered this error before? If so, I would appreciate if you could share the fix/work around for this issue.
Thanks,
Dinakar.

Hi,
The log is as follows:
Opportunity status changes to Cancelled
..... in pel_lead_utilities.update_oppty_header
..... Error Message In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre
..... AS_OPPORTUNITY_PUB.Update_Opp_Header
..... x_return_status = E
..... Error Details = In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre
... pel_lead_utilities.update_oppty_header :: v_return_status : E
... pel_lead_utilities.update_oppty_header :: In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre In Update_Opportunity_Pre

Call function in update task empty variables error

Hello,
I'm experiencing a weird error while using the addition "In update task".
My Scenario is the following:
Use the bapi_goodsmvt_create -> if there are no errors, fill some values and call my function and then commit everything.
The problem is, when the function runs in update task, all import parameters are empty!
Also, this only happens in the following code structure
CALL METHOD run_migo( IMPORTING bapireturn = t_bapireturn).
IF t_bapireturn IS INITIAL.
CALL METHOD save_custom_tables. "this runs my function 'IN UPDATE TASK'
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
ENDIF.
if I commit inside the method SAVE_CUSTOM_TABLES, the data is passed normally to the function, if I commit like the code above, everything is empty.

Here's the code:
METHOD save_partial.
DATA: t_wegritm    LIKE gt_wegritm,
        t_tegrp_parc TYPE TABLE OF ztegrp_parc,
        w_tegrp_parc TYPE ztegrp_parc,
        w_tegrk_parc TYPE ztegrk_parc.
FIELD-SYMBOLS <w_wegritm> LIKE LINE OF t_wegritm.
t_wegritm = gt_wegritm.
DELETE t_wegritm WHERE mengee IS INITIAL.
CHECK NOT t_wegritm IS INITIAL.
*-->save xml iten
LOOP AT t_wegritm ASSIGNING <w_wegritm>.
    MOVE-CORRESPONDING <w_wegritm> TO w_tegrp_parc.
    w_tegrp_parc-id = gw_tegrk-id.
    w_tegrp_parc-gr_docto = <w_wegritm>-gr_docto.
    w_tegrp_parc-gr_mjahr = <w_wegritm>-gr_mjahr.
    w_tegrp_parc-gr_zeile = <w_wegritm>-gr_zeile.
    APPEND w_tegrp_parc TO t_tegrp_parc.
ENDLOOP.
MOVE-CORRESPONDING gw_tegrk TO w_tegrk_parc.
CALL FUNCTION 'Z_SAVE_PARTIAL'
    IN UPDATE TASK
    EXPORTING
      iw_tegrk_parc = w_tegrk_parc
    TABLES
      it_tegrp_parc = t_tegrp_parc.
ENDMETHOD.
I tried to re-create this scenario with a local class, but the code that I originally sent worked(the commit work outside of the routine).

Call function '' in update task - code inside is BDC

hi to all,
in using call function '' in update task
the code inside is bdc. is this possible?
my scenario is from VA01 then post billing to VF01,
i am using user-exit MV45AFZZ in subroutine userexit_save_document.
i need to post billing after va01 save.
thanks to all.

To debug in the update task, you have to set that option on in the debugger.
If the user exit runs in the update task, then you must have something like: CALL FUNCTION MODULE my_fm_to_do_BDC STARTING NEW TASK. ( This function module should wait until the SD is created. You might want to check in a loop, with a WAIT command. Once it is created, then you start your BDC and CALL TRANSACTION. ) This is NOT an update function module. It may need to be RFC enabled - I'm not certain at the moment.
If the user exit doesn't run in the update task, you need to create, and call from the user exit, an update function module that calls your function module "my_fm_to_do_BDC" STARTING NEW TASK.
The attribute "collective run", which is V3, means that the update task won't run that function module until a regularly scheduled job on the application server runs. For processing to run during the rest of the SD save, you must use V1 (could be run in any order with other V1s) or V2 (Will run after V1, but in any order with other V2s). Typically, I use V2 for this kind of task.
matt

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;

Debugging a function in UPDATE TASK

Hi All,
I'm debugging a function in UPDATE TASK. I have just actived the flag 'Update Debug'.
My problem is Find how the Function's parameters are passed. The function is called dynamically by a statement like this:
" PERFORM (VBFUNC) IN PROGRAM (TFDIR-PNAME) USING VBID. "
Does someone help me?
Thanks

Hi,
Your question is not clear to me.
wht I understood that you want to get the parameters passing to a function module which is dynamically called.
" PERFORM (VBFUNC) IN PROGRAM (TFDIR-PNAME) USING VBID. "
this statement is not calling any FM it is calling a subroutin which exist in TFDIR-PNAME program variable after USING stat is your parameter.
You can get the name of the form, program and the parameters if you debug at this point.
Thanks,
Anmol.

Queries on Call Function In update Task

Hi ,
I have a requirement where I have to update a ztable in background once I execute the report.THe requirement is to exceute the updation in background.Will
Call funtion in update task help me?If yes, I have never used call function in update task .so can you guide me on the same.If no, how best can I acheive this?
Thanks & Regards,
Jyotsna

Hi,
look F1 to call function pls:
It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task.
-> so in error case you can analyse err. with TA SM13
(update records)
regards Andreas

SQL Functions to Update XML Data

Hi,
Can anybody please tell me whether SQL Functions to Update XML Data (such as updateXML, insertChildXML, insertXMLbefore etc) are available with oracle 9i or not?
Please tell me.

You can also do a describe on SYS.XMLTYPE to see what methods are supported in your release. How would you find e.g. insertChildXML in DESC sys.xmltype? I suppose it is not a Method of the Type: Summary of XMLType Subprograms.

Modify functionality of "Update Opportunity Totals"

Similar Messages

Maybe you are looking for