Configuration Assumptions
Windchill ESI assumes that your
SAP distribution targets provide the APIs listed in the topic
SAP APIs and they are characterized as described in Appendix C.
Windchill ESI may not work as designed unless any differences between these assumptions and your
SAP distribution targets are resolved through configuration or customization of
Windchill ESI, or
SAP distribution targets, or both.
|
|
The detailed configuration steps and the screen examples provided in the section, "Installing Windchill ESI" in the Installing and Configuring Windchill ESI in an SAP Environment (Installation et configuration de Windchill ESI dans un environnement SAP) are also based on these assumptions.
|
Create and Change Part Configuration Assumptions
To create or change parts in your SAP distribution targets, the following are assumed:
• For material types HALB and ROH:
◦ Configurations are not changed from those delivered with a standard version of SAP.
◦ No fields are configured as required with the exception of those fields that are consistently sent from Windchill PDMLink to the SAP distribution target.
• Material view is configured as: Basic Data 1, MRP.
• Company codes and plants are configured.
• Change management is enabled for material masters, BOMs, and documents.
• Versioning and revisioning flags for material masters are configured to allow versioning and revisioning.
• The login used by the TIBCO connection has the appropriate roles assigned to it such as create material and change material.
• Material master fields to be populated fromWindchill PDMLink data are not configured as locked.
• Materials are configured for external revisioning and to accept external naming for material numbers and intervals are maintained.
• TheWindchill PDMLink attribute values are cross-referenced with the SAP distribution target values.
Create and Change Document Configuration Assumptions
To create or change documents in your SAP distribution targets, the following are assumed:
• Standard SAP document types are maintained and configured as outlined in the "Setting up SAP Configurations" section of the Installing and Configuring Windchill ESI in an SAP Environment (Installation et configuration de Windchill ESI dans un environnement SAP).
• The only fields that are configured as required are those that are consistently passed fromWindchill PDMLink to the SAP distribution target.
• Documents are enabled for external versioning and to accept external numbering.
• Company codes and plants are configured.
• Change management is enabled.
• The login used by the TIBCO connection has the appropriate roles assigned to it such as create document and change document.
• The SAP document info record fields to be populated fromWindchill PDMLink data is not configured as locked.
• Required document fields are maintained.
• TheWindchill PDMLink attribute values are cross-referenced with the SAP distribution target values.
Create and Change BOM / Group BOM Configuration Assumptions
To create or change BOMs / Group BOMs in your SAP distribution targets, the following are assumed:
• Required BOM/Group BOM fields are maintained and the only BOM/Group BOM fields that are configured as required are those that are consistently passed fromWindchill PDMLink to the SAP distribution targets.
• The SAP BOM/Group BOM fields to be populated fromWindchill PDMLink data are not configured as locked.
• Company codes and plants are configured.
• The login used by the TIBCO connection has the appropriate roles assigned to it such as create material, change material, and create BOM.
• Allowed material types for BOM/Group BOM header and items are maintained.
• External assignment of line numbers is enabled.
• Change management is enabled.
• Versioning and revisioning flags for BOMs/Group BOMs are enabled.
• TheWindchill PDMLink attribute values are cross-referenced with the SAP distribution target values.
Create CN Configuration Assumptions
To create CNs in your SAP distribution targets, the following are assumed:
• The only fields that are configured as required are those that are consistently passed fromWindchill PDMLink to the SAP distribution targets.
• Company codes and plants are configured.
• The login used by the TIBCO connection has the appropriate roles assigned to it such as create material, change material, and create BOM.
• Required change master fields are maintained and those fields populated fromWindchill PDMLink data are not configured as locked.
• The material, BOM, and document object types are not configured as required.
• Change management is enabled for materials, BOMs, and documents.
• External assignment for change numbers is enabled.
• TheWindchill PDMLink attribute values are cross-referenced with the SAP distribution target values.
Creating and Changing Process Plans
To create or change process plans in your SAP distribution targets, the following are assumed:
• Associated Operation Work centers exist in SAP.
• The following mappings for time are based on the default AP Workcenter 1100
◦ Setup time — Standard value: 1; and Standard unit: 1
◦ Processing time — Standard value: 2; and Standard unit: 2
◦ Labor time — Standard value: 3; and Standard unit: 3
This mapping needs to be customized based on the workcenter and plant configuration.
• When Process Plans are published to SAP, the associated BOMs, operations, sequences and control characteristics are also published. Resources allocated to operations are published as well; however, skills are ignored by the middleware business logic.
• Documents associated to operations and resources are published, but those associated to process plans and sequences are ignored by the middleware business logic.
• A CN with Parametric effectivity, such as serial effectivity, is not supported for Process Plan publication.
• A standard sequence must have a branching and returning operation.
• Labels of operations that occur in a parallel sequence must fall in the range between the branching and returning operations.
• By default Process Plans are published with a status of 4 (Released)
• Sub-operations are supported only up-to one level. This means a sub-operation cannot have a sub-operation within itself.
• The middleware throws an exception for the following conditions:
◦ IsStandard flag is set to true
◦ Multiple versions for the same part are published in a single transaction
◦ Component of a phantom BOM is allocated to a Routing operation
◦ BOM is a Phantom CAD subassembly
