SLA Case Study

7/24/2019 SLA Case Study

http://slidepdf.com/reader/full/sla-case-study 1/33

1. Case Study – Sub-Ledger Accounting

Introduction

This section is aimed to guide you through the defnition o rules to

account or a Payables invoice. The environment to be used does

not have the adequate ledger setup to accommodate each user to

be able to create accounting using her/his own rules. Remember

that a primary or secondary ledger can have a single accounting

method eective at any given date or a given application.

Thereore, with a single primary ledger defnition !ision

"perations, #$%&, it will not be possible or all users to create

accounting concurrently or the same ledger. 'e will be

concentrating on the defnition o the rules in this class.

Defne Rules to Account or Payables Invoices

!ercise 1 - Co"y and #odiy $lo%

&as'

#sing the seeded Payables defnitions, copy and create your own

rule to account or an invoice. (our rule should)

- *ave your own description on the liability line,

- *ave a separate liability line or each invoice line, i.e. not

summari+ed.

Detailed Ste"s

opy the seeded -ournal line defnition Accrual, Invoices All and

perorm the ollowing changes or your copy)

. efne a -ournal entry description to be used on the liability

line. The description should contain your name as a

constant and the supplier name. 0t should appear only on

invoices having invoice date o 1ebruary 2, 2334.Responsibility) Payables, !ision "perations

5avigation) $etup 67 %ccounting $etup 67 %ccounting 8ethods

9uilder 67 8ethods and efnitions 67 :ournal ;ine efnitions

$ield (alue

:ournal escription ode <nter a code. :ournal escription 5ame <nter a name.<nabled (es Transaction hart o %ccounts 5ullescription <nter a description or this component you are

defning= can leave null.Priority etails This is what will show on the liability line as the



description. efne such that your name aswell as your supplier>s name is displayed.

onditions efne a condition such that this description isused only when invoice date is 1ebruary 2,2334.

2. ;iability lines o the entry should not be summari+ed i.e.there should be a liability entry or each invoice line. To

accomplish this, copy the seeded -ournal line type ?;iability,

9asic@, and modiy it such that -ournal entry lines with

matching criteria are not merged.

A. 8odiy your copied :; to use above components.

B. opy and modiy the seeded Payables application defnition

Accrual Basis to use your :;.

C. 8odiy the $ubledger %ccounting 8ethod Standard Accrual

to de6activate the seeded Payables %% and activate yoursas o 1ebruary st, 2334.



Solution

5avigation) $etup 67 %ccounting $etups 67 $ubledger

%ccounting $etup 67 %ccounting 8ethods 9uilder 67 :ournal

<ntry $etups 67 :ournal <ntry escriptions

. (our description should looD liDe below)

Figure 1 –JED for Liability Line

Figure 2 - JED Detail



Figure 3 - JED Condition

2. To ensure that liability lines with matching criteria E;

account, accounting class being a ew o many. 1or the ull

list, please reer to the $;% 0mplementation guide& are not

merged into a single line and that the granularity o theinvoice lines are preserved, set the Merge Matching Lines

option to ?5o@ on your :;T. 0n order to maDe the defnition

easier, instead o creating the :;T rom scratch, use the

copy unctionality on the seeded JLT Liability, Basic and

change the desired option. (our :;T should be similar to

below)

Figure 4 – New Liability JLT



A. Remove or de6activate the seeded ;iability, 9asic :;T rom

your copied :;, and assign your :;T, instead. o not orget

to assign your description to this :;T, as well as the same

account derivation rule as was on the seeded :;T that you

removed/de6activated. (our :; should looD liDe below)

Figure 5 – New n!oi"e JLD



B. opy the seeded %P %%= replace the :; or the event

class 0nvoice with your own. Remember to validate your

%%= the validation will checD or inaccuracies in the setup

and compile the code to create accounting per these rules.

(our %% should looD liDe below)

Figure # – New $% $$D



C. opy the seeded $tandard %ccrual $;%8, put an end6date

o :anuary Ast, 2334 on the seeded Payables %%. %dd a

new row and activate your %% as o 1ebruary st, 2334.

The $;%8 should looD liDe below)

Figure & - 'odified (L$'



!ercise ) Create $lo%

&as'

efne an %% or the accounting chart o accounts Operations Accounting Flex , such that it will generate a -ournal entry)

- "nly or the validation o %P invoices,

- with only item eFpense and liability lines i.e. no taF,

reight etc,

- booDing the liability line to the account) 36333622236

33336333,

- booDing the eFpense line to the distribution account on

the invoice line, but with the account segment valueoverwritten with 44B3.

Detailed Ste"s

efne the ollowing components and build your $;%8)

! ;iability :;T) opy your liability :;T defned in the previous

eFercise and modiy it such that lines with matching criteria

are merged. all your ;iability :;T

G105HII7H;0%90;0T(H8<RE<

"! <Fpense :;T) to create a line or invoice lines o type Ite#,

$ield (alue<vent lass 0nvoices;ine Type ode <nter G105HII7H05!"0<H<IP<5$<%ccounting lass

- 0tem <Fpense.

- This value will be on the entry line and is usedto categori+e lines, primarily or reportingpurposes.

5ame <nter a name.Rounding lass

- <nter the same value as in %ccounting lass.

- %long with the Rounding Reerence, this valueis used to determine at what level transactionrounding should be perormed advancedtopic&.

escription <nter a description or the component you aredefning= can leave null.

<nabled (es9alance Type %ctual, as we are not looDing to create budget or

encumbrance entries.$ide ebit. <Fpense amount should be debited to the

eFpense account.$witch ebit/redit

- 5o.

- etermines i the side on a line with anegative amount should be switched and the

negative made positive, or both the negativeand the side preserved. 1or eFample, an



amount o 633 may generate an entry linewith R 633 or R 33.

8erge 8atching ;ines - 5o.

- etermines i lines with matching criteriashould be merged into a single line.

$ubledger Eain/;oss -

5o.- 'ill this :;T be used to create an eFchange

gain/loss line calculated by the transactingapplication or the primary ledger advancedtopic&J

Transaction hart o %ccounts - 5ull.

- #sed in interpreting or converting anaccounting KeFfeld source carrying a valuerom the transaction or the primary ledgeradvanced topic&.

9usiness 1low 8ethod - 5one.

- etermines i certain attributes o the -ournal

line should be inherited rom another line. 1oreFample, or a liability line, copy the 9$! romthe corresponding eFpense line in the sameentry= or, on a payment, bacD out rom thesame liability account that was used on theinvoice o this payment advanced topic&.

9usiness 1low lass - 5ull.

- #sed together with the above when $rior%ntry is selected.

8ultiperiod - 5one.

- etermines i/how a payment should berecogni+ed as eFpense over multiple

accounting periods advanced topic&. Transer to E;

- $ummary.

- etermines whether the lines should betranserred to E; in the same level ogranularity as in $;% or summari+ed byaccounting KeFfeld and other criteria.

onditions efne a condition such that this :;T is used onlyor invoice lines with distribution type L 0tem.

%ccounting %ttribute%ssignments

- Review the sources assigned to theaccounting attributes to be used in derivingvalues or this -ournal entry line.

- #nchecD the <vent lass eault boF or the

attribute Party 0dentifer, and select 0nvoice$upplier $ite 0dentifer rom the list o values. This will result in the -ournal entry lineshowing the party site identifer as both theparty and the party site. 5ote that you canchange the event class deault only i therehave been multiple source assignments to anaccounting attribute on the event class level.

Note: This may not worD in our current trainingenvironment

A. ;iability %R) a constant based %R deriving accounting

KeFfeld 3633362223633336333, defned or accountingchart o accounts Operations Accounting Flex,



$ield (alueRule ode <nter a code. G105HII7H;0%90;0T(Rule 5ame <nter a name. G105HII7 ;iability %ccount<nabled (esescription <nter a description or the component you are

defning= can leave null.

hart o %ccounts6Transaction -

5ull


hart o %ccounts6%ccounting - "perations %ccounting 1leF

- 'ill allow defning constant values byvalidating against the "%.

"utput Type 1leFfeldPriority !alue Type onstant!alue 3633362223633336333

&! %R or invoice distribution account) already eFists as

seeded rule see the %R Invoice 'istribution Account

attached on the :;T Ite# %xpense :;T on seeded :; Accrual,

Invoices All&,

C. %R or account segment) a constant based %R deriving

value 44B3 or account segment, defned or accounting

chart o accounts Operations Accounting Flex,

$ield (alue

Rule ode <nter a code. G105HII7H<IP<5$<Rule 5ame <nter a name. G105HII7 <Fpense %ccount<nabled (esescription <nter a description or the component you are

defning= can leave null.hart o %ccounts6Transaction

- 5ull


hart o %ccounts6%ccounting - "perations %ccounting 1leF

- 'ill allow defning constant values by

validating against the "%."utput Type $egment M %ccountPriority !alue Type onstant!alue 44B3

(! :< optional&) you can use the :< already defned in the

previous eFercise,

4. :; or invoice validation event type) defned or accounting

chart o accounts " perations Accounting Flex)

- %ssign the liability :;T rom step N and the

liability %R rom step NA. 5ote that this %R



will determine the value or all the segments o

the accounting KeFfeld.

- %ssign the eFpense :;T rom step N2 and the

%R or invoice distribution account rom step

NB and %R or account segment rom step NC.

5ote that the ormer will determine the value

or all the segments o the accounting KeFfeld,

and the latter will overwrite the account

segment value.

-

*! Payables %%) defned or accounting chart o accounts

Operations Accounting Flex, to generate an entry only or

invoice validation events. %ssign the :; rom step N4. #se

the efnition ode G105HII7 "P<R%T0"5$H"%H%%.

*it the *eader %ssignments button, and checD the sourceassigned to the E; ate accounting attribute. The value o

this source rom the transaction will determine what the E;

date will be on the accounting entry. "ptionally, assign a

description or the header o the entry.

Remember to !alidate your %%.

+! $;%8) defned or accounting chart o accounts Operations

Accounting Flex, to generate accounting only or Payables

application. 5ote that you can also assign your "%6

specifc %% on a "%6generic $;%8. *owever, or the

purposes o this eFercise, defne a new one, calledG105HII7H"P<R%T0"5$H$;%8.



Solution

5avigation) $etup 67 %ccounting $etup 67 $ubledger

%ccounting $etup 67 %ccounting 8ethods 9uilder 67 :ournal

<ntry $etup 67 :ournal ;ine Types

! (our new liability :;T should be similar to below)

Figure ) - New Liability JLT



2. (our :;T or the eFpense line should be similar to below)

5ote) (ou may have to set the $ubledger Eain/;oss feld to

5"&

Figure * - New E+,ene JLT

Figure 1. - E+,ene JLT Condition



Figure 11 - E+,ene JLT $""ounting $ttribute

A. (our liability %R should be similar to below)

$etup 67 %ccounting $etup 67 $ubledger %ccounting $etup

67 %ccounting 8ethods 9uilder 67 :ournal <ntry $etups 67

%ccount erivation Rules

Figure 12 - Liability $D/



&! $eeded %R Invoice 'istribution Account will read the value

o the source Invoice 'istribution Account rom the

transaction, and will use the same account on the -ournal

line.

Figure 13 - (eeded $D/ for n!oi"e Ditribution $""ount



! <Fpense account %R should be similar to below)

Figure 14 - E+,ene $D/ for $""ount (eg0ent

(! The :< is defned in the previous eFercise.



-! (our :; should be similar to below)

$etup 67 %ccounting $etups 67 $ubledger %ccounting $etup

67 %ccounting 8ethods 9uilder 67 8ethods and efnitions

67 :ournal ;ines efnitions

Figure 15 - JLD for n!oi"e alidation E!ent



*! (our %% should looD liDe below)


67 %ccounting 8ethods 9uilder 67 8ethods O efnitions 67

%pplication %ccounting efnition

Figure 1# - $$D for ,eration $""ounting Fle+



Figure 1& - $$D eader $ign0ent

. (our $;%8 should be similar to below)


67 %ccounting 8ethods 9uilder 67 8ethods and efnitions

67 $ubledger %ccounting 8ethod

Figure 1) - (L$' for (er!i"e $""ounting Fle+



!ercise * - Create Accounting +sing Seeded SLA# %it,

Custo AAD

&as'

0n the opy and reate Kow above in <Fercise , you created your

own %89 components by copying and modiying the seeded

defnitions. (ou assigned your %% to the seeded $;%8 Standard

Accrual. 'hen you create accounting or any ledger that has this

$;%8 assignment, the invoices will be accounted per your rules.

This eFercise involves entering a transaction and generating

accounting or it per your defnition in <Fercise .

Detailed Ste"s

. reate a standard Payables invoice or operating unit

!ision "perations #$%&, with 2 item lines, validate

the invoice, and create online accounting in fnal

mode to post to E;.

ote/ 0 you use $upplier number 33C, you should

remove the istribution $et name that will deault

into the invoice header, otherwise this will generate

conusing results.

2. !iew the accounting lines generated.

A. !iew the -ournal entry.

B. !iew the details o one liability line.

C. !iew the entry in t6account ormat. 0arning/ this

might taDe a long time to appear M go or a coeeQ&



Solution

. #se the Actions button to submit online accounting or the

invoice.

Figure 1* - Create nline $""ounting for a %ayable n!oi"e

2. #se the toolbar to access accounting entry or the invoice,

displaying all lines generated. 5ote that i there are

multiple representations i.e. reporting currencies and

secondary ledgers, a separate entry will be generated oreach= but all lines belonging to all entries will be displayed

on this page.

Figure 2. - $""eing $""ounting Entry fro0 n!oi"e orben"6

Figure 21 - iew Journal Entry Line



A. #se the button .ie/ Journal %ntry to access more details o

the entry with the header inormation. 5otice that the

liability lines have not been summari+ed per the liability :;T

defnition you had created.

Figure 22 – iew Journal Entry

B. $elect the linD Sho/ or one o the liability lines to view the

details. 5otice the description is created per your :<.

Figure 23 - Journal Line Detail and De"ri,tion



C. $elect the button .ie/ T0Account .

Figure 24 - iew Journal Entry in T-$""ount For0at



!ercise - Create Accounting +sing Custo SLA# %it,

Custo AAD

&as'

0n the opy and reate Kow above in <Fercise 2, you created your

own %89 components including the $;%8. 0n order to use your

$;%8, you need to assign it to the ledger you are using. 'hen you

create accounting or any ledger that has this $;%8 assignment,

the invoices will be accounted per your rules. This eFercise

involves entering a transaction and generating accounting or it

per your defnition in <Fercise 2.

Detailed Ste"s

. reate a standard Payables invoice or operating unit !ision"perations #$%&, with 2 item lines, validate the invoice,

and create online accounting in fnal mode to post to E;.

2. "n $ubledger %ccounting :ournal <ntries page, search or

the two invoices you have entered in this eFercise and the

previous one.

A. $elect the two entries and hit 1o#pare button.

B. $witch to E; responsibility and view the new -ournal.

C. rill down to the $;% entry.

. rill down to the transaction.



Solution

. reate an invoice with the same date, amount, and

distribution accounts as in the previous eFercise.

2. epending on your search criteria, multiple entries may bereturned.

Figure 25 - (ear"6 Journal Entrie

A. ompare the details o the two entries, and notice the

dierence in the accounts and liability line summari+ation.

Figure 2# - Co0,are Journal Entrie

B. 5otice that the entry in E; has two lines with the eFpense

lines summari+ed, whereas the entry was created in $;%

with 2 eFpense lines to the same account. This is because



o the Transer to E; setting on the eFpense :;T, which was

set to $ummary. *ence, during transer to E;, lines hitting

the same account are summari+ed into a single one, with

the details being preserved in $;%. $;% entries are more

detailed than the E; entries.

Figure 2& - Entry iewed in 7L

C. #sing the ;ine rilldown button or the debit line, you

navigate to the $;% page to view the detail lines that were

summari+ed together to create the line as seen in E;.

Figure 2) - Detail Line in (L$

. 1rom the lines view, you can drill bacD to the transaction on

Payables invoice worDbench.

Figure 2* - Drilldown to Trana"tion



!ercise 2 - &roubles,oot Accounting rrors

Create Accounting +sing Custo SLA# %it, Custo AAD

&as'

0n this eFercise, you will be running diagnostics to troubleshoot an

error in accounting. #se your own $;%8, %%, and :; or invoice

validation, but replace the 0tem <Fpense :;T with the ollowing one

already defned as a template or you) ?L$ Ite# %xpense 2error34 .

" course, you should not be using this :;T, but copying it and

creating your own eFact copy with no modifcations.

Detailed Ste"s

. reate a standard Payables invoice or operating unit !ision

"perations #$%&, validate the invoice, and create

accounting in fnal mode to post to E;.

2. 'hen the process errors, run the reate %ccounting

program through $R$ in batch mode so you can see the

errors.

A. <nable diagnostics or your user i not already done= and

run the diagnostics report.

B. 0dentiy and fF the error.



Solution

. 1ollowing error will be displayed)

Figure 3. - nline $""ounting Error

2. $et the profle option $;%) <nable iagnostics to (es or

your user, and submit the Transaction "b-ects iagnosticsprogram.

Figure 31 - Enable Diagnoti"



A. $ubmit reate %ccounting program or your ledger, and

when completed, view the output or errors.

Figure 32 - Create $""ounting ffline

Figure 33 - Error on $""ounting /e,ort



Figure 34 - (ub0it Trana"tion b8e"t Diagnoti"

B. "n the output, locate the accounting attribute that the error

was reported or, i.e. %ccounted %mount. 5otice the source

and its value mapped to this attribute or the :;T that was

eFpected to create the entry line, ?Suantity !ariance

%mount in ;edger urrency@ with no value. This shows that

the accounting program was trying to create the entry line

using the value o this source, and was unable to create a

successul entry as the there was no value. % valid -ournal

entry line must always have a value or accounted amount.

1or a list o validations on a -ournal entry, please see the

appendiF o the $;% 0mplementation Euide.

To fF the error, you will need to change the source

mapped to this accounting attribute on the :;T that was

in error, i.e. your copy o the L$ Ite# %xpense 2error3

:;T. 5ote that ater modiying any component used in

it, your %% will need to be revalidated to compile the

code with the new settings.

'hen you generate accounting ater these changes

oine or online&, you will see an entry successully

created.



Figure 35 - Diagnoti" /e,ort

Figure 3# - $""ounting $ttribute $ign0ent on t6e JLT



Figure 3& - /e!alidating t6e $$D

SLA Case Study

Documents

Transcript of SLA Case Study