Create Great Custom Report Design Specs for Your ABAP Team Using Table COEP

  • by Bill McNaughten , Senior Consultant, Cap Gemini Ernst & Young
  • November 15, 2002
Sometimes the only way to meet a CO reporting requirement is to have your ABAP team generate a custom program. The integrity and performance of that program depends on the quality of the instructions you give the team. Table COEP plays an important role here, because its indexes will help ensure good report response time and it contains the data that the report will need. The author shows you how to confirm that the data you expect to be in that table really exists.
Key Concept

Invariably, users will need reporting functionality that a standard CO report doesn’t provide or that is not possible using R/3 reporting tools such as Report Writer and Report Painter. Your only option might be custom ABAP development. Once you are convinced that this is your only option for creating a CO report, then you will probably have to create design specifications for an ABAP programmer.

The quality of the ABAP program you get back depends on those design specifications. A mistake in the specs might mean poor performance or the reports not running at all. You can provide good program specifications for ABAP development if you focus on two key areas: ensuring good response speed and the manual validation of data. In both cases, you need to know where and how the data needed for the reports is stored, and this is what I will show you in this article.

Understanding the data contained in the table COEP is helpful for both reducing response time and manually validating data. You typically use this table when customized reports require dollars and quantities for CO objects. Transactions contained within the table include cost center assessments and distributions; activity confirmations; settlement; issues; receipts; and settlement for discrete, repetitive processes and make-to-order production orders. COEP also contains similar transactions for plant maintenance, project systems, and so on.

The rows populated and the data contained in the COEP fields will vary depending on your system’s configuration and modules implemented.

Using Indexes Boosts Performance

Performance is a critical issue when dealing with any large SAP table. For example, the COEP table in just a mid-sized company can easily contain 60 million records or more. The most important step in ensuring good response time for a custom CO report is the use of one of the COEP indexes when accessing table records. The larger the table the more critical this step becomes. Typically, the fastest COEP indexes use the controlling area (KOKRS) and document number (BELNR) fields, or ledger (LEDNR) and (OBJNR) object number fields. Using indexes allows the specified data to be accessed directly without sequentially reading through the file to find each record.

Bill McNaughten

Bill McNaughten is a senior applications consultant for Cap Gemini Ernst & Young who specializes in the implementation and support of the SAP R/3 CO module. His SAP career began in 1996 with Anheuser Busch. After completing a successful implementation, Bill spent several years as an independent consultant before joining CGEY. In his seven years of experience, he has specialized in implementing product costing systems in manufacturing environments. Bill's hobbies include playing the guitar and listening to all styles of music.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.