Computer-Aided Design (CAD) Transfer#
General#
The Computer-Aided Design (CAD) Transfer allows you to import data from the PDM system into KUMAVISION factory365 as article as well as production BOM. Each imported file is saved in KUMAVISION factory365 as a PDM process and in a second step created as article as well as parts list(s). A readout of the articles to the PDM system is also possible. The solution serves as a basis for the customer-specific definition of the interface.
Prerequisite#
The following Microsoft Dynamics 365 Business Central1 license extensions are required for this credit:
- KUMAVISION factory365
- Anveo2 EDI Connect Business or higher,
Establishment#
Before you can use the data exchange from a PDM system in KUMAVISION factory365, some settings have to be made in the system, which are explained in the following.
Design & development facility#
Call up the design and development facility via the user search. On the setup card on the "PDM" info tab, the following fields must be set up for data transfer:
| Field | Description |
|---|---|
| Ignore New PDM Articles | If the switch in this field is activated, newly imported articles (marked by the article field "New PDM article") are excluded from the planning. |
| PDM connection code | You can use this value during mapping to assign a connection code to the components. This is helpful if you are already working with connection codes in the routing For more detailed information on connection codes, please refer to the Microsoft Dynamics 365 Business Central1 Helpsite. |
| Last Lfd. No. Change log | Used internally by the system. Represents the last Lfd. No. processed from the system. |
| PDM Base Hyperlink | The hyperlink for the PDM system call is stored in this field. Note:In the hyperlink, %1 must be entered at the point where the hyperlink expects the article number. |
| PDM separator multiple articles | Specifies the separator for separating the articles to be displayed in the PDM system by calling "Call PDM" via the article overview. |
Article categories#
Via the article categories you have the possibility to define or group articles that are relevant for the PDM exchange.
To do this, call up the "Article categories" via the user search.
You can create a new article category via "New" in the ribbon or edit an existing article category via "Edit". For further information on the topic of "Article categories", please refer to the Microsoft Dynamics 365 Business Central1 Helpsite.
Via the field "PDM exchange" you can define for which, and if a data transfer for the corresponding article category should take place. The following selection options are available:
| Selection option | Description |
|---|---|
| No | No data exchange between KUMAVISION factory365 and PDM system |
| In-depth | Inbound data exchange from PDM system to KUMAVISION factory365. |
| Based on | Outgoing data exchange from KUMAVISION factory365 to PDM system. |
| Both | Inbound and outbound data exchange between KUMAVISION factory365 and PDM system. |
Finally, the item category is assigned to the corresponding items in the "Item category" field on the item card.
Change log setup#
To define the PDM relevant data, the change log has been extended to use it for the PDM interface. This means, in the log setup fields can be marked as "PDM change" for the tables listed in the subchapters. These fields are analyzed by the system to determine which records are PDM relevant, have been updated and need to be exported.
To set up the change log, first access the change log setup via the user search and activate the "Activate change log" field.
The "Tables" menu item in the ribbon takes you to the "Edit - Proto. settings (Tab.) - Trans.
In the table definition, the "PDM Logging" column can be used to specify whether all field changes or only certain field changes are relevant for the PDM interface.
The change log can be used to specify the article fields from which the data record is to be transferred in the event of changes in the following tables.
- Article (table no. 27)
- Article version (table no. 5026352)
- Material (Table No. 5026357)
- Finished parts list header (table no. 99000771)
- Finished parts list line (table no. 99000772)
- Finished parts list version (table no. 99000779)
| Selection | Description |
|---|---|
| Some fields | Selecting "Some fields" logs certain field changes that are relevant to the PDM interface. The field list of the specified fields can be viewed via the Assist button [...]. |
| All fields | By selecting "All fields", all field changes in the table are logged. The change log items have the "PDM Entry" flag, which indicates that PDM relevant data has been adjusted. |
PDM status#
Via the "PDM Status" you can define if the corresponding locked fields should be set on the article card during the later transfer to KUMAVISION factory365. The definition is done once in the "PDM Status".
To do this, call up the "PDM status" via the user search. Via "New" in the menu ribbon you can define a new PDM status using the table below.
By selecting "Yes" or "No" you determine whether the fields in the article are to be set during transfer. If the selection "Yes" is set, then the current status of the field remains, this means, a locked indicator cannot be changed by transmission. Exception here is the field "New PDM article", which can remove a lock again, here it is to be noted that with New PDM article no, as well as Set locked, the lock indicator is set.
| Field | Description |
|---|---|
| Code | Indicates the "code" (abbreviation) of the PDM status. Note: For the assignment of the locked license plates, the code must be identical to the code in the transmitting PDM system. |
| Description | Indicates the description of the PDM status. |
| Set Locked | If activated, the fields "Locked" and "Locked (user)" are automatically set on the respective item card during transfer. As a result, the item is locked for the processes in the system. |
| Set Locked Sale | When activated, the "Sale locked" field is automatically set on the respective item card during the transfer. As a result, the item is blocked for the sales process in the system. |
| Set locked purchase | When activated, the "Purchasing blocked" field is automatically set on the respective item card during the transfer. As a result, the item is blocked for the purchasing process in the system. |
| Set Locked Production | When activated, the "Production locked" field is automatically set on the respective item card during transfer. As a result, the article is blocked for the production process in the system. |
| Set Locked Service | When activated, the "Service locked" field is automatically set on the respective item card during transmission. As a result, the item is blocked for the service process in the system. |
| Set Locked Production Consumption | If activated, the field "Blocked prod. consumption" is automatically set on the respective article card during the transfer. As a result, the item is blocked for production consumption in the system. |
Materials#
Via the table "Materials" you can create the materials your articles consist of. During the later transfer to KUMAVISION factory365 these materials will be transferred directly on the respective article card.
To create the materials in the system, call up the "Materials" via the user search.
Via "New" in the ribbon you can define a new material using the table below.
| Field | Description |
|---|---|
| Code | Indicates the "code" (abbreviation) of the material. Note:For the assignment of the materials, the code must be identical to the code in the transferring PDM system. |
| Description | Indicates the description of the material. |
| Specific gravity (g/m³) | Indicates the specific gravity of the material. |
Article map#
For the PDM transfer, the following fields are available on the article card on the "Article" info tab:
| Field | Description |
|---|---|
| Material | The "Material" field identifies the item, from which material it is made. The information can be transmitted via the PDM system. Further information on the subject of materials can be found in the section of the same name. |
| PDM status | The "PDM Status" field indicates the status of the article in the PDM system. At the same time, the system sets the defined blocked indicators on the respective article card. For more information on PDM status, see the section with the same name. |
| PDM Status Description | Indicates the description of the respective PDM status set. |
| New PDM article | If the field "Ignore new PDM articles" is activated in the Design & Development setup, the switch is set here when an article is created for the first time. If the switch is set, the article will be ignored in the planning worksheets and order worksheets Note: If you deactivate the switch, no locked indicators will be removed if work is being done without PDM status. The system does not know at this time whether none, only one specific or all processes must be unlocked. For a deliberate control of the locked indicators refer to the use of the PDM Status. |
| Ignore for PDM Export | If the switch is set, the data of the respective article will be ignored for the export. |
PDM Call#
From the article map and the article overview you have the possibility to call up the PDM system directly via the call "Call up PDM" in the menu ribbon. The PDM system is called directly with the corresponding article information from which you have started the call.
Note: Please note that this functionality is only available to you if the fields "PDM Base Hyperlink" and "PDM Separator Multiple Items" are set up in the Design & Development setup.
Task maintainers#
For a periodic execution of the readings in and out, the mappings are defined in the queue items.
To do this, call up the task queue items via the user search.
The following facilities are to be made for this purpose:
| Field name | Import | Export |
|---|---|---|
| Type of object to be executed | CodeUnit | CodeUnit |
| ID of the object to be executed | 5327312 | 5327312 |
| Labeling of the object to be executed | EDI Job Handler | EDI Job Handler |
| Description | PDM Import | PDM Export |
| Task queue - category code | PDM | PDM |
| Recurring task | Yes | Yes |
| Number of minutes between executions | 240 | 240 |
| Parameter string | RECEIVE(Folder=210, ProcessFollowing=True) | RUN(ProjectFilter=PDM,FormatFilter=NAV,CodeFilter=EXPORT 10 SURFACE, ProcessFollowing=True) |
The number of minutes between executions can be customized, as well as the definition of the days of the week.
For more information for the task queue, see the Microsoft Dynamics 365 Business Central1 Helpsite.
Anveo2 EDI#
For completeness, the EDI setup is described below. Further information can be found in the manual provided by the Anveo2 Group.
EDI setup#
Via the EDI setup you can import the bitmaps, for example. To do this, call up the "EDI setup" via the user search.
Via the call "QuickInstall" in the menu ribbon, you can import the essential facilities, such as the bitmaps.
Note
Running Quickinstall is a must. This will import the QuickInstall.nav file.
Import EDI configuration data...#
In the next step the essential mappings for the PDM connection are read in. To do this, call up "Import EDI configuration data..." via the user search.
Note
The mapping is provided by KUMAVISION AG and is parameterized together with a KUMAVISIONS employee.
EDI formats#
The basic processing types are mapped in Anveo2 EDI via the EDI formats. To do this, call up the "EDI formats" via the user search.
For the interface to the PDM system, the formats 020 XML files and 100 NAV processing are used.
EDI value translations#
The translation tables are maintained in Anveo2 EDI via the EDI value translation. By calling up "EDI Value Translations Overview" via the user search, you can access the overview of the same name.
Note
The translation tables are used individually for each project and are not part of any installation package.
EDI project#
The grouping of the interface as well as processes are realized via the EDI projects.
The PDM project is used to group all mappings to the PDM system.
File directories#
The file directories are defined via the EDI communication channels.
Data exchange directories#
The following directory structure is generally defined for file exchange with a PDM system:
\ExchangeDir\ERPRequest
\ExchangeDir\ERPRequestResponse
\ExchangeDir\PDMRequest
\ExchangeDir\PDMRequestResponse
EDI communication channel overview#
For each of the data exchange directories an EDI communication channel must be created. To do this, call up the "EDI communication channel overview" via the user search. Via "New" in the menu ribbon you can define a new EDI communication channel.
EDI Transmissions Folder Overview#
An EDI transfer order must also be defined for the exchange. To do this, call up the "EDI transmissions folder overview. Via "New" you can define a new EDI transmission folder.
The transmission folder is assigned to the communication channel in the Folder Code field.
Via the function call Set up you reach the EDI data transmission setting.
Here you define the read-in or read-out directory as well as the file extension.
It is recommended to archive the imported files. The archive directory is also to be maintained in the EDI file transfer settings card in the Archive folder field via the Action field to be activated after reading in.
Mapping#
An operation record is created for each import. This is done by an inserted element Operation. The operation record is initialized by filter values.
The import can contain several data sets, in this respect it is important to keep the file as a reference in Microsoft Dynamics 365 Business Central1. The referencing corresponds to the
The element Part is imported into the article PDM Item. For this purpose, a loop item for the table PDM Item is integrated before the element
Processing#
In-depth#
EDI processing queue#
The processing queue is the log of Anveo2. All processes are logged in this table.
PDM operations#
The read-in data is stored in the PDM operation card. The operation forms a bracket over the different components of the import. The data to be processed in Microsoft Dynamics 365 Business Central1 are then stored in the PDM table and PDM link.
Based on#
Processing stack#
On the basis of a batch processing