How to adapt in-app extensibility in SAP with Custom Logic app

How to find transport Request for SAP Beginner✅ Transport Request (TR) ✅ A transport request (TR) in SAP is a container used to collect and move changes—such as new programs, configuration settings, or customizations—from one SAP system to another (for example, from development to testing or production). ✅ This process ensures that changes are made in a controlled and consistent way across your SAP landscape. Understanding how to create, release, and import TRs is a foundational SAP skill for both technical and functional users. In SAP, you can find a transport request (TR) using several methods depending on your requirement. Below are different ways to locate transport requests in SAP: 1️⃣ Using Transaction SE10 (Transport Organizer)✅ Go to Transaction SE10. Enter your User ID (or leave blank to see all requests). Click Display to see transport requests assigned to you. Expand the request to see transport tasks and objects inside. 2️⃣ Using Transaction SE09 (Workbench Organizer)✅ Similar to SE10, but mainly for Workbench Requests (custom developments). Follow the same steps as above.✅ 3️⃣ Using Transaction STMS (Transport Management System)✅ Go to Transaction STMS. Click Import Overview (F5) to see transport requests available in the landscape. Select the appropriate system and double-click to see pending requests. Find the Transport Request Number in the queue. 4️⃣ Using Transaction SE01 (Extended Transport Organizer)✅ Use SE01 if you need advanced filtering options for transport requests. You can search for requests by user, type, status, or object. 5️⃣ Checking TR from a Specific Object (Using SE03)✅ Go to Transaction SE03. Select Find Objects in Requests/Tasks. Enter the object name (e.g., a program, table, or function module). Execute to get the Transport Request that contains the object. 6️⃣ Checking TR in Tables (Technical Method)✅ Open Transaction SE16N and check these tables: E070 → Transport request headers. E071 → Objects inside transport requests. E07T → Transport request texts/descriptions. 7️⃣ Checking TR via Transport Logs✅ Go to Transaction SLG1 (Application Log). Enter Object: TRANSPORT and execute. Check logs related to transport requests. Join SAP Daily Insights on Telegram for daily SAP Updates! 📢 https://lnkd.in/gmPNGNJE https://lnkd.in/gCqhmKJX Connect with me https://lnkd.in/gYMRkhAi Follow SAP Daily Insights™ for more amazing updates. #jatintiwarisap #sapdailyinsight Link to Join my discord channel 👇 https://lnkd.in/gHfQNXUQ

Day 1 : SAP knowledge refresh series : SAP Project types 1️⃣Implementation (Greenfield Project) 📌 First-time SAP setup in a company. ⚙️ System built from scratch → org structure, master data, processes, interfaces, reporting. 🏭 Example: Moving from legacy ERP to S/4HANA to manage finance, sales, supply chain. 💡 Like constructing a brand-new house on empty land. 2️⃣ Brownfield Conversion 📌 Migrating ECC to S/4HANA while retaining history & processes. ⚙️ System conversion, data migration, adjustments for simplifications. 🏭 Example: ECC 6.0 converted to S/4HANA, keeping custom developments. 💡 Like reinforcing your old house’s foundation without changing the layout. 3️⃣ Bluefield (Selective Data Transition) 📌 Hybrid approach – selective migration of data/processes. ⚙️ Some processes redesigned, only required history carried forward. 🏭 Example: Move to S/4HANA with 5 years of FI data while redesigning SD pricing. 💡 Like moving into a redesigned house but carrying only the furniture you need. 4️⃣ Testing Project 📌 Projects dedicated to validating functionalities. ⚙️ Unit, SIT, UAT, Regression testing before rollout/upgrade. 🏭 Example: Third party company perform UAT to validate PP-DS integration before go-live. 💡 Like performing a safety inspection before moving into the house. 5️⃣Rollout Project 📌 Extending SAP to new plants, countries, or divisions. ⚙️ Reuse template → adjust for local tax/currency/compliance. 🏭 Example: Template from USA rolled out to India, configuring GST (TAXINN) procedure for CGST/SGST/IGST compliance. 💡 Like replicating a house design in another city but adjusting for the local climate. 6️⃣Support / Maintenance Project 📌 Continuous support after go-live. ⚙️ Resolve user tickets, fix errors, apply small changes, train users. 🏭 Example: End user faces invoice posting error → consultant resolves account determination. 💡 Like routine maintenance on your home — fixing leaks, updating appliances. 7️⃣Upgrade Project 📌 Moving to a higher SAP version. ⚙️ Technical upgrade, regression testing, minor process changes. 🏭 Example: ECC 6.0 EHP6 → EHP8. 💡 Like renovating your house with new wiring and plumbing. 8️⃣Enhancement / Development Project 📌 Adding new functionalities or custom developments. ⚙️ WRICEF objects, Fiori apps, workflows, exits. 🏭 Example: Custom Fiori app for delivery tracking. 💡 Like adding a balcony or smart devices to your house. 9️⃣ Integration Project 📌 Connecting SAP with external systems. ⚙️ Middleware (PI/PO, CPI), IDoc/EDI setup, interface monitoring. 🏭 Example: Ariba integrated for POs/invoices; Salesforce with SD for orders. 💡 Like linking your house with solar panels or a smart ecosystem. Which project type have you found most challenging in your SAP career?

Unlock the Power of SAP S/4HANA: A Guide to Flexible Workflows 🚀 Tired of rigid, outdated approval processes? SAP S/4HANA's Flexible Workflow is the modern solution your business needs. Think of it as a sophisticated GPS for your documents, allowing you to create dynamic, multi-step approval routes with ease. This powerful tool lets you define: WHO needs to approve (by role, team, or user) WHEN their approval is needed (e.g., for POs over $10,000) HOW MANY steps are required All of this is managed through user-friendly Fiori apps like "My Inbox"! Getting Started: 3 Key Phases Activate the Scenario: Before you can configure your workflow in Fiori, you must first activate the corresponding scenario in the SAP backend (SPRO). This is a mandatory one-time setup that makes the scenario visible in the Fiori Workflow Editor app. Configure in Fiori: Once activated, use the "Manage Workflows" Fiori app to build your approval process. Set preconditions (e.g., PO value > $5,000), define steps, and assign approvers. Test and Deploy: Run end-to-end tests to ensure your rules work as expected. Create test cases for auto-approval, single-level approval, and multi-level approval to cover all your bases. Ready to streamline your business processes and improve financial controls? Dive into the world of Flexible Workflows and take your SAP S/4HANA experience to the next level! #SAP #S4HANA #FlexibleWorkflow #SAPFiori #DigitalTransformation #Procurement #Workflow #Automation #BusinessProcess

Is your head spinning trying to figure out #SAP TM? 😵💫 You're not alone! Let's break down ECC TM vs. S/4HANA TM for all my fellow SAP newbies! Think of it like this: SAP ECC TM: Your trusty old flip phone 📱 • It does the job for transportation management (planning, freight, etc.). • But it's a bit clunky, needs extra apps (integrations) to do cool stuff, and sometimes feels like a separate system glued on. • Reliable, but not exactly "future-proof." SAP S/4HANA TM: Your sleek, integrated smartphone! 🤳 • All your transportation needs are built right into the core of S/4HANA. No more separate systems or tricky integrations! • Faster, smarter, and uses that fancy Fiori interface for a much better user experience. • Think real-time insights, better optimization, and a smoother flow from order to delivery. The TL;DR for Dummies: • ECC TM: TM is an "add-on" that needs a lot of love to play nice with the rest of your SAP system. • S/4HANA TM: TM is a native, integrated part of S/4HANA, making everything simpler and more efficient! Why does this matter? For companies looking to streamline their logistics and get real-time visibility, S/4HANA TM is the clear winner for the long haul. It's like upgrading from dial-up to fiber optics! Here's a little visual to help you remember!

Often system conversion customers have created several custom (aka “Z”) transactions in SAP ECC that they intend to continue using in SAP S/4HANA. They need to bring these custom transactions into the SAP Fiori launchpad to create a unified user experience across new SAP Fiori apps and classic UIs (including SAP GUI transactions). https://shorto.in/An1CZa #SAPFiori

Difference Between Technical Catalog and Business Catalog in SAP Fiori It can be confusing sometimes, so let’s clarify each type of catalog:   Technical Catalog: Contains all technical information (e.g., technical area: MM, SD, FI), tiles, target mappings, app definitions. Acts as a repository of apps—often includes more apps than needed for a single business role. Usually has _TC_ in the catalog ID. Business Catalog: A role-based collection of apps that a business user sees on the launchpad. Apps are derived from technical catalogs and grouped by business roles (e.g., HR, Sales Manager, Purchaser). Assigned to users via PFCG so they can access the apps on the launchpad. Usually has _BC_ in the catalog ID. Business Group: A collection of tiles from one or more catalogs, grouped for easier access and layout management on the Fiori launchpad. Helps users see all authorized apps together. Usually has _BG_ in the catalog ID.   Catalog Relationships in SAP Fiori- Technical Catalog -----> Business Catalog -----> Business Group (Repository)     (Role-based)     (User Layout)           |                    |                       |  Contains all apps           Contains apps for           Groups tiles from   and technical info          a business role             multiple catalogs Technical Catalog: All apps, technical details Business Catalog: Subset for a business role Business Group: Tiles for user layout https://lnkd.in/gKBhQPH4

Day 25 – Navigation Between Views (Master-Detail Concept) in SAP UI5 👋 Hi Everyone, Welcome to Day 25 of my #100DaysOfSAPJourney 🌟 Today, we’ll dive into one of the most important SAP UI5 concepts — Navigation Between Views (Master-Detail Pattern) 💼 📘 What is Master-Detail Navigation? The Master-Detail pattern is widely used in Fiori apps. It displays a list of items (Master View), and when the user selects one, the details (Detail View) of that item appear. For example: Master View → Employee List Detail View → Selected Employee’s Info ⚙️ Step-by-Step Implementation 1️⃣ Create Two Views 👉 Master.view.xml <Page title="Employee List"> <List id="employeeList" items="{/EmployeeSet}" itemPress=".onItemPress"> <items> <StandardListItem title="{EmpName}" description="{Dept}" type="Active" /> </items> </List> </Page> 👉 Detail.view.xml <Page title="Employee Details"> <VBox class="sapUiSmallMargin"> <Text text="Employee ID: {/EmpID}" /> <Text text="Name: {/EmpName}" /> <Text text="Department: {/Dept}" /> <Text text="Email: {/Email}" /> </VBox> </Page> 2️⃣ Configure Routes in manifest.json "routing": { "config": { "routerClass": "sap.m.routing.Router", "viewType": "XML", "viewPath": "com.app.view", "controlId": "app", "controlAggregation": "pages", "transition": "slide" }, "routes": [ { "pattern": "", "name": "Master", "target": "Master" }, { "pattern": "Detail/{EmpID}", "name": "Detail", "target": "Detail" } ], "targets": { "Master": { "viewName": "Master" }, "Detail": { "viewName": "Detail" } } } 3️⃣ Handle Navigation in Controller 👉 Master.controller.js onItemPress: function (oEvent) { const oItem = oEvent.getSource().getBindingContext(); const sEmpID = oItem.getProperty("EmpID"); this.getOwnerComponent().getRouter().navTo("Detail", { EmpID: sEmpID }); } 👉 Detail.controller.js onInit: function () { const oRouter = this.getOwnerComponent().getRouter(); oRouter.getRoute("Detail").attachPatternMatched(this._onObjectMatched, this); }, _onObjectMatched: function (oEvent) { const sEmpID = oEvent.getParameter("arguments").EmpID; const sPath = "/EmployeeSet('" + sEmpID + "')"; this.getView().bindElement(sPath); } 🌟 Key Takeaways ✅ Use sap.m.routing.Router for navigation between views. ✅ Bind details dynamically using bindElement. ✅ Pass data via route parameters like {EmpID}. ✅ A foundation for real-world SAP Fiori apps (e.g., Sales Orders, Employees, Products). #100DaysOfSAPJourney #Day25 #SAP #SAPUI5 #Fiori #FioriApps #FioriUX #SAPLearning #SAPForBeginners #SAPCommunity #SAPDeveloper #SAPConsultant #SAPProjects #OData #SAPBTP #CAPM #SAPUI5Development #SAPRouting #SAPNavigation #SAPMasterDetail #SAPFioriDevelopment

Know the Difference #4 — OData vs API (SAP Consultant’s Perspective) We all hear these terms in integration discussions. But what’s the real difference — and when do we use which? ⸻ OData: 💡 Think of it as SAP’s native language for data exchange — especially for Fiori apps. It’s built for real-time read/write between SAP and external systems, following REST principles and using URLs for access. API: 🌐 Broader concept — covers any interface (SOAP, REST, OData, RFC) that lets one system talk to another. In S/4HANA, you’ll often use SAP Standard APIs (e.g., via API Hub) to integrate SAP with other platforms or third-party tools. ⸻ 🧩 Example • A Fiori app uses an OData service to fetch Purchase Orders. • An external vendor portal calls an API to create PO directly in SAP. 🎯 Takeaway 📍 OData is a type of API. 📍 All OData are APIs, but not all APIs are OData. ⸻ KONNECT Insight 💬 As consultants, we don’t need to code APIs — but we must know which one fits the scenario. 👉 Comment “Integration” if you’ve ever debugged a Fiori app that wouldn’t fetch data. 😅

SAP Fiori App: Balance Sheet / Income Statement - Multidimensional In SAP S4/HANA, you can also create financial statements using the SAP Fiori app balance sheet / Income statement - Multidimensional. With this app, you can display balance sheets and profit and loss statements using operational, local, and global chart of accounts. From this Point you can also navigate to line items of specific G/L accounts or customer or supplier line items. Export to Microsoft Excel or PDF is also supported.