$&2YHUKHDG&RVW2UGHUV
$&
2YHUKHDG&RVW2UGHUV SAP AG 1999
n
R/3 System
n
Release 4.6C
n
December 2000
n
Material Number 5004 2614
&RS\ULJKW
&RS\ULJKW6$3$*$OOULJKWVUHVHUYHG
1HLWKHUWKLVWUDLQLQJPDQXDOQRUDQ\SDUWWKHUHRIPD\ EHFRSLHGRUUHSURGXFHGLQDQ\IRUPRUE\DQ\PHDQV RUWUDQVODWHGLQWRDQRWKHUODQJXDJHZLWKRXWWKHSULRU FRQVHQWRI6$3$*7KHLQIRUPDWLRQFRQWDLQHGLQWKLV GRFXPHQWLVVXEMHFWWRFKDQJHDQGVXSSOHPHQWZLWKRXWSULRU QRWLFH $OOULJKWVUHVHUYHG
SAP AG 1999
7UDGHPDUNV n
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
n
Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of Microsoft Corporation.
n
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
n
ORACLE® is a registered trademark of ORACLE Corporation, California, USA.
n
INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.
n
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.
n
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139.
n
JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto, CA 94303 USA.
n
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
n
SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP™, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.
n
Design: SAP Communications Media
&RQWUROOLQJ /HYHO
/HYHO
Cost Center Accounting
2 days Cost Center Accounting: Extended Functionality 3 days
2 days
Activity Based Costing
3 days Cost Object Controlling for Products 3 days
Product Cost Planning
5 days
Profitability Analysis
Profit Center Accounting
SAP AG 1999
2 days
Overhead Orders
5 days
Cost Management and Controlling
2 days
2 days Executive Information System (EIS) 1 Reporting
3 days Cost Object Controlling for Sales Orders
Actual Costing / Material Ledger
2 days 2 days
Transfer Prices
2 days Executive Information System (EIS) - Setting up the System
1 day Executive Information System (EIS) 3 Business Planning
&RXUVH3UHUHTXLVLWHV
l 6$36$352YHUYLHZ UHFRPPHQGHG l $&&RVW&HQWHU$FFRXQWLQJ UHTXLUHG
l %DVLFNQRZOHGJHDQGH[SHULHQFHLQFRVWDFFRXQWLQJ
l *RRGZRUNLQJNQRZOHGJHRI:LQGRZVRSHUDWLQJHQYLURQPHQW
SAP AG 1999
7DUJHW*URXS l $XGLHQFH
3URMHFWWHDPPHPEHUVUHVSRQVLEOHIRULPSOHPHQWLQJ 2YHUKHDG&RVW&RQWUROOLQJ
$FFRXQWLQJSHUVRQQHOUHVSRQVLEOHIRUSODQQLQJ DOORFDWLQJDQGDQDO\]LQJRUJDQL]DWLRQDOFRVWV
l 'XUDWLRQ GD\V
SAP AG 1999
1RWHVWRWKHXVHU n
The training materials are QRWWHDFK\RXUVHOISURJUDPV. They FRPSOHPHQWWKHFRXUVHLQVWUXFWRU¶V H[SODQDWLRQV. Your material includes space for noting down this additional information.
n
There may not be enough time to do all the exercises during the course. The exercises are intended to be additional examples that are dealt with during the course. Participants can also use them to deepen their knowledge after the course.
&RXUVH2YHUYLHZ &RQWHQWV l &RXUVHJRDOV
l &RXUVHREMHFWLYHV l &RXUVHFRQWHQW
l &RXUVHRYHUYLHZGLDJUDP l 0DLQEXVLQHVVVFHQDULR
SAP AG 1999
© SAP AG
AC415
1-1
&RXUVH*RDOV
7KLVFRXUVHZLOOSUHSDUH\RXWR l l
&RQILJXUHDQGXVHWKH,QWHUQDO2UGHUVFRPSRQHQW
$FTXLUHNQRZOHGJHWRSODQSRVWDOORFDWHDQG DQDO\]HFRVWV
SAP AG 1999
© SAP AG
AC415
1-2
&RXUVH2EMHFWLYHV
$WWKHFRQFOXVLRQRIWKLVFRXUVH\RXZLOOEHDEOHWR l 'HVFULEHDQGPDLQWDLQPDVWHUGDWDIRULQWHUQDORUGHUV
l ,GHQWLI\VRXUFHVRILQWHUQDORUGHUSRVWLQJVDQGSURFHVV
WUDQVDFWLRQV
l 'HVFULEHDQGXVHSHULRGLFSURFHVVLQJIXQFWLRQVDQGVHW
WKHVHIXQFWLRQVXS
l 'LVFXVVLQWHUQDORUGHUSODQQLQJDQGWKHRSWLRQVIRU
HQWHULQJSODQGDWD
l 6XPPDUL]HDQGDQDO\]HLQWHUQDORUGHULQIRUPDWLRQ
XVLQJUHSRUWV
l 'HILQHVSHFLDORUGHUFDWHJRULHV
SAP AG 1999
© SAP AG
AC415
1-3
&RXUVH&RQWHQW
3UHIDFH Unit 1 Unit 2 Unit 3 Unit 4
&RXUVH2YHUYLHZ
Unit 5
0DVWHU'DWD
Unit 7
,QWHUQDO2UGHUV 2YHUYLHZ Unit 6
(YHQWEDVHG3RVWLQJV
Unit 8 Unit 9
3HULRGHQG&ORVLQJ
3ODQQLQJDQG%XGJHWLQJ
2UGHU6XPPDUL]DWLRQ
&RQFOXVLRQ $SSHQGL[
([HUFLVHV 6ROXWLRQV SAP AG 1999
© SAP AG
AC415
1-4
&RXUVH2YHUYLHZ'LDJUDP
,QWHUQDO2UGHUV 2YHUYLHZ 0DVWHU'DWD (YHQW%DVHG 3RVWLQJV (YHQW%DVHG3RVWLQJV 3HULRG(QG &ORVLQJ 3HULRG(QG&ORVLQJ 3ODQQLQJDQG%XGJHWLQJ 2UGHU6XPPDUL]DWLRQ SAP AG 1999
© SAP AG
AC415
1-5
0DLQ%XVLQHVV6FHQDULR
l l
l
? # % % +< :@%
,QYHVWPHQW 2UGHUV
$FFUXDO 2UGHUV
( "!$#% &('2% >D # ,%( I%
ACBA ( >? # ,% % BD# # % E :@% :
&RVW$FFRXQWLQJ)XQFWLRQV
2UGHUV:LWK 5HYHQXHV
F( 8 ,GH% ,% 9% 5HYHQXHV
"!$# %&(')% *+( %,#- . % /0" 1 " &)% %'2% 34. % #45- 768%:9 % % #
SAP AG 1999
n
Internal orders in the R/3 System describe individual jobs within a controlling area. Orders support action-oriented planning, monitoring, and allocation of costs.
n
You can use internal orders to: é Monitor internal jobs settled to cost centers (overhead orders) é Monitor internal jobs settled to fixed assets (investment orders) é Offsetting postings of accrued costs calculated in CO (accrual orders) é Display the cost controlling parts of Sales and Distribution customer orders and revenues that do not affect the core business of the company (orders with revenues)
n
The management of internal orders represents the most detailed operational level of cost and activity accounting and can be used for the following: é You can analyze costs differently than in Cost Center Accounting for cost management. é You can compare in-house production and external procurement costs for decision-making.
n
The primary focus of this course is overhead orders. The other types of internal orders are discussed in more detail in “Special Subjects”.
© SAP AG
AC415
2-9
,QYHVWPHQW2UGHUV ,QYHVWPHQW 0HDVXUH 'HELWVGXULQJ FRQVWUXFWLRQ3KDVH 3XUFKDVH2UGHUV Down Payments Acquisitions Internal Activities
Order/WBS-Element Budget Plan values Commitments Actual Values Periodic Settlement / Capitalization $VVHWXQGHU FRQVWUXFWLRQ
$VVHW+LVWRU\ 6KHHW
)XOO 6HWWOHPHQW
$VVHW $VVHW $VVHW
$FW9DOXHV
&RVW&HQWHU SAP AG 1999
n
Investment Management (IM) provides functions that support the planning, investment, and financing processes involved in investment measures in your enterprise. You can control measures that your company undertakes for the purpose of producing long-term assets for its own use, and which have to be entered in the balance sheet as assets under construction.
n
Measures are represented in the system by either internal orders or WBS (work breakdown structure) elements. You can create an internal order that automatically includes an asset under construction. To do so, you need to enter an investment profile in the order master data.
n
In the construction phase, you post all business transactions to the order. During periodic settlement all debits that do not have to be capitalized are settled to a CO receiver, such as a cost center. All items that are not to be settled to receivers in Controlling and which require capitalization, are settled directly to the asset under construction. The monthly balance evaluations display the investment measure in the asset inventory.
n
Full settlement is made when the investment measure is complete. For complete or partial activation, you specify the final assets (which are to be used for settlement of the asset under construction) in the order settlement rules. The asset under construction is automatically credited.
n
The settlement side includes a procedure for line item settlement for this particular order type, in addition to the standard settlement methods for internal orders.
© SAP AG
AC415
2-10
$FFUXDO2UGHUV :DJH&RVWV
$FFUXHG YDFDWLRQ ERQXV RI ZDJHFRVWV
-DQ
)HE
0DU
$SU
0D\
-XQ
-XO
$XJ
6HS
2FW
1RY
$FFUXDORUGHU Period 01 02 03 04 05 06 ... 12
Accrualcostsand effectiveactualcosts
-1,200 +
∑
2UGHU &DWHJRU\
-1,200 -1,200 -1,200 -1,200 -1,200 -1,200
Balance:
'HF
9DFDWLRQ ERQXVSDLG
600
SAP AG 1999
n
Internal orders can be used for collecting monthly credits that result from the accrual calculation.
n
Organizational expenses are often allocated differently in Financial Accounting (FI) than in Controlling (CO). For example, an expense entered into FI in one accounting period may cover a whole year. In order to avoid cost fluctuations in Cost Center Accounting, irregularly occurring expenses should be allocated to the relevant time periods and cost centers. This even distribution of an irregular expense is termed accrued cost.
n
You can use the percentage method or the target=actual method to calculate accrued costs.
n
With the percentage method, you determine accrued costs using an overhead percentage rate that is applied to a reference cost element or group of cost elements.
n
In accrual calculation, the amounts of the accrued costs are debited to the cost centers. Simultaneously, an accrual object defined by you (cost center or internal order) is credited. The actual costs are also posted to the accrual object in order to calculate, analyze, and allocate any balances between expenses from FI and accrued costs from CO.
n
In the target=actual method you also can use an internal order for collecting the credits.
n
Accrual calculation requires order category 02 (accrual calculation order).
n
Both methods of accrual cost calculation are dealt with the in course AC410 - Cost Center Accounting course.
© SAP AG
AC415
2-11
,QWHUQDO2UGHUV 8QLW6XPPDU\2YHUYLHZ
5 +! 1 D;" 1
Y ZG [ a bbbbb Y^ _ `
8 +! " +# J1 1
f e i Z;
8VHU
8;$ " " !>( %'" & "81 9+ " (
f e i ZG _ Z'] \ c _ d[ e f g h[ c e _ f
2UGHU/D\RXWZLWK 0RGHO2UGHU
\]
ba b b
klm llonH;)$text /I0BJ&;0
=! Percent ">"? "" !","6? ""
@Type ; &0 DE)
Strategy Changeable Status %KL@5"6#>sequence " M/.,/'I/>N&0GOP20 QS RI&) T J
$XWRPDWLF DGGLWLRQ
Type Rcvr aPacbde5 aPacbde5
UV WYXZV\[ ]Z^YX_Z` _ _ Short text fhgji fhgji
Settlement type d k lkmon
SAP AG 1999
n Automatic generation of settlement rules is a new feature of Release 4.6. n Instead of settling each order after manually creating a settlement rule, you can now define a
settlement rule in Customizing. This rule automatically creates the settlement rule for each order at the time of the settlement.
n You have three options: You can either use the standard strategy sequence, create your own, or user-
exits.
n You can create an automatic settlement rule for each order type. n The advantage of this tool is that it saves the time you would normally spend maintaining settlement
rules manually.
© SAP AG
AC415
5-23
+LHUDUFKLFDO6HWWOHPHQW fp kqIsrGut1Zvk k w;xoy r o kzk{ w Costs... Settlement: 651000
20,000
z krG5 kIo tvk o w;x y r k s zk{ w I Costs... Settlement: 652000
t|vo k=}b moY~srGI y r okz {5 e5 651000 Repairs
20,000
652000 Maintenance: 20,000
&RVW&HQWHU
tvk s\}ks | o L*Yr y r k oz { 5I 651000 Repairs:
20,000
5HSDLUDQG 6HWWOHPHQW 0DLQWHQDQFH
40,000
t|vo o\} a:onGrB y r kkz {5
Ie5
fp kqIsrGut1Zvk k Ixoy r o kzk{ w Costs... Settlement: 651000
652000 Maintenance: 20,000
651000 Repairs: 20,000 20,000
SAP AG 1999
n You can settle from one order to another, and create information at different summarization levels.
Our example uses orders to collect costs for individual repair and maintenance activities. These are settled to the Turbine and Cooling orders to obtain summarized information on the repair and maintenance costs of these machines. After this, the "machine" orders are settled to a final order ("power plant") to display the total repair and maintenance costs for the location.
n You can process this group of independent orders using collective processing in the same settlement
run. To ensure that all the orders have been completely settled, you need to settle them in the correct order. For this purpose, the system determines the settlement hierarchy.
n The system automatically specifies the processing sequence (settlement hierarchy) based on the
settlement rules that you create for each order. It assigns a hierarchy number between 000 and 999 to the order. The orders are settled in descending order (highest to lowest hierarchy number), in other words: 000 is at the top of the hierarchy, and this order is settled last.
n If you enter settlement rules that do not lead to a complete settlement of your orders in one
settlement run, the system issues a corresponding message. In this case repeat settlement until all objects can be completely settled. You can also enter hierarchy numbers manually.
© SAP AG
AC415
5-24
6HWWOHPHQW $OWHUQDWLYH3RVWLQJ3HULRG &RVW&HQWHU
2UGHU %URDGFDVW 6SRUWV (YHQW
1RY
6HUY 0DLQW 6HUY 0DLQW
1RUPDO 6HWWOHPHQW
6HWWOHPHQW
2FWREHU
&RVW&HQWHU
&RUUHFWLRQ
6HWWOHPHQWV WR&RUUHFW
2UGHU 6SRUWV(Y &&WU 5HSDLU &&WU 6HUY 0DLQ
5HSDLU
1RYHPEHU
1RYHPEHU
SAP AG 1999
n
During order settlement you can enter a posting period that differs from the settlement period. This means that you can correct settlements from the prior period after it has been closed and locked and post the correction in the current period.
n
You enter the period to be corrected in the 6HWWOHPHQW3HULRG field. The posting period is the period in which the correction is posted. The posting period must be the period immediately after the correction period.
n
You must process the correction settlement prior to making settlements in the posting period. The system does not allow you to enter a posting period that has already been settled. If you specify that a correction settlement for the prior period is required after settlement in the posting period, you must reverse all the settlements made in the posting period first.
n
The settlement period and posting period must be made the same fiscal year.
n
You can use individual and collective processing for settlement corrections.
© SAP AG
AC415
5-25
3HULRG(QG&ORVLQJ
7RSLF
l 6FKHGXOH0DQDJHU8VH
SAP AG 1999
© SAP AG
AC415
5-26
6FKHGXOH0DQDJHU0RWLYDWLRQ 3HULRG(QG&ORVLQJ
l +DVDQXPEHURIVWHSVWKDWDUHSURFHVVHG IRUHDFKPRQWKHQGFORVLQJLQDVSHFLILF RUGHU
l ,VRIWHQSURFHVVHGE\GLIIHUHQWHPSOR\HHV ZKR $UHUHVSRQVLEOHIRUFHUWDLQIXQFWLRQVRU REMHFWVLQWKHHQWHUSULVH IRUH[DPSOHFRVW FHQWHUVRUSURGXFWLRQRUGHUV
$UHQRWLQWHUHVWHGLQWHFKQLFDOV\VWHP GHWDLOV
&RVW $FFRXQWDQW
'RQRWDOZD\VZDQWWRDVNWKH,7 GHSDUWPHQWIRUVXSSRUW
l 3HULRGHQGFORVLQJWDVNVDUHRQO\WKH PHDQVWRDQHQG
$FFRXQWDQW
SAP AG 1999
n Period-end closing must be processed quickly, simply and reliably. n Normally, the cost accountant is responsible for processing period-end closing n The cost accountant knows the functions that are to be used, and the objects that are to be processed n This person does not wish to deal with technical system details n Nor do they wish to make repeated calls to the IT department to ask for help n The Schedule Manager enables the cost accountant to structure, schedule, process and monitor
period-end closing as required.
© SAP AG
AC415
5-27
8VLQJ6FKHGXOH0DQDJHUIRU3HULRG(QG&ORVLQJ
&RVW $FFRXQWDQW 'HILQHV
VWHSVWREH SHUIRUPHG RQFHRQO\
8VHV'UDJ 'URS IRUVFKHGXOLQJ
SAP AG 1999
© SAP AG
AC415
5-28
6FKHGXOH0DQDJHU&RPSRQHQWV
6FKHGXOH0DQDJHU
7DVN/LVW
6FKHGXOHU
0RQLWRU
:RUNOLVW
SAP AG 1999
n
The four main components of the Schedule Manager are the task list, scheduler, monitor and worklist.
n
All remaining function elements belong to one of these four components.
© SAP AG
AC415
5-29
6FKHGXOH0DQDJHU2YHUYLHZ
6FKHGXOH0DQDJHU
1RWHVRQ8VH
7DVN/LVW
'DLO\2YHUYLHZ
1RWHVRQ8VH
mzsvur sqon um5 (*u kqsn urG| 5I rG voGBG
SAP AG 2000
SAP AG 1999
n
The Schedule Manager is the central initial screen for period-end closing.
n
The notes show you how to use the components of the Schedule Manager, and how to set them up.
n
In the task list, you define the single steps of the tasks, schedule them, and trigger task processing.
n
Daily and monthly overviews simplify orientation and display the periodic flows.
© SAP AG
AC415
5-30
'HILQLWLRQRID7DVN/LVW &UHDWHWDVNOLVW 7DVNOLVW
5XQVFKHGXOHKHDGHUV
7DVNOLVW+HDGHU •*HQHUDOFDOHQGDUVHWWLQJV CCC
•3URFHVVLQJWLPHIUDPH •&RQILJXUDWLRQRIGD\YLHZ
SAP AG 1999
n
The task list is the main organizational and administrative level in Schedule Manager.
n
It collects and manages all periodically-executed tasks in a clearly-arranged, graphical tree structure. This also enables you to schedule the tasks using Drag&Drop.
n
You define the desired calendar settings for subsequent task scheduling.
n
You also define the corresponding time frame for subsequent monitoring in the work lists. Note that if the time frame is overly long, then it can have a detrimental effect on performance.
n
You set the day view according to your preferences.
© SAP AG
AC415
5-31
7DVN/LVW
7DVNOLVWHOHPHQWV 5HSRUW %DWFKMRE 7UDQVDFWLRQ 1RWH )ORZGHILQLWLRQ
SAP AG 1999
n
The many order types and the flexible links between them enable you to portray and evaluate complex, period-end closing scenarios that are cross-application and tailored to your needs.
n
In combination with further "sub-" workflow definitions, the task type in the flow definition, based on the R/3 workflow, allows almost any nesting level.
n
The flow definition is composed of jobs, reports or other flow definitions.
© SAP AG
AC415
5-32
6FKHGXOH0DQDJHU6WUXFWXUH 7DVN/LVW
5I
6FKHGXOHU
Send mail
-XO\
Period-end closing starts Set period lock Accrual calculation CO Period-end closing FI Period-end closing CO
'DLO\RYHUYLHZ Time Description
'UDJ 'URS
Status User
8:00 Send mail
Bertha
8:15 Set period lock
Dora
8:30 Accrual calculation CO
Emil
9:45 Period-end closing FI
Kurt
11:30 Period-end closing FI
Max
SAP AG 1999
n
The task list is a central component of Schedule Manager.
n
It provides a structured overview of all period-end closing activities.
n
The task list contains the following task types: é Flow definitions: Complex processing chains that consist of many different processing steps.
é Report and jobs: Processing steps that you can define individually using variants, and can execute in the background. é Online transactions.
é Notes: These do not lead to processing in R/3. They often act as reminders for processing steps that you execute outside R/3. You can include office documents without any problems.
n
The day view provides a complete overview of the process and status of individual task elements. Depending on processing status, you can go to the Job Monitor and perform detailed error analysis.
© SAP AG
AC415
5-33
6FKHGXOH0DQDJHU )ORZ'HILQLWLRQ
3URFHVVLQJ)ORZ'HILQLWLRQV
)ORZ'HILQLWLRQ ,QWHUQDO2UGHUV Workflow started
Flow definition: Internal orders
Worklist selected
Description Period-end closing Internal orders Application
Calculate overheads
Cost collector Internal orders
Settlement
:LWKRXWZRUNOLVW
:LWKZRUNOLVW
"
Check worklist of internal orders Process worklist again Workflow ended
)ORZGHILQLWLRQ ZLWKZRUNIORZPHWKRG SAP AG 1999
n The flow definition consists of single flow steps, which include scheduling programs with variants in
the job control for the R/3 System, and user interaction whereby users are provided with information by mail.
n Application specific requirements of the interface for the flow definition can be realized using the
workflow profiles. If required, these profiles can be created and delivered using the project team. A report must exist to enable processing to be made available as flow steps. This report must provide all processing parameters and have an ergonomic interface.
© SAP AG
AC415
5-34
6FKHGXOH0DQDJHU )ORZ'HILQLWLRQ7HPSODWH 6WDQGDUG)ORZ'HILQLWLRQDVD7HPSODWHIRU8VHU'HILQHG)ORZ'HILQLWLRQ cG96/.,J|40Q Ê,"">"Ë!$Ì;Â Ð,";ÂG!6É
Î ¿7 09/.,J|40
