In Controlling, the Actual line items due to Technical changes with SAP Simple Finance: Actual data of COEP is stored in ACDOCA in value types 4&11 (4 -Actual and 11-Statistical Actual). Required actual data for long running orders/projects from COSP_BAK and COSS_BAK, is stored in table ACDOCA. Currently, the header table COBK is written as before. The target is to replace COBK through BKPF. Table COBK is replaced by Table BKPF. Compatibility views V_TABLENAME (e.g. V_COEP) are provided in order to reproduce the old structures. Access to data in the old tables is still possible via the views V_TABLENAME_ORI (e.g. V_COEP_ORI).
Technical changes in controlling with SAP HANA Simple Finance. Actual data of COEP (value types 04 & 11) Required actual data orders/projects from COSP_BAK, COSS_BAK Compatibility views in order to reproduce the old structures Access to data in the old tables Value types other than 04 & 11 still stored in Header table COBK.
CO Postings without specifying ledger groups in Simple Finance, EC-CS as before with New G/L real time integration, but now including secondary cost (G/L accounts). The system works directly with the original CO activities like RKU1 instead of using the activity "COFI". True False.
CO Compatibility Views Provide Non-Disruptiveness due to: Access to table COEP is redirected via the view V_COEP to the new Universal Journal Entry. Access to table ACDOCA is redirected via the view V_COEP to the new Universal Journal Entry.
CO Compatibility Views Provide Non-Disruptiveness due to: Any custom ABAP programs that read table COEP directly via select statements continue to run as before. Any custom ABAP programs that read table ACDOCA directly via select statements continue to run as before.
In Controlling, line items Compatibility Views Provide Non-Disruptiveness because: Any custom ABAP programs that read table COEP directly via select statements continue to run as before. Access to table COEP is redirected via the view V_COEP to the new Universal Journal Entry. Access to table ACDOCA is redirected via the view V_COEP to the new Universal Journal Entry.
CO Postings without specifying ledger groups in SAP HANA Simple Finance ACDOCA is posted via the Accounting Interface similarly to FAGLFLEXA (New G/L) in the past. ACDOCA stores full detail. Former COEP, FAGLFLEXA, ANEP, MLIT etc. data are stored in ACDOCA BSEG is only written in case open item managed accounts are affected (e.g. usually for cross company postings). Cost Based CO-PA works as before (with the SAP HANA accelerators of course).
CO Postings without specifying ledger groups in Simple Finance, PCA, Fl-SL work as before. Where the Fl-SL was posted via activity "COFI" (real time integration CO-FI), now secondary cost (G/L accounts) are posted directly and there is no mapping to a primary cost element. True False.
With Simple Finance, CO processes are enabled to post into ledger groups and you can also specify the document type. True False.
With Simple Finance, CO processes are enabled to post into ledger groups but you can not specify the document types. True False.
With Simple Finance CO: Processes are enabled to post into ledger groups. You can also specify the document types. On UI this is enabled for KB11N, KB41N and KB15N. Other processes can be configured in the IMG to post with ledger groups. Processes are not enabled to post into ledger groups. You can not specify the document types.
--> CO Postings when specifying Ledger groups ACDOCA is posted in any case taking the respective ledgers into account. BSEG is only written in case open item managed accounts are affected (e.g. for cross company postings), and the ledger group contains the Leading Ledger. Other components (PCA, Fl-SL, Cost Based CO-PA, industry solutions like public sector and joint venture accounting etc.) are only posted if the ledger group contains the Leading Ledger. BADI_FINS_APPL_RELEVANCE allows customers to overrule this behavior. Other components (PCA, Fl-SL, Cost Based CO-PA, industry solutions like public sector and joint venture accounting etc.) are only posted, if the ledger group contains the Non-Leading Ledger. BADI_FINS_APPL_RELEVANCE allows customers to overrule this behavior.
CO Postings when specifying ledger groups, BSEG is only written in case open item managed accounts are affected (e.g. for cross company postings) and the ledger group contains the Leading Ledger. True False.
CO Postings when specifying ledger groups, other components (PCA, Fl-SL, cost based CO-PA, industry solutions like public sector and joint venture accounting etc.) are only posted, if the ledger group contains the Non-Leading Ledger. True False.
CO Postings when specifying ledger groups, BSEG is only written in case open item managed accounts are affected (e.g. for cross company postings) and the ledger group contains the Non-Leading Ledger. False True.
--> In Controlling with Simple Finance, we should: Align Fiscal Year Variants between controlling areas and the assigned company codes. Define the Document Type for CO postings. Define one or more Document Type Mapping Variants (pre-delivered: 000001) and assign these to the company codes. Specify default ledger group. Define Intercompany Clearing Accounts for CO cross company postings,.
--> In Controlling with Simple Finance: Specify default ledger group. Ledger group is only for manual re-postings on the UI (KB11, KB41). Ledger group is only for automatic re-postings on the UI (KB11, KB41). If no ledger group is entered in CO transactions the default ledger group is taken. If no default ledger group is configured all ledgers are updated.
In Controlling with Simple Finance, Define the document type for CO postings and define one or more Document Type Mapping Variants (pre-delivered: 000001) and assign these to the company codes. True False.
In Controlling with Simple Finance, we don't need to align Fiscal Year Variants between controlling areas and the assigned company codes. False True.
In Controlling with Simple Finance, Fiscal Year Variants of all productive controlling areas and their assigned company codes have to be the same. True False.
In Controlling with Simple Finance (check and Adopt Fiscal Year Variants), Fiscal Year Variants of all productive controlling areas and their assigned company codes can be the same. False True.
With the Simple Finance On-Premise Edition 1503 all Controlling business transactions use document types. Controlling now uses document types when posting to FI. True False.
With the Simple Finance On-Premise Edition 1503 all Controlling business transactions use document types. It is Not recommended to have a separate document type for Controlling postings with only the indicator "GL account" set in the account type. False True.
--> With regards to defining Document Type Mapping Variants for CO Business Transactions for postings in Controlling with Simple Finance: Assign the document type for postings in Controlling to a document type mapping variant. You Should Copy the provided sample to a customer specific entry. The entry will be created automatically in case you already use real-time integration in new G/L, Assign the document type for postings in Controlling to a document type mapping variant in FI.
With regards to defining Document Type Mapping Variants for CO Business Transactions for postings in Controlling with Simple Finance - The document types can be specified on the following levels: Company code, via different document type mapping variants. Controlling business transactions. Normal postings and cross-company postings. At Controlling level.
--> For Controlling in Simple Finance, as Parallel actual versions are currently not supported; so Version 0 must be assigned to the leading ledger in all company codes assigned to the controlling area. Therefore CO reads from the leading ledger (reporting and allocations). CO writes to the manually specified ledger group. In case no ledger group is entered and no default ledger group is set in customizing it is posted to all ledgers. Usually CO should write into Leading Ledger (because this is the source for reading).
For Controlling in Simple Finance, as Parallel Actual versions are currently not supported; so how CO reads the actual data? Version 0 must be assigned to the leading ledger in all company codes assigned to the controlling area. Therefore CO reads from the leading ledger (reporting and allocations). No Version 0 needs to be assigned to the leading ledger as CO reads from leading ledger automatically.
--> For Controlling in Simple Finance, CO writes to the manually specified ledger group. Usually CO should write into Leading Ledger (because this is the source for reading). True False.
--> For Controlling in Simple Finance, default settings are necessary for postings, where there is no possibility to manually define the document type and ledger group in the Controlling business transaction, which ledger should controlling update in this case? Leading Ledger 0L Non Leading Ledgers All Ledgers.
For Controlling in Simple Finance, regarding defining intercompany clearing accounts Posting transfers between cost objects belonging to different company codes now update the Universal Journal. You need to assign Clearing G/L accounts for the transaction and for each combination of Company Codes such postings occur.
For Controlling in Simple Finance, posting transfers between cost objects belonging to different company codes now update
the Universal Journal. True False.
What are the correct Controlling-Technical changes with simple finance? Actual data of table COEP (only Value types-04&11) is stored in ACDOCA. The header table COBK is written as it before. COBK table values replaced with BKPF. Access to data in old tables is still possible via views V_<TABLENAME>_HANA. Non-Actual items are stored in COEP, COSP_BAK, COSS_BAK (Other than Value types - 04 & 11).
With simple finance CO processes are enabled to post into the ledger groups, but can't specify the document type. True False.
The Fiscal year variants of all productive controlling areas and their assigned co. codes should be same Yes No.
--> What is True about CO Ledger groups, document types and versions? You can define your own document types for CO postings for each co. code. Normal postings and cross-company postings can have separate doc. types per business transaction. Parallel actual versions are currently not supported. Version 0 can be assigned to any ledger for the co. codes assigned to controlling area.
--> Technical Changes to the ML with SAP Simple Finance:
Usage of Material Ledger for parallel currencies and parallel valuation purpose, which one(s) Not True? Tables MLIT, MLPP, MLPPF, MLCR, MLCRF, MLCD, CKMI1, BSIM is now stored in ACDOCA. Compatibility views V_TABLE NAME (e.g. V_ MLIT) are provided in order to reproduce the old structures. Access to old data in tables still possible via the views V_TABLE NAME_ORI (e.g. V_MLIT_ORI). MLHD, MLIT, MLPP, MLCR still keep prima nota information, in case of manual price changes or material debit/credit. MLHD data is not stored in BKPF. MLHD data is stored in BKPF. .
Technical Changes to the ML with SAP Simple Finance:
Usage of Material Ledger for Actual costing purpose - MLIT, MLPP, MLPPF, MLCR, MLCRF, MLCD are used as before Simple Finance? True False.
To provide more details of income statement, a refinement of posting mechanism for COGS in S/HANA, What are true? You can define multiple COGS Accounts (COGS material, COGS labor etc) and link to main COGS account. One or more cost components can be assigned to one refinement account to distinguish fixed and variable values. You can have one refinement account as a default account to redirect unassigned cost components post to this account.
Material Price Analysis (CKM3) with reference to Material Ledger in Simple Finance. Material Price Analysis (CKM3) is widely used to analyze all factors contributing to the cost of a material. Material Price Analysis initially displays data from aggregated data sets (MLCD) and then drills down to the document level (MLIT, MLPP). You can switch between valuations and currencies and navigate between periods in this view. The data is read directly from the universal journal.
--> What is Not True about Material Ledger in Simple Finance? The values of material valuation balances per inventory account in co. code currency is now included in Universal Journal. The values of material valuation balances per inventory account in multiple currencies is now included in Universal Journal. It provides option to perform multilevel actual costing using a costing run as before and now included in Universal Journal. ML provides option to perform multilevel actual costing using a costing run as before and not in scope for the Universal Journal.
--> Price Determinations in Material Ledger with Simple Finance, choose correct answers. Multiple (Parallel) Valuations - Price Determination 2, Prices and Values shown in the Material Master are taken directly from the Universal Journal. Multilevel Actual Costing - Price Determination 3, No Change - Costing Run Needed to Update Inventory Values at Period Close (not in scope for the Universal Joumal). Multiple (Parallel) Valuations - Price Determination 2, Prices and Values shown in the Material Master are taken directly from old Tables.
What are the new improvements with COPA in S/HANA? Account based COPA is fully integrated in the Universal Journal. Costing based COPA is fully integrated in the Universal Journal. SAP recommends Account based COPA approach. SAP recommends Costing based COPA approach. You can use both approaches in parallel. For derivation of customer specific profitability attributes CO-PA offers advanced derivation functionality, this can be used for both types of CO-PA.
--> Refinement of COGS in SAP Accounting powered by SAP HANA - CO-PA Line Items The cost component structure of Cost of Goods Sold (COGS) will be posted in the Account Based Profitability Analysis and Financial Accounting as well. The values are stored on line item level in the universal journal table (ACDOCA) and the accounts are updated on the basis of total costs. The COGS with fixed and variable cost will continue to be posted in the Costing Based COPA on different value fields. The contribution margin can be calculated in the Costing Based COPA. The contribution margin can be calculated in the Account Based COPA.
Due to HANA Acceleration of CO-PA - Report Execution, In both types of CO-PA, you will see a great speed improvement in processing when comparing to a non-HANA DB system. Only for Account Based. Only for Costing Based. Both Costing and Account Based.
Real-time Account Based Profitability Analysis and Reporting in Simple Finance.
Choose correct one(s): The Universal Journal as a single source of truth in Financials provides profitability attributes for every P&L line item. The Operating Concern generation appends the CO-PA characteristics to the Universal Journal. Profitability attributes are derived online. Profitability attributes can be enriched by further processes such as settlement or allocations. Reconciled Profitability Reporting only at period end (not any time).
Results Analysis for Sales Orders (Transaction: KKAKH) regarding period-end.
Which ones(s) are correct? Supports in the first release two commonly used methods 01 revenue-based RA and 03 cost-based RA (out of 17 methods). Not supported of Some Expert methods, Customer Enhancements, Multiple Result Analysis Versions, from other 15 methods.
What are SAP HANA coding options? HANA views are used to select the relevant costs from the Line item tables rather than Total tables. HANA procedures are used to handle the complicated calculation logic in the close transactions.
Settlement Transaction during period end, costs that arise from processing an order, or project (for example, costs for material, personnel or external services) are transferred to the settlement receiver specified in the settlement rule in the master record of the object. True False.
What are SAP Introduced new period close transactions in SAP Simple Finance? Result analysis on sales orders (KKAKH) WIP calculation at actual costs (KKAOH) Settlements (internal orders/projects)(KO8GH/CJ8GH) Settlements (Plant selection)(CO88H) WIP Calculation for product cost collectors and process orders. Production Variances (KKS1H).
WIP Calculation (Transaction: KKAOH): KKAOH values production orders only, at actual cost for the selected plant with defined legal valuation for a single result analysis version. Not Supported yet: Customer Enhancements, WIP calculation for product cost collectors; WIP calculation for process orders, Multiple result analysis versions.
Select correct options for new Period-End transactions(optimized) in S/HANA. Mass settlement run executed only in the background. Both (Old and new) period end transactions can be used in S/HANA. Old period end transactions are obsolete in S/HANA. New variant with reduced options (less selection criteria) must be created to use new period end transactions. .
Compare fiscal year variant check between Controlling area and FI is irrelevant in S/4 HANA Accounting. Yes No.
What is True about fiscal year variant (FYV) check in S/4 HANA migration? Controlling area FYV can be different from FI FYV. You should execute FYV check for all Co. codes. You should execute FYV check for all Controlling areas. You should execute FYV check for required Controlling areas.
In S/4 HANA overhead cost and COPA reconciliation is not required. True False.
In S/4 HANA overhead cost and COPA reconciliation have direct impact on: Balance Sheet account. Profit & Loss account. Cost center reports. None of the above.
What are the components SAP focused to remove manual reconciliation for Balance Sheet accounts. Asset Accounting. Controlling. Material Ledger. COPA.
What are the components SAP focused to remove manual reconciliation for Profit & Loss accounts. Asset Accounting. Controlling. Material Ledger. COPA.
What are the fields Not available in Asset table before SFIN? Cost center. General Ledger. Profit center. Unit of production values.
What are the fields Not available in Material ledger tables before SFIN? Profit center. General ledger. Cost center. Material code.
What is True about Material price analysis data in SFIN? All the required data derives from ACDOCA table. It helps to determine all factors contributing to the cost of material. All the required data derives from Material ledger tables.
What is possible with Refining COGS concept? More detailed income statement possible. It reflect the standard cost component split on the GL Account. It helps to distinguish fixed and variable values. More detailed Balance sheet possible.
Many period close activities redesigned to improve processing speed in S/4 HANA finance. True False.
How SAP improved the processing speed of new period-end closing activities? With HANA Views. With HANA Procedures. With HANA Views and Procedures. With HANA database tables.
What is True about HANA Views and Procedures in S/4 HANA finance? HANA Views are used to select relevant cost from the line item tables. HANA Views are used to select relevant cost from the total tables. HANA Procedures are used to handle complicated calculation logic.
--> New Result Analysis for Sale Orders (KKAKH) supports below methods. Revenue based Result Analysis. Cost based Result analysis. It supports all Results Analysis without restriction. Quantity based Result Analysis.
SAP Does Not support below methods new WIP calculation (KKAOH) period-end program. Calculation of product cost collectors. Calculation of process orders. Multiple result analysis versions. Calculation of production orders.
Can you execute mass settlement runs in foreground with new settlement transactions in S/4 HANA? Yes No.
-->> Does material ledger's actual costing data store in ACDOCA table? Yes No.
What concepts are True as part of Universal journal for Material Ledger valuation in S/4 HANA Accounting? Material ledger provides balances per inventory account in multiple currencies - these values are now included in the universal journal. Classic material ledger provides balances per inventory account in co. code currency - these values are now included in the universal journal. Material ledger provides option to perform multi-level actual costing by using costing run as before - not in scope for the universal journal. Costing run needed to update inventory values at period close is part of valuation - not in scope for the universal journal.
Can you post CO transactions to non ledger group without leading ledger assigned? Yes No.
|
