- We use Agentry.db in our landscape to distribute to end users
- The intent is that they don't have to perform an intial sync (or Full Agentry transmit)
- Currently we are facing an issue where Agentry.db is not behaving in an expected manner
- The below scenario is failing in a Dev environment and thus we cannot move the changes to Production fearing the new MOD will trigger an intial reset in Prouduction
- SMP 3.0 SP 11 PL02
- SMP 3.0 SDK SP 11 PL06
"Agentry full sync", "Branding an Agentry client does a full sync", "Reload Agentry complex table" , KBA , MOB-SYC-SAP , Syclo Mobility for SAP backend , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.