Infolinks

Thursday, 21 June 2012

Customers Payment Terms


Customers

Payment Terms

Receivables lets you define standard payment terms for your customers to specify the due date and discount date for their open items. Payment terms can include a discount percent for early payment and you can assign multiple discounts to each payment term line. For example, the payment term '2% 10, Net 30' indicates that a customer is allowed a two percent discount if payment is received within 10 days; after 10 days, the entire balance is due within 30 days of the transaction date with no applicable discount.
You can define balance forward payment terms to bill customers periodically (daily, weekly, or monthly) at the account or site level using balance forward billing. The balance forward bill for a billing period shows the previous balance carried over from the last billing period, payment received, current charges and activities, and current total outstanding balance. See: Balance Forward Billing, Oracle Receivables User Guide.
You can also create split payment terms for invoice installments that have different due dates.
You can use payment terms to determine the amount of each installment. Receivables lets 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. You can use prepayment payment terms to indicate which business transactions require prepayment for goods and services. Receivables displays the active payment terms you define as list of values choices in the Customers, Customer Profile Classes, and Transactions windows.
Note: If you have Multi Lingual Support (MLS), you can define payment terms in each of your installed languages. To enter translations, select Translations from the View menu or click on the globe icon. For more information, see:Oracle Applications Concepts or the Oracle Applications User Guide.

Default Payment Terms Hierarchy

Receivables uses the following hierarchy to determine the default payment term for your transactions, stopping when one is found:
1.    Bill-to site
2.    Customer Address
3.    Customer
4.    Transaction Type

Predefined Payment Terms

Receivables provides the following 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 a payment term:

1.    Navigate to the Payment Terms window.
2.    Enter the Name of this payment term.
3.    Select the Prepayment check box if you are defining a prepayment payment term.
Receivables feeder systems, such as Oracle Order Management, can optionally implement business processes around prepayment payment terms to indicate that a particular business transaction requires the capture of funds before the delivery of a product or service.
See: Managing Prepayment Receipts, Oracle Receivables User Guide.
4.    To associate a credit check with this payment term, check the Credit Check box. Oracle Order Management uses this information to determine when to place an order on hold.
In Oracle Order Management, 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.
5.    If you do not want to let your customers take discounts for partial payments on items associated with this payment term, then uncheck both the Allow Discount on Partial Payments check box as well as the check box for the Discount on Partial Payment system option.
6.    Enter the Installment 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 in first installment' to include all tax and freight charges in the first installment. Choose 'Allocate tax and freight' to distribute tax and freight charges across all installments.
7.    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 installments 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. See: Payment Terms Field Reference.
8.    If you want to use this payment term for balance forward billing, select a balance forward billing cycle from the Billing Cycle list of values. See:
o    Balance Forward Billing, Oracle Receivables User Guide.
Note: You cannot update the billing cycle, once a balance forward billing payment term is attached to a customer, account, or site profile.
Because balance forward bills cannot be split across installments, in the case of a balance forward payment term:
o    Any value entered in Base Amount defaults to 100.
o    Installment Options becomes disabled and any data entered before selecting a cycle defaults to Include tax and freight in first installment.
o    You can populate only one row in the Payment Schedule section and the Sequence Number and Relative Amount values for the row default respectively to 1 and 100.
o    Date Due becomes disabled. However, you can populate Days, Day of Month, and Months Ahead.
Note: You cannot change an existing payment term back and forth for use as both a non-balance forward billing and balance forward billing payment term.
9.    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.
10. Enter the Discount Basis you want Receivables to use when calculating discounts for your invoices. 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.
11. 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.
12. Enter a line number for the installment term that you are defining in the 'Seq' field. Enter a higher number for each installment 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.
13. 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 installment 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.
14. Enter the number of Days after the invoice date that payment is due for this installment term (optional). For split payment terms, this number indicates the number of days after the invoice date that an installment is due.
15. Enter the Date on which payment is due for this installment term (optional). If you do not complete this field, enter a value for either Due Days or both Day of Month and Months Ahead.
16. If you are defining proxima terms, enter the Day of Month that payment is due for this installment term. For example, if payment is due on the fifteenth of each month, enter '15.'
17. If you are defining proxima terms and you entered a value for Day of Month, enter the Months Ahead to which this installment term of the proxima terms refer. 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.
18. Save your work. To assign discounts to each payment schedule line of your payment term, see: Entering Discount Information.
Related Topics
Entering Transactions, Oracle Receivables User Guide
Payment Terms Listing, Oracle Receivables User Guide

Entering Discount Information

Receivables lets you assign discounts to your payment terms. You can also assign multiple discount line terms to each installment of your payment terms. For example, you might give your customer a 10% discount if they pay within 10 days, but only a 5% discount if they pay 11 to 20 days after the invoice date.
Discounts do not apply to Automatic Receipts. If you use the automatic receipts feature to create your Direct Debits, Receivables will not calculate discounts, even if your customers pay before the due date.
Prerequisites
·         Define payment terms

To assign discount information to a payment term:

1.    Navigate to the Payment Terms window.
2.    Query or enter the payment term.
3.    Choose Discounts.
4.    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.
5.    To limit the period of time that the discount for this installment'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.
Related Topics
Discounts, Oracle Receivables User Guide
Discount Projection Report, Oracle Receivables User Guide

Payment Terms Field Reference

Base Amount: If the base amount is different from the relative amount, and you set the Installment Options field for this payment term to 'Allocate tax and freight', Receivables prorates the base amount across the relative amounts of this term's payment schedules based upon the ratio you define. Receivables uses the following equation to determine the original amount due for each installment of invoices to which you assign this payment term:
Amount Due = Relative Amount/Base Amount * Invoice Amount
If you select 'Include tax and freight in first installment' as the Installment Options field value for a payment term, the base amount and the relative amounts that you specify for this term's payment schedules only indicate how the original line amounts of the invoices to which you assign this term are distributed across different installments.
In this case, the original freight and tax amounts are included in the first installment in addition to the line amount allocated by the ratio of the base amount and the relative amount that you specify for the term's first payment schedule. Receivables uses the following equation to determine the original amount due for the first installment of invoices to which you assign this payment term:
Amount Due = (Relative Amount/Base Amount * Base Line Amount) + Base Freight Amount + Base Tax Amount

Defining Customer Profile Classes

Use Customer Profiles to group customer accounts with similar creditworthiness, business volume, payment cycles, and late charge policies. For each profile class you can define information such as credit limits, payment terms, statement cycles, invoicing, and discount information. You can also define amount limits for your late charges and statements for each currency in which you do business.
Define your standard customer profiles in the Customer Profile Classes window. These profiles contain generic options that you can use to group your customers into broad categories.
For example, you might define three categories: one for prompt paying customers; one for late paying customers with high late charge rates; and a third for customers who mostly pay on time, with discount incentives for early payment. You can also use the profile class 'DEFAULT,' which Oracle Receivables provides.
You can assign a profile class to customer accounts and sites on the Create Customer page or the Account Profile subtab of the Account Overview page. The customer profile class you assign provides the default values, which you can optionally customize to meet specific requirements for each account or site.
Profile class options set at the account or site level take precedence over those defined at the customer profile class level.
For statement site, dunning site, and late charges site profile amounts, Receivables uses the profile amounts defined at the site level only if the site is assigned a dunning, statement, or late charge business purpose and you set the AR: Use Statement, Dunning, and Late Charges Site Profiles profile option to Yes. Otherwise, Receivables uses the profile amounts defined on the billing site.
Prerequisites
·         Define statement cycles
·         Define collectors
·         Define credit analysts, Oracle Credit Management User Guide
·         Define payment terms
·         Define AutoCash rule sets
·         Define System Options
·         Define grouping rules
·         Define currencies, Oracle General Ledger User's Guide
·         Optionally define interest tiers and charge schedules, if you are using charge schedules when calculating late charges.

To define a new customer profile class:

1.    Navigate to the Customer Profile Classes window.
2.    Enter a Name and a brief description of this profile class.
3.    Check the Active check box to make this profile class active.
Important: Active profile classes appear in the Profile Class list on the Create Customer page or the Account Profile subtab of the Account Overview page.
4.    Enter other profile class information.
5.    Use the Late Charge Profile tab to enter default information for late charge calculations.
6.    Open the Profile Class Amounts tabbed region, then enter the Currency in which customers assigned to this profile class will do business. For each currency that you enter, define the currency rates and limits for customers using this profile class, including Credit Limit and exchange rate information.
You also use this tab to continue defining your late charge policy. See: Setting Up Late Charges.
Important: If you do not assign an interest rate to a currency, Receivables does not calculate late charges for past due items in that currency. See: Currencies Without Rates, Oracle Receivables User Guide.
Note: If Credit Management is installed, then Credit Management matches the currencies assigned in the profile class with the credit usage rules in Order Management to identify the transactions to include in a credit review.
Related Topics
Creating and Updating Customers, Oracle Receivables User Guide
Creating and Updating Accounts, Oracle Receivables User Guide
Creating and Updating Account Sites, Oracle Receivables User Guide
Discounts, Oracle Receivables User Guide
Processing Credit Reviews, Oracle Credit Management User Guide

Assigning Profile Classes to Customers, Accounts, or Addresses

After you define your standard profile classes, you can assign them to your customers, accounts, and addresses. You can also update specific information for a customer when you assign a new profile class.
When you enter a new customer, Receivables assigns the profile class 'DEFAULT.' You can use this profile class, modify this profile class information, or choose one of the profile classes that you have defined.
Prerequisites
·         Creating a Customer, Oracle Receivables User Guide

Procedure:

See:
·         Adding and Updating Customer Profiles, Oracle Receivables User Guide.
·         Adding and Updating Account Profiles, Oracle Receivables User Guide.
·         Adding and Updating Account Site Profiles, Oracle Receivables User Guide.
Related Topics
Creating a Customer, Oracle Receivables User Guide
Creating an Account, Oracle Receivables User Guide
Creating an Account Site, Oracle Receivables User Guide

Updating a Customer Profile Class

You can modify an existing customer profile class in the Customer Profile Classes window. When you modify profile class information using this window, Receivables requires that you indicate whether and in what way your changes will affect other customers using this profile class.
To update profile class information for a specific customer, use the Customers window. See: Assigning Profile Classes to Customers.
Prerequisites
·         Define profile classes

To update a customer profile class:

1.    Navigate to the Customer Profile Classes window.
2.    Query the profile class to update.
3.    Update information in the Profile Class, Credit Profile, and Profile Class Amounts tabbed regions as necessary.
4.    Save your work. Oracle Receivables displays a pop-up window that lets you decide how to apply your changes. Choose one of the following options:
Do Not Update Existing Profiles: Choose this option if you do not want to update existing customer profiles with your new profile class values. When you choose this option, Oracle Receivables only assigns the new profile values to new customers to whom you assign this profile class.
Update All Profiles: Choose this option to update your new profile class values for all existing customers whom you previously assigned to this profile class. To preserve your customizations to a customer's individual profile, this option does not update every field on a customer's profile with values from the newly modified profile class; only the fields you changed for this profile class will affect your customer's profile. When you choose this option, Oracle Receivables automatically generates the Update Customer Profiles report so you can review your changes.
Update All Uncustomized Profiles: Choose this option to update only customer profiles for which the corresponding options have the same original setting.
For example, you change the Statement Cycle for a profile class from Weekly to Monthly. When you choose Update All Uncustomized Profiles, Oracle Receivables selects all customers who are using the profile class that have a Statement Cycle currently set to Weekly and changes this option to Monthly. All of the other profile class options remain the same.
When you choose this option, Oracle Receivables generates the Update Customer Profiles report. Refer to the 'Exceptions' section of this report to review the customized profile classes that were excluded from the update process. You can then use the Account Profile subtab of the Account Overview page, to update customers whose profile classes were not automatically updated.
Related Topics
Update Customer Profiles Report, Oracle Receivables User Guide

Customer Profile Class and Customer Account Profiles Field Reference

This section provides a brief description of some of the fields in the Customer Profile Classes window, as well as in the Customer set of pages, both at the account and site levels.
See: Adding and Updating Account Profiles, Oracle Receivables User Guide.

Fields Available at the Customer Profile Class, Customer Account, or Site Level

Automatic Cash Rule Set: Determines the sequence of AutoCash Rules that Post QuickCash uses to update the customer’s account balances. If an Automatic Cash Rule Set is not defined at the profile class or customer account or site level, then Receivables uses the Automatic Cash Rule Set that you specify in the System Options window.
AutoReceipts Include Disputed Items: Check the AutoReceipts Include Disputed Items check box to include debit items that have been placed in dispute when you create automatic receipts for customers.
Balance Forward Billing: To send a single, consolidated bill to customers assigned to this profile class, select the Enable check box. If you select the Enable check box, select the bill level and type of printing format for the balance forward bill. See: Balance Forward Billing, Oracle Receivables User Guide.
Bill Level: The level, account or site, at which you can generate balance forward bills.
Selecting Account as the Bill Level at the customer profile class or account profile level lets you generate a single consolidated account level bill for all sites (with Balance Forward Billing enabled) for an operating unit.
The Bill Level at the site profile level is a read-only field, defaulted from the account profile level. To generate site level bills, you must select Site as the bill level at the customer profile class or account profile level and enable Balance Forward Billing at the site profile level.
Collector Name: Enter a default Collector for customer accounts or sites.
Credit Analyst: Select the default credit analyst for customer accounts or sites. The credit analyst is responsible for monitoring the creditworthiness of the account and for assisting in the resolution of credit-related issues. Oracle Credit Management automatically assigns this analyst to credit review requests.
Credit Classification: Select the default credit classification for customers assigned to this profile class. Updated classifications are assigned to the customer, either in Credit Management or through the Assign Customer Credit Classification concurrent program. Credit Management uses the credit classification for credit reviews.
Note: When a credit review is performed for a customer who has relationships with other customer accounts and sites, Credit Management consolidates this information in the case folder.
Credit Check: If you select the Credit Check box, then Oracle Order Management will check the customer's credit before creating a new order, provided that the Payment Term and Order Type associated with the order also require credit checking. Receivables does not check your customer's credit when you create transactions in Receivables.
Credit Limit: The total amount of credit in this currency to give to customers with this profile. This field is used by Oracle Order Management. If credit checking is active for this customer and their outstanding credit balance exceeds this amount, then all new orders for this customer are automatically put on hold in Oracle Order Management.
A customer's outstanding credit balance is calculated using Credit Check Rules that you define in Oracle Order Management. For more information, see: Define Credit Checking Rules in the Oracle Order Management Implementation Manual.
Note: If you are using Oracle Credit Management, then you should update credit limits only via the submission of credit recommendations following a credit review.
Currency: The currency for which you want to define amount limits. You define currencies in the Currencies window.
Dunning: To enable Oracle Advanced Collections to send dunning letters to customers with past due items, check the Send Dunning Letters check box.
Enable Late Charges: To assess late charges for customer accounts or sites, select the Enable Late Charges box. See: Setting Up Late Charges.
Grouping Rule: Enter the grouping rule to use for customers. See: Grouping Rules.
Match Receipts By: Enter a Match Receipts By rule to indicate the document type that customers will use to match receipts with invoices during AutoLockbox validation (optional).
Minimum and Maximum Charge Per Invoice: If the late charge amount that Receivables calculates for a past due debit item in this currency is outside the entered range, then Receivables assesses the entered minimum or maximum charge.
Minimum Customer Balance: If the customer balance of past due items in this currency is less than the minimum amount that you specify here, then Receivables does not assess late charges. Receivables ignores this option when the selected late charge calculation method is Average Daily Balance.
Minimum Invoice Balance: If the balance of a past due invoice in this currency is less than the minimum invoice amount that you specify here, then Receivables does not assess late charges on this item.
Minimum Receipt Amount: Oracle Receivables does not generate automatic receipts in this currency that are less than this amount. You can also define a minimum receipt amount for a receipt method. Receivables will use the larger of the two minimum receipt amounts when creating automatic receipts.
Minimum Statement Amount: The minimum outstanding balance in this currency that a customer must exceed in order for Receivables to generate a statement. For example, if you enter 100 in U.S. dollars, then Receivables does not generate a statement if the customer's outstanding balance is less than or equal to 100 USD. The default minimum statement amount is 0.
Order Credit Limit: The maximum amount of an individual order. This field is used by Oracle Order Management. If credit checking is active for this customer and they exceed this amount on a new order, all new orders for this customer are put on credit hold in Oracle Order Management.
The default order credit limit is the amount you enter in the Credit Limit field. If you enter a Credit Limit, you must either enter an Order Credit Limit or accept the default. The limit per order must be less than or equal to the Credit Limit. You must enter a Credit Limit before entering an Order Credit Limit.
Note: If you are using Oracle Credit Management, then you should update credit limits only via the submission of credit recommendations following a credit review.
Remainder Rule Set: Enter a Remainder Rule Set to specify how Post QuickCash applies any leftover receipt amounts created by a partial receipt application (optional). If you do not enter a Remainder Rule Set, Receivables marks the remaining amount Unapplied.
Review Cycle: Select a review cycle period from the list of values. The periodic review cycle specifies how often to perform a credit review in Credit Management. For example, you can specify that the creditworthiness of an account is reviewed each month.
Receipt Grace Days: Enter the number of Receipt Grace Days that you allow customers with this profile to be overdue on receipts before they will be assessed late charges. For example, if you enter 10, customers have 10 days beyond the transaction due date to pay before they incur a penalty or late charges.
Note: Receipt grace days affect whether late charges are calculated for balance forward bills using the Average Daily Balance method.
Send Credit Balance: To send statements to customers, even if they have a credit balance, select the Send Credit Balance check box.
Statements: To send statements to customers, select the Send Statement check box.
Statement Cycle: If you select the Send Statement check box, enter a Statement Cycle. Statement cycles indicate how often to print your statements.
Tax Printing: To indicate how to print tax on invoices for customers to whom you assign this profile class, enter a Tax Printing value. If you did not enter a default Tax Printing value in the System Options window and you do not specify one here, then Receivables uses Total Tax Only as the default value when you print invoices. See: Transactions and Customers System Options.
Payment Terms: Enter the default payment terms for customers. The payment terms available for selection depend on whether you enabled balance forward billing. See: Setting Up Customer Profile Classes for Balance Forward Billing.
To enable the update of default payment terms when entering transactions for customers, check the Override Terms check box. To provide discount incentives for early payment to customers using this profile class, check the Allow Discount check box. If you allow discounts, enter the number of Discount Grace Days after the discount term date that customers using this profile class can take. If you do not allow discounts, Receivables skips this field. See: Discounts, Oracle Receivables User Guide.
Tolerance: Enter the credit check tolerance (percentage over the credit limit). If a customer account exceeds this tolerance when credit checking is performed, then new orders for this account are put on hold.

Fields Available Only at the Customer Account or Site Levels

These fields are available only at the customer account profile or customer account site profile level, in the Customer set of pages.
Account Status: The status of this account. You can define additional account statuses in the Receivables Lookups window by selecting the lookup type 'Account Status.'
Clearing Days: You can enter a number of Clearing Days (optional) in the Customer set of pages. This is the number of days that it will take for a bank to clear a receipt that has been remitted (for factored receipts, this is also the number of days after the maturity date when the customer risk of non-payment is eliminated).
Collectible (% ): The percentage amount of this customer’s account balance that you expect to collect regularly.
Credit Hold:
·         If credit checking is active for your customer and the customer exceeds its credit limit, then all new orders for the customer are put on hold in Order Management, and Order Management automatically initiates a credit review request.
·         If the credit analyst determines that a customer should be placed on credit hold, then Credit Management automatically places the customer on credit hold by selecting the Credit Hold check box on the Account Profile subtab of the Accounts Overview page.
After you place the credit hold, you cannot create new orders in Order Management, nor can you create invoices for this customer in Oracle Projects. However, you can still create new transactions for this customer in Receivables.
Important: You can use the Credit Hold check box to manually place customer accounts or sites on credit hold. If you use Credit Management, however, then do not make manual updates because Credit Management automatically updates this box. See: Credit Holds, Oracle Receivables User Guide.
Credit Rating: The credit rating for this customer. You can define additional credit rating names in the Receivables Lookups window by selecting the lookup type 'Credit rating for customers.'
Important: Credit Management does not use the credit rating for credit reviews. Instead, it uses the credit classification that is assigned to the customer either in Credit Management, or through the Assign Customer Credit Classification concurrent program.
Minimum Dunning Amount: If a customer has a past due balance in this currency that is greater than the minimum dunning amount specified for this currency, then Oracle Advanced Collections selects this customer for dunning, provided that the scoring engine or strategy uses this value.
Important: If you have defined a dunning site for a customer and have set the AR_USE_STATEMENTS_AND_DUNNING_SITE_PROFILE profile option to Yes, you must define a minimum dunning amount for the customer.
Minimum Dunning Invoice Amount: You can also define the minimum invoice amount in a specific currency for a customer account or site. If a customer does not have any past due items in a specific currency with balances greater than the minimum invoice amount that you specify for this currency, then Advanced Collections does not select this customer for dunning in this currency.
For example, a customer's site has a minimum dunning amount of $100 and a minimum dunning invoice amount of $40. If this site has four past due USD invoices, each with a balance of $30, then Advanced Collections will not select this site for dunning in this currency, even though its total past due balance ($120) exceeds its minimum dunning amount.
Next Credit Review: The next credit review date for an account is calculated based upon the last review date and the review cycle period. All eligible accounts meeting the criteria are selected when you submit the Periodic Credit Review concurrent program in Credit Management.
Risk Code: The credit risk code for your customer. You can define additional risk codes in the Receivables Lookups window by selecting the lookup type 'Customer credit risk.'
Related Topics

Setting Up DQM

1.    Define attributes and transformations.
See also: Defining Attributes and Transformations, Oracle Trading Community Architecture Administration Guide.
Note: The Customer Search page displays the attribute names from the User Defined Name field of the Attributes and Transformations page as the search criteria.
Important: The number of match rule attributes usable in the Customers set of pages is limited to 18.
2.    Generate the staged schema and interMedia indexes.
See also: DQM Staging Program, Oracle Trading Community Architecture Administration Guide.
3.    Optionally define match rules. You need to create separate match rules for search and duplicate identification.
Tip: To ensure accurate results from the DQM search, define all the acquisition attributes of a search match rule as scoring attributes also.
See also: Match Rules Overview, Oracle Trading Community Architecture Administration Guide.
When defining match rule thresholds, keep in mind that:
o    A record must have a match score that exceeds the match threshold to be considered:
§  A search match to display on the Customer Search Page.
§  A potential duplicate to display on the Duplicate Customer page.
o    Records with match scores that exceed the override threshold are exceptionally strong duplicates of the new customer account. In this case, the new account cannot be saved unless the HZ: Duplicate Allowed profile option is set to Yes.
4.    Compile all match rules.
See also: DQM Compile All Rules Program, Oracle Trading Community Architecture Administration Guide.
5.    Synchronize the staged schema with the TCA registry.
See also: DQM Synchronization Program, Oracle Trading Community Architecture Administration Guide.
6.    Set up profile options:
o    HZ: Enable DQM Party Search: Turn DQM on or off, and, therefore, accepts Yes or No values only. This profile option does not store match rules. If this profile option is set to Yes, the application looks at another set of profile options to determine match rules for search. See: DQM Deployment Category, Oracle Trading Community Architecture Administration Guide.
o    DQM Match Rule for Online Duplicate Identification: Specify a seeded or user-defined match rule to use to identify potential duplicates.
o    DQM Search Profile Options: Specify the match rule to use to search for parties and customer accounts using an appropriate DQM Search Profile option. See: DQM Deployment Category, Oracle Trading Community Architecture Administration Guide.
The acquisition attributes in this match rule determine which search criteria appear on the Customer Search page.
You can use a seeded or user-defined match rule. See: Seeded Search Match Rules, Oracle Receivables Reference Guide.
o    HZ: Duplicate Allowed: Define whether new customer accounts can be saved or not when potential duplicates have match scores that exceed the override threshold.
Related Topics
Profile Options and Profile Option Categories Overview, Oracle Trading Community Architecture Administration Guide
Seeded Match Rules, Oracle Trading Community Architecture Reference Guide

Enabling the Funds Capture Process

Funds capture refers to the automated funds capture process that enables the retrieval of customer payments (receipts) through electronic payment methods. To accomplish this funds capture process, Oracle Receivables integrates with Oracle Payments, the Oracle Applications payment engine.
With this integration, Payments provides a central repository for your customers' payment information and uses that information when interacting directly with third party payment systems and financial institutions. Payments handles all funds capture processing for Receivables transactions that have automatic receipt methods.
Oracle Payments captures funds for these types of Receivables transactions:
·         Bank account transfers
See: Remitting Electronic Payments, Oracle Receivables User Guide.
·         Credit card transactions
See: Credit Cards, Oracle Receivables User Guide.
·         Bills receivable remittances
See: Bills Receivable Remittance, Oracle Receivables User Guide.
For a description of the overall Payments process flow, see: Funds Capture Flow Overview, Oracle Payments Implementation Guide.

Setting Up Funds Capture by Oracle Payments

To enable the proper processing of electronic payments, complete the general Payments setup steps. See: Oracle Payments Implementation Guide.
In addition, be sure to complete these additional funds capture setup steps in Oracle Payments:
1.    Define funds capture payment methods, Oracle Payments Implementation Guide.
The payment method is the payment medium which your customers use to remit payments.
2.    Define funds capture process profiles, Oracle Payments Implementation Guide.
The funds capture process profile include processing rules for funds capture.
3.    Set up first party payees, Oracle Payments Implementation Guide.
The first party payee is the company who is deploying Oracle Applications.
4.    Set up credit card brands, Oracle Payments Implementation Guide.
Enable the credit card brands that the deploying company, or its organizations, accept for payment.
You must also complete these setup steps in Oracle Receivables:
1.    Define automatic receipt methods, and assign a funds capture payment method.
An automatic receipt method is a receipt method whose assigned receipt class has an Automatic creation method. See: Receipt Methods.
2.    Assign default payment details at the customer account or site level.
When you enter payment details, you create payment instruments (credit cards and customer bank accounts) for a customer account or site. This customer payment information that you create is actually stored in Payments for use during funds capture processing.
See: Entering and Updating Account Payment Details, Oracle Receivables User Guide and Entering and Updating Account Site Payment Details, Oracle Receivables User Guide.
Note: The payment details you enter at the customer account or site level default to that customer's transactions. You can also overwrite payment details at the transaction level. See: Entering Transactions, Oracle Receivables User Guide.

Correcting Funds Transfer Errors

Oracle Payments manages funds transfer error handling.
For errors that Payments cannot successfully resolve, you can enable the automatic correction of funds transfer errors in Receivables. If the automatic correction feature is not successful or not enabled for specific error codes, then failed transactions display on the Correct Funds Transfer Errors page for manual correction.
See: Enabling Automatic Funds Transfer Error Corrections and Correcting Funds Transfer Errors, Oracle Receivables User Guide.
Related Topics
Understanding Funds Capture Bank Account Transfers, Oracle Payments User Guide
Understanding Credit Card Transactions, Oracle Payments User Guide
Automatic Receipts, Oracle Receivables User Guide
About Remittances, Oracle Receivables User Guide

Bank Account Validation by Country

Oracle Payments validates bank numbers and bank account numbers for certain countries. This helps you detect data entry errors. Refer to your country-specific documentation and to Oracle Payments user documentation for details.

Bank Branch Validation by Country

Oracle Payments validates bank numbers and bank account numbers for certain countries. This helps you to detect data entry errors. Refer to your country-specific documentation and to Oracle Payments user documentation for details.

Flexible Addresses

Oracle Applications let you enter customer, supplier, bank, check, and remit-to addresses in country-specific formats. For example, if you have customers in Germany, you can enter German addresses in the format recommended by the Bundespost, or you can enter addresses for customers in the United Kingdom in the format recommended by the Royal Mail.
This is done by using descriptive flexfields to enter and display address information in the appropriate formats. The flexfield window opens if the country you enter has a flexible address style assigned to it, which lets you enter an address in the layout associated with that country. If there is no address style associated with the country, Oracle Receivables uses the standard address format.

Address Style

An address style tells Oracle Applications how to format and arrange the address fields so that they best suit the address entry requirements of a particular country. Many countries can use the same address style, although a country can only use one address style at a time.
You assign address styles to countries using the Countries and Territories window. You can assign one of the address styles provided or you can create your own. See: Address Style Mappings.

Address Validation

You can define country-specific validation on any element of your address style. This controls the information you enter in these address elements. For example, you may want to restrict the entry of cities for French addresses to a predefined list, or restrict a postal code to a certain range of numbers. See: Defining Flexible Address Validation.

Customized Address Styles

You can define your own address formats if you have specific address entry requirements not covered by the address styles Oracle Receivables provides. You can also set up validation against any address styles you define. See:Creating Custom Address Styles.

Default Country

The Default Country profile option expedites address entry. For example, if most of the addresses you enter are in France, you can set the profile to 'France' so that this will be the default country for all addresses entered.
This profile is also used for Flexible Bank Structure, Tax Registration Number, and Taxpayer ID validation for banks, customers, and suppliers.
Related Topics
Oracle Applications Flexfields Guide

Address Style Mappings

Oracle Applications provides five predefined address styles. These address styles cover the basic entry requirements of many countries. The following address styles are provided:
·         Default
·         Japanese
·         Northern European
·         Southern European
·         South American
·         United States
Address information is stored in different tables for different functions, so there are different mapping of address elements to the database columns for each of the following:
·         Customer and remit-to addresses
·         Bank addresses
·         Supplier addresses
·         Payment addresses
The following tables show the address elements contained in each of the seeded address styles and the mappings of these address elements to the database columns.

Default Address Style

Customer and Remit-To Addresses
This table shows the mapping of the customer and remit-to address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address 1
HZ_LOCATIONS
ADDRESS1
VARCHAR2(50)
Address 2
HZ_LOCATIONS
ADDRESS2
VARCHAR2(50)
Address 3
HZ_LOCATIONS
ADDRESS3
VARCHAR2(50)
Address 4
HZ_LOCATIONS
ADDRESS4
VARCHAR2(50)
City
HZ_LOCATIONS
CITY
VARCHAR2(50)
County
HZ_LOCATIONS
COUNTY
VARCHAR2(50)
State
HZ_LOCATIONS
STATE
VARCHAR2(50)
Province
HZ_LOCATIONS
STATE
VARCHAR2(50)
Postal Code
HZ_LOCATIONS
POSTAL_CODE
VARCHAR2(20)
Supplier, Bank and Payment Addresses
This table shows the mapping of the supplier, bank, and payment address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address 1
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE1
VARCHAR2(50)
Address 2
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE2
VARCHAR2(50)
Address 3
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE3
VARCHAR2(50)
Address 4
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE4
VARCHAR2(50)
City
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
CITY
VARCHAR2(50)
County
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
COUNTY
VARCHAR2(50)
State
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
STATE
VARCHAR2(50)
Province
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
PROVINCE
VARCHAR2(50)
Postal Code
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ZIP
VARCHAR2(50)

Japanese Address Style

Customer and Remit-To Addresses
This table shows the mapping of the customer and remit-to address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Postal Code
HZ_LOCATIONS
POSTAL_CODE
VARCHAR2(20)
Province
HZ_LOCATIONS
STATE
VARCHAR2(25)
City
HZ_LOCATIONS
CITY
VARCHAR2(25)
Address Line1
HZ_LOCATIONS
ADDRESS1
VARCHAR2(35)
Address Line2
HZ_LOCATIONS
ADDRESS2
VARCHAR2(35)
Address Line3
HZ_LOCATIONS
ADDRESS3
VARCHAR2(35)
Supplier, Bank and Payment Addresses
This table shows the mapping of the supplier, bank, and payment address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Postal Code
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ZIP
VARCHAR2(20)
Province
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
STATE
VARCHAR2(25)
City
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
CITY
VARCHAR2(25)
Address Line1
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE1
VARCHAR2(35)
Address Line2
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE2
VARCHAR2(35)
Address Line3
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE3
VARCHAR2(35)

Northern European Address Style

Customer and Remit-To Addresses
This table shows the mapping of the customer and remit-to address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address Line1
HZ_LOCATIONS
ADDRESS1
VARCHAR2(35)
Address Line2
HZ_LOCATIONS
ADDRESS2
VARCHAR2(35)
Address Line3
HZ_LOCATIONS
ADDRESS3
VARCHAR2(35)
Country Code
HZ_LOCATIONS
STATE
VARCHAR2(2)
Postal Code
HZ_LOCATIONS
POSTAL_CODE
VARCHAR2(10)
City
HZ_LOCATIONS
CITY
VARCHAR2(25)
Supplier, Bank and Payment Addresses
This table shows the mapping of the supplier, bank, and payment address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address Line1
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE1
VARCHAR2(35)
Address Line2
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE2
VARCHAR2(35)
Address Line3
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE3
VARCHAR2(35)
Country Code
PO_VENDOR_SITES
AP_BANK_BRANCHES 
AP_CHECKS
STATE
VARCHAR2(2)
Postal Code
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ZIP
VARCHAR2(10)
City
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
CITY
VARCHAR2(25)

Southern European Address Style

Customer and Remit-To Addresses
This table shows the mapping of the customer and remit-to address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address Line1
HZ_LOCATIONS
ADDRESS1
VARCHAR2(35)
Address Line2
HZ_LOCATIONS
ADDRESS2
VARCHAR2(35)
Address Line3
HZ_LOCATIONS
ADDRESS3
VARCHAR2(35)
Postal Code
HZ_LOCATIONS
POSTAL_CODE
VARCHAR2(10)
City
HZ_LOCATIONS
CITY
VARCHAR2(25)
State
HZ_LOCATIONS
STATE
VARCHAR2(25)
Supplier, Bank and Payment Addresses
This table shows the mapping of the supplier, bank, and payment address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address Line1
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE1
VARCHAR2(35)
Address Line2
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE2
VARCHAR2(35)
Address Line3
PO_VENDOR_SITES
AP_BANK_BRANCHES
ADDRESS_LINE3
VARCHAR2(35)
Postal Code
PO_VENDOR_SITES
AP_BANK_BRANCHES 
AP_CHECKS
ZIP
VARCHAR2(10)
City
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
CITY
VARCHAR2(25)
State
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
STATE
VARCHAR2(25)

South American Address Style

Customer and Remit-To Addresses
This table shows the mapping of the customer and remit-to address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address Line1
HZ_LOCATIONS
ADDRESS1
VARCHAR2(35)
Address Line2
HZ_LOCATIONS
ADDRESS2
VARCHAR2(35)
Address Line3
HZ_LOCATIONS
ADDRESS3
VARCHAR2(35)
City
HZ_LOCATIONS
CITY
VARCHAR2(25)
Province
HZ_LOCATIONS
PROVINCE
VARCHAR2(25)
State
HZ_LOCATIONS
STATE
VARCHAR2(25)
State Code
HZ_LOCATIONS
COUNTY
VARCHAR2(2)
Postal Code
HZ_LOCATIONS
POSTAL_CODE
VARCHAR2(10)
Supplier, Bank and Payment Addresses
This table shows the mapping of the supplier, bank, and payment address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address Line1
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE1
VARCHAR2(35)
Address Line2
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE2
VARCHAR2(35)
Address Line3
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE3
VARCHAR2(35)
City
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
CITY
VARCHAR2(25)
Province
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
PROVINCE
VARCHAR2(25)
State
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
STATE
VARCHAR2(25)
State Code
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
COUNTY
VARCHAR2(2)
Postal Code
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ZIP
VARCHAR2(10)

United Kingdom/Africa/Australasia Address Style

Customer and Remit-To Addresses
This table shows the mapping of the customer and remit-to address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address Line1
HZ_LOCATIONS
ADDRESS1
VARCHAR2(35)
Address Line2
HZ_LOCATIONS
ADDRESS2
VARCHAR2(35)
Address Line3
HZ_LOCATIONS
ADDRESS3
VARCHAR2(35)
Town/City
HZ_LOCATIONS
CITY
VARCHAR2(25)
County
HZ_LOCATIONS
STATE
VARCHAR2(25)
Postal Code
HZ_LOCATIONS
POSTAL_CODE
VARCHAR2(10)
Supplier, Bank and Payment Addresses
This table shows the mapping of the supplier, bank, and payment address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address Line1
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE1
VARCHAR2(35)
Address Line2
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE2
VARCHAR2(35)
Address Line3
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE3
VARCHAR2(35)
Town/City
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
CITY
VARCHAR2(25)
County
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
STATE
VARCHAR2(25)
Postal Code
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ZIP
VARCHAR2(10)

United States Address Style

Customer and Remit-To Addresses
This table shows the mapping of the customer and remit-to address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address 1
HZ_LOCATIONS
ADDRESS1
VARCHAR2(50)
Address 2
HZ_LOCATIONS
ADDRESS2
VARCHAR2(50)
Address 3
HZ_LOCATIONS
ADDRESS3
VARCHAR2(50)
Address 4
HZ_LOCATIONS
ADDRESS4
VARCHAR2(50)
City
HZ_LOCATIONS
CITY
VARCHAR2(50)
County
HZ_LOCATIONS
COUNTY
VARCHAR2(50)
State
HZ_LOCATIONS
STATE
VARCHAR2(30)
Postal Code
HZ_LOCATIONS
POSTAL_CODE
VARCHAR2(20)
Supplier, Bank and Payment Addresses
This table shows the mapping of the supplier, bank, and payment address elements to the database columns:
User Prompt
Table Name
Database Column
Display Type (Size)
Address 1
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE1
VARCHAR2(50)
Address 2
PO_VENDOR_SITES 
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE2
VARCHAR2(50)
Address 3
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE3
VARCHAR2(50)
Address 4
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ADDRESS_LINE4
VARCHAR2(50)
City
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
CITY
VARCHAR2(50)
County
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
COUNTY
VARCHAR2(50)
State
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
STATE
VARCHAR2(30)
Postal Code
PO_VENDOR_SITES
AP_BANK_BRANCHES
AP_CHECKS
ZIP
VARCHAR2(50)
Related Topics

Setting Up Flexible Addresses

Flexible Address Formats let you enter and validate addresses in country-specific formats. Following are the setup steps you need to perform to implement this feature.
Prerequisites
If you are using Receivables, Order Management, or Projects:
·         Define your Default Country system option. See: Miscellaneous System Options
If you are using Payables or Purchasing:
·         Define the financials option member state. See: Financials Options, Oracle Payables Implementation Guide

To implement flexible address formats:

1.    Choose an address style.
Before you can enter an address using the flexible addresses functionality, you must decide which address styles best suit your address entry requirements. Receivables provides five predefined address styles, but you can also create customized address styles. See: Creating Custom Address Styles.
2.    Define address validation.
You can use specific validation for a particular country that uses a flexible address format. See: Address Validation.
3.    Assign an address style.
Once a country has been assigned an address style, all addresses entered or modified for that country will use the flexible address functionality. See: Assigning an Address Style to a Country.
4.    Assign a value to the Default Country profile option. See: Profile Options in Oracle Application Library.
The flexible address formats feature checks the value in the Country field of the address region to determine which address style to use. The country assigned to the Default Country profile option will be the default for the Country field in this window.
The Default Country profile option is not mandatory; it lets you change the default country by user, responsibility, site, or application. If you do not set the profile, the default value is the Default (home) Country defined in the System Options window. See: Miscellaneous System Options.
If you are using Payables or Purchasing and do not set the Default Country profile option, the default value is the Member State in the VAT Registration Information region of the Financials Options window.
5.    Assign a value to the AR: Item Flexfield Mode profile option. See: Overview of Receivables User Profile Options.
If this option is set to 'Always Pop a Flexfield Window,' the descriptive flexfield opens automatically when you navigate to an address field. If it is set to 'Concatenated Segment Entry,' the descriptive flexfield will not open when you navigate through the field. If this option is set to 'No Window for a Single Segment Flexfield,' the descriptive flexfield will only open if it has more than one segment enabled.

Assigning an Address Style to a Country

To assign address styles to a country:
1.    Navigate to the Countries and Territories window.
2.    Query the countries to which you want to assign a flexible address.
3.    Select the address style you want from the list of values for the address style field.
Note: Setting the Address Style back to a blank value will turn off the flexible address functionality for that country.
4.    Save your work.
Note: Addresses within a country that is not assigned an address style will use the standard address format.

Implementing Flexible Addresses for the Address Alternate Name Field

If you want to use the flexible address format with the Alternate Name field in the Customer Addresses window, perform the following setup steps.
To set up flexible address formatting for the Alternate Name field in the Addresses window:
1.    Choose the Application Developer responsibility, then navigate to the Descriptive Flexfield Register window.
2.    Query the descriptive flexfield 'Remit Address,' then choose Columns.
3.    Check the Enabled check box for the column name 'ADDRESS_LINES_PHONETIC.'
4.    Save your work.
5.    Navigate to the Descriptive Flexfield Segments window.
6.    In the Title field, query the descriptive flexfield 'Remit Address.'
7.    Select the Context Field Value 'JP' (Japanese Address Style), then choose Segments.
8.    Add the segment 'Alternate Address' and the column ADDRESS_LINES_PHONETIC, then choose Open.
9.    Enter segment information. For example:
o    Name: Alternate Address
o    Number: 7
o    Required: No
o    Security Enabled: No
o    Display Size: 50
o    Description Size: 50
o    List of Values: Alternate Address
o    Window: Alternate Address
o    Concatenated Description Size: 25
Related Topics
Defining Value Sets, Oracle Applications Flexfields Guide
Descriptive Flexfield Concepts, Oracle Applications Flexfields Guide

Creating Custom Address Styles

If the five address styles that Receivables provides do not suit the requirements of the countries in which you do business, you can create your own, custom address styles. You can then use these custom address styles for entering addresses for your customers, banks, suppliers, payments, and remit-to sites.

To create a custom address style:

1.    Choose address style database columns.
Important: When you set up a new address style you must decide which columns from the database you are going to use and how you are going to order them. See: Choosing address style database columns.
2.    Map address style to database columns.
Define the appearance of your flexible address window and the information it will include. See: Mapping address style to database columns.
3.    Add address style to the address style lookup.
Add the address style name to the Address Style Special lookup so that you will be able to assign the style to countries and territories. See: Adding a new style to the address style lookup.
4.    Assign the address style to the appropriate country using the Countries and Territories window. See: Assigning an address style to a country.

Choosing address style database columns

To choose address style database columns:
Decide which columns from the database you are going to use and how you are going to order them.
All the seeded address styles use the following database columns. See: Address Style Mappings.
·         Bank Addresses
o    AP_BANK_BRANCHES.ADDRESS_LINE1
o    AP_BANK_BRANCHES.CITY
o    AP_BANK_BRANCHES.STATE
o    AP_BANK_BRANCHES.ZIP
·         Customer and Remit-To Addresses
o    HZ_LOCATIONS.ADDRESS1
o    HZ_LOCATIONS.CITY
o    HZ_LOCATIONS.POSTAL_CODE
o    HZ_LOCATIONS.STATE
·         Supplier Addresses
o    PO_VENDOR_SITES.ADDRESS_LINE1
o    PO_VENDOR_SITES.CITY
o    PO_VENDOR_SITES.STATE
o    PO_VENDOR_SITES.ZIP
·         Payment Addresses
o    AP_CHECKS.ADDRESS_LINE1
o    AP_CHECKS.CITY
o    AP_CHECKS.STATE
o    AP_CHECKS.ZIP
For example, notice in the Japanese address style that the address element called Province maps onto the STATE database column and that in the United Kingdom/Africa/Australasia address style the address element called County also maps onto the STATE database column.
We recommend that all custom address styles also include at least the above database columns because these address columns are used extensively throughout Oracle Receivables for printing and displaying.
Warning: Most reports do not display the PROVINCE, COUNTY, or ADDRESS4/ADDRESS_LINE4 database columns for addresses.

Mapping address styles to database columns

To map address styles to database columns:
To do this mapping, you must create a new context value for each of the descriptive flexfields as described in this table:
Descriptive Flexfield Name
Displayed in:
Bank Address
Banks
Remit Address
Remit-to Address, Customers
Payment Address
Payment Summary, Payment Overview
Site Address
Suppliers
1.    Using the Application Developer responsibility, navigate to the Descriptive Flexfield Segments window.
2.    Query the appropriate address descriptive flexfield and uncheck the Freeze Flexfield Definition check box.
3.    Navigate to the Context Field Values region. This region contains the address styles that have already been defined for the flexfield.
4.    Enter a name and description for your new address style. The name should be a short, unique code similar to the ones already provided.
5.    Choose Segments, then create address elements for your address style. Each segment consists of a database column, which will store the address information, and the prompt the user will see inside the address window. The columns you assign to your address elements are restricted to the address columns that have been predefined for the flexfield.
You can also define any validation you want to use on a particular segment of your address in this region. To do this, enter an existing Value Set, or choose Value Set, then enter a new value set. See: Address Validation.
6.    Recheck the Freeze Flexfield Definition check box, then save your new address style.
7.    Follow the above steps to set up the same address style for each address descriptive flexfield that you use.
The address styles must be identical across all address flexfields; otherwise, you risk creating addresses that are incompatible with different windows.

Adding a new style to the address style lookup

To add a new style to the address style lookup:
1.    Using the Application Developer responsibility, navigate to the Application Object Library Lookups window.
2.    Query the ADDRESS_STYLE lookup.
Receivables displays all of the address styles used by Flexible Addresses.
3.    To add your new address style, enter the following information:
o    Language
o    Code
This must correspond exactly to the name you assigned your flexfield context value in the Context Field Values region of the Descriptive Flexfield Segments window.
o    Meaning
This should correspond to the short description you provided for your address style in the Context Field Values region of the Descriptive Flexfield Segments window.
4.    Note: Do not enter a start or end date.
5.    Enable this style by checking the Enabled check box.
Related Topics

Using Flexible Addresses

Prerequisites
·         Set Up Flexible Addresses

Entering Flexible Addresses

To enter a flexible address:
1.    Navigate to the window in which you want to enter your flexible address.
Flexible address regions are provided in the following windows:
o    Customers (Receivables, Order Management, and Projects)
o    Suppliers (Payables and Purchasing)
o    Banks (Payables and Receivables)
o    Remit-To Addresses (Receivables)
o    Payments Summary (Payables)
2.    To determine whether an address is to be entered using the standard layout or a flexible address format, you must first enter a value in the Country field.
If you enter the name of a country that does not have an address style assigned to it, the address will be entered using the standard layout. If you enter a country that has an address style assigned to it, a window opens containing the address elements defined for the address style associated with that country.
3.    Enter the address, then choose OK.
Oracle Receivables displays the concatenated address in the standard address fields. Whenever you move the cursor into any of the address fields, the window opens. This prevents you from using the standard address entry for an address entered using flexible addresses.
To query a flexible address:
1.    Navigate to the window in which you want to query your flexible address. For a list of windows in which flexible addresses are available, see: Entering Flexible Addresses.
Any addresses entered using the flexible address functionality can be queried using the standard querying methods. However, you can also query the address in the same format in which it was entered.
2.    Select Enter from the Query menu.
3.    Enter the Country name.
4.    Execute the query to return all addresses for that country. Or, navigate to the address fields to enter additional query criteria.
If the country you choose has a flexible address style assigned to it, Receivables opens a window when you navigate to the address fields.
5.    Choose OK.
6.    Execute the query.
Related Topics
Oracle Applications Flexfields Guide

Address Validation

You can define country-specific validation rules on any element of your address style. Validation rules determine the information you can enter in these address elements. The validation rules Oracle Receivables uses to verify your address information during address entry depend on the following:
·         your home country and the country of the address you are entering
·         the address validation level you choose
·         the flexible address format and validation rules assigned to the country of the address you are entering

Home Country

You define your home country in the Default Country field of the System Options window. Oracle Receivables uses this information to specify the home country for flexible address formats, and taxpayer id and tax registration number validation. It also provides a default value of the Country field when you enter addresses; however, you can override this value by setting the user profile option 'Default Country'. See: Overview of Receivables User Profile Options.

Address Validation Level

You can choose how Oracle Receivables will respond when you enter an invalid address. You can choose to display an error message, a warning, or simply choose 'No Validation'.

Flexible Address Format and Validation Rules

The Country field is the first field of the address region on every window because it determines the format and validation for the rest of the address fields.
If you implement the Flexible Address Formats feature, when you enter a value in the Country field that has been assigned to an address style, a window opens with the address elements defined for that style. See: Flexible Addresses.
Related Topics

Address Validation Level

You set your address validation level in the System Options window. This information only validates addresses that are in your home country.
There are three levels of address validation:
Variable
Description
Error
This level ensures that all components of your customer address are valid before you can save it in the Customer windows.
Warning
This level lets you save an address even if all of the locations do not exist, but displays a warning message informing you of locations that are not defined. If these locations do not exist, Oracle Receivables creates them for you, but does not create the corresponding rates for these new locations.
No Validation
This level lets you save an address without displaying a warning message, even if all of the locations do not exist. If these locations do not exist, Oracle Receivables creates them for you but does not create the corresponding rates for these new locations.
Related Topics

Defining Flexible Address Validation

Use the Flexible Address Formats feature to enter and validate addresses in country-specific formats. See: Flexible Addresses.
For each address style, you can define country-specific validation that controls the information you enter in certain address elements. For example, you may want to restrict the entry of cities for French addresses to a predefined list, or you may want to restrict a postal code to a certain range of numbers.
Validation can take the form of a simple list of values or a complex parent-child relationship between address elements. This section discusses how to implement list of value validation on your flexible address formats. Refer to theOracle Applications Flexfields Guide for information on complex validation.
This section uses the Southern European address style for Spanish and French address entry to demonstrate how to set up a list of values on an address style. Assume that within this flexfield you want to have a list of values on the City field that will list either Spanish or French cities, depending upon the country of the address you are entering. For more information about the Southern European and other address styles, see: Address Style Mappings.
Prerequisites
·         Set up flexible addresses
·         Create custom address styles (optional)

To define flexible address format validation:

1.    Decide which values you want to display in your list of values.
This example uses the following locations: France, Spain, Bordeaux, Barcelona, Lyon, Balboa, Paris, and Madrid.
2.    Navigate to the Countries and Territories window.
3.    Query the countries for which you wish to validate address information.
4.    Note the two character short code which identifies each of the countries you want to validate against in the list of values.
The country codes for Spain and France are 'ES' and 'FR', respectively.
Important: It is very important to identify the correct country code. Otherwise, the list of values will return no data for these countries and you will be unable to enter any information in the address element to which the value is assigned.
5.    Create a valid list of values for each address component you wish to validate. See: Creating a valid list of values for address components.
6.    Define a value set listing your location values. This value set will be attached to the appropriate segment of the address style.
7.    Assign the value set to the appropriate address element in each of the address descriptive flexfields. See: Assigning a value set to an address element.
Warning: The address styles should be identical across all address flexfields. If they are not the same, you risk creating addresses that are incompatible with different windows.

Creating a valid list of values for address components

To create a valid list of values for each address component you wish to validate:

1.    Using the Application Developer responsibility, navigate to the Special Lookups window.
2.    Enter your new lookup Type.
The lookup should belong to the Application Object Library application and should have an Access Level of System.
You should name all of your flexible address lookups consistently to avoid confusion. For example, FAF_<column_name>, where <column_name> is the name of the address column to which you are assigning the list of values choice. In this example you would call your lookup type FAF_CITY.
Important: If more than one country uses a particular address style, you can only have one lookup type for each address element. For example, you can only have one City lookup type for all countries using the Northern European address style. It is advisable to adopt this policy for all lookup types, regardless of the number of countries using them, because they will be easier to maintain.
3.    Enter a list of valid locations. You only need to enter three pieces of information: Language, Code, and Meaning.
The Code is a unique identifier which will enable Oracle Receivables to identify which city to select when it displays the list of values. Therefore, the Code column must be called <country_code><n>, where <country_code> is the two character short code for the country of the address information you are entering, and <n> is a sequential number which ensures the Code is unique.
4.    Enter the actual information you wish to retrieve in the Meaning column.
In this example, the code and meaning values would look as follows in this table:
Code
Meaning
ES1
Barcelona
ES2
Balboa
ES3
Madrid
FR1
Bordeaux
FR2
Lyon
FR3
Paris

Defining a value set

To define a value set that lists your location values:

1.    Using the Application Developer responsibility, navigate to the Value Sets window.
2.    Enter the name of your value set.
For example, FAF_<address_column>, where <address_column> is the name of the column that you will attach to the value set. In this example you would call your value set FAF_CITY.
3.    Ensure that the Format Type and Maximum Size correspond to the type and size of the column you will be populating with this value set.
4.    Set the Validation Type to Table.
5.    Choose Edit Information.
6.    Enter Application Object Library as the Table Application.
7.    Enter FND_LOOKUP_VALUES as the Table Name.
8.    Enter MEANING as the Value Column.
9.    Enter the following statement in the WHERE / ORDER BY region:
10. WHERE LOOKUP_TYPE = '<lookup_name>' AND SUBSTR(LOOKUP_CODE,1,2) =:GLOBAL.FLEX_COUNTRY_CODE
Where <lookup_name> is the name of the lookup you defined which contains the valid values you want to include in the list of values. See: Creating a valid list of values for address components.
In this example the following statement would be used:
 WHERE LOOKUP_TYPE = 'FAF_CITY' AND SUBSTR(LOOKUP_CODE,1,2) =:GLOBAL.FLEX_COUNTRY_CODE
The two-character country code of the country that you enter in all windows with flexible addresses is stored in the :GLOBAL.FLEX_COUNTRY_CODE field. Use this country code to develop country-specific validation within a flexfield that can be used in many countries.

Assigning a value set to an address element

In this example, we will assign the value set to the City segment in the Southern European address style for the Site Address descriptive flexfield.

To assign a value set to the appropriate address element in the descriptive flexfield:

1.    Using the Application Developer responsibility, navigate to the Descriptive Flexfield Segments window.
2.    Query the appropriate address descriptive flexfield, then uncheck the Freeze Flexfield Definition check box.
Oracle Receivables provides the following address descriptive flexfields, as described in this table:
Descriptive Flexfield Name
Displayed in:
Bank Address
Banks
Remit Address
Remit-to Address, Customers
Check Address
Payment Summary, Payment Overview
Site Address
Suppliers
3.    Navigate to the Context Field Values tabbed region, then select the address style to which you are assigning the value set.
In this example the value set will be added to the Southern European address style.
4.    Choose Segments, then select the relevant address segment.
In this example it is the City segment.
5.    Enter the name of the Value Set that you created (in this example it is FAF_CITY).
6.    Return to the Descriptive Flexfield window and check the Freeze Flexfield Definition check box.
7.    Save your work.
8.    Follow the above steps to set up the same validation for each address descriptive flexfield.
The address styles should be identical across all address flexfields. If they are not the same, you risk creating addresses that are incompatible with different windows.
Warning: Do not assign a value set to a flexfield if any of the countries using that flexfield do not have any data defined in the lookup. Using the list of values will return no data for these countries and you will be unable to enter any information in the address element on which the value set is used.
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)