122CLENOUG v2 27MAR18

Oracle® EMEA Add-on Localization
User Guide for Norway

Release 12.2
Part No. E49866-01
March
2018
I
Oracle EMEA Add-on Localization User Guide for Norway, Release 12.2
Part No. E49866-01
Copyright © 2009, 2010, 2014 Oracle and/or its affiliates. All rights
reserved. Primary Author: Zlatko Alvir
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf
of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication,
disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the
applicable Government contract, and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle
USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications which may
create a risk of personal injury. If you use this software in dangerous applications, then you shall be
responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of
this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software in dangerous applications.
This software and documentation may provide access to or information on content, products and services
from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third party content, products and services. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third
party content, products or services.
II
Contents
CHAPTER 1 ADD-ON LOCALIZATION OVERVIEW ....................................................................... 1-1

Add-on Localizations for Norway ............................................................................................................................... 1-1
CHAPTER 2 PREREQUISITES .............................................................................................................. 2-1

Assignment of Concurrent Programs to Request Groups .............................................................................................. 2-1
Reports for Norway Add-on Localization .................................................................................................................. 2-1
Concurrent Programs for Norway Add-on Localization ........................................................................................ 2-2
CHAPTER 3 GENERAL SETUP STEPS ................................................................................................ 3-1

Bank Acknowledgement codes definition....................................................................................................................... 3-1
Bank Statement Mapping ............................................................................................................................................ 3-2
Profile Options ............................................................................................................................................................. 3-3
CHAPTER 4 CLE: NORWEGIAN TELEPAY ACKNOWLEDGEMENT IMPORT AND

VALIDATION REPORT .................................................................................................................................... 4-1
Requirement ................................................................................................................................................................. 4-1
Overview ....................................................................................................................................................................... 4-1
Report Layout ............................................................................................................................................................... 4-2
Setup ............................................................................................................................................................................. 4-3
Transactions Processing ............................................................................................................................................ 4-4
How to Launch the Program ..................................................................................................................................... 4-4
Program Parameters for CLE: Norwegian Telepay Acknowledgement Load Program ............................................. 4-5
CLE: Norwegian Telepay acknowledgement import and validation report .................................................................. 4-6
Report Headings .......................................................................................................................................................... 4-6
Column Headings ........................................................................................................................................................ 4-6
Row Headings ............................................................................................................................................................. 4-7
Summary Details ......................................................................................................................................................... 4-7
CHAPTER 5 CLE: NORWEGIAN BANK STATEMENT LOADER PROGRAM ............................ 5-1

Requirement ................................................................................................................................................................. 5-1
Overview ....................................................................................................................................................................... 5-1
Setup ............................................................................................................................................................................. 5-2
Transactions Processing ................................................................................................................................................... 2
How to Launch the Program ..................................................................................................................................... 5-3
III
Program Parameters ................................................................................................................................................... 5-4
CHAPTER 6 CLE: NORWEGIAN PROCESSED TELEPAY PAYMENTS REPORT ..................... 6-1

Overview ....................................................................................................................................................................... 6-1
Report Layout ............................................................................................................................................................... 6-2
How to Launch Report ............................................................................................................................................... 6-2
Report Parameters ...................................................................................................................................................... 6-3
Report Headings .............................................................................................................................................................. 3
Column Headings ........................................................................................................................................................ 6-4
Summary Details ......................................................................................................................................................... 6-4
CHAPTER 7 CLE: NORWEGIAN BANK REFERENCE AND STATUS REPORT ........................ 7-1
Overview ....................................................................................................................................................................... 7-1
Report Layout ............................................................................................................................................................... 7-2
User Procedure ............................................................................................................................................................. 7-3
Report Headings .......................................................................................................................................................... 7-6
Column Headings .......................................................................................................................................................... 7-6
CHAPTER 8 CLE: NORWEGIAN BANK STATEMENT BY DETAILS REPORT ........................ 8-1

Overview ....................................................................................................................................................................... 8-1
Report Layout ............................................................................................................................................................... 8-2
User Procedure ............................................................................................................................................................. 8-3
Report Headings .......................................................................................................................................................... 8-6
Column Headings .......................................................................................................................................................... 8-7
CHAPTER 9 INDEX .................................................................................................................................. 9-1
IV
Send Us Your Comments
Oracle EMEA Add-on Localization User Guide for Norway, Release 12.2
Part No. E49866-01
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
V
Preface
Intended Audience
Welcome to Release 12.2 of the Oracle EMEA Add-on Localization User Guide for Norway.
This user guide is intended for a customer in Norway.
See Related Information Sources on page viii for more Oracle E-Business Suite product
information.
Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call
Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle
technical issues and provide customer support according to the Oracle service request
process. Information about TRS is available at
http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is
available at http://www.fcc.gov/cgb/dro/trsphonebk.html.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible
to all users, including users that are disabled. To that end, our documentation includes
features that make information available to users of assistive technology. This
documentation is available in HTML format, and contains markup to facilitate access by
the disabled community. Accessibility standards will continue to evolve over time, and
Oracle is actively engaged with other market-leading technology vendors to address
technical obstacles so that our documentation can be accessible to all of our customers.
For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/.
VI
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The
conventions for writing code require that closing braces should appear on an otherwise
empty line; however, some screen readers may not always read a line of text that
consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations
that Oracle does not own or control. Oracle neither evaluates nor makes any
representations regarding the accessibility of these Web sites.
Structure
1 Add-on Localizations Overview
2 Prerequisites
3 General Setup Steps
4 CLE: Norwegian Telepay acknowledgement import and validation report
5 CLE: Norwegian Bank Statement Loader Program
6 CLE: Norwegian Processed Telepay Payments Report
7 CLE: Dynamic Due Date Calculation for AR invoices
8 CLE: Norwegian Bank Reference and Status Report
9 CLE: Norwegian Bank Statement by Details Report
VII
Related Information Sources
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
VIII
Chapter 1 Add-on Localization Overview
Add-on Localizations for Norway

Oracle® EMEA Add-on Localizations provide additional functionalities to help
customers in Norway meet legal and business requirements. This user guide provides
details about setup and functionality of the following program and reports:
Payables
• CLE: Norwegian Telepay acknowledgement import and validation Report.
• CLE: Norwegian Bank Reference and Status Report.
Cash Management
• CLE: Norwegian Bank Statement Loader.
• CLE: Norwegian Processed Telepay Payments Report.
• CLE: Norwegian Bank Statement by Details Report.
Receivables
• CLE: Dynamic Due Date Calculation for AR Invoices.
Add-on Localization Overview 1-1

Chapter 2 Prerequisites
Assignment of Concurrent Programs to Request Groups

Request Group setup provides access to the Concurrent Program to the user
responsibilities. Assign the following programs to the request group attached to the
responsibility from which you want to access the functionality. This section provides
information on the following:
1. Reports for Norway Add-on Localization
2. Concurrent Programs for Norway Add-on Localization
Reports for Norway Add-on Localization
S. No. Program Name Oracle E-Business XML Publisher

Suite Template Code
1 CLE: Norwegian Telepay EMEA Add-on CLEF351ACKREP

acknowledgement import Localizations
and validation report
2 CLE: Norwegian Processed EMEA Add-on CLEF351TELREP

Telepay Payments Report Localizations
3 CLE: Norwegian Bank EMEA Add-on CLE_F351_BANK_STATUS

Reference and Status Report Localizations
4 CLE: Norwegian Bank EMEA Add-on CLEF351NOBANK

Statement by Details Report Localizations
Prerequisites 2-1
Concurrent Programs for Norway Add-on Localization
S. No. Program Name Oracle E-Business XML Publisher

Suite Template Code
1 CLE: Norwegian Telepay EMEA Add-on CLEF351LOAD

Acknowledgement Load Localizations
Program
2 CLE: Norwegian Bank EMEA Add-on CLEF350CESQLLDR

Statement Loader Localizations
3 CLE: Dynamic Due Date EMEA Add-on CLE_F353_DDDC

Calculation for AR Invoices Localizations
2-2 Oracle EMEA Add-on Localization User Guide for Norway

Chapter 3 General Setup Steps
Bank Acknowledgement codes definition

Definition of bank acknowledgement codes as mentioned in Norway telepay bank
acknowledgement file and mapping them with the corresponding acknowledgement
status established by ISO standards is mandatory for CLE: Norwegian Telepay
acknowledgement import and validation report.
To define bank acknowledgement codes navigate to Payments setup administrator

responsibilityOracle payments setupBank acknowledgement codes
Click on ‘GOTO Task’ icon Create button
Possible AH return codes (Bank status codes) and their description:

If a record contains several errors, the application header and BETFOR record will
appear for each error.
00 Batch rejected, but no errors in this record.

01 Batch ok received (R1).
02 Batch ok. This batch contains processed payment orders (R2).
10 Erroneous enterprise number/customer numbers
11 Cannot Change/Cancel
12 Total amounts of invoices/credit notes cannot be less than 0
13 Serial number does not exist or is invalid
14 Transaction type cannot be changed in BETFOR21
15 Missing debit/credit code
16 Mixing of structured/unstructured message information not allowed
17 Incorrect use of KID / invalid KID
18 Use of KID is mandatory for this beneficiary
19 Invalid credit account number
20 Invalid debit account number
21 Payment date invalid
22 Ref. no. does not exist or is invalid
25 Password expired (Password too old)
26 Operator locked
27 Invalid password
28 Operator not authorised
29 Invalid Operator ID
30 Invalid version number in BETFOR00
34 Error(s) in name/address fields
35 Incorrect currency code
36 Error in agreed exchange rate/forward rate
General Setup Steps 3-1

37 Invalid cheque code
38 Invalid charges codes
39 Invalid notification indicator
40 Invalid priority code
41 Invalid authority report code
42 Invalid amount field
43 Missing mandatory authority report free text for authority report code
44 Incorrect payee country code
45 Error in SWIFT code field
46 Error in bank code
47 Invalid production date
80 Error in sequence control field
81 Incorrectly constructed batch
82 Invalid transaction code
83 Seal invalid
84 Missing new seal key
85 Incorrectly constructed payment order
86 BETFOR not followed by sufficient number of records
87 Errors in BETFOR99
88 Errors in BETFOR00
89 Count error for number of transactions within a batch (BETFOR99)
90 Sequence error in AH-sequence (application header)
91 Unknown AH-PROCEDURE-ID
92 Invalid AH-TRANSACTION DATE
93 Freetext information exceeds the limits in the format
95 Invalid Division.
Bank Statement Mapping

Responsibility: Use any standard Cash Management responsibility
Navigation path: Setup-->Bank Statement Mapping
Patch installs the following Bank Statement Mapping setups. These need to be verified
once the patch installation is completed.
1. NO Telepay Map

Profile Options
Set the profile options ''CLE: Dynamic Due Date Calculation for AR Invoices':
Responsibility: System Administrator
Navigation path: Profile-->System
This profile option will be accessible only at organization level. This profile option
needs to be set to "Yes" if the transaction belonging to this organization is classified as
an Operating Unit and needs to be considered for Dynamic Due Date calculation. By
default the value will be null which is equivalent to value "No".
This profile option is required if the 'CLE: Dynamic Due Date Calculation for AR
Invoices' functionality is required.
Set the profile option 'JG: Territory':
This profile option can be used to set the value for the particular territory for which the
JG product is available. This is a mandatory setup step for the Localization Descriptive
Flex fields.
Ensure that the value defined for the profile option is 'Norway' at responsibility / user
level.
General Setup Steps 3-3

Chapter 4 CLE: Norwegian Telepay acknowledgement
import and validation report
Requirement
Requirement is to have program to import the bank acknowledgment data to Oracle

payments and to display the acknowledgement file validation information returned
by the bank.
The Acknowledgement file is a part of the Teleplay EFT payment service and also
legal requirement for all banks in Norway to produce such file. This solution is only
intended for customers receiving acknowledgement files in the Norwegian Telepay
format.
Overview
1. Acknowledgement file received from the bank is placed at a specified location.
2. User will execute the CLE: Norwegian Telepay acknowledgement Load Program by
providing the following parameter value:
• File Name: (Name of the Bank acknowledgement File along with file directory path).
3. CLE: Norwegian Telepay acknowledgement Load Program is a sql loader program

which takes the Bank acknowledgement file path as an input parameter and performs
the load process by uploading the acknowledgement input file that the bank sends
when it receives Telepay EFT file into custom tables.
4. User will then execute CLE: Norwegian Telepay acknowledgement import and
Validation report which imports the acknowledgement data into EBS and displays the
file validation information returned by the bank and prints each payment transfer
request with the status code that results. The report displays error sources that cause the
file/record to be rejected or displays OK if no errors exist.
5. CLE: Norwegian Telepay acknowledgement import and Validation report displays

the details of payment reference numbers grouped by Tax payer id and operating units
based on the payment data available in bank acknowledgement file for respective Legal
entity.
CLE: Norwegian Telepay acknowledgement import and validation report 4-1

Report Layout

Setup
Define the bank acknowledgement codes as mentioned in Norway

acknowledgement file and Map the bank’s acknowledgement status with the
corresponding acknowledgement status established by ISO standards. Possible
Bank acknowledgement codes for Norway are mentioned in chapter 3 under
‘General setup steps’ section.

Transactions Processing
 Create Invoices in Payables module.
 Make EFT payments using the Norwegian Telepay format and ensure that
payments are formatted and sent to the bank.
 Include Bank acknowledgement codes and Payment reference numbers in the
Bank acknowledgement file in specified positions for respective BETFOR
records and place the file in appropriate location.
 Run CLE: Norwegian Telepay Acknowledgement Load Program to upload the
acknowledgement file and the CLE: Norwegian Telepay File Validation report
to display the file validation information returned by the bank.
 CLE: Norwegian Telepay Acknowledgement import and Validation report first
calls the IBY API to import Payment Acknowledgement data into EBS and
then displays the file validation information.
How to Launch the Program

The Bank acknowledgment file received from the bank will be placed at a specified
location in the system.
Responsibility: Use any standard Payables responsibility
Navigation path: View--> Request -->Submit a New Request -->Single Request
CLE: Norwegian Telepay Acknowledgement Load Program by specifying the

Parameter file name along with file directory path.

Program Parameters for CLE: Norwegian Telepay Acknowledgement
Load Program
The program parameters are:
S. No. Parameter Description Required
1 File Bank acknowledgement file name to be Yes

Name entered manually by the user along with the
server location where the data file is uploaded.
Upon successful completion of CLE: Norwegian Telepay Acknowledgement Load

Program run CLE: Norwegian Telepay acknowledgement import and validation report.
 CLE: Norwegian Telepay Acknowledgement Load Program log file

shows the number of records loaded and those, which were rejected,
arguments received by report program, exceptions handled and
Timestamp of start & end report.
 CLE: Norwegian Telepay acknowledgement import and validation

report doesn’t have parameters and log file shows the errors returned by
IBY’s API namely ‘Payment acknowledgement import public API’,
arguments received by report program , exceptions handled and Timestamp of
start & end report.

CLE: Norwegian Telepay acknowledgement import and validation report
Report Headings
Report Title: The title of the report "CLE: Norwegian Telepay File Validation Report".
Page: Total page numbers of the report.
Date: Date of generating the report.
Tax Payer Id: Tax payer id of the Legal entity.
Operating Unit: Name of operating unit for which report is run.
Production Date: The date that the Bank acknowledgement file is produced and
identifies the production date of the batch. This information is available in Bank
acknowledgement file in BETFOR00: Start –of-batch record with (Position 81-84), length
is 4 and format is MMDD. This field is not confused with payment date.
Column Headings
Code: Code number that the bank sends for each transaction and is taken from Bank
acknowledgement file. This is from AH return codes from positions 4-5 with length 2
numeric characters in bank acknowledgement file.
Return Message: The explanation of the Bank code in the ‘Code’ field.
Sequence number: The sequence in Telepay file.
Reference number: The bank reference from the acknowledgement file. Reference
number for BETFOR01/02/03/04 and BETFOR21/22/23 is from (Position 75-80) with
length 6 alpha numeric characters The reference number is supplied by the bank in the
acknowledgment reply (R1) and also used in the processing reply(R2). The reference
number must be supplied when transmitting an electronic request for cancellation of
payment orders.
Pay date: The date of payment of respective payment reference number.
Supplier Name: Name of Supplier for whom Payment is made.
Account: Supplier Bank account number.
Document Number: Payment Document number which is taken from Bank

acknowledgement file.
Amount: Payment amount.
Currency: Payment currency.
Acknowledgement status: Acknowledgement status of the payments. The report shows

‘Y’ if Payment is acknowledged
Row Headings
Accepted Transfer Transactions (Domestic): The number of accepted records that are in
a domestic currency
Rejected Transfer Transactions (Domestic): The number of rejected records that are in a
domestic currency
Accepted Transfer Transaction (Foreign): The number of accepted records that are in a
foreign currency
Rejected Transfer Transactions (Foreign): The number of rejected records that are in a
foreign currency
Accepted Amount (Domestic): The total amount of the accepted records that are in a
domestic currency
Rejected Amount (Domestic): The total amount of the rejected records that are in a
domestic currency
Accepted Amount (Foreign): The total amount of accepted records that are in a foreign
currency.
Rejected Amount (Foreign): The total amount of rejected records that are in a foreign
currency.
Summary Details
Once all of the above programs have completed successfully, then user can see the
payment acknowledgement information in Payables responsibility.
Login under Payables responsibility > Payments:Entry > Payments Manager >
Payments tab > query up an existing "formatted" payment:

Click on the ‘amount’ field.
Click on ‘Acknowledgement information’.
Acknowledgement status can also be seen at payment s workbench by using ‘show field’.

Chapter 5 CLE: Norwegian Bank Statement Loader
Program
Requirement
Requirement is to load the Payment clearing file into the Cash Management Module
and ensure bank reconciliation is completed. This solution is only intended for
customers receiving payment clearing files in the Norwegian Telepay format.
Overview
1. Payment clearing file received from the bank will be placed at a specified location.
2. User will execute the CLE: Norwegian Bank Statement Loader Program by
providing the following parameter values:
• Loading Name: NO Telepay Map
• Data File Name: (Name of the Payment clearing File)
• Directory Path: Path where the data file is stored
This program will take the Payment clearing file path as an input parameter and
perform the load process.
This program will internally call additional programs when executed:
• Run SQL*Loader- CLE_F350_NO
• CLE: NO Load Bank Statement Data
• Bank Statement Loader Execution Report
• Bank Statement Import & Auto Reconciliation (Standard Program)
CLE: Norwegian Bank Statement Loader Program 5-1

• Auto Reconciliation Execution Report
CLE: Norwegian Bank Statement Loader Program uploads, imports the Payment
clearing file and ensures the reconciliation is completed successfully in Cash
Management.
Setup
Define Bank Transactions codes:

Bank Transaction codes must be defined for all possible transactions that can be loaded by the
'CLE: Bank Statements Loader' program, and for all bank accounts expected to be used to load
Bank Statements.
Navigation path: Setup-->Banks-->Bank Transaction Codes:
• Select the bank account number.
• Type should be "Payment"
• Define the following list of Bank Transaction Codes Required for foreign and domestic
transaction.
1. BETFOR01
2. BETFOR02
3. BETFOR03
4. BETFOR04
5. BETFOR21
6. BETFOR23
• Enter the description of the codes.
• Enter Effective start date for the code.
Transactions Processing
1. Run the CLE: Norwegian Bank Statement Loader Program in order to import, load
and reconcile the Bank Statements based on the statement file. Once Bank Statement
Loader Program is launched, the following set of programs will be automatically
initiated:

• Run SQL*Loader- CLE_F350_NO:This is used to upload the bank file data in a
temporary table.
• CLE: NO Load Bank Statement Data:This is used to upload interface tables

from the temporary table. The Bank Statement Interface form (navigate to the
Bank Statement Interface) can be used to review the content of the files and any
error messages. This is a standard program where some modification has been
made. Validations on the interface data is completed by the program and the
following exceptions are handled. These exceptions will be displayed in the log
file.
1. Error while updating a foreign payment from a foreign currency account.
2. Error while checking transactions.
This program will internally call the Bank Statement Loader Execution Report,
Bank Statement Import & Auto Reconciliation report and Auto Reconciliation
Execution Report:
• Bank Statement Loader Execution Report: This is standard report available in

the application.
• Bank Statement Import & Auto Reconciliation: This is a standard program

and will create bank statement from interface files. This request is started for
each bank account reported in the file. Once it's completed it will launch the
auto reconciliation execution report.
• Auto Reconciliation Execution Report: This is a standard report available in

the application.
How to Launch the Program

The payment clearing file received from the bank will be placed at a specified location
in the system.
Navigation path: View--> Request -->Submit a New Request -->Single Request

Program Parameters
The program parameters are:
1 Loading "NO Telepay Map" will be defaulted Yes

Name automatically.
2 Data file Data file name to be entered manually by the Yes

Name user. The name used should be similar to the
Payment Clearing File received from the bank.
3 Directory Enter the server location where the data file is Yes
Path uploaded.
4 Bank Branch You can choose the names of the Bank Branches No
Name from the List of Values. Optionally, the user can
leave this field empty to load all the data from
the bank file.
5 Bank You are able enter a value in this field if any No

Account value in the Bank Branch Name parameter has
Number been entered.

6 GL Date The default value is the System Date. No
Upon successful completion of CLE: Norwegian Bank Statement Loader Program the
following programs will be automatically submitted. Ensure to check that all of these
programs have been completed without any exceptions.
• Run SQL*Loader- CLE_F350_NO
• CLE: NO Load Bank Statement Data
• Bank Statement Loader Execution Report
• Bank Statement Import & Auto Reconciliation
• Auto Reconciliation Execution Report
Once all of the above programs have completed successfully, then the user can see the
uploaded Bank Statement in the Cash Management responsibility.
Navigation path: Bank Statement-->Bank Statement and Reconciliations
Enter the Bank Account and other Details for the Search.

Chapter 6 CLE: Norwegian Processed Telepay
Payments Report
Overview
The CLE: Norwegian Processed Telepay Payments Report displays EFT payment details
in two different sections, based on payment type.
First section displays the EFT payment made and the second section displays the
summary of the number of payments made based on payment type and transaction
format.
CLE: Norwegian Processed Telepay Payments Report 6-1

Report Layout
How to Launch Report

Navigation path: View-->Request-->Submit a New Request-->Single Request
Run: CLE: Norwegian Processed Telepay Payments Report.

Report Parameters
The report parameters are:
S. No. Parameter Description Required LOV
1 Account Default value will be NULL.This Yes Yes

Number parameter will display all Internal
Bank account numbers defined (both
active and inactive). If there is at least
one common operating unit between
Bank Account Access setup and MO
Security Profile then users will be able
to see the bank account. The report
can only be run for one bank account
at a time.
2 From Period The List of Values will contain all Yes Yes
periods for the primary ledger that is
attached to the legal entity.
3 To Period The List of Values will contain all Yes Yes

periods for the primary ledger that is
attached to the legal entity.
4 From Date Enter a date if you want to limit the No No

report to show transactions during a
particular time period.
5 To Date Enter a date if you want to limit the No No

report to show transactions during a
particular time period
Report Headings
Report Title: The title of the report "CLE: Norwegian Processed Telepay Payment
Report".
Bank Account: Bank Account should be displayed in the same way as selected in the
report parameters. Bank account numbers in Norwegian banks always have 11 digits.
From To Period: It should be displayed according to selected in report parameters.
From to Date: From to date should be displayed according to report parameters.
This will be based on ICX: Date format.
CLE: Norwegian Processed Telepay Payments Report 6-3

Page:Total page numbers of the report.
Column Headings
Date: Transaction date would be displayed in the column.
Payment Type: Payment methods used for making the payments.
Transaction Format: Transaction format value will be derived based on following logic:
• If the currency code is 'NOK' and if there is no remit to account defined for supplier
then 'payment order' would be displayed.
• If the currency code is NOK and supplier has a remit to a/c defined and if the
payment is made with remittance advice then "with remittance advice" would be
displayed.
• If the payment currency code is NOK and payment is made without remittance
advice, then "Without Remittance Advice" would be displayed on the report
• In case of foreign payments then "Regular" will be displayed for foreign payments.
Document Number: Transaction number would be displayed in the column.

Supplier Number: Supplier number would be displayed in this column.
Supplier Name: Supplier name would be displayed in this column. If the name of
the supplier is longer than the column width then it will wrap to the next line.
Bank Account Number: Supplier's bank account number will be displayed.
Invoice Number: One line per invoice number will be displayed. If multiple
invoices/credit memos and debit memos are paid in one payment, then all such invoice
payment amounts and invoice/credit and debit memo numbers will be displayed
separately.
Currency: The currency in which invoice is paid.
Amount: Paid invoice amount will be displayed in this column. The format will
be based on ICX: Number Format.
Summary Details
Payment Type Name of the payment types in generated report. Transaction
Format: Name of the transaction format in generated report. Payments: Count of
payments against combination of payment type and transaction
format in generated report.

Chapter 7 CLE: Norwegian Bank Reference and
Status Report
Overview
CLE: Norwegian Bank Reference and Status report displays EFT payment details
including the bank reference number that the system has received on the payment
transaction from the bank, and the AP payment status. Bank reference number is the
number that the bank inserts in the acknowledgement file as an audit trial between bank
and customer transaction. In this report user can choose the bank account as well as the
lowest and highest document number for which to print the report and can search for all
AP Payment statuses or one status in particular.
CLE: Norwegian Bank Reference and Status Report 7-1

Report Layout

User Procedure
 Define the bank acknowledgement codes as mentioned in acknowledgement
file and Map the bank’s acknowledgement status with the corresponding
acknowledgement status established by ISO standards.
payment acknowledgement file in specified positions for respective BETFOR
records.
 Payment acknowledgement file received from the bank will be placed at a
specified location.
 Run CLE: Norwegian Telepay acknowledgement import and validation report
to upload the payment acknowledgement file data from server to payables and
 Place the R2 file (Processing reply file consists of Processed and cancelled
orders) in Specified path and Run CLE: Norwegian Bank Statement Loader and
Reconciliation Program to upload the bank statement file /R2 file from server to
Cash Management and perform the auto-reconciliation process. However this
step is not prerequisite to run the CLE: Norwegian Bank Reference and Status
Report but this is pre-requisite to achieve payment statuses from the later stages
of the payment cycle.
 Run CLE: Norwegian Bank Reference and Status Report.

Responsibility: Use any standard Payables responsibility
Navigation path: View-->Request-->Submit a New Request-->Single
Request Run: CLE: Norwegian Bank Reference and Status Report.

Report Parameters
The report parameters are:
1 Bank Account Name Displays all Internal Bank account Yes Yes
names along with account numbers
defined (both active and inactive). If
there is at least one common
operating unit between Bank
Account Access setup and MO
Security Profile then users will be
able to see the bank account name.
The report can only be run for one
bank account at a time.
2 From Document Number List of Values displays Payment Yes Yes

document numbers available for the
selected Bank account. Document
number here refers to Payment
reference number or Paper document
numbers available for Oracle
Payments.
3 To Document Number List of Values displays Payment Yes Yes

document numbers available for the
selected Bank account and the
selected document number should
be equal or greater than From
document number.
4 AP Payment Status List of Values displays AP Payment No Yes

statuses available in the Oracle
applications. If nothing is selected
then report displays details of all
document numbers selected above
along with their AP Payment
statuses. AP Payment status
comprises of the following statuses:
Cleared, Cleared but Unaccounted,
Issued, Negotiable, Overflow,
Reconciled, Setup, Spoiled, Stop
Initiated, Unconfirmed Setup,
Voided, Reconciled but
Unaccounted.

Report Headings
Report Title: The title of the report "CLE: Norwegian Bank Reference and Status
Report”.
Operating Unit: Name of the Operating unit for which report is run is displayed.
Bank Account: Bank Account name selected in report parameters is displayed.

Page: Total page numbers of the report.
Column Headings
Document Number: Document numbers within the range selected in report parameters are displayed.
Payment Batch: Displays payment batch name for the document numbers selected in report parameters.
Supplier Name: Payee’s / supplier name of corresponding invoice is displayed.
Invoice number: Invoice number of corresponding document numbers selected in report parameters is
displayed.
Invoice date: Invoice date of corresponding document numbers selected in report parameters is
displayed. Format is ICX: Date Format.
Amount: The payment currency amount of the paid invoice. The format is based on ICX: Number
Format.
Bank reference Number: This is the reference number given by the bank for the transaction in its
acknowledgement reply (R1). This value is taken from ‘Bank Assigned reference code 2’ field. To view
this navigate to Payables responsibility > Payments: Entry > Payments Manager > Payments tab > query
up an existing "formatted" payment: Click on the ‘amount’ field.
Click on ‘Acknowledgement information’ Bank Assigned reference code 2.
Status: Displays the AP payment status of corresponding document numbers selected in report
parameters.

Chapter 8 CLE: Norwegian Bank Statement by
Details Report
Overview
CLE: Norwegian Bank Statement by Details Report displays EFT payment details by
comparing the Payee’s account number and payments amount on the file sent to bank
with the actual values on the payment clearing file from the bank. If there is any
deviation, the report shows deviation with deviation code.
The report prints variance code ‘B’, if there is any variance between original amount and
bank statement amount. It prints variance code ‘K’, if there is any variance between
original account and payee's account as per bank statement. Original amount and
account here refers to amount and account details from payables module as of the time
the invoices were selected for payment. Bank statement amount and payee's account as
per bank statement refers to details from payment clearing file which is loaded to cash
management module.
Report displays the details of bank statement lines based on operating unit wise and
break level I.e. either on Bank Account or Statement level selected in report parameters.
This break level indicates the report to have a page break for every bank account or for
every bank statement level. If break level is Bank account, report groups all the Bank
statement lines based on Bank account and operating unit wise. If break level is
Statement, report groups all the Bank statement lines based on statement number,
statement date and operating unit wise
CLE: Norwegian Bank Statement by Details Report 8-1

Report Layout

User Procedure
 Define the bank acknowledgement codes as mentioned in acknowledgement
file and Map the bank’s acknowledgement status with the corresponding
acknowledgement status established by ISO standards.
payment acknowledgement file in specified positions for respective BETFOR
records.
 Payment acknowledgement file received from the bank will be placed at a
specified location.
 Run CLE: Norwegian Telepay acknowledgement import and validation report
to upload the payment acknowledgement file data from server to payables and
 Place the R2 file (Processing reply file consists of Processed and cancelled
orders) in Specified path and Run CLE: Norwegian Bank Statement Loader and
Reconciliation Program to upload the bank statement file /R2 file from server to
Cash Management and perform the auto-reconciliation process.
 Run CLE: Norwegian Bank Statement by Details Report.

Responsibility: Use any standard Cash management responsibility
Navigation path: View-->Request-->Submit a New Request-->Single
Request Run: CLE: Norwegian Bank Statement by Details Report.

Report Parameters
The Report Parameters are:

1 Statement or Account List of Values includes two values Yes Yes
namely Statement and Bank
Account. This is the break level
which indicates the report to have a
page break for every bank account
or for every bank statement level.
2 Bank Account Displays all Internal Bank account No Yes
numbers defined (both active and
inactive). If there is at least one
common operating unit between
Bank Account Access setup and
MO Security Profile then users will
be able to see the bank account. If
bank account is not selected, then
the report can be run for all bank
accounts and OUs that user have
access for the responsibility from
which report is run.
3 Statement Number From Displays the List of statement of No Yes
account numbers available for bank
account selected. User selects the
Statement from which he wants to
compares the amount and account
number variances.
4 Statement Number To Displays the List of statement of No Yes
account numbers available for bank
account selected. User selects the
Statement till which he wants to
compares the amount and account
number variances.
5 Statement Date From Based on the statement number No No
selected above, user enters a range
of dates to see information only for
statement lines that fall within those
dates. The format is based on the
ICX: Date Format
6 Statement Date To Based on the statement number No No
selected above, user enters a range
of dates to see information only for
statement lines that fall within those
dates. The format is based on the
ICX: Date Format.

Report Headings
Report Title: The title of the report is "CLE: Norwegian Bank Statement by
Details Report".
Operating Unit: Name of the Operating unit for which report is run is
displayed.
Break Level: This is the break level which indicates the report to have a page
break for every bank account or for every bank statement level.
Statement Number: For Parameter ‘Statement or Account’ if value is

account, then value is from table
‘AP_BANK_ACCOUNTS_ALL.bank_account_num’ and if value is
Statement, then value is from table
‘CE_STATEMENT_HEADERS.statement_number’ is displayed.
Statement Date: Statement date is displayed.
Bank Branch Name: Corresponding Bank Branch name is displayed as per

the Bank Account Number selected in report parameters.
Bank Account Number: Bank Account Number is displayed the same as

selected in report parameters. Bank account numbers in Norway always
have 11 digits.
Bank Name: Corresponding Bank Name should be displayed based on Bank

Account number selected in Parameter ‘Bank Account number’.
Bank Account Name: Corresponding Bank account Name should be

displayed based on Bank Account number selected in Parameter ‘Bank
Account number’.

Bank Account Currency: Corresponding Bank account currency name
should be displayed based on Bank Account number selected in Parameter
‘Bank Account number’.
Page No: Total page numbers of the report.
Report Date: Date of generating the report.
Column Headings
Line Number: The sequence of the records in the CLE: Norwegian bank
statement by details report is displayed.
Bank Statement Number: Bank statement numbers within the account or the
selected range of statement numbers selected in report parameters is
displayed.
Transaction Number: Bank Transaction number from Bank statement lines

window is displayed.
Supplier Number: Payee’s / supplier number of corresponding invoice is

displayed.
Supplier Name: Payee’s / supplier name of corresponding invoice is

displayed.
Invoice number: Invoice number of corresponding payment reference

number in payment clearing file is displayed.
Original account no: Bank Account number from the bank instruction sent
to bank for domestic and foreign EFT payments is displayed. This is taken
from the selected invoice payments data.
Payee account no: The payee’s bank account number actually credited;
stored in attribute7 which is uploaded from bank statement file (R2) through
Bank reconciliation concurrent program is displayed.
Currency: The Currency Code in which invoice is paid is displayed.
Original amount: The payment currency amount of the paid invoice. The
format is based on ICX: Number Format.
Settled amount: Paid currency amount available in Bank statement lines

window in cash management is displayed.
Variance: Displays value “K” if deviation in account exists and “B” if

deviation in amount exists.
Functional Amount: Amount in Functional Currency. Total amount in

functional currency is grouped and displayed in the bottom of the column.

Chapter 9 Index
Profile Options, 3-1

A Program Parameters, 4-4
Add-on Localizations Overview, 1-1
Assignment of Concurrent Programs to Request R
Groups, 2-1 Report Headings, 5-3
Report Layout, 5-2, 6-2
B Report Parameters, 5-3, 6-3
Requirement, 4-1, 6-1
Bank Statement Mapping, 3-1
C S
Setup, 4-2
CLE: Dynamic Due Date Calculation for AR
Summary Details, 5-4
invoices, 7-1
CLE: Norwegian Bank Statement Loader
Program, 5-1 T
CLE: Norwegian Telepay acknowledgement Transactions Processing, 4-2, 6-2
import and validation report, 4-1
CLE: Norwegian Processed Telepay Payments
Report, 5-1
Column Headings, 6-4
CLE: Norwegian Bank Reference and Status
Report, 8-1
CLE: Norwegian Bank Statement by Details
Report, 9-1
G
General Setup Steps, 3-1
H
How to Launch Report, 5-2
How to Launch the Program, 4-3, 6-3
O
Overview, 4-1, 5-1, 6-1
P
Prerequisites, 2-1
Index 9-1

122CLENOUG v2 27MAR18

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

122CLENOUG v2 27MAR18

Uploaded by

Copyright:

Available Formats

Oracle® EMEA Add-on Localization

User Guide for Norway

Part No. E49866-01

reserved. Primary Author: Zlatko Alvir

U.S. GOVERNMENT RIGHTS

CHAPTER 1 ADD-ON LOCALIZATION OVERVIEW ....................................................................... 1-1

CHAPTER 2 PREREQUISITES .............................................................................................................. 2-1

CHAPTER 3 GENERAL SETUP STEPS ................................................................................................ 3-1

CHAPTER 4 CLE: NORWEGIAN TELEPAY ACKNOWLEDGEMENT IMPORT AND

CHAPTER 5 CLE: NORWEGIAN BANK STATEMENT LOADER PROGRAM ............................ 5-1

CHAPTER 6 CLE: NORWEGIAN PROCESSED TELEPAY PAYMENTS REPORT ..................... 6-1

CHAPTER 8 CLE: NORWEGIAN BANK STATEMENT BY DETAILS REPORT ........................ 8-1

CHAPTER 9 INDEX .................................................................................................................................. 9-1

Deaf/Hard of Hearing Access to Oracle Support Services

Accessibility of Links to External Web Sites in Documentation

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Add-on Localizations for Norway

Add-on Localization Overview 1-1

Assignment of Concurrent Programs to Request Groups

2. Concurrent Programs for Norway Add-on Localization

Reports for Norway Add-on Localization

S. No. Program Name Oracle E-Business XML Publisher

1 CLE: Norwegian Telepay EMEA Add-on CLEF351ACKREP

2 CLE: Norwegian Processed EMEA Add-on CLEF351TELREP

3 CLE: Norwegian Bank EMEA Add-on CLE_F351_BANK_STATUS

4 CLE: Norwegian Bank EMEA Add-on CLEF351NOBANK

S. No. Program Name Oracle E-Business XML Publisher

1 CLE: Norwegian Telepay EMEA Add-on CLEF351LOAD

2 CLE: Norwegian Bank EMEA Add-on CLEF350CESQLLDR

3 CLE: Dynamic Due Date EMEA Add-on CLE_F353_DDDC

2-2 Oracle EMEA Add-on Localization User Guide for Norway

Bank Acknowledgement codes definition

To define bank acknowledgement codes navigate to Payments setup administrator

Possible AH return codes (Bank status codes) and their description:

00 Batch rejected, but no errors in this record.

General Setup Steps 3-1

Bank Statement Mapping

3-2 Oracle EMEA Add-on Localization User Guide for Norway

General Setup Steps 3-3

Requirement is to have program to import the bank acknowledgment data to Oracle

1. Acknowledgement file received from the bank is placed at a specified location.

3. CLE: Norwegian Telepay acknowledgement Load Program is a sql loader program

5. CLE: Norwegian Telepay acknowledgement import and Validation report displays

CLE: Norwegian Telepay acknowledgement import and validation report 4-1

4-2 Oracle EMEA Add-on Localization User Guide for Norway

Define the bank acknowledgement codes as mentioned in Norway

CLE: Norwegian Telepay acknowledgement import and validation report 4-3

How to Launch the Program

CLE: Norwegian Telepay Acknowledgement Load Program by specifying the

4-4 Oracle EMEA Add-on Localization User Guide for Norway

The program parameters are:

S. No. Parameter Description Required

1 File Bank acknowledgement file name to be Yes

Upon successful completion of CLE: Norwegian Telepay Acknowledgement Load

 CLE: Norwegian Telepay Acknowledgement Load Program log file

 CLE: Norwegian Telepay acknowledgement import and validation

CLE: Norwegian Telepay acknowledgement import and validation report 4-5

Page: Total page numbers of the report.

Date: Date of generating the report.

Tax Payer Id: Tax payer id of the Legal entity.

Operating Unit: Name of operating unit for which report is run.

Sequence number: The sequence in Telepay file.

Pay date: The date of payment of respective payment reference number.