Important CO tables

CO

TKA01 Controlling areas

TKA02 Controlling area assignment
KEKO Product-costing header
KEPH Cost components for cost of goods manuf.
KALO Costing objects
KANZ Sales order items - costing objects

Cost center master data

CSKS Cost Center Master Data
CSKT Cost center texts
CRCO Assignment of Work Center to Cost Center

Cost center accounting

COSP CO Object: Cost Totals for External Postings
COEP CO Object: Line Items (by Period)
COBK CO Object: Document header
COST CO Object: Price Totals

COBK is the header for CO docs

COEP is the line-item for CO docs
BKPF is the header for FI docs
BSEG is the line-item for CO docs.

In most cases when an FI doc. is created there is an associated CO document (I say most,
because if you have an FI doc with balance sheet accounts only, there will be no CO document).

Some FI/CO data are the same (e.g. vendors, customers are in the same fields, the FI G/L
account corresponds to CO cost element, etc.). So for reporting purposes you can take the data
from either FI or CO.

Note however that there may be CO docs without FI docs. For instance with Requisitions or
P.O.'s. There the correspondence is EKKO (PO header), EKPO (PO line item) & EKKN (PO
acct.assignment) and COBK (CO header) COEP (CO line item) for CO and EBAN (Req line item
- there is no Req header) and EBKN (Req acct assignment).

I've since learned that P.O.'s & Reqs are not in COBK. At this point I think that the only CO
documents that are not in FI are the "Cost in Excess of Award Total" documents. These are the
documents produced by ZPSR002C via KB11, mentioned below.

A fast access to COEP is via the view COVP.

COSP is summarized primary cost table

COSS is summarized secondary cost table
Questions to follow up on:

Are purchase requisitions in COEP? If so, what happens with COBK since there is no header for
purchase requisition? (Some fields from P.Req. that behave like "header fields" such as p.req.
date, user id would go to COBK and not to COEP. In COBK there is a field called 'Transaction
type' (cobk-vrgng) that identifies whether a document came from a P.Req., P.O. or FI. The
transaction types are 4 letter codes and a little vague on what they mean, but that is the answer.
For instance for FI->CO transfer, transaction type is COIN. KB11, transfer cost overruns - see
ZPSR002C, produces transaction code RKU1 (Repost costs)). I tried finding POs or Reqs or
even invoices in COBK and could not. Perhaps the document numbers used are not the FI or MM
document numbers. This is true because in COEP, BELNR & BUZEI uniquely identify a line item
within a controlling area and there is a separate entry in COEP for each account assignment
(EKKN - account assignment in purchasing document). I finally checked out COOI (open item
management ), which looks like it reflects the open items in COEP. From there I discovered that
RMBA refers to requisitions and RMBE refers to purchase orders. At the COEP (and COOI) level
there is another helpful column, COEP-WRTTP ("Value Type"). 21 indicates a requisition and 22
a purchase order. But I still can not find a single RMBA in COBK. When I check the document
range I do not find a range assign to RMBA. So...I'm confused. I checked COBK for other
transaction types successfully. Therefore I'm really led to believe that POs are not configured to
be in COBK here at M.I.T.
How are P.O.s distinguished from paid invoices in COBK & COEP? via these transaction codes,
see table TJ01.