Rogerio De Souza Lima’s Post

Tip 228# Tip Of The Friday Evening : : 3615663 - Overview Note for SAP Business One 10.0 SP 2411 : SAP Business One 10.0 Feature Package 2411 has been release : Feature Package & Patch Delivery Schedule for Components Related to SAP Business One ------------------------------------------------------------------ There has been a new Patch Update as SAP Business One 10.0 Support Package 2411 Released on this evening on 15-11-2024 with 150+ SAP Refer Notes! ----------------------------------------------------------------------- So get ready for new update with enhanced feature very soon. #sapbusinessone #patchupdate #SP2411 #planning #sap #business #change

SAP Message for dummies BP integration: message R11119 "Business partner GUID is blank" appears in SLG1 log 1.1.1       Symptom During the Employee to Business Partner synchronization, the error "Business partner GUID is blank" (Message R11119) appears in SLG1 log. Also message "Partner data processed with key PartnerGUID 00000000000000000000000000000000" appears in SLG1 log.

HELLO to SAP folks, #SUCCESSFACTORS We all are moving towards the Configuration Transport center for syncing the configs from lower instances to upper instances. Today I realized that the limitations which were present in the Instance Synchronisation tool for moving RBP is still having presence in the 'configuration transport center'. Is anyone using dynamic filters from any mdf to define the permissions group for RBP? CONFIGURATION TRANSPORT CENTER' does not sync those groups which have multiple dynamic filters category used for people pool. e.g. A pool with country of registration and Job classification will throw an error while syncing. We only have to move that manually and imagine if the number is very high initially, we will spend lot's of time on these manual work just to sync. Does anyone have any insight/thoughts/suggestion around this? How are you guys syncing RBP groups/roles in different instances? looking for feedback!! Any inputs are appreciated!! #Sap #employeecentral #RBP

#SAP SD SPRO FOR DUMMIES Define Transaction/Event Keys In this step, you define transaction/event keys for condition types involving provisions. To enable the system to find the relevant account for provisions (for accrued delivery costs or miscellaneous provisions, for example), you must assign a transaction/event (internal processing) key to each condition type that is relevant to provisions in the step Define Calculation Schema. If purchase account management is active within a company code, you must specify the transaction/event key in the field 'AccKy'. If not, you make this specification in the field 'Provis.'. Via "Transaction/Event Key Usage" and "Usage of Transaction Key in Purchase Account Management", you can determine the calculation schemas in which these keys are used.

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

In the process of legacy asset data migration in SAP, you typically follow a sequence when using AS91 and ABLDT (OI). Here's how you can approach it: 1. Use AS91 First: You start with AS91 to create the asset master data for your legacy assets. This involves inputting the details of the assets that existed before the SAP implementation. You also enter the asset values such as acquisition cost, accumulated depreciation, etc., as of the cutover date. 2. Then Use ABLDT (OI): After you’ve created the legacy asset master records using AS91, you use ABLDT (Open Item Transfer) to post any unposted depreciation or accrued depreciation for those legacy assets that were not transferred during the legacy asset data load. ABLDT allows you to adjust any open asset transactions like depreciation that was not yet posted in the legacy system but needs to be reflected in SAP. Order: First: AS91 (to create the asset master record and enter the legacy values). Then: ABLDT (OI) (to handle any open or pending transactions like unposted depreciation). Regards Ramarao.M #RAMARAOFI

Most of the cases, we load the Delivery costs like Freight or other charges on Inventory Account (BSX). If there is a requirement to load those costs on a separate account as per the business requirement, you can follow the below document which has step by step configuration along with testing. A blog from #2015 and it is still valid. Beauty of SAP and power of core business processes. Few hours of efforts in 2015 has been giving blessings for 9 years. You can check and provide your comments. Thanks. #sap #accounting #inventory #deliverycosts #sapfunctional #sapfico

Hello Folks..!! #SAP #BP #CONFIGURATION If we want to BP and Customer same number ? & What is the back end configuration ? 1) Create account group for customer master 2) Create number ranges for customer master 3) Assign customer account group to number ranges 4) Create BP account group 5)  Create BP number ranges 6)  Assign BP account group to number ranges 7) Assign customer account group to BP account group and check same numbers. I hope it will clear for you, Feel free to connect and discuss further! 💬 Thanks..!! 😎 #BP #INTERVIEWTIPS #SAPSD #S4HANA

👀 Came across an essential SAP Note: 3432855 - Authorization errors: A quick self-check for customers. This note provides detailed steps for customers to perform a self-check before raising an OSS ticket due to authorization errors. The guidance goes beyond the usual SU53 checks, making it a must-read for anyone dealing with SAP authorization issues. 📚🔍 Check it out here: https://lnkd.in/dd_zU6Rs #SAP #Authorization #TechTips #SAPNote #SelfCheck

How to Create SD Output Master Data There are two options to start the transaction for creating new #SAP SD output master data for shipping :