Sign in
  1. Promob Support
  2. Manufacture
  3. Promob Builder

Plugin Builder - ERP Promob Integration - Customization

Updated
Follow

Check out the customization procedures for ERP integration in this article. It covers the following sections:

 

Attributes for ERP Integration

Operations Budget Registration

Registration of edge band references

How to order operations

Modulation changes

Volume Settings

Configuration of partner base items

Library Builder Integration

Organization of drawings generated by the integration

Export Base Item

Application of attributes for application in exports

 

 

Attributes for ERP integration

For integration with Promob ERP, it is necessary to create a group of attributes called Database_Database. It is important that this group is created inside entity.attributes.

 

02pt.png

 

The attributes created for the integration must have the following configuration:

  • Visible and Editable must be unchecked.
  • In the behavior, the Automatic Creation option must be unchecked.

Below are the attributes that are required for integration. Their default values may vary depending on library configurations and needs, so the default settings and values are listed below.

ID NAME STANDARD VALUE
LARGURA_AMBIENTE Width $W$
ALTURA_AMBIENTE Height $H$
PROFUNDIDADE_AMBIENTE Depth $D$
ESPESSURA Thickness @($H$-#FOL_PAI#)
COMPRIMENTO Length $W$
TIPO_PRODUTO Product type F (pode ser F ou C)
MATERIAL  Material  @com_*(MATERIAL)@
COR Color @com_*(ACABENTO)@
FANTASMA  Ghost S (pode ser S ou N)
BORDA_FRONTAL Front edge band $FRONTBORDERBUILDER$
BORDA_ESQ Left edge band $LEFTBORDERBUILDER$
BORDA_TRASEIRA Bback edge band $REARBORDERBUILDER$
BORDA_DIR Right edge band $RIGHTBORDERBUILDER$
VOLUME Volume VOL01
BORDA_DIR_COMPLETE Referencia Complete da Borda Direita $RIGHTBORDERCOMPLETE$
BORDA_ESQ_COMPLETE Referencia Complete da Borda Esquerda $LEFTBORDERCOMPLETE$
BORDA_TRASEIRA_COMPLETE Referencia Complete da Borda Traseira $REARBORDERCOMPLETE$
BORDA_FRONTAL_COMPLETE Referencia Complete da Borda Frontal $FRONTBORDERCOMPLETE$

 

Attribute definitions and their default values

The attributes of the Database_Database family usually appear in the XML with the tag inside the node . Within the characteristics, there is the CÓDIGO attribute, which is usually the attribute's ID, and the RESPONSE attribute, which is the value given to the attribute.

EXAMPLE:

01pt.png

 

Below is an explanation, default value and an example of how the information is in XML.

 

LARGURA_AMBIENTE

What it does?

Loads the width of the final module or composition items.

Where to apply?

Must be applied to all modules and composition items.

Value?

$W$

Where does it appear in XML?

It appears in both modules and compositions.

XML Image:

03pt.png

 

What does ERP do with information?

The ERP uses this feature to assemble item descriptions and fill in their registration. This description will only be visible in the ERP, not changing the Promob registration.

004pt.png

 

ALTURA_AMBIENTE

What it does?

Loads the height of the final module or the depth of the composition parts.

Where to apply?

Must be applied to all modules and composition items.

Value?

$H$ (for modules) and $D$ (for compositions)

Where Does it Appear in XML?

It appears in both modules and compositions.

XML Image:

04pt.png

 

What does ERP do with information?

The ERP uses this feature to assemble item descriptions and fill in their registration. This description will only be visible in the ERP, not changing the Promob registration.

 

004pt.png

 

PROFUNDIDADE_AMBIENTE

What it does?

Defines the depth of the module in the environment. This information is given without discounting the thickness of the edge strip and without adding up the overcut.

Where to apply?

Apply to all modules. It should not be applied to compositions.

Value?

$D$

Where does it appear in XML?

Unlike the others, this attribute is not shown with this name in the XML. It is only shown as DEPTH. This solution was made in this way, as it generated a conflict with the information of values proposed in Promob.

XML Image:

05pt.png

 

What does ERP do with information?

The ERP uses this feature to assemble item descriptions and fill in their registration. This description will only be visible in the ERP, not changing the Promob registration.

004pt.png

 

 

ESPESSURA

What it does?

Loads the thickness of composition items.

Where to apply?

Must be applied to all composition pieces.

Value?

The default value is $H$-#FOL_PAI#, where $H$ is the height of the part and #FOL_PAI# is the attribute that defines the sheet thickness clearance. This formula may vary depending on the information contained in the system.

Where Does it Appear in XML?

Appears in compositions.

XML Image:

06pt.png

 

What does ERP do with information?

The ERP uses this feature to register the item and to assemble its descriptions.

 

005pt.png

 

COMPRIMENTO

What it does?

Loads the length of linear items.

Where to apply?

Must be applied to linear items. Example: gola handle, profile handle and rails for sliding doors.

Value?

The default value is $W$, but this information can be changed according to the linear direction of the item, for example, if it is linear in height the value should be $H$.

Where Does it Appear in XML?

For linear items that have the poly-cut operation, it appears in the XML in the parent item's characteristics.

XML Image:

07pt.png

 

What does ERP do with information?

ERP uses this feature to assemble item descriptions. Taking as an example a runner and its description in Promob as RunnerTL 22, in the ERP the LENGTH information can be concatenated with the description sent by XML, thus generating a description Runner TL 22 400mm.

 

TIPO_PRODUTO

What it does?

Define se um item é fabricado ou comprado.

Onde aplicar?

Defines whether an item is manufactured or purchased.

Value: F (manufactured) or C (bought)

Where Does it Appear in XML?

It should appear on all library items except structures, as by default all structures are purchased.

XML Image:

08pt.png

 

What does ERP do with information?

The ERP uses the information to register the item. Depending on the result, he has a series of different behaviors.

EXAMPLE: If it is manufactured, it generates a production order, if it is purchased, it generates a purchase order.

 

MATERIAL

What it does?

Loads the information of the type of material used in the composition parts.

Where to Apply?

Must be applied to all composition pieces.

Value?

The default value is @com_*(MATERIAL)@, but this information may vary depending on the models created for the modulation. Usually the loaded values are MDF or MDP.

Where Does it Appear in XML?

Appears in compositions in the item characteristics part.

XML Image:

09pt.png

 

What does ERP do with information?

The ERP uses this feature to register the item and to assemble its descriptions.

 

COR

What it does?

Loads the raw material finish information.

Where to Apply?

It must be applied to all modules and composition parts.

Value?

The default value is @com*(FINISH)@, but this information may vary depending on the models created for the modulation. The information that will be loaded must have a maximum of 3 characters and can be alphanumeric.

Where Does it Appear in XML?

Appears in all modules and compositions, appears in the item characteristics part.

XML Image:

10pt.png

 

What does ERP do with information?

The ERP uses this feature to register the item and to assemble its descriptions.

 

 

006pt.png

FANTASMA

What it does?

Defines if the registered item should be considered in the ERP structure or if it is just a grouper of several other items.

Where to apply?

It must be applied when you do not want the registered item to be part of the product structure. EXAMPLE: a drawer body that is budgeted together with the module, in this case the drawer body is created just to facilitate registration, as it groups several pieces that are part of the module structure.

When a Hardware Kit is created that can be inserted either separately or aggregated in any module and the Phantom feature is applied, this kit must not be budgeted and cannot contain aggregated structures.

Where Does it Appear in XML?

Appears in XML in grouping items such as kits, appears at the end of the first line of the item.

XML Image:

11pt.png

 

Value?

S (grouper item) or N (consider in the structure)

What does ERP do with information?

When the attribute value is S, ERP will ignore it when generating reports.

 

007pt.png

 

BORDA_FRONTAL | BORDA_ESQ | BORDA_TRASEIRA | BORDA_DIR

What it does?

Loads the applied edge tape reference into the profile of each composition part.

mceclip20.png

 

NOTE: When the part has more than 4 sides, it considers the part boundary, since for the generation of the cutting plane the cutouts of the parts are not considered.

Where to apply?

The four attributes must be applied in compositions. When generating the integration, the plug-in will recognize whether or not there is a border applied to the parts.

Values?

  • BORDA_FRONTAL: $FRONTBORDERBUILDER$
  • BORDA_ESQ: $LEFTBORDERBUILDER$
  • BORDA_TRASEIRA: $REARBORDERBUILDER$
  • BORDA_DIR: $RIGHTBORDERBUILDER$

Where Does it Appear in XML?

Appears in the XML in compositions, in the part where the characteristics appear, only on the sides where the edge bands are applied.

XML Image:

12pt.png

 

What does ERP do with information?

The ERP uses this information in the label generated by the cutting plan.

 

008pt.png

 

VOLUME

What it does?

Loads the volume information where the part will be packed. It is one of the most important attributes for Product Structure definitions.

Where to apply?

It must be applied to all items that are packaged, both compositions and accessories.

Value?

The default value is VOL01, following this logic the next values will be VOL02, VOL03 and so on. The hardware volume by default is VOLFER.

Where Does it Appear in XML?

It should appear on all items except items that contain a grouper item, for example, the chests of drawers that appear on the volume should only appear in the Kit. It appears in the xml in the first line of each item.

XML Image:

14pt.png

What does ERP do with information?

The ERP uses this attribute to group items according to the information sent and thus assemble the product structure tree.

009pt.png

 

 

REFERÊNCIA COMPLETE

 

What it does?

The functionality allows the user to obtain the value of the Complete reference of a given border when using this assembler.

 

How to access?

Access through the mounts: $LEFTBORDERCOMPLETE$ for the left edge, $RIGHTBORDERCOMPLETE$ for the right edge, $FRONTBORDERCOMPLETE$ for the front edge, and $REARBORDERCOMPLETE$ for the rear edge.

 

Value?

By using these assemblers, you will get as return the value of the Complete reference of the structure of the item used.

 

Operations Budget Registration

The operations budget register is where we carry out the register of operations that are part of the production itinerary and the budget.

To register an operation budget, you can access the registration editor in two ways.

1. Through the Register - Builder - Operation Budget Registration

13pt.png

 

2. Or, in the module editor, on the Builder tab, on the Operations Budget icon;

15pt.png

To register the operations, there are fields to fill, which vary according to the library and others that vary according to the operation.

Are they:

Provider: Price provider ID (budget purposes);

Data source: Data source ID (budget purposes);

Margin category: It can be created according to the client's need and the client's library. It is the budget margin where the operation will respect;

Description: It can be created according to the client's needs and its library;

ID: It can be created according to the client's need and the client's library. It  is associated in the Builder tab;

Quantity: It can be created according to the client's need and its library;

Reference (COMPLETE): It can be created according to the client's needs and its library. It is through this that a price for the operation is provided;

Dimension text: It can be created according to the customer's need and the customer's library. This text appears in the budget.

Type of Operation: Varies according to the operation to be registered (see operations specification);

Unit: Is the unit respected and considered for budgeting (see operations specification, to verify agreed standard);

 

16pt.png

 

The standard operations registered for integration with ERP Promob are as follows:

RASGAR:

This operation must be applied to all slots.

Standards:

  • Type of Operation: Rip
  • Quantity: $DISTANCEBUILDER$/1000
  • Unit: M

Where Appears in XML: Appears at the end of the tree of linear items that have this operation, as shown in the image:

17pt.png

 

BORDEAR:

This operation must be applied on all edges.

Standards:

  • Type of Operation: Edge
  • Quantity: $PERIMETERBUILDER$/1000
  • Unit: M

Where Appears in XML: Appears at the end of the tree of linear items that have this operation, as shown in the image:

 

 

CORTAR:

This feature does not need to be associated. It is automatically created on parts that are sent to the cut plane. The information that defines that the part will go to the cutting plane is the COMPONENT attribute with the value TRUE. As in Promob there is no way to define where the cuts will be made, as the cutting plan has not yet been performed, the calculation of this operation is usually done by adding the length of all sides of the part (perimeter):

Padrões:

  • Type of Operation: Cut
  • Quantity: (2*$PLATECUTTINGWIDTHBUILDER$+2*$PLATECUTTINGHEIGHTBUILDER$)/1000
  • Unit: M

Where Appears in XML: Appears at the end of the tree of linear items that have this operation, as shown in the image:

18pt.png


CORTE EM POLICORTE:

This operation must be applied to accessories, which in their production, have the need to make this type of cut.

Standards::

  • Type of Operation: Extra
  • Quantity: 1
  • Unit: UN

Where Appears in XML: Appears at the end of the tree of linear items that have this operation, as shown in the image:

19pt.png

 

FURAR:

This operation must be applied to all holes.

Standards:

  • Type of Operation: Hole
  • Quantity: 1
  • Unit: UN

Where Appears in XML: Appears at the end of the tree of linear items that have this operation, as shown in the image:

20pt.png

 

MOUNTING:

This operation must be applied to the final module. The application of this operation is done automatically when the module has the attribute ASSEMBLED with the value TRUE.

  • Type of Operation: Assembly
  • Quantity: 1
  • Unit: UN

When registering an operation, Budget Rules and Structures are automatically created. These can be viewed in the following ways:

  • Registry - Budget - Budget Rules
  • Registry - Budget - Structures

IMPORTANT:

  • The above budget rules should not be “Adding Up Quantities”;
  • The default.structures file should not be changed from the outside, as it will lose the link with the Builder information;
  • If you want the operations not to appear, but remain budgeting, register the HIDE_STRUCTURE = TRUE reference in the structure, as shown in the image below:

 

Register the following in Exploded Budget Layouts (System\budget\Layouts\Listing)
code:

22pt.png

 

And register after the the code below:

236pt.png

 

VARIABLES:

  • $DISTANCEBUILDER$: Variable that gives the slot operation length in millimeters.
  • $PERIMETERBUILDER$: Variable that gives the perimeter of the Edge banding operation in millimeters.
  • $PLATECUTTINGWIDTHBUILDER$: It responds with the value of the cut dimensions in width, deducting edge band thicknesses and adding their overcut.
  • $PLATECUTTINGHEIGHTBUILDER$: It responds with the value of the cut dimensions in height, deducting edge bands thicknesses and adding their overcut.

 

 

 

Label Edge Band Reference

The reference of the edge tape that appears on the label can identify some characteristics of the label, for example, thickness and finish. This assembly of the reference is registered in Registry -  Builder -  Register Edge References

 

24pt.png

The screen below will be displayed:

25pt.png

 

The reference usually loads the thickness of the tape ($BORDERTHICKNESSBUILDER$) and the finish of the tape (@*_fita@). The model information may vary depending on the model registration existing in the system.

The reference must be applied to the edge registration in Registry - Modules - Builder:

26pt.png

 

On the label, the information appears as the image below (the label layout may vary depending on the cut plan used):

27pt.png

 

 

 

How to order operations

The order of operations defines the sequence of processes that the part performs during production. This information is registered in Register -  Modules -  Builder in the option  Order of Operations.

All composition pieces must have this information, registration can be done both in items and in groups:

028pt.png

 

NOTE: When the definition takes place in the group, a message is displayed asking whether the definition should be applied to the children or not.

 

 

 

Modulation changes

Linear Items

For Profile, Gola and Linear Rail handles (items that are purchased by the meter and processed within the factory), structures must be budgeted in meter and the item must budget by unit.

Inside this item they must contain the operations that are performed at the factory (poly-cut), and they must contain the Length characteristics.

Glasses

The personalization of Glasses in libraries with ERP follows the same logic as linear items and compositions. It is necessary that the entity is budgeted by Unit, and the price is not placed on it.

Associated with it, a structure budgeted by Square Meter must be registered, where its reference will have the price.

Hardware

Hardware aggregated in modules must have the BUDGETAGGREGATE attribute as TRUE, so that in the XML they are children of the compositions to which they are aggregated. It must contain Volume = VOLFER, in case the hardware has items added to it, such as a screw, or other similar item, such as a hinge item with a screw. For this item, a Hinge Kit must be created, where it contains the following information:

  • Fantasma: “S”
  • Calculated: False
  • Tipo_Produto: “F”
  • Unidade: “UN”

Inside this Kit must contain the hinge and the screw as sibling items, these items must have the Volume Reference and must contain the following characteristics:

  • Tipo_produto: “C”
  • Unity: “UN”
  • How does it look in XML:

 

 

Structures

The structures must be marked as Module Composition and Link to the first budgeted parent, in this way, they are as children of the composition parts. As compositions do not look for attributes in their reference, they cannot apply the attribute Product_Type, thus, by default, all structures are Purchased items.

For Hardware that are considered Ghosts = “S”, structures must not be created, but a module must be created within the library, as this kit must not be calculated, but only the items that make up this kit will be calculated.

Drawer body

The drawer body assembly must receive the CALCULATED attribute with the value TRUE, however, the NOPRICEALERT attribute must also be placed, with the value TRUE, so that the item without price message does not appear when entering the budget. This must be done so that in the export XML, the drawer set appears as a brother to the bases, sides and crossbars of the modules, and within this set are the children, which are the sides, back and bottom of the drawer.

References

All system modules and structures must have the ITEM_BASE reference registered, it is the link between Promob modulation and ERP modulation. This information can be registered in two ways, together with the TEXT reference in the variables on the Dimensions tab or on the Reference tab, creating a new variable called ITEM_BASE. Usually for modulation, it is created on the Dimensions tab and for structures on the References tab, it must have a maximum of 9 characters. Below is an example of the two ways:

33pt.png

 

34pt.png

 

On systems with Cabinet Builder, the ITEM_BASE reference must be created in the builder files, according to the code below:

35pt.png

 

In addition to the ITEM_BASE reference, Promob also sends the COMPLETE reference in the XML. It is listed along with ITEM_BASE in ERP orders. It is very important that it is no longer than 20 characters and is applied to all items.

 

Repetition in the Budget

When there is integration with the ERP, the grouping of items in the column  Repetition  of the budget is not used, as each item has a unique ID, which is treated later in the Builder.

 

 

 

Volume Settings

VOLUME settings may vary from customer to customer. In Promob Start Labs, hardware has the attribute with VOLFER value, and compositions with VOL01. Hardware items that are registered as structures receive a reference called VOLUME, with the value VOLFER. VOLUME, KITFER is registered in the screws of the handles. This information is reprocessed within the ERP where there is a tree redistribution to show the composition of the module.

 

0010.png

There are some cases where it is necessary for an item to be inside another, but inside the same volume.

 

EXAMPLE:

A Minifix Kit is created, this kit has VOLUME = VOLFER.

If we put in its children (Drum, Screw and Tapa Bore) the same volume information as the kit, the ERP assembles a structure with the children and the kit at the same level, and does not assemble the quantities correctly.

To adjust this, it is necessary to leave the VOLUME information of the children empty. So that in this way, they are always below the father.

Reset of Volumes

You can redefine volumes from module to module, even applying the attribute in the composition group. For this, just go to the desired module and in aggregates reset the attribute value.

 

36pt.png

 

 

 

Configuration of partner base items

In order to be able to carry out the integration between the products of partner libraries and Promob ERP, it is necessary that in the reference of the products, there is a variable called ITEM_BASE.

To insert base_item in partner items, it is necessary to perform the following procedure:

1. Access the registration of modules and in the partner's root, fill in the variable ITEM_BASE in the proposed references;

37pt.png

 

2. Access the reference of all partner products and apply the value to the variable ITEM_BASE;

  • If the partner's library uses the concept of Collection of References, the registration of the variable ITEM_BASE  happens in the registered references, in the collection and not directly in the entities.
  • The filling value of the ITEM_BASE variable must contain a maximum of 9 characters, so it must be composed of the 4 digits corresponding to the partner's library number and the 4 numbers that represent the product in question.
  • The information must be separated by a period ( . ), with the following format: nrobblioteca.codigoproduto

38pt.png

 

Some product codes are repeated as the product process is the same. Below are some examples of products that have the same value as ITEM_BASE:

  • Swing doors, straight corner, 45° corner, 90° corner, reducer, potter;
  • Top and reverse lift up;
  • Sliding doors with one handle, with two handles, with TV.

The registration of ITEM_BASE was performed in the Standard Door Partner System. View here for consultation (run it through Notepad). This file is registered in the following Promob path: Disk C:/Program Files/Promob/Promob Name/System/Config/References.

 

 

 

Integration ERP Promob Library Builder + Library Studio

To integrate a library, where both types of integration with the ERP exist, the XML file, generated through Plugin ERP Promob, is responsible for carrying out the integration.

The file is more complete and generates production information for modules made with the Builder. To generate the Studio library integration, it is necessary to register attributes, according to the needs of each client, in addition to the ITEM_BASE reference.

Taking as an example:

The reference: MOD001 | Gray | White

We define that: MOD001 will be the ITEM_BASE reference, since it is the unconfigured item.

39pt.png

40pt.png

 

In this item, 2 models are applied that allow the user to configure the product. Are they:

  • Plastic Covering and Plastic Structures

For each of these models, we will create an attribute inside the Database_Database group.

41pt.png

 

When generating the Promob ERP Integration XML. The item is in the XML as follows:

42pt.png

 

The characteristics passed by the XML enable the configuration of rules within the ERP, making it possible, according to the request, to create the configured items in the correct way.

 

 

 

Organization of drawings generated by the integration

The folder organization of drawing files generated by the integration is done like technical drawings, where drawings are grouped according to their parent-child elements.

29pt.png30pt.png

 

 

 

Export Base Item

Available from version:

  • Plugin ERP Promob – 1.12.9.0 ou superior
  • Plugin ERP Promob Start – 1.12.4.2 ou superior

In this functionality, all base library items will be imported, in a *.csv file, with the following columns:

 

NAME VALUE
ITEM_BASE Base Item field value
DESCRIPTION Base Item Description
MEASURE UNITY Unit of measurement
PATH OF THE GROUP Item path in library
ID Base Item ID

 

To access the functionality, click on Registry - Builder - Export Base Item

31pt.png

EXAMPLE:

32pt.png

 

NOTE: To export the files it is necessary that the Promob library is on the local machine.

 

Application of attributes for application in exports

In order for all ERP integrations to be carried out correctly, the attributes must be applied to the items as follows:

ERP INTEGRATION INFORMATION
ATTRIBUTE SHOW ITEM FATHER'S SON FATHER'S BROTHER DRAWING CODE OPERATION CUT
COMPOSED Indifferent Indifferent Indifferent Indifferent False
COMPONENT Indifferent Indifferent Indifferent True True
CALCULATED True True True True True
BUDGETAGGREGATE Indifferent True False Indifferent Indifferent

 

ERP INTEGRATION INFORMATION
ATTRIBUTE BORDER OPERATION ASSEMBLY OPERATION MISCELLANEOUS OPERATION TECHNICAL DRAWING MACHINE PROGRAMS LABELS
COMPOSED Indifferent Indifferent False Indifferent False False
COMPONENT Indifferent Indifferent True True True True
CALCULATED True True True True True True
BUDGETAGGREGATE Indifferent Indifferent Indifferent Indifferent Indifferent Indifferent

 

 

ERP START INTEGRATION INFORMATION
ATTRIBUTE SHOW ITEM FATHER'S SON FATHER'S BROTHER DRAWING CODE OPERATION CUT BORDER OPERATION
COMPOSED Indifferent Indifferent Indifferent Indifferent False Indifferent
COMPONENT Indifferent Indifferent Indifferent True True Indifferent
CALCULATED True True True True True True
BUDGETAGGREGATE Indifferent True False Indifferent Indifferent Indifferent

 

 

ERP START INTEGRATION INFORMATION
ATTRIBUTE ASSEMBLY OPERATION MISCELLANEOUS OPERATION TECHNICAL DRAWING MACHINE PROGRAMS LABELS CUT PLAN
COMPOSED Indifferent False Indifferent False False False
COMPONENT Indifferent True True True True True
CALCULATED True True True True True True
BUDGETAGGREGATE Indifferent Indifferent Indifferent Indifferent Indifferent Indifferent