S4F16

S4F16
SAP Financial Closing cockpit in

SAP S/4HANA
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 17
Course Duration: 2 Day(s)
e-book Duration: 4 Hours 40 Minutes
Material Number: 50156834
SAP Copyrights, Trademarks and
Disclaimers
© 2021 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical errors or
inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any
reason without notice. The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking statements are subject to
various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
© Copyright. All rights reserved. iii

Typographic Conventions
American English is the standard used in this handbook.

The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control Example text
Window title Example text
© Copyright. All rights reserved. iv

Contents
vi Course Overview
1 Unit 1: SAP Financial Closing cockpit for SAP S/4HANA - Overview
2 Lesson: Presenting the SAP Financial Closing cockpit for SAP S/

4HANA
36 Unit 2: SAP S/4HANA Financial Closing cockpit for SAP S/4HANA

Solution in Detail
37 Lesson: Understanding Customizing Relevant for SAP S/4HANA

Financial Closing cockpit
52 Lesson: Performing Additional Functions
70 Unit 3: SAP Business Process Automation in SAP Financial Closing

cockpit
71 Lesson: Introducing SAP Business Process Automation by Redwood

and the Relation to SAP Financial Closing cockpit
84 Unit 4: Summary and Outlook
85 Lesson: Summarizing the Solution

93 Lesson: SAP S/4HANA Cloud for Advanced Financial Closing
111 Unit 5: Appendix
112 Lesson: Appendix FCc 2.0 (SAP ERP)

115 Lesson: Appendix SAP Business Process Automation (BPA)
126 Lesson: Appendix General
© Copyright. All rights reserved. v

Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
© Copyright. All rights reserved. vi

UNIT 1 SAP Financial Closing
cockpit for SAP S/
4HANA - Overview
Lesson 1
Presenting the SAP Financial Closing cockpit for SAP S/4HANA 2
UNIT OBJECTIVES
Describe the challenges of financial closing
Plan closing tasks
Create a task list for a closing cycle
Execute closing tasks
© Copyright. All rights reserved. 1

Unit 1
Lesson 1
Presenting the SAP Financial Closing cockpit
for SAP S/4HANA
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Plan closing tasks
Challenges of Financial Closing
Figure 1: Growing Pressure is Here to Stay
The world has changed with new pressures that are here to stay, such as the following:
Volatility in markets, commodity prices, and stocks
Increased focus on risk
Regulation that will not go away
Increasing globalization, requiring corporate management across diverse cultures
Continuing pressure on margins

Lesson: Presenting the SAP Financial Closing cockpit for SAP S/4HANA
Potentially disruptive technologies, some that will bring benefits, some that will change the
shape of the markets in which we compete
Figure 2: Greater Expectations from Finance
All of these issue impact the chief financial officer (CFO) and his or her team. As a result, the
CFO must balance sound stewardship and value creation, balancing entrepreneurship and
caution. The CFO must strike a balance between keeping track of the big picture, while
ensuring accuracy in the details. The balance requires the following:
Fulfilling the stewardship role by ensuring regulatory compliance and effective risk
management
The expectation to add value by helping the organization to outperform stakeholder's

financial expectations, generating more profit in the private sector or achieving more cost
effective outcomes in the public sector
Satisfying the requests from the organization for higher service quality at reduced cost
It is a struggle with to deal with increasing pressure. While there is nothing fundamentally
new, the stakes and challenges have increased significantly in past years.
Figure 3: Our Solutions for Finance
The SAP end-to-end processes for lines of business (LoB) finance maps to three business
challenges:

Unit 1: SAP Financial Closing cockpit for SAP S/4HANA - Overview
Ensure regulatory compliance and effective risk management

To meet these challenges, SAP provides treasury and financial risk management,
enterprise risk and compliance, and accounting and financial closing solutions.
Outperform financial objectives and create sustainable value

SAP provides a solution to manage financial performance.
Deliver superior service

SAP has solutions for the operations area of finance, Invoice to Pay, Receivables
Management, Travel Management, and Real Estate life-cycle management, typically
deployed in a shared services environment, and a Shared Services Framework for Finance,
which unifies the solutions with the collaboration and communication elements need to
make a shared service function work.
SAP Portfolio of Applications

Together, the SAP comprehensive portfolio of applications and end-to-end processes can
help you achieve financial excellence:
Strong cash flow and liquidity
Compliant and accurate financial reporting
Maximized profitability
Reduced cost of finance
Partnership with the organization to drive value creation
Figure 4: Financial Closing - The Reality
Financial close processes are increasingly more complex and period and year-end are often
chaotic times.

Figure 5: Accounting and Financial Close
The SAP S/4HANA Financial Closing cockpit is part of the SAP S/4HANA core delivery,
because this is where most of the end-users work. In larger enterprises, consolidation might
take place on separate software and by departments with specific consolidation tasks.
The SAP Financial Closing cockpit is an add-on to SAP NetWeaver and can be installed on any
other SAP NetWeaver stack, such as Solution Manager, CRM, SRM, or it can be stand-alone.
Therefore, in this course, we focus on the common case of local or entity close.
Figure 6: Challenges of the Financial Close Process
When you mix complex organizations, disparate systems, and poor coordination, you can
have serious delays in the reporting cycle. The basic goals for closing include:
Compliance
You must meet strict filing deadlines and conformance with financial reporting standards,
while ensuring the effectiveness of internal controls.

Transparency
You require accurate and auditable accounting transactions, centrally managed close
process, and more accurate financial reports.
Efficiency
You must streamline the close cycle, reduce errors, and execute it with greater
automation, fewer resources, and lower costs.
Figure 7: Financial Close Functionality in the SAP Business Suite
Common questions that have to be answered when defining and executing a closing process,
including the following:
Who will execute what, and at what time?
In what order do we need to execute the steps?
What is the current status of the task list?
Has the process started?
Is the process complete?
It is questions like these that the SAP S/4HANA Financial Closing cockpit is designed to
answer.

Figure 8: Entity Close Management without SAP Manual Orchestration
In the figure, you can see a customer example of month-end closing, organized with Microsoft
Excel.
Figure 9: Entity Close Management without SAP Facing Complexity
In summary, the individual financial close is a network of processes, brains, and resources,
and involves:
Network of Processes:
- Process disruption
- Manual handover
- Lots of interfaces

Network of Brains:
- Transactional activities
- Spread over regions and countries
- E-mail- and phone-driven communication
Network of Resources:
- ERP and non-ERP
- SAP and non-SAP
Figure 10: SAP S/4HANA Financial Closing cockpit
The aim is to establish the SAP S/4HANA Financial Closing cockpit as a common, uniform
starting point for complete entity close management.

Closing Task Planning
Figure 11: Define the Game Plan for the Financial Close
The template contains all default tasks related to the local close and a relative default
schedule. Based on the milestones defined for the global close, the template defines the
detailed schedule of the local close. Templates can either be defined in the development
system or the production system.
In transaction FCCGC , you can set a flag Maintain Template in Each Client , which allows you to
maintain a template directly in the production system.
Setting Up a Closing Template - What to Consider

The following are the main points to consider when defining templates:
Task types (manual, transactions, job, workflows, web application…)
Closing types (monthly, quarterly, …)
Organizational units
Time Variables
Dependencies
Responsible users and processors
Factory calendars
Workflows and Worklists
Custom-specific closing programs
Additional automation and tasks in a remote system

Figure 12: Types of Closing Tasks
There are different types of tasks, including the following:
Notes (manual steps)
Transactions
Programs with or without variant
Jobs (program and variant)
Flow Definition
Web Application
BAE (former SAP CPS)
External Job
Remote tasks

Figure 13: Task Details
For each task, you define a few extra settings for planning to work:
Offset in days
Planned start time
Planned duration
Indicator, if on critical path
You can use the Additional Fields button to include custom fields. To do this, add your custom
fields, in the CI_CLOCOAF_INSTinclude of the FCC_INST_ITEMor FCC_TEMPL_ITEMtable.

Figure 14: Assignment of Organizational Units to Closing Tasks
Folders can be used to group tasks in the template by organizational unit. For example, if you
want to perform the same closing tasks for multiple company codes, you group them in one
folder of type company code. Then, you select the individual company codes using the change
characteristic values button and selecting the valid entries. The values with the green plus are
those that are assigned to the folder.
The folders can be for controlling area, company code, or plant.
To limit the access to users, these values can be checked by the SAP Financial Closing cockpit
organizational authorizations. The values can also be used in report variants by using the
SAP_FAST_CLOSE*selection variables in your report variants. This allows you to maintain a
single variant, instead of a separate one per company code.
Figure 15: Available Closing Hierarchies
The following closing hierarchies are available while creating a new template:

1 - Company Code
2 - Controlling Area / Company Code
3 — W/o Hierarchy
4 - Controlling Area
5 - Controlling Area / Plant
6 - Plant
7 - Company Code / Plant
8 - Controlling Area / Company Code / Plant
Further hierarchies than the above cannot be defined. The most flexible hierarchy is 8 -
Controlling Area / Company Code / Plant . This allows you to select any level that you require,
you do not need to use them all. Once a template is created, you can no longer change the
closing hierarchy.
Figure 16: Assignment of Organizational Units to Closing Tasks — Plants
In most cases, closing is a company code level process, because the company code is the
fundamental business entity responsible for financial reporting. However, for some closing
processes, such as the settlement of production orders, it might make sense to include the
plant as a closing entity.

Figure 17: Closing Hierarchy and Close Types
A template contains a list of tasks in a hierarchy of folders. All tasks in the template are
classified by close types. A single template can hold all closing tasks.
A task list is always created for a single close type, for example period-end closing May 2020.
Other tasks, which are only relevant for year-end closing, will not show up in the period-close
task list.
The month-end closing, quarter end closing, and year end closing check-marks indicate
whether the tasks are copied into the task list when it is generated. For example, you carry out
the depreciation run monthly, so you would select all three check-marks. On the other hand,
the balance carry forward is performed once a year, in the last fiscal period, therefore, you
only mark it for year-end closing. The task list for the final fiscal period corresponds to the
Termination Y = year end closing, so both the depreciation run and the balance carried
forward will be copied as a task in the task list.
The hierarchy and the setup of the folders are flexible to allow you to structure the closing
activity presentation.

Figure 18: Tasks and Responsibilities
Each task in the template is assigned to a role, a responsible user, and a processor. You
maintain the role, the processor, and the responsible person under the task details.
All users entered must be SAP users with authorization to use transaction FCLOCOand the
respective tasks they are to perform. You can also define responsibility on the folder level.

Figure 19: Factory Calendars
Each task includes a default offset, with respect to the key date of the close, and a default
runtime. Additionally, a planned start time and duration must be maintained. If tasks are to be
scheduled only on work days, each template can include a link to the factory calendar. You
can maintain multiple factory calendars in one template, at folder level a different factory
calendar can be assigned.
If required, you can maintain the delivered factory calendar with transactions OY05 or SCAL.
You can maintain multiple factory calendars in one template, for example, to serve the
requirements of different subsidiaries.
Caution:
With the transport of a factory calendar, all factory calendars that are available in
the system are transported. See the message while saving a factory calendar.
With the offset-days, you define how many days before the key date (negative offset), or
number of days after the key date (positive offset), the task should be scheduled. If the task is
relevant for the key date, the offset is zero.
The system calculates the reference date based on the key date as follows:
If no factory calendar is used, the reference date equals the key date.
If a factory calendar is used and the key date is a working day, it equals the reference day
equals the key date.

If a factory calendar is used and the key date is NOT a working day, the system uses the
first working day following after the key date as reference date.
For example, January 31, 2021 is a Sunday. This is the key date of your task list and it is a non-
working day. The factory calendar moves the tasks of day zero (31st of January) to next
working day, February 1st, 2021.
Figure 20: Time Variables for Efficient Re-Use
When you create a task list, parameters (type P) and selection variables (type S) will be
entered in the header of the task list based on the key date for the close.
For time parameters in the variants, you set the selection variable T, to ensure that the
parameters will be pulled from the task list header and written to the variant when the task is
scheduled (the values are read via the TVARC table).
Scheduling a job automatically generates a new variant for each task that contains the
appropriate time variables (and organizational units).
The SAP S/4HANA Financial Closing cockpit offers various selection variables that are
automatically filled from the task list. They are named SAP_FAST_CLOSE*and can be found
in the TVARC table or report variants. If you already have your own additional variables, or
need more in the future, you can create them in the TVARC table using transaction STVARV
and by adjusting the stored values. In regularly changing variables, such as period or fiscal
year, it is appropriate to adjust the variables using a small auxiliary program, depending on
the system date. The utility is to scheduled just once per day.

Figure 21: Task Dependencies
Set the Critical Path flag to identify key tasks in the template. You define dependencies by
working backwards from the balance sheet, through all tasks that lead to a complete balance
sheet. Dependencies can be created within a task group. This is inherited later in the
template. In the template, you can define dependencies between tasks and tasks of task
groups. The system checks whether the function order can be executed using the predefined
scheduled start time and planned duration, if not, an error message is issued.
Figure 22: Dependencies between Tasks

While creating a dependency, you drag and drop the tasks and the SAP S/4HANA Financial
Closing cockpit application checks whether the planned start time and duration are
compatible with each other. In this way, no dependencies can be created where the successor
would start before the successor task.
There can be a 1:1, a 1:N, or an N:M dependency with successors as well as with predecessors.
Figure 23: Tasks and Responsibilities
Each object in the template is associated with a person responsible and a processor. The
person responsible and processor are the ones who receive e-mail notifications
All end users need to have the permission for transaction code FCLOCO
. Authorization groups
can further limit the possibilities.
The SAP modules Finance, Controlling, Asset Accounting, and so on, or departments of the
company could be considered as a user or authorization group. User groups can be created in
Customizing. In the transaction, FUSRGR, you assign users to a user group.
SAP HR (HCM) organizational objects, such as job or org. unit and position can also be used, if
available at the system where the SAP S/4HANA Financial Closing cockpit is installed.

Figure 24: Including Instructions in the Template
You can include all types of documents as Instructions or job aids in your template.
Figure 25: Custom-Specific Closing Programs
A task can only send status information to the SAP S/4HANA Financial Closing cockpit if the
underlying program is "attached" to the cockpit.
Around 800 SAP close programs are already attached. However, if you want to include your
own programs in the template, consult SAP Note 1609030, which has instructions that show
how to enhance your closing program and how to list it in the SCMAPROGRAMStable.
In transaction FCCGC(General Customizing), you can set the Integrate Technical Status
indicator, which allows you to get the job status, which you can see in transaction SM37.

Figure 26: Scheduling Tasks in a Remote System via ext. Scheduler
Business Automation Enabler (BAE) is an interface between the SAP Financial Closing cockpit
and external scheduling tools, such as the Central Process Scheduling by Redwood or other
schedulers for scheduling jobs and job chains and integrating of business and infrastructure
events. The interface is released for all external schedulers that have passed either the SMSE
or the BAE certification procedure.
You can also set up more complex automation job definition with automatic bug fixing.
Usually, the scheduling capabilities of the financial closing cockpit are sufficient.
You install SAP BPA on the SAP NetWeaver Stack and create queues for each remote system.
SAP BPA will schedule the remote task on the other system via RFC. As each remote task is
scheduled, the financial closing cockpit calls SAP BPA via a standard API.
Note:
Up to version 8, the product is named SAP Central Processing (SAP CPS) by
Redwood. Starting from version 9, this product is named SAP Business Process
Automation (SAP BPA) by Redwood.

Figure 27: Scheduling Tasks in a Remote System Setting Up Job Definitions
SAP Business Process Automation includes job definitions designed to run with the financial
closing cockpit. The details of the parameters needed to run the job are entered in the
template in SAP S/4HANA.
Additional parameters are maintainable in the financial closing cockpit for SAP BPA tasks.
They are defined in the job definition at SAP BPA.
Closing Cycle Task List
Figure 28: Task List Contains All Tasks of a Concrete Close Cycle

The task list contains all tasks related to a concrete close cycle as well as the time-schedule
for the tasks. The task list is generated from the template and adjusted according to the
closing cycle of the subsidiary.
Note:
The generation of task lists can be organized under corporate responsibility to
ensure a harmonized closing process across subsidiaries.
Figure 29: Creation of a Task List
The source of monthly task list is always a template. You must make all changes to a template
before creating new task lists.
Caution:
The template is always the source from which a task list is generated for a
specific month end closing. Subsequent changes to the template will not affect
task lists that have already been created.

Figure 30: Creating a Task List
The task list header contains the key date (in the figure, this is 01.09.2019), the closing type
(M for monthly, Q for quarterly, and Y for yearly), and time variables for use in the individual
close tasks
Figure 31: Creating Multiple Task Lists
Two reports exist for creating task lists: FCC_CREATE_TASKLISTand

FCC_CREATE_TASKLISTS.
These reports enable the creation of the task list based on various input parameters, as seen
in the figure, Creating Multiple Task Lists. Basic parameters include the option to set the
status of the task list and to schedule all tasks of the task list.

Figure 32: Changing a Task List
For an individual close, you might need to make changes, such as to change the processor or
make minor adjustments to the schedule. You might also want to add notes or documents
specific to that particular close.
As you create the task list, the default schedule is assigned to "actual" start and end times.
Until the tasks are scheduled, you can make changes by right-clicking the task.
Figure 33: Adding Documentation to the Task List
If you open the task list in change mode, you can add supporting documentation to the task
list. To update an existing document, click the document icon, make your changes, and save.
Your document changes will be loaded to the task list.
To add a new document, right-click the Document column and choose Import Office
Document or Create Office Document .

Note:
The currently supported document types are displayed in the figure, Adding
Documentation to the Task List. Support for additional types are planned.
Figure 34: Filtering the Task List
Typical global business companies complete more than 150-300 closing tasks per company
code in a local close cycle. This makes quick identification and batch update processing for
maintenance objects crucial.
Figure 35: Mass Change in the Task List
The figure, Mass Change in the Task List, shows the options for making mass changes to the
task list.

Figure 36: Separate Authorizations for Template and Task List
With the transaction FCLOCOT , users can only create a task list or task lists based on an
existing closing template. Users cannot create or manipulate the closing template, or execute
the closing tasks through this transaction code.
Figure 37: Pre-Set Template or Task List and Selection Maintenance
You can set a template or a task list as default, so that it opens automatically when you start
the FCLOCOC(FCLOCO , FCLOCOT ) transaction. You can save the current state of the task tree
and the list of tasks selected in the details view. The saved state is restored when this user
opens the same template or task list.
The template or task list can be set as default using a menu item or by setting the
corresponding user parameter, CLOCO_TASKLIST.

Figure 38: Change Documents for All Task Changes During Execution
The SAP S/4HANA Financial Closing cockpit tracks changes in:
Tasks (status, notes, or documents attached, messages sent, locks)
Templates
Task lists
Figure 39: Factory Calendar
Without a factory calendar, the date of execution will not change. Tasks will be planned on
non-working days, such as weekends or public holidays. You maintain the factory calendar to
define public holidays or other non-working days with transaction code OY05 or SCAL.
The factory calendar can offset tasks to the next working day, however keep in mind some
limitations:
Bridge days are possible, something common in countries like Germany.
People can have various extra or priority tasks to execute at certain points.
The goal is to provide as good as possible plan for the task execution, taking known or
predictable factors into consideration. This will require at least a minimum adjustment after a

task list has been created. Additional custom or BAdI implementation can be used to improve
the results.
On the template header, you can define a common group factory calendar, which is assigned,
by default, to all company codes. In addition, you can assign a separate factory calendar on
the folder level, for example on company code specific folders.
Caution:
When you change and save a factory calendar in the development system, ALL
factory calendars are transported together.
Closing Task Execution
Figure 40: Execution and Documentation of the Close
The task list provides status information on each task and links to all system documentation
(job logs, spool lists, application logs) and user-created documentation (supporting
spreadsheets and word documents).
It can be accessed and processed by all stakeholders, either using SAP GUI or an SAP Fiori
launchpad or Web application.

Figure 41: Task List in Hierarchical View
To select further details for each task, double-click the line for the task in the Hierarchy View.
Figure 42: Navigation and Filtering in the Task List
The figure, Navigation and Filtering in the Task List, shows additional navigation and display
options.

Figure 43: Execution and Scheduling Tasks
To start one or more tasks, select the tasks and choose the action.
The job will be scheduled at the time calculated by the system, with the dependencies
between jobs taken into account.
When the job is complete, the status information is updated and any logs specified will be
added to the task list for analysis by the task owner.
Figure 44: Task Details - Documentation of the Close

The SAP Financial Closing cockpit saves all start time, duration, and end time of task
executions. The financial closing cockpit keeps a link to log files and spool lists, which can be
copied into the cockpit. At the same time, they are converted into PDF files. The prerequisite
is that, at the header data of the task list, the Copy Protocol option is selected.
The system updates all links to the log files, as well as the message lists created during
execution (Task-Related Files).
When you change the task list status to complete, or once a day, the spools and logs are
converted into PDF files. This means that, for a while (usually 6 - 8 days), you can choose
between online display or display of the copy.
The system updates the start and end time and the duration of each automatically executed
task (General Data).
You can also enter own comments, attach documents, and send e-mails.
Figure 45: Multiple Documents per Task
The system also keeps the record of who made the last change and when it was made.
You can assign multiple documents to a single task. The following document types are
supported:
Office documents
PDF documents
Text files
URL links

Figure 46: Status Change for Manual Tasks
When you click the Set Status For button for manual closing tasks, the system offers a
dialogue box for you to choose status and input status change reason.
The system records all the historical status change records, including status change date and
time, users, changes in status, and status change reasons.
Figure 47: Workflow Monitoring
The SAP S/4HANA Financial Closing cockpit provides extended visibility and processing
capabilities for workflows and worklists

Figure 48: Monitoring of Remote Tasks
You can schedule Remote Tasks within the SAP S/4HANA Financial Closing cockpit. The Job
IDs from SAP Business Process Automation by Redwood (SAP BPA) appear as Remote Tasks
in the financial closing cockpit. All logs for remote tasks are available using the financial
cockpit.
Figure 49: More Detail for Remote Tasks
The integration with SAP BPA allows users to schedule tasks in multiple systems. End users
working in the financial closing cockpit have access to all relevant data about the remote task
in SAP BPA.
Once initiated, you will find information, such as the status, about execution in SAP BPA, on
the Remote Task Data tab page.

LESSON SUMMARY
You should now be able to:
Plan closing tasks

UNIT 2 SAP S/4HANA Financial
Closing cockpit for SAP
S/4HANA Solution in
Detail
Lesson 1
Understanding Customizing Relevant for SAP S/4HANA Financial Closing cockpit 37
Lesson 2
Performing Additional Functions 52
UNIT OBJECTIVES
Configuring the SAP S/4HANA Financial Closing cockpit
Manage templates, task groups, and the task Global ID
Understand the Authorization concept
Manage Customer Variables, Fields, and Internal Controls
Perform additional functions
Manage mail notifications
Execute remote tasks
Manage external jobs
Use Smart Business apps

Unit 2
Lesson 1
Understanding Customizing Relevant for SAP
S/4HANA Financial Closing cockpit
LESSON OBJECTIVES
Customizing Tasks for SAP Financial Closing cockpit
Figure 50: Customizing for SAP Financial Closing Cockpit
Most of the SAP S/4HANA Financial Closing cockpit customizing is available using the menu
of transaction code FCLOCOC , but the BAdIs are only listed in the Implementation Guide
(IMG). To reach the IMG, choose the SPRO Cross-Application Components SAP S/
4HANA Financial Closing cockpit .
Note:
The reason that the financial closing cockpit customizing is under Cross-
Application Components is that the cockpit was an add-on to SAP NetWeaver, and
this node is available in all SAP systems.

Unit 2: SAP S/4HANA Financial Closing cockpit for SAP S/4HANA Solution in Detail
Figure 51: General Customizing for SAP Financial Closing Cockpit
In General Customizing , you define basic settings for the financial closing cockpit, and the
settings are kept clear.
The authorization checks on task or organizational unit level must be activated separately.
In the Background Job Monitor , the interval of 5 min. for the first job is fixed. You define the
time interval for the other jobs here. For test systems, set an interval of 1 minute so that you
do not have to wait to test. In productive operation, intervals of 10 to 15 minutes should be
used.
Figure 52: Background Job Monitor
The background job monitor lists all utility programs that are needed for a proper task list
execution. You can also find the relevant documentation for each job. It provides a better
insight for running background jobs. These are critical to the operation and functioning of the
financial closing cockpit, for example, e-mail notifications, remote job or workflow, external
jobs, and so on.

Lesson: Understanding Customizing Relevant for SAP S/4HANA Financial Closing cockpit
Not all programs need to run, for example, FCC_RJ_BACKGROUPD_JOBis only needed in the
case of usage of remote jobs.
The interval of 5 Min. at the first job is fixed. The interval of the others are maintained in the
General Customizing of the financial closing cockpit.
Figure 53: Change Documents
With the Change Document Monitor , you can view changes to templates and task lists. The
change document monitor displays changes to the basic data of the templates and task lists
and the field values of the folders and objects in the templates and task lists.
You can see the values before and after a change, who made the change, when the change
was made and some further information.
Templates, Task Groups, and the Task Global ID
Figure 54: Download and Upload of Templates

The benefits of the upload and download template functionality include the following:
Accelerated template creation
Reduced effort for mass changing in one template
Help to import from unconnected system (third parties, spread sheet, legacy systems)
Reduced template lock time, back-up, and more
Define:
A special template, which contains a group of tasks.
Support inner structure with normal folder.
Does not contain org unit information.
No mutual assignment between task groups.
Assign:
One task can be assigned in each folder in one/multiple templates.
One task group can be assigned multiple times in one template.
In the assigned folder, task group should not be duplicated.
In template, local task can't be inserted into task group.
No mutual assignment between task groups.
Update:
Task group change (AUD) can be updated to assigned folders.
Update fields configured determine which fields will be compared, updated, or controlled.
Update supports pull and push
Difference between task group and assigned folder can be compared.
Report:
Provide cross templates or assigned folders reporting based on task group.

Figure 55: Task Groups
Task groups are a set of structured folders and tasks can be used across templates. They can
also be used multiple times within the same template.
You use task groups for:
Cross template maintenance or mass change
To cover multiple companies with the same or similar tasks
Increased efficiency
Global or local control

Figure 56: Global ID and Organization Unit Monitor
To help you to display task status across multiple Organizational Units, you can assign a
Global ID to link tasks from different Org Units.
It also helps you to create dependencies by inserting tasks in predecessor or successor
positions.
Figure 57: Global ID - Define and Assign to Tasks
With global IDs, you achieve a better view for the dependency display:
1. Dependency summary is listed in task overview.

2. Action column is displayed to hint next step.
3. Predecessors and successors chain are displayed in dependency tab.
Authorization Concept
Figure 58: Extended Authorization Concept
The SAP Financial Closing cockpit offers authorization control at all levels. Authorization for
SAP GUI and the Web UI interfaces are harmonized.
Figure 59: Authorization Assigned in User Profile
The following roles are delivered with the SAP Financial Closing cockpit:
SAP_FCC_ADMIN
Authorization for Template Administrator for the financial closing cockpit
SAP_FCC_ALL

Test role for the financial closing cockpit add-on
SAP_FCC_AUDITOR
Authorization for Auditor for the financial closing cockpit
SAP_FCC_MANAGER
Authorization for Closing Manager for the financial closing cockpit
SAP_FCC_MENU
Authorization for NWBC Access for the financial closing cockpit
SAP_FCC_PROCESSOR
Authorization for Task Processor for the financial closing cockpit
The roles contain all authorization objects used by SAP Financial Closing cockpit. In your
implementation, you might not need all of them. It depends on the functionalities that you are
using, and what has already added to other roles.
The authorization objects belong to different areas, for example:
Schedule Manager
Basis
SAP HR
SAP FCC
Hint:
The arrows in the figure point to the prerequisite activity in the upper level.
Figure 60: Integration to HR-ORG
If multiple users take charge of template, task, or the Processing or Responsible folders, it can
be difficult to update the folders if there is a change.
To make this easier, we can extend access Processing or Responsible folders to the following:
Organization unit

Position(/nppocw)
Job
User
Role
Customized user group
List users for extended organization
Demo
Assign position 'CO Accounting' for task 'General Adjustment Postings '
Change processor of task 'Period Lock for Customer/Vendor'
Figure 61: Example Authorization Role for SAP Financial Closing Cockpit
In the figure, you can see that you can maintain permissions for various fields. Many of these
will already be contained in existing roles and assigned to employees. The sample roles
represent the dull detail that may be needed. Furthermore, it also depends on the used
functions of the financial closing cockpit.

Figure 62: Authorization Definition at Template / Task List
Authorization groups can be used to restrict access either at task level or on the template.
Example 1 — Template Level
Each region has a template that is maintained by different employees. To prevent wrong
entries an authorization group is maintained at the template header. The authorization group
is added to an authorization role. The relevant employees always get just one of these roles so
they can maintain the templates independent of each other.
Example 2 — Task Level
You are responsible for asset accounting, all tasks of asset accounting can have authorization
group ASSETS assigned. Then with the authorization group ASSETS you can display &
change the task and tasks status. For all other tasks of your template you would have only
display authorization.
All other authorization which are already existing and used in daily business will not change
from implementing SAP FCc.

Figure 63: Integration of HR-ORG-Models
Individual users or user groups might be responsible for the execution of a task. The setting
might be different for the managers and performers. In the event of a roll-call commitment to
an SAP user, the template has to be adapted with each change.
Advanced manager or performers in the form of groups:
Organizational unit
Location
Post
Authorization role
Custom user groups
For mass changes, there are various solutions:
Microsoft Excel Upload and Download
Mass changes in the template via the context menu (right-click in the ALV layout)
Mass changes in the task list

Customer Variables, Fields, and Internal Controls
Figure 64: Custom-Defined Variables (1/2)
Custom variables can be easily defined in the SAP Financial Closing cockpit. These are used in
programs the same way as other variables defined in transaction STVARV. By creating custom
variables, you can reduce the number of variants significantly.
Figure 65: Custom-Defined Variables (2/2)
When the task is executed, the value of a certain field in the programs that use this variable is
replaced automatically.

Figure 66: Customer-Specific Fields
Customers can define own fields using any of the three includes that are provided:
CI_CLOCOAF_TEMPLfor fields used at template
CI_CLOCOAF_INSTfor fields used at task list
CI_ADD_DISP_FIELDSfor calculated fields, which are used at task details
Custom fields can also be changed through a mass change process.
Note:
This functionality is available in the SAP GUI and Web UI.

Figure 67: Internal Controls
New task properties with pre-defined and customer-extensible values:
Significance (key control, normal control)
Automation (automated, semi-automated, manual)
Purpose (detective, preventive, corrective)
These properties can be set per task in the template to differentiate internal controls from
‘normal’ tasks. They are available in execution and reporting.
Figure 68: Example - Internal Control System SAP FCC
In customizing, you can define any value that can then be added as additional criteria to tasks.
LESSON SUMMARY


Unit 2
Lesson 2
Performing Additional Functions
LESSON OBJECTIVES
Additional Functions
Figure 69: Time Zone Support
You can set a specific time-zone for each task.

Lesson: Performing Additional Functions
Figure 70: Time Zone Support on Task Level
The grayed out line represents the system time zone. The first line is the local time zone of the
respective task. Here is the local scheduled start time and time zone of the object to maintain.
When saving it is converted into the System time zone.
Figure 71: Creation of a Task List
In the task list header, you enter a key date (31.12.2017) and close type (M = monthly) and
also time dependent SAP_FAST_CLOSE variables.

Figure 72: Creation of More Than One Task List
You can generate multiple task lists at once.
Caution:
Changes to the template do not have any impact on tasks lists that have already
been created.
Figure 73: Manual Send and Save of Additional Mails
You can send (and save) additional mail messages for each task.

Mail Notifications
Figure 74: Built-In Notification Scenarios
Figure 75: Notification on Task List Execution Status
The figure, Notification on Task List Execution Status, shows the steps to configure and use
mail notifications.

Figure 76: Example of Notification - SAP Financial Closing Cockpit
The figure shows an example notification.
Figure 77: Storage of Spool List and Job Log
For Job Log or Spool Log, the history execution logs are stored automatically, so that, even if
the logs are archived through SM37, these logs can still be accessed as a PDF file.
The log links are displayed in detailed format with Run times, ID, and Time. You can activate
this feature with the Copy Logs checkbox on the template basic data screen.
SAP Financial Closing cockpit can copy the spool lists and job logs into the financial closing
cockpit tables. The spool lists and job logs will be converted into PDF files. Using transaction
code FCCGC(General Customizing), you can define an alternative storage place for the
generated PDF files, for example, an optical archive.

Figure 78: Task Export Possibilities
You can export you task list to Microsoft Excel on the Utilities menu tab.
Figure 79: Enhancements in Web UI
You can refresh the status directly from the transaction.

Figure 80: Guideline for Integrating Custom Programs
SAP note 1609030 should be added to your development guideline. It provides better support
for including custom programs.
It contains detailed steps, sample code, and the sample program,
FCC_SAMPLE_CUSTOMER_REPORT.
The requirement is that new customer programs, which are relevant for periodic closing,
should be connected to SAP Financial Closing cockpit. This connection makes a later
implementation of the financial closing cockpit easier.
You can change existing programs later, if needed. For example, if a program has a bug, but
you can live with a workaround, it saves implementation and test effort for now. Examples
include:
1. The program does not provide adequate status (status unknown) to the financial closing
cockpit, and this is sufficient.
2. The program is not connected to the financial closing cockpit and you use the transaction
code FCCGCto flag Technical status , then you get what you can see in the SM37. Running,
green or red. Possible error messages in the protocol of the respective program are not
considered.
3. The program is not connected to the financial closing cockpit, but you need a precise
status. Then, SAP Note 1609030 should be included in the relevant program. ( 1609030
contains an example FUBA, but you could also look in the report FCC_TEST_REPORT.)
This can be used to set the status in the financial closing cockpit.
Note:
It could be that further adaptations to the respective z-program are
necessary messages must be written to the application log if the program
does not do it today.
4. Program SCMABOX ( SAP Note 551743) delivers a utility program, which starts the real
program. This could be a workaround for your situation.

5. The financial closing cockpit should be connected to external scheduler in the future.
Then, you don't need to adopt you coding, as the status will be set by the external
scheduler directly into the cockpit.
Check whether your coding needs optimization regarding:
Performance
Functionality, for example, additional error messages
Change to direct postings instead of BI file creation
Figure 81: Transparency while Executing Tasks
Create dependency by inserting a task as a predecessor or successor.
1. Dependency summary is listed in task overview.
2. Action column is displayed to provide a hint for the next step.
3. Predecessor and successor chains are displayed on the Dependencies tab.

Figure 82: Notes and Mails for a Task
The figure shows the notes and mails for a task.
Remote Tasks
Figure 83: Online Execution of Remote Tasks
Remote tasks allow you to connect with a simple trusted Remote Function Call (RFC)
connection to other SAP systems to execute transaction codes, programs, jobs, or flow
definitions. In the SAP Financial Closing cockpit (SAP FCc), you see the correct status of the
remote task.
The challenges that need to be overcome in the execution of remote tasks include the
following:

Connection to remote accounting system directly from the financial closing cockpit
Single log on required, with need to logon separately
Support for lower releases of remote system, for example, SAP ERP Enterprise, and so on
The solution to these challenges include:
New task types introduced in SAP Financial Closing cockpit
Execution of transactions and programs online in remote systems from the cockpit
Figure 84: Batch Execution of Remote Task
The program, variant, and user are checked against the target systems. Once the job or
remote workflow has been executed, the results, such as spool list and job log are retrieved by
SAP FCc and attached to the task in the cockpit.
Note:
This can only be set up with ABAP programs.

Figure 85: Remote Tasks - Execution Online or at Batch
Remote tasks can be executed directly by an RFC call in the financial closing cockpit to
another in an SAP S/4HANA, SAP ERP, or SAP NetWeaver system.
No separate logon is required; a trusted RFC connection can be used.
Figure 86: Remote Workflow
The flow definitions (also called workflow) can be used both in the clients in which the
financial closing cockpit is installed, or in remote systems, for example, other SAP S-4HANA,
or SAP ERP systems that are connected. Then, we talk about remote flow definitions. The
specification of a remote system in the task is required.
Execution of remote flow definitions
Collection status of flow definition at remote system
Collection of job log, spool for each step of flow definition

Status history for task
External Jobs
Figure 87: Architecture
The SAP Financial Closing cockpit (SAP FCc) is integrated with the SAP Business Process
Automation application by Redwood (BPA). End users can create SAP BAE tasks in the
financial closing cockpit.
Customers also use other schedulers, such as BM TWS, Control-M, and UC4. It is difficult to
connect them to financial closing cockpit and to retrieve the results in the financial closing
cockpit. External schedulers and the financial closing cockpit run their own time schedules,
independently of each other.
To overcome this difficulty, SAP FCc has an External job task type.
The financial closing cockpit checks jobs (use transaction code SM37) to check whether an
external scheduler (for example, SAP ERP) has scheduled jobs items, and monitors the
externally scheduled job. SAP FCc retrieves the result of the job automatically. There is no
need to extend or modify external schedulers.
Figure 88: Architecture for Automic (UC4) Customers

Automic, with their product UC4, claims that they have got a simpler way of orchestration of
scheduling of closing tasks.
Customer own programs, which are relevant for closing different options for Automic or other
schedulers.
1. The program is scheduled over external scheduler, then SAP FCc may already searching
only the results of the program in the SM37 and deliver back to the SAP FCc. SAP FCc and
Scheduler operate independently of each other.
2. The program is scheduled over SAP FCC and passed to UC4 V10 + Web Service. The new
interface of UC4 transfers the status directly to the FCC. A Job Log can be collected with a
second job spool list from the SM37 (this is no longer needed; see SAP Note 2391918 -
BAE Interface).
3. In case 1 and 2, changes are not required to Z-coding. SAP Note 1609030 will not be
needed here.
4. Use the renamed task type Business Automation Enabler, see SAP Note 2391918.
Figure 89: External Scheduler - Runtime Match
As of SAP Note 2391918, this task type is no longer required. You can use it, but there will be a
time delay and the status information is not as precise as it could be with the Business
Automation Enabler task type.
Note:
If several jobs fulfill the search criteria, all runs are displayed as task details on the
Output Logs tab.

Figure 90: Monitoring the Entity Close
The status and progress of the entity close can be displayed as SAP NetWeaver BW queries
that provide real-time access to the close figures.
This enables corporate managers and managers of the subsidiaries to monitor the status of
the closing process on their levels of responsibilities.
Figure 91: Analyzing and Continually Improving the Entity Close
The duration of the tasks in a single close can be compared with the planned duration using
an SAP BW query.
This enables the user to improve the template based on clear insights for the next closing
cycle.

Figure 92: Monitoring Task Groups
Within SAP FCc, you can use the Global ID monitor (based on Global IDs), as shown above the
Cross Template Monitor. The Cross Template Monitor provides insights for a single task
group for each task of a task group for the company codes which are using this task group.
External Job Reporting
Figure 93: BI Reporting - Closing Schedule Analysis (Cross Period)
You can monitor the task implementation status and analyze the task completion status.
The schedule analysis for cross periods provides an overview of the cross period schedule
analysis of each task.

Figure 94: BI Reporting - Status Monitoring cross Templates
Cross template reporting provides a better overview of the closing status for different
templates. It helps local and group end users to monitor closing.
Smart Business Apps
Figure 95: Analyzing progress on financial close and continually improving entity close
The status and progress of the entity close can be displayed via real-time access
Corporate managers and subsidiaries managers may analyze the status of the closing
process for both this closing cycle and the last several closing cycles
Color coding give you an immediate status regarding progress on the close so far
- Green: the process for different company codes looks fine and under control
- Yellow or red: there are some problems i.e. delays

Figure 96: Chart and Filter Types
You can analyze the close status by different views, such as region, country and phase.
Furthermore, for each information i.e. completed tasks, delayed tasks, tasks with errors,
omitted tasks and the planned and actual start and end times, you can display the resulting
information in different charts suiting your purpose.
Figure 97: Close Progression
You can get a quick overview of the close progression status.

Figure 98: Delayed and Erroneous Tasks
You can get immediate awareness of tasks that are delayed or have execution errors.
Figure 99: Close Evolution (per Posting Period)
You can track the time to close and evaluate it per period.
LESSON SUMMARY

UNIT 3 SAP Business Process
Automation in SAP
Financial Closing
cockpit
Lesson 1
Introducing SAP Business Process Automation by Redwood and the Relation to SAP Financial 71
Closing cockpit
UNIT OBJECTIVES
Understand the relationship between SAP BPA and SAP FCc
Understand the Process Automation Engine
Understand details and view examples for the Process Automation Engine

Unit 3
Lesson 1
Introducing SAP Business Process Automation
by Redwood and the Relation to SAP Financial
Closing cockpit
LESSON OBJECTIVES
SAP Business Process Automation by Redwood

SAP Business Process Automation by Redwood (SAP BPA) is an automation platform based
on the SAP NetWeaver JAVA stack. This is the basic technology for FCA.
Financial Close Automation (FCA) by Redwood
FCA is a version of BPA; BPA includes Financial Close Automation (FCA) content.
The Business Automation Enabler (BAE) interface has been released to other external
schedulers using SAP Note 2391918.
Additional effort is required to implement such a highly automated close including automated
bug-fixing. A separate system landscape and IT resources are required for implementation.
Figure 100: SAP FCc and FCA Architecture 1/2

Unit 3: SAP Business Process Automation in SAP Financial Closing cockpit
This architecture would be the same for other schedulers. Any external scheduler has built-in
functionality, such as reading and interpreting table content, spool lists, and job logs and can
react to certain error messages. However, during implementation, you have to provide
instructions to the scheduler, about, for example, how to react per error message.
A common example of such an automatic bug-fixing process is the depreciation run. It often
fails due to locked cost centers. The task is started by a business user using the financial
closing cockpit, and the scheduler is first to run the depreciation run. Once finished, the
business user checks the spool list and job log. If cost centers are locked, the user can reopen
them, repeat the depreciation run and close cost centers again. Cost center owners will be
informed, and the task status is set to finished in SAP FCc.
Figure 101: FCA with SAP FCc and ERP Systems
Figure 102: FCA with SAP FCc and One ERP System

Lesson: Introducing SAP Business Process Automation by Redwood and the Relation to SAP Financial Closing cockpit
Process Automation Engine
Figure 103: SAP S/4HANA Financial Closing Cockpit with Process Automation Engine
The Process Automation Engine provides increased speed, efficiency, and compliance
through the automation of manual steps.
Use cases for the Process Automation Engine include the following:
Closing tasks in SAP and non-SAP systems
Event-based execution
Validation of task output
Intelligent auto-reactions
Automation of reporting
Automation of batch-input processing
Automation of transactions
Extended notifications, extended management of variants and parameters
Management of hardware resources (for example, load balancing)
The Process Automation Engine provides a network of insights:
Single source of truth
Human intelligence
Exception focus
It provides a network of processes:

Process integration
Automated handover
Event-driven interaction
The engine also provides a network of technology, with a process automation component that
is fully integrated into the SAP NetWeaver technology platform.
The engine has a network of resources, both ERP and non-ERP and both SAP and non-SAP.
Figure 104: Benefits of the Process Automation Component
The benefits of the Process Automation Component are as follows:
SAP and non-SAP systems

The Process Automation Component enables the closing process of all entities to be
automated and monitored centrally within the financial closing cockpit, regardless of
source system.
For SAP systems, this can be multiple instances or versions of SAP ERP Financials (ECC
6.0, 5.0, R3) or other SAP systems (for example, NW BW, BPC, GRC, CRM).
For non-SAP systems, this could be subsidiary ledger systems (for example, JD
Edwards) for multiple topics (fixed asset, payroll, and so on) or other systems.
Event-Based Automation
Once programs or tasks are successfully completed, an "event" is triggered
automatically to begin processing of next dependent step, eliminating any wait time
between tasks.
The automation component can also "react" to external triggers.
For example, it can automatically recognize file arrivals from various sources as "event
triggers" and post data into SAP or alert users by email.
Task Output Validation

Even if the job and application log are correct, results may need to be checked from a
business perspective. For example, a reconciliation report runs fine, but identifies
multiple mismatches.
Task output validation allows you to analyze the spool list, examples include Balance
Zero, Check Columns Equal, Check Column Zero, Check Text Exists, Check SAPLog
Message, Check Totals Zero.
Intelligent Auto-Reactions
It is possible to define decision trees about how to continue processing dependent on
results of task execution or task output validation.
Examples include identifying posted documents or section of a spool list, splitting and
sending to multiple owners for approval, and only setting task to complete after sign-off
is received from all owners.
Batch-Input Automation
You can automate the process of batch input map creation, batch input map
identification (single or multiple ones), autostart, checking of status and log of processed
batch input maps, retrieving booked documents, and even further processing (see auto-
reactions).
Automation of Transactions
You can fill in values and trigger processing even though there are no variants on SAP
side.
Extended Notifications
The Process Automation Component can provide alerting for all tasks, based on triggers
that are outside the financial closing cockpit and SAP.
This functionality goes beyond financial closing cockpit concepts.
Extended Variant and Parameter Management
The Process Automation Component supports dynamic calculation for dates and values,
and formatting.
This functionality goes beyond financial closing cockpit concepts.
Management of Computing Resources
Examples include load balancing between multiple systems and closing tasks having
priority during certain time ranges.

Figure 105: Maturity Levels
The figure shows a list of possible EPA Maturity Levels.
Details and Examples of the Process Automation Engine

The benefits of the SAP Business Process Automation by Redwood (SAP BPA) include
automated closing tasks in SAP and non-SAP systems.
The automation engine allows closing process of all entities to be centrally automated and
monitored regardless of source systems.
Examples of SAP source systems:

- SAP S/4HANA
- SAP ERP (ECC 6.0, 5.0, R3)
- Other SAP systems (for example, NW BW, BPC, GRC, CRM)
Examples of non-SAP source systems:

- Non-SAP sub-ledger systems (for example, for fixed asset, payroll, and so on)
- Home-grown systems
- Operating systems
- Other systems

Figure 106: Platform Integration - Business Objects Crystal Reports
A scheduler can create a report. Once created, the task owner will be informed that the report
is available.
Figure 107: Platform Integration - BW Process Chains
The figure shows an example of financial closing cockpit initialization for BW Reporting.

Figure 108: Platform Integration - Solution Manager Incident Creation
Solution Manager Incident tickets can be created from SAP BPA as part of the process.
SAP BPA Benefits: Event-Based Execution
Once a process step is successfully completed, an “event” is triggered.
This can start the processing of the next steps automatically, eliminating any wait time.
This is different from SAP S/4HANA Financial Closing cockpit because the automation
component can be set for external triggers.
For example, the process automation engine can:

- Automatically recognize file arrivals from various sources as “event triggers”.
- Alert users by e-mail or start the next step, such as the posting of data into SAP.
Validation of Task Output
Even if the job and application log are correct, the results may need to be checked from a
business perspective.
For example:
A reconciliation report runs properly, but identifies multiple mismatches.
The Automation Engine allows you to automate the analysis of the spool list.
Examples include:
Check balance zero
Check column zero
Check two columns equal
Check text exists
Check SAP Log message

Figure 109: Match Asset Details with G/L Account Balances
Building Block can be used for SAP and FCC.

Function: Temporary Variants, Validation
Figure 110: Table BFOD_A - Check Entries Without Clearing Date

Function: Temporary Variants, Validation
SAP BPA Benefits: Intelligent Auto-Reactions
It is possible to define decision trees about how to continue processing base on:
- Results of task execution
- Task output validation

The Automation Engine enables multi-step tasks with automatic hand-over of results
between the steps.
Examples of Intelligent Auto-Reactions
Example 1:
- Identify sections of a spool list.
- Split and send parts of spool list to multiple owners for approval.
- Set task to OK, only if sign-off is received from all owners
Example 2:
- Identify whether account balance equals zero.
- If account balance is not zero, create automatic correction posting.
Example 3:
- Run report in test mode first. If it runs correctly, then run in update mode.
Figure 111: AFAR - Recalculate Unplanned Depreciation

Function: Sequence, Temporary Variants

Figure 112: KSV5 - Actual Distribution with Notifications

Function: Temporary Variants, Sequence, Notification with Workflow, Validation
Note:
Additional check included so that the job waits for asynchronous processes
(update) to complete.
In the financial closing cockpit, the input provided by the user consists only of a list
with Cycles to process.
Figure 113: FBL5N - Set Payment / Dunning Blocks

Function: Temporary Variants, Validation, Corrections (FB02), BDC processing

Figure 114: FBL3N - Clearing Account Accrual / Reversal at End of Period

Function: Temporary Variants, Validation, Corrections (FB01), BDC processing
Figure 115: Retrieve Excel from Predecessor Task in SAP FCC and Process It
Building Block can only be used with FCC.

Function: FCC retrieval, BDC processing

Figure 116: Retrieve G/L Postings with Attachments

Function: Document details retrieval
Hint:
Similar tasks and processes can be executed with other schedulers. Please reach
out to your vendor to understand what is available and possible with their
solutions.
LESSON SUMMARY

UNIT 4 Summary and Outlook
Lesson 1
Summarizing the Solution 85
Lesson 2
SAP S/4HANA Cloud for Advanced Financial Closing 93
UNIT OBJECTIVES
Summarize the Solution
Analyze the Availability
Summarize the Benefits
Introduce Advanced Financial Close

Unit 4
Lesson 1
Summarizing the Solution
LESSON OBJECTIVES
Solution Summary
Figure 117: SAP S/4HANA Financial Closing Cockpit
Summary
The SAP S/4HANA Financial Closing cockpit is a comprehensive solution for managing
your global financial close on the entity level.
It covers the planning, execution, monitoring, and analysis of financial close tasks.
It allows you to standardize your close process across entities and closing cycles, increase
compliance, gain transparency, and drive efficiency through higher automation.
External schedulers are an additional process automation component, tightly integrated

into, and accessible via, the SAP S/4HANA Financial Closing cockpit.

Unit 4: Summary and Outlook
It supports you with SAP and non-SAP tasks, event-based scheduling, intelligent validation
of task output, intelligent auto-reactions, batch input management, and more, to reduce
manual effort.
SAP S/4HANA Financial Closing cockpit and external schedulers (optional) are part of a
full suite of comprehensive solutions for the end-to-end Financial Close, making it faster,
more accurate, and less costly to execute.
Availability
SAP S/4HANA Financial Closing cockpit

The SAP S/4HANA Financial Closing cockpit is part of S4CORE, but it requires a separate
license fee.
A new support package for SAP S/4HANA Financial Closing cockpit is delivered in
accordance to the SAP S/4HANA support package schedule.
SAP Financial Closing cockpit add-on 2.0

The SAP Financial Closing cockpit add-on 2.0 can be used with SAP ERP 6.0.
The add-on has to be installed separately, which gives you more flexibility for upgrades to
the SAP Financial Closing cockpit add-on. It requires a valid license.
Figure 118: Upgrade Monitor - Highlights
Check transaction code FCC_UPGRADE_MONITOR , which allows the migration of templates

and task lists of the financial closing cockpit into new data structures of SAP S/4HANA
Financial Closing cockpit after a system conversion.
It offers:
Single entry for upgrade process to SAP FCc add-on or SAP S/4HANA FCc
Clearly defined steps to follow

Lesson: Summarizing the Solution
Status control for each upgrade step
Easy access to each upgrade activity
No interruption to your running FCc
Selectable Upgrade Possibility
Online and job copy mode selection
Real-time monitor of copy progress
Application log for recording copy activities
Figure 119: Upgrade Path SAP ERP
For upgrade from FCc in EA-APPL:
FCc in EhP4, EhP5, EhP6, EhP7 directly to FCc add-on 2.0
Figure 120: Upgrade Path — SAP S/4HANA
For Upgrade from FCc in EA-APPL:
FCc in EhP4, EhP5, EhP6, EhP7 directly to SAP S/4HANA FCc
For upgrade from FCc add-on 2.0:
FCc add-on 2.0 to SAP S/4HANA Financial Closing cockpit
When you upgrade your system to the current SAP S/4HANA release, the upgrade of the SAP
FCc add-on 2.0 is automatic. No additional customizing or tasks are necessary to use the
same functionality. For setting up the Web UI at SAP S/4HANA Financial Closing cockpit, you
need to follow the instructions at help.sap.com .

To upgrade from the closing cockpit or SAP Financial Closing cockpit (based on business
functions) to SAP S/4HANA Financial Closing cockpit (the embedded free of charge version),
you run transaction FCC_UPGRADE_MONITOR after your system has been converted to SAP
S/4HANA.
Figure 121: Available User Interfaces (UI), SAP GUI - Template
Figure 122: Available User Interfaces (UI), SAP GUI - Task List

Figure 123: Available User Interfaces (UI), SAP GUI - Task List
Figure 124: Available User Interfaces (UI), SAP Fiori - Manage Template

Figure 125: Available User Interfaces (UI)m SAP Fiori - Process Task List (classic)
Figure 126: Available User Interfaces (UI), SAP Fiori -Task List

Figure 127: SAP S/4HANA Financial Closing cockpit
For online help, go to help.sap.com/s4hana .

Notes and message component: CA-GTF-FCC (older notes under CA-GTF-SCM) and CA-GTF-
FCC-FIO (for SAP Fiori App for FCC)
Figure 128: Important Notes

The notes are relevant for SAP S/4HANA Financial Closing cockpit and SAP Financial Closing
cockpit add-on although the validity of all notes might not be extended to new versions of SAP
S/4HANA.
Benefits
Figure 129: SAP S/4HANA Financial Closing Cockpit - Benefits
LESSON SUMMARY

Unit 4
Lesson 2
SAP S/4HANA Cloud for Advanced Financial
Closing
LESSON OBJECTIVES
Solution Overview
Figure 130: Solution history
SAP S/4HANA Cloud for advanced financial closing is SAP's strategic Record-to-report
orchestration solution and builds upon decades of proven technology.
Figure 131: Planning, automation and monitoring
Benefits & Capabilities:
Closing is faster and efficient because it's orchestrated with tasks automatically triggered
by completion of the earlier tasks - along an optimized timeline, with minimized downtime.

- The solution delivers many automated closing tasks - alerts are going to let you know if
there's been any issues
- The solution has workflow-supported intuitive apps for manual tasks - users are notified
when it's time to do manual tasks - and have access to collaboration and escalation
tools to keep the process moving smoothly
Closing is optimally governed and auditable. Your users can define a Global game plan for
the entity close; this template gets serialized for multiple org units and closing cycles
- The performance of all steps (automatic and manual) are documented with a complete
audit train of status changes and incidents
- Approval workflows can be configured for specific tasks, and comments can be added
as necessary
- The Audit trail with detailed logging and documentation for each step in the process is
available for review
Transparency and Insight - management reporting analytics are built directly into the tool
to let everyone know exactly what the status is at all times
- Comprehensive analytics provide real-time insight into the closing status - I can see
exactly the status of the area I'm responsible for
- Close analysis also provides monitoring for subsidiaries and the headquarter - this is
information you can use to improve your close with each cycle
Figure 132: Role-based approach coordinates tasks across your team
Advanced Financial Closing allows you to plan, execute, monitor, and even analyze financial
closing tasks for the entities of your group. Five easy-to-use apps with a uniform look and feel
have been specifically designed to support periodically recurring closing activities. This can be
done in a fixed chronological or dependent sequence and allows for multiple stakeholders.
The solution provides support for the various stakeholders such as:
Business Experts, who define the overall plan.
Accountants, who process manual tasks and monitor automated steps
Approvers, with a dedicated App

Lesson: SAP S/4HANA Cloud for Advanced Financial Closing
Management with comprehensive Analytics
Figure 133: Closing Hub with out-of-the-box connectivity
The SAP Cloud Connector (https://help.sap.com/viewer/

cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/
e6c7616abb5710148cfcf3e75d96d596.html?q=cloud%20connector) is required in all
scenarios between an SAP S/4HANA or SAP ECC system and SAP S/4HANA Cloud for
advanced financial closing on the SAP Cloud Platform to establish a secure communication
scenario. It is a non-modifying add-on, and it is not separately priced.
The Integration Component (https://help.sap.com/viewer/product/
SAP_ERP_CONNECTOR_FOR_ADVANCED_FINANCIAL_CLOSING/1.0/en-US) is required in
all scenarios between an SAP ECC system (EHP4+) and SAP S/4HANA Cloud for advanced
financial closing on the SAP Cloud Platform to enable scheduling. It is a non-modifying add-
on, and it is not separately priced.
From back-end Accounting Systems to AFC:
Organizational Data: such as Company Codes,
Accounting Principles
Ledgers
Fiscal Year Variants
Factory Calendars
Results of jobs (view-only of spools)
SAP S/4HANA and SAP ECC spools are saved in dedicated AFC tables of the Back-end
Accounting systems
From AFC to Back-end Accounting Systems:
Triggers for scheduling background jobs
Parametrization of SAP Fiori apps for intent-based navigation
Authorization data (User ID and E-Mail) for access checks in the Back-end Accounting
Systems

Figure 134: Key Roadmap Areas
The key roadmap topics are divided into three main buckets.
1. Closing Hub Scenario: This is about extending the integration and connectivity capabilities
of AFC so that it can even better serve as a centralized closing hub in heterogeneous
system landscapes - today we can already connect to both SAP ECC and SAP S/4HANA
systems and looking at your future move to SAP S/4HANA, this would already work and
integrate out-of-the-box.
2. Intelligent Closing is about leveraging modern technologies to further automate and

streamline the close - this includes even smarter automation, alerting and simulation
capabilities than we have today.
3. Central Steering is about aligning our multiple tools along the Record-to-Report process
and enabling AFC to be the core orchestration engine. This would include that we use AFC
to monitor processes like statutory reporting, organizational changes and integrate the
entity close tighter with the Group Close.
Check the SAP Roadmap Explorer for all the latest innovations.
Business Objects and Process Flow
Figure 135: Major business objects in financial close management
The most important business objects in AFC are outlined in the following:

1. Task represents a single closing activity, for example the foreign currency valuation run or
the asset depreciation run.
2. Task List is an organized worklist for a specific closing cycle's execution. It is generated
from a predefined Task List Template and can be further adjusted.
3. Task List Template is a predefined worklist to be used as the template for repeatable Task
List generation.
4. Task List Model is the predefined abstracted Task List Template for a dedicated business
context in the Communication System. It is delivered as customizing/ content to be
copied when defining Task List Templates in AFC.
5. Task Model Type and Task Model are abstracts of the tasks with detailed attributes like
program name, parameter variant, web address, closing types, etc., maintained.
You can include different types of task types:
SAP Fiori Application: Process closing task manually by means of transactional or

analytical application defined on the SAP Fiori launchpad. Parameters defined on the
folders or on the tasks of the folders such as company code are automatically transferred
to ensure that the assigned processor has all necessary authorizations to process the
assigned application.
Job - Schedule automatic process steps. If the closing task is marked as automatic, the job
is scheduled automatically once the start time is reached and the predecessor task is
completed. Otherwise, you can schedule jobs manually.
Note - Process closing tasks manually by external means.
Web Application - Closing steps that are processed using external web services or to
assign documentation resources. A web application is any service or HTML page
accessible via a URL. In the web application use case, parameters are not transferred to
the web application.
Figure 136: Process Overview
This flow diagram represents the typical process steps and roles per system. In the following
concepts, each step will be described in detail.

Task Modeling
Note:
SAP provides standard content for task models, customers with on-premise SAP
S/4HANA and SAP ERP systems can customize the task models with the
transactions mentioned in following slides, SAP S/4HANA Cloud customers can
directly use the standard content but can't currently change it.
Figure 137: Task Modeling - Overview
Through Task Modeling in the Communication System, customers can abstract the existing
applications as Task Models to be selected when defining a Task List Model or Task List
Template. Right now, the following application types are supported:
1. ABAP programs can be scheduled as a job, for example, fixed asset depreciation run
2. SAP Fiori apps or GUI transaction codes (SAP Internet Transaction Server needed)
3. Notes
4. Web applications, can be web services or HTML pages, accessible via URL
Note:
Task Model Type is currently also known as Closing Business Transaction Type
(BTY). This will be fully renamed as Task Model Type in all AFC- supported ERP
releases.

Figure 138: Task Modeling - Define Task Model Type
Task Modeling is done in the Communication System as configuration step. SAP delivers
sample content for the supported SAP ERP product releases. Users can define business
transactions and link them with existing applications.
Note:
Task Modeling is necessary for job type tasks, SAP Fiori app type tasks. Users can
directly maintain the web or note type tasks information when defining a Task List
Template in AFC.
Figure 139: Task Modeling - Define Task Model and Task List Model
Customers further define the Task Model by maintaining the important attributes like linked
business transaction type, applicable closing cycles, context and country assignment, and so
on.

1. Define the Task Models. If needed, assign country codes to Task Models so that they are
only applied to specific countries when assigning a Task List Model to a Task List
Template.
2. Organize the tasks models as a hierarchy in a Task Model set to model a task structure
applicable to all of your organizational units.
3. Define task dependency to control the execution sequence.
Other configuration data, replicated from Communication Systems to AFC:

To define and to execute the tasks, the following master data objects are automatically
replicated from connected Communication Systems to AFC:
1. Company Code: the ID, description, and attributes value like Country, Fiscal Year Variant,
and so on are copied
2. Accounting Principles
3. Ledgers
4. Fiscal Year Variants
5. Factory Calendar
Hint:
Tips:
The system automatically syncs changes of configuration data once per day.
Users can also manually sync changes immediately by choosing the
Synchronize now button for a selected system in the Specify Communication
System app.
All of the above configuration data is system-dependent - if multiple systems

are assigned to one Task List (*1), those configuration data need to be defined
in each corresponding system folder or on organizational unit folder level.
If the Fiscal Year Variants used by companies in one system are different,
separate Task Lists should be considered for each Fiscal Year Variant as a
best practice.
Note:
The assignment of multiple communication systems to one Task List in AFC is not
possible in the first release, but is planned to be enabled in the future.

Task List Definition
Figure 140: Task List header
To generate executable Task Lists, accounting experts need to plan tasks by defining the Task
List Template. It includes the Organizational Units, the tasks that need to be executed, the
process controls and parameter settings, and so on.
A Task List Template comprises two main parts: Task List header and Closing Structure.
Task Detail Information
The following aspects should be considered for task execution, therefore they need to be set
up on Task List Template level:
1. What tasks should be executed (Closing Structure)
2. Who should execute and monitor the tasks? (Roles/authorization, approval settings)
3. How should the tasks be executed? (Parameters, additional task knowledge like
attachment, notes, and so on)
4. When should the tasks be started and finished? (Scheduling settings)
5. How should users be informed about important events? (E-mail and notification settings)

Figure 141: Closing Structure
1. The Closing Structure consists of Folders (for example, system, org. unit, folder) and
Tasks. It defines which Tasks apply for which Organizational Units and shall be executed in
which sequence. The structure can be defined in different ways:
2. Manually add the tasks, Organizational Units
3. Use organizational hierarchy, and then manually add tasks to Organizational Units
4. Use organizational hierarchy, apply predefined Task List Model to all units in the hierarchy,
then manually adjust
5. It's possible to display the structure by hierarchy view, list view, or tasks dependency view.
AFC orchestrates closing tasks in multiple systems and organizational units from one
Task List; typically, there are the following levels of hierarchy nodes:
6. Communication System level
7. Organizational Unit level
8. Sub-folder level to group the tasks
9. Tasks can be added below each hierarchy node level
Note:
The assignment of multiple communication systems to one Task List in AFC is not
possible in the first release, but is planned to be enabled in the future.

Figure 142: User Roles and Access Control
The setup depends on the customers' authorization governance model, there are two ways to
control the tasks access:
By user/user group: You can directly assign a user or a user group as responsible person
or processor on Closing Structure items; those users are then automatically granted the
access to Task List Template, Task List (for responsible person) and tasks (for both
processor and responsible person).
By Authorization Group: You can indirectly give Authorization Groups access to Closing
Structure items; those users who get authorization groups via assigned user roles can
execute operations as illustrated in the figure.
There are two roles for task execution:
The processor, who needs to execute the tasks
The responsible person, who is responsible for the task status and the approval of the task
completion
Additionally, Substitutes can be defined for the responsible person or the processor and can
automatically inherit the object access of substituted persons.
Note:
By enabling the Enforce SOX Requirements compliance setting, the system will
not allow the processor and responsible user to be the same.
Note:
The responsible user or user group must be maintained if a task needs an
approval process, so that the workflow items can be sent to the responsible
persons.

Figure 143: Approvals for Formal Task Sign-Offs
Completed Approval Required: Task completion approval needed, it's not possible to
execute successor tasks without this task being approved
Pending Approval Required: Task completion approval needed, but the pending approval
does not impact the successor tasks execution
No Approval Required
Figure 144: Approval Status Flow
It depends on the setting of the task approval type whether the system triggers the workflow
for the task responsible user's approval. The figure explains the approval status flow in the
system.
Figure 145: Parameters for Tasks of Type Job

For job type Tasks, parameter values are assigned generically to ensure automatic job
execution. There are two places where parameters values can be maintained in AFC:
1. Parameter Types:
2. SAP managed for automatic value assignment, or not SAP managed for manual value
assignment
3. Modeled in the Communication Systems
4. Assigned on Folder level to assign common parameters on multiple tasks
5. Job parameters: Individually set for each specific task of type Job
Note:
If job parameters get values from both job parameter value settings and
parameter type value settings, job parameter settings overwrite the more generic
parameter type value settings.
Note:
AFC can transfer SAP managed parameters values to URLs – it depends on the
SAP Fiori app or web service whether the parameter values can be successfully
transferred.
Figure 146: Scheduling
Task scheduling and monitoring are important functions to enable an accelerated and
accurate close. Each task has planned scheduling data and actual status change data to
enable tracking of the closing process.
The Factory Calendar is considered by AFC for scheduling manual task types (Fiori
Application, Note, Weblink) so that the planned start date is on a working day; automatic task
types like tasks of type Job are planned without considering the Factory Calendar.

Figure 147: Notifications
Users and users' substitutes can get an E-Mail notifications and SAP Fiori notifications when
there is a predefined event happening on the Task List or single task level.
Figure 148: Attachments and Notes Handling and Storage
To provide additional information like detailed working instructions within the Task Lists and
tasks, customers can add attachments and notes to each task – all of this additional
information will be copied to the generated tasks for the user's reference.
Link addresses must start with http:// or https://
Attachments and Notes are stored with draft logic. When generating task lists, only links to
the attachments are copied. This means the file is only stored once. As soon as the last link is
deleted, the file is deleted. Attachments are encrypted.
Attachments can be uploaded to store documentation and provide proof about completed
tasks:
Attachments created in the Define Closing Tasks app cannot be deleted in the Process
Closing Tasks app
Attachments created in the Process Closing Tasks app can be deleted in both processing
and defining closing tasks apps
Once the task list is set as completed , attachments can no longer be changed

Task List Creation and Execution
Figure 149: Task List Generation
Once the Task List Template is fully maintained, users can generate executable Task Lists.
Dynamic scoping:
A Task List Template can cover tasks of all Closing Types. At Task List creation, the
system will only consider the tasks which are assigned to the chosen Closing Type.
A Task List Model covers tasks for all countries. When assigning a Task List Model,
country-specific(*1) tasks are added only to Company Code Folders with matching(*2)
country.
Note:
Country assignments of Task Models are maintained in the communication
system.
Note:
Company Code Master Data are defined as assigned to countries in the
communication system (table T001, "Company Codes").

Figure 150: Processing Task Lists
For released Task Lists, users can schedule the execution, change the status, and monitor the
progress.
Different actions can be done, based on the type of tasks:
For tasks of type Note, users can give notes and change the task status.
For tasks of type SAP Fiori Application or Web Application, users can navigate to the local
or remote system, execute the task, and then go back to AFC to change the status, add
notes and attachments, and so on.
Figure 151: Job Tasks
For tasks of type Job, users can schedule the task to plan the execution of the jobs in
connected Communication Systems.

Figure 152: Define Tasks Dependency
If tasks need to be processed in a logical sequence, users can define dependencies. There are
additional checks on allowed task status changes and it is possible to automatically trigger
the execution of successor tasks of type Job.
The system will auto check:
Dead loop of task's sequence.
Successor task's start time cannot be earlier than the predecessor task's start time.
Figure 153: Display Task Dependencies
You can visualize the dependencies in diagram form.

Figure 154: Task Logs
Users can check the task logs like the status change logs, job logs, spool lists (PDF), and
additional notes which are attached.
Figure 155: Task Execution Analysis
Managers can check the analytics reports to get the closing status overview and drill down to
the lowest level of detail, using multiple filter attributes like Task Lists, Countries, Country
Groups, Task Status, or Company Codes.
LESSON SUMMARY

UNIT 5 Appendix
Lesson 1
Appendix FCc 2.0 (SAP ERP) 112
Lesson 2
Appendix SAP Business Process Automation (BPA) 115
Lesson 3
Appendix General 126
UNIT OBJECTIVES
Explain FCc 2.0 in SAP ERP
Explain SAP Business Process Automation (BPA)
Appendix

Unit 5
Lesson 1
Appendix FCc 2.0 (SAP ERP)
LESSON OBJECTIVES
SAP FCc add-on 2.0
Figure 156: Filtering the Task List (NWBC)
Typical global business companies complete more than 150-300 closing tasks per company
code in a local close cycle. This makes quick identification and batch update processing for
maintenance objects crucial.

Lesson: Appendix FCc 2.0 (SAP ERP)
Figure 157: Activation of Services for SAP Business Client - Web UI Set Up
With SAP S/4HANA, the relevant services are switched on by default, but remember to check.
After activation of the FAGL_FCC* services, you need to check the authorization role delivered
by SAP SAP_FCC_MENU.In that role, you find the user menu and necessary authorizations
for use of Web UI. Add these authorizations to all of your financial closing cockpit
authorization roles, and then you are ready for a later implementation of the Web UI.
Figure 158: SAP Financial Closing Cockpit Add-On 2.0
SAP Financial Closing cockpit Add-On 2.0 does NOT need activation of Business Functions.

Unit 5: Appendix
Figure 159: SAP Financial Closing Cockpit Add-On 2.0
For online help, go to http://help.sap.com/erp_fcc_02 .

Notes and message component: CA-GTF-FCC (older notes under CA-GTF-SCM) and CA-GTF-
FCC-FIO (for SAP Fiori App for FCC)
LESSON SUMMARY

Unit 5
Lesson 2
Appendix SAP Business Process Automation
(BPA)
LESSON OBJECTIVES
SAP BPA
Figure 160: SEM-BCS Consolidation - Company Level Preparation Tasks [Planned]
A scheduler could retrieve a status of other monitors, for example cons monitor into SAP FCc.

Unit 5: Appendix
Figure 161: Platform Integration - Web Services
The figure, Platform Integration - Web Services, shows an example of a process that uses
Web Service to retrieve Exchange Rate (using SOAP request).
Figure 162: Platform Integration - Oracle Applications

Lesson: Appendix SAP Business Process Automation (BPA)
Figure 163: Platform Integration - Starting a Platform (*) Based Process
The figure shows the integration of an OS-based process.
Figure 164: Platform Integration - Java Database Connector Integration
Any database with a Java Database Connector integration can be connected to SAP BPA.
It can execute queries and stored procedures.

Unit 5: Appendix
Figure 165: Platform Integration - Mainframe Job Control Language
Figure 166: Platform Integration - Waiting on External (File) Event
The figure shows the system waiting for an external process to provide the file to be
processed.

Figure 167: CK40N - Costing Run

Function: Temporary Variants, Validation, CK40N automation
Figure 168: CKMLCP - Actual Costing Run

Function: Temporary Variants, Validation, CKML automation.

Unit 5: Appendix
Figure 169: End–to–End Automated Cycle for SAP S/4HANA Financial Closing Cockpit [Planned]
Building Block can only be used for FCC.

EHP5 OSS Note 1696446 to implement functionality.
EHP6 or Add-On release provide functionality as standard.
SAP BPA Benefits: Batch Execution of Reports
Automatic execution of reports in batch, instead of people running them online.
Report results are stored in SAP BPA or in the SAP S/4HANA Financial Closing cockpit
Examples include:
- Drill-down reports
- Report Painter reports
- Logistic Information System reports
Figure 170: KE80 / 8A-PCA001G - EC-PCA Profit Center Group: Plan/Actual/Variance


Function: Temporary Variants
Figure 171: GR55 / 1AIP - Report Writer - Area: Cost Elements

Figure 172: MC.1 - Plant Analysis

Note:
LIS reports in batch do not generate output.

Unit 5: Appendix
SAP BPA Benefits: Batch-Input Automation
Batch-input automation allows you to automate the overall process of batch input
processing:
- Batch input map creation
- Batch input map identification (single or multiple ones)
- Autostart of batch input map
- Checking of status and log of processed batch input maps
- Retrieving booked documents
- Further processing (see auto-reactions)
Figure 173: Batch Input Processing

Function: Temporary Variants, Validation, Sequence

Figure 174: Processing Batch Input Maps in SAP Standard
Figure 175: Processing Batch Input Maps with SAP BPA
Further SAP BPA Benefits
Fill in values and trigger processing even though there are no variants on the SAP side

Unit 5: Appendix
Alerting for all tasks and based on triggers also outside the Financial Closing cockpit and
SAP
Functionality goes beyond Financial Closing cockpit concepts
Dynamic calculation for dates and values, formatting
Functionality goes beyond Financial Closing cockpit concepts
Example: Load balancing between multiple systems
Example: Closing tasks have priority during certain time ranges
Figure 176: OB52 / OKP1 - Open / Close Periods

Figure 177: Automatic Notifications for all FCC Task Types

Building Block can only be used for FCC.

It retrieves FCC task specific information. An SAP generic version is also available.
LESSON SUMMARY

Unit 5
Lesson 3
Appendix General
LESSON OBJECTIVES
Appendix
Appendix
Figure 178: SAP Financial Closing cockpit - Previous Releases

Lesson: Appendix General
Figure 179: SAP Financial Closing cockpit Add On Scope
Figure 180: SAP Financial Closing cockpit 1.0 - Benefits and New Capabilities

Unit 5: Appendix
Figure 181: SAP Financial Closing cockpit 2.0 - Benefits and New Capabilities
Figure 182: History of Releases

Lesson: Appendix General
Figure 183: New Functionality in SAP ERP 6.0 EhP5
Figure 184: New Functionality in SAP ERP 6.0 EhP6
LESSON SUMMARY
Appendix

S4F16 - EN - Col17 SAP Financial Closing Cockpit in SAP S4HANA

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

S4F16 - EN - Col17 SAP Financial Closing Cockpit in SAP S4HANA

Uploaded by

Copyright:

Available Formats

SAP Financial Closing cockpit in

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

© Copyright. All rights reserved. iii

American English is the standard used in this handbook.

This information is displayed in the instructor’s presentation

Related or Additional Information

User interface control Example text

Window title Example text

© Copyright. All rights reserved. iv

1 Unit 1: SAP Financial Closing cockpit for SAP S/4HANA - Overview

2 Lesson: Presenting the SAP Financial Closing cockpit for SAP S/

36 Unit 2: SAP S/4HANA Financial Closing cockpit for SAP S/4HANA

37 Lesson: Understanding Customizing Relevant for SAP S/4HANA

70 Unit 3: SAP Business Process Automation in SAP Financial Closing

71 Lesson: Introducing SAP Business Process Automation by Redwood

84 Unit 4: Summary and Outlook

85 Lesson: Summarizing the Solution

111 Unit 5: Appendix

112 Lesson: Appendix FCc 2.0 (SAP ERP)

© Copyright. All rights reserved. v

© Copyright. All rights reserved. vi

Describe the challenges of financial closing

Plan closing tasks

Create a task list for a closing cycle

Execute closing tasks

© Copyright. All rights reserved. 1

Describe the challenges of financial closing

Plan closing tasks

Create a task list for a closing cycle

Execute closing tasks

Challenges of Financial Closing

Figure 1: Growing Pressure is Here to Stay

Volatility in markets, commodity prices, and stocks

Increased focus on risk

Regulation that will not go away

Increasing globalization, requiring corporate management across diverse cultures

Continuing pressure on margins

© Copyright. All rights reserved. 2

Figure 2: Greater Expectations from Finance

The expectation to add value by helping the organization to outperform stakeholder's

Figure 3: Our Solutions for Finance

© Copyright. All rights reserved. 3

Ensure regulatory compliance and effective risk management

Outperform financial objectives and create sustainable value

Deliver superior service

SAP Portfolio of Applications

Strong cash flow and liquidity

Compliant and accurate financial reporting

Reduced cost of finance

Partnership with the organization to drive value creation

Figure 4: Financial Closing - The Reality

© Copyright. All rights reserved. 4

Figure 5: Accounting and Financial Close

Figure 6: Challenges of the Financial Close Process

© Copyright. All rights reserved. 5

Figure 7: Financial Close Functionality in the SAP Business Suite

Who will execute what, and at what time?

In what order do we need to execute the steps?

What is the current status of the task list?

Has the process started?

Is the process complete?

© Copyright. All rights reserved. 6