主数据之account assignment group

在material和customer的sales相关view中，有一个字段，account assignment group，它可以决定最终billing doc到FI doc时，进入哪个revenue account

相关配置在 IMG->Sales and Distribution->Basic Functions->Account Assignment/Costing->Revenue Account Determination下

执行Check Master Data Relevant For Account Assignment就可以配置material和customer的account assignment grp

之后通过执行Define Dependencies Of Revenue Account Determination 来定义决定收益帐户的条件table

比入001 就由sales org./acct assgGr/accout key 组成

然后执行Define Access Sequences And Account Determination Types来定义帐户决定的一个过程的condition type，跟定价类似，通过不同顺序和condition table来定义搜索的过程

之后通过Define And Assign Account Determination Procedures将condition type分配给一个决定过程

Define And Assign Account Keys可以定义和分配account key给condition type 这样可以使得进入FI的不同帐户，比如SAP内置了

• ERF freight revenues

• ERL revenues

• ERS sales deductions

• EVV cash settlement

• MWS sales tax

最后通过Assign G/L Accounts 分配帐户。
http://www.sapscene.com/sapscene/accassg.html

SD-FI Account Determination and Postings

This is known in the IMG as "revenue account determination", but it covers a lot more than that (discounts, taxes etc).  This is what determines how the financial impact of your SD Billing document is posted into the FI General Ledger.

The integration is controlled both in SD and in FI.

In SD there is a awesome area of configuration called the pricing procedures.   The pricing procedure determines the final price quoted to the customer for a particular product.  This could be a complicated calculation taking into account the base price, any special prices or discounts that may apply to that scenario, taxes, freight charges etc.  These prices or charges are called 'condition types'.  This condition technique is used in a number of areas of SAP.

For now all we need to know is that each condition type is assigned to an account key (or in the case of rebates two account keys).  You can assign multiple condition types to the same account key. There are a number of account keys that are pre-defined in the system. For example:

• ERF freight revenues
• ERL revenues
• ERS sales deductions
• EVV cash settlement
• MWS sales tax

Now we start getting to the integration by mapping the account keys to GL accounts.  But it is not as simple as that. It can be as flexible (ie: as complex) as you want. Start off with the most simple approach.  Generally if one is using a good sales / revenue reporting tool (eg: CO-PA) then one does not need a lot of flexibility and variety in the GL accounts that are posted to.  The level of detail that you need in GL should be determined by your financial statement reporting requirements - you may end up with only one Revenue account - it is a good bet!

So, taking the simple approach we would ignore most of the configuration possibilities : procedures, access sequences, condition tables etc  (Yes it is that 'condition technique' kicking in again.  Once you have worked through it once in one area and encounter it in another then hopefully you will be comfortable in knowing that most of the standard configuration can be left as is. )  

We have to decide which access sequences we want to use (Five access sequences are defined in the standard SAP R/3 System). To keep it simple, let us assume we just use one - for example: the access sequence "chart of accounts/sales org./account keys".

The chart of accounts part is standard in all account determinations, so let us look at the rest.  This access sequence allows us to specify different GL accounts for different Sales Organisations. 

So if we had a billing document line item where the customer had some special deductions for one of the products he purchased, we could map accounts by Sales Organisation.  To make it even simpler a document is within one Sales Organisation so we have an overall mapping as follows:

SD Line Item Condition typeSD AmountAccount KeySales OrganisationGL Account

1	Sales deduction for being such a nice guy	$10	ERS	1000	800010 - Sales deductions for 1000
Sales deduction for special promotion on particular product	$15	ERS
Base Revenue	$200	ERL	800000 - Revenue for Sales Org 1000
	Total for item 1	$175
2	Base Revenue	$100	ERL	1000	800000 - Revenue for Sales Org 1000
	Total for item 2	$ 100
Document Total	$ 275

So the invoice that the customer gets (and that you can view in SD) will look something like:

Item (Note this is the SD Invoice line item)Amount

Item 1:	$175
Item 2:	$100
Total owing , 30 days terms etc:	$275

The GL document posting that the system will make to FI will look something like this though:

FI Line Item Debit / Credit AccountAmount

1	Debit (PK=01)	Customer (AR Account)	$ 275
2	Credit (PK=50)	Revenue (GL Account)	-$ 300
3	Debit (PK=40)	Sales Deduction (GL Account)	$25
Balancing to 0 as all GL documents must....	$0

Note : There is no direct relation between an SD Line item and an FI Line Item - they are different things.