Senior ERP master data cleansing: products and derivations
How to clean up the product master in Senior ERP: families, derivations, cascading status, NCM, per company products and suppliers, per official docs.
To clean up the product master in Senior ERP, start with the hierarchy, not the item: origin, family, derivation mask, product and derivation, in that order. In Senior the family passes parameters down to the product and status changes cascade, so a poorly planned fix can deactivate a lot at once. Then move on to the tax classification, the product to supplier link, the product in each company and the supplier master.
Senior Sistemas is a Brazilian software vendor, and its ERP is called Gestão Empresarial | ERP (business management ERP). Its official documentation, cited throughout this article, is in Portuguese, so screen and field names appear in their original form with an explanation in parentheses the first time.
Picture this (hypothetical) scene: an analyst finds three codes for the same glove, one per size. They decide to clean up and deactivate two of them. The following week, the purchase order for size L does not go through, because that code was the only one linked to the right supplier.
What was missing was knowing how Senior ties one record to another before touching anything. This guide is based on Senior's official documentation for version 5.10.4, and it keeps the system's rules apart from our own recommendations.
What does Senior mean by "product"?
Senior's documentation defines the product master as the record for consumables, raw materials, assembly items, intermediates and finished goods for sale. Each product belongs to a Família (family), and each family belongs to an Origem (origin). This hierarchical chain provides a set of parameters to the product. The same record holds derivations, characteristics, free text histories and Produtos Equivalentes (equivalent products), and a product can have up to three units of measure (Senior, Product concept).
The full code is product plus Derivação (derivation). According to the documentation, the first part has up to 14 alphanumeric positions and the derivation up to 7. The derivation is an extension of the code for size, measure, dimension, color or a small variation that does not need a new code. Common fields stay on the product and are not repeated (Senior, F084MDP Derivation mask). So part of the cleanup in Senior is deciding what is a product and what is a derivation.
Why start with the family instead of the product?
Senior's documentation says that almost every family parameter is inherited by the product: inventory unit of measure, order quantities and tax information. The family carries origin, Máscara de Derivação (derivation mask), units of measure, product type for taxes, tax classification and tax situation (Senior, F012FAM Family master). On the product, the derivation mask comes from the family and a different one cannot be set (Senior, F075PRO Product master).
If the family is wrong, every new product is born with the same error. Fix the family first, checking whether it groups items that share unit, tax rules and derivation mask.
This is also where taxonomy comes in. In Senior, the family separates products from a commercial point of view and, for purchased items, can relate them to strategic material groups, as long as they share the same unit of measure (Senior, F012FAM). If your company uses UNSPSC, we recommend mapping each family to it before moving products.
What happens when I deactivate a family, a product or a derivation?
Senior's documentation describes the consistency between product and derivation as follows (Senior, F075PRO):
- Deactivating or activating a product deactivates or activates all its derivations.
- Deactivating, unlinking or deleting all derivations deactivates the product.
- Linking an active derivation to an inactive product activates the product; activating a derivation of an inactive product requires activating the product manually.
At family level the rule is stronger. When the family's Situação (status) is set to inactive, all its products and derivations become inactive, regardless of whether they are on open records such as orders, purchase orders and invoices (Senior, F012FAM).
We recommend never deactivating a family as a bulk cleanup move without first listing what is open in it.
Is it a duplicate product or a badly registered derivation?
In Senior, duplicates come in two forms: two codes for the same item, or separate codes for what should be derivations of a single product, such as sizes and colors. The reverse also happens.
Use Senior's own definition as the yardstick. If the difference is size, measure, dimension, color or a small variation, and the common fields are the same, the case tends to be a derivation (Senior, F084MDP). If the variation changes data that lives on the product, such as tax classification, unit of measure or class, we recommend treating it as another product.
Step 1: group candidates by standardized description
Descriptive material standardization (PDM) separates noun, attributes and values, and makes visible the items that differ only in size. The guide on how to identify duplicate materials shows how to build these groups.
Step 2: check the family's derivation mask
Any new derivation must first exist in the derivation mask table, and the possible derivations depend on the mask set on the family (Senior, Product concept). If the family does not have the right mask, converting to derivations starts there.
Step 3: tell duplicates apart from equivalents
In Senior, equivalent products are similar products that can replace the original as alternatives and are suggested when it is missing (Senior, Product concept). An equivalent is for a different item that can be used instead, such as another approved brand. Two codes for the same item are duplicates, and flagging them as equivalents only hides the problem.
Step 4: choose the surviving code
We recommend keeping the code with the most useful history (transactions, supplier link, use in structures) and deactivating the other, with the reason in the history.
Be careful with grid entry. On the F075GRD screen, the "Propor Produtos Possíveis" (propose possible products) option builds every combination of the family's product masks and derivation masks (Senior, F075GRD Grid). Review the proposal before saving.
What gets locked once the product has transactions?
The Classe Produto (product class: inventory, direct pass through, fixed asset or other) cannot be changed when the product already has inventory movements, requisitions, purchase requests or purchase orders (Senior, F075PRO).
The usual path is to create a new code with the right class and retire the old one, with controlling and inventory involved.
When creating those new codes, remember that the documentation advises against special characters: quotes, apostrophes, percent signs, spaces and periods can cause syntax errors in SQL statements (Senior, F075PRO).
How do I check tax classification, CEST and the product to supplier link?
NCM, NBS and CEST are tax codes used in Brazilian operations; check them with your Brazilian tax team.
The documentation describes the Classificação Fiscal (tax classification) field as an internal tax classification code that only accepts the analytic level, with 8 numeric characters in the format XX.XX.XXXX (Senior, F075PRO). Check with your tax team how this internal code relates to the NCM classification in your environment. For services, the tax team also checks the NBS.
The documentation also describes a chain effect when the product to supplier link is active. With the global parameter ExiAtuFis set to S, a change to the tax classification on the product is carried automatically to the Produto x Fornecedor (product to supplier) link and the IPI rate (a Brazilian federal tax on manufactured goods) is updated. With P (the default), the system asks before changing it. With N, the link is not changed. The product also has a field for CEST, suggested on new products from the Classificações Fiscais (tax classifications) screen, and the ExiAtuCes parameter controls whether the system asks to suggest CEST from the classification (Senior, F075PRO).
We recommend two precautions:
- Before fixing the tax classification in bulk, find out how ExiAtuFis and ExiAtuCes are set in your environment, so you know what else will change.
- Check the Tipo produto para impostos (product type for taxes). The documentation lists options 0 to 11 and 99, and points to the Parâmetros por Filial (parameters by branch, F075FPI) screen when the type varies by branch (Senior, F075PRO).
NCM, NBS and CEST are attributes to check against the technical description; the classification itself is a tax decision. The NCM review guide for the material master helps organize that check.
Look at the description too. According to the documentation, the Descrição p/ Nota Fiscal (invoice description) field is only used for printing on continuous forms; for Brazilian electronic invoices (NF-e), the XML uses the Descrição (description) field by default (Senior, F075PRO). The rules on writing material descriptions apply directly to that field.
How do I prove what the cleanup changed?
Senior's documentation says that every change to a product or derivation is written to the E075VPR (product changes) and E075VDR (derivation changes) tables, including grid entry (Senior, F075PRO; Senior, F075GRD). We recommend using these tables as the before and after record of each batch: they show what was changed and help plan a rollback.
Why does a fix in one company not reach the other?
In Senior, the product master is per company: a product is only available in the active company (Senior, F075PRO). For groups with several companies there is automatic duplication of products and services, and its documentation has four points that affect cleansing (Senior, Automatic product/service duplication):
- Duplication is enabled in the source and target companies and also on the family, through the Duplica Produtos Outras Empresas (duplicate products to other companies) field.
- The product arrives with inactive status in the target company.
- The code is only the same in both companies if the family has the same derivation mask and product mask.
- Only new products and derivations are duplicated. Changes to existing products are not replicated.
We recommend a plan per company: for each family, list which companies it exists in and whether the masks match, and treat each company as a batch with its own check.
What about the supplier master?
For suppliers, besides duplicates, what weighs is status that does not match, suppliers left half registered (pre-registration) and outdated tax data. Senior offers control points for this in the supplier master (Senior, F095CAD Supplier master):
- Situação, Motivo Situação and Observação Motivo (status, status reason and reason note). We recommend that every inactive supplier has a reason filled in, so you know whether it was blocked for documents, quality or lack of use.
- Pré Cadastro (pre-registration). When set to "S" (yes), the record is blocked for various operations. We recommend listing stalled pre-registrations and deciding: complete or close.
- Query to SEFAZ. The documentation describes updating customer, supplier and carrier records by querying the centralized registry of SEFAZ (the Brazilian state tax authorities), through the ERP's integration with eDocs. If it exists in your environment, it is the first source to check.
- Customer to supplier link. The RemVinFxC parameter defines whether the Cliente x Fornecedor (customer to supplier) link is removed when the CNPJ/CPF (Brazilian company and individual taxpayer IDs) changes, and AltFisCad defines whether tax fields are updated from customer to supplier and vice versa. Check both before fixing tax IDs in bulk.
For validating tax IDs, state registration and addresses, see the customer and supplier data cleansing page.
Checklist: what to review in the Senior master
The "Who decides" column is our recommendation, not a Senior rule. Adapt it to your company's structure.
| What to check | Warning sign | Batch or item by item | Who decides (recommendation) |
|---|---|---|---|
| Family and origin | Family with items of different units or tax rules | Item by item, per family | Master data with tax and procurement |
| Product vs derivation | Product codes that differ only in size or color | Item by item, per group | Master data with item users |
| Status | Inactive family with open orders; product and derivations whose status does not follow the cascade rule (investigate the cause) | Item by item | Master data with procurement and sales |
| Product class | Wrong class on a product with transactions | Item by item | Controlling with inventory |
| Tax classification (internal code), CEST and product type for taxes | Internal code that, for the tax team, does not match the NCM of the description; CEST empty where the tax team requires it | Batch, after checking parameters | Tax |
| Description | Abbreviated or unreadable text going into the NF-e XML | Batch, with PDM rule | Master data |
| Product per company | Same product with different descriptions across companies | Batch, per company | Master data with IT/ERP |
| Supplier: status and reason | Inactive with no reason; stalled pre-registration | Batch | Procurement |
| Supplier: tax data | State registration that does not match SEFAZ | Batch, with review | Tax with procurement |
Hypothetical example: gloves that became three products
Hypothetical example, created only for illustration. It is not a customer case.
A personal protective equipment family has three product codes: GLOVENITS, GLOVENITM and GLOVENITL. Same description, same supplier, same tax classification. Only the size changes.
- The family has no derivation mask with sizes. The team first registers the mask with components S, M and L.
- They create a product GLOVENIT with three derivations, inheriting the family's mask.
- They check open orders, stock and supplier link for the old codes. Only GLOVENITL has an active product to supplier link, so it is recreated on the new code before anything is deactivated.
- They deactivate the three old codes one by one, with the reason in the history, without touching the family, and check the record in E075VPR and E075VDR.
Where to start
- Map the parameters that change how fixes behave: ExiAtuFis, ExiAtuCes, RemVinFxC, AltFisCad and the cross company duplication setup.
- List families per company, with origin, derivation mask, unit and tax classification. Fix the family before the product.
- Build the description standard and the attribute dictionary for each family, so items are compared with the same yardstick.
- Pick a pilot family, separate duplicates, misregistered derivations and equivalents, and check open orders and the product to supplier link before deactivating.
- Work in small batches, check the history tables and repeat per company.
- In parallel, work on suppliers: status reason, stalled pre-registrations and checks against SEFAZ.
If your group also runs another ERP, note that in Protheus the path is different.
Frequently asked questions
Can I delete duplicate products in Senior ERP?
We recommend deactivating and recording the reason instead of deleting, especially when the code has history. First check open orders and the supplier link.
How do I change the class of a product that already has transactions?
According to Senior's documentation, the class cannot be changed when the product has inventory movements, requisitions, purchase requests or purchase orders. The usual path is to create a new code with the right class and retire the old one, with the controlling team involved.
I fixed the product in one company. Why is the other company in the group still wrong?
In Senior the product master is per company. Automatic duplication only copies new products and derivations; changes to existing products are not replicated. The fix has to be made in each company.
Does changing a product's tax classification change anything else?
It can. According to Senior's documentation, with the product to supplier link active, the ExiAtuFis parameter decides what happens: with S, the tax classification on the link is changed automatically and the IPI rate is updated; with P (the default), the system asks first; with N, the link is not changed. Check the parameter before fixing in bulk.
How 4MDG can help
4MDG does material master data cleansing item by item: it removes duplicates, standardizes descriptions with PDM, classifies items in NCM and UNSPSC, normalizes units of measure and packaging and enriches technical attributes, with a family taxonomy and attribute templates. For third party data, customer and supplier cleansing validates tax IDs, state registration and addresses. To see where your catalog stands, request an assessment or get in touch.
The fields, parameters and screens mentioned vary by version and configuration of Senior ERP. This article uses the documentation for version 5.10.4, which is in Portuguese. Confirm the behavior in your environment with your technical and tax teams before making bulk changes. This content is not tax advice.
Sources
- Senior Sistemas, Portal de Documentação, "Produto". https://documentacao.senior.com.br/gestaoempresarialerp/5.10.4/menu_cadastros/conceito_produto/. Accessed on November 17, 2026.
- Senior Sistemas, Portal de Documentação, "F075PRO - Cadastro de Produtos". https://documentacao.senior.com.br/gestaoempresarialerp/5.10.4/menu_cadastros/f075pro/. Accessed on November 17, 2026.
- Senior Sistemas, Portal de Documentação, "F084MDP - Máscara de Derivação". https://documentacao.senior.com.br/gestaoempresarialerp/5.10.4/Menu_Cadastros/f084mdp/. Accessed on November 17, 2026.
- Senior Sistemas, Portal de Documentação, "F075GRD - Grade". https://documentacao.senior.com.br/gestaoempresarialerp/5.10.4/menu_cadastros/f075grd/. Accessed on November 17, 2026.
- Senior Sistemas, Portal de Documentação, "F012FAM - Cadastro de Famílias". https://documentacao.senior.com.br/gestaoempresarialerp/5.10.4/Menu_Cadastros/f012fam/. Accessed on November 17, 2026.
- Senior Sistemas, Portal de Documentação, "Duplicação automática de produto/serviço para outras empresas". https://documentacao.senior.com.br/gestaoempresarialerp/5.10.4/manuais_processos/mercado/duplicacao-automatica/. Accessed on November 17, 2026.
- Senior Sistemas, Portal de Documentação, "F095CAD - Cadastro de Fornecedores". https://documentacao.senior.com.br/gestaoempresarialerp/5.10.4/Menu_Cadastros/f095cad/. Accessed on November 17, 2026.