{"id":4691,"date":"2020-10-02T10:52:00","date_gmt":"2020-10-02T08:52:00","guid":{"rendered":"https:\/\/integrtr.com\/?p=3000"},"modified":"2022-07-01T15:18:32","modified_gmt":"2022-07-01T09:48:32","slug":"sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert","status":"publish","type":"post","link":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-what-really-happens-to-employee-data-during-go-live\/","title":{"rendered":"SF EC to SAP HCM Core hybrid: Was passiert wirklich mit den Mitarbeiterdaten beim Go-Live?"},"content":{"rendered":"\n<h3 class=\"wp-block-heading\">Introduction:<\/h3>\n\n\n\n<p>Customers choose SuccessFactors Employee Central, EC from hereon, for a myriad of reasons. The most common amongst those is the creation of a Global HR system. Global HR system creates the necessary boundary between HR functions and non-HR utility functions like Payroll\/Time etc. Whilst such a boundary is great for business, it breaks the Hire to Pay business process into two systems \u2013 this necessitates an integration.<\/p>\n\n\n\n<p>With EC earmarked as the global HR system, employees are hired and terminated from this system. If the Payroll system is an SAP payroll system, the integration goes through a well established integration pattern called the \u201cCore Hybrid\u201d Integration. This integration is supported by a time tested yeomanly infrastructure called the Business Integration Builder (BIB) that comes with the add-on PA_SE_IN. Much has been discussed and debated about BIB on this forum and elsewhere. The focus of this blog is not about the intricacies of BIB, but rather how SAP has designed BIB to behave during go-live.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img decoding=\"async\" src=\"https:\/\/blogs.sap.com\/wp-content\/uploads\/2020\/09\/Screenshot-2020-09-28-at-3.53.57-PM.png\" alt=\"\"\/><\/figure>\n\n\n\n<p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [Image source: Self made]<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">BIB supports both Migration and integration:<\/h3>\n\n\n\n<p>Customers going live often start their go-live process with a migration from SAP HCM to EC followed by a subsequent integration load from EC to SAP HCM.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Entities commonly involved in the go-live process:<\/h4>\n\n\n\n<ol class=\"wp-block-list\"><li>Org Objects \u2013 Business Unit, Division, Department, Team, custom objects<\/li><li>Positions<\/li><li>Jobs<\/li><li>Employees<\/li><li>Interlinked associations<\/li><\/ol>\n\n\n\n<h4 class=\"wp-block-heading\">User Persona:<\/h4>\n\n\n\n<p><strong>Mary Mustermann:&nbsp;<\/strong>Is an example persona that we will use through-out this blog to articulate the migration\/integration runs. Mary has been working for nearly 30 years now. The table shows her job slices (drawn from infotypes 0000\/0001 on SAP HCM.)<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><tbody><tr><td><strong>Event<\/strong><\/td><td><strong>Start Date<\/strong><\/td><td><strong>End Date<\/strong><\/td><\/tr><tr><td>Hire<\/td><td>01.01.1991<\/td><td>31.12.1998<\/td><\/tr><tr><td>Data Change<\/td><td>01.01.1999<\/td><td>31.08.2002<\/td><\/tr><tr><td>Data Change<\/td><td>01.09.2002<\/td><td>31.12.2014<\/td><\/tr><tr><td>Data Change<\/td><td>01.01.2015<\/td><td>31.12.2018<\/td><\/tr><tr><td>Data Change<\/td><td>01.01.2019<\/td><td>31.12.2021<\/td><\/tr><tr><td>Data Change<\/td><td>01.01.2022<\/td><td>31.12.9999<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Migration :<\/h3>\n\n\n\n<p>Migration brings in data from SAP to SF via SAP Infoporter (BIB). Migration brings in only restricted historical data. It\u2019s recommended not to go too far into the history during migration.&nbsp;<strong>The extent of data that\u2019s brought in via migration is controlled with the cut-off date<\/strong>.It\u2019s prudent to bring in as little baggage as possible \u2013 so, the cut-off date should not be too far away in the past from the date of run.<\/p>\n\n\n\n<p>Migration has two types of runs: full migration and delta migration run.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Full migration run brings in all data from the cut-off date to the high-date<\/strong>. After the migration run, the SF system is expected to become the master data of records system.<\/li><li>When that doesn\u2019t happen (e.g. deferred go-live where customers take one legal entity at a time to the cloud) data on SAP continues to grow thereby rendering data on SF stale.<\/li><li>To solution such a scenario, delta migration is used where only the delta between SAP from date of first migration run is replicated.<\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Migration deep dive:<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li>Let\u2019s say<strong>&nbsp;Migration<\/strong>&nbsp;run has a&nbsp;<strong>cut-off date<\/strong>&nbsp;of 01.<strong>01.2021.<\/strong><\/li><li>On the date of migration, all objects (O\/S\/P\/C\/\u2026) are replicated from SAP to SF. Org objects go in without much fan-fare. Therefore, our focus is on the employee.<ol><li>All employee records whose end-date is less than the cut-off date is ignored<\/li><li>All future dated employee records are replicated as is.<\/li><li>The employee records where the begin date is less than cut-off date and the end date is greater than the cut-off date \u2013 let\u2019s call them current records \u2013 are split at the cut-off date. Only the slice with the cut-off date as the begin date is transferred.<\/li><li>The recruit date on SF is defaulted to the cut-off date. This wrecks Talent Modules. To resolve this, it\u2019s a common practise to bring in an initial job slice for all employees from the hire date till the cut-off date. Whilst doing so, we can either choose to have a dummy mass position on SF or flag the position optional during migration. The latter option allows for employee job migration before cut-off date without a position.<\/li><li>The initial job record thus becomes the initial hire record. The event on this record is H and the event reason can be anything to uniquely denote migration. Can be called \u201cMIGRATION\u201d as well.<\/li><li>In wake of all these information, let\u2019s see how Mary gets migrated.<\/li><li><\/li><\/ol><\/li><\/ul>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><tbody><tr><td><strong>Event<\/strong><\/td><td><strong>Event Reason<\/strong><\/td><td><strong>Start Date<\/strong><\/td><td><strong>End Date<\/strong><\/td><\/tr><tr><td>Hire<\/td><td>MIGRATION<\/td><td><strong>01.01.1991<\/strong><\/td><td><s>31.12.1998&nbsp;<\/s><strong>31.12.2020<\/strong><\/td><\/tr><tr><td><s>Data Change<\/s><\/td><td><s>ignored<\/s><\/td><td><s>01.01.1999<\/s><\/td><td><s>31.08.2002<\/s><\/td><\/tr><tr><td><s>Data Change<\/s><\/td><td><s>ignored<\/s><\/td><td><s>01.09.2002<\/s><\/td><td><s>31.12.2014<\/s><\/td><\/tr><tr><td><s>Data Change<\/s><\/td><td><s>Ignored<\/s><\/td><td><s>01.01.2015<\/s><\/td><td><s>31.12.2018<\/s><\/td><\/tr><tr><td><s>Data Change<\/s><\/td><td><s>Split &amp; ignored<\/s><\/td><td><s>01.01.2019<\/s><\/td><td><s>31.12.2020<\/s><\/td><\/tr><tr><td>Data Change<\/td><td>Data Change<br>Cut-off slice<\/td><td><strong>01.01.2021<\/strong><\/td><td>31.12.2021<\/td><\/tr><tr><td>Data Change<\/td><td>Data ChangeFuture dated slice (comes in as is)<\/td><td>01.01.2022<\/td><td>31.12.9999<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Delta Migration Runs:<\/strong>&nbsp;The actual date of migration run can technically be any date on or after the cut-off date. After the migration run, the entities participating in the integration (O\/S\/P) of the legal entities for which the migration has been done should now be mastered in SF. If not, data continues to grow on SAP necessitating another migration (perhaps delta) run.<\/li><\/ul>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Integration:<\/h3>\n\n\n\n<p>Upon migration, integration runs from SF to SAP. Dubbed the core-hybrid integration, this integration brings in org and employee data regularly to SAP. Akin to migration, integration also starts with a cut-off date.&nbsp;<strong>The integration cut-off date is the date after which data changes are replicated to SAP.<\/strong><\/p>\n\n\n\n<p>Again as with migration, integration also has two types of runs. The very first integration run that levels data between both the systems and subsequent delta replication runs that bring in data on a regular basis. At this stage it\u2019s important to note that:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Delta runs have to be mandatorily preceded by an initial run.<\/li><li>The initial run doesn\u2019t necessarily split infotype records at the cut-off date.<\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integration deep dive:<\/h3>\n\n\n\n<ol class=\"wp-block-list\"><li>Let\u2019s say,&nbsp;<strong>Integration<\/strong>&nbsp;also has a&nbsp;<strong>cut-off date<\/strong>&nbsp;of&nbsp;<strong>01.2021.&nbsp;<\/strong>Integration should have a cut-off date that\u2019s same as migration or later than migration \u2013 certainly not before.<\/li><li><strong>Full Transmission Start Date: FTSD\/Cut Off<\/strong><ol><li>Also known as Cut-off date, this is the date from which data slices are transferred to SAP.<\/li><li>This is infact the cut-off date that\u2019s maintained on the transformation template that\u2019s used to query for EC objects (Employee\/Org\/Position\/\u2026)<\/li><li>The cut-off dates on org and employee templates should be the same.<\/li><\/ol><\/li><li><strong>Initial Run:<\/strong>&nbsp;Initial run is a data levelling run between EC and HCM. Initial run replicates data slices from the FTSD to high date (31.12.9999) for all entities. This is mandatory.&nbsp;<strong>There can\u2019t be a delta run without the initial run.<\/strong><ol><li>Data Slices before FTSD are ignored.<\/li><li>Infotype data slices with begin dates before FTSD and end dates after FTSD are by default NOT cut at FTSD. This is as against popular perception. Whether it gets cut or not is purely based on how identical the data is between SAP and SF. Data is sliced ONLY if data in SF has been worked on\/changed post the last successful delta migration run =&gt; Migrated data is not the same as integrated data.<img decoding=\"async\" src=\"https:\/\/blogs.sap.com\/wp-content\/uploads\/2020\/09\/Picture-1-2.png\" alt=\"\">This picture from SAP documentation is often used to misconstrue that Infotypes will be split at the cut-off date. Infotypes will be split only if the data migrated and the data integrated aren\u2019t the same. SAP has even issued an addendum offering clarity on the same.<br><br><img decoding=\"async\" src=\"https:\/\/blogs.sap.com\/wp-content\/uploads\/2020\/09\/Picture-1-3.png\" style=\"width: 2000px;\" alt=\"\"> &nbsp; &nbsp;[Image source of both images :&nbsp;<a href=\"https:\/\/help.sap.com\/viewer\/a7f164924edd4dfe817b7bdc2fc4927a\/1911\/en-US\/ef916965e1b5483ba2e6dfa2a14a89f0.html\" target=\"_blank\" rel=\"noreferrer noopener\">SAP help documentation<\/a>]<br><\/li><\/ol><ol><li>So, When does the infotype really split?<ol><li>It\u2019s possible to migrate all data for legacy reasons, but integrate only parts of data. E.g. 0009 \u2013 it\u2019s possible that the migration template copies all 0009 fields as is to SF. But, during integration only IBAN and payment mode (e.g.&nbsp;<em>Uberweisung<\/em>) is integrated.<\/li><li>Upon migration, a company-wide employee update is performed e.g. username change. This will result in a split of 0105 on SAP.<\/li><li>A future dated slice freshly created in the SF system (that wasn\u2019t a part of migration) after migration will always lead to an infotype split of the currently effective data slice.<\/li><li>Lastly, if it\u2019s explicitly split on SF with a \u201cFirst Event after Migration\u201d event. Or it\u2019s already split on SAP with a similar event before it\u2019s migrated. Infotype splitting was the norm up until BIB came in. This resulted in retro-payroll issues and downstream interfaces were unnecessarily activated leading to further complications. Hence SAP came up with the initial run concept with BIB that doesn\u2019t necessarily require an explicit infotype split.<\/li><\/ol><\/li><\/ol><\/li><li>So, what else does the initial run actually do?<ol><li>As mentioned earlier, it selectively splits infotype records.<\/li><li>Establishes a last run date for the entities participating in the integration.<\/li><\/ol><\/li><li>What is Last Run Date: LRD<ol><li>The very first last run date is created at the end of the initial run.<\/li><li>Let\u2019s say, the initial run runs on the 1<sup>th<\/sup>&nbsp;Jan 2021 at 13:30, then the LSRD is recorded as 01.01.2021 13:30:00.<\/li><li>During the next run, any delta data growth in EC that occurred after the LSRD is passed on to HCM and again an LRD is recorded. This is used in the subsequent run. Such runs are called Delta Runs.<\/li><\/ol><\/li><li><strong>Delta runs:<\/strong>&nbsp;Explained above, these are runs that occur after initial run. The anchor point for the LRD run is the Initial run and hence the FTSD. Without fixing a FTSD there\u2019s no possibility of a delta run.<\/li><li>At any point in time, if in case needed, the initial run can be run again. This will again refer to the same FTSD. Hence, FTSD is set in stone for an integration. Once set it can\u2019t be changed.<\/li><\/ol>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Final Standing of Mary Mustermann\u2019s Data Slices upon Integration:<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Migration<\/strong><\/td><td><strong>Integration<\/strong><\/td><\/tr><tr><td><strong>Event<\/strong><\/td><td><strong>Event Reason<\/strong><\/td><td><strong>Start Date<\/strong><\/td><td><strong>End Date<\/strong><\/td><td><strong>Event<\/strong><\/td><td><strong>Start Date<\/strong><\/td><td><strong>End Date<\/strong><\/td><td><strong>Comments<\/strong><\/td><\/tr><tr><td>Hire<\/td><td>MIGRATION<\/td><td><strong>01.01.1991<\/strong><\/td><td><s>31.12.1998&nbsp;<\/s><strong>31.12.2020<\/strong><\/td><td>Hire<\/td><td>01.01.1991<\/td><td>31.12.1998<\/td><td>untouched<\/td><\/tr><tr><td><s>Data Change<\/s><\/td><td><s>ignored<\/s><\/td><td><s>01.01.1999<\/s><\/td><td><s>31.08.2002<\/s><\/td><td>Data Change<\/td><td>01.01.1999<\/td><td>31.08.2002<\/td><td>untouched<\/td><\/tr><tr><td><s>Data Change<\/s><\/td><td><s>ignored<\/s><\/td><td><s>01.09.2002<\/s><\/td><td><s>31.12.2014<\/s><\/td><td>Data Change<\/td><td>01.09.2002<\/td><td>31.12.2014<\/td><td>untouched<\/td><\/tr><tr><td><s>Data Change<\/s><\/td><td><s>Ignored<\/s><\/td><td><s>01.01.2015<\/s><\/td><td><s>31.12.2018<\/s><\/td><td>Data Change<\/td><td>01.01.2015<\/td><td>31.12.2018<\/td><td>untouched<\/td><\/tr><tr><td><s>Data Change<\/s><\/td><td><s>Split &amp; ignored<\/s><\/td><td><s>01.01.2019<\/s><\/td><td><s>31.05.2020<\/s><\/td><td>Data Change<\/td><td>01.01.2019<\/td><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;31.12.2021<\/td><td>If data between SF and SAP differ, then there\u2019s a split. It\u2019s possible that some Infotypes split, whilst others don\u2019t.<\/td><\/tr><tr><td>Data Change<\/td><td>Data Change<br>Cut-off slice<\/td><td><strong>01.01.2021<\/strong><\/td><td>31.12.2021<\/td><td>Data Change<\/td><\/tr><tr><td>Data Change<\/td><td>Data ChangeFuture dated slice (comes in as is)<\/td><td>01.01.2022<\/td><td>31.12.9999<\/td><td><\/td><td>01.01.2022<\/td><td>31.12.9999<\/td><td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<p><strong>Conclusion:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>All that is written here is purely based on our (INTEGRTR\u2019s) experiences with LE and upper SME clients.<\/li><li>Our experience with migration is also purely based on SAP\u2019s BIB\/Infoporter. Other migration contrivances like Accenture\u2019s Clone and Test are designed different and could behave different.<\/li><li>Finally, every customer\u2019s path to migration and succeeding integration is unique. Business sensibilities and ground realities dictate and trump all known wisdom.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Introduction: Customers choose SuccessFactors Employee Central, EC from hereon, for a myriad of reasons. The most common amongst those is the creation of a Global HR system. Global HR system creates the necessary boundary between HR functions and non-HR utility functions like Payroll\/Time etc. Whilst such a boundary is great for business, it breaks the [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":4771,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[31,64,39],"tags":[26,25,36,65,42],"class_list":["post-4691","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-integration","category-sap-cpi","category-techtalk","tag-core-hybrid","tag-integration","tag-cpi","tag-sap-hcm","tag-successfactors"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>SF EC to SAP HCM Core hybrid: What really happens to employee data during go-live? - INTEGRTR<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SF EC to SAP HCM Core hybrid: What really happens to employee data during go-live? - INTEGRTR\" \/>\n<meta property=\"og:description\" content=\"Introduction: Customers choose SuccessFactors Employee Central, EC from hereon, for a myriad of reasons. The most common amongst those is the creation of a Global HR system. Global HR system creates the necessary boundary between HR functions and non-HR utility functions like Payroll\/Time etc. Whilst such a boundary is great for business, it breaks the [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/\" \/>\n<meta property=\"og:site_name\" content=\"INTEGRTR\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/integrtr\/\" \/>\n<meta property=\"article:published_time\" content=\"2020-10-02T08:52:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-07-01T09:48:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/integrtr.com\/wp-content\/uploads\/2020\/10\/iStock-915689772-scaled-1200x600-1.jpeg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"600\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Girish Bangalore\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@integrtr\" \/>\n<meta name=\"twitter:site\" content=\"@integrtr\" \/>\n<meta name=\"twitter:label1\" content=\"Verfasst von\" \/>\n\t<meta name=\"twitter:data1\" content=\"Girish Bangalore\" \/>\n\t<meta name=\"twitter:label2\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data2\" content=\"9\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/\"},\"author\":{\"name\":\"Girish Bangalore\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/#\\\/schema\\\/person\\\/2d8324a2d0a6b74bd10b124e88114754\"},\"headline\":\"SF EC to SAP HCM Core hybrid: What really happens to employee data during go-live?\",\"datePublished\":\"2020-10-02T08:52:00+00:00\",\"dateModified\":\"2022-07-01T09:48:32+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/\"},\"wordCount\":1787,\"publisher\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/integrtr.com\\\/wp-content\\\/uploads\\\/2020\\\/10\\\/iStock-915689772-scaled-1200x600-1.jpeg\",\"keywords\":[\"#core hybrid\",\"#INTEGRATION\",\"CPI\",\"SAP HCM\",\"Successfactors\"],\"articleSection\":[\"INTEGRATION\",\"SAP CPI\",\"TechTalk\"],\"inLanguage\":\"de\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/\",\"url\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/\",\"name\":\"SF EC to SAP HCM Core hybrid: What really happens to employee data during go-live? - INTEGRTR\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/integrtr.com\\\/wp-content\\\/uploads\\\/2020\\\/10\\\/iStock-915689772-scaled-1200x600-1.jpeg\",\"datePublished\":\"2020-10-02T08:52:00+00:00\",\"dateModified\":\"2022-07-01T09:48:32+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/#primaryimage\",\"url\":\"https:\\\/\\\/integrtr.com\\\/wp-content\\\/uploads\\\/2020\\\/10\\\/iStock-915689772-scaled-1200x600-1.jpeg\",\"contentUrl\":\"https:\\\/\\\/integrtr.com\\\/wp-content\\\/uploads\\\/2020\\\/10\\\/iStock-915689772-scaled-1200x600-1.jpeg\",\"width\":1200,\"height\":600,\"caption\":\"hand holding jigsaw piece with background of teamwork people connection\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/de\\\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/integrtr.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SF EC to SAP HCM Core hybrid: What really happens to employee data during go-live?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/#website\",\"url\":\"https:\\\/\\\/integrtr.com\\\/\",\"name\":\"INTEGRTR\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/integrtr.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/#organization\",\"name\":\"INTEGRTR GmbH\",\"url\":\"https:\\\/\\\/integrtr.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/integrtr.com\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/integrtr-logo.png\",\"contentUrl\":\"https:\\\/\\\/integrtr.com\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/integrtr-logo.png\",\"width\":364,\"height\":96,\"caption\":\"INTEGRTR GmbH\"},\"image\":{\"@id\":\"https:\\\/\\\/integrtr.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/integrtr\\\/\",\"https:\\\/\\\/x.com\\\/integrtr\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/integrtr\\\/\",\"https:\\\/\\\/www.instagram.com\\\/integrtr\\\/\",\"https:\\\/\\\/www.youtube.com\\\/@integrtr9894\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/integrtr.com\\\/#\\\/schema\\\/person\\\/2d8324a2d0a6b74bd10b124e88114754\",\"name\":\"Girish Bangalore\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0cb86c66063e3f243fa1ca82f612e4c85f8651ddf7dcd1cd6fba0b85d5771e9c?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0cb86c66063e3f243fa1ca82f612e4c85f8651ddf7dcd1cd6fba0b85d5771e9c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0cb86c66063e3f243fa1ca82f612e4c85f8651ddf7dcd1cd6fba0b85d5771e9c?s=96&d=mm&r=g\",\"caption\":\"Girish Bangalore\"},\"url\":\"https:\\\/\\\/integrtr.com\\\/de\\\/author\\\/girish\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"SF EC to SAP HCM Core hybrid: Was passiert wirklich mit den Mitarbeiterdaten beim Go-Live? - INTEGRTR","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/","og_locale":"de_DE","og_type":"article","og_title":"SF EC to SAP HCM Core hybrid: What really happens to employee data during go-live? - INTEGRTR","og_description":"Introduction: Customers choose SuccessFactors Employee Central, EC from hereon, for a myriad of reasons. The most common amongst those is the creation of a Global HR system. Global HR system creates the necessary boundary between HR functions and non-HR utility functions like Payroll\/Time etc. Whilst such a boundary is great for business, it breaks the [&hellip;]","og_url":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/","og_site_name":"INTEGRTR","article_publisher":"https:\/\/www.facebook.com\/integrtr\/","article_published_time":"2020-10-02T08:52:00+00:00","article_modified_time":"2022-07-01T09:48:32+00:00","og_image":[{"width":1200,"height":600,"url":"https:\/\/integrtr.com\/wp-content\/uploads\/2020\/10\/iStock-915689772-scaled-1200x600-1.jpeg","type":"image\/jpeg"}],"author":"Girish Bangalore","twitter_card":"summary_large_image","twitter_creator":"@integrtr","twitter_site":"@integrtr","twitter_misc":{"Verfasst von":"Girish Bangalore","Gesch\u00e4tzte Lesezeit":"9\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/#article","isPartOf":{"@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/"},"author":{"name":"Girish Bangalore","@id":"https:\/\/integrtr.com\/#\/schema\/person\/2d8324a2d0a6b74bd10b124e88114754"},"headline":"SF EC to SAP HCM Core hybrid: What really happens to employee data during go-live?","datePublished":"2020-10-02T08:52:00+00:00","dateModified":"2022-07-01T09:48:32+00:00","mainEntityOfPage":{"@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/"},"wordCount":1787,"publisher":{"@id":"https:\/\/integrtr.com\/#organization"},"image":{"@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/#primaryimage"},"thumbnailUrl":"https:\/\/integrtr.com\/wp-content\/uploads\/2020\/10\/iStock-915689772-scaled-1200x600-1.jpeg","keywords":["#core hybrid","#INTEGRATION","CPI","SAP HCM","Successfactors"],"articleSection":["INTEGRATION","SAP CPI","TechTalk"],"inLanguage":"de"},{"@type":"WebPage","@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/","url":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/","name":"SF EC to SAP HCM Core hybrid: Was passiert wirklich mit den Mitarbeiterdaten beim Go-Live? - INTEGRTR","isPartOf":{"@id":"https:\/\/integrtr.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/#primaryimage"},"image":{"@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/#primaryimage"},"thumbnailUrl":"https:\/\/integrtr.com\/wp-content\/uploads\/2020\/10\/iStock-915689772-scaled-1200x600-1.jpeg","datePublished":"2020-10-02T08:52:00+00:00","dateModified":"2022-07-01T09:48:32+00:00","breadcrumb":{"@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/"]}]},{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/#primaryimage","url":"https:\/\/integrtr.com\/wp-content\/uploads\/2020\/10\/iStock-915689772-scaled-1200x600-1.jpeg","contentUrl":"https:\/\/integrtr.com\/wp-content\/uploads\/2020\/10\/iStock-915689772-scaled-1200x600-1.jpeg","width":1200,"height":600,"caption":"hand holding jigsaw piece with background of teamwork people connection"},{"@type":"BreadcrumbList","@id":"https:\/\/integrtr.com\/de\/sf-ec-to-sap-hcm-core-hybrid-was-wirklich-mit-mitarbeiterdaten-wahrend-der-live-phase-passiert\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/integrtr.com\/"},{"@type":"ListItem","position":2,"name":"SF EC to SAP HCM Core hybrid: What really happens to employee data during go-live?"}]},{"@type":"WebSite","@id":"https:\/\/integrtr.com\/#website","url":"https:\/\/integrtr.com\/","name":"INTEGRTR","description":"","publisher":{"@id":"https:\/\/integrtr.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/integrtr.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/integrtr.com\/#organization","name":"INTEGRTR GmbH","url":"https:\/\/integrtr.com\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/integrtr.com\/#\/schema\/logo\/image\/","url":"https:\/\/integrtr.com\/wp-content\/uploads\/2022\/05\/integrtr-logo.png","contentUrl":"https:\/\/integrtr.com\/wp-content\/uploads\/2022\/05\/integrtr-logo.png","width":364,"height":96,"caption":"INTEGRTR GmbH"},"image":{"@id":"https:\/\/integrtr.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/integrtr\/","https:\/\/x.com\/integrtr","https:\/\/www.linkedin.com\/company\/integrtr\/","https:\/\/www.instagram.com\/integrtr\/","https:\/\/www.youtube.com\/@integrtr9894"]},{"@type":"Person","@id":"https:\/\/integrtr.com\/#\/schema\/person\/2d8324a2d0a6b74bd10b124e88114754","name":"Girish Bangalore","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/secure.gravatar.com\/avatar\/0cb86c66063e3f243fa1ca82f612e4c85f8651ddf7dcd1cd6fba0b85d5771e9c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/0cb86c66063e3f243fa1ca82f612e4c85f8651ddf7dcd1cd6fba0b85d5771e9c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0cb86c66063e3f243fa1ca82f612e4c85f8651ddf7dcd1cd6fba0b85d5771e9c?s=96&d=mm&r=g","caption":"Girish Bangalore"},"url":"https:\/\/integrtr.com\/de\/author\/girish\/"}]}},"_links":{"self":[{"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/posts\/4691","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/comments?post=4691"}],"version-history":[{"count":0,"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/posts\/4691\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/media\/4771"}],"wp:attachment":[{"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/media?parent=4691"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/categories?post=4691"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/integrtr.com\/de\/wp-json\/wp\/v2\/tags?post=4691"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}