Prove partner selection, access and the assessed capture Use a Public Edition test tenant, two distinguishable business partners and two Seal test groups. One group should use the library; the other should have no library access through any membership. Keep the first evaluation limited to identity references and optional copies so the result can be checked end to end. FIRST RUN 1. Prepare the inbound communication arrangement The SAP administrator creates a dedicated communication user, assigns it to the communication system and creates the SAP_COM_0008 arrangement with Basic authentication for the inbound service. Record the test tenant, arrangement and API URL supplied by that setup. Use the communication user credentials in Seal’s setup, not a business user’s browser session. Check: The SAP owner can identify the arrangement and its inbound user. The endpoint belongs to the intended Public Edition tenant. Keep the username’s purpose and credential owner in the handover, while keeping its password out of screenshots and downloadable evidence. SAP sample: communication settings and Basic authentication: https://github.com/SAP-samples/btp-s4hana-nocode-extension/blob/main/setup/s4hc-setup/setup-s4hc-system.md 2. Connect and constrain the initial population Open Settings → Integrations → Set up SAP S/4HANA. Enter the API URL and communication credentials, then choose Test and connect. Select the intended test partner and Seal group. Review the copied-field preview before enabling the library; record that field list with the evaluation. Check: The selected partner key and displayed identity agree with SAP. Confirm that bank details, addresses and transactions are absent from the intended copy. A request for those fields changes the project scope and needs a separate supported design. 3. Inspect the reference as the actual reviewer Open a test supplier assessment as a user in the intended Seal group and choose the selected partner. Inspect the available reference and optional captured copy. Repeat the selection as a user in the unrelated group, checking that this user has no other membership granting access. Check: The permitted user can identify the correct partner; the unrelated user cannot browse the library through unintended group access. Check any separately shared assessment or captured record under its own permissions too: library access and access to an already shared review are different questions. 4. Capture the assessment’s identity basis For the fictional SUP-045 example, retain the first identity capture with the assessment and inspect the reference mode used. Record the source environment, partner key, retrieval time, copied values and actual content-based Seal version. Capture-A below is a readable placeholder for that version. Check: A reviewer can reconstruct which identity supported the assessment. Do not label the content hash an SAP revision, and do not use the existence of the partner reference as evidence that the supplier is qualified. 5. Evaluate a later change without rewriting the earlier decision With the test-data owner, change the test partner’s name in SAP and retrieve it through the supported library workflow again. Compare the copied values and resulting capture. Reopen SUP-045 to inspect its earlier evidence, then document whether the supplier owner needs a reassessment. Check: The earlier assessed identity remains identifiable and the later changed content can be inspected separately. Record the observed retrieval behavior; this test does not establish continuous synchronization, a refresh interval or complete SAP audit-history replication. What belongs in the supplier identity handover Use the actual field preview from this library. The labels below describe review evidence rather than additional SAP fields promised by the connector. Evidence: Environment and partner Worked value: Test tenant / 100045 What to establish: Resolve the source key without matching solely on a display name. Evidence: Selected library group Worked value: Supplier reviewers (test) What to establish: Verify access using the intended member and an unrelated user. Evidence: Copied-field list Worked value: Saved setup preview What to establish: Confirm exactly which identity values were included. Evidence: Assessed capture Worked value: SUP-045 / capture-A What to establish: Identify the actual Seal version supporting the assessment. Evidence: Change assessment Worked value: Name changed / owner review pending What to establish: Retain the supporting supplier evidence and unresolved decision. A completed first-run review note Fictional outcome format for a test run; this is neither an API request nor evidence that the checks have run in your tenant. Review: SUP-045 Source: Public Edition test tenant / partner 100045 Selection: one partner; Supplier reviewers (test) Copy scope: saved identity-field preview Original assessment: capture-A / North Coast Materials Ltd Later observation: capture-B / North Coast Process Materials Ltd Library access: intended member passed; unrelated member denied Open action: supplier owner to assess the name-change evidence Manufacturing transactions: outside this evaluation This note separates a successful connection test from the remaining supplier decision. Replace the capture placeholders and access outcomes with observed evidence before using it as a project handover. PROPOSED RECEIVING CHECKS — NOT EXECUTED CUSTOMER VALIDATION Two partners share a name Input: Use two test partner keys with the same display name, selecting only the intended key. Expected: The review resolves the selected partner by environment and key. It neither merges both partners nor grants selection to the other key because its name matches. A user belongs to another permitted group Input: Check a test user who is absent from the selected group but has a second membership that grants the same access. Expected: Explain the effective membership before declaring the access control broken. Repeat with a genuinely unrelated user and record both results. The copied identity changes after assessment Input: Run the two-capture example and inspect the existing SUP-045 evidence. Expected: The assessed identity and later observation remain distinguishable. Supplier qualification is reconsidered only through its review, not automatically granted by the latest name. A manufacturing team asks for stock movements Input: Try to specify a consumption-reconciliation report from the selected partner library alone. Expected: The missing transaction evidence is explicit. The handover scopes a separate manufacturing operation and recovery contract instead of implying that SAP_COM_0008 setup has enabled it. HANDOFF Retain the tenant and arrangement identifiers, copied-field preview, selected partners and groups, effective-access results, capture comparison and supplier owner’s open actions. This gives the implementation team a bounded, reviewable library setup and gives quality reviewers a usable identity trail.