Event-Based (3F0) versus Period-Based (BEI) for Product Cost Collectors

来源SAP 官网

Event-Based Production Cost Posting (scope item 3F0) is introduced to enable real-time insights and enriched information for product cost collectors in Production Accounting. It achieves real-time product costing and parallel valuation for group and local accounting standards in support of Parallel Accounting. It’s offered as a replacement for the traditional solution Period-End Closing - Plant (scope item BEI), which is deprecated starting from <pname conkeyref="loio163a8772470142f8a27da3efe8c859f2/S4H-PRODUCT"/>.2408.

Below is a detailed comparison between 3F0 and BEI for product cost collectors:

Features

3F0: Product Cost Collectors with Event-Based Production Cost Posting (primary approach)3F0: Product Cost Collectors with Manual Settlement (alternative approach)BEI: Period-End Closing - Plant (deprecated)
Usage suggestion

You want to benefit from parallel ledgers and multiple currencies available in Parallel Accounting.

You want to drive your business with real-time analytical insights while reducing the period-end closing workload for controllers.

In most cases, your business operations follow the expected sequence.

See more details in 3F0: Production Costs - Event-Based (Recommended).

You want to benefit from parallel ledgers and multiple currencies available in Parallel Accounting.

However, you want to reduce the overwhelming settlement documents due to the following:
  • Backflush is used massively.

  • Cost collectors are rather short-lifecycle.
  • Logistic operations cannot always follow the expected sequence.

See more details in 3F0: Production Costs - Event-Based (Recommended).

Deprecation announced. Please switch to 3F0 by the end of year 2025.

See more details in Transition from Period-Based to Event-Based for Product Cost Collectors.

Settlement documents postedAlong with each business transaction, such as raw material issuing, activity confirmation, delivery to stock, and so on.Manually settled, usually when production cycle is finished.During period-end closing activities

Period-End Closing Steps

  1. Check and process exceptional orders in apps Postprocess Event-Based Postings - Overhead Calculation and Postprocess Event-Based Postings - Product Costing or their equivalent jobs.

  2. Calculate WIP quantity using job WIP Quantity Calculation for Actual Costing: Event-Based Order and PCC (required if 33Q is activated).

Note

After resolving all the errors and executing the WIP quantity job, you can proceed with actual costing run (if scope item 33Q is activated). For more information, see Actual Costing.

  1. Run Overhead Calculation - Actual (CO43) or job Overhead Calculation: Order and PCC.

  2. Settle the orders using job Manual Settlement: Event-Based Order and PCC.

  3. Calculate WIP quantity using job WIP Quantity Calculation for Actual Costing: Event-Based Order and PCC (required if 33Q is activated).

Note

After resolving all the errors and executing the WIP quantity job, you can proceed with actual costing run (if scope item 33Q is activated). For more information, see Actual Costing.

  1. Overhead Calculation

  2. WIP Calculation
  3. Variance Calculation
  4. Settlement

Note

After finishing the above closing steps, you can proceed with actual costing run (if 33Q is activated).

WIP Calculation

Based on WIP calculation settings, including WIP calculation control, source and account determination, in configuration Event-Based WIP and Variance Posting.

Total WIP posted in B/S (as journal entries in ACDOCA) with no WIP breakdown and separate CO documents or tables. See Event-Based WIP and Variance Posting.

Based on WIP results analysis key and results analysis version settings.

Calculated in WIP calculation run (KKAX and KKAO) and posted in settlement run (KO88 and CO88H).
  • Total WIP posted in B/S (as journal entries in ACDOCA)

  • WIP breaks down by results analysis cost elements (controlling object in COSB).
Target Cost Calculation
  • Calculated in variance calculation run (KKS5)

    Saved in tables COSS and COSP.

Variance Calculation

Based on variance category settings in configuration Event-Based WIP and Variance Posting.

Calculated and posted with business transactions such as goods issue, activity confirmation, and goods receipt.
  • Total variances as journal entries in ACDOCA

  • Variance category denoted by SLA line item type in origin cost elements. For journal entries in ACDOCA, first offset PRD line items and then split into category line items in the same document.

Based on variance key and variance variant settings.

Calculated in variance calculation run (KKS5 and posted in order settlement run (KO88 and CO88H).
  • Total variances as journal entries in ACDOCA

  • Variance category in origin cost elements (controlling object in COSB).
Ledger and currencies
  • Based on company code setting for each ledger.

  • Support parallel ledgers (multiple ledgers).

  • Support legal view and group view.

    Note

    Group view is currently supported for pilot customers.

  • Support alternative fiscal year variants in same company code for different ledgers.
  • Support company code currency, group currency, and freely defined currencies. All currencies are calculated in parallel.

See Parallel Accounting.

  • Based on CO version which is assigned to the leading ledger.

  • Support the leading ledger only.
  • Support legal view only.
  • Support one fiscal year variant, which is company code specific.
  • Support two currencies: controlling area currency (group currency) and company code currency (object currency).

    Note

    Controlling area currency is the base currency while company code currency is translated based on the exchange rate type.

Solution Enablement

3F0: Product Cost Collectors with Event-Based Production Cost Posting (primary approach)3F0: Product Cost Collectors with Manual Settlement (alternative approach)BEI: Period-End Closing - Plant (deprecated)
Scope Item3F0 (Standard)BEI (Deprecated)
Business Catalogs
  • SAP_FIN_BC_PRD_EB_REP_PC (Event-based reporting)

  • SAP_FIN_BC_PRD_EB_PED_PC (Event-based period-end activities)

  • SAP_CA_BC_IC_LND_FIN_PRD1_PC (Event-based configuration)

  • SAP_FIN_BC_PRD_MDT_PC (Production cost accounting - master data)
  • SAP_A4C_BC_DEV_TST_FIN_PRD_PC (Released CDS views)

  • SAP_FIN_BC_PRD_PB_REP_PC (Period-based reporting)

  • SAP_FIN_BC_PRD_PB_PED_PC (Period-based activities)

  • SAP_CA_BC_IC_LND_FIN_PRD0_PC (Period-based configuration)

  • SAP_FIN_BC_PRD_MDT_PC (Production cost accounting - master data)
  • SAP_A4C_BC_DEV_TST_FIN_PRD_PC (Released CDS views)

Configuration Activities
  • Define Repetitive Manufacturing Profiles
  • Define Assignment

  • Define Cost-Accounting-Relevant Default Values for Order Types and Plants (Assign key MBMF03)

ApplicationsReporting: Reporting:
Period-end activities: Period-end activities:

Period-end activities:

Restrictions

3F0: Event-Based Production Cost Posting (primary and alternative approaches)BEI: Period-End Closing - Plant (deprecated)
Restrictions
  • Make-to-stock (MTS) production with valuated sales order stock

  • Engineer-to-Order (ETO)
  • Product material with valuation split
  • Cross-company production (with warning message)
  • Settlement receivers with a mixed usage of MAT (material) and non-MAT receivers
  • Engineer-to-Order (ETO)
  • Product material with valuation split
  • Settlement receivers with a mixed usage of MAT (material) and non-MAT receivers

Related Information 

Transition from Period-Based to Event-Based for Product Cost Collectors

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值