Contents
What is the link between materials from the logistics system and the EHS module? How to keep the EHS database up to date and in line with the businesses' activities? In this page, you will learn how PROD_COM s* are created, materials assigned to them and how to manage their life cycle.
Product Initialization
It is always possible to create manually a PROD_COM from scratch in EHS . However to allow interaction with the logistics system, mandatory for automatic SDS distribution and Dangerous Goods Controls , there are some tools to automatically create the PROD_COM in EHS based on a trigger in the logistics system.
Interface Product axis
In WP1, there is a complete integration between the Material Master Module and EHS . In the material master, the businesses work at the packed material level (Product A as drum, bulk, etc.) but also at a higher level, called the commercial product or "ZPRC" level . This combines any packaging of the same recipe (a virtual Product A without any packaging). Every time a new Commercial Product is created, its corresponding PROD_COM is automatically created in the EHS module the following day. All the packed materials attached to the Commercial Product in the Material Master are also attached to the PROD_COM and the list is updated automatically when there is a relevant change in the Material Master. The names are also transferred, so when a material is set as *OBS* in the logistics system, we can see it in the EHS module.
This is also applicable for Raw Materials.
The product axis is not able to assign the PROD_COM to the relevant authorization groups so when they are created, the new PROD_COMs are always in "ALL" . It is the responsibility of the Product Stewards of the Businesses to move them to the relevant group before making any update (because anyone can access to ALL in display mode).
Interface PF1-WP1
Unfortunately a complete integration was impossible because the EHS module and the logistics system where materials are created are 2 different SAP systems. However, in order to better align the management of SDS on business activity, an automatic PROD_COM creation was implemented.
in PF1:
The first program reads the table of material groups in the logistics system (PF1) and selects the ones that have following criteria:
- Not R&D written in the description
- Material group code starts with a number contained in a dedicated table (ZZE_DIVISION) validated by each business
An initial run was made of this program and from a starting date, the program then identifies any new creation of a material group. Then a second program comes into play. Any new material group creation in PF1 (detected by the first program) will trigger a PROD_COM creation in WP1.
The PROD_COM created will have the material group code as identifier NUM:Z_MATGROUP and its description as NAM:Z_MATGROUP.
One report of creation will be sent by division. The address of the Google group and the division concerned is stored in a table and can be updated on request.
If an update is detected on a material group, the NAM:Z_MATGROUP of the relevant PROD_COM will be updated also but no report will be send.
For Composite Materials / BOM Vault
The PROD_COMs for Composite Materials products are created in the same way as all other GBUs, meaning that the "Product Axis" program automatically creates the PROD_COM in CG02 in WP1 based on the commercial product or "ZPRC" creation.
A new logic was added to the "Product Axis" program specifically for Composite Materials GBU where it automatically set the Authorization group at the PROD_COM during its creation.
Rule >> Checks on ZPRC data:
- If Material group = 0450 (FG) and Lab/Office field = Z20 >> It sets Authorization group = ZZ_BU_20 on the creation of the PROD_COM.
- If Material group = 0451 (RM) and Lab/Office field = Z20 >> It sets Authorization group = ZZ_BU_00 on the creation of the PROD_COM.
The field: “Lab/Office” identifies the product belongs to Composite Material GBU .
There are interfaces that copy the material codes of ZPRCs and ZMATs to the BOM Vault(*) or WPX .
Once the PROD_COM is created in WP1 (only with Header information: header, identifiers and material assignment - no data on the Property tree), another Interface is executed to copy the PROD_COM to WPX. This interface copies only PROD_COM whose authorization groups are = ZZ_BU_20* and ZZ_BU_00 . They have different configurations between them. Find below the details:
Interface from WP1 to WPX => Copy PROD_COM - ZZ_BU_20 (FG, R&I and Intermediates): Click here to get more details about this interface.
For ZZ_BU_20 => There is only Header data in WP1. No Property tree data is added directly in WP1. Property tree data is added/maintained only in WPx, since there is CUI (**) data. SDS and Labels are generated in WPX. All these PROD_COMs are classified for Export Control.
Interface from WP1 to WPX => Copy PROD_COM - ZZ_BU_00 (Raw Materials): Click here to get more details about this interface.
For ZZ_BU_00 (Raw Materials) => There is a difference on the data maintenance depending on the Export Control Classification of the products. If the products is classified as:
- TC2: all data (Header and Property tree) is maintained directly in WP1 and transferred to WPx. But no data update is done in WPx. These Raw Materials are therefore available in both systems WP1 and WPx. But in WPx it's mainly display mode. We also do not transfer Reports to WPX like SDS and others, we only transfer data. If CM wants to check reports of these Raw Materials, they have to check them in WP1 or Sinequa.
- All other classifications (not TC2): Only few data is maintained in WP1: Some identifiers and some RM specific data. All other property tree data must be maintained only and directly in WPx, since there is CUI (**) data. That's why these Raw Materials are dedicated to Composite Materials and can not be shared to other GBUs, since all EHS data is only available in WPX and other GBUs do not have access to it.
The Export Control Classification is maintained at PROD_COM level in WPx by the Export Control team at the field: "Rating" on the Header of CG02 transaction.
(*) Bom Vault is an SAP system dedicated for Composite materials GBU, also named WPX. The server is located in USA soil and only Composite Materials GBU has access to it.
(**) CUI (Controlled unclassified information) and Technology data: All the data that must be protected due to some Export control restrictions is called CUI (Controlled unclassified information) data or Technology data (for ITAR) and the access of this data is restricted by citizenship and specially for ITAR, it should be stored only in US location. These are the main data considered as CUI: Bill of Material and Composition data in EHS (all types of compo) including Composition report. The final document of SDS and Labels are considered Public data and therefore are not considered CUI or Technology. Unclassified information concerning certain items, commodities, technology, software, or other information whose export could reasonably be expected to adversely affect the United States national security and nonproliferation objectives. To include dual use items; items identified in export administration regulations, international traffic in arms regulations and the munitions list; license applications; and sensitive nuclear technology information.
Material Assignment
- For PROD_COMs automatically created by the Interface Product axis, all materials are automatically assigned to the Materials tab. It is not possible to modify in EHS the material assignment, it has to be done by the Business Data Administrator in the Material Master Data module and the change will be replicated automatically in EHS.
- For PROD_COMs automatically created by the PF1 - WP1 interface, it is trickier. In WP1, the Materials tab will remain empty however the material group code and name is attached as an identifier. In EHS in PF1, the materials can be found in the Materials tab and adjustments can be made manually from there.
| More questions? Ask them in our Discussion board or contact EH&S support team . |
|---|
This page has no comments.