[svn] 762: -update the 3.0 branch to use build. properties to create the flex-sdk-description.xml

Question

Revision: 762
Author: [email protected]
Date: 2008-03-10 07:44:49 -0700 (Mon, 10 Mar 2008)
Log Message:
-update the 3.0 branch to use build.properties to create the flex-sdk-description.xml
Modified Paths:
flex/sdk/branches/3.0.x/build.properties
flex/sdk/branches/3.0.x/build.xml
Added Paths:
flex/sdk/branches/3.0.x/collateral/en_US/flex-sdk-description.xml

Answer 1

By the way, simply adding the quotes around the lexical names in the sql statement doesn't work. That causes the lexical references to be ignored as simple string values:
SELECT
   '&FLEX_GL_BALANCING_APROMPT' alias_gl_balancing_aprompt
  ,'&FLEX_GL_ACCOUNT_LPROMPT'   alias_gl_account_lprompt
  ,'&ACCT_BAL_LPROMPT'          alias_acct_bal_lprompt
FROM dualI turned on statement-level debugging via xdodebug.cfg and saw how it compiled the lexicals. By replicating the call to apps.fnd_flex_xml_publisher_apis.kff_segments_metadata that I found there, I was able to hack together a workaround for this issue.
Please point me to a better way of doing this if possible, as I had to GRANT EXECUTE on this apps package to my custom code schema. Is there a better lexical/flexfields reference than the XML Publisher documentation?
Here is the call I made in my before-report trigger:
--set ACCT_BAL_LPROMPT flexfield segment metadata lexical
begin
apps.fnd_flex_xml_publisher_apis.kff_segments_metadata(
  'FLEX_ACCT_BAL_LPROMPT',
  'SQLGL',
  'GL#',
  101,
  'GL_BALANCING',
  'Y',
  'LEFT_PROMPT',
  c_FLEX_ACCT_BAL_LPROMPT
end;