Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
R=responsible
A=approve
T&M=service provided at additional costs
I=inform
P=participate
F=future plan (currently not available, can not be offered)
CS=cloud support
EC=employee central
PM=Product management
BAS_00.000 General
BAS_00.001 Ensure compliance with financial and privacy regulations in context of system usage and R all on-going
operation (customizing, parameterization, user authorization etc.)
BAS_00.002 payroll system and data location is Germany, Australia or USA R I all
BAS_00.003 provide dedicated customer contact R (CS) all only support counterpart, no dedicated operation counterparts
(interaction via tickets planned)
BAS_00.004 regular customer communication/service review R (EC) all customer service communication driven from EC side
BAS_00.005 location of operation teams R all no local operation, operation mainly out of india
BAS_00.006 SAP integrates supplier personnel in operation teams R all administrators are not SAP employees only
BAS_00.007 weekly maintenance window for payroll operations R R all on-going SAP Cloud Operations has a weekly maintenance window of 4h
for system and infrastructure maintenance. During this time
customer cannot expect system uptime (downtimes are not SLA
relevant) and should not schedule payroll runs. There are 3
windows and customer can choose between those, default is the
window which fits time zone of customer location best:
AMERICA: SA 05:00–09:00 UTC; EUROPE: SA 00:00–04:00
UTC; AUSTRALIA: FR 14:00–18:00 UTC
There is no customer communication taking place if this
maintenance window is used.

BAS_00.008 further weekly maintenance window for BSI related maintenance R R all on-going only if BSI SaaS integration for US payroll is used, BSI
maintenance window is currently Saturdays between 12:01 and
7:00 AM US Easter Time; time schedule could be changed by
BSI in the future
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_10.000 Implementation
BAS_10.100 Overall
BAS_10.101 create and maintain implementation plan R all one time no implementation support by SAP Cloud Operations
BAS_10.102 s-user creation and rights assignment for EC payroll installation number R P one time SAP needs an s-user for the EC payroll installation number
under customer ID, customer to add the following rights to this s-
user:
• Confirm customer messages
• Create customer messages
• Display system data
• Maintain system data
• Maintain my logon data
• Open Serviceconections
• Register object keys
• Register object and Developer keys
• Request license keys
• Reserve namespases
• Send customer messages to SAP
• Software download
BAS_10.200 Sizing and procurement
BAS_10.201 sizing the system landscape R P/A (PM) all service start-up, or based on customer seats and provided sizing figures
new systems
BAS_10.202 solution landscape design R P/A (PM) all service start-up, or
new systems
BAS_10.203 hardware procurement R all service start-up, or
new systems
BAS_10.204 procurement of operating system software license R all service start-up, or
new systems
BAS_10.205 procurement of database license R all service start-up, or
new systems
BAS_10.300 Network management & access
BAS_10.301 provide technical network infrastructure (customer side) R all service start-up IPSEC VPN infrastructure (SAProuter, VPN Device, firewalls),
Devices for internet connectivity and IDM/IDP if needed

BAS_10.302 provide technical network infrastructure (SAP Cloud side) R all service start-up VPN Device, SAProuter, Loadbalancer with whitelist which
restricts webaccess to defined ICF nodes
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_10.303 VPN setup for system access via SapGui/SAPRouter R R all service start-up VPN is for SAPGui mainly and can be also used for RFC
integrations with on premise systems in customer network, all
other integration scenarios have to use internet connectivity
(https, webservice). Network experts from both sides needed for
VPN setup (SAP Cloud Operations will provide VPN
questionnaire and VPN diagrams).
Standard is only one VPN connection between customer
network and SAP.

BAS_10.304 certificate handling for based external (B2A), certificate based communications R (opt.) P all service start-up standard certificates are included, customer to provide and
request add. required certificates, SAP Cloud Operations to
maintain accordingly
BAS_10.400 Security planning
BAS_10.401 determine security requirements R all on-going infrastructure & technical system components only
BAS_10.402 create and maintain security policies R all on-going
BAS_10.403 determine security strategy and implementation plans R all on-going
BAS_10.500 Storage management
BAS_10.501 Develop storage management architecture (Filer, Raid level, Striping, SAN/NAS design etc) R all service start-up, or based on published SAP Guidelines
new systems
BAS_10.502 define initial data file, file system and disk management standards R all service start-up, or based on published SAP Guidelines
BAS_10.600 Operating system administration new systems
BAS_10.601 define operating system security requirements R all service start-up, or
new systems
BAS_10.602 installation of operating system, current patches and additional operating system components R all service start-up, or version: Suse Linux 2.6.32.59-0.7-xen
new systems
BAS_10.603 implement operating system security controls R all service start-up, or
new systems
BAS_10.604 application server up and download all not possible as customer does not have OS access
BAS_10.700 Installation and configuration of SAP solution
BAS_10.701 installation and configuration of database and SAP software as described in the SAP R all service start-up, or EHP7 for SAP ERP 6.0 plus EA-HR608 and EC Integration
installation guide of the respective component new systems AddOn PA_SE_IN 100; MaxDB
BAS_10.702 create initial customer clients R all service start-up, or one customer client (100) per system
new systems
BAS_10.703 configuration of SAP transport management system R all service start-up, or standard TMS settings D-Q-P; customer can modify/request
new systems specialities (f.e. fixed transport cycles etc.) later on if needed
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_10.704 configure output management R P all service start-up, or outbound email and ADS will be configured
new systems
BAS_10.705 configuration of SAP payroll system (application) R all on-going
BAS_10.800 System startup/shutdown
BAS_10.801 define startup/shutdown schedule R all service start-up, or maintenance window: first 4h of EC window [SA00:00-SA04:00
new systems in UTC+2, UTC-5 or UTC+8], details see BAS_00.007

BAS_10.802 define startup/shutdown procedures for payroll system R all service start-up, or
new systems
BAS_10.900 Backup/Restore management
BAS_10.901 define backup policy R all service start-up, or per SAP Cloud Operations service standards
new systems
BAS_10.902 schedule regular backups for new payroll systems R all service start-up, or per SAP Cloud Operations service standards
new systems
BAS_11.100 User management
BAS_11.101 define new customer user request and approval procedures R all service start-up, or With system handover SAP Cloud Operations will provide an
new systems initial customer user; all further customer user handling is in
customer responsibility (rules see integration handbook); please
also consider best practices published on service market place
e.g. not to have Dev users in Prod, have limited and restrictive
transport rights etc.

BAS_11.102 definition and creation of customer users and authorizations R all on-going As there are no restrictions beyond user name convention and
user group (see integration handbook) customer can
theoretically contradict SAP´s basis operations. In this case,
SAP can not take any liability on SLAs and compliance.
Customer is responsible for eventual manipulations.

BAS_11.103 assignment of Development keys to customer users R on-going customer to create Development keys for single customer users
in SAP service marketplace
BAS_11.104 configure external user management tool and integrate with EC payroll systems R service start-up Only SAP IDM is allowed as external user management tool. In
addition you can create users manually, by using a User
Creation Report (see Integration Documentation, chapter 4.2).

BAS_11.105 design, implementation and functionality check of the basis administration roles R all service start-up
BAS_11.106 definition and creation of basis users R all service start-up
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_11.107 setup initial passwords for SAP Cloud admin user and SAP delivered users R all service start-up, or SAP retains exclusive control of these special users
new systems
BAS_11.200 Print management
BAS_11.201 enabling of frontend printing for payroll- and HR-admin R P all service start-up customer to download latest SAPGUI and use report RSPO0075
to add access method “G”; enduser printing (f.e. payslip) via EC

BAS_11.202 printserver provisioning (customer side) R all service start-up customer to provide printserver (and configure SAP router and
EC Payroll accordingly) in case frontend printing is not sufficient

BAS_11.203 cheque or high volume payslip printing incl. franking R all customer has to integrate a partner for this service
BAS_11.300 Event detection and notification
BAS_11.301 define hardware monitoring requirements R all service start-up
BAS_11.302 define operating system monitoring requirements R all service start-up
BAS_11.303 define SAP basis monitoring requirements R all service start-up
BAS_11.304 define database monitoring requirements R all service start-up
BAS_11.305 define Application monitoring requirements R all
BAS_11.306 define 3rd party software monitoring requirements R all SAP Solution Manager is used by SAP Cloud Operations for
BAS_11.300.
It is not possible to connect EC payroll systems to an additional
customer SAP Solution Manager.

BAS_11.307 define event notification and escalation procedures (non application part) R P all service start-up customer to provide technical contact information; support ticket
process
BAS_11.400 Migration projects / Data upload
BAS_11.401 new empty payroll system installation R service start-up, or there is no a system migration done, data upload in customer
new system responsibility with standard upload features
BAS_11.402 planning and coordiantion of data migration/upload projects R all
BAS_11.403 cordination of interfaces with 3rd party service provider R all
BAS_11.404 upload/import of data R all via standard tools (RFC, transports etc.)
BAS_11.500 Functionality check of complete solution
BAS_11.501 test SAP software installation (basis) R all service start-up
BAS_11.502 test SAP software installation (application solution) R all
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_11.600 Setup integration to other systems
BAS_11.601 connecting payroll system via Boomi with EC system P (Dev/ R service start-up or all integration steps which have to be performed initially and
PM) new systems; regularly by the customer (incl. Boomi content mapping) are
ongoing documented in integration handbook.
Besides the initial setup, also responsible for the regular
maintenance of the used integration packs.

BAS_11.602 connecting payroll systems to BSI Saas system R service start-up, or customer to buy BSI Saas solution; according integration via
new systems webservices; integration handbook provided by SAP showing
how this is done
BAS_11.603 connection to check or high volume print partner R service start-up, or
new systems
BAS_11.604 connecting payroll systems to other systems R service start-up, or there are 2 payroll integration options: 1.) webservice via
new systems internet (https) 2.) RFC based via VPN and SAP router -
recommendation is to go for 1.) as webgui might replace VPN in
future
BAS_11.700 Customer Developments or partner extensions
BAS_11.701 customer can Develop new objects in defined areas (NO modification of existing objects R Dev allowed areas are: new payroll functions, payroll operations, new
allowed!) custom tables, new custom infotypes, new fields for SAP-
defined infotypes with customer-include, new reports, BADI
implementations. Anything that could raise conflicts during
upgrade or patch is not allowed. This means also using "implicit
enhancement points" or applying notes that include
modifications that are not part of a future Support package (such
notes are for On Premise and must not be applied in the hosted
payroll system).
The development rights assigned to a customer may
theoretically allow the customer to circumvent the
aforementioned restrictions.
Should SAP determine that modifications are made outside of
the allowed areas mentioned above, SAP cannot be held
responsible for adhering to the agreed SLA for EC Payroll. In
such cases, the customer is responsible for all such
modifications and their consequences.
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_11.702 standard partner payroll extension development (Add-Ons, tools) R Dev/all only payroll related extensions like payroll reporting, statutory
reports or test tools (see note 2167337).
Must be: in partner/customer namespace, no interference with
SAP standard, no impact on sizing and performance.

BAS_11.703 import & installation (via TMS or SAINT) of partner extensions (Add-Ons, tools) P R only payroll related extensions like payroll reporting, statutory
reports or test tools; customer has to upload
transport/installation files plus documentation via ticket, SAP
Cloud imports/installs on behalf. Before you request the
installation of a partner add-on, please read note 2167337.

BAS_11.800 BSI TaxFactory implementation and integration

BAS_11.801 BSI SaaS service license for BSI TaxFactory PM R all one time only if BSI SaaS integration is needed for US payroll; customer
to license BSI SaaS cloud access from SAP/SF as reseller

BAS_11.802 Payroll integration with BSI SaaS solution R all service start-up BSI SaaS solution integrates via webservice with payroll

BAS_11.803 payroll system prerequisites for BSI SaaS solution integration R all service start-up, or SAP_HRCUS with min. PL 64; SAP Cryptographic Library
new systems (SAPCRYPTOLIB) with min. PL 35; Go Daddy Inc. certificat
used by BSI
BAS_11.804 integration configuration R all service start-up, or based on BSI integration guide provided by PM in SAP service
new systems market place
BAS_11.805 BSI SaaS instance and payroll systems configuration for BSI usage R all on-going e.g. filling experience rates in BSI SaaS instance
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_20.000 Operation
BAS_20.100 Physical site management
BAS_20.101 test environmental control plans periodically R all regularly
BAS_20.102 manage physical site R all on-going
BAS_20.200 Network management & access
BAS_20.201 network monitoring R R all on-going customer is responsible for the parts on his side
BAS_20.202 system access maintenance R R all on-going customer is responsible for the parts on his side
BAS_20.203 related network Device operation R R all on-going customer is responsible for the parts on his side
BAS_20.300 Security planning - site security
BAS_20.301 determine security requirements R all on-going
BAS_20.302 create and maintain security policies R all on-going
BAS_20.303 determine security strategy and implementation plans R all on-going
BAS_20.304 generate and disseminate reports on security plans R all as needed
BAS_20.305 monitor and assess security strategies R all as needed
BAS_20.400 Hardware operations
BAS_20.401 maintain valid vendor maintenance agreements as needed R all on-going for SAP managed equipment; as required to support overall
system SLA
BAS_20.402 use vendor proactive support capabilities to help identify potential failures R all as needed for SAP managed equipment
BAS_20.403 schedule hardware maintenance (for hardware failures and planned modifications) R I all as needed for SAP managed equipment, typically virtualization moves -
repair in background, customer information if downtime outside
our maintenance window needed

BAS_20.404 schedule hardware/equipment maintenance as recommended by vendors R I all on-going for SAP managed equipment, typically virtualization moves -
repair in background, customer information if downtime outside
our maintenance window needed

BAS_20.405 monitor hardware R all on-going

BAS_20.406 execute change requests as required for hardware upgrades, additions etc. R all as needed internal change requests; for external change requests additinal
BAS_20.407 hardware exchange R all as needed if required due to provider reasons
BAS_20.500 Storage management
BAS_20.501 manage data files, file systems, and disks/storage systems per standards R all as needed
BAS_20.502 create file systems and/or logical volumes or NFS shares R all as needed
BAS_20.503 create file directories on OS level (in payroll landscape, outside DB) for customer usage R (opt.) P all on request to be requested via ticket, details on possible path and access
are described in integration handbook
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_20.600 Operating system
BAS_20.601 maintain operating system users as necessary R all as needed SAP access only, no access to operating system by customer

BAS_20.602 maintain groups of users R all as needed

BAS_20.603 report on security effectiveness periodically R all audit cycles infrastructure participates in regular audits, audit result
BAS_20.604 configure operating system parameters R all as needed
BAS_20.605 troubleshoot operating system problems, monitor system log and file systems R all as needed
BAS_20.606 work with hardware vendor to resolve operating system issues R all as needed
BAS_20.607 monitoring swap- and page areas R all on-going
BAS_20.608 monitoring memory load R all on-going
BAS_20.609 apply patches to the operating system R all as needed mainly security updates
BAS_20.610 perform operating system upgrades R all as needed if required for SAP Cloud Operations (typically via new VM and
move)
BAS_20.700 System startup/shutdown
BAS_20.701 perform scheduled startup/shutdown of hardware and OS R all as needed
BAS_20.702 perform scheduled startup/shutdown of OS, for SAP software R all as needed
BAS_20.703 perform ad-hoc startup/shutdown of SAP software R I all as needed customer informed if outside regular maintenance windows

BAS_20.704 restart the hardware/OS after failure R all as needed

BAS_20.705 restart SAP software after failure R all as needed
BAS_20.800 Backup & restore
BAS_20.801 perform application filesystem backups R all on-going per SAP standards: full snaphost per day, permanent logging

BAS_20.802 maintain secondary backup storage system R all on-going full snapshot transfer per day, logs every 2h
BAS_20.803 restore a file or multiple files from the backup media R / T&M A all as needed if caused by customer, additional charges apply
BAS_20.804 restore complete file system or incremental file system backup as needed after system R / T&M A all as needed if caused by customer, additional charges apply
failures
BAS_20.805 notify requestor that restore has been completed R I all as needed
BAS_20.806 notify users that restore has been completed R all as needed
BAS_20.807 rework and validate logical integrity and consistency of restored system R all as needed re-sync of user master data for lost time, rework of business
BAS_20.808 test backup/restore procedures periodically R all regularly inconsistencies needed and restart standard replication
per SAP guidelines
BAS_20.900 Database management
BAS_20.901 plan and perform extensions via autoextend R all as needed
BAS_20.902 monitor database free space R all on-going
BAS_20.903 monitor database log files R all on-going
BAS_20.904 analyze and resolve database failures R all as needed
BAS_20.905 schedule periodic statistical database collectors (DB13 job once per day) R all on-going
BAS_20.906 optimize database, maintain database parameters R all as needed
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_20.907 start/stop database R all as needed
BAS_20.908 create and check optimizer statistics (DB13 jobs via monitoring) R Prod on-going
BAS_20.909 perform database software updates R all as needed
BAS_21.100 SAP basis administration
BAS_21.101 analyze SAP system basis logs and fix failures R all regularly
BAS_21.102 monitor update mechanism R all regularly technical functionality
BAS_21.103 check for basis ABAP dumps R all regularly
BAS_21.104 schedule, monitor and maintain standard SAP basis system jobs R all regularly
BAS_21.105 optimize SAP system (system basis tuning) R all as needed
BAS_21.106 maintain SAP system profile parameters R all as needed
BAS_21.107 manage basis and admin users and roles R all as needed
BAS_21.200 SAP system & client operations
BAS_21.201 additional client creation R R Dev/QA on request Customer can request via ticket one additional client in Dev
system and two additional clients in QA. If the new client shall be
copied from an existing client, a 4h downtime window for the
source client has to be provided in the ticket.
During the critical time shortly before Go-Live customer might be
allowed (by PM) to request some additional (QA) clients for a
limited period of time.

BAS_21.202 client refreshes R R all on request Customer can request via ticket up to 3 client refreshes per
quarter (refresh = copy new client from master or an existing
client to another existing client number, e.g. Prod -> QA). If the
source client is an existing customer client, a 4h downtime
window has to be provided in the ticket.

BAS_21.203 system copies of existing systems all system copies are not performed
BAS_21.204 additional systems all until further notice, additional systems cannot be requested, only
the three standard systems (Dev, QA, Prod) are supported

BAS_21.300 SAP version updates

BAS_21.301 mandatory quarterly update of ERP EC Integration AddOn (PA_SE_IN) R all quarterly (PAY SAP Cloud Operations will update the integration AddOn in
Dev/QA 1 week regular maintenance window upfront EC update and send
before and PAY information update to customer; no customer interaction needed
PRD with EC
update)
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_21.302 import urgent security notes, technical notes or kernel patches required for operations R all as required SAP Cloud Operations will import prio 1 security notes, technical
notes or kernel patches if required for operations in the weekly
maintenance window; no customer interaction needed

BAS_21.303 Payroll ERP patching incl. legal payroll patch import P P (PM) R all as required Customer has to check in service market place which patches
(incl. legal) are available and to judge if needed: Patch can
either be applied by customer himself or by SAP Cloud
operations (recommended). In the latter case customer has to
request patching via ticket, provide a downtime plus perform pre
and post patching steps; details see patch process. If a patch
can't be applied by customer himself because of modifiability
settings of the system, appliance has to be requested by ticket.
If patch is applied by SAP, customer has to request explictely
the systems in which the patch has to be applied.
Recommendation is to ask to apply a patch in DEV/Q first and
after successfull test ask to apply the test to PROD.

BAS_21.304 Mandatory upgrade of ERP Core and Renewal R P (PM) P all as required (about Upgrade of the ERP-Core and the Renewal-Package will be
once a year) triggered and done by SAP. SAP will only implement packages
that are in general availability. SAP will notify the customer
beforehand and request him to create a ticket. The desired
upgrade date for DEV-system has to be within three months
after the upgrade-date proposed by SAP.
Quality and Productive System will be upgraded latest 4 weeks
later each (customer has to confirm within this timeframe the
successfull test of the previously upgraded system).
Additional Downtime might be needed for the upgrade.
Dependent from the functionality of the new release,
adjustments in customers' systems (e. g. customizing) might be
necessary.
In any case, customer needs to test in DEV and Q before
upgrade in PROD is done
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_21.400 Customer user management
BAS_21.401 create new customer users R all as needed customer users have to be in group customer and following the
nameconvetion (see handbook); SAP Cloud Operations retains
control of all other (technical) users

BAS_21.402 user profile, master data, and password maintenance R all as needed
BAS_21.403 add/change/delete/lock/unlock user master records R all as needed
BAS_21.404 maintain activity groups R all as needed
BAS_21.405 unlock users in SAP system R all as needed
BAS_21.406 reset passwords R all as needed
BAS_21.407 checking authorizations R all as needed
BAS_21.408 define and maintain custom profiles R all as needed
BAS_21.500 Application management
BAS_21.501 application job management R all on-going define business requirements govering job schedule; define job
BAS_21.502 monitor update processes and fix update terminations R all regularly dependencies and parameters;
typically expressmail distribute
or pop-up during and adjust schedule to
usage
BAS_21.503 check for application ABAP dumps R all regularly
BAS_21.504 monitor SAP payroll application and payroll processes R all on-going

BAS_21.505 identify end-user performance problems R Prod as needed

BAS_21.506 provide application performance analysis (e.g. ABAP) R Prod as needed performance of payroll rules in customer ownership

BAS_21.507 archiving of customer data (e.g. Payroll results) R prod as needed archiving is in customer responsibility, no SAP solution offered

BAS_21.600 Change control

BAS_21.601 document and maintain transport request & execution procedures R all service start-up, or transport process and content in customer responsibility
new systems only

BAS_21.602 transport creation and release of transport orders (incl. documentation) R all as needed customer owns transport management; SAP recommends to set
up an approval hierarchy on customer side (e.g. to avoid
conflicts between transport and patch requests)

BAS_21.603 carry out transports P R all as needed customer is responsible to import the transports into his
systems; SAP Cloud Operations can support on request (ticket)
in case of problems with transports
BAS_21.604 check transport protocols R all as needed to be checked by transporter
BAS_21.605 address technical transport problems R R all as needed by transporter via ticket
BAS_21.606 address functional transport problems R all as needed
BAS_21.607 test and acceptances of transport R all as needed
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_21.608 apply SAP notes P R all as needed customer is responsble for applying notes himself, SAP Cloud
Operations can support in case of problems with notes
application

BAS_21.609 language imports R all as needed standard languages imported with intial setup; further languages
to be requested by customer via ticket
BAS_21.700 Print management
BAS_21.701 maintain printers (within SAP software) R all as needed customer to maintain printer in payroll system (transaction
SPAD) based on his print(server) information

BAS_21.702 analyze faulty output requests R all as needed printer config & maintenance in customer responsibility
BAS_21.703 provision and set-up for pre-printed forms (including design) R all as needed printer config & maintenance in customer responsibility

BAS_21.704 troubleshooting spool- and print-problems (within SAP system) R P all as needed via tickets
BAS_21.705 troulbeshooting external volume and queue printing R all as needed interface and external provider
BAS_21.800 Integration management
BAS_21.801 technical integration monitoring (EC payroll - employee central) R all on-going component monitoring and connection test
BAS_21.802 technical integration monitoring (EC payroll - foreign system) R all on-going
BAS_21.803 maintain technical integration settings R all as needed maintained connections in SOA Manager etc.
BAS_21.804 monitor application integration R all on-going application logs in EC payroll, alerts in Boomi/XI/HCI or in
connected system (f.e. EC)
BAS_21.900 Customer Developments or partner extensions
BAS_21.901 Development extensions updates R on-going incl. adaptations to fit latest SAP version (SAP Cloud Operations
patching does not consider these extensions)

BAS_21.902 import & patch of partner extensions (via TMS or SAINT) P R customer has to upload transport/installation files plus
documentation via ticket, SAP Cloud Operations
imports/patches on behalf
BAS_21.903 Development extensions maintenance and support R on-going
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_22.100 BSI TaxFactory maintenance (USA only)
BAS_22.101 BSI TaxFactory SaaS and BSI eFormsFactory server maintenance BSI Up to weekly TaxFactory does the net tax calculation. eFormsFactory allows
employees and admins on-behalf of employees to file payroll
withholding certificates (a.k.a., W-4).
BSI may perform maintenance activities Saturdays between
12:01 and 7:00 AM US Easter Time. Typically, Development
and Quality are updated in the 3rd Saturday of the month with
Production one week later on the 4th Saturday. Additional
updates likely at year-end/year-begin. This is an update of a
SaaS server shared with other EC Payroll customers and
updates cannot be scheduled/delayed based on any one
customer. Customers may obtain details regarding update from
their myBSI portal.

BAS_22.102 BSI TaxFactory and eFormsFactory SaaS user creation/maintenance BSI, P P on-demand Customers supply up to 4 contacts to be registered as BSI SaaS
users/support contacts at time of order/registration. Subsequent
changes are done via SF Cloud Support ticket that will be routed
to BSI who will then contact customer.

BAS_22.103 BSI customer data backup/restore BSI R on-demand Designated BSI users may backup/restore customer specific
(moving between environments, e.g., DEV -> QA -> PROD) data in one TaxFactory environment, such as DEV, and restore
in QA. Typically customers will do this themselves but may also
request BSI to do on their behalf. Registered BSI support
contacts can enter a SF Cloud Support ticket that will be routed
to BSI who will then perform request. Number of requests
fulfilled by BSI may be limited.

BAS_22.104 Maintenance of Tax Update Bulletin (TUB) relevant tables in Employee Central Payroll R all up to weekly, Certain TUB related tables in the payroll system must be kept in
typically 1x/month: sync with the BSI SaaS server. SAP SuccessFactors supplies a
DEV: 3rd Saturday; tool called Synchronize Payroll Tax Data, program
PROD: 4th RPUPAYUS_SYNC_TAX_DATA, transaction
Saturday HRPAYUS_SYNC_TAX_DT. It is recommended that customers
schedule this to run as a reoccurring batch job in each
environment/client where payroll is run. Customers not wanting
to run program in Production may also use a transport method.
Details and current limitations can be found in the user guide:
http://service.sap.com/~sapidb/011000358700000237052014E
 Service Description for Payroll Landscape Application Hosting (EC-Payroll Offering)

service description SAP Cloud other Customer relevant frequency remarks

Operations SAP/SF Payroll
unit Systems
BAS_30.000 Customer support center
BAS_30.100 Problem & service request management
BAS_30.101 standard support ticket handling functionality (tacking, prio, escalation, updates): P R (CS) all on-going via EC support process; same support process for EC/Boomi
subcomponent responsibilty for operations and payroll; payroll issues should be opened via:
https://launchpad.support.sap.com/#/incident/create
Choose Product 'SFSF' and Sub-Product ‘Employee Central &
Cloud/EC Payroll’

BAS_30.200 SAP basis event detection and notification

BAS_30.201 monitor console for event notification R all on-going
BAS_30.202 detect events per monitoring requirements R all on-going
BAS_30.203 log events R all on-going
BAS_30.204 react to events according to event notification and escalation procedures R P all as needed
BAS_30.205 monitor the success/failure of the startup/shutdown processes R all as needed
BAS_30.206 monitor backup processes (use SAP backup tools) R all on-going