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.
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*??
thanksHi 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 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 -
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,
RamHi 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 -
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 advanceI 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 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!
CecilThe 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.
ThanksAnother 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, -
Function module to update operation assignment for a BOM Item
Hi Group,
we have a requirement as under:
Goto BOM Change using CS02->select any BOM item and click the Menu path->Extras->Operation Assignment; and check one or more Operations and then save the transaction.
The above functionality has to be achieved through an Upload program(using Excel) with a Function module/BAPI to serve our purpose. we already did the functionality upto creation of BOM but could not proceed further on this current requirement.
Kindly let me know your inputs if you have already worked in such type of requirement.
thanks in advance for your inputs and let me know if any further info is needed.
Regards,
VishnuHi,
Check the Bapis for BOM
BAPI_MATERIAL_BOM_GROUP_CREATE
CSAP_MAT_BOM_MAINTAIN
I hope second BAPI will be more usefull for your requirement.
Regards,
Goutam Kolluru. -
Update rules for 0PU_C02
I am working on the Funds Management and the Standard Business content cube 0PU_C02, which pulls the data from 7 ODSs through the Update rules. The update rules does not have characteristics fields that needs to passed on to the cube, but it has the Key figure fields (0Amount) to pull. However, On looking in the Infocube content, the data are availble for the Characteristics field along with the expected Key Figure value.
How is this situation possible, where we are getting the data (in the infocube) for the characteristics, which does not have any field specified in the Update rules. I checked other update rules too for getting to the bottom of this.
ThanksHi Saura,
In the update rules screen, click on an update rule for the key figure (in column Ty.) In the screen that opens up you should be able to see update rules for the chars on the char tab.
Hope this helps... -
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,
WernerHi 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... -
hi all
i need to write a routine at the update rule level for currency type....
currency type has data of type 00,01,02 loaded to psa and then to infocube
i need only 00 data to be loaded into cube, so want to write a routine
can you please provide the coding for the same so that i can write at the update rule level for curr type field
RegardsPROGRAM CONVERSION_ROUTINE.
Type pools used by conversion program
TYPE-POOLS: RS, RSARC, RSARR, SBIWA, RSSM.
Declaration of transfer structure (selected fields only)
TYPES: BEGIN OF TRANSFER_STRUCTURE ,
InfoObject 0COMP_CODE: CHAR - 000004
HEADER_COMP_CO(000004) TYPE C,
InfoObject 0PLANT: CHAR - 000004
HEADER_PLANT(000004) TYPE C,
InfoObject 0MATERIAL: CHAR - 000018
HEADER_MATERIAL(000018) TYPE C,
InfoObject 0MATL_TYPE: CHAR - 000004
HEADER_MAT_TYPE(000004) TYPE C,
InfoObject 0MATL_GROUP: CHAR - 000009
HEADER_P_GROUP(000009) TYPE C,
InfoObject 0LOTSIZE_IT: QUAN - 000013
LOTSIZE(000007) TYPE P,
InfoObject 0UNIT: UNIT - 000003
LOTSIZE_QTY_UNIT(000003) TYPE C,
InfoObject 0FISCPER: NUMC - 000007
PERIODE(000007) TYPE N,
InfoObject 0FISCVARNT: CHAR - 000002
FISCAL_Y_VARIANT(000002) TYPE C,
InfoObject 0PCPITEMCAT: CHAR - 000001
ITEM_CATEGORY(000001) TYPE C,
InfoObject 0PCP_RES: CHAR - 000035
COST_ITEM(000035) TYPE C,
InfoObject 0COMPONENT: CHAR - 000018
MATERIAL(000018) TYPE C,
InfoObject 0VAL_CLASS: CHAR - 000004
VALUATION_CLASS(000004) TYPE C,
InfoObject 0PLANT_COMP: CHAR - 000004
PLANT(000004) TYPE C,
InfoObject 0SEND_CMPC: CHAR - 000004
COMPANY_CODE(000004) TYPE C,
InfoObject 0CO_AREA: CHAR - 000004
CONTROLLING_AREA(000004) TYPE C,
InfoObject 0COSTCENTER: CHAR - 000010
COST_CENTER(000010) TYPE C,
InfoObject 0ACTTYPE: CHAR - 000006
ACTIVITY_TYPE(000006) TYPE C,
InfoObject 0WORKCENTER: CHAR - 000008
WORK_CENTER(000008) TYPE C,
InfoObject 0VENDOR: CHAR - 000010
VENDOR(000010) TYPE C,
InfoObject 0INFO_REC: CHAR - 000010
INFO_RECORD(000010) TYPE C,
InfoObject 0ABCPROCESS: CHAR - 000012
PROCESS(000012) TYPE C,
InfoObject 0AMOUNT: CURR - 000015
VALUE(000008) TYPE P,
InfoObject 0AMOUNTFX: CURR - 000015
VALUE_FIXED(000008) TYPE P,
InfoObject 0AMOUNTVR: CURR - 000015
VALUE_VARIABLE(000008) TYPE P,
InfoObject 0OI_MENGE: QUAN - 000015
QUANTITY(000008) TYPE P,
InfoObject 0BASE_UOM: UNIT - 000003
QUANTITY_UNIT(000003) TYPE C,
InfoObject 0PRICEUNIT: DEC - 000005
PRICE_UNIT(000003) TYPE P,
InfoObject 0CURRENCY: CUKY - 000005
CURRENCY(000005) TYPE C,
InfoObject 0CURTYPE: CHAR - 000002
CURRENCY_TYPE(000002) TYPE C,
InfoObject 0COSTELMNT: CHAR - 000010
COST_ELEMENT(000010) TYPE C,
InfoObject 0COSTCOMP: NUMC - 000003
COST_COMPONENT(000003) TYPE N,
InfoObject 0CCOMPSTRUC: CHAR - 000002
COST_COMP_STR(000002) TYPE C,
InfoObject 0SCRAPQTY: QUAN - 000015
SCRAP_QTY(000008) TYPE P,
InfoObject 0COMP_SCRAP: QUAN - 000015
COMP_SCRAP_QTY(000008) TYPE P,
InfoObject 0COSTVAR: CHAR - 000004
COSTING_VARIANT(000004) TYPE C,
InfoObject 0COSTVERS: NUMC - 000002
COSTING_VERSION(000002) TYPE N,
END OF TRANSFER_STRUCTURE .
Global code used by conversion rules
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA: ...
$$ end of global - insert your declaration only before this line -
FORM COMPUTE_CURTYPE
Compute value of InfoObject 0CURTYPE
in communication structure /BIC/CS0CO_PC_PCP_10
Technical properties:
field name = CURTYPE
data element = /BI0/OICURTYPE
data type = CHAR
length = 000002
decimals = 000000
ABAP type = C
ABAP length = 000002
reference field =
Parameters:
--> RECORD_NO Record number
--> TRAN_STRUCTURE Transfer structure
<-- RESULT Return value of InfoObject
<-> G_T_ERRORLOG Error log
<-- RETURNCODE Return code (to skip one record)
<-- ABORT Abort code (to skip whole data package)
FORM COMPUTE_CURTYPE
USING RECORD_NO LIKE SY-TABIX
TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
G_S_MINFO TYPE RSSM_S_MINFO
CHANGING RESULT TYPE /BI0/OICURTYPE
G_T_ERRORLOG TYPE rssm_t_errorlog_int
RETURNCODE LIKE SY-SUBRC
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel datapackage
$$ begin of routine - insert your code only below this line -
DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
If <SOURCE_FIELDS>-CURTYPE NE '00'
Delete DATA_PACKAGE.
RESULT = .
returncode <> 0 means skip this record
RETURNCODE = 0.
abort <> 0 means skip whole data package !!!
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.
FORM INVERT_CURTYPE
Inversion of selection criteria for InfoObject 0CURTYPE
This subroutine needs to be implemented only for SAP RemoteCubes
(for better performance) and for the Report/Report Interface
(drill through).
--> I_RT_CHAVL_CS Ranges table for current InfoObject
--> I_THX_SELECTION_CS Selection criteria for all other InfoObjects
<-- C_T_SELECTION Selection criteria for fields of
transfer structure
<-- E_EXACT Flag: Inversion was exact
FORM INVERT_CURTYPE
USING I_RT_CHAVL_CS TYPE RSARC_RT_CHAVL
I_THX_SELECTION_CS TYPE RSARC_THX_SELCS
CHANGING C_T_SELECTION TYPE SBIWA_T_SELECT
E_EXACT TYPE RS_BOOL.
$$ begin of inverse routine - insert your code only below this line-
DATA:
L_S_SELECTION LIKE LINE OF C_T_SELECTION.
An empty selection means all values
CLEAR C_T_SELECTION.
L_S_SELECTION-FIELDNM = 'CURRENCY_TYPE'.
Selection of all values may be not exact
E_EXACT = RS_C_FALSE.
$$ end of inverse routine - insert your code only before this line -
ENDFORM. -
I removed from my comm structure some objects that I didn't need there.
Some of them are not connected in the datasource to any field, they just get filled in the update rules by routines. Others just weren´t used anymore and already out of the cube. Since that when I extract the info to the cube, the requisition freezes in the end of update rules waiting for final response.
I re-activated the comm structure, the datasources, the cube, but the update rules gives me a short dump:
Message type x
Msg classe RSAU
N.º 001
Var 1 " "
Var 4 " "
The termination occurred in the ABAP program "%_T0ITS2" in "INSTANTIATE".
the main program was "SAPMRSAU"
The termination occured in line 0 of the source code of the (Include)
program " "
of the source code of program " " (when calling the editor 00).
Did this happen to someone?! Or knows what could bwe the problem?!
Thank you
JoãThank you for forcing me to go there once again.
I was looking at my routines, and forgot to check the formulas.
Had a calculated key figure with one of that objects. By correcting this I also correct other error. 2 in 1 :-D
Thankx -
Dependant routines in Update Rules ?
Hello all
Is it possible to create a routine in the Update Rules that uses a result of a previous routine in the same set of Update Rules ?
For example:- I have a routine in the Update Rules for converting sales units from the communication structure to base units of measure. In the same set of Update Rules I then want to use that base UOM to fill a characteristic that evaluates quantity bands. Can this be done? If so how do you ensure that the sales unit to base unit conversion works first?see this article too..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/60cecb1d-0a01-0010-8289-b14fd99062fa
(the difference being that instead of select on the MD tables,u will loop on the data package and place it into work-area..declare work_area like data_package or like commn structure..
declare internal table with key fields,and the field for base UoM,also have field for sales unit(but may not be required)..
cal base UoM in loop and then set..
ITAB-BASEUOM = calculated-BASEUoM
iTAB-key field1 = WA_keyfield1.
APPEND ITAB.
then in the update routine..
do READ on ITAB as in the document.
Vishvesh -
Update rule could not be found during business content activation
Dear BW experts,
I am having an issue activating business content for an update rule (2LIS_03_BX) for 0IC_C03. Below is a log of the error. It seems like the system is not recognizing the update rule for some reason. Can somebody please help shed some light on this.
Installation (simulation mode) of: Update Rules (UPDR)
Transfer/Merge of the Content Version (Object Type Update Rules )
Object Update Rules BW9VUFZSUYTTIZS0HT9I4U3RP: Installation of the Content Version
Transfer update rules IC: 0IC_C03 / IS: 2LIS_03_BX
Object UPDR BW9VUFZSUYTTIZS0HT9I4U3RP could not be found
Transferring the 1 objects from type UPDR took 1.2 seconds
Post-processing of Objects after activation
The post-processing lasts 0.0 seconds
Thank you.
AndrewRavi,
Thanks for you reply. I checked the underlying cube (0IC_C03) and the info source (2LIS_03_BX) and they are both active. I didn't choose the option in data flow before and after because it would have brought way too much contents which I don't need. Instead, I only activated the info source and update rule individually. All three info sources (2LIS_03_BF, BX, UM) and the info cube were successfully activated. I am only having problem with the update rule.
Any other ideas?
Thanks,
Andrew -
Hi Guru's,
Happy New Year.
ktosl field not coming in update rule, after unhideing from data source.
till communication stru. i can see after updating TR.
but this info object not coming in update rule.
looking for your input.Dear SSMS,
There are 2 possibilities.
1) You dont have the same Infoobject in your Target, but still you want to map it with the Infoobject coming from your CommStructure, if the datatype and length are same you could do it in Update Rules> Source Characteristic> F4 -->Find your Infoobject and Map it .
2) You have your Infoobject in Target and still you are unable to Map it , reason , may be you have to check the Comm.Structure, if its there , it should come, orelse Add it and Activate it again , then go to the Update Rules, For the specific Infoobject --> Manually maintain the characteristic as specified above.
Hope it helps..
Thanks,
Krish
Maybe you are looking for
-
Taking too much time in Rules(DTP Schedule run)
Hi, I am Scheduling the DTP which have filters to minimize the load data. when i run the DTP it is taking too much time in the "rules" (i can see the DTP monitor ststus package by pakage and step by step like "Start routine" "rules" and "End Routine
-
STO. How to create the stock in transit if the plant has been block.
Problem with STO. How to clear the stock in transit if the plant has been block.
-
Is there an appropriate adaptor to hook the new MacBook (USB-C port) to the Cinema Display?
-
Switching To Mac From Windows?
First post here, so I'd firstly like to say Hello to everyone and wish them a happy new year Basically, I'm curious to know if any of you have switched to a MAC from a Windows based machine, and if you found the transition easy and "complete" in the
-
I am doing a SOAP -> XI --> IDoc scenario.I am trying to have an external organization send soap messages into our interface and they need to be secure. So I am using the HTTPS authentication in the sender SOAP adapter. How do you make sure that the