Passing parameters in process flow

Hi All,
Is there a way to pass parameters between different process flow operators like transformation activity, mapping, etc using any variable. Either defining new variable or using existing variable. Does process flow provides any variables whose values can be changed by one mapping and used by mapping following it.
Any help would be appreicated.
Platform - OWB 10gR1
Regards,
Ron.

write a PL/SQL transformation, function or procedure either. Call the Transformation before the mapping, like if you want to execute that mapping or not based on the return vale.
"can be changed by one mapping and used by mapping following it"
Yes, you can. Log the value into database , then convert the following mapping as the PL/SQL transformation, where you can easily take the previous mapping output value, which has been stored. All you need some temp parameter table. The way you can define a table to be used for more than one case.

Similar Messages

  • Passing Parameter to Process flow

    Hello,
    I have a mapping that has input parameter. Now i create a process flow and use this mapping, each time i run the process flow it prompt for the parameter
    Is there a way to pass the parameter to the process flow directly withput prompting ?
    Thanks

    Hi ,
    I found something related in doc. http://download.oracle.com/docs/cd/B31080_01/doc/owb.102/b28223/ref_processflows.htm#i1173362
    "If a mapping contains a Mapping Input Parameter operator, specify a value according to its data type. The Process Flow Editor expects to receive a PL/SQL expression when you add a Mapping Input Parameter operator to a mapping. If the Mapping Input Parameter is a string, enclose the string in double quotes."
    But it is not clear how to do this ?
    Thanks

  • Passing paramater from process flow to unix script in owb

    Hi,
    I need help in calling a function the return value must be passed as a paramater to user defined activity operator in owb which would in turn run a unix script on the server which would use the paramater passed.
    Thanks,
    Ashvin.

    hi let me give you some more infor about my proble.
    i have a unix script named caproc. The script would be passed a paramater. the script would be called from simple owb process flow and i need to pass the paramater to it.
    i have tested running other unix scripts and the are running fine.
    as you said to create a variable 'x' i did that and under paramater_list of the user activity operator under binding i selected the variable 'X'
    the process flow was valiadated fine and deployed but when i run it it gives me this error.
    COPY_OF_UX_SCP_CALL
    Error
    RPE-01003: An infrastructure condition prevented the request from completing.
    COPY_OF_UX_SCP_CALL
    Error
    RPE-01038: Failed to evaluate expression declare "$LOOP_DETECT$" NUMBER := 0;function "COPY_OF_UX_SCP_CALL" return VARCHAR2 is "WARNING" NUMBER := 2;"RETURN_RESULT_NUMBER" NUMBER := NULL;"NUMBER_OF_ERRORS" NUMBER := 0;"SUCCESS" NUMBER := 1;"ITEM_TYPE" VARCHAR2(4000) := (owbsys.wb_rt_task_variable.get_value(305587));"ERROR" NUMBER := 3;"EVAL_LOCATION" VARCHAR2(4000) := (owbsys.wb_rt_task_variable.get_value(305590));"OK" NUMBER := 1;"FAILURE" NUMBER := 3;"AUDIT_ID" NUMBER := 305586;"RETURN_CODE" NUMBER := NULL;"NUMBER_OF_WARNINGS" NUMBER := 0;"ITEM_KEY" VARCHAR2(4000) := (owbsys.wb_rt_task_variable.get_value(305589));"RETURN_RESULT" VARCHAR(64) := NULL;"PARENT_AUDIT_ID" NUMBER := NULL;"OK_WITH_WARNINGS" NUMBER := 2;begin "$LOOP_DETECT$" := "$LOOP_DETECT$" + 1;if "$LOOP_DETECT$" > 2 then raise_application_error(-20001, 'Loop detected calling "COPY_OF_UX_SCP_CALL"');end if;return to_char(?'acac');end;begin :result := "COPY_OF_UX_SCP_CALL";end;. Please modify the expression, redeploy and retry again.
    COPY_OF_UX_SCP_CALL
    Error
    Missing IN or OUT parameter at index:: 2
    i am pasting the xml script owb generates which might help someone to point me the problem
    <?xml version = '1.0'?>
    <!DOCTYPE Package SYSTEM "jar:file:/C:/product/11.1.0/db_1/owb/lib/int/rtpcommon.jar!/Package_dtd.txt">
    <Package Id="SPT_TRY" Name="SPT_TRY">
    <PackageHeader>
    <XPDLVersion/>
    <Vendor/>
    <Created/>
    <Description></Description>
    </PackageHeader>
    <TypeDeclarations/>
    <Applications>
    <Application Id="A805FAF687910739AE04011AC69063028" Name="UX_SCRIPT">
    <FormalParameters>
    <FormalParameter Id="EXIT_CODE" Mode="OUT">
    <DataType>
    <DeclaredType Id="EXIT_STATUS"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:COMMAND">
    <DataType>
    <BasicType Type="STRING"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:PARAMETER_LIST">
    <DataType>
    <BasicType Type="STRING"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:SUCCESS_THRESHOLD">
    <DataType>
    <BasicType Type="INTEGER"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:SCRIPT">
    <DataType>
    <BasicType Type="STRING"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:RESULT_CODE" Mode="OUT">
    <DataType>
    <BasicType Type="INTEGER"/>
    </DataType>
    </FormalParameter>
    </FormalParameters>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:Function" Value="SHELL"/>
    <ExtendedAttribute Name="OWB:ExtendedAttributes" Value="TASK_ID">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:TaskName"/>
    <ExtendedAttribute Name="OWB:ExecStoreUOID"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </Application>
    <Application Id="A81117E4A8F6699DAE04011AC680650B6" Name="UX_SCRIPT">
    <FormalParameters>
    <FormalParameter Id="EXIT_CODE" Mode="OUT">
    <DataType>
    <DeclaredType Id="EXIT_STATUS"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:COMMAND">
    <DataType>
    <BasicType Type="STRING"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:PARAMETER_LIST">
    <DataType>
    <BasicType Type="STRING"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:SUCCESS_THRESHOLD">
    <DataType>
    <BasicType Type="INTEGER"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:SCRIPT">
    <DataType>
    <BasicType Type="STRING"/>
    </DataType>
    </FormalParameter>
    <FormalParameter Id="CFG:RESULT_CODE" Mode="OUT">
    <DataType>
    <BasicType Type="INTEGER"/>
    </DataType>
    </FormalParameter>
    </FormalParameters>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:Function" Value="SHELL"/>
    <ExtendedAttribute Name="OWB:ExtendedAttributes" Value="TASK_ID">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:TaskName"/>
    <ExtendedAttribute Name="OWB:ExecStoreUOID"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </Application>
    </Applications>
    <WorkflowProcesses>
    <WorkflowProcess Id="UX_SCP_CALL" Name="UX_SCP_CALL">
    <ProcessHeader>
    <Description></Description>
    </ProcessHeader>
    <FormalParameters>
    <FormalParameter Id="EXIT_CODE" Mode="OUT">
    <DataType>
    <DeclaredType Id="EXIT_STATUS"/>
    </DataType>
    </FormalParameter>
    </FormalParameters>
    <DataFields/>
    <Activities>
    <Activity Id="UX_SCRIPT" Name="UX_SCRIPT">
    <Description></Description>
    <Implementation>
    <Tool Id="A805FAF687910739AE04011AC69063028" Type="APPLICATION">
    <ActualParameters>
    <ActualParameter/>
    <ActualParameter>"/bin/bash"</ActualParameter>
    <ActualParameter/>
    <ActualParameter>"0"</ActualParameter>
    <ActualParameter/>
    <ActualParameter/>
    </ActualParameters>
    <Description></Description>
    </Tool>
    </Implementation>
    <TransitionRestrictions>
    <TransitionRestriction>
    <Split Type="XOR"/>
    </TransitionRestriction>
    </TransitionRestrictions>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="805FAF687910739AE04011AC69063028"/>
    <ExtendedAttribute Name="OWB:ExtendedAttributes" Value="TASK_ID">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:TaskName" Value="&quot;UX_SCP_CALL:UX_SCRIPT&quot;"/>
    <ExtendedAttribute Name="OWB:ExecStoreUOID" Value="&quot;{0}&quot;"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    <ExtendedAttribute Name="OWB:Position">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:XPos" Value="262.0"/>
    <ExtendedAttribute Name="OWB:YPos" Value="-219.0"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </Activity>
    <Activity Id="END_SUCCESS" Name="END_SUCCESS">
    <Description></Description>
    <Implementation>
    <Tool Id="END" Type="APPLICATION">
    <ActualParameters>
    <ActualParameter>OK</ActualParameter>
    </ActualParameters>
    <Description></Description>
    </Tool>
    </Implementation>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="805FAF68790F739AE04011AC69063028"/>
    <ExtendedAttribute Name="OWB:Position">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:XPos" Value="450.0"/>
    <ExtendedAttribute Name="OWB:YPos" Value="-40.0"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </Activity>
    <Activity Id="START1" Name="START1">
    <Description></Description>
    <Implementation>
    <Tool Id="START" Type="APPLICATION">
    <Description></Description>
    </Tool>
    </Implementation>
    <TransitionRestrictions>
    <TransitionRestriction>
    <Split Type="XOR"/>
    </TransitionRestriction>
    </TransitionRestrictions>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="805FAF68790E739AE04011AC69063028"/>
    <ExtendedAttribute Name="OWB:Position">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:XPos" Value="-321.0"/>
    <ExtendedAttribute Name="OWB:YPos" Value="-211.0"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </Activity>
    </Activities>
    <Transitions>
    <Transition Id="TRANSITION_1" From="UX_SCRIPT" To="END_SUCCESS">
    <Condition Type="OTHERWISE"/>
    </Transition>
    <Transition Id="TRANSITION" From="START1" To="UX_SCRIPT"/>
    </Transitions>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="805FAF687909739AE04011AC69063028"/>
    <ExtendedAttribute Name="OWB:ExtendedAttributes" Value="TASK_ID">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:RootUOID" Value="&quot;805FAF687909739AE04011AC69063028&quot;"/>
    <ExtendedAttribute Name="OWB:TaskName" Value="&quot;UX_SCP_CALL&quot;"/>
    <ExtendedAttribute Name="OWB:ExecStoreUOID" Value="&quot;{0}&quot;"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </WorkflowProcess>
    <WorkflowProcess Id="COPY_OF_UX_SCP_CALL" Name="COPY_OF_UX_SCP_CALL">
    <ProcessHeader>
    <Description></Description>
    </ProcessHeader>
    <FormalParameters>
    <FormalParameter Id="EXIT_CODE" Mode="OUT">
    <DataType>
    <DeclaredType Id="EXIT_STATUS"/>
    </DataType>
    </FormalParameter>
    </FormalParameters>
    <DataFields>
    <DataField Id="X">
    <DataType>
    <BasicType Type="STRING"/>
    </DataType>
    <InitialValue>`?'acac'`</InitialValue>
    </DataField>
    </DataFields>
    <Activities>
    <Activity Id="END_SUCCESS" Name="END_SUCCESS">
    <Description></Description>
    <Implementation>
    <Tool Id="END" Type="APPLICATION">
    <ActualParameters>
    <ActualParameter>OK</ActualParameter>
    </ActualParameters>
    <Description></Description>
    </Tool>
    </Implementation>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="81117E4A8F6999DAE04011AC680650B6"/>
    <ExtendedAttribute Name="OWB:Position">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:XPos" Value="450.0"/>
    <ExtendedAttribute Name="OWB:YPos" Value="-40.0"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </Activity>
    <Activity Id="UX_SCRIPT" Name="UX_SCRIPT">
    <Description></Description>
    <Implementation>
    <Tool Id="A81117E4A8F6699DAE04011AC680650B6" Type="APPLICATION">
    <ActualParameters>
    <ActualParameter/>
    <ActualParameter>"/bin/bash"</ActualParameter>
    <ActualParameter>X</ActualParameter>
    <ActualParameter>"0"</ActualParameter>
    <ActualParameter/>
    <ActualParameter/>
    </ActualParameters>
    <Description></Description>
    </Tool>
    </Implementation>
    <TransitionRestrictions>
    <TransitionRestriction>
    <Split Type="XOR"/>
    </TransitionRestriction>
    </TransitionRestrictions>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="81117E4A8F6699DAE04011AC680650B6"/>
    <ExtendedAttribute Name="OWB:ExtendedAttributes" Value="TASK_ID">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:TaskName" Value="&quot;COPY_OF_UX_SCP_CALL:UX_SCRIPT&quot;"/>
    <ExtendedAttribute Name="OWB:ExecStoreUOID" Value="&quot;{0}&quot;"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    <ExtendedAttribute Name="OWB:Position">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:XPos" Value="262.0"/>
    <ExtendedAttribute Name="OWB:YPos" Value="-219.0"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </Activity>
    <Activity Id="START1" Name="START1">
    <Description></Description>
    <Implementation>
    <Tool Id="START" Type="APPLICATION">
    <Description></Description>
    </Tool>
    </Implementation>
    <TransitionRestrictions>
    <TransitionRestriction>
    <Split Type="XOR"/>
    </TransitionRestriction>
    </TransitionRestrictions>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="81117E4A8F6499DAE04011AC680650B6"/>
    <ExtendedAttribute Name="OWB:Position">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:XPos" Value="-321.0"/>
    <ExtendedAttribute Name="OWB:YPos" Value="-211.0"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </Activity>
    </Activities>
    <Transitions>
    <Transition Id="TRANSITION_1" From="UX_SCRIPT" To="END_SUCCESS">
    <Condition Type="OTHERWISE"/>
    </Transition>
    <Transition Id="TRANSITION" From="START1" To="UX_SCRIPT"/>
    </Transitions>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="81117E4A8F6199DAE04011AC680650B6"/>
    <ExtendedAttribute Name="OWB:ExtendedAttributes" Value="TASK_ID">
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:RootUOID" Value="&quot;81117E4A8F6199DAE04011AC680650B6&quot;"/>
    <ExtendedAttribute Name="OWB:TaskName" Value="&quot;COPY_OF_UX_SCP_CALL&quot;"/>
    <ExtendedAttribute Name="OWB:ExecStoreUOID" Value="&quot;{0}&quot;"/>
    </ExtendedAttributes>
    </ExtendedAttribute>
    </ExtendedAttributes>
    </WorkflowProcess>
    </WorkflowProcesses>
    <ExtendedAttributes>
    <ExtendedAttribute Name="OWB:UOID" Value="805FAF687904739AE04011AC69063028"/>
    </ExtendedAttributes>
    </Package>

  • Data Type for Process Flow... PB with Date?

    I've got a problem by passing parameters in process flow.
    I have a mapping with a parameter DATE_EXEC (data type : DATE) and a default value that is TO_DATE('20/01/2007' , 'dd/mm/yyyy') . My mapping is working good when i launch it.
    I have a process flow which contains the mapping. This process has a parameter DATE_EXEC (data type : DATE). I bind the 2 DATE_EXEC. But when i launch my mapping the value is not recognized, I try with :
    - TO_DATE('20/01/2007' , 'dd/mm/yyyy')
    - 20/01/2007
    - 2007.01.20
    - 2007-01-20
    My question is what are the data type in process flow? They are not ORACLE TYPE.
    For example , a parameter in a mapping which is a VARCHAR2 must be input between quotes but if you bind it to a parameter of a process flow which is a STRING (not ORACLE Data type) , you must input it without quotes?
    Anybody has some rules about that?
    I apologize for my english, i'm a french people.

    Here is some information on the literal quote or not quote query and what I think you need to do at the end, hope it helps. Not exactly intuitive...since the flow designer (you) have to know what is a PLSQL object and what is not.
    1. Literal = FALSE
    When Literal = FALSE is set then the value entered must be a valid PL/SQL expression which is evaluated at the Control Center e.g.
    'Hello World!'
    22 / 7
    2. Literal = TRUE
    When Literal = TRUE then the value is dependent on the the type of Activity. If the activity is a PL/SQL object i.e. Mapping or Transformation, then the value is PL/SQL snippet. The critical difference here is that the value is macro substituted into the call for the object. The format of the value is identical to that entered as default value in the Mapping editor. e.g.
    'Hello World!'
    sysdate()
    If the activity type is not a PL/SQL object then the value is language independent. e.g.
    Hello World
    3.1427571
    What you should try......
    Check the map activity parameter in your process flow to see if literal is false (an expression), set it to false and then try using your TO_DATE('20/01/2007' , 'dd/mm/yyyy') expression, deploy your flow and execute. Alternatively the user guide defines the DATE type for flow with the format YYYY-MM-DD so you can have the parameter value as '2007-01-20' use literal equal to true and remember and quote your value.
    Cheers
    David

  • Process Flow Parameter Binding.

    The docs on using process flow parameters are a bit sparse, so I wonder if anyone else has some input.
    We kick off our ETL processes by an external enterprise scheduling tool due to several remote dependencies. This tool provides us with an audit id that we want to tag all of our current rows loaded with. Now, creating input parameters on the mappings is easy, but the docs seem to indicate that a parameter passed into a process flow can only be bound to one location. Given that our process includes a few hundred mappings, this would require the input parameter be input several hunderd times with each instance bound to a single mapping. That is not a maintainable option. Similarly, any documentation on passing OUT parameters from mappings to subsequent mappings seems entirely absent, so I'm not sure if I can "daisy chain" passing this parameter along.
    Which, at this point, leaves me with passing in the variable to the process flow, having the first step be a SQL call that saves this ID to a table, and then having each mapping query this table for the audit ID in a pre-mapping procedure to use to tag the rows. The Process Flow will also have to have a closing SQL script to clear the audit id out of the table.
    Is this my best option? Or does anyone have a better idea?
    Thanks,
    Mike

    In 9.2, parameters were added by way of the property sheet for the Start activity.
    In 10.2 what you do is, in the Explorer portion (the top section) of the palette you select the "Start" activity. If you then look at the top bar of the Explorer portion of the palette you will note that the leftmost icon (a green plus sign over a folder) is enabled. This is the Create button which, when pressed, will create an input parameter to the process flow. This paramter may then be used as a bind variable by other activities in the process flow.
    Cheers,
    Mike

  • OWB 11g  Process Flow - How to see variables and how to create variables

    Dear All,
    I have recently migrated from 10g to 11g rel 2.
    In 10g when I open a proces flow I can see all the parameters and variables I created on each activities on "Explorer" window. this allows me to craete new parameters and variables as well.
    But ones after I migrated to 11g, I cant see explorer window and there is no place to enable it as well.
    How Can I create variables, parameters in processes flow on 11g?
    Thanks in advance.
    Alex

    Hi,
    In 11g "Explorer" window renamed as "Stucture" and same details as 10g shows in Structure window. This window can enable and dissable (Show and Hide) using Menu => View=> Stuture option.
    Thanks

  • How can I pass parameters from one process flow to another process flow?

    How can I pass parameters from one process flow to another process flow (sub process) in warehouse builder? let me know the steps I have to do in warehouse builder.
    Thanks in advance,
    Kishan

    Hi Kishan,
    Please post this question to the Warehouse Builder forum:
    Warehouse Builder
    Thanks, Mark

  • Passing parameters from shell script to OWB process flow

    Hi all,
    I am running OWB process flow (using the template script provided by oracle) and i want to pass two date parameters as shown below:
    sqlplus -s $SQL_USER/$SQL_PWD@$ORACLE_SID @$HOME_DIR/src/vmc_oem_exec_script.sql OWB_OWNER VMC_POST_DW_PF_LOC_SIT PROCESS VMC_NM1_PORT_MAIN "," "P_DATE_FROM=$DATE_FROM,P_DATE_TO=$DATE_TO"
    How do i catch those values in process flow and pass those to mappings in Process flow?
    Do i need to create PF variables with same names or any name will do?
    Thanks in advance

    This document is explaining how to pass data between activities in process flow.
    I am passing parameters from a shell script.
    Any ideas,how to pass parameters from shell script and then initialize the process flow variables based on those values and then pass them further to mappings.
    Thanks

  • Passing parameters from mapping to mapping with in process flows

    I am new to OWB and i would appreciate if any one can suggest me on how to solve the issue i have.
    I am trying to pass a parameter from one mapping to another mapping.
    ex: key need to be passed
    start ----->A--->B--->C----->END
    B needs to pass the key to mapping C
    In B i have mapping Out put parameter and in C i have a mapping input parameter.
    In process flow palatte i could see Key as OUT and in C properties i could bind it to Key .
    but i try to deploy this mapping i am getting error below
    PF_PKG Create Error
    RPE-02040: Internal error: KEY cannot be converted to a constant value. Please correct the value. If the problem persists then please contact Oracle Support with the stack trace and details on how to reproduce it.
    TEST_PFCreate INFORMATIONAL
    RPE-02071: Deployment has been aborted due to a previously reported critial error.
    please suggest me how to pass parameters between mappings with in a process flow.

    Hi
    You have to use process flow variables. So the output of map A, say parameter P would bind to variable V and then the input of map B, say Q would bind to variable V. In this way you can push parameters from one activity to the other. Although the UI lets you bind B.Q to A.P, it should not, I think there is a bug reported on this.
    Cheers
    David

  • Process Flow and Passing Parameters to Mappings

    I am missing something.
    I have an Input Parameter on mapping Strategy_Start.
    I want to pass a value from my Process Flow to the Mapping Strategy_Start that is in the Process Flow.
    I have tried to create a Parameter on the Start that has a Literal value and bind that to the Strategy_Start Mapping.
    That didn't work.
    I tried to create variable and pass the value to the Strategy_start,
    That didn't work, I got an error about binding to a out literal.
    What am I missing.
    I could not really find steps in Documentation for this.
    I am using 11gr1
    thanks for any advice or help.
    greG

    Ok,
    For Literal Expressions It was easier than I thought.
    In my Process Flow for the mapping that has a parameter,
    I just set the value of the Parameter when looking in Explorer.
    I thought I had to create a parameter or a variable and then pass that into the value. That is why it was yelling at me about
    can't use a constant value as a parameter in value.
    If this is not the way let me know, but it appears to be ok now.
    thanks
    greG

  • Pass output parameter from mapping to external process in a Process Flow

    In Process flow, how do we pass an Output parameter from a mapping (generated by a post mapping operator) into an external process (shell script)?
    I have a mapping that generates an output parameter and I would like to pass this parameter to an external process (a shell script) with a process flow. Is this possible?

    Hi Norman,
    Unfortunately in the current release, you cannot do this. What you can do, is store the value into a table and read it in the external process, or write it into a file and read it from there. The next release will support passing output parameters from one activity to the next.
    Thanks,
    Mark.

  • Process Flow - Pass paramters between activities

    Need to pass argument from one mapping/component to next piece. What is the way. Process Flow Editor does not seem to show OUT paramters.
    Pasting from a previous post
    Hi,
    I have a requirement to pass output parameter from a Mapping as input to another Mapping. These Mappings are tied together through a Process Flow.
    Start Proc1 -> Map1 -> Map2 -> Proc2 -> End
    Proc 1 will produce an output that will be used by Map1, and then Map1 will produce an oputput to be used by Map2, and so on till Proc2.
    Also, Mapping Output Parameter is not showing up in the Process Flow.
    What is the way to pass a parameter from one Mapping to next one one in a Process Flow?
    Any answers are most welcome.
    - Jojo
    Message was edited by:
    user467494
    Message was edited by:
    user467494
    Message was edited by:
    user467494
    Message was edited by:
    user467494

    Hi,
    What I have is a wrapper procedure that does a select from a control table. I would like to use this wapper procedure to drive the rest of the mapping by passing the parameter through the process flow.
    It makes no sense to do the same select directly as this would be bypassing the wrapper/interface routine.
    Would still prefer to have the ability to pass parameters between activities.
    Would anybody who is presently close to OWB be in a position to answer that. It is important if we want to continue to use OWB to provide us benefits than headaches.
    - Jojo

  • How to pass a paramter to a schedued process flow

    I have a process flow with a one varchar type parameter.
    I want to schedule this process flow and for that I have created a schedule and then attached it to the process flow using Process Flow -> Configuration -> Referred Calendar Option.
    Now my issue was how can I pass the parameter value into the process flow?
    OWB Version : 10.2.x
    Thanks,
    mc

    Hi Si,
    This is what I did.
    I have deployed the process flow with schedule and then goto control center and start the job.
    Then under parameters it's ask for a "EVAL_LOCATION" value. Which is something else.
    In my process flow I have a parameter called "Job_Name" and I want to pass a value for that parameter. But in either control center, no in direct API allow me to pass a value for that parameter.
    Thanks,
    mc

  • Process Flow Parameters.

    A quick question:
    Does anyone know if it is possible to have a process flow pass variable values into variables defined in a sub-process? I mean, clearly I could have the main process run a transformation to write this value to a table, and then have a transformation in the sub-process retrieve it, but I would prefer a cleaner approach if possible.
    Any ideas?

    Aha! It was the Parameters I hadn't got figured out.
    Thanks a lot!
    --Mike                                                                                                                                                                                   

  • SQLPLUS Acitivity in process flow Input parameters to the script

    I have a sqlplus Activity in the process flow. In the script section I have a update statement which has a where clause where I need to pass a date field as input paramter to this script to compare and update the records.
    Is there a way to pass Input Parameters to the script.
    update test
    set last_name = 'TEST'
    where trunc(begin_date) = :begin_date;
    Begin_date is a variable in my process flow which I need to pass to this script.
    Any ideas as to how I can accomplish this.
    Thanks in advance.

    You can Create a procedure of the Update statement with one input paramenter like
    Create Or replace procedure Update_test ( p_begin_date date )
    IS
    update test
    set last_name = 'TEST'
    where trunc(begin_date) = p_begin_date;
    End;Then call this Procedure in the Process Flow and give input parameter from PF variable.
    Cheers
    Nawneet

Maybe you are looking for