PDM to ERP — Item master transfer from PDM to ERP

PDM to ERP moves the stock card and operation routing that engineering creates in PDM into the ERP. The current value in Netsis and the new value coming from PDM are shown side by side; opening cards by hand is no longer needed.

A card is not completed in the ERP until the departments have checked and approved it; a rejected card goes back to the sender with its reason. Every change is logged with who, when, and the old and new value.

Capabilities

Field mappingPDM variables are linked to Netsis stock card fields through a fixed map.

Operation routingOn an approved card, operation items and a chained routing are written to Netsis from the PDM operations; the old routing is kept in the log.

Departmental approval flowR&D, Production Engineering, Purchasing, Suppliers, Planning and Sales check their own fields on the same data card and approve, or reject with a reason.

Missing data warningRequired fields, unmatched group codes and missing department cards are flagged on screen; records without a purchasing card are shown on the dashboard with a warning strip.

Faulty records are not lostBulk update shows the result and error reason for every row; the record stays in the approval list and is resubmitted once fixed.

Transfer logWhat was transferred, when and by whom — a complete record.

Side by side with NetsisOn the data card, the current value in Netsis on the left and the new value from PDM on the right; the difference is visible before approval.

Keyboard approvalWith the X (close), B (next code) and G (approve and go to next) shortcuts, cards are processed one after another without leaving the list.

PDM process dashboardUntouched, pending and approved records, completion rate and transfer by department on one screen.

Contribution by personThe staff who check and approve the most are listed; the report refreshes automatically every night.

Netsis SearchStock card, warehouse balances, open orders/requests/work orders, stock movements, a monthly work order-sales chart and order warehouse receipt time on one screen.

Drawings and documentsAccess from the data card to the item's image, technical drawing and specification in PDM; manufacturer code search.

How a transfer works

Example flow: SolidWorks PDM Bella integration layer Netsis ERP. Engineering data is never typed into the ERP by hand; every step is recorded.

ReadItem master fields, operations and the latest revision of every variable are read from PDM.
MapPDM variables are linked to ERP fields through a fixed map; which field goes where is defined in one place.
ValidateRequired fields, unmatched group codes and missing department cards are flagged before the transfer.
CompleteR&D, production and purchasing complete their own fields on the same data card; who checked and approved the card is recorded.
TransferThe approved card is written to Netsis; a faulty row stays in the approval list and is resubmitted once fixed.

Every transfer is written to a log that answers who, when and with which value.

Case studies

Clients

PDM to ERPManufacturingA change in PDM reaches Netsis within minutesAn integration that automatically moves item masters, product trees and revisions from PDM to Netsis and notifies people when a code does not match; followed by task and quality-control tracking on the shop floor.Read the case study PDM to ERPMachinery manufacturingNew parts drawn every week reach the ERP without waiting and without errorsAn integration in which the new machine drawings and revisions constantly produced by a large R&D team flow automatically into ERP item cards and bills of materials, only approved revisions go to the ERP, and every transfer is traceable.Read the case study Integrated software (PDM · Netsis · access control · Zirve)Machinery manufacturingFour separate systems, from design to payroll, now meet in one applicationAn integrated system that brings the data carried by hand between PDM, Netsis ERP, badge access control (time & attendance) and Zirve payroll into one in-house application; engineering data flows to the ERP and access records flow to timesheets and payroll by rule.Read the case study

Screenshots

PDM to ERP — PDM records pending approval — PDM records pending approval

PDM to ERP — Data card: comparison with Netsis — Data card: comparison with Netsis

PDM to ERP — Netsis stock search — Netsis stock search

PDM to ERP — Monthly movements and delivery time — Monthly movements and delivery time

Frequently asked

What happens to a failed record?

It does not disappear silently. Bulk update shows the faulty row with its reason; the record stays in the pending-approval list and is resubmitted once fixed.

Which revision is transferred to the ERP?

The values of the latest revision in PDM are read; they go through departmental approval before being written to the ERP.

Can multi-level BOMs be transferred?

Today, operation items and a chained routing are built from the item's operations in PDM. If multi-level product structure transfer is needed, it is added within the project scope.

Which PDM and ERP systems does it work with?

The installation running in the field connects SolidWorks PDM and Netsis. For another PDM or ERP, the read and write layer is adapted within the project scope; the departmental approval flow and change log stay the same.

Other products

What can PDM to ERP do for you?

Let's plan the whole process together, from installation to integration.

Request a Call All Products