Skip to main content

SAP Note 1946054 SAP Simple Finance, on-premise edition: Transaction codes and programs - Comparison to EHP7 and EHP8 for SAP ERP 6.0

SAP Note 1946054 focuses on the changes in transaction codes and programs within the AC, CO, FI, AA, and FIN application areas after installing the SAP Simple Finance on-premise edition. It indicates that compared to EHP7 and EHP8 for SAP ERP 6.0, some have been removed or replaced. SAP suggests referring to SAP Note 2119188 for an overview of supported functions and compatibility. Solutions are provided for different scenarios such as CO-OM planning transactions and BW-Extractors. The affected items in Asset Accounting can be found in its release notes. 

1946054 - SAP Simple Finance, on-premise edition: Transaction codes and programs - Comparison to EHP7 and EHP8 for SAP ERP 6.0

Symptom

With the installation of the SAP Simple Finance on-premise edition certain transaction codes and programs in the application areas of AC, CO, FI, AA and FIN - compared to EhP7 for SAP ERP 6.0 - have been removed and partially replaced with newer transactions, programs or WebDynpro applications.

SAP recommends you to read the SAP Simple Finance release scope information in SAP Note 2119188 for a general overview on supported functions and compatibility information.

Note that with SAP Simple Finance the logic of SAP General Ledger (New GL) is used. Therefore transactions of classic General Ledger have to be replaced by the relevant transactions from New General ledger. These transactions are not explicitly mentioned in this note.

Transactions, programs and WebDynpro applications which are not supported or replaced by newer applications in SAP Simple Finance are listed in the page List of Transactions, Programs and WebDynpro Applications Not Supported or Replaced by Newer Applications in SAP Simple Finance.

Other Terms

SAP Accounting powered by SAP HANA, SAP AC on HANA, SFIN, SFIN_OBJECT_VISIBLE, Simple Finance, Out of scope, disabled transactions

Solution

Since release SAP Simple Finance, on-premise edition 1503 (formerly named SAP Simple Finance add-on 2.0):

Classic CO-OM planning transactions instead of SAP BPC optimized for SAP S/4HANA

In case you cannnot transition to SAP BPC optimized for SAP S/4HANA in the short-term, but have strong reasons to continue to use the classic CO-OM planning functions, you may apply the modifications as indicated in SAP Notes 2142732 (CJ40, CJ42), 2142447 (KP06, KP07), 2148356 (KPF6, KPF7), 2135362 (CJR2, CJR3) in SAP Simple Finance.

From SAP S/4HANA 1511 these transactions have been reenabled, but are not included in the SAP Easy Menu. Please be aware that the classic planning functions update the totals tables in Controlling rather than the new planning table (ACDOCP) available from SAP S/4HANA 1610. This means that legacy reports and follow-on processes will continue to work but that Fiori apps are based on the new table.

BW-Extractors and SAP BPC optimized for SAP S/4HANA

Customers that in the past used BW-extractors to extract and report FI-GL plan data will as of now make use of the SAP BPC optimized for SAP S/4HANA functionality. This new planning application serves to record plan data for FI and CO. In order to activate the SAP BPC optmized for SAP S/4HANA functionality, check SAP Note 1972819. The documentation can be found here: http://help.sap.com .

Follow the path: help.sap.com/sfin200 > Application Help > SAP ERP (Choose your language)  > SAP ERP Central Component > SAP Simple Finance, on-premise edition > Integrated Business Planning for SAP Simple Finance, on-premise edition

The classic GL planning functions can be reactivated for a transition period by following the instructions in the SAP Note 2253067.

Asset Accounting

The affected transactions, programs and WebDynpro applications and its replacements are listed in the release notes for Asset Accounting:

Release, SPLanguageLink
sFIN 1.0, SP00DE

http://help.sap.com/saphelp_sfin100/helpdata/de/a5/9b8d5389a7f37ae10000000a44176d/content.htm?frameset=/de/68/79b05278636656e10000000a445394/frameset.htm&current_toc=/de/dc/e7d353ca9f4408e10000000a174cb4/plain.htm&node_id=27&show_children=false

 EN

http://help.sap.com/saphelp_sfin100/helpdata/en/a5/9b8d5389a7f37ae10000000a44176d/content.htm?frameset=/en/68/79b05278636656e10000000a445394/frameset.htm&current_toc=/en/dc/e7d353ca9f4408e10000000a174cb4/plain.htm&node_id=27&show_children=false

sFIN 2.0, SP00DE

http://help.sap.com/saphelp_sfin200/helpdata/de/ce/fbe15459e0713be10000000a44176d/content.htm?frameset=/de/6f/bf8f546ac0c164e10000000a44176d/frameset.htm&current_toc=/de/55/4b6154b6718c4ce10000000a4450e5/plain.htm&node_id=12

 EN

http://help.sap.com/saphelp_sfin200/helpdata/en/ce/fbe15459e0713be10000000a44176d/content.htm?frameset=/en/6f/bf8f546ac0c164e10000000a44176d/frameset.htm&current_toc=/en/55/4b6154b6718c4ce10000000a4450e5/plain.htm&node_id=12

Change log:

[19.12.2017] Update of product name for planning and changes to planning with SAP S/4HANA 1511 and 1610

[18.05.2015] Product name change from SAP Simple Finance add-on 2.0 to SAP Simple Finance, on-premise edition reflected

[04.03.2015] Note is now relevant for Simple Finance add-on 2.0

[18.06.2014] Update official name.

[20.06.2014] Added paragraph for Integrated Business Planning

[23.10.2014] Re-activated CO-Masterdata transaction for Cost Center, Order, Activity type (single maintenance and group maintenance); see note 2084604

[07.11.2014] Transactions KB33 and KB34 have been replaced by KB33N and KB34N



Labels:

Comments

Post a Comment

Popular posts from this blog

MMPV_DATE_CHECK: Error occurred (SAP Note 1082841) how to solve

SAP Note 1082841 - MMPV/Close Periods : Prevent shifting to a future period by mistake You must backup the database before executing following program or function in the Production system! Symptom When running MMPV/ Close Periods, prevent shifting to a future period by mistake (for example, a common mistake is running MMPV twice at the beginning of a month). Other Terms MMPV, MMPI, MARV, period roller, period shift, material ledger, MMPV_READ_NOTE, MMPV_DATE_CHECK, T001, PERIV Reason and Prerequisites In the event that MMPV is mistakenly executed twice at the beginning of a period, the active period could be shifted to a future period. As a consequence, system would accept goods movements with a posting date pointing to this wrong future period. To revert wrong period shift and correct such posting errors is difficult, especially when Material Ledger is active. Solution This note provides a feature to prevent using MMPV to shift into a future period.  The future period is defi...
Post a Comment
Read more

SAP How to mass close open sales orders (Partially or Not Executed)

Sometimes we need to mass close open sales orders (Partially or Not Executed). Using VA02 to close them one by one is inefficient. Method 1: You can use the TCODE MASS . Method 2: You can also use the  TCODE VKM4  to close all open orders. Firstlly use VA06 to choose what SO you wana to mass close, then copy the SO number to VKM4, and execute. Select all item and click Reject.
Post a Comment
Read more

S/4 HANA create or modify PO Error WY 163 - no contact person found

  Symptom You are creating purchase order (PO) and you get terminating message "Express document 'Update was canceled' when user releasing the document and hence output messages automatically processed due to dispatch time 4 settings, or you use dispatch time 3 and using ME9f for output sending. Or you are using S/4HANA Output Control with dispatch time 2 and the output ends in error or similar termination visible. Further details from canceled update in transaction SM13 shows message is from class WY with number 163 and text "no contact person found". Environment Materials Management (MM) SAP ERP Central Component SAP ERP SAP enhancement package for SAP ERP SAP enhancement package for SAP ERP, version for SAP HANA SAP S/4HANA Cause The causing part is the output processing program, very likely the standard SAPFM06P program or its unmodified custom copy, as it has checks about plant and assigned customer master nr.: The root cause is that for the PO's receivi...
Post a Comment
Read more

SAP Error message FPUIFB086: Could not start Layout Designer (see long text) Please read SAP Note 1121176

SAP Error message FPUIFB086: Could not start Layout Designer (see long text) It means SAP require to open Adobe LiveCycle Designer locally. But your PC do not install any version of Adobe LiveCycle Designer. Form SAP Note 1121176 is obsoleted, and LiveCycle Designer 8.0 is quite an old release and newer Windows operating systems are not supported (for example Windows 7/Windows 8). Please use Designer 9.8 (SAP note 1658830) or higher instead of Designer 8.0. SAP Note 1658830 Adobe LiveCycle Designer 9.8 - Installation Symptom You want to install Adobe LiveCycle Designer (LCD) 9.8 on your local computer or upgrade your existing installation. Other Terms Adobe Document Services, ADS, Adobe LiveCycle Designer, SAP Interactive Forms by Adobe, PDF form Reason and Prerequisites You can use Adobe LiveCycle Designer 9.8 with the following versions of Adobe Document Services (ADS): SAP NetWeaver 7.31 and higher For lower releases of SAP NetWeaver, see SAP Note 1317925. This describes the ret...
Post a Comment
Read more

Newest version of Adobe LiveCycle Designer 11.0 download

As SAP Note 1121176  descripts, Adobe LiveCycle Designer 8.0 is quite an old release and newer Windows operating systems are not supported (for example Windows 7/Windows 8). Please use Designer 9.8 (SAP note 1658830) or higher instead of Designer 8.0. The newest version of Adobe LiveCycle Designer is 11.0.  SAP release a patch at 17.07.2024. PL 28 for ADOBE LIVECYCLE DESIGNER 11.0 Adobe LiveCycle Designer 11.0 Click here to download. PL 28 for ADOBE LIVECYCLE DESIGNER 11.0 Click here to download.
Post a Comment
Read more