period-end closing activities 224 bpp en zh

SAP ECC 6.00

March 2008

English

Period End Closing Activities (224)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Procedure

SAP Best Practices Period End Closing Activities (224): BPP

Copyright

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 8


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 8


Contents

1 Purpose........................................................................................................................................ 5

2 Structure Period End Closing Process.........................................................................................5

3 Business Process Procedure for Period End Closing...................................................................6

4 Period End Closing Activities........................................................................................................7

4.1 Number................................................................................................................................. 7

4.2 Process Category.................................................................................................................. 7

4.3 Description............................................................................................................................ 7

4.4 Transaction............................................................................................................................ 7

4.5 Application............................................................................................................................. 7

4.6 Industry................................................................................................................................. 7

4.7 Reference Business Process Procedure...............................................................................7

4.8 Building Block ID...................................................................................................................8

4.9 Day/Month/Year.................................................................................................................... 8

4.10 SAP Menu.......................................................................................................................... 8

© SAP AG of 8


Period End Closing Activities

1 Purpose This building block provides the means and sequence of period end closing steps related to SAP Best Practices.

SAP Best Practices for Baseline covers all different kind of scenarios with a broad variable implementation approach. It is possible to select scenarios and implement different solution scopes. Therefore the period end closing can not be fixed to scenarios since it is not clear what scenarios will eventually be available.

The solution for SAP Best Practices provides a flexible method for period end closing on daily, monthly and yearly basis. It should be possible to select all required steps depending on the solution scope selected.

The purpose of this scenario documentation is to provide a method to help select these steps. Specific period end closing steps are not described here.

2 Structure Period End Closing ProcessPeriod end closing steps are closely related to scenarios and applications. Mostly the steps are performed in the FI and CO area, but there are also some steps covered by SD, MM, PP and other applications. Additionally steps are to be performed in a certain sequence so that it is not possible to cover all necessary steps in one application before starting with the next one.

SAP Best Practices for Baseline structures the period end closing in basically two sections.

Section 1:

The period end closing process steps are described in detail in specific business process procedures. These procedures are application oriented and contain all steps which are to be done in this regard. For example the business process procedure Period End Closing Financial Accounting describes all steps necessary to be performed in the FI area. These steps are described in a certain sequence determined by the application. Prerequisite steps of other applications are not included.

Section 2:

The business process procedures do not cover the correct sequence of all period end closing steps in one solution. Therefore an additional description is provided which contains all steps in a certain sequence. This sequence is determined by prerequisite steps required before proceeding with a next step.

The description is delivered as a list which contains all steps with a sequence number. To know how to perform this step is now described in the period end closing business process procedure (section 1). Therefore references to the business process procedures are included in the list as well. If the step is to be performed the step of the business process procedure should be selected and executed.

With this procedure it is possible to adopt the period end closing steps to the solution scope. If a business process procedure is not implemented the step should not be done. This means that this step is irrelevant and the next period end closing step can be performed.

© SAP AG of 8


Users executing period end closing should know the solution scope. Period end closing is closely related to the business content and can not be automatically executed without business knowledge.

3 Business Process Procedure for Period End Closing

Business process procedures for period end closing are provided within the baseline implementation. They are related to certain applications and delivered separately. Following you can find an overview of business process procedures which contain period end closing steps.

Business Process Procedure Title

Number (technical information only

Relevance Industry Implementation Recommendation

Period End Closing in Financial Accounting

159 All Foundation dependant

Asset Accounting 162 All Foundation dependant

Overhead Cost Controlling – Actual

184 All Foundation dependant

Closing Operations SD 203 All Foundation dependant

Internal Order R&D Actual

185 Manufacturing/Trade Foundation dependant

Internal Order for Marketing and Other Overhead Actual

186 Manufacturing/Trade Foundation dependant

Period End Closing Service Orders

189 Service Foundation dependant

Period End Closing Projects

207 Service Foundation dependant

Cost of Sales Accounting

161 All Optional

Online Split 165 All Optional

Foreign Trade Export Processing

118 Manufacturing/Trade Optional

Standard Cost Calculation


Period End Closing “General Plant”


Inventory Valuation for Year End Closing


© SAP AG of 8


4 Period End Closing ActivitiesRefer to Integrated_PeriodEnd_Closing_Activities.xls.

4.1 NumberThe number contains the sequence steps. All steps should be executed in the sequence as provided by the number.

4.2 Process CategoryAll steps in one sequence which belong to an application are structured into period end closing process categories. You can use the categories as additional information to find certain process steps or to decide to include new steps.

4.3 DescriptionThe description contains the process step. The same process step has to be selected in the assigned business process procedure and is to be executed.

4.4 TransactionThe transactions assigned to the process steps are listed.

4.5 ApplicationThe application areas are assigned.

FI = external financial accounting

CO = controlling

MM = material management (purchasing)

SD = sales and distribution

PP = production

FI-AA = asset management

4.6 IndustryThe step is assigned to the industry which is selected with the baseline installation. In some cases the process steps are industry independent and have to be executed for all industries

All: step is relevant for manufacturing/trade and service

Service: step is only relevant for the service industry

Manuf: step is only relevant for manufacturing/trade

4.7 Reference Business Process ProcedureHere you can find the business process procedure, which contains the detailed description of the period end closing step. The business process procedure contains a process step with the same text

© SAP AG of 8


as the description of the period end closing check list. This step should be executed in period end closing.

4.8 Building Block IDThis is the technical ID number of the business process procedure.

4.9 Day/Month/YearAll period end closing steps are assigned to the period for which they are to be performed. Closing steps can be done on daily basis, but also on monthly and yearly basis. The year end closing requires first the monthly closing of period 12 (December), so the year end closing includes also all steps of the monthly closing.

4.10 SAP MenuHere you can find the path of the transaction in the SAP ECC Menu.

This building block provides the means and sequence of period–end closing steps for period–end closing on a daily, monthly and yearly basis.

SAP Best Practices covers all different kinds of scenarios with a broad variable implementation approach. It should be possible to select all required steps depending on the selected solution scope.

Process FlowPeriod-end closing steps are closely related to scenarios and applications. SAP Best Practices for Baseline structures the period–end closing in two sections.

← Section 1: The period–end closing process steps are described in detail in specific business process procedures. These procedures are application oriented and contain all steps which are to be done in this regard.

← Section 2: The business process procedures do not cover the correct sequence of all period–end closing steps in one solution. Therefore an additional description is provided which contains all steps in a certain sequence. If the step is to be performed, the corresponding step of the business process procedure should be selected and executed.

Key Points← Business process procedures for period–end closing are provided within the SAP

Best Practices Baseline implementation. They are related to certain applications and delivered separately. The purpose of this scenario documentation is to provide a method to help select these steps.

© SAP AG of 8

period-end closing activities 224 bpp en zh

Documents