Using Pre-Mapping Process

Hi,
Can you please let me know how to use the pre-defined WB_DISABLE_ALL_CONSTRAINTS(p_table) function.
Do we have any link of the demo.
I followed the users guide ,but could not replicate that.
Thanks
Vinay

The OWB Transformation Guide shows usage, purpose and example of each transformation. Here is the place for WB_DISABLE_ALL_CONSTRAINTS http://download-west.oracle.com/docs/html/B12151_01/sqltrans03.htm#sthref261
Nikolai Rochnik

Similar Messages

How to use pre-mapping process operator

Hi,
I am using OWB version 10.1.0.4.0.
There are two source tables namely src1_tb(id1,field1,field2), src2_tb(id2,field3,field4) and a target table namely target_tb(id1,id2,field1,field2,field3,field4).
It's a simple mapping with a join operator. Here, when I try to use a pre-mapping process operator 'LENGTH', with input from outgroup of join operator (field1) and output linked to an added field( VALUE_LENGTH) in Traget Table, it gives error "VLD-2451: Connection to premapping is invalid" and a warning "VLD-1008 :Referenced mapping column VALUE_LENGTH" does not exist"
Can anyone please let me know how to use pre-mapping process operator.
Any help will be greatly appreciated.
Regards,
Pawan

yes, a pre-mapping procedure is not what you want here.
Pre-mapping procedures run once when the mapping initializes and before the actual ETL is run. IT is a place where you could do some custom data cleansing / validation, populate your own audit loggin tables if you wish, or whatever other things you might like to do.
For what you are describing, you want to pass the field through an expression object. Drop the Expression on the canvas and drag a link from the field in your OUTGRP to the INGRP on the expression This will auto-create the corresponding ingrp attribute in the expression for that field. Then double-click the expression object to bring up it's properties sheet. You will then want to create an OUTGRP attribute called length_value of type number, and set it's Expression property to length(ingrp1.your_Field_name_here). You can then connect from this outgrp field to your field in the target table.
Cheers,
Mike

Problem using pre-mapping process operator in owb 9i

Hi,
I was trying to use the pre-mapping process operator in owb 9i. Problem is that the manual does not specify how the inputs need to be connected to this operator. Following is what I went through -
I created a mapping table operator and a mapping dimension operator and connected these two. Then i created a pre-mapping process operator selecting the LTRIM function. Further I connected one of the table attributes to this pre-mapping operator as input and connected the output of this pre-mapping operator to the appropriate dimension operator attribute. On performing Validate, following error message was flashed -
VLD-2451 : Illegal connection to pre-mapping process operator
I am trying to learn how to use OWB 9i from the manual. So my interpretation of the use of the pre-mapping process operator may be wrong.
In any case kindly help,
Thanks
Saju

Pre-mapping process is use to perform some operations preceding to mapping operation itself.
For example, if your mapping is designed to incrementally append data to table for the definite time interval (witch is a parameter of the map operation) you might want to perform the table data cleanup for that period. That will allow for reload data number of time.
In this case you have to define the procedure witch perform cleanup and than include the call to that procedure as a pre-mapping process.
Other examples of pre- and post mapping process is disabling referential integrity before loading and re-enabling them after loading.
Anyway, OWB documentation has clear definition for pre- and post-mapping processes.

Pre-Mapping Process Operator

We are not getting any documentation, how to use Pre-Mapping Process Operator(I went through the help documentation and tried to apply whatever is there).
I am using this operator for a function that returns single value. The output of this operator I want to load into the Expression input and expression operator output I want to load into the target table. The output from the Pre-mapping Operator is blank when I am seeing indebugging mode. I am not getting result in execution mode also. Its a simple function that returns number. The function is
FUNCTION Tesppt RETURN NUMBER IS
BEGIN
RETURN 100;
END;
I want to know how Pre-Mapping operator works . When I am using the function in expression it works fine.
I tried out simple mapping to load a table, it did not work out. The code generated is
CREATE OR REPLACE PACKAGE "TEREEES" AS
sql_stmt VARCHAR2(32767);
get_abort BOOLEAN := FALSE;
get_trigger_success BOOLEAN := TRUE;
get_errors NUMBER(22) := 0;
get_status NUMBER(22) := 0;
-- Status variable for Batch cursors
"TEST_PP_St" BOOLEAN;
"PREMAPPING_0_VALUE" NUMBER;
-- Function Main -- Entry point in package "TEREEES"
FUNCTION Main RETURN NUMBER;
END "TEREEES";
CREATE OR REPLACE PACKAGE BODY "TEREEES" AS
-- Function "TEST_PP_Bat"
-- performs batch extraction
-- Returns TRUE on success
-- Returns FALSE on failure
FUNCTION "TEST_PP_Bat" RETURN BOOLEAN IS
BEGIN
EXECUTE IMMEDIATE 'ALTER SESSION ENABLE PARALLEL DML';
BEGIN
INSERT
/*+ APPEND PARALLEL(TEST_PP, DEFAULT, DEFAULT) */
INTO
"TEST_PP"
("C1",
"C2")
(SELECT
"TEST_COUNTRY"."CODE" "CODE",
"PREMAPPING_0_VALUE" "VALUE"
FROM "TEST_COUNTRY" "TEST_COUNTRY"
COMMIT;
EXCEPTION WHEN OTHERS THEN
ROLLBACK;
COMMIT;
RETURN FALSE;
END;
COMMIT;
RETURN TRUE;
END "TEST_PP_Bat";
FUNCTION Main RETURN NUMBER IS
get_batch_status BOOLEAN := TRUE;
BEGIN
-- Pre-Model Triggers
BEGIN
"PREMAPPING_0_VALUE" :=TESPPT();
EXCEPTION WHEN OTHERS THEN
get_trigger_success := FALSE;
END;
-- Initialize all batch status variables
"TEST_PP_St" := FALSE;
IF get_trigger_success THEN
"TEST_PP_St" := "TEST_PP_Bat";
END IF;
RETURN get_status;
END Main;
END "TEREEES";
Thanks in advance.

We are having one table which will be populated from other source. It will have one value and we need to fetch that value and this value will be constant for the the whole mapping as there is only one record. So, this the reason why we wanted to do this process before the start of the mapping. The code that I have pasted is sample that I did as an trial for testing how pre mapping process operator works.
Actually we are using expression and in expression for every record, we don't want to call a function. We want to call function once only so thats the reason why we are using Pre-Mapping Process operator. I don't think that there is anything better than this but the function returns no value when we are using the Pre-Mapping process operator but when I use this function in the outgroup of the expression it returns the value.
I wanted to see how Pre-mapping operator works, so we tried out simple mapping with simple function but did not work there also. This simple mapping code is there in the query that I asked first.
Thanks in Advance

Problems with pre-mapping process operator in owb 9i

Hi,
I was trying to use the pre-mapping process operator in owb 9i. Problem is that the manual does not specify how the inputs need to be connected to this operator.
Following is what I went through -
I created a mapping table operator and a mapping dimension operator and connected these two. Then i created a pre-mapping process operator selecting the LTRIM function. Further I connected one of the table attributes to this pre-mapping operator as input and connected the output of this pre-mapping operator to the appropriate dimension operator attribute.
On performing Validate, following error message was flashed -
VLD-2451 : Illegal connection to pre-mapping process operator
I am trying to learn how to use OWB 9i from the manual. So my interpretation of the use of the pre-mapping process operator may be wrong.
In any case kindly help,
Thanks,
Saju

Pre-mapping process is use to perform some operations preceding to mapping operation itself.
For example, if your mapping is designed to incrementally append data to table for the definite time interval (witch is a parameter of the map operation) you might want to perform the table data cleanup for that period. That will allow for reload data number of time.
In this case you have to define the procedure witch perform cleanup and than include the call to that procedure as a pre-mapping process.
Other examples of pre- and post mapping process is disabling referential integrity before loading and re-enabling them after loading.
Anyway, OWB documentation has clear definition for pre- and post-mapping processes.

Problems with pre-mapping process in owb 9i

Hi,
I was trying to use the pre-mapping process operator in owb 9i. Problem is that the manual does not specify how the inputs need to be connected to this operator.
Following is what I went through -
I created a mapping table operator and a mapping dimension operator and connected these two. Then i created a pre-mapping process operator selecting the LTRIM function. Further I connected one of the table attributes to this pre-mapping operator as input and connected the output of this pre-mapping operator to the appropriate dimension operator attribute.
On performing Validate, following error message was flashed -
VLD-2451 : Illegal connection to pre-mapping process operator
I am trying to learn how to use OWB 9i from the manual. So my interpretation of the use of the pre-mapping process operator may be wrong.
In any case kindly help,
Thanks,
Saju

Hi,
Essentially the pre (and post) mapping processes are executed before and after the mapping logic. These are separate procedures in the generated package and are "stand alone" from the main package procedure holding the actual mapping diagram.
If you want to use LTRIM, there are 2 supported ways:
1) use an expression, this means you feed the column you want to do the expression on into the expression operator, open the code editor and select from the transformations (or type ltrim......) and then link the result to the target object
2) use a transformation operator, choose ltrim from the Oracle library and connect the operator as I stated in use case 1
We do not encourage you to use a filter to do transformations, it is better to use the operators that are intended for transformations.
Thanks,
Jean-Pierre

Adding pre-mapping process breaks target load order

OWB 11.2.0.2 on Oracle database 11.2.0.2
I created a mapping that has 4 sources (views on external tables) and 4 targets (3 regular tables).
V1 => T1 (truncate/insert)
V2 => T2 (truncate/insert)
V3 => T3 (truncate/insert)
V4 => T3 (update/insert)
The above is the target load order. It tested fine.
I added a pre-mapping process (packaged procedure) that is unrelated to any of these source/target tables, but just exits or raises a failure to control whether the mapping should continue to run or not.
When I run it, the selected/inserted/merged counts are identical, but from what I'm seeing in T3 is that the order was update/insert followed by truncate/insert. I verified that the target load order remained the same.
Has anyone else run into this problem?

Hi,
For OWB 11.2.0.2 the target load order property will set to 'False' by default.
If this is the case you can not guarantee that the targets will be loaded in the order specified. It should be set to 'true'
Right click on your map and select configure -> Code generation Properties -> Use target load ordering set it to true.
Please note that you should have ODI EE licence and you must have installed OWB with Enterprise opton to set this property.
Regards,
Pnreddy

Sequence initialize problem with pre-mapping process

Hi,
I use a pre-mapping process in a mapping which executes a function which :
a) drops a sequence
b) re-creates the dropped sequence ( CREATE SEQUENCE xxxx START WITH 1)
But OWB creates always the sequence beginning with 21 as value ?
If I executes the procedure in SQL manually then it works fine and starts the sequence with 1.
Is there an explanation for this action (bug ?) ?
Thanks in advvance,
Eric

Hi,
Its always better to create the sequence manually,import it into OWB and then use it.
Regards
Bharath

Truncate tables in pre-mapping process

I am using OWB 9.0.4 and I have 10 staging area tables that I will be loading in one mapping. I want to truncate all of these tables before I load them. I can not use the TRUNCATE/INSERT option on the target tables because each table will be loaded from two different source tables and I can't specify order in the mapping so I can't have one TRUNCATE/INSERT and the other just INSERT. I would prefer not to have two mappings. I have also tried doing a union on the two source tables but this was not working out well. If I use a pre-mapping operator and select the WB_TRUNCATE_TABLE function, how do I specify multiple tables?
Is there a better way to do this?

WB_TRUNCATE_TABLE function takes in only one parameter, so you would have to have 10 pre-mapping processes with that function, or a single one with a custom function.
I guess you figured the other two choices yourself:
- If your sources have the same number of attributes and matching datatypes - map them through a Set Operator in a single map with TRUNCATE/INSERT loading type
- If your sources are different, put them in different maps, with TRUNCATE/INSERT on one and INSERT on the other. Then you can control the order of map execution.
Nikolai

Pre-mapping process seems to be called after instead of before

Hi,
I'm new here and this is my first time posting, so please be gentle! :-)
Running OWB 10.2.0.1.0 on an oracle 10g target db and a 9i source db.
I have a mapping which contains a pre-mapping process and it contains a simple mapping from a source view into the target table.
When I look at the generated code, the pre mapping process is at the bottom, after the main insert part of the mapping.
Next, when I perform a test, updating a test record and following it through the logic, it seems that the pre-mapping process really is in fact getting called after the main mapping.
Has anyone experienced this?
Thanks,
Sammi

Resolved. Pre-mapping works fine and as intended. Problem in logic was elsewhere.

Pre-mapping process

Hi everybody,
Could somebody pls help me to figure out how to set a table name parameter in WB_TRUNCATE_TABLE operator in Mapping Editor?
Thanks, Alex

Hi Vibhuti, to enter a bound table name for this operator is exactly my problem. Operator WB_TRUNCATE_TABLE has one ingroup INGRP1 with one attribute P_TABLE. Unfortunately in property inspector Bound Name for this attribute has default value 'p_table' and is dimmed out - so I can't entre my table name. I also do not see a property 'table _name' in Property Inspector. Any suggestions?
Thanks, Alex

About Pre-Mapping

Here my problem:
I use Pre-Mapping which contains a function turning over a value. Until nothing very difficult...
Now, which I must try to make is to stop or not my mapping (RAISE) according to the value of return and to thus be able to use this function in various other mapping (which will stop according to another value of return of the function)... But it is where I block, I do not manage to find how, in OWB, I can make a "RAISE" of Mapping...
For the moment I use procedures which make the in-house RAISE, but in this case I must as many create procedures as of treated cases...
If somebody can inform me on this subject, or same can be to say to me that it is quite simply not possible in OWB..
It would be brilliant
Thank you, Sebastien

Hi Sebastien,
Which version of Warehouse Builder do you use? In the latest release (and I think this was introduced in 9.0.3) you can specify as a PREMAPPING property a Mapping Run Condition: ON SUCCES, ON ERROR, or ALWAYS. In that case, if you raise an error in the pre-mapping process, then you can influence whether or not the mapping runs.
Alternatively, in 9.0.4 or higher, you can define a process flow, use the transformation in the process flow, configure the transformation in the process flow to Use Return as Status to return 1, 2 or 3 to direct the process flow into SUCCESS, WARNING or ERROR respectively.
Hope this helps,
Mark.

How to design a mapping with a pre-mapping operator

Hi,
I want to design a mapping with only one operator: a pre-mapping operator that uses a procedure with no parameters (so there are no input/output groups). When I validate this mapping I get error VLD-1009: Mapping lines have not been created.
Question 1: how do I design a mapping if all I want to do is to execute a procedure and there are no target operators involved?
Question 2: how are pre-mapping process operators intended to be used? (apparently not the way I use one here)
Jaap.

One way of doing this is to jus add a constant and a target table to insert a value into a dummy target. (i.e sysdate into dummy_table) This way you can execute the procedure using a pre mapping operator.

Pre-mapping problem

Hello ,
I would like to delete some records before inserting new records to the target table. So I use the Pre-mapping process for this situation. I wrote a simple "Delete record" procedure in the "Public transformation/Customs/Procedures. But when I deploy the mapping , there is an error.
PLS-00201: identifier 'DELETE_RECORD' must be declared
My delete_record procedure is as follow
--initialize variables here
-- main body
BEGIN
NULL; -- allow compilation
delete from ora_tb5 where c1=1
EXCEPTION
WHEN OTHERS THEN
NULL; -- enter any exception code here
END;
Is there any problems in the above procedure code ? How to declare the procedure in OWB ? How can I deploy the mapping successfully ? Thanks !
Dan

Hi,
Sorry I did not realize that you were trying the Custom functions.
Deploying Custom Functions it is bit trivial. There are 2 ways to deploy them.
1. Using GUI - Copy and Paste the Function into the module where you have your mapping and then deply it into that location.
2. Using OMB+ -
OMBCONNECT < to design repo>
OMBCC '<your project>'
OMBCONN RUNTIME '<ur RT connection>' USE PASSWORD '<rt password>'
OMBCC '<ur project>/WB_CUSTOM_TRANS'
--list available functions / procs
OMBLIST FUNCTIONS
OMBLIST PROCEDURES
--create deployment action plan
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEP_PLAN'\
ADD ACTION 'DEP_FUNC' SET PROPERTIES (OPERATION) \
VALUES ('CREATE') SET REFERENCE FUNCTION '<your func/proc name>'
--Change back to the module where your mapping exists
OMBCC '/<ur project>/<your module>'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEP_PAN'
OMBCOMMIT
The above steps will deploy the function. Reconcile the pre-mapping. Deploy mapping. This should work.
Yes. I think you are right regarding the usage of DELETEs.
hope the above resolves your issues.
Thanks
mahesh

Post-mapping process error

I have built all of my process in v9.0.2.62.3 except for once the row is loaded into my staging table, I want to delete this row from the source. I was trying to use the post-mapping process to call a procedure that would perform the deletion. However, I can not get the post-mapping process to work.
The manual states to add a post-mapping process operator to a mapping:
Drop a Post-Mapping Process operator onto the Mapping Editor canvas.
Select the appropriate procedure from the selection list. This were I select a procedure called drop_ind with one input parameter, v_ind_id, of type number.
Connect the output attribute of a source operator to the INOUTGRP1 of the Post-Mapping Process operator.
This is where things start to go wrong with the manual. There is no INOUTGRP1, but only an INPUTS. If I try and attach the target column to the INPUTS, I get an API8009 cannot add attributes to POSTMAPPING INPUTS error. So I attach my target column directly to the input parameter
Rename the operator:
This goes well enough.
Then I try and validate, and I get the following message wehn I try to generate the mapping :
Code cannot be generated.
Specify another operating mode or see validation messages for details.
When I validate I get :VLD-2451 Illegal connection to POSTMAPPING. details = Illegal connection to POSTMAPPING.
Obviously, I am doing something wrong, but what?

Matthew,
First a question, what are you trying to add to the post mapping process? The ID of the single row that is processed?
In that case, you will have to rethink the strategy. What happens in a post map process (and the rest of the map) is the following:
1) execute any pre mapping processes
2) execute the main body of the mapping (this is you diagram excluding pre and post mapping processes)
3) execute the post mapping process
This means that the post mapping process will be run whenever the rest of the mapping is complete.
So to do what you want, you can use the post mapping process but you would add a marker to every inserted record and then in the post map procedure delete all the ones that have this marker in the target from the source.
In that case you would need any parameters from your map into the procedure and you should be all set.
Hope this helps,
Jean-Pierre

Using Pre-Mapping Process

Similar Messages

Maybe you are looking for