Update rules error for 0IC_c03

HI all,
I have replicated the BF,BX and UM datasources into BI and I restored the BX datasource to 3.x and assigned the DS to standard Infosource 2lis_03_BX and activated.
one field 0GN_R3_SSY was not mapped because there was no field in the DS 2lis_03_BX.
I activated the transfer rules,it got activated without error,but it was in yellow.
And I created a Zcube copying the standard cube 0IC_C03 and tried to create update rules,giving the Infosource name 2lis_03_bx
then a message popped up saying
'InfoSource 2LIS_03_BX is only set up for the initial run for non-cumulatives.' I clicked on ok and then another message as
'No update exists for time-reference characteristic 0CALDAY' and clicked ok then update rules proposal generated,and in update rules the status of some of keyfigures with type routine was showing error
for example:
Value Received into Valuated Stock , Receipt Quantity: Blocked Stock , Quantity Received into Consignment Stock
Receipt Quantity Total Stock
please explain in detail what could be the reason?

Try to create an infosource by using copy from the standard one. Then try to See the std mapping between infosource & data target. Similarily do the mapping between Zinfosource & Z data target as the std one.
Hi PT,
I will do as you said, I have a doubt is it all because 0GN_R3_SSY is not mapped in the transfer rules ,because transfer rules are not in green when I activated it and Iam going to create the Update rules.
How to copy the standard Infosource as you wont get any option to copy it.
Thx

Similar Messages

Update rule/routine for 0PUR_C04

hi experts,
can someone give the update rule/routine for uploading 0ORDER_VAL(effective order value) into the cube 0PUR_C04 and the calculations for it?
and also some explantion on how this effective purchase order value 0ORDER_VAL is calculated*??
thanks

Hi Surya,
If you are using standard content for 0PUR_C04, you can get the update rule in standard update rules, which you can see in Business content on Metadata repository. For standard content four data source used to fill cube. Purchasing Group (2LIS_02_S011 ), Purchasing Data (2LIS_02_HDR), Pur.Data (2LIS_02_SCL) and Purchasing Data (2LIS_02_ITM). The mapping for different update rules are done as:
2LIS_02_S011: Direct Mapping
2LIS_02_HDR: No Update
2LIS_02_SCL: Routine (mm_convert_effwr)
fill the internal table "MONITOR", to make monitor ent *ries
IF ( COMM_STRUCTURE-PROCESSKEY = '001' or "Bestellu *ng
COMM_STRUCTURE-PROCESSKEY = '011' or
COMM_STRUCTURE-PROCESSKEY = '021' or
COMM_STRUCTURE-PROCESSKEY = '004' or "LP
COMM_STRUCTURE-PROCESSKEY = '014' or
COMM_STRUCTURE-PROCESSKEY = '024' )
AND COMM_STRUCTURE-BWAPPLNM EQ 'MM'
AND COMM_STRUCTURE-ORDER_VAL <> 0.
perFORM LOC_CURR_CONVERT
USING COMM_STRUCTURE-ORDER_VAL
COMM_STRUCTURE-DOC_DATE
COMM_STRUCTURE-ORDER_CURR
COMM_STRUCTURE-LOC_CURRCY
COMM_STRUCTURE-EXCHG_RATE
CHANGING RESULT.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
else.
RETURNCODE = 4.
endif.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
2LIS_02_ITM: No Update
Hope this will give you some lead.
Regards,
Kams

Update Rule error while loading the data

Hello All,
I tried to do the init load for the datasource 2LIS_02_VAKON (Sales Document Condition), But it error's out in the Update rule saying:
Short text: Error when generating the update program
Long Text: Diagnosis
     An error occurred during program generation for InfoSource 2LIS_11_VAKON
     and InfoProvider 0SD_C15 . This may be extrapolated to incorrect update
     rules.
Procedure
     Check and correct your update rules and then generate the update program
     again. You can find help on the error in the error log.
The update rule looks very fine. I even deleted it and re created, but no success..... Please give me your thoughts abt it..... Any suggestions will be great for me.....

Hello Gokul,
I could'nt see any analyse button in RSMON. This is the only error message I could get from the Process monitor:
Short text: Error when generating the update program
Long Text: Diagnosis
An error occurred during program generation for InfoSource 2LIS_11_VAKON
and InfoProvider 0SD_C15 . This may be extrapolated to incorrect update
rules.
Procedure
Check and correct your update rules and then generate the update program
again. You can find help on the error in the error log.
Do you expect something else ? Also I went through your OSS note, they are asking to apply support pack 18. Is this a serious issue to apply SP? Because in Quality and Prod it loads fine......
Please let me know your idea

While creating Update rules -"Error Info source does not exist"

While creating an update rule I am getting an error that Info source doesnot exist though the inf source is active.
here is error:
No communication structure exists in version abc... A
Message no. RSAU251
Diagnosis
In order to be able to maintain the update rules an active communication structure must be available.
Procedure
This error message can have two causes.
No active communication structure exists.
Activate the communication structure in the Data Warehousing Workbench.
No communication structure exists for the InfoSource.
Create a communication structure in the Data Warehousing Workbench for the InfoSource.
<<text removed>>
Thanks,
Vasu
Edited by: Matt on Apr 26, 2010 9:31 AM

Hi Vasu,
as it clearly shows below message
No communication structure exists for the InfoSource.
Create a communication structure in the Data Warehousing Workbench for the InfoSource.
Create an info source first and assign it to your datasource and map the fileds in transfer rules and activate it.
Then try to create the update rules between your target and info source.
Hope this helps.
Regards,
Reddy

Update Rule Error

Hi Friends,
I am installing Update rule for info Cube name: 0PAPA_C02 ( HeadCount ).
I am facing problem in installing update rule wiht following error "Object Update rules 907KB92TLFDNXIKNGFCS15IN4: Error installing the Content version" , can any one will help on this.
I shall be glad for every one for positive reply.
Regards
Deepak

Hi Mansi,
As per SAP Note No 336229, we are installing info cube 0PAPA_C02 ( Headcount ) with Grouping selection as "In dataflow before and after" . On simulation we got this error only. pl. suggest where to find detail logs for this..
info source is active.
Note no 336229 Detail
Do the following steps in your BW System:
1. Transfer the Business Content in the Administrator Workbench:
Choose InfoCube 'Headcount' (0PAPA_C02), collect all objects with
grouping 'Data flow before and after' and copy them from the Business
Content afterwards.
Check whether key figures 0ANSAL_NC / 0ANSAL_VC, 0HDFTE_NC / 0HDFTE_VC
and 0HDCNT_NC / 0HDCNT_VC were activated in the process.In addition,
InfoCube 0PAPA_C02 itself, InfoSource 0HR_PA_PA_1 and the respective
update rules should be active.
Regards
Deepak

Update rules only for the keys of a DSO

Hi everybody,
We have a problem after our recent migration to BI 7.0.
In a transfer rule, the 0RECORDMODE is set to 'D' and in the update rules only the keys of the DSO are mapped. It's just for a deletion of data in the DSO.
In BW 3.5, everything was fine but now it doesn't work anymore. Data are transfered but not inserted in the DSO.
I've tried to affect a constant to a characteristic which is not a key in the update rules and the data are correctly inserted.
Is it a normal comportment ?
Any idea is welcome.
Thanks in advance

I think I have a similar problem. I've got updates for iWork apps available after upgrading to Mavericks. I've tried both my apple ID and my wife's but I get an error with both saying the software was purchased with a different ID. I have no idea what ID that would be. Is there anyway to check the ID the software is licensed to?

Update Rule: error during activate process

Dear Guys!
I could not activate one of my update rules. When i go to transport connection
to try solve the problem, found this errors:
Object '0SPL_EXPHRZ' (IOBJ) of type 'InfoObject' is not available in version 'A'
Object '0SPL_TARGET' (IOBJ) of type 'InfoObject' is not available in version 'A'
Object '0SPL_TRSORD' (IOBJ) of type 'InfoObject' is not available in version 'A'
If i ignore this errors and transport the rule, i receive the RSAU466 message.
But i checked the rule's program and didn't found any error.
Can somebody please help?
Regards,
Wilson
PS.: Sorry my english, it's not my natural language.

Hi Manga!
First of all, thank you for the attention!
I solved the update rule's problem transporting the infocube and the rules again. The infocube after the rules.
Now every thing is OK. I sent your tips to the BW-Administrator, he will solve the problem about 0SPL_EXPHRZ, 0SPL_TARGET and 0SPL_TRSORD, because the rule's problem it wasn't related with this.
Best Regards
Wilson.

DTP Vs Update Rules Error!!!!!!!!!!!!!!!!!!!!!!1

Hi guys,
I have a scenerio , where I need to have data from 2 DSOs in to one combined DSO. Lets Says the 2 DSOs as DSO A and DSO B. and the Third as DSO C.
I want to get DSO C Structure as exactly as DSO A. and DSO B structure is only few fiew fields from DSO A (Key Fields are same). I have loaded the data in to DSO A and DSO B using Transformation and DTP . Now How to load DSO C data I mean combined data of DSO A and B.
1.If I create update Rules to DSO C using DSO A and DSO B. Iam not getting any data in to DSO C. (Do I need to make any settings in DSOs to update the data of A and B in to C ?).
2.If I create 2 transformations between DSO A -C and DSO B-C. I am sure I need to create DTPs to get the corresponding data. When I do that Iam getting 2 separate sets of data for DSO C. But I need data as one set from DSO A & B in to C.
Please help me ASAP and let me know if you need more information on it.
Thanks in advance

Harish,
as i told you earlier, if the fields you are looking from DSO B is not available in DSO A, you can create transformation usign respective DSO if your Key fields are same in both DSO A and DSO B..
assume...F1, F2, F3 are key fields in both DSO A and B.
DSO A:
F1, F2, F3, F4, F5, F6, F7.
DSO B:
F1, F2, F3, F8, F9.
DSO C:
F1, F2, F3, F4, F5, F6, F7, F8, F9.
If you load data from DSO A to DSO C, it will create one record in DSO C with updation of F1, F2, F3, F4, F5, F6, F7(because f1, f2, f3, f4, f5, f6, f7 only mapped).
If you load data from DSO B to DSO C, it will <b>Update</b> existing entry using Key fields for other 2 fields(which mapped from DSO B to DSO C).
Change log table of DSO C update with 2 records(i'm talking about Standard table).
write optimized works differently.
all the best.
Regards,
Nagesh Ganisetti.
assign points if it helps.

Purchasing cube designing, update rule mapping for 0calday

Hi All,
Iam designing cube for Purchasing module in BW. Iam having doubt in mapping for 0calday in update rules, is it with document date or scheduline date. I have searched in SAP cube 0PUR_C01, it is mapped with 0SCHED_DATE( schedule line date). How the difference comes when we choose document date and schedule line date.
FYI, we are using only schedule line data source, which is giving relevant information.
Thanks,
Ram

Hi Ram,
Please note:
0SCHED_DATE: The schedule line date is the day on which the scheduled quantity of the material is to be delivered.
0DOC_DATE: The date on which document has been craeted.
Use the first one for purchasing.
Thanks...
Shambhu

BW 0HR_PA_2 - 3 Update rules assignment for 0PA_DS02 - 3

Hello experts
I am just another one tryng to figure out how to assign the update rulesfor DSO's 0PA_DS02 and 3. The business content activation of the update rules yields a no update type of rule. So I guess we need to assign the fields manually. I read the <How-to> document on the BW/HR authorization but I am still trying to pass <GO> and load the initial data as the document does not mention the update rules assignment. In that regards I searched SDN on how to modify the update rules but I can't seem to pin point the exact complete information.
Please help.
Thanks.
YB.

=========================
Update Rules for 0PA_DS03 (Part 2)
=========================
0TCTNDEF - BW Reporting Authorizations: Node Variables Defaul
Initial value
0TCTNIOBJNM - InfoObject of Node
Routine:
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA:   ...
$$ end of global - insert your declaration only before this line   -
FORM compute_key_field
TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING    COMM_STRUCTURE LIKE /BIC/CS0HR_PA_3
           RECORD_NO LIKE SY-TABIX
           RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BI0/APA_DS0300-TCTNIOBJNM
           RETURNCODE LIKE SY-SUBRC
           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
RETURNCODE = 0.
result value of the routine
IF COMM_STRUCTURE-hr_otyobj IS INITIAL.
    RESULT = '1NODENAME'.
ELSE.
    CASE COMM_STRUCTURE-hr_objtype.
      WHEN 'O'.   RESULT = '0ORGUNIT'.
      WHEN 'C'.   RESULT = '0JOB'.
      WHEN 'S'.   RESULT = '0HRPOSITION'.
      WHEN 'P'.   RESULT = '0EMPLOYEE'.
      WHEN 'Q'.   RESULT = '0QUALIFICTN'.
      WHEN 'QK'. RESULT = '0QUALIGROUP'.
      WHEN 'BA'. RESULT = '0APPRAISAL'.
      WHEN 'A'.   RESULT = '0HRWORKCNTR'.
      WHEN 'BK'. RESULT = '0AP_CRIT'.
      WHEN 'BS'. RESULT = '0AP_SCHEME'.
      WHEN 'E'.   RESULT = '0EVENT'.
      WHEN 'D'.   RESULT = '0EVENTTYPE'.
      WHEN 'L'.   RESULT = '0EVENTGROUP'.
      WHEN 'F'.   RESULT = '0EVLOCATION'.
      WHEN 'G'.   RESULT = '0RESOU'.
      WHEN 'R'.   RESULT = '0RESTYPE'.
      WHEN 'H'.   RESULT = '0EXTPERS'.
      WHEN 'U'.   RESULT = '0EXTORG'.
      WHEN OTHERS.RETURNCODE = 4.
    ENDCASE.
ENDIF.
if the returncode is not equal zero, the result will not be updated
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.
0TCTNODE    - Nodes of a Hierarchy
Routine:
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA:   ...
$$ end of global - insert your declaration only before this line   -
FORM compute_key_field
TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING    COMM_STRUCTURE LIKE /BIC/CS0HR_PA_3
           RECORD_NO LIKE SY-TABIX
           RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BI0/APA_DS0300-TCTNODE
           RETURNCODE LIKE SY-SUBRC
           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
IF COMM_STRUCTURE-hr_otyobj IS INITIAL.
    RESULT = 'ROOT_H'.
ELSE.
    RESULT = COMM_STRUCTURE-hr_otyobj.
ENDIF.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
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.
0TCTOBJVERS- Object Version
Constant: A
0TCTSYSID - BW System
Routine:
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA:   ...
$$ end of global - insert your declaration only before this line   -
FORM compute_key_field
TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING    COMM_STRUCTURE LIKE /BIC/CS0HR_PA_3
           RECORD_NO LIKE SY-TABIX
           RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BI0/APA_DS0300-TCTSYSID
           RETURNCODE LIKE SY-SUBRC
           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
CALL METHOD cl_rso_repository=>get_logical_system_self
    RECEIVING
      r_logsys = RESULT.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
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.

DSO - Cube : Update Rule Error

When trying to push data from an DSO to a ube, the request stays amber until finally short dumping.
The update rule is activated and all key figures, characteristics and time characteristics are filled correctly from the DSO.
The error message in the monitor of the request is:
<i>Update Rules (15199 => 0 records) : Errors Occurred</i>
How do I see the exact error description of what caused the update rule not to transfer any records? I can't seem to find much information in the monitor of what went wrong.
Thanks in advance,
Matt

There is a characteristic called 'Reporting Week' that uses some routine to convert the a document 'created on' date in the week/year format (e.g 01.2008).
Code of this routine is below. All other characteristics or key figures in this update rule are matched with source fields.
fill the internal table "MONITOR", to make monitor ent *ries
result value of the routine
DATA: i_per(3) type n,
i_year(4) type n.
CALL FUNCTION 'DATE_TO_PERIOD_CONVERT'
EXPORTING
I_DATE = COMM_STRUCTURE-createdon
I_PERIV = 'ZW'
IMPORTING
E_BUPER = i_per
E_GJAHR = i_year
EXCEPTIONS
INPUT_FALSE = 1
T009_NOTFOUND = 2
T009B_NOTFOUND = 3
OTHERS = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
concatenate i_year i_per+1(2) into RESULT.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
if abort is not equal zero, the update process will be canceled
ABORT = 0.

Update rules error urgent

Hi friends,
Iam uploading data Parallely ODS &CUBE.
But iam getting Red in ODS and Yellow in CUBE.
When i check the error in ods level.
showing below error ...
Update rules ( 12485 -> 0 Records ) : Errors occurred
Fatal error in customer routine 9998.
What does it mean?
My routine progrm is written in ODS level like
fill the internal table "MONITOR", to make monitor entries
LOOP AT DATA_PACKAGE.
    IF DATA_PACKAGE-doc_categ NE 'C' AND
       DATA_PACKAGE-doc_categ NE 'I'.
      DELETE DATA_PACKAGE.
    elseif DATA_PACKAGE-recordmode eq 'R'.
      DATA_PACKAGE-recordmode = 'X'.
      modify DATA_PACKAGE.
    ENDIF.
ENDLOOP.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
HERE ANY CHANGESS REQURIED?
Kindly help me.
Thanks in advance
Ramya
Message was edited by:
        ramya thulluru

Hi Ramya,
You would need to debug the code to find the exact place where it is failing.
You would need to include an infinite loop in the start routine of the update rules. Your code may be as follows:
data: t_debug_flag_start value 'X'.
if t_debug_flag_start = 'X'.
do.
if t_debug_flag_start = ' '.
exit.
endif.
enddo.
endif.
Now when you execute the infopackage you would find that a generated program GP*** in sm50. You can debug the generated program by changing the value of t_debug_start.
Bye
Dinesh

Update rules error

Hi All,
I got this error when i try to activate the update rule of the InfoCube:
IC=(infocube's name) IS=8(ODS' name) error when generating InfoCube Update program.
IC=(infocube's name) IS=8(ODS' name) syntax error: The Dictionary structure or table "/BIC/DP_SRM011" rows 32
Does anyone know anything about this error?
Thanks!

Have a look at this:
Error in Update Rules
Regards

ZSD_C14 - Backorders - Update rules error

Hi Friends,
I want to load into (ZSD_C14) from ZSD_O04. Actually when i copy from 0SD_C14, 0SD_O04 Update routines didn't copied. I have copied manually. Once it's done i was trying to load into ZSD_c14 but it's strucking in the Update rules. It's taking lot of time. I notice that it may be update rules problem.
Kinly give me the solution it's very urgent.
Siri

HI Gajendra,
Thank you for your quick response.. But i'm not very good in Coding..
pls find the below coding which i have.
DATA: g_workarea LIKE /bi0/asd_o0100,
      l_/bi0/asd_o0100_itab TYPE HASHED TABLE OF /bi0/asd_o0100 WITH
      UNIQUE KEY doc_number s_ord_item,
      g_doc_number_save LIKE /bi0/asd_o0100-doc_number,
      g_s_ord_item_save LIKE /bi0/asd_o0100-s_ord_item,
      l_days_open TYPE i,
      l_index LIKE sy-tabix.
FORM check_new_data
--> L_DOC_NUMBER
--> L_S_ORD_ITEM
--> G_WORKAREA
FORM check_new_data USING    l_doc_number
                             l_s_ord_item
                    CHANGING g_workarea LIKE /bi0/asd_o0100.
IF l_doc_number NE g_doc_number_save OR
     l_s_ord_item NE g_s_ord_item_save.
    CLEAR g_workarea.
    SELECT SINGLE * FROM /bi0/asd_o0100
                    INTO CORRESPONDING FIELDS OF g_workarea WHERE
                    doc_number = l_doc_number AND
                    s_ord_item = l_s_ord_item.
    g_doc_number_save = l_doc_number.
    g_s_ord_item_save = l_s_ord_item.
ENDIF.
ENDFORM.                    "check_new_data
$$ 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/CS8ZSD_O04
           RECORD_NO LIKE SY-TABIX
           RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/VZSD_C14T-OPQTCRGI
           RETURNCODE LIKE SY-SUBRC
           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
IF sy-datum GT COMM_STRUCTURE-dsdel_date AND
     COMM_STRUCTURE-gi_sts NE 'C'.
    RESULT = COMM_STRUCTURE-conf_qty - COMM_STRUCTURE-gis_qty.
ENDIF.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
Where i need to change please let me know.
Siri

Trouble shoot update rules error??

Hello Experts,
After i created an update rules, when i tried to activated the update rules, i encountered the error message as below:
"IC=MA1SD_0 IS=MA1_IS_12VCITM error when checking the update rules
Message no. RSAU461"
can anyone advise how shall i go about to trouble shoot this error message?

Check your infosource consistency..and update rules...

Update rules error for 0IC_c03

Similar Messages

Maybe you are looking for