Troubleshooting ServiceNow Software Asset Management SAP Ariba integration: Complete Troubleshooting GUIDE for profile will not publish, wrong or missing subscriptions, last activity not updatingSummary :root { color-scheme: light; --blue:#005baa; --ink:#172033; --muted:#5b6678; --line:#d6dee8; --surface:#fff; --page:#f3f6fa; --red:#b42318; --amber:#9a6700; --green:#087443; } * { box-sizing:border-box; } html { scroll-behavior:smooth; } body { margin:0; padding:24px; background:var(--page); color:var(--ink); font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif; line-height:1.55; } .kb-page { max-width:920px; margin:0 auto; } .kb-hero { background:var(--blue); color:#fff; padding:28px 32px; border-radius:10px; margin-bottom:24px; } .kb-eyebrow { margin:0 0 6px; font-size:11px; letter-spacing:1px; opacity:.78; text-transform:uppercase; } .kb-hero h1 { margin:0 0 7px; font-size:clamp(22px,4vw,30px); line-height:1.15; } .kb-lede { margin:0; font-size:14px; opacity:.9; } .kb-badges { display:flex; flex-wrap:wrap; gap:8px; margin-top:16px; } .kb-badge { padding:3px 11px; border-radius:12px; background:rgba(255,255,255,.18); font-size:12px; } .kb-toc,.kb-panel { background:var(--surface); border:1px solid var(--line); border-radius:8px; } .kb-toc { padding:18px 24px; margin-bottom:24px; } .kb-toc-title { margin:0 0 8px; color:#374151; font-size:13px; font-weight:700; letter-spacing:.5px; text-transform:uppercase; } .kb-toc ol { margin:0; padding-left:22px; line-height:2; } .kb-toc a { color:var(--blue); text-decoration:none; } .kb-section { margin-bottom:28px; scroll-margin-top:16px; } .kb-section-title { margin:0; padding:12px 20px; border-radius:8px 8px 0 0; background:var(--blue); color:#fff; font-size:16px; } .kb-panel { padding:20px 22px; border-top:0; border-radius:0 0 8px 8px; } .kb-panel p:first-child { margin-top:0; } .kb-panel p:last-child { margin-bottom:0; } .kb-callout { margin:0 0 18px; padding:13px 16px; border-left:5px solid var(--blue); border-radius:0 7px 7px 0; background:#eef5fc; } .kb-callout.critical { border-color:var(--red); background:#fff1f0; color:#7a271a; } .kb-callout.warning { border-color:var(--amber); background:#fff8e7; color:#6b4d00; } .kb-callout.success { border-color:var(--green); background:#ecfdf3; color:#05603a; } .kb-table-wrap { overflow-x:auto; margin:16px 0; } table { width:100%; border-collapse:collapse; font-size:13px; } th { padding:9px 12px; background:#31506d; color:#fff; text-align:left; } td { padding:9px 12px; border-bottom:1px solid #e5e7eb; vertical-align:top; } tr:nth-child(even) td { background:#f8fafc; } code { padding:1px 4px; border-radius:3px; background:#f1f3f5; font-family:ui-monospace,SFMono-Regular,Menlo,monospace; font-size:.92em; overflow-wrap:anywhere; } pre { overflow:auto; padding:14px; border-radius:6px; background:#111827; color:#f9fafb; } details { margin:0 0 12px; border:1px solid #bfdbfe; border-radius:6px; overflow:hidden; } summary { cursor:pointer; padding:12px 16px; background:#eff6ff; color:#1e3a5f; font-weight:700; } details > div { padding:16px; background:#fff; } .kb-footer { padding:16px 20px; color:var(--muted); font-size:12px; background:#f8fafc; border:1px solid var(--line); border-radius:8px; } @media (max-width:640px) { body { padding:12px; } .kb-hero { padding:22px 20px; } .kb-panel { padding:16px; } .kb-section-title { padding:11px 16px; } th,td { min-width:140px; } } .kb-hero { padding:24px 28px; } .kb-toc ol { display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:2px 26px;line-height:1.7; } .kb-toc li { padding:3px 0; } h3 { color:#183653;line-height:1.3; } a { color:#005baa;overflow-wrap:anywhere; } th,td { overflow-wrap:anywhere; } pre code { padding:0;background:transparent;color:inherit;overflow-wrap:normal; } code.kb-err { color:#c62828;font-weight:700;background:#fdecea; } .kb-err-list { display:flex;flex-wrap:wrap;gap:6px;margin-top:8px;font-weight:400; } .kb-err-chip { display:inline-block;max-width:100%;padding:2px 8px;border-radius:4px;background:#fdecea;border:1px solid #f5c2c0;color:#c62828; font-family:ui-monospace,SFMono-Regular,Menlo,monospace;font-size:12px;font-weight:700;line-height:1.45;overflow-wrap:anywhere; } .kb-sum-title { font-weight:700; } .branch-index { margin:18px 0 20px;padding:14px 18px;background:#f8fafc;border:1px solid var(--line);border-radius:8px; } .branch-index ol { list-style:none;margin:0;padding:0;display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:6px 28px; } .branch-index li { font-size:14px;line-height:1.45;padding:4px 0; } .kb-section-title + .kb-panel { margin-top:0; } details > div p { margin:0 0 14px; } details > div p:last-child { margin-bottom:0; } @media(max-width:640px) { .kb-toc ol,.branch-index ol { grid-template-columns:1fr; } .kb-hero {padding:20px;} } @media print { body {padding:0;background:#fff;} .kb-toc,.branch-index {display:none;} } .flow { margin:4px 0 26px;padding:18px;border-radius:12px;background:linear-gradient(135deg,#f8fafc,#eef2ff);border:1px solid var(--line); } .flow-intro { display:flex;flex-wrap:wrap;justify-content:space-between;gap:10px;font-size:13px;color:#475569;margin-bottom:14px; } .flow-legend { display:flex;flex-wrap:wrap;gap:6px; } .flow-key { padding:2px 9px;border-radius:10px;background:var(--b);color:var(--c);font-weight:700;font-size:11px;border:1px solid var(--c); } .flow-lane { margin-top:14px; } .flow-lane-head { display:flex;align-items:center;gap:10px;margin-bottom:8px;color:#0f172a; } .flow-lane-head span { font-size:11px;padding:2px 8px;border-radius:10px;background:#0f172a;color:#fff;text-transform:uppercase;letter-spacing:.05em; } .flow-track { display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:16px 30px; } .flow-node { position:relative;display:flex;flex-direction:column;gap:3px;padding:12px 10px 10px 12px;border-radius:10px; background:var(--b);border:2px solid var(--c);color:#1e293b;text-decoration:none;box-shadow:0 1px 2px rgba(15,23,42,.06); transition:transform .2s ease,box-shadow .2s ease;animation:flowPulse 4.4s ease-in-out infinite;animation-delay:var(--d); } .flow-node::after { content:"";position:absolute;top:50%;right:-27px;width:22px;height:4px;margin-top:-2px;border-radius:2px; background:repeating-linear-gradient(90deg,var(--c) 0 6px,transparent 6px 10px);background-size:20px 4px;animation:flowDash .8s linear infinite;opacity:.7; } .flow-node:nth-child(4n)::after,.flow-node:last-child::after { display:none; } .flow-node:hover,.flow-node:focus { transform:translateY(-3px);box-shadow:0 8px 20px rgba(15,23,42,.18);outline:none;z-index:5; } .flow-node:focus-visible { outline:3px solid var(--c);outline-offset:2px; } .flow-num { position:absolute;top:-9px;left:-9px;width:22px;height:22px;border-radius:50%;background:var(--c);color:#fff;font-size:12px;font-weight:700; display:flex;align-items:center;justify-content:center;box-shadow:0 0 0 2px #fff; } .flow-title { font-weight:700;color:var(--c);font-size:13.5px;line-height:1.25; } .flow-what { font-size:12px;line-height:1.35;color:#334155;overflow-wrap:anywhere; } .flow-tip { position:absolute;left:50%;top:calc(100% + 8px);transform:translateX(-50%) translateY(-4px);width:210px;padding:10px 12px;border-radius:8px; background:#0f172a;color:#f8fafc;font-size:12px;line-height:1.4;opacity:0;pointer-events:none;transition:opacity .18s ease,transform .18s ease;z-index:10; } .flow-tip::before { content:"";position:absolute;top:-6px;left:50%;margin-left:-6px;border:6px solid transparent;border-top:0;border-bottom-color:#0f172a; } .flow-tip em { display:block;margin-top:6px;font-style:normal;color:#93c5fd;font-weight:700; } .flow-node:hover .flow-tip,.flow-node:focus .flow-tip { opacity:1;transform:translateX(-50%) translateY(0); } .tri { margin:14px 0 20px;padding:16px;border-radius:12px;background:#0f172a;color:#e2e8f0; } .tri-head { font-size:12px;text-transform:uppercase;letter-spacing:.08em;color:#93c5fd;font-weight:700;margin-bottom:12px; } .tri-row { display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:12px 26px; } .tri-step { position:relative;display:flex;flex-direction:column;gap:4px;padding:12px;border-radius:10px;background:#1e293b;border:1px solid #334155; animation:triGlow 4.2s ease-in-out infinite;animation-delay:var(--d); } .tri-step::after { content:"";position:absolute;top:50%;right:-22px;width:16px;height:3px;background:repeating-linear-gradient(90deg,#60a5fa 0 5px,transparent 5px 8px); background-size:16px 3px;animation:flowDash .7s linear infinite; } .tri-step:last-child::after { display:none; } .tri-step strong { color:#f8fafc;font-size:14px; } .tri-where { font-size:12px;color:#93c5fd; } .tri-tells { font-size:12px;color:#cbd5e1;line-height:1.35; } .tri-num { position:absolute;top:-9px;left:-9px;width:22px;height:22px;border-radius:50%;background:#2563eb;color:#fff;font-size:12px;font-weight:700;display:flex;align-items:center;justify-content:center; } @keyframes triGlow { 0%,100% { border-color:#334155;box-shadow:none; } 10% { border-color:#60a5fa;box-shadow:0 0 0 3px rgba(96,165,250,.35); } 22% { border-color:#334155;box-shadow:none; } } .tri-row.tri-5 { grid-template-columns:repeat(5,minmax(0,1fr)); } @media (max-width:820px) { .tri-row,.tri-row.tri-5 { grid-template-columns:repeat(2,minmax(0,1fr)); } .tri-step:nth-child(2n)::after { display:none; } } @media (max-width:520px) { .tri-row { grid-template-columns:1fr; } .tri-step::after { display:none; } } @media (prefers-reduced-motion: reduce) { .tri-step,.tri-step::after { animation:none; } } @keyframes flowPulse { 0%,100% { box-shadow:0 1px 2px rgba(15,23,42,.06); } 8% { box-shadow:0 0 0 4px var(--b),0 0 0 6px var(--c),0 6px 18px rgba(15,23,42,.2); } 18% { box-shadow:0 1px 2px rgba(15,23,42,.06); } } @keyframes flowDash { to { background-position:20px 20px; } } @media (prefers-reduced-motion: reduce) { .flow-node,.flow-node::after { animation:none; } } @media (max-width:820px) { .flow-track { grid-template-columns:repeat(2,minmax(0,1fr)); } .flow-node:nth-child(4n)::after { display:block; } .flow-node:nth-child(2n)::after { display:none; } } @media (max-width:520px) { .flow-track { grid-template-columns:1fr;gap:24px; } .flow-node::after,.flow-node:nth-child(4n)::after,.flow-node:nth-child(2n)::after { display:block;top:auto;bottom:-22px;right:auto;left:50%;width:4px;height:18px;margin:0 0 0 -2px; background:repeating-linear-gradient(180deg,var(--c) 0 6px,transparent 6px 10px);background-size:4px 20px; } .flow-node:last-child::after { display:none; } .flow-tip { position:static;transform:none;width:auto;margin-top:6px;display:none;opacity:1; } .flow-node:focus .flow-tip,.flow-node:hover .flow-tip { display:block;transform:none; } } @media print { .flow-node,.flow-node::after { animation:none; } .flow-tip { display:none; } } Software Asset Management - Knowledge Article Troubleshooting ServiceNow SAM SAP Ariba integration: profile will not publish, wrong or missing subscriptions, last activity not updating Find the failing stage, correct its cause, and verify complete recovery. Contents Scope and applicabilityImplementation checklistSymptoms and expected behaviorExecution path and evidence correlationDetailed troubleshooting branchesCause-specific correction and controlled recoveryVerification criteria and recovery evidenceEscalation evidence to collectReferences, processing rules and known limitationsServiceNow Otto / Now Assist troubleshooting 1. Scope and applicability This article covers the SAP Ariba direct integration profile (profile type store_sap_ariba_subscription). It is different from every API-based SaaS integration: there is no connection, no credential, no OAuth sign-in and no Validate Connection step. You export four reports from SAP Ariba as .csv files, attach all four to the integration profile, and publish it. ServiceNow imports the reports into staging tables, and a subflow named SAP Ariba Download Subscription turns the staged rows into subscriptions. Only the download subflow exists on a reference instance; no reclaim subflow or activity subflow was found. The four reports. The file name of each attachment must contain the report name below. A prefix or suffix is allowed; the match is case-sensitive. Sourcing - User Names and PermissionsAll Contract WorkspacesNumber of Users Creating ProjectsSPM Project Report What it counts. The integration reads who holds access to the SAP Ariba products covered by the reports, which license each user consumes and when each user was last active. The exact column-to-license mapping is not stated in the sources, so check generated models against your SAP Ariba entitlements (branch J). What last activity means. Last activity comes only from the dates inside the uploaded reports. It changes only when you upload newer reports; nothing is read live from SAP Ariba. What reclaim does. Nothing is written back to SAP Ariba. Reclamation candidates (if your rules create them) are advisory: remove the user in SAP Ariba yourself and then close the candidate. Read branches O and P. Not the same as the SAP Ariba Spoke. The Store spoke for SAP Ariba is a procurement-automation spoke (purchase orders, sourcing events and similar). It is not used by this license integration, and installing it does not set up license tracking. Guidance that describes an API application key, an ANID, an OAuth token URL or an API-based connection does not apply to this profile. Applies to: SAM Professional with the Software Asset Management - SaaS License Management (sn_sam_saas_int) Store application, from the Yokohama release onward. It does not cover other SAP integrations (SAP systems, SAP S/4HANA Cloud Public Edition, SAP SuccessFactors), which are separate articles. 2. Implementation checklist CheckWhere and what to inspectReady conditionApplicationApplication Manager: SaaS License ManagementInstalled and currentRoles (ServiceNow)User creating the profilesam_integrator or sam_admin (admin for the first setup)SAP Ariba accessThe person exporting the reportsPermission to run the four reports in SAP Ariba; the sources do not name the SAP Ariba roleReportsSAP AribaThe four reports exported as .csv with the report name kept in the file nameProfileSoftware Asset Workspace > License operations > User subscriptions > Direct integration profiles > New > SAP Ariba > ContinueDisplay name; profile type SAP Ariba SubscriptionAttachmentsProfile > attachments (paper clip)Exactly four attachments, one per report, all .csvPublishProfile > PublishStatus Published; no attachment messageSubflowFlow Designer > Operations > ExecutionsSAP Ariba Download Subscription ran after the last attachmentEntitlementsSoftware models for SAP AribaEntitlements created, then reconciliation runUserssys_user email versus the SAP Ariba user IDResolvable, or user resolution rules exist What the profile and attachments rely on ItemDetailAttachment ruleSAP Ariba Schedule Import (runs asynchronously whenever any attachment is added to a profile)Data sourcesOne per report; they read the attached file, sheet 1, first row as the headerImport tablesariba_user_permission, ariba_contract_workspace, ariba_project_owner, ariba_spm_reportStagingsamp_subscription_staging: subscription profile, subscription identifier, external user ID, user principal name, consumes license, last activity, activeHelperScript include SAPAribaAttachmentUtil There are no SAP Ariba permissions or scopes to grant to ServiceNow, because ServiceNow never calls SAP Ariba. What happens when a setting is missing or wrong Setting, field or propertyIf it is missing or wrongTypical symptomFewer or more than four attachments on the profilePublish refused; import not startedPlease upload all 4 reports and then publish the integration profile.An attachment that is not .csvPublish refused; import not startedPlease upload the reports in .csv format and then publish the integration profileReport name missing from a file nameThat file is never copied to its data sourceIncorrect or missing subscriptions after publishReport name in different letter caseThe match is case-sensitive, so the file is skippedSame as aboveExtra attachment (screenshot, old copy of a report)Attachment count is five or moreThe same "upload all 4 reports" message and no importNew attachment addedAll staging rows for the profile are set inactive firstSubscriptions stop updating until the import finishesProfile edited after publishStatus returns to DraftJobs stop until published againReport columns renamed or removed in SAP AribaImport columns do not mapEmpty or partial staging rowsEntitlements missingNothing to reconcile againstCompliance shows nothingNo matching sys_userSubscription user stays emptyReconciliation consumes no rightDebug properties left onExtra loggingSlow instance after troubleshooting 3. Symptoms and expected behavior SymptomFirst branchHealthy evidence to seekSAP Ariba option, application or subflow missingASAP Ariba profile type availableCannot publish: attachment messagesBStatus PublishedExpected a connection or Validate Connection buttonCUnderstanding that none existsCannot export the reports from SAP AribaDFour .csv files with the right namesSubscriptions are old after SAP Ariba changesEReports newer than the last changeWrong or no subscriptions after publish (report names)FEach file name contains its report nameImport or subflow did not run or failedGImport set rows and a completed flow executionCounts differ from SAP AribaHCounts match licensed users in SAP AribaSeveral SAP Ariba sites, realms or profilesIOne profile and one set of reports per scopeModel or entitlement problemsJSAP Ariba model on every subscriptionUser empty or wrongKIntended sys_user linkedLast activity blank or staleLReport dates reflected in last activitySubscriptions inactive or disappearing after re-uploadMActive staging rows after the importNo or wrong reclamation candidatesNCandidates only for truly inactive usersReclaim does not remove the userOUser removed in SAP Ariba by an administratorAfter reclaim: user still active, stuck candidatesPCandidate closedLarge reports, encoding, timeoutsQRows imported equal rows in the fileProblems after clone, upgrade or repairRProfile published with working attachments A healthy run creates one subscription per user and product combination found in the reports, with the consumed license in the subscription identifier and the report date as last activity. 4. Execution path and evidence correlation Hover or tap a step to see what breaks there; click it to open the matching branch.SetupConnectionCollectionMatchingWriteDownstream Reports and publishmanual, per refresh 1Export reportsFour .csv reports from SAP AribaBreaks here: No permission; wrong formatOpen branch D →2Name the filesFile name contains the report name, case-sensitiveBreaks here: Name missing; wrong dashOpen branch F →3Attach to profileExactly four attachments, all .csvBreaks here: Five files; not csvOpen branch B →4PublishChecks only count and type; no Validate ConnectionBreaks here: Please upload all 4 reportsOpen branch C →5Attachment ruleCopies each file to its data source; staging set inactiveBreaks here: Rule inactive; no importOpen branch G →6ImportScheduled import runs once when four csv existBreaks here: Empty import tablesOpen branch G →7SubflowSAP Ariba Download Subscription creates subscriptionsBreaks here: Failed action; no runOpen branch G →8EntitlementsCreate for the generated modelsBreaks here: Compliance shows nothingOpen branch J → Activity and reclaimeach new set of reports 1User matchReport user ID to sys_userBreaks here: Empty userOpen branch K →2Last activityReport date; moves forward onlyBreaks here: Stale until reports refreshedOpen branch L →3Refresh reportsDelete old four, attach new fourBreaks here: Count of five; inactive stagingOpen branch M →4Candidates60-day rule on report datesBreaks here: Wrong candidatesOpen branch N →5ReclaimManual in SAP Ariba; no write-backBreaks here: User still activeOpen branch O →6After reclaimNext reports no longer list the userBreaks here: Subscription reappearsOpen branch P →7After clone or upgradeAttach the reports againBreaks here: Missing attachments or ruleOpen branch R → Upload, import and download path Export four .csv reports from SAP Ariba → attach each to the profile → SAP Ariba Schedule Import rule (async, per attachment) → all staging rows for the profile set inactive → file copied to the matching data source as <profile sys_id>::<file name> → when exactly four .csv attachments exist, the scheduled import runs once → ariba_* import tables → samp_subscription_staging → SAP Ariba Download Subscription subflow → samp_sw_subscription → reclamation rule (60 days) → user resolution The step from the import tables to the staging table (a transform) and the point at which the subflow starts were not readable on the reference instance. Check them in Flow Designer and the import set log for your release. Reclaim path There is no reclaim subflow on the reference instance. Reclamation is manual: remove the user in SAP Ariba, then close the candidate. StageRecord or source to inspectBehaviorAttachmentsProfile attachmentsFour .csv filesAttachment ruleSAP Ariba Schedule Import (System Definition > Business Rules, table sys_attachment)Active, asynchronousData sourceData source records for the four reportsLatest file attached with your profile ID in the file nameImportSystem Import Sets > Import SetsRows loaded into the four ariba_* tablesStagingsamp_subscription_stagingActive rows for your profileFlow runFlow Designer > Operations > ExecutionsSAP Ariba Download Subscription runSubscriptionssamp_sw_subscriptionOne row per user and licenseLast activitySubscriptionReport date; moves forward only Correlate one execution before deciding a cause Record the profile, the time of the last attachment in UTC, and the application version.Open the profile's attachments and confirm four .csv files whose names contain the report names.Open System Import Sets > Import Sets and the four import tables; confirm rows loaded at the time of the last attachment.Open Flow Designer > Operations > Executions and find the subflow run for the same window; open the failing action.Open System Logs > All and look for messages containing SAP Ariba or ariba, sorted by created time. There are no SAP Ariba-specific debug properties.For deeper tracing, set com.snc.process_flow.reporting.level to All; rerun once, then set it back. 5. Detailed troubleshooting branches Each branch lists the symptoms with the exact text the integration writes, where to look, each cause with its fix, and how to confirm recovery. Identifiers shown as <id> or <name> are placeholders; keep the real values private. Start every investigation here 1AttachmentsProfile > attachmentsCount of four, all .csv, names contain report names 2Import setsSystem Import Sets > Import SetsRows loaded into the four ariba tables 3Flow executionFlow Designer > Operations > ExecutionsSAP Ariba Download Subscription run and failing action 4Pick a branchMatch the message belowattachment message → B/F, empty tables → G, stale data → E/L, reclaim → O Start every investigation the same way. (1) The profile's attachments: count, type and names. (2) The import tables and import set log. (3) Flow Designer > Operations > Executions for the subflow. Read the message, not only the status. A. SAP Ariba option, application or subflow is missingB. The profile cannot be publishedC. There is no connection and no Validate Connection buttonD. Cannot export the reports from SAP AribaE. Subscriptions are out of dateF. Wrong or missing subscriptions after publish (report names and columns)G. The import or the subflow did not run or failedH. Subscription counts differ from SAP AribaI. Several SAP Ariba sites, realms or profilesJ. Model or entitlement problemsK. Subscription user is empty or wrongL. Last activity is blank or staleM. Subscriptions inactive or disappearing after re-uploadN. No reclamation candidates, or wrong onesO. Reclaim does not remove the user in SAP AribaP. After reclaim: user still active, stuck candidatesQ. Large reports, encoding, timeoutsR. Problems after a clone, upgrade or repair A. SAP Ariba option, application or subflow is missing Symptoms. SAP Ariba is not offered when creating a direct integration profile.The SAP Ariba Download Subscription subflow is not listed.The SAP Ariba Schedule Import business rule is missing. Where to check. Application Manager > SaaS License Management version and status; Flow Designer > Subflows; System Definition > Business Rules. Causes and fixes. Application missing or old. The integration was introduced in the Yokohama release; install or update SaaS License Management.Core UI create option inactive. With Software Asset Workspace installed, create the profile from License operations > User subscriptions > Direct integration profiles > New > SAP Ariba.Business rule or subflow inactive or customized. Compare with a fresh instance; restore the out-of-box record, then repair SaaS License Management if needed (R).Wrong product. Do not install the SAP Ariba Store spoke to get license tracking; it does not provide it (section 1). Verify. The profile type is offered and the subflow is Published. B. The profile cannot be published Symptoms. Please upload all 4 reports and then publish the integration profile.Please upload the reports in .csv format and then publish the integration profileA published profile is back in Draft. Where to check. The profile's attachments (count, type, names); the profile status. Causes and fixes. Not exactly four attachments. The check is a count of all attachments on the profile. Three, five or more all fail. Remove extra files (screenshots, older copies of a report) until exactly four remain.Not .csv. Every attachment must be .csv. Export from SAP Ariba as CSV; do not rename an Excel file. If you open a report in Excel and save it again, save as CSV (Comma delimited).Content type. The type check reads the file's content type, not only the extension. A file whose content type is not text/csv (for example an Excel type after re-saving on some systems) fails even when it ends in .csv. Re-export or re-save as CSV and attach again. This reading comes from the code and is not tested on every browser and operating system.Profile edited after publish. Changing the profile returns it to Draft; publish again.Where Now Assist for SAM is available, the Troubleshoot button may help for runtime failures (section 10); publish messages are shown directly on the form. Verify. Status Published, with no attachment message. C. There is no connection and no Validate Connection button Symptoms. You look for a connection, a credential or Validate Connection and find none.Instructions mention an OAuth token, an API application key or an ANID.A published profile "passes" but data is wrong. Where to check. The profile form; the attachments. Causes and fixes. By design. This profile is not validated against SAP Ariba, because the framework excludes it from the connection-validation requirement. Publishing checks only the attachments (B).Different integration. Guidance for an API-based SAP Ariba connection does not apply; ServiceNow does not call SAP Ariba. The Store spoke is separate.A successful publish is not proof of data. It only proves four .csv files were present. Verify the import and the subscriptions (G, H).MID Server and network. Not involved; the files are uploaded by a person. Verify. You are working from the attachments, import tables and flow executions rather than a connection. D. Cannot export the reports from SAP Ariba Symptoms. A report is missing, empty, or in another format; permission denied in SAP Ariba; columns differ. Where to check. SAP Ariba reporting for each of the four reports; the exported file. Causes and fixes. Permission. The exporting user needs rights to the Sourcing user and permission report, the contract workspace report, the project-creation report and the supplier performance (SPM) project report. The sources do not name the SAP Ariba roles; ask your SAP Ariba administrator.Report names. Use the four report names exactly (section 1); the file name must contain the name.Format. Export as CSV. Keep the first row as the column headings; the import reads the first sheet and treats the first row as the header.Columns changed. If SAP Ariba changed a report layout, the import may not map the new columns (F, G). Compare against a previous good export.Not licensed or enabled. A report for a product you do not use may be empty; check that the SAP Ariba product is enabled for your realm. Verify. Four .csv files, each with data and the original headings. E. Subscriptions are out of date Symptoms. New or removed SAP Ariba users do not appear; last activity does not move. Where to check. The date of the attached reports; the time of the last import. Causes and fixes. Reports are a snapshot. Nothing refreshes by itself. The subscriptions reflect the last reports you attached.Refresh procedure. Export four new reports. Delete the old four attachments from the profile, then attach the four new files (so that the count returns to exactly four). The import starts when the fourth correct attachment is added (G, M).Replacing a single file. A report replaced while the other three stay, or a new file added without deleting the old one, makes the count five. Always return to four.Plan a schedule. Choose how often to refresh (for example monthly) and who does it; the integration cannot do it for you. Verify. The newest report date appears in last activity after the import. F. Wrong or missing subscriptions after publish (report names and columns) Symptoms. Subscriptions are incorrect or only partly created; one report's data is missing. Where to check. The four file names; the four import tables; the data sources. Causes and fixes. File name does not contain the report name. The rule copies a file to its data source only if the name contains Sourcing - User Names and Permissions, All Contract Workspaces, Number of Users Creating Projects or SPM Project Report exactly. Rename the file (a prefix or suffix is fine) and attach it again.Letter case and spacing. The match is case-sensitive; keep the spaces and the hyphen.Hyphen character. A typographic dash instead of a plain hyphen in "Sourcing - User Names and Permissions" will not match.Data source names differ from report names. The data source records use shorter names (for example "Sourcing User and Permission"); the file name matching is what counts, not the data source name.Older release. In some earlier releases the data source definitions needed correction before the subscriptions came out right even with correct file names. Update SaaS License Management; if you cannot, contact support for the fix for your release. Verify. Each of the four import tables shows rows from the current profile's files. G. The import or the subflow did not run or failed Symptoms. Four .csv files are attached, but the import tables are empty or old.The flow execution of SAP Ariba Download Subscription is missing, or failed.Subscriptions are not created. Where to check. System Import Sets > Import Sets and the four tables; Flow Designer executions; System Logs > All for SAP Ariba or ariba. Causes and fixes. Count or type check not met. The import is started only when the profile has exactly four attachments and they are .csv (B). If it was five at the moment of the last attachment, no import ran; fix the count, then add or re-add the last file to retrigger.Rule did not fire. SAP Ariba Schedule Import must be active. It runs asynchronously, so allow a short time after attaching.Scheduled import record changed. The import that is started is a "run once" scheduled import; if it was deleted, deactivated or edited, the rule has nothing to run. Compare with a fresh instance.Import ran, but staging is empty. Open the import set rows and the transform history for errors; a missing or renamed column or a malformed CSV stops the transform. The transform could not be read on the reference instance, so use the import set log for your release.Subflow failed. Open the failing action in Flow Designer and match its message. The subflow looks up the staging rows and creates subscriptions when its conditions match.No subflow run. The sources do not state when the subflow starts (after import or on a schedule). Check the profile's scheduled jobs and the flow trigger on your release.Two runs at once. Wait for the active run to finish before attaching again. Verify. Import tables have rows, staging has active rows for the profile and the subflow shows Completed. H. Subscription counts differ from SAP Ariba Symptoms. Fewer or more subscriptions than users in SAP Ariba; a product is missing. Where to check. The four reports (row counts, products covered); exclusion rules; the staging table. Causes and fixes. Only four reports are read. Users and products that do not appear in those four reports are not counted. Compare the reports' row counts with the subscriptions.Same user in several reports. One person may appear in more than one report; the integration builds subscriptions from the combined data, so counts per user can exceed one.Exclusion rules. Subscription Identifier Exclusion Rule and Subscription User Exclusion Rule silently drop matching rows.Old reports. Users added or removed since the export are missing or still present (E).Inactive staging rows. Adding an attachment sets staging rows inactive until the import finishes (M).Which products. The sources describe "distinct SAP Ariba products" without a complete list; open the generated software models to see which were created. Verify. Subscription counts match the report rows you expect. I. Several SAP Ariba sites, realms or profiles Symptoms. A second SAP Ariba site or realm is not imported; data from two profiles is mixed. Where to check. Each profile's attachments; the data source attachments. Causes and fixes. One profile per set of reports. Each profile holds its own four reports.Shared data sources. Each report type has a single data source, and the file is copied to it with the profile's ID in the file name. Two profiles attached at nearly the same time can therefore compete for the same import. This is inferred from the code; attach and finish one profile before starting the next.Do not merge sites in one export. Keep realms separate and give each profile its own reports.Not documented. The sources do not describe multi-realm behavior; test one profile first. Verify. Each profile shows only its own realm's users. J. Model or entitlement problems Symptoms. A raw identifier and no software model; entries under Unrecognized Subscription Identifiers; compliance shows nothing. Where to check. Profile > Software Models and Unrecognized Subscription Identifiers; entitlements. Causes and fixes. Entitlements missing. Software models and reclamation rules are created automatically; entitlements are not. Create entitlements for the SAP Ariba models and run reconciliation.License to model mapping. The sources do not say how the report columns map to models; open the generated models and compare them with your SAP Ariba contract.Unknown identifier. Open it under Unrecognized Subscription Identifiers, set the correct software model and save.Content out of date. Download current subscription-identifier content.Product settings. Check the Ignore Installs flag on the product definition if analytics counts look wrong. Verify. Subscriptions show the SAP Ariba model and reconciliation produces results. K. Subscription user is empty or wrong Symptoms. Subscriptions with an identifier but no User; records on the Subscriptions without user page. Where to check. sys_user email and user ID versus the SAP Ariba user ID in the report; User resolution rules; sn_itam_samp.user_resolution_exclude_table. Causes and fixes. No match. The report's user name or ID may not equal the email in sys_user. Align the data or add a user resolution rule (Software Asset Workspace > License operations > User subscription > User resolution rules), then rerun the import.Same email in several user tables. List the extra tables in sn_itam_samp.user_resolution_exclude_table.Manual edits overwritten. The User field is recalculated each run.Rules created later. An older version filled the user only for new records after a rule was created; update the application. Verify. The subscription shows the intended user. L. Last activity is blank or stale Symptoms. SAP Ariba subscriptions have no last activity, or it does not move. Where to check. The date columns in the reports; the staging table's last activity; the subscription's last activity. Causes and fixes. What it measures. Last activity is a date from the reports, not a live sign-in. A user with no date in the reports has no last activity.Reports not refreshed. Nothing moves until you attach newer reports (E).No activity subflow or job. The reference instance has only the download subflow; activity does not update separately.Import not finished. If the staging rows are still inactive or missing, last activity cannot update (G, M).Never cleared. Last activity only moves forward; an older report does not lower it.Which report provides it. The sources do not say which report supplies the date; compare a known active user across the four files. Verify. A user active after the previous export shows the newer date after the next upload. M. Subscriptions inactive or disappearing after re-uploadactive = false Symptoms. After attaching new files, subscriptions vanish or stop updating for a time; staging rows show active = false. Where to check. samp_subscription_staging filtered by your profile; the time of the last attachment. Causes and fixes. By design. Each attachment event sets all active staging rows for the profile inactive before importing. New active rows appear only after the import finishes with four .csv files.Import never started. If the count or type check failed (B, G), the staging rows stay inactive. Fix the attachments and re-add the last file.Slow or partial replacement. Replace all four files in one sitting; leaving the profile with three files for a long time keeps staging inactive.Rows for no profile. The inactive step also covers staging rows with an empty profile; do not edit staging rows by hand.Confirm before cleanup. Check staging and the next subflow run before deleting subscriptions. Verify. Staging has active rows for the profile and subscriptions are present after the next subflow run. N. No reclamation candidates, or wrong ones Symptoms. Inactive users get no candidate; active users are proposed for removal. Where to check. The SAP Ariba reclamation rule; subscriptions' user and last activity; existing candidates. Causes and fixes. Last activity blank or old. Candidates depend on last activity; fix E and L first. A user with no date can look inactive.Rule configuration. A rule with a 60-day threshold is created automatically, once. Confirm Create reclamation candidate is checked and the threshold is what you want. Do not delete the rule while the profile is active.Reports out of date. Old reports make everyone look inactive; refresh first (E).User empty. With Notify user on, a candidate without a user goes to Attention Required; fix K.Candidate states. Attention Required, Ready, Awaiting User, Awaiting Approval, Awaiting Revocation, Closed Complete, Closed Skipped, Closed Canceled (cancelled when activity is detected).Review before acting. Reclamation here is manual in SAP Ariba (O); review each candidate. Verify. A user inactive beyond the threshold receives one candidate; active users do not. O. Reclaim does not remove the user in SAP Ariba Symptoms. A candidate is approved but the user still has access in SAP Ariba.The candidate waits in Awaiting Revocation.This subscription cannot be auto-reclaimed. It must be deleted manually Where to check. The candidate; SAP Ariba user administration; the profile options. Causes and fixes. No write-back. ServiceNow does not call SAP Ariba. No reclaim subflow exists on the reference instance, and the reports are read-only input. This is the expected behavior.Manual removal. Remove or deactivate the user's access in SAP Ariba, then close the candidate (for example Closed Skipped if you handled it yourself, or Closed Complete per your process).Message above. It is the framework's text for profile types with no automatic reclaim route; it is consistent with this profile, but the routing table could not be read, so confirm on your release.Custom automation. If you build your own removal, test with one user and keep it outside this profile. Verify. The user is removed in SAP Ariba, the candidate is closed, and after the next reports the subscription is gone. P. After reclaim: user still active, stuck candidates Symptoms. The subscription reappears after the next upload.A candidate stays open. Where to check. The user in SAP Ariba; the date of the report; the candidate's state. Causes and fixes. User still in SAP Ariba. If the user still holds access when the next reports are exported, the subscription is created again.Old report used. Export a fresh report after the removal.Candidate stays open. Close it manually once the user is removed, or let it close after the subscription disappears on a later import.Wrong user removed. ServiceNow does not reverse a manual change; restore the access in SAP Ariba. Verify. The user is gone from the next set of reports and from subscriptions. Q. Large reports, encoding, timeouts Symptoms. Import takes a long time; fewer rows imported than in the file; garbled characters; a failed import with a size message. Where to check. The import set row counts; the file size; the system log. Causes and fixes. Limits. The sources document no row or size limit for these imports. Compare the number of rows in the file with the number of import rows.Encoding. Save the CSV as UTF-8; a different encoding can garble names and break user matching.Commas and quotes in values. A malformed CSV (unquoted commas) shifts columns; export again rather than editing by hand.Extra header or footer rows. The first row must be the header; remove report titles added above it.Run off peak. Attach large files outside business hours. Verify. Rows imported equal rows in the file and the import completes. R. Problems after a clone, upgrade or repair Symptoms. The profile type or subflow is missing after an upgrade; attachments are gone after a clone; the import does not start. Where to check. Installed versions; customizations of SaaS License Management; the profile's attachments; the SAP Ariba Schedule Import rule. Causes and fixes. Attachments after a clone. Clones may not carry attachments or the imported data; attach the four reports again on the target instance.Rule or scheduled import changed. Restore the out-of-box business rule and scheduled import; repair only SaaS License Management.Form damaged by customization. Check customized files for the profile form, set them to be replaced on upgrade, then repair.Versions out of step. Keep SaaS License Management current. Verify. Four attachments, a completed import and a completed subflow run in the target instance. 6. Cause-specific correction and controlled recovery Attaching reports sets staging rows inactive and starts an import; deleting attachments changes what is imported. Obtain approval before changing production profiles. Established causeCorrection ownerControlled recovery and stop conditionApplication or subflowServiceNow platform administratorUpdate, repair, publishAttachment count, type or namesIntegration ownerReturn to exactly four .csv files with correct names, publishSAP Ariba exportSAP Ariba administratorRe-export all four reports, attach againImport or subflowSAM administratorCheck the import set and flow execution, retrigger by adding the fourth fileCoverage (reports, exclusions)Integration ownerUse exclusion rules, run once, compare countsMapping and user resolutionSAM administratorCreate entitlements, add rules, rerunLast activitySAM integration ownerRefresh reports, check the importReclaimSAM process owner and SAP Ariba administratorReview candidates, remove in SAP Ariba, close the candidateClone, upgrade, repairPlatform ownerRestore out-of-box components, reattach reports, import once 7. Verification criteria and recovery evidence Verification layerEvidence requiredWhat does not satisfy itConfigurationPublished profile with exactly four .csv attachmentsA Published status with a stale attachment setExecutionImport set rows and a completed subflow executionAttachments present with no importCoverageSubscriptions match the users in the four reportsTotals that ignore the report row countsMatchingSAP Ariba model and user on every subscriptionRaw identifiers as display namesActivityThe newer report date in last activityBlank activity read as inactivityReclaimUser removed in SAP Ariba and absent from the next reportsCandidate closed without the SAP Ariba change 8. Escalation evidence to collect Application and platform versions; recent upgrades, repairs or clones.Profile status; the number, names (without customer data), types and dates of the attachments.Import set names, row counts and any transform errors; staging row counts (active and inactive) for the profile.The flow execution, failing action and message; the matching system log lines.Number of rows in each report versus subscriptions created.Steps already taken and results. Never include report contents, user names, emails or realm names in shared evidence. 9. References, processing rules and known limitations Key records Profile type store_sap_ariba_subscription (SAP Ariba Subscription).Subflow: SAP Ariba Download Subscription. No reclaim or activity subflow was found.Business rule SAP Ariba Schedule Import on sys_attachment; script include SAPAribaAttachmentUtil; scheduled import Import Sourcing - User Names and Permissions (run once).Data sources: Sourcing User and Permission, All Contracts Workspace, Number of Users Creating Project, SPM Project Report.Tables: ariba_user_permission, ariba_contract_workspace, ariba_project_owner, ariba_spm_report, samp_subscription_staging, samp_sw_subscription_profile, samp_sw_subscription, samp_sw_unrecognized_subscription_identifier, samp_discovered_user, exclusion rules samp_sw_subscription_id_excl_rule and samp_sw_subscription_user_excl_rule. System properties There are no SAP Ariba-specific debug properties.com.snc.process_flow.reporting.level — set to All for subflow detail; set back afterwards.com.snc.samp.disableeventstorage — when true, usage events are not stored (last activity still updates).sn_itam_samp.user_resolution_exclude_table — sys_user extended tables excluded from user matching. Processing rules to remember No connection, credential or Validate Connection; publish checks only the attachments.Exactly four attachments, all .csv; every attachment on the profile is counted.A file is used only if its name contains the report name (case-sensitive).Each attachment sets the profile's staging rows inactive; the import starts when the fourth correct file is attached.Data is a snapshot of the last reports; last activity comes from report dates and only moves forward.No write-back to SAP Ariba; reclamation is manual.A default reclamation rule of 60 days is created once. Known limitations The mapping from report columns to licenses and models is not stated in the sources.The transform into the staging table and the trigger of the subflow could not be read.The SAP Ariba roles needed to export the reports and any report size limits are not documented here.Which report supplies last activity is not stated.A reclaim action in SAP Ariba is not available from ServiceNow. Documentation ServiceNow product documentation for your release: Integrating with SAP Ariba under Software Asset Management > SaaS License Management.SAP Ariba documentation for exporting reports in your realm.ServiceNow: Configure Now Assist for SAM 10. ServiceNow Otto / Now Assist troubleshooting ServiceNow Otto for Software Asset Management (formerly Now Assist for SAM, application sn_now_assist_sam) adds generative AI help for SaaS integrations. Use it to explain a failed SAP Ariba import or subflow run, and to propose user resolution rules when imported subscriptions do not match users. Treat its output as a starting point: confirm every recommendation against the branch in section 5 before changing configuration. How Troubleshoot works 1Failure bannerProfile in Software Asset WorkspaceFailed job or failed Validate Connection 2TroubleshootButton on the error bannerDebug-level validation, ~15–20 s 3Read guidanceError Summary + Suggested ResolutionsMap each item to a section 5 branch 4Fix and validateApply the fix yourselfValidate Connection again; rerun Troubleshoot if needed 5Publish or runPublish new / run existing jobConfirm with section 7 What the AI skills do SkillWhat it doesWhen it runsDefault model providerError log summarizationReads the logs of the failed run and produces an Error SummaryWhen you click TroubleshootAWS Claude (from Australia Patch 4)Error resolution recommendationTurns the summarized errors into Suggested Resolutions, one per errorChained after the summaryAWS Claude (from Australia Patch 4)SaaS user resolutionProposes user resolution rules that map the SAP Ariba user identifier to sys_userAutomatically after a subscription download, when prerequisites are metAzure OpenAI The model provider can be changed per skill in the Now Assist Admin console; Now LLM Service can still be selected manually. Before you start Installed and licensed. Otto for SAM (sn_now_assist_sam) is installed and your subscription includes generative AI for SAM. Confirm entitlement with your account team. The capability is not available, or is limited, in in-country, FedRAMP, NSC DOD IL5, IRAP-Protected, self-hosted, regulated-market and other restricted environments.Skills active and displayed. Go to All > Now Assist Admin > Skills, choose the SAM workflow group, open each skill and confirm it is active with Display turned on. To activate: Activate skill > Save and continue > Select display (turn on Display, add roles if needed) > Review and activate > Activate. Skills are active by default from Zurich Patch 4, but a skill you deactivate stays off until reactivated.Roles. sam_integrator to use Troubleshoot and SaaS user resolution; skills are available to sam_user and sam_admin by default. If an administrator changed the skill roles, the custom roles apply instead. Activating or configuring skills needs the Now Assist administrator role.Software Asset Workspace. Troubleshoot appears in the workspace profile form, not in the classic form.Privacy. Inputs and outputs are processed in ServiceNow's generative AI environment and may be processed by the selected third-party model provider. Review your organization's AI data-handling settings and the Now Assist opt-out options before use. Use Troubleshoot on a failed run Go to Workspaces > Software Asset Workspace > License operations > User subscription > Direct integration profiles and open the SAP Ariba profile.SAP Ariba has no Validate Connection step. If a subflow run fails, check whether the profile shows an error banner for the failed run; publish problems (attachment count or type) appear as messages on the form and are fixed with branch B. Whether the banner appears for every SAP Ariba failure was not confirmed.Click Troubleshoot on the banner. Otto runs the validation with debug-level logging, summarizes the errors and proposes resolutions. Expect a response in around 15–20 seconds.Read the Error Summary and Suggested Resolutions on the profile. Map each resolution to the matching branch in section 5 and follow that branch's fix and verify steps.Apply the fix yourself (Troubleshoot never changes connection or integration configuration), then attach the reports or rerun the subflow again. Click Troubleshoot again to regenerate guidance if the failure continues.When the fix works, Publish a new profile, or rerun the import for an existing profile, and confirm the result with section 7. What Troubleshoot writes. The error summary and suggested resolutions are stored on the integration profile, and each run is kept in a troubleshooting log shown as a related tab on the profile. It does not modify subscriptions, credentials or jobs. The AI indicator may not appear on these fields when the system rather than the AI last updated them. What it covers. Runtime failures of integration jobs and flows for SaaS and SSO integration profiles. It does not read your report files, so a wrong report or wrong file name is found only through branches B and F. It does not diagnose data-quality questions such as missing users in a product scope, model mapping or reconciliation results; use section 5 for those. AI-generated user resolution rules After each subscription download, SAM checks whether a rule should be generated. The SAM - Generate user resolution rule job calls the SaaS user resolution skill only when at least 10% of subscriptions have no user, and either it is the first run, or the previous run created no rule and the data has changed (a new field or about 10% more user data). Review results: Software Asset Workspace > License operations > SaaS license management > User resolution rules. Rules created by the skill show Source = AI. Steps are listed in the AI activity log in the Activity center on the Software asset overview.Activate deliberately: a generated rule that is inactive shows Review needed. Check it against a few known users, then set it Active and save. Rerun the SAP Ariba import (re-add the fourth report) to apply it.Each run is logged in samp_user_resolution_rule_log with the outcome. When the assistant does not help What you seeLikely causeWhat to doNo Troubleshoot buttonApplication not installed, skill inactive or Display off, missing role, classic form instead of the workspace, or no current failureCheck the prerequisites above; the button appears only on the error banner of a failed runTroubleshoot runs but returns nothing or an errorSkill call or output formatting failedOpen the generative AI log (sys_generative_ai_log.list) for the skill request: error code, message and whether the response was formatted correctly. Check System Logs > Errors for formatting failuresSummary is short, generic or cut offOlder application version with a smaller output limit, or too little log detailUpdate Otto for SAM to the latest version; rerun Troubleshoot after reproducing the failure so fresh logs existRecommendation contradicts the logsAI output is a suggestion, not a verified diagnosisFollow the outbound HTTP status and the matching section 5 branch; report the mismatch with the generative AI log entryProfile reference fields show invalid field name: troubleshooting_logTroubleshooting component not active on an older SaaS License Management versionUpdate SaaS License ManagementUser resolution job ends with "did not meet the pre-requisites" or "no change in your user data"Expected: fewer than 10% unresolved, or nothing changed since the last runNo action; create a rule manually if needed (branch K)User resolution job ends with "failed due to some error in the Gen AI skill"Skill call or output failedCheck sys_generative_ai_log for the skill runNo rule created: "no user table field could uniquely be identified"the SAP Ariba user identifier has no unique exact match in any sys_user fieldCorrect user data or create the rule manually (branch K) Limitations Output is AI-generated and can be inaccurate or incomplete; a person must review it before acting.Only job and validation failures are analyzed; ingestion completeness, mapping, usage and optimization still need section 5.Responses take several seconds because each Troubleshoot click chains more than one model call.Availability depends on your AI entitlement and hosting environment.