Arch announces Looply for SAP MDG

Arch launches new Looply Packaged Service for SAP MDG

Arch has launched a new Looply Packaged Service for SAP MDG, designed to make it easier for business users to participate in SAP Master Data Governance processes through Microsoft Teams.

The packaged service extends existing SAP MDG Change Request workflows into Teams without replacing the underlying MDG process. SAP MDG continues to control the Change Request, workflow routing, business rules, validations and final processing, while Looply presents the relevant workflow step and business context to the user in Microsoft Teams.

Depending on the nature of the workflow step, users can either act directly from the Teams card or continue processing in SAP.

For straightforward approval steps, Looply can present the relevant Change Request information together with Approve and Reject actions, allowing the user to complete the decision without opening SAP.

Where additional data entry, enrichment or specialist processing is required, the Teams card provides the user with the relevant context and then directs them to the appropriate SAP Fiori or NetWeaver Business Client application.

A reusable framework for SAP MDG

A key feature of the new packaged service is that it is designed as a reusable, configuration-driven framework, rather than a bespoke integration for an individual Change Request type.

Looply dynamically reads the structure of the SAP MDG Change Request and can use the headings defined in the SAP floorplan to organise information into logical sections on the Teams card.

Additional configuration can be used to control elements such as:

  • field ordering;
  • presentation sections;
  • workflow-step behaviour; and
  • how individual MDG scenarios should be presented to the user.

Where more specific business interpretation is required, the framework can also be selectively enhanced without creating a completely separate application for each Change Request type.

This means the same underlying approach can be applied progressively across different SAP MDG business models, including Supplier and Business Partner, Customer, Material and Financial Master Data.

Keeping governance in SAP

The objective is not to move SAP MDG into Teams.

Instead, Looply provides a simpler way for occasional users, managers and business approvers to participate in the governance process while SAP remains the system responsible for controlling it.

This can help reduce reliance on email notifications and SAP worklists, while giving users clearer business context at the point where a decision is required.

It also gives organisations a practical way to expand the use of Teams across MDG processes without repeatedly designing and developing new integrations.

See Looply for SAP MDG in action

You can find full details of the new packaged service here:

Explore the Looply Packaged Service for SAP MDG

We have also published a demonstration showing how an SAP MDG Change Request can be presented and processed through Microsoft Teams:

Watch the Looply for SAP MDG demo

For more background on the business case for bringing SAP MDG processes into Teams, read:

Accelerating SAP MDG Processes with Microsoft Teams

Keep the governance in SAP. Bring the work to the user.