SMDS Vendor Data Architecture

Upstream/Sourcing systems:

http://ml.com : is the upstream system which will request to create the Vendor entity.

Vendor Portal: this is the UI component of Vendor MDM application can be considered as upstream system which will request to create the Vendor and Bank entity.

SAP ECC (H4 HANA): is the upstream system which will provide only the Reference data related to Company Code, Purchasing Organization and Vertex Tax mapping information on weekly basis

HSUD/L&S/CW: These are existing running applications to onboard vendor data. Once the Vendor modernization is done and all the data from these applications is migrated to new system, all these applications will be decommissioned.

NFTP: New Finance and Tax Platform is exiting SAP solution and which will continue under SAP solution. This system will go out of picture once the data from this systems get migrated to new modernized Vendor application.

Downstream/Consuming systems:

SAP ECC (H4 HANA): New SAP ECC application as consumer to consume the vendor entity data for billing and invoice purpose.

SAP TMS: SAP Transportation and Management System, will consumer Vendor entity data.

CUPA:

HSUD: This will consume the vendor data to feed its consumers. This will get decommissioned post all its consumers consume the vendor feed from EMP

L&S: This will consume the vendor data to feed its consumers. This will get decommissioned post all its consumers consume the vendor feed from EMP

SAP ECC (Old) (MQ Channel): Old SAP ECC application as consumer to consume the vendor entity data for billing and invoice purpose. This will continue to consume until this this system gets sunset.

SAP TMS (MQ Channel): SAP Transportation and Management System, will consumer Vendor entity data. This will continue to consume until this this old system gets sunset and new SAP TMS is live and all data from old to new system gets migrated.