on 07-07-2016 8:59 AM
Hi Guys,
I'm currently trying to figure out how to disable a complex table we would like to skip during initial sync for our Service Manager.
We are currently hosting our Service manager in SMP 3.0.
Here is what I did:
In Configpanel -> CTProductHierarchy
1. Enable_table = -1
Table_refresh = 168
Table_check = 168
Active flag = unchecked
2. Enable_table = 0
Table_refresh = -1
Table_check = -1
Active flag = unchecked
With both parameter settings we tried restarting the SMP 3.0 services thinking that It's not picking up the changes readily.
Both to no avail and still downloading the complex table during initial sync.
What I'm thinking next is to disbale the BAPI wrapper for the CTProductHierarchy.
What am I missing here guys?
Thanks,
Kurt
Kurt,
Are you trying to disable the table permanently or just during initial sync?
The Table check and refresh values only apply after the table is initially loaded on the device and control when to next check for delta changes (table check) or when to completely reload (table refresh) based on the last update date of that table on the client. The enable table flag should control if the table is considered "active" or completely ignored. However this would apply to all transmits not just the initial transmit.
Can you explain your scenario a bit further?
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kevin,
Even if you disable a complex table, it still appears in the transmit screen when it's checked, even though no data will be read.
The only way around I found to disable a complex table for good was to delete it from Agentry editor. Maybe there should be an option to disable a CT from the Editor as well and then the client won't try to fetch it or even check the parameters.
After restarting the CRM server the changes took place. Thanks for all the help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kevin,
For your issue: we would like to skip during initial sync
Option 1: Due to you did not indicate what version is your Service Manager, let me try to approach this in a different angle. Let me assume you are using something older.
In older version, the javaBE.ini may be source = ini. If this is your case then the update and turning off is in the javaBE.ini.
Option 2: There were reports on older version of SMP 3.0 that was fixed to avoid this type of issue. So hopefully you are using a much newer SMP 3.0 runtime server and SDK.
- What is your version of SMP 3.0 runtime server?
- You may always try to see if you can do it in a later version
Option 3: At any time during your startup, did you do any publish from an Agentry editor? Potentially changing the time or resetting the time of new definition?
Option 4: Branding a pre-built client.
Regards,
Mark Pe
SAP Platinum Support Engineer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kevin,
Only enable_table value change is sufficient. yes you have to restart the Agentry app after changing in configpanel.
in this case Agentry client will call complex table class but as the enable table value is 0 so the return value from Java will be 0.
if you remove all the complex table from agentry editor, no doubt the complex table download request will not go to server. but the problem is in future, if you need these complex tables you have to rewrite in Agentry editor or you can restore it from Trash(if you haven't cleared your trash). which is risky sometimes. so its recommended to change the Enable_table value in SAP configpanel.
Hope this makes you clear
Thanks
Ajitesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.