Skip to main content

Vendor MDM Application Integration

Vendor MDM application will be integrated with source systems to get the data from and consuming system to provide the golden copy of vendor data.

There are various ways to integrate with source and consuming systems, Below are the options used in SMDS Vendor MDM application to integrate.

Option 1: EMP (Event Management Platform)

Option 2: MQ (Message Queue) , this option will be decommissioned once all consumer connected to this channel are moved to EMP platform.

Source Systems:​

  1. Vendor Portal application
    1. This is UI application as part of SMDS Vendor application
    2. This is owned by SMDS platform, and used by business users who can create/update the vendor data
    3. This will be accessible by only internal Maersk employees
    4. This application will also be used to approve the task pending for approvals
    5. This application is integrated with few validation and enrichment services to ensure data quality
    6. Vendor and Bank entities can be onboarded from this portal
    7. The message structure from UI to Vendor database will be designed and handled by Ingest APIs
  2. ML.com self service portal
    1. This is publicly exposed web portal through which public users can register themselves as Vendor
    2. ML.com will capture the vendor data and feed to SMDS Vendor MDM system by calling Ingest API
    3. This portal will be only used basic details of the Vendor (CO & PO can not be provided by this portal)
    4. This application will be completely under ML.com team
    5. Only Vendor entity can be onboarded from this portal
    6. The message structure Is defined in below sections
  3. SAP ECC
    1. This is SAP application, which will only provide the Company codes, Purchasing Organizations & Vertex Tax details as reference data to SMDS Vendor Application.
    2. The CO, PO and Vertex Details will be defined in SAP ECC and same will be feed to SMDS Vendor application to be used during the Vendor onboarding from Vendor Portal application and during extended vendors with CO/PO for vendors onboarded with ML.com
    3. CO/PO, Vertex tax details will synched from SAP ECC to SMDS Vendor application periodically.
    4. The message structure is defined in below sections, if we sync data by EMP channel

Consuming Systems:​

  1. SAP ECC (New)
  2. SAP TMS (New)
  3. SAP ECC (Old)
  4. SAP TMS (Old)
  5. HSUD
  6. L&S/DAMCO
  7. CUPA

Outbound Messages Structure:​

  • VendorEntity
    • VendorGeneralData
    • ExternalSystemIdentifiers
    • TaxNumberInformation
    • AdditionalTaxInfo
    • AliasNames
    • VendorBankAccRelationships
      • BankAccountInformation
        • BankInformation
    • CustomerInformation
    • BusinessUnitInformation
      • VendorPaymentMethods
      • BusinessUnitTaxWithholding
      • BusinessUnitVendorRelationship
    • PurchasingOrganization
      • VendorPartnerFunction
    • Relationships
    • ContactInformation
      • TelecommunicationInformation
      • ElectronicInformation
      • PostalAddress
      • PostalAddressLocal
    • VendorBusinessUnitRelationshipContact
      • TelecommunicationInformation
      • ElectronicInformation
  • BankEntity
    • BankGeneralData
    • BankAccountsInformation
    • BankContactInformation

Inbound Messages Structure:​

  • BusinessUnitEntity
    • BusinessUnit
    • siteAuditData
  • PurchasingOrganizationEntity
    • PurchasingOrganization
    • siteAuditData
  • VendorEntity
    • VendorGeneralData
    • ExternalSystemIdentifiers
    • TaxNumberInformation
    • AdditionalTaxInfo
    • AliasNames
    • CustomerInformation
    • Relationships
    • ContactInformation
      • TelecommunicationInformation
      • ElectronicInformation
      • PostalAddress
      • PostalAddressLocal

Sample json messages for Vendor, Bank, Purchasing Organization, Company Code.

Was this page helpful?