Search trusted KBAs, release updates and expert insights across your modules.
Updated daily
Curated monitoring
Latest intelligence
40 results
Release updateEmployee Central
Android edit view can show the wrong custom MDF card label
SAP confirms a SuccessFactors Mobile defect where the Android edit view for a custom MDF card can display an incorrect title instead of the section name configured in Manage Configuration UI. The configured label remains correct on iOS, the web application, and the mobile View All screen. SAP plans the Android correction for September 22, 2026, with Google Play availability potentially extending to September 24.
Customer impact: Android users editing custom MDF information from Latest People Profile can see a misleading section title. Although SAP describes this as a display issue rather than a data-loss problem, the mismatch can confuse users about which record they are changing and generate avoidable support requests.
Review or test: Until the corrected Android app is installed, ask affected users to confirm the card in View All or the web profile before editing, especially where several custom MDF sections have similar fields. Record the configured Title Type and Title Format, Android app version, and affected card. After the release reaches Google Play, update the app and test the pencil/edit view, save and cancel actions, View All, iOS/web consistency, and representative role-based permissions.
Mobile Time Off approval can display raw JSON instead of request details
SAP confirms a mobile display defect where a manager opening a pending Time Off workflow can see raw code or JSON, including time-account fields, instead of formatted leave-request details. The manager may be unable to complete the approval in the app. SAP plans the correction for the next mobile release around September 22, 2026.
Customer impact: Managers relying on mobile approvals can be blocked from reviewing or approving leave requests, delaying workflows and creating a risk that approvers act without readable request details. The underlying workflow remains available through the web application.
Review or test: Until the corrected app is installed, direct managers to review and approve affected Time Off workflows in the web application. Capture the mobile OS, app version, workflow ID, and whether Latest People Profile and the latest home page are enabled. After the September mobile release reaches the applicable app store, update the app and test representative paid, unpaid, and time-account-based requests, confirming readable details and successful approve, decline, and send-back actions.
MDF onChange rules can fail without Create or Correct permission
SAP confirms a known error where an onChange business rule on a custom MDF object does not trigger for a user who has View Current and Insert permissions but lacks Create or Correct permission. SAP plans a correction for September 24, 2026; granting the additional object permissions is the documented interim workaround.
Customer impact: Fields that should be derived or updated by an MDF onChange rule can remain unchanged when users edit a custom People Profile portlet. Granting broader Create or Correct access may restore the rule but can also exceed the intended role design and data-governance boundary.
Review or test: Reproduce with a test role that mirrors the affected View Current and Insert permissions, use Rule Trace where available, and compare the result with a controlled role that also has Create or Correct. Do not broaden production permissions without a security review of target population, field access, and edit history. After the September 24 patch, remove any temporary excess permissions and regression-test insert and edit scenarios, rule conditions, derived fields, and audit behavior.
Unchanged Compensation statement XML can be rejected on import
SAP documents a known Compensation error where a statement template exported from Manage Statement Templates can be rejected on re-import with a message claiming that the XML was modified outside the Statement Editor, even when no changes were made. SAP schedules the fix for Preview on September 8 and Production on September 10, 2026.
Customer impact: Compensation teams can be blocked from importing statement-template XML, including templates added from the Success Store, delaying statement configuration, transport preparation, or cycle readiness work.
Review or test: Avoid repeatedly editing or transforming the XML to bypass the validation. Preserve the original export and error evidence, and defer non-urgent imports until the applicable patch. In Preview after September 8, export an unchanged representative template and re-import it; then test a controlled Statement Editor change, generated statements, tokens, formatting, and permissions. Repeat the import regression in Production after September 10 before resuming critical template deployment.
Disabled Performance module can remain visible in the mobile menu
SAP confirms a known SuccessFactors Mobile issue where the Performance menu item can remain visible even after Performance Management is disabled in Provisioning and under Enable Mobile Features. SAP plans the correction for the Mobile 2609 release, with deployment scheduled for September 16, 2026 (US time).
Customer impact: Organizations that have intentionally disabled Performance Management can still expose a non-applicable mobile navigation option. Users may assume the module is available, encounter an unusable path, or raise avoidable support requests even though the underlying feature configuration remains disabled.
Review or test: Confirm the module is disabled in both Provisioning and Admin Center → Enable Mobile Features, then document whether the Performance menu still appears on representative iOS and Android devices. Until the correction is available, advise users to ignore the menu item. After the 2609 mobile release reaches the applicable app store, update the app and verify the menu is hidden for affected roles while enabled mobile modules and permissions remain unchanged.
Story-report IAS configuration check returns September 11
SAP confirms that the SACTenantConfigurationCheckTool check has been missing from Check Tool since the 1H 2026 release. The check validates six IAS and SAP Analytics Cloud identity settings that can otherwise contribute to blank screens when users create, edit, or run Story reports. SAP plans to restore it with a patch on September 11, 2026.
Customer impact: Administrators currently cannot use this built-in system-health check to detect mismatched conditional-authentication, corporate identity-provider, issuer, subject-identifier, or trust settings for Story reports. Misconfiguration can remain harder to identify and may surface as blank Story-report screens.
Review or test: Before September 11, manually compare the six IAS settings listed in SAP KBA 3336576 for SuccessFactors and SAP Analytics Cloud, and retain evidence of the current configuration. After the patch, open Check Tool, select System Health and Reporting, remove any Result Type filter if necessary, run SACTenantConfigurationCheckTool, resolve reported differences in a non-production tenant first, and regression-test creating, editing, and running representative Story reports. Open an SAP case if the check remains unavailable after the patch reaches the tenant.
SAP will replace the RSA host key for `sftp19.sapsf.com` in datacenter DC62 (Azure Brazil South) with an ECDSA key on September 17, 2026. Systems that perform strict host-key validation must trust the new fingerprint before the scheduled change.
Customer impact: SAP Integration Suite/CPI, BTP applications, third-party middleware, scripts, and managed file-transfer clients that pin only the existing RSA key can reject the SFTP connection after the switch, interrupting inbound and outbound SuccessFactors file transfers.
Review or test: Identify every connection to `sftp19.sapsf.com`. Download and independently verify the ECDSA public key attached to SAP KBA 3765214, add it to each affected known_hosts file or trust store before September 17, and test login plus representative upload and download flows. Retain the old RSA key through the transition, then remove it only after SAP completes the change and scheduled processing is confirmed.
Android app overrides dropdown rating style with stars
SAP confirms a known Android mobile-app issue in the Latest Performance Management form experience: rating fields configured with the dropdown style in the browser display as stars on Android. SAP plans the correction in a mobile release after September 23, 2026.
Customer impact: The underlying rating field remains available, but Android users see a different input control than the configured browser experience. This can confuse reviewers, weaken process consistency, and affect user instructions or training materials.
Review or test: Until the corrected app is available, advise affected Android reviewers that the star control represents the configured rating scale, or complete sensitive ratings in the browser. After September 23, update the Android app from the applicable store and test objective and competency rating fields on representative forms, scales, and permissions before closing the issue.
Mobile Latest People Profile can hide MDF attachment records
SAP confirms a SuccessFactors Mobile display defect where a custom MDF card containing an attachment can show “There's no data yet” on the Latest People Profile summary even though the record exists and displays correctly on the web. The record remains reachable through the history or View All option. SAP plans a mobile-app fix for September 22, with app-store availability potentially extending to September 24, 2026.
Customer impact: Mobile users may wrongly conclude that an employee's custom MDF attachment record is missing, while the same data remains present in the system and accessible through alternate views.
Review or test: Tell affected users to use View All, the history icon, or the web profile as a temporary workaround. After the corrected mobile version reaches the applicable app store, update the app and test custom MDF cards with attachments on iOS and Android, verifying summary, history, View All, permissions, and web/mobile consistency.
SAP confirms a known Calibration issue where the standard boolean fields Future Leader and New to Position can display correctly in the session List View but always appear as “No” in the Executive Review Subjects List. Filtering still uses the correct underlying values. SAP plans the correction in patch 2605p23, scheduled for Preview on September 22 and Production on September 24, 2026.
Customer impact: Talent-review participants can see misleading values after drilling into a matrix cell even though filters and stored employee data are correct. This can create confusion during calibration discussions and lead reviewers to question otherwise accurate talent data.
Review or test: Before the patch, compare the Executive Review Subjects List with the Calibration List View or source employee data before acting on Future Leader or New to Position values. After patch 2605p23 reaches the tenant, test both Yes and No employees, drill into several matrix cells, confirm displayed values match the List View, and verify that filters continue to return the expected subjects.
Kazakh locale can block Talent Intelligence Hub competencies
SAP documents a locale-specific Talent Intelligence Hub defect in Suite 2605: users working in Kazakh (Kazakhstan) can receive an “Invalid Locale passed while fetching libraries with filter” error and a blank screen when opening Competencies. SAP plans the fix for Preview on September 15 and Production on September 17, 2026.
Customer impact: The issue is limited to the Kazakh locale, but affected administrators and users cannot access the Competencies area until they change locale or the correction is deployed.
Review or test: Identify whether any Talent Intelligence Hub users operate in the Kazakh locale. If affected, validate that another supported locale provides temporary access without changing competency data. After the applicable patch, switch back to Kazakh, open Competencies, test library filtering and representative competency records, and confirm the blank-screen error no longer occurs.
SAP confirms that Identity Authentication Service (IAS) adoption becomes mandatory by November 2026 for SuccessFactors customers. SAP advises completing the migration in advance to avoid disruption when corporate-IdP and basic-authentication access methods are removed; tenants created after December 9, 2022 were automatically deployed with IAS.
Customer impact: Tenants that have not integrated SuccessFactors with IAS risk authentication and access disruption when legacy access methods are withdrawn. The change can affect administrators, end users, integrations, SSO flows, and operational support procedures.
Review or test: Confirm whether every production and non-production tenant is integrated with IAS and inventory remaining basic-authentication or direct corporate-IdP dependencies. Follow SAP's Upgrade Center integration guidance, validate corporate IdP trust and user provisioning, test administrator recovery access and representative user journeys, and complete cutover rehearsals well before November.
SAP will replace the RSA host key for `sftp17.sapsf.com` in datacenter DC60 (Toronto, Azure Canada Central) with an ECDSA key on September 10, 2026. The SFTP URL and credentials do not change, but systems that perform strict host-key checking must trust the new fingerprint.
Customer impact: CPI, BTP, third-party middleware, scripts, and managed file-transfer systems that pin the existing RSA host key can reject the SFTP connection after the switch, interrupting inbound and outbound SuccessFactors file exchanges.
Review or test: Download and verify the new ECDSA key from the KBA, then add it to each affected client's known_hosts or equivalent trust store before September 10. Test a representative connection and file transfer, retain the old RSA key only through the transition, and remove it after SAP completes the switch and successful processing is confirmed.
SAP will introduce an ECDSA host key for `sftp55.sapsf.eu` in datacenter DC55 (Frankfurt, GCP) on September 7, 2026. Strict host-key checking can require one-time acceptance; SAP states the SFTP URL, user credentials, and Provisioning or Integration Center schedules are unchanged.
Customer impact: External clients and SAP Cloud Integration flows that trust only the current RSA host key may fail with a changed or rejected host-key error after the rollout, interrupting scheduled SuccessFactors data transfers.
Review or test: Identify every connection to `sftp55.sapsf.eu`, download the attached ECDSA public key from SAP, and add it to the CPI known_hosts file or the external client's trust store before September 7. Do not remove the old key until the switch is complete; then validate login, upload, download, and downstream processing before closing the change.
Latest People Profile trend configuration fix reaches production September 3
SAP confirms a known issue where the Trend Information card's Content Configuration is blank in Configure Latest People Profile when many active Performance Management templates exist. Patch M2608P3 is scheduled for Preview on September 1 and Production on September 3, 2026; reducing the number of active templates is the interim workaround.
Customer impact: Administrators may be unable to configure the Performance & Goals trend card, which can delay Latest People Profile setup or leave performance-history presentation incomplete.
Review or test: Before the patch, avoid deactivating templates without confirming retention and reporting consequences. After M2608P3 reaches the tenant, open Configure Latest People Profile, edit the Trend Information card, verify Content Configuration loads with the normal template volume, save the configuration, and confirm expected trend data with representative users and permissions.
SuccessFactors API rate-limit monitoring starts August 17
SAP confirms that the 2608 release introduces soft rate limits and standardized RateLimit response headers for existing SuccessFactors tenants from August 17, 2026. Soft-limit breaches are initially observed rather than blocked, but quotas are shared at tenant and resource level across OData, REST, Compound Employee, SAP Integration Suite/BTP, third-party middleware, custom applications, and direct API clients. SAP also states that new public APIs released from November 13, 2026 and new tenants provisioned from January 1, 2027 will start with hard limits.
Customer impact: High-volume or poorly staggered integrations can consume a shared tenant quota and later receive HTTP 429 responses when hard enforcement applies. One integration's traffic can reduce the budget available to other interfaces, while immediate retries can amplify congestion and extend processing delays.
Review or test: From August 17, capture and monitor the RateLimit-Policy and RateLimit headers across representative production-like calls. Inventory peak API consumers, stagger schedules, use batching and delta queries, cache stable reference data, and leave operating headroom. Test HTTP 429 handling with Retry-After, exponential backoff, jitter, logging, and controlled recovery in CPI/BTP and third-party middleware. Note that internal Integration Center calls are excluded; request a time-limited exemption through SAP Support for justified go-live or hypercare peaks.
SAP confirms that the SAP Analytics Cloud 2026.15 (Q3 2026) rollout is planned for August 14–16, 2026 and deprecates the Classic Story experience. After the applicable tenant update, classic stories and analytic applications are no longer accessible, new classic content cannot be created, and schedules based on classic stories are cancelled. This is a general SAC change; customers should verify its exact applicability to their SuccessFactors-connected and embedded analytics landscape.
Customer impact: Workforce dashboards or analytic applications built in the SAC Classic Experience can become unavailable, while scheduled distributions can stop until the content is successfully converted to the Optimized Story Experience.
Review or test: Inventory SAC classic stories and analytic applications that use SuccessFactors data, including business owners and schedules. Use SAP's Story Conversion tool, review blocked or unsupported features, save copies where rollback evidence is needed, and regression-test calculations, filters, permissions, linked models, scripts, exports, mobile behavior, and scheduled delivery. Confirm the tenant's actual 2026.15 deployment before closing readiness activities.
Termination End Handling workaround for post-termination absences
SAP confirms that approved absences after a future termination are not automatically cancelled. Its detailed interim solution uses a rule assigned to the Time Management Task object so Termination End Handling is scheduled for the day after the termination is entered, rather than waiting until the termination date. SAP explicitly requires the one-day delay and warns against immediate processing because dependent tasks, such as accrual recalculation, may still be incomplete.
Customer impact: Post-termination absences can continue consuming time-account balances and affect payout, payroll inputs, approvals, and reporting. A rule that forces immediate or indiscriminate task processing can also generate alerts and create a server-performance risk.
Review or test: Follow the full KBA exactly in a non-production tenant. Test representative future terminations with approved absences before and after the end date; confirm next-day processing cancels only the post-termination records, valid absences remain, and accrual recalculation completes. Monitor task volume and performance, do not force same-day processing or all tasks, and ask your SAP CSM or CEE to track the unconfirmed Product Engineering enhancement TIM-30264.
SAP expands certificate guidance and plans to discontinue KBA 2533915
SAP's certificate repository still lists new certificates for `*.successfactors.com` and `*.successfactors.eu`, valid from August 27, 2026. SAP has now added that KBA 2533915 will be discontinued in December 2026 and relays DigiCert's recommendation to stop pinning or hard-coding root and intermediate CA certificate acceptance. The certificate change does not affect the BizX SSO certificate.
Customer impact: API, file-transfer, CPI, PI/PO, Boomi, or other middleware connections that pin certificates or rely operationally on this KBA can face avoidable outages or lose their familiar certificate-reference source after December 2026.
Review or test: Identify integrations using the affected domains and validate the August 27 certificate chain in non-production. Inventory certificate pinning and hard-coded root or intermediate CA trust, then plan controlled removal where platform security standards permit. Record any monitoring or runbook dependency on KBA 2533915 and follow SAP's official guidance for its replacement source before December; retain old endpoint certificates only until the applicable rollout is complete, then run authentication and representative data-transfer tests.
Repeated failures now auto-cancel recurring Provisioning jobs
SAP confirms a new SuccessFactors scheduled-job policy effective August 1, 2026. A recurring request is automatically cancelled when it has no successful execution and at least three total executions within the previous seven days. The policy applies to multiple MDF import/export, reporting, integration export, time, recruiting, and Check Tool job types.
Customer impact: An important recurring job can stop running after repeated failures even though its original schedule remains visible, leading to missed imports, exports, reports, recalculations, or integration deliveries.
Review or test: Review Provisioning execution history for affected recurring job types, especially jobs that depend on SFTP files or external systems. Correct failing parameters or missing inputs, re-establish cancelled schedules where appropriate, and confirm at least one successful run. Add operational monitoring for cancelled status and gaps in expected execution logs.
Overlapping agency ownership can occur before expiry
SAP confirms a Recruiting Management defect where a second agency can forward a candidate even though another agency still holds active ownership. The second submission creates overlapping ownership periods without displaying an error. Engineering is investigating and lists a tentative correction during August 2026.
Customer impact: Recruiting teams may face conflicting agency ownership claims, inaccurate ownership reporting, duplicated submissions, and potential commercial disputes over candidate fees.
Review or test: Until SAP confirms the correction, report on candidate forwarding and ownership-expiry dates before accepting or processing agency submissions. Test scenarios where two agencies previously held and later regain ownership, document exceptions, and repeat the tests after the applicable production patch.
SAC 2026.8.5 restores SuccessFactors live-model system type
SAP states that SAP Analytics Cloud version 2026.8.5 resolves an issue where the System Type list did not show SAP Cloud Application when creating a new model from an existing SuccessFactors live connection. Existing connections and models could remain usable even though administrators could not create the new live model.
Customer impact: Analytics teams blocked from creating new SuccessFactors live models can resume model creation after the applicable SAC update, without rebuilding otherwise valid live connections.
Review or test: Confirm the SAC tenant is on version 2026.8.5 or later, then create a test live model and verify that SAP Cloud Application appears as a System Type. Validate representative SuccessFactors connections, model access, refresh behavior, and downstream stories before restarting paused production work.
SAP removes previously stated Onboarding 1.0 deletion date
SAP has materially revised its release-information page for replacing Onboarding 1.0. The page now says SAP removed the earlier statements about code removal after the 2H 2026 release and deletion on November 13, 2026. This is a change to the published timeline, not confirmation that Onboarding 1.0 has been restored or will remain available indefinitely.
Customer impact: Customers using legacy Onboarding 1.0 may have project plans, support assumptions, data-retention activities, or shutdown communications based on dates that SAP no longer presents as current.
Review or test: Recheck the official release-information and Onboarding 1.0 decommissioning guidance before changing any migration plan. Confirm the status of each legacy account, preserve required audit or compliance data, and obtain tenant-specific confirmation from SAP Support before relying on a revised retirement date.
Blended tables arrive in Optimized Story Experience
SAP confirms that the SAC Q3 release adds support for creating blended tables in the Optimized Story Experience for SuccessFactors Story reports. The capability was previously limited to the Classic Story Experience.
Customer impact: Report designers can combine data from different sources in tables while moving away from the Classic experience, reducing a key migration gap for cross-source reporting.
Review or test: In a Preview or non-production tenant on the applicable SAC Q3 release, recreate representative classic blended tables in Optimized Story Experience. Validate linked dimensions, joins, filters, aggregation, totals, row counts, and exported results before converting business-critical reports.
Spain Model 145 can generate the wrong disability checkbox
SAP confirms a product defect in Onboarding Compliance 2.0 where selecting “Igual o superior al 65%” can map to a different disability-related checkbox in the generated Spain Model 145 document. Engineering identified the cause and plans to deliver the correction in compliance bundle 2026_v1.
Customer impact: The signed tax form can misrepresent the candidate’s selection, creating a compliance and employee-record accuracy risk for Spanish onboarding processes.
Review or test: Until the correction is deployed, manually review affected generated forms after submission and verify the selected checkbox against the candidate’s response. After compliance bundle 2026_v1 is available, regression-test the option in a non-production tenant before relying on the generated document; contact SAP Support with replication details if the mismatch continues.
HRIS Sync can overwrite the latest same-day People Profile header
SAP confirms a defect where HRIS Sync reads assignmentDisplayHeader from the lowest-sequence Job Information record when multiple records share today’s effective date. The header can initially show the correct latest value after a real-time sync, then revert after the scheduled HRIS Sync. SAP scheduled the correction for Preview on July 28 and Production on July 30, 2026.
Customer impact: People Profile can display an outdated employment differentiator or other header value after HRIS Sync, creating inconsistency between the latest Job Information record and the visible employee header.
Review or test: In Preview, create representative same-day Job Information sequences with different header-driving values, run HRIS Sync, and confirm the highest-sequence value remains displayed. Repeat after the July 30 production patch and verify any downstream process that consumes the affected header field.
Growth Portfolio correction for missing new-hire competencies
SAP documents a known Talent Intelligence Hub issue where a new hire’s Growth Portfolio does not automatically receive competencies and skills mapped to the role. SAP scheduled patch PTCH-50717 for Preview on July 28 and Production on July 30, 2026.
Customer impact: New hires can see incomplete Growth Portfolios, while administrators may need to repeatedly refresh role content to expose the missing attributes.
Review or test: Before the production patch, SAP’s workaround is to export Role entities and reimport the unchanged file. After deployment, test several new hires across representative role mappings and confirm competencies and skills appear without manually saving or reimporting the role.
Position fields return “No matches” in SmartRecruiters mapping
SAP documents a configuration issue where SuccessFactors Integration Hub returns no selectable Position fields while mapping SuccessFactors Position data to SmartRecruiters Job fields. The empty result prevents administrators from completing the Position-to-Job mapping.
Customer impact: Position-driven job creation or synchronization can be delayed because required SuccessFactors Position fields cannot be selected and mapped to the corresponding SmartRecruiters job fields.
Review or test: Reproduce with a representative Position field and capture the mapping area, search term, field metadata, and synchronization status. Review the full SAP KBA and the current SmartRecruiters integration guide before changing mappings or rerunning synchronization; the public preview confirms the symptom but does not expose SAP’s complete resolution.
Applicant Workbench status mismatch patch scheduled for production
SAP documents a Latest Applicant Workbench issue where moving a candidate from a sub-status can update the header while leaving the Application Information status picklist on the old value. A later save can unintentionally move the candidate back. SAP scheduled the production patch for July 23, 2026.
Customer impact: Recruiters may unknowingly reverse a candidate's workflow status, affecting processing, reporting, communications, and downstream recruiting activities.
Review or test: Until the patch is verified in your tenant, update status through the Candidate Status picklist in Application Information instead of the Move button. After deployment, regression-test sub-status moves and confirm the header, picklist, and saved application remain aligned.
Permanent Work Zone file-access correction scheduled
SAP reports that a backend streaming defect caused HTTP 500 errors when downloading or previewing Workspace files. Engineering disabled the affected functionality as an immediate mitigation and scheduled the permanent correction for July 23, 2026.
Customer impact: Affected users may be unable to download or preview workspace documents, disrupting collaboration and access to shared content, particularly in tenant-migration or legacy-path scenarios.
Review or test: Confirm downloads and previews currently work after SAP's mitigation, then repeat the tests after the permanent correction. If failures continue, capture the workspace, file type, timestamp, tenant-migration context, and HTTP response for support.
Android Job Information access correction dated July 21
SAP documents a defect in Employee Central Mobile 2605 where Android users can open Employment Information but Job Information fails to load. SAP states that a code correction was created and scheduled for release on July 21, 2026.
Customer impact: Affected Android users may be unable to review employee Job Information from the mobile app, even though the data remains available through other supported access channels.
Review or test: Confirm the installed SuccessFactors mobile app version, reproduce with an affected Android user after updating, and verify that Job Information loads from View Full Profile → Employment Information. Keep the incident open if the correction is not yet available in the applicable app distribution channel.
Rehire Data Review position-to-job rule patch reached production
SAP confirms that a defect can prevent the position-to-job onChange rule from running when Rehire Data Review first loads, leaving related Job Information fields blank. Patch PTCH-50614 reached production on July 17, 2026; the correction remains opt-in through 2H 2026.
Customer impact: Rehired employees may reach Manage Pending Hires with incomplete job, grade, role, or pay-scale values if the missing fields are not detected and corrected.
Review or test: Confirm whether the 2H 2026 feature toggle is enabled, then regression-test rehire-on-old-employment scenarios with representative positions. Until enabled, changing the Position to another value and back triggers the rule as SAP's documented workaround.
Onboarding custom task blocked by missing task-status permission
SAP confirms that a responsible user can receive an access error when opening an assigned custom onboarding task if the required role-based permission is missing.
Customer impact: Responsible users may be unable to complete custom tasks, delaying onboarding activities.
Review or test: Check the responsible user's permission role for Onboarding or Offboarding Permissions → Show Onboarding Tasks Status, then retest with a representative responsible user.
Australian STP2 submission rejected when country code is uppercase
SAP documents an ATO validation rejection where the STP2 Payee Data report contains the country value “AU” instead of lowercase “au” for impacted employees.
Customer impact: Affected Employee Central Payroll, SAP ERP, or SAP S/4HANA payroll submissions can be rejected by the ATO.
Review or test: For Australian concurrent-employment payroll, review the Payee Data report before submission, reproduce with an affected employee, and assess the related SAP correction referenced in the full KBA.