Function to update dependent characteristic in QP02

Hello,
Is there any function or BAPI which updates dependent characteristic in QP02. I looked for some BAPIs but those are called for QP01 not for QP02.
I think this functionality is not possible through BDC also (Please correct if i am wrong).
Any help will be appreciated.
Regards,
Sunil Joyous

Hello Everyone,
I have found the new transcation for mass change of inspection plan. The transaction is CWBQM. This solves my problem.
Regards,
Sunil Joyous

Similar Messages

Dependent characteristic Updation using QP02

Hi ,
Could you please help me regarding updation of dependent characteristics in the transaction QP02.
My requirement is i will give the plant and group and material no in the first screen and i select the first entry and i will click inspection characteristics in the appl tool bar and then i will select master inspection characteristics and i have to press dependent characteristics update
to update
diameter,unit of measurment.... based on material assignment. CAn i use any BAPI for this?
I am using 'bapi_inspectionplan_create ' but it is not update.
If i am using BDC program I am facing problem with selection of line item in inspection charcterisitic based Material Inspection characteristic and
In the Dependent characteristic i am updating based on Customer Number .But how i can select the particular line item based on customer number.
If you anybody know the solution please help to me .
Regards
Nandan.

Hi,
We have more than 10000 entires its not possible using this Transaction .
Can anybody help me regarding solving my problem.
Regards
Nandan.N

Function modules or BAPI for transacction QP02

Hi to all,
Please give me solution for assignment of inspection plan through QP02 transacion. My file contains Material number,Inspection paln, Group counter, Vendor no and plant fields.
These fields are updating the MAPL through QP02. For these requirement I developed LSMW. But it is taking long time to update.
Thanks,
NAgesh.

did you try any of these ??
BAPI_INSPCHAR_GETREQUIREMENTS Load Inspection Specifications for an Inspection Lot Charac.
BAPI_INSPCHAR_GETRESULT        Load Inspection Results
BAPI_INSPCHAR_SETRESULT        Confirm Inspection Results
BAPI_INSPLOT_GETDETAIL         Load Detail Data and Usage Decision for Inspection Lot
BAPI_INSPLOT_GETLIST           Select Inspection Lots
BAPI_INSPLOT_GETOPERATIONS     Select Inspection Operations for Inspection Lots
BAPI_INSPLOT_GETSTATUS         Get Current Status Information for Inspection Lot
BAPI_INSPLOT_SETUSAGEDECISION Automatic Usage Decision
BAPI_INSPOPER_GETCHAR          Select Inspection Characteristics
BAPI_INSPOPER_GETLIST          Select Inspection Operations for Inspection Lots
BAPI_INSPPOINT_CHANGE          Change Inspection Point
BAPI_INSPPOINT_CREATEFROMDATA Create Inspection Point
BAPI_INSPPOINT_GETLIST         Select Inspection Points
BAPI_INSPPOINT_GETREQUIREMENTS Load Inspection Specifications and Inspection Points
BAPI_MATINSPCTRL_REPLICATE     Prepare Inspection Setup (Inspection Types) for Distribution
BAPI_MATINSPCTRL_SAVEREPLICA   Replication of QM Inspection Setup

Hi. i used Function module to change Characteristic values of a sales order

hi. i used Function module to change Characteristic values of a sales order..
but sales order's Characteristic values didn't change.
And the Function module doesn't occur any log message.
please tell me wrong code, and how to solve this problem.
if i have wrong method, what data can i pass to change the characteristic values
DATA: LT_E1CUVAL TYPE TABLE OF E1CUVAL.
DATA: WA_E1CUVAL TYPE E1CUVAL.
DATA: LS_CFG_HEAD LIKE CUXT_CUCFG_S,
 LS_INSTANCES LIKE CUXT_CUINS_S,
 LS_VALUES LIKE CUXT_CUVAL_S,
 LS_E1CUCFG LIKE E1CUCFG,
 LS_E1CUINS LIKE E1CUINS,
 LS_E1CUVAL LIKE E1CUVAL,
 LS_PROFILE LIKE E1CUCOM,
 LS_VBAP LIKE VBAP,
 L_CUOBJ LIKE INOB-CUOBJ,
 L_ATINN LIKE CABN-ATINN.
DATA: LT_INSTANCES LIKE CUXT_CUINS_S OCCURS 0,
 LT_PART_OF LIKE CUXT_CUPRT_S OCCURS 0,
 LT_VALUES LIKE CUXT_CUVAL_S OCCURS 0,
 LT_VAR_KEYS LIKE CUXT_CUVK_S OCCURS 0,
 LT_KSML LIKE KSML OCCURS 0 WITH HEADER LINE,
 BEGIN OF LT_CLINT OCCURS 0,
 CLINT LIKE KSSK-CLINT,
 END OF LT_CLINT.
DATA: LT_CUIB LIKE CUIB_CUOBJ_S OCCURS 0 WITH HEADER LINE.
DATA: E_ROOT_INSTANCE TYPE CUXT_INSTANCE_NO.
DATA: EV_ROOT_PERSIST_ID TYPE IBEXTINST_DATA-EXT_INST_ID.
DATA: EV_CFG_HAS_CHANGED TYPE XFELD.
DATA: EV_HANDLE_APPL_LOG TYPE BALLOGHNDL.
DATA: L_CUOBJ_NEW TYPE CUOBJ.
DATA: L_OWNER TYPE IBXX_BUSINESS_OBJECT.
REFRESH LT_E1CUVAL.
CLEAR LS_VBAP.
SELECT SINGLE CUOBJ INTO CORRESPONDING FIELDS OF LS_VBAP
 FROM VBAP WHERE VBELN = I_VBELN
 AND POSNR = I_POSNR.
IF SY-SUBRC <> 0.
 RAISE INSTANCE_NOT_FOUND.
ENDIF.
REFRESH LT_CUIB. CLEAR LT_CUIB.
LT_CUIB-INSTANCE = LS_VBAP-CUOBJ.
APPEND LT_CUIB.
CALL FUNCTION 'CUCB_INITIALIZER'
 EXPORTING
 IT_INSTANCES = LT_CUIB[].
CALL FUNCTION 'CUXI_GET_SINGLE_CONFIGURATION'
 EXPORTING
 I_ROOT_INSTANCE = LS_VBAP-CUOBJ
 IMPORTING
 E_CFG_HEAD = LS_CFG_HEAD
 ES_PROFILE = LS_PROFILE
 ET_RETURN = ET_RETURN
 TABLES
 E_TAB_INSTANCES = LT_INSTANCES
 E_TAB_PART_OF = LT_PART_OF
 E_TAB_VALUES = LT_VALUES
 E_TAB_VAR_KEYS = LT_VAR_KEYS
 EXCEPTIONS
 INVALID_INSTANCE = 1
 NO_ROOT_INSTANCE = 2
 INSTANCE_IS_A_CLASSIFICATION = 3
 INTERNAL_ERROR = 4
 NO_PROFILE_FOUND = 5
 INVALID_DATA = 6
 OTHERS = 7.
IF SY-SUBRC <> 0.
 CASE SY-SUBRC.
 WHEN 1.
 RAISE INSTANCE_NOT_FOUND.
 WHEN 3.
 RAISE INSTANCE_IS_A_CLASSIFICATION.
 WHEN OTHERS.
 RAISE INVALID_DATA.
 ENDCASE.
ELSE.
 LOOP AT LT_VALUES INTO LS_VALUES.
 IF LS_VALUES-CHARC = 'SAP_MILLCA_PACKAGING'
 OR LS_VALUES-CHARC = 'PD_CA_PACKING_DM'.
 LS_VALUES-VALUE = '7100010'. "This is test data
 MODIFY LT_VALUES FROM LS_VALUES.
 ELSE.
 DELETE LT_VALUES WHERE CHARC = LS_VALUES-CHARC.
 ENDIF.
 CLEAR LS_VALUES.
 ENDLOOP.
ENDIF.
영업정보 특성 변경
CALL FUNCTION 'CUXI_SET_SINGLE_CONFIGURATION'
 EXPORTING
 I_CFG_HEADER = LS_CFG_HEAD
 I_ROOT_INSTANCE = LS_VBAP-CUOBJ
 I_PLANT =
 I_STRUCTURE_EXPLOSION_DATE =
 I_STRUCTURE_EXPLOSION_APPL_ID =
 I_LOGSYS =
 IS_PROFILE = LS_PROFILE
 IV_ONLY_SINGLE_LEVEL =
 IV_HANDLE_APPL_LOG =
 IV_OBJECT_APPL_LOG = 'CIF'
 IV_SUBOBJECT_APPL_LOG = 'T_CNFG'
 IMPORTING
 E_ROOT_INSTANCE = E_ROOT_INSTANCE
 EV_ROOT_PERSIST_ID = EV_ROOT_PERSIST_ID
 EV_CFG_HAS_CHANGED = EV_CFG_HAS_CHANGED
 EV_HANDLE_APPL_LOG = EV_HANDLE_APPL_LOG
 ET_RETURN = ET_RETURN
 TABLES
 I_TAB_INSTANCES = LT_INSTANCES
 I_TAB_PART_OF = LT_PART_OF
 I_TAB_VALUES = LT_VALUES
 I_TAB_VAR_KEYS = LT_VAR_KEYS
 I_TAB_BLOB =
 EXCEPTIONS
 NO_CONFIGURATION_DATA = 1
 NO_ROOT_INSTANCE = 2
 INVALID_INSTANCE = 3
 INSTANCE_IS_A_CLASSIFICATION = 4
 INTERNAL_ERROR = 5
 NO_PROFILE_FOUND = 6
 INVALID_DATA = 7
 OTHERS = 8
IF SY-SUBRC <> 0.
 CASE SY-SUBRC.
 WHEN 1.
 RAISE NO_CONFIGURATION_DATA.
 WHEN 3.
 RAISE NO_ROOT_INSTANCE.
 WHEN 3.
 RAISE INVALID_INSTANCE .
 WHEN 3.
 RAISE INSTANCE_IS_A_CLASSIFICATION.
 WHEN 3.
 RAISE INTERNAL_ERROR.
 WHEN OTHERS.
 RAISE INVALID_DATA.
 ENDCASE.
ENDIF.
COMMIT WORK.
save configuration with next commit
CLEAR: LS_INSTANCES.
READ TABLE LT_INSTANCES INTO LS_INSTANCES INDEX 1.
L_OWNER-OBJECT_TYPE = LS_INSTANCES-OBJ_TYPE.
L_OWNER-OBJECT_TYPE = 'PVS_POSVAR'.
L_OWNER-OBJECT_KEY = LS_INSTANCES-OBJ_KEY.
CALL FUNCTION 'CUCB_CONFIGURATION_TO_DB'
 EXPORTING
 ROOT_INSTANCE = LS_VBAP-CUOBJ
 ROOT_OBJECT = L_OWNER
 IMPORTING
 NEW_INSTANCE = L_CUOBJ_NEW
 EXCEPTIONS
 INVALID_INSTANCE = 1
 INVALID_ROOT_INSTANCE = 2
 NO_CHANGES = 3
 OTHERS = 4.
IF SY-SUBRC > 1 AND SY-SUBRC <> 3.
 CLEAR LS_VBAP-CUOBJ.
 RAISE INTERNAL_ERROR.
ELSEIF SY-SUBRC = 1.
 LS_VBAP-CUOBJ = L_CUOBJ_NEW.
ENDIF.
What's wrong?
help me to solve this problem.
Thanks a lot.

SD_SALES_DOCUMENT_READ Reads sales document header and business data: tables VBAK, VBKD and VBPA (Sold-to (AG), Payer (RG) and Ship-to (WE) parties)
SD_SALES_DOCUMENT_READ_POS Reads sales document header and item material: tables VBAK, VBAP-MATNR
SD_DOCUMENT_PARTNER_READ partner information including address. Calls SD_PARTNER_READ
SD_PARTNER_READ all the partners information and addresses
SD_DETERMINE_CONTRACT_TYPE
In: at least VBAK-VBELN
Exceptions: NO CONTRACT | SERVICE_CONTRACT | QUANTITY_CONTRACT
SD_SALES_DOCUMENT_COPY
RV_ORDER_FLOW_INFORMATION Reads sales document flow of sales document after delivery and billing
SD_SALES_DOCUMENT_SAVE create Sales Doc from the copied document
SD_SALES_DOCUMENT_ENQUEUE to dequeue use DEQUEUE_EVVBAKE
RV_DELIVERY_PRINT_VIEW Data provision for delivery note printing
SD_PACKING_PRINT_VIEW
SD_DELIVERY_VIEW Data collection for printing
called from RV_DELIVERY_PRINT_VIEW, SD_PACKING_PRINT_VIEW
RV_BILLING_PRINT_VIEW Data Provision for Billing Document Print
regards
vinod

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

How to create the change document functionality for a dependent objects?

May I please know how to create the change document functionality for a dependent objects?
I have done it follow the same process as for business process objects. But when i try to test it in BOBT, there is no records under "FIELD_CHANGE_WITH_FILTER". It seems the change hasn't been recorded.
If the way I did to create change document for dependent object is correct, please also kindly advise the possibilities for why there is no record during testing.
thanks in advance.

I also have some doubts about the business object.In this case,one abstract BO hase a subnode wihich is root extended.I added the change document for this node under the category "root_extended" and then tested the function in BOBT.I got some error message "can't find the root key".Shall i redefine the method /BOFU/IF_CDO_CREATION~IS_CDO_CREATION_ACTIVE so as to solve the problem?
Thx.

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.

Dependent Characteristic specs in routing

Hello all,
Some of our materials are subjected for in-process inspection.
The lower, upper and target values differs for the different customers.
I know the procedure of dependent characteristic specs and I am using that in inspection plan already.
But in case of routing while material ssignment I am not getting customer field which usually I get in inspection plan.
Now without that I can't go for dependent characteristic specs.
How to overcome this?
Mimiri

Routings do not support customer specific values in QM.
If you create different specs for the same material, you need to create multiple routings. There are no fields to indicate the customer in routings.
I don't know what business you are in. Have you considered variant config?
FF

Dependent characteristic specifications

We maintain dependent characteristic specifications based on material, plant, and vendor for an inspection plan. Each time a new entry is created, the SAP assigned dependent characteristic specs. number (PLMW-ZUORDNR) is incremented by 10. So the first entry was assigned 10, second entry assigned 20 & so on. We are currently at 6810.
The PLMW-ZUORDNR field length = 4, so I am wondering if there is a limit on the number of dep. char. entries we can create? If so, how do other companies handle this?
I have tried to find a setting in configuration to change the increment from 10 to 1, but was unsuccessful.
Regards,
A. Scott

Angela,
I've worked with Multiple specs before and implemented them at one client but I haven't had a chance to talk with anyone else that has. I'd be interested in finding out more about the issues you ran into and the problems you have had to resolve. I'd like to know if they were similar to mine or not. Right now I'm not the biggest fan of multiple specs the way SAP implemented them. I'm wondering about other peoples thoughts on the subject. With over 680 specs in a plan you must have some experience with them!!!!
Would you be willing to discuss them with me some time?
Thanks,
Craig

Update item characteristic values using BAPI_SALESORDER_CHANGE

Hi Experts,
Could anyone give me sample code on how to update the characteristic values of a sales order item? Points will be awarded... Thanks!
Regards,
LM

Just checked on OSS note 549563 regarding this. This is resolved. Thanks

How to create a time dependent characteristic

Hi,
Can someone give me steps to create time dependent characteristic? there is a tab for attributes to make them time dependent. I don't know whether we can make the characteristic as time dependent or only the attribute.
Thanks,
Sam

What makes a IO a time dependent char?
The attribute values of the IO change according to the time. meaning atleast one attribute value has to(supposed to) change during the course. So to make a IO time dependent, atleast one of ur attribute values should be time dependent.
IO - change _ attributes - 4th column - time dependent - check that box. that would generate - MasDataTab. timDep - SIDTab timeDepAttr(tables)
simple saying in real time - cost center ABC's manager is XYZ from 06/19/2007 to 06/19/2008. So the manager (attribute of costcenter) has to be time dependent.
Hope that makes it understandable. In essence the costcenter itself never changes but the attribute values do change.

Function to update dependent characteristic in QP02

Similar Messages

Maybe you are looking for