12.2 IL Open Format UG 26 Feb 2018

Oracle® EMEA Add-on Localizations User
Guide for Israel Open Format Solution
Release 12.2
Part No. E49988-01
Feb 2018
Oracle CLE User Guide EMEA Consulting Localizations User Guide for Localization-Israel Open Format
Solution, Release 12.2
Part No. E49988-01
Copyright © 2009, 2011, 2013 Oracle and/or its affiliates. All rights reserved.
Primary Author: Chytanya Galam, Pawan Kumar Tallam and Anup Naik
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 or hardware 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 that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then
you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure
its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware 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
Contents .......................................................................................................................................................... iii
Preface .............................................................................................................................................................. vi
1 - Add-on Localizations Overview ................................................................................................................ 2-1
Objective ................................................................................................................................................... 2-1
2 - CLE Israel Open Format Solution .............................................................................................................. 2-1
Business requirement: .............................................................................................................................. 2-1
Implementation......................................................................................................................................... 2-1
Prerequisites & Assumptions .................................................................................................................... 2-1
3 - CLE: Israeli Localization Populating Open Format Tables (Request Set) .................................................. 3-3
Objective ................................................................................................................................................... 3-3
Parameters ................................................................................................................................................ 3-4
Processing.................................................................................................................................................. 3-5
Snapshot of the Output ............................................................................................................................. 3-9
Exception ................................................................................................................................................. 3-10
Log file ..................................................................................................................................................... 3-10
4 - Child Requests .......................................................................................................................................... 4-1
CLE: IL OF Generate Header Record (A100) Program ............................................................................... 4-1
CLE: IL OF Collect Acct Index and Account Journals ..................................................................................... 3
CLE: IL OF Collect Documents Header and Document Lines Program ......................................................... 4
CLE: IL OF Collect Inventory Balances (M100) Program ............................................................................ 4-8
CLE: IL OF Generate Wrapper Record (Z900) Program ................................................................................ 9
CLE: Israeli Localization Open Format Generate INI Data .......................................................................... 10
CLE: INI Counter Report .......................................................................................................................... 4-11
CLE: C100 Documents Summary Report ................................................................................................. 4-12
CLE: Israeli Localization Open Format File Generation BKMVDATA .......................................................... 14
E-Text Program and CLE: Israeli Localization Open Format File Generation INI E-Text Program .............. 14
5 - Position details of BKMVDATA and INI text files ...................................................................................... 5-1
Introduction............................................................................................................................................... 5-1
6 - General Setup Steps ................................................................................................................................. 6-1
iii
Overview ................................................................................................................................................... 6-1
Attach Form Personalization functions to the menu ................................................................................ 6-8
7 - Technical Prerequisites ............................................................................................................................ 7-1
Introduction............................................................................................................................................... 7-1
Localization Descriptive Flex Field............................................................................................................. 7-1
LDFF: AR Invoice Transaction Type............................................................................................................ 7-6
LDFF: AR Receipt type ............................................................................................................................... 7-8
LDFF: AR Receipts – CLE: Additional Info On Cash Receipts...................................................................... 7-9
Profile Options......................................................................................................................................... 7-14
Tax Authority Document Setup ............................................................................................................... 7-14
8 - Index .......................................................................................................................................................... 16
Symbols ...................................................................................................................................................... 16
iv
Send Us Your Comments
Oracle CLE User Guide EMEA Consulting Localizations User Guide for Localization-Israel
Open Format Solution, Release 12.2
Part No. E49988-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 CLE User Guide EMEA Consulting Localizations
User Guide for Localization-Israel Open Format Solution.
It includes information to help you understand the information of Israel Open

Format Solution aspects and to implement it effectively for an Israeli Customer:
• Add-on Localization Overview
• Add-on Localization Setup
• Add-on Localization Reports
About this Localization Manual

This manual is to be referred in conjunction with Oracle Applications –Release 12.2
Reference Manuals of the respective modules.
User Guides Related to This Add-On Localization

This guide contains references to the following Oracle publications. Use the Release 12.2
versions of these guides, unless otherwise specified.
• Oracle Receivables User Guide
• Oracle Payables User Guide
• Oracle Order Management User Guide
• Oracle Purchasing User Guide
• Oracle Inventory User Guide
• Oracle E-Commerce Gateway User Guide
vi
Audience for this Manual
This manual is a source of information about Israeli requirements and designed
to provide useful guidance and assistance to:
• Consultants implementing Israel Open Format Solution for Oracle Applications
Release 12.2
• Key User team of Oracle Applications
The Israel Localization guide assumes the users to have a basic understanding of
core modules and the country specific localization requirement. If users have never
used Oracle Applications, we suggest users to attend one or some of the Oracle
training classes available through Oracle Education Services.
Installation
This Add-On localization is installed after the base install of Oracle e-Business Suite.
The Israel Localization patches to be applied are available for download from Metalink.
Please ensure the prerequisites are taken care before installing the patch, especially the
product splicing for CLE (EMEA Add-On Localizations).
Once the patches are installed, please ensure that the Post-installation steps are
completed. These patches create Localization Descriptive Flex field definitions for
use
to store the additional information; the user should not modify these definitions at any
time. The user needs to fill the required values in the Descriptive Flex fields.
See Related Information Sources on page ix for more Oracle E-Business Suite
product information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/
Structure
1 Add-on Localizations Overview
2 CLE Israel Open Format Solution
3 CLE: Israeli Localization Populating Open Format Tables (Request Set)
4 Child Requests
5 Position details of BKMVDATA and INI text files
6 General Setup Steps
7 Technical Prerequisites
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
1
Chapter 1 Add-on Localizations Overview
Objective
Oracle EMEA Add-On Localizations for Israel provides additional functionality to help
Israeli customers to meet legal and business requirements for tax authority reporting
as a part of core General Ledger, Oracle Payables, Oracle Receivables, Purchasing,
Order management, Inventory, Work In Progress (WIP) and E-Commerce Gateway
products. Israel Add-On Localization provides the functionality not available in core
product but essential for Israeli customers. This User Guide provides details about setup
and functionality of the Israeli Tax Authority Open Format file generation.
This Israel Open Format File User Guide describes the requests CLE: Israeli
Localization Populating Open Format Tables, CLE: Israeli Localization Open Format
Generate INI Data, C L E : Israeli Localization Open Format File Generation BKMVDATA
E-Text Program and CLE: Israeli Localization Open Format File Generation INI E-Text
Program.
Note: R11i upgraded data will not be considered in the generated file.
Add-on Localizations Overview 2-1

2
Chapter 2 CLE Israel Open Format Solution
Business requirement:
From the year 2006 the Israeli Tax Authority require the accounting software to provide
ASCII files with detailed information regarding transaction information like posting
entries in General Ledger and various sub-ledger transaction information like customer
receipts, inventory receipts, supplier invoices, customer invoices, sales order, returns to
vendors. The outcome of this requirement will be generation of two data files, these
two data files should be saved with names as per the Israeli Tax Authority requirement
(BKMVDATA.TXT and INI.TXT).
Implementation
Below setups are required for working of Open Format feature:
a)Oracle's General Ledger, Oracle Payables, Oracle Receivables,

Oracle Purchasing, Oracle Order management, Oracle Inventory and Work In Progress
(WIP)guides.
b)Installation setup steps provided as part of this User Guide
Prerequisites & Assumptions

The following mandatory setup steps need to be completed before using this solution.
• Data Access Set Profile option.
• Legal Entity setup and Open Format Solution necessary information has
been completed.
CLE Israel Open Format Solution 2-1

• Localization Descriptive Flex field setup at Balancing Segment Value (BSV) has
been completed.
• Localization Descriptive Flex field setup at Receipt Class for each operating unit
has been completed.
• Localization Descriptive Flex field setup at Transaction Types for each operating
unit has been completed.
• Localization Descriptive Flex field setup at Receipts and this is used for
capturing the additional information related to credit card payments.
• The existing customers who are still using DFF (Descriptive Flex Field) need to
discontinue DFF setup and start using Localization DFF introduced.
• The user needs to query for DFF 'Receipts' and manually disable the following 3
context codes namely:
1. IL.CREDIT_CARD_INFO --- Additional information on Israel Credit Card Deal.

2. IL.CLE_IL_OF_CHECK_INFO --- Additional information on Israel Check.
3. IL. IL_OF_DOC_TYPE --- Additional information on Israel Document Type.
• The existing data from DFF will be migrated automatically to Localization tables
after applying the Open Format patch.
• It is assumed that user enters no transaction in the period for which data
are extracted. This may generate an incorrect data.
• Only posted journals are considered from General ledger
• Only Purchasing Order types Like Standard, blanket and planned PO with
approval status as 'approved' and 'closed' status are considered.
• Taxes entered at transaction header or lines are selected for extraction.
• Tax calculation will happen based on the definition in E-Business Tax.
• The Legal Entity is derived from the standard setup from Organization.
• Request set can be run for Primary Ledger only.
• Request set can be run for a date range, irrespective of period status.
2-2 Oracle® EMEA Add-on Localizations User Guide for Israel Open Format Solution
3
Chapter 3 CLE: Israeli Localization Populating Open
Format Tables (Request Set)
Objective
This request set consists of different requests; each request populates the data for
different document type. The data is populated to different CLE tables from the tables.
Following is the list of Concurrent Programs forming part of the request set, presented in
sequence. The last two reports in the request set where added after a new legal
requirement for these summarization reports of the data collected in the previous
requests of the relative set.
This program can also be run separately In case the user wants to run all child
concurrent programs in the same sequence as in the request set. However, it is
suggested not to run these requests individually.
Display Sequence Stage Program Description
10 CLE: IL OF Generate Header Populate table with

Record (A100) BKMVDATA.TXT file first
record data (A100)
20 CLE: IL OF Collect Acct Index Populate table with

and Account Journals Accounting Index (B110) and
GL Journals (B100)
30 CLE: IL OF Collect Document Populate table with PO, SO,

Header and Document Lines Invoices, header data (C100),
lines data (D110) and
Remittance lines data (D120)
40 CLE: IL OF Collect Inventory Populate table with Inventory

Balances (M100) Items balance data (M100)
CLE: Israeli Localization Populating Open Format Tables (Request Set) 3-3
50 CLE: IL OF Generate Populate Table with
Wrapper Record (Z900) BKMVDATA.TXT file closing
record data (Z900)
60 CLE: Israeli Localization Generates INI Data File.

Open Format Generate INI
Data
70 CLE: INI Counter Report show INI file in specific Israeli

Format.
80 CLE: C100 Documents A new report that summarizes

Summary Report the C100 records (count and
amounts)
Each concurrent program in the request set populates the specific document type
into the CLE tables. The requests are submitted in the sequence assigned at the
header level of the request set. They are submitted sequentially and in case any
request completes in warning, the data is rolled back for that document type. The
Subsequent concurrent requests continue whether the previous concurrent requests
completes in normal/warning.
Parameters
The following table details the list of parameters to be given while submitting
the request set. The required output is based on the parameters entered here
Parameter Required (Y/N) Displayed (Y/N) Default Value List Of Values
Ledger Yes Yes Null This List Of Values

will list Primary
ledger attached in the
Data Access Set.
Legal Entity Yes Yes Null This LOV will list all
the Legal Entities
available under the
Ledger selected
above.
Start Date Yes Yes Null The format of the start

date should be in
YYYY.MMM.DD and
within the range of
year chosen above
End date Yes Yes Null The format of the start
date should be in
YYYY.MMM.DD and
within the range of
year chosen above
Conversion Rate Type Yes Yes Corporate Rate The LOV will contain
Conversion Rate
Types available
except ‘User’ Rate
type.
Constant No Yes Null Free text,

alphanumeric field of
length 50 characters.
Future Use No Yes Null Free text,

alphanumeric field of
length 50 characters.
This field is reserved
for future use.
Notes:
1) Values for Conversion Rate Type Parameter is relevant only when Ledger currency is other than
ILS. If Ledger currency is ILS, then values from functional currency are selected into CLE tables.
2) Constant' and 'Future Use' parameters do not have any relevance for now. So, any text entered for
these parameter values are displayed in output file.
Processing
The request set can be submitted from SRS (Standard Request Submission) window.
This request set can be submitted for any date range for a particular year. This request
set is run on yearly basis as most of the reporting is done to the Israeli Tax Authority on
yearly basis. :
Localization criteria consist of the inclusions mentioned under "Table for Localization
Criteria. "
The parameters given in the Request set are cascaded to the individual requests. The
Program selects the data based on the Primary ledger, Legal Entity and date range
mentioned in the parameters. Since each individual request is for each document type,
it will
populate the data into the respective CLE table. Each concurrent program log file
displays the entire count of transactions to be considered (without localization criteria)
and the count of transactions, which qualifies the localization criteria.
Request Set Header
Field Value
Set CLE: Israeli Localization Populating Open Format Tables

(Request Set)
Application EMEA Add-on Localizations
Description CLE: Israeli Localization Populating Open Format Tables
Links Stages
Display Name Success Warning Error
Sequence
10 CLE: IL OF CLE: IL OF Stop the request Stop the request

Generate Header Collect Acct set set
Record (A100) Index and
Account Journals
20 CLE: IL OF CLE: IL OF CLE: IL OF CLE: IL OF

Collect Acct Collect Collect Collect
Index and Document Document Document
Account Journals Header and Header and Header and
Document Lines Document Lines Document

Collect Collect Collect Collect
Document Inventory Inventory Inventory
Header and Balances (M100) Balances (M100) Balances (M100)
Document Lines

Collect Generate Generate Generate
Inventory Wrapper Record Wrapper Record Wrapper
Balances (M100) (Z900) (Z900) Record
50 CLE: IL OF CLE: Israeli CLE: Israeli CLE: Israeli

Generate Localization Localization Localization
Wrapper Record Open Format Open Format Open Format
(Z900) Generate INI Generate INI Generate INI
Data Data Data
60 CLE: Israeli CLE: INI Counter CLE: INI Counter CLE: INI Counter
Localization Report Report Report
Open Format
Generate INI
Data
70 CLE: INI CLE: C100 CLE: C100 CLE: C100

Counter Report Documents Documents Documents
Summary Summary Summary
Report Report Report
80 CLE: C100
Documents
Summary
Report
Each concurrent program whether it completes in normal/warning/error will trigger the

next concurrent program. The user has the flexibility of running the warning/errored
concurrent program again for the given parameters in A100 Concurrent program.
Snapshot of the Output
Based on the these data the last two reports summarize the information of the relative request set.
The layout follows in the following snapshots:
Exception
The requests are submitted in the sequence assigned at the header level of the request
set. They are submitted sequentially and in case any request completes in warning,
the data is rolled back for that document type. The subsequent concurrent requests
continue whether the previous concurrent requests completes in normal/warning.
Log file
The log file is printed with the following details.
• Timestamp of start & end report
4
Chapter 4 Child Requests
CLE: IL OF Generate Header Record (A100) Program
Objective
This Program populates the CLE table with the header record of the
BKMVDATA.TXT.
Parameters
The parameters are shared automatically from the request set, while request set is
submitted. If the Program is submitted Individually, parameter are the following:
Parameter Required (Y/N) Displayed (Y/N) Default Value LOV
Ledger Yes Yes Null List of Values

will list
Primary Ledger
attached in the
Data Access Set.
Legal Entity Yes Yes Null List of Values

will list all the
Legal Entities
available under
the Ledger
selected above.
Child Requests 4-1

Parameter Required (Y/N) Displayed (Y/N) Default Value LOV
Year Yes Yes Null Year from the

associated GL
Calendar related
to the selected
Ledger
Start Date Yes Yes Null Calendar is

displayed
End date Yes Yes Null Calendar is

displayed
Constant No Yes Free text

numeric field of
length 50
characters
Future Use No Yes Null Free text

alphanumeric
field of length 50
characters. This
field is reserved
for future use.
Processing
This program creates a unique sequence which helps in the identification for the
information related to a particular data file. This sequence is increased every time
the request set is submitted.
After successful execution of this concurrent program, CLE_IL_OF_A100 table
are populated with the parameter information for which the request set has been
submitted. These parameter information will later be accessed by the other child
concurrent programs following this concurrent program.
Output
Only the Ledger, Legal Entity, Year, Start and End date, Future Use parameters and also
BSV enabled for this reporting are displayed as part of output.
Log file
The log file is printed with the following details:
• Exceptions handled
CLE: IL OF Collect Acct Index and Account Journals
Objective
The concurrent request populates table with Accounting Index (B110) and Account
Journals (B100) Information. During the time of flat file generation, accounting
Index and Account Journal data are retrieved from the CLE_IL_OF_B110 and
CLE_IL_OF_B100 tables.
Parameters
There is no parameter for this concurrent program. Selection criteria information like
Ledger, Legal Entity, Year, Start Date, End Date, Constant and Future Use is
defaulted from the CLE_IL_OF_A100 table.
Processing
This program is used to populate the Journal header and journal line information into
Child Requests 4-3

the respective tables.
This program does not have any parameters and derives the required selection
criteria based on the parameter information stored in CLE_IL_OF_A100 Table.
However, In case this program completes in warning, the data is rolled back. In
such scenario, this program can be run individually to populate the respective tables
after making necessary corrections as per the message in the log file.
Every time this request set or individual program is submitted, the data in this table
is cleared first before inserting any new records into the table. If this program is ran
separately, the user should run the program CLE: IL OF Generate Wrapper Record
(Z900) Program as well to update the count of the transaction information.
Output
Transactions which failed to populate the balance sheet code due to non availability
of tax authority Document type code setup are displayed with the details.
Exception Handling
Where the data from the Core Module tables cannot be loaded to the CLE tables,
the program completes in warning providing the reason for error in the log file.
Log file
The log file is printed with the following details.
• Exceptions handled - for example, missing currency LDFF
• The Total count of transactions (without localization criteria) and the count of
transactions which qualifies the localization criteria. This data is displayed at
Legal Entity Level
CLE: IL OF Collect Documents Header and Document Lines Program
Objective
The concurrent request is to populate table with Collect Documents Header (C100),
Collect Document Lines (D110) and Remittance lines date (D120). During the time
of flat file generation, this information is retrieved from the CLE tables
Parameters
Ledger, Legal Entity, Year, Start Date, End Date, Constant and Future Use are defaulted
from the CLE_IL_OF_A100 table.
Processing
This program is used for the purpose to populate data from various sources. Data like
sales order, Purchase orders, inventory related information are populated into the CLE
tables. The C100 table contains the header information related to the above types of
transaction. The D110 contains line level information for the above transaction types.
The D120 contains line level information for cash receipts. For details of table you can
refer to the Technical Reference Manual.
after making necessary corrections as per the message in the logfile.
Every time this request set or individual program is submitted, the data in this table is
cleared first before inserting any new records into the table. If this program is ran
(Z900) Program as well to update the count of the transaction information and should
also run the CLE: Israeli Localization Open Format Generate INI Data.
Output
All the header, line information with regard to different document types are
populated in the following tables.
CLE table Type of Information populated in
Sales Order Header C100-100 All the sales order header information like
party_name, Delivery_details_id, city,
Postal_code, Address, tax registration_id,
Doctype (which is sales order),
ordered_date, ordered-value
Sales Order Shipment Header C100-200 All the sales order shipment details like Total
shipment value details, transactional value
and Delivery details with other details like tax
registration
Sales Order Return Header C100-210 All the sales order return header details
get stored in this table from Core Module table
Sales Invoice Header C100-300,305,330 All the sales invoice header details get stored in
this table from Core Module tables
Child Requests 4-5

Sales Receipts Header C100-400, 405 All the sales receipts details get stored in this
table from Core Module tables
Sales Receipts Remittance Header C100-420 All the sales receipts remittance header details get
stored in this table from Core Module tables
Purchase Order Header C100-500 All the Purchase order header details get stored in
PO Receipt Header C100-600 All the Purchase receipt header details get stored in
Purchase Invoice Header C100-700 All the Purchase invoice header details get stored in
Purchase Invoice Credit Header C100-710 All the credit Invoice header details get stored in
Delivery to Inventory Header C100-810 All the material delivery to Inventory get stored in
Issue from Inventory Header C100-820 All the material issue header details get stored in
Sub-Inventory Transfer Header C100-830 All the material transfer header details get stored in
Inventory count adjustments Header C100-840 All the material adjustment header details get
stored in this table from Core Module tables
WIP Completion Header C100-900 All the assembly completion details get stored
in this table from Core Module tables
Sales Order Lines D110-100 All the sales order Lines information get stored
Sales Order Shipment Lines D110-200 All the sales order shipment Lines information
get stored in this table from Core Module tables
All the sales Lines return header details get

Sales Order Return Lines D110-210 stored in this table from Core Module table
Sales Invoice Lines D110-300,305,330 All the sales invoice Lines details get stored
Purchase Order Header D110-500 All the Purchase order Lines details get stored
PO Receipt Lines D110-600 All the Purchase receipt lines details get
stored in this table from Core Module
tables
Purchase Invoice lines D110-700 All the Purchase lines details get stored in this
table from Core Module tables
Purchase Invoice Credit Header D110-710 All the credit Invoice lines details get stored in
Delivery to Inventory lines D110-810 All the material delivery to Inventory get
stored in this table from Core Module
tables
All the material issue lines details get stored in

Issue from Inventory lines D110-820
Sub-Inventory Transfer Lines D110-830 All the material transfer lines details get stored
Inventory count adjustments Lines D110-840 All the material adjustment lines details
get stored in this table from Core Module tables
WIP Completion Lines D110-900 All the assembly completion details get stored
Sales Receipts Lines D120-400, 405 All the sales receipt lines details get stored in
Sales Receipts Remittance Lines D120-420 All the sales receipts remittance header details
get stored in this table from Core Module
Exception Handling
In case the data from the Core Module tables cannot be loaded to the CLE
tables, the program completes in warning providing the reason for error in the
log file.
Log file
The log file is printed with the following details
Child Requests 4-7

• Exceptions handled – for example, missing Currency LDFF
• The total count of transactions (without localization criteria) and the count of
Legal Entity Level
CLE: IL OF Collect Inventory Balances (M100) Program
Objective
The concurrent program populates Inventory items balance details into
CLE_IL_OF_M100 table.
Parameters
from the CLE_IL_OF_A100 table.
Processing
This program is to populate the inventory related information into the respective tables.
is cleared first before inserting any new records into the table. If this program is ran
(Z900) Program as well to update the count of the transaction information.
Output
There is no output available for this concurrent program.
Exception Handling
In case where the data from the Core Module tables cannot be loaded to the CLE tables,
the program completes in warning providing the reason for error in the log file.
Log file
Legal Entity Level
CLE: IL OF Generate Wrapper Record (Z900) Program
Objective
The objective of this concurrent program to populate last record into CLE table.
During the actual file generation the last file record is retrieved from the table.
Parameters
Ledger, Legal Entity, Year, Start Date, End Date, Constant and Future Use is
defaulted from the CLE_IL_OF_A100 table.
Processing
This program is used for generating the footer record for the BKMVDATA.TXT. It
provides the count of the total number of records selected in the file. There are no
specific validations. This information are stored in CLE_IL_OF_Z900.
is cleared first before inserting any new records into the table.
Output
Exception Handling
None
Child Requests 4-9

Log file
transactions, which qualifies the localization criteria. This data is displayed at Legal
Entity Level
CLE: Israeli Localization Open Format Generate INI Data
Objective
This program is used for populating the CLE_IL_OF_INI_COUNTER and
CLE_IL_OF_INI which stores the count of qualified transaction information for
each record type.
Parameters
The following are the parameters to be entered when submitting the request set.
Output
Log file
CLE: INI Counter Report
Objective
The concurrent program creates a presentable output of the counts of qualified
transaction information for each record type as this is depicted in the INI table
from the previous request.
Parameters
from the CLE_IL_OF_A100 table as these are defined when the request set (CLE: Israeli
Localization Populating Open Format Tables(1)) is launched.
Processing
This program is run in order to present the counts of the qualified transaction
information that has populated the CLE_IL_OF_INI_COUNTER table.
If this request is submitted individually, the whole set of the requests of the CLE:
Israeli Localization Open Format File generation that preceded this request in the set,
need to have been completed first in order for the data to have populated the relative
tables. This is why it is highly suggested to use the proposed Request set.
Output
As it can be seen from the snapshot that is shown in Chapter 3 above, the information depicted
in the header of this report includes the Tax id information of the User Company (VAT
Registration number, Business name) , the date of the report, the time range it covers and also
the exact path where this date is stored in the database.
In the detail part of the report, it depicts the Total Record Count per Record Code
(A100, B100,C100, etc).
Finally, there is a placement on the report output for a Registration Certificate Number by the
auditors.
Child Requests 4-11

Exception Handling
the program completes with zeros in the relative fields for the respective categories.
Log file
CLE: C100 Documents Summary Report
Objective
The concurrent program creates a presentable output that summarizes the
Amounts and counts of qualified transaction information for each record type
as these have been collected from the previous requests on the request set.
Parameters
from the CLE_IL_OF_A100 table as these are defined when the request set (CLE: Israeli
Localization Populating Open Format Tables(1)) is launched.
Processing
This program is run in order to depict in a summarized and presentable way (pdf) the
amounts in ILS and counts of all the qualified transaction that have populated the
related information into the respective tables per transaction document type.
Just like the INI Counter Report, if this request is submitted individually, the whole
set of the requests of the CLE: Israeli Localization Open Format File generation that
preceded this request in the set, need to have been completed first in order for the
data to have populated the relative tables. This is why it is highly suggested to use
the proposed Request set.
Output
As it can be seen from the snapshot that is shown in Chapter 3 above, the information
depicted in the header of this report is only the title and the date of the report.
In the detail part of the report, it depicts the Following Columns:
Sum Amounts (in ILS) The Sum of the amounts of all the transactions in the
particular Document category, including Taxes. The
amount is depicted in ILS only and all foreign
currency transactions are shown translated to ILS
currency.
Total Count The count of all the relative transactions per document
category.
Document Description The analysis of these document categories is fixed and

always presented in the report output. If no
transaction has taken place for a particular category,
the corresponding field will yield the zero value (0).
Document Number The analysis on the values of this column is also fixed
and always presented in the report output. It identifies
the exact type of transactions that will be included in
the Sum amounts and Counter.
Exception Handling
the program completes with zeros in the relative fields for Sum Amount and count for
the respective document categories.
Log file
Legal Entity Level
Child Requests 13
CLE: Israeli Localization Open Format File Generation BKMVDATA
E-Text Program and CLE: Israeli Localization Open Format File Generation
INI E-Text Program
Objective
This is a concurrent program, which can be run from SRS ( Core Module
Request Submission). Once the request set CLE: Israeli Localization
Populating Open Format Tables has populated the data into CLE tables,
the user needs to run this program. This CLE: Israeli Localization Open
Format File Generation BKMVDATA E-Text program and CLE: Israeli
Localization Open Format File Generation INI E-Text Program has an
inbuilt validation, which validates whether all the concurrent programs
submitted earlier have completed in normal or not. If they have ended
in warning or error the Open Format File Generation BKMVDATA
E-Text program will not generate any output file.
This request creates output file and this file can be opened
from View Output of SRS window in Firefox browser and
should be saved using Hebrew (IBM-862) encoding and
also this file is placed at in output directory as per the
setup of the instance.
Parameters
There is a non mandatory parameter namely ‘Report group’ for
these concurrent programs. Selection criteria information like
Ledger, Legal Entity, Year, Start Date, End Date, Constant and
Future Use are defaulted from the CLE_IL_OF_A100 table. The file
creation program collects the information available in the CLE
tables.
14 Oracle® EMEA Add-on Localizations User Guide for Israel Open Format Solution
This new ‘Report group’ parameter is used to filter data based on the
group it belongs to .The related records are grouped together. This
grouping is added to avoid the program from ending into warning as
the output file size is huge.
At any point of time, information related to Primary ledger and Legal
Entity will be available. This file creation program will directly pick the
information available in the CLE tables.
The possible values for this ‘Report group’ parameter is mentioned
below and is from Lookup namely ‘CLE_F262_REPORTING_GROUPS’.
1. Sales Order Header C100-100 -- Sales Order Lines D110-100.

2. Sales Order Shipment Header C100-200----Sales Order Shipment
Lines D110-200
3.Sales Order Return Header C100-210--Sales Order Return Lines D110-
210.
4. Sales Invoice Header C100-300,305,330--Sales Invoice Lines D110-
300,305,330.
5. Sales Receipts Header C100-400, 405--Sales Receipts Lines D120-400,
405.
6. Sales Receipts Remittance Header C100-420--Sales Receipts
Remittance Lines D120-420.
7. Purchase Order Header C100-500---Purchase Order Lines D110-500.
8. PO Receipt Header C100-600--PO Receipt Lines D110-600.
9. Purchase Invoice Header C100-700---Purchase Invoice lines D110-700.
10. Purchase Invoice Credit Header C100-710--Purchase Invoice Credit
Lines D110-710.
11. Delivery to Inventory Header C100-810--Delivery to Inventory lines
D110-810.
12. Issue from Inventory Header C100-820--Issue from Inventory lines
D110-820.
13. Sub-Inventory Transfer Header C100-830--Sub-Inventory
Transfer Lines D110-830.
14.Inventory count adjustments Header C100-840-Inventory count
adjustments Lines D110-840
15.WIP Completion Header (In) C100-900--WIP Completion Lines D110-
900
16.WIP Completion Header (Out) C100-910—No lines
17.WIP Completion Return Headers C100 - 910--WIP Completion
Return Lines D110 - 910.
18. B100 journal lines (only lines without header).
When these programs are submitted individually from SRS, generates

two output files namely BKMVDATA.TXT and INI.TXT respectively.
The BKMVDATA.TXT output file shows the detailed records of the
report group for which program is run and the INI.TXT output file
shows the summary of the record count inserted in the CLE tables of the
report group for which program is run.
Child Requests 4-15

Processing
This program i s used for O p e n format output fi le
BKMVDATA.TXT and INI.TXT file. Validation of record count in
the Core Module tables and CLE tables is displayed in the log file
while output file is generated.
Output
These requests create two output files using corresponding
programs and the files should be saved with Hebrew (IBM-862)
encoding using the names BKMVDATA.TXT and INI.TXT.
The BKMVDATA.TXT output file is generated based on the setup
done in the E-Commerce Gateway for each CLE table. The records
in the data file are padded, if required as per the setup done in the
E-Commerce Gateway. The length for each information is decided
by the user through the E-Commerce Gateway setup.
The INI.TXT output file shows the summary of the record count
inserted in the CLE tables.
Exception Handling
This program has an inbuilt validation where it checks for record

count for each type of document type in the Core Module table and
in the CLE tables. Only if the counts match the output files are
generated, else the program completes in error providing the reason
for error in the log file.
Log file

• The total count of transactions (without localization criteria) and

the count of transactions which qualifies the localization criteria. This
data is displayed at Legal Entity Level.
5
Chapter 5 Position details of BKMVDATA a n d INI text files
Introduction
Once the BKMVDATA.txt file is generated, the user can read/interpret the output file
with the below table. The table denotes the start, end position of each value type for
each tax authority document code. The table also provides the total length in terms
of each tax authority document code.
Tax Authority Document Code Start End Length Total

Position Position Length
A100 95
Record Code 0 3 4
Future Use 4 12 9
Tax identifier 13 21 9
Reference Key 22 36 15
Constant 37 44 8
Future Use 45 94 50
Position details of BKMVDATA and INI text files 5-1

B100 317
Record Code 0 3 4
Future Use 4 12 9
Tax Identifier 13 21 9
Transaction Number 22 31 10
Transaction Line Number 32 36 5
Batch 37 44 8
Transaction Type 45 59 15
Audit field1 60 79 20
Audit type1 80 82 3
Audit field2 83 102 20
Audit type2 103 105 3
Details 106 155 50
Date 156 163 8
Effective Date 164 171 8
Account Key 172 186 15
Countra Account 187 201 15
Sign 202 202 1
Transaction currency 203 205 3
Amount without VAT 206 220 15
5-2 Oracle CLE User guide EMEA Consulting Localizations User Guide for Localization-Israel Open Format
Solution
Non ILS currency 2.221 235 15
Qty 236 247 12
Adjustment reference1 248 257 10
Adjustment reference2 258 267 10
Branch identify – Required only if 1034 = 1 268 274 7
Update date/creation date 275 282 8
User name 283 291 9
Reference Key 292 316 25
Future Use 321 344 25
B110 376
Record Code 0 3 4
Future Use 4 12 9
Tax Identifier 13 21 9
Account Key 22 36 15
Account name 37 86 50
Balance sheet code 87 101 15
Balance sheet description 102 131 30
Customer/Vendor street 132 181 50
Customer/Vendor home number 132 191 10

Customer/Vendor city 192 221 30
Customer/Vendor zip code 222 229 8
Customer/Vendor state 230 259 30
State code 260 261 2
Summary account 262 276 15
Beginning balance 277 291 15
Total Dr without beginning balance 292 306 15
Total Cr without beginning balance 307 321 15
Accounting classification 322 325 4
Customer/Supplier tax identifier 326 334 9
Open balance in foreign currency 342 356 15
Currency code from the VS 357 359 3
Future use 360 375 16
C100 444
Record Code 1 4 4
Future Use 5 13 9
Company Tax Identifier 14 22 9
Document Type 23 25 3
Solution
Document Number 26 45 20
Document issue Date 46 53 8
Document issue time 54 57 4
Customer/Vendor name 58 107 50
Required only for documents from 100 to 710
Customer/Vendor street 108 157 50
Customer/Vendor house number 158 167 10
Customer/Vendor city 168 197 30
Customer/Vendor zip code 198 205 8
Customer/Vendor state 206 235 30
Customer/Vendor state code 236 237 2
Customer/Vendor phone number 238 252 15
Customer/Vendor tax identifier 253 261 9
Effective date 262 269 8
Non ILS currency amount 270 284 15
Non ILS currency code 285 287 3
Document amount (in ILS) without discount 288 302 15
Document discount amount in ILS 303 317 15
Document amount with discount without 318 332 15

VAT in ILS
VAT amount in ILS 333 347 15

Document amount in ILS including VAT . In 348 362 15

receipt without WHT.
Witholding tax amount in ILS 363 374 12
External supplier/customer number 375 389 15
Required only for documents from 100 to 710
Adjustment field 390 399 10
Cancelled Document If the document is 400 400 1

cancelled than the default is 1
Document date 401 408 8
User name 416 424 9
Header_id 425 431 7
D110 339
Record Code 0 3 4
Future use 4 12 9
Company Tax Identifier 13 21 9
Document Type 22 24 3
Document Number 25 44 20
Document Line number 45 48 4
Solution
Document Classification 49 51 3
Document Classification Number 52 71 20
Deal Type 72 72 1
Internal Item 73 92 20
Line Description 93 122 30
Vendor Name 123 172 50
Manufacturer serial number 173 202 30
Unit of measure 203 222 20
Qty 223 239 17
Unit price 240 254 15
Line discount 255 269 15
Total Line 270 284 15
Line VAT Rate 285 288 4
Document date Format YYYYMMDD 296 303 8
Header_ID 304 310 7
D120 222
Record Code 0 3 4

Future use 4 12 9
Company tax identifier 13 21
Document classification 22 24 3
Document number 25 44 20
Receipt line 45 48 4
Receipt method 49 49 1
Cheque Bank number 50 59 10
Cheque branch number 60 69 10
Cheque account number 70 84 15
Cheque number 85 94 10
Cheque maturity date 95 102 8
Line Amount 103 117 15
Clearing house 118 118 1
Credit card name 119 138 20
Credit deal type 139 139 1
Document date Format YYYYMMDD 147 154 8
Header_id 155 161 7
Solution
M100 298
Record code 0 3 4
Record number 4 12 9
Company tax identifier 13 21 9
Universal item 22 41 20
Vendor item 42 61 20
Internal item 62 81 20
Item description 82 131 50
Category code 132 141 10
Category Description 142 171 30
Unit of measure description 172 191 20
Item Beginning balance 192 203 12
Item receipts for period range 204 215 12
Item issues for period range 216 227 12
Item cost for end of period out of bondage 228 237 10

inventory*
Item cost for end of period in bondage 238 247 10

inventory*

Z900 110

Record code 0 3 4
Future use 4 12 9
Reference key 22 36 15
Constant 37 44 8
Total qty of records in file 45 59 15
5-10 Oracle CLE User guide EMEA Consulting Localizations User Guide for Localization-Israel Open
Format
Solution
Once the INI.txt file is generated, the user can read/interpret the output file with the
below table. The table (2) denotes the start, end position of each value type for each
tax authority document code. The table (1) provides the total length in terms of each
tax authority document code
INI.TXT Max length
A000 466
B100 19
B110 19
C100 19
D110 19
D120 19
M100 19
Total 580
Length, Start Position and End Position in INI TXT

Table –(2)
INI Length Start Position End Position
Record code 4 0 3
Future use 5 4 8
Total qty of records in 15 9 23

BKMVDATA file
Reference key 15 33 47
Constant 8 48 55
Software registration 8 56 63
number
Software name 20 64 83
Software version 20 84 103
Tax identifier of 9 104 112

software
manufacturer
Software 20 113 132

manufacturer name
Software type 1 133 133
Backup path 50 134 183
Software accounting 1 184 184

type
Accounting type 1 185 185
Company registration 9 186 194

number
Format
Solution
INI Length Start Position End Position
Company tax file 9 195 203
Company name 50 214 263
Company street 50 264 313
Company location 10 314 323

number
Company city 30 324 353
Company zip code 8 354 361
Tax year 4 362 365
Date range (start) 8 366 373
Date range (end) 8 374 381
Process start date 8 382 389
Process start time 4 390 393
Language code 1 394 394
Character set 1 395 395
Software zip code 20 396 415
Currency code 3 416 418
Branch Information 1 419 419
Future Use 46 420 465

6
Chapter 6 General Setup Steps
Overview
In order to implement this object, the following setup steps are required
Specific Legal Entity Setup:
In order to provide flat file per company, Legal Entity is defined and maintained
through standard organization including address, tax registration number. Balancing
Segments that are eligible for reporting are enabled.
The following information related to the Legal Entity defaults from the Legal Entity
setup. However, certain information which cannot be captured from the standard
fields in Legal Entity setup are captured in the contact information page of the Legal
Entity.
Location information defaults from the location attached to the Legal Entity as
the registered address for the establishment where identifying flag is enabled.
Tax registration number is derived from the contact information where the last name is
with TRN and its corresponding value from the first name of the contact of the Legal
Entity,
Information Source
Legal Entity Location Address Location attached to the Legal Entity as the
registered address for the establishment with
identifying flag
General Setup Steps 6-1

Information Source
Tax Registration Number First Name of the contact in Contact

information page of the Legal Entity where
Last name is TRN.
At any point of time, the file creation can happen only for particular year. It can also
be done periodically depending upon user decision. The Year parameter ensures that
the entered period belongs to one single calendar year only. The year information will
default from the associated GL calendar.
E-Commerce Gateway
Below E-Commerce Gateway setup would be available for review after running CLE:
Israeli Localization Populating Open Format Tables (Request Set). Please note that this
setup need not be created manually
E-Commerce Gateway is used for deriving the file structure with respect to field, length
of the field, type of padding, characters used for padding. This setup can be modified
by the user at any point of time depending upon the Israeli Tax Authority requirements.
The solution is flexible enough to identify any changes in the E-Commerce Gateway
setup and generates the file outputs as per the modified Setup.
Solution
File Generation information is managed using EDI conversion table:
Responsibility: E-Commerce Gateway Setup->Code Conversion->Define Code
Conversion Category
IL Open Format Documents – Lists all the document types for which data need to be
extracted to BKMVDATA.TXT file. For each document, document code, description and
table names are maintained.
CLE_IL_OF_XXXX – Maintain file structure mapping for each table
in CLE_IL_OF_C100, CLE_IL_OF_D110.
Open Format Documents List
Setup->Code Conversion->Define Code Conversion Values

• Description – Document description
• Key 1 – Name of the table storing the document header information.

• Key 2 – Name of the table storing the document lines information.
• Internal Value – Document code in the Tax Authority design document
• External 1 – End position
File Mapping
Each table is mapped to file positions. For example , the following illustrates
the mapping of table IL_OF_C100 to file positions:
• Category – Table Name
• Description – Column name in the table
• Internal Value – Start position in the file record
• External 1 – End position in the file record
• External 2 – File segment length
• External 3 – Type of padding if any
• External 4 – Padding Character
All tables are mapped to file structure using this method.

INI.TXT:
This file provides data pertaining to –
• General Information of the tax company
• Total number of records of BKMVDATA.TXT
Solution
• Process start date and end date and time (for the entire process generating both
the files)
• Total number of records – per document type in BKMVDATA.TXT file.
BKMVDATA.TXT:
• This file contains 4 types of records for each type of Tax Authority document (like Purchase
Invoice, Sales Order, Accounting Journal).
• Document header information ( total invoice amount, invoice number)
• Document details information (Invoice line details)
• Closing record.
The diagram below describes the files records and the tables, which populate the data of
these files records.
The Israeli Tax Authority requirement is to receive detailed transactions flat file per Legal
Entity
.
Table for Localization Criteria
The following table would list the types of documents that are selected in the
request (inclusions) and the ones that are not selected (exclusions).
Application Inclusions Exclusions

Payables • Standard Invoice • Payments
• Mixed Invoice • Withholding Invoices
• Credit Memo • Retainage Invoices
• Debit memo • Transportation Invoices
• Cancelled Invoices • Accrual Write offs
• Pre Payments • Supplier site information
• Expense Reports
It is necessary the invoices are

validated.
• • Incomplete Transactions
Receivables Transaction Types where
LDFF is enabled
•
• Receipt classes where
Bills Receivables
LDFF is enabled
• Guarantees
• Receipt reversals •
Chargeback
• Miscellaneous Receipts
• Customer site
information
Solution
• Manual Journals · Budget journals

General Ledger
• Revaluation Journals
• Recurring Journals
• Mass Allocation Journals
• Closing Journals
• Adjustment entries
Reversed Journals
All entries which are in

posted status are considered.
Order Management All types of sales order where

• All types of sales order order_category_code
where ='MIXED'
order_category_code='O
RDER' or 'RETURN'
• Order Shipment detail

where delivery status is
closed
• Approved Standard
Purchasing
• Blanket Purchase Orders
• Planned Purchase Orders
• Only receipts for

approved Purchase
Orders are considered
• Cancelled Purchase
Orders

Inventory • In transit receipt • Move Order receipt
• Receipt into stores • Move Order Issue
• Issue from stores
• In transit shipment
• Sub inventory transfer
• Direct organization
transfer
• Assembly completion
WIP
• WIP Completion
• WIP Completion Return
Attach Form Personalization functions to the menu

1) Switch to 'System Administrator' Responsibility.
2) Navigate to 'Applications -> Functions' and query for the Function CLE_F220_DFFX. It
should exist else please contact system administrator or log a service request.
Solution
Figure: LDFF Function exists
3) Query for the following menu and add the CLE Localization DFF Function to
the menu. (If the CLE Localization DFF function does not already exist)
Menu Name AR_NAVIGATE_GUI
User Menu Name AR_NAVIGATE_GUI
Function Name CLE Localization DFF

Format
Solution
7
Chapter 7 Technical Prerequisites
Introduction
There are some additional setup steps, which need to be performed for this solution
to work.
Localization Descriptive Flex Field

Balancing Segments – Reporting Assignment
This LDFF is defined for identifying the balancing segments value from the selected
which are eligible for Israeli Tax Authority reporting. This is done in the BSV Assignment
OA Page for the particular setup in the Accounting Setup Manager. Only those BSVs for
which Reporting is set to 'Yes' are considered for reporting and populate data into the CLE
tables. Information relating to other BSVs are skipped.
Field Name Field Value
Application EMEA Add-on Localization Flex
field Title Balancing Segment Flex fields Context
reference field None
Displayed Yes
Required Yes
Technical Prerequisites 7-1

Code Code: IL.IL_OF_BSV_INFO
Name: CLE: IL Additional BSV Information
Description: CLE: IL Additional BSV

Information
Name Window Column Value Set Required Display Purpose

Prompt Size
Reportable Reportable Attribute1 CLE_YES_ Yes 5 It is used

BSV BSV NO for
identifying
the BSVs
which are
eligible for
tax
reporting.
Extending OA Page Controller
1. Switch Responsibility to General Ledger >> Accounting Setup manager
Solution
2. Query for the Primary Ledger and click in Update Accounting Options icon

3. Click on the 'Balancing Segment Value Assignments' update icon in the list
4. Click on 'personalize page' link in the top right
5. Click on Personalize icon corresponding to 'Page layout: Accounting Setup Manager' from the Personalization
Structure.
6. Set the Controller Class at the site level to 'oracle.apps.cle.f262.webui.CLEConfigBSVSummaryPageCO'
Solution
Apply the changes.
7. Click on 'Return to the Application' link at bottom left. A link is shown for each of the BSV Description.
Click on the link to enter the LDFF information

LDFF Setups:
The patch installs the following Localization Descriptive Flexfields:
LDFF: AR Invoice Transaction Type

A flex field in the Transaction Type Setup form is used for capturing the
Transaction Type assignment to the Tax Authority document types.
Application EMEA Add-on Localizations Flex
field Title Transaction Type Information Context
reference field
Displayed Yes Required
No
Code Context
Code:IL.IL_OF_TAX_DOCUMENT_TYPE
Name: IL Localization Document Types
Description: IL Israeli Localization Tax

Document Type Assignment
Segment Values
Name Window Column Value Required Displaye Display Purpose

Prompt Set y
d/Securit Size
enabled
CLE_IL_ CLE: Attribute1 CLE_F262_ No yes 40 For Identifying

OF_TAX_DO Localization IL_OF_AR_
IL_ The transaction
C_TYPE Document TRANS_TY Types Eligible for
Type PES Reporting to Israeli
Tax Authority
Solution
LDFF: AR Receipt type
A Flex field in the AR Receipt Classes Setup form will is used for capturing the Receipt
Type assignment to the Israeli Tax Authority document types.
All "Tax" related Receipt types must be assigned a value.
Flex field Title Receipt Class Information
Context reference field
Displayed Yes
Required No
Code Context Code:IL.IL_OF_TAX_RECEIPT_TYPE
Name: IL Localization Receipt Types
Description: IL Israeli Localization Tax Receipt

Type Assignment
Segment Values
Name Window Column Value Required Displaye Display Purpose

Prompt Set d/Securit Size
y
enabled
CLE_IL_ IL ATTRIBU IL_AR_R No Yes 40 This is

OF_TAX_ Localizati TE1 ECEIPT_ used for
RECEIPT on TYPES the
_TYPE Receipt identifyin
Type g the
receipt
types
eligible
for
reporting
.
LDFF: AR Receipts – CLE: Additional Info On Cash Receipts

This is a localization flexfield on the Receipts Entry / Update form where the user needs
to identify additional information regarding the type of this Receipt and then depending
on the type, additional information for specific receipt types. The name of the LDFF may
be a little misleading as it refers to “Cash Receipts” when in fact it pertains to information
for any type of receipt.
The user will have to select from a list of 9 values the Type of the specific Receipt. The
nine values are identified in the segment table below
If the selection is 1, 4, 5, 6, 7, 8, 9 then no other segment is becoming available as tis

information is adequate for the SHAAM needs. If the selection is 2. Check, then the user
needs to identify additional information for the Check in question. The exact fields and
the required data is included in the segment table below. Likewise, if the selection is
3.Credit Card, then the user needs to identify additional information regarding the Credit
card used.
7-7-9 Oracle CLE User guide EMEA Consulting Localizations User Guide for Localization-Israel Open
Format
Solution
Flex field Title: CLE: Additional info on Cash Receipts
Context reference field
Displayed Yes
Required No
Code Context Code: IL.IL_REC_ADD_INFO
Name: CLE: Receipt Additional
Information
Description: CLE: Receipt Type

Dependent Additional Information
Segment values
Solution
Seque D120 Name Window Column Value Set Req Disp Disp Purpose
nce Colu Prompt uire laye lay
mn # d d/Se Size
curi
ty
ena
bled
1 1306 CLE_IL_RECEIP IL Receipt ATTRIBU CLE_OPN_FRM Yes Yes 2 To identify the

T_TYPE Type TE1 T_PMT_TYPE Receipt type and
(Drop-Down List) thus define which
other segments will
be required to be
filled by the user.
The values in the list
are:
1-Cash
2-Check
3-Credit Card
4-Bank Transfer
5-Vouchers
6-Coupon swap
7-Bill
8-Direct Debit
9-Other
If values 2 or 3 are
selected then the
following segments
are available
respectively for each
value. If values
1,4,5,6,7,8,9 are
selected then no
other segment
becomes available
2 1315 CLE_IL_CREDIT IL Credit Deal ATTRIBU CLE_CREDIT_D No Yes 2 Open if Value of
_DEAL_TYPE Type TE2 EAL_TYPE_LK Segment 1 = 3
UP To identify the
credit value type
from the relative
value-set. The
values in the list are:
1.regular
2.payments
3. Credit
4. Future debit
5. other .
This filed is numeric

and you choose the
value 1 or 2 etc.
4 1314 CLE_IL_CREDIT IL Credit Card ATTRIBU CLE_CREDIT_C No Yes 15 Open if Value of
_CARD_NAME Name TE3 ARD_NAME Segment 1 = 3
To capture
information on the
Credit Card Name
Seque D120 Name Window Column Value Set Req Disp Disp Purpose
nce Colu Prompt uire laye lay
mn # d d/Se Size
curi
ty
ena
bled
3 1313 CLE_IL_CREDI IL Credit ATTRIBU CLE_CREDIT_H No Yes 2 Open if Value of

Clearing TE6 OUSE_LKUP Segment 1 = 3
T_CLEAR_H To identify the
House
credit clearing house
from the relative
value-set.
The values in the list
are:
1.Isracard
2.Visa
3. Diners
4. Amex
6.Leumi Card
This filed is numeric

and you choose the
value 1 or 2 etc.
6 1308 CLE_IL_CHECK IL Check ATTRIBU CLE_CHECK_B No Yes 10 Open if Value of
_BANK_BRAN_ bank branch TE7 RANCH_NUM Segment 1 = 2
NUM number To capture bank
branch number
information
7 1309 CLE_IL_CHECK IL Check ATTRIBU CLE_CHECK_A No Yes 15 Open if Value of
_ACCOUNT_NU account TE8 CCT_NUM Segment 1 = 2
M number To capture the bank
account information
5 1307 CLE_IL_CHECK ΙL Check ATTRIBU CLE_CHECK_B No Yes 10 Open if Value of
_BANK_NUM Bank Number TE9 ANK_NUMBER Segment 1 = 2
To capture bank
information of the
check
8 1310 CLE_IL_DOC_N IL Check ATTRIBU CLE_CHECK_N No Yes 10 Open if Value of
UMBER Number TE10 UMBER Segment 1 = 2
To capture the
Check number
Above, there is an example of the initial screen where the user will have to make the Receipt Type selection.
Below, there is an example of a selection of the values where no other action is necessary and one example
each of the additional information needed for Credit card and Check respectively.
Please notice that this new LDFF is actually replacing three previous LDFFs that were used in the Receipts
form for Document type, Credit card info and Check info, whose context codes need to be disabled (
IL.IL_OF_DOC_TYPE, IL.CLE_IL_OF_CHECK_INFO, IL.CREDIT_CARD_INFO).
Solution
Profile Options
Set Profile Option 'CLE: IL of File Path' with directory path, where the files need to be generated
under UTL_FILE_DIRECTORY.
The BKMV and INI files in the directory path would be refreshed with every run of concurrent
program "CLE: Israeli Localization Open Format File Generation". So these files need to be saved on
a local directory before initiating subsequent run.
Tax Authority Document Setup
A). Forms Personalization:

The patch installs the following forms personalizations. These needs to be added to
required menu:
Custom Form
S.No Form Functions
Name
CLE:IL TA Doc CLE:IL TA Doc Types, To be attached to
1 Types General Ledger Menu.
B) The Israeli Tax Authority Document setup has to be done, so as to populate the
balance sheet code column (Journals from General Ledger) in the CLE tables. A Tax
Authority document type code has to be associated with pair of Journal Source and
Journal Category. Existing combination cannot be modified. User has to end date
existing combination and create new combination for any modifications.
The basic setup for each combination of the Journal Source and Journal Category is to be
completed before running the request set.
Solution
Chapter 8 Index
information, 7-6
Symbols DFF AR Receipts- Document Type, 7-10
General Setup Steps, 6-1
E
A Exception, 3-7
Additional Cost Allocation, 3-1
Add-on Localizations, 1-1 I
Add-on Localizations Overview, 1-1 Implementation, 2-1
Israeli Localization Populating Open Format
B Tables, 3-1
Business requirement, 2-1
L
C LDFF: AR Invoice Transaction Type , 7-3
Child Requests, 4-1 LDFF: AR Receipt type, 7-5 Localization
CLE: IL OF Collect Acct Index and Account Descriptive FlexField, 7-1 Log file, 3-7
Journals, 4-3
CLE: IL OF Collect Documents Header and
Document Lines Program, 4-4 O
CLE: IL OF Collect Inventory Balances (M100) Output, 3-7
Program, 4-8 Overview, 6-1
CLE: IL OF Generate Header Record (A100)
Program, 4-1 P
CLE: IL OF Generate Wrapper Record (Z900)
Program, 4-9 Parameters, 3-2
CLE: Israeli Localization Open Format File Position details of BKMVDATA and INI
Generation, 4-11 text files., 5-1
CLE: Israeli Localization Open Format Generate Prerequisites Assumptions, 2-
INI Data, 4-10 1 Processing, 3-3
Profile Options, 7-12
D
T
DFF: AR Receipts – Check information , 7-8
DFF: AR Receipts – Credit Card deal Tax Authority Document Setup, 7-11
Technical Prerequisites, 7-1

12.2 IL Open Format UG 26 Feb 2018

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

12.2 IL Open Format UG 26 Feb 2018

Uploaded by

Copyright:

Available Formats

Oracle® EMEA Add-on Localizations User

Guide for Israel Open Format Solution

Part No. E49988-01

U.S. GOVERNMENT RIGHTS

• Are the implementation steps correct and complete?

It includes information to help you understand the information of Israel Open

• Add-on Localization Setup

• Add-on Localization Reports

About this Localization Manual

User Guides Related to This Add-On Localization

• Oracle Payables User Guide

• Oracle Order Management User Guide

• Oracle Purchasing User Guide

• Oracle Inventory User Guide

• Oracle E-Commerce Gateway User Guide

• Key User team of Oracle Applications

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

Add-on Localizations Overview 2-1

Below setups are required for working of Open Format feature:

a)Oracle's General Ledger, Oracle Payables, Oracle Receivables,

Prerequisites & Assumptions

CLE Israel Open Format Solution 2-1

1. IL.CREDIT_CARD_INFO --- Additional information on Israel Credit Card Deal.

• Only posted journals are considered from General ledger

• Taxes entered at transaction header or lines are selected for extraction.

• Tax calculation will happen based on the definition in E-Business Tax.

• Request set can be run for Primary Ledger only.

Display Sequence Stage Program Description

10 CLE: IL OF Generate Header Populate table with

20 CLE: IL OF Collect Acct Index Populate table with

30 CLE: IL OF Collect Document Populate table with PO, SO,

40 CLE: IL OF Collect Inventory Populate table with Inventory

60 CLE: Israeli Localization Generates INI Data File.

70 CLE: INI Counter Report show INI file in specific Israeli

80 CLE: C100 Documents A new report that summarizes

Parameter Required (Y/N) Displayed (Y/N) Default Value List Of Values

Ledger Yes Yes Null This List Of Values

Start Date Yes Yes Null The format of the start

Constant No Yes Null Free text,

Future Use No Yes Null Free text,

Set CLE: Israeli Localization Populating Open Format Tables

Application EMEA Add-on Localizations

Description CLE: Israeli Localization Populating Open Format Tables

10 CLE: IL OF CLE: IL OF Stop the request Stop the request

20 CLE: IL OF CLE: IL OF CLE: IL OF CLE: IL OF

30 CLE: IL OF CLE: IL OF CLE: IL OF CLE: IL OF

40 CLE: IL OF CLE: IL OF CLE: IL OF CLE: IL OF

50 CLE: IL OF CLE: Israeli CLE: Israeli CLE: Israeli

70 CLE: INI CLE: C100 CLE: C100 CLE: C100

Each concurrent program whether it completes in normal/warning/error will trigger the

CLE: IL OF Generate Header Record (A100) Program

Parameter Required (Y/N) Displayed (Y/N) Default Value LOV

Ledger Yes Yes Null List of Values

Legal Entity Yes Yes Null List of Values

Child Requests 4-1

Year Yes Yes Null Year from the

Start Date Yes Yes Null Calendar is

End date Yes Yes Null Calendar is

Constant No Yes Free text

Future Use No Yes Null Free text

CLE: IL OF Collect Acct Index and Account Journals

Child Requests 4-3

• Exceptions handled - for example, missing currency LDFF