SRM: Transformation Error

Dear Experts,
When activating the Transforamtions DSO--> Datasource.
Error Message: Start Routine Syntax Error.
I checked the syntax for the start routine
Error Msg: In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter "SOURCE_PACKAGE" is incompatible with the formal parameter"DATA_PACKAGE".
When I checked the ROUTINE_9998, no. of fields in datasource are not equal to no. of fields in target.
I hope this is not the issue.
Would anyone suggest on how to cope with this issue ??
Regards
KV

Hi,
The error "SOURCE_PACKAGE" is incompatible with the formal parameter "DATA_PACKAGE is a version problem.
Take a look at your routine and use SOURCE_PACKAGE and ABAP OO instead of DATA_PACKAGE.
or
When getting an error 9998 in running means that your start routine encountered an abort command.
Have you programmed an ABORT statement somewhere in your start routine yourself?
Or is this a Compile error?
By the way: your error message also seems to indicate a version problem.
Data_package is 3.x language, source_package = 7.0 language.
or
think in function call of 'ROUTINE_9998' the parameter 'Source_package' is causing problem rather pass the parameter that is the technical name of the ods /bic/a*... try this
or
check the routine_9998...i guess there the parameter definition is for data_package but since u r using a transformation and sending the source_package..it is not accepting..compatilibity issue.
Regards,
MARASA.

Similar Messages

  • How can I display XSLT transformer errors on a web page ?

    Hi,
    I have some JSP pages that access DB, create an XML based on DB data and then transform it into HTML through an XSLT stylesheet. Developing the XSL code it's easy to make mistakes and generate errors on trasformation, but what I receive on the web page is only a "Could not compile stylesheet" TransformerConfigurationException, while the real cause of the error is displayed only on tomcat logs. This is the code for transformation:
    static public void applyXSLT(Document docXML, InputStream isXSL, PrintWriter pw) throws TransformerException, Exception {
            // instantiate the TransformerFactory.
            TransformerFactory tFactory = TransformerFactory.newInstance();
            // creates an error listener
            XslErrorListener xel = new XslErrorListener();
            // sets the error listener for the factory
            tFactory.setErrorListener(xel);
            // generate the transformer
            Transformer transformer = tFactory.newTransformer(new SAXSource(new InputSource(isXSL)));
            // transforms the XML Source and sends the output to the HTTP response
            transformer.transform(new DOMSource(docXML), new StreamResult(pw));
    }If an exception is thrown during the execution of this code, its error message is displayed on the web page.
    This is the listener class:
    public class XslErrorListener implements ErrorListener {
        public XslErrorListener() {
        public void warning(TransformerException ex) {
            // logs on error log
            System.err.println("\n\nWarning on XEL: " + ex.getMessage());
        public void error(TransformerException ex) throws TransformerException {
            // logs on error log
            System.err.println("\n\nError on XEL: " + ex.getMessage());
            // and throws it
            throw ex;
        public void fatalError(TransformerException ex) throws TransformerException {
            // logs on error log
            System.err.println("\n\nFatal Error on XEL: " + ex.getMessage());
            // and throws it
            throw ex;
    }When I have an error in the XSL stylesheet (for examples a missing closing tag), I can find on tomcat logs the real cause of the error:
    [Fatal Error] :59:10: The element type "table" must be terminated by the matching end-tag "</table>".
    Error on XEL: The element type "table" must be terminated by the matching end-tag "</table>".but on my web page is reported just the TransformerConfigurationException message that is:
    "Could not compile stylesheet".
    How can I display the real cause of the error directly on the web page?
    Thanks,
    Andrea

    This code is part of a bigger project that let developers edit XSL stylesheets through a file upload on the system and we can't impose the use of any tool for checking the xsl. So, I need to display the transformer error on the web page.I see. This code is part of an editorial/developmental tool for developers to create and edit XSL stylesheets.
    As part of the editorial process, XSL errors during editing can be considered a normal condition. In other words, it is normal to expect that the developers will generate XSL errors as they are developing stylesheets.
    In this light, handling the XSL transformation errors is a business requirement that you need to handle. Using the Java Exceptions mechanisms, e.g. try / catch are inappropriate to handle business requirements, in my opinion.
    I suggest that you look at how you handle the occurence of XSL errors differently than what you currently have. You need to:
    (1) capture the Transformation exception on the server;
    (2) extract the message from the exception and put it into a message that can be easily understood by the user;
    The current error message that you have going to the web browser is not useful.
    And you should not have the Transformation exception sent to the web browser either.
    What you are attempting to do with the exception is not appropriate.
    Handle the Transformation exception on the Business tier and use it to create a useful message that is then sent to the Presentation tier. In other words, do not send Java exceptions to web browser.
    />

  • XML to Internal table using XSLT by CALL TRANSFORMATION error

    Dear experts,
    I have to fetch the data from an XML file using XSLT into internal tables. The XML file is very big as following:-
    <?xml version="1.0" standalone="yes" ?>
    - <Shipment>
      <shipmentID>25091203S000778</shipmentID>
      <manifestDateTime>2009-12-03T20:16:52.00</manifestDateTime>
      <shipmentFacilityNumber>025</shipmentFacilityNumber>
      <shipmentFacilityAbbreviation>CHI</shipmentFacilityAbbreviation>
      <shipmentFacilityAddress1>810 KIMBERLY DRIVE</shipmentFacilityAddress1>
      <shipmentFacilityAddress2 />
      <shipmentFacilityCity>CAROL STREAM</shipmentFacilityCity>
      <shipmentFacilityState>IL</shipmentFacilityState>
      <shipmentFacilityPostalCode>601880000</shipmentFacilityPostalCode>
      <shipmentTruckCarrierCode>X150</shipmentTruckCarrierCode>
      <shipmentSourceCode>T</shipmentSourceCode>
      <userID>CAMPOSG</userID>
    - <Delivery>
      <primaryCustomerNumber>954371</primaryCustomerNumber>
      <primaryCustomerName>MIDWEST OFFICE SUPPLY</primaryCustomerName>
      <primaryCustomerAddress1 />
      <primaryCustomerAddress2>4765 INDUSTRIAL DR</primaryCustomerAddress2>
      <primaryCustomerCity>SPRINGFIELD</primaryCustomerCity>
      <primaryCustomerState>IL</primaryCustomerState>
      <primaryCustomerPostalCode>627030000</primaryCustomerPostalCode>
      <primaryCustomerPhoneNumber>2177535555</primaryCustomerPhoneNumber>
      <shuttleStopFacilityNumber />
      <billOfLadingNumber>25HZK99</billOfLadingNumber>
      <carrierProNumber />
      <shipmentTotalCartonCount>6</shipmentTotalCartonCount>
      <shipmentTotalWeight>266</shipmentTotalWeight>
    - <order>
      <orderNumber>25HZK99</orderNumber>
      <subOrderNumber />
      <dateProcessed>2009-12-03</dateProcessed>
      <primaryOrderNumber />
      <shipTruckCode>X150</shipTruckCode>
      <shipTruckDescription>UDS - ADDISON</shipTruckDescription>
      <shipTruckPriorityCode>01</shipTruckPriorityCode>
      <shipTruckGroupCode>01</shipTruckGroupCode>
      <shipTruckDepartureTime>20.00.00</shipTruckDepartureTime>
      <shipTruckDockID>07</shipTruckDockID>
      <ldpFacilityAbbreviation />
      <shuttleAvailableIndicator>N</shuttleAvailableIndicator>
      <shuttleMessageText />
      <crossDockFacilityCode />
      <crossDockTruckCode />
      <crossDockID />
      <subsidizedFreightTruckID />
      <customerPurchaseOrderNumber>623559</customerPurchaseOrderNumber>
      <headerTypeCode>P</headerTypeCode>
      <orderTypeID>RG</orderTypeID>
      <deliveryTypeID>DS</deliveryTypeID>
      <deliveryMethodCode />
      <customerBarCode />
      <customerReferenceData>25HZK99</customerReferenceData>
      <customerReferenceText />
      <customerRouteData>ZNED UNTED</customerRouteData>
      <customerRouteText>ROUTE</customerRouteText>
      <endConsumerPurchaseOrderNumber />
      <endConsumerPurchaseOrderText />
      <endConsumerName>CHARLESTON TRANS. FACILITY</endConsumerName>
      <endConsumerAddress1>HOMEWOOD DT PROGRAM DEPT. 3</endConsumerAddress1>
      <endConsumerAddress2>17341 PALMER BLVD.</endConsumerAddress2>
      <endConsumerAddress3 />
      <endConsumerCity>HOMEWOOD</endConsumerCity>
      <endConsumerState>IL</endConsumerState>
      <endConsumerPostalCode>60430</endConsumerPostalCode>
      <endConsumerCountryCode />
      <fillFacilityNumber>025</fillFacilityNumber>
      <shpFacilityNumber>025</shpFacilityNumber>
      <homeFacilityAbbrCode>STL</homeFacilityAbbrCode>
      <homeFacilityNumber>015</homeFacilityNumber>
      <multiCartonIndicator>Y</multiCartonIndicator>
      <primaryCustomerIndicator>Y</primaryCustomerIndicator>
      <shipToCustomerNumber>954371001</shipToCustomerNumber>
      <customerCompanyID>01</customerCompanyID>
      <customerTruckID>U888</customerTruckID>
      <customerTruckDescription>UDS - ADDISON</customerTruckDescription>
      <customerTruckDockID>13</customerTruckDockID>
      <thirdPartyBillCarrier />
      <thirdPartyBillID />
      <thirdPartyBillType />
      <qualityCheckIndicator>N</qualityCheckIndicator>
      <warehouseLaydownID />
      <packListPosition>I</packListPosition>
      <preferredPackingType>CTN</preferredPackingType>
      <preferredPackingMaterial>PAPER</preferredPackingMaterial>
      <preferedPackingInstructions />
      <totalOrderCartonQty>6</totalOrderCartonQty>
      <convertAddressIndicator>N</convertAddressIndicator>
      <dealerInstructionIndicator>Y</dealerInstructionIndicator>
      <dealerinstructions1>CPO#: 623559</dealerinstructions1>
      <dealerinstructions2>ATTN: DANA GRIFFIN</dealerinstructions2>
      <dealerinstructions3>INFO: 612</dealerinstructions3>
      <dealerinstructions4>ROUTE: ZNED UNTED</dealerinstructions4>
      <dealerinstructions5 />
      <dealerinstructions6 />
      <shippingInstructionsIndicator>N</shippingInstructionsIndicator>
      <shippingInstructions1 />
      <shippingInstructions2 />
      <shippingInstructions3 />
      <shippingInstructions4 />
      <shippingInstructions5 />
      <shippingInstructions6 />
      <specialInstructionsIndicator>N</specialInstructionsIndicator>
      <specialInstructions1 />
      <specialInstructions2 />
      <customeContainerDesc />
    - <carton>
      <deliveryCartonID>253370905995</deliveryCartonID>
      <shipIndicator>Y</shipIndicator>
      <deliveryPalletID>X150</deliveryPalletID>
      <consolidatedDeliveryCartonID />
      <scanDateTime>2009-12-03T19:36:12.00</scanDateTime>
      <cartonWeight>52</cartonWeight>
      <dropShipFlag>1</dropShipFlag>
      <carrierTrackingNumber />
      <carrierZoneID>0</carrierZoneID>
      <codAmount />
      <customerPackageAmount />
      <declaredValue />
      <residentialDeliveryIndicator />
      <serviceTypeCode>00</serviceTypeCode>
      <ssccCode>006860244400829393</ssccCode>
    - <Item>
      <shipPrefix>UNV</shipPrefix>
      <shipStockNumber>21200</shipStockNumber>
      <itemDescription>PAPER XERO/DUP WE LTR 20#</itemDescription>
      <orderQuantity>1</orderQuantity>
      <originalShipQuantity>1</originalShipQuantity>
      <shipQuantity>1</shipQuantity>
      <inventoryUnitCode>CT</inventoryUnitCode>
      <inventoryWeightQuantity>52.000</inventoryWeightQuantity>
      <upcNumber>00000000000000</upcNumber>
      <upcRetailCode>087547212004</upcRetailCode>
      <hazmatIndicator>N</hazmatIndicator>
      <serialRequiredIndicator>N</serialRequiredIndicator>
      <dealerMemoPO>S</dealerMemoPO>
      <cartonLineNumber>1</cartonLineNumber>
      <orderLineNumber>11</orderLineNumber>
      <originalOrderPrefix>UNV</originalOrderPrefix>
      <originalOrderStockNumber>21200</originalOrderStockNumber>
      <reasonCode />
    - <Item_Serial>
      <serialNumber />
      </Item_Serial>
        </Item>
      </carton>
       </order>
      </Delivery>
      </Shipment>
    This is not the complete XML file as it exceeds the 15000 characters and then I cann't post here. So I have deleted much part of it.
    The hierarchy is as following: Shipment->Delivery->Order->Carton->Item.
    I have created a XSLT for it which is working fine.
    But when I execute my report program it gives CX_SY_XSLT_FORMAT_ERROR saying that
    Transformation error:  Non-canonical structure of element name XML_OUTPUT.

    Dear experts,
    My report program is as following:-
    *& Report  Z_ASNTRNS
    REPORT  Z_ASNTRNS.
    *& Report  Z_ASNTRNS
    TYPE-POOLS: abap, ixml.
    TABLES: ZASN_SHIPMENT,ZASN_DELIVERY,ZASN_ORDER,ZASN_CARTON,ZASN_ITEM.
    *CONSTANTS gs_file TYPE string VALUE 'C:Documents and SettingsC5134126DesktopRajesh_kandakatlaSampleASNFile.xml'.
    This is the structure for the data from the XML file
    TYPES: BEGIN OF ts_item,
          ZSHIPMENT LIKE ZASN_ITEM-ZSHIPMENT,
          VBELN LIKE ZASN_ITEM-VBELN,
          ORDER_NUMBER LIKE ZASN_ITEM-ORDER_NUMBER,
          CARTON_ID LIKE ZASN_ITEM-CARTON_ID,
           ITEM LIKE ZASN_ITEM-ITEM,
           CARTON_LINE_NUM LIKE ZASN_ITEM-CARTON_LINE_NUM,
           CARTON_LINE_NUMBER LIKE ZASN_ITEM-CARTON_LINE_NUM,
          AEDAT(8),
          AEZET(6),
           ITEM_DESCRIPTION LIKE ZASN_ITEM-ITEM_DESCRIPTION,
           ORD_QTY(16),
           ORIGINAL_SHIP(16),
           SHIP_QTY(16),
           UPC_NUMBER LIKE ZASN_ITEM-UPC_NUMBER,
           DEALER_MEMO_PO(5),
           ORDER_LINE_NUM LIKE ZASN_ITEM-ORDER_LINE_NUM,
          STATUS LIKE ZASN_ITEM-STATUS,
           END OF ts_item.
    TYPES: BEGIN OF ts_carton,
          ZSHIPMENT LIKE ZASN_CARTON-ZSHIPMENT,
          VBELN LIKE ZASN_CARTON-VBELN,
          ORDER_NUMBER LIKE ZASN_CARTON-ORDER_NUMBER,
           CARTON_ID LIKE ZASN_CARTON-CARTON_ID,
          AEDAT(8),
          AEZET(6),
           SHIP_INDICATOR LIKE ZASN_CARTON-SHIP_INDICATOR,
           TRACKING_NUMBER LIKE ZASN_CARTON-TRACKING_NUMBER,
           ZZCARTON_WGT(18),
           Item type ts_item,
           END OF ts_carton.
    TYPES: BEGIN OF ts_order,
          ZSHIPMENT LIKE ZASN_ORDER-ZSHIPMENT,
          VBELN LIKE ZASN_ORDER-VBELN,
           ORDER_NUMBER LIKE ZASN_ORDER-ORDER_NUMBER,
          AEDAT(8),
          AEZET(6),
           SUB_ORDER LIKE ZASN_ORDER-SUB_ORDER,
           ORDER_DATE(8),
           PRIMARY_ORDER LIKE ZASN_ORDER-PRIMARY_ORDER,
           CUSTOMER_PO LIKE ZASN_ORDER-CUSTOMER_PO,
           PRIMARY_ID LIKE ZASN_ORDER-PRIMARY_ID,
           SHIP_TO LIKE ZASN_ORDER-SHIP_TO,
          ANZPK(5),
           carton type ts_carton,
           END OF ts_order.
    TYPES: BEGIN OF ts_delivery,
          ZSHIPMENT LIKE ZASN_DELIVERY-ZSHIPMENT,
          VBELN LIKE ZASN_DELIVERY-VBELN,
          AEDAT(8) TYPE C,
          AEZET(6) TYPE C,
           PRIMARY_CUSTOMER LIKE ZASN_DELIVERY-PRIMARY_CUSTOMER,
           BILL_OF_LADING LIKE ZASN_DELIVERY-BILL_OF_LADING,
           CARTON_COUNT(5),
           TOTAL_WEIGHT(18),
           order type ts_order,
           END OF ts_delivery.
    TYPES: BEGIN OF ts_shipment,
           ZSHIPMENT LIKE ZASN_SHIPMENT-ZSHIPMENT,
           MANIFEST_DATE_TIME(25),
          AEDAT(8) TYPE C,
          AEZET(6) TYPE C,
          SDATE(8) TYPE C,
          STIME(6) TYPE C,
           SFACILITY_NUMBER LIKE ZASN_SHIPMENT-SFACILITY_NUMBER,
           ZZCARRIERCODE LIKE ZASN_SHIPMENT-ZZCARRIERCODE,
           Delivery type ts_delivery,
           END OF ts_shipment.
    TYPES: BEGIN OF ts_shipment1,
           ZSHIPMENT LIKE ZASN_SHIPMENT-ZSHIPMENT,
           MANIFEST_DATE_TIME(25),
           SFACILITY_NUMBER LIKE ZASN_SHIPMENT-SFACILITY_NUMBER,
           ZZCARRIERCODE LIKE ZASN_SHIPMENT-ZZCARRIERCODE,
           PRIMARY_CUSTOMER LIKE ZASN_DELIVERY-PRIMARY_CUSTOMER,
           BILL_OF_LADING LIKE ZASN_DELIVERY-BILL_OF_LADING,
           CARTON_COUNT(5),
           TOTAL_WEIGHT(18),
           ORDER_NUMBER LIKE ZASN_ORDER-ORDER_NUMBER,
           SUB_ORDER LIKE ZASN_ORDER-SUB_ORDER,
           ORDER_DATE(8),
           PRIMARY_ORDER LIKE ZASN_ORDER-PRIMARY_ORDER,
           CUSTOMER_PO LIKE ZASN_ORDER-CUSTOMER_PO,
           PRIMARY_ID LIKE ZASN_ORDER-PRIMARY_ID,
           SHIP_TO LIKE ZASN_ORDER-SHIP_TO,
           CARTON_ID LIKE ZASN_CARTON-CARTON_ID,
           SHIP_INDICATOR LIKE ZASN_CARTON-SHIP_INDICATOR,
           TRACKING_NUMBER LIKE ZASN_CARTON-TRACKING_NUMBER,
           ZZCARTON_WGT(18),
           ITEM LIKE ZASN_ITEM-ITEM,
           CARTON_LINE_NUM LIKE ZASN_ITEM-CARTON_LINE_NUM,
           CARTON_LINE_NUMBER LIKE ZASN_ITEM-CARTON_LINE_NUM,
           ITEM_DESCRIPTION LIKE ZASN_ITEM-ITEM_DESCRIPTION,
           ORD_QTY(16),
           ORIGINAL_SHIP(16),
           SHIP_QTY(16),
           UPC_NUMBER LIKE ZASN_ITEM-UPC_NUMBER,
           DEALER_MEMO_PO(5),
           ORDER_LINE_NUM LIKE ZASN_ITEM-ORDER_LINE_NUM,
           END OF ts_shipment1.
    TYPES: BEGIN OF t_xml_line,
                 data(256) TYPE x,
               END OF t_xml_line.
    *Typdefinition für Airplus
    *READ THE DOCUMENTATION "LASG_XML_INVOICE_BTM"!!!
    VARs beginning with "a_" are ATTRIBUTES
    DATA: l_ixml            TYPE REF TO if_ixml,
          l_streamfactory   TYPE REF TO if_ixml_stream_factory,
          l_parser          TYPE REF TO if_ixml_parser,
          l_istream         TYPE REF TO if_ixml_istream,
          l_ostream         TYPE REF TO if_ixml_ostream,
          l_document        TYPE REF TO if_ixml_document,
          l_node            TYPE REF TO if_ixml_node,
          l_xml TYPE REF TO cl_xml_document,
          l_xmldata         TYPE string.
    DATA: l_xml_table       TYPE TABLE OF t_xml_line,
             l_xml_line        TYPE t_xml_line,
             l_xml_table_size  TYPE i.
    DATA: l_filename        TYPE string.
    DATA: xml_out TYPE string ,
          size type i.
    DATA: l_xml_x1   TYPE xstring.
    DATA: l_len      TYPE i,
              l_len2     TYPE i,
              l_tab      TYPE tsfixml,
              l_content  TYPE string,
              l_str1     TYPE string,
              c_conv     TYPE REF TO cl_abap_conv_in_ce.
             l_itab     TYPE TABLE OF string.
    DATA: BEGIN OF l_itab occurs 0,
          data(256) type c,
          end of l_itab.
    TYPES : BEGIN OF TY_TEXT,
              data(255) type C,
            END OF TY_TEXT.
    DATA: F_XML TYPE STRING.
    DATA : LT_TEXT_OUT type table of TY_TEXT with header line.
    tables
    DATA: it_shipment    TYPE STANDARD TABLE OF ts_shipment,
          wa_shipment    TYPE  ts_shipment.
    *Errorvariables
    DATA: xslt_err   TYPE REF TO cx_xslt_exception,
          err_string TYPE string.
    PARAMETERS: pa_file TYPE localfile OBLIGATORY
    DEFAULT 'C:Documents and SettingsC5134126DesktopRajesh_kandakatlaSampleASNFile.xml'.
    START-OF-SELECTION.
      Creating the main iXML factory
        l_ixml = cl_ixml=>create( ).
      Creating a stream factory
        l_streamfactory = l_ixml->create_stream_factory( ).
        PERFORM get_xml_table CHANGING l_xml_table_size l_xml_table.
    here we use the CALL TRANSFORMATION method which calls
    the XSLT program "z_asnfile"
    TRY.
        CALL TRANSFORMATION ('Z_ASNFILE')
          SOURCE xml LT_TEXT_OUT[]
          RESULT xml_output = it_shipment
    catch any error, very helpful if the XSLT isn't correct
        CATCH cx_xslt_exception INTO xslt_err.
        err_string = xslt_err->get_text( ).
        WRITE: / 'Transformation error: ', err_string.
        EXIT.
      ENDTRY." setting a breakpoint to watch the workarea
    by the internal table "it_airplus"
           break-point.
      LOOP AT it_shipment INTO wa_shipment.
      ENDLOOP.
    *&      Form  get_xml_table
      FORM get_xml_table CHANGING l_xml_table_size TYPE i
                                  l_xml_table      TYPE STANDARD TABLE.
        l_filename = pa_file.
      upload a file from the client's workstation
        CALL METHOD cl_gui_frontend_services=>gui_upload
          EXPORTING
            filename   = l_filename
            filetype   = 'BIN'
          IMPORTING
            filelength = l_xml_table_size
          CHANGING
            data_tab   = l_xml_table
          EXCEPTIONS
            OTHERS     = 19.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                     WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
    Convert binary to text.
    CALL FUNCTION 'SCMS_BINARY_TO_TEXT'
      EXPORTING
        INPUT_LENGTH          = 70000
                FIRST_LINE            = 0
                LAST_LINE             = 0
                APPEND_TO_TABLE       = ' '
                MIMETYPE              = ' '
        WRAP_LINES            = 'X'
              IMPORTING
                OUTPUT_LENGTH         =
      TABLES
        BINARY_TAB            = l_xml_table
        TEXT_TAB              = LT_TEXT_OUT
              EXCEPTIONS
                FAILED                = 1
                OTHERS                = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM.                    "get_xml_table

  • XSLT Transformation error:  Non-canonical structure of element name

    Good day experts,
    I have recently started using xslt, and came upon the following demo in the sdn.
    http://wiki.sdn.sap.com/wiki/display/ABAP/XMLXSLTwith+ABAP
    I have retrieved the example xml files from airplus.com, as per the instructions, and implemented the code.
    When I test the xslt transformation in se80, it transforms correctly.
    However, when I run the program, I get the following error.
    CX_XSLT_FORMAT_ERROR
    Transformation error:  Non-canonical structure of element name XML_OUTPUT   
    Is there an error in the example that I am not aware of?
    Thanks in advance,
    Johan Kriek

    Found the solution.
    You rename the tag <XML_OUTPUT> to anything else like <TEST>. And Hurray!!! it works.
    It looks like SAP is using this name internally somewhere so we are getting error when we are using same name.
    Anyways the problem is solved.
    Regards,
    Jai

  • Detecting transform errors when using org.xml.sax.XMLFilter

    I am using javax.xml.transform.sax.SAXTransformerFactory.newXMLFilter to transform xml against a pipeline of stylesheets (See function testPipelineTransform in the example below). The process works okay, excepting that I cannot figure out how to detect errors in the transformation process.
    I would like to achieve the same result for the pipeline process as I would for a single transformation using javax.xml.transform.Transformer.setErrorListener. The example below demonstrates how the call to javax.xml.transform.Transformer.setErrorListener does not generate the same result when using org.xml.sax.XMLFilter as it does when using a single transformation.
    import javax.xml.parsers.ParserConfigurationException;
    import javax.xml.parsers.SAXParser;
    import javax.xml.parsers.SAXParserFactory;
    import org.xml.sax.SAXException;
    import org.xml.sax.InputSource;
    import org.xml.sax.XMLReader;
    import org.xml.sax.XMLFilter;
    import javax.xml.transform.ErrorListener;
    import javax.xml.transform.Source;
    import javax.xml.transform.Transformer;
    import javax.xml.transform.TransformerException;
    import javax.xml.transform.TransformerFactory;
    import javax.xml.transform.TransformerConfigurationException;
    import javax.xml.transform.sax.SAXTransformerFactory;
    import javax.xml.transform.sax.SAXSource;
    import javax.xml.transform.stream.StreamSource;
    import javax.xml.transform.stream.StreamResult;
    import java.io.*;
    public class FilterChain {
        static private final String newline = System.getProperty("line.separator");
         public static void main(String argv[]) {
              System.out.println("Testing pipeline transform");
              testPipelineTransform();
              System.out.println("Testing single transform");
              testXsltSingleTransform();
         } // main
         static private void testPipelineTransform() {
              try {
                   // Set up the input stream
                   BufferedInputStream bis = new BufferedInputStream(
                             new ByteArrayInputStream(getExample().getBytes()));
                   InputSource input = new InputSource(bis);
                   // Set up to read the input file
                   SAXParserFactory spf = SAXParserFactory.newInstance();
                   SAXParser parser = spf.newSAXParser();
                   XMLReader reader = parser.getXMLReader();
                   // Create the filters
                   SAXTransformerFactory stf = (SAXTransformerFactory) TransformerFactory
                             .newInstance();
                   XMLFilter filter1 = stf.newXMLFilter(new StreamSource(new StringReader(getStylesheet1())));
                   XMLFilter filter2 = stf.newXMLFilter(new StreamSource(new StringReader(getStylesheet2())));
                   // Wire the output of the reader to filter1
                   // and the output of filter1 to filter2
                   filter1.setParent(reader);
                   filter2.setParent(filter1);
                   // Set up the output stream
                   StreamResult result = new StreamResult(System.out);
                   // Set up the transformer to process the SAX events generated
                   // by the last filter in the chain
                   Transformer transformer = stf.newTransformer();
                   transformer.setErrorListener(new ErrorListener() {
                        public void error(TransformerException te)
                                  throws TransformerException {
                             System.out.println("Transform generated Transform Error");
                             System.out.println(te.getMessage());
                        public void fatalError(TransformerException te)
                                  throws TransformerException {
                             System.out
                                       .println("Transform generated Transform Fatal Error");
                             System.out.println(te.getMessage());
                        public void warning(TransformerException te)
                                  throws TransformerException {
                             System.out.println("Transform generated Transform Warning");
                             System.out.println(te.getMessage());
                   SAXSource transformSource = new SAXSource(filter2, input);
                   transformer.transform(transformSource, result);
              } catch (TransformerConfigurationException tce) {
                   // Error generated by the parser
                   System.out.println("\n** Transformer Factory error");
                   System.out.println("   " + tce.getMessage());
                   // Use the contained exception, if any
                   Throwable x = tce;
                   if (tce.getException() != null)
                        x = tce.getException();
                   x.printStackTrace();
              } catch (TransformerException te) {
                   // Error generated by the parser
                   System.out.println("\n** Transformation error");
                   System.out.println("   " + te.getMessage());
                   // Use the contained exception, if any
                   Throwable x = te;
                   if (te.getException() != null)
                        x = te.getException();
                   x.printStackTrace();
              } catch (SAXException sxe) {
                   // Error generated by this application
                   // (or a parser-initialization error)
                   Exception x = sxe;
                   if (sxe.getException() != null)
                        x = sxe.getException();
                   x.printStackTrace();
              } catch (ParserConfigurationException pce) {
                   // Parser with specified options can't be built
                   pce.printStackTrace();
         static private void testXsltSingleTransform() {
              try {
                   BufferedInputStream bis = new BufferedInputStream(
                             new ByteArrayInputStream(getExample().getBytes()));
                   // Set up the output stream
                   StreamResult result = new StreamResult(System.out);
                   InputSource input = new InputSource(bis);
                   TransformerFactory factory = TransformerFactory.newInstance();
                   Source source = new StreamSource(new StringReader(getStylesheet2()));
                   Transformer stylesheet = factory.newTransformer(source);
                   stylesheet.setErrorListener(new ErrorListener() {
                        public void error(TransformerException te)
                                  throws TransformerException {
                             System.out.println("Transform generated Transform Error");
                             System.out.println(te.getMessage());
                        public void fatalError(TransformerException te)
                                  throws TransformerException {
                             System.out
                                       .println("Transform generated Transform Fatal Error");
                             System.out.println(te.getMessage());
                        public void warning(TransformerException te)
                                  throws TransformerException {
                             System.out.println("Transform generated Transform Warning");
                             System.out.println(te.getMessage());
                   SAXSource transformSource = new SAXSource(input);
                   stylesheet.transform(transformSource, result);
              } catch (Exception exc) {
                   exc.printStackTrace();
         private static String getStylesheet1() {
              return
                     "<?xml version='1.0' encoding='ISO-8859-1'?>" + newline
                   + "<xsl:stylesheet" + newline
                   + "xmlns:xsl='http://www.w3.org/1999/XSL/Transform'" + newline
                   + "version='1.0'>" + newline
                   + "<xsl:output method='xml'/>" + newline
                   + "<xsl:template match='/'>" + newline
                   + "<DontCareAboutContent></DontCareAboutContent>" + newline
                   + "</xsl:template>" + newline
                   + "</xsl:stylesheet>" + newline;
         private static String getStylesheet2() {
              return
                     "<?xml version='1.0' encoding='ISO-8859-1'?>" + newline
                   + "<xsl:stylesheet" + newline
                   + "xmlns:xsl='http://www.w3.org/1999/XSL/Transform'" + newline
                   + "version='1.0'>" + newline
                   + "<xsl:output method='html'/>" + newline
                   + "<xsl:template match='/'>" + newline
                  + "<html><body>" + newline
                 + "<xsl:message>" + newline
                 + "Error Message for the xslt processor" + newline
                 + "</xsl:message>" + newline
                 + "Dont care about the xslt content," + newline
                 + "The only significant part is the xsl:message element" + newline
                 + "which results in a error to be handled by the xslt" + newline
                 + "processor" + newline
                   + "</body></html>" + newline
                   + "</xsl:template>" + newline
                   + "</xsl:stylesheet>" + newline;
         private static String getExample() {
              return
                     "<?xml version='1.0' encoding='ISO-8859-1'?>" + newline
                   + "<DontCareAboutContent>" + newline
                   + "</DontCareAboutContent>" + newline;
    }

    I made the following change which solves the problem but the sollution is tightly coupled to Xalan. If anyone has any ideas, I would still like to find a way to achieve the desired result using JAXP API's.
                   XMLFilter filter1 = stf.newXMLFilter(new StreamSource(new StringReader(getStylesheet1())));
                   if (filter1 instanceof org.apache.xalan.transformer.TrAXFilter) {
                        ((org.apache.xalan.transformer.TrAXFilter)filter1).getTransformer().setErrorListener(...);
    ...

  • Runtime Mapping Transformation Error

    Hi Experts,
    I am doing a file to idoc scenario in which the sender system is MDM and the Idocs are to be received in the R/3 system.
    I have generated XSD from the IDOC itself , that is MATMAS05 and used it as the source structure by importing in External Definition and the targer is of course the Idoc.
    In SXMB_MONI i get the Runtime Mapping Transformation error. What can be the reason for this.I read somewhere that the XSD and the xml file that is being picked might have different structures.
    But i checked and they are same.
    Only the problem can be with the encoding part.
    In the XML structure of the Idoc , it is UTF-8 and also after exporting it to file it is UTF-8. But after importing it in the External Definition,it becomes ISO-8859-1 and we are unable to change it.
    Also, the xml file that is given from the MDM system has encoding as UTF-8.
    Kindly help.
    Thanks in Advance.
    -Shweta.

    Hi,
    1) check out imported xsd is correct , valid. Hope while importing you have used Type as "XSD" and then after importing, check out the messages tab to know this
    2) In the mapping, did you map all the madatory fields ? like some of the attributes like BEGIN? For this BEGIN attribute map with constant value. also check all the mandatory nodes/fields
    3) check the mapping in the mapping editor independently in Repository by picking the input xml from the SXMB_MONI. So that you can test the mapping
    Hope this will solve the mapping problem. btw, it is prefer to have exact error posted here.
    Regards, Moorthy

  • OSB transformation error- BEA-382513- Error parsing XML

    Hi Gurus -
    I am struggling to fix one OSB Xquery transformation error
    <con:errorCode>BEA-382513</con:errorCode>
    <con:reason>OSB Replace action failed updating variable "body": Error parsing XML: {err}FORG0005: expected exactly one item, got 0 items
    I am passing SIL formatted data to this transformation an expecting a transformation but its keep on failing, I have tested the transformation and thats looking good.
    This is my replace operation where I am doing transformation.
    Replace [ node contents ] of [ ./* ]
    in [ body ] with
    XQuery Resource: TestProject/Common/Transformation/XQJMS2DBTransformation
    Variable Names And Bindings:
    commonInterfaceLayout1 - $body/*:CommonInterfaceLayout
    transformation file
    (:: pragma bea:global-element-parameter parameter="$commonInterfaceLayout1" element="ns0:CommonInterfaceLayout" location="../../Common/Schema/CommonInterfaceLayout.xsd" ::)
    (:: pragma bea:global-element-return element="ns1:EaiAuditCollection" location="../../Common/Schema/XSD_InsertEAIAuditDBTable.xsd" ::)
    declare namespace ns1 = "http://xmlns.oracle.com/pcbpel/adapter/db/top/InsertEAIAuditDBTable";
    declare namespace ns0 = "http://eai.fpl.com/schema/CommonInterfaceLayout";
    declare namespace xf = "http://tempuri.org/ErrorHandlingR1V1/XQJMS2DB/";
    declare function xf:XQJMS2DB($commonInterfaceLayout1 as element(ns0:CommonInterfaceLayout))
    as element(ns1:EaiAuditCollection) {
    <ns1:EaiAuditCollection>
    <ns1:EaiAudit>
    <ns1:eaiAuditId></ns1:eaiAuditId>
    <ns1:messageId>{ data($commonInterfaceLayout1/ns0:Header/ns0:MessageId) }</ns1:messageId>
    <ns1:messageDate>{ data($commonInterfaceLayout1/ns0:Header/ns0:MessageReceivedDate) }</ns1:messageDate>
    <ns1:messageType>{ data($commonInterfaceLayout1/ns0:Header/ns0:MessageType) }</ns1:messageType>
    <ns1:messageSource>{ data($commonInterfaceLayout1/ns0:Header/ns0:MessageSource) }</ns1:messageSource>
    <ns1:messageTarget>{ data($commonInterfaceLayout1/ns0:Header/ns0:MessageTarget) }</ns1:messageTarget>
    <ns1:appUniqId>{ data($commonInterfaceLayout1/ns0:Header/ns0:ApplicationUniqueId) }</ns1:appUniqId>
    <ns1:payload>{ data($commonInterfaceLayout1/ns0:Body) }</ns1:payload>
    <ns1:componentName>{ data($commonInterfaceLayout1/ns0:Header/ns0:ComponentName) }</ns1:componentName>
    <ns1:clientId>{ data($commonInterfaceLayout1/ns0:Header/ns0:ClientId) }</ns1:clientId>
    <ns1:createDate>{ fn:current-date() }</ns1:createDate>
    <ns1:processFlag></ns1:processFlag>
    </ns1:EaiAudit>
    </ns1:EaiAuditCollection>
    declare variable $commonInterfaceLayout1 as element(ns0:CommonInterfaceLayout) external;
    xf:XQJMS2DB($commonInterfaceLayout1)
    pls advice whats wrong I am doing here.
    Edited by: KumarB on Feb 7, 2013 9:56 PM

    update - I dont see this error any more but transformation is not happening. as a result of transformation, i get same message as output .. no change in it.

  • After Upgrade to PI7.1 getting Simple transformation error

    HI Experts,
    I have an Issue, the scenario which i', working its working properly in DEV, QA, PROD in PI 7.0, We upgraded the system to PI7.1
    Unknown Simple transformation error in converting XML to internal table
    Application error in mapping program , error text: Unknown Simple transformation error in converting XML to internal table An exception has occurred.
    Can any one suggest related notes are suggestion.
    appericate in advance for the solutions which you all provide me
    Thank you
    Venkat Anil

    What kind of mapping is that ? Graphical, Java, XSLT, ABAP ?
    The XML parser in 7.1 contains many subtle changes compared to 3.0
    But this error sounds like a bug. Is there something special in the XML input ? is it wellformed-XML ?
    CSY

  • Simple transformation error in converting XML to internal table

    Hi Team,
    I have an issue, its working in Dev, QA, and Prod in PI 7.0, once we upgrade it to PI 7.1 I'm getting the  below mention error,   
    Unknown Simple transformation error in converting XML to internal table
    Application error in mapping program ZF_INT006_FILE_TO_SAP_FILE, error code: , error text: Unknown Simple transformation error in converting XML to internal table An exception has occurred.
    Can any one suggest related notes are suggestion.
    appericate in advance for the solutions which you all provide me
    Thank you
    Venkat Anil

    Check the flag "use SAP XML toolkit" for the operation mapping and try, if that works then.
    Check the flag for all XSLT and Java mappings which is migrated from PI 7.0

  • SRM Workflow error-  Error' 9' when calling service ' SO_OBJECT_SEND'

    Hi Team,
    We are facing problem with SAP SRM Workflow error-  Error' 9' when calling service ' SO_OBJECT_SEND' .
    Due to this WI is not going to Approver/Requester INBOX and unable to process that WI.
    Please advice .
    Greatly Appreciated for Help.
    Regards
    CK

    Hi,
    Not sure what '9' is, the exceptions called by the SO_OBJECT_SEND function are as follows:
    EXCEPTIONS
                   ACTIVE_USER_NOT_EXIST      = 35
                   COMMUNICATION_FAILURE      = 71
                   COMPONENT_NOT_AVAILABLE    = 01
                   FOLDER_NOT_EXIST           = 06
                   FOLDER_NO_AUTHORIZATION    = 05
                   FORWARDER_NOT_EXIST        = 08
                   NOTE_NOT_EXIST             = 45
                   OBJECT_NOT_EXIST           = 13
                   OBJECT_NOT_SENT            = 15
                   OBJECT_NO_AUTHORIZATION    = 13
                   OBJECT_TYPE_NOT_EXIST      = 17
                   OPERATION_NO_AUTHORIZATION = 21
                   OWNER_NOT_EXIST            = 22
                   PARAMETER_ERROR            = 23
                   SUBSTITUTE_NOT_ACTIVE      = 31
                   SUBSTITUTE_NOT_DEFINED     = 32
                   SYSTEM_FAILURE             = 72
                   TOO_MUCH_RECEIVERS         = 73
                   USER_NOT_EXIST             = 46
                   OTHERS                     = 1000.
    Regards,
    Jason

  • SRM-8001 error

    Hi team, I continue to get skipping, glitchy viewing on live TV and On Demand, both at random. Worse, when I often attempt to watch a TV show On Demand, I get the SRM-8001 error.  All my cables are tight and properly connected, so not sure what the problem can be. I often have to go back and forth after the message to finally be able to view the program. Please advise. Thanks. 

    I began getting this On Demand problem for the past few months after having an HD TV for 18 months with no problems with HD ON Demand.  I finally got COMCAST to send out a service guy at the beginning of July (after multiple "unplug the box attemps" over those months when I called) and he found a low signal level at the street (had to call in a separate team to fix), tightened all the connections, and gave me a new box. Since then I still get times when the picture breaks up then freezes then I get thrown back to the On Demand screen, and more recently a frozen blank screen when going from an "embedded commercial" back to the program, and then when trying to go back and re-start the program from where it was, I get the SRM-8001 error. It is nice to know that I am not alone, but after seeing "years" of this SRM-8001 problem on the forums, it is obviuosly not a priority for COMCAST, otherise they would have put enough resources on the problem to get it fixed... The "years old" workaround I read about in the forums (play an SD On Demand free movie for a few seconds, then retry the HD program that had the problem) seems to work at least for the rest of the time I am watching that day.

  • SRM MDM, Error, "Table with Code 'null' does not exist in repository"

    Hi experts,
    We has SRM MDM scenario, while doing OCI settings, we are able to connect with MDM repository but getting follwoing error message in portal, "java.lang.IllegalArgumentException: Table with Code 'null' does not exist in the repository 'Repository' or is one of the system table (e.g. Workflows) that is not exposed in repository schema" 
    Can You please suggest,
    Thanks and Regards,
    Munish

    Hi everyone,
    Sudhanshu and Anshuk:- Thanks for your response, let me try and explain the real scenario in details:-
    We have deployed the SRM-MDM Catalog Search UI in Portal.
    We tried accessing the http://<Portal Host>:<Portal Port>/SRM-MDM/SRM_MDM
    Then we got a screen (Search UI App screen), where in we have provided the MDM Server name, then the MDM Server Password, then presses the Connect button, then below this, it displayed the Repository name created in the MDM. We have selected the Repository, then provided the Credentials of a User (Name: T_CORP) in MDM which has "Catalog Manager", and the "UI Configuration Manager" Roles. Please note that these Role names were created by us in MDM. Is it the right procedure or do we have any standard Roles delivered by SAP in MDM to map? If any standard Roles are available, where we need to check these.
    Once the Credentials of MDM User is provided, and then selected the "Login" button.
    Then we are getting the below error.
    "java.lang.IllegalArgumentException: Table with Code 'null' does not exist in the repository 'Repository' or is one of the system table (e.g. Workflows) that is not exposed in repository schema"
    Please clarify; we are not configuring any values in iViews. Where we need to do this, I mean name of the iView, and what values do we need provide generally? We are just running the Search UI App application; I don't think it is an iView, because the URL shows the Application name details, etc...
    Please guide us, how to fix this Error.
    Thanks and Regards,
    Munish

  • Inventory Transformation error

    Hi All
    I have loaded the Inventory data to the infocube 0IC_C03
    No my req is i need to add the infoobject 0VALSPECST in to cube. I done this now i am trying to activate the transformation but it is showing Start routine syntax errror
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    "SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE".
    Can any one help me on this....
    Thanks in advance
    Raju

    Hi
    Remove that infoobject and try again..
    i think that it may be some system error..
    Refer to this thread..
    Re: How to add the field in infocube?
    It may help..
    Regards
    gaurav

  • SRM Installation Error - Start Java engine

    Hello gurus,
    OS platform -- Windows Server 2008 (R2) Stantard X64
    DataBase - MS SQL Server 2008 (R2) X64
    System - SAP SRM 7.0 / NW7.01
    Iu00B4m facing with an error during a SRM Installation of AS JAVA system (with plus EP & EP Core). I installed last week the ABAP system.
    The error is in the phase 25 - Start Java engine. I checked the sapinst.log and sapinst_dev.log and both show the following error:
    INFO 2011-05-17 12:35:13.073
    Disconnect from message server (SRVSIAPP01/3902) succeeded.
    WARNING[E] 2011-05-17 12:35:13.160
    CJS-30150  Java processes of instance JRM/JC01 [Java: UNKNOWN] did not reach state PARTRUNNING after 20:30 minutes. Giving up.
    ERROR 2011-05-17 12:35:14.42
    FCO-00011  The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|6|0|startJava was executed with status ERROR .
    I also checked others log files, like as start<SID>.log and dev_jcontrol:
    running D:\usr\sap\JRM\SYS\exe\uc\NTAMD64\sapstart.exe name=JRM nr=01 SAPDIAHOST=SRVSIAPP01 -wait
    SAPSTART finished successfully on SRVSIAPP01_JRM_01, but at least one process doesn't run correctly:
    D:\usr\sap\JRM\SYS\exe\uc\NTAMD64\sapstart.exe=>sapparam(1c): No Profile used.
    trc file: "D:\usr\sap\JRM\JC01\work\dev_jcontrol", trc level: 1, release: "701"
    node name   : jcontrol
    pid         : 1436
    system name : JRM
    system nr.  : 01
    started at  : Tue May 17 12:14:55 2011
    arguments       :
           arg[00] : D:\usr\sap\JRM\JC01\exe\jcontrol.EXE
           arg[01] : pf=D:\usr\sap\JRM\SYS\profile\JRM_JC01_SRVSIAPP01
    [Thr 1544] Tue May 17 12:14:55 2011
    [Thr 1544] *** ERROR => OS release Windows NT 6.1 7601 Service Pack 1 2x AMD64 Level 6 (Mod 15 Step 11) is not supported with this startup framework (701) [jstartxx.c   4389]
    This last file (dev_jcontrol) is kindly weird... I checked the PAM and it said this OS (Windows 2008 (R2) is supported!
    Can you help me to solve this problem?
    Kind regards,
    Jou00E3o Dimas - Portugal

    Hello Rajneesh,
    I read that note 1152240 and tell me in which way this apply to my case, because I only see for my case... the part that say "Installing SAP systems based on SAP Netweaver 7.0 EHP1 (7.01) or SAP Netweaver 7.0 EHP1 SR1"  and in there is recommended to:
    . Patch your runtime libraries as described in SAP note 684106 --> I already did this when I installed the ABAP system/part
    . Apply the latest DBSL patch --> I did a kernel upgrade to the latest version and also the DBSL patch on ABAP system/part
    So... I don't see anything related with my case... the Java part that is what I´m trying to install and now I´m with an error!
    Best regards,
    João Dimas - Portugal

  • SRM Installation error during abap import

    Hi SAP Gurus,
    This is the error during the ABAP Import.
    >>>Import_Monitor.log
    INFO: 2007-10-07 14:25:17
    Import Monitor is started.
    CONFIG: 2007-10-07 14:25:17
    Application options:
    dbCodepage=4103
    dbType=ORA
    extFiles=yes
    importDirs=C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1;C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2;C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3
    installDir=C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS
    jobNum=3
    loadArgs= -stop_on_error
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-10-07 14:25:17
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-10-07 14:25:17
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-10-07 14:25:17 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is started.
    INFO: 2007-10-07 14:25:17 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is successfully completed.
    Primary key creation: after load.
    Index creation: after load.
    INFO: 2007-10-07 14:25:18
    Data codepage 1100 is determined using TOC file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2007-10-07 14:25:18
    Version table 'SVERS' is found in STR file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    INFO: 2007-10-07 14:25:18
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    TRACE: 2007-10-07 14:25:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is started.
    TRACE: 2007-10-07 14:25:18 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDIC' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDIC.TSK ORA -l SAPSDIC.log
    TRACE: 2007-10-07 14:25:18 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDIC' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error
    INFO: 2007-10-07 14:28:04 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is successfully completed.
    TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1\DATA\SAPSSEXC.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC.TSK ORA -l SAPSSEXC.log
    TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL1' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2\DATA\SAPAPPL1.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1.TSK ORA -l SAPAPPL1.log
    TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2\DATA\SAPAPPL0.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0.TSK ORA -l SAPAPPL0.log
    TRACE: 2007-10-07 14:28:18 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
    TRACE: 2007-10-07 14:28:18 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -stop_on_error
    TRACE: 2007-10-07 14:28:19 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -stop_on_error
    INFO: 2007-10-07 14:38:56 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is successfully completed.
    TRACE: 2007-10-07 14:39:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is started.
    TRACE: 2007-10-07 14:39:17 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL2' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2\DATA\SAPAPPL2.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2.TSK ORA -l SAPAPPL2.log
    TRACE: 2007-10-07 14:39:18 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error
    INFO: 2007-10-07 14:40:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    TRACE: 2007-10-07 14:40:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is started.
    TRACE: 2007-10-07 14:40:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSRC' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSSRC.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSRC.TSK ORA -l SAPSSRC.log
    TRACE: 2007-10-07 14:40:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSRC' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error
    INFO: 2007-10-07 14:41:42 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is successfully completed.
    TRACE: 2007-10-07 14:41:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is started.
    TRACE: 2007-10-07 14:41:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPPOOL' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPPOOL.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPPOOL.TSK ORA -l SAPPOOL.log
    TRACE: 2007-10-07 14:41:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPPOOL' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error
    INFO: 2007-10-07 14:42:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is successfully completed.
    ERROR: 2007-10-07 14:42:38 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPAPPL2.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-10-07 14:42:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is started.
    TRACE: 2007-10-07 14:42:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is started.
    TRACE: 2007-10-07 14:42:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSPROT' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSPROT.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSPROT.TSK ORA -l SAPSPROT.log
    TRACE: 2007-10-07 14:42:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDOCU' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDOCU.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDOCU.TSK ORA -l SAPSDOCU.log
    TRACE: 2007-10-07 14:42:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDOCU' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error
    TRACE: 2007-10-07 14:42:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSPROT' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error
    ERROR: 2007-10-07 14:42:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSDOCU.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-07 14:42:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSPROT.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-10-07 14:43:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is started.
    TRACE: 2007-10-07 14:43:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is started.
    TRACE: 2007-10-07 14:43:17 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLEXC' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSLEXC.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLEXC.TSK ORA -l SAPSLEXC.log
    TRACE: 2007-10-07 14:43:17 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPCLUST' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPCLUST.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPCLUST.TSK ORA -l SAPCLUST.log
    TRACE: 2007-10-07 14:43:18 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLEXC' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
    TRACE: 2007-10-07 14:43:18 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPCLUST' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
    ERROR: 2007-10-07 14:43:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPCLUST.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2007-10-07 14:43:19 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is successfully completed.
    TRACE: 2007-10-07 14:43:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is started.
    TRACE: 2007-10-07 14:43:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is started.
    TRACE: 2007-10-07 14:43:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLOAD' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSLOAD.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLOAD.TSK ORA -l SAPSLOAD.log
    TRACE: 2007-10-07 14:43:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDDIM' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPDDIM.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDDIM.TSK ORA -l SAPDDIM.log
    TRACE: 2007-10-07 14:43:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLOAD' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
    TRACE: 2007-10-07 14:43:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDDIM' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error
    ERROR: 2007-10-07 14:43:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSLOAD.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-07 14:43:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPDDIM.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-10-07 14:44:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is started.
    TRACE: 2007-10-07 14:44:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is started.
    TRACE: 2007-10-07 14:44:17 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDFACT' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPDFACT.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDFACT.TSK ORA -l SAPDFACT.log
    TRACE: 2007-10-07 14:44:17 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDODS' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPDODS.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDODS.TSK ORA -l SAPDODS.log
    TRACE: 2007-10-07 14:44:18 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDFACT' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
    TRACE: 2007-10-07 14:44:18 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDODS' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
    ERROR: 2007-10-07 14:44:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPDODS.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-07 14:44:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPDFACT.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-10-07 14:44:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is started.
    TRACE: 2007-10-07 14:44:47 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is started.
    TRACE: 2007-10-07 14:44:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPUSER.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER.TSK ORA -l SAPUSER.log
    TRACE: 2007-10-07 14:44:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAP0000' import package:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAP0000.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAP0000.TSK ORA -l SAP0000.log -o D
    TRACE: 2007-10-07 14:44:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAP0000' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -stop_on_error
    TRACE: 2007-10-07 14:44:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error
    INFO: 2007-10-07 14:44:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    INFO: 2007-10-07 14:44:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is successfully completed.
    INFO: 2007-10-08 08:15:14
    Import Monitor is started.
    CONFIG: 2007-10-08 08:15:14
    Application options:
    dbCodepage=4103
    dbType=ORA
    extFiles=yes
    importDirs=C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1;C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2;C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3
    installDir=C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS
    jobNum=3
    loadArgs= -stop_on_error
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-10-08 08:15:14
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-10-08 08:15:14
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-10-08 08:15:14 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is started.
    INFO: 2007-10-08 08:15:15 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is successfully completed.
    Primary key creation: after load.
    Index creation: after load.
    INFO: 2007-10-08 08:15:15
    Data codepage 1100 is determined using TOC file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2007-10-08 08:15:15
    Version table 'SVERS' is found in STR file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    INFO: 2007-10-08 08:15:15
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is started.
    TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is started.
    TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
    TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error
    TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSPROT' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error
    ERROR: 2007-10-08 08:15:20 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSSEXC.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-08 08:15:20 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSPROT.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-08 08:15:30 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPAPPL2.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-10-08 08:15:44 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is started.
    TRACE: 2007-10-08 08:15:44 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is started.
    TRACE: 2007-10-08 08:15:44 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is started.
    TRACE: 2007-10-08 08:15:45 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDOCU' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error
    TRACE: 2007-10-08 08:15:45 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPCLUST' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
    TRACE: 2007-10-08 08:15:45 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLOAD' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
    ERROR: 2007-10-08 08:15:48 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPCLUST.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-08 08:15:49 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSLOAD.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-08 08:15:49 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPSDOCU.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-10-08 08:16:14 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is started.
    TRACE: 2007-10-08 08:16:14 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is started.
    TRACE: 2007-10-08 08:16:14 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is started.
    TRACE: 2007-10-08 08:16:15 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDDIM' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error
    TRACE: 2007-10-08 08:16:15 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDFACT' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
    TRACE: 2007-10-08 08:16:15 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDODS' import package into database:
    C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
    ERROR: 2007-10-08 08:16:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPDDIM.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-08 08:16:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPDFACT.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-10-08 08:16:19 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is interrupted with R3load error.
    Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
    For mode details see 'SAPDODS.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    WARNING: 2007-10-08 08:16:44
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2007-10-08 08:16:44
    9 error(s) during processing of packages.
    INFO: 2007-10-08 08:16:44
    Import Monitor is stopped.
    Please let me know your thoughts.
    Points will be given.

    Hi Joseph,
    Pls remove any spaces in names of Export Dir Dump Location e.g. SRM files make it SRM_files etc and restart the installation.
    Hope this is useful
    Regards
    Umesh

Maybe you are looking for

  • Problem with vtp on catos-switches

    Problem with vtp on catos-switches connected are three switches: | vtp | | server | | cat or ios | | | | vtp | C3750 or C4506 | client | | ios | | | | vtp | C2948-GE-TX or C2980 | client | | catos | 1) when the ios-vtp-client restarts after power fai

  • Checkbox submit problem.

    Hi, Im working on adf faces with jdev 10.1.3 . There is a checkbox which shud render a button based on its value. If i use onclick="submit()" it works correctly, but I dont want it to submit the page fully. Is there some other way to do it . I tried

  • Display gone out

    My Studio Display screen has gone black -- power light stays on steady. For a few days it would work fine for 30 mins., then go black, come back, then go black again intermittently. Now it's completely black. Any suggestions to fix? G4 quicksilver  

  • Will a lower wattage affect how my macbook pro charges

    My roommate's power cord got mixed up with mine and I won't be seeing her for 3 weeks. She has a macbook air while I have a macbook pro. I have noticed that her power cord works on my computer, but it just takes longer to charge and sometimes it stop

  • Material Availability in MTO

    Hi, How to configure ATP for MTO Scenario when multilevel BOM explosion is possible and Material Availability date for higher level Item should be the highest amoung the lower level Item. Regards, Sachin