Update rule 0CFM_C11 0CFM_MARKET_RATES: not executable

Hi BI friends
We would like to activate the BI content for update rule 0CFM_C11 -> 0CFM_MARKET_RATES.
After selecting this update rule in BI content area of RSA1 and simulating the installation we get errors:
Chararacteristic 0CFM_AC_REF is available in version M but not in version D
Chararacteristic 0CFM_BOOK_S is available in version M but not in version D
Chararacteristic 0CFM_BT_CT is available in version M but not in version D
Chararacteristic 0CFM_BT_ID is available in version M but not in version D
Chararacteristic 0CFM_FLO_TP is available in version M but not in version D
Chararacteristic 0CFM_FL_NR is available in version M but not in version D
All of the mentioned characteristics are in a active version.
Where is the problem for installing this business content? How can we fix it?
thanks for your help!
BEOplanet

Hi Andreas
I have tried your proposal no. 1 via RSA1: no success. I am getting the same error message:
Regarding your proposal no. 2 via FM RSDG_IOBC_REORG: How should I set the fields after executing the FM?
I_OBJVERS                       A
I_PROGRESS                      R
I_IOBJTP                        *
I_ALL_IOBJ                      R
I_T_IOBJNM                         0 Einträge
I_BYPASS_BUFFER                 R
Thanks
BEOplanet

Similar Messages

"Old" update rule from ODS not working

Hi Gurus,
I need to set up the "old" fashioned update rule to load data from an ODS1 to another ODS2.
The thing is that I need to set up an update rule because I need to implement a Return Table Routine that is not supported (as far as I know) by the new Transformation/DTP.
When I select option (through the right mouse click over ODS1) "Other Options" - "Create Update Rule" it takes me out of the RSA1 and leaves me in the main menu making it impossible to create a new update rule.
The strange thing is that I have this working from and ODS to an InfoCube.....
Suggestions, a workaround??
Andrea.

Hi Jerry,
Just to confirm that this is not working. The tys_TG_1 structure only shows me the target infoprovider structure. Check that in the how to, to be able to derive employee first you need to assign eache source_filed to the result_field leaving employee blank.
I need to have in the same place, the source_field structure (source infoprovider field structure) and the result_field structure (target infoprovider structure). That is what the "old" return table gives me as in the same place I can have the communication_structure (source infoprovider field structure) with the return_table structure (target infoprovider structure).
Just to understand, in the source infoprovider I have 12 Key Figures (1 for each period) and I have to split each incoming record to 12 records. If I work only with the result_field structure tys_TG_1 and the result_package tyt_TG_1 I'm not able the see those 12 KF.
So... return table functionality is not fully supported by BW 7 as far as I know.
Any other ideas why I'm not able to create the old Update Rules from an ODS?
Regards,
Andrea.

Update Rules inactive-Log not found in main memory

Hi
I am trying to active update rules but it is failing with log not found in main memory.
I tried update rules syntax check and system says no error when checking the update rules.
What could the reason? How can I dig this further? Please advise ASAP as this is urgent.
Regards
Vennela

Check out if there has been any update error in VA02 using transaction SM13.
Lokesh

Update Rule in Q not active

Hi SDNers,
when i transported a update rule from D to Q, the update rule still remains inactive. I repeated the transport again and again still it wont change although in D it is active. Even other objects are fine. I did only necessary objects first time and in the repeats i did dataflow b4..Any help??
Thanks
Dave

Hi Dave,
You need to ask your BASIS Team help in this regard.
First you have to identify which trnsports are to be reversed. For Example, The update rules were active until 17 jun 06. On 18 june 06 you transported some new changes to the cube or IS and the update rules were deactivated. Then you created several transports to activate the update rules and they are all failed.
So you have to back the changes upto 17 jun 06.
Once all the transports are reversed you can see the update rules active in QA.
Then you create a fresh transport and apply the changes. Make sure,If you change a cube ot IS, you also have to include UR in your transport.
Hope this helps
Praveen

Update rules infocube 0py_c02 not found BI 7.0

Hello Forum,
By activating the infocube standard payroll (0PY_C02), I found the problem that the rules for updating the infocube not exist and neither are activated in the BI content version 7.0. I have written a note to Sap, and I say it is not a mistake that the rules in version 7.0 will have to manually create. But of course, I have a doubt. There are features and ratios that are calculated using ABAP and routines are not fed directly from the data source, therefore not as cargo and where can I get the code. Someone has an idea?
Thank you.

My mistake, I hadn't selected my system to view the metadata. I also deleted the original source system client and will re-start the replication and migration with the new client

3.x Update rules does not appear in std 0IC_C03 business content

Hi,
We are using BI 7.0.
When trying to install business content update rules for the cube 0IC_C03 (DATA FLOW BEFORE), the three update rules are not appearing in the screen for installation.
Instead , I'm getting three Transformations !! But I need 3.x Update rules only.
Note : The data source used are of type 3.x ONLY.

Hi,
When you Create the update rules manually by default Keyfigures will be set to no-update. You have to propose the rules as you want and it depends on the requirement. And for 0IC_C03 Inventory Cube, almost all the Kfigs are updated based on Routines.
So it is better to Install from BI Content.
Replicate your Datasources. Then Install Transfer rules,and then Install update rules.
Hope this Helps,
Regards
Karthik

Error while Transporting Update Rules.

hi xperts,
   I am getting Error while Transporting the Update rules,i already transported the INFOCUBE,INFOPACKAGE EVERYTHING.
    Start of the after-import method for object type R3TR ROUT (Delete Mode)
Errors occurred during post-handling RS_AFTER_IMPORT for ROUT L
The errors affect the following components:
    BW-WHM (Warehouse Management)
Is the error,I didn't change any thing in the Cube or changes to Update rules.
Can anybody Help me?.
   thanking you,
                               with regards,
                               Narendra.

Hi,
Are you still facuing the issue ?
No need to worry about the routines, once you save the update rules if there is any routines in it it will be saved in the same request. If you want to check the routines you can check in the transport connections. Transfer the update rule to the right hand side of the screen and you can see all the routines that belong to the UR.
If you know the technical names of the routines you can check in the TADIR table.
Have you transported the info-sources for this update rules ? why not you again capture the info-source and the update rule in a single request and transport again.
Hope it helps.
Thanks,
Soumya

Error while copy of Update Rules from ODS 0SD_O03 to InfoCube 0SD_C13

Hi all,
I work on a NW04s SPS9 System I would like to simply copy Update Rules (from an ODS to an InfoCube) from the BCT to the 1:1 Z-Copies of these Objects.
To do so, I copied the InfoProviders 0SD_O03 and 0SD_C13 to Z-Versions. In SAP BCT the InfoCube is updated from the ODS. The ODS itself is updated from InfoSource.
After successfully copying the two InfoProviders as next step I tried to copy the Update Rules from the Content version Objects to the Z-Version Objects to link them.
Similar to copying update rules in 3.5 I tried
- right click on "ZSD_C13"
- choose Additional Functions - Create Update Rules"
- choose DataSource: ODS Object "ZSD_O03"
- choose Copy from: InfoCube "0SD_C13"
This result in the error "0SD_C13 is not suitable as a template for copying update rules".
Some hints that might help:
1. The very same error occurs if I try to copy the Update Rules from 0SD_O03 to 0SD_C13.
2. I also tried to copy both Update Rules (to C12 & C13) on a BW 3.5 system where it worked fine: The update rules from both Z-ODSs to both Z-Cubes were copied correctly 1:1 and without any errors.
3. In the NW04s System I was able to copy the Update Rules from the InfoSource 2LIS_11_VAITM to 0SD_O01 (as well as from 2LIS_11_VAHDR to ODS 0SD_O03). So I only cannot copy Update Rules from ODSs to InfoCubes while it is possible to copy Update Rules from InfoSources to ODSs.
4. During copy of 0SD_O03 the system warned: "InfoObject 0FISCVARNT needs to be in key for DataStore object ZSD_O03". No matter whether I move this IO to the keys of the Z-ODS, the Update Rules copy does not work.
- This warning does not show up on BW3.5 when I copy the very same ODS. Can anyone explain this?
- This warning is not displayed during the copy of ODS 0SD_O01, just for 0SD_O03.
5. Obviously during a preceding test I actually must have been able to copy the Update Rules for another copy of 0SD_C13 (as I can see the Update Rules in the SAPGUI). I stopped this first test as I was not able to do the Update Rules copy for 0SD_C12.
Yet as of today I cannot copy Update Rules this for both cubes 0SD_C13 as well as 0SD_C12. So yesterday there was no error on copying the Update Rules to InfoCube ZSD_C13, but today there is. To my knowledge nothing has been changed in the System Setup / Customizing in the mean time.
6. For both cubes ZSD_C13 as well as ZSD_C12 it is possible to copy Update Rules that map from the BCT ODS to the Z-InfoCbes. So I can copy Update Rules from 0SD_O03 to ZSD_C13 and from 0SD_O01 to ZSD_C12. This would point in the direction that the copied ODSes are the source of this behavior?
I am not sure whether this is a special NW04s behavior and how to use it correctly so the Update Rules can be copied.
Please could you help on how to copy these Update Rules in NW04s or share your experience if you had similar?
Thanks a lot,
Werner

Hi Vinod,
Check the update rules for the original cube. Are they active? It appears that they contain a formula...check this too.
Hope this helps...

Unable to delete update rule

Hello All,
When iam deleting an update rule it is not getting deleted and iam getting message saying underlying infosource does not exists .The underlying infosource is deleted long before any way how come deleting update rule depends on infosource. Please give me solution to delete update rule.

Try going into RSRV and choose All Elementary Tests => Database => Database Information about InfoProvider Tables and Databank Paramerters of *-Schema Tables for Infocube.
Those two options may help to correct the inconsistent state the database is currently in.
Another option .. copy your data target as a backup. Delete the data target, then copy it back.
Brian

Simple update rule question

Hi Gurus, you gave me the right answer, but please help me with this, i see below update rule, it does not tell me the logic or program how it populate the group cost
tell me where i can find the programs for update rule in system by looking below code or from ur knowledge. its very imp for me to understand how the group cost get the value but there is no code it just say result = ws_zgrp_cost which is not the answer please help
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ... DATA: /BIC/AZCOPC_O200.
DATA: WS_ZLGL_COST(16) decimals 2 TYPE P,
WS_ZGRP_COST(16) decimals 2 TYPE P.
DATA: ZPRICE_AVG LIKE /BIC/AZCOPC_O100-PRICE_AVG.
DATA: ZPRICE_STD LIKE /BIC/AZCOPC_O100-PRICE_STD.
DATA: ZPRICE_VAL LIKE /BIC/AZCOPC_O100-PRICE_VAL.
DATA: ZPRICE_VAL1 LIKE /BIC/AZCOPC_O100-PRICE_VAL.
DATA: ZPRICE_VAL2 LIKE /BIC/AZCOPC_O100-PRICE_VAL.
CLEAR WS_ZLGL_COST.
CLEAR WS_ZGRP_COST.
DATA: i_/BIC/AZCOPC_O140 like /BIC/AZCOPC_O140.
$$ end of global - insert your declaration only before this line -
FORM compute_data_field
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING COMM_STRUCTURE LIKE /BIC/CS0CO_PC_ACT_05
RECORD_NO LIKE SY-TABIX
RECORD_ALL LIKE SY-TABIX
SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/AZCOPC_O100-/BIC/ZGRP_COST
RETURNCODE LIKE SY-SUBRC "Do not use!
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal table "MONITOR", to make monitor entries
result value of the routine
RESULT = ws_zgrp_cost.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.

Hi Sonia,
Definitely, the value for that field is not calculated at this UR level. If there is a start routine, it might have been calculated/derived there. If it is pdated for all records in the start routine it does not make sense to have a UR just to assign this as it is already assigned in the start routine. Please check you start routine. Hope this helps.
Thanks and Regards
Subray Hegde

Update Row into Run Table Task is not executing in correct sequence in DAC

Update Row into Run Table Task is not executing in correct sequence in DAC.
The task phase for this task is "Post Lost" . The depth in the execution plan is 19 but this task is running some times in Depth 12, some times in 14 and some time in Depth 16. Would like to know is this sequence of execution is correct order or not? In the out of the Box this task is executed at the end of the entire load. No Errors were reported in DAC log.
Please let me know if any documents that would highlight this issue
rm

Update into Run table is a task thats required to update a table called W_ETL_RUN_S. The whole intention of this table is to keep the poor mans run history on the warehouse itself. The actual run history is stored in the DAC runtime tables, however the DAC repository could be on some other database/schema other than warehouse. Its mostly a legacy table, thats being carried around. If one were to pay close attention to this task, it has phase dependencies defined that dictate when this task should run.
Apologies in advance for a lengthy post.... But sure might help understanding how DAC behaves! And is going to be essential for you to find issues at hand.
The dependency generation in DAC follows the following rules of thumb!
- Considers the Source table target table definitions of the tasks. With this information the tasks that write to a table take precedence over the tasks that reads from a table.
- Considers the phase information. With this information, it will be able to resolve some of the conflicts. Should multiple tasks write to the same table, the phase is used to appropriately stagger them.
- Considers the truncate table option. Should there be multiple tasks that write to the same table with the same phase information, the task that truncates the table takes precedence.
- When more than one task that needs to write to the table that have similar properties, DAC would stagger them. However if one feels that either they can all go in parallel, or a common truncate is desired prior to any of the tasks execution, one could use a task group.
- Task group is also handy when you suspect the application logic dictates cyclical reads and writes. For example, Task 1 reads from A and writes to B. Task 2 reads from B and writes back to A. If these two tasks were to have different phases, DAC would be able to figure that out and order them accordingly. If not, for example those tasks need to be of the same phase for some reason, one could create a task group as well.
Now that I described the behavior of how the dependency generation works, there may be some tasks that have no relevance to other tasks either as source tables or target tables. The update into run history is a classic example. The purpose of this task is to update the run information in the W_ETL_RUN_S with status 'Completed' with an end time stamp. Because this needs to run at the end, it has phase dependency defined on it. With this information DAC will be able to stagger the position of execution either before (Block) or after (Wait) all the tasks belonging to a particular phase is completed.
Now a description about depth. While Depth gives an indication to the order of execution, its only an indication of how the tasks may be executed. Its a reflection of how the dependencies have been discovered. Let me explain with an example. The tasks that have no dependency will have a depth of 0. The tasks that depend on one or more or all of depth 0 get a depth of 1. The tasks that depend on one or more or all of depth 1 get a depth of 2. It also means implicitly a task of depth 2 will indirectly depend on a task of depth 0 through other tasks in depth 1. In essence the dependencies translate to an execution graph, and is different from the batch structures one usually thinks of when it comes to ETL execution.
Because DAC does runtime optimization in the order in which tasks are executed, it may pick a task thats of order 1 over something else with an order of 0. The factors considered for picking the next best task to run depend on
- The number of dependent tasks. For example, a task which has 10 dependents gets more priorty than the one whose dependents is 1.
- If all else equal, it considers the number of source tables. For example a task having 10 source tables gets more priority than the one that has only two source tables.
- If all else equal, it considers the average time taken by each of the tasks. The longer running ones will get more preference than the quick running ones
- and many other factors!
And of course the dependencies are honored through the execution. Unless all the predecessors of a task are in completed state a task does not get picked for execution.
Another way to think of this depth concept : If one were to execute one task at a time, probably this is the order in which the tasks will be executed.
The depth can change depending on the number of tasks identified for the execution plan.
The immediate predecessors and successor can be a very valuable information to look at and should be used to validate the design. All predecessors and successors provide information to corroborate it even further. This can be accessed through clicking on any task and choosing the detail button. You will see all these information over there. As an alternate method, you could also use the 'All/immediate Predecessors' and 'All/immediate Successor' tabs that provide a flat view of the dependencies. Note that these tabs may have to retrieve a large amount of data, and hence will open in a query mode.
SUMMARY: Irrespective of the depth, validate
- if this task has 'Phase dependencies' that span all the ETL phases and has a 'Wait' option.
- click on the particular task and verify if the task does not have any successors. And the predecessors include all the tasks from all the phases its supposed to wait for!
Once you have inspected the above two you should be good to go, no matter what the depth says!
Hope this helps!

Mail 7 (build 1822) does not execute rules

Yesterday's Mail 7 upgrade has (build 1822) no longer not executes my set of rules. Is anyone else having this problem? Is there any solution

Hello Sg42
Check to see if you have downloaded the latest update for Mail, it does resolve issues with syncing with Gmail.
Mail Update for Mavericks
http://support.apple.com/kb/DL1703
Regards,
-Norm G.

Can not view update rules on production BW server

This can be quite a time-consuming problem as I can't always tell if the latest update rules are successfully transported to production.
Most every where else in production I can choose to DISPLAY however this is not the case with update rules only.
Is this a typical setting for most companies? Can I turn off this setting so I can at least DISPLAY the update rules?

hi,
as far as I know you can only see any rules (transfer, update etc.) in BW in change mode.
if you know where to change this setting (i.e. to see rules) - do it
you only have to remember to change it on dev and transport.
Regards,
Andrzej
ps. work around would be to debugg it with simulate data package processing, how to do this?
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/advanced sap bw data transformation
page 12
Message was edited by: Andrzej Krysiuk

Bi content update rule not in prod

Dear Experts,
I'm checking our BI production system today as part of our GO-LIVE activities and I realized that some objects are missing.
Namely the update rules for some attributes and texts of Master Data such as 0customer_ATTR,0customer_TEXT, 0Vendor_ATTR, 0Vendor_TEXT...
I don't know what went wrong as those objects are activated in our QA system.
I have only a few hours to check production then I am not supposed to access it.
Do you have suggestions on how to proceed?
Regards,
Alice

Hi,
Before coming to issue, check if the infoobjects are modeledby direct update. If it is direct update then there wont be any update rules.
You can check weather they are transported to the target system or not. Goto transport connection-->check the objects weather collected in a package or not. If the transport is released there wont be any request number against it.
The better option is to collect the missing objects in a new TR and transport it. There is no big deal doing it as it is only update rules.
Regards
R Karthik K

IN BW UCCHECK transaction for Unicode does not list Transfer/Update rules

Hi All,
We are going to update our BW system to install Enhancement Package 1 SP 7 on our BW 7.0 and we are going also to convert our data base to Unicode.
We used the UCCKECK Transaction to have a list of the abap programs to be modified before the u201Cconversionu201D procedure.
But the transaction does not list the abap code included into transfer rules, update rules and start routines.
Have you an idea to recover them?
And do you think the conversion procedure will abort if these kinds of routines are not adjusted or they will go in error at runtime?
Do you have experienced this problem?
Thanks a lot.
Antonella

Hi Nils, sorry for delay in replyu2026
Unfortunately we started to develop our routines in BW2.0 and checking some of them we receive the error u201CIn Unicode programs, the "-" character cannot appear in names, as it does here in the name "W-DATE" u201Du2026
And further more in subsequent BW releases the same error is only a u201Cwarningu201D into a NON Unicode system.
So I think we should check and correct all our routines before the Unicode conversion.
My best regards, Antonella

Update rule 0CFM_C11 0CFM_MARKET_RATES: not executable

Similar Messages

Maybe you are looking for