`
Jack Wu
  • 浏览: 877680 次
  • 来自: ...
社区版块
存档分类
最新评论

Auto Acc Assign(MM)

阅读更多

Table T030 - GL account assignments in MM 

Trans CKM9 - shows MM config / GL assignments

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.

Under Further information there is a list of transactions in Materials Management and their definitions.

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 of 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.
    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.
    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.
    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).

Default settings

G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.

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.
    2. 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
      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.

Note

The simulation function does NOT obviate the need for a trial posting!

Further notes

The following list shows the individual transactions with examples of how they are used. The transaction/event key is specified in brackets.

  • Agency business: income (AG1)
    This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
  • Agency business: turnover (AG2)
    This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
  • Agency business: expense (AG3)
    This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
  • 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.
  • Supplementary entry for stock (BSD)
分享到:
评论

相关推荐

    auto-assign-action:在拉取请求打开时向拉取请求添加审阅者的操作

    name : ' Auto Assign 'on : pull_request : types : [opened, ready_for_review]jobs : add-reviews : runs-on : ubuntu-latest steps : - uses : kentaro-m/auto-assign-action@v1.1.2 with : configuration-path...

    auto-assign-review-teams:GitHub 分配审核团队的操作

    自动分配审核团队分配个人或成员如果启用了... - name : " Assign Team and Persons " uses : rowi1de/auto-assign-review-teams@v1.0.1 with : repo-token : ${{ secrets.GITHUB_TOKEN }} teams : " gitub-org-team "

    auto-author-assign:GitHub动作

    name : ' Auto Author Assign ' on : pull_request_target : types : [opened, reopened] jobs : assign-author : runs-on : ubuntu-latest steps : - uses : toshimaru/auto-author-assign@v1.3.0 with : ...

    jira-auto-assign:Github操作将自动从PR分配JIRA问题

    标题 "jira-auto-assign: Github操作将自动从PR分配JIRA问题" 指示了一个集成工具或工作流程,该工具旨在自动化JIRA(一个流行的问题追踪和项目管理工具)与GitHub(一个广泛使用的代码托管平台)之间的交互。...

    assign-issues-action

    将问题自动分配给用户的GitHub操作 输入项 范围 必需的 描述 repo-token 真的 需要更新GITHUB_TOKEN。... - name : ' Auto-assign issue ' uses : Bugheist/assign-issues-action@main with : repo-token : ${{ sec

    auto-assign-when-review

    在IT行业中,"auto-assign-when-review" 这个标题暗示了一个自动化的工作流程,它涉及到代码审查(Code Review)过程中的自动任务分配。在这个场景下,开发团队可能使用了一个工具或者自定义脚本,当一个新的代码...

    ios_assign,retain和copy详解

    在iOS开发中,Objective-C语言提供了@property关键字来声明属性,并且可以在属性声明时指定不同的内存管理行为,主要涉及到assign、retain和copy这三个关键字。为了深入理解这三者的区别,首先需要了解Objective-C的...

    对于Retain和Assign属性的理解

    这个模型中,`Retain`和`Assign`是两个重要的属性,它们决定了对象间的引用计数如何处理。本文将深入探讨这两个属性,以及它们在内存管理和对象生命周期中的作用。 首先,`Retain`属性是Objective-C中一种常见的...

    BAPI_ACC_DOCUMENT_POST增强

    SAP系统中的BAPI_ACC_DOCUMENT_POST增强 在SAP系统中,会计凭证过账时,需要将预留预算清掉,但是在接口中没有该字段。为了解决这个问题,可以使用BAPI_ACC_DOCUMENT_POST中的EXTENSION2传入值来实现。下面是实现的...

    object-assign_Objectassign_

    《深入理解JavaScript中的Object.assign与对象合并》 在JavaScript中,`Object.assign`是一个非常实用的方法,用于合并多个源对象的属性到一个目标对象中。这个功能在开发过程中经常被用到,特别是在处理数据合并、...

    BAPI-ACC-DOCUMENT-POST 结构字段扩展

    ASSIGN COMPONENT 'ITEMNO_ACC' OF STRUCTURE <l_struc> TO <l_field>. READ TABLE c_accit WITH KEY posnr = <l_field> INTO wa_accit. IF sy-subrc IS INITIAL. MOVE-CORRESPONDING <l_struc> TO wa_accit. ...

    Verilog中-reg和wire-用法和区别以及always和assign的区别.pdf

    在Verilog硬件描述语言中,wire和reg是两种基本的数据类型,而always和assign是两种常用于给变量赋值的关键字。理解他们的用法和区别对于编写正确且高效的Verilog代码非常重要。 首先,wire和reg数据类型的区别非常...

    retain和copy还有assign的区别

    ### retain、copy与assign的区别详解 #### 一、前言 在Objective-C中,了解`retain`、`copy`和`assign`这三个属性对于管理内存至关重要。这些属性主要用于定义对象属性时,它们决定了如何处理对象的引用。本文将...

    auto-assign-owner-action:Github Action-自动将所有者分配给PR

    自动指派拥有者动作 此操作将拉取请求的所有者添加为受让人(如果尚不存在) 输入项 ... uses: danielswensson/auto-assign-owner-action@v1.0.1 with: github-token: ${{ secrets.GITHUB_TOKEN }}

    前端开源库-es-object-assign

    **前端开源库-es-object-assign** 是一个针对JavaScript编程中的对象合并问题的开源库,它在ES2015(也称为ES6)环境中提供了一种友好的解决方案。在JavaScript中,对象是引用类型,因此直接复制对象时,只会复制...

    assign_matlab里的assig_matlabassign_全局指派_匈牙利算法_

    《MATLAB中的assign_matlabassign_全局指派_匈牙利算法详解》 在MATLAB编程环境中,"assign_matlabassign_全局指派_匈牙利算法"涉及到的是一个优化问题的解决方法,特别是用于处理任务分配或资源匹配的问题。这篇...

    maven 3.5.0 Cannot assign configuration entry 'pluginArtifacts' with value '${pl

    标题 "maven 3.5.0 Cannot assign configuration entry 'pluginArtifacts' with value '${pl" 描述了一个在使用 Maven 3.5.0 版本时遇到的问题,该问题涉及到配置项 'pluginArtifacts' 的赋值错误,错误信息显示尝试...

    Learning to Assign Orientations to Feature Points

    "Learning to Assign Orientations to Feature Points"的研究工作聚焦于改进特征点方向的计算方法。传统的特征点方向分配通常基于局部梯度信息,例如SIFT(尺度不变特征变换)算法。然而,这种方法可能会受到噪声、...

Global site tag (gtag.js) - Google Analytics