XSD validation for incoming data into BPEL process

Please suggest how to validate XSD incoming data into BPEL process.
I just wanted to verify the data before entering into BPEL

Hi,
I guess i am replying very late.
In BPEL 2.0 we have an activity called "Validate" which can do the XSD validations.
"Lets Learn Oracle SOA: Validate XML schema In BPEL"
Regards,
Chinmaya

Similar Messages

  • Oracle data into BPEL

    Hi,
    I am new to this forum so pls. pardon me if I am not familier with the rules. I need to know how to integrate DB Adapter data into BPEL rules engine. Actually, based on a status column value in Oracle table this rules engine would guide it to a human task. I need help to do this.
    Thx,

    Hi
    I am exactly working on the same scenario as below and wanted to use the Oracle Apps Adapter
    1. Import the CSV files using File Adapter.
    2. Move the CSV data into Oracle Staging Table using Databse Adapter.
    3. Validate the Record by PL/SQL Package that i publish as WebService.
    4. Move the Validated Record to Oracle Base table using Apps Adapter.
    I created a package for validating the data and call the Oracle Seeded APIs and registered the same as a concurrent program. Now when i am trying to find the same concurrent program through apps adapter I couldn't find.
    Am I missing something? Or do I have only one option to call the Concurrent Program through DB Adapter?
    Can any one help me out please

  • Service reads data but Bpel process does not start

    i have a very simple project. I have db2(as400) adapter and it reads data, i will receive data, transfom and send to oracle database. I deployed the project successfuly but when instance start i see the service reads the data but bpel process does not start and and there is no error. At the flow chart there is only readAS400 partnerlink, there is no bpelprocess. In the partnerlink i am usin polling, i read the data's with 1 and update to 2. It reads but dont update to 2.
    In deploy step and when instance starts there is no errors. But when i am deploying i get a warning but i dont know it's related with this situation.
    (Warning: property "activationAgent.readAs400.className" may not be understood by BPEL component BPELProcessEqpType - it will likely be ignored.)
    Do you have any suggestion ? Thanks in advance.

    check the recovery console, the bpel process possibly is going into manual recovery,
    Another thing you might wanna try is using checkpoints in your process..
    also, instead of getting the db adapter to instantiate the process, try a simpler process just to see if the db adapter is working or not..
    A normal process, which you manually instantiate from em console, with the db adapter in it after the recevie activity
    Edited by: AshishSharma on Jun 24, 2010 5:48 PM

  • Steps for loading data into the infocube in BI7, with dso in between

    Dear All,
    I am loading data into the infocube in BI7, with dso in between. By data flow looks like....
    Top to bottom:
    InfoCube (Customized)
    Transformation
    DSO (Customized)
    Transformation
    DataSource (Customized).
    The mapping and everything else looks fine and data is also seen in the cube on the FULL Load.
    But due to some minor error (i guess), i am unable to see the DELTA data in DSO, although it is loaded in DataSource through process chains.
    Kindly advise me, where did i miss.
    OR .. Step by step instructions for loading data into the infocube in BI7, with dso in between would be really helpful.
    Regards,

    Hi,
    my first impulse would be to check if the DSO is set to "direct update". In this case there is no Delta possible, because the Change log is not maintained.
    My second thought would be to check the DTP moving data between the DSO and the target cube. If this is set to full, you will not get a delta. It is only possible to create one DTP. So if you created one in FULL mode you can't switch to Delta. Just create the DTP in Delta mode.
    Hope this helps.
    Kind regards,
    Jürgen

  • FDMEE Import error "No periods were identified for loading data into table 'AIF_EBS_GL_BALANCES_STG'

    Hi,
    We are having trouble while importing one ledger 'GERMANY EUR GGAAP'. It works for Dec 2014 but while trying to import data for 2015 it gives an error.
    Import error shows " RuntimeError: No periods were identified for loading data into table 'AIF_EBS_GL_BALANCES_STG'."
    I tried all Knowledge docs from Oracle support but no luck. Please help us resolving this issue as its occurring in our Production system.
    I also checked all period settings under Data Management> Setup> Integration Setup > Global Mapping and Source Mapping and they all look correct.
    Also its only happening to one ledger rest all ledgers are working fine without any issues.
    Thanks

    Hi,
    there are some Support documents related to this issue.
    I would suggest you have a look to them.
    Regards

  • IFS-12635: SimpleXmlParser: Value(10/10/99) not valid for type (Date)

    I am trying to uplaod an xml document sample which has an attribute of date datatype.
    My sample is :
    <?xml version="1.0" standalone="yes"?>
    <document>
    <name> test</name>
    <createdate>1999/03/12</createdate>
    </document>
    I am getting this error:
    IFS-12635: SimpleXmlParser: Value(10/10/99) not valid for type (Date).
    If I input just the "name attribute" value, there is no problem. What is the date format, I should use?
    Please suggest.
    Thank you
    null

    Is there any way to specify the format in the custom type document itself. ? I do not want to specify the format in every document sample. Is there any way that it is possible. If I give the format in the document samples, as Matt said, there is no problem.
    Now I tried to give the format in the type document itself.
    I created a custom type document as follows:
    <?xml version="1.0" standalone="yes"?>
    <!--myTestType.xml-->
    <ClassObject>
    <Name>myTestType</Name>
    <Description> myTestType Document </Description>
    <Superclass Reftype ="name">Document</Superclass>
    <Attributes>
    <Attribute>
    <Name> Category </Name>
    <DataType> String </DataType>
    <DataLength> 80 </DataLength>
    </Attribute>
    <Attribute>
    <Name> posted_date </Name>
    <DataType format="mm-dd-yyyy"> date </DataType>
    </Attribute>
    </Attributes>
    </ClassObject>
    I could able to upload this to ifs. No problem at this time. But when I try to load the below sample, I am getting the same parse problem.(IFS-12635 SimpleXmlParser: Value(12-25-1992) not valid for type (Date.).
    sample xml document
    <?xml version="1.0" standalone="yes"?>
    <myTestType>
    <name> testing.myTestType</name>
    <Category>Administration_4</Category>
    <posted_date >12-25-1992</posted_date>
    </myTestType>
    Thank you.

  • ORABPEL-11811 - Error while calling PL/Sql API Into BPEL Process

    Hi,
    I have created a BPEL Process for creating a Order in Oracle using the synchronous process.
    I have followed the below steps.
    1) Created a Stored procedure using the Order Creation API's by passing Recard Type IN parameters.
    2) Created Synchronous BPEL Process and called the above Procedure using APPS Adapter.
    3) Created a xsd file and mapped the input and output parameter values using Transform Activity.
    After the above steps, when I try to run the BPEL process I am getting the below error:
    An error occurred while preparing and executing the APPS.PROC_PROC_NAME API. Cause: java.sql.SQLException: ORA-06531: Reference to uninitialized collection
    ORA-06512: at "APPS.PROC_PROC_NAME ", line 149
    ORA-06512: at line 1
    [Caused by: ORA-06531: Reference to uninitialized collection
    ORA-06512: at "APPS.PROC_NAME", line 149
    ORA-06512: at line 1
    ; nested exception is:
    ORABPEL-11811
    Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.PROC_PROC_NAME API. Cause: java.sql.SQLException: ORA-06531: Reference to uninitialized collection.
    Can anybody help in resolving the error?
    Thanks,
    Mastanvali.

    Here is the API Code..
    CREATE OR REPLACE PROCEDURE XXMAST_PRC(
    arg_in_p_header_rec           IN HeaderObject,
    arg_in_p_line_tbl          IN arrayLines,
    arg_out_x_return_status          OUT VARCHAR2,
    arg_out_order_number          OUT NUMBER,
    arg_out_header_id          OUT NUMBER,
    arg_out_flow_status_code     OUT VARCHAR2
    ) AS
         p_api_version_number          NUMBER;
         x_return_status      VARCHAR2(2);
         x_msg_count      NUMBER;
         x_msg_data      VARCHAR2(2000);
         v_msg_data               VARCHAR2(8000);
         v_msg_index_out               NUMBER(10);
         p_header_rec      OE_ORDER_PUB.HEADER_REC_TYPE;
         p_old_header_rec      OE_ORDER_PUB.HEADER_REC_TYPE;
         p_header_val_rec      OE_ORDER_PUB.Header_Val_Rec_Type;
         p_old_header_val_rec      OE_ORDER_PUB.Header_Val_Rec_Type;
         p_Header_Adj_tbl      OE_ORDER_PUB.Header_Adj_Tbl_Type;
         p_old_Header_Adj_tbl      OE_ORDER_PUB.Header_Adj_Tbl_Type;
         p_Header_Adj_val_tbl      OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
         p_old_Header_Adj_val_tbl      OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
         p_Header_price_Att_tbl      OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
         p_old_Header_Price_Att_tbl      OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
         p_Header_Adj_Att_tbl      OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
         p_old_Header_Adj_Att_tbl      OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
         p_Header_Adj_Assoc_tbl      OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
         p_old_Header_Adj_Assoc_tbl      OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
         p_Header_Scredit_tbl      OE_ORDER_PUB.Header_Scredit_Tbl_Type;
         p_old_Header_Scredit_tbl      OE_ORDER_PUB.Header_Scredit_Tbl_Type;
         p_Header_Scredit_val_tbl      OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type;
         p_old_Header_Scredit_val_tbl      OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type;
         p_line_tbl      OE_ORDER_PUB.Line_Tbl_Type;
         p_old_line_tbl      OE_ORDER_PUB.Line_Tbl_Type;
         p_line_val_tbl      OE_ORDER_PUB.Line_Val_Tbl_Type;
         p_old_line_val_tbl      OE_ORDER_PUB.Line_Val_Tbl_Type;
         p_Line_Adj_tbl      OE_ORDER_PUB.Line_Adj_Tbl_Type;
         p_old_Line_Adj_tbl      OE_ORDER_PUB.Line_Adj_Tbl_Type;
         p_Line_Adj_val_tbl      OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
         p_old_Line_Adj_val_tbl      OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
         p_Line_price_Att_tbl      OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
         p_old_Line_Price_Att_tbl      OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
         p_Line_Adj_Att_tbl      OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
         p_old_Line_Adj_Att_tbl      OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
         p_Line_Adj_Assoc_tbl      OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
         p_old_Line_Adj_Assoc_tbl      OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
         p_Line_Scredit_tbl      OE_ORDER_PUB.Line_Scredit_Tbl_Type;
         p_old_Line_Scredit_tbl      OE_ORDER_PUB.Line_Scredit_Tbl_Type;
         p_Line_Scredit_val_tbl      OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
         p_old_Line_Scredit_val_tbl      OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
         p_Lot_Serial_tbl      OE_ORDER_PUB.Lot_Serial_Tbl_Type;
         p_old_Lot_Serial_tbl      OE_ORDER_PUB.Lot_Serial_Tbl_Type;
         p_Lot_Serial_val_tbl      OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
         p_old_Lot_Serial_val_tbl      OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
         p_action_request_tbl      OE_ORDER_PUB.Request_Tbl_Type;
         x_header_rec OE_ORDER_PUB.Header_Rec_Type;
         x_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type;
         x_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
         x_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
         x_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
         x_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
         x_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
         x_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
         x_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type;
         x_line_tbl OE_ORDER_PUB.Line_Tbl_Type;
         x_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type;
         x_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type;
         x_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
         x_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
         x_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
         x_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
         x_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
         x_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
         x_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type;
         x_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
         x_action_request_tbl     OE_ORDER_PUB.Request_Tbl_Type;
         icount                    NUMBER :=0;
    BEGIN
         fnd_global.apps_initialize(1318,21623,660);
         fnd_client_info.set_org_context(204);
         p_header_rec:= OE_ORDER_PUB.G_MISS_HEADER_REC;
         SELECT OE_ORDER_HEADERS_S.NEXTVAL INTO p_header_rec.header_id FROM DUAL;
         dbms_output.put_line('Header ID          = '|| p_header_rec.header_id);
         p_api_version_number := 1.0;
    ------------------------------------------header code-----------------------------------------------------------------------
              p_header_rec.order_type_id          := arg_in_p_header_rec.order_type_id;
              p_header_rec.sold_to_org_id          := arg_in_p_header_rec.sold_to_org_id;
              p_header_rec.ship_to_org_id          := arg_in_p_header_rec.ship_to_org_id;
              p_header_rec.transactional_curr_code:= arg_in_p_header_rec.transactional_curr_code;
              p_header_rec.order_source_id          := arg_in_p_header_rec.order_source_id;
              p_header_rec.org_id               := arg_in_p_header_rec.org_id;
              p_header_rec.ship_from_org_id          := arg_in_p_header_rec.ship_from_org_id;
              p_header_rec.payment_term_id           := arg_in_p_header_rec.payment_term_id;
              p_header_rec.price_list_id          := 1000;
              p_header_rec.freight_terms_code          := 'Due';     -- Prepay and Add
              p_header_rec.operation               := OE_GLOBALS.G_OPR_CREATE;
              p_header_rec.pricing_date          := SYSDATE;
              p_header_rec.creation_date          := SYSDATE;
              p_header_rec.booked_flag          := 'N';
              p_header_rec.created_by               := 1318;
              p_header_rec.last_updated_by          := 1318;
              p_header_rec.last_update_date          := SYSDATE;
              p_header_rec.invoice_to_org_id          := 1424;
              p_header_rec.version_number          := 1;
              p_header_rec.open_flag               := 'Y';
              p_header_rec.ordered_date          := SYSDATE;
              p_header_rec.flow_status_code          := 'ENTERED';
              p_header_rec.tax_exempt_flag          := 'S';
              p_header_rec.salesrep_id          := -3;
    --------------------------------------------LINES CODE------------------------------------------------------------
         icount := 0;
         for icount in 1 .. arg_in_p_line_tbl.count loop
              p_line_tbl(icount) := Oe_Order_Pub.G_MISS_LINE_REC;
              SELECT OE_ORDER_LINES_S.NEXTVAL INTO p_line_tbl(icount).line_id FROM DUAL;
              dbms_output.put_line('Line ID               = '|| p_line_tbl(icount).line_id);
         p_line_tbl(icount).inventory_item_id          := arg_in_p_line_tbl(icount).inventory_item_id;
         p_line_tbl(icount).ordered_quantity          := arg_in_p_line_tbl(icount).ordered_quantity;
         p_line_tbl(icount).pricing_quantity          := arg_in_p_line_tbl(icount).pricing_quantity;
         p_line_tbl(icount).line_type_id               := arg_in_p_line_tbl(icount).line_type_id;
         p_line_tbl(icount).line_number          := icount;
         p_line_tbl(icount).shipment_number          := arg_in_p_line_tbl(icount).shipment_number;
         p_line_tbl(icount).ship_to_org_id          := arg_in_p_line_tbl(icount).ship_to_org_id;
         p_line_tbl(icount).sold_to_org_id          := arg_in_p_line_tbl(icount).sold_to_org_id;
         p_line_tbl(icount).salesrep_id          := arg_in_p_line_tbl(icount).salesrep_id;
         p_line_tbl(icount).payment_term_id          := arg_in_p_line_tbl(icount).payment_term_id;
              p_line_tbl(icount).price_list_id          := 1000;
              p_line_tbl(icount).operation               := OE_GLOBALS.G_OPR_CREATE;
              p_line_tbl(icount).open_flag               := 'Y';
              p_line_tbl(icount).booked_flag               := 'N';
              p_line_tbl(icount).header_id               := p_header_rec.header_id;
              p_line_tbl(icount).line_category_code          := 'ORDER';
              p_line_tbl(icount).order_quantity_uom          :='Ea';
              p_line_tbl(icount).request_date               := SYSDATE;
              p_line_tbl(icount).schedule_ship_date          := SYSDATE;
              p_line_tbl(icount).ship_from_org_id          := 204;
              p_line_tbl(icount).flow_status_code          := 'ENTERED';
              p_line_tbl(icount).ship_to_customer_id          := 1290;
              p_line_tbl(icount).invoice_to_org_id          := 1424;
              p_line_tbl(icount).tax_exempt_flag          := 'S';
              p_line_tbl(icount).tax_date               := '02-Mar-2005';
              p_line_tbl(icount).tax_code               := 'Location';
              SELECT OE_PRICE_ADJUSTMENTS_S.NEXTVAL INTO p_Line_Adj_tbl(icount).price_adjustment_id FROM DUAL;
              dbms_output.put_line('Price Adjustment ID     = '|| p_Line_Adj_tbl(icount).price_adjustment_id);
              p_Line_Adj_tbl(icount).created_by          := 1318;
              p_Line_Adj_tbl(icount).header_id          := p_header_rec.header_id;
              p_Line_Adj_tbl(icount).line_id               := p_line_tbl(icount).line_id;
              p_Line_Adj_tbl(icount).percent               := 10;
              p_Line_Adj_tbl(icount).operation          := OE_GLOBALS.G_OPR_CREATE;
              p_Line_Adj_tbl(icount).list_header_id          := 8988;
              p_Line_Adj_tbl(icount).list_line_id          := 16596;
              p_Line_Adj_tbl(icount).list_line_type_code     := 'DIS';
              p_Line_Adj_tbl(icount).arithmetic_operator     := 'AMT';
              p_Line_Adj_tbl(icount).updated_flag          := 'Y';
              p_Line_Adj_tbl(icount).update_allowed          := 'Y';
              p_Line_Adj_tbl(icount).applied_flag          := 'Y';
              p_Line_Adj_tbl(icount).automatic_flag          := 'N';
              p_Line_Adj_tbl(icount).OPERAND               := 10;
         end loop;
         oe_msg_pub.initialize;
         oe_order_pub.process_order
              ( p_api_version_number =>      p_api_version_number
              , p_init_msg_list =>      FND_API.G_FALSE
              , p_return_values =>      FND_API.G_FALSE
              , p_action_commit =>      FND_API.G_FALSE
              , x_return_status =>      x_return_status
              , x_msg_count =>      x_msg_count
              , x_msg_data =>      x_msg_data
              , p_header_rec =>     p_header_rec
              , p_old_header_rec =>     p_old_header_rec
              , p_header_val_rec =>     p_header_val_rec
              , p_old_header_val_rec =>     p_old_header_val_rec
              , p_Header_Adj_tbl =>     p_Header_Adj_tbl
              , p_old_Header_Adj_tbl =>     p_old_Header_Adj_tbl
              , p_Header_Adj_val_tbl =>     p_Header_Adj_val_tbl
              , p_old_Header_Adj_val_tbl =>     p_old_Header_Adj_val_tbl
              , p_Header_price_Att_tbl =>     p_Header_price_Att_tbl
              , p_old_Header_Price_Att_tbl =>     p_old_Header_Price_Att_tbl
              , p_Header_Adj_Att_tbl =>     p_Header_Adj_Att_tbl
              , p_old_Header_Adj_Att_tbl =>      p_old_Header_Adj_Att_tbl
              , p_Header_Adj_Assoc_tbl =>     p_Header_Adj_Assoc_tbl
              , p_old_Header_Adj_Assoc_tbl =>      p_old_Header_Adj_Assoc_tbl
              , p_Header_Scredit_tbl =>     p_Header_Scredit_tbl
              , p_old_Header_Scredit_tbl =>     p_old_Header_Scredit_tbl
              , p_Header_Scredit_val_tbl =>     p_Header_Scredit_val_tbl
              , p_old_Header_Scredit_val_tbl =>     p_old_Header_Scredit_val_tbl
              , p_line_tbl =>     p_line_tbl
              , p_old_line_tbl =>     p_old_line_tbl
              , p_line_val_tbl =>     p_line_val_tbl
              , p_old_line_val_tbl =>     p_old_line_val_tbl
              , p_Line_Adj_tbl =>     p_Line_Adj_tbl
              , p_old_Line_Adj_tbl =>     p_old_Line_Adj_tbl
              , p_Line_Adj_val_tbl =>     p_Line_Adj_val_tbl
              , p_old_Line_Adj_val_tbl =>     p_old_Line_Adj_val_tbl
              , p_Line_price_Att_tbl =>     p_Line_price_Att_tbl
              , p_old_Line_Price_Att_tbl =>     p_old_Line_Price_Att_tbl
              , p_Line_Adj_Att_tbl =>     p_Line_Adj_Att_tbl
              , p_old_Line_Adj_Att_tbl =>      p_old_Line_Adj_Att_tbl
              , p_Line_Adj_Assoc_tbl =>     p_Line_Adj_Assoc_tbl
              , p_old_Line_Adj_Assoc_tbl =>      p_old_Line_Adj_Assoc_tbl
              , p_Line_Scredit_tbl =>     p_Line_Scredit_tbl
              , p_old_Line_Scredit_tbl =>     p_old_Line_Scredit_tbl
              , p_Line_Scredit_val_tbl =>     p_Line_Scredit_val_tbl
              , p_old_Line_Scredit_val_tbl =>     p_old_Line_Scredit_val_tbl
              , p_Lot_Serial_tbl =>     p_Lot_Serial_tbl
              , p_old_Lot_Serial_tbl =>     p_old_Lot_Serial_tbl
              , p_Lot_Serial_val_tbl =>     p_Lot_Serial_val_tbl
              , p_old_Lot_Serial_val_tbl =>     p_old_Lot_Serial_val_tbl
              , p_action_request_tbl =>     p_action_request_tbl
              , x_header_rec =>      x_header_rec
              , x_header_val_rec =>      x_header_val_rec
              , x_Header_Adj_tbl =>      x_Header_Adj_tbl
              , x_Header_Adj_val_tbl =>      x_Header_Adj_val_tbl
              , x_Header_price_Att_tbl =>      x_Header_price_Att_tbl
              , x_Header_Adj_Att_tbl =>      x_Header_Adj_Att_tbl
              , x_Header_Adj_Assoc_tbl =>      x_Header_Adj_Assoc_tbl
              , x_Header_Scredit_tbl =>      x_Header_Scredit_tbl
              , x_Header_Scredit_val_tbl =>      x_Header_Scredit_val_tbl
              , x_line_tbl =>      x_line_tbl
              , x_line_val_tbl =>      x_line_val_tbl
              , x_Line_Adj_tbl =>      x_Line_Adj_tbl
              , x_Line_Adj_val_tbl =>      x_Line_Adj_val_tbl
              , x_Line_price_Att_tbl =>      x_Line_price_Att_tbl
              , x_Line_Adj_Att_tbl =>      x_Line_Adj_Att_tbl
              , x_Line_Adj_Assoc_tbl =>      x_Line_Adj_Assoc_tbl
              , x_Line_Scredit_tbl =>      x_Line_Scredit_tbl
              , x_Line_Scredit_val_tbl =>      x_Line_Scredit_val_tbl
              , x_Lot_Serial_tbl =>      x_Lot_Serial_tbl
              , x_Lot_Serial_val_tbl =>      x_Lot_Serial_val_tbl
              , x_action_request_tbl     =>      x_action_request_tbl
         IF (x_return_status = FND_API.G_RET_STS_SUCCESS) THEN
              COMMIT;
         dbms_output.put_line('Return Status - '|| SUBSTR (x_return_status,1,255));
         dbms_output.put_line('------------------------------------');
         dbms_output.put_line('Order Number ==== '|| x_header_rec.order_number);
         dbms_output.put_line('------------------------------------');
              arg_out_x_return_status := x_return_status;
              arg_out_order_number          := x_header_rec.order_number;
              arg_out_header_id          := p_header_rec.header_id;
              arg_out_flow_status_code     := p_header_rec.flow_status_code;
         ELSE
              dbms_output.put_line('Return Status = '|| SUBSTR (x_return_status,1,255));
              dbms_output.put_line('Msg Count = '|| TO_CHAR(x_msg_count));
              dbms_output.put_line('Msg Data = '|| SUBSTR (x_msg_data,1,255));
              IF x_msg_count >1 THEN
                   FOR I IN 1..x_msg_count LOOP
                        Oe_Msg_Pub.get(
                             p_msg_index           => i
                             ,p_encoded           => Fnd_Api.G_FALSE
                             ,p_data           => v_msg_data
                             ,p_msg_index_out      => v_msg_index_out
                        DBMS_OUTPUT.PUT_LINE('v_msg_index_out '|| v_msg_index_out);
                        DBMS_OUTPUT.PUT_LINE('v_msg_data '|| v_msg_data);
                   END LOOP;
              END IF;
         END IF;
    END;
    /

  • How to read values from Property file into BPEL process local variable?

    I would like to use a Property file with some parameters e.g.
    <myparm1>12345</myparm1>
    How can I read from a BPEL process such a Property file and assign it into e.g. local variable "intparm1"?
    Where (in which directory) should I put this XML Property file to have it always available for reading?
    Peter

    Hi,
    You can also use
    ora:readFile( ) function as follow :
    ora:readFile(xml file location (ex. "file:///D:\\SOA\\FileAdapters\\readFile\\test\\test.xml"),xsd file location (ex."file:///D:\\SOA\\FileAdapters\\readFile\\test\\test.xsd"))
    inside the assign activity and assign this to the variable you want.
    regards
    arababah
    Edited by: arababah on Aug 10, 2009 12:55 AM

  • How to read values from Property XMLfile into BPEL process local variable?

    I would like to use a Property file with some parameters e.g.
    <myparm1>
    12345
    </myparm1>
    How can I read from a BPEL process such a Property XML text file and assign it into e.g. local variable "intparm1"?
    Where (in which directory) should I put this XML Property file to have it always available for reading?
    Peter

    Hi,
    You can also use
    ora:readFile( ) function as follow :
    ora:readFile(xml file location (ex. "file:///D:\\SOA\\FileAdapters\\readFile\\test\\test.xml"),xsd file location (ex."file:///D:\\SOA\\FileAdapters\\readFile\\test\\test.xsd"))
    inside the assign activity and assign this to the variable you want.
    regards
    arababah
    Edited by: arababah on Aug 10, 2009 12:55 AM

  • XML input into BPEL Process

    Hi,
    I am trying to create a BPEL process which receives XML input and then uses this input to insert data into the database.
    I have a stored procedure which will accept the input variables and do the insert.
    My XML looks like below:
    <Acc_type>
    <code> ABC </code>
    <name> Savings Account </name>
    </Acc_type>
    My stored Procedure has to input variables - code and name. I have changed the Receive activities, Process Request to include 2 inputs - code and name.
    I am not sure what changes need to be made to specify that the input will be in XML and also how to map the XML to the variables.
    Also, is it possible to use the same format for the XML as used when you initiate a BPEL Process and select XML Source? If I do this will I still need to make other changes?
    Thanks...

    Hi,
    I have tried implementing the ora:parseEscapedXML function, I have used the following expression to copy the data in the CODE node to my variable also called CODE.
    ora:parseEscapedXML(bpws:getVariableData('inputVariable','payload','/client:TestXML2ProcessRequest/client:input','/Acc_Type/code'))
    I get the following error message:
    ORABPEL-09500 XPath expression failed to execute. Error while processing xpath expression, the expression is "ora:parseEscapedXML(bpws:getVariableData('inputVariable','payload','/client:TestXML2ProcessRequest/client:input','//Acc_Type/code'))", the reason is FOTY0001: type error. Please verify the xpath query.
    I am not sure if the format of my expression is correct especially - '/Acc_Type/code'
    Please help...

  • Attaching BLOB Data using BPEL Process

    Hi,
    I need to upload resume(BLOB Data) into irc_documents.binary_doc(binay_doc is BOLB Data type) by using BPEL Process.
    Could you please let me know the steps to be followed to upload the Binary Document.
    My Contact Mail Id:[email protected]
    Regards,
    Praveen

    by use of for example a opaque schema you should be able to get the data in your process.
    http://soastuff.wordpress.com/2007/06/06/handling-opaque-datatypes-in-bpelesb/
    this might help.
    do you want to send the binary data thrue the whole bpel process, or do you want to get in somewhere in the middle of the process ?

  • How to convert cXML dtd files into xsd format and use them into BPEL application

    Hi,
    In my BPEL application I have to use cXML dtd files by converting them into xsd format.
    I have used 'Microsoft Visual Studio' for converting cXML.dtd file into xsd format, for this 1 dtd file I am getting three xsd files (cXML.xsd, cXML1.xsd and cXML2.xsd).
    Please check this once and let me know
    1. why I am getting three xsd files for one dtd file,
    2. how can I use cXML.xsd file in my application, do I ll have to use all the three files in my BPEL app and
    3. what should I include in main xsd file (cXML.xsd) to import other two xsd files.
    kindly check this once and let me know your suggestions .
    Thanks

    Hi,
    While downloading the cXML dtd there will be example xml files. Using this xml's we can generate xsd.
    Regards,
    KANN.

  • Validation for Incoming Orders

    Hi,
         Can somebody tell me how to process the segments in a customer function (Exit)? I am developing an interface for incoming ORDERS05 (Sales Order).Before the Idoc is posted, I need to check whether the Ship-To Customer is a One time account. If somebody could give me the code, that would be appreciated.
    Thanks,
    Venkat.

    You need to do it using the predefined SAP user exits.
    You need to find, based on the message type you are dealing with, the corresponding function module used (for outbound or inbound processing). In this function module (ex: IDOC_INPUT_ORDER) you will find the function exit calls like this:
        CALL CUSTOMER-FUNCTION '011'
             EXPORTING
                  dxvbak  = xvbak
                  docnum  = idoc_contrl-docnum
             TABLES
                  derrtab = errtab
                  dxvbap  = xvbap
                  dxvbep  = xvbep
                  dxvbadr = xvbadr
                  dxvbpa  = xvbpa
                  dxvbuv  = xvbuv
                  dedidc  = idoc_contrl
                  dedidd  = idoc_data
                  dxkomv  = xkomv
                  dxvekp  = xvekp
                  dyvekp  = yvekp.
    Create a enhancement project in CMOD, using the enhancement that contains the function exit (you can search for it in SMOD dropdown and entereing the function module in the component Additional search in SMOD).
    Activate it and enter your code in there.
    For specific examples, you will need to provide us the name of the message type or function module you are trying to "enhance".
    This is simple example and you can write your own logic based on below example :
    DATA: ZE1EDPT2 LIKE E1EDPT2.
    LOOP AT IDOC_DATA.
      CASE IDOC_DATA-SEGNAM.
         WHEN 'E1EDPT2'.
           MOVE IDOC_DATA-SDATA TO ZE1EDPT2.
           ZE1EDPT2-TDLINE   = <...>   
           ZE1EDPT2-TDFORMAT = <...>    
           MOVE ZE1EDPT2 TO IDOC_DATA-SDATA.
           MODIFY IDOC_DATA.
         WHEN <...>
         OTHERS.    
       ENDCASE.
    ENDLOOP.
    Thanks
    Seshu

  • Parameter Validation for invalid date entered

    I enter an invalid date like 99/08/2014 as one of the parameters for my report and get the following error.
    The value provided for the report parameter 'P1' is not valid for its type. (rsReportParameterTypeMismatch)
    To the report user audience, this message is not meaningful and it happened before the report is even executed . 
    Is there any way to override this and put a more meaningful error in ?

    Hello,
    According to your description, you want to custom the error message when the input date value is invalid. In Reporting Services, it doesn’t provide any interference for us to modify the system error message (the text in grey color). That means we can’t modify
    the system message when error occurs. However we can create a textbox in this report, use custom code and expression to display the custom error message. For more details, please refer to the following steps:
    Go to Report Properties. Put the code below into custom code:
    Public Shared a As Integer=0
    Public Shared Function IsDate(d1 As String) as Integer
    Try
    FormatDateTime(d1)
    Catch ex As Exception
    a=1
    End Try
    return a
    End Function
    Change the parameter data type from Date to Text.
    Change the filter expression from Parameters!ReportParameter1.Value to the following:
    =IIF(Code.IsDate(Parameters!ReportParameter1.Value)=0,cdate(Parameters!ReportParameter1.Value),CDate("1/3/2013"))
    Use the expression below to set the visibility of the tablix:
    =IIF(Code.IsDate(Parameters!ReportParameter1.Value)=0,false,true)
    Create a textbox with the expression below:
    =IIF(Code.IsDate(Parameters!ReportParameter1.Value)=0,"","custom error message")
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Urgent Requirement : XSD Validation for internal references

    Hi,
    I have a requirement , according to which....i have
    Invoice Date and Contract Date and XSD validations on these two fields are dependent.
    i.e, invoice date is required if contract date is absent .
    Contract date is required if invoice date is absent.
    How can we validate the xml file with this scenario using XSD.
    Thanks for the help....in advance.
    Regards,
    Aru

    Hi,
    The solution to the problem u gave works fine but validates like AND condition not OR.........
    Any other answers..........Thanks for ur reply......
    Aru

Maybe you are looking for

  • How do i use my apple id with ichat?

    how do i use my apple id with ichat?

  • Photo stream is no longer working on my Sony Vio even though it's toggle "on"

    I need help getting the photo stream to begin working again on my Sony Vio PC, Windows 7.   It used to work beautifully with my iphone 5 & ipad.  I've uninstalled iCloud and reinstalled hoping that would reset things.  All 3 devices have photo stream

  • Help? Satellite M645 Overheatin​g

    Hey guys!       I'm a Toshiba user from Brazil, and I have a little problem (by the way, can become a very big problem i think) and maybe u guys can help me, my notebook its overheating, i got no shutdown's BUT the heat its very high i don't monitor

  • Use a chained SSL cert instead of root CA cert?

    We have a PKI infrastructure in place, and I was wondering if I could use the cert and key from one of our issuing CA's which chains back to our root CA, instead of the root CA's cert to do HTTPS proxy?            or more technically, will the WSA ta

  • Gateway URL setting?

    Hi - I think I screwed something up and am looking for a quick hand. * G6 .NET box lives at https://www.mydomain.com/portal/server.pt * Collab appears to think the gateway URL is https://www.mydomain.com/server.pt (NOTE that key bit - lacking "/porta