Nothing Special   »   [go: up one dir, main page]

7 Sets of Consulting Notes For CO PA Analysts

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 1

7 Sets of Consulting Notes for CO-PA

Analysts
 by Mitresh Kundalia, Director — SAP Practice, Quality Systems & Software
 July 15, 2003

A common misunderstanding about OSS is that it provides information on bugs and fixes only.
However, OSS also provides advisory consulting notes that are based on past experience and
frequently asked questions. You can search for CO-PA consulting notes via transaction code OSS1
(Category Consulting). Here is a list of my favorite seven sets:
Free-of-Charge Deliveries. One of the most common business requirements is handling free-of-
charge delivery costs. If no billing document is generated, costs are not transferred to costing-based
PA. Note 36129 describes how costs can be transferred to CO-PA with a statistical condition type in
the invoice document. Consulting note 33258 explains how to configure an invoice with a 100 percent
discount. Note 33382 describes free-of-charge items for inter-company billing.
Characteristics from SD transaction tables to CO-PA. Another common requirement is to transfer
Sales and Distribution (SD) characteristics from transaction tables (VBKD, VBAK, or VBAP), rather
than master tables (KNVV). Note 33968 explains how to do this.
SD Partner functions in CO-PA. Certain standard SD partner functions such as sold-to, ship-to,
payer, and sales employee are available in CO-PA as pre-defined characteristics. Refer to note 36557
to transfer additional SD partner functions to CO-PA.
Product Hierarchies. The product hierarchy field is typically made up of three parts. If you have only
one characteristic in PA to store the product hierarchy, you are not able to drill down through all the
levels in CO-PA reports. To do this, you need three separate characteristics in CO-PA. Note 62690
helps you define characteristics. As of Release 4.5, an integrated option is available.
Signs and Conditions. Revenues in different applications are stored with different (+)/(-) signs. In the
FI module, debits have a positive sign and credits have a negative sign. However, direct credit
revenue postings from FI to CO-PA have positive signs. To avoid this confusion, in CO-PA amounts
are typically stored as positive. Notes 52849 and 33178 explain the sign logic of value fields and how
the Transfer with (+)/(-) indicator in transaction code KE4I can cause unexpected results in CO-PA.
SD Condition Types to Value Fields. Condition type is the link between the SD module and CO-PA.
Condition types from SD are mapped to value fields in CO-PA. Sometimes you don’t know which SD
condition types are transferred. Note 20254 describes this.
Valuation with Condition Technique in CO-PA. Valuation in CO-PA is used for calculating additional
values in the PA ledger. Basically, there are three valuation techniques: product costing information,
costing sheets, and user exits. Note 62536 explains condition technique using costing sheets.

You might also like