3599914 - About the transition from the scope item BEI to the scope item 3F0

Symptom

From S/4HANA Cloud, public edition CE2105 onwards, SAP released new scope item 3F0 (Event-Based Production Accounting) as the successor for the scope item BEI (Period-End Production Cost Posting). The new scope item 3F0 offers enhanced features and improved functionality for product cost posting. The scope item BEI has been deprecated since SAP S/4HANA Cloud, public edition 2408, and plans to be decommissioned in SAP S/4HANA Cloud, public edition 2602. This means the functionalities related to the scope item BEI will no longer be available after the decommission. The transition from the scope item BEI to the new scope item 3F0 is required for your current processes.

Environment

SAP S/4HANA Cloud Public Edition

Cause

The scope item BEI deprecation.

Resolution

Kindly refer to the following documentation and resources.

SAP Community blog:

English Version: Transition to Event-Based Production Accounting in SAP S/4HANA Cloud

Chinese Version: 采取行动：过渡到 SAP S/4HANA Cloud 中基于事件的生产成本过账3F0

SAP Note 3042687: SAP S/4HANA Cloud: Transition from Period-End Closing (BEI) to Event-Based Production Accounting (3F0)

SAP Note 3042082: SAP S/4HANA Cloud: Universal Parallel Accounting with Event-Based Production Accounting

SAP Online Help:
Transition from Period-Based to Event-Based for Manufacturing Orders

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

Kindly check below FAQs if interested:

Q1: How long can I still use BEI? At latest when should I finish the transition?
A1: For customers using Production Orders and Process Orders: Legacy BEI customers can still create new non-event-based orders until April 2026. Start from CE2602.2 upgrade, you cannot create any new non-event-based orders anymore. If you want to extend the creation of BEI orders for a limited time period because you were not able to complete the transition in time, you can do this by using the Activate Features configuration activity to deactivate feature FTGL_BEI_DEPRECATION. But please be aware that this is only possible for a few more months, the creation of BEI orders will be completely disabled in CE2608 release! For customers using Product Cost Collectors: Legacy BEI customers can still create new BEI PCC until end of April 2026. Starting from CE2602.3 upgrade, you cannot create new BEI PCC anymore without exception.

The operation business (goods movement, confirmation, etc.) and period-end execution (WIP/variance calculation, settlement) of already created BEI objects would be available until CE2702 release (Jan, 2027).

Q2: How long does the transition take?
A2: Most already transited customers spent 2-3 months until no new BEI orders were created anymore.

The already created BEI orders might go through a few more months until production cycle finishes, thus orders are closed depending on production duration of different industries, in general, half a year is sufficient.

Q3: Am I the first one to start the transition? Is there already any reference customer?
A3: There are already 100+ customers who have finished the transition starting from the year 2024.

Q4: Is there any data migration for the transition? If so, is there any data inconsistency risk?
A4: There are no data migration in the transition from BEI to 3F0. The transition means the flipping of configuration and usage change of applications.

Q5: Is there any suggested switch timing?
A5: There are no specific timing preferences. However, it is not suggested to switch around the upgrade weeks, when the configuration change projects are blocked for transportation; in addition, for 2SL customers, please carefully plan the switch time window to avoid rushing the existing open change project in the Test System.

Q6: After the production starts and it is found that the operation confirmation cannot follow the expected strict sequence, can I still switch the event-based processing key from RSEBW to ORDMS?
A6: Once the order has been settled, the event-based processing key cannot be changed anymore. You can only switch the event-based processing key before the first settlement has occurred.

Q7: If I have some BEI rework order still running, and want to settle it to a 3F0 order, is that allowed?
A7: No, BEI order and 3F0 order are technically totally different; you cannot settle BEI order to 3F0 order. In such a case, you are advised to cancel the BEI order business and create a new 3F0 rework order to settle to another 3F0 order.

Q8: In configuration activity Event-Based WIP and Variance Posting - WIP Sources definition, can material consumption (P) and material delivery (D) use the same account?
A8: No, P (Production Costs) is used to determine the increase of WIP and D (Delivered Costs) is used to determine the decrease of WIP, so they can not be the same.

Q9: In configuration activity Event-Based WIP and Variance Posting - WIP Account Determination Rule, can WIP offset account use N (non-operating) account?
A9: If you activated 3F0 long-time ago when the default content was still with the N-Account, you could keep using it. But SAP strongly suggests you to switch to P-Account (primary cost). If you are newly activated 3F0 or have already switched it to P-Account, it cannot be switched back to N-Account anymore.

Q10: In 3F0, is there any case that the production variances are not split into detail categories?
A10: If you are producing a material that is with 'V-Price Control' (moving-average price), the variance categories will not be split. Please note SAP always suggests to use 'S-Price Control' for in-house produced materials. If you want to valuate the material at the actual price, activate 33Q (actual costing) so the actual price will be revalued in the actual costing run. In addition, the variances account PRD-PRF should be using the P&L account instead of the B/S account.

Q11: In event-based variance settlement, what will happen if the production order is with additional goods issue/confirmation after the order is with status DLV/TECO?
A11: If business allows to continue doing goods issue/confirmation after the order is TECO/DLV, there is no need to revoke TECO/DLV. Another settlement document will be posted. If business restricts TECO/DLV must be revoked to do additional goods issue/confirmation; once the revoke is triggered, variance settlement document will be cancelled; later when the order is TECO/DLV again, the settlement document will be re-posted. Please note revoke TECO/DLV especially across the period is very dangerous and might be harmful to settlement; it should be done very carefully. If you foresee frequent revoke of TECO/DLV, you are suggested to use 3F0 with manual settlement instead of event-based settlement.

Q12: In event-based variance settlement, what will happen if the order has cross-period settlement and the DLV/TECO status is revoked?
A12: It is very dangerous to reopen the order with variance settlement across periods, especially if the material is using S+3 control in Actual Costing. SAP will not automatically reverse the variance settlement in such a case and leave the order in F3669 Postprocess Event-Based Posting - Product Costing for a manual decision on which period the variance should be reversed. Ideally variance settlement document should be reversed in the original settlement period; if it is reversed in another period, the settlement result in that period may be distorted.

Q13: What if I found missing goods issue/confirmation when the Actual Costing Run (33Q) has finished, can I still do it? Will the settlement still be triggered automatically?
A13: After Actual Costing Run (33Q) has completed, you cannot do any further posting on the production order because that won't be considered in the actual price revaluation which already happened! You need to first reverse the Actual Costing Run, then post additional goods issue/confirmation, and re-run the Actual Costing Run (33Q) again.

Q14: What if I forgot to calculate WIP quantity when the Actual Costing Run (33Q) has finished? Will the WIP be revalued?
A14: No, in 3F0, WIP quantity calculation currently is a separate job to be executed manually before the Actual Costing Run to ensure WIP is revalued at the actual price. If that is missing, you need to first reverse the Actual Costing Run, then calculate WIP quantity, and re-run the Actual Costing Run.

Q15: How is actual cost rate determined and reflected on production order in 3F0?
A15: The actual cost rate could be either calculated by running app/job Actual Cost Rate Calculation - Cost Centers (KSII) or manually maintained in app Manage Cost Rates - Actual. The activity consumption is revaluated using the actual cost rate only in Actual Costing Run (33Q) on public cloud. The order will not be revaluated with the actual cost rate, neither in 3F0 nor in BEI.

Q16: Is it a must to assign a costing sheet? If customer has no overhead surcharge, can I remove it?
A16: Overhead surcharge is not mandatory. If that is not needed, feel free to remove the costing sheet from the planned costing variant.

Q17: If I use an event-based costing sheet to surcharge overhead cost, is that calculated based on the planned rate or the actual rate? If the planned rate is used, what if I want to change it in the production cycle?
A17: Event-based overhead uses the planned rate to calculate overhead costs. Currently, it cannot be adapted to the actual. The workaround could be to manually allocate costs on production order from cost center. If you have such a strong requirement, please raise CIP to SAP.

Q18：Is it possible to have non event based orders even when scope item BEI is not active?

A18: Potential yes, when the "Event-Based Processing Keys" is set as 'Empty', orders with empty key will be considered as non event based order, we will enhance the check to avoid such empty key in the future. Kindly consider to maintain the key as 'ORDMS' if you would like to have manually settlement.

Keywords

3F0, BEI, transition from BEI to 3F0, event based, migrate from BEI to 3F0. , KBA , CO-PC-OBJ-2CL , Cost Object Controlling (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions