Alternative to process flow

Hi!
I have a scenario which looks like it should be implemented with a process flow, but it requires a workflow server and I don`t want to go that way for the moment.
I want to call a stored procedure in the source schema, which populates a temporary table in the source schema. Then I just want to map this temporary table to a cube in the target schema.
This can`t work with a pre-mapping processor because the procedure doesn`t have any input or output parameters. It just reads some data from a table, does some processing and then populates the temporary table with the result.
The (temporary) table is necessary because the generated data are huge (about 2.500.000 rows).
Do I have any other options to execute this mapping, except for the process flow?
Thank you,
Yorgos

Yorgos,
Any mapping can be invoked through PLSQL. You can do it as described in http://www.oracle.com/technology/products/warehouse/sdk/web_services/ws_single_record.html
So, instead of process flow you will have PLSQL wrapper that calls other stored procedures with your logic.
The pseudo code for the wrapper may look like the one below:
begin
Populate temp table
Call OWB mapping that populates cube.
Other stuff (clean up)
End
In the earlier thread we were discussing how to pack multiple workflows together
Calling Process Flows from other projects
You can use the same scenario but think mapping when we say workflow.
Vladimir

Similar Messages

  • 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 and Workflow

    Hi experts, does a process flow cannot be used if we dont have oracle workflow?
    If yes, any of you know the alternative ways to run a schedule mapping sequentially?
    Currently i am running schedule from OWB (Control center manager). And i am not satisfied because the lack of Log / information regarding the job execution. Is there a way to get more detail schedule job logs???
    Thank you in advance guys...

    Oracle is pretty smart when it comes to those things, Im sure the table is not lock because one session is DML:ing it and one is querying it. You can get a deadlock when the sessions are trying to DML for the same row, because update/insert/delete is based on row lock, not table lock.
    What you can do to test these kinds of long operation mappings is to generete the intermediate code from the map - open the map editor and click on genereate - choose intermediate from the dropdown list and click on your target table. Copy that code and run it from i.e toad, do the same thing instantly for the other map and you will found out if your sessions are locking each other.
    Because the owb map is bascly configured in a way that it most of it is unnecessery when your are not running it thrue the repository, like I said. Try to run it they way it is - else create a new one by the code generated in the intermediate mapping.
    Cheers

  • URGENT: Oracle Workflow Error: API-10020 on Creation of OWB Process Flows

    I am trying to use Oracle Workflow to create Process Flows, in order to link together various mappings and components in Oracle Warehouse Builder. However, in the process flow editor window when I attempt to drag an object such as a mapping onto the editor panel, I get an error message stating the below:
    API-10020: Unable to determine if the map is a PLSQL or SQLLDR map, please correct the map or choose another map.
    All my maps are in PLSQL, and the language setting is set to this. I have tried modifying the langauge settings to see if it makes a difference but with no luck. My colleague believes this is a known bug in Oracle Workflow and there is a patch available to correct it.
    Can anyone help with this query please? Thank you for your time.

    In some versions of OWB (10.1, 10.2) The mapping property will display PL/SQL, but will actually be set to NULL in the repository (which will cause PL/SQL to be displayed as default).
    The fix is easy enough: in the developer navigator, right-click on the mapping and go to configure and set the generation language first to something other then PL/SQL (you should get an error) and then place it back to PL/SQL. This should force the GUI to reset the parameter.
    Alternatively, use OMB*Plus:
    OMBALTER MAPPING 'MAPPINGNAME' SET PROPERTIES \
    (GENERATION_LANGUAGE) VALUES ('PLSQL');
    Good Luck,
    Robbert

  • OWB Process Flow - How is the best  version control tool ??

    HI all,
    I just start work with OWB and I have a question to know how is the best way to do something.
    Imagine the scenario below:
    If I have 2 or more requests for example:
    Request 1: Create a Dimension City.
    Request 2: Create a Dimension Products.
    I Have ONE process flow and i need put my changes inside. This is my problem.
    In my scenario I don't know what Request goes to Prod First.
    If I put the Request 1 and Request 2 in my PROCESS FLOW, maybe I need change is someone decide change MY REQUEST PRIORITY.
    There is something in OWB to "control the version or changes" ?? For a mapping I export the MDL and commit on SVN, but I dont know haw can i do with the process flow.
    Something to agree multiples peoples work in different mappings and a SAME PROCESS FLOW ??
    What is best way to work with process flow and version control.
    What are the best practices when it comes to version control?
    Thanks.

    Amit,
    Are you really doing this in 10.1.3.x and not 11g?
    At any rate, I don't see how #2 and #3 relate whatsoever to your choice of a version control system. OK, maybe in #2 if there is some "maintenance" activity to be done against the version control server. Subversion is the open source alternative that you listed there and is pretty commonly used. If your company is already using one of the mentioned tools, why change? About the only thing I'd mention is to advise you NOT to use CVS for well documented reasons (JDev does support it) - if you would have picked CVS otherwise, choose Subversion. As far as question #1 - I've only used Subversion (well, I did use CVS for a while) with JDeveloper, so I can say it was "effective enough for me." In 10.1.3.x, I also used the external svn tools for doing lots of things like merging and so forth; in 11g, the support is much much better.
    Best,
    John

  • Calling pl/sql package on different database in process flow

    Hi there
    Have a process flow which calls procedure on different database. This procedure truncates a table on the remote database.
    Please could somebody confirm we would need to set up dblinks from the owf_mgr schema to the remote database.
    New to wokflow - am i Correct in assuming the process flows run on the owf_mgr
    rather than the control center owbrt.
    Many Thanks

    Hi there,
    Thanks for the reply.
    If my understanding is correct I could have a procedure as follows.
    hkeeping.trunc_table@dblinkname('TABLE_NAME');
    Is this the case?
    Another alternative was to call directly the transformation in the process flow
    e.g. we have pl/sql package on remote database whioch truncates the remote table.
    When we try this with same procedure on same databas as owb user exists on then works fine.
    However on remote database get message below. Does this mean anything to you? How could we sort this?
    RPE-01003: An infrastructure condition prevented the request from completing.
      TEMP_PLOW:TRUNC_TABLE
    Error
    RPE-01038: Failed to evaluate expression null. Please modify the expression, redeploy and retry again.
       TEMP_PLOW:TRUNC_TABLE
    Error
    RPE-01003: An infrastructure condition prevented the request from completing.
       TEMP_PLOW:TRUNC_TABLE
    Error
    RPE-02226: Cannot test Control Center user REMOTEUSERNAME. This user must match the login credentials of the deployment location.
       TEMP_PLOW:TRUNC_TABLE
    Error
    ORA-01937: missing or invalid role name
    Many Thanks

  • PPT on SD process flow

    Hi guys am in need of help from u
    am not so clear about the SD process flow
    can anyone pls send me a PPT on SD process flow
    to my email id:- (<REMOVED BY MODERATOR>).
    thanking u in advance..
    Regards
    Jino.

    Sales Organization   :
    Responsible for:
    •     Distribution of goods and services
    •     Negotiating Sales Conditions
    •     Product Liability and rights of recourse
    •     A sales organization is uniquely assigned to a company code
    •     Master data’s are separately maintained for a sales organization
    •     All items in the Sales and Distribution document belong to a sales organization
    Distribution Channel:
    Means through which products and services reach the customer 
    A distribution channel:
    •     Defines responsibilities
    •     Helps in achieve flexible pricing
    •     Differentiate Sales statistics
    Division:
    •     A division is used to group products and services.
    •     A division represents a product line.
    Sales Area:
    A Sales area is a combination of
    •     Sales organization
    •     Distribution Channel
    •     Division
    Each Sales and distribution document is assigned exactly to one sales area.
    A sales area can belong to only  one company code.
         Sales Organization
         Distribution Channel
         Division
                     Sales Area
    Plant and Storage Location:
    •     A Plant is a location where stock is maintained
    •     Plant and storage location are used by all logistic area of R/3 System
    •     A Plant is uniquely assigned to a company code
    Shipping point:
    •     Shipping point is the highest level of organizational unit in shipping
    •     Each outbound delivery is processed by one shipping point
    •     Shipping points are assigned to a plant
    •     More than one shipping point can be assigned to a plant
    Sales and Distribution is SAP begins with establishing customer relationship and ends with invoicing for the delivery of goods or service provided to the customer .
    A Standard sales transaction has the following flow:
    Inquiry
    Quotation
    Order
    Delivery
    Billing
    The customer order management cycle begins with pre-sales activities.
    A standard order in SAP contains:
    •     Customer and material info
    •     Pricing conditions
    •     Delivery dates and quantities
    •     Shipping info
    •     Billing Info
    Inventory sourcing in SAP is taken care by
    •     Availability check
    Shipping in SAP supports
    •     Outbound delivery creation
    •     Picking
    •     Packing
    •     Post Goods Issue
    Billing in SAP supports
    •     Creating invoices for products and services
    •     Creating credit and debit memo
    •     Cancel previously posted billing documents
    •     Automatically transferring billing documents to accounting
    When a billing document is created for a sales order we
    •     Credit the sales revenue account
    •     Debit the customer receivables account
    Sales Document
    A sales document is grouped into three structures
    •     Header
    •     Item
    •     Schedule Line
    Outbound delivery
    A delivery document is grouped into two structures
    •     Header
    •     Item
    Several orders can be grouped into same outbound delivery if they have same
    •     Shipping point
    •     Delivery date
    •     Ship-to- address
    Picking
    •     A transfer order is created for an outbound delivery
    •     A transfer order is created for a warehouse number
    Post Goods Issue
    When PGI is done the system
    •     Updates the quantity in inventory management and delivery requirements in materials planning
    •     Generates additional documents for accounting
    •     Adds the delivery to the billing due list
    •     Updates status in sales documents
    Billing
    We can group deliveries into single billing document if the deliveries have same
    •     Billing date
    •     Payer
    •     Destination Country
    The effects of billing are
    •     Debit on the customer receivables account and credit on sales revenue account is created
    •     Sales information system
    •     Sales statistics is updated
    Master data in SAP
    SAP SD has got the following main masters:
    •     Customer master
    •     Material master
    •     Condition master
    •     Output master
    •     Customer material information master
    Customer master
    General Data                                         Sales Area Data          Company Code data
    Tab pages                                              Tab pages                                      Tab pages
    Address     Order             Accounting
    Control data                                              Shipping               Payment
    Payment terms                                          Billing               Correspondence
    Marketing                                                   Partner functions                Insurance
    Unloading points
    Export data
    Contact persons
    The chart above shows detail on three main areas of customer master and the tab pages found under each area.
    Material Master is maintained in different views and important views of sales and distribution are
    •     Basic data 1
    •     Sales Org 1
    •     Sales Org 2
    •     Sales : Gen/Plant
    •     Foreign Trade
    •     Sales text
    Sales document in Sales and distribution mainly controls:
    •     Number range
    •     Item No increment
    •     Reference mandatory
    •     Item division
    •     Read info record
    •     Document pricing procedure
    •     Incomplete messages
    •     Alternative sales documents
    •     Delivery block
    •     Billing block
    •     Immediate delivery
    •     Delivery type
    •     Billing type
    •     Proposed delivery date
    •     Lead time for delivery
    •     Proposed pricing date
    Plant determination in Sales and distribution:
    To determine the plant in an order the system checks the master in the following order:
    a)     Customer material info. record of the sold-to –party
    b)     Customer master record of the ship-to-party
    c)     Material master record of the material
    Shipping point determination
    The following rule is used in determining shipping point in a sales order   :
    Plant + Shipping condition (Sold-to-Party) + Loading group                  Shipping point
                                                          Maintained in Material master Gen: Plant data
    Route determination
    Route determined using the following rule in Sales and Distribution (SAP)
    Departure Zone of Shipping Point
    +
    Shipping condition (Sold-to-Party)
    +
    Transportation Group (Material master)
    +
    Transportation Zone (Ship-to-Party)
    Route
    Delivery scheduling:
    As name denotes delivery scheduling is scheduling delivery for an order and it carries the following important dates:
    •     Material availability date
    •     Transportation planning date
    •     Loading date
    •     Goods Issue date
    •     Delivery date
    Availability Check in SAP:
    •     Availability check is carried out at item level for a plant
    •     Availability check is done on the material availability date
    •     If material availability date is in the past the forward scheduling is done, if not backward  scheduling is done.
    Item category determination in the order:
    Item category denotes the category to which the item belongs and the following rule is used for determination of item category. Item category controls the way in which item behaves in a sales document.
    Sales document type
    +
    Item category group (Material master)
    +
    Item usage
    +
    Item category of higher level item
    Item category of the item
    Item category in a sales document mainly controls the following
    •     Relevance for billing of an item
    •     Billing block
    •     Pricing relevance
    •     Business data relevance item
    •     Schedule line allowed
    •     Item relevant for delivery
    •     Returns
    •     Determine cost
    •     Credit active
    •     Incompletion procedure
    •     Partner determination procedure
    •     Structure scope (relevant for bill of material explosion)
    •     Value contract material
    •     Contract release control
    Schedule line category:
    Every item which has a delivery will have a schedule line and the schedule line category is determined with the following rule:
    Item category + MRP type(Material Master)         Schedule line category
    Schedule line category mainly controls:
    •     Delivery Block
    •     Movement type
    •     Item relevant for delivery
    •     Req/Assembly
    •     Availability
    •     Product Allocation
    Copy Control:
    Copy control is normally set for
    •     Header
    •     Item
    •     Schedule line  levels
    To control copying procedure we have
    •     Data transfer routines
    •     Copying requirements
    •     Switches
    Pricing Procedure determination:
    Pricing is an important component in SAP-SD. Once an order is entered taking into consideration some major factors, the pricing procedure for the particular order is determined.
    The major factors taken into consideration for pricing procedure determination is:
    Sales area
    +
    Customer Pricing procedure(Customer Master –Sales area data)
    +
    Document Pricing Procedure(Sales Document Type)
    Pricing Procedure
    What are the components of pricing procedure?
    How is  that a person should work on Pricing Procedure?
    To start with first
    Define a Condition table:
    What is a condition table?
    A table where the key fields are data combinations for which messages are triggered (and offered for processing).
    For each data combination, there is a condition record in the table. The data part contains the actual message.
    As mentioned above a condition table is a table which carries key fields for picking up the prices.
    Define Access Sequences
    The access sequence is a search strategy which the SAP System uses to search for condition records valid for a condition type.
    For example, you can define for a price that the SAP System first searches for a customer-specific price and then for a price list price.
    Recommendation
    •     If you define your own access sequences, the key should start with the letter Z since SAP reserves this letter for the standard system.
    •     Do not change access sequences contained in the standard SAP R/3 System.
    Actions
    1. Check to what extent you can use the access sequences contained in the standard SAP R/3 System.
    2. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key which may have up to 4 digits and a textual description.
    3. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. With the sequence, you define the priority of the accesses. You can display combinations of key fields using possible entries.
    4. Generating the accesses is no longer necessary as of 3.0, as this is carried out automatically. You can generate the accesses manually, if required, by choosing "Utilities".
    Example
    In pricing, you use a customer-material discount. The condition records you create are based on customer data from the document header and material data from each document item. The discount is only valid for 2% of your customers, however. Normally, this would mean that the system would needlessly search through every available item for 98% of your customers. In this case, pre step would improve system performance.
    Define Condition Type
    A characteristic of a condition. For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
    Price elements are represented in the SAP system by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.
    You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.
    You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.
    Note
    •     The pricing procedure groups all condition types together which the SAP system is to automatically take into account during pricing for a business transaction (see the section "Define and assign pricing procedures").
    Remember that you can only specify manually in a document those condition types which are contained in the pricing procedure.
    •     You can change the outcome of pricing in the sales document manually. You can limit options for changing a condition type in this IMG step.
    Recommendation
    •     If you define your own condition types, the key should start with the letter Z since SAP reserves these letters for that purpose in the standard system.
    •     Do not change the condition types which are contained in the standard SAP R/3 System.
    Actions
    1. Check to what extent you can use the condition types contained in the standard SAP R/3 System.
    2. Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is you may require a calculation rule for a discount which is not available in the standard system.
    Specify an alphanumeric key which can have up to 4 digits, and a textual description.
    Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
    3. Maintain the detail screen of the condition type.
    You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.
    In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.
    Define Pricing Procedures
    The pricing procedure defines the conditions permitted for a document and the sequence in which the system takes these conditions into account during pricing.
    A standard pricing procedure is defined in the standard SAP system.  It contains conditions most commonly used.  These include material prices, discounts, and surcharges, such as freight, or tax.
    SAP Recommendation
    •     Define your own pricing procedures which contain only those condition types which you use. Otherwise, the system makes un neccessary accesses to conditions.
    •     Do not change the pricing procedures contained in the standard SAP R/3 System.
    Actions
    1. Create new pricing procedures by copying a similar pricing procedure.
    o     Specify a key with up to 6 characters and a description.
    o     For a procedure, specify the condition types in the sequence of their usage.
    Maintain the lines of the pricing procedure
    2. Afterwards define the customer determination procedures for determining the procedure.
    3. Define the document pricing procedures for determining the procedure.
    4. Assign the procedure to the sales document types and billing types.
    5. To determine the procedure, define the allowed combinations of:
    o     Sales area
    o     Customer pricing  procedure
    o     Document pricing procedure
    o     Pricing procedure
    Shipping:
    The basis for shipping is delivery.
    Delivery document controls the following in deliveries
    •     Number range
    •     Item no increment
    •     Storage location rule
    •     Route determination
    •     Text determination
    •     Delivery split
    •     Gen. packing material / item
    •     Order required
    Delivery item category controls:
    •     Check min delivery
    •     Availability check
    •     Relevant for picking
    •     Storage location required
    •     Determine storage location
    •     Automatic batch determination
    •     Text determination procedure
    Billing:
    Billing is the last phase in the SD process .Billing is the phase where the major integration of SD and FI Module happens.
    Billing document has got the following structure:
    •     Header
    •     Item
    Billing documents mainly control:
    •     No. range
    •     Posting block (Controls posting to accounting)
    •     Relevant for rebate
    •     Account determination procedure
    •     Account determination recon account
    •     Account determination pay.cards
    •     Output determination procedure
    Account Determination in SAP
    Account determination in SAP-SD happens with the following rule
    Sales Organization
    Chart of Accounts
    Account assignment group –Customer
    Account assignment group-Material
    Account Key
    G/L account on which the postings  has to happen.
    CHeers!!!

  • Customer consignment materials - process flow

    Hi PP Guru's,
    pls explain customer consignment materials - process flow ?
    how to recd parts and transaction for consignment parts.
    customer ordered FG, but some of the components (items) customer consignment parts, other parts buying from other vendor.
    Regards,
    Sankaran

    One alternative would be:
    - Customer material (CM) are non valuated ones.
    - BoM contains both CM and normal raw materials (CS01)
    - Routing ot Recipes is the base for manufacturing costing (CA01 or C201).
    - Create a process order for the product (COR1)
    - Do the whole processing of the order (release, GI, GR, Confirmation, Settlement).
    -.Delivery the product to the customer (and eventually the remaining CM )
    The process is just like the normal, only there are some differences in costing, and the stock of CM has no value.

  • Use of Business Process Flow in BPC

    Hello Everybody,
    I am new to SAP BPC. I am able to create a New Business Process Flow in BPC.
    But Can any one tell me what are the actual Uses of Business Process Flow in BPC.
    Thanks a lot in Advance!
    Regards,
    Satish.

    Hi,
    BPF can be compared a little bit with 'guided procedures' in BI: you define a pre-defined process consisting of multiple steps which have to be executed by the user to come to the end result. You can choose to oblige the user to first finish step X before starting step Y. A step can be lots of things like input data, set a certain status, ... BPF are executed in BPC web. Disadvantage is that once you finished a step in a BPF, you cannot set it back (unless everything is initialized ...)
    Alternative could be a custom menu, in which you also make a list of activities, but the user is free to execute any step in any sequence
    regards
    Dries

  • How to stop OWB Process Flow job

    I have a problem.
    For scheduling OWB Process Flows I use EM (create Job - SQL Script) in which I schedule jobs with script @/home/oracle/scripts/oem_exec_template.sql.
    Sometimes it happens, that the job doesn't finish and I also can't expedite it through Workflow manager because it is not listed there. So next executions for this job doesn't fire, because it is still active (it is shown in EM as Running …..and also I can't stop it there).
    I also can't find the session for this job and also in dictionary I can't find the job, I went through these views, but nowhere I can't find any of my scheduled jobs, and of course also not the ones that are still running.
    DBA_SCHEDULER_JOBS
    DBA_SCHEDULER_RUNNING_JOBS
    DBA_SCHEDULER_JOB_RUN_DETAILS
    Where in dictionary can I find my jobs?
    How can I kill my running jobs?
    OS: Red Hat Linux 3
    DB: 10.1.0.3.0
    OWB: 10.1.0.2.0
    I'm quite desperate about this isue,
    Thank you,
    Gorazd

    Gorazd,
    the best way to identify problem with processflow execution - using OWB Runtime Audit Browser.
    Other variant - using public OWB runtime view, for example for reporting executions of you process run this select under OWB repository owner or any OWB user:
    select created_on,elapse_time,return_result from all_rt_audit_executions
    where object_name='<your processflow name in uppercase>' order by created_on;
    RETURN_RESULT must be equal 'OK' and ELAPSE_TIME (in seconds) greater then 0.
    If this query returns rows with null RETURN_RESULT or RETURN_RESULT<>'OK' or with zero elapse_time and this cases match (by date) with EM problems then you need analyze process executions in more detail with Runtime Audit Browser.
    Alternatively use select from view ALL_RT_AUDIT_EXEC_MESSAGES / ALL_RT_AUDIT_MAP_RUN_ERRORS / ALL_RT_AUDIT_PROC_RUN_ERRORS.
    Oleg

  • Is It Possible To Start a Process Flow on Receipt of an Email?

    Hi
    Does anyone know if you can trigger the start of a process flow once an email has been received?
    thanks ...

    alternatively what you can done is:
    If you are using unix/linux OS then:
    create an SMTP service on unix/linux
    have the email coming into unix/linux
    write a unix shell scrpt to read he mails on a regular basis
    if the email is existing create a "touch file" referred as flag file
    use the OWB to check if the flat file exists on unix as owb can communicate with unix/linux
    and then run the process flow which has the mappings
    If you are using Windows OS then:
    have a program which will extract the mail from your local mailbox onto a server, there are few softwares available in the market
    use the option of writing it into a table or follow the flag file approach stated above.

  • Locking source tables during process flow

    Hi All,
    I have a process flow which calls multiple mappings and stored procedures. I pull data from source located in different database and insert data into current database. Since, this migration is delta migration, I want to make sure that during migration, no user should add data into source till migration is successfully completed.
    I had called a procedure which locks individual tables, but as soon as next mapping is completed the lock gets released, since each mappings commits data. I want that the lock should be active till all mappings gets completed.
    Regards,
    Danish

    Commit will release all locks. Therefor, no matter how you lock the table, the lock will release when you commit the map. An alternative might be to capture a frozen image of the data into a local GTT created with the on commit preserve rows option.

  • URGENT:error while deploying a process flow

    EMP_COUNT is a mapping which i have deployed .
    when i try to deploy a process flow i get the following error:
    OMB05602: An unknown Deployment error has occured for Object Type API8028: No signature is available for mapping EMP_COUNT because the generation language is undefined. Please set the generation language property of this mapping, or generate this mapping to set the generation language property to a default value..
    thnx in advance

    OMB+> OMBALTER MAPPING 'EMP_COUNT' SET PROPERTIES (GENERATION_LANGUAGE) VALUES ('PLSQL')
    Fast enough? ;-)
    Regards,
    Detlef

  • Cannot deploy process flow package specification from file

    Hi,
    we are using owb 11gr2 on linux. We successfully managed to deploy mappings and tables into a specification file, and then deploy from that file into the target database (RAC). But when we try to deploy a process flow package we run into an error:
    A process flow package can be deployed to a specification file. But a deployment from that specification file fails with the error: " OMB05623: Cannot deploy specification from file. Exception follows. nulll"
    ### SETUP
    set CONN_DESIGN "xxx"
    set CONN_TARGET_DESIGN "yyy"
    set CONN_TARGET_RT "xxx'"
    set DIR "D:\\tmp"
    set RELEASE "V0_2"
    set file "$DIR\\$RELEASE"
    set plan "FILE_DEPLOY_$RELEASE"
    ### Deployment via control center: works!
    OMBCONNECT $CONN_DESIGN
    OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
    OMBCC '/KLINGEL_DWH'
    OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$plan'
    OMBALTER DEPLOYMENT_ACTION_PLAN '$plan' ADD ACTION 'PF_TEST' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE '/KLINGEL_DWH/WF_DWH/PF_TEST'
    OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$plan'
    OMBDISCONNECT CONTROL_CENTER
    OMBCOMMIT
    OMBDISCONNECT
    ### Deployment via specificatin file: fails!
    OMBCONNECT $CONN_DESIGN
    OMBCONNECT CONTROL_CENTER $CONN_DESIGN
    OMBCC '/KLINGEL_DWH'
    OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$plan'
    OMBALTER DEPLOYMENT_ACTION_PLAN '$plan' ADD ACTION 'PF_TEST' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE '/KLINGEL_DWH/WF_DWH/PF_TEST'
    OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$plan' AS SPECIFICATION TO '$file.xml'
    OMBDROP DEPLOYMENT_ACTION_PLAN '$plan'
    OMBDISCONNECT CONTROL_CENTER
    OMBCOMMIT
    OMBDISCONNECT
    OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
    OMBDEPLOY SPECIFICATION FROM '$file.xml'
    ### OMB05623: Deployment von Spezifikation aus Datei nicht möglich. Exception folgt. null
    ###OMB05623: Cannot deploy specification from file. Exception follows. nullIf we use the operation DROP it works. But REPLACE and CREATE do not work.
    We get the error regardless whether the code is executed as an expert or on the command line at a windows client.
    Does anyone knows a workaround?
    Deployment via a specification file is a must due to license and architecture requirements.
    Thanks,
    Carsten.

    Its woked fine for me for OWB 10.2.0.4 .... some steps are missing from code like
    when you are connecting again it should be
    OMBDISCONNECT
    OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
    OMBDISCONNECT
    OMBCC '/KLINGEL_DWH'
    OMBCONNECT CONTROL_CENTER $CONN_TARGET_RTI think you can try the same on different system .
    Cheers
    Nawneet

  • A/R process flow with notice of readiness for shipment

    Hi,
    I'm trying to implement the following A/R process flow:
    - sales order
    - xx% A/R down payment invoice
    - notice of readiness for shipment
    - incoming payment
    - delivery
    - A/R invoice (xx% down payment to be deducted here)
    What's the best way to implement it?
    Thanks
    Fabio

    Hi,
    no, it's something different. It is because we want to be paid before shipping anything.
    In more detail:
    - we request a certain amount of down payment after the order and before starting production
    - we request final payment before we deliver goods
    Thanks
    Fabio

Maybe you are looking for