SQL extension for XSLT

Hi,
I am working on SQL extensions on XSLT using xalan SQL Library. My requirement is to insert some data which comes in the form of XML to one of our tables. I tried to write a sample XSLT to retrieve the data from the database (thought I can change it to insert once I succeed retrieving data). The XSLT is not working. I think I am able to connect to database successfully but not able to retrieve any results. Any help would be greatly appreciated.
Thanks in advance,
Latha
Here is my sample XSLT.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0"
xmlns:sql="org.apache.xalan.lib.sql.XConnection"
extension-element-prefixes="sql"
xmlns:xalan="http://xml.apache.org/xalan"
exclude-result-prefixes="xalan"
>
<xsl:param name="queryString" select="'SELECT * FROM FASTATUS'"></xsl:param>
<xsl:output method="html" indent="yes"/>
<xsl:template match="/">
<xsl:variable name="dbObj" select="sql:new()"></xsl:variable>

<xsl:if test="not(sql:connect($dbObj, 'extpool'))" >
<xsl:message>Error Connecting to the Database</xsl:message>
<xsl:copy-of select="sql:getError($dbObj)/ext-error" />
</xsl:if>
<xsl:message>Database Coneection successful</xsl:message>
<HTML>
<HEAD>
<TITLE>List of Values</TITLE>
</HEAD>
<BODY>

<xsl:variable name="table">
<xsl:copy-of select="sql:query($dbObj, $queryString)"/>
</xsl:variable>
<xsl:if test="not($table)" >
<xsl:message>Error in Query</xsl:message>
<xsl:copy-of select="sql:getError($dbObj)/ext-error" />
</xsl:if>
<xsl:message>Query execution successful</xsl:message>
<TR>

<xsl:for-each select="$table/sql/metadata/column-header">
<TH>
<xsl:value-of select="@column-label"/>
</TH>
</xsl:for-each>
</TR>
<xsl:apply-templates select="$table/sql/row-set/row"/>
<xsl:text>
</xsl:text>
</BODY>
</HTML>
<xsl:value-of select="sql:close($dbObj)"/>
</xsl:template>
<xsl:template match="row">
<TR><xsl:apply-templates select="col"/></TR>
</xsl:template>
<xsl:template match="col">
<TD><xsl:value-of select="text()"/></TD>
</xsl:template>
</xsl:stylesheet>

No idea. You didn't mention pquery in your original post, and I don't even know what that is (even after googling it).
Anyway, your problem is the same as in your first post. You haven't done your research. All you know is it's "not working". Find out in what way it is not working and then post a detailed question.

Similar Messages

Writing extension for SQL Developer

Hello all,
I'm new to writing extensions for SQL Developer using JDeveloper. Can you help me with some example with common functionality, like how to get the current connection? Is there some documentation for the oracle.sqldeveloper package? The example may include some techniques like how to get the schema name for a chosen table, get some other info for the table and so on.
Thank you in advance!

Hello all,
I'm new to writing extensions for SQL Developer using JDeveloper. Can you help me with some example with common functionality, like how to get the current connection? Is there some documentation for the oracle.sqldeveloper package? The example may include some techniques like how to get the schema name for a chosen table, get some other info for the table and so on.
Thank you in advance!

Announcement: OrindaBuild 5.0 Extension for SQL Developer 1.5.1

Folks,
OrindaBuild is now available as an extension for SQL Developer 1.5.1.
OrindaBuild creates Java source code to run your existing PL/SQL. This is a non-trivial task and for large projects can consume hundreds on man hours as well as delay development.
OrindaBuild does roughly the same thing that JPublisher does, but writes human readable code, doesn't need SQLJ and doesn't require that you use oracle TYPE objects as parameters for records and arrays.
Another way of thinking of OrindaBuild is "We reach that parts of your application that Hibernate can't".
OrindaBuild is available as extensions for JDeveloper and SQL Developer 1.1. After an unreasonably long gestation OrindaBuild is now available as an extension for SQL Developer 1.5.1 The delay has been caused by us rewriting both the JDeveloper and SQL Developer extensions so that code base has now been unforked. We've also standardized the functionality with that of our recently upgraded Eclipse extension.
To install the demo select 'Help/Check for updates' and then use the 'Add' button to create an update center for Orinda Software using this URL:
http://www.orindasoft.com/public/sqldev15Center.xml
Functionality:
The demo version is fully playable, with the only limitation being that it expires after 1 month. You can install the demo multiple times.
In addition to generating Java to call PL/SQL it also allows you to create code to run any SQL statement and access database tables.
OrindaBuild generates code for PL/SQL procedures that take %ROWTYPE and Package Records as parameters. Generated code uses a library. If you buy OrindaBuild you get the source code for the library and end up with a 100% source code solution - i.e. there are no mysterious runtime binary dependencies.
Limitations:
The extension does not work with versions of SQLDeveloper prior to 1.5.1 (build 5440). We expect you to buy a licence if you deploy generated code in a production environment.
For more information see
http://www.orindasoft.com/public/sdefeatures.php4
David Rolfe

It is possible that the patch has replaced you shortcut with one pointing to the version within the 11g home. Try running sqldeveloper directly from the executable in the 151 directory.

Java extension for SQL Developer 2.1 (SqlEditor)

Hello,
we are developing a java extension for SQL Developer. It was working fine in version 1.5.5 but it seems that some of the java classes were changed in version 2.1 so it does not any more. In the SQL editor, we want to have a context menu action that gets the selected SQL statement and calls a database function with it as an argument. Our code looks like
@RegisteredByExtension("our.developer.extension")
public final class OurCommand extends Command {
public int doit() {
SqlEditor sqlEditor = (SqlEditor)getContext().getView();
String query = sqlEditor.getView().getSqlStatement();
sqlEditor.executeSql(query, "");
//or
//sqlEditor.getView().scriptRunner(query);
Unforunately, in SQL Developer 2.1 the class oracle.dbtools.sqlworksheet.sqlview.SqlEditor does not exist. Does anybody know how to write this example for version 2.1? Is there an API documentation (alas, [http://wiki.oracle.com/page/SDK+2.0] is an empty article)?
BTW, does anybody know how to open the dialog for connecting to a database when sqlEditor.getConnection() is null?

I got it to work using a BASIC call instead of my normal TNS call.
We use MS SMS to package the Oracle client and SQL Developer and push it out to users so we don't have people visiting desktops. Also, we use OID to store the entries instead of a tnsnames file so that we don't have to maintain a TNSNAMES file.
I am testing 2.1 as we would eventually upgrade when it goes GA.
2.1 seems to be built on Oracle 11g. Issue will be that since 99% of our databases are 10gr2 as well as 100% of our client population will be be forced to upgrade the Oracle client to use 2.1 as we do today without lots of changes for the end user?
We don't broadcast the information the average user requires for a BASIC connection so that is out for non technical users..
We have SQL Developer 1.5.5 right now and this is not and issue.
Hopefully, this will be resolved during EAI for 2.1.

Table API Extension for Oracle SQL Developer

I just created small project [Table API Generator for Oracle|http://code.google.com/p/tapig/].
Idea is to only maintain tables and generate table API (TAPI) packages for data manipulation.
Generated:
- insert, update, delete, querying procedures
- documentation based on table columns comments
Do you think it will be useful to have custom Table API Generator as extension for Oracle SQL Developer?

Never used them myself and quite legacy, but I'm sure there's still a lot of people using them and the basic idea is quite nice.
This would also qualify perfectly as a User Defined XML Extension for sqldev; little work but big results. Even if you were the only one using it, it would still pay off.
Have fun,
K.

Implement and deploy a JSON rendering extension for SSRS.

Hi,
Can anyone please let me know how to implement and deploy a JSON extension for SSRS 2005?

Hi Anoopmulamoodu,
In Reporting Services, we can implement custom rendering extensions to generate reports in expected formats. After doing some research, I am afraid there is no example of JSON Rendering Extension for Reporting Services. Generally, it is difficult to write
a custom rendering extension because it must typically support all possible combinations of report elements and requires that you implement hundreds of classes, interfaces, methods, and properties. Before you decide to create a custom rendering extension,
you should evaluate simpler alternatives:
Customize rendered output by specifying device information settings for existing extensions.
Add custom formatting and presentation features by combining XSL Transformations (XSLT) with the output of the XML rendering format.
If you indeed to implement a custom rendering extension, please go through the following MSND document as well as an code example of Zip Rendering Extension:
Implementing a Rendering Extension
Zip Rendering Extension for SQL Server Reporting Services 2005/2008/2012
Hope this helps.
Regards,
Mike Yin
TechNet Community Support

Custom File Extension for Microsoft Access Text Driver (*.txt, *.csv)

I'm trying to use a custom file extension for the Microsoft Access Text Driver (*.txt, *.csv) driver.
I have updated the FileExtns registry to have my new extension.
When I issue the following it does not work.
select [NoName]
from openrowset('MSDASQL'
           ,'Driver={Microsoft Access Text Driver (*.txt, *.csv)};
                DefaultDir=c:\filedir'
           ,'select * from "file.lst"')
If I make the file a .csv it works fine. However, if it has an extension of not CSV or TXT (in this case .lst, which is in the registry setting) extension it throws the following error and cannot seem to find a solution to it.
OLE DB provider "MSDASQL" for linked server "(null)" returned message "[Microsoft][ODBC Text Driver] Cannot update. Database or object is read-only.". Msg 7350, Level 16, State 2, Line 1 Cannot get the column information from
OLE DB provider "MSDASQL" for linked server "(null)".
In addition, (although I can probably find this elsewhere), I need to have the first line 'BLANK' so that it does not miss data (there is no header row). Is there a way to use OPENROWSET without BULK to basically include all rows as data?
Any help is appreciated.

Hi,
According to your description, I did a test with your script, and got the same message as your post. Usually, by default, the Microsoft Access Text Driver (*.txt, *.csv) supports the four extensions file, such as *.asc, *.csv, *.tab, *.txt. To solve this issue,
I recommend you try to save the LST file in the above format, then use OPENROESET to get data from the supported extensions file in SQL Server.
In addition, the
OPENROWSET function is mainly used to retrieve remote data from an OLEDB data source, when you use OPENROWSET without BULK, provider_name is a necessary parameter in the script. However, the OPENROWSET (BULK...) is mainly called from a SELECT…FROM clause
within an INSERT statement, when importing bulk data from a data file into SQL Server table. Thus if you need to import bulk data, you should use the basic syntax: INSERT ... SELECT * FROM OPENROWSET(BULK...), also there are some alternatives, such as
BULK INSERT
and
BCP .
Thanks
Lydia Zhang

Using CVS in SQL Developer for Data Modeler changes.

Hi,
I am fairly new to SQL Developer Data Modeler and associated version control mechanisms.
I am prototyping the storage of database designs and version control for the same, using the Data Modeler within SQL Developer. I have SQL Developer version 3.1.07.42 and I have also installed the CVS extension.
I can connect to our CVS server through sspi protocol and external CVS executable and am able to check out modules.
Below is the scenario where I am facing some issue:
I open the design from the checked out module and make changes and save it. In the File navigator, I look for the files that have been modified or added newly.
This behaves rather inconsistently in the sense that even after clicking on refresh button, sometimes it does not get refreshed. Next I try to look for the changes in Pending Changes(CVS) window. According to the other posts, I am supposed to look at the View - Data Modeler - Pending Changes window for data modeler changes but that shows up empty always( I am not sure if it is only tied to Subversion). But I do see the modified files/ files to be added to CVS under Versioning - CVS - Pending Changes window. The issue is that when I click on the refresh button in the window, all the files just vanish and all the counts show 0. Strangely if I go to Tools - Preferences - Versioning - CVS and just click OK, the pending changes window gets populated again( the counts are inconsistent at times).
I believe this issue is fixed and should work correctly in 3.1.07.42 but it does not seem to be case.
Also, I m not sure if I can use this CVS functionality available in SQL Dev for data modeler or should I be using an external client such as Wincvs for check in/ check out.
Please help.
Thanks

Hi Joop,
I think you will find that in Data Modeler's Physical Model tree the same icons are used for temporary Tables and Materialized Views as in SQL Developer.
David

Extensions For Dreamweaver 8 and CFMX 7

Just upgraded from ColdFusion 5 to ColdFusion MX 7. Have been
using Studio 8 with of course, Dreamweaver 8, for the last 7
months.
The CF7 MX upgrade package comes with an 18 meg .MXP file,
entitled: CF7 Extensions For Dreamweaver MX. Should I install this
in my Dreamweaver 8 Extensions? Or does DW 8 already come with
most, or ALL of these? In other words, are they only designed for
DW MX? Is there anything at all to be gained by installing these
extensions, or perhaps something to get "messed up", like an
existing extension being overwritten by an older one in the 18 meg
upgrade file?
Also, most of the extensions seem to be for that Enterakt
product, which doesn't support SQL Server or Oracle, right? Which
is what I use.
Or should I just ignore this 18 meg file? Or just go ahead
and install it? Appreciate any help/advice. Thank you.
Gary

The CF7 extensions were designed to add extra capabilities to
DWMX. They
were built into DW8.
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver
Valleybiz Internet Design
www.valleybiz.net
"Gary1" <[email protected]> wrote in message
news:edhbat$npe$[email protected]..
> Just upgraded from ColdFusion 5 to ColdFusion MX 7. Have
been using
> Studio 8
> with of course, Dreamweaver 8, for the last 7 months.
>
> The CF7 MX upgrade package comes with an 18 meg .MXP
file, entitled: CF7
> Extensions For Dreamweaver MX. Should I install this in
my Dreamweaver 8
> Extensions? Or does DW 8 already come with most, or ALL
of these? In
> other
> words, are they only designed for DW MX? Is there
anything at all to be
> gained
> by installing these extensions, or perhaps something to
get "messed up",
> like
> an existing extension being overwritten by an older one
in the 18 meg
> upgrade
> file?
>
> Also, most of the extensions seem to be for that
Enterakt product, which
> doesn't support SQL Server or Oracle, right? Which is
what I use.
>
> Or should I just ignore this 18 meg file? Or just go
ahead and install
> it?
> Appreciate any help/advice. Thank you.
>
> Gary
>

How can get a database like ****.SQL file for test in sqlplus in oracle8i

How can get a database like ****.SQL file for test in sqlplus in oracle8i,I am a beginner,thanks

I'll give it a guess as to what it is you want but I'm afraid you'll have to give some more information to go on. I appreciate it's difficult for people who are beginners or who don't have English as their first language.
Are you trying to run a SQL file? From SQL*plus you can do either of these:
SQL> start my_file
or
SQL> @my_file
N.B.: if th efile has a .sql extension you don't need to include it, but you do for any other file extension e.g.
SQL> @myfile.run
Here is the page Vijay referred to:
Re: Physical storage Checks & adding disk on server. I hope you find it useful.
You will more helpful links (including links to the Oracle on-line manuals at this page:
Re: How to attach a java bean in forms6i
good luck, APC

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

PHP Hotfix for XSLT

I have developed a website at home using PHP and XSLT to read
a number of RSS feeds. The server I use at home is PHP 5.1.2, but
work (where it will be hosted) uses 5.1.4 so the XSLT no longer
works.
A hotfix was released to address the problem (
Link
here).
I have installed this extension and re-opened DW, but when I
now open my original .xsl file, under Server Behaviours I'm now
told I have no Behaviours installed for XSLT!?
Anyone know what I'm supposed to do here?
Thanks in advance.

Anyone?

Error while executing a sql query for select

HI All,
ORA-01652: unable to extend temp segment by 128 in tablespace PSTEMP i'm getting this error while i'm executing the sql query for selecting the data.

I am having 44GB of temp space, while executing the below query my temp space is getting full, Expert please let us know how the issue can be resolved..
1. I dont want to increase the temp space
2. I need to tune the query, please provide your recomendations.
insert /*+APPEND*/ into CST_DSA.HIERARCHY_MISMATCHES
(REPORT_NUM,REPORT_TYPE,REPORT_DESC,GAP,CARRIED_ITEMS,CARRIED_ITEM_TYPE,NO_OF_ROUTE_OF_CARRIED_ITEM,CARRIED_ITEM_ROUTE_NO,CARRIER_ITEMS,CARRIER_ITEM_TYPE,CARRIED_ITEM_PROTECTION_TYPE,SOURCE_SYSTEM)
select
REPORTNUMBER,REPORTTYPE,REPORTDESCRIPTION ,NULL,
carried_items,carried_item_type,no_of_route_of_carried_item,carried_item_route_no,carrier_items,
carrier_item_type,carried_item_protection_type,'PACS'
from
(select distinct
c.REPORTNUMBER,c.REPORTTYPE,c.REPORTDESCRIPTION ,NULL,
a.carried_items,a.carried_item_type,a.no_of_route_of_carried_item,a.carried_item_route_no,a.carrier_items,
a.carrier_item_type,a.carried_item_protection_type,'PACS'
from CST_ASIR.HIERARCHY_asir a,CST_DSA.M_PB_CIRCUIT_ROUTING b ,CST_DSA.REPORT_METADATA c
where a.carrier_item_type in('Connection') and a.carried_item_type in('Service')
AND a.carrier_items=b.mux
and c.REPORTNUMBER=(case
when a.carrier_item_type in ('ServicePackage','Service','Connection') then 10
else 20
end)
and a.carrier_items not in (select carried_items from CST_ASIR.HIERARCHY_asir where carried_item_type in('Connection') ))A
where not exists
(select *
from CST_DSA.HIERARCHY_MISMATCHES B where
A.REPORTNUMBER=B.REPORT_NUM and
A.REPORTTYPE=B.REPORT_TYPE and
A.REPORTDESCRIPTION=B.REPORT_DESC and
A.CARRIED_ITEMS=B.CARRIED_ITEMS and
A.CARRIED_ITEM_TYPE=B.CARRIED_ITEM_TYPE and
A.NO_OF_ROUTE_OF_CARRIED_ITEM=B.NO_OF_ROUTE_OF_CARRIED_ITEM and
A.CARRIED_ITEM_ROUTE_NO=B.CARRIED_ITEM_ROUTE_NO and
A.CARRIER_ITEMS=B.CARRIER_ITEMS and
A.CARRIER_ITEM_TYPE=B.CARRIER_ITEM_TYPE and
A.CARRIED_ITEM_PROTECTION_TYPE=B.CARRIED_ITEM_PROTECTION_TYPE
AND B.SOURCE_SYSTEM='PACS'
Explain Plan
==========
Plan
INSERT STATEMENT ALL_ROWSCost: 129 Bytes: 1,103 Cardinality: 1
     20 LOAD AS SELECT CST_DSA.HIERARCHY_MISMATCHES
          19 PX COORDINATOR
               18 PX SEND QC (RANDOM) PARALLEL_TO_SERIAL SYS.:TQ10002 :Q1002Cost: 129 Bytes: 1,103 Cardinality: 1
                    17 NESTED LOOPS PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 129 Bytes: 1,103 Cardinality: 1
                         15 HASH JOIN RIGHT ANTI NA PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 129 Bytes: 1,098 Cardinality: 1
                              4 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 63 Bytes: 359,283 Cardinality: 15,621
                                   3 PX SEND BROADCAST PARALLEL_TO_PARALLEL SYS.:TQ10001 :Q1001Cost: 63 Bytes: 359,283 Cardinality: 15,621
                                        2 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1001Cost: 63 Bytes: 359,283 Cardinality: 15,621
                                             1 MAT_VIEW ACCESS FULL MAT_VIEW PARALLEL_COMBINED_WITH_PARENT CST_ASIR.HIERARCHY :Q1001Cost: 63 Bytes: 359,283 Cardinality: 15,621
                              14 NESTED LOOPS ANTI PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 65 Bytes: 40,256,600 Cardinality: 37,448
                                   11 HASH JOIN PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 65 Bytes: 6,366,160 Cardinality: 37,448
                                        8 BUFFER SORT PARALLEL_COMBINED_WITH_CHILD :Q1002
                                             7 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1002Cost: 1 Bytes: 214 Cardinality: 2
                                                  6 PX SEND BROADCAST PARALLEL_FROM_SERIAL SYS.:TQ10000 Cost: 1 Bytes: 214 Cardinality: 2
                                                       5 INDEX FULL SCAN INDEX CST_DSA.IDX$$_06EF0005 Cost: 1 Bytes: 214 Cardinality: 2
                                        10 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1002Cost: 63 Bytes: 2,359,224 Cardinality: 37,448
                                             9 MAT_VIEW ACCESS FULL MAT_VIEW PARALLEL_COMBINED_WITH_PARENT CST_ASIR.HIERARCHY :Q1002Cost: 63 Bytes: 2,359,224 Cardinality: 37,448
                                   13 TABLE ACCESS BY INDEX ROWID TABLE PARALLEL_COMBINED_WITH_PARENT CST_DSA.HIERARCHY_MISMATCHES :Q1002Cost: 0 Bytes: 905 Cardinality: 1
                                        12 INDEX RANGE SCAN INDEX PARALLEL_COMBINED_WITH_PARENT SYS.HIERARCHY_MISMATCHES_IDX3 :Q1002Cost: 0 Cardinality: 1
                         16 INDEX RANGE SCAN INDEX PARALLEL_COMBINED_WITH_PARENT CST_DSA.IDX$$_06EF0001 :Q1002Cost: 1 Bytes: 5 Cardinality: 1

Warranty extension for Satellite U400

Hello!
I have a question about possibility to extend warranty for my laptop.
On the official web-ste there is information about my device and it;s written over there:
"Standard Warranty
Coverage: International Days:365 Expiration Date: 2010-05-25
Extended Warranty
Servicename: International Warranty Extension from 1 to 2 years Service Coverage: International Days: 730 Expiration Date: 2011-05-25 "
It's written that I have already an extended warranty, but i've just register the standard warranty of my new laptop!
Anyway, the question is: can i buy a warranty extansion in my cause and what type of extension i have to buy (from 2 to 4, from 2 to 3 e.t.c.)
Thank you in advance!
P.S. And one more question: my friend is going to buy Toshiba Satellite A500-1F2. The same question: which kind of warranty extension is he able to purchase?
Thank you!
Best regards,
Dmitry

Hi
Usually all notebooks are covered by standard warranty for a 1 year.
If you register the notebook on the Toshiba page, you will get an additional warranty year (altogether 2 years).
I think this is what you can see on the Toshiba page.
I think you can extend the warranty too.
You have to look here:
http://eu.computers.toshiba-europe.com -> Peripherals & Services -> Services -> Warranty extensions
There you will have to check available Warranty Extensions for your notebook model.
Greets

Custom service (using Reader Extensions) for REST invocation

Hello,
is it possible to implement and configure a custom service (using Reader Extensions) for REST invocation?
Best regards
CommanderPeek

Yes LiveCycle does support REST as an endpoint http://help.adobe.com/en_US/livecycle/9.0/programLC/help/index.htm?content=000562.html

SQL extension for XSLT

Similar Messages

Maybe you are looking for