1. Case Stu dy – Sub-Ledger Ac counting Introduction This section is aimed to guide you through the defnition o rules to account or a P ayables invoice. The environment to b e used does not have the adequate ledger setup to accommodate each user to be able to create a ccounting 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. Thereor e, with a single primary ledger defnition ! ision "perations, #$%&, it will not be possible or all users to create accounti ng concurrently or the same ledger. 'e will be concentrating on the defnition othe 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 invo ice. ( 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 defnitionAccrual, Invoices All and perorm the ollowing changes or your copy) . efn e a -our nal 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 on ly on invoices having invoice date o1ebruary 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 T ransaction hart o% ccounts 5ull escription <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
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
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
- #sed in interpreting or converting anaccounting KeFfeld source carrying a valuerom the transaction or the primary ledgeradvanced topic&.
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
- #sed in interpreting or converting anaccounting KeFfeld source carrying a valuerom the transaction or the primary ledgeradvanced topic&.
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