HCM Planning

SAP Best Practices for BPC (Business

Planning and Consolidation) V1.75

SAP Best Practices

Scenario Overview 1

Purpose and Benefits:

Purpose
Plan salary and bonus per organization and position. Plan other personnel
expenses such as welfare, benefit and pension per organization

Benefits
Ensure integration and consistency with PL planning
Scenario Overview 2

SAP Applications Required:

SAP BusinessObjects Planning and Consolidation 7.5, version for the Microsoft
platform

Company Roles Involved in Process Flows:

HR Responsible Person
Responsible Planner

Key Process Flows Covered:

HCM Planning Setup

Planning Data Confirmation
Confirm Reporting Data and Approve Planning Data in BPF
Data Transfer from HCM Planning to P&L Planning
Scenario Overview 3

Detailed Process Description:

HCM Planning
This scenario is about the processes of planning HCM data and approving planning
data.
HR staff plans the HR rate and headcount per organization and position. Salary and
bonus amount is calculated automatically.
HR staff inputs the planning data for other personnel expenses such as welfare,
benefit and pension are planned per organization.
After confirmation of the HCM planning data in the relevant report, the HR staff sets
the status in the BPF to submitted.
Budget planner confirms the HCM planning data and approve/reject it.
If approved, the BPF step is set to completed.
If rejected, the flow is returned to the HR staff side; after further adjustment of the
planning data, the BPF step is set to completed.
Budget planner confirms the BPF status, he copies the HCM planning data to the P&L
planning side.
Process Flow Diagram
HCM Planning

Start of
Event

HCM End of HCM

Planning Planning
Process Process
HR Staff

Plan Salary Plan Welfare, HCM Planning HCM Planning

Benefit and Data Submit for Data
and Bonus Confirmation Approval
Pension Adjustment

No
Planner
Budget

App HCM Planning

rove BPF
d? YES Complete
Legend

Symbol Description Usage Symbol Description Usage Comments

Comments

Band: Identifies a user role, such as Accounts Role band To next / From last Diagram: Leads Flow chart continues on the next /
to the next / previous page of the previous page
<Function>

Payable Clerk or Sales Representative. This band contains tasks

Diagram
can also identify an organization unit or group, common to that Diagram
rather than a specific role. role. Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to
cover all of the roles in the scenario.
Hardcopy / Document: Identifies a Does not correspond to a task
External Events: Contains events that start or end the printed document, report, or form step in a document; instead, it is
used to reflect a document
Hardcopy /
External

scenario, or influence the course of events in the generated by a task step; this
to SAP

scenario. Document shape does not have any outgoing

flow lines

Flow line (solid): Line indicates the normal sequence Connects two
tasks in a Financial Actuals: Indicates a Does not correspond to a task
of steps and direction of flow in the scenario. scenario financial posting document step in a document; instead, it is
Flow line (dashed): Line indicates flow to infrequently- process or a used to reflect a document
used or conditional tasks in a scenario. Line can non-step event Financial generated by a task step; this
Actuals shape does not have any outgoing
also lead to documents involved in the process flow. flow lines

Business Activity / Event: Identifies an action that Does not

Business either leads into or out of the scenario, or an outside correspond to a Budget Planning: Indicates a Does not correspond to a task
Process that happens during the scenario task step in the budget planning document step in a document; instead, it is
Activity / document
Event used to reflect a document
Budget generated by a task step; this
Planning shape does not have any outgoing
flow lines
Unit Process: Identifies a task that is covered in a Corresponds to
step-by-step manner in the scenario a task step in
Unit Process the document
Manual Process: Covers a task Does not generally correspond to
that is manually done a task step in a document;
Manual instead, it is used to reflect a task
Proces that is manually performed, such
Process Reference: If the scenario references another Corresponds to as unloading a truck in the
scenario in total, put the scenario number and name a task step in s warehouse, which affects the
Process here. the document process flow.
Reference

Existing Version / Data: This block Does not generally correspond to

Sub-Process Reference: If the scenario references Corresponds to covers data that feeds in from an a task step in a document;
another scenario in part, put the scenario number, a task step in Existing external process instead, this shape reflects data
Sub- name, and the step numbers from that scenario here the document Version / coming from an external source;
Process Data this step does not have any
Reference incoming flow lines

Process Decision: Identifies a decision / branching Does not

point, signifying a choice to be made by the end usually
Proces
user. Lines represent different choices emerging correspond to a
s from different parts of the diamond. task step in the
Decisio document;
n Reflects a
choice to be
made after step
execution
System Pass / Fail Decision: This Does not generally correspond to
System block covers an automatic a task step in the document;
Pass/F
decision made by the software instead it is used to reflect an
ail automatic decision by the system
Decisio that is made after a step has been
n executed.