COSS TCode in SAP : Transport of C Tables

There may be an error in the URL, or you may be trying to access a legacy page that is no longer supported. Please try searching for your content, or browse the links below.

"COSS ( CO Object: Cost Totals for Internal Postings )"

ACT_INPUT Leistungsart ...

"AUFK, AFPO, COSS, COSP, COSB, COSL, COKEY, TKA09, TKV09."

Since the archiving objects in Profitability Analysis depend on the operating concern (which is generated at customer) and on the Customizing settings under , the corresponding information structures and the field catalog must also be generated for the Archive Information System (AS).

"Totals record tables (tables concerned: COSS, COSP, COKA)"

The purpose of this section is to familiarize you with the technical processes in the Time Sheet. The graphic below shows which tables the system uses to process the recorded time sheet data.

"COSS ( CO Object: Cost Totals for Internal Postings )"

Within Overhead Cost Controlling you need to run certain reconciliation programs , which ensure that reconciled data is available both before and after the Euro changeover. You need to run these programs in different phases.

"To reconcile the balance, the system needs to determine which objects had a balance of zero before the changeover. To do this, start the RKASAL01 program in the FILL phase. For each object that has already been settled at least once, this program determines the balance of every individual posting period, using the COSP and COSS tables. These values are then saved in the EWUCOSUM table. The system does not change the EWUCOSM table during the subsequent changeover."

0PIOVALUE and 0PIOBJSV are determined from the partner object field of the COSS records for the following partner object types:

InfoObject Description Data Element ...

"In the OLTP system, DataSources are created so that delta datasets can be recorded. These DataSources select data from the line item table COEP. This enables additional fields (not contained in the COSP and COSS totals tables) to be transferred to the BW."

Thank you. Please enter any additional feedback you would like to leave, then press submit.

This DataSource supplies costs (primary and secondary) and quantities posted to cost centers (actual, plan, and commitments). These costs could have been posted to the cost centers as primary cost postings or internal allocations.

This DataSource is especially suitable for marginal costing. The costs are supplied after splitting has been carried out. Through splitting the activity-independent cost portions become activity dependent. In the actual, the system splits the actual costs corresponding to the target costs. If no target costs exist, the actual costs are allocated according to splitting rules or equivalence numbers, just as the plan costs are. It is best to divide the costs into fixed and variable on the allocation receiver side only after splitting has taken place.