Configuring Certificate Profiles and Certificate Types for Results Selection
Learn how certificate profiles and certificate types are configured to determine which inspection characteristics, results, and text elements appear on a generated quality certificate.
Explanation
A quality certificate is only as trustworthy as the configuration that decides what data it pulls and how it is formatted. In SAP QM, this is governed primarily by two configuration objects: the certificate profile and the certificate type, both maintained in Customizing under Quality Management > Certificates. The certificate type defines the overall category of certificate you intend to issue - for example a certificate of analysis, a certificate of conformance, or a material safety-related document. It controls the print program or form association, the certificate profile assignment logic, and how the system determines the object (material, batch, inspection lot, or delivery) that the certificate refers to. The certificate profile is where the real content design happens. Within a profile you define selection rules that tell the system which inspection characteristics to pull results from, whether to use results from a specific inspection lot, a batch's usage decision history, or an aggregated set of lots for a material/plant combination. You can restrict the profile to characteristics with a certain status (for example only those characteristics that received a valid result and are relevant for certificate output), and you can define fixed text characteristics that always appear regardless of whether an inspection took place, useful for boilerplate compliance statements. A key design decision is the selection strategy: results-based certificates pull actual numeric or qualitative results from completed inspections, whereas specification-based or standard certificates print the target specification values regardless of what was measured, which is only appropriate for conformance statements, not for analytical certificates. Getting this distinction wrong is a common audit finding - a certificate of analysis must show real values, not planned specification ranges. Characteristic selection within the profile can be based on the inspection plan's characteristic master data, the material specification, or a class characteristic view, depending on how your master data landscape is structured. It matters which characteristics are marked as relevant to the certificate at the master data level, because irrelevant or internal-only characteristics (like internal process temperatures) should typically be excluded from an externally facing document even if they were inspected. Output formatting is tied to a print program together with a Smart Form or SAPscript form (in ECC and S/4HANA on-premise) or increasingly Adobe Forms, referenced from the certificate type. The profile supplies the data; the form determines layout, logos, and legal disclaimers. Testing the combination of profile plus form against a real inspection lot before going live is essential, because certificate output is customer-facing and errors are visible externally, unlike many internal QM documents. In S/4HANA, the underlying configuration concepts are largely unchanged from ECC, but the surrounding creation and monitoring experience is increasingly delivered through Fiori apps, and Adobe Forms are the more common target for new certificate layouts. Regardless of release, the profile-to-type-to-form chain must be tested end to end, including scenarios where a characteristic has no recorded result, to confirm the certificate does not silently omit mandatory information.
Real project scenario
A specialty chemicals manufacturer needed a certificate of analysis for exported batches showing actual measured pH, viscosity, and purity values rather than target ranges. The initial profile had been copied from a conformance-certificate template and was configured for specification-based output, so early test certificates showed target ranges instead of lab results. The QM consultant reconfigured the profile to a results-based selection tied to the batch's inspection lot history, restricted to characteristics flagged as certificate-relevant in the material specification, and validated output against three historical lots with known results before releasing the profile for production use.
Common mistakes
• Copying a conformance certificate profile as the base for an analytical certificate without switching the selection strategy from specification-based to results-based. • Including internal-only characteristics on customer-facing certificates because master data relevance flags were never reviewed. • Not testing the profile against a lot with missing or partial results, leading to silent omissions on live certificates. • Assuming certificate profile changes take effect immediately for already-created inspection lots without regenerating the certificate. • Failing to align text elements and legal disclaimers in the form with what regulatory or customer contracts actually require.
Best practices
• Explicitly decide and document whether each certificate type is results-based or specification-based before configuring the profile. • Mark only genuinely externally relevant characteristics as certificate-relevant in material specifications or inspection plans. • Validate every new or changed profile against multiple historical lots, including edge cases with missing results. • Keep certificate forms and profiles under formal change control given their external, often regulatory, audience. • Document the mapping between certificate type, profile, and form so support teams can trace issues quickly.
Interview angle
Interviewers often probe whether a candidate understands the difference between results-based and specification-based certificate profiles, and why using the wrong one is a compliance risk rather than a cosmetic issue. Be ready to explain how characteristic relevance is controlled at the master data level and how that interacts with profile selection logic.