Synchronizing Updates on a Staging Table

Please help me out with the resolving the following issue:
A load script is running for moving records from a data file to a staging table.
After this script completes, there is a code to update two fields of the staging table.
To do this the shell script runs a script (generate_ranges.sql). It takes a parameter of 5000000. It creates ranges based on this passed in number upto the total number of rows in the staging table. So say the staging table has 65,000,000 rows.
This script will create a file that looks like the following (when 5000000 is passed in):
1 | 5000000
5000001 | 10000000
10000001 | 15000000
15000001 | 20000000
20000001 | 25000000
25000001 | 30000000
30000001 | 35000000
35000001 | 40000000
40000001 | 45000000
45000001 | 50000000
50000001 | 55000000
55000001 | 60000000
60000001 | 65000000
The script goes on to read the data file for each row and it calls a shell script and passes in each range. So in this case there are 13 ranges. What is happening is there are 13 seperate updates on the staging table happening in the background.
The first update rows 1 - 5000000, the second rows 5000001 - 10000000 etc.
So there are 13 updates happenng behind the scenes.
The problem is that there is no way for the script to know that all updates are completed successfully before proceeding automatically. Right now I manually check to see that that all updates completed and then I restart the script at the next step. However we want to code to ensure that all the updates are done automatically and then move on in the script. So we need a way to count the number of candidate updates ( right now 13 but could be 14 or more in future) and know that all "x" updates completed, it may be the case that update (1-5000000) is taking 30 mins and the next update ( 5000001 - 10000000) is taking 35 mins, all updates iare running parallely, and only when after the 13 parallel updates are complete, the script can proceed with subsequent steps.
So please help me out with fixing this problem programmatically.
Thanks for your cooperation in advance.
Regards,
Ayan.

Ayan,
Are you really sure you want to update 65 million rows ?
Alternative: create table as select <columns with 2 columns updated> from staging table;
While using this approach, you probably don't need to split the update.
Regards,
Rob.

Similar Messages

My requirement is to update 3 valuesets daily based on data coming to my staging table. What is the API used for this and how to map any API to our staging table? I am totally new to oracle and apps. Please help. Thanks!

My requirement is to update 3 valuesets daily based on data coming to my staging table. What is the API used for this and how to map any API to our staging table? I am totally new to oracle and apps. Please help. Thanks!

Hi,
You could use FND_FLEX_LOADER_APIS.UP_VALUE_SET_VALUE to upload them from staging table (I suppose you mean value set values...).
You can find a sample scripts if you google around.
What do you mean "how to map any API to our staging table" ?
You should do at least the following mapping (which column(s) in the staging table will provide these information):
- the 3 value sets name which you're going to update/upload (I suppose these are existing value sets or which have been already created)
- the value set values and description
Try to start with something and if there is any issues the community could then help... but for the time being with the description of the problem you have provided, that's the best I can do...

Staging table update?

Hi,
I have a scenario where i I am loading the data from table A to table B. A is a staging table and B is the target.
I need to load the data from A to B and update those records in A, which are successfully loaded onto B.
In other words, I might initially have 100 records in A..Run teh interface and load them to B and update a flag in A, saying those are done.
Again, I will pump in data (200 records) onto A ..Now the interface will pick only 200 records from A and push to B.
Please advice.

This is very simple. In you package use one ODI procedure to update the flag in table A. If you have got some records in E$ table then update the table A accordingly. The package structure should be like
ODI procedure to seth flag N where flag not equals to U-----ok--->Interface(A->B)--------ok--->Odi procedure to update the flag in table A where flag Equals to N
N= these records need to be loaded to target
U= already loaded/updated in target.
Keep in mind your table should be locked while doing above operation to avoid data loading to table A from other interfaces. otherwise there will be inconsistency.
Thanks.

Unable to load data from FDMEE staging table to HFM tables

Hi,
We have installed EPM 11.1.2.3 with all latest related products (ODI/FDMEE) in our development environment
We are inprocess of loading data from EBS R12 to HFM using ERPI (Data Managemwnt in EPM 11.1.2.3). We could Import and validate the data but when we try to Export the data to HFM, the process continuously running hours (neither it gives any error nor it completes).
When we check the process details in ODI work repository, following processes are completed successfully
COMM_LOAD_BALANCES - Running .........(From past 1 day, still running)
EBS_GL_LOAD_BALANCES_DATA - Successful
COMM_LOAD_BALANCES - Successful
Whereas we could load data in staging table of FDMEE database schema and moreover we are even able to drill through to source system (EBS R12) from Data load workbench but not able to load the data into HFM application.
Log details from the process are below.
2013-11-05 17:04:59,747 INFO [AIF]: FDMEE Process Start, Process ID: 31
2013-11-05 17:04:59,747 INFO [AIF]: FDMEE Logging Level: 4
2013-11-05 17:04:59,748 INFO [AIF]: FDMEE Log File: C:\FDMEE\outbox\logs\OASIS_31.log
2013-11-05 17:04:59,748 INFO [AIF]: User:admin
2013-11-05 17:04:59,748 INFO [AIF]: Location:VisionLoc (Partitionkey:1)
2013-11-05 17:04:59,749 INFO [AIF]: Period Name:JAN (Period Key:1/1/12 12:00 AM)
2013-11-05 17:04:59,749 INFO [AIF]: Category Name:VisionCat (Category key:3)
2013-11-05 17:04:59,749 INFO [AIF]: Rule Name:VisionRule (Rule ID:2)
2013-11-05 17:05:00,844 INFO [AIF]: Jython Version: 2.5.1 (Release_2_5_1:6813, Sep 26 2009, 13:47:54)
[Oracle JRockit(R) (Oracle Corporation)]
2013-11-05 17:05:00,844 INFO [AIF]: Java Platform: java1.6.0_37
2013-11-05 17:05:02,910 INFO [AIF]: -------START IMPORT STEP-------
2013-11-05 17:05:02,953 INFO [AIF]: -------END IMPORT STEP-------
2013-11-05 17:05:03,030 INFO [AIF]: -------START EXPORT STEP-------
2013-11-05 17:05:03,108 INFO [AIF]:
Move Data for Period 'JAN'
Any help on above is much appreciated.
Thank you
Regards
Praneeth

Hi,
I have followed the steps 1 & 2 above. Noe the log shows something like below
2013-11-05 09:47:31,179 INFO [AIF]: FDMEE Process Start, Process ID: 22
2013-11-05 09:47:31,179 INFO [AIF]: FDMEE Logging Level: 4
2013-11-05 09:47:31,179 INFO [AIF]: FDMEE Log File: C:\FDMEE\outbox\logs\OASIS_22.log
2013-11-05 09:47:31,180 INFO [AIF]: User:admin
2013-11-05 09:47:31,180 INFO [AIF]: Location:VisionLoc (Partitionkey:1)
2013-11-05 09:47:31,180 INFO [AIF]: Period Name:JAN (Period Key:1/1/12 12:00 AM)
2013-11-05 09:47:31,180 INFO [AIF]: Category Name:VisionCat (Category key:3)
2013-11-05 09:47:31,181 INFO [AIF]: Rule Name:VisionRule (Rule ID:2)
2013-11-05 09:47:32,378 INFO [AIF]: Jython Version: 2.5.1 (Release_2_5_1:6813, Sep 26 2009, 13:47:54)
[Oracle JRockit(R) (Oracle Corporation)]
2013-11-05 09:47:32,378 INFO [AIF]: Java Platform: java1.6.0_37
2013-11-05 09:47:34,652 INFO [AIF]: -------START IMPORT STEP-------
2013-11-05 09:47:34,698 INFO [AIF]: -------END IMPORT STEP-------
2013-11-05 09:47:34,744 INFO [AIF]: -------START EXPORT STEP-------
2013-11-05 09:47:34,828 INFO [AIF]:
Move Data for Period 'JAN'
2013-11-08 11:49:10,478 INFO [AIF]: FDMEE Process Start, Process ID: 22
2013-11-08 11:49:10,493 INFO [AIF]: FDMEE Logging Level: 5
2013-11-08 11:49:10,493 INFO [AIF]: FDMEE Log File: C:\FDMEE\outbox\logs\OASIS_22.log
2013-11-08 11:49:10,494 INFO [AIF]: User:admin
2013-11-08 11:49:10,494 INFO [AIF]: Location:VISIONLOC (Partitionkey:1)
2013-11-08 11:49:10,494 INFO [AIF]: Period Name:JAN (Period Key:1/1/12 12:00 AM)
2013-11-08 11:49:10,495 INFO [AIF]: Category Name:VISIONCAT (Category key:1)
2013-11-08 11:49:10,495 INFO [AIF]: Rule Name:VISIONRULE (Rule ID:1)
2013-11-08 11:49:11,903 INFO [AIF]: Jython Version: 2.5.1 (Release_2_5_1:6813, Sep 26 2009, 13:47:54)
[Oracle JRockit(R) (Oracle Corporation)]
2013-11-08 11:49:11,909 INFO [AIF]: Java Platform: java1.6.0_37
2013-11-08 11:49:14,037 INFO [AIF]: -------START IMPORT STEP-------
2013-11-08 11:49:14,105 INFO [AIF]: -------END IMPORT STEP-------
2013-11-08 11:49:14,152 INFO [AIF]: -------START EXPORT STEP-------
2013-11-08 11:49:14,178 DEBUG [AIF]: CommData.exportData - START
2013-11-08 11:49:14,183 DEBUG [AIF]: CommData.getRuleInfo - START
2013-11-08 11:49:14,188 DEBUG [AIF]:
        SELECT brl.RULE_ID
        ,br.RULE_NAME
        ,brl.PARTITIONKEY
        ,brl.CATKEY
        ,part.PARTVALGROUP
        ,br.SOURCE_SYSTEM_ID
        ,ss.SOURCE_SYSTEM_TYPE
        ,CASE
          WHEN ss.SOURCE_SYSTEM_TYPE LIKE 'EBS%' THEN 'N'
          WHEN ss.SOURCE_SYSTEM_TYPE LIKE 'PS%' THEN 'N'
          WHEN ss.SOURCE_SYSTEM_TYPE LIKE 'FUSION%' THEN 'N'
          WHEN ss.SOURCE_SYSTEM_TYPE LIKE 'FILE%' THEN 'N'
          ELSE 'Y'
        END SOURCE_ADAPTER_FLAG
        ,app.APPLICATION_ID
        ,app.TARGET_APPLICATION_NAME
        ,app.TARGET_APPLICATION_TYPE
        ,app.DATA_LOAD_METHOD
        ,brl.PLAN_TYPE
        ,CASE brl.PLAN_TYPE
          WHEN 'PLAN1' THEN 1
          WHEN 'PLAN2' THEN 2
          WHEN 'PLAN3' THEN 3
          WHEN 'PLAN4' THEN 4
          WHEN 'PLAN5' THEN 5
          ELSE 0
        END PLAN_NUMBER
        ,br.INCL_ZERO_BALANCE_FLAG
        ,br.PERIOD_MAPPING_TYPE
        ,br.INCLUDE_ADJ_PERIODS_FLAG
        ,br.BALANCE_TYPE ACTUAL_FLAG
        ,br.AMOUNT_TYPE
        ,br.BALANCE_SELECTION
        ,br.BALANCE_METHOD_CODE
        ,COALESCE(br.SIGNAGE_METHOD, 'ABSOLUTE') SIGNAGE_METHOD
        ,br.CURRENCY_CODE
        ,br.BAL_SEG_VALUE_OPTION_CODE
        ,brl.EXECUTION_MODE
        ,COALESCE(brl.IMPORT_FROM_SOURCE_FLAG, 'Y') IMPORT_FROM_SOURCE_FLAG
        ,COALESCE(brl.RECALCULATE_FLAG, 'N') RECALCULATE_FLAG
        ,COALESCE(brl.EXPORT_TO_TARGET_FLAG, 'N') EXPORT_TO_TARGET_FLAG
        ,CASE
          WHEN (br.LEDGER_GROUP_ID IS NOT NULL) THEN 'MULTI'
          WHEN (br.SOURCE_LEDGER_ID IS NOT NULL) THEN 'SINGLE'
          ELSE 'NONE'
        END LEDGER_GROUP_CODE
        ,COALESCE(br.BALANCE_AMOUNT_BS, 'YTD') BALANCE_AMOUNT_BS
        ,COALESCE(br.BALANCE_AMOUNT_IS, 'PERIODIC') BALANCE_AMOUNT_IS
        ,br.LEDGER_GROUP
        ,(SELECT brd.DETAIL_CODE
          FROM AIF_BAL_RULE_DETAILS brd
          WHERE brd.RULE_ID = br.RULE_ID
          AND brd.DETAIL_TYPE = 'LEDGER'
        ) PS_LEDGER
        ,CASE lg.LEDGER_TEMPLATE
          WHEN 'COMMITMENT' THEN 'Y'
          ELSE 'N'
        END KK_FLAG
        ,p.LAST_UPDATED_BY
        ,p.AIF_WEB_SERVICE_URL WEB_SERVICE_URL
        ,p.EPM_ORACLE_INSTANCE
        FROM AIF_PROCESSES p
        INNER JOIN AIF_BAL_RULE_LOADS brl
          ON brl.LOADID = p.PROCESS_ID
        INNER JOIN AIF_BALANCE_RULES br
          ON br.RULE_ID = brl.RULE_ID
        INNER JOIN AIF_SOURCE_SYSTEMS ss
          ON ss.SOURCE_SYSTEM_ID = br.SOURCE_SYSTEM_ID
        INNER JOIN AIF_TARGET_APPLICATIONS app
          ON app.APPLICATION_ID = brl.APPLICATION_ID
        INNER JOIN TPOVPARTITION part
          ON part.PARTITIONKEY = br.PARTITIONKEY
        INNER JOIN TBHVIMPGROUP imp
          ON imp.IMPGROUPKEY = part.PARTIMPGROUP
        LEFT OUTER JOIN AIF_COA_LEDGERS l
          ON l.SOURCE_SYSTEM_ID = p.SOURCE_SYSTEM_ID
          AND l.SOURCE_LEDGER_ID = COALESCE(br.SOURCE_LEDGER_ID,imp.IMPSOURCELEDGERID)
        LEFT OUTER JOIN AIF_PS_SET_CNTRL_REC_STG scr
          ON scr.SOURCE_SYSTEM_ID = l.SOURCE_SYSTEM_ID
          AND scr.SETCNTRLVALUE = l.SOURCE_LEDGER_NAME
          AND scr.RECNAME = 'LED_GRP_TBL'
        LEFT OUTER JOIN AIF_PS_LED_GRP_TBL_STG lg
          ON lg.SOURCE_SYSTEM_ID = scr.SOURCE_SYSTEM_ID
          AND lg.SETID = scr.SETID
          AND lg.LEDGER_GROUP = br.LEDGER_GROUP
        WHERE p.PROCESS_ID = 22
2013-11-08 11:49:14,195 DEBUG [AIF]:
      SELECT adim.BALANCE_COLUMN_NAME DIMNAME
      ,adim.DIMENSION_ID
      ,dim.TARGET_DIMENSION_CLASS_NAME
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID1
      ) COA_SEGMENT_NAME1
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID2
      ) COA_SEGMENT_NAME2
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID3
      ) COA_SEGMENT_NAME3
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID4
      ) COA_SEGMENT_NAME4
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID5
      ) COA_SEGMENT_NAME5
      ,(SELECT CASE mdd.ORPHAN_OPTION_CODE
          WHEN 'CHILD' THEN 'N'
          WHEN 'ROOT' THEN 'N'
          ELSE 'Y'
        END DIMENSION_FILTER_FLAG
        FROM AIF_MAP_DIM_DETAILS_V mdd
        ,AIF_MAPPING_RULES mr
        WHERE mr.PARTITIONKEY = tpp.PARTITIONKEY
        AND mdd.RULE_ID = mr.RULE_ID
        AND mdd.DIMENSION_ID = adim.DIMENSION_ID
      ) DIMENSION_FILTER_FLAG
      ,tiie.IMPCONCATCHAR
      FROM TPOVPARTITION tpp
      INNER JOIN AIF_TARGET_APPL_DIMENSIONS adim
        ON adim.APPLICATION_ID = 2
      INNER JOIN AIF_DIMENSIONS dim
        ON dim.DIMENSION_ID = adim.DIMENSION_ID
      LEFT OUTER JOIN TBHVIMPITEMERPI tiie
        ON tiie.IMPGROUPKEY = tpp.PARTIMPGROUP
        AND tiie.IMPFLDFIELDNAME = adim.BALANCE_COLUMN_NAME
        AND tiie.IMPMAPTYPE = 'ERP'
      WHERE tpp.PARTITIONKEY = 1
      AND adim.BALANCE_COLUMN_NAME IS NOT NULL
      ORDER BY adim.BALANCE_COLUMN_NAME
2013-11-08 11:49:14,197 DEBUG [AIF]: {'APPLICATION_ID': 2L, 'IMPORT_FROM_SOURCE_FLAG': u'N', 'PLAN_TYPE': None, 'RULE_NAME': u'VISIONRULE', 'ACTUAL_FLAG': u'A', 'IS_INCREMENTAL_LOAD': False, 'EPM_ORACLE_INSTANCE': u'C:\\Oracle\\Middleware\\user_projects\\epmsystem1', 'CATKEY': 1L, 'BAL_SEG_VALUE_OPTION_CODE': u'ALL', 'INCLUDE_ADJ_PERIODS_FLAG': u'N', 'PERIOD_MAPPING_TYPE': u'EXPLICIT', 'SOURCE_SYSTEM_TYPE': u'EBS_R12', 'LEDGER_GROUP': None, 'TARGET_APPLICATION_NAME': u'OASIS', 'RECALCULATE_FLAG': u'N', 'SOURCE_SYSTEM_ID': 2L, 'TEMP_DATA_TABLE_NAME': 'TDATASEG_T', 'KK_FLAG': u'N', 'AMOUNT_TYPE': u'MONETARY', 'EXPORT_TO_TARGET_FLAG': u'Y', 'DATA_TABLE_NAME': 'TDATASEG', 'DIMNAME_LIST': [u'ACCOUNT', u'ENTITY', u'ICP', u'UD1', u'UD2', u'UD3', u'UD4'], 'TDATAMAPTYPE': 'ERP', 'LAST_UPDATED_BY': u'admin', 'DIMNAME_MAP': {u'UD3': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Generic', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT5', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'UD3', 'DIMENSION_ID': 9L}, u'ICP': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'ICP', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT7', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'ICP', 'DIMENSION_ID': 8L}, u'ENTITY': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Entity', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT1', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'ENTITY', 'DIMENSION_ID': 12L}, u'UD2': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Generic', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT4', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'UD2', 'DIMENSION_ID': 11L}, u'UD4': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Generic', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT6', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'UD4', 'DIMENSION_ID': 1L}, u'ACCOUNT': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Account', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT3', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'ACCOUNT', 'DIMENSION_ID': 10L}, u'UD1': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Generic', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT2', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'UD1', 'DIMENSION_ID': 7L}}, 'TARGET_APPLICATION_TYPE': u'HFM', 'PARTITIONKEY': 1L, 'PARTVALGROUP': u'[NONE]', 'LEDGER_GROUP_CODE': u'SINGLE', 'INCLUDE_ZERO_BALANCE_FLAG': u'N', 'EXECUTION_MODE': u'SNAPSHOT', 'PLAN_NUMBER': 0L, 'PS_LEDGER': None, 'BALANCE_SELECTION': u'FUNCTIONAL', 'BALANCE_AMOUNT_IS': u'PERIODIC', 'RULE_ID': 1L, 'BALANCE_AMOUNT_BS': u'YTD', 'CURRENCY_CODE': None, 'SOURCE_ADAPTER_FLAG': u'N', 'BALANCE_METHOD_CODE': u'STANDARD', 'SIGNAGE_METHOD': u'SAME', 'WEB_SERVICE_URL': u'http://localhost:9000/aif', 'DATA_LOAD_METHOD': u'CLASSIC_VIA_EPMI'}
2013-11-08 11:49:14,197 DEBUG [AIF]: CommData.getRuleInfo - END
2013-11-08 11:49:14,224 DEBUG [AIF]: CommData.insertPeriods - START
2013-11-08 11:49:14,228 DEBUG [AIF]: CommData.getLedgerListAndMap - START
2013-11-08 11:49:14,229 DEBUG [AIF]: CommData.getLedgerSQL - START
2013-11-08 11:49:14,229 DEBUG [AIF]: CommData.getLedgerSQL - END
2013-11-08 11:49:14,229 DEBUG [AIF]:
          SELECT l.SOURCE_LEDGER_ID
          ,l.SOURCE_LEDGER_NAME
          ,l.SOURCE_COA_ID
          ,l.CALENDAR_ID
          ,'0' SETID
          ,l.PERIOD_TYPE
          ,NULL LEDGER_TABLE_NAME
          FROM AIF_BALANCE_RULES br
          ,AIF_COA_LEDGERS l
          WHERE br.RULE_ID = 1
          AND l.SOURCE_SYSTEM_ID = br.SOURCE_SYSTEM_ID
          AND l.SOURCE_LEDGER_ID = br.SOURCE_LEDGER_ID
2013-11-08 11:49:14,230 DEBUG [AIF]: CommData.getLedgerListAndMap - END
2013-11-08 11:49:14,232 DEBUG [AIF]:
        INSERT INTO AIF_PROCESS_PERIODS (
          PROCESS_ID
          ,PERIODKEY
          ,PERIOD_ID
          ,ADJUSTMENT_PERIOD_FLAG
          ,GL_PERIOD_YEAR
          ,GL_PERIOD_NUM
          ,GL_PERIOD_NAME
          ,GL_PERIOD_CODE
          ,GL_EFFECTIVE_PERIOD_NUM
          ,YEARTARGET
          ,PERIODTARGET
          ,IMP_ENTITY_TYPE
          ,IMP_ENTITY_ID
          ,IMP_ENTITY_NAME
          ,TRANS_ENTITY_TYPE
          ,TRANS_ENTITY_ID
          ,TRANS_ENTITY_NAME
          ,PRIOR_PERIOD_FLAG
          ,SOURCE_LEDGER_ID
                SELECT DISTINCT brl.LOADID PROCESS_ID
                ,pp.PERIODKEY PERIODKEY
                ,prd.PERIOD_ID
                ,COALESCE(prd.ADJUSTMENT_PERIOD_FLAG, 'N') ADJUSTMENT_PERIOD_FLAG
                ,COALESCE(prd.YEAR, ppsrc.GL_PERIOD_YEAR,0) GL_PERIOD_YEAR
                ,COALESCE(prd.PERIOD_NUM, ppsrc.GL_PERIOD_NUM,0) GL_PERIOD_NUM
                ,COALESCE(prd.PERIOD_NAME, ppsrc.GL_PERIOD_NAME,'0') GL_PERIOD_NAME
                ,COALESCE(prd.PERIOD_CODE, CAST(COALESCE(prd.PERIOD_NUM, ppsrc.GL_PERIOD_NUM,0) AS VARCHAR(38)),'0') GL_PERIOD_CODE
                ,(COALESCE(prd.YEAR, ppsrc.GL_PERIOD_YEAR,0) * 10000 + COALESCE(prd.PERIOD_NUM, ppsrc.GL_PERIOD_NUM,0)) GL_EFFECTIVE_PERIOD_NUM
                ,COALESCE(ppa.YEARTARGET, pp.YEARTARGET) YEARTARGET
                ,COALESCE(ppa.PERIODTARGET, pp.PERIODTARGET) PERIODTARGET
                ,'PROCESS_BAL_IMP' IMP_ENTITY_TYPE
                ,(COALESCE(prd.YEAR, ppsrc.GL_PERIOD_YEAR,0) * 10000 + COALESCE(prd.PERIOD_NUM, ppsrc.GL_PERIOD_NUM,0)) IMP_ENTITY_ID
                ,COALESCE(prd.PERIOD_NAME, ppsrc.GL_PERIOD_NAME,'0') IMP_ENTITY_NAME
                ,'PROCESS_BAL_TRANS' TRANS_ENTITY_TYPE
                ,(COALESCE(prd.YEAR, ppsrc.GL_PERIOD_YEAR,0) * 10000 + COALESCE(prd.PERIOD_NUM, ppsrc.GL_PERIOD_NUM,0)) TRANS_ENTITY_ID
                ,pp.PERIODDESC TRANS_ENTITY_NAME
                ,'N' PRIOR_PERIOD_FLAG
                ,2202 SOURCE_LEDGER_ID
                FROM (
                  AIF_BAL_RULE_LOADS brl
                  INNER JOIN TPOVCATEGORY pc
                    ON pc.CATKEY = brl.CATKEY
                  INNER JOIN TPOVPERIOD_FLAT_V pp
                    ON pp.PERIODFREQ = pc.CATFREQ
                    AND pp.PERIODKEY >= brl.START_PERIODKEY
                    AND pp.PERIODKEY <= brl.END_PERIODKEY
                  LEFT OUTER JOIN TPOVPERIODADAPTOR_FLAT_V ppa
                    ON ppa.PERIODKEY = pp.PERIODKEY
                    AND ppa.PERIODFREQ = pp.PERIODFREQ
                    AND ppa.INTSYSTEMKEY = 'OASIS'
                INNER JOIN TPOVPERIODSOURCE ppsrc
                  ON ppsrc.PERIODKEY = pp.PERIODKEY
                  AND ppsrc.MAPPING_TYPE = 'EXPLICIT'
                  AND ppsrc.SOURCE_SYSTEM_ID = 2
                  AND ppsrc.CALENDAR_ID IN ('29067')
                LEFT OUTER JOIN AIF_GL_PERIODS_STG prd
                  ON prd.PERIOD_ID = ppsrc.PERIOD_ID
                  AND prd.SOURCE_SYSTEM_ID = ppsrc.SOURCE_SYSTEM_ID
                  AND prd.CALENDAR_ID = ppsrc.CALENDAR_ID
          AND prd.SETID = '0'
          AND prd.PERIOD_TYPE = '507'
                  AND prd.ADJUSTMENT_PERIOD_FLAG = 'N'
                WHERE brl.LOADID = 22
                ORDER BY pp.PERIODKEY
                ,GL_EFFECTIVE_PERIOD_NUM
2013-11-08 11:49:14,235 DEBUG [AIF]: CommData.insertPeriods - END
2013-11-08 11:49:14,240 DEBUG [AIF]: CommData.moveData - START
2013-11-08 11:49:14,242 DEBUG [AIF]: CommData.getPovList - START
2013-11-08 11:49:14,242 DEBUG [AIF]:
        SELECT PARTITIONKEY
        ,PARTNAME
        ,CATKEY
        ,CATNAME
        ,PERIODKEY
        ,COALESCE(PERIODDESC, TO_CHAR(PERIODKEY,'YYYY-MM-DD HH24:MI:SS')) PERIODDESC
        ,RULE_ID
        ,RULE_NAME
        FROM (
          SELECT DISTINCT brl.PARTITIONKEY
          ,part.PARTNAME
          ,brl.CATKEY
          ,cat.CATNAME
          ,pprd.PERIODKEY
          ,pp.PERIODDESC
          ,brl.RULE_ID
          ,br.RULE_NAME
          FROM AIF_BAL_RULE_LOADS brl
          INNER JOIN AIF_BALANCE_RULES br
            ON br.RULE_ID = brl.RULE_ID
          INNER JOIN TPOVPARTITION part
            ON part.PARTITIONKEY = brl.PARTITIONKEY
          INNER JOIN TPOVCATEGORY cat
            ON cat.CATKEY = brl.CATKEY
          INNER JOIN AIF_PROCESS_PERIODS pprd
            ON pprd.PROCESS_ID = brl.LOADID
          LEFT OUTER JOIN TPOVPERIOD pp
            ON pp.PERIODKEY = pprd.PERIODKEY
          WHERE brl.LOADID = 22
        ) q
        ORDER BY PARTITIONKEY
        ,CATKEY
        ,PERIODKEY
        ,RULE_ID
2013-11-08 11:49:14,244 DEBUG [AIF]: CommData.getPovList - END
2013-11-08 11:49:14,245 INFO [AIF]:
Move Data for Period 'JAN'
2013-11-08 11:49:14,246 DEBUG [AIF]:
          UPDATE TDATASEG
          SET LOADID = 22
          WHERE PARTITIONKEY = 1
          AND CATKEY = 1
          AND RULE_ID = 1
          AND LOADID < 22
            AND PERIODKEY = '2012-01-01'
2013-11-08 11:49:14,320 DEBUG [AIF]: Number of Rows updated on TDATASEG: 1842
2013-11-08 11:49:14,320 DEBUG [AIF]:
        INSERT INTO AIF_APPL_LOAD_AUDIT (
          LOADID
          ,TARGET_APPLICATION_TYPE
          ,TARGET_APPLICATION_NAME
          ,PLAN_TYPE
          ,SOURCE_LEDGER_ID
          ,EPM_YEAR
          ,EPM_PERIOD
          ,SNAPSHOT_FLAG
          ,SEGMENT_FILTER_FLAG
          ,PARTITIONKEY
          ,CATKEY
          ,RULE_ID
          ,PERIODKEY
          ,EXPORT_TO_TARGET_FLAG
        SELECT DISTINCT 22
        ,TARGET_APPLICATION_TYPE
        ,TARGET_APPLICATION_NAME
        ,PLAN_TYPE
        ,SOURCE_LEDGER_ID
        ,EPM_YEAR
        ,EPM_PERIOD
        ,SNAPSHOT_FLAG
        ,SEGMENT_FILTER_FLAG
        ,PARTITIONKEY
        ,CATKEY
        ,RULE_ID
        ,PERIODKEY
        ,'N'
        FROM AIF_APPL_LOAD_AUDIT
        WHERE PARTITIONKEY = 1
        AND CATKEY = 1
        AND RULE_ID = 1
        AND LOADID < 22
            AND PERIODKEY = '2012-01-01'
2013-11-08 11:49:14,321 DEBUG [AIF]: Number of Rows inserted into AIF_APPL_LOAD_AUDIT: 1
2013-11-08 11:49:14,322 DEBUG [AIF]:
        INSERT INTO AIF_APPL_LOAD_PRD_AUDIT (
          LOADID
          ,GL_PERIOD_ID
          ,GL_PERIOD_YEAR
          ,DELTA_RUN_ID
          ,PARTITIONKEY
          ,CATKEY
          ,RULE_ID
          ,PERIODKEY
        SELECT DISTINCT 22
        ,GL_PERIOD_ID
        ,GL_PERIOD_YEAR
        ,DELTA_RUN_ID
        ,PARTITIONKEY
        ,CATKEY
        ,RULE_ID
        ,PERIODKEY
        FROM AIF_APPL_LOAD_PRD_AUDIT
        WHERE PARTITIONKEY = 1
        AND CATKEY = 1
        AND RULE_ID = 1
        AND LOADID < 22
            AND PERIODKEY = '2012-01-01'
2013-11-08 11:49:14,323 DEBUG [AIF]: Number of Rows inserted into AIF_APPL_LOAD_PRD_AUDIT: 1
2013-11-08 11:49:14,325 DEBUG [AIF]: CommData.moveData - END
2013-11-08 11:49:14,332 DEBUG [AIF]: CommData.updateWorkflow - START
2013-11-08 11:49:14,332 DEBUG [AIF]:
    SELECT tlp.PROCESSSTATUS
    ,tlps.PROCESSSTATUSDESC
    ,CASE WHEN (tlp.INTLOCKSTATE = 60) THEN 'Y' ELSE 'N' END LOCK_FLAG
    FROM TLOGPROCESS tlp
    ,TLOGPROCESSSTATES tlps
    WHERE tlp.PARTITIONKEY = 1
    AND tlp.CATKEY = 1
    AND tlp.PERIODKEY = '2012-01-01'
    AND tlp.RULE_ID = 1
    AND tlps.PROCESSSTATUSKEY = tlp.PROCESSSTATUS
2013-11-08 11:49:14,336 DEBUG [AIF]:
        UPDATE TLOGPROCESS
        SET PROCESSENDTIME = CURRENT_TIMESTAMP
        ,PROCESSSTATUS = 20
          ,PROCESSEXP = 0
          ,PROCESSENTLOAD = 0
          ,PROCESSENTVAL = 0
          ,PROCESSEXPNOTE = NULL
          ,PROCESSENTLOADNOTE = NULL
          ,PROCESSENTVALNOTE = NULL
        WHERE PARTITIONKEY = 1
        AND CATKEY = 1
        AND PERIODKEY = '2012-01-01'
        AND RULE_ID = 1
2013-11-08 11:49:14,338 DEBUG [AIF]: CommData.updateWorkflow - END
2013-11-08 11:49:14,339 DEBUG [AIF]: CommData.purgeInvalidRecordsTDATASEG - START
2013-11-08 11:49:14,341 DEBUG [AIF]:
        DELETE FROM TDATASEG
        WHERE LOADID = 22
          AND (
        PARTITIONKEY = 1
        AND CATKEY = 1
        AND PERIODKEY = '2012-01-01'
        AND RULE_ID = 1
        AND VALID_FLAG = 'N'
2013-11-08 11:49:14,342 DEBUG [AIF]: Number of Rows deleted from TDATASEG: 0
2013-11-08 11:49:14,342 DEBUG [AIF]: CommData.purgeInvalidRecordsTDATASEG - END
2013-11-08 11:49:14,344 DEBUG [AIF]: CommData.updateAppLoadAudit - START
2013-11-08 11:49:14,344 DEBUG [AIF]:
        UPDATE AIF_APPL_LOAD_AUDIT
        SET EXPORT_TO_TARGET_FLAG = 'Y'
        WHERE LOADID = 22
        AND PARTITIONKEY = 1
        AND CATKEY = 1
        AND PERIODKEY= '2012-01-01'
        AND RULE_ID = 1
2013-11-08 11:49:14,345 DEBUG [AIF]: Number of Rows updated on AIF_APPL_LOAD_AUDIT: 1
2013-11-08 11:49:14,345 DEBUG [AIF]: CommData.updateAppLoadAudit - END
2013-11-08 11:49:14,345 DEBUG [AIF]: CommData.updateWorkflow - START
2013-11-08 11:49:14,346 DEBUG [AIF]:
        UPDATE TLOGPROCESS
        SET PROCESSENDTIME = CURRENT_TIMESTAMP
        ,PROCESSSTATUS = 21
          ,PROCESSEXP = 1
          ,PROCESSEXPNOTE = 'Export Successful'
        WHERE PARTITIONKEY = 1
        AND CATKEY = 1
        AND PERIODKEY = '2012-01-01'
        AND RULE_ID = 1
2013-11-08 11:49:14,347 DEBUG [AIF]: CommData.updateWorkflow - END
2013-11-08 11:49:14,347 DEBUG [AIF]: CommData.exportData - END
2013-11-08 11:49:14,404 DEBUG [AIF]: HfmData.loadData - START
2013-11-08 11:49:14,404 DEBUG [AIF]: CommData.getRuleInfo - START
2013-11-08 11:49:14,404 DEBUG [AIF]:
        SELECT brl.RULE_ID
        ,br.RULE_NAME
        ,brl.PARTITIONKEY
        ,brl.CATKEY
        ,part.PARTVALGROUP
        ,br.SOURCE_SYSTEM_ID
        ,ss.SOURCE_SYSTEM_TYPE
        ,CASE
          WHEN ss.SOURCE_SYSTEM_TYPE LIKE 'EBS%' THEN 'N'
          WHEN ss.SOURCE_SYSTEM_TYPE LIKE 'PS%' THEN 'N'
          WHEN ss.SOURCE_SYSTEM_TYPE LIKE 'FUSION%' THEN 'N'
          WHEN ss.SOURCE_SYSTEM_TYPE LIKE 'FILE%' THEN 'N'
          ELSE 'Y'
        END SOURCE_ADAPTER_FLAG
        ,app.APPLICATION_ID
        ,app.TARGET_APPLICATION_NAME
        ,app.TARGET_APPLICATION_TYPE
        ,app.DATA_LOAD_METHOD
        ,brl.PLAN_TYPE
        ,CASE brl.PLAN_TYPE
          WHEN 'PLAN1' THEN 1
          WHEN 'PLAN2' THEN 2
          WHEN 'PLAN3' THEN 3
          WHEN 'PLAN4' THEN 4
          WHEN 'PLAN5' THEN 5
          ELSE 0
        END PLAN_NUMBER
        ,br.INCL_ZERO_BALANCE_FLAG
        ,br.PERIOD_MAPPING_TYPE
        ,br.INCLUDE_ADJ_PERIODS_FLAG
        ,br.BALANCE_TYPE ACTUAL_FLAG
        ,br.AMOUNT_TYPE
        ,br.BALANCE_SELECTION
        ,br.BALANCE_METHOD_CODE
        ,COALESCE(br.SIGNAGE_METHOD, 'ABSOLUTE') SIGNAGE_METHOD
        ,br.CURRENCY_CODE
        ,br.BAL_SEG_VALUE_OPTION_CODE
        ,brl.EXECUTION_MODE
        ,COALESCE(brl.IMPORT_FROM_SOURCE_FLAG, 'Y') IMPORT_FROM_SOURCE_FLAG
        ,COALESCE(brl.RECALCULATE_FLAG, 'N') RECALCULATE_FLAG
        ,COALESCE(brl.EXPORT_TO_TARGET_FLAG, 'N') EXPORT_TO_TARGET_FLAG
        ,CASE
          WHEN (br.LEDGER_GROUP_ID IS NOT NULL) THEN 'MULTI'
          WHEN (br.SOURCE_LEDGER_ID IS NOT NULL) THEN 'SINGLE'
          ELSE 'NONE'
        END LEDGER_GROUP_CODE
        ,COALESCE(br.BALANCE_AMOUNT_BS, 'YTD') BALANCE_AMOUNT_BS
        ,COALESCE(br.BALANCE_AMOUNT_IS, 'PERIODIC') BALANCE_AMOUNT_IS
        ,br.LEDGER_GROUP
        ,(SELECT brd.DETAIL_CODE
          FROM AIF_BAL_RULE_DETAILS brd
          WHERE brd.RULE_ID = br.RULE_ID
          AND brd.DETAIL_TYPE = 'LEDGER'
        ) PS_LEDGER
        ,CASE lg.LEDGER_TEMPLATE
          WHEN 'COMMITMENT' THEN 'Y'
          ELSE 'N'
        END KK_FLAG
        ,p.LAST_UPDATED_BY
        ,p.AIF_WEB_SERVICE_URL WEB_SERVICE_URL
        ,p.EPM_ORACLE_INSTANCE
        FROM AIF_PROCESSES p
        INNER JOIN AIF_BAL_RULE_LOADS brl
          ON brl.LOADID = p.PROCESS_ID
        INNER JOIN AIF_BALANCE_RULES br
          ON br.RULE_ID = brl.RULE_ID
        INNER JOIN AIF_SOURCE_SYSTEMS ss
          ON ss.SOURCE_SYSTEM_ID = br.SOURCE_SYSTEM_ID
        INNER JOIN AIF_TARGET_APPLICATIONS app
          ON app.APPLICATION_ID = brl.APPLICATION_ID
        INNER JOIN TPOVPARTITION part
          ON part.PARTITIONKEY = br.PARTITIONKEY
        INNER JOIN TBHVIMPGROUP imp
          ON imp.IMPGROUPKEY = part.PARTIMPGROUP
        LEFT OUTER JOIN AIF_COA_LEDGERS l
          ON l.SOURCE_SYSTEM_ID = p.SOURCE_SYSTEM_ID
          AND l.SOURCE_LEDGER_ID = COALESCE(br.SOURCE_LEDGER_ID,imp.IMPSOURCELEDGERID)
        LEFT OUTER JOIN AIF_PS_SET_CNTRL_REC_STG scr
          ON scr.SOURCE_SYSTEM_ID = l.SOURCE_SYSTEM_ID
          AND scr.SETCNTRLVALUE = l.SOURCE_LEDGER_NAME
          AND scr.RECNAME = 'LED_GRP_TBL'
        LEFT OUTER JOIN AIF_PS_LED_GRP_TBL_STG lg
          ON lg.SOURCE_SYSTEM_ID = scr.SOURCE_SYSTEM_ID
          AND lg.SETID = scr.SETID
          AND lg.LEDGER_GROUP = br.LEDGER_GROUP
        WHERE p.PROCESS_ID = 22
2013-11-08 11:49:14,406 DEBUG [AIF]:
      SELECT adim.BALANCE_COLUMN_NAME DIMNAME
      ,adim.DIMENSION_ID
      ,dim.TARGET_DIMENSION_CLASS_NAME
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID1
      ) COA_SEGMENT_NAME1
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID2
      ) COA_SEGMENT_NAME2
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID3
      ) COA_SEGMENT_NAME3
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID4
      ) COA_SEGMENT_NAME4
      ,(SELECT COA_SEGMENT_NAME
        FROM AIF_COA_SEGMENTS cs
        WHERE cs.COA_LINE_ID = tiie.IMPSOURCECOALINEID5
      ) COA_SEGMENT_NAME5
      ,(SELECT CASE mdd.ORPHAN_OPTION_CODE
          WHEN 'CHILD' THEN 'N'
          WHEN 'ROOT' THEN 'N'
          ELSE 'Y'
        END DIMENSION_FILTER_FLAG
        FROM AIF_MAP_DIM_DETAILS_V mdd
        ,AIF_MAPPING_RULES mr
        WHERE mr.PARTITIONKEY = tpp.PARTITIONKEY
        AND mdd.RULE_ID = mr.RULE_ID
        AND mdd.DIMENSION_ID = adim.DIMENSION_ID
      ) DIMENSION_FILTER_FLAG
      ,tiie.IMPCONCATCHAR
      FROM TPOVPARTITION tpp
      INNER JOIN AIF_TARGET_APPL_DIMENSIONS adim
        ON adim.APPLICATION_ID = 2
      INNER JOIN AIF_DIMENSIONS dim
        ON dim.DIMENSION_ID = adim.DIMENSION_ID
      LEFT OUTER JOIN TBHVIMPITEMERPI tiie
        ON tiie.IMPGROUPKEY = tpp.PARTIMPGROUP
        AND tiie.IMPFLDFIELDNAME = adim.BALANCE_COLUMN_NAME
        AND tiie.IMPMAPTYPE = 'ERP'
      WHERE tpp.PARTITIONKEY = 1
      AND adim.BALANCE_COLUMN_NAME IS NOT NULL
      ORDER BY adim.BALANCE_COLUMN_NAME
2013-11-08 11:49:14,407 DEBUG [AIF]: {'APPLICATION_ID': 2L, 'IMPORT_FROM_SOURCE_FLAG': u'N', 'PLAN_TYPE': None, 'RULE_NAME': u'VISIONRULE', 'ACTUAL_FLAG': u'A', 'IS_INCREMENTAL_LOAD': False, 'EPM_ORACLE_INSTANCE': u'C:\\Oracle\\Middleware\\user_projects\\epmsystem1', 'CATKEY': 1L, 'BAL_SEG_VALUE_OPTION_CODE': u'ALL', 'INCLUDE_ADJ_PERIODS_FLAG': u'N', 'PERIOD_MAPPING_TYPE': u'EXPLICIT', 'SOURCE_SYSTEM_TYPE': u'EBS_R12', 'LEDGER_GROUP': None, 'TARGET_APPLICATION_NAME': u'OASIS', 'RECALCULATE_FLAG': u'N', 'SOURCE_SYSTEM_ID': 2L, 'TEMP_DATA_TABLE_NAME': 'TDATASEG_T', 'KK_FLAG': u'N', 'AMOUNT_TYPE': u'MONETARY', 'EXPORT_TO_TARGET_FLAG': u'Y', 'DATA_TABLE_NAME': 'TDATASEG', 'DIMNAME_LIST': [u'ACCOUNT', u'ENTITY', u'ICP', u'UD1', u'UD2', u'UD3', u'UD4'], 'TDATAMAPTYPE': 'ERP', 'LAST_UPDATED_BY': u'admin', 'DIMNAME_MAP': {u'UD3': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Generic', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT5', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'UD3', 'DIMENSION_ID': 9L}, u'ICP': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'ICP', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT7', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'ICP', 'DIMENSION_ID': 8L}, u'ENTITY': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Entity', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT1', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'ENTITY', 'DIMENSION_ID': 12L}, u'UD2': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Generic', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT4', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'UD2', 'DIMENSION_ID': 11L}, u'UD4': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Generic', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT6', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'UD4', 'DIMENSION_ID': 1L}, u'ACCOUNT': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Account', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT3', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'ACCOUNT', 'DIMENSION_ID': 10L}, u'UD1': {'IMPCONCATCHAR': None, 'TARGET_DIMENSION_CLASS_NAME': u'Generic', 'COA_SEGMENT_NAME5': None, 'COA_SEGMENT_NAME1': u'SEGMENT2', 'COA_SEGMENT_NAME2': None, 'COA_SEGMENT_NAME3': None, 'DIMENSION_FILTER_FLAG': None, 'COA_SEGMENT_NAME4': None, 'DIMNAME': u'UD1', 'DIMENSION_ID': 7L}}, 'TARGET_APPLICATION_TYPE': u'HFM', 'PARTITIONKEY': 1L, 'PARTVALGROUP': u'[NONE]', 'LEDGER_GROUP_CODE': u'SINGLE', 'INCLUDE_ZERO_BALANCE_FLAG': u'N', 'EXECUTION_MODE': u'SNAPSHOT', 'PLAN_NUMBER': 0L, 'PS_LEDGER': None, 'BALANCE_SELECTION': u'FUNCTIONAL', 'BALANCE_AMOUNT_IS': u'PERIODIC', 'RULE_ID': 1L, 'BALANCE_AMOUNT_BS': u'YTD', 'CURRENCY_CODE': None, 'SOURCE_ADAPTER_FLAG': u'N', 'BALANCE_METHOD_CODE': u'STANDARD', 'SIGNAGE_METHOD': u'SAME', 'WEB_SERVICE_URL': u'http://localhost:9000/aif', 'DATA_LOAD_METHOD': u'CLASSIC_VIA_EPMI'}
2013-11-08 11:49:14,407 DEBUG [AIF]: CommData.getRuleInfo - END
2013-11-08 11:49:14,407 DEBUG [AIF]: CommData.getPovList - START
2013-11-08 11:49:14,407 DEBUG [AIF]:
        SELECT PARTITIONKEY
        ,PARTNAME
        ,CATKEY
        ,CATNAME
        ,PERIODKEY
        ,COALESCE(PERIODDESC, TO_CHAR(PERIODKEY,'YYYY-MM-DD HH24:MI:SS')) PERIODDESC
        ,RULE_ID
        ,RULE_NAME
        FROM (
          SELECT DISTINCT brl.PARTITIONKEY
          ,part.PARTNAME
          ,brl.CATKEY
          ,cat.CATNAME
          ,pprd.PERIODKEY
          ,pp.PERIODDESC
          ,brl.RULE_ID
          ,br.RULE_NAME
          FROM AIF_BAL_RULE_LOADS brl
          INNER JOIN AIF_BALANCE_RULES br
            ON br.RULE_ID = brl.RULE_ID
          INNER JOIN TPOVPARTITION part
            ON part.PARTITIONKEY = brl.PARTITIONKEY
          INNER JOIN TPOVCATEGORY cat
            ON cat.CATKEY = brl.CATKEY
          INNER JOIN AIF_PROCESS_PERIODS pprd
            ON pprd.PROCESS_ID = brl.LOADID
          LEFT OUTER JOIN TPOVPERIOD pp
            ON pp.PERIODKEY = pprd.PERIODKEY
          WHERE brl.LOADID = 22
        ) q
        ORDER BY PARTITIONKEY
        ,CATKEY
        ,PERIODKEY
        ,RULE_ID
2013-11-08 11:49:14,409 DEBUG [AIF]: CommData.getPovList - END
2013-11-08 11:49:14,409 DEBUG [AIF]: CommData.updateWorkflow - START
2013-11-08 11:49:14,409 DEBUG [AIF]:
    SELECT tlp.PROCESSSTATUS
    ,tlps.PROCESSSTATUSDESC
    ,CASE WHEN (tlp.INTLOCKSTATE = 60) THEN 'Y' ELSE 'N' END LOCK_FLAG
    FROM TLOGPROCESS tlp
    ,TLOGPROCESSSTATES tlps
    WHERE tlp.PARTITIONKEY = 1
    AND tlp.CATKEY = 1
    AND tlp.PERIODKEY = '2012-01-01'
    AND tlp.RULE_ID = 1
    AND tlps.PROCESSSTATUSKEY = tlp.PROCESSSTATUS
2013-11-08 11:49:14,410 DEBUG [AIF]:
        UPDATE TLOGPROCESS
        SET PROCESSENDTIME = CURRENT_TIMESTAMP
        ,PROCESSSTATUS = 30
          ,PROCESSENTLOAD = 0
          ,PROCESSENTVAL = 0
          ,PROCESSENTLOADNOTE = NULL
          ,PROCESSENTVALNOTE = NULL
        WHERE PARTITIONKEY = 1
        AND CATKEY = 1
        AND PERIODKEY = '2012-01-01'
        AND RULE_ID = 1
2013-11-08 11:49:14,411 DEBUG [AIF]: CommData.updateWorkflow - END
2013-11-08 11:49:14,412 DEBUG [AIF]:
    SELECT COALESCE(usr.PROFILE_OPTION_VALUE, app.PROFILE_OPTION_VALUE, site.PROFILE_OPTION_VALUE) PROFILE_OPTION_VALUE
    FROM AIF_PROFILE_OPTIONS po
    LEFT OUTER JOIN AIF_PROFILE_OPTION_VALUES site
      ON site.PROFILE_OPTION_NAME = po.PROFILE_OPTION_NAME
      AND site.LEVEL_ID = 1000
      AND site.LEVEL_VALUE = 0
      AND site.LEVEL_ID <= po.MAX_LEVEL_ID
    LEFT OUTER JOIN AIF_PROFILE_OPTION_VALUES app
      ON app.PROFILE_OPTION_NAME = site.PROFILE_OPTION_NAME
      AND app.LEVEL_ID = 1005
      AND app.LEVEL_VALUE = NULL
      AND app.LEVEL_ID <= po.MAX_LEVEL_ID
    LEFT OUTER JOIN AIF_PROFILE_OPTION_VALUES usr
      ON usr.PROFILE_OPTION_NAME = usr.PROFILE_OPTION_NAME
      AND usr.LEVEL_ID = 1010
      AND usr.LEVEL_VALUE = NULL
      AND usr.LEVEL_ID <= po.MAX_LEVEL_ID
    WHERE po.PROFILE_OPTION_NAME = 'JAVA_HOME'
2013-11-08 11:49:14,413 DEBUG [AIF]: HFM Load command:
%EPM_ORACLE_HOME%/products/FinancialDataQuality/bin/HFM_LOAD.vbs "22" "a9E3uvSJNhkFhEQTmuUFFUElfdQgKJKHrb1EsjRsL6yZJlXsOFcVPbGWHhpOQzl9zvHoo3s%2Bdq6R4yJhp0GMNWIKMTcizp3%2F8HASkA7rVufXDWEpAKAK%2BvcFmj4zLTI3rtrKHlVEYrOLMY453J2lXk6Cy771mNSD8X114CqaWSdUKGbKTRGNpgE3BfRGlEd1wZ3cra4ee0jUbT2aTaiqSN26oVe6dyxM3zolc%2BOPkjiDNk1MqwNr43tT3JsZz4qEQGF9d39DRN3CDjUuZRPt4SEKSSL35upncRJiw2uBOtV%2FvSuGLNpZ2J79v1%2Ba1Oo9c4Xhig7SFYbE6Jwk1yXRJLTSw0DKFu%2FEpcdjpOnx%2F6YawMBNIa5iu5L637S91jT1Xd3EGmxZFq%2Bi6bHdCJAC8g%3D%3D" "C%3A%5COracle%5CMiddleware%5Cuser_projects%5Cepmsystem1" "%25EPM_ORACLE_HOME%25%2F..%2Fjdk160_35"
Is there anywhere we need to set EPM Home and also let me know what is PSU1 ?
Thanks in advance.
Praneeth

How to move data from a staging table to three entity tables #2

Environment: SQL Server 2008 R2
I have a few questions:
How would I prevent duplicate records, when/ IF SSIS is executed many times?
How would I know that all huge volume of data being loaded in the entity tables?
In reference to "how to move data from a staging table to three entity tables ", since I am loading large volume of data, while using lookup transformation:
which of the merge components is best suited.
How to configure merge component correctly. (screen shot is preferred)
Please refer to the following link
http://social.msdn.microsoft.com/Forums/en-US/5f2128c8-3ddd-4455-9076-05fa1902a62a/how-to-move-data-from-a-staging-table-to-three-entity-tables?forum=sqlintegrationservices

You can use RowCount transformation in the path where you want to capture record details. Then inside rowcount transformation pass a integer variable to get count value inside
the event handler can be configured as below
Inside Execute SQL task add INSERT statement to add rowcount to your audit table
Can you also show me how to Check against destination table using key columns inside a lookup task and insert only non
matched records (No Match output)
This is explained clearly in below link which Arthur posted
http://www.sqlis.com/sqlis/post/Get-all-from-Table-A-that-isnt-in-Table-B.aspx
For large data I would prefer doing this in T-SQL. So what you could do is dump data to staging table and then apply
T-SQL MERGE between tables (or even a combination of INSERT/UPDATE statements)
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Injecting data into a star schema from a flat staging table

I'm trying to work out a best approach for getting data from a very flat staging table and then loading it into a star schema - I take a row from a table with for example 50 different attributes about a person and then load these into a host of different tables, including linking tables.
One of the attibutes in the staging table will be an instruction to either insert the person and their new data, or update a person and some component of their data or maybe even to terminate a persons records.
I plan to use PL/SQL but I'm not sure on the best approach.
The staging table data will be loaded every 10 minutes and will contain about 300 updates.
I'm not sure if I should just select the staging records into a cursor then insert into the various tables?
Has anyone got any working examples based on a similar experience?
I can provide a working example if required.

The database has some elements that make SQL a tad harder to use?
For example:
CREATE TABLE staging
(person_id NUMBER(10) NOT NULL ,
title VARCHAR2(15) NULL ,
initials VARCHAR2(5) NULL ,
forename VARCHAR2(30) NULL ,
middle_name VARCHAR2(30) NULL ,
surname VARCHAR2(50) NULL,
dial_number VARCHAR2(30) NULL,
Is_Contactable CHAR(1) NULL);
INSERT INTO staging
(person_id, title, initials, forename, middle_name, surname, dial_number)
VALUES ('12345', 'Mr', 'NULL', 'Joe', NULL, 'Bloggs', '0117512345','Y')
CREATE TABLE person
(person_id NUMBER(10) NOT NULL ,
title VARCHAR2(15) NULL ,
initials VARCHAR2(5) NULL ,
forename VARCHAR2(30) NULL ,
middle_name VARCHAR2(30) NULL ,
surname VARCHAR2(50) NULL);
CREATE UNIQUE INDEX XPKPerson ON Person
(Person_ID ASC);
ALTER TABLE Person
ADD CONSTRAINT XPKPerson PRIMARY KEY (Person_ID);
CREATE TABLE person_comm
(person_id NUMBER(10) NOT NULL ,
comm_type_id NUMBER(10) NOT NULL ,
comm_id NUMBER(10) NOT NULL );
CREATE UNIQUE INDEX XPKPerson_Comm ON Person_Comm
(Person_ID ASC,Comm_Type_ID ASC,Comm_ID ASC);
ALTER TABLE Person_Comm
ADD CONSTRAINT XPKPerson_Comm PRIMARY KEY (Person_ID,Comm_Type_ID,Comm_ID);
CREATE TABLE person_comm_preference
(person_id NUMBER(10) NOT NULL ,
comm_type_id NUMBER(10) NOT NULL
Is_Contactable CHAR(1) NULL);
CREATE UNIQUE INDEX XPKPerson_Comm_Preference ON Person_Comm_Preference
(Person_ID ASC,Comm_Type_ID ASC);
ALTER TABLE Person_Comm_Preference
ADD CONSTRAINT XPKPerson_Comm_Preference PRIMARY KEY (Person_ID,Comm_Type_ID);
CREATE TABLE comm_type
comm_type_id NUMBER(10) NOT NULL ,
NAME VARCHAR2(25) NULL ,
description VARCHAR2(100) NULL ,
comm_table_name VARCHAR2(50) NULL);
CREATE UNIQUE INDEX XPKComm_Type ON Comm_Type
(Comm_Type_ID ASC);
ALTER TABLE Comm_Type
ADD CONSTRAINT XPKComm_Type PRIMARY KEY (Comm_Type_ID);
insert into comm_type (comm_type_id, NAME, description, comm_table_name) values ('23456','HOME PHONE','Home Phone Number','PHONE');
CREATE TABLE phone
(phone_id NUMBER(10) NOT NULL ,
dial_number VARCHAR2(30) NULL);
Take the record from Staging then update:
'person'
'Person_Comm_Preference' Based on a comm_type of 'HOME_PHONE'
'person_comm' Derived from 'Person' and 'Person_Comm_Preference'
Then update 'Phone' with the number based on a link derived from 'Phone' which is made up of Person_Comm Primary_Key where 'Comm_ID' (part of that composite key)
relates to the Phone table Primary_Key which is Phone_ID.
Does you head hurt as much as mine?

How to improve the updating a sql server table with another table in Oracle

Hi there.
I am trying to do the next updating in SSIS
UPDATE S
SET
S.COLUMN_A = OT.COLUMN_A,
S.COLUMN_B = OT.COLUMN_B
FROM
SQLT1 S INNER JOIN ORACLET1 OT ON
S. COLUMN_C = OT.COLUMN_C
This is what I am doing:
I am taking the Oracle data with the ODBC Source like this.
Select column_A, column_B, column_C
from OracleT1
The thing is, the Oracle table has millions of registers and this updating is taking a lot. But I am not sure if it is maybe because of the design of the update query.
I wonder is if there is another way to design this query or improve the performance of this task.
Thanks a lot.

Yes
Use a OLEDB destination instead and save the records to a staging table
Then use a subsequent Execute sql task and do the set based update in it as below
UPDATE t
SET COLUMN_A = s.COLUMN_A,
COLUMN_B = s.COLUMN_B
FROM SQLT1 t
INNER JOIN stagingTable s
ON s.COLUMN_C = t.COLUMN_C
This would be much faster as its set based
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

SQL Bulk Update using Update query in SQL Table

Hello All,
I want to update data in sql table depends on some condition.
I am getting excel sheet from client and want to change value of field say Status = c.
Client is sending excel sheet with 300 field and want to change value for all 300 records with unique fields (field1 and field2) comming in that excel sheet...
How can i write and update records as Bulk.
Instaed updating one one recors ?
Example ( Update Table_Name Set Status = 'c' Where Field1 = Value from Excel for Field1 and
Field2 = Value from Excel for Field2 )
Same needs to do for 300 records...
Any help will wellcome.
Thanks,
Nilesh....
Thanks and Regards, Nilesh Thakur.

you can use OPENROWSET for that
http://www.mssqltips.com/sqlservertip/1540/insert-update-or-delete-data-in-sql-server-from-excel/
Another way is to use SSIS with data flow task having Excel source connecting to excel and using OLEDB command to update rows in table using it. You may also use staging table to get data from excel and later use it inexecute sql task to update your table
to make update set based which would be faster.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

How does it work for synchronous update via distributed scheme?

How does the synchronous update work between the primary JVM and backup JVM via the distributed cache threads?
Once a primary distributed worker thread updates the cache, the update needs to be synchronized to the backup.
Does the primary distributed worker thread continue to start sending the update to the backup? Or it's the primary distributed service thread to start sending the update to the backup?
On the backup side, is it the backup distributed service thread updating the backup cache? Or the backup distributed service thread delegate to a backup distributed worker thread to update the backup cache?
There are some concerns about if it's the distributed service thread participating the synchronization which might cause bottleneck given it is single thread.
Thanks in advance.

When you do a SELECT ... FOR UPDATE, Oracle locks each row that is returned by the SELECT. The mechanics of locking in Oracle is that the lock bit is actually stored in the row, rather than being centralized in the v$lock table. This allows Oracle to be very scalable and prevents you from worrying about things like lock escalation, but it makes it hard for individual DBA's and developer's to know what rows are locked.
Justin

How to create staging Tables with synonyms

Hi All,
I have a package which runs and updates a table weekly.
My question is,the web service is hitting on this table(TABLE CC) all the time.When my script runs it will be at least 20 minutes.Hence there would be a gap and the web service is unable to hit anything on the table as the previous data will be deleted and loaded with new data.
I have heard of staging tables and synonyms but I hope someone could share how do I start about it.
1)Rename CCto CC_1;
2)Create synonym CC for CC_1;
3)Run the scripts to load the data into a new table called CC_2;
4)Drop the synonym CC
5)Create synonym CC for CC_2;
6)check in select * from all_synonyms to see whether the synonyms are pointing to which table.
What about my scripts that would update the table CC.Do I need to change it to CC1 or CC2 all the time??Or can it be done dynamically.Stuck and don't knwo where to start.
Tha!

Why exactly do you need to do all this and what type(s) of DML are done on the table? In other words, WHY do all the rows need to be deleted and why does the table need to be loaded with completely new rows?
"What-cha driving at dude?"
Is it possible to just insert, delete or update rows in place based on whatever new information you've loaded into a staging table? Because, if you have say 100,000 rows, and you need to delete 20,000, update 5,000 and insert 15,000, you could just do it all live even if it takes 20 minutes--and I think that could likely be improved upon with bulk collections and bulk binding in you're PL/SQL.
OTOH, if your table contains last weeks data and you need to load this weeks data, I'd suggest partitioning by range (1 week at a time). Then you can merely load the new week's data and afterwards drop the prior week's data partition. If you do all the inserts on a single commit, no user will ever notice the difference until they see this week's data instead of last week's.
HTH

How to Compare Data length of staging table with base table definition

Hi,
I've two tables :staging table and base table.
I'm getting data from flatfiles into staging table, as per requirement structure of staging table and base table(length of each and every column in staging table is 25% more to dump data without any errors) are different for ex :if we've city column with varchar length 40 in staging table it has 25 in base table.Once data is dumped into staging table I want to compare actual data length of each and every column in staging table with definition of base table(data_length for each and every column from all_tab_columns) and if any column differs length I need to update the corresponding row in staging table which also has a flag called err_length.
so for this I'm using cursor c1 is select length(a.id),length(a.name)... from staging_table;
cursor c2(name varchar2) is select data_length from all_tab_columns where table_name='BASE_TABLE' and column_name=name;
But we're getting data atonce in first query whereas in second cursor I need to get each and every column and then compare with first ?
Can anyone tell me how to get desired results?
Thanks,
Mahender.

This is a shot in the dark but, take a look at this example below:
SQL> DROP TABLE STAGING;
Table dropped.
SQL> DROP TABLE BASE;
Table dropped.
SQL> CREATE TABLE STAGING
2 (
3          ID              NUMBER
4 ,       A               VARCHAR2(40)
5 ,       B               VARCHAR2(40)
6 ,       ERR_LENGTH      VARCHAR2(1)
7 );
Table created.
SQL> CREATE TABLE BASE
2 (
3          ID      NUMBER
4 ,       A       VARCHAR2(25)
5 ,       B       VARCHAR2(25)
6 );
Table created.
SQL> INSERT INTO STAGING VALUES (1,RPAD('X',26,'X'),RPAD('X',25,'X'),NULL);
1 row created.
SQL> INSERT INTO STAGING VALUES (2,RPAD('X',25,'X'),RPAD('X',26,'X'),NULL);
1 row created.
SQL> INSERT INTO STAGING VALUES (3,RPAD('X',25,'X'),RPAD('X',25,'X'),NULL);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT * FROM STAGING;
        ID A                                        B                                        E
         1 XXXXXXXXXXXXXXXXXXXXXXXXXX               XXXXXXXXXXXXXXXXXXXXXXXXX
         2 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXX
         3 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXX
SQL> UPDATE STAGING ST
2 SET     ERR_LENGTH = 'Y'
3 WHERE   EXISTS
4          (
5                  WITH    columns_in_staging AS
6                  (
7                          /* Retrieve all the columns names for the staging table with the exception of the primary key column
8                           * and order them alphabetically.
9                           */
10                          SELECT COLUMN_NAME
11                          ,       ROW_NUMBER() OVER (ORDER BY COLUMN_NAME) RN
12                          FROM    ALL_TAB_COLUMNS
13                          WHERE   TABLE_NAME='STAGING'
14                          AND     COLUMN_NAME != 'ID'
15                          ORDER BY 1
16                  ),      staging_unpivot AS
17                  (
18                          /* Using the columns_in_staging above UNPIVOT the result set so you get a record for each COLUMN value
19                           * for each record. The DECODE performs the unpivot and it works if the decode specifies the columns
20                           * in the same order as the ROW_NUMBER() function in columns_in_staging
21                           */
22                          SELECT ID
23                          ,       COLUMN_NAME
24                          ,       DECODE
25                                  (
26                                          RN
27                                  ,       1,A
28                                  ,       2,B
29                                  ) AS VAL
30                          FROM            STAGING
31                          CROSS JOIN      COLUMNS_IN_STAGING
32                  )
33                  /*      Only return IDs for records that have at least one column value that exceeds the length. */
34                  SELECT ID
35                  FROM
36                  (
37                          /* Join the unpivoted staging table to the ALL_TAB_COLUMNS table on the column names. Here we perform
38                           * the check to see if there are any differences in the length if so set a flag.
39                           */
40                          SELECT STAGING_UNPIVOT.ID
41                          ,       (CASE WHEN ATC.DATA_LENGTH < LENGTH(STAGING_UNPIVOT.VAL) THEN 'Y' END) AS ERR_LENGTH_A
42                          ,       (CASE WHEN ATC.DATA_LENGTH < LENGTH(STAGING_UNPIVOT.VAL) THEN 'Y' END) AS ERR_LENGTH_B
43                          FROM    STAGING_UNPIVOT
44                          JOIN    ALL_TAB_COLUMNS ATC     ON ATC.COLUMN_NAME = STAGING_UNPIVOT.COLUMN_NAME
45                          WHERE   ATC.TABLE_NAME='BASE'
46                  )       A
47                  WHERE   COALESCE(ERR_LENGTH_A,ERR_LENGTH_B) IS NOT NULL
48                  AND     ST.ID = A.ID
49          )
50 /
2 rows updated.
SQL> SELECT * FROM STAGING;
        ID A                                        B                                        E
         1 XXXXXXXXXXXXXXXXXXXXXXXXXX               XXXXXXXXXXXXXXXXXXXXXXXXX                Y
         2 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXX               Y
         3 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXHopefully the comments make sense. If you have any questions please let me know.
This assumes the column names are the same between the staging and base tables. In addition as you add more columns to this table you'll have to add more CASE statements to check the length and update the COALESCE check as necessary.
Thanks!

Staging Table Challenge in PL SQL Proc

Hi Guys,
Need your idea for my below requirement.
I have two DB's and daily we'll sync Data from DB1 to DB2 (similar structures) using some plain SQL queries as below
Data synching to only few tables that too only to few columns on some conditions (and we are using nearly 25 temp tables to copy data) but we were unable to track the data what is getting updated dailiy..?
But we badly need to track the data that is getting updated daily, so please suggest me how could I do this...?
Staging Tables..? Note: (we can't maintain staging tables for all the temp tables and every now and then we'll change the DB tables structure also.)
Or else is there any other way to achieve this....?
At the end we should have the data that got updated each day and reports on that data.
Please help me.
Cheers,
Naresh

Naresh wrote:
Hi Guys,
Need your idea for my below requirement.
I have two DB's and daily we'll sync Data from DB1 to DB2 (similar structures) using some plain SQL queries as below
Data synching to only few tables that too only to few columns on some conditions (and we are using nearly 25 temp tables to copy data) but we were unable to track the data what is getting updated dailiy..?
But we badly need to track the data that is getting updated daily, so please suggest me how could I do this...?
Staging Tables..? Note: (we can't maintain staging tables for all the temp tables and every now and then we'll change the DB tables structure also.)
Or else is there any other way to achieve this....?
At the end we should have the data that got updated each day and reports on that data.
Please help me.
Cheers,
NareshChange Data Capture

OWB: how can automatic updation perform in staging database using OWB

I am using OWB-etl to fetch data from source database and store to staging db.
in target table operator i am using insert operation.
it is inserting data fien.
but my requirement is target database must be automatically updated with what ever modification made to source data base.
can u pls help me how to achive this ?
Thanks alot ...
k azamtulla khan

Hi,
why do you want to do this using OWB, is it not easier to create a before/after insert/update trigger on source table so that your target table is updated automatically. You can benefit by using owb in scenarios where you need to transform and load data and then schedule this process and for the rest of it i would recommend using triggers for row level activities such as update.

How to update standard warehouse mgmt tables LTAK, LTAP, LTBK and LTBP

Dear gurus,
I had a requirement to change the update statements on the below standard tables.
LTAK, LTAP, LTBK and LTBP
Can anyone guide me like which function modules or BAPI's or anything that can update these tables.
Thanks & Regards,
Sridhar.

HI Arul, Here is the help document on Local Updates.
In a local update, the update program is run by the same work process that processed the request. The dialog user has to wait for the update to finish before entering further data. This kind of update is useful when you want to reduce the amount of access to the database. The disadvantage of local updates is their parallel nature. The updates can be processed by many different work processes, unlike asynchronous or synchronous update, where the update is serialized due to the fact that there are fewer update work processes (and maybe only one).
You switch to local update using the ABAP statement SET UPDATE TASK LOCAL. This statement sets a "local update switch". When it is set, the system interprets CALL FUNCTION IN UPDATE TASK as a request for local update. The update is processed in the same work process as the dialog step containing the COMMIT WORK. The transaction waits for the update to finish before continuing.
As an example, suppose you have a program that uses asynchronous update that you normally run in dialog mode. However, this time you want to run it in the background. Since the system response time is irrelevant when you are running the program in the background, and you only want the program to continue processing when the update has actually finished, you can set the SET UPDATE TASK LOCAL switch in the program. You can then use a system variable to check at runtime whether the program is currently running in the background.
By default, the local update switch is not set, and it is reset after each COMMIT WORK or ROLLBACK WORK. You therefore need to include a SET UPDATE TASK LOCAL statement at the beginning of each SAP LUW.
If you reset data within the local update, the ROLLBACK WORK statement applies to both the dialog and the update part of the transaction, since no new SAP LUW is started for the update.
Regards,
Ravi

How to update value in RMUSER_TAV table.

Dear experts,
how the field type in rmuser_tav table is updated,can we update directly in the table or will it get it through a roll or from configuration.
In the staging server i have updated directly in the table shall i proceed with the same or any idea
Regards,
krishna maohn

Hi krishna mohan,
Even I want to know how the table RMUSER_TAV is getting updated. Please let me know if you have idea on it.

Synchronizing Updates on a Staging Table

Similar Messages

Maybe you are looking for