Sei sulla pagina 1di 6

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 /
Payable Clerk or Sales Representative. This band contains tasks to the next / previous page of the previous page
<Function>

can also identify an organization unit or group, common to that Diagram


rather than a specific role. role. Diagram
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
scenario, or influence the course of events in the Hardcopy /
External

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

Business Activity / Event: Identifies an action that Does not


either leads into or out of the scenario, or an correspond to
Business outside Process that happens during the scenario a task step in Budget Planning: Indicates a Does not correspond to a task
Activity / the document budget planning document step in a document; instead, it is
Event used to reflect a document
Budget generated by a task step; this
shape does not have any
Planning 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
that is manually performed, such
Process Reference: If the scenario references Corresponds to Proces as unloading a truck in the
another scenario in total, put the scenario number a task step in s warehouse, which affects the
Process and name 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- coming from an external source;
name, and the step numbers from that scenario here the document Version / this step does not have any
Process Data incoming flow lines
Reference

Process Decision: Identifies a decision / branching Does not


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

Potrebbero piacerti anche