Supplier certificates: which plant is covered?

One supplier, two plants

Suppose a company's purchasing policy requires a particular certificate for the plant supplying a specified product group. The supplier operates Plants A and B. The planned purchase concerns Plant B, but the certificate provided names only Plant A. Its validity date is current.

The reviewer can record that a document for Plant A has arrived. Plant B still lacks a document matching the company's requirement. The current date does not resolve that difference, so the employee asks the supplier for a certificate covering B.

A register designed for this work shows the supplier’s two plants separately. For Plant A, the employee opens the attachment and review finding. For Plant B, they see the purchase requiring a document, what is missing, and who is handling the supplier conversation. A colleague taking over can return to those findings without reading the entire email thread.

When the supplier responds, the employee saves the explanation and new attachment with the same case. The designated reviewer checks them against the requirement for Plant B and records the decision.

What a buyer needs beside the purchase

The useful connection is specific: this supplier, this plant, and the requirement for this purchase. A certificate folder may store files well while review findings live in a separate spreadsheet. The buyer can find a document but still has to ask whether anyone checked it for their situation.

A focused view can place the requirement and the reviewer's finding side by side, with access to the attachment. If the plant's name in the system differs from the name in the file, someone who knows the supplier needs to resolve that association.

When a certificate is replaced, the earlier record still helps explain past decisions. The new file needs to be checked for the relevant scope; adding it to the supplier profile does not establish which plants it covers. Someone in the company also needs to maintain purchasing requirements so the register reflects what the team actually expects from suppliers.

Check your existing module first

SAP Ariba documents certificate profiles with attachments, dates, and status, plus modular questionnaires associated with dimensions including commodities, regions, and departments. Approvers compare questionnaire details with attachments; the system does not validate that correspondence itself (SAP supplier certificate management).

Ask your administrator to show how a certificate is linked to one plant and a planned purchase. The buyer needs to see the document's scope, the review finding, and unresolved requirements. If the module already supports that view, organizing records and using the available fields or questionnaires may be enough. Compare the work and ongoing support this would require with building an additional application.

An integration makes sense when the purchasing system holds the plant and purchase details while documents and reviews are managed elsewhere. Connecting them could let the buyer open the relevant file and finding without searching again. Establish which information both tools make available before commissioning the connection.

Consider a custom register when staff repeatedly reconstruct these relationships from several sources and the available modules make them difficult to use. An initial scope could cover one certificate type and one purchasing category. The main deliverable is a shared view for the people reviewing documents and the buyers relying on those findings.

Keeping reviews usable over time

When migrating records, keep attachments with their plant associations and review findings. Importing a list of certificates alone leaves staff to work out what each one covers again. Open supplier questions should move with the person responsible for them, while older materials can remain in an accessible archive.

Agree with the provider who handles a plant change in the purchasing system that fails to appear in the register. Your company continues to own its requirements and document reviews; application and integration maintenance need an agreed scope. Settle code and data ownership, exports that retain attachment relationships, and the arrangements for another provider to take over maintenance before buying.

If documents are already associated correctly and the difficulty is following up on renewals, our article on expiring document reminders and follow-up covers that work.

Commission a supplier certificate register

Syntalith builds custom applications. For this project, we propose a view connecting the certificate, supplier site, purchasing requirement, and review finding to your existing purchasing module. The buyer opens the document with the assessment relevant to their purchase, while the reviewer records that assessment once against the correct file.

Tell us about the last certificate that required someone to clarify which plant it covered. Explain where the employee found it and where they recorded the answer. That will help determine whether you need a connection between existing tools or a dedicated view for reviewing and using the documents. See Syntalith pricing for information about billing.