Got any questions, get in touch and see how we can help.

Contact Us



Discover the variety of Data Objects that Maextro can interact with. Improve your data landscape with a Master Data Management tool that is custom built specifically for the following Data Objects.

data objects icon

How Maextro Transforms Data Objects

Maextro is a master data management system designed to unlock new levels of efficiency in an organisation via governance and automation. Interactions with Data Objects make up a key factor in Maextro’s success. Maextro ensures data quality and maintenance of these Data Objects via automated governance checks throughout the data usage process, including input, sharing and analytics.

What sets Maextro apart from other MDM solutions is a variety of Data Objects already set to fit Maextro deployment from deployment.  Maextro is capable of understanding and processing 16 types of Data Objects, with the potential for creating custom processes for additional Data Objects.

No matter which data object is required at any stage of your business process, you can make progress with certainty that the quality of the data is always at a strategic decision-making level

Data Objects compatible with Maextro

Maextro’s MDM Experts have been continuously building and innovating on Maextros capabilities for more than half a decade. In this time, we have catered for a variety of uncommon and complex business processes, which require uncommon Data Objects. All this experience has been fed back into core Maextro. The Result? Maextro is capable of managing and maintaining a formidable 16 unique Data objects, such as Material Master and Vendor information. Below are the Data Objects Maextro has been designed to Manage.

Supply Chain & Manufacturing Objects

Supply Chain and Manufacturing objects cover a variety of areas. From raw materials to finished products, master data quality is essential at every step of the manufacturing process. Here are the Data Objects Maextro covers for Supply chain and manufacturing:

Product & Material

Supports create, change and extend scenarios.

Mass processing across different org units ( plants, storage location, warehouse and sales org ).

Conditional plant views. Create a material across 2 different plants with 2 different view requirements. For e.g. A material in plant 1000 can be created for Work scheduling view but not in plant 2000.

Ability to create several materials in the single request.

Multiple BAPI calls to update and create a material in the same workflow step. e.g. step 10 creates basic data and in step 20 you can further enrich basic data and create plant data.

Org dependent workflow allows a task to be split across multiple owner groups. For e.g. A purchasing data task can be split across different plant owners based on number of plants being requested for the material.

Cross-object processing capabilities. Link bom, routings and recipes with material workflow.

Mass cleanse of legacy data available through Align tool.

materials object
vendor objects

Vendor, Customer & Business Partner

Supports create, change and extend.

Mass processing across different org units ( company codes & sales org)..

Ability to create several BP’s and its associated roles in the single request.

Auto partner function assignment when multiple BP’s ( sold-to’s and ship-to’s ) are created in the same request. For e.g. if a sold-to and a ship-to is created in the same request, the newly created ship-to can be assigned to a sold-to with one single BAPI interface.

Org dependent workflow allows a task to be split across multiple owner groups. For e.g. A sales data task can be split across different sales owners based on number of sales org being requested for the BP.

Mass cleanse of legacy data available through Align tool.

Material Master

Supports create & change scenarios.

Supports alternate BOM creation

Supports basic item categories Stock items ( L ), Non-stock items ( N ), Text items (T).

Supports BOM creation as ava

material masters object
routing objects


Supports create, change and extend scenarios.

Mass processing capabilities to create multiple routing group counters under one Maextro request no.

Consolidate views for PRT data enrichment.

Simple material bom component allocation screens.

Supports alternate and parallel routing sequences

MIC allocations against operations.




Equipment Masters

extra objects

Financial Objects

GL Account

Supports create, change and extend scenarios.

Allows default field values that are specific to account-types and to configurable sub-account-types.

Mass processing capabilities available to business users:-

Creation of a GL account in multiple company codes within a single request.

Extend multiple accounts to a company codes within a single request.

Mass change of field values at company code level, for a selected GL account.

Org dependent workflow allows a task to be split across multiple owner groups. For example, the collection and approval of country-specific data can be allocated to multiple regional data owners, while centralized data is processed at the global level.

From the GL account display screen in SAP, users can directly access the Maextro requests responsible for maintaining the GL account data.

general ledger
system objects

Project systems & Work Breakdown Structure

Supports create, change and extend scenarios.

Supports user defined WBS structure. All required WBS levels can predefined in Maextro for easy selection and data enrichments.

Supports user defined fields

Follow on function to create sales orders against WBS no.

Cost Element

Supports Cost Element in Breaking down line items into individual cost elements

Cost Centre

Supports Cost center create and change scenarios.

Profit Centre

Supports Profit center create, change and extend scenarios


Supports Asset create, change and extend scenarios

financial data objects icons

Custom Data Objects

Maextro is also capable of supporting Data Objects unspecified above. The built-in flexibility enables Maextro to be quickly adapted to supported other Data Objects as required. If you are currently using a Data Object unspecified above or would like to know more about how Maextro can help manage your Data Objects, get in touch with our Master Data Experts today.

Data Objects best practices

In order for Data objects to serve their purpose effectively, there are a few best practices for that must be respected. However, when looking at business object best practices, we need to shift our focus outward to everything hanging around the object, rather than the object itself. As an object, it’s fine on its own. With Maextro, objects come pre-configured with the option to modify but are generally ‘plug and play’. To ensure they are being used correctly, consider:

Data cleansing- Is the data going into the object being maintained and ran through a cleansing program regularly to preserve data quality?

Managing data quality- Business Objects Master Data Management is essential to get the most out of data objects. Audits can be undertaken via governance automation tools to regularly preserve data quality without the potential for user errors.

Consider interdependencies- how various objects interact with each other at various stages of the process and where there is potential for duplication or errors to occur.

If best practices were not followed for a Customer Object, organisations would not be able to add delivery notes, raise sales orders correctly or raise invoices, which could create a knock-on effect to cashflow, slowing business operations.

Data Objects Migration

With the imminent, if not already due migration from SAP ECC to SAP S/4HANA, it may leave many CDOs wondering what impact this could have on existing Data Objects. Maextro supports data object migrations by aligning data records and remediating data records before migrating- removing the need for manual governance audits prior to making the move.

However, it is worth noting that Vendor & Customer Data Objects have been merged into Business Partner Data Objects. This will make it easier to support the wider landscape of process transactions.

Consideration for Data Object dependencies are also essential for migrating data objects. This is where a parent topic, relies on drawing data from the Data Object. When migrating Data Objects over, the dependencies must follow in order for the higher data objects to function properly.

Discover how Maextro can interact with your Data Objects

Maextro is a solution that has been built to support multiple Data Objects, increasing data efficiency and quality. Taking care of master data on this level creates a culture for innovation, and better decision-making and helps drive Enterprises forward. Discover how Maextro can support your Data Objects today by registering for a live demo below.


Data object is a term used to group specific sets of data based on their values or topic. It’s used as a way to differentiate various data points that should be thought of separately from the main master data. Each Data object normally relates to a specific business function. They are essential to define the information used in the business function and the variables needed for that process.

Data Objects can encompass many aspects of organisational data, including Material Master, Routing, Recipe, vendor, etc. An example of a data object would be the representation of all vendor data for an organisation. The values within the data object would include a name, address and/or other relevant information that are essential to business processes.

Put simply, Data Objects are data silos based on specific topics that form a wider business process.

There are many types of data objects, serving many areas of business processes. Broadly, there are two main types of data objects- supply chain & manufacturing and Finance.

Common manufacturing object types include:
• Material Master: which contains data on the storage, use, purchasing and selling of materials used by a manufacturer.
• Business Partner: this acts as a single point of entry for data on both customers and vendors- combining the previously two separate objects.
• Recipe Management: This is essential for correctly manufacturing consumed products- like food or medicine. This is a point of entry for all data on recipe quantities, ingredients and production. It’s essential for large-scale food manufacturers and pharmaceutical companies.

Common Financial object types include:
• GL Account: this is an object which creates the means to record a company's overall finances, including assets, liabilities, equity, expenses, and income or revenue.
• Cost Centre: this is used to identify where companies are making a loss, track these events and group them together so that they can be rectified.
• Profit Centre: this is a single point of entry for data from financial statements, profit and loss statements & balance sheets with the goal of recording where profits are being created from and enabling full reporting on this.

Data objects are a way of defining structure for specific types of business data, an example can be ‘Business Partner’, ‘Materials’ or ‘Products’. Within these objects, data can be represented as Boolean, email, names, addresses and numbers.

A data object is just an object stored in SAP (or other systems). It is the building block upon which all other functions and transactions rely. Whereas a data set is a collection of data which forms a part of a wider database.