Cost Accounting Documents (CO) in the DRB
Use
The following object type is linked to the DRB and can therefore be displayed including any links:
Object Type with related Field Catalog and Archive Information Structure
Object Type |
Archiving Objects |
Field Catalog |
Information Structure |
Cost Accounting Document |
CO_ALLO_ST |
SAP_COBK_ALLO01 |
SAP_COBK_ALLO01 |
CO_CCTR_EP |
SAP_COBK_CCEP01 |
SAP_COBK_CCEP01 |
|
CO_CCTR_ID |
SAP_COBK_CCID01 |
SAP_COBK_CCID01 |
|
CO_CCTR_PL |
SAP_COBK_CCPL01 |
SAP_COBK_CCPL01 |
|
CO_COSTCTR |
SAP_COBK_CCTR01 |
SAP_COBK_CCTR01 |
|
CO_ITEM |
SAP_COBK_ITEM01 |
SAP_COBK_ITEM01 |
|
CO_KSTRG |
SAP_COBK_KSTR01 |
SAP_COBK_KSTR01 |
|
CO_ORDER |
SAP_COBK_COOR01 |
SAP_COBK_COOR01 |
|
CO_PROCESS |
SAP_COBK_PROC01 |
SAP_COBK_PROC01 |
|
PM_ORDER |
SAP_COBK_PMOR01 |
SAP_COBK_PMOR01 |
|
PP_ORDER |
SAP_COBK_PPOR01 |
SAP_COBK_PPOR01 |
|
PR_ORDER |
SAP_COBK_PRORD1 |
SAP_COBK_PRORD1 |
|
PS_PROJECT |
SAP_COBK_PROJ01 |
SAP_COBK_PROJ01 |
|
RE_BUILDNG |
SAP_COBK_REBG01 |
SAP_COBK_REBG01 |
|
RE_BUSN_EN |
SAP_COBK_REBE01 |
SAP_COBK_REBE01 |
|
RE_MGT_CNT |
SAP_COBK_REMC01 |
SAP_COBK_REMC01 |
|
RE_PROPRTY |
SAP_COBK_REPR01 |
SAP_COBK_REPR01 |
|
RE_RNTL_AG |
SAP_COBK_RERA01 |
SAP_COBK_RERA01 |
|
RE_RNTL_UN |
SAP_COBK_RERU01 |
SAP_COBK_RERU01 |
|
RE_STLM_UN |
SAP_COBK_RESU01 |
SAP_COBK_RESU01 |
|
SD_VBAK |
SAP_COBK_VBAK01 |
SAP_COBK_VBAK01 |
|
COPA2_nnnn* |
SAP_COBK_Pannnn* |
SAP_COBK_Pannnn* |
* where nnnn stands for the operating concern. The archiving object is generated per operating concern.
Prerequisites
To optimize the DRB functions for archived cost accounting documents, you are recommended to proceed as follows:
Integration
Handling archived cost accounting documents in the DRB is more involved than accounting documents, for example. The reason for this is the way the document lines are distributed across the archive. Cost accounting documents can be archived using differing archiving objects (such as CO_ITEM, PP_ORDER, CO_COSTCTR, SD_VBAK, ...). An additional complication is that the cost accounting documents are not archived by document number.
For a posting involving a production order and a cost center, you may find that one part of the document is in a PP_ORDER archive, whilst the other part is still in the database.
Consequently it is not possible to determine with certainty which archive a cost accounting document is stored in, nor whether it is in the database or in the archive. You can only determine this for individual document lines (line items).
As the Archive Information System (AS) field catalog depends on the archiving object, several field catalogs (and therefore information structures) may be needed. To access the cost accounting document, field catalogs have been delivered that begin with SAP_COBK_.
Due to the way cost accounting documents are archived, the number of entries in the required information structures roughly equals the number of document lines. Only the number of document lines that are found in those archives for which the corresponding information structure was created are relevant.
You should therefore decide carefully whether you want to view archived cost accounting documents. In addition, you should only include fields REFBT, AWTYP and AWORG in the information structures if you experience runtime problems.
With cost accounting documents (as for other documents too) only the respective source document and other accounting documents are linked. The objects on which the costs are collected are not regarded as being linked to the cost accounting document. If this were not the case, you could find that the number of documents linked to an object would be so huge that it would overwhelm the capacity of the DRB.
You make an FI posting involving a sales order and a cost center. This also leads to the creation of an accounting document and a cost accounting document. In this case the accounting document is the source document. The accounting document is then linked to the cost accounting document. However, there is no link (in the DRB sense) to either the sales order or the cost center.