ERP俱乐部
ERP爱好者、ERP从业者互相交流、互相学习的乐园;我们的愿景是成为全球一流的中文ERP(Enterprise Resource Planning)交流平台
网站首页 论坛首页 搜索 用户列表 FAQ 注册 登录  
ERP俱乐部 -> SAP专栏 -> MM(物料管理) -> KBS科目问题
  KBS科目问题
帖子发起人: 啊利   发起时间: 2008-04-16 09:03 上午   回复数: 7
? 上一主题 下一主题 ?
楼主
  2008-04-16, 09:03 上午
啊利 离线,最后访问时间: 2012/2/16 10:53:26 啊利

无等级
男

20级
等级: 20级
注册: 2007年9月7日
经验: 40
积分: 40
精华: 0
发贴: 27
排名: 689
Site Registered Users
  KBS科目问题
附件:
KBS 1000___3100.png(14K, 下载次数:278)
 
各位前辈们好:

     我们在收货的时候发现一个问题,请看截图.很郁闷不知道啥回事?




分享按钮 IP 地址: 已登录   来自: 已登录    返回顶部
第 2 楼
  2008-05-05, 09:10 上午
鸿烈 离线,最后访问时间: 2015/3/16 15:42:38 鸿烈

发帖数前200位
男

40级
等级: 40级
注册: 2004年12月23日
区域: 成都
经验: 128
积分: 128
精华: 2
发贴: 84
排名: 190
Site Registered Users
Re: KBS科目问题
 
你的定制没到位,用OBYC,科目表EH01,valuation modification = 1000,valuation class= 3100,补上正确的财务总账科目。否则你永远收不了货。
IP 地址: 已登录   来自: 已登录    返回顶部
第 3 楼
  2008-09-02, 01:44 下午
toman 离线,最后访问时间: 2008/10/28 16:59:48 toman

无等级

10级
等级: 10级
注册: 2008年4月30日
经验: 11
积分: 11
精华: 0
发贴: 9
排名: 3,128
Site Registered Users
Re: KBS科目问题
 
楼主中文怎么搞的,我的ides4怎么就标题是中文的,内容是英文的。
分享按钮 IP 地址: 已登录   来自: 已登录    返回顶部
第 4 楼
  2008-09-03, 09:23 上午
朝圣 离线,最后访问时间: 2009/7/9 13:05:58 朝圣

发帖数前500位

30级
等级: 30级
注册: 2007年4月17日
经验: 91
积分: 961
精华: 0
发贴: 66
排名: 275
Site Registered Users培训学员(MM学员服务区-上海200712班)
Re: KBS科目问题
 
ECC6.0 都是这样的,help全是中文。

KBS,很少听说国内的企业会用到这个TE码,呵呵。看看是不是操作的问题。
IP 地址: 已登录   来自: 已登录    返回顶部
第 5 楼
  2008-09-03, 09:27 上午
朝圣 离线,最后访问时间: 2009/7/9 13:05:58 朝圣

发帖数前500位

30级
等级: 30级
注册: 2007年4月17日
经验: 91
积分: 961
精华: 0
发贴: 66
排名: 275
Site Registered Users培训学员(MM学员服务区-上海200712班)
Re: KBSヘ问题
 
--篕ま
Important SAP Notes on Configuration of MM-FI AAA Posting

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 R/3 System automatically finds the accounts to which postings are to be made using 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 R/3 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 for the valuation area

If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.

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 (internal processing key)

Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers. You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction.

Account grouping (only for offsetting entries, consignment liabilities, and price differences)

Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, 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.

An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting".



Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts.

If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key.

Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.

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. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials. You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class.

If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.

Requirements

Before you maintain automatic postings, you must obtain the following information:

1. Valuation level (plant or company code)
Establish whether the materials are valuated at plant or at company code level
When valuation is at plant level, the valuation area corresponds to a plant. When
valuation is at company code level, the valuation area corresponds to a company
code.

2. Chart of accounts and valuation grouping code per valuation area
Find out whether the valuation grouping code is active.
Activate split valuation
If it is not active, determine the chart of accounts assigned to each valuation area
(via the company code). If it is active, determine the chart of accounts and the
valuation grouping code assigned to each valuation area. Group valuation areas

You must define a separate account determination process for chart of accounts
and each valuation grouping code.


3 Valuation class per material type

If you wish to differentiate the account determination process for specific
transactions according to valuation classes, find out which valuation classes are
possible for each material type Define valuation class

4. Account grouping for offsetting entries to stock accounts
Under Define account grouping for movement types, determine for which
movement types an account grouping is defined for the transaction/event keys
GGB (offsetting entry to stock posting), KON (consignment liabilities) and PRD
(price differences).

Activities

1. Create account keys for each chart of accounts and each valuation grouping code
for the individual posting transactions. To do so, proceed as follows:

a) Call up the activity Configure Automatic Postings.

The R/3 system first checks whether the valuation areas are correctly
maintained. If, for example, a plant is not assigned to a company code, a dialog
box and an error message appear. From this box, choose Continue (next entry)
to continue the check.

Choose Cancel to end the check.

The configuration menu Automatic postings appears.

b) Choose Goto -> Account assignment.

A list of posting transactions in Materials Management appears.
For further details of the individual transactions, see Further information.
The Account determination indicator shows whether automatic account
determination is defined for a transaction.

c) Choose a posting transaction.

A box appears for the first posting transaction. Here you can enter a chart of
accounts

You can enter the following data for each transaction:

- Rules for account number assignments
With Goto -> Rules you can enter the factors on which the
account number assignments depend:
- debit/credit indicator
- general grouping (= account grouping)
- valuation grouping
- valuation class

- Posting keys for the posting lines
Normally you do not have to change the posting keys. If you
wish to use new posting keys, you have to define them in the
Customizing system of Financial Accounting.

- Account number assignments
You must assign G/L accounts for each transaction/event key
(except KBS). You can assign these accounts manually or copy
them from another chart of accounts via Edit -> Copy.
If you want to differentiate posting transactions (e.g.
inventory postings) according to valuation classes, you must
make an account assignment for each valuation class.
Using the posting transaction "Offsetting entry for inventory
posting", you have to make an account assignment for each
account grouping

If the transaction PRD (price differences) is also dependent on
the account grouping, you must create three account assignments:
- an account assignment without account grouping
- an account assignment with account grouping PRF
- an account assignment with account grouping PRA
If the transaction KON (consignment and pipeline liabilities) is
also dependent on the account grouping, you must create two
account assignments:
- an account assignment without account grouping (consignment)
- an account assignment with account grouping (pipeline)

d) Save your settings.

Then check your settings with the simulation function.
With the simulation function, you can simulate the following:

- Inventory Management transactions

- Invoice Verification transactions
When you enter a material or valuation class, the R/3 system
determines the G/L accounts which are assigned to the corresponding
posting transactions. Depending on the configuration, the SAP system
checks whether the G/L account exists
In the simulation you can compare the field selection of the
movement type with that of the individual accounts and make any corrections.
If you want to print the simulation, choose Simulation -> Report.
To carry out the simulation, proceed as follows:

a) Choose Settings to check the simulation defaults for
- the application area (Invoice Verification or Inventory
Management)
- the input mode (material or valuation class)
- account assignment
Instructions

b) Choose Goto -> Simulation.
The screen for entering simulation data appears.

c) Depending on the valuation level, enter a plant or a company
code on the screen.

d) When you simulate Inventory Management transactions, goods
movements are simulated. The R/3 system suggests the first
movement type for simulation. If several movements are possible
with this movement type, you can select a line.
When you simulate Invoice Verification transactions, a list
appears on the screen of the possible transaction types. Select
a line.

e) Then choose Goto -> Account assignments.
A list appears of the posting lines which can be created by the
selected transaction. For each posting line, the G/L account for
the debit posting as well as the G/L account for the credit
posting are displayed.

f) From this screen, choose Goto -> Movement+ to get a list of the
posting lines for the next movement type or transaction type.
If you work with valuation classes, choose Goto -> Valuation
class+ to receive the simulation for the next valuation class.
This function is not possible when simulating with material
numbers.
Choose Goto -> Check screen layout to compare the movement type
with the G/L accounts determined by the system and make any
necessary corrections.

Further Notes

刪 Expense/revenue from consumption of consignment material (AKO)

This transaction is used in Inventory Management in the case of
withdrawals from consignment stock or when consignment stock is
transferred to own stock if the material is subject to standard
price control and the consignment price differs from the standard
price.

刪 Expenditure/income from transfer posting (AUM)

This transaction is used for transfer postings from one material to
another if the complete value of the issuing material cannot be
posted to the value of the receiving material. This applies both to
materials with standard price control and to materials with moving
average price control. Price differences can arise for materials
with moving average price if stock levels are negative and the stock
value becomes unrealistic as a result of the posting. Transaction
AUM can be used irrespective of whether the transfer posting
involves a transfer between plants. The expenditure/income is added
to the receiving material.

刪 Provisions for subsequent (end-of-period rebate) settlement (BO1)

If you use the "subsequent settlement" function with regard to
conditions (e.g. for period-end volume-based rebates), provisions
for accrued income are set up when goods receipts are recorded
against purchase orders if this is defined for the condition type.




刪 Income from subsequent settlement (BO2)

The rebate income generated in the course of "subsequent settlement"
(end-of-period rebate settlement) is posted via this transaction.

刪 Income from subsequent settlement after actual settlement (BO3)

If a goods receipt occurs after settlement accounting has been
effected for a rebate arrangement, no further provisions for accrued
rebate income can be managed by the "subsequent settlement"
facility. No postings should be made to the account normally used
for such provisions. As an alternative, you can use this transaction
to post provisions for accrued rebate income to a separate account
in cases such as the one described.

刪 Change in stock (BSV)

Changes in stocks are posted in Inventory Management at the time
goods receipts are recorded or subsequent adjustments made with
regard to subcontract orders.

If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the
table of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.

Stock posting (BSX)

This transaction is used for all postings to stock accounts. Such
postings are effected, for example:

- In inventory management in the case of goods receipts to own
stock and goods issues from own stock

- In invoice verification, if price differences occur in
connection with incoming invoices for materials valuated at
moving average price and there is adequate stock coverage

- In order settlement, if the order is assigned to a material with
moving average price and the actual costs at the time of
settlement vary from the actual costs at the time of goods
receipt

Because this transaction is dependent on the valuation class, it is
possible to manage materials with different valuation classes in
separate stock accounts.

Caution :

Take care to ensure that:

- A stock account is not used for any transaction other than BSX

- Postings are not made to the account manually

- The account is not changed in the productive system before all
stock has been booked out of it

Otherwise differences would arise between the total stock value of
the material master records and the balance on the stock account.

Revaluation of "other" consumptions (COC)

This transaction/event key is only relevant to Brazil. It is used if
a revaluation report is used for company codes in Brazil.
The revaluation report uses the actual prices determined by the
material ledger/actual costing to:

- Revaluate costs on the basis of actual prices

- Post the price differences arising from "other" consumptions
(e.g. consumption to cost center) to a collective account

This transaction/event key is needed to post the price differences.
The account specified here is posted with the price differences for
"other" consumptions.

o documentation currently available.

Small differences, Materials Management (DIF)

This transaction is used in Invoice Verification if you define a
tolerance for minor differences and the balance of an invoice does
not exceed the tolerance.

Purchase account(EIN), purchase offsetting account (EKG), freight
purchase account (FRE)

These transactions are used only if Purchase Account Management is
active in the company code.


Freight clearing (FR1), provision for freight charges (FR2), customs
duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental
procurement costs) in the case of goods receipts against purchase
orders and incoming invoices. Which transaction is used for which
delivery costs depends on the condition types defined in the
purchase order.
You can also enter your own transactions for delivery costs in
condition types.

External service (FRL)

The transaction is used for goods and invoice receipts in connection
with subcontract orders.
If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the
table of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.

External service, delivery costs (FRN)

This transaction is used for delivery costs (incidental costs of
procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must

Offsetting entry for stock posting (GBB)

Offsetting entries for stock postings are used in Inventory
Management. They are dependent on the account grouping to which each
movement type is assigned. The following account groupings are
defined in the standard system:

- AUA: for order settlement

- AUF: for goods receipts for orders (without account
assignment)
and for order settlement if AUA is not maintained

- AUI: Subsequent adjustment of actual price from cost center
directly
to material (with account assignment)

- BSA: for initial entry of stock balances

- INV: for expenditure/income from inventory differences

- VAX: for goods issues for sales orders without
account assignment object (the account is not a cost
element)

- VAY: for goods issues for sales orders with
account assignment object (account is a cost element)

- VBO: for consumption from stock of material provided to
vendor

- VBR: for internal goods issues (for example, for cost
center)

- VKA: for sales order account assignment
(for example, for individual purchase order)

- VKP: for project account assignment (for example, for
individual PO)

- VNG: for scrapping/destruction

- VQP: for sample withdrawals without account assignment

- VQY: for sample withdrawals with account assignment

- ZOB: for goods receipts without purchase orders (mvt type
501)
- ZOF: for goods receipts without production orders
(mvt types 521 and 531)

You can also define your own account groupings. If you intend to
post goods issues for cost centers (mvt type 201) and goods issues
for orders (mvt type 261) to separate consumption accounts, you can
assign the account grouping ZZZ to movement type 201 and account
grouping YYY to movement type 261.

Caution

If you use goods receipts without a purchase order in your system
(movement type 501), you have to check to which accounts the account
groupings are assigned ZOB
If you expect invoices for the goods receipts, and these invoices
can only be posted in Accounting, you can enter a clearing account
(similar to a GR/IR clearing account though without open item
management), which is cleared in Accounting when you post the vendor
invoice.
Note that the goods movement is valuated with the valuation price of
the material if no external amount has been entered.
As no account assignment has been entered in the standard system,
the assigned account is not defined as a cost element. If you assign
a cost element, you have to enter an account assignment via the
field selection or maintain an automatic account assignment for the
cost element.

Purchase order with account assignment (KBS)

You cannot assign this transaction/event key to an account. It means
that the account assignment is adopted from the purchase order and
is used for the purpose of determining the posting keys for the
goods receipt.

Exchange rate differences in the case of open items (KDM)

Exchange rate differences in the case of open items arise when an
invoice relating to a purchase order is posted with a different
exchange rate to that of the goods receipt and the material cannot
be debited or credited due to standard price control or stock
undercoverage/shortage.

Differences due to exchange rate rounding, Materials Management
(KDR)

An exchange rate rounding difference can arise in the case of an
invoice made out in a foreign currency. If a difference arises when
the posting lines are translated into local currency (as a result of
rounding), the system automatically generates a posting line for
this rounding difference.

Consignment liabilities (KON)

Consignment liabilities arise in the case of withdrawals from
consignment stock or from a pipeline or when consignment stock is
transferred to own stock.
Depending on the settings for the posting rules for the

transaction/event key KON, it is possible to work with or without
account modification. If you work with account modification, the
following modifications are available in the standard system:

- None for consignment liabilities

- PIP for pipeline liabilities

Offsetting entry for price differences in cost object hierarchies
(KTR)

The contra entry for price difference postings (transaction PRK)
arising through settlement via material account determination is
carried out with transaction KTR.

Price differences (PRD)

Price differences arise for materials valuated at standard price in
the case of all movements and invoices with a value that differs
from the standard price. Examples: goods receipts against purchase
orders (if the PO price differs from the standard pricedardpreis),
goods issues in respect of which an external amount is entered,
invoices (if the invoice price differs from the PO price and the
standard price).
Price differences can also arise in the case of materials with
moving average price if there is not enough stock to cover the
invoiced quantity. In the case of goods movements in the negative
range, the moving average price is not changed. Instead, any price
differences arising are posted to a price difference account.
Depending on the settings for the posting rules for
transaction/event key PRD, it is possible to work with or without
account modification. If you use account modification, the following
modifications are available in the standard system:

- None for goods and invoice receipts against purchase orders

- PRF for goods receipts against production orders and
order settlement

- PRA for goods issues and other movements

- PRU for transfer postings (price differences in the case
of external amounts)

Provision for delivery costs (RUE)

Provisions are created for accrued delivery costs if a condition
type for provisions is entered in the purchase order. They must be
cleared manually at the time of invoice verification.

Taxes in case of transfer posting GI/GR (TXO)

This transaction/event key is only relevant to Brazil (nota fiscal).


Revenue/expense from revaluation (UMB)

This transaction/event key is used both in Inventory Management and
in Invoice Verification if the standard price of a material has been
changed and a movement or an invoice is posted to the previous
period (at the previous price).

Unplanned delivery costs (UPF)

Unplanned delivery costs are delivery costs (incidental procurement
costs) that were not planned in a purchase order (e.g. freight,
customs duty). In the SAP posting transaction in Logistics Invoice
Verification, instead of distributing these unplanned delivery costs
among all invoice items as hitherto, you have the option of posting
them to a special account. A separate tax code can be used for this
account.

Input tax, Purchasing (VST)

Transaction/event key for tax account determination within the
"subsequent settlement" facility for debit-side settlement types.
The key is needed in the settlement schema for tax conditions.

Goods issue, revaluation (inflation) (WGI)

This transaction/event key is used if already-posted goods issues
have to be revaluated following the determination of a new market
price within the framework of inflation handling.

Goods receipt, revaluation (inflation) (WGR)

This transaction/event key is used if already-effected transfer
postings have to be revaluated following the determination of a new
market price within the framework of inflation handling. This
transaction is used for the receiving plant, whereas transaction WGI
(goods receipt, revaluation (inflation)) is used for the plant at
which the goods are issued.

GR/IR clearing (WRX)

Postings to the GR/IR clearing account occur in the case of goods
and invoice receipts against purchase orders. For more on the GR/IR
clearing account, refer to the SAP Library (documentation MM
Material Valuation).
Caution
You must set the Balances in local currency only indicator for the
GR/IR clearing account to enable the open items to be cleared. For
more on this topic, see the field documentation.

Path
IMG (Implementation Guide) 劤 Materials Management 劤Valuation And Account Assignment 劤 Account Determination 劤 Account Determination without wizard 劤 Configure Automatic Postings


Note: Configuration related to the above for growel attached as Annexure

Define Accounts for Materials Management

In this step, you store accounts for Materials Management transactions that lead to automatic postings in Financial Accounting.

Store the required accounts for every transaction that is posted in your company.

Path
IMG (Implementation Guide) 劤 Financial Accounting 劤 General Ledger Accounting 劤 Business Transaction 劤 Integration 劤Materials Management 劤 Define Accounts for Materials Management

Transaction Code OBYC


What MM does

Path
IMG (Implementation Guide) 劤 Materials Management 劤Valuation And Account Assignment 劤 Account Determination 劤 Account Determination without wizard 劤 Define Valuation Control

Transaction Code OMVVM

For account determination, you can group together valuation areas by activating the valuation grouping code. This makes the configuration of automatic postings much easier.

In the standard SAP R/3 System, the valuation grouping code is set to active.

Activities

Set the valuation grouping code.

Notes on transport

In this step, you maintain the table TCURM. This table activates/deactivates key functions in the client. It:

Defines the valuation level (plant / company code), Activates the Late material block,
Activates split valuation

Since the automatic transport of an indicator could activate/deactivate other functions, you cannot use the automatic transport function here.


Maintain the Customizing function manually in the target system.

For the first Customizing transport to a target system that is not yet productive, you can transport the table manually. To do this, you must include the entry R3TR TABU TCURM in the transport request.

Group Together Valuation Areas

In this step, you assign valuation areas to a valuation grouping code.

The valuation grouping code makes it easier to set automatic account determination. Within the chart of accounts, you assign the same valuation grouping code to the valuation areas you want to assign to the same account.

Valuation grouping codes either reflect a fine distinction within a chart of accounts or they correspond to a chart of accounts.

Within a chart of accounts, you can use the valuation grouping code

to define individual account determination for certain valuation areas (company codes or plants), to define common account determination for several valuation areas (company codes or plants)

Requirements

You must have activated the valuation grouping code in the step Define valuation control.
Define valuation control

You must have defined the valuation level in corporate structure Customizing.
Define valuation level

You must have assigned each plant to a company code in "Corporate structure" Customizing. When assigning your plants, the valuation areas are defined automatically.
Assign plant to company code

Recommendation

We recommend that you only use a valuation grouping code within a chart of accounts in order to prevent account determination from becoming confusing.






Path
IMG (Implementation Guide) 劤 Materials Management 劤Valuation And Account Assignment 劤 Account Determination 劤 Account Determination without wizard 劤 Group Together Valuation Areas

Transaction Code OMVVD

Following are the settings done

Define Valuation Classes

In this step, you define which valuation classes are allowed for a material type.

If a user creates a material, he must enter the material's valuation class in the accounting data. The R/3 System uses your default settings to check whether the valuation class is allowed for the material type.

The valuation class is a group of materials with the same account determination. If a transaction is to be posted to different accounts depending on the valuation class, create an account determination for each valuation class in the step Create automatic postings.

The valuation classes allowed depend on the material type. Several valuation classes are generally allowed for one material type. A valuation class can also be allowed for several material types.

The link between the valuation classes and the material types is set up via the account category reference.

The account category reference is a combination of valuation classes. Precisely one account category reference is assigned to a material type.






Requirements

You must have defined your material types. You must have defined the chart of accounts, You must have agreed with Financial Accounting which materials are
assigned to which accounts.

Default settings

In the standard SAP R/3 System, an account category reference is created for each material type. The account category reference is, in turn, assigned to precisely one valuation class. This means that each material type has its own valuation class.

Recommendation

We recommend that you create the account groups of your chart of accounts as an account category reference.

Activities

1. Create account category references under account category reference

2. Under valuation class, define the valuation classes for each account category
reference

3. Under Material type/account category reference, assign an account category
sreference to each material type.


Path
IMG (Implementation Guide) 劤 Materials Management 劤Valuation And Account Assignment 劤 Account Determination 劤 Account Determination without wizard 劤 Define Valuation Classes

Transaction Code OMSK

Following are the settings made











Account Category Reference



Valuation Classes




Material Type/ Account Category Reference





Define Account Groupings 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.

Example with ChOA-INT

During a goods movement, the offsetting entry for the inventory posting (transaction GBB) can be made to different accounts, depending on the movement type:


Movement Type Account Grouping Account
561 Init. entry of stock bal BSA 399999
201 GI for cost center VBR 400000


Standard Settings

The account grouping is provided for the following transactions:

o GBB (offsetting entry for inventory posting)
Overview of account groupings GBB

o PRD (price differences)
Overview of account groupings PRD

o KON (consignment liabilities)
Overview of account groupings KON

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

Recommendation

We recommend that you use the default setting.

Activities

You do not have to carry out any activities here if you are using the default setting.

You can also define your own account groupings for transaction GBB.





Example:
If you want to post goods issues for cost centers on separate consumption accounts (movement type 201) and goods issues for orders (movement type 261), you can, for example, assign account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261. In the step Configure automatic postings, you can then assign different accounts to the individual account groupings.

The account groupings for transactions PRD and KON are predefined.


Path
IMG (Implementation Guide) 劤 Materials Management 劤Valuation And Account Assignment 劤 Account Determination 劤 Account Determination without wizard 劤 Define Account Groupings for Movement Type

Transaction Code OMVVN
分享按钮 IP 地址: 已登录   来自: 已登录    返回顶部
第 6 楼
  2008-09-03, 09:27 上午
朝圣 离线,最后访问时间: 2009/7/9 13:05:58 朝圣

发帖数前500位

30级
等级: 30级
注册: 2007年4月17日
经验: 91
积分: 961
精华: 0
发贴: 66
排名: 275
Site Registered Users培训学员(MM学员服务区-上海200712班)
Re: KBS科目问题
 
再补充一点自动记账的基础知识:
FI/MM通过tcode OBYC为所有的库存移动设置过帐科目,系统用不同的TransactionKey决定了
不同的移动类型/业务类型,对于这些TK的含义,SAPLIB中有较为详细的解释,可参阅。
科目的配置可以按照需要做在ValuationArea(Plant)和ValuationClass层。
特别是我认为FI/MM AccountDetermination中最有意思的就是TK为GBB的科目定义,其中有一个
东东叫做GeneralModificationKey,这个GMK是同MovementType直接相连的;除了很多标准的
GMK之外,用户也可以自定义,并将它们同自定义的MovementType相关联,以决定不同的MT连接
到不同的过帐科目上。

可以按照资料到系统中配置一下,并做一些例子,有助于理解这些科目配置~
1、对于收货(特别是来自采购的收货)和发票录入IV/LIV,常用的TransactionKey为:
BSX 同ValuationClass相关联的所有基于存货科目的过帐
FR1、FR3 运费和关税的清帐科目(需要通过IV/LIV做Clear,类似GR/IR科目)
FR2、FR4 运费和关税预提科目(无需Clear)
WRX 存货GR/IR科目
DIF SmallDifference(小金额差异),未超过发票价差容限的金额过到此科目(OMR6中
定义ToleranceLimit)
KDM 处理收货同收发票汇率不一致造成的差异过帐
KDR 处理收外币发票时,由于四舍五入的原因造成的本币金额同GRIR本币金额不一致
的差异过帐
UPF 处理UnplannedDeliveryCost(计划外运费)是否单独过到某个制定科目而不是过到
存货或价差科目
PRD 标准成本法下处理PPV的科目,即采购价差科目

2、对于发货和其他库存移动,常用的TransactionKey通常只需要关注GBB,即所谓库存移动的抵
减或对应科目,其中比较重要的一个概念就是GeneralModificationKey,这个东东是同
MovemtType关联的,
较常用的有:

AUA: 生产订单结算的差异科目。
AUF : 无Acct.Assignmt的PP/CO订单的收货和结算
BSA : 通过561/562做库存初始化的过帐科目
INV : 库存差异导致的收入和费用科目,一般为P+L科目
VAX/VAY: 销售订单的发货成本科目
VBO : 委托加工业务,提供给供应商的库存出货科目
VBR : 处理内部发货业务,如直接消耗到成本中心、资产或内部订单等 ,同时这个也是成本估算的原材料科目的去向,所以这里这些科目一定要设为成本要素。生产的发货也用这个科目
VKA : 基于Acct.Assignmt的销售订单业务,如BTO、MTO业务等
VKP : 基于Acct.Assignmt的项目业务,如BTP、MTP业务等
ZOB : 无PO收退货,如501/502
ZOF : 无PP订单收退货,如521/522 ,及副产品在成本估算时使用。
同样,你可以基于自定义的MovemtType,设置相关联的自定义的GMK,并在GBB中指定科目。

此外,如果启用MaterialLedger、标准成本法核算货ProductCostbyPeriod等,相关的LKW,PRV,
PRP,PRQ和PRY等也需要做相关设置,详见帮助。

对于收货科目设置,举个稍复杂的例子:
A000工厂下的物料A,ValuationClass为V000;拟在MM/InfoRecord中定价2%的采购运费,
不需要通过IV/LIV清帐;价差容限定义1元以下为SmallDifference;在采购过程中发生了
计划外运费,并希望过到制定科目上;收发票时的汇率同收货时不同,有差异。
示例会计科目如下:
1401 原材料存货科目
2181 预提运费
5121 计划外运费
5122 SmallDifference
5151 汇率差异
6000 存货GR/IR

可通过OBYC配置为:
库存过帐 BSX A000 V000 1401
预提运费 FR2 A000 V000 2181
小额价差 DIF 5122
计划外运 UPF 5121
汇率差异 KDM A000 V000 5151
GR/IR WRX A000 V000 6000

收货时的分录为(MAP计价方式,忽略VAT):
Dr. 1401 1020.00
Cr. 6000 1000.00
2181 20.00
收采购发票时的分录为:
Dr. 6000 1000.00
5121 100.00
5122 0.80
5151 1.20
Cr. A/P 1102.00
收运费发票的分录:
Dr. 2181 20.00
Cr. A/P 20.00
IP 地址: 已登录   来自: 已登录    返回顶部
第 7 楼
  2008-11-20, 03:28 下午
hacken 离线,最后访问时间: 2018/6/26 14:27:51 hacken

发帖数前25位

70级
等级: 70级
注册: 2007年4月27日
经验: 699
积分: 80
精华: 0
发贴: 605
排名: 39
Site Registered Users每日发帖之星每日发帖之星每日发帖之星每日发帖之星
Re: KBS科目问题
 
Purchase order with account assignment (KBS)

You cannot assign this transaction/event key to an account. It means
that the account assignment is adopted from the purchase order and
is used for the purpose of determining the posting keys for the
goods receipt.

楼主,这应该对你有所帮助。。
分享按钮 IP 地址: 已登录   来自: 已登录    返回顶部
第 8 楼
  2008-11-20, 03:34 下午
hacken 离线,最后访问时间: 2018/6/26 14:27:51 hacken

发帖数前25位

70级
等级: 70级
注册: 2007年4月27日
经验: 699
积分: 80
精华: 0
发贴: 605
排名: 39
Site Registered Users每日发帖之星每日发帖之星每日发帖之星每日发帖之星
Re: KBS科目问题
 
谢谢朝圣,我对AAA有了进一步的认识。。。。
IP 地址: 已登录   来自: 已登录    返回顶部
 第 1 页 总共 1 页 [共有 8 条记录]
ERP俱乐部 -> SAP专栏 -> MM(物料管理) -> KBS科目问题
(C)Copyright 2005-2020 www.erpclub.org All Rights Reserved.
Tel:+86-755-26444630
Email:webmaster@yok.com.cn