All information from the top-level reported part that is directly connected to the material declaration is copied to the manufacturer equivalent part (MEP). If more than one MEP is associated with a material declaration, the reported part will be copied to each MEP. Reported materials directly connected to the top-level reported part are copied to the manufacturer equivalent part directly as external materials. Any child EBOM structure under the reported part are copied to the manufacturer equivalent part as the supplied part EBOM structure along with materials as external materials. The app copies reference documents attached to reported materials to external materials, and documents attached to parts to MEPs. Any attachments to the material declaration itself are not copied or removed. You must have the Author/ Leader or Compliance Engineer access role. Materials Compliance Management can be configured for parallel approval of material declarations to speed up the process. If your system is configured for parallel approval, the process is submitted as a master job that runs in the background and can be monitored on the Background Jobs Page. Import, export, and some other operations also create a master jobs. The number of concurrent master jobs is configurable. If the maximum number of master jobs are in process, the approval job waits until the prior jobs complete. If your job is waiting, you can apply the Running filter on the Background Jobs page to evaluate the jobs waiting to be executed. You can then decide to abort the prior job, if appropriate, to allow the approval process to complete. For further troubleshooting, a System Administrator with access to MQL can run this command to identify the running master jobs: temp query bus Job * * where "current=='Running' && description=='Master Job'"; The result lists all master jobs in the Running state. You can abort any NON important job to allow the Material Declaration job to start running. | |||||||