SAP 是採間接對應方式
iDempiere是產品類別下有會計科目
將產品功能用途分類
將產品材質製成分類
直接與會計科目歸屬分類相同
會造成會計科目設定太發散沒有管制
大型上市公司客製化 iDempiere 版本將類似 SAP 採用間接對應方式

CREATE TABLE IDEMPIERE.C_BP_GROUP_ACCT(  C_ACCTSCHEMA_ID         NUMBER(10)       NOT NULL,  C_BP_GROUP_ID           NUMBER(10)       NOT NULL,  AD_CLIENT_ID            NUMBER(10)       NOT NULL,  AD_ORG_ID               NUMBER(10)       NOT NULL,  ISACTIVE                CHAR(1 BYTE) DEFAULT 'Y'      NOT NULL,  CREATED                 DATE         DEFAULT SYSDATE  NOT NULL,  CREATEDBY               NUMBER(10)       NOT NULL,  UPDATED                 DATE         DEFAULT SYSDATE  NOT NULL,  UPDATEDBY               NUMBER(10)       NOT NULL,
  第一組.... 第N組         組別名稱
  ACCT_NAME               VARCHAR2(40)     NOT NULL,
  ACCT_ID                 NUMBER(10)       NOT NULL
===
ACCT_NAME 放欄位原名稱例如:C_RECEIVABLE_ACCT
ACCT_ID   放C_Validation
CREATE TABLE IDEMPIERE1.C_VALIDCOMBINATION
(
  C_VALIDCOMBINATION_ID  NUMBER(10)     NOT NULL,
  AD_CLIENT_ID           NUMBER(10)     NOT NULL,
  AD_ORG_ID              NUMBER(10)     NOT NULL,
  ISACTIVE               CHAR(1 BYTE)   DEFAULT 'Y'      NOT NULL,
  CREATED                DATE           DEFAULT SYSDATE  NOT NULL,
  CREATEDBY              NUMBER(10)     NOT NULL,
  UPDATED                DATE           DEFAULT SYSDATE  NOT NULL,
  UPDATEDBY              NUMBER(10)             NOT NULL,
  ALIAS                  NVARCHAR2(40),
  COMBINATION            NVARCHAR2(60),
  DESCRIPTION            NVARCHAR2(255),
  ISFULLYQUALIFIED       CHAR(1 BYTE)   DEFAULT 'Y' NOT NULL,
  C_ACCTSCHEMA_ID        NUMBER(10)     NOT NULL,
  ACCOUNT_ID             NUMBER(10)     NOT NULL,
  M_PRODUCT_ID           NUMBER(10),    料品
  C_BPARTNER_ID          NUMBER(10),    對象
  AD_ORGTRX_ID           NUMBER(10),    轉移
  C_LOCFROM_ID           NUMBER(10),    位置
  C_LOCTO_ID             NUMBER(10),    位置
  C_SALESREGION_ID       NUMBER(10),    銷售區域
  C_PROJECT_ID           NUMBER(10),    專案
  C_CAMPAIGN_ID          NUMBER(10),    檔期
  C_ACTIVITY_ID          NUMBER(10),    行動
  USER1_ID               NUMBER(10),    定義一
  USER2_ID               NUMBER(10),    定義二
  C_SUBACCT_ID           NUMBER(10),    次會計科目
  USERELEMENT1_ID        NUMBER(10),    次定義一
  USERELEMENT2_ID        NUMBER(10),    次定義一
  C_VALIDCOMBINATION_UU  NVARCHAR2(36)  DEFAULT NULL,
  AD_DEPTORG_ID          NUMBER(10)

)

CREATE TABLE IDEMPIERE.C_BP_GROUP_ACCT(  C_ACCTSCHEMA_ID         NUMBER(10)       NOT NULL,  C_BP_GROUP_ID           NUMBER(10)       NOT NULL,  AD_CLIENT_ID            NUMBER(10)       NOT NULL,  AD_ORG_ID               NUMBER(10)       NOT NULL,  ISACTIVE                CHAR(1 BYTE) DEFAULT 'Y'      NOT NULL,  CREATED                 DATE         DEFAULT SYSDATE  NOT NULL,  CREATEDBY               NUMBER(10)       NOT NULL,  UPDATED                 DATE         DEFAULT SYSDATE  NOT NULL,  UPDATEDBY               NUMBER(10)       NOT NULL,  C_RECEIVABLE_ACCT       NUMBER(10)       NOT NULL,  C_PREPAYMENT_ACCT       NUMBER(10)       NOT NULL,  V_LIABILITY_ACCT            NUMBER(10)   NOT NULL,  V_LIABILITY_SERVICES_ACCT   NUMBER(10)       NOT NULL,  V_PREPAYMENT_ACCT           NUMBER(10)       NOT NULL,  PAYDISCOUNT_EXP_ACCT        NUMBER(10)       NOT NULL,  PAYDISCOUNT_REV_ACCT        NUMBER(10)       NOT NULL,  WRITEOFF_ACCT               NUMBER(10)       NOT NULL,  NOTINVOICEDRECEIPTS_ACCT    NUMBER(10)       NOT NULL,  UNEARNEDREVENUE_ACCT        NUMBER(10)       NOT NULL,  NOTINVOICEDREVENUE_ACCT     NUMBER(10),  NOTINVOICEDRECEIVABLES_ACCT NUMBER(10),  PROCESSING                  CHAR(1 BYTE),  C_RECEIVABLE_SERVICES_ACCT  NUMBER(10),  C_BP_GROUP_ACCT_UU          NVARCHAR2(36)    DEFAULT NULL,  AD_DEPTORG_ID               NUMBER(10),  C_RECEIVABLEMASK_ACCT       NUMBER(22,10),  C_RECEIVABLEOTHER_ACCT      NUMBER(22,10))

OMSK – Account category reference button
會計類別




OMSK - Valuation Class Button
評價分級




材料型式 (Material Type) 對應    會計分類(Account category)

OMSK - Material Type/Account category reference

   

• Define Account Grouping (account modifier) for Movement Types
  
  依據   移動類型   定義會計分組  (會計修飾)  

Using this function, you can assign an account grouping to movement types. The account grouping is a finer subdivision of the transaction/event keys for the account determination.
The account grouping is provided for the following transactions keys:

• GBB (offsetting entry for inventory posting) 庫存過帳沖銷分錄
• PRD (price differences) 進貨價差
• KON (consignment liabilities) 寄售負債

The account grouping in the standard system is only active for transaction key GBB (offsetting entry for inventory posting).

OMWN - Define Account Grouping for Movement Types

• Purchase Account Management

It is used to attend legal requirement from specific countries (France, Italy, Finland, Belgium, Spain and Portugal). In this step, you will define a specific valuation and a separate accounting document for Purchase Order postings.

• Configure Automatic postings

In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
You can then check your settings using a simulation function.
What are automatic postings?
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a goods issue for a cost center:

• Stock account
• Consumption account 

How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a G/L account, since the ERP system automatically finds the accounts for each posting based on the following data:

• Chart of accounts of the company code

If the user enters a company code or a plant when entering a transaction, the ERP system determines the chart of accounts which is valid for the company code.
You must define the automatic account determination individually for each chart of accounts.

• Valuation grouping code of the valuation area

You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.

• Transaction/event key

You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). In this step, you can only insert the account number for each transaction key.

• Account grouping (modifier) (only for GBB, PRD and KOM)

Since the transaction key GBB is used for different transactions (for example, goods issue, scraping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.

• Valuation class of material or (in case of split valuation) the valuation type

The valuation class allows you to define automatic account determination that is dependent on the material.
You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the transaction key for every valuation class. 
Default settings:
G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.
OMWB - Configure Automatic Postings



OBYC - Maintain FI configuration 













How to test my account determination settings?
You should go to transaction OMWB and click on ‘simulation’ button. Then, insert the affected material, the correspondent plant and the movement type. After that, click on ‘account assignments’ button and you will see the simulation’s result.
OMWB - Simulation








Important:      
Report DFKB1INT: Display the source code in transaction SE38. It is used to shows us the possible values for the account determination customizing settings. If the customer changed something here, it is not standard anymore.