SAP QA.pptx
- 1. Hi I’m Sathyamoorthy I’m from Andhrapradesh I did my MBA in 2007 with a Bcom (2004) background I have 12+ years of experience in total, out of which 5 years in IT field that is SAP FICO. I have experience in 1 implementation and 2 supporting projects My recent company is Cognizant. Where I involved in one implementation and one support project. In implementation project, along with my lead, I did involved in workshops like getting the AS IS data from the client and preparing TO BE documents as per the requirement from the client. Creating enterprise structure. Also did configuration and customization of sub modules like AP, AR, AA ,GL, and Controlling area part like cost center creation, profit center creation.
- 2. Projects: 1. In Wipro – Cargill – Support/Maintenance - Mar 2017 – Oct 2018 Agriculture services, Animal nutrition production, food & Beverages manufacturers. We are into Food & Beverages division (caramel, chocolates, corn flakes, medical based food products and many) I observed the final stage of implementation when the senior consultants were preparing, and I was into support for the project, where I used to take are of day to day tickets. 2. In Cognizant – Leo Pharma – Implementation & Support - Nov 2018 to May 2022. Its based out of Denmark. I’m part of Leo Pharma US – which produces medicines, ointments, injections, medical equipment related to dermatology. – I joined in the realization part were I have prepared as is documents, based on the client requirement we have prepared to be doc to map those info into the SAP. And prepared organization structure, configuration steps like GL, AP, AR, AA and CO, integration between FIMM and FISD. Currently I’m into supporting consultant into the same projects.
- 3. What is APP in SAP? Automatic Payment Program (APP) is used to make the payment to the vendor/customer automatically - F110 It is used to find the dues/overdues of invoice and to process the list of vendors and customers invoice and make the payments in one go. And it can not be used for cross company payments with different countries with currencies. Settings for APP (FBZP): 1. Set up all company codes 2. Set up paying company codes 3. Payment method in country 4. Payment method in company code 5. House bank set up (FI12) 6. Bank determination
- 8. Next payment run date means that if any item is overdue before that date will be included in current payment run.
- 9. BRS / EBS (Electronic Bank Statement): OT83 BRS is reconciliation between Bank statement and GL In S4 HANA, it does with electronic bank statement with Bank GL accounts. In S4 HANA, First we need to define : OT83 ->Account Symbol (like 1. Bank Incoming GL account, 2. Bank outgoing GL account, 3. Bank Charges, 4. Interest paid, 5. Interest received, etc) -> Assign account symbol to GL accounts -> Define posting keys for posting rules -> Posting rules -> Create Transaction type -> Assign External Transaction type to posting rule. To read the statement electronically, there are different formats available such as BAI, SWIFT MT100, MT940, etc. for SAP. We need to write an interpretation algorithm as per the above formats to read the Bank statement. Based on the BTC (Bank transaction code) in the bank statement system will reconcile the transactions and post the documents accordingly. For example: Bank charges – BKCH (BTC), system will post the GL Bank charges Dr Main Bank Charges A/c Cr
- 10. DMEE stands for Extended Data Medium Exchange A data medium exchange (DME) is a data exchange file which is used to send payment information of an enterprise to banks or tax authority. Basically, these files contain financial data which can be in flat file or xml file format. Different File formats can be created for different countries and different banks based on their own norm which replaces conventional ABAP programs. Main communication structure This structure is normally used as main comfort DME file that contains header/ item etc. information and is used to build XML structure based on delivered items. DMEE Tree: - Segment Level Group - Header Level (Date/Company code/Bank Ref No. - Payment details (Seq No, HsBank, Pyr Bank acc, IFCS code….)
- 11. New GL Concept: It enable segment wise reporting It eliminates data redundancy by providing all details in total table FAGLFLEXT Leading Ledger & Non-Leading ledger It has document splitting which makes profit center reconciliation. Document splitting are 3 types 1. Active document splitting 2. Passive document splitting 3. Zero balancing doc splitting
- 12. Leading Ledger & Non – Leading ledger: Leading ledgers are defined based on the accounting principles that are of consolidated financial statements. Only one leading ledger can be used for one company code, SAP provided default leading ledger is 0L Non leading ledger is a parallel ledgers to leading ledger this will be defined based on local accounting principles for reporting purpose.
- 13. Document splitting option which enables profit center reconciliation easy. It enables segment wise reporting a.Active Document splitting In Active Splitting the document is split according to SAP predefined rules. SAP almost supports all the business process transactions but if it doesn’t suit to any requirement the own splitting rules can be created. b.Passive Document Splitting This type of splitting is mostly occurs when the payment transaction is posted for a vendor invoice. Now system splits the payment document bases on how the vendor invoice was split in place already. c.Zero balance Doc splitting When the amounts within financial documents are not able to balance out to Debit of Profit Centre and Credit of Profit Centre which does not Net Off as its own, SAP then automatically generates new line item to balance the document. Account Amount Profit Centre Vendor A/C -11,000 Expenses 1 8,000 PC – X Expenses 2 2,000 PC – Y Input Tax 1,000
- 14. FIMM Integration Whichever the transactions performing the material management and the transactions are involved financial are need to be defined with GL account which are specified in FIMM integration. The setup is done in OBYC settings. Valuation class – Material type Transaction Key – Posting key (BSX WRX PRD General Modifier – Further classification of Transaction key. Movement Type – Inventory movements (GR from Vendor, GI to production, GR from Production order, Goods issued to cost center)
- 15. PTP Cycle: Purchase order: (ME21N) No entry On Goods receipt: (MIGO) Inventory RM a/c Dr To GR/IR ac On Invoice receipt: (MIRO) GR/IR account Dr To Vendor a/c On Payment: (F110 or F-53) Vendor ac DR To Bank sub Ac
- 16. Movement Types: Trxn Key Gen. Modfr N/APurchase order No journal entry 101GR from Vendor Inventory RM Dr BSX Price difference Dr/Cr PRD To GR/IR Clearing Cr WRX N/AInvoice Receipt GR/IR Clearing Dr WRX To Vendor A/c Cr KBS 261GI to Production order RM consumption Dr GBB VBR To Inventory RM Cr BSX 201GI to Cost center RM consumption Dr GBB VBR To Inventory RM Cr BSX 101GR from Production Order Dr. Stock BSV Cr. COGM/Factory out put of prod GBB AUF FIMM Integration
- 17. FISD Integration: FISD integration is set up in T-code VKOA First, we need to define Sale area i.e., Sales Org, Distribution Channel & Division. OTC Cycle Sales Order -No entry PGI -COGS ac Dr – GBB – VAX/ VAY -Stock ac Cr - BSX Billing- Bill sent to customer -Customer ac Dr -Sales acc Cr Receipt of money- Customer Payment -Incoming Bank Acc Dr -Customer ac Cr Real SD Condition Types Statistical Condition Type PR00 Sales Price This will not have FI entries VK07 Discount Only for repoting purpose. RB00 Rebate Ex: Royalty charges VPRS Cost of goods sold EK01 Cost of sales
- 18. Assessment method & distribution method ECC vs S4 HANA GL - Universal Journal ACDOCA introduced - Extension ledger concept Prediction Ledger and Extension Ledger (underlying ledger of leading ledger), it will not get posted if post doc in leading ledger, need to post separately for reporting purpose - Unified Master Data - i.e. GL account and cost element both can be defined in FS00 - In OB52 fiscal period for cost center also included. - We can run FCR multiple times, it will override the previous run for the period. (FAGL_FCV) -Fiori app support is there AP-AR Customer master and Vendor master both are integrated in to BP, depending on the roll business partner can act as customer or vendor. AA Usage of New asset accounting is mandatory Realtime Depreciation run, we can run Depreciation multiple times Catchup methodology (no smoothing method in S4hana) Technical Clearing account
- 19. The Technical Clearing Account is a new account that has been introduced for accounts that cannot be posted to in a single ledger only. If you've set up parallel ledgers in the New General Ledger, you will know that there are certain accounts that the system will not let you post to in one ledger and not another.
- 20. LTMC is Legacy Transfer Migration Cockpit. Ready-made templates are available to upload the data. Nearly all Master/Transaction scenarios are covered in LTMC, which is introduced in S4 HANA, it can be done with the help of FIORI app. LSMW – Legacy System Migration Workbench LSMW is a older version of LTMC where it needs consultant’s involvement and it is used in ECC, also here we can create and change the template as we required.
- 21. What is CO-PA Controlling - Profitability analysis is used to evaluate the company's profit and contribution margins by market segments and strategic business units. Market Seg: product, Product grp, Customer, Customer grp, Sales region, Sales person, Profit center etc. Strategic BU: Sales org, Sales division. There are mainly 2 types of CO-PA available in S4 HANA. 1. Account Based COPA: is also known as Margin Analysis. Account based COPA stores the revenues and costs in accounts and uses revenue and cost elements. This type of analysis provides the report that permanently reconciled with Financial Accounting. 2. Costing Based COPA: groups the costs and revenues according to the value fields and it provides the report with complete, temporary reconciliation.
- 22. Depreciation methods: SLM DMV Units of production Sum-of-the-Years-Digits Depreciation Method
- 23. Dunning: When the customer is failed to pay the amount as per the agreed term we will send a reminder correspondence to the particular customer, which is called dunning. In SAP the maximum reminder level is 9. First we need to define “dunning area” in Tcode OB61 (co.code/region) and then we need define the dunning procedure in Tcode FBMP. Where we define: How many dunning levels Grace period Dunning Charges Minimum amount for dunning Dunning texts Dunning procedures will be defined in Customer master (BP) Dunning can be run in F150
- 24. Asset Accounting: Depreciation Area (EC08) – which is defined based on the country specific accounting principles (i.e. US-IFRS, US-GAAP, IN-IFRS, IN-GAAP) Chart of Depreciation (OADB)– which has the list of depreciation area belongs to one country (ex: DepArea for India includes IN-IFRS & IN- GAAP or all as required by the management) Asset Class (OAOA)– Type of asset (Building, Plant& Machnry, Furniture etc) No. Ranges – Asset accounting no. ranges. Specify account determination Screen Layout Depreciation Key (AFAMA)– Methods of depreciation
- 26. AUC with Inter Order: AUC is Asset under construction where some assets are in construction phase and cost needs to capture through internal order for the time being. Once asset is fully completed then cost would be transferred to another cost object (E.g. Cost center) and settle with final asset. Internal Order Creation – KO01 Assign budget plan for IO – KO22 AUC creation – AS01 PO Creation – ME21N PO Release – ME29N Good Receipt – MIGO Invoice Receipt – MIRO Payment – F-53 Asset Creation – AS01 Settlement – AIAB Asset explore – AW01N
- 27. Primary and secondary cost element? Primary cost elements are like material costs, personnel costs, energy costs... where a corresponding GL account exists in FI..to allow costs to flow... Primary cost elements – 01-General cost/cost reducing revenues 03 – Imputed cost (% method) 04 - Imputed cost element (Actual=Target) 11 – Revenues 22 – External settlement Secondary cost elements are like production costs, material overheads, production overheads, they can be created and administered in only CO. These are used in internal cost allocation, overhead calculation, settlement transactions., it does not flow to FI... Secondary cost elements 21, 31, 41, 42, 43
- 28. Predictive ledger in SAP s4 Hana? Predictive accounting enables you to take the most up-to-date data from areas in S/4HANA outside of Finance, such as Sales; other integrated products, such as SAP Concur; or external systems, and use it to predict future results at any time Simulation Ledger An example of a simulation is a closing activity with Foreign Currency Valuations. Imagine that you would like to see an impact of foreign currency revaluation on your financial statement before actually running it.
- 29. IDoc / EDI / ALE (search WE09, create WE30) Idoc is an SAP object that carries data of a business transaction from one system to another in the form of electronic message. The purpose of an IDoc is to transfer data or information from SAP to other systems and vice versa. The transfer from SAP to non-SAP system is done via EDI (Electronic Data Interchange) subsystems whereas for transfer between two SAP systems, ALE (Application Link Enabling) is used.
- 30. Did you do any validation? Yes, client wanted to restrict certain set of customers for down payment (F-29) GGB0 Step - Prerequisites > BKPF-BUKRS = 'L100’ AND BSEG-KUNNR = '25102' AND BSEG-UMSKZ = 'A’ special gl indicator Check > BKPF-TCODE = ‘F-29’ Message : “This Customer is restricted for down payment” OB28: Assign the validation to company code
- 32. What is difference between assessment and distribution in SAP? DISTRIBUTION (KSV1-Create, KSV5-Run) Distribution was created for transfer primary costs from a sender cost center to receiving controlling objects. During distribution, only cost centers or business process can be used as sender. A distribution receiver can be a cost center, WBS element, internal order, cost object, or a business process. You can restrict the number of receiver categories in customizing. Primary Postings (such as, energy costs) are collected on a cost center, and allocated at the end of the period by means of the user-defined key. You can only distribute primary costs. During this process, the original cost element remains the same. ASSESSMENT (KSU1-Create, KSU5-Run) Assessment was created to transfer primary and secondary costs from a sender cost center to receiving controlling objects. During assessment, cost center or business processes can be used as senders. The receivers for an assessment can be a cost center, WBS element, internal order, cost object, or a business process. You can restrict the number of receiver categories in customizing. Primary and secondary posting are allocated at the end of the period by the user-defined key. During assessment, the original cost elements are summarized into assessment cost elements (secondary cost element category = 42)
- 33. Month end: Posting period open and close FCR Asset Depreciation posting WIP calculation BRS Accruals and Deferrals Process recurring entries Clear open items (GL, AR, AP & GR/IR accounts) Post tax payables Reporting ME Financials Year end activities Number range year shift - GL balance movement - FAGLGVTR
- 34. Sales_Regiter Enhancement Usually sales report will have RV client wants FI related doc like Customer DOC no, Customer Name, Doc type we have prepared the logic and provided to the ABAPer We have analyzed the tables like BKPF, BSEG, RBKP,
- 35. Payment Type: F110 – Automatic Payment F-53 – Manual payment FBCJ – Petty cash F-28 – Incoming Payment F-29 – Customer Down Payment
- 36. Foreign Currency Revaluation: Ex rates be updated in OB08 FCV – run in FAGL_FCV
- 37. Filed Status Group: Field status group is defined under field status variant in T code OBC4. Field Status Group like G001, G002, YB01, YB02 etc. is to define what are the fields required while posting different type of document based on the GL account used. There are 3 different ways to have the fields 1. Suppress/hide – not required 2. Required entry – mandatory field 3. Optional entry - After defining the field status variant, the same should be assigned to company code. In FS00, when creating GL accounts, we need to apply the FSG for each account under “create/bank/interest” tab.
- 38. Fiscal Year Variant: (OB29) Fiscal year variant is used to define the fiscal posting periods at client level. The same will be assigned to company codes as needed. There are some predefined variants given by SAP such as, K4 - for Jan – Dec V3 - for Apr – Mar - in this case, year shift should be defined based on the fiscal year we choose. For ex: for FY 2022-2023, if we choose 2022 as FY, then for Jan - Mar of 2023, the year shift should be defined -1. if we choose 2023 as FY, then for Apr - Dec of 2022, the year shift should be defined as +1. Year Dependent variant: In year dependent variant the fiscal period’s calendar days depends on the specific year and which is to be updated each year. For ex: if a company decides to have last working day of the month to be the fiscal period close, then in the 2022, Apr 29th would be the period close for the month of Apr, but the same cannot be happen in 2023, in 2023, 28th would be last working day in Apr, so the period close would be on 28th. This is called year dependent, which need to be updated each year.
- 39. Customer down payment – F-29 Sub bank account Customer account credit Customer - Clearance F-32 Debit note: DG-FB75 Sales return account Dr
- 40. Smoothing and Catchup method: An asset is acquired for $12,000 on 01/01/2012 and its useful life is 10 years. Hence the yearly depreciation will be $12,000/10 years = $1,200 per year and the monthly depreciation will be $1,200/12 months = $100 per month. Depreciation is posted for period 1 to period 6. Now the useful life of the above asset is changed from 10 years to 5 years in the asset master record in the mid of the year i.e on 01/07/2012. Then, the revised (new) depreciation will be $12,000/5 years = $2,400 per year and the monthly depreciation will be $2,400/12 months = $200 per month. This resulted in increase of Depreciation from $ 1200 to $2400 for the fiscal year 2012. Original Depreciation: $ 100/ Month Revised Depreciation: $ 200/Month Smoothing: The difference will be equally distributed over the remaining planned periods. Catch up : The whole difference will be posted in the Current/next planned period:
- 41. Tables: BSEG-Accounting Document segment BKPF-Accounting Document Header LFA1-Vendor Master general data LFB1-Vendor Master Company code data KNA1-Customer Master General Data KNB1-Customer Master Company code data SKA1-G/L Account Master COA SKB1- GL master data at Co Code level CEPC – Profit center Master
- 42. P1- Critical-within no time P2- High-2 to 4 hrs P2- Medium-One day P4- Low- 2days (enhancement - FX rate not updated automatically for ILS to USD - IC reconciliation account not set in Vendor master - Vendor Street address were not picked correctly, after that we changed the all- vendor master data to correct the address. - Cost center deactivatoin, one of the business segment was sold.
- 43. SM36 – Define background job SM37 – Job Execution SM38 - Queue Maintenance Transaction
- 44. Classification of GL account for Document splitting 1000 Balance Sheet Account 1001 Zero Balance Posting (Free Balancing Units) 1100 Company Code Clearing 1300 Cash Discount Clearing 2000 Customer 2100 Customer: Special G/L Transaction 3000 Vendor 3100 Vendor: Special G/L Transaction 4000 Cash Account 5100 Taxes on Sales/Purchases 5200 Withholding Tax 6000 Material 7000 Fixed Assets 20000 Expense 30000 Revenue 40100 Cash Discount (Expense/Revenue/Loss) 40200 Exchange Rate Difference 80000 Customer-Specific Item Category