1. Context & Scope

1.1 Business Context

Within the SyWay Source-to-Pay transformation, supplier collaboration must support a broad range of processes:

  • Procurement execution (PO, ASN, SES, Invoice)
  • Supplier lifecycle (qualification, onboarding, enablement)
  • Logistics collaboration (carrier integration)
  • Integration with S2S (Product Compliance) and S2P (Procurement)
  • Regulatory compliance (e-invoicing)

As identified during workshops, standard solutions (S/4 + Ariba) do not fully cover the required collaboration scope, especially for:

  • Long-tail suppliers
  • Operational collaboration scenarios (consignment, subcontracting, services)
  • Flexible qualification logic

Therefore, a custom SAP BTP Supplier Portal is introduced as the primary interaction channel

1.2 Solution Scope

The scope is aligned with the “orange areas” from the functional scope diagram below


In Scope

  • Supplier collaboration (PO, ASN, SES, Invoice, etc.)
  • Supplier Qualification
  • Supplier Onboarding (data + enablement)
  • Supplier User Management
  • Integration with S/4HANA core processes

Out of Scope (Future Waves)

  • Supplier Risk Management
  • Advanced ESG scoring
  • Supplier 360 analytics
  • Extended lifecycle automation

2. Target Architecture Overview

2.1 Hybrid Supplier Collaboration Model


ChannelRoleUsage ScopeArchitecture Position
Ariba SourcingSourcing platformUsed for all suppliers for RFx / sourcing eventsUpstream (Pre-Procurement)
SyWay Supplier Portal (BTP)Qualification platformUsed for all suppliers for qualification & onboardingLifecycle / Governance Layer
SyWay Supplier Portal (BTP)Operational collaborationDefault platform for PO collaboration (non-BN suppliers)Execution Layer (Default)
SAP Business Network (BN)Strategic collaborationUsed for selected/high-volume suppliers for PO, ASN, invoicingExecution Layer (Selective)
SAP Business Network for Logistics (BN4L)Carrier collaborationUsed for all carriers globallyLogistics Layer
EDICOME-invoicing complianceUsed for country-specific e-invoicing regulationsRegulatory / Compliance Layer

2.2 Architectural Principles

  • S/4HANA = System of Record
    • ZQUAL = Qualification Source of Truth
  • BTP = Supplier Interaction Layer

3. Solution Structure

3.1 Base Solution — Supplier Collaboration (ERP-1162)

Purpose

Enable operational collaboration between suppliers and S/4HANA

  • operational flexibility

  • supplier adoption

  • automation for high-volume suppliers

  • long-tail supplier accessibility

Functional Scope

From scope diagram :

  • Purchase Orders & Scheduling Agreements
  • Goods Receipt / Returns
  • Consignment / Subcontracting
  • Service Entry Sheets
  • Invoicing / Credit Memo
  • Payment visibility
  • Quality interactions

3.2 Supplier Lifecycle Add-on (ERP-2089)

Purpose

Provide supplier governance layer:

  • Qualification
  • Onboarding
  • Eligibility control

Qualification Model

Event-driven (NPI / MOC / Sourcing / Risk)

Supported Qualification Levels

  • Supplier
  • Supplier + Country
  • Supplier + MGC
  • Supplier + Material
  • Supplier + Material + Application

Core Data Model

ZQUAL (Custom Table in S/4) = Single Source of Truth

  • Stores:
    • Scope
    • Answers
    • Validity
  • No duplication of SAP standard data

4. Application Architecture

4.1. BTP Application Landscape

DomainApplicationCapabilitiesDescription
Lifecycle (Governance)My Compliance & QualificationQuestionnaire ExecutionSuppliers receive and complete qualification questionnaires (multi-level scope: Supplier / MGC / Material / Country)
Lifecycle (Governance)My Compliance & QualificationDynamic FormsQuestionnaire content dynamically adjusted based on scope, category, and regulatory context
Lifecycle (Governance)My Compliance & QualificationDocument UploadSuppliers upload certificates and supporting documents (OpenText integration)
Lifecycle (Governance)My Compliance & QualificationStatus TrackingTrack qualification lifecycle (Draft, Submitted, Rework, Approved, Rejected, Expiring)
Lifecycle (Governance)Company InformationSupplier Data MaintenanceSuppliers maintain company data, contacts, and banking information
Lifecycle (Governance)Company InformationData SynchronizationData submitted and synchronized to S/4HANA Business Partner
Lifecycle (Governance)Manage User AccessUser ManagementSupplier Admin creates and manages users within their organization
Lifecycle (Governance)Manage User AccessRole AssignmentAssign roles (Admin / Contributor) and control access to portal apps
Lifecycle (Governance)Manage User AccessIdentity IntegrationIntegration with IAS/IPS for authentication and provisioning
Collaboration (Execution)Procurement CollaborationPurchase Order VisibilitySuppliers access and monitor purchase orders
Collaboration (Execution)Procurement CollaborationOrder ConfirmationSuppliers confirm purchase orders directly via portal
Collaboration (Execution)Logistics CollaborationAdvance Shipment Notice (ASN)Suppliers submit shipment notifications to S/4HANA
Collaboration (Execution)Logistics CollaborationGoods Receipt VisibilitySuppliers track goods receipt status
Collaboration (Execution)Logistics CollaborationReturns ManagementManage return POs and shipment notifications
Collaboration (Execution)Inventory & ManufacturingConsignment ManagementManage consignment stock and withdrawals
Collaboration (Execution)Inventory & ManufacturingSubcontractingManage component shipments and consumption
Collaboration (Execution)Inventory & ManufacturingComponent Inventory VisibilityView supplier-managed inventory levels
Collaboration (Execution)Service CollaborationService Entry Sheet (SES)Suppliers submit service confirmations
Collaboration (Execution)Service CollaborationTime Entry SheetSubmit time-based service activities
Collaboration (Execution)Finance CollaborationInvoice SubmissionSubmit invoices for non e-invoicing countries
Collaboration (Execution)Finance CollaborationCredit MemoSubmit invoice corrections
Collaboration (Execution)Finance CollaborationPayment VisibilityTrack invoice payment status

5. Integration Architecture

DomainSourceTargetObjectDirectionTriggerTechnologyNotes
Procurement CollaborationS/4BTP PortalPurchase OrderOutboundPO creation/changeOData APISupplier views PO
Procurement CollaborationBTP PortalS/4Order ConfirmationInboundSupplier actionOData APISupplier confirms PO
Logistics CollaborationBTP PortalS/4ASNInboundSupplier submissionOData APIShipment notification
Logistics CollaborationS/4BTP PortalGoods Receipt StatusOutboundGR postingAPIVisibility only
Service CollaborationBTP PortalS/4Service Entry SheetInboundSupplier submissionOData APISES submission
Service CollaborationS/4BTP PortalSES StatusOutboundApproval/rejectionAPIStatus feedback
Finance CollaborationBTP PortalS/4InvoiceInboundSupplier submissionOData APIOnly for non e-invoicing countries
Finance CollaborationBTP PortalS/4Credit MemoInboundSupplier submissionOData APICorrections
Finance CollaborationS/4BTP PortalPayment StatusOutboundPayment postingAPIVisibility
Qualification LifecycleS/4BTP PortalQuestionnaire AssignmentOutboundBuyer actionAPITrigger qualification
Qualification LifecycleBTP PortalS/4Questionnaire ResponsesInboundSupplier submissionAPIStored in ZQUAL
Qualification LifecycleS/4BTP PortalQualification StatusOutboundApproval/ReworkAPIFeedback to supplier
OnboardingBTP PortalS/4Supplier Data (BP)InboundSupplier updateAPICompany / Bank / Contacts
User ManagementS/4 / BTPIASUser ProvisioningOutboundSupplier activationSCIM APIIdentity & access
Document ManagementBTP PortalOpenTextAttachmentsOutboundUploadAPIStore documents
Document ManagementOpenTextBTP PortalAttachmentsInboundRetrievalAPIDisplay documents

Jira Cards

Functional Specs

  • No labels