7
Wednesday, 01 December 2010 07:24 Anil Passi SLA Part 3 - Journal Line Definition User Rating: / 12 Poor Best RATE The Journal Line Definition "defines" how the entire journal is built. To create any journal, one of the key things is to get the CCID or the code combination of segments. SLA needs to know where this CCID will be coming from. You also need to know whether this CCID will be debit or this CCID will go into credit. Therefore you not just require the CCID, but you also need to decide whether a specific CCID will be debited or credited. In SLA, the "Journal Line Type" will specify whether the accounting entry is credit or debit. Also, you can then "attach something called an ADR to this Journal Line Type". The ADR returns the final code combination. Therefore Journal Line type will leverage the JLT+ADR to know which CCID is crediting and which CCID is debiting in the journal. For each and every application there is a combination of event class and event type. Depending upon the combination of event class and event type the accounting gets triggered. The standard SLA out of the box from Oracle meets your requirement by 90%. For example you can fetch the standard accounting from payables or receivables options. However where these standard seeded accounting do not suffice, you can go and modify SLA to meet your business needs. There is something called as Journal Entry Description. When a transaction is transferred as a journal, then every journal has credit/debit and description. The journal has description at header and also at line level. The JED allows you to generate the description of the Journal at both header and line level. For example you may want Customer Name or Customer Number in the journal description for a journal that is initiated from Oracle Receivables module. Using JED in SLA you can build header or line level descriptions. The image below describes the end result journal that is produced by SLA RELATED ITEMS Forms Customization Steps in Oracle Applications OA Framework R12 Extension Example Oracle General Ledger Overview Oracle Payables Overview - Functional Document Oracle Fixed Assets Implementation Document R12 New Functionality - Differences with 11i R12 SLA - Subledger Accounting Explained Part 1 R12 Cash Forecasting Reconcile Bank Statements in R12 R12 - Cash Pool In Cash Management R12 - Accounting Setup Manager in Oracle General Ledger R12 Procurement Features R12 Inventory Features R12 - Fixed Assets Presentation Oracle iProcurement in R12 R12 New Features in Oracle Payables R12 - Oracle General Ledger Features R12 Oracle Receivables Features R12 Cash Management Features R12 - Netting Functionality Step By Step Oracle Apps Functional Overview Oracle Payables - Step by Step functional in 11i - PART 1 Oracle Payables - Step by Step functional in 11i PART 2 Oracle Payables - Step by Step functional in 11i - PART 3 SLA Part 11 - Steps to Customize of SLA - Subledger Accounting APPS TO FUSION .......Our Journey from Apps To Fusion Home Technical Articles Training Articles Receive Email for New Articles Contributors Forum My Book Solutions SLA Part 3 - Journal Line Definition http://apps2fusion.com/apps-training/r12-functional-docu... 第1页 共7页 2013/4/9 20:57

SLA Part 3 - Journal Line Definition.pdf

  • Upload
    soiree

  • View
    19

  • Download
    0

Embed Size (px)

Citation preview

Page 1: SLA Part 3 - Journal Line Definition.pdf

Wednesday, 01 December 2010 07:24 Anil Passi

SLA Part 3 - Journal Line Definition

User Rating: / 12

Poor Best RATE

The Journal Line Definition "defines" how the entire journal is built. To create any journal, one of the key things is to get the CCID or the code combination of segments. SLA needs to know where this CCID will be coming from. You also need to know whether this CCID will be debit or this CCID will go into credit. Therefore you not just require the CCID, but you also need to decide whether a specific CCID will be debited or credited. In SLA, the "Journal Line Type" will specify whether the accounting entry is credit or debit. Also, you can then "attach something called an ADR to this Journal Line Type". The ADR returns the final code combination. Therefore Journal Line type will leverage the JLT+ADR to know which CCID is crediting and which CCID is debiting in the journal.

For each and every application there is a combination of event class and event type. Depending upon the combination of event class and event type the accounting gets triggered. The standard SLA out of the box from Oracle meets your requirement by 90%. For example you can fetch the standard accounting from payables or receivables options. However where these standard seeded accounting do not suffice, you can go and modify SLA to meet your business needs.

There is something called as Journal Entry Description. When a transaction is transferred as a journal, then every journal has credit/debit and description. The journal has description at header and also at line level. The JED allows you to generate the description of the Journal at both header and line level. For example you may want Customer Name or Customer Number in the journal description for a journal that is initiated from Oracle Receivables module. Using JED in SLA you can build header or line level descriptions.

The image below describes the end result journal that is produced by SLA

RELATED ITEMS

Forms Customization Steps in

Oracle Applications

OA Framework R12 Extension

Example

Oracle General Ledger

Overview

Oracle Payables Overview -

Functional Document

Oracle Fixed Assets

Implementation Document

R12 New Functionality -

Differences with 11i

R12 SLA - Subledger

Accounting Explained Part 1

R12 Cash Forecasting

Reconcile Bank Statements in

R12

R12 - Cash Pool In Cash

Management

R12 - Accounting Setup

Manager in Oracle General

Ledger

R12 Procurement Features

R12 Inventory Features

R12 - Fixed Assets

Presentation

Oracle iProcurement in R12

R12 New Features in Oracle

Payables

R12 - Oracle General Ledger

Features

R12 Oracle Receivables

Features

R12 Cash Management

Features

R12 - Netting Functionality

Step By Step

Oracle Apps Functional

Overview

Oracle Payables - Step by

Step functional in 11i - PART 1

Oracle Payables - Step by

Step functional in 11i PART 2

Oracle Payables - Step by

Step functional in 11i - PART 3

SLA Part 11 - Steps to

Customize of SLA - Subledger

Accounting

APPS TO FUSION.......Our Journey from Apps To Fusion

Home Technical Articles Training Articles Receive Email for New Articles Contributors Forum My Book

Solutions

SLA Part 3 - Journal Line Definition http://apps2fusion.com/apps-training/r12-functional-docu...

第1页 共7页 2013/4/9 20:57

Page 2: SLA Part 3 - Journal Line Definition.pdf

In JLT Journal Line Type, you can specify whether the entry is for credit or debit side. The Journal Line Type also provides options to do accounting for Gain/Loss of Foreign currency transactions. Further to that you can specify if SLA should merge the journal lines that have same CCID.

Control or Third Party

Accounts in R12 General

Ledger

E Business Tax R12 - EBiz

Tax Implementation Steps

EBiz Tax - Part 1

SLA Part 1 - Why SLA

SLA Part 2 Entities - Event

Class - Event Types

Oracle Payables - Step by

Step functional in 11i - PART 4

SLA - Account Analysis Report

- Out of memory error

Generate BACS File in R12

Payables for Payment run

PO to AP to Fixed Assets

Order to Cash - Technical

Flow in R12

Steps for Closing Period in

R12 Financials - Part 1 - USE

FIREFOX

Steps for Closing Period in

R12 Financials - Part 2

Global Consolidation R12

SLA Part 4 - Application

Accounting Definitions

SLA Part 5 - Subledger

Accounting Methods

SLA Part 6 - Overall SLA

Diagram

SLA Part 7 - Creating Journal

Line Definition

Financials Notes

R12 - Create Banks and Bank

Accounts in Oracle Apps R12

SLA Part 8 - Creating

Application Accounting

Definition - AAD

SLA Part 9 - Create Subledger

Accounting Method

SLA Part 10 - Testing and

explaination of SLA Config

SEARCH APPS2FUSION

SLA Part 3 - Journal Line Definition http://apps2fusion.com/apps-training/r12-functional-docu...

第2页 共7页 2013/4/9 20:57

Page 3: SLA Part 3 - Journal Line Definition.pdf

ADR - We specify how the account combination must be generated. We tell the system how we want the CCID should be built and transferred to the general ledger. You can either transfer the standard account as calculated within Subledger(AP or AR or PA etc) or the account generated from Subledger can be modified or replaced via ADR configuration within SLA.

Further to this, when defining ADR, you can specify the conditions under which a specific segment or CCID is returned. These conditions are like IF Conditions.

It is good to remember that the "Journal Line Definition=JED+JLT+ADR"

This is visible from the screenshot as shown below

SLA Part 3 - Journal Line Definition http://apps2fusion.com/apps-training/r12-functional-docu...

第3页 共7页 2013/4/9 20:57

Page 4: SLA Part 3 - Journal Line Definition.pdf

You will notice that two "Journal Line Types" have been attached to this Journal Line Definition. The first journal line type assignment creates a credit line in the journal and the second journal line type assignment creates a debit line in the journal.

By now you would have understood the significance of Journal Line Definition. However you might be wondering how this Journal Line Definition gets associated with a Subledger transaction. For example, how does Oracle E-Business Suite decide which specific Journal Line Definition should be used when a specific event takes place against an invoice in Oracle Payables. In other words, how will SLA decide how the Journal will be constructed when an invoice is validated within Payables. We will learn this via AAD in next part of the article using Application Accounting Definitions.

Comments (7)Subscribe to this comment's feed

Set as favoriteBookmarkEmail ThisHits: 12638

report abusevote downvote up

Oracle Apps Consultant

written by Joy , December 02, 2010

Hi Anil,

Thanks for your posts on SLA. The concepts are explained in very simple terms and can be grasped very easily. I

believe in many R12 implementations we are not fully leveraging SLA functionality because of lack of clarity on this

area. I am sure we can do away with lot of customizations on accounting generators if we can leverage SLA. Please

confirm on this point. Waiting for your newer posts on this subject. Keep up the good work.

Thanks

Joy

Votes: +2

SLA

written by Prasad CP , December 02, 2010

Thanks Anil , you have put the concepts very lucidly . Those who like it diagramitically this is how it all fits

ADR JED JLT

| /

SLA Part 3 - Journal Line Definition http://apps2fusion.com/apps-training/r12-functional-docu...

第4页 共7页 2013/4/9 20:57

Page 5: SLA Part 3 - Journal Line Definition.pdf

report abusevote downvote up

| /

| /

| /

| /

| /

| /

JLD

|

|

AAD

|

|

SLAM

|

Ledgers

ADR = Account Derivation Rules

JED = Journal Entry Description

JLT = Journal Line Type

JLD = Journal Line Definition

AAD = Application Accounting Definition

SLAM = Subledger Accounting Method

Votes: +2

report abusevote downvote up

...

written by Anil Passi , December 03, 2010

That is right Joy, you no longer need to customize Account Generator Workflow, as you can control account build

from SLA centrally. Also this gives business users visibility into the config of SLA.

Thanks,

Anil Passi

Votes: +0

report abusevote downvote up

doubt in FAH

written by SwatiT , June 28, 2011

Hi Puneet,

Very nice way of writing.

Could you please tell me if FAH has its own reporting?

Thanks

Swati

Votes: +0

report abusevote downvote up

Adding Intercompany segment in accrual account

written by Sagar Gaikwad , October 12, 2011

Currently when a PO item is received in Oracle the system generates an automatic accrual into the GRNI accounts

223000/224000.

Is it possible for the system to recognize the supplier and to continue using the GRNI accounts but to add an

intercompany segment where applicable?

Votes: +0

ADR Derivarion rule

written by Shoban , May 22, 2012

Hello Anil,

I have scenario here, Wanted to understand if this is achievable scenario. If yes, can you please guide me on this

please.

Currently, IPV and EPV are being coded to 12345 accounts in the case of inventory items, and to the 56789 clearing

account in the case of ABC service fee invoices.

Below i have shown as to how IPV and EPV should be coded to the relevant 13*20 account depending on whether it

relates to;

SLA Part 3 - Journal Line Definition http://apps2fusion.com/apps-training/r12-functional-docu...

第5页 共7页 2013/4/9 20:57

Page 6: SLA Part 3 - Journal Line Definition.pdf

Write comment

report abusevote downvote up

1. Raw Materials, WIP (BLKT) or Finished Goods (BSTK or FG), or in the case of

2. ABC Service fees, where the relevant 13*20 account is determined by whether the fee is for WIP (BLKT) or FG

(BSTK of FG).

In Oracle PV’s should be booked to the Balance Sheet – COMPANY.000.13*20.00000.Product Code.000.

In the manufacturing entities, price variances on the purchase of raw materials and on ABC fees charged should be

coded to the relevant PV accounts on the balance sheet [13120, 13220, 13320]

IPV and EPV should be coded to the relevant 13*20 account depending on whether it relates to raw materials, WIP

(BLKT) or FG (BSTK or FG).

IPV and EPV on ABC fee invoices should be coded to the relevant 13*20 account driven by whether the fee is for

WIP (BLKT) or FG (BSTK or FG).

The coding should be based on the inventory category code set attached to each item number, which contains

Manufacturing Stage, Material Type, Product and Alliance. The material type and the product categories should be

able to determine the US GAAP account and product code combinations.

Note:

· The Material type in the category code set drives the natural account in the GL

· The Product in the category code set drives the Product segment in the GL

This table outlines the logic upon which each attribute in the Account Segment String is determined.

BS = from purchasing LE

CC = Always 0000 on balance sheet

NATURAL ACCOUNT = Derived from the MATERIAL TYPE on the Inventory Category Code Set

Location = Always 00000

PRODUCT = Derived from PRODUCT SEGMENT on the Inventory Category Code Set

INTERCOMPANY = Always 000

FUTURE 1 = Always 000000

FUTURE 2 = Always 000000

Votes: +0

report abusevote downvote up

Difference between SLA and FAH

written by Gunjan Bansal , June 14, 2012

Hi Anil,

Very nice Article .. Simple language and easy to understand..

Could you please tell me the difference between SLA and FAH..

Votes: +0

Name

Email

Title

Comment

smaller | bigger

Subscribe via email (Registered users only)

Write the displayed characters

SLA Part 3 - Journal Line Definition http://apps2fusion.com/apps-training/r12-functional-docu...

第6页 共7页 2013/4/9 20:57

Page 7: SLA Part 3 - Journal Line Definition.pdf

Last Updated ( Sunday, 28 November 2010 08:42 )

SLA Part 3 - Journal Line Definition http://apps2fusion.com/apps-training/r12-functional-docu...

第7页 共7页 2013/4/9 20:57