10.1.3ea - EO attribute Precision Rule?

In JDev 10.1.3r3 EA, does anybody know what the Entity Object attribute Precision Rule property does? It's viewable in the Entity Object Wizard when looking at an attribute. Only appears to be enabled for attributes based on the Boolean Domain.
Cheers,
CM.

A miracle has occurred, the properties purpose has now been documented: ADF BC 11g Undocumented Property
CM.

Similar Messages

Load Parent-Child dimension with attributes by rule file

Well, I've cracked my head open while banging against this wall.
Task is plain & simple:
How can I load build dimension from such table, using rule file?
Data
ProductParent ProductChild ProductAttribute
Balls Ball_8 Round
I want to load both product dimension and attribute by single rule file (neither of these dimensions exists in database before load), so I do the following:
1) Set dimension build settings, creating dimension Products (marking it P\C generated, sparse), having an attribute dimension AttributeDim
2) Mark the fields as Parent, Child and AttributeDim of dimension Products
After loading rule file a get three types of errors:
a) "Base member (Balls) association level does not match base dimension association level" -- does this mean that I cannot assign attributes in P\C way?
b) "Record #327 - Can not uniquely identify member by Balls (3335)
Balls Ball_8 Round" -- That's strange, I thought member should be identified by Ball_8 (and this column is unique)
c) "\\Record #418 - Error in association transaction [Ball_8] to [Round] (3362)"
I've read all I could find on topic from this forum, network45 board and going to start my way through metalink3, but maybe some kind soul will rescue me from drowning in information ocean?

Hi,
Outline is blank at the start of load and I expect dimensions Product and ProdAttribute to be added.
Generations are unapplicable, since I can't turn this parent-child dimension (it's ragged) into generation one.
And, by the way Integration Services manages to do this somehow, why rule files wouldn't?

How can I use database constraints in entity attribute validation rules

I am interested in using database constraints to validate attributes in entity objects.
I would like to implement a JboValidatorInterface in a way that I can use an operator like "GreaterOrEqualTo" to compare with values retrieved from the database for a column associated with an entity object attribute.
I have used this pattern with success in other environments, where the user community decides the minimum value for a thing should change from x to y, and simply changing a database object also changes the validation methods of all applications which access it.
I am not certain that column constraints are the appropriate vehicle, but so far that seems to be the case.
I see that you can create a validation rule which makes comparisons against a view object attribute. I am wondering if there is a generic way to use standardized names for column constraints along with ADF hooks into properties of database columns, to avoid writing individual queries for each attribute.
Thanks in advance!!!

Jeffrey,
If you already have constraints on the underlying tables, why do you need to validate them in ADF BC? You can certainly use some framework extension classes to give the user nicely formatted error messages - see ER: ADF BC - allow custom error msgs for common exceptions (e.g. DML) for more details.
I am using this method so that anything that is enforced in the database (check constraints, foreign keys, unique constraints, etc) are not enforced in the ADF BC layer as well - after all, there's more than one way to get data into a table, and DB constraints ensure that even if data gets in through another mechanism (apart from the ADF application), it is valid. My 2 cents, of course.
Hope this helps,
John

OSM O2A - Using extensible attributes in rules

In our RODOD implementation using OSM 7.0.3, we are using the concept of "extensible attributes" intensively.
The concept is great: lots of data coming from Siebel or gathered during the fulfillment process is stored in my order lines' "extensible attributes", almost OOTB, without no need for further customization.
The problem comes when we want to use these extensible attributes in conditions for data jeopardies, change notifications, process branching, etc. All these conditions are configured as "Order Rules", which are based on simple dictionary elements, and which cannot refer to my "extensible attributes" using complex XPath like the following one:
+BaseLineItemData/ItemReference/SpecificationGroup[Name="ExtensibleAttributes"]/Specification[Name="Call Waiting"]+
My question is: Is there any way to use complex XPath in "Order Rules" so I can refer directly my "extensible attributes"?
Right now, we are using lots of workarounds to copy the "extensible attributes" in simple order elements, so they can be referred directly from the "order rules". This approach works in a sunny day scenario, but it will bring problems with revisions that are changing the "extensible attributes" but not the simple order elements.
Thank you in advance

Hi Viktor,
Right now we'll try to use a workaround that doesn't go through low level customization.
The point is that we can do this because our rule is associated to a Jeopardy event. Basically, we'll let the Jeopardy be always triggered and leave the complexity of checking the extensible attributes to the jeopardy's automation.
Unfortunately, this solution only works for rules associated to events triggering any automation. In other cases, your solution should be considered, even if it's not configurable from the design studio.

AAD Sync - updates to attribute and partition filter rules are not applied

The first Attribute filter rules and/or Directory Partition filters we add with a new AAD Sync Installation work fine immediately.
Any subsequent changes to the rules / new rules / removed rules / updated partition filters don't have an impact on the filtering behavior until we
reboot the AAD Sync host.
We've tried restarting the sync service, all sorts of Full Sync etc., nothing else helps.
We don't have any duplicate rules (have those regularly due to the known bug, but always remove them).
We're running AAD Sync build 1.0.0485.0222.
Thanks for any suggestions.

Thanks for your swift suggestions. We've set up a new environment now which finally works fine. We have the same issue at the customer's site where we'll verify next week (100k user accounts, filters are crucial there).
Problem seems to have been the Full Import that we didn't do or didn't do in the right place (can no longer verify since the original test environment is now gone). We were probably doing Full Synchronization instead (as suggested in
the documentation on MSDN).
Still interesting that the reboots had helped every time - they don't imply a Full Import just by themselves I assume?
Thanks again,
René

Rule Policies Attributes

Hi all,
Where I can add my custom attributes to Rule Policies(WebUI->Service Operations->Rule Policies, Context - Service Request Management) and assign values to them?
Thank you in advance.

Hi Egor,
Have you already created the custome rule policy attributes?
If not then first you have to create your custom attributes and then assign them to you rule policy conditions. Follow below steps:
1. Go to SPRO->SAP Reference IMG->Customer Relationship management->Email response management System->Define repository
2. Select Context ERMS and click on Attributes in the left pane:Here you can define your custom attribute (e.g. ZITEM)
3. Provide description
4. Check the checkbox for show attributes
5. provide relevant Xpath Expression( as per your fact gathering)
6. Provide fact Gathering service( You can create your custom Fact gathering service also by copying standard )
7.Provide Attribute Extension class( Refer any std. aatribute for this)
8. Concatenated ID
Save it this will allow you to select your custom rule policy attribute in Conditions.
Regards,
Atul

Save date with precision (Hour, Minutes, seconds ) using V.O.

Hi all,
I'm using Jdeveloper 11g.
I have an Entity object with a column called 'createdOn' of type Date and an entity based View Object with the same type.
I'm trying to save today's Date with precision (day, month, year, hour, minutes, seconds) Using the view Object, but when I look in the Data Base, always appears the date without time.
Here is my code in the application Module to save the data, I've tried some things but nothing...
First I've tried using oracle.jbo.domain.Date, and I've tryed using Calendar as well. Nothing with
ViewObjectImpl voSample = getSamples1View1();
//Date creation for View Object
oracle.jbo.domain.Date today = new Date(Date.getCurrentDate());
//Calendar today = Calendar.getInstance();
//loop through the list of samples (TESTGROUPTYPES), and create the objects
while( it.hasNext())
Row rowSample = voSample.createRow();
SequenceImpl sequence = new SequenceImpl("SAMPLES_SEQ", voSample.getApplicationModule());
rowSample.setAttribute("SampleId", sequence.getSequenceNumber());
rowSample.setAttribute("CollectionId", stCollectionId);
rowSample.setAttribute("TestgroupType",it.next());
rowSample.setAttribute("UnitId",stUnitId);
rowSample.setAttribute("SampleStatus", "ORDERED");
rowSample.setAttribute("SampleBackup", "false");
rowSample.setAttribute("CreatedOn", today);
voSample.insertRow(rowSample);
voSample.getApplicationModule().getTransaction().commit();
Any help will be usefull,
thanks in advance
XAVI.

Hello John,
yes, I changed the date mask using
alter session set NLS_DATE_FORMAT='DD/MM/YYYY-hh24:mi:ss'
if i execute to_char(<date_column>, 'YY-MON-DD HH:MI:SS') on that column, the result is:
09-MAY-27 12:00:00
09-MAY-27 12:00:00
09-MAY-27 12:00:00
To launch the queries and see the results I'm using the JDeveloper's SQL WorkSheet.
I can update the data and time and the time persists in the DB
08-FEB-26 08:07:56
so, i think there's something in hte EO, VO or App Module method that I'm doing wrong...
The Entity Attribute is confirured:
name: CreatedOn
Type: Date
Value type: literal
Values checked: Persistent, Precision Rule and Queryable
database column: CREATED_ON, type: DATE
The View attribute is configured:
Name: CreatedOn
Type: Date
Value type: Literal
checked: Mapped to Column or SQL, Selected in query, queryable
query column: Alias: CREATED_ON, Type: DATE

Gettin Error While activating Device Mapping Rule

Hi all,
I am getting below error while generating Device attribute mapping Rule :
Err:Metainfo FM MMW_DM_DSMS_METH_META - Class Name not specified
Any idea how to resolve this problem.
Regards,
Abhishek

Hi Abhishek,
Custom attributes will not be reflected under category list.
It can be viewed by clicking 'customize' button only in sdoe_rmm01.Do not add custom attributes part of category.
If you have clicked 'Admin UI display' while creating it will get reflected in the admin portal under single valued or multi valued attributes tabs .This way it allowes you to assign custom atrribute values to devices from admin portal.
By the way when you created the other attributes.in category .how did you manage to give proper data types ?
When you say , backward compatible, are you planning to migrate the SyncBOs defined in MI to the current DOE?If yes , this is all that you need to do.
Regards,
Liji

What are the two different rules for organizational data determination

What are the two different rules for organizational data determination???

Hi
1) Rule type Responsibilities
want to determine organizational data for individual responsibilities
have not created an organizational model but want to create one
have a lot of organizational units and must only assign a few attributes
2) Rule type Organizational Model
You would use rule resolution using organizational model if you
have created an organizational model or have distributed a plan to SAP CRM and also want to use this for determining organizational data
assign a lot of attributes to the organizational units and these are to be evaluated
Regards
Manohar

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;

Assigning Territory Attribtues Using Rule Builder

Hi ,
I am not able to assing the Territory Attributes using the Rule Builder.
1. I have create the Rule Policy and Rule set in the Rule Builder.
2. Under the territory I assigned myself as employee and I have created a Rule saying that 'if the Account Hierarchy is X then the Terriotry is X'
3. I go to the Trade Promotion applicaton.
i. I search for the Account hierarchy, the Terrioty is defaulted but no Account Hierarchies are found Under that.
ii. when I search for all the available account Hierarhcies and assign the one that I used in the rule I get a warning '' Account Hierarchy X is not assigned to Territory X "
What additional steps am I missing . Is it possible to assign Territory attributes using rule builder. Is there any other way of doing it.
Thank you,
Siva

HI,
You need to run a program to update the territory relationships/chnages..
you can search for it in se38 -- terrProcrel..
rgds,
Venkat

Entity rule violations: more descriptive error messages

We have several BC4J entity objects, view objects and a JSP application. The entity objects contain rules like mandatory attributes, validation rules at the attribute level, etc. If the user enters invalid data in an HTML form and submits, the errors are generally cryptic and difficult for the user to understand. For example, if the user misses a required field, the exception indicates that "JBO-12345 ... ReqTypeId is required" (for example). It would be ideal if the message could be changed to include the label hint in the message. For example, "Requirement Type is required", where "Requirement Type" is the label hint that is displayed on browse, edit and query pages.
Validation rules (e.g. range rule) applied at the attribute level have a similar issue. Custom rules in validateEntity() do not have this issue because they are custom and we can throw whatever exception we want, with a detailed, user-friendly message.
If this is not possible in JDeveloper 9.0.2 (without extensive custom coding), will it be possible in a future release?
Thanks,
Bill

We have several BC4J entity objects, view objects and a JSP application. The entity objects contain rules like mandatory attributes, validation rules at the attribute level, etc. If the user enters invalid data in an HTML form and submits, the errors are generally cryptic and difficult for the user to understand. For example, if the user misses a required field, the exception indicates that "JBO-12345 ... ReqTypeId is required" (for example). It would be ideal if the message could be changed to include the label hint in the message. For example, "Requirement Type is required", where "Requirement Type" is the label hint that is displayed on browse, edit and query pages.
Validation rules (e.g. range rule) applied at the attribute level have a similar issue. Custom rules in validateEntity() do not have this issue because they are custom and we can throw whatever exception we want, with a detailed, user-friendly message.
If this is not possible in JDeveloper 9.0.2 (without extensive custom coding), will it be possible in a future release?In 9.0.2 you can route all JboExceptions at the JSP level via a handle-all-jbo-exceptions method where you may perform such 'message conversions'. IN general that's the practice most apps have to implement to wrap framework exceptions into user-level exceptions. IN JCLient that's the paradigm followed so that applications can funnel all exceptions via a single handler and perform any exception message massaging.
However you suggestion about involving control-hints into messages by default is a good one and I'd log an Enhancement #2623360 to track this idea.
Thanks,
Bill

Problem in migration of Territory Attributes - dump : GETWA_NOT_ASSIGNED

Hi,
I am trying to migrate CRM Territory attributes using rule builder. But, I am getting run time error saying 'GETWA_NOT_ASSIGNED.
Program : CRM_TERRMAN_DATA_MIGRATION
Termination occurred in the ABAP program "CRM_TERRMAN_DATA_MIGRATION" - in
"EXECUTE_DM".
Code Extract:
777       LOOP AT lt_data_mig_output_all ASSIGNING <fs_data_mig_output_all> .
778         READ TABLE lt_terr_rule_dm ASSIGNING <fs_terr_rule_dm>
779           WITH KEY terr_id = <fs_data_mig_output_all>-terr_id .
780         IF <fs_data_mig_output_all>-success = '3'. "green
781           <fs_terr_rule_dm>-status = '@08@'.
782         ELSE.
783           <fs_terr_rule_dm>-status = '@0A@'. "red.
784         ENDIF.
>>>>>         MODIFY lt_terr_rule_dm INDEX sy-tabix
786         FROM <fs_terr_rule_dm> TRANSPORTING status .
787       ENDLOOP.
Can you please let me know, how can I solve my issue.
Thanks,
Sandeep

Hi Sandeep,
Can you please check what's the value in lt_terr_rule_dm, sy-tabix and <fs_terr_rule_dm> in debug mode?
If possible, can you please attach the debuggin screen?
Or, please report an SAP Customer Message, because it seems to be a standard coding problem.
Best regards,
Maggie

OIM LDAP sync default attributes

Hi,
i am using LDAP sync to provision user/roles to LDAP (OID).
I did the experience, that organization cannot be sync'd to ldap using ldap sync.
Are there a list of all attributes, which will sync between OIM and LDAP (OID)?
Thanks in advance!

This bit of XML just tells reconciliation to copy the "o" attribute in LDAP to a user database field usr_ldap_organization. It does not reconcile organizations as such. I hope the below is an accurate summary of handling of LDAP organizations by LDAP sync which will help.
1) LDAP Synch does not reconcile organization objects into OIM
2) LDAP Synch does provision organization objects to LDAP (although as pointed out perhaps you can customize something outside LDAP sync using an event handler)
3) Users reconciled from LDAP to OIM ar eby default placed in one OIM organization based on the the LDAP Sync scheduled job settings, irrespective of their organization in LDAP (although their LDAP organization can be reconciled to an OIM user attribute, perhaps allowing you to do some more work in an event handler)?
4) Users provisioned from OIM to LDAP use LDAP Container mapping to choose the organisation they are written to in LDAP. This is by default a simple set of attribute based rules, however custom code can be written in a plugin. Not that I found a bug that unfortunately the information that holds an OIM users OIM organization (ACT_KEY) is not made available to this plugin on create.
As to your further question, you can add other mappings as you require in the MDS files (LDAPUser.xml etc.) to map other attributes, either using supplied utilities to simply add UDFs (as mentioned in a previous post) or for less simple changes by modifying the XML by hand.

UI Hints displayWidth conflict issue with precision value in 11.1.1.6

Hi All,
Env. 11.1.1.6
Issue : "bindings.VoAttribute.hints.displayWidth" is taking value of precision (validation>> precision i.e. DB Table precision for VarChar ) in 11.1.1.6 which I am migrating from 11.1.1.3 that was working fine. I have checked apps running in both 1.6 showing precision value of displayWidth if not explicitly define UI Hints displayWidth in EO. Is this issue with 11.1.1.6 ? and of course, is there any configuration to disallow precision value as displayWidth for default hints ?
Thanks .
-Robin

Hi Timo,
The issue is like this :
in 11.1.1.6 for inputText which is using column attribute as bindings.voAttribute.hints.displayWidth. But the displayWidth is not explicitly defined in EO attribute i.e. non value for UI Hints displayWidth. And EO attribute precision is being picked from database table precision for that field as validation for that attribute. While checking in UI Hints for that bindings attribute in UI is taking displayWidth from attribute precision value (255) which is stretching that component whole width of page as its database table column precision is defined as 255 varchar.
Does UI Hints displayWidth checks precision value of attribute if it is not explicitly defined in EO newer version than 11.1.1.3? In my case displayWidth is taking value from EO attribute's precision value. If I define display width for UI Hints, then only it overrides its value in 11.1.1.6. But in jdev 11.1.1.3, it is coming up as 0 for displayWidth for same attribute with precision 255 Varchar.
Thanks,
Robin

10.1.3ea - EO attribute Precision Rule?

Similar Messages

Maybe you are looking for