sap sd and co-pa
DESCRIPTION
This document provides an insight into the SD-COPA relationship.A must for SAP functional consultants...TRANSCRIPT
SAP AG 1999 filename (author) / 1
Processes in Detail
SD CO-PA Workshop
SAP AG 1999 filename (author) / 2
Processes in Sales and Distribution
MMAATTEERRIIAALLSS
MMAANNAANNGGEEMMEENNTT
MMAATTEERRIIAALLSS
MMAANNAANNGGEEMMEENNTT
SalesSalesInformationInformation
SystemSystem
SalesSalesInformationInformation
SystemSystem
USD
SalesSalesSupportSupport
SalesSales
ShippingShipping
BillingBilling
Financial AccountingFinancial AccountingFinancial AccountingFinancial Accounting
Delivery
Debit memo Credit memoInvoice
Free-of-chargedelivery Order
Contract
Schedulingagreement
Sales activity
Inquiry
Quotation
Transport
ReturnsFree-of-charge
subsequentdelivery
SAP AG 1999 filename (author) / 3
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 4
1
1
SalesOrder
SDSD
Quantity FlowLogistic Documents
3
BillingDocument
Sales from Stock: Business Background
Process Partners
t
Customer
1
2
Delivery
SAP AG 1999 filename (author) / 5
Sales Order Entry
Sales document items (contract or sales orders), including an item category which is relevant for billing, are transferred to CO-PA with record type A
Sales Order
Goods Issue
Billing Document
SDSD
Incoming Sales Orders
Ordered qty 100 unitsRevenue 9,000.00COGS 6,000.00
Sales orders transferred withrecord type A
CO-CO-PAPA
SAP AG 1999 filename (author) / 6
Transfer of Incoming Sales Orders
Data entry
Sales orders transferred can be recorded under:
The period in which the order was created
The period of the planned delivery / billing
Subsequent posting of sales orders
Prepare: Determine profitability segment for order
Post: Subsequent transfer of sales order
SalesSalesorderorder
Assignment to period
Rel. 4.0A
SAP AG 1999 filename (author) / 7
1
1
SalesOrder
SDSD
3
BillingDocument1
2
Delivery
Quantity FlowLogistic Documents
t
CO-CO-PAPA
FIFI
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
X
X
XRevenue
Customer
Rebates
X
COGS
XInventory
Sales from Stock: Postings
Valuation at Good Issue
date
CO-CO-PCPC
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
SAP AG 1999 filename (author) / 8
1
1
SalesOrder
SDSD
3
BillingDocument1
2
Delivery
Quantity FlowLogistic Documents
t
CO-CO-PAPA
FIFI
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
X
X
XRevenue
Customer
Rebates
X
COGS
XInventory
Sales from Stock: Postings
ConditionTypeVPRS
SDSD
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
SAP AG 1999 filename (author) / 9
1
1
SalesOrder
SDSD
3
BillingDocument1
2
Delivery
Quantity FlowLogistic Documents
t
CO-CO-PAPA
FIFI
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
X
X
XRevenue
Customer
Rebates
X
GI / II Acc.
XInventory
Sales from Stock using Goods Issue / Invoice Issue Account
XGI / II Acc.
X COGS
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
SAP AG 1999 filename (author) / 10
Incoming Payment Cash Discount
The accrued discount is transferred to costing-based CO-PA at the point of time when the billing document is released to accounting.
The cash discount is calculated during the run of the payment program in FI.
Use automatic account assignment to account actual cash discount at a higher level into CO-PA
Start the Program “Profit and Loss Readjustment” (SAPF181) in your period closing activities.
Actual cash discount will now be assigned to customer level, in order to trace your true customer profitability
SAP AG 1999 filename (author) / 11
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 12
SDSD
Quantity FlowLogistic Documents
BillingDocument
Credit Notes: Business Background
Process Partners
t
Customer
Delivery
1SalesOrder 1
CreditMemo
Request
CreditMemo
G2
SAP AG 1999 filename (author) / 13 t
CO-CO-PAPA
FIFI
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
X
XRevenue
Customer
Sales from Stock: Quantity-Dependent Credit Memo
SDSD
Quantity FlowLogistic Documents
1
CreditMemo
Request
CreditMemo
Sold qty -
Revenue -
Rebates -
COGS -
var.PC -
fi xed PC - Valuation
G2
BillingDocument
Delivery
1SalesOrder
SAP AG 1999 filename (author) / 14
Examples
Error in Pricing Procedure in SD
Goods are scrapped at customer
High tec ( Disks)
Food (Expiration date is over)
SAP AG 1999 filename (author) / 15 t
CO-CO-PAPA
FIFI
FI Postings /(CO-PA account-based)
CO-PA Postings(costing-based)
X
XRevenue
Customer
Sales from Stock: Value Credit Note
SDSD
Quantity FlowLogistic Documents
BillingDocument
Delivery
1SalesOrder 1
CreditMemo
Request
CreditMemo
Revenue -
No quantity No valuation
G2
SAP AG 1999 filename (author) / 16
Notes and Problems relating to Credits
To deactivate the quantity, define the field item type in the item category. The field item type indicates whether
a standard item (quantity and values) or
only a value item
is billed.
Make sure that in the case of value items, only those value fields are filled that are related to this credit memo.Function: Reset Value Fields in Customizing CO-PA
Accordingly, reset the value field for cost of goods sold
Reset other valuated value fields
SAP AG 1999 filename (author) / 17
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 18
Quantity FlowLogistic Documents
Free Delivery (Subsequent Delivery): Business Background
Process Partners
t
Customer
Customer complaint
SDSD SalesOrder 1
Delivery Billing
BillingDocument
Delivery
SalesOrder
CD
SAP AG 1999 filename (author) / 19
Scenarios: Free Deliveries
Customer order > Delivery > Billing without revenues and no posting to FI
OR
Customer order > Delivery > Billing including revenues and100 % rebate
Free deliveries / delivery of samples
Delivery of marketing brochure posted to cost centers
Replacement of broken products (guarantee, good will)
Free extras (see under free goods)
Basic Process
Variations
SAP AG 1999 filename (author) / 20 t
CO-CO-PAPA
FIFI
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
X
XCOGS
Inventory
Quantity FlowLogistic Documents
Sold qty +
COGS +
var.PC +
fi xed PC + Valuation
Free Delivery: Postings - Scenario 1
SDSD 1
SalesOrder 1
Delivery Billing
KL
SAP AG 1999 filename (author) / 21 t
CO-CO-PAPA
FIFI
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
X
XCOGS
Inventory
Quantity FlowLogistic Documents
Valuation
Free Delivery: Postings - Scenario 2
SDSD 1SalesOrder 1
Delivery Billing
YRevenue
Sold qty +
Revenue +
Rebates -
COGS +
var.PC +
fi xed PC +
YRebates
KL
SAP AG 1999 filename (author) / 22
Notes on Customizing
Although there is no posting in FI, free deliveries have to be invoiced .
Ensure that item category KLN is relevant for billing (indicator A): Statistic value “ ” Determine cost “x” Price determination “ ”
Net value is 0 and has to be allowed in the complete protocol
Ensure that calculated value fields (such as sales commission) are reset in CO-PA Customizing. This is only possible dependant on the Billing Type. For this reason, the following Customizing is needed:
Order type KL -> determines Billing type
Change Copy Control (transaction VTFA) ....
Dependent on the order reason, you might want to analyze the different reasons for complaint in CO-PA.
To do this, add the order reason as a characteristic in CO-PA and use it as a segment-level characteristic.
You may also wish to assign these values to different value fields (guarantee and good will) using the user-exit.
SAP AG 1999 filename (author) / 23 t
CO-CO-PAPA
FIFI
CO-PA Postings(costing-based)
X
XCOGS
Inventory
Quantity FlowLogistic Documents
Free Delivery: Postings - with Order Reason
SDSD 1SalesOrder 1
Delivery Billing
Marketing
KL
CO-CO-CCACCA Cost-Center COGS
SAP AG 1999 filename (author) / 24
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 25
Returns: Business Background
Process Partners
t
Customer
Customer complaint
SDSD
Deliveryto
restrictedstock
Billing
BillingDocument
Delivery
1
SalesOrder
1
CreditMemo
Request
RE
MMMM
Transferto
unrestrictedstock
Quantity FlowLogistic Documents Scrap
SAP AG 1999 filename (author) / 26
Scenarios: Returns
Blocked stock returns
Valuated stock returns
Basic Process
Follow-on Functions
Customer receives a credit (parts not required)
Customer received a replacement part (parts were broken)(see also free delivery)
SAP AG 1999 filename (author) / 27
Return into Restricted Stock: Postings
t
SDSD
Deliveryto
restrictedstock
Billing
BillingDocument
Delivery
1SalesOrder
1
CreditMemo
Request
RE
MMMM
Scrap
Transferto
normalstock
Quantity FlowLogistic Documents
CO-CO-PAPA
FIFI
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
No posting
Sold qty -
Revenue -
Rebates -
COGS -
var.PC -
fi xed PC -
Movement651
X
XRevenue
Acct Receiv.
Movement453
X
XInventory
COGS
For update ofaccount-based
CO-PACheck note 75653
SAP AG 1999 filename (author) / 28
Return to Unrestricted Stock: Postings
t
SDSD
Deliveryto un-
restrictedStock
Billing
BillingDocument
Delivery
1
SalesOrder
1
CreditMemo
Request
RE
MMMM
Quantity FlowLogistic Documents
CO-CO-PAPA
FIFI
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Sold qty -
Revenue -
Rebates -
COGS -
var.PC -
fi xed PC -
Movement653
X
XRevenue
Acct Receiv.X
XInventory
COGS
SAP AG 1999 filename (author) / 29
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 30
Process in General / Document Flow with Rebates
t
BillingDocument
BillingDocument
BillingDocument
Rebate credit memo
Rebateagreement
1 5SalesOrder
SalesOrder
SalesOrder
2GoodsIssue
GoodsIssue
GoodsIssue
43
Process Partners
Customer Plant
MMMM
Quantity FlowLogistic Documents
SDSD
SAP AG 1999 filename (author) / 31
Value Flows with Rebates
t
CO-CO-PAPA
FIFI XX
XRevenue
Customer
SDSD
Quantity FlowLogistic Documents
MMMM
COGS
XInventory X
Accr.Reb.
XReserves
BillingDocument
BillingDocument
BillingDocument
Rebatecredit memo
Rebateagreement
1 5SalesOrder
SalesOrder
SalesOrder
2GoodsIssue
GoodsIssue
GoodsIssue
43
Accr.Reb.
Reserves
Act. Rebate
X
X
Y CustomerY
CO-PA Postings(costing-based)
FI Postings / (CO-PA account-based)
Sold qty +
Revenue +
Accr. Rebts. -
COGS +
var.PC +
fi xed PC +
Accr. Rebts. +
Act. Rebates -
Copy +/- sign
One Value-field
SAP AG 1999 filename (author) / 32
Processing Rebates
Credit memorequest
120Billing doc. 2
3000
Billing doc. 3
6000
Billing doc. 1
3000
Startsettlement run
Rebate agreement
Customer 1from 10000 1- %
Accumulated sales vol.12000
SAP AG 1999 filename (author) / 33
Prerequisites for Rebate Processing
Sales organizationSales organization
PayerPayer
Billing typeBilling type
Rebate active
SAP AG 1999 filename (author) / 34
Creating Rebate Agreements (1)
Rebate agreement type: 0001 material/group rebateRebate agreement type: 0001 material/group rebate
Rebate recipient: C1Valid from: 01 Jan 1998Valid to: 31 Dec 1998Status: open
Rebate recipient: C1Valid from: 01 Jan 1998Valid to: 31 Dec 1998Status: open
SAP AG 1999 filename (author) / 35
Creating Rebate Agreements (2)
Condition record BO01 group rebateCondition record BO01 group rebate
Cust. C1 Validity period: 01 Jan 1998 to 31 Dec 1998
MaterialM1 Amount: from 1000 USD 2- %
5000 USD 4- %Accrual: 3- %
Cust. C1 Validity period: 01 Jan 1998 to 31 Dec 1998
MaterialM1 Amount: from 1000 USD 2- %
5000 USD 4- %Accrual: 3- %
Rebate agreement type: 0001 material/group rebateRebate agreement type: 0001 material/group rebate
Rebate recipient: C1Valid from: 01 Jan 1998Valid to: 31 Dec 1998Status: open
Rebate recipient: C1Valid from: 01 Jan 1998Valid to: 31 Dec 1998Status: open
SAP AG 1999 filename (author) / 36
Rebate Processing (1)
Billing documentBilling document
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USD
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USD
SAP AG 1999 filename (author) / 37
Rebate Processing (2)
Pricing procedurePricing procedure...400 Rebate basis...901 BO01 Material/Group rebate902 BO02 Material rebate...
...400 Rebate basis...901 BO01 Material/Group rebate902 BO02 Material rebate...
Billing documentBilling document
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USD
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USD
SAP AG 1999 filename (author) / 38
Rebate Processing (3)
Pricing procedurePricing procedure...400 Rebate basis...901 BO01 Material/Group rebate902 BO02 Material rebate...
...400 Rebate basis...901 BO01 Material/Group rebate902 BO02 Material rebate...
Condition type: BO01Condition type: BO01
Access sequence: BO01Access sequence: BO01
Billing documentBilling document
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USD
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USD
SAP AG 1999 filename (author) / 39
Rebate Processing (4)
Accrual3- %
Pricing procedurePricing procedure...400 Rebate basis...901 BO01 Material/Group rebate902 BO02 Material rebate...
...400 Rebate basis...901 BO01 Material/Group rebate902 BO02 Material rebate...
Condition type: BO01Condition type: BO01
Access sequence: BO01Access sequence: BO01
Access sequence: BO01Access sequence: BO01
1. Customer / Material2. Customer / Rebate group1. Customer / Material2. Customer / Rebate group
Records for condition type BO01Records for condition type BO01
Valid record existsValid record exists
SAP AG 1999 filename (author) / 40
Rebate Processing (5)
Billing documentBilling document
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USDBO01 3- % 30- USD
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USDBO01 3- % 30- USD
Accrual 3- %Accrual 3- %
SAP AG 1999 filename (author) / 41
Sales volume in rebate agreementSales volume in rebate agreement
BO01:Rebate basis 1000 USDAccrual 30- USD
BO01:Rebate basis 1000 USDAccrual 30- USD
Accounting documentAccounting document
Accrual rebate 30 USDAccrual rebate 30 USDReserves 30- USDReserves 30- USDAccrual rebate 30 USDAccrual rebate 30 USDReserves 30- USDReserves 30- USD
Rebate Processing (6)
Billing documentBilling document
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USDBO01 3- % 30- USD
Item 10 M1 10 pc
Price 1100 USDDiscount 100- USDRebate basis 1000 USDBO01 3- % 30- USD
Accrual 3- %Accrual 3- %
SAP AG 1999 filename (author) / 42
Creating Rebate Settlements (1)
Sales volume in the rebate agreementSales volume in the rebate agreement
BO01:Payment Amount Basis Accrual20 USD 2% 1000 USD 30- USD
BO01:Payment Amount Basis Accrual20 USD 2% 1000 USD 30- USD
Status
AAAAor blank
SAP AG 1999 filename (author) / 43
Creating Rebate Settlements (2)
Rebate credit memo requestRebate credit memo request
Item 10: BO01 2% 20 USDBO01 Accrual 30- USD
Item 10: BO01 2% 20 USDBO01 Accrual 30- USD
Sales volume in the rebate agreementSales volume in the rebate agreement
Create settlement
Status
AAAA
CCCC
BBBB
or blankBO01:Payment Amount Basis Accrual20 USD 2% 1000 USD 30- USD
BO01:Payment Amount Basis Accrual20 USD 2% 1000 USD 30- USD
SAP AG 1999 filename (author) / 44
Creating Rebate Settlements (3)
AccountingAccounting
Rebate credit memoRebate credit memo
Rebate credit memo requestRebate credit memo request
Sales volume in the rebate agreementSales volume in the rebate agreement
Create settlement
Status
AAAA
CCCC
BBBB
DDDD
or blankBO01:Payment Amount Basis Accrual20 USD 2% 1000 USD 30- USD
BO01:Payment Amount Basis Accrual20 USD 2% 1000 USD 30- USD
Item 10: BO01 2% 20 USDBO01 Accrual 30- USD
Item 10: BO01 2% 20 USDBO01 Accrual 30- USD
Item 10: BO01 2% 20 USDBO01 Accrual 30- USD
Item 10: BO01 2% 20 USDBO01 Accrual 30- USD
SAP AG 1999 filename (author) / 45
Rebates: Update CO-PA
SD condition types (such as BO..) are relevant for accruals
Two accounts are assigned to the same condition type (accounts: accrued Bonus and actual Bonus)
Transfer to CO-PA
Create cost element (cost element type “12”) for rebate accounts
A reserve account is a balance sheet account (no cost element)
Set the flag “Transfer with +/- sign” for the related condition types
During billing, the rebate is updated in CO-PA
During rebate settlement, the accruals are reversed in FI and account-based CO-PA. In costing-based CO-PA, the difference of the reversed and the granted rebate is posted.
See note 37114
SAP AG 1999 filename (author) / 46
Retroactive Rebate Agreements (1)
Billing document from 01 Oct 1997Billing document from 01 Oct 1997
Rebate basis 1000 USDRebate basis 1000 USD
Billing document from 02 Nov 1997Billing document from 02 Nov 1997
Rebate basis 1000 USDRebate basis 1000 USD
SAP AG 1999 filename (author) / 47
Retroactive Rebate Agreements (2)
Rebate agreement 0001 created on 12 Dec 1997 Rebate agreement 0001 created on 12 Dec 1997
Rebate recipient C1 Subsequent creation X Valid from 01 Sep 1997to 31 Aug 1998
Rebate basis 2000 USDAccrual 0 USD
Rebate recipient C1 Subsequent creation X Valid from 01 Sep 1997to 31 Aug 1998
Rebate basis 2000 USDAccrual 0 USD
Billing document from 01 Oct 1997Billing document from 01 Oct 1997
Rebate basis 1000 USDRebate basis 1000 USD
Billing document from 02 Nov 1997Billing document from 02 Nov 1997
Rebate basis 1000 USDRebate basis 1000 USD
SAP AG 1999 filename (author) / 48
Retroactive Rebate Agreements (3)
Billing document from 05 Jan 1998Billing document from 05 Jan 1998
Rebate basis 1000 USDRebate BO01 10- USDRebate basis 1000 USDRebate BO01 10- USD
Rebate agreement 0001 created on 12 Dec 1997 Rebate agreement 0001 created on 12 Dec 1997
Rebate recipient C1 Subsequent creation X Valid from 01 Sep 1997to 31 Aug 1998
Rebate basis 3000 USDAccrual 10- USD
Rebate recipient C1 Subsequent creation X Valid from 01 Sep 1997to 31 Aug 1998
Rebate basis 3000 USDAccrual 10- USD
Billing document from 01 Oct 1997Billing document from 01 Oct 1997
Rebate basis 1000 USDRebate basis 1000 USD
Billing document from 02 Nov 1997Billing document from 02 Nov 1997
Rebate basis 1000 USDRebate basis 1000 USD
SAP AG 1999 filename (author) / 49
01 Apr 199801 Apr 1998
01 Apr 1998 01 Apr 1998
01 Mar 199801 Mar 1998
01 Mar 1998 01 Mar 1998
Partial Rebate Settlement
Partial rebate settlementPartial rebate settlement
Partial rebate settlement request 01 Feb 1998Partial rebate settlement request 01 Feb 1998
Item 10: BO01 30.00 USDBO01 Accrual 25.00- USD
Item 10: BO01 30.00 USDBO01 Accrual 25.00- USD
Sales volume in the rebate agreement 01 Feb 1998Sales volume in the rebate agreement 01 Feb 1998
BO01:Payment AmountBasisAccrual30 USD 1%3000 USD- 25 USD
BO01:Payment AmountBasisAccrual30 USD 1%3000 USD- 25 USD
Partial settlement
Item 10: BO01 30.00 USDBO01 Accrual 25.00- USD
Item 10: BO01 30.00 USDBO01 Accrual 25.00- USD
SAP AG 1999 filename (author) / 50
Settlement Material (1)
Condition record BO03 Customer rebateCondition record BO03 Customer rebate
CustomerC1 Amount: from 1000 USD 2- %
5000 USD 4- %Accrual: 3- %
Settlement material: Rebate material 01
CustomerC1 Amount: from 1000 USD 2- %
5000 USD 4- %Accrual: 3- %
Settlement material: Rebate material 01
Rebatematerial 01
SAP AG 1999 filename (author) / 51
Settlement Material (2)
Rebate credit memo requestRebate credit memo request
Item Net value10 Rebate material 01 240 USDItem Net value10 Rebate material 01 240 USD
Settlement
...
Rebatematerial 01
Condition record BO03 Customer rebateCondition record BO03 Customer rebate
CustomerC1 Amount: from 1000 USD 2- %
5000 USD 4- %Accrual: 3- %
Settlement material: Rebate material 01
CustomerC1 Amount: from 1000 USD 2- %
5000 USD 4- %Accrual: 3- %
Settlement material: Rebate material 01
SAP AG 1999 filename (author) / 52
Rebate Agreement Types
The following rebate agreement types have been defined in the SAP R/3 standard version. Related condition types are listed as well.
Rebate agreement type Condition table Condition type Rebate agreement type Condition table Condition type
0001 Customer / Material BO01(percentage rebate)
Customer / Rebate group BO01(percentage rebate)
0002 Customer / Material BO02(absolute rebate)
0003 Customer BO03(percentage rebate)
0004 Customer hierarchy BO04(percentage rebate)
Customer hierarchy / Material BO05(percentage rebate)
0005 Independent of sales volume BO06
SAP AG 1999 filename (author) / 53
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 54
Intercompany Process: Organizational Units
CustomerCustomerCustomerCustomer
Salesorganization 2
Salesorganization 1 Sales organization 3
Plant 1 Plant 2 Plant 3 Plant 5 Plant 4
Selling CompanyDelivering Company
SAP AG 1999 filename (author) / 55
1
1
SalesOrder
SDSD
Quantity FlowLogistic Documents
MMMM2
Delivery
3
BillingDocument
Process Partners
t
Customer
Intercompany Sales: Business Background
DeliveringCompany
4Inter-companyBilling
Selling Company
5InvoiceReceipt
SAP AG 1999 filename (author) / 56
1
1
SalesOrder
SDSD
Quantity FlowLogistic Documents
MMMM2
Delivery
3
BillingDocument
t
Intercompany Sales: Make-to-Stock
4Inter-companyBilling
5InvoiceReceipt
CO-CO-PAPA
FIFI
X
X
Revenue
COGS
XInventory
X FI Postings / (CO-PA acct-based)
CO-PA Postings(costing-based)
Sold qty +
Revenue +
Rebates +
COGS +
Var.PC +
fi xed PC +
ConditionPI01/02
Selling Company
IntercoRev
Sell.CompanyX
X
Customer
RebatesX
XCOGS
Del.Company
X
Delivering Company
Sold qty +
I ntercoRev +
COGS +
var.PC +
fi xed PC +
ConditionVPRS
ConditionZI01/02
int.ext.
SAP AG 1999 filename (author) / 57
Company Code 0001
Sales order
External billing document (F2) PR00 PI0n ( n = 1,2 ) statistical
Company code 0002
DeliveryGoods issue
Internal billing document (IV) ZI0n ( n = 1,2 ) active VPRS
CO-PAline-item
“F”
CO-PAline-item
“F”
CO-PAline-item
“A”
Companycode!
See OSS notes 68195 and 121859
The delivering company code is taken as thebasis for determining the profitabilitysegment number on the sales order! However, the line item for the sales orderentry is posted for the selling company code!
Sales Order Entry
SAP AG 1999 filename (author) / 58
Customizing Intercompany Business: SD View
Which billing type is used for intercompany business?
Which sales organizations are involved in intercompany sales?
Which customer is used for intercompany billing?
SAP AG 1999 filename (author) / 59
Reporting Group Results
Use a characteristic (such as an intercompanyflag) to classify your customers as companies within the same corporate group, thereby distinguishing them from group-external companies.
Valuate your sales in parallel value fields with legal costs and group costs of goods manufactured.
Organize your reports as follows:
Legal reports to show the legal costs of goods manufactured
Group reports to show the group costs of goods manufactured
SAP AG 1999 filename (author) / 60
Notes on Customizing Intercompany Business
The material to be delivered needs to have been created in both plants and sales organizations
The intercompany customer must exist for the sales organization relating to the delivering plant
The sales organization relating to the company code making the sale must be assigned to the delivering plant (-> delivering company code)
SAP AG 1999 filename (author) / 61
Customizing Price Determination for Make-to-Stock
Using Two Condition Types(by creating a second condition type with a reference to PI01/PI02)
SAP AG 1999 filename (author) / 62
Creation of a second costing sheet with condition types VPRS and the “new” condition type
Integration of the costing sheet by:
Define the document pricing procedure
Assign this procedure to billing type IV
Activate the second costing sheet for the delivering sales organization
Assignment of the condition types in CO-PA to the corresponding value fields (internal revenue / internal cost)
Customizing Price Determination for Make-to-Stock
SAP AG 1999 filename (author) / 63
How to report Intercompany-Business in CO-PA
CO-CO-PAPA
Transferred Billing-items into CO-PA
Cust. Prod. Interc., Region, Plant, Comp. Rev. Rev. COS, COS- Prod. Mat.- Indic. code ext. Intern., Intern., costs, costs
1000 P-200 int. N 2000 2000 500.- 80.- 60.- 20.-1171 P-200 ext. S 1000 1000 520.- 500.- 60.- 20.-
intern extern
Reven. (ext.) (int.)COS (ext.) (int.)
Act. Act.
Analyze Ccode: 1000 2000 Selling Prod.
520.- 500.- 80.-500.-
Revenue(int.+ext.)COSProd.costsMat.costs
Act.Cross-company
520.-
80.- 60.- 20.-
Selection
Intercomp.-Indicator: external
Ab
stim
mu
ng
mit F
I
Company ViewCorporate View
SAP AG 1999 filename (author) / 64
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 65
1
1
SalesOrder
SDSD
Quantity FlowLogistic Documents
MMMM 2PurchaseRequisition
3PurchaseOrder
4GoodsReceipt
5InvoiceReceipt
6
BillingDocument
Process Partners
t
Customer Vendor
Third-Party Business: Business Background
SAP AG 1999 filename (author) / 66
Third-Party Order Processing: Procedure
Create sales order with a third-party item
The system automatically generates the purchase requisition (PReq) and writes it back to the order when you save (Item -> Schedule Lines -> Procurement)
In purchasing, create a purchase order from the purchase requisition
Invoice receipt from the supplier in purchasing
Invoice receipt can occur before and after billing document issue
Create customer billing document
SAP AG 1999 filename (author) / 67
Scenarios
Cust. Order > Goods Rec. > Invoice Receipt > Customer Billing
Cust. Order > Goods Rec. > Customer Billing > Invoice Receipt
Cust. Order > Customer Billing > Invoice Receipt
Cust. Order > Invoice Receipt > Customer Billing
Basic Process
Variations
SAP AG 1999 filename (author) / 68
Pur. order
Billing doc.
Third-Party Order Processing: Procedure (Invoice Receipt before Billing)
Sales orderSales order
Invoice receiptInvoice receipt
PurchasingPurchasing
BillingBilling
Invoice
CO-PACO-PA
Delivery note
SAP AG 1999 filename (author) / 69
1
1
SalesOrder
SDSD
Quantity FlowLogistic Documents
MMMM 2PurchaseRequisition
3PurchaseOrder
4GoodsReceipt
5InvoiceReceipt
6
BillingDocument
t
Third-Party Business: Postings
CO-CO-PAPA
FIFI X
X
XRevenue
Customer
Rebates
X
COGS
XGR/IR
XGR/IR
X Supplier
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
ConditionVPRS
SAP AG 1999 filename (author) / 70
Pur. order
Billing doc.
Third-Party Order Processing: Procedure (Invoice Receipt after Billing)
Sales orderSales order
Pseudo ship-to partyPseudo ship-to party
PurchasingPurchasing
BillingBilling
Invoice
CO-PACO-PA
Delivery note
Invoice receiptInvoice receipt
SAP AG 1999 filename (author) / 71
1
1
SalesOrder
SDSD
Quantity FlowLogistic Documents
MMMM 2PurchaseRequisition
3
PurchaseOrder
6InvoiceReceipt
5
BillingDocument
t
CO-CO-PAPA
FIFI 1800 3000Revenue
Customer
Rebates
COGS
GR/IR
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Third-Party Business: Customer Billing before Invoice Receipt
4GoodsReceipt
PreliminaryCOGS / via VPRS
= 1800
180020
2980 100COGS
GR/IR1800
Supplier1900
Rel. 4.6
Sold qty +
Revenue +
Rebates +
COGS +
COGS +
Correctionsvia VPRS
100
SAP AG 1999 filename (author) / 72
Notes on Customizing
SD
Use the item category TAS that has been set as the default by the Item Category Group in the Material Master or manually entered in the sales document
Make the following entries:
Invoice receiptbefore customer billing
Customer billingbefore invoice receipt
Item category TAS
Relevance for billing = F
Relevance for billing = B
(order-related billing)
Copy control order-> billing
transaction VFTAQuantity = invoice quantity
Indicator FQuantity = delivered quantity
Indicator E
SAP AG 1999 filename (author) / 73
Notes on Customizing in Releases prior to Rel. 4.6
Problems when the invoice receipt comes after customer billing:
When the price between the purchase order and the invoice receipt changes, then costing-based CO-PA is not updated.Solution: Transfer the invoice receipt directly into CO-PA
See also note 35367
Account-based CO-PA is not updated because the PA object is not transferred to MM documents.Solution: See note 35367
Reversal of Third-Party Business
Resetting cost of goods sold when credit memos are posted
SAP AG 1999 filename (author) / 74
1
1
SalesOrder
SDSD
Quantity FlowLogistic Documents
MMMM 2PurchaseRequisition
3
PurchaseOrder
5
BillingDocument
t
CO-CO-PAPA
FIFI 3000Revenue
Customer
Rebates
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Third-Party Business: Solution using Note 35367 for Releases prior to Release 4.6
4InvoiceReceipt
20
2980
COGS1900 Supplier
1900
Sold qty +
Revenue +
Rebates +
+
+
+
COS +
Updatinginvoice receiptdirectly into CO-PA
SAP AG 1999 filename (author) / 75
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 76
Bill of Material for a Computer
Monitor Hard drive KeyboardMouse Floppy drive
Screen
Computer
Casing
SAP AG 1999 filename (author) / 77
Bill of Material in the Sales Document
A computer is made up of several components that, in turn, are made up of separate parts
You can store this structure in the system as a bill of material. All items in the bill of material (BOM) that you want to control in the sales document must be flagged as relevant for sales. If you create a BOM material with BOM usage 5 (SD), all the items in the BOM will automatically be flagged as relevant to sales.
By making the appropriate settings in Customizing for the item categories in the sales document, you can copy the components in the BOM to a sales order. To process the sales document, you only need to enter the material number of the BOM.
The BOM appears in the sales document as a structure with main and sub-items. The system automatically explodes the BOMs in the sales order by generating sub-items for the components.
SAP AG 1999 filename (author) / 78
Overview-Scenarios to handle Bill of Materials
Computer
Monitor
Hard drive
Pricing and costs at header or Sub-item-level ?
• Pricing & costs at header-level
• Pricing & costs at sub-item-level
• Pricing at header and costs at sub-item-level
• Pricing at header-level and cumulated cost of sub-items
• (Costs at sub-item-level and revenues distributed on sub- item-level)
Possible Answers
SAP AG 1999 filename (author) / 79
BOM Explosion
Item category of sub-item:
Explanation
TAQ
TAE
Material Master:R-1001
Sales: Sales org. 2
Item category group: ERLA
Material Master:R-1002
Item category group: LUMF
Sales: Sales org. 2
Alternative control of bill of material
Sales documentSales document
Item category of main item:
Pricing
Item category of sub-item:
Pricing
Sales documentSales document
Item category of main item:
Explanation
TAP
TAN
SAP AG 1999 filename (author) / 80
BOM Explosion
The individual item categories control what a BOM can do in the sales document. In Customizing, you define and assign item categories for the main and sub-items.
A specific item category group for the BOM in the material master specifies which item categories are assigned to the main item.
To determine how far the BOM should be exploded in the sales document, you need to define the extent of the structure of the item category for the material that has been defined as a BOM.
When you determine the sub-items, the system also needs to know the item category for the higher-level item.
In Customizing for item categories, you control which items are relevant to pricing and how requirements transfer is implemented.
SAP AG 1999 filename (author) / 81
Value Flows with BOM (1) Pricing at Main Item Level
t
CO-CO-PAPA
FIFI X
X
XRevenue
Customer
SDSD
Quantity FlowLogistic Documents
COGS
XInventory X
Rev.Deduct.
Sales order
It|Mat.|Qty.
10|M00|1 cond. types PR00... COGS
11|M01|2 statistical
12|M02|3 statistical
1 Goods issue
Material:M00
2
•Main item
•No sub-items
Billing
It|Mat.|Qty.
10|M00|1 cond. types PR00... COGS
11|M01|2 statistical
12|M02|3 statistical
3
CO-PA Postings(costing-based)
FI Postings / (CO-PA account-based)
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
Quantity: 1Main Item
SAP AG 1999 filename (author) / 82
Value Flows with BOM (2) Pricing at Sub-Item Level
t
CO-CO-PAPA
FIFI X
X
XRevenue
Customer
SDSD
Quantity FlowLogistic Documents
COGS
XInventory X
Rev.Deduct.
Sales order
It|Mat.|Qty.10|M00|1 statistical
11|M01|2 cond. types PR00... COGS
12|M02|3 cond. Types PR00... COGS
1 Goods issue
Material:M01M02
2
•No main item
•all sub-items
Billing
It|Mat.|Qty.10|M00|1 statistical
11|M01|2 cond. types PR00... COGS
12|M02|3 cond. Types PR00... COGS
3
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
Quantity: 2Sub-Item
Qty.: 3Sub-Item
SAP AG 1999 filename (author) / 83
BOM Explosion: Alternative Scenarios
Item category of sub-item:
Determine cost
ZTAQ
ZTAE
Material Master:R-1001
Sales: Sales org. 2
Item category group: ERLA
Material Master:R-1002
ERLAItem category group:
Sales: Sales org. 2
Alternative control of bill of material
Sales documentSales document
Item category of main item:
Pricing
Item category of sub-item:
Cost
Sales documentSales document
Item category of main item:
Pricing + cost
ZTAQ
ZANNFree of charge!
SAP AG 1999 filename (author) / 84
Value Flows BOM (3) Pricing Main Item/ Detailed Cost Sub-Item
t
CO-CO-PAPA
FIFI X
X
XRevenue
Customer
SDSD
Quantity FlowLogistic Documents
COGS
XInventory X
Rev.Deduct.
Sales order
It|Mat.|Qty.10|M00|1 cond. types PR00...
11|M01|2 cond. types COGS
12|M02|3 cond. Types COGS
1 Goods issue
Material:M01M02
2
•main item
•all sub-items
Billing
It|Mat.|Qty.10|M00|1 cond. types PR00...
11|M01|2 cond. types COGS
12|M02|3 cond. Types COGS
3
CO-PA Postings(costing-based)
FI Postings / (CO-PA account-based)
Sold qty +
Revenue +
Rebates +
Sold qty +
COGS +
var.PC +
fi xed PC +
Qty: 1Main Item
Sold qty +
COGS +
var.PC +
fi xed PC +
Qty: 2Sub Item
Qty: 3Sub Item
SAP AG 1999 filename (author) / 85
Value Flow BOM (4) Pricing Main Item/ Cost Sub-Item > Main Item
t
CO-CO-PAPA
FIFI X
X
XRevenue
Customer
SDSD
Quantity FlowLogistic Documents
COGS
XInventory X
Rev.Deduct.
Sales order
It|Mat.|Qty.10|M00|1 cond. types PR00... COGS
11|M01|212|M02|3
1 Goods issue
Material:M01M02
2
•main item
•all sub-items
Billing
It|Mat.|Qty.10|M00|1 cond. types PR00... COGS...
11|M01|212|M02|3
3
sub-items free of charge
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Sold qty +
Sold qty +
Qty: 1Main Item
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
Qty: 3Sub ItemQty: 2
Sub Item
SAP AG 1999 filename (author) / 86
Value Flows with BOM: Problems
Sales price is defined at main-item level and costs are created at the sub-items relevant for goods movement. In some cases, sub-items may not be relevant for billing at all.
Cost can be assigned to main-item level
Sub-items contain the quantity (free of charge)
Customizing SD Billing -> Billing documents -> Maintain copying rule for billing documents: Copying Control: Delivery to Billing Document -> Item -> Item category: flag cumulate cost
Note 65908 required up to Release 3.1I
SAP AG 1999 filename (author) / 87
Summary BOM
Pricing & costs at header-level
SD CO-PA
Pricing Determ. Cos Cum.Cos Material Qty Rev. Cos
Header
Item
X X X X X X
Pricing Determ. Cos Cum.Cos Material Qty Rev. Cos
Header
Item X X X X X X
Pricing Determ. Cos Cum.Cos Material Qty Rev. Cos
Header
Item
X
X
X X X
X
Pricing Determ. Cos Cum.Cos Material Qty Rev. Cos
Header
Item
X X X X X X
X X
X
X X
Pricing & costs at sub-item-level
Pricing at header and costs atsub-item-level
Pricing at header-level and cumu-lated cost of sub-items
SAP AG 1999 filename (author) / 88
Free Goods Inclusive
Customer OrderFirma
Rechnung
Firma
Rechnung
Firma
Bestellung MMM
10 Pieces
Delivery
10 Pieces
BillingFirma
Rechnung
Firma
Rechnung
Firma
Rechnungx y z
8 Pieces
SAP AG 1999 filename (author) / 89
Free Goods Exclusive
Customer orderFirma
Rechnung
Firma
Rechnung
Firma
Bestellung MMM
Delivery
4 Packages+1 Coffee-maschine
BillingFirma
Rechnung
Firma
Rechnung
Firma
Rechnung x y z
4 Packages1 Coffee- maschine
4 Packages
Kaffee
Kaffee
Kaffee
Kaffee
+++
Kaffee
Kaffee
SAP AG 1999 filename (author) / 90
Free Goods
CO
SD
Quantity
PriceDiscountCost
RevenueDeductionCosts
SAPstandard
MI SI
10 1
100
40 5
100
40 5
1MI SI
10 1
100
40 5
20-20
100
40 5
20-20
TANN• Pricing: B• Cond. type with req. 55
2MI SI
3
10 1
100
40
100
45
LF F1TANN• No pricing
Transfer to CO-PA (examples)
5
SAP AG 1999 filename (author) / 91
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 92
Factoring discountpayer 1
- 1%
Factoring discountpayer 1
- 1%
Invoice Lists
Billing doc. 1Billing doc. 1Billing doc. 1Billing doc. 1
Customer 1Payer 1
1000 USD
Customer 1Payer 1
1000 USD
Billing doc. 2Billing doc. 2Billing doc. 2Billing doc. 2
Customer 2 Payer 1
1000 USD
Customer 2 Payer 1
1000 USD
Billing doc. 3Billing doc. 3Billing doc. 3Billing doc. 3
Customer 3 Payer 1
1000 USD
Customer 3 Payer 1
1000 USD
Invoice list
Bill. doc. 1 1000 USD Bill. doc. 2 1000 USD Bill. doc. 3 1000 USD 3000 USD Factoringdiscount 30 USD
SAP AG 1999 filename (author) / 93
Invoice Lists
Invoice lists contain various billing documents (invoices, credit/debit memos) and can be sent to a payer on specified days or at certain intervals
Maintain the following data in Customizing for SD:
If you have agreed on a factoring discount, maintain condition type RL00 (factoring discount) as well as condition type MW15 (for tax)
Each billing type to be included in an invoice list must be assigned an invoice list type (LR for invoices and debit memos, LG for credit memos)
SAP AG 1999 filename (author) / 94
Invoice Lists
Maintain the following master data:
Define a factory calendar that specifies when invoice lists are to be created. Enter this factory calendar in the payer customer master record (Billing screen, “invoice list schedules” field)
Maintain condition records for condition type RL00 for the payer
Create output condition records for condition types LR00 or RD01 (you can specify whether invoice papers are sent to the customer upon invoice creation or only when the invoice list has been created)
SAP AG 1999 filename (author) / 95
Process in General / Document Flow with Invoice List
t
BillingDocument
BillingDocument
BillingDocument
InvoiceList
1MaintainFactoringDiscountfor Payer
5SalesOrder
SalesOrder
SalesOrder
2GoodsIssue
GoodsIssue
GoodsIssue
43
Process Partners
Customer
MMMM
Payer Plant
1
Quantity FlowLogistic DocumentsSDSD
SAP AG 1999 filename (author) / 96
Value Flows with Invoice Lists
t
CO-CO-PAPA
FIFI X
X
XRevenue
Customer
SDSD
Quantity FlowLogistic Documents
MMMM
COGS
XInventory
BillingDocument
BillingDocument
BillingDocument
InvoiceList
5SalesOrder
SalesOrder
SalesOrder
2GoodsIssue
GoodsIssue
GoodsIssue
43
Fact.Discount.Y
PayerY
MaintainFactoringDiscountfor payer
1
CO-PA Postings(costing-based)
FI Postings / (CO-PA account-based)
Sold qty +
Revenue +
Fact. Disct. -
COGS +
var.PC +
fi xed PC +
Sold qty +
Revenue +
Fact. Disct. -
COGS +
var.PC +
fi xed PC +
Sold qty +
Revenue +
Fact. Disct. +
COGS +
var.PC +
fi xed PC +
Fact. Disct. +StatisticalFact. Disct.
SAP AG 1999 filename (author) / 97
Invoice Lists: Update CO-PA
SD condition type for factoring discount (RL00) is statistical on the billing documents -> Transfer to costing-based CO-PA
When the invoice list is created, the factoring discount of the payer‘s billing documents is posted in FI
Problems with the transfer to CO-PA:
The invoice list refers to several billing documents but there is no reference to a single item -> profitability segment of billing document cannot be used -> account-based CO-PA not updated
Solutions for transfer of factoring discount:
Note 75665
Find profitability segment with automatic account assignment -> account-based (and once again costing-based CO-PA) are updated
Note 110444
Condition for factoring discount is relevant for accrual (account- based and costing-based are updated during billing)
SAP AG 1999 filename (author) / 98
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 99
Order Settlement
Sales Order Bearing Costs and Revenues
CO ObjectSDSD
Sales Order
Goods Issue
Billing Doc.
Invoice
Customer 1000
6,000.00
800000 - 6,000.00893010 5,000.00------------------------- - 1,000.00
Revenue 6,000.00COGS 5,000.00--------------------------Result 1,000.00
Cost of Goods Sold
5,000.00
Revenue
6,000.00
FIFI
CO-CO-PAPA
SAP AG 1999 filename (author) / 100
ProductionType
Value Flowin CO-PA
Make-to-Stock Make-to-OrderProject
As shown on"Point of Data Transfer from SD" (4)
Settlement ofsales order orproject
Valuated Stock
Valuated sales orderstock without aCO object
Valuated sales-orderstock with aCO object
Different Manufacturing Scenarios and CO-PA
SAP AG 1999 filename (author) / 101
Sales-Order-Related Production with Valuated Stock
Sales order
Goodsissue
Billingdocument
Salesordercost
estimate
Valuatedsales orderstock
Actual costsof production
order
Delivery
Productionvariance
Actual costsof production
order
Delivery
Productionvariance
OrderEntry Production Delivery Billing
CO-CO-PAPA
RevenuesDiscountsCost of sales- Raw material- Prod. costs- ...Production variances
SAP AG 1999 filename (author) / 102
Processes in Make-to-Order Production
Salesorder
Salesorder
GoodsIssue
GoodsIssue BillingBilling
Salesordercostestimate
Valuated,sales order specificstock
Deliveryto stock
(Results Analysis),Settlementto CO-PA
RevenuesCOS- raw mat.- prod.costs- ...
Customer-Order-Related Controlling (Plant Engineering and Construction)
Cost-CollectorCost-Collector
Otherpostings,
or processcosts
Otherpostings,
or processcosts
Productionorder
Act-Std=Variances
Productionorder
Act-Std=Variances
SAP AG 1999 filename (author) / 103
Processes in Make-to-Order Production
Salesorder
Salesorder
GoodsIssue
GoodsIssue BillingBilling
Productionorder
Productionorder
Salesordercostestimate
Quantities only
Deliveryto stock
Results Analysis,Settlementto CO-PA
RevenuesCOS- raw mat.- prod.costs- ...
Scenario 3.0 Non-Valuated Stock
Cost-CollectorCost-Collector
Otherpostings
or processcosts
Otherpostings
or processcosts
SAP AG 1999 filename (author) / 104
Settling Orders - PA Transfer Structure
Controlling Area Operating Concern
Source Assignment Lines Value Fields
Cost ElementGroup:
OAS
400000 - 699999
10 Total Costs Marketing
PA Transfer StructurePA Transfer Structure
SAP AG 1999 filename (author) / 105
1
1
SalesOrder
SDSD
Quantity FlowLogistic Documents
MMMM 2Delivery
3
BillingDocument
t
Intercompany Sales: Make-to-Order
4Inter-companyBilling
5InvoiceReceipt
CO-CO-PAPA
FIFI
X
Revenue
X FI Postings /(CO-PA acct-based)
CO-PA Postings(costing-based)
Sold qty +
Revenue +
Rebates +
COGS +
Var.PC +
fi xed PC +
ConditionPI01/PI02
Selling Company
IntercoRev
Sell.CompanyX
X
Customer
RebatesX
XCOGS
A/P
X
Delivering Company Production Costs IntercompRev
I ntercoRev +
Material +
Labour +
.............. +
Cost Collector
SAP AG 1999 filename (author) / 106
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 107
Definition of Revenue Recognition
What does revenue recognition mean?
You can use revenue recognition to determine if and how much revenue should be recognized in a certain posting period.
The revenue is recognized independently of the invoicing.
Prerequisites
Services relevant to revenue need to have been performed.
The revenue recognition process needs to have been initiated.
Types of Revenue Recognition
Standard revenue recognition (normal billing)
Time-Based Revenue Recognition
Performance-Based Revenue Recognition
SAP AG 1999 filename (author) / 108
Revenue Recognition
Normally, revenue is recognized at the point of time when the invoice is issued. When the invoice is posted to accounting, a posting is made to the revenue G/L account.
However, when you have a contract that is valid over a long period of time, the invoice/invoices are issued at various intervals, whereas you want to recognize revenue on a more regular basis using your fiscal year periods. This means that the invoice will not recognize the revenue.
SAP AG 1999 filename (author) / 109
Function Model for Revenue Recognition
Delivery
Contract
Billingp lan
• periodi c• m ei lstone
Unbilled receiva bles
Accounts receiva bles
Deferredrevenues
Revenues
Unbilled receiva bles
Deferredrevenues
Order
Billing pla n
• pe ri odi c• m ei lsto ne
SD FI CO
CO-P A
SAP AG 1999 filename (author) / 110
Value Flows with Standard Revenue Recognition
t
CO-CO-PAPA
FIFI X
X
XRevenue
Acc.Receivable
SDSD
Quantity FlowLogistic Documents
MMMM
COGS
XInventory
BillingDocument
BillingDocument
BillingDocument
SalesOrder
SalesOrder
SalesOrder
1GoodsIssue
GoodsIssue
3GoodsIssue
2
XRev.Deductions
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
SAP AG 1999 filename (author) / 111
Time Based Revenue Recognition
The value of this item is recognized for the same amounts according to the accrual period.
A contract with a periodic billing plan would usually have time-based revenue recognition. For example, a rental contract with 4 billing periods per year would generate an invoice 4 times a year.
In the absence of revenue recognition, then entries are made in your revenue G/L account in each of the 4 months when an invoice is issued.
But if your fiscal year periods are monthly periods, you would like to distribute your revenue equally over 12 months.
A more extreme case would be if you have a contract and bill only once at the end of the year. In that case, you would only show revenue in one month and zero revenue otherwise throughout the rest of the year. It would therefore be preferable to recognize revenue equally for each month throughout that year.
SAP AG 1999 filename (author) / 112
Time-Based Revenue Recognition
For time-based revenue recognition, unrealized revenue for each month is written when the contract is created.
You then run the revenue recognition program on a monthly basis. This program takes the unrealized revenue and makes G/L account entries in the revenue G/L. The offsetting entry is in either a deferred G/L account or the unbilled G/L account, depending on whether or not an invoice exists.
SAP AG 1999 filename (author) / 113
Value Flows with Time-Based Revenue Recognition (A)
t
CO-CO-PAPA
FIFI
X
X (18000,-)
Deferred Revenue
Acc.Receivable
SDSD
Quantity FlowLogistic Documents
MMMM
BillingDocument18000,-
Revenue Recognition Process
RevenueX1
(1500,-)XnDeferr.Rev.
RevenueXn
....
Deferr.Rev.(1500,-)X1
SD/MMDocument
period1 122 ....
CO-PA Postings(costing-based)
FI Postings / (CO-PA account-based)
Sold qty +
Revenue +
COGS +
var.PC +
fi xed PC +
SAP AG 1999 filename (author) / 114
Value Flows with Time-Based Revenue Recognition (B)
t
CO-CO-PAPA
FIFI
X
X (18000,-)
Unbilled Rev.
Acc.Receivable
SDSD
Quantity FlowLogistic Documents
MMMM BillingDocument18000,-
Revenue Recognition Process
RevenueX1
(1500,-)XnUnbilled Rev.
RevenueXn
....
Unbilled Rev.(1500,-)X1
SD/MMDocument
period1 122 ....
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Sold qty +
Revenue +
COGS +
var.PC +
fi xed PC +
SAP AG 1999 filename (author) / 115
Revenue Recognition and CO-PA
“Accounts Deferred Revenue” and “Unbilled Revenue” are balance sheet accounts. They do not involve cost elements or transfers to CO-PA.
Costing-based CO-PA is updated with revenues and cost of goods sold at the point of time when the revenue account is updated (during the revenue recognition process).
Account-based CO-PA does not receive cost of goods sold when there is no goods issue posting!
Up to Release 4.6A, it is not possible to post cost of goods sold (a lacking SD function)!
Since no SD condition types are available, you have to assign cost elements to CO-PA value fields (except for the statistical condition type VPRS (cost of goods sold)).
SAP AG 1999 filename (author) / 116
Performance-Based Revenue Recognition
Revenue recognition is based on business transactions, such as goods receipt for delivery-relevant items or posting sales orders for items that are not relevant to delivery.
SAP AG 1999 filename (author) / 117
Value Flows with Performance-Based Revenue Recognition
CO-CO-PAPA
FIFI
X
X (5000,-)
Deferred Revenue
Acc.Receivable
SDSD
Quantity FlowLogistic Documents
QuarterlyBillingDocument5000,- (X)
X1 (3000,-)
Deferr.Rev.
RevenueX1
Product&ConsultingContract2000,-
SalesOrder9000,-
Consulting 3000,- (X1)
(2000,-)
Deferr.Rev.
RevenueX2
(4000,-)Unbilled Recv.
Delivery
6000,- (X2)
....
MMMM
Revenue Recognition Process
CO-PA Postings(costing-based)
FI Postings / (CO-PA account-based)
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
SAP AG 1999 filename (author) / 118
Revenue Recognition
Transaction VF44:
This is the program that takes the unrealized revenue and posts it as real revenue.
The selection for VF44 is by contract numbers and by the period for which revenue should be recognized. Additionally, you can enter the posting date so that the FI posting is made to the period relating to that date.
This program first involves the revenue G/L account (the normal 800000), then the deferred G/L account 99000 and the unbilled G/L account 159100.
With transaction VF44, the values are applied to any value in the deferred account first and then the unbilled.
During invoicing (that is, when the invoice is transferred to FI), the value is applied against the unbilled first and then the deferred.
SAP AG 1999 filename (author) / 119
Example for Revenue Recognition (1)
Posting example (time-based revenue recognition)
Rental for a machine
Contract for 18,000 USD
Contract start: 01/01/1998
Contract end: 31/12/1998
First billing on 20/03/1998
Revenue recognition
01/01/1998 DM 1,500.00
01/02/1998 DM 1,500.00
01/03/1998 DM 1,500.00
20/03/1998 DM 5,000.00 (Invoicing)
30/03/1998 DM 5,000.00 (Payment per bank electronically)
01/04/1998 DM 1,500.00
01/05/1998 DM 1,500.00
SAP AG 1999 filename (author) / 120
Example for Revenue Recognition (2)
Postings1. Posting - Revenue Recognition (01/01/1998)
Unbilled receivables (159201) 1500
Revenue (800000) 1500
2. Posting - Revenue Recognition (01/02/1998)
Unbilled receivables (159201) 1500
Revenue (800000) 1500
3. Posting - Revenue Recognition (01/03/1998)
Unbilled receivables (159201) 1500
Revenue (800000) 1500
4. Posting - Invoice (20/03/1998)
Accounts receivable (140000) 5000
Unbilled receivables (159201) 4500
Deferred revenue (099000) 500
5. Posting - Revenue Recognition (01/04/1998)
Deferred revenue (099000) 500
Unbilled receivables (159201) 1000
Revenue (800000) 1500
6. Posting - Revenue Recognition (01/05/1998)
Deferred revenue (099000) 1500
Revenue (800000) 1500
Deferred reven. (099000) CD
01/04 500 20/03 500
Acc. receivable (140000) CD
20/03 5000 30/03 5000
Unbilled receiv. (159201) CD
01/01 150001/02 150001/03 150001/04 100001/05 1500
20/03 4500
Bank (110000) CD
30/03 5000
Revenues (800000) CD
01/01 150001/02 150001/03 150001/04 150001/05 1500
CO-CO-PAPA
Revenues and
COGS (>= Rel. 4.6B)
SAP AG 1999 filename (author) / 121
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 122
Budget Assignments - Business Background
In CO-PA, budgets can be created for sales and marketing campaigns, such as promotions.
Release 4.0 lets you assign funds from these budgets by assigning plan values to the condition records (prices, discounts, etc.) created for a particular sales deal or customer agreement.
CO-PA lets you monitor the process by comparing the budgeted values with the committed funds or the actual values in the billing document.
SAP AG 1999 filename (author) / 123
Budget Assignment
CO-PA
SD
Reporting
Budget
Promotion
Line item
Condition recordSales deals
Committedfunds
CO-CO-PAPA
SDSD
SAP AG 1999 filename (author) / 124
Promotion Planning
PromotionSales dealValid
78
Conditionrecord in sales deal
Commitments:Line items inCO-PA
108108
Update
Promotion
108109
05/1998
Cust. Material Cond.value Plan basis Plan value
Mat.AMat.A
5%10%
10,000 USD20,000 USD
500 USD2,000 USD
Customer Mat. AmountPeriod
78
AA
500 USD2,000 USD
05/9805/98
CO-CO-PAPA
SDSD
SAP AG 1999 filename (author) / 125
Monitoring Budget Assignments in CO-PA
Promotion 108
Sales deal 109
Customer discount
Material discount
Quantity discount
Total
Planned
10,000
50,000
40,000
100,000
Assigned
2,500
53,000
31,000
86,500
Variance
7,500
-3,000
9,000
13,500
SAP AG 1999 filename (author) / 126
Monitoring of Sales Deals
BudgetBudget CommitmentCommitment Sales orderSales order ActualsActuals
CustomeragreementsCustomer
agreements
Sales orderSales order
Billingdocument
Billingdocument
PA
SD
Sales dealPromotionSales dealPromotion
Sales dealPromotionSales dealPromotion
Sales dealPromotionSales dealPromotion
Planningin CO-PAPlanningin CO-PA
SAP AG 1999 filename (author) / 127
Processes in Detail
Make-to-Stock Processes in Detail
Sales from Stock
Complaints
Credit Memo/Debit Memo
Free Delivery
Returns
Bonus Agreements
Intercompany Sales
Third-Party Business
Promotion Packs/ Bill of Material
Invoice Lists
Make-to-Order Processes
Updating CO-PA without Cost Collector
Updating CO-PA with Cost Collector
Appendix: Industry-Specific Requirements
Revenue Recognition
Commitments from Promotions
Proof of Delivery
SAP AG 1999 filename (author) / 128
Vendor Customer
VendorVendor CustomerCustomer
1
3
2Proof ofDelivery
95 PC
Billing document
95 PC
Delivery
100 PC
Proof of Delivery
SAP AG 1999 filename (author) / 129
Without Proof of Delivery (POD), delivery processing ends with the posting of goods issue. However, confirmation of the received goods is essential to POD. Delivery processing is incomplete until POD is carried out.
POD primarily supports the business process whereby an invoice is created only when the customer has confirmed the arrival of the goods.
In addition to the confirmation of the inbound delivery, you can enter the goods receipt date, the quantity that was actually received, and the reason for any quantity differences. This is particularly important for deliveries where the delivery quantity varies due to the characteristics of the goods in question, or where the exact delivery quantity is not known to begin with.
Confirmation from the customer allows you to create an exact invoice. The reasons for differences in day-to-day situations are stored in the system and evaluated. Such reasons include goods disappearing or being stolen, certain characteristics of the goods (for example, volatility), or damage during shipment.
This evaluation is particularly useful when dealing with forwarding agents, vendors, or customers, since the differences can be followed up accurately in the system.
Proof of Delivery - Business Background
SAP AG 1999 filename (author) / 130
Proof of Delivery - Customer Benefits
Correct billing• Invoiced quantity = quantity delivered/received • Payment runs are improved and customer satisfaction is greater• Error-free billing is essential for efficient use of EDI
Service level and monitoring• Quantity variances • Where do we lose quantities and why?• Incorrect handling of the forwarding agent • Losses when the goods are packed into different containers• Goods characteristics (temperature/volatility)• Stock shrinkage
Accounting and cost accounting• You can assign costs and revenues more easily.
Legal basis• You post goods issue when the goods physically leave the vendor's plant (which affects insurance issues, for example).
SAP AG 1999 filename (author) / 131
Proof of Delivery - Customizing
IMG: Logistics Execution Shipping Deliveries Proof of Delivery. Here you can assign the POD relevancy to the item category. The flag “PODKZ” indicates which delivery item category is relevant for POD processing.
IMG: Logistics Execution Shipping Deliveries Proof of Delivery. Here you define reason codes that can be assigned to the differences.
Set the “Relevant for POD” indicator on the shipping tab page of the customer master for which you want to carry out POD processing in the “sales area” data of that customer's file.
SAP AG 1999 filename (author) / 132
Process in General / Document Flow with POD
t
BillingDocument
BillingDocument
BillingDocument
SalesOrder
SalesOrder
SalesOrder
1GoodsIssue
GoodsIssue
GoodsIssue
42
Process Partners
Customer Plant
MMMMPOD
3
Quantity FlowLogistic Documents
SDSD
SAP AG 1999 filename (author) / 133
Value Flows with POD
t
CO-CO-PAPA
FIFI XX
XRevenue
Customer
SDSD
Quantity FlowLogistic Documents
MMMM
COGS
XInventory
BillingDocument
BillingDocument
BillingDocumentQTY:5
SalesOrder
SalesOrder
SalesOrderQTY:7
1GoodsIssue
GoodsIssue
GoodsIssueQTY:7
42PODQTY:5
3
X Rev. Deduc.
FI Postings / (CO-PA account-based)
CO-PA Postings(costing-based)
Sold qty +
Revenue +
Rebates +
COGS +
var.PC +
fi xed PC +
COGS
Inventory
Y
Y ScrapYor
Availableas of Release4.6C