DTP and Transformation error

Hi All,
Iam loading master data through process chain.
The process chain got failed at some particular DTP giving a error message
"Exception CX_RS_ERROR occurred (program: CL_RSTRAN_RUNTIME_EXE=========CP, include: CL_RSTRAN_RUNTIME_EXE=========CM001, line: 231).
It seems that the particular transformation or DTP needs to be transported.
As this is a productios system, it takes some time for the transport.
I have created a new DTP , activated the transformation .Then also iam getting the same problem while loading the data in DTP
Mean while some one guided to edit master data to load new master data some thing like this.....but i didnt undersatnd properly what exactly they suggested.
Can any one advise me how to load new master data.What will be the other methods to load data
Regards
Saha

Hi,
i Mailed clearly , its a transformation problem and that cant be transportable immediatly.
And i have given clue also, master data editing is the alternate way but i dont know how to edit master data.
Please some one explain me how to edit master data for the new records and et me know if any other ways are there.
Regrads
Saha

Similar Messages

Regarding DTP and Transformations

How can i check who has changed/created the DTP or Transformations. Is there any table which gives this information ?
Thanks,
Santosh

Hi,
When you open the Transformations -> there is an icon (it will display as Detail when you keep the cursor on the icon) just before the Start Routine button. click it -> you will get the details of Last changed by/Changed On/Changed at and Person Responsible.
For DTP -> Go to (in the menu bar) -> overview of the DTP -> you will get details of Last changed by/Changed On/Changed at and Person Responsible.
Hope this helps you
Regards
Sunil

Reg: introduction of DTP and Transformation in BI 7.0

Hi all,
I've two questions here one is:
1. what is the purpose of introduction of DTP with NW 7.0 BI 7.0
i know the bcoz of these reasons:
>Improved transparency of staging processes across data warehouselayers
>Improved performance:Intrinsic parallelism
>Separation of deltamechanism for differentdata targets: deltacapability is controlledby the DTP..
>Enhanced filtering indataflow..
>Repair modus based ontemporary buffers (bufferskeep complete set of data)
but can any one explain me how this happens in detail.
coming to my question 2.
Why transformation replaced tranfer rules and update rules
(excluing graphical UI)
Regards
Ganesh

>Improved transparency of staging processes across data warehouselayers
PSA to multiple datatargets allows you transparency and overcomes the spiderweb of export datamart
>Improved performance:Intrinsic parallelism
need not have to wait for one infoprovider to load(datamart) to load the consecutive dataprovider - data can be parallely loaded to different providers at the same time once the data is in PSA
>Separation of deltamechanism for differentdata targets: deltacapability is controlledby the DTP..
delta in DTP's is governed by datamart status
>Enhanced filtering indataflow..
you can set ur filters independent of any other dataproviders like in datamarts .
>Repair modus based ontemporary buffers (bufferskeep complete set of data)
error stack allow you to resurrect the data and load it again
Why transformation replaced tranfer rules and update rules
transformations and DTP have 1:1 relationship - so if u pretty sure to use DTP (ur 1st question) - the pre req would be to have transformation - u can create a DTP only after you create a transformation(source and target mapping )

Master data loading in 7.0 and transformation error

I am trying to load master data to BI 7.0, here are what I got;
1) InfoObject: COSTCENTER1
2)DataSource: ZGRCO_ATTR
The COSTCENTER1 is the master data, I made it infoprovider, when I try to create transformation, it always gives me this error:
Can not generate proposal
Can any one kelp me out?
Thanks

Hi,
please have a look here: http://help.sap.com/saphelp_nw70/helpdata/en/44/0243dd8ae1603ae10000000a1553f6/frameset.htm
regards
Siggi

ODS and Transformations get inactive after i transport it in PD.

i have transported my ETL model in production , Now Everything what we have transported has come into production system but transformation and ODS in our ETL model get inactivated . Also while i want to display the transformation it give massege that " 'the infosource that we have created before the transformation in not active and can not be used . '
Our ETL model is like
Cube(now Active) --- tranformation(Now is in not active state) -- ODS(Now is in not active state) -- transformaion(Now is in not active state) -- infosource(Now in active state) -- transformation(Now in active state) -- PSA .
the part    ": tranformation -- ODS -- transformaion " gets inactivated after transportation also DTP which pull data from ODS to cube also get inactive .
Please suggest me to how i can activate these inactive object or i have to transport these object again to PD
Thanks .

Hi Bryan ,
        Yes data was their inside the ODS while transporting , Now i have successfully transported the request , nd now activating ODS transformation nd DTP . Actually i got a prog to activate transformation and DTP and want to share with all ... . i juz activate mt DTP and transformation though these prog .
Program for DTP ACTIVATION
*& Report ZDTP_ACTIVATE
*Coded by NBS BI team
*Date: 15-JAN-2010
*Function: For DTPs activation
REPORT ZDTP_ACTIVATE.
TYPES: BEGIN OF t_dtp,
dtp LIKE rsbkdtpstat-dtp,
objstat LIKE rsbkdtpstat-objstat,
src LIKE rsbkdtp-src,
tgt LIKE rsbkdtp-tgt,
END OF t_dtp.
TYPES: i_dtp TYPE STANDARD TABLE OF t_dtp.
DATA: lv_output(255) TYPE c,
lv_subrc TYPE sysubrc,
tab_dtp TYPE i_dtp,
r_dtp TYPE REF TO cl_rsbk_dtp.
SELECTION-SCREEN BEGIN OF BLOCK b1.
SELECTION-SCREEN SKIP 1.
PARAMETERS: p_id TYPE char35.
SELECTION-SCREEN END OF BLOCK b1.
START-OF-SELECTION.
FIELD-SYMBOLS: <fs_dtp> TYPE t_dtp.
REFRESH tab_dtp.
SELECT * FROM rsbkdtp AS a JOIN rsbkdtpstat
         AS b ON adtp = bdtp INTO
        CORRESPONDING FIELDS OF TABLE tab_dtp
         WHERE a~dtp = p_id AND
            a~objvers = 'A' AND
              b~objstat = 'INA'.
IF tab_dtp IS NOT INITIAL.
    LOOP AT tab_dtp ASSIGNING <fs_dtp>.
      CALL METHOD cl_rsbk_dtp=>factory
        EXPORTING
          i_dtp   = <fs_dtp>-dtp
        RECEIVING
          r_r_dtp = r_dtp.
      IF sy-subrc = 0.
        CALL METHOD r_dtp->activate
          EXPORTING
            i_objvers             = rs_c_objvers-modified
            i_force_activation    = rs_c_true
            i_show_check_protocol = rs_c_false
            i_with_cto            = rs_c_true
          IMPORTING
            e_subrc               = lv_subrc.
        IF lv_subrc = 0.
          CONCATENATE 'Activated DTP : ' <fs_dtp>-dtp ' : ' <fs_dtp>-src '->' <fs_dtp>-tgt INTO lv_output.
        ELSE.
          CONCATENATE 'DTP : ' <fs_dtp>-dtp ' : ' <fs_dtp>-src '->' <fs_dtp>-tgt ' Could Not be Activated' INTO lv_output.
        ENDIF.
      ENDIF.
      WRITE:/ lv_output.
    ENDLOOP.
ELSE.
    WRITE:/ 'DTP is not Inactive'.
ENDIF.
Program for TRANSFORMATION ACTIVATION
**& Report ZTRFN_ACTIVATE
*Coded by NBS BI team.
*Date: 15-Jan-2010
*Function: Activates in-active transformation only.
REPORT ZTRFN_ACTIVATE.
TYPES: t_tran TYPE rstran,
i_tran TYPE STANDARD TABLE OF t_tran.
DATA: r_tran_maintain TYPE REF TO cl_rstran_maintain,
lv_subrc TYPE sy-subrc,
lv_output(255) TYPE c,
tab_tran TYPE i_tran,
i_s_source TYPE rstran_s_tlogo,
i_s_target TYPE rstran_s_tlogo.
SELECTION-SCREEN BEGIN OF BLOCK b1.
SELECTION-SCREEN SKIP 1.
PARAMETERS: p_id TYPE char35.
SELECTION-SCREEN END OF BLOCK b1.
START-OF-SELECTION.
FIELD-SYMBOLS: <fs_trans> TYPE t_tran.
REFRESH tab_tran.
SELECT * FROM rstran
INTO TABLE tab_tran
WHERE tranid = p_id AND objvers = 'A' AND objstat = 'INA'.
SORT tab_tran.
IF tab_tran IS NOT INITIAL.
    LOOP AT tab_tran ASSIGNING <fs_trans>.
      TRY.
          CREATE OBJECT r_tran_maintain
            EXPORTING
              i_tranid       = <fs_trans>-tranid
              i_s_source     = i_s_source
              i_s_target     = i_s_target
              i_expert       = rs_c_false
              i_mode         = rsawc_c_tfc-display
              i_with_message = rs_c_true.
        CATCH cx_rstran_not_found .
        CATCH cx_rstran_input_invalid .
        CATCH cx_rstran_cancelled .
        CATCH cx_rstran_not_authorized .
        CATCH cx_rstran_display_only .
        CATCH cx_rstran_already_exist .
        CATCH cx_rstran_error_with_message .
      ENDTRY.
      CALL METHOD r_tran_maintain->check
        EXPORTING
          i_with_display = rs_c_true
        IMPORTING
          e_subrc        = lv_subrc.
      IF lv_subrc = 0.
        CONCATENATE 'Activated Transformation : ' <fs_trans>-tranid ' : ' <fs_trans>-sourcename '->' <fs_trans>-targetname INTO lv_output.
      ELSE.
        CONCATENATE 'Transformation : ' <fs_trans>-tranid ' : ' <fs_trans>-sourcename '->' <fs_trans>-targetname 'Could Not be Activated' INTO lv_output.
      ENDIF.
      IF lv_subrc = 0.
        TRY.
            CALL METHOD r_tran_maintain->execute
              EXPORTING
                i_wrkmode = cl_rstran_stat=>wrkmode_activate
              IMPORTING
                e_subrc   = lv_subrc.
          CATCH cx_rstran_cancelled .
          CATCH cx_rstran_error_with_message .
          CATCH cx_rstran_display_only .
        ENDTRY.
      ENDIF.
      WRITE:/ lv_output.
    ENDLOOP.
ELSE.
    WRITE:/ 'Transformation is not Inactive'.
ENDIF.

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

BPM Transformation Error not Raising Exceptions

Hi,
I've got a BPM receives a message, then call a transformation step and then send the message. I've created exception branches for the transformation and send steps. If the message mapping called in the transformation step works, the message is send, no problems. If a message mapping exception occurs, for example a string index out of bounds, the exception branch is not executed. Instead the BPM continues to the send step and an error occur because of the empty container element.(the container is empty because the mapping fails). SAP Help states that an exception is "Thrown when a permanent system error occurs" in the Transformation step. My question is what exactly is a permanent system error if normal message mapping exceptions is not a permanent system error? And also, how do I generate a permanent system error when a message mapping exception is thrown in order for the exception branch in my BPM to execute?
Any suggestions will be appreciated.

I dont think there is a direct way to raise such error in mapping
What is the sxi_cache status for ur integration process?
Here r the steps for which permanent error is thrown
http://help.sap.com/saphelp_nw04s/helpdata/en/33/4a773f12f14a18e10000000a114084/frameset.htm
Regards,
Prateek

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.

Regarding assign and transform

Hi all,
iam doing a task, in which the data from one (oracle 10g) is moved to another database(oracle 12i ),
source table contains around 30 columns and destiantio contans some N number of columns.
I just used data polling for source . when data is inserted in the source side ,it is automatically picked and inseted in to destination.
Around 22 columns are directly mapped , and remaining are validated based on some conditons and then inserted to desinaiton.
iam using transform activity for direct mapping , and remaining columns are mapped with assign activity(after chcecking the conditions).
Promblem is only transform values are getting inserted in the destination table.
can't we use both assign and transform in one bpel process .
can't we use two transform activities in same bpel process.
regrads,
ramakrishna

HI Buddy,
<?xml version = "1.0" encoding = "UTF-8" ?>

<process name="assing_transform"
targetNamespace="http://xmlns.oracle.com/assing_transform"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:client="http://xmlns.oracle.com/assing_transform"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns5="http://xmlns.oracle.com/pcbpel/adapter/db/source/"
xmlns:ns6="http://xmlns.oracle.com/pcbpel/adapter/db/top/source"
xmlns:ns7="http://xmlns.oracle.com/pcbpel/adapter/file/source/"
xmlns:ns8="http://www.emp.org"
xmlns:ns2="http://xmlns.oracle.com/pcbpel/adapter/db/dest/"
xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/db/soure/"
xmlns:ns4="http://xmlns.oracle.com/pcbpel/adapter/db/top/dest"
xmlns:ns3="http://xmlns.oracle.com/pcbpel/adapter/db/top/soure"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">

<partnerLinks>
<partnerLink myRole="dest_role" name="dest" partnerRole="dest_role"
partnerLinkType="ns2:dest_plt"/>
<partnerLink myRole="Read_role" name="source"
partnerLinkType="ns7:Read_plt"/>
</partnerLinks>

<variables>
<variable name="input" messageType="ns7:emp_msg"/>
<variable name="output" messageType="ns2:EmpCollection_msg"/>
</variables>

<sequence name="main">
<receive name="Receive_1" partnerLink="source" portType="ns7:Read_ptt"
operation="Read" variable="input" createInstance="yes"/>
<assign name="Transform_1">
<bpelx:annotation>
<bpelx:pattern>transformation</bpelx:pattern>
</bpelx:annotation>
<copy>
<from expression="ora:processXSLT('Transformation_2.xsl',bpws:getVariableData('input','emp'))"/>
<to variable="output" part="EmpCollection"/>
</copy>
</assign>
<assign name="Assign_1">
<copy>
<from variable="input" part="emp" query="/ns8:emp/ns8:empdet/ns8:name"/>
<to variable="output" part="EmpCollection"
query="/ns4:EmpCollection/ns4:Emp/ns4:empname"/>
</copy>
</assign>
<invoke name="Invoke_1" partnerLink="dest" portType="ns2:dest_ptt"
operation="insert" inputVariable="output"/>
</sequence>
</process>
THIS IS MY BPEL FILE , CREATED FOR TESTING PURPOSE
IN WHICH I HAVE TAKEN THREE FIELDS IN XML FILE AND TRIYING TO SEND TO DATABASE
FOR TWO FIELDS IAM USING TRANSFORM
AND FOR ONE FIELD ,IAM USING ASSIGN
THE BPEL PROCESS SUCESSFULLY DEPLOYING , BUT IT IS GIVING RUNTIME (CHECKING IN BPEL CONSOLE PROCESS FLOW)
THE ERROR IS ASSIGN ACTIVITY SHOWING ERROR IN BPEL SPEC 1.1 SECITON 14.3
COULD U SUGGEST ME , IS THERE ANY OTHER ALTERNATIVES TO SOLVE THE ISSUE
THANKS AND REGRADS
RAM

Missed get delta once option in dtp and transported to prod

hi all
we have transported DTP for our infocube 0wbs_c11 into production.
This infocube 0wbs_c11 is loaded from 4 datasources of which one datasource supports delta and rest donot.
so in process chains we are using the option for delete overlapping requests. for all the 3 datasources which doesnot support delta.
But for one of these 3 datasources we have transported DTP without ticking GET DELTA ONCE OPTION AND loaded to infocube.
now we should tick the get delta once option and transport it to production, where we already ran this dtp once.
Since we cannot enable the get delta once option enabled in dtp after the first dtp run
my question is should i delete the request from infocube and transport the dtp transport request (to prod )with getdelta once option ticked and run the dtp again will it work.
or do i need to delete the request as well as dtp from prod and then transport the new request with delta once option ticked.
regards
krishna

based on the above link which says after activating transformations using the program rsdg_trfn_activate if we run process chain the dtp's get activated by itself
i have done a trial based on the above point
i went to dtp execute tab and press execute ,and when it asks me for furthur process
YES NO CANCEL
I have cancelled the execution of dtp.
and now when i refresh the tree the dtp is seen active .
i followe the same for all.
regards
Edited by: krishnav3.5 on Sep 16, 2011 4:17 PM

Reg: dtps and infocubes,Dsos in bi 7

HI All,
Can you please explain in details about types of dtps and use(singifiance of each dtp) them in bi 7 as well as cubes and dsos, please do not send links it is difficult to get what i want.
Thanks in advance
Vis
Please search the forum/SDN before posting a thread.
Edited by: Pravender on Jun 29, 2010 10:46 AM

Hi,
In BI 7.0 when you need update rules and transfer rules, you can create it by
right click on data target --> additional Fumctions --> create Update Rules
Using this you can create Update Rules , but only thing is the Infosource you are planning to use should be 3.X infosource.
But same functianality or you can say better functionality you can achieve by using Transformation rather than Update and Transfer rules.
I hope this satisfies your query.
Thanks,
Geetanjali.

DTP and Transformation error

Similar Messages

Maybe you are looking for