Mapping P and O and Maturity Attributes During Import

Mapping P&O and Maturity Attributes during Import enables you to share the same value or modify the incoming values of P&O and maturity attributes between two sites during import of PLM objects.

Required baseline access roles: Author, Leader.

For example, the objects coming from a specific supplier are always imported in a specific project even though the values of P&O attributes are different for two sites. These different values of P&O attributes could be mapped declaring and implementing a Business Logic named PLMAttributeMapping. You can also use Business Logic to map other attributes such as maturity that can be executed during 3D XML with authoring or synchronization of a PLM Channel. For more information about this BL, see Feature Specialization: Reference Information: Business Logic: Coexistence: Attribute-Mapping Business Logic.

This page discusses:

Map P&O Attributes

Mapping P&O Attributes during Import functionality also determines the attribute values of owner, project and organization of the imported object through business rules.

Required baseline access roles: Author, Leader.

These business rules, by default, are defined by the administrator and are executed during Import As Reference or synchronization of a PLM Channel. Let us understand how Mapping P&O Attributes during Import functionality behaves when:

  • Business Logic Not Assigned: If business logic is not defined to map the value of P&O attributes such as User Name, Project and Organization, then the default values of importing user are considered during import.
  • Business Logic Assigned: When you define Business Logic to map the P&O attributes, the imported data comprises of the value of P&O attributes assigned through business logic. The data is only updated if the import is a new iteration of the object.

For example, if the User1 of Site1 exports a data containing P&O Attributes, the User2 of Site2 can access the same data while importing.

The table below demonstrates the business logic for customization of P&O Attributes during Import:

PLM Opening ID PLMAttributeMapping
Operation Id BriefcaseImport
Customization Intent The P&O attribute initializes with the data of the current connected user

For more information about customization, see Feature Specialization: Reference: Business Logics: Other: Attribute-Mapping Business Logic.

Note: While mapping attributes,
  • When you assign invalid values for P&O attributes, error message appears.
  • It is mandatory to map the three P&O attributes User Name, Project, and Organization in the BL otherwise the mapping will fail and the default-mapping behavior is used.

Map Maturity Attribute

Mapping Maturity Attribute during Import functionality also determines the attribute value of V_maturity of the imported object through business rules.

Required baseline access roles: Author, Leader.

These business rules, by default, are defined by the administrator and are executed during Import As Reference or synchronization of a PLM Channel. Let us understand how Mapping maturity Attribute during Import functionality behaves when:

  • Business Logic Not Assigned: When you do not define business logic to map the value of Maturity attribute then the default value of importing user is considered during import.
  • Business Logic Assigned: When you define business logic to map the maturity attribute, the imported data comprises of the value of maturity attribute assigned through business logic. The data only updates if the import is a new iteration of the object.

The table below demonstrates the business logic for customization of Maturity Attribute during Import:

PLM Opening ID PLMAttributeMapping
Operation Id BriefcaseImport
Customization Intent The maturity initializes with the start state of the maturity graph associated to the custom type.

Note: An error message appears when you assign invalid value to Maturity attribute.