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

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

Querying Cubes on Update Rules?

I have an update rule that currently queries an ODS to get the value of a key figure and then apply that key figure to the cube the update rule is intended for.
Basically, this is the select statement I use in the routine:
select defect_quantity from table_a
where notification = notification
    and notif_item = notif_item.
Since the ODS is a flat table, this works fine. However, I am having trouble figuring out how to write this same query against a cube.
Is there a way to query a cube with ABAP in an update rule? Any info or link to how to do this would be appreciated.
Thanks,
Brent

Hi,
There is simple example:
**> You must fill G_T_RANGE table with selection conditions for
**> InfoCube data. In this case char 0VERSION = '1' and
**> 0CALYEAR = '2005'.
CLEAR G_S_RANGE.
G_S_RANGE-CHANM    = '0VERSION'.
G_S_RANGE-SIGN     = 'I'.
G_S_RANGE-COMPOP   = 'EQ'.
G_S_RANGE-LOW      = '1'.
APPEND G_S_RANGE TO G_T_RANGE.
G_S_RANGE-CHANM    = '0CALYEAR'.
G_S_RANGE-SIGN     = 'I'.
G_S_RANGE-COMPOP   = 'EQ'.
G_S_RANGE-LOW      = '2005'.
APPEND G_S_RANGE TO G_T_RANGE.
**> You should also provide information for which combination
**> of characteristic you need value
CLEAR G_S_SFC.
G_S_SFC-CHANM    = '0VERSION'.
G_S_SFC-CHAALIAS = '0VERSION'.
G_S_SFC-ORDERBY = 0.
INSERT G_S_SFC INTO TABLE G_TH_SFC.
G_S_SFC-CHANM    = '0PROFIT_CTR'.
G_S_SFC-CHAALIAS = '0PROFIT_CTR'.
G_S_SFC-ORDERBY = 0.
INSERT G_S_SFC INTO TABLE G_TH_SFC.
G_S_SFC-CHANM    = '0CALYEAR'.
G_S_SFC-CHAALIAS = '0CALYEAR'.
G_S_SFC-ORDERBY = 0.
INSERT G_S_SFC INTO TABLE G_TH_SFC.
**> And finaly which keyfigure should be aggregated
CLEAR G_S_SFK.
G_S_SFK-KYFNM    = '0AMOUNT'.
G_S_SFK-KYFALIAS = '0AMOUNT'.
G_S_SFK-AGGR     = 'SUM'.
INSERT G_S_SFK INTO TABLE G_TH_SFK.
**> I_INFOPROV - InfoProvider name. In this case InfoCube name
**> I_TH_SFC - table with selected chars
**> I_TH_SFK - table with selected keyfs
**> I_T_RANGE - table selection conditions
**> I_PACKAGESIZE - number of records in one function call
**> You should call this function as many times as parameter
**> E_END_OF_DATA will receive 'X' which means that last data
**> packet has been read
**> G_T_DATA - table with aggregated data from InfoCube
CALL FUNCTION 'RSDRI_INFOPROV_READ'
    EXPORTING
      I_INFOPROV                   = 'ZINFOCUBE'
      I_TH_SFC                     = G_TH_SFC
      I_TH_SFK                     = G_TH_SFK
      I_T_RANGE                    = G_T_RANGE
      I_PACKAGESIZE                = 10000
      I_ROLLUP_ONLY                = ''
    IMPORTING
      E_T_DATA                     = G_T_DATA
      E_END_OF_DATA                = END_OF_DATA
    CHANGING
      C_FIRST_CALL                 = G_FIRST_CALL
    EXCEPTIONS
      OTHERS                       = 1.
Krzys

Update rules mapping

Hi Friends,
I have ZSTCSDF coming from transfer structure now I need to map this field with InfoCube field ZCUSTOMER.
ZSTCSDF is using ZCUSTOMER as a reference characteristic.
If it is an attribute then I can map that in update rules but it is reference characteristic instead.
Can anyone suggest me what to do in this?
Thanks,
John.

Hi Friend,
I already have ZSTCSDF this field. This gfield is using 0CUSTOMER as reference characteristic.
So, I have ZSTCSDF in communication structure.
my question is can I map ZSTCSDF and 0CUSTOMER one to one in update rules characteristics.
by referenceing source characteristic in update rules mapping options.
Thanks,
John.

Cubes without Update Rules

Please can i know why is it that a cube can contain data but has no update rules?
Pls give me a hint. thanks.
regards,
Pascal
Message was edited by: Pascal Gabin

Hi!
If the infocube is transational, you should find an option when doing administration on it (right-click on rsa1, infoproviders) than enables it to be loaded like a normal cube(with update rules) or to be planned (BPS input);
Otherwise, the cube is a normal one; and the implementation is incomplete or someone wanted to kept the cube from being further uploaded!
Go figure!
Also you can check in the request log, if you have a log, it was made via upadate rules. If it was made by BPS, the system will not identify Infosource or Datasource on the request!

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

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?

Error in update rules mapping

Hi,
I have added two new fileds into the view and then replicated in bw side.The two fields mapping correctly in Transfer rules.Getting error for two fileds while adding in the update rule.
Thanks,
Jayapal.

Hi Jayapal,
Hope, SAP Note 588247 will help you to resolve this issue. It is giving "Rule incorrect" error, may be because of Infoobject 0RECORDMODE is ignored.
Veerendra.

Find Update Rule mapping!!!

Hi All,
Please let me know a method to find thru a FM or thru any Class (method) the mapping for characteristics in Update rule...
I want to find how is target fields mapped with src field in update rule...
Regards
Aadil
Point will be assigned!!!

Thanks 4 response!!!
@ Raj,
I know it can be found like that but i want to find it in backend...ie an ABAP program to find it.....
@Aduri
Thanks for the table name... but i still would like to know some FM or some standard class cause i know it shud be present...
But thanks for suggestion.

Update rules mapping display

I need to check the update rules and its mapping for objects in production.
I clicked the next arrow button to see the mapping but not able to . It is good enought for me to just see it in display mode.
How can i see the mappings in display mode in Production system?

Hi,
Please double click on the update rule and it show the update rule in display mode .If it is a keyfigure you can see the mapping for all keyfigures and click on the Ty symbol then you can see the mapping for charachterstics.If it is a ODS then you can see the mapping for all char and whne you will double click on Ty symbol you can see the mapping for key fields in ODS.
Regards
Bibhu

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.

Updating Country maps for Nokia Belle

In the past Nokia Suite announced me, when there were newer mapversions of a country available to download.
It is very long time ago (a year?) that I have received any country update. I'm wondering if this service is still available for Nokia with the OS Belle?
I have a Nokia N8.
PS For a long time Nokia Suite couldn't connect with the Nokia server. With some help on internet I am now able to re-connect with the nokia server....But may be not for updating country maps??

Nothing wrong at your side. The last update was in June 2013, there you go …
Two months later, there was a second thread …

Update rule problem for date in Prod

My scenario is like this:-
ODS 2 is loaded from ODS 1, in ODS 1 there is a data field calendar day (DATS, time characteristic) and there is a data field posting date (DATS, characteristic) in ODS 2. In the update rule, the posting date is updated from calendar day by a formula source.
The problem is the posting date data field is updated into ODS 2 correctly in development box but it is not updated (blank) in production box. I can't figure out what is the cause, hopefully someone can give me some help. Thanks.
Cheers!
Cecil

The only different is the development system is having this part of code in the update rules program compare to production system. Do I need to compile the update rules formula manually?
*This ABAP Code was generated automatically          *
*Formula Calculator                                  *
*Generated :2008:09:12-10:47
*User: XXX
*Calculation:
result = COMM_STRUCTURE-CALDAY.
ENDCATCH.
if sy-subrc <> 0.
    perform error_message using 'RSAU' 'E' '507'
            'ROUTINE_0004' g_s_is-recno
            rs_c_false rs_c_false g_s_is-recno
            changing c_abort.
endif.
Cheers!

Update Rule Problem for conversion char values

Hi all,
I need to implement the following logic into the update rule:
data: ch1(10) type c,
ch(8) type c.
ch = ch1.
The value in ch1 can be only characters or only numbers. I am facing problem in converting this, as characters are left aligned and the numbers are right-aligned.
Please guide.
Thanks

Another example can be:
data: ch1(10) type c,
ch(8) type c,
ln type n.
ch1 = '0000000010'.
condense ch1.
ch = ch1.
write:/ ch1, '-----', ch.
In this case, we get only 0 in ch field.
Thanks,

Updating view mapping for atg migration

Hi experts
In the migration document they have mentioned about update view mappings. i am not able to understand this? they also mentioned
Before you import the new ATG 10.0 view mappings, edit the following files in
>/home/localconfig/atg/dynamo/service/jdbc
FakeXADataSource.properties
FakeXADataSource_production.properties.
here is my question- why do we need to change FakeXADataSource.properties. is this mandetory? If you are using Oracle (XA datasource) , why do we need to edit fakexadatasource. please help me to understand .
thanks
Krish

Hi Krish,
yes, it is mandatory. the FakeXADataSource.properties used during initial export and import of data when installing.
Thanks & Regards
Suman Vasireddy
Please mark any update as "Correct Answer" or "Helpful Answer" if that update helps/answers your question, so that others can identify the Correct/helpful update between many updates.

Purchasing cube designing, update rule mapping for 0calday

Similar Messages

Maybe you are looking for