It is not necessary for the user to remember all the information while entering the order.

It is just enough to remember the customer number (say) and all the other customer related data will be defaulted. Oracle has provided this feature with the defaulting rules setup. Defaulting refers to the supply of a value for a field that has no value. You can create and modify defaulting rules to improve the efficiency and accuracy with which you enter orders. You can define the rules to determine the source and prioritization for defaulting order information to reduce the amount of information you must enter manually in the Sales Order window. Seeded defaulting rules can be disabled, but not modified.

Query entities and attributes: 1. Navigate to the Defaulting Setup - Entity Attributes window. 2. Application: The Application field displays the application context for the entity displayed. 3. Entity: The Entity field displays the name of the object for which defaulting rules and conditions are being defined such as the order line. For Order Management you have the following options: Order Header Order Line Sales Agreement Header Sales Agreement Line Order Payment Line Payment 4. The Defaulting Sequence field enables a user to assign the sequence (priority) number in which this attribute should be defaulted. 5. The Attribute field stores the name of available attributes. Values are currently displayed based upon the entity selected. 6. The Include in Building Defaulting Conditions check box indicates whether an attribute can be used in defining conditions for the entity selected. This check box is for display purposes only, and is non-updateable. 7. Save your work. Define defaulting rules: 1. Navigate to the Attribute Defaulting Rules window. 2. Enter a value in the Precedence field to determine the precedence when resolving multiple TRUE defaulting conditions. 3. Select a Defaulting Condition from the List of Values and then enter the defaulting rules to be used if this defaulting condition is TRUE. 4. Select the Enable check box if you wish to enable the defaulting condition. If this check box is not selected, the defaulting condition is disabled and the rules and condition associated with this condition are not used in default possessing. 5. The check box for the field Seeded cannot be updated. This value is seeded by Order Management. For seeded Order Management defaulting conditions, you are unable to update or delete any fields except: The Precedence field on the defaulting rule condition The Enable check box. You can disable seeded Order Management defaulting rules. 6. Within the Default Sourcing Rules region, select the priority sequence in which you want to retrieve the default for this attribute. The defaulting process searches for a default for your attribute by evaluating defaulting rules in ascending order.

7. Select the defaulting source type. The defaulting source type determines data entry in the Default Source/Value field. 8. Based on the default source type selected, either select the default sources or enter default values in the Default Source/Value field. The table below describes Order Management Source Types and the appropriate action required by a user.

Defaulting Rules Listing Report: This report displays the defaulting rules you have defined for various objects and attributes in Order Management. This listing includes objects, conditions, attributes and seeded data.

If defaulting rules or conditions are updated, the Defaulting Generator concurrent program must be run to generate new defaulting packages. If you update an existing defaulting rule or condition from within the Defaulting Rules window and the update is saved, a pop up window will display a note reminding you to submit the Defaulting Generator concurrent program. Choose to submit the program by selecting Defaulting Generator from the Tools menu while within the Defaulting Rules window, or from the Order Management SRS window. To generate the Defaulting Generator concurrent program for an entity, you must go to the Requests form and select your entity. Order Management Source Types and Actions Source Type Action required Constant Value Enter the default constant value.

ble

Application Profile Select the profile option from where you want to retrieve the default value. Select the attribute on the same record from where you want to retrieve the default value. Object->Select the related object. Attribute->Select the attribute on the related object from where you want to retrieve the default value. Expression--Enter the system expression to be evaluated to obtain the default value. (E.g. System Date.) You can write a custom API to obtain a default value if the value cannot be obtained using other source types such as, the default order number from a sequence. WAD Attribute WAD Object Attribute

Posted by Kishore C B at 02:43 Email ThisBlogThis!Share to TwitterShare to Facebook Labels: Order Management No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom)

Labels

Account Payables (2) AGIS (11) BI/XML Publisher (2) COGS (Cost Of Goods Sold) (1) FNDLOAD (1) Interfaces/Conversions (1) Inventory (7) MOAC (MultiOrgAccessControl) (2) Oracle Alerts (1) Oracle Apps Interview Q/A (7) Oracle Apps Technical (2) Order Management (34) PL/SQL (6) Purchasing (1) SLA (SubLedgerAccounting) (2) WorkFlow (4)

Oracle Applications R12..........

2013 (66) o April (1) o March (3) o January (62)

Collections in Oracle PL/SQL Database Triggers Overview Autonomous Transactions Inventory Transactions Useful Information Order Management Useful Information ORACLE Applications 11i Q/A Reports (D2K) Q/A Drop Ship tables in Order Management Order Management Tables Prerequisite setups required for Order to Cash(O2C... Complete Order to Cash(O2C) Techno-Functional flow... Scheduling in Order Management Defaulting rules in Order Management Validation Template for Processing Constraints in ... Processing Constraints in OM Transaction Type Definition(OM Setups) Document Sequence (OM Setups) Order Management Setups - Profile Options Oracle Workflows in Order Management Oracle apps MOAC setup $FLEX$ Profile Usage XML Publisher Basic Steps Drop Ship Cycle in Order Management Return Material Authorization (RMA) in Order Manag... How to Trace a file in Oracle Apps FNDLOAD Oracle Alerts SQL Loader Part - I SQL Loader With Examples Oracle Apps Interview Q/A - 4 Oracle Apps Interview Q/A - 3 Oracle Apps Interview Q/A - 2 Oracle Apps Interview Q/A - 1 PL/SQL Interview Q&A - 1 Query to Check if a particular e E-Business Suite ... R12 - Profiles to Set the Credit Card authorizatio... Oracle Workflow Background CP Process OM Issue (Drop Ship Order Stuck in Awaiting Receip... Complete Flow from Sales Order to WIP OM RMA Issue (Not able to Receive an RMA in Invent... OM Issue on SalesOrder Line Stuck with Deferred St... Serial Control Item & Drop Ship in Oracle Apps OM ITS Issue (Key Features of Interface Trip Stop ... R12 COGS (Cost Of Goods Sold) Oracle 10g Bulk Binding For Better Performance R12 Multi-Org Access Control (MOAC)

How to Customize COGS Workflow Inventory Queries How to Skip/Retry Workflow OM Issue (RMA stuck at APPROVAL_RETURN_ORDER_NTFA ... How to Setup transaction type in Order Management ... APP-FND-01564. Oracle Error 1403 in fdxwho (R11i, ... OM Issue (ORA 1403 : No Data Found.... Issue on Sh... Order Management MACD OM Scheduling Issue Oracle Order to Cash Queries How to Progress Order lines STUCK in Fulfillment S... How to Skip Scheduling in Oracle Order Management ... Creating and testing a simple business event in Or... How to create your own serial numbers using API Create, Allocate and Transact a Move Order using A... Importing Sales Orders From Excel

2012 (35)

About Me
Kishore C B View my complete profile Picture Window template. Powered by Blogger.