Sivaramakrishnan R’s Post

Ever Wonder What Happens Behind the SAP Scenes? Unveiling the Power of SM37! Feeling curious about those mysterious background jobs running in your SAP system? The SM37 tcode holds the key! This blog dives deep into the world of SM37, exploring: 😎 What it is & Why it Matters: Uncover the purpose of SM37 and its role in monitoring background jobs. 😎 Unlocking Job Details: Learn how to filter, analyze, and understand the status of your background jobs. 😎 Troubleshooting & Optimization: Discover tips for identifying and resolving issues with background jobs to ensure smooth system operations. Ready to become an SAP background job guru? Head over to our blog and explore the power of SM37! ➡️ https://lnkd.in/dNcNZtph #SM37 #SAP #BackgroundJobs #Monitoring #Troubleshooting #Blog #SAPBasis #EnterpriseResourcePlanning

Important Oss Notes for TM Location: 👉 3517635 - How to create or update locations when a Business Partner is saved 3516193 - Final deletion of Transportation Zones via report /SAPAPO/DELETE_LOCATIONS 3486172 - Report /SAPAPO/DELETE_LOCATIONS finishes successfully but location is not deleted in S4 2981582 - Location description is not updated when changing Business Partner name 3500764 - Make the shipping point Location -SP_3710 not relevant for Advanced Shipping and Receiving 3496189 - 'Return to Loading Location' does not work with non-direct FU-FO assignment #SAPTM #SAP

What Happens When Mainstream Maintenance for GTS 11.0 Ends? With Mainstream Maintenance (MM) for GTS 11.0 ending at the end of 2025, companies are now gearing up to carry out the migration project to its successor (E4H). With the migration non-compulsory, MM will automatically enter Customer-Specific Maintenance (CSM) on the 1st January 2026, meaning users can still access a similar service to that found in MM. There will be some restrictions in the scope of service due to the fact that GTS 11.0 will no longer be adjusted to new requirements. Want to learn more? Read our latest article found here: https://lnkd.in/d8BMD7mq ________________ Seeking more SAP expertise? You can find our other insights from our SAP Consultants here: https://lnkd.in/djzm_Rwu If you're currently thinking about starting the migration from GTS11.0 to E4H, get in touch with SAP GTS expert Jack Duffy and discover how Trillion can support you. #SAP #SAPSolutions #SAPGTS #MainstreamMaintenance

Commonly used transactions in SAP Security includes: SU01: Create and maintain user accounts SU10: Mass user maintenance. PFCG: Role maintenance. SU24: Maintenance of authorizations for transaction codes. SU53: Display authorization data for failed authorization checks. SE16: Data browser for table access (with appropriate authorizations). SUGR: Maintain user groups. SUIM: User Information System for various reports on users, roles, and authorizations. What list should i post next ? Let me know in comment section.

SAP T.CODES FOR R2R PROCESS FS10N: GL Account display F.02 : GL Account posting with single journal. FB50 : GL Account posting with multiple. FB03 : To check the document number FB08 : Reverse document FBL5N: To check the customer line items FBL1N: To check the vendor line items FBL3N: To check to open line items OB52 : Books closure F.01 : Financial statement of Trial balance /OF.02: GL Account posting with new session /NEX : close the SAP logout. Or exit from login. #rtr #generalledger

**Troubleshooting Long-Running Transport Requests in SAP** When dealing with long-running SAP transport requests, here's a quick checklist to resolve issues efficiently: 1. **Run the RSTPTEST Report** (SE38) to test tp status and STMS configuration. 2. **Check tp System Logs** in STMS_IMPORT for any errors. 3. **Monitor RDD Jobs** in SM37 and ensure they’re running. If not, schedule them. 4. **Verify Update Status** in SM13, and activate it if needed. 5. **Inspect Background Work Processes** in SM50; ensure no waiting processes. 6. **Check Filesystem Space** for adequate space in directories like sapmnt and oraarch. 7. **Advanced Steps**: Clear temporary files, delete 'in process' requests in STMS, and reschedule RDDIMPDP with RDDNEWPP. 8. **Last Resort**: Restart SAP instance and reschedule jobs during non-productive hours. This checklist ensures smooth transport request execution and resolves common issues quickly. #SAP #TransportRequests #SAPSupport #SAPSystem #TransportManagement #SAPPerformance #SystemTroubleshooting #SAPTips #SAPBasis #ITSupport #SAPCommunity

🌟 New Changes to the System Error Message 🌟 📢 With the new release of 2411, SAP has enhanced the user troubleshooting process - the error messages in SAP Business ByDesign now include the KBA numbers. Now the error message in SAP Business ByDesign will include the KBA (Knowledge Based Article) number along with the actual error message. 💡 How it works: • We perform a particular task which has some kind of error in the backend. Before the 2411 release, the system used to just pop-in the error message below, which sometimes was easy to get a solution for that and sometimes it needed the help of some KBA stored in the system. • But now as a particular task is performed which has error in the backend, the system pops-in the error along with the KBA which is related to that error. 💡 Why is this important? • Reduces the solution giving time: This enhancement has reduced the time for solving an error. • Increased Accuracy: If we have a proper KBA number for solving a particular error, it becomes easy for the consultant to resolve it. • Streamlined Cases and Service Task Process: With this new enhancement, the process of cases and service task/ incident management is streamlined. For more details on all the exciting features and updates in SAP ByD 2411 release, check out the full release highlights here: https://lnkd.in/gfN9uhPK #SAP #SAPBusinessByDesign #SAPByD #crossareatopic #systemerrormessage #incidencemanagement #caseandservicetask #KBA #incidenterror #2411ByD Article credit: Deepali Shenoy

SAP Message For Dummies No dunning settings have been maintained for company code Message no. F2090 Diagnosis You have tried to define dunning data in company code 1239 for the current account. Before you do this, however, you must define the company code data for company code 1239 within the dunning program configuration.

#SAP Knowledge Message V1498 when creating credit memo request Message V1498 "Credit memo request already exists for item &1: &2 &3" when creating credit memo request