AIM

MD.050-070
APPLICATION EXTENSIONS FUNCTIONAL DESIGN
ORACLE EBS R12 RECEIVABLES & GEANT LEGACY INTEGRATION

Fucom (Geant)
Oracle Receivables

Author : Ravi Saini

Creation Date : January 29, 2013
Last Updated : January 15, 2014
Document Ref : Geant/AR/MD.050-070
Version : 1.3

Approvals:

Gaurav Thakur Project Head Prism

Sajid Azmi Project Manager - Fucom

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential i

Document Control

Change Record
16

Date Author Version Change Reference

29-Jan-2013 Ravi Saini V1 No Previous Documents

08-Apr-2013 Ravi Saini V1.2 Added updated mapping columns table

15-Jan-2014 Mohit Gupta V1.2 Added updated mapping columns table

Business Reviewers

Name Position/Role

Mr. Santosh Ratana Finance Manager – Bahrain

Mr. Susheer Valiya Corporate Office Finance

Mrs. Radhika Appulingum Finance Manager – Kuwait

Mr. Feroz Merchant Finance Manger – UAE

Mr. Adil Khan Project Co-ordinator

Mr. Mirzaa Payables Manager

Mr. Sajid Azmi IT Manager

Mr Aftab Hashmi Asst. Finance Manager

Distribution

Copy No. Name Location

1 Library Master Project Library – Geant

2 Library Master Project Library – Prism

Note to Holders:
If you receive an electronic copy of this document and print it out, please write your name on the equivalent of
the cover page, for document control purposes.

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential ii

If you receive a hard copy of this document, please write your name on the front cover, for document control

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential iii

Contents

Document Control...................................................................................................................ii
Distribution........................................................................................................................ii

Basic Business Need.........................................................................................................3

Major Features...................................................................................................................5

Receivables Transactions Interface (Sales Invoice)......................................................5

Other Income Integration / Mapping............................................................................6

Customer Integration.......................................................................................................7

Manual Income Entry in Oracele Receivables..............................................................7

High Level Integration Flow (To be Process).......................................................................4

Interface Technical Specification............................................................................................5
Receivables Tenant Agreement Custom Form (Technical Review)..........................6

Technical Process Flow....................................................................................................7

Interface Import Concurrent Programs................................................................................8

Master Interface Sheet.............................................................................................................9
Frequency...........................................................................................................................9

IBM Legacy Tables Provided for Integration Mapping..............................................9

Oracle/Legacy Mapping.......................................................................................................10
Open and Closed Issues........................................................................................................20
Open Issues......................................................................................................................20

Closed Issues....................................................................................................................20

Basic Business Need

Geant needs to integrate existing legacy systems IBM POS with Oracle EBS Receivables.

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential iv

Followings are the details of legacy systems that need to integrate with Oracle Receivables.

 Navision – Used for Inventory and PO/Accounting

 IBM: Point of Sales –Captures the Sales

Major Features

The following defines the integration major features:

Receivables Transactions Interface (Sales Invoice)

All the Sales invoices for the day will be taken in a batch and transfer to Oracle Receivables on a daily basis end
of the day.

This will contain under below transaction types/tender type

 Cash (Multi Currency): BHD, EUR, USD, SAR, AED, KWD, OMR, QAR, GBP
 Credit Card Sales (Multi /Vendors): Master Card, Visa, Diners, Benefit cards
 Staff Sales : Employee ID wise
 Internal Sale/LPO sales : Credit Sales for certain specific customers (Internal or External)
:
Internal – HR department purchased stationery for office use or Butchery section purchased oil from
Grocery section for marinating of meat.

External – Jasmiss (customer name) purchasing cheese on credit by lpo.

 Discount Vouchers – Are type of tenders where vouchers issued to the customers gets redeemed. (debit
Liability)
 Gift Vouchers – Are type of tender where Gift vouchers sold are redeemed. (Debit liability)
 Excess / Short – Value/balance for each cashier after closing cash counter. Excess to be trated as income,
Short to be treated as Receivable from Cashier at Employee ID level. End of month (15 th cut off) to be

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential v

 recovered from Cashier if Value above tolerance Value or to be net off against Excess income if under
tolerance limit.

Example: Tolerance limit Aed 50/-

Day-1 Cashier Balance Excess 10/-

Day-2 Cashier Balance Short 15/-

Day one to be considered Income, Day two to be accumulated till month end… if out of limit full
amount charged to cashier

 Store Coupons : It is nothing but manual vouchers

Other Income Integration / Mapping

Other Income: Below is part of other income:

Tenant Agreement: Tenant agreement will be entered in Oracle directly using custom form based on custom
tables. Geant will provide the fields need to enter in custom form / table. Below are the various income
categories under tanant agreement.

 ATM Rent Income

o Rental income collected from Banks for installing ATM machines inside stores.
o Example: BMI Bank ATM rent at Geant –Bahrain Mall Bd 750/- pm

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential vi

  Space Rent income
o Space rent Income collected from small vendors for exhibitions inside store.
o Example: New car launched on display for 3 weeks- Fees collected

 Shop Rent Income

o Rental Income received by subleasing a part of store space

o Example: Omega travels rental Income by Geant Bahrain Mall

 Electricity Income

o For the purpose of Mall, All electricity bill paid considered as Expense but the amount collected
from tenants (As per tenant agreement) are recognized as Income.

o Note: fix and variable. For variable we will create a recurring entry with default amount as 1
AED and that will be later editable by users.

 Sale of Carton Income

o Income generated from sale of empty cartons. Mainly monthly in nature.(Fixed per month per
store @ Bahrain). Not Applicable for U.A.E/Dubai.

o Note: Fix and variable. For variable we will create a recurring entry with default amount as 1
AED and that will be later editable by users.

 Lease Rent Income

o For the purpose of mall, rent collected from tenants are considered as lease rent income.(As per
tenant agreement terms)

 Exhibition Income
o Income collected from the Kiosk rental in mall, mainly in the nature of short term agreements (1
week to 2 yrs) with temporary structures (no shop address) are considered as exhibition income.

Customer Integration

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential vii

Cash Sales Transaction

Generally Geant (IBM (POS) sales happen in Cash under various types of sales categaries as mentioned above.
So for that we will create a cash customer (Geant Customer) in Oracle EBS. Geant have some 5-6 specific
customer names for above cash transactions so the same will be defined in Oracle EBS Receiavables based on the
list provide by Geant.

Some of the stores are using Navision for Sales so similarly like IBM AR invoice transaction will be also interface
from Navision.

Credit Sales Transaction

There are only some occasions for credit sales in Geant. Based on average there is only 1-2 credit sales in month
or sometime 1-2 credit sales in 2-3 months. So yearly there are only few transactions for credit sales. So for Credit
customer there will be manual entry in oracle as and when it happens.

Manual Income Entry in Oracele Receivables

Following type of income will be manually entered in the system and there will be no integration for such kind
of income and it need to manually enter in system as and when transactions happen.

 Miscellaneous Income
o All income of miscellaneous nature is considered. Example: sale of scraps.

 Security Income
o Income generated by security by penalizing shop lifters are considered as security income.

 Sale of Carton Income

o Income generated from sale of empty cartons. Mainly monthly in nature.(Fixed per month per
store @ Bahrain) ..This manual entry applicable only for U.A.E
 Barcode Income
o Income collected from Supplier for printing Barcodes on behalf of supplier products. To be
deducted from supplier by debit notes.

 Marketing Income

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential viii

 o From Suppliers: As per BAS terms income received for Promotion on daily subject to yearly
contract conditions.
o From Others: Marketing income received from outsiders for co-branding or participating in our
promotions.(May be in our stores or in our Mall)
o Example: Master card contribution for BD 20,000/- during Ramadan promotion of mall
o Or Credimax Participation in Geant Anniversary.
 Credit Transactions

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential ix

High Level Integration Flow (To be Process)

Source Destination

Legacy Systems Intermediate Table Pre Interface Table Oracle Interface Table Oracle EBS R12

IBM (Point Of Sales) Intermediate Table for Source DataPre Inteface Table for Basic Validations Oracle Standard Interface Table Oracle EBS R12 (Receivables)

Navision

Oracle Receivables and IBM Point of Sales /Navision (Geant legacy) Integration Flow Diagram

Interfaces Integrations Flow Details:

Data that need to integrate with Oracle Receivables will come from IBM Point of Sales source systems.
Following is the details of intergration flow between Geant Legacy and Oracle EBS Receivables.

IBM (Point of Sales)

There will be one interface between Geant IBM Legacy System and Oracle Receivables
 AR Transaction Interface(Auto Invoice)

Navision
There will be one interface between Geant Navison Legacy System and Oracle Receivables
 AR Transaction Interface(Auto Invoice)

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 4

Interface Technical Specification

Oracle Receivables will import and create invoices/Credit Memo as below:

Following are the intermediate tables what will be created and where Geant team needs to provide the data from source legacy systems on daily basis:

1. XXGEANT_RA_INT_LINES_ALL

2. XXGEANT_REV_RA_INT_LINES_ALL

Note: Above intermediate tables will have the same columns given in mapping section.

Oracle Receivables will uses the below three interface tables for AutoInvoice (Internal Use Only)

1. RA_INTERFACE_LINES_ALL

2. RA_INTERFACE_DISTRIBUTIONS_ALL

AutoInvoice transfers transaction data from the above three interface tables into the following Receivables tables:

 RA_BATCHES_ALL

 RA_CUSTOMER_TRX _ALL

 RA_CUSTOMER_TRX_LINES _ALL

 RA_CUST_TRX_LINE_GL_DIST_ALL

 AR_PAYMENT_SCHEDULES_ALL

 AR_RECEIVABLE_APPLICATIONS_ALL

 AR_ADJUSTMENTS_ALL

RA_INTERFACE_LINES:

 This table contains information relating to all transactions to be processed by AutoInvoice.

 Transactions include invoices, debit memos, credit memos, and on-account credits.

 Each record contains line, tax, freight, or finance charges information.

 The Line_Type field identifies the type of information contained in the record.

 A record can be a parent record: Line, Header Freight, or Charges; or a child record: Tax or linelevel Freight.

 A child record is linked to the parent record using the Link-To Transaction flexfield.

RA_INTERFACE_DISTRIBUTIONS:

 This table contains accounting distributions to be used by the transactions defined in RA_INTERFACE_LINES.

 Accounts defined in this table override any accounts created using AutoAccounting.

 You can choose to pass some or all account information to AutoInvoice. Any accounts that are not passed will be derived using AutoAccounting.

 Records in this table are linked to records in the RA_INTERFACE_LINES table using the Transaction flexfield.

 Not required if AutoAccounting determines GL distributions.

What occurs during Auto-Invoice:

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 5

 1. Populates the RA_Interface_Lines, RA_Interface_distribution and RA_Interface_salescredit tables.

2. Lines are grouped and ordered by the grouping rule and line ordering line. Grouping rules are mandatory and determine how transaction lines are grouped into
transactions. Optionally, you can use line-ordering rules to determine the order in which lines are displayed on a transaction.

3. Tax, freight, commitments and credit memos are linked to transaction line by transaction line, transaction reference and transaction link-to descriptive flex fields. To
uniquely identify imported transactions and link the tax, freight, commitments and credit memos, define the Transaction flexfields.

4. GL date is determined.

5. GL accounting code combinations are assigned using auto accounting rule.

6. TAX is determined.

7. All transactions are batched.

8. Validated lines are used to create the transaction.

9. When run, AutoInvoice produces the AutoInvoice Execution Report and the AutoInvoice Validation Report.

10. Any entries which failed validation can be reviewed in Oracle Receivables’ AutoInvoice Interface Exceptions window. Depending on the error, changes may need to be made
in Receivables, the feeder program or the imported records in the interface tables.

Transaction flexfields:

 Transaction flexfields are descriptive flexfields that AutoInvoice uses to uniquely identify transaction lines.

 Because they are unique for each transaction line, they can also be used to reference and link to other lines.

 Receivable lets you determine how you want to build your transaction flexfield structure and what information you want to capture.

 Define a flexfield for each import source. Specify which one to use during import.

Types of transaction flexfields:

 Invoice Header (optional): Specifies invoice header information

 Line (required): Uniquely identifies invoice lines

 Link-To (optional): Link tax and freight to invoice lines

 Reference (optional): Links credit memos to transactions

What is inside AutoInvoice?

AutoInvoice is a tool consists of 3 main programs. Each program will have unique nature of work to do and they are called internally except Purge program whose execution is derived
on the setup otherwise ready to execute stand alone.

 Master (RAXMTR)

 Import (RAXTRX)

 Purge (RAXDEL)

1] Auto Invoice Master Program:

Selects and marks records in the interface tables to be processed based on the parameters the user entered and then calls the AutoInvoice Import program. Auto Invoice Master program
has no report output.

 Gathers statistics, it means it gathers the stats on interface tables and set the stats on certain indices on interface tables.

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 6

  Marks interface records for processing by marking request_id.

 Submits multiple workers for Parallel Processing by creating instances for request.

2] Auto Invoice Import Program:

Validates the selected record and creates transaction if it passes validation. Any record that fails validation is left in the interface table with an error code. Depending on the setup, related
records may be rejected as well. This program has an output file called Auto Invoice Execution report, which you can view by clicking the View Report button in the Requests window.

 Workhorse of Auto invoice

 Validates data

 Inserts records

 Deletes interface data

 Only when system option purge set to ‘Y’

3] Auto Invoice Purge Program:

Deletes records from the interface tables. If you set the Purge Interface Table system option to No in Define System Option window, Auto Invoice does not delete processed records from
the interface tables after each run, and we must submit Auto Invoice Purge Program periodically to clean up the interface tables. This program only deletes transaction lines that have
been successfully imported.

AutoInvoice Exception Handling:

Records that fail validation are called ‘Exceptions’

 Exceptions stay in Interface Tables which is RA_INTERFACE_ERRORS_ALL.

 Errors can be corrected in the Exception Handling window.

 Once corrections are made, Auto invoice must be resubmitted.

 Records that pass validation get transferred to Receivables tables.

AutoInvoice Exception Handling Windows:

 Interface Exception window displays exception messages associated with all invalid records.

 Interface Lines window displays records that fail validation, provides an error message and can be used to correct the errors.

 The Line Errors windows displays errors associated with a specific line, and can only be opened from Interface Lines window.

 Interface Exceptions window displays Interface Id, Exception Type, Error Message and Invalid Value associated to the error.

 Data cannot be edited in this window, but error can be viewed and corrected by clicking the Details button.

 Error Message and Column name with invalid data are displayed in the Message column, and the invalid value that needs to be corrected is displayed in the Invalid Value
column.

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 7

Technical Process Flow

In Day end there will an automatic batch which will be trigged that will take data from Geant legacy system (IBM (Pos) \Navision and insert in the intermediate tables where the basic
validations will be done. After validation data will inserted in oracle above interface tables and later same will be revalidate and transfer to oracle base tables using starndard interface
concurrent program.

Destination
Intermediate Table Pre Interface TableOracle Standard Interface Table
Legacy Systems Sources Oracle EBS R12 (Receivables)

IBM (Point of Sales)

Navision

Integration Process Steps

1. Get vallid data from legacy system to Intermediate Tables. In Day end there will an automatic batch which will be trigged that will take data from Geant legacy system IBM
Point of Sales and insert in the intermediate tables

2. Load the intermediate table data into Pre-Interface table called staging table.

3. Validate the data in Pre-interface table using pl/sql procedures to define rules of validation.

4. Successful Validation rakes up the data to the Oracle standard interface tables.

5. These Validate data will be directed to base tables using predefined Seeded program.

6. Check for errors and report on interface.

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 8

Interface Import Concurrent Programs
 Auto Invoice Master Program

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 9

Master Interface Sheet
Follow is the master interface sheet for interface tracking.

Interface Souce Interface Name Interface Interface Tables Interface ConCurrent Programs
Destination

IBM Point of Sales AR Transactions (Auto Invoice) Oracle Oracle Receivables uses three interface Auto Invoice Master Program
Receivables tables for AutoInvoice:

 RA_INTERFACE_LINES_ALL

 RA_INTERFACE_DISTRIBUTIONS_ALL

Navision AR Transactions (Auto Invoice) Oracle

Receivables

Frequency

Above interfaces will run once daily after business hours. Later we can decide on exact scheduling time.

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 10

Oracle/Legacy Mapping

Oracle Receivables Invoice and Geant Legacy IBM column mapping:

Sales/Revenue
Name Datatype Length Mandatory Comments Notes for Devlopers Table Name Notes Sample Data

Start Level: 1              

Interface Object 1.        XXGEANT_RA_INT_LINES_ALL    

Name: RA_INTERFACE_LI
NES_ALL XXGEANT_REV_RA_INT_LINES_
ALL

INTERFACE_LIN NUMBER (15)   This column is

E_ID used by
AutoInvoice and
should be left
null. AutoInvoice
defaults a
value in this
column using the
RA_CUSTOMER
_TRX_LINES_S RA_CUSTOMER_TRX_LI
sequence. NES_S.NEXTVAL      

INTERFACE_LIN VARCHA (30)   This is a required

E_CONTEXT R2 column in
AutoInvoice.
Enter the context
of the Line
Transaction
Flexfield entered
in columns
INTERFACE_LI
NE_ATTRIBUTE
1. For Example
"Invoice Defautl Value
Migration" ="GEANTIMPORT "      

INTERFACE_LIN VARCHA (150)   Attribute value Trx_number      

E_ATTRIBUTE1 R2 used to
uniquely identify
this
transactionYou
must enter values
for
enabled
attributes.

INTERFACE_LIN VARCHA (150)   Attribute value

E_ATTRIBUTE2 R2 used to
uniquely identify
this
transactionYou
must enter values
for
enabled
attributes.  Defautl Value ="1 "      

INTERFACE_LIN VARCHA (150)   Attribute value

E_ATTRIBUTE3 R2 used to
uniquely identify
this
transactionYou
must enter values
for
enabled
attributes.        

BATCH_SOURC VARCHA (50) Yes Enter the name of

E_NAME R2 the batch source
for this
transaction.Name
of the batch
source associated
with the
trx_number, if
Source Name (IBM IBM POS,
specified. Only POS, NAVISION)     NAVISION

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 11

 used in
association with
trx_number to
help ensure
uniqueness.

LINE_TYPE VARCHA (20) Yes Enter 'LINE',

R2 'TAX', 'FREIGHT'
or 'CHARGES' to
specify the line
type for this
transaction.
(CHARGES
refers to finance
charges.) You
must enter a
value in this
column. Default Value = Line      

DESCRIPTION VARCHA (240) Yes Enter a

R2 description for Any Decription like
transaction if any ‘11121’   Location 11121

CURRENCY_CO VARCHA (15) Yes Enter currency Currency

DE R2 code for Code in
transaction  Like AED,BHD,KWD etc   Oracle AED

AMOUNT NUMBER   Yes Enter transcation Transaction Amount

amount for example 4000 AED Tender wise Sales Amount   4000

CUST_TRX_TYP VARCHA (20)   Enter the

E_NAME R2 transaction type
name for this
transaction.
This column is
optional, but
depending on the
value you
entered for your
batch source
Predefined Transaction
you must enter
either a value in type id from table
this column or in "ra_cust_trx_types_all"
CUST_TRX_TYP like " Cash " Gift
E_ID Voucher " etc   0

CUST_TRX_TYP NUMBER (15)   Enter the

E_ID transaction type
ID for this
transaction.
This column is
optional, but
depending on the
value you
entered for your
batch source
you must enter
either a value in
this column or in
CUST_TRX_TYP
E_NAME. If you
entered a value in
CUST_TRX_TYP
E_NAME,
AutoInvoice
defaults a value CUST_TRX_TYPE_ID
in this From table
column "ra_cust_trx_types_all"      

TERM_ID NUMBER (15)   Enter the

payment term ID
for this Predefined term_id
transaction. from table ra_terms_tl      

TERM_NAME VARCHA (15)   Enter the name of Predefined term_name

R2 the payment term from ra_terms_tl. We
for transaction. will use IMMIDIATE
as Default      

CONVERSION_T VARCHA (30) Yes Currency Default Value

YPE R2 conversation type =User\Corporate      
details . For

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 12

 example
corporate\user
etc.

CONVERSION_R NUMBER     Currency

ATE conversion rate
details Default =1      

TRX_DATE DATE     Enter transcation

date   Transaction date   11/15/2013

GL_DATE DATE     enter GL date for

transaction Transaction date  Transaction date    11/15/2013

TRX_NUMBER VARCHA (20)   Transaction

R2 number
  1261115112013

LINE_NUMBER NUMBER (15)   Line number

detaisl for
transaciton        

QUANTITY NUMBER     Quantity details

for transaction      

UNIT_SELLING_ NUMBER     Unit selling price

PRICE for transaction      

SALES_ORDER VARCHA (50)   sales order

R2 number for Good if you can
transation if any provide for reporting
for reference purpose      

SALES_ORDER_ DATE     sales order date Good if you can

DATE for transation if provide for reporting
any purpose      

ORIG_SYSTEM_ VARCHA 240     Default Customer

BILL_CUSTOME R2 Name = Geant
R_REF Customer    

ORIG_SYSTEM_ NUMBER (15)   Enter the Bill-To Default Customer

BILL_CUSTOME customer ID for Name = Geant
R_ID this transaction. Customer      

ORIG_SYSTEM_ NUMBER (15)   Enter the Bill-To

BILL_ADDRESS_ customer address
ID ID for this
transaction. This
Bill-To customer
address
ID is for the Bill-
To customer you
entered in
ORIG_SYSTEM_
BILL_CUSTOME Default Bill to Address
R_ID. ID for Geant Customer      

ORIG_SYSTEM_S NUMBER (15)   Enter the Ship-To

HIP_CUSTOMER customer ID for Default Values for Ship
_ID this transaction. to ID      

ORIG_SYSTEM_S NUMBER (15)   Enter the Ship-To

HIP_ADDRESS_I customer address
D ID for this Default value for
transaction. address ID      

PRIMARY_SALE NUMBER (15)   Sales person id

SREP_ID for tranaction if
any salesperson        

ORG_ID\ORG_N NUMBER (15)   Organization We will get the

AME identifier predefined id from table
hr_operating_units. You
just give the legal entity
name like "FUCOM LLC
DUBAI" , "Bahrain Mall" ,
"FUCOM CORPORATE",
"ELCOM INVESTMENT"
etc    

Some Column extra Colums for XXGEANT_REV_RA_INT_LINES_ALL

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 13

 Name Datatype Length Note Sample Data

ATTRIBUTE1 VARCHAR2 (150) Employee Code HD7184

SEGMENT3_ACCOUNT VARCHAR2 (25) IBM POS Tender Type Code 2000

ERROR_FLAG VARCHAR2 (1) Interface Status

G= General Ledger Interface

P=AR Interface

E= Error in AR Interface

N=Error in GL interface

ERROR_MESSAGE VARCHAR2 (240) Error Message if data is not

interface

Some Column extra Colums for XXGEANT_RA_INT_LINES_ALL

Name Datatype Length Note Sample Data

SEGMENT4_DEPARTMENT VARCHAR2 (25) Department Code 03-MARKET

SEGMENT5_SECTION VARCHAR2 (25) Section Code 29-COFFEE SHOP

ERROR_FLAG VARCHAR2 (1) Interface Status

G= General Ledger Interface

P=AR Interface

E= Error in AR Interface

N=Error in GL interface

ERROR_MESSAGE VARCHAR2 (240) Error Message if data is not

interface

Note:- Tender Type Data should be matched with Revenue data(Department/Section)

Yellow Mandatory

Green Optional

We can use
Blue
default Values

Concurrent Progarm name and procedure:-

1. Concurrent Program:- Geant IBM POS AR Interface

proc.txt

2. Concurrent Program:- Geant Revenue Distributon to Sections Program

proc.txt

Note: - Above program can be run from AR super responsibility and having To Date and From Date non-mandantoy parameter.

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 14

Open and Closed Issues

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

Doc Ref: Geant/AR/MD.050-070/V1.0 Prism / Geant Confidential 15