Cemi Concept Ii Manual

Getting Started with Cemi Concept II

The Cemi Concept II is a PLM and MES integration layer originally developed by SAP for the pharmaceutical and biotech industries. It connects ERP systems to manufacturing execution systems using the CEMIPAC standard. If you are running this in a production environment, you already know the documentation can be sparse. The manual covers the basics, but it leaves out a lot of the stuff that actually breaks during implementation. The manual walks you through installation, configuration, and the key objects like the Business Object Model, Communication Objects, and the Interface Catalog. It is organized by functional area rather than by workflow, which means you will likely flip between chapters instead of reading straight through. Most people treat it as a reference rather than a tutorial. Here is what the core setup actually involves. You install the Cemi Concept II component, configure the communication layer to talk to your SAP R/3 or ECC system, define your Business Process Objects, and then map them to your MES using the provided interface catalog. The manual gives you the transaction codes, the relevant table names, and the standard field mappings. What it does not tell you is how many of those standard mappings fail in real installations.

One thing that catches people off guard is the versioning behavior. Cemi Concept II uses a version-based release model where each update can shift field positions in the interface catalog without a clear migration path. I spent about three days troubleshooting a data mapping failure that turned out to be caused by a minor version mismatch between the Concept II runtime and the MES adapter. The error messages pointed to missing fields, but the fields were there, just renumbered. The workaround was to lock both sides to the same patch level and verify the interface catalog build number before each deployment. Write that number down somewhere.

Configuration Steps That Actually Matter

The manual lists roughly thirty configuration steps, but most of them are optional or situational. The ones you cannot skip are the communication channel setup, the authorizations for the Cemi service user, and the Business Object Model activation. Everything else depends on your specific environment. When you configure the communication channel, use RFC connectivity unless you have a specific reason to use XI/PI. RFC is faster, easier to debug, and the Cemi runtime was designed around it. XI/PI adds a middleware layer that introduces its own failure modes on top of Cemi's already complex error handling. For authorizations, the manual gives you a standard role template. It is incomplete. You will need additional permissions for table access on CRMD_ORDER_H and APLZS in most setups. If you skip this, the system will throw authorization dumps during runtime that look like data errors. I learned this the hard way on a client site where the ABAP team refused to grant direct table access, and we spent two weeks chasing ghosts before someone suggested checking the trace logs.

Common Pitfalls Beginners Miss

The biggest mistake people make is assuming the standard interface catalog is production ready out of the box. It is not. The catalog contains hundreds of object definitions, most of which are generic templates. Several of them assume a specific MES architecture that does not match your environment. You need to audit the catalog against your actual process flows before you activate anything. Another issue is the handling of batch master data. Cemi Concept II expects batch characteristics to be fully populated before a manufacturing order is released. If your ERP allows partial batch creation, the integration will silently drop records. There is no error message. The order just never appears in your MES. I built a pre-validation check using a custom BAdI on the order save event that flags incomplete batches before they reach the Cemi queue. It added maybe twenty minutes of development time and saved weeks of downstream troubleshooting. The manual does mention batching and queue management briefly, but it does not cover what happens when your queue backs up. In practice, if you process more than five hundred orders per hour through a single Cemi connector, you will start seeing timeout errors. The recommended fix is to split your connectors by material group or plant and route them through separate communication channels. This is not in the manual. It is something you figure out after the first incident.

Where Cemi Concept II Falls Short

It is not a complete solution. Cemi Concept II handles the integration layer well, but it does not replace proper process validation. If your manufacturing workflows are not standardized in SAP before you integrate with Cemi, you will spend more time working around data inconsistencies than you would building a simpler point-to-point interface. The tool assumes a mature SAP PP/PM and QM setup. If you do not have that, you are going to have a rough time. Support is another concern. SAP still maintains Cemi Concept II, but the community around it is small. There are fewer active forums, fewer third-party resources, and the documentation has not been significantly updated in several years. If you hit a bug, you are largely on your own unless you have a good SAP partner who has worked with it before. For smaller implementations, a custom RFC-based integration between SAP and your MES using standard IDocs often takes less time to build and maintain. Cemi Concept II shines in regulated environments where you need the full audit trail, structured data modeling, and the CEMIPAC compliance layer. If you do not need those, you are adding complexity without a proportional benefit.

Where to Find the Manual

The official Cemi Concept Ii Manual is available through the SAP Support Portal under the Product and Version Matrix for CEMIPAC. You will need an S-user account with the appropriate role. The manual is typically packaged with the implementation guide and includes appendices with transaction codes, table structures, and sample interface definitions. Third-party vendors like Siemens and GE also publish their own adaptation guides for their MES products, which can fill gaps in the official documentation. If you are starting a new project, I would recommend downloading the manual, skimming the interface catalog chapter first, and then mapping your actual process requirements against it before you begin any configuration. It will save you a significant amount of time later.