How to triger RDDIMPDP at operational level

Hi Basis experts,
We are importing support package, and get stucked at the IMPORT_PROPER stage. The RDDIMPDP is not running at the background, and we cannot use the SE38 to run RDDNEWPP.  So, anyone can tell me how can I run the RDDIMPDP from UNIX level?  Thanks alot in advance.
Amy

It gives me error message like: 
Runtime Errors         SYNTAX_ERROR                                                    
Date and Time          02.08.2007 16:16:20                                                                               
Short text                                                                               
Syntax error in program "SAPLSEWORKINGAREA ".                                                                               
What happened?                                                                        
     Error in the ABAP Application Program                                             
     The current ABAP program "SAPLWBABAP" had to be terminated because it has         
     come across a statement that unfortunately cannot be executed.                                                                               
The following syntax error occurred in program "SAPLSEWORKINGAREA " in include    
      "LSEWORKINGAREAU01 " in     line 54:                                                                               
"The data object "WORK_ITEMS" does not have a component called "JUST_FO"          
     "R_CHECKING"."                                                                    
The include has been created and last changed by:                                 
     Created by: "SAP "                                                                
     Last changed by: "SAP "                                                                               
What can you do?                                                                      
     Please eliminate the error by performing a syntax check                           
     (or an extended program check) on the program "SAPLSEWORKINGAREA ".               
     You can also perform the syntax check from the ABAP Editor.                                                                               
If the problem persists, proceed as follows:                              
     Note down which actions and inputs caused the error.                                                                               
To process the problem further, contact you SAP system administrator.                                                                               
Using Transaction ST22 for ABAP Dump Analysis, you can look               
     at and manage termination messages, and you can also keep them for a long time.                                                                               
Error analysis                                                                
     The following syntax error was found in the program SAPLSEWORKINGAREA :   
     "The data object "WORK_ITEMS" does not have a component called "JUST_FO"  
     "R_CHECKING"."                                                            
How to correct the error                                                      
     Probably the only way to eliminate the error is to correct the program.   
If you cannot solve the problem yourself and want to send an error        
     notification to SAP, include the following information:                                                                               
1. The description of the current problem (short dump)                                                                               
To save the description, choose "System->List->Save->Local File (Unconverted)".                                                                               
2. Corresponding system log                                                                               
Display the system log by calling transaction SM21.                       
        Restrict the time interval to 10 minutes before and five minutes          
     after the short dump. Then choose "System->List->Save->Local File            
     (Unconverted)".                                                                               
3. If the problem occurs in a problem of your own or a modified SAP          
     program: The source code of the program                                      
        In the editor, choose "Utilities->More                                    
     Utilities->Upload/Download->Download".                                                                               
4. Details about the conditions under which the error occurred or which      
     actions and input led to the error.                                                                               
System environment                                                               
     SAP-Release 700                                                                               
Application server... "btrcmap6"                                             
     Network address...... "172.17.2.211"                                         
     Operating system..... "AIX"                                                  
     Release.............. "5.3"                                                  
     Hardware type........ "000C4658D600"                                         
     Character length.... 16 Bits                                                 
     Pointer length....... 64 Bits                                                
     Work process number.. 0                                                      
     Shortdump setting.... "full"                                                                               
Database server... "btrcmap6"                                                
     Database type..... "ORACLE"                                                                               
Database name..... "AP7"                                                          
     Database user ID.. "SAPSR3"                                                                               
Char.set.... "C"                                                                               
SAP kernel....... 700                                                             
     created (date)... "Apr 2 2006 20:44:50"                                           
     create on........ "AIX 2 5 005DD9CD4C00"                                          
     Database version. "OCI_101 "                                                                               
Patch level. 52                                                                   
     Patch text.. " "                                                                               
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."    
     SAP database version. 700                                                         
     Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
Memory consumption                                                                
     Roll.... 16192                                                                    
     EM...... 8379696                                                                  
     Heap.... 0                                                                        
     Page.... 40960                                                                    
     MM Used. 1830352                                                                  
     MM Free. 2356896                                                                               
User and Transaction                                                                               
Client.............. 000                                                          
     User................ "DDIC"                                                       
     Language key........ "E"                                                          
     Transaction......... "SE38 "                                                                               
Transactions ID..... " "                                                                               
Program............. "SAPLWBABAP"                                               
     Screen.............. "SAPLWBABAP 0100"                                          
     Screen line......... 5                                                                               
Information on where terminated                                                     
     Termination occurred in the ABAP program "SAPLWBABAP" - in "SET_STATUS".        
     The main program was "RSABAPPROGRAM ".                                                                               
In the source code you have the termination point in line 23                    
     of the (Include) program "LWBABAPO00".                                                                               
Source Code Extract                                                                               
Line  SourceCde                                                                               
1 *----
     2 *   INCLUDE LWBABAPO00                                                 *      
     3 *----
     4                                                                               
5 *----
     6 *       MODULE SET_STATUS                                                     
     7 *----
     8 *       Status und Titlebar                                                   
     9 *----
    10 MODULE SET_STATUS OUTPUT.                                                     
    11                                                                               
12 * Programmnamen setzen                                                        
    13   if rs38m-programm is initial                                           
    14   or xcode = copy                                                        
    15   or xcode = renm.                                                       
    16     GET PARAMETER ID 'RID' FIELD RS38M-PROGRAMM.                         
    17   endif.                                                                 
    18                                                                               
19 * Änderungen in Einstellungen?                                           
    20   perform settings_check using settings.                                 
    21                                                                               
22   REFRESH EXCLTAB.                                                       
>>>>>   CALL FUNCTION 'RS_WORKING_AREA_ACTIVE_CHECK' "Aktive/Inaktive Sourcen  
    24        EXCEPTIONS                                                        
    25             NOK     = 1                                                  
    26             OTHERS  = 2.                                                 
    27   IF SY-SUBRC NE 0.                                                      
    28     HANDLE_ACTIVE_SOURCES = NO.                                          
    29     EXCLTAB-FUNCTION = AKTI.                                             
    30     APPEND EXCLTAB.                                                      
    31     EXCLTAB-FUNCTION = INAC.                                             
    32   ELSE.                                                                  
    33     HANDLE_ACTIVE_SOURCES = YES.                                         
    34   ENDIF.                                                                 
    35                                                                               
36   call 'C_SAPGPARAM' id 'NAME'  field 'transport/systemtype'             
    37                      id 'VALUE' field system_id.                         
    38   if system_id ne 'SAP'.                                                 
    39     EXCLTAB-FUNCTION = SYCR.                                             
    40     APPEND EXCLTAB.                                                      
    41   endif.                                                                 
    42                                                                               
Cannot use SM37, SE38, SM50 etc to watch the process, or do anything.     I am thinking to manually run the RDDIMPDP or RDDNEWPP from unix level.  Need help!!
Thanks.
Amy

Similar Messages

  • PM: change all Orders from sub-operation to operation level

    Hi Folks,
    I've a requirement to change all PM-Orders from Operation-SubOperation to only Operation Level.
    Example:
    Op SubOp --> New Op   (no subOp)
    10__10__-->____10
    10__11__-->____11
    10__12__-->____12
    10__13__-->____13
    10__14__-->____14
    20__10__-->____20
    20__11__-->____21
    Does someone here know, how I can make do this in an easy and save way?
    The only way I see is to make an own report with calling BAPI BAPI_ALM_ORDER_MAINTAIN.
    Have someone another solution
    - SAP-Standard-Report?
    - LSMW?
    Regards

    Hi Raghu,
    Many Thanks for your quick reply.
    Okay ... no LSMW.
    And also no Standard-Reports?
    Do you think, making my own program is the best way?
    Regards,
    Daniel

  • Error in operation level result recording

    Hi,
    I need held; result recording of inspection type =03 (operation level Quality inspection)
    A product manufacture via three operations (10, 20, 30)
    All operation quality inspection active let operation no-10, all products reject and confirm as rework.
    Next operation level quality record is done but confirmation not allow Reason is operation -10, rework quantity, (Actual quantity is more than planned quantity)
    How to add the quantity after reworks for next operation quality inspection?
    Pl helps me finding the solution.

    Hi,
    As per your more clearence , As per Example  production order Quanity =1, passes 3 operation10,20,30
    Operation=10 require rework as per quality ,
    Operation =20 system raise the error message = Operation =10 rework .
    If want to operation =10 ok Quantity =1 then system raise error messges =Actual quanity more than planned Quanitity
    ( 1 Rework + 1 Ok ) .
    Supose rework order create and confirm then next 20 & 30 operation how complete .
    Real scenerio :- Rework on operation =10 then again Quality check then goes to 20 operation Quality check pass / Rework if rework then again quality pass then goes to next operation level
    I hope under stand my problem
    Need help- please

  • Release of Production Order at operation level

    Dear Experts,
    Production order to be released at operation level automatically one by one, after confirmation of operation.
    Let us suppose
    Op 10 ...... 10 Confirmed
    Op 20 ...... 10 Confirmed
    then in the Op 30 ..... 4 Qunatity to be released automatically once Operation 20 is confirmaed.
    Please give your valuble inputs
    regards
    Ram Kumar

    Dear Experts,
    Production order to be released at operation level automatically one by one, after confirmation of operation.
    Let us suppose
    Op 10 ...... 10 Confirmed
    Op 20 ...... 10 Confirmed
    then in the Op 30 ..... 4 Quantity to be released automatically once Operation 20 is confirmed.
    How to create trigger point for this?
    Can anybody give clear idea, what all the fields I need to maintain ?
    regards
    Ram Kumar

  • How to see the current drill-level?

    Hello,
    I want to apply some conditional formating on a report with drill-down function, depending on the drill-level of the report.
    Question: How can I determine on which level the user currently is in order to apply my formating?
    Thank you
    Turalf

    If you don't want to install any extensions, then I think at best you might take a look at toolkit.zoomManager.zoomValues preference (in about:config). It gives you information about available zoom levels, but you have to remember how many times zoom in/zoom out actions were used (i.e. there is no current zoom level indicator like in e.g. Opera). For example .3,.5,.67,.8,.9,1,1.1,1.2,1.33,1.5,1.7,2,2.4,3 means that you have:
    Levels down (five):
    '''30%''' 50% 67% 80% 90%
    Levels up (eight):
    110% 120% 133% 150% 170% 200% 240% '''300%'''

  • Inspection Point at Operation Level

    In inspection plan of a material there are 2 operations.Out of these 2 operations, i want to assign inspection point only for 1 operation.and for 2nd operation i dont want inspection point.but as it is a header level data,i am not able to do it.so how can i do this?

    Hi
    Then by std method it is very difficult to achieve.This may need some enhancement in QP01/QE11/QF01.
    Here you have to make sure that for which operation you don't want Inspection point even if you have maintained in header of QP01.How will you differeciate this operation from other.
    May be you can try user exit :QAPP0001
    The user exit EXIT_SAPLQAPP_001 is called from module QAPP_IP_CREATE_1.
    This module is run through when you go into the create, change and
    display transactions for the results recordings. This is independent of
    whether the inspection point data screen is called up at a later time.
    Regards
    Sujit

  • Maintain different unit of measure at operation level

    HI
    I am working on a scenario where I have to maintain product in different units after each operation for a material. like i am working on SFG to get FG in 3 steps. my base unit of measure is lb. I maintain my product after 1st operation in lb, after 2nd operation in PC, and after 3rd operation again in PC. but weight of Piece after II & III operation are not same. how can i maintain relation between PC & lb at operation level. is it possible?
    regards
    Rajesh

    Hi,
    1. Routing can be created for one header unit of measure only
    2. But in the routing we can have different "Operation Unit"
    3. In the routing in the operation details  there is a unit of measure conversion details
    1 header unit = 1 operation unit
    4. In your case you need to maintain this which can solve your problem.
    Kindly let me know if this is useful or if it doesnt work we can find alternate solution for the same.
    thanks

  • Rework activities in operation level in routing

    HI SAP GURUS,
    As per blue print   rework is to be treated  as a additional operation in the routings, where ever required. In shop floor control activities  client  requires for a check for rework activity  in each operation level , they have 21 operations. Please clarify is it really viable to go for a rework check in each operation level,  how I can set the rework operation in routing.?
    thanks,

    Hi
    Yow can follow the below procedure to create a rework order and Assign it to the trigger point
    1.) Create Reference Operation Set ( T.code ca11)
    2.) Create Standard Trigger Point (T.Code co31)
    Enter the Trigger Point usage /Group as FERT.
    Tick the Trigger Point Functions.
    3.) Enable the indicator creates order with Reference.
    4.) Enter the system status as PCNF.
    5.) Enter change as +.
    6.) Enable the indicator once.
    7.) Now place the cursor on the create order with reference.
    8.) Goto Parameters.
    9.) In the Parameter enter in the group the created Reference op set group no.
    Reward points if usefull
    Regards
    Palaniappan

  • Costs at Operation Level

    Hi,
    I know that Costs at Operation Level is possible in Ehp6 version of ECC 6.0, but in our system it is not available/not showing. I hope some business function need to activate to get the Costs at Operation Level node,
    Any body have idea how to activate this node in spro?
    Thanks in advance.
    Best Regards
    Kalyan

    Hi Kalyan,
    Probably following is the Business Function/s you are searching for.
    LOG_EAM_OLC (EHP5)
    To use detailed planning, capture and reporting of costs at the order operation level. The operations have their own settlement rules enabling more accurate cost updating of multiple assets maintained using a single PM/CS order.
    LOG_EAM_OLC_2 (EHP6)
    To use enhanced BI content and XI/ESR content to read and analyse OLC data.
    Jogeswara Rao K

  • Release the order on operation level

    Hi,
    Currently we are releasing the complete production order. But Now we want to release the order operation by operation. How can we do that?
    Regards
    deepak sharma

    Hi Deepak,
    I think that you have already realesed the order at header level and now you want to realese the production order at operation level. If this is correct,then follow step as below.
    1.Goto CO02
    2.Select Function,then Read PP master data.continue,enter & save. So status of order will be changed to created.
    3. Now follow the step given by SAP PP consultant.
    Hope this help you.
    Regards,
    Raja.

  • Standard Report for missing parts at production order operation level?

    Hi PP Gurus,
                We have standard report for missing parts at production orders level.
    For our client, they need a report for missing parts analysis at production order operation level. Do we have any such standard report in the SAP?
    Please help.
    Thanks,
    Reddy.

    Hi Arvind,
          Thanks for for your response.
    1. List: Components,  Layout: Standard layout          set the Missing part
           It shows the component requirement/withdrawn  quantity for each operation of production order. It is not showing the commit quantity.
    2. List: Components,  Layout: Pick list          set the Missing part
           It shows the component requirement/withdrawn  quantity for each production order.
    3. List: Components,  Layout: Missing Parts List-Material View          set the Missing part
           It shows the component requirement/commit quantity for each production order. It is not showing the commit quantity at opertion level.
    4. List: Components,  Layout: Missing Parts List-Order View          set the Missing part
           It shows the component requirement/commit quantity for each production order. It is not showing the commit quantity at opertion level.
          We are unable to get the solution from all these 1 to 4 reports from COOIS.
    Do we have any option to change the existing layout (ex: 3 ) to get the commit quantity for operation with missing parts indicator?
    If avilable, what is the procedure to be followed?
    Thanks,
    Reddy.

  • How to use multiple WSDL operations in One BPEL process Recieve Activity ?

    Is there anyway to attach multiple WSDL operations with a Single BPEL process ? How ?

    Thanks Melvin for your quick respond.
    When I create a BPEL process, It asks me to give the XSD as an Input. When I import the XSD it asks me to select an operation not more than one. Let suppose I select addRequest and finish the wizard.
    Now what I can see, It create Recieve activity with an Input msg of Add operation. Well what I understand from your statement is that, I remove the recieve activity and put the Pick activity.
    Now my question is How to mention the other operations like update and delete ? And how to test them ?? The link provided by you is just tell me what Pick activity can do for me, But its not telling me how to use it ?? and how the give the operation to it. Where should I need to change in the BPEL ???

  • HT1338 Purchased a used macbook pro with Mountain Lion. My old Mac runs Snow Leopard is backed up to Time machine. How do I register the operating system to me and how do I use Time Machine to move my files to the new used computer?

    Purchased a used macbook pro with Mountain Lion. My old Mac runs Snow Leopard is backed up to Time machine. How do I register the operating system to me and how do I use Time Machine to move my files to the new used computer?

    If you look at the User Tips tab, you will find a write up on just this subject:
    https://discussions.apple.com/docs/DOC-4053
    The subject of buying/selling a Mac is quite complicated.  Here is a guide to the steps involved. It is from the Seller's point of view, but easily read the other way too:
    SELLING A MAC A
    Internet Recovery, and Transferability of OS & iLife Apps
    Selling an Old Mac:
    • When selling an old Mac, the only OS that is legally transferable is the one that came preinstalled when the Mac was new. Selling a Mac with an upgraded OS isn't doing the new owner any favors. Attempting to do so will only result in headaches since the upgraded OS can't be registered by the new owner. If a clean install becomes necessary, they won't be able to do so and will be forced to install the original OS via Internet Recovery. Best to simply erase the drive and revert back to the original OS prior to selling any Mac.
    • Additionally, upgrading the OS on a Mac you intend to sell means that you are leaving personally identifiable information on the Mac since the only way to upgrade the OS involves using your own AppleID to download the upgrade from the App Store. So there will be traces of your info and user account left behind. Again, best to erase the drive and revert to the original OS via Internet Recovery.
    Internet Recovery:
    • In the event that the OS has been upgraded to a newer version (i.e. Lion to Mountain Lion), Internet Recovery will offer the version of the OS that originally came with the Mac. So while booting to the Recovery Disk will show Mountain Lion as available for reinstall since that is the current version running, Internet Recovery, on the other hand, will only show Lion available since that was the OS shipped with that particular Mac.
    • Though the Mac came with a particular version of Mac OS X, it appears that, when Internet Recovery is invoked, the most recent update of that version may be applied. (i.e. if the Mac originally came with 10.7.3, Internet Recovery may install a more recent update like 10.7.5)
    iLife Apps:
    • When the App Store is launched for the first time it will report that the iLife apps are available for the user to Accept under the Purchases section. The user will be required to enter their AppleID during the Acceptance process. From that point on the iLife apps will be tied to the AppleID used to Accept them. The user will be allowed to download the apps to other Macs they own if they wish using the same AppleID used to Accept them.
    • Once Accepted on the new Mac, the iLife apps can not be transferred to any future owner when the Mac is sold. Attempting to use an AppleID after the apps have already been accepted using a different AppleID will result in the App Store reporting "These apps were already assigned to another Apple ID".
    • It appears, however, that the iLife Apps do not automatically go to the first owner of the Mac. It's quite possible that the original owner, either by choice or neglect, never Accepted the iLife apps in the App Store. As a result, a future owner of the Mac may be able to successfully Accept the apps and retain them for themselves using their own AppleID. Bottom Line: Whoever Accepts the iLife apps first gets to keep them.
    SELLING A MAC B
    Follow these instructions step by step to prepare a Mac for sale:
    Step One - Back up your data:
    A. If you have any Virtual PCs shut them down. They cannot be in their "fast saved" state. They must be shut down from inside Windows.
    B. Clone to an external drive using using Carbon Copy Cloner.
    1. Open Carbon Copy Cloner.
    2. Select the Source volume from the Select a source drop down menu on the left side.
    3. Select the Destination volume from the Select a destination drop down menu on the right
    side.
    4. Click on the Clone button. If you are prompted about creating a clone of the Recovery HD be
    sure to opt for that.
    Destination means a freshly erased external backup drive. Source means the internal
    startup drive. 
    Step Two - Prepare the machine for the new buyer:
    1. De-authorize the computer in iTunes! De-authorize both iTunes and Audible accounts.
    2, Remove any Open Firmware passwords or Firmware passwords.
    3. Turn the brightness full up and volume nearly so.
    4. Turn off File Vault, if enabled.
    5. Disable iCloud, if enabled: See.What to do with iCloud before selling your computer
    Step Three - Install a fresh OS:
    A. Snow Leopard and earlier versions of OS X
    1. Insert the original OS X install CD/DVD that came with your computer.
    2. Restart the computer while holding down the C key to boot from the CD/DVD.
    3. Select Disk Utility from the Utilities menu; repartition and reformat the internal hard drive.
    Optionally, click on the Security button and set the Zero Data option to one-pass.
    4. Install OS X.
    5. Upon completion DO NOT restart the computer.
    6. Shutdown the computer.
    B. Lion and Mountain Lion (if pre-installed on the computer at purchase*)
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because
    it is three times faster than wireless.
    1. Restart the computer while holding down the COMMAND and R keys until the Mac OS X
    Utilities window appears.
    2. Select Disk Utility from the Mac OS X Utilities window and click on the Continue button. 
    3. After DU loads select your startup volume (usually Macintosh HD) from the left side list. Click
    on the Erase tab in the DU main window.
    4. Set the format type to Mac OS Extended (Journaled.) Optionally, click on the Security button
    and set the Zero Data option to one-pass.
    5. Click on the Erase button and wait until the process has completed.
    6. Quit DU and return to the Mac OS X Utilities window.
    7. Select Reinstall Lion/Mountain Lion and click on the Install button.
    8. Upon completion shutdown the computer.
    *If your computer came with Lion or Mountain Lion pre-installed then you are entitled to transfer your license once. If you purchased Lion or Mountain Lion from the App Store then you cannot transfer your license to another party. In the case of the latter you should install the original version of OS X that came with your computer. You need to repartition the hard drive as well as reformat it; this will assure that the Recovery HD partition is removed. See Step Three above. You may verify these requirements by reviewing your OS X Software License.

  • How can i NOT include top level keyword in the metadata of an image?

    Hello,
    I want to know how can i NOT include top level keyword in the metadata of an image. I know there is an option for not applying a keyword to an exported image, but is there an option for not applying the top level keyword to the actual image?
    I have organized my geographical (by location) keywords like this:
    Places
    USA
    New York
    Miami
    Spain.
    If i add geographical keywords to all my images, all my images will have the keyword "Places", i dont think that it have any sence to have all your images with one keyword. How can i fix this? Any sugestion? i will appreciate it a lot any help or information that you could give me.
    Excuse my english, i know it is not good. I hope that you could understand me.
    Thanks,
    Marcelo :)

    Explicitly excluding a keyword only applies when "exporting". Unfortunately, there's currently no way to stop the keyword being written to the file when "Save Metadata to File" command is used. The natural reaction of users to this difference is to suggest that it is stupid. Nevertheless, there are good reasons why the difference exists:
    1. "Export" creates a new file whereas "Save Metadata to File" writes the metadata back into the existing file.
    2. There are very good reasons why certain keywords should not be written to file, and the example given in the OP is one. Saving metadata to file is more often used as means of backing up important image related metadata, independently of the catalog or allowing the metadata to be visible in other aplications. It would be rare that such a file would be shared with a third party, so the reason for not including certain keywords is less obvious. Actually, not including it can result in no end of confusion and grief. For example, if the top level (or any keyword) was excluded during the save metadata process then the other keywords would be orphaned when image is imported back into the catalog (e.g. buiding a new catalog).
    The development team are aware of the need, in some circumstances, to exclude certain keywords when save metadata command is used. How and when the issue is resolved, without adding even more confusion/complexity, is some way off.

  • How to remove xmlns in node level

    Hi Experts!
    How to remove xmlns in node level in response xml file. I tried to use AF_Modules/XMLAnonymizerBean, but it did not work.
    Can you please help me out on this.
    I want to remvoe  xmlns tag in LEVICOM
    Eg:
    - <Addenda>
       - <LEVICOM xmlns="">
    Thanks,
    Hari

    Hi Expers!
    Please help me out on this. The below xslt mapping working only to remove xmlns prefix in xml file, if parent having only one child. This code is not working if parent having multiple childs.
    Eg:  <parent>
               <phild  xmlns="">
                 test1
                </phild>
            </parent>
    The above example working fine with below xslt mapping to remove xmlns tag.
    Second scenarion  not working
    Eg:  <parent>
              <child1  xmlns="">
                 test1
              </child1>
              <child2  xmlns="">
                  test2
               </child2>
            </parent>
    The above example is not working.
    Here is the code:
    You can remove the namespace prefixes using an XSLT mapping if they are causing problems with applications outside of XI.
    Try the following code:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns="http://www.arconw.com/XI/XSLT_Library/XmlNamespacePrefixRemoval"
    version="1.0">
    <xsl:output method = "xml" />
    <xsl:template match="/">
    <xsl:apply-templates select="*" mode="remprefix"/>
    </xsl:template>
    <xsl:template match="*" mode="remprefix">
    <xsl:variable name="newname" select="local-name(.)"/>
    <xsl:element name="{$newname}" namespace ="{namespace-uri()}">
    <xsl:apply-templates mode="copyall" select="@*|comment()|processing-instruction()|text()"/>
    <xsl:apply-templates select="*" mode="remprefix"/>
    </xsl:element>
    </xsl:template>
    <xsl:template mode="copyall" match="@*|comment()|processing-instruction()|text()">
    <xsl:copy>
    <xsl:apply-templates mode="copyall" select="@*|comment()|processing-instruction()|text()"/>
    </xsl:copy>
    </xsl:template>
    </xsl:stylesheet>
    Thanks,
    Hari

Maybe you are looking for