Sonu Kumar Singh

Dear SAP BN4L GTT Learners : Basic setting for GTT to send the tracking requests from TM to GTT. 1.Make sure the PPF settings for the action definition of tracked process request is added. 2.Make sure the output profile is added to FO/FB type in TM 3.Define logical systems for BN4L GTT 4. Define port for BN4L GTT 5.Define partner profiles for BN4L GTT 6.map the GTTMSG01 message type to Idoc type. 7.Define the CI tenant for BN4L GTT All and above configure the SOAP message to send FO/FB data to GTT (TransportationOrderRequest_out). Put the FO/FB execution status in in EXECUTION. Post to this system triggers the tracked process request and Idoc and this will in turn convert to JSON message and same get loaded to GTT. Thanks Me

14

SAP purchase-to-payment  flow — showing PR → PO → GR → Invoice Verification → Vendor Payment → TDS Payment → Security Deposit handling, with T-codes and debit/credit effects at each steptransaction order, covering both FI (Financial Accounting) and MM (Materials Management) entries ✅ This sequence ensures: Proper material accounting GST claimed as input TDS deducted & remitted Security deposits / charges handled transparently ✅ T -CODE used : Proper material accounting ME51N ME21N MIGO MIRO F-53/ F110 F07 / F110

295

19 Comments

Core SAP Basis Troubleshooting t-code and Tools 1. System Performance & Workload Analysis ST03N – Workload analysis (dialog response time, background jobs) ST02 – Buffer and memory analysis (SAP Memory, Extended Memory, Paging) ST06 – OS-level performance (CPU, memory, disk, network stats) SM66 / SM50 – Process overview, long-running work processes 2. System Logs & Errors SM21 – System log (kernel, app server, security, dumps) ST22 – ABAP runtime errors (short dumps) SM13 – Update requests (failed updates) SOST / SCOT – Email/SAPConnect issues 3. Database Performance DB02 – Database performance, table growth, missing indexes DB12 – Backup logs/status DBACOCKPIT – Advanced DB monitoring (depends on DB platform) 4. Background Jobs & Batch Processing SM37 – Job monitoring (status, logs, runtime, failures) SM36 – Job scheduling 5. RFC & Connectivity Issues SM59 – RFC destination test/config SMGW – Gateway monitor (RFC, TCP/IP connections) SICF – ICF services (for web services, Fiori, Gateway) SMICM – ICM status and logs (HTTP, HTTPS, SAProuter) 6. Transport & Change Management** STMS – Transport Management System (TMS overview) SE09 / SE10 – Transport request management TP / R3trans – Command line tools for deeper analysis 7. User & Authorization Issues SU01 – User maintenance SU53– Last authorization failure ST01 / SM19 / SM20– Security trace and audit logs 8. Optional Tools & Transactions SNOTE – SAP Note implementation SPAM / SAINT – Patch and Add-on installation SPRO – Customizing (for config errors) SICK – System checks for inconsistencies

194

5 Comments

MIRO in SAP MM isn’t just about posting vendor invoices—it plays a critical role in SAP FICO as well! Understanding the different types of invoices processed through MIRO helps ensure both operational and financial accuracy. 💡 Invoice Types You Can Process via MIRO: 📄 Standard Invoices – Based on PO & GR, forming the backbone of the P2P process. 🔄 Credit Memos – For returns or vendor-issued adjustments. ➕ Subsequent Debits/Credits – For post-invoice price corrections without affecting quantities. 🚚 Planned/Unplanned Delivery Costs – Freight and other costs captured directly in MIRO or planned at the PO level. 📊 Impact on SAP FI: • Automatically generates FI documents (Vendor A/P entries, GR/IR clearing). • Posts taxes (e.g., GST, TDS) for compliance. • Triggers payment terms, impacting cash flow & due dates. • Ensures correct cost center/internal order postings via integration with CO. 📌 This seamless integration ensures real-time financial visibility and strengthens internal controls across procurement and finance. #SAP #SAPMM #SAPFI #MIRO #InvoiceProcessing #ProcureToPay #FinanceIntegration #SAPTraining #SAPforBusiness

48

3 Comments

In the SAP space, if the clients look for quantity based just to save cost, they will only find bad quality, which they cannot afford to hire. Corporates must get out of "Quantity based Experience" profiles, and shift towards "Capability based" profiles. I know about few requirements open for the last 8-10 months, and the only reason is budget. They will never find good quality this way and it's sheer waste of time. #hiringanomalies #corporatestories #venkyvibes

8

1 Comment

In SAP SD (Sales and Distribution), a User Exit is a custom enhancement point where developers can add custom logic without modifying standard SAP code. This is commonly used in real projects to meet business requirements. 🔹 What is User Exit in SAP SD? A User Exit is a predefined enhancement point provided by SAP using ABAP includes where custom code can be inserted. 📌 Purpose: Custom validation Default value population Pricing logic Delivery logic Billing logic Account determination 🔹 Common SAP SD User Exits 1️⃣ Sales Order User Exits Program: MV45AFZZ Important User Exits: User ExitPurposeUSEREXIT_MOVE_FIELD_TO_VBAKFill header fieldsUSEREXIT_MOVE_FIELD_TO_VBAPFill item fieldsUSEREXIT_SAVE_DOCUMENT_PREPAREValidation before savingUSEREXIT_NUMBER_RANGECustom number rangeUSEREXIT_CHECK_VBAKHeader validationUSEREXIT_CHECK_VBAPItem validation Example: Block sales order if customer credit limit exceeded Mandatory field validation 2️⃣ Delivery User Exits Program: MV50AFZ1 User ExitPurposeUSEREXIT_SAVE_DOCUMENT_PREPAREValidation before PGIUSEREXIT_MOVE_FIELD_TO_LIKPHeader dataUSEREXIT_MOVE_FIELD_TO_LIPSItem data Example: Prevent PGI if transport not assigned 3️⃣ Billing User Exits Program: RV60AFZZ User ExitPurposeUSEREXIT_NUMBER_RANGEBilling number logicUSEREXIT_FILL_VBRK_VBRPFill billing fieldsUSEREXIT_ACCOUNT_PREP_KOMKCVFI account determination Example: Change revenue account dynamically 4️⃣ Pricing User Exits Transaction: VOFM Types: Requirement routine Formula routine Base value routine Example: Special discount calculation 5️⃣ Partner Determination User Exit User Exit: EXIT_SAPLV09A_001 Example: Automatic partner assignment

126

4 Comments

How to Crack L2 (Level 2) Interview Round L2 interviews are often conducted by Senior Consultants, Team Leads, or Architects, and they test your ability to work independently, solve real-time issues, and think critically in project situations. Key Focus Areas to Crack the SAP SD L2 Interview 1. Deep Understanding of Core SD Processes a) Order-to-Cash (OTC) full cycle: Inquiry → Quotation → Sales Order → Delivery → PGI → Billing → Accounting. b) Order types and how to configure them (e.g., OR, RE, KE, ZOR) c) Copy controls (VTAA, VTLA, VTFA) with conditions d) Sales document item category and schedule line category determination logic e) Handling return and credit memo with accounting impact 2. Advanced Pricing Knowledge a) Creation of custom condition types b) Routine development (VOFM) and user exit locations c) Real-time scenario: freight varies by shipping condition or zone d) Special cases: condition exclusion, scales, alternate calculation type e) Tax determination (MWST) and integration with FI 3. Availability Check and aATP (Advanced ATP) a) ATP logic: Checking rule, group, schedule line category b) Difference between basic ATP and advanced ATP (aATP) in S/4HANA c) Backorder processing (BOP), Reconfirmation, Product Allocation 4. Shipping and Delivery Deep-Dive a) Shipping point determination formula b) Route determination and its dependency on transportation zone c) Real-time: Handling batch split, serial numbers in delivery d) PGI failure troubleshooting e) Transportation planning integration with LE 5. Billing and SD-FI Integration a) Invoice split criteria (VBRK/VBRP) b) Billing plans – milestone vs periodic c) VKOA entries and how revenue is posted to G/L d) Error: "Account determination not found for entry …" – root cause and resolution 6. Business Partner (BP) Concept in S/4HANA a) Difference between BP and old customer master (XD01) b) Roles: FLCU00, FLCU01 – What is stored where? c) Number range configuration and mapping to account group d) Common issue: BP created but not extending to sales area – how to fix? 7. Output Determination using BRF+ a) Difference between NAST vs BRF+ b) Output type creation using OPD c) Email outputs, smartform/pdf configuration d) Real-time: Auto-emailing invoice to customer on PGI or billing 8. Credit Management (FSCM vs Classic) a) Credit check configuration: Risk category, control area b) Static vs dynamic credit check c) Document blocking, dunning relevance d) S/4HANA FSCM integration with collections 9. Special Sales Scenarios a) Third-party order with billing b) Intercompany order and billing flow c) Consignment fill-up/issue/return/pick-up d) Rush order vs cash sale e) One-time customer process 10. IDocs / EDI Integration (for client-facing roles) a) Common SD IDocs: ORDERS, INVOIC, DESADV b) Partner profile, port, message type configuration c) Error handling: WE02, WE19, BD87 d) Inbound vs outbound IDoc troubleshooting 11. Enhancements & User Exits #SAPSD #Interview

254

13 Comments

SAP BODS Interview Questions: 1. Core Concepts What is SAP BODS and how does it work in real-time projects? What are the different types of repositories? How is a Data flow different from a Workflow? What is the role of Job Server and Access Server? 2. ETL Design How do you design an end-to-end ETL job? How do you handle job dependencies and parameterization? What is the difference between Batch and Real-time jobs? 3. Transformations (Most Frequently Asked!) How does Table_Comparison work and where do you use it? What is Map_CDC_Operation and how does it help with delta loads? Explain the use of Key_Generation and History_Preserving. When do you use Merge / Validation / Pivot transforms? 4. File & SAP System Integration How do you load data from Flat Files? What are the steps to extract data from SAP ECC or S/4HANA? Have you worked with IDocs, RFCs, or SAP Tables? 5. Real-Time & CDC Scenarios How do you implement Change Data Capture in BODS? How to handle Slowly Changing Dimensions (SCD Type 1 & 2)? How do you manage delta vs full loads? 6. Performance Tuning What is Pushdown Optimization and when is it applied? How do you optimize a slow-running job? What are the best practices for improving performance? 7. Error Handling & Debugging How do you handle errors in BODS jobs? What is the use of try-catch in BODS? How do you debug a failed job? 8. Migration Projects (Hot Topic!) How do you migrate data from ECC to S/4HANA using BODS? What are the common issues during BODS migration? How do you validate the migrated data? 9. Scheduling & Monitoring How do you schedule a job in Management Console? How do you monitor job performance and failures? 10. SQL Knowledge (Very Important) How do you write a query to remove duplicates? What is the difference between inner join and left join? How do you use subqueries and window functions in validation?

7

Interviewer in #Deloitte asked me the below questions on #DMEE in SAP FICO 💡 Interviewer: Can you explain what DMEE is in SAP and its purpose? ✔ Me: DMEE (Data Medium Exchange Engine) is a tool in SAP used to create file formats for electronic payments and bank communication. It enables us to generate payment medium files (like XML, SEPA, MT940, etc.) that banks require for processing transactions. Instead of hardcoding file formats, DMEE provides a tree structure where nodes can be defined and mapped to SAP fields, constants, or user exits. 💡 Interviewer: How does DMEE work in the payment process? ✔ Me: When we execute an SAP payment run (transaction F110), the system generates a payment medium based on the DMEE format assigned to the payment method using transaction FBPM1. 📍 The DMEE tree defines the file structure — header, line items, and trailer — which is filled with data from the SAP system. 📍 The output file is generated through transaction FBPM1 & stored in transaction code BNL_MONI to Monitor payment batches, check status, and troubleshoot payment medium issues. 💡 Interviewer: What are the configurations steps in DMEE? ✔ Me: The key steps are: 📍 Create DMEE Tree (Transaction DMEE): Define the format tree (XML, flat file, etc.) with nodes representing header, items, and trailer. 📍 Define Node Attributes: Each node is assigned attributes such as mapping type (constant, structure field, or exit). 📍 Assign Format to Payment Method (Transaction FBZP): Link the DMEE format tree to payment methods per country. 📍 Generate Payment Medium Format (Transaction FBPM1): Connect DMEE tree to Payment Medium Workbench settings and generate after payment run. 📍 Activate & Test the DMEE Tree: Generate test files and validate the output with the bank’s required format (Transaction BNK_MONI). 🔑 Key Transaction Codes for DMEE & Payment Medium ⚙️ Configuration DMEE → Create & maintain DMEE format trees (define file structure for payment files like SEPA, XML, MT940). FBZP → Configure payment methods in country, and assign DMEE formats at country level. ▶️ Execution F110 → Execute Payment Run for different Company Codes, Payment methods and Vendors. FBPM1 → Payment Medium Workbench – generate payment files based on assigned DMEE tree. 🔍 Monitoring / File Handling BNK_MONI → Monitor payment files, batches, check status of the file sent to bank, and troubleshoot payment medium issues. AL11 → Check if DMEE-generated files are stored correctly. PS - Repost to help one person in your network and comment #CFBR🙏🏻 ------------------------------------------ 📍 Follow: Chirag Thakkar↗ 📌⭐𝐃𝐨𝐰𝐧𝐥𝐨𝐚𝐝 𝐅𝐈𝐂𝐎 𝐈𝐍𝐓𝐄𝐑𝐕𝐈𝐄𝐖 𝐏𝐑𝐄𝐏𝐀𝐑𝐀𝐓𝐈𝐎𝐍 𝐏𝐀𝐂𝐊𝐀𝐆𝐄: https://lnkd.in/d_D72586 📌⭐𝟓𝟎 𝐅𝐈𝐂𝐎 𝐑𝐄𝐀𝐋𝐓𝐈𝐌𝐄 𝐈𝐍𝐂𝐈𝐃𝐄𝐍𝐓𝐒 𝐀𝐍𝐃 𝐒𝐂𝐍𝐄𝐑𝐈𝐎𝐒 𝐏𝐀𝐂𝐊𝐀𝐆𝐄 (New Launch): https://lnkd.in/ddjCdDjA #india  #europe #germany #world #usa #southafrica #malaysia #singapore  #egypt #erpgurus #technology

473

44 Comments

SAP FICO Tables Explained for Beginners ✅ SAP FICO tables are special storage areas in the SAP system where important financial and controlling data is kept. Each table stores a specific type of information. Here’s a simple guide to help you get started:✅ Main SAP FI Tables✅ BKPF: Stores the header (main information) for every accounting document, like date, document number, and type. BSEG: Stores the line items (details) for each accounting document, such as amounts, accounts, and descriptions. SKA1 / SKB1: Store the master data for G/L (General Ledger) accounts—SKA1 at the chart of accounts level, SKB1 at the company code level. KNA1 / KNB1: Store customer master data—KNA1 for general data, KNB1 for company code-specific data. LFA1 / LFB1: Store vendor master data—LFA1 for general data, LFB1 for company code-specific data. BSID / BSAD: Store open and cleared items for customers (used to track unpaid and paid invoices). BSIK / BSAK: Store open and cleared items for vendors. ANLA / ANLB / ANLC: Store asset master data and values for asset accounting. Why Are These Tables Important?✅ They help organize financial data for easy reporting, auditing, and analysis. Each table has a specific purpose, making it easier to find the information you need. How to View Data in SAP Use transaction SE16N to look up table data. Use transaction SE11 to see the table structure (fields and descriptions) Table 👉 What It Stores BKPF 👉 Document header info BSEG 👉 Document line item details KNA1 👉 Customer general info LFA1 👉 Vendor general info SKA1 👉 G/L account master (chart level) ANLA 👉 Asset master record

20

1 Comment

Testing in SAP is not just a project phase—it’s the backbone of a stable and successful go-live.   In SAP implementations, testing ensures that business processes work exactly as expected before they reach end users.   Below are few testing's performed in SAP 1. Unit Testing (UT) 🧩 2. Integration Testing (IT) 🔗 3. User Acceptance Testing (UAT) 👥 4. System Integration Testing (SIT) 🖥️ 5. Regression Testing 🔁 6. Performance / Volume Testing ⚡   👉Follow for more SAP insights or reach out to learn with hands-on, project-driven SAP FICO training.

629

7 Comments

Reflecting on a challenging SAP CPI scenario: SAP Commerce orders failing to reach S/4HANA due to a crucial oversight - the absence of a Content-Type header in the HTTP adapter. Lessons for building resilient CPI processes: - Implement robust error management and retry mechanisms - Exercise caution when utilizing dynamic headers - Simplify testing for current and future developers - Enhance visibility with comprehensive logging and monitoring What unforeseen CPI obstacles have derailed your projects? Let's exchange experiences and insights! #SAPCPI #SAPIntegration #SAPBTP #iFlowDesign #Middleware #ErrorHandling #SAPDevelopers #CloudIntegration #IntegrationBestPractices

8

The Aggregate Technical & Commercial (AT&C) losses have reduced over the years, signalling a transformation. The AT&C losses have reduced from 22.62% in FY 2013-14 to 15.04% in FY 2024-25. #DISCOM #Utilities #RDSS https://lnkd.in/dKzCbSfj

32

SAP S/4HANA Finance 2021 Training by Alok Kumar of ZaranTech With the new SAP S/4HANA 2021 release, SAP is actively expanding the range of functions and thus driving forward the promised integration with the involved departments in the end-to-end process. The new 2021 release provides companies with 1,269 major and minor innovations - for example, in the area of user guidance (SAP Fiori) or in the further automation of business processes through machine learning and predictive analytics. With Release 2021, SAP has integrated the SAP Analytics Cloud into the on-premise version of SAP S/4HANA.

11

3 Comments