Why SQL queries are not saving in agentry editor for first publish?

Question

Hello Experts,
     In the process of developing an agentry application i have defined SQL steps and saved in agentry editor with out any errors .When i have published definations for first time it is displaying error 'Invalid object some where' in back end SQL log file ,when i have seen in editor some times the query is not saved,some times even it is defined then also the same  error.So i have copied the steps and saved again.Now i have done a publish,it is working fine.This is happening only when i implement exchange mechanism(Showing error in ATE getfetch error).But with out exchange mechanism  it is working fine.Is this related to the installation of editor plig-in is not correct?. I have done preferences setting in my workspace correctly.
          Help me in this regared.Thanks in advance.
Thanks & Regard,
Sravanthi Polu

Answer 1

Sravanthi,
For your error: displaying error 'Invalid object some where' in back end SQL log file.. This is happening only when i implement exchange mechanism(Showing error in ATE getfetch error)
Two suggestions (My best suggestion is item 2 below - I think that is where you have the error)
Item 1: Are you using the right encoding? In your Eclipse Editor under the main menu Windows - Preference -> General -> Workspace. What is your Text file encoding set to? Cp1252? Try setting it to UTF-16.
There is a tutorial about this in:
https://service.sap.com/sap/bc/bsp/spn/esa_redirect/index.htm?gotocourse=X&courseid=70246375 (Enterprise Academy classes). The course is really a simple < 5 minutes discussion on different types of encoding and why they exist and how to change the Eclipse to what you wanted.  SQL is normally done in UTF-16 for 16 bit.
I am assuming that the encoding could be wrong.
Item 2: Another thing that could be wrong is how you specify the SDML (Flunky code). 
In your SQL Script: Anything that has the "<<" and ">>" open and close marker is an SDML (Data Markup Language) and needs to be pre-populated before the Agentry Server submits your SQL query to the backend. In essence, this is use to populate the SQL query with predefine information like your userID or location and when the SQL gets process it will populate the script with the correct information.
So if you are not properly using the flunky (ex: <<object.address>> where address is not a key ID in a Fetch step (Check manual for usage of SDML AgentryLanguageReference_6.0.0.0.pdf) then you may get invalid object.
When you do a SQL "Fetch" Client Exchange and Server Exchange Steps, you can select a few options:
For this discussion let us talk about these 2 items below.
1. Run Attribute: Run One Time
or
2. Run Attribute: Run Once Per Object.
When you select Run Once Per Object the only available Flunky or SDML commands you have are:
object.keyPropertyName
lastUpdate
fetch.messageNumber
The 3 above are your only options
If you try to do something like object.property1 where property1 is part of your object properties then it will not work for Run Once Per Object.
It may work for Run One time as fetch.propertyname.
From your symptoms where you are complaining about an issue in exchange steps, your error is a typo or a misused or a misunderstanding of how fetches and SDML works (documented in page 398 or 399 of AgentryLanguageReference_6.0.0.0.pdf).
See pictures just in case you don't have access to that pdf file (The picture below simply proves what SDML options is available for your Fetch Client Exchange Step).
Hope this helps.
Regards,
Mark Pe
SAP Senior Product Support Engineer