Have you checked our new Android App!!! Please download and learn oracle at ease

January 9, 2013


Defining Sales Representatives

Navigate to the OM Super user
Setup à Sales à Salespersons, in Resources form select New
  1.  Enter the Sales Person name
  2. Select the Category
  3. Optionally enter the end date
  4. In Roles tab, select the Role Type as Sales and Role as Sales Representative
  5. Save your work, this will generate the Salesperson number
Read More

1 comments:


Defining Payment Terms

Receivable lets you define standard payment terms for your customers. Payment terms can include a discount percent for early payment and you can assign multiple discounts to each payment term line. You can define proxima payment terms to pay regular expenses such as telephone bills and credit card bills that occur on the same day each month. You can also create split payment terms for invoice installments that have different due dates.
You can use your payment terms to determine the amount of each installment. Receivables let you either distribute tax and freight charges across all installments, or allocate all freight and tax amounts in the first installment of a split term invoice. Receivables displays the active payment terms you define as list of values choices in the Customers, Customer Profile Classes, and Transactions windows.
Receivables provides two predefined payment terms:
  • 30 NET: The balance of the transaction is due within 30 days
  • IMMEDIATE: The balance of the transaction is due immediately (i.e. on the transaction date). You can use this payment term with your chargebacks and debit memos.   
To Define, navigate to
Setup à Orders à Payment Terms
  1.  Enter the name, description
  2. Enter the Base Amount for this payment term. The default is 100, but you can change it. The base amount is the denominator for the ratio Receivables uses to determine the amount due for instalments of invoices to which you assign this payment term. The sum of the relative amounts for all of the payment schedules that you define for these payment terms must be equal to the value that you specify as a base amount.
  3. If this payment term uses proxima terms, enter the day to start the new billing cycle for the next month in the Cutoff Day field. Customers who have invoices that fall due before the cutoff day of the invoices' payment terms receive invoices on the day that you specify in the Due: Day of Month field for the current month. Customers who have invoices with payment terms that fall due after the terms' cutoff day receive invoices on the day that you specify in the Due: Day of Month field for the next month of each of these terms
  4. If you want transactions assigned to this payment term to be printed before the due date, enter a number of Print Lead Days. Receivables will print this transaction x number of days before the due date, where x is the number of days you enter here.
  5. To associate a credit check with this payment term, check the Credit Check check-box. Oracle Order Entry uses this information to determine when to place an order on hold. In Oracle Order Entry, if the profile for an address does not have credit checking limits defined in a particular currency but the customer does, then the order passes credit check. If the address does not have limits in the currency and neither does the customer, then the order is compared to the customer limit in that currency.
  6. If you do not want to let your customers take discounts for partial payments on items associated with this payment term, uncheck the Allow Discount on Partial Payments check box.
  7. Enter the First Instalment option for items assigned to this payment term. This indicates how Receivables will allocate the freight and tax charged to transactions using this payment term. Choose 'Include tax and freight' to include all tax and freight charges in the first instalment. Choose 'Allocate tax and freight' to distribute tax and freight charges across all instalments
  8. Enter the Discount Basis you want Receivables to use when calculating discounts for your invoices. The default is the value that you entered in the System Options window. Choose one of the following discount methods:
    Invoice Amount: Choose this option to calculate the discount amount based on the sum of the tax, freight charges, and line amounts of your invoices.
    Lines Only: Choose this option to calculate the discount amount based on only the line amounts of your invoices.
    Lines, Freight Items and Tax: Choose this option to calculate the discount amount based on the amount of line items, freight, and tax of your invoices, but not freight and charges at the invoice header level.
    Lines and Tax, not Freight Items and Tax: Choose this option to calculate the discount amount based on the line items and their tax amounts, but not the freight items and their tax lines, of your invoices.
  9. Enter a range of Effective Dates for this payment term. If you do not enter an end date, this payment term will be active indefinitely.
  10. Enter a line number for the instalment term that you are defining in the 'Seq' field. Enter a higher number for each instalment term with a later due date. For example, if you create terms with 50% due in 15 days and 50% in 30 days, enter '1' in this field for the first line and '2' for the second line.
  11. Enter the Relative Amount for this payment term. This is the numerator of the ratio that Receivables uses to determine the amount due for this instalment of these payment terms. The sum of the relative amounts for all of the payment schedules that you define for each payment term must be equal to the base amount for this term.
  12. Enter the number of Days after the invoice date that payment is due for this instalment term (optional). For split payment terms, this number indicates the number of days after the invoice date that an instalment is due.
  13. Enter the Date on which payment is due for this instalment term (optional). If you do not complete this field, enter a value for either Due Days or both Due Day of Month and Due Months Ahead.
  14. If you are defining proxima terms, enter the Day of Month that payment is due for this instalment term. For example, if payment is due on the fifteenth of each month, enter '15.'
  15. If you are defining proxima terms and you entered a value for Day of Month, enter the Months Ahead to which this instalment term of the proxima terms refers. For example, if you entered '15' for Day of Month and you enter '2' here, an invoice dated in May will have a due date of July 15.

Entering Discount Information

  • Enter the discount percentage and number of Days for this payment term. For example, to give customers using this payment term a two percent discount if payment is received within ten days, enter '2' and '10' respectively.
  • To limit the period of time that the discount for this instalment’s discount line will be active, enter the Date, day of the Month, and the number of Months Ahead for this discount's expiration date. Receivables uses these values to calculate the discount date during invoice entry.
Read More

1 comments:


Setting OM System Parameters

Parameters in the Oracle Order Management Parameters window can be functionally grouped, and you can define controls as easily as defining profile options.
To define navigate to
Setup à System Parameters à Define
1.       Enter a unique code in parameter code
2.       Enter the definition name for the parameter code
3.       Select the category from the Category field that the parameter belongs to. This is controlled with a lookup. To create a new category, add the lookup code in the lookup type “OM_PARAMETER_CATEGORY” and then enter that lookup type in the parameter definition window.
4.       In the Value Set field, enter a value set associated as the source of values. The possible value sets can have validation types of NONE or TABLE. For seeded parameters, use a value set that begins with “ONT.”
5.       Select a value from the Open Orders Check field. This provides a control to allow or restrict changes to the parameter value once it is set for a given operating unit. Available options are Allow, Give error, or Give warning.
6.       When the Enabled box is selected the parameter is available to use. For seeded parameters this field is active only for internal users.
7.       The Seeded check box indicates if the parameter is a seeded parameter or a user defined parameter. This is active only for internal users.
Save your work

To setup Parameter Values

Navigate to Setup à System Parameter à Values
1.       Select the operating unit from the available list of values. The Operating Unit field displays your default Operating Unit. You can change this if required.
2.       The Category field identifies the category to which the parameter belongs. The available parameters and their currently selected values display. Select the Show All check box to display all the parameters for all categories.
3.       In the value field next to the parameter you want to set, select a value. The Value field displays a list of values available for each respective parameter. The Description field describes the currently selected parameter.
4.       Save work.

Read More

0 comments:

January 7, 2013

Order Management: Profile Options

During implementation, you set a value for each user profile option to specify how Order Management controls access to and processes data.

Profile Categories

Profiles have been categorized so that they can be easily classified or grouped. The following table displays the profile categories and the profile options that belong to each one. Some profile options belong to more than one category and are indicated in the table below.
Profile Category Name Profile Option(s) 
ConfigurationsOM: Allow model  fulfilment without configuration;
OM: Configuration Quick Save;
OM: Copy Model DFF to child lines;
OM: Included Item Freeze Method;
OM: Party Totals Currency;
OM: Use Configurator;
Customer UsageOM: Add Customer;
OM: Add Customer (Order Import);
OM: Create Account Information;
OM: E-Mail Required on New Customers;
OM: Party Totals Currency;
OM: Sales Order Form: Restrict Customers
DebugOM: Debug Log Directory;
OM: Debug Level;
OM: Generate Diagnostics for Error Activities;
DeploymentOM: DBI Installation;
OM: Orders Purge Per Commit;
OM: New EDI Acknowledgment Framework;
OM: Printed Document Extension Class Name;
OM: Use Configurator;
Electronic MessagingOM: Change SO Response Required;
OM: Electronic Message Integration Event Sources
OM: New EDI Acknowledgment Framework;
OM: Order Accept State for XML;
OM: Run Order Import for XML;
OM: Send Acknowledgment for Change PO Response;
Forms UIOM: Add Customer;
OM: Administer Public Queries;
OM: Automatically Open Related Items Window;
OM: Contact Center Actions Menu Name;
OM: Cust Item Shows Matches;
OM: Display Actions Button vs. Poplist;
OM: Display Current Selections in Pricing/Availability;
OM: Enable Related Items and Manual Substitutions;
OM: Item View Method;
OM: Quick Sales Order Form: Auto Refresh;
OM: Quick Sales Order Form: Defer Pricing;
OM: Sales Order Form: Cascade Header Changes to Line;
OM: Sales Order Form: Refresh Method (Query Coordination);
OM: Sales Order Form: Restrict Customers;
OM: Sales Order navigation from Pricing/Availability form;
OM: Sales Orders Form preference;
OM: Scheduling Role;
OM: Show Line Details;
OM: Show Process Messages Flag;
OM: Use Configurator;
OM: View Cancel Lines;
OM: View Closed Lines;
OM: View Pricing & Availability Information in Related Items;
FulfillmentOM: Allow model fulfillment without configuration;
OM: Included Item Freeze Method;
OM: Over Return Tolerance;
OM: Over Shipment Tolerance;
OM: Population Of Buyer Code For Dropship Lines;
OM: Source Code;
OM: Under Return Tolerance;
OM: Under Shipment Tolerance;
OM: Automatically Interface Lines to IB on Fulfillment
HoldsOM: Modify Seeded Holds;
OM: Prevent Booking for Line Generic Holds;
InvoicingOM: Interface freight tax code from line;
OM: Invoice Numbering Method;
OM: Set Receivables Transaction Date as Current Date for Non-Shippable Lines;
OM: View Intercompany AR Invoice
Item UsageOM: Customer Item Shows Matches;
OM: Enable Related Items and Manual Substitutions;
OM: Item Flexfield;
OM: Restrict Customer Items for Line Level Ship To Address;
LogisticsOM: Sequence for TP Ship/Deliver Deadline;
OM: Source for TP Early Ship/Deliver Date;
Order ImportOM: Add Customer (Order Import);
OM: Import Multiple Shipments;
OM: Unique Order Source, Orig Sys Document Ref Combination For Each Customer;
PaymentsOM: Commitment Sequencing;
OM: Credit Card Privileges;
OM: Preserve External Credit Balances
Portal UIOM: Customer Service Feedback;
OM: Customer Service Report Defect;
OM: Records On Summary Page For External Users;
PricingOM: Charges For Backorders;
OM: Charges for included item;
OM: Charging Privilege;
OM: Discounting Privileges;
OM: Enable Group pricing for DSP lines;
OM: Item Change Honors Frozen Price;
OM: List Price Override Privilege;
OM: Negative Pricing;
OM: Promotion Limit Violation Action;
OM: Send Changed Lines to Pricing;
OM:Unit Price Precision Type;
OM: UOM Class for Charge Periodicity;
OM: Price Adjustment Modifier for AIA Order Lines
ReturnsOM: Customer Service Feedback;
OM: Customer Service Report Defect;
OM: Over Return Tolerance;
OM: Notification Approver;
OM: Return Item Mismatch Action;
OM: Return Unfulfilled Referenced Line Action;
OM: Under Return Tolerance;
SchedulingOM: Assign New Set For Each Line;
OM: Authorized To Override ATP;
OM: Auto Push Group Date;
OM: AutoSchedule;
OM: Enforce Shipping Method for Ship Sets;
OM: Schedule ATO Item Without BOM;
OM: Scheduling Role;
SecurityOM: Add Customer;
OM: Add Customer (Order Import);
OM: Administer Public Queries;
OM: Authorized To Override ATP;
OM: Cascade Service;
OM: Charging Privilege;
OM: Create Account Information;
OM: Credit Card Privileges;
OM: Discounting Privileges;
OM: List Price Override Privilege;
OM: Modify Seeded Holds;
OM: Scheduling Role;
OM: Authorized To Override ATP;
ServiceOM: Cascade Service;
Transaction EntryOM: Apply Automatic Attachments;
OM: Cascade Service;
OM: Configuration Quick Save;
OM: Copy Model dff to child lines;
OM: Default Blanket Agreement Type;
OM: Default Blanket Transaction Phase;
OM: Default Sales Transaction Phase;
OM: Default Salesrep;
OM: Display New Order After Copy
OM:Enforce check for duplicate Purchase Orders;
OM: Generic Update Constraints Apply to DFF?;
OM: Prevent Booking for Line Generic Holds;
OM: Return Item Mismatch Action;
OM: Return Unfulfilled Referenced Line Action;
UpgradeOM: Context Responsibility for Upgraded Orders;
OM: Notification Approver;

Navigate to System Administrator Responsibility
Profiles à System

Read More

1 comments:

Copyright © . Oracle Apps (SCM) . All Rights Reserved
Oracle Apps (SCM) is an online knowledge sharing blog which index online free tutorials, blogs and other sources, to get easier and accessible manner. The blog has been created keeping only one intention of sharing knowledge and for learning purpose. All trademarks, trade names, service marks, copyrighted work, logos referenced herein belong to their respective owners/companies. If any of the posting is violating copyright and you want us to remove that content. Please contact Here