Upload
others
View
13
Download
1
Embed Size (px)
Citation preview
1
X-BOM Connector for Oracle Manufacturing User's Guide
3DEXPERIENCE R2018x
2
3DEXPERIENCE Platform is based on the V6 Architecture © 2007-2017 Dassault Systèmes.
The 3DEXPERIENCE Platform for 2018x is protected by certain patents, trademarks, copyrights, and other
restricted rights, the full list of which is available at the 3DS support site: http://help.3ds.com/ .
Certain portions of the 3DEXPERIENCE Platform R2018x contain elements subject to copyright owned by
third party, the full list of which is also available at the 3DS support site mentioned above.
You will require an account with support in order to view this page. From the support page, select your
desired product version and language to launch the appropriate help. Select Legal Notices from left frame.
This displays the full list of patents, trademarks and copyrights for this product.
Any copyrights not listed belong to their respective copyrights owners.
Prepared by International TechneGroup Inc.
3
Table of Contents
Table of Contents ................................................................................................................ 3 Introduction to the Integrations ........................................................................................... 4 Part Transfer........................................................................................................................ 5
Introduction ..................................................................................................................... 5 How to Transfer a Part (Integration with ENOVIA Engineering BOM Management) .. 5
Automatic Transfer ..................................................................................................... 5 Transferring a Part Manually .................................................................................... 12
How to Transfer a Part (Integration with ENOVIA Manufacturing BOM Management)
....................................................................................................................................... 13
Automatic Transfer ................................................................................................... 13 Transferring a Part Manually .................................................................................... 17
BOM Transfer (Integration with ENOVIA Engineering BOM Management) ................. 20
How to Transfer a BOM ............................................................................................... 20 How to Transfer a BOM without an Engineering Change (Optional) .......................... 21
BOM Transfer (Integration with ENOVIA Manufacturing BOM Management) ............ 23
How to Transfer a BOM ............................................................................................... 23 Viewing ERP Data ............................................................................................................ 25
Displaying ERP Item Master and Item Revision Data ................................................. 25 Displaying an ERP BOM .............................................................................................. 31 Using the Powerview .................................................................................................... 32
Creating ENOVIA Live Collaboration Parts from ERP Item Masters ............................. 35 Comparing ERP and ENOVIA BOMs ............................................................................. 37
4
Introduction to the Integrations
ENOVIA ERP Integrations offer a flexible and powerful way to manage, control, and
unite information and processes between ERP Applications and the ENOVIA PLM
Solution. Utilizing the ENOVIA Engineering BOM Management™ application as the
interfacing medium, this integration enables organizations to maximize information reuse
while eliminating both duplication of effort and inconsistencies across bills of materials
(BOMs), inventory data, and Engineering Change Orders (ECOs). This real-time link
affords companies up-to-date information, driving quicker product-to-market deliveries.
This manual reviews the integration from a user’s perspective. The setup and optional
parameters are discussed in the respective System Administration Guide and the
“ENOVIA / ERP Integrations Core Installation and Administration Manual” available to
all the ITI-developed ERP Integrations. The Integration administrator should review
these manuals.
Note: This manual describes integration functionality only. The instructions in this
manual assume that the user is already familiar with proper ENOVIA Engineering BOM
Management or Manufacturing BOM Management usage, including: Part creation and
maintenance, Bill of Material creation and manipulation, Engineering Change
management, and any special sign-off or lifecycle functionality that may be in place at
your site.
5
Part Transfer
Introduction
The integration provides the facility to transfer Part types and the associated metadata
from the ENOVIA Live Collaboration into the ERP system. The integration provides
two methods to accomplish this task:
1. The installation adds an event trigger on the policy between two different steps in
either the Part, Change Action (CA), Change Order (CO), or MCO lifecycles. If
the trigger is on the Part lifecycle, then when the Part is promoted, the event
trigger fires and the transfer takes place. If the trigger is on the CA or CO
lifecycle, then the Part will be transferred when the Change is promoted. If the
ENOVIA Manufacturing BOM Management module is installed, then the Part
will be exported as part of the MCO lifecycle. The particular method used at your
site will depend on how the integration is configured to fit your specific business
practices.
2. An “On-Demand” Action command that allows the user, based on privileges, to
initiate the transfer.
How to Transfer a Part (Integration with ENOVIA Engineering BOM Management)
Automatic Transfer
In order to transfer a Part from the ENOVIA Live Collaboration, the object typically
must have certain metadata associated with it for the ERP system to accept it. Many of
these attributes are configurable in ENOVIA Engineering BOM Management, while
others may not be user parameters, but site-specific parameters that are static or defaulted
by the ERP system. The integration allows for the setup and/or mapping of the
appropriate attributes during the installation and configuration phase. Please refer to the
administration guides for this information. Besides typical information such as Unit of
Measure, Description, etc., the manufacturing organizations that the Part(s) should
populate must also be established. This parameter can be permanently set if these are
static values; otherwise, the integration provides a GUI to allow you to specify the
organizations to transfer the Parts to.
Part updates may be sent to the ERP system without generating a revision. The
information in the ERP system is then simply overwritten. Parts may also be revised and
the revised object information passed to the ERP system. In ENOVIA Engineering BOM
Management, this process requires that an CA be associated with the Part. If your
business process allows Parts without associated Engineering Changes, the integration
will support that configuration as well. The integration performs the same regardless of
whether it is a new Part, Part update, or Part revision.
6
Figure 1 ERP integration options are added to the Part menu
The integrations enhance the ENOVIA Engineering BOM Management schema and user
interface to facilitate the actions required of the integration. In the figure above, the
“ERP Organizations” menu choice has been added to the menu tree in the left frame.
“ERP Organizations” is used with the EBOM integration to connect ERP organizations to
the current Part.
“ERP Powerview” displays a window containing links to both the ENOVIA Live
Collaboration and ERP data for the current Part.
The “ERP Transaction Status” is an optional menu option utilized by the Oracle
Integration if batch mode is used. It reports the status of batch item imports in the Oracle
ERP system.
The first step in exporting a Part to ERP is to associate one or more organizations to the
Part. To do this, select the ERP Organizations command from the menu tree in the left
frame. All organizations currently associated with the Part will be displayed. For new
Parts, the display is blank.
7
Figure 2 Related organizations are displayed in the ERP Organizations form
To enable editing of associated ERP organizations, select the Edit icon
Figure 3 Select the Edit icon to enable organization assignments
Select the “Add Existing” ( icon) . To start the selection process, the “Find” dialogue
is used to find all appropriate organizations in the ENOVIA Live Collaboration database.
8
Figure 4 Use the Find dialogue to locate and assign all ERP organizations to the Part
9
Once the list is presented, select one or more Organizations to associate with the Part.
The Part will be transferred to each manufacturing Organization as well as the Part
Master in the ERP system (if required).
Figure 5 Organization-specific attributes can be set for the Part
The third and final step is to assign values to the appropriate attributes. In the diagram
above, you can see that there are entries for Effectivity and Production Make Buy Code.
The integration can be molded to fit your business process--i.e., these values are not
required in the out-of-the-box (OOTB) installation but may be required at your site. The
Effectivity Date is a date field input and the Make-Buy Code is a pull-down option menu.
Figure 6 Select Save to finalize organization assignment
10
Select "Save" and the Part will now have one or more manufacturing Organizations
associated to it.
11
Figure 7 Part exported to ERP by promoting it through its Lifecycle
The typical approach to exporting Parts is to transfer the information via an event trigger.
The event is either the promotion of the Part through its lifecycle or the promotion of the
Engineering Change through its lifecycle, depending on how your integration is
configured.
Figure 8 Part exported successfully via promotion
In the example above, the event is triggered on the promotion of the part from the Review
state to the Approved state. The position in the lifecycle where the trigger fires is
configurable during setup. On success or failure, the user is presented a status window
containing a message of the transaction.
If the Part export event is triggered on the promotion of the Part, then the functionality is
the same – that is, the Part will be exported to all ERP Organizations with which it is
associated.
As Parts are revised and updated, these Part attribute updates may be exported to ERP as
well. Whether this occurs depends on the setting of various setup configuration
12
parameters. The integration can be set up to always export Part updates, to never export
Part updates, or to compare revisions and only export if there are changes.
Transferring a Part Manually
A Part export to ERP can be manually forced from ENOVIA Engineering BOM
Management. In order to do this, select the “Export Part to ERP” button as shown below.
(In some installations, the “Export Part to ERP” button may appear as a separate pull-
down rather than a button). If you do not see the “Export Part to ERP” option, then your
account does not have the required privilege to exercise this option. Parts that are
exported using this option are specially tagged in the Part history in order to indicate that
they were not exported via the standard lifecycle process.
Figure 9 Select the "Export Item to ERP" icon to manually export a Part to all associated
ERP organizations
Figure 10 Successful manual ERP Part export
13
How to Transfer a Part (Integration with ENOVIA Manufacturing BOM Management)
Automatic Transfer
In order to transfer a Part from the ENOVIA Live Collaboration, the object typically
must have certain metadata associated with it for the ERP system to accept it. Many of
these attributes are configurable in ENOVIA Manufacturing BOM Management, while
others may not be user parameters, but site-specific parameters that are static or defaulted
by the ERP system. The integration allows for the setup and/or mapping of the
appropriate attributes during the installation and configuration phase. Please refer to the
administration guides for this information. Besides typical information such as Unit of
Measure, Description, etc., the manufacturing Organizations that the Part(s) should
populate must also be established.
Part updates may be sent to the ERP system without generating a revision. The
information in the ERP system is then simply overwritten. Parts may also be revised and
the revised object information passed to the ERP system.
The first step in exporting a Part to ERP is to associate one or more Organizations to the
Part. To do this, select the Manufacturing Responsibility command from the menu tree in
the left frame.
Figure 11 A Manufacturing Responsibility must be assigned to each Part
14
From the top menu, choose ‘Edit All’ to enable Manufacturing Responsibilities for the
part to be added or changed.
Check the box of the corresponding part, and from the top ‘Actions’ menu, choose
‘Create new Manufacturing Responsibility’ (OR, if configured to do so, select
“Manufacturing Responsibility -> Create New Manufacturing Responsibility” from the
“Change Action”)
Figure 12 Select a Manufacturing Responsibility option
After Locations are assigned to the Part, Plant-specific attributes can also be assigned.
Figure 13 Plant-specific attributes can be assigned to each Part if desired
After all assignments have been made, use standard ENOVIA Engineering BOM
Management and ENOVIA Manufacturing BOM Management functionality to promote
the Part and its associated Engineering Change through their lifecycles.
When the Change Action is released, this results in the creation of one or more MCOs.
15
Figure 14 An MCO is created for each Plant associated with the Part
To export the Part, promote the MCO from Create to the next State.
Figure 15 Promote the MCO through its Lifecycle to trigger ERP Part and MCO export
16
Figure 16 MCO promotion to Review triggers export of all associated Parts to ERP
If the export is successful, the MCO will move to the next state. If it is not, then an error
will be displayed. After the problem is resolved, the MCO can be promoted again for a
successful Part export.
As Parts are revised and updated, these Part attribute updates may be exported to ERP as
well. Whether this occurs depends on the setting of various setup configuration
parameters. The integration can be set up to always export Part updates, to never export
Part updates, or to compare revisions and only export if there are changes.
17
Transferring a Part Manually
A Part export to ERP can be manually executed in ENOVIA Manufacturing BOM
Management outside of the promotion process.
There are two ways to do this:
1) Export pre-released Parts to all associated Plants
A Part can be exported to all plants that it is associated with. An MCO does not have
to exist.
In order to manually export a Part to all Plants, select the Action pull-down from the
main Part menu and select “Export Part to ERP” as shown below. (In some
installations, the “Export Part to ERP” button may appear as a separate button rather
than a pull-down.). If you do not see the “Export Part to ERP” option, then your
account may not have the required privilege to exercise this option. Parts that are
exported using this option are specially tagged in the Part history in order to indicate
that they were not exported via the standard lifecycle process.
Figure 17 Select "Export Part to ERP" to export a Part manually to all Plants
18
Figure 18 Succesful manual Part export
2) Export All MCO Parts to ERP
All Parts associated with a specific MCO can be manually exported to the MCO’s
Plant.
In order to manually export a Part, select the “Export MCO Parts” button on the main
MCO form as shown below. If you do not see the button, then your account may not
have the required privilege to exercise this option. Parts that are exported using this
option are specially tagged in the Part history in order to indicate that they were not
exported via the standard lifecycle process.
19
Figure 19 Select "Export MCO Parts to ERP" to export Parts related to an MCO
Figure 20 Successful export of all MCO Parts
20
BOM Transfer (Integration with ENOVIA Engineering BOM Management) The transfer of a BOM is triggered by the associated Change Order (CO) or Change
Action (CA). ENOVIA Engineering BOM Management (EC) defines the events that will
typically occur when creating, promoting, and otherwise managing COs, CAs, and
BOMs. There are, for example, also other checks unrelated to the integration that are
performed in EC before the BOM may be released to manufacturing. To export a BOM
to ERP, the integration traverses the CA to find all parent Parts attached to it. It is
possible to export multiple BOMs in one transaction if they are all associated to the same
Engineering Change. If a previous revision of the BOM exists, then the components of
the new revision will be compared with the components on the previous revision. Only
BOM differences will be sent to ERP.
How to Transfer a BOM
The transfer of a BOM assumes the following:
--The BOM meets all of the required engineering specifications.
--The BOM has been released from engineering design.
--The BOM has an associated CA.
Figure 21 BOM with two children
In the example above, we are using a simple BOM with two children. The parent item
has been selected and the resulting structure is shown in the bottom table display. The
parent Part has been “Approved” and is ready for transfer. The next step is to promote
the associated Engineering Change.
21
Figure 22 BOM successfully exported
When a BOM is transferred successfully, information is displayed for each MFG
Organization that the information was sent to. This information is also written to a log
file on the operating system.
If there is an error, the Engineering Change promotion will fail and you will be presented
with a message that describes the problem. Once the error has been resolved, you can
restart the promotion.
Subsequent revisions of the BOM are processed in exactly the same way. The
Engineering Change process in EC controls the building and release of the BOM
revision.
How to Transfer a BOM without an Engineering Change (Optional)
The integration provides the optional capability to export (copy) a BOM to organizations
where it does not yet exist. The entire single-level BOM is exported. No BOM
comparison is performed. The integration provides a way to manually initiate this BOM
Copy.
To copy a BOM, query for an existing Part. Select the “BOM Powerview” option for the
Part. Next, select the “Export BOM to ERP (no ECO)” option from the “Reports” pull-
down menu as shown below.
22
Figure 23 Export BOM without an ECO
The BOM will be copied to all ERP organizations where it does not yet exist and will
return a message indicating the orgs to which the BOM was copied.
Figure 24 Successful export of BOM without an ECO
NOTE: The capability described above is an example of how this could be implemented.
Consult your applications administrator for details on the usage of this capability at your
site.
23
BOM Transfer (Integration with ENOVIA Manufacturing BOM Management) The transfer of a BOM is triggered by the associated Manufacturing Change Order
(MCO). ENOVIA Engineering BOM Management and ENOVIA Manufacturing BOM
Management define the events that will typically occur when creating, promoting, and
otherwise managing MCOs, CAs and BOMs. There are, for example, also other checks
unrelated to the integration that are performed in EC before the BOM may be released to
manufacturing. To export a BOM to ERP, the integration traverses the MCO to find all
changed Parts attached to it. It also looks at any associated CAs as well as the Part
objects themselves. It is possible to export multiple BOMs in one transaction if they are
all associated to the same MCO. In the ENOVIA Manufacturing BOM Management
product, there is no concept of a current and previous BOM. Instead, the integration
looks solely at the changes on the MCO under consideration and exports the BOM
structure changes to ERP.
How to Transfer a BOM
The transfer of a BOM assumes the following:
--The BOM meets all of the required engineering specifications.
--The BOM has been released from engineering design.
--The BOM has an associated MCO.
Once these criteria are met (along with any other criteria required by the ENOVIA
Manufacturing BOM Management module), the BOM changes are exported to ERP
simply by promoting the associated MCO from “Review” to “Release”.
Figure 25 Export BOM by promoting MCO through Lifecycle
24
Figure 26 Successful MCO export
When a BOM is transferred successfully, information is displayed for the MFG
Organization that the information was sent to. Each MCO exports the BOM to one
specific Organization.
If there is an error, the MCO promotion will fail and you will be presented with a
message that describes the problem. Once the error has been resolved, you can restart the
promotion.
Subsequent revisions of the BOM are processed in exactly the same way. The MCO
process controls the building and release of the BOM revision.
25
Viewing ERP Data
The integration provides the capability for users to view information in ERP directly
while in the ENOVIA Live Collaboration. This ERP data is not stored in the ENOVIA
Live Collaboration, but is a real-time view of actual data in the ERP system. The
viewing of this information is made possible by the implementation of the ENOVIA Live
Collaboration Adaplet.
The integration adaplet implementation is in “read-only” mode. This means that the ERP
information may be viewed, but cannot be modified in any way.
The integration provides two means of displaying ERP data. The functionality is
identical, but the means used to find the ERP Items are different, as shown below:
1. Query for the ERP item and display the data. This allows you to query for any
ERP Part, regardless of whether it exists in ENOVIA already.
2. Link a ENOVIA Part to an ERP Part and view the ERP data in the resulting
Powerview. By clicking on “Integration Tools->Powerview” when viewing an
ENOVIA Part, the program will automatically display any existing ERP data for
the ENOVIA Part.
Note: ERP data may appear differently than it is shown here, and also may contain
varying levels of detail depending on the target ERP system.
Displaying ERP Item Master and Item Revision Data
To display ERP data, the “Engineering->General” search or the “Find Like” search can
be used. A sample search is shown below:
26
Figure 27 Enter name and select ERP Type for ERP data search
Perform an Engineering "General" search. Specify an item name and click on the Type
Selector to display the default types. Select the "ERP Part Master" Type. If using "Find
Like" you may need to select a vault name. Enter any other desired criteria for the
search. Select the “Search” button.
27
Figure 28 Select ERP part to display
A list of possible ERP items is returned. The information in the example above lists the
item “SB41430*” for every Organization that the item belongs to. The Revision column
lists the Organizations. By further selection of the item, the actual revisions may be
viewed. Select the ERP Part that you want to view.
28
Figure 29 Select option to view ERP data
Here we have selected the “Atlanta” Organization from the results display list. The
menus have been trimmed to only display the commands that are available for the ERP
data items -- in this case, Lifecycle, Revisions and ERP Bill of Materials. The attribute
information that is displayed is read directly from ERP via the adaplet. This information
is not retained in ENOVIA.
29
Figure 30 ERP States or Lifecycle steps
After selecting the Lifecycle command, the display lists the current state or status of the
Part in ERP (varies by ERP system).
Figure 31 Select ERP revision
After selecting the Revisions command, the display lists the revisions that belong to the
Atlanta ERP Organization. Each revision can be selected to display revision-specific
ERP attributes.
30
Figure 32 ERP revision data
31
Displaying an ERP BOM
The adaplet also enables the display of the ERP BOM. The BOM display is based on
specific Organizations. There are several options in displaying BOMs, which are
described below.
Figure 33 ERP BOM displays all components before filtering
After retrieving the parent item and selecting the “ERP Bill of Materials” command, the
display will be as shown as above. The default display shows all of the children items in
the BOM for all effectivity dates, including those from the past. Note that each entry has
an effectivity start and end date so it is possible that a display could contain multiple
entries for the same item.
Figure 34 ERP BOM effectivity date can be specified
Also note that the display has two input fields at the top of the table: 1) Display by
Effectivity Date and 2) Filter by Revision. These are the options that the user can use to
manipulate the display.
32
Using the Powerview
As described above, the Powerview can be used to view the identical ERP data for Parts
that exist both in the ENOVIA Live Collaboration and in ERP. To use the Powerview,
query for an ENOVIA Part, then select the “Integration Tools” menu and the
“Powerview” submenu. This will display the ERP data Powerview.
Figure 35 Select ERP Powerview
If the ENOVIA Part that is selected already exists in ERP, then a list of Organizations
will be displayed in the “Set Locations” panel. If the Part does not exist in ERP, then
there will be no locations listed.
33
Figure 36 Select an ERP organization
Select the ERP Organization for which you want to view ERP data. Until you select this
Organization, you will not be able to view any ERP data.
34
Figure 37 Select tabs to view ERP data
Once you have selected the ERP Location, click on the various ERP data tabs. Each tab
functions identically to the descriptions above as far as viewing ERP data is concerned.
35
Creating ENOVIA Live Collaboration Parts from ERP Item Masters
The integration provides the capability to instantiate “Parts” in the ENOVIA Live
Collaboration from Item Master information stored in the ERP system. This capability is
being provided to allow companies that do not bulk load all of the ERP Masters into
ENOVIA to do so on a single case-by-case basis.
Figure 38 Select "Create ENOVIA Part" to create Part from ERP data
Figure 39 Part is created and associated with ENOVIA organizations
36
The “Create ENOVIA Part” command button is available for any ERP item that has been
retrieved. Once the item is highlighted, the user may press the “Create ENOVIA Part”
button (in some installations, this may be located in an Action menu pull-down). If the
item already exists, you will be notified and no action will be taken. If the item does not
exist in the ENOVIA database, then the item(s) are created and associated with each
available Organization.
The above example shows a typical success message stating that the item was created for
one Organization but not for others. This is because the ENOVIA Live Collaboration
does not include Business Units for those Organizations.
37
Comparing ERP and ENOVIA BOMs Note: This capability is not available in the Integration with ENOVIA Manufacturing
BOM Management.
A report comparing ENOVIA and ERP BOMs can be generated. To generate this report,
first query for an ENOVIA Part. Then navigate to the Part’s Engineering Bill of
Materials. Select the “Compare ERP BOM” option from the Action menu.
Figure 40 Select Compare ERP BOM from BOM Powerview
This will generate a report that contains the instructions required to cause the ENOVIA
BOM to have the same structure as the ERP BOM. If the BOMs are identical, the
instructions will be blank. This report can also be generated from the “Integration Tools”
Powerview by selecting the “Compare ERP BOM” tab. The integration will compare the
currently selected ENOVIA Part revision with the latest effective ERP BOM revision.
38
Figure 41 Sample ERP BOM comparison report