Skip Headers

Oracle Financials for Europe User Guide
Release 12.1
Part Number E13421-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Oracle Receivables

Using the Customer Interface Program

Use the Customer Interface program to import and validate customer information from other systems. Country-specific global descriptive flexfield content is imported and validated during this process.

You use SQL*Loader, or other import program, to load customer information into the interface tables. When you import customer information, the Customer Interface program validates the global attribute columns in the interface tables and transfers those values into the customer tables.

Before the Customer Interface program can properly validate your data file, you must:

  1. Assign the appropriate context code for your country to the appropriate global attribute category column.

  2. Map your global attribute columns from the interface tables to the corresponding global descriptive flexfield segment columns in the customer tables.

This table shows how the global attribute columns in the interface tables map to the global descriptive flexfield segment columns in the corresponding customer tables:

Interface Table.Global Attribute Column Customer Table.Global Attribute Column
RA_CUSTOMERS_INTERFACE_ALL. GLOBAL_ATTRIBUTE1-20 HZ_CUST_ACCOUNTS. GLOBAL_ATTRIBUTE1-20
RA_CUSTOMERS_INTERFACE_ALL. GDF_ADDRESS_ATTRIBUTE1-20 HZ_CUST_ACCT_SITES_ALL. GLOBAL_ATTRIBUTE1-20
RA_CUSTOMERS_INTERFACE_ALL. GDF_SITE_USE_ATTRIBUTE1-20 HZ_CUST_SITE_USES_ALL. GLOBAL_ATTRIBUTE1-20
RA_CUSTOMER_PROFILES_INT_ALL. GDF_CUST_PROF_ATTRIBUTE1-20 HZ_CUSTOMER_PROFILES. GLOBAL_ATTRIBUTE1-20

After you map your global attribute columns, run the Customer Interface program. The Customer Interface program will:

The following sections describe in detail how to import country-specific attributes into the customer tables in Receivables using the Customer Interface program.

Related Topics

Customer Interface, Oracle Receivables User Guide

Mapping Global Descriptive Flexfield Context Codes

To use the Customer Interface program to import and validate global descriptive flexfield content, you must first assign the appropriate global descriptive flexfield context code for your country to one of the global attribute category columns in the RA_CUSTOMERS_INTERFACE_ALL table.

For a given context code, the Customer Interface program confirms that the values of the global attribute columns in the interface table match the value sets that are defined for the global descriptive flexfield segments in the corresponding customer table. In other words, if the global attribute category has a context code, the required global attribute columns for that country must have the correct data.

For example, if your country is Greece and you want to import information for the JG_HZ_CUST_ACCOUNTS global descriptive flexfield from the interface tables to standard Receivables customer tables, then you must enter the JE.GR.ARXCUDCI.CUSTOMER context code in the GLOBAL_ATTRIBUTE_CATEGORY column and enter either Yes or No in the GLOBAL_ATTRIBUTE1 column.

This table shows you how to map this global descriptive flexfield context code for Greece to the GLOBAL_ATTRIBUTE_CATEGORY column in the RA_CUSTOMERS_INTERFACE_ALL table.

For this country… For this flexfield... Map this global descriptive flexfield context code…
Greece JG_HZ_CUST_ACCOUNTS JE.GR.ARXCUDCI.CUSTOMER

This table shows you how to map these global descriptive flexfield context codes for your country to the GDF_SITE_USE_ATTR_CAT column in the RA_CUSTOMERS_INTERFACE_ALL table.

For this country… For this flexfield... Map this global descriptive flexfield context code…
Greece JG_HZ_CUST_SITE_USES JE.GR.ARXCUDCI.RA
Portugal JG_HZ_CUST_SITE_USES JE.PT.ARXCUDCI.RA

Mapping Global Descriptive Flexfield Segments

Map these global attribute columns in the interface tables to the corresponding global descriptive flexfield segments. For each context code that you assign to a global attribute category column, confirm that the values of the matching global attribute columns are compatible with the designated value sets.

Greece

This table shows the valid values with descriptions for the JE.GR.ARXCUDCI.CUSTOMER Greek context.

Global Descriptive Flexfield: JG_HZ_CUST_ACCOUNTS

Context Code: JE.GR.ARXCUDCI.CUSTOMER

In this column... Oracle Receivables stores... For this location...
RA_CUSTOMERS_INTERFACE_ALL.GLOBAL_ATTRIBUTE1 Public sector company reporting. Valid values are Yes or No. HZ_CUST_ACCOUNTS.GLOBAL_ ATTRIBUTE1

This table shows the valid values with descriptions for the JE.GR.ARXCUDCI.RA Greek context.

Global Descriptive Flexfield: JG_HZ_CUST_SITE_USES

Context Code: JE.GR.ARXCUDCI.RA

In this column... Oracle Receivables stores... For this location...
RA_CUSTOMERS_INTERFACE_ALL.GDF_SITE_USE_ATTRIBUTE1 Receipt acknowledgment designation. Valid values are Yes or No. HZ_CUST_SITE_USES_ALL.GLOBAL_ ATTRIBUTE1

Portugal

This table shows the valid values with descriptions for the JE.PT.ARXCUDCI.RA Portuguese context.

Global Descriptive Flexfield: JG_HZ_CUST_SITE_USES

Context Code: JE.PT.ARXCUDCI.RA

In this column... Oracle Receivables stores... For this location...
RA_CUSTOMERS_INTERFACE_ALL.GDF_SITE_USE_ATTRIBUTE1 Receipt acknowledgment designation. Valid values are Yes or No. HZ_CUST_SITE_USES_ALL.GLOBAL_ ATTRIBUTE1

Customer Interface Transfer Report

Each time you run Customer Interface program, Receivables generates the Customer Interface Transfer report. If any validation fails, the Customer Interface program populates the INTERFACE_STATUS column in the interface tables with the concatenated error codes for the Customer Interface Transfer report. This report shows the rows with problems and related error descriptions.

Related Topics

Customer Interface Transfer Report, Oracle Receivables User Guide

Using the AutoInvoice Interface Program

The RA_INTERFACE_LINES_ALL interface table stores invoice information. You use SQL*Loader to load invoice information into the interface table for each invoice that you create.

When you initiate importing invoices, the AutoInvoice open interface validates global attribute columns in the RA_INTERFACE_LINES_ALL table according to country-specific requirements. AutoInvoice then transfers global attribute columns from the RA_INTERFACE_LINES_ALL table to the RA_CUSTOMER_TRX_ALL table and the RA_CUSTOMER_TRX_LINES_ALL table.

Before the AutoInvoice program can properly validate your data file and create invoice and invoice lines in Oracle Receivables, you must:

  1. Assign the appropriate context code for your country to the appropriate global attribute category column

  2. Map your global attribute columns from the interface table to the corresponding global descriptive flexfield segment columns in the transaction tables

This table shows how the global attribute columns in the interface table maps to the global descriptive flexfield segment columns in the corresponding transaction tables:

Interface Table.Global Attribute Column Transaction Table.Global Attribute Column
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE1-30 RA_CUSTOMER_TRX_ALL. GLOBAL_ATTRIBUTE1-30
RA_INTERFACE_LINES_ALL. LINE_GDF_ATTRIBUTE1-20 RA_CUSTOMER_TRX_LINES_ALL. GLOBAL_ATTRIBUTE1-20

Related Topics

Importing Invoice Information Using AutoInvoice, Oracle Receivables User Guide

Mapping Global Descriptive Flexfield Context Codes

To use the AutoInvoice program to import and validate global descriptive flexfield content, you must first assign the appropriate global descriptive flexfield context code for your country to one of the global attribute category columns in the RA_INTERFACE_LINES_ALL table.

For a given context code, the AutoInvoice program confirms that the values of the global attribute columns in the interface table match the value sets that are defined for the global descriptive flexfield segments in the corresponding transaction tables. In other words, if the global attribute category has a context code, the required global attribute columns for that country must have the correct data.

This table shows you how to map these global descriptive flexfield context codes for your country to the HEADER_GDF_ATTR_CATEGORY column in the RA_INTERFACE_LINES_ALL table.

For this country… For this flexfield... Map this global descriptive flexfield context code…
Poland JG_RA_CUSTOMER_TRX JE.PL.ARXTWMAI.TAX_DATE
Spain JG_RA_CUSTOMER_TRX JE.ES.ARXTWMAI.MODELO347PR
Spain JG_RA_CUSTOMER_TRX JE.ES.ARXTWMAI.MODELO349
Spain JG_RA_CUSTOMER_TRX JE.ES.ARXTWMAI.MODELO415_347PR

Mapping Global Descriptive Flexfield Segments

Map these global attribute columns in the interface table to the corresponding global descriptive flexfield segments. For each context code that you assign to a global attribute category column, confirm that the values of the matching global attribute columns are compatible with the designated value sets.

Poland

This table shows the valid values with descriptions for the JE.PL.ARXTWMAI.TAX_DATE Polish context.

Global Descriptive Flexfield: JG_RA_CUSTOMER_TRX

Context Code: JE.PL.ARXTWMAI.TAX_DATE

In this column… Oracle Receivables stores… For this location…
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE3 Bank account number. The value set for this segment is JGZZ_AR_BANK_ACT_NUM. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE3

Spain

This table shows the valid values with descriptions for the JE.ES.ARXTWMAI.MODELO347PR Spanish context.

Global Descriptive Flexfield: JG_RA_CUSTOMER_TRX

Context Code: JE.ES.ARXTWMAI.MODELO347PR

In this column… Oracle Receivables stores… For this location…
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE2 Rental location. The value set for this segment is JEES_RENTED_LOCATION. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE2

This table shows the valid values with descriptions for the JE.ES.ARXTWMAI.MODELO349 Spanish context.

Global Descriptive Flexfield: JG_RA_CUSTOMER_TRX

Context Code: JE.ES.ARXTWMAI.MODELO349

In this column… Oracle Receivables stores… For this location…
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE3 Correction year. The value set for this segment is JEES_YEARYYYY. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE3
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE4 Correction period. The value set for this segment is JEES_PERIOD_349. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE4

This table shows the valid values with descriptions for the JE.ES.ARXTWMAI.MODELO415_347PR Spanish context.

Global Descriptive Flexfield: JG_RA_CUSTOMER_TRX

Context Code: JE.ES.ARXTWMAI.MODELO415_347PR

In this column… Oracle Receivables stores… For this location…
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE2 Property location. The value set for this segment is JEES_RENTED_LOCATION. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE2

Bills of Exchange

In Release 12, you cannot create new bills of exchange automatic receipts. You can continue to remit previously existing bills of exchange receipts using these Bills of Exchange receipt formats:

Italian Remittance EFT Format

Use the Italian Remittance EFT Format to produce a file that contains an automatic remittance for bills of exchange Italy for the open bills of exchange. This remittance format is sent to the bank to initiate the transfer of funds.

This EFT format is made up of a header record, detail records that describe the receipts, and an end record.

This table is a summary of the detail records:

Record Type Description
14 Receipt Details
20 Supplier Name
30 Customer Name
40 Customer Address
50 Invoice Details
51 Supplier Details
70 Additional information for the bank

You can generate the Italian Remittance EFT Format by running the Italian Remittance EFT concurrent program once the Remittance batch has been approved.

Regional and Country Reports

Regional Invoice Format

For the Czech Republic, Hungary, and Poland, use the Regional Invoice Format to print all Receivable documents for a given document type, document number range, and customer name. To assist in packaging and delivering your billings, you can order your printed transactions by document number, customer name, or postal code.

Based on your responsibility, you may print either original or duplicate invoice documents.

Use the Standard Request Submission windows to submit the Regional Invoice Format.

Setting Up the Duplicate Profile Option

For the Czech Republic, Hungary, and Poland, set the JG: Duplicate profile option at the responsibility level. This profile option value populates the Duplicate parameter in the Regional Invoice Format. The parameter lets you print either original or duplicate Receivables documents based on the profile option setting for your responsibility.

Prerequisites

Before running the Regional Invoice Format, you must complete these tasks:

Assign Product Fiscal Classifications to Items and Tax Product Categories to Memo Lines

You can assign product fiscal classifications to inventory items or tax product categories to standard memo lines, to represent statistical codes as determined by the Hungarian or Polish government.

Define Transaction Types

When you define transaction types for the Czech Republic, Hungary, or Poland, ensure that your naming standards comply with official document types as printed on the invoice.

Report Parameters

Order By

Enter one of the following:

The default is Transaction Number.

Batch (for the Czech Republic only)

Enter the batch number for the invoices you want to report on.

Document Type

Enter one of the active transaction types defined in Oracle Receivables.

Invoice Number Low

Enter the lowest invoice number that you want to print.

Invoice Number High

Enter the highest invoice number that you want to print.

Invoice Date Low

Enter the earliest invoice date that you want to print.

Invoice Date High

Enter the latest invoice date that you want to print.

Customer Name

Enter a specific customer name or leave this parameter blank for all customers.

Report Headings

In this heading… Oracle Receivables prints…
Bill To The billing site customer name, address, tax registration number, and purchase order number
Ship To The shipping site address
Remit To Your company's name, remittance address, tax registration number, and company number
VAT Date The tax invoice date
Invoice Date The invoice date
Invoice Num The invoice number
Invoice Type The name of the transaction type

Column Headings

In this column… Oracle Receivables prints…
Num The line number of the invoice.
Description The line item description.
Item Code The item statistical code associated with the line item. This column is not used in the Czech Republic.
UOM The unit of measure for a given line.
Unit Price The unit selling price of the line item.
Qty The quantity billed of the item.
Amount The net invoice line amount
VAT% The tax rate for any tax rate codes that do not have a zero rate. The report prints the tax name for any tax rate codes that have a zero rate.
VAT The VAT amount for the invoice line.
Total The total invoice line amount.
VAT by Rate Amount The total net invoice amount for each tax rate.
VAT by Rate VAT% The tax rate for any tax rate codes that do not have a zero rate. The report prints the tax name for any tax rate codes that have a zero rate.
VAT by Rate VAT The total tax amount for each tax rate.
VAT by Rate Total Amount The total invoice amount for each tax rate.
Invoice Amount The total invoiced amount.
In Words The total invoiced amount in words.
Payment Terms The payment terms for the invoice
Due Date The due date for the invoice.
Invoice Amount The total invoiced amount.
Curr The currency of the invoice.
Remittance Bank The remittance bank name.
Branch The remittance bank branch.
Bank Num The remittance bank number.
Bank Account Num The remittance bank account number.
Issuer A line for the issuer's signature.
Receiver A line for the receiver's signature.
Comments Optional additional invoice information.

Related Topics

Running Reports and Programs, Oracle Applications User Guide

Receipt Acknowledgment Letter

Use the Receipt Acknowledgment Letter report to confirm the receipt of any payment from a customer.

Note: This functionality is only used and active for Greece and Portugal.

Oracle Receivables produces a separate receipt acknowledgment for each receipt currency. You can produce:

You can match a receipt in a different currency to the invoice that the receipt is applied to when you manually enter a receipt.

Use the Standard Request Submission windows to submit the Receipt Acknowledgment Letter report.

Prerequisites

Before submitting the Receipt Acknowledgment Letter report, you must:

Related Topics

Running Reports and Programs, Oracle Applications User Guide

Defining Document Categories, Oracle Applications System Administrator's Guide

Defining a Document Sequence, Oracle Applications System Administrator's Guide

Assigning a Document Sequence, Oracle Applications System Administrator's Guide

Regional Dunning Letter

Use the Regional Dunning letter as a statement that you can send to customers advising them about open balances.

Use the Standard Request Submission windows to submit the Regional Dunning letter.

Prerequisites

To use the Regional Dunning letter, you must set up at least one dunning letter in the Dunning Letters window. Specify &F_AS_OF_DATE in the message text for the as of date and &F_TOTAL_BALANCE in the message text for the customer site total balance in the ledger currency.

Parameters

As of Date

Enter the effective date of the letter.

Dunning Letter

Choose the dunning letter that you would like to send.

Customer From

Enter the customer that you would like to run the letter from.

Customer To

Enter the customer that you would like to run the letter to.

Currency Code

Choose the currency for the letter.

Include Receipts at Risk

Choose Yes to include receipts at risk in the letter. Choose No not to include at risk receipts.

Report Headings

This table shows the report headings.

In this heading... Oracle Receivables prints...
Customer The customer's name
Tax ID The customer's tax identification number
Customer Site The customer's bill to site
<Note to Customer> The user-defined note that you specified in the dunning letter that you choose

Column Headings

This table shows the column headings.

In this column... Oracle Receivables prints...
Invoice Number The invoice number for this transaction. Only invoices with outstanding balances are printed.
Invoice Date The date of the invoice.
Invoice Type The type of the invoice.
Original Amount The original amount of the transaction in the entered currency. The currency code for the entered currency is shown in parentheses.
Amount Due Remaining The remaining amount due of the transaction in the entered currency. The currency code for the entered currency is shown in parentheses.
Original Amount The original amount of the transaction in the ledger currency. The currency code for the ledger currency is shown in parentheses.
Amount Due Remaining The remaining amount due of the transaction in the ledger currency. The currency code for the ledger currency is shown in parentheses.
Due Date The date that the transaction balance is due.
Days Late The number of days that payment of this invoice is overdue. A negative number indicates that the payment is not yet due.

Related Topics

Running Reports and Programs, Oracle Applications User Guide

Portuguese Receivables Taxpayer ID Exception Report

Use the Portuguese Receivables Taxpayer ID Exception report to produce a list of all customers without a taxpayer ID. You can run this report by the legal entity, ledger, or balancing segment value. The report only selects the suppliers for whom you inserted at least one transaction.

Use the Standard Request Submission windows to submit the Portuguese Receivables Taxpayer ID Exception report.

Prerequisites

Add a Legal or Contencioso line in each Customer Business Purpose Address Site.

Report Headings

In this heading… Oracle Receivables prints…
<Report Title> Portuguese Receivables Taxpayer ID Exception Report
Report Date The date that the report is run
Page The current and total pages of the report

Column Headings

In this column… Oracle Receivables prints…
Customer Name The customer's name
Customer Number The customer's number

Related Topics

Running Reports and Programs, Oracle Applications User Guide