SERIS To Oracle GL Interface



Technical Specifications

SERIS TO ORACLE GENERAL LEDGER INTERFACE

DOCUMENT CONTROL

|Author |Update Date |Version |Comments |

|Lax Koonshetty |20-Aug-10 |1.0 |Original Document |

| | | | |

| | | | |

Reviewers

|nAME |pOSITION |

|Todd Leiby |Applications Director, OIT |

|Dan Krautheim |Director, DBA |

|Bob Kurtis |Applications Analyst/Developer, OIT |

Contents

Technical Overview 3

Purpose 3

Background 3

Design 3

Technical Specifications 4

Business Requirements 4

Data Mapping Definition 5

Configuration 7

Setup 7

Concurrent Processes 7

User Procedures 9

N To update the table of contents, put the cursor anywhere in the table and press [F9]. To change the number of levels displayed, select the menu option Insert->Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

Purpose

The purpose of this process is to load daily transactional data from a feeder system to Oracle Financials General Ledger module.

Background

SERIS maintains transactional data that is being loaded daily into SBT Accounting System for accounting purposes. Due to the growing needs, it was decided to replace SBT Accounting system with Oracle E-Business Suite package. As part of the migration efforts, this process will replace the daily scheduled interface from SERIS to SBT Accounting system.

Design

[pic]

Technical Specifications

Business Requirements

General

• Process should be registered as a concurrent request accessible by end users with General Ledger responsibility

• Process should be automated to run on a daily basis

Parameters

Ledger ID

Fund

Selection Criteria

All detail journal lines where:

• Transaction Status = Unprocessed

• Fund = Input Parameter

Validation

Validation will be performed by the standard Oracle Journal Import program and errors will be corrected using Oracle standard correction form. For too many errors, GL_INTERFACE table is cleared & the custom process is re-run to extract corrected data

Import Defaults

• Status = ‘NEW’

Output Report

• Log file containing all the selected journal entries should be displayed as a report with process status, to verify/confirm the processing of data in Oracle EBS

• All associated tables should be updated to reflect processing completion in SERIS (logic to update SERIS tables should be similar to the one used in ‘GL002’ COBOL program)

Data Mapping Definition

|Target Table |Target Field |Source Table |Source Field |Hint |

| | | | | |

|GL_INTERFACE |STATUS | |‘NEW’ | |

|GL_INTERFACE |LEDGER_ID | | |From Oracle Setup |

| | | | |(select ledger_id, name from |

| | | | |gl_ledgers;) |

|GL_INTERFACE |USER_JE_SOURCE_NAME | | |From Oracle Setup |

|GL_INTERFACE |USER_JE_CATEGORY_NAME | | |From Oracle Setup |

|GL_INTERFACE |ACCOUNTING_DATE |GL_DPS_TRNS |TRNS_DATE | |

|GL_INTERFACE |CURRENCY_CODE | |‘USD’ | |

|GL_INTERFACE |DATE_CREATED | |SYSDATE | |

|GL_INTERFACE |CREATED_BY | | |From Oracle Setup |

| | | | |(select user_id |

| | | | |from fnd_user;) |

|GL_INTERFACE |ACTUAL_FLAG | |‘A’ |Balance type (Actual (A), |

| | | | |Budget(B), Encumbrance(E) ) |

|GL_INTERFACE |SEGMENT1 | | |Fund |

| | | | |(From Oracle Setup) |

|GL_INTERFACE |SEGMENT2 |GL_DP_TRNS |CREDIT_GLAC/ |Account (‘323’=’3230’) |

| | | |DEBIT_GLAC | |

|GL_INTERFACE |ENTERED_CR |GL_DP_TRNS |TRNS_AMT | |

|GL_INTERFACE |ENTERED_DR |GL_DP_TRNS |TRNS_AMT | |

|GL_INTERFACE |REFERENCE1 | |‘NULL’ |Batch Name |

|GL_INTERFACE |REFERENCE2 | |‘NULL’ |Batch Description |

|GL_INTERFACE |REFERENCE4 |GL_DP_TRNS |DOC_NUM |Journal Entry Name |

|GL_INTERFACE |REFERENCE5 | |‘NULL’ |Journal Entry Description |

|GL_INTERFACE |REFERENCE10 | |‘NULL’ |Journal Entry Line Description |

|GL_INTERFACE |PERIOD_NAME | | |From Oracle Setup |

|GL_INTERFACE |REFERENCE21 |MEMBER/ |ID |Member ID |

| | |BENEFICIARY | | |

|GL_INTERFACE |REFERENCE22 |AGENCY_RECEIPT |INV_ID |Invoice ID |

|GL_INTERFACE |REFERENCE23 |AGENCY_RECEIPT |AGCY_ID |Agency ID |

|GL_INTERFACE |REFERENCE24 |GL_DP_TRNS |PROCESS_TYPE |Process Type |

|GL_INTERFACE |REFERENCE25 |GL_DP_TRNS |ALLOC_TYPE |Allocation Type |

|GL_INTERFACE |REFERENCE26 |MEMBER/ |SSN |SSN |

| | |BENEFICIARY | | |

|GL_INTERFACE |REFERENCE27 |AGENCY_RECEIPT |RPTING_PERIOD |Reporting Period |

|GL_INTERFACE |REFERENCE28 |AGENCY_RECEIPT |RPTING_YEAR |Reporting Year |

|GL_INTERFACE |REFERENCE29 |MEMBER_RECEIPT/AGENCY_INVOICE_I|ARREARS_TYPE |Arrears Type |

| | |TEM | | |

|GL_INTERFACE |REFERENCE30 |GL_DP_TRNS |REV_CODE |Revenue Code |

Configuration

Setup

Navigate to Setup>Journal>Sources

|Source |Source Key |Description |Import Journal References |Freeze Journals |

| | | | | |

|SERIS Interface |SERIS Interface |SERIS Interface |Yes |No |

Concurrent Processes

Following concurrent program and request sets will be defined

• Define concurrent program as specified –

SERIS To Oracle GL Interface

Parameters – None

Executable Type – PL/SQL

• Define Request Set as specified –

SERIS To Oracle GL Import

Programs – SERIS To Oracle GL Interface

Journal Import

User Procedures

Steps to run the process are as below

• Login to General Ledger responsibility

• Navigate to Other>Report>Run

• Select ‘SERIS To Oracle GL Interface’ from the list of values (‘SERIS To Oracle GL Import’ to run both the custom process & Journal Import) & submit

• After successful completion, select ‘Journal Import’ program from the list of values & submit (Ignore this step if you ran the request set)

• Verify the log files of two spawned concurrent requests

• Data Errors, if any, can be corrected by navigating to Journals>Import>Correct

• Re-submit ‘Journal Import’ program to load the corrected data elements, if any

-----------------------

SERIS

No

Yes

Error?

Oracle EBS

ORACLE GL Base tables

!! CONTROL POINT !!

Standard Oracle Journal Import Process

GL_INTERFACE table

SERIS to Oracle GL Interface (Custom PL/SQL Import Process)

SERIS tables

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download