Update rules import/export

Hi expterts,
I'm trying to export some structures from a BW system in order to import them in to another one.
I'm using the XML import/export tool and it seems to work fine for ODS but I'm finding some problems to export the update rules because when I import them it simply does not create anything.
Is there a way to manage this issue ?
best regards,
mirco

You can try using the Microsoft.Office.Server.Search.Portability namespace in the object model. This can be done per site collection and does include query rules.
http://technet.microsoft.com/en-us/library/jj871675.aspx
Blog | SharePoint Field Notes Dev Tools |
SPFastDeploy | SPRemoteAPIExplorer

Similar Messages

"update rules inactive " error when importing transport request

Hi experts,
I am stuck while importing transport request of update rules. I am moving transport request of update rules from 1 system to another and stuck while importing it in 2nd system. Only two update rules are stuck among all giving an error of "inactive update rules".
I have again tranported it twice after activating theose two update rules.
Please help!!!!!

Hi Heena,
Can you provide more details of the issue like is it a DSO to DSO transformation, error message etc.

Update rules wont activate after import

Hi,
I am struggling with few of the update rules not activating after import. Is there any mass update program which will activate all the update rules similar to RS_TRANSTRU_ACTIVATE_ALL for transfer structure.
I dont understand why its failing is it because i am not transfering the datasources for the data targets. All the 8* update rules are not activating.
can someone put some light on this....I am sure someone has faced a problem like this.
thanks

This is what it says
Error when activating update rule 17Z1GSU08CYFZZYZASTYEOWN7
IC=YO11_ITM IS=2LIS_11_VAITM error when checking the update rules
Error when activating update rule 4Q1OIGZH4UMX80V06YQRYOHKK
IC=YC11_CR IS=8YO11_SRI error when checking the update rules
Error when activating update rule AQMSG7R1YNRZWXOOWOJX9JVKF
IC=YO11_SRI IS=8YO11_ITM error when checking the update rules
Error when activating update rule DA60J5BWJ0PMB4ZWDAEESP4N4
IC=YO11_ITM IS=2LIS_12_VCITM error when checking the update rules

After Security Update 2012-01 cannot print/import/export

Yesterdag we downloaden the new Security Update 2012-01.
Now we can't print anymore.
Everytime when we are in a programm, and we want to save as/print/import/export my Mac doens't want to doe anything.
How can i fix this?

Same problem !
Please Apple fix-it quickly…

Can you help me interpret the following lines in UPDATE rule?

Hi,
Can you help me interpret the following lines in UPDATE rule?
1. What is the role of role of u201CCHANGING RESULT.u201D and u201CCHANGING lc_local_value.u201D?
2. What is the role of the CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY', in particular the Exporting and Importing parts?
3. Can I say that u201CCOMM_STRUCTURE-ORDER_VALu201D in the subroutine is passed to u201Clc_document_valueu201D in the u201CFORM loc_curr_convertu201D; and further passed to u201Cforeign_amountu201D in the u201CCALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'u201D?
4. Finally, what becomes of my original u201CActual Goods receipt quantityu201D( 0GR_QTY ) which I am writing the routine for? I donu2019t see any where in the code that it is being referred to? Do any of these codes affect the value of 0GR_QTY?
5. Also, if there are 3 different subroutines in the INCLUDE and I am making the change described in #4 above, how do I know which of the 3 subroutines to call?
===============================
===============================
So I am reviewing a transfer routine in for u201CActual Goods receipt quantityu201D and routine an INCLUDE statement: INCLUDE RS_BCT_MM_UPDATE_RULES.
The update rule also includes the following properties to run the following subroutine in the Include:
IF u2026..
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.
I verified in the INCLUDE (RS_BCT_MM_UPDATE_RULES) and the subroutine is as follows:
FORM loc_curr_convert
USING    lc_document_value
           lc_date
           lc_document_currency
           value(lc_local_currency)
           lc_rate
CHANGING lc_local_value.
conversion of lc_rate from floating-point to decimal. Necessary for *
call of CONVERT_TO_LOCAL_CURRENCY.
data lc_rate_dec type p decimals 5.
lc_rate_dec = lc_rate.
IF lc_document_currency = lc_local_currency
no conversion necessary -> Main case 1
    AND NOT ( lc_document_currency IS INITIAL
           OR lc_local_currency IS INITIAL ) .
    lc_local_value = lc_document_value.
ELSEIF NOT ( lc_document_currency IS INITIAL
OR lc_local_currency IS INITIAL OR lc_date IS INITIAL ) .
conversion necessary with lc_date -> Normally not possible
    CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
      EXPORTING
        date                 = lc_date
        foreign_amount       = lc_document_value
        foreign_currency     = lc_document_currency
        local_currency       = lc_local_currency
        rate                 = lc_rate_dec
      IMPORTING
      EXCHANGE_RATE        =
        local_amount         = lc_local_value
      EXCEPTIONS
        NO_RATE_FOUND        = 1
        OVERFLOW             = 2
        NO_FACTORS_FOUND     = 3
        NO_SPREAD_FOUND      = 4
        DERIVED_2_TIMES      = 5.
    IF sy-subrc NE 0.
message a802 with lc_date lc_document_currency lc_local_currency
                    sy-subrc.
    ENDIF.
ELSE.
if conversion not possible -> assign target values
    lc_local_value = lc_document_value.
    lc_local_currency = lc_document_currency.
ENDIF.
ENDFORM.

HI,
Thanks so much the explanations.
I just verified again on our dev system and the update rule for 0GR_QTY (Actual goods receipt quantity) include the following:
    perFORM QUANTITY_CONVERT
       USING    COMM_STRUCTURE-CPQUAOU
                COMM_STRUCTURE-po_UNIT
                COMM_STRUCTURE-base_uom
                COMM_STRUCTURE-numerator
                COMM_STRUCTURE-denomintr
       CHANGING RESULT
Now, in the include, I also found:
FORM QUANTITY_CONVERT
USING    QC_SOURCE_VALUE
           QC_SOURCE_UNIT
           VALUE(QC_TARGET_UNIT)
           QC_UMREZ
           QC_UMREN
CHANGING QC_TARGET_VALUE.
i. Does it mean it actually does quantity conversion?
ii. If you have access to the INCLUDE I will appreciate some hints on what the subroutine QUANTITY_CONVERT is doing. It does not appear do to be saying anything about quantity conversion; but it is supposed to be doing something with the parameters being passed from the update routine.
iii. In your response to #5, after all the computation in the INCLUDE, what comes back to the Update rule i.e. what comes back to become the value of 0GR_QTY?
Is it the u201CRESULT.u201D in the update rule or u201CQC_TARGET_VALUE.u201D in the subroutine in the INCLUDE.
iv. So, am to create an Update rule for 0PSTNG_DATE and the source is BUDAT; and I need to write a routine using the include INCLUDE RS_BCT_MM_UPDATE_RULES.
I looked through the INCLUDE and identified all the subroutines in this INCLUDE as follows:
QUANTITY_CONVERT
LOC_CURR_CONVERT
GET_WEEK
WEEK_DAY
QUARTER_DAY
--Does it mean that to use this subroutine, I can only use the USING parameters of one of these listed subroutines?
--Also, does it mean that because 0PSTNG_DATE is a date, I can only use one of
GET_WEEK
WEEK_DAY
QUARTER_DAY
--Or, are there other includes to be used for 0PSTNG_DATE
Thanks

BW 3.5 Update rule routine and start routine convert to BI 7.0 Endroutine.

I have bw 3.5 update routine and update rules start routine( r/3 to ODS). i need to replicate that routine into BI 7.0 endroutine with the same logic with some minor changes(DSO to DSO).
IN BW 3.5 the data is getting from r/3 where as in BI7.0 the data fetching from DSO itself but the logic is same as bw 3.5.
following is the start routine:
DATA: G_FISCPER_TO TYPE /BI0/OIFISCPER,
      G_CALMONTH   LIKE /BI0/PCALMONTH-CALMONTH,
      G_MONAT      TYPE /BIC/OIYRDFMONAT.
ABORT = 0.
------ Globale Variable füllen --------------------------------------*
CALL FUNCTION 'Y_RDF_FISCPER_FOR_INFOPACKAGE'
    EXPORTING
      I_ISOURCE    = '0FI_AA_001' (*** this is infosurce getting from r/3, in 7.0 this one is DSO 'B")
    IMPORTING
      E_FISCPER_TO = G_FISCPER_TO
      E_MONAT      = G_MONAT
    EXCEPTIONS
      OTHERS       = 1.
IF SY-SUBRC = 0.
    CALL FUNCTION 'Y_RDE_FISCPER_TO_CALMONTH'
      EXPORTING
        I_PERIV    = 'K4'
        I_BDATJ    = G_FISCPER_TO(4)
        I_POPER    = G_FISCPER_TO+4(3)
      IMPORTING
        E_CALMONTH = G_CALMONTH
      EXCEPTIONS
        OTHERS     = 1.
    IF SY-SUBRC NE 0 OR G_CALMONTH IS INITIAL.
      CALL FUNCTION 'Y_RDN_MONITOR_SET'
        EXPORTING
          I_MSGID   = 'YRDFBW'
          I_MSGNO   = '027'
          I_MSGV1   = '0FI_AA_001'
          I_MSGV2   = 'YRDF_FIAA_PERIOD'
        TABLES
          T_MONITOR = MONITOR.
      ABORT = 1.
    ENDIF.
ELSE.
    CALL FUNCTION 'Y_RDN_MONITOR_SET'
      EXPORTING
        I_MSGID   = 'YRDFBW'
        I_MSGNO   = '027'
        I_MSGV1   = '0FI_AA_001'
        I_MSGV2   = 'YRDF_FIAA_PERIOD'
      TABLES
        T_MONITOR = MONITOR.
    ABORT = 1.
ENDIF.
Update routine:
RETURNCODE = 0.
ABORT = 0.
CLEAR RESULT.
IF NOT COMM_STRUCTURE-ASSET_MAIN BETWEEN '000000200000' AND
                                           '000000299999'.
    CALL FUNCTION 'Y_RDF_GET_CCTR_0ASSET'
      EXPORTING
        I_COMP_CODE = COMM_STRUCTURE-COMP_CODE
        I_ASSET      = COMM_STRUCTURE-ASSET
        I_ASSET_MAIN = COMM_STRUCTURE-ASSET_MAIN
      IMPORTING
        E_COSTCENTER = RESULT
      EXCEPTIONS
        OTHERS       = 1.
    IF SY-SUBRC NE 0 OR RESULT IS INITIAL.
      CALL FUNCTION 'Y_RDN_MONITOR_SET'
        EXPORTING
          I_MSGID   = 'YRDFBW'
          I_MSGTY   = 'E'
          I_MSGNO   = '061'
          I_MSGV1   = COMM_STRUCTURE-COMP_CODE
          I_MSGV2   = COMM_STRUCTURE-ASSET
          I_MSGV3   = COMM_STRUCTURE-ASSET_MAIN
        TABLES
          T_MONITOR = MONITOR.
      RETURNCODE = 1.
    ENDIF.
ENDIF.
How can i write this in BI7.0?
Thanks

Hi ,
solved on my own. Thankyou very much..
thanks & regards,
M.S
Edited by: M.S on Oct 27, 2009 6:57 AM
Edited by: M.S on Oct 27, 2009 6:59 AM

Unit calculation at routine in update rule

Hello,
Can anybody explain me how to calculate unit in update rule routine.
In update rule routine how to access infocube keyfigure like we access communication structure as comm_structure.
Is there any sample code?
Please help me out.
Thanks,
Regards,
Steve

Hi,
You can find out the no of routines with standard Update rules.
one of them is :
for 'Net weight in kilograms' 2LIS_13_VDITM-->0SD_C03
IF COMM_STRUCTURE-UNIT_OF_WT NE 'KG'.
 WEIGHT = COMM_STRUCTURE-GRS_WGT_DL.
 CALL FUNCTION 'UNIT_CONVERSION_SIMPLE'
 EXPORTING
 INPUT = COMM_STRUCTURE-GRS_WGT_DL
 UNIT_IN = COMM_STRUCTURE-UNIT_OF_WT
 UNIT_OUT = 'KG'
 IMPORTING
 OUTPUT = WEIGHT
 EXCEPTIONS
 CONVERSION_NOT_FOUND = 1
 DIVISION_BY_ZERO = 2
 INPUT_INVALID = 3
 OUTPUT_INVALID = 4
 OVERFLOW = 5
 TYPE_INVALID = 6
 UNITS_MISSING = 7
 UNIT_IN_NOT_FOUND = 8
 UNIT_OUT_NOT_FOUND = 9
 OTHERS = 10.
 IF SY-SUBRC NE 0.
 CLEAR MONITOR.
 MONITOR-msgno = '009'.
 MONITOR-msgid = 'SDBW'.
 MONITOR-msgty = c_msgty_e.
 MONITOR-msgv1 = COMM_STRUCTURE-UNIT_OF_WT.
 append MONITOR.
 RETURNCODE = 4.
 WEIGHT = 0.
 ELSE.
 RESULT = WEIGHT.
 RETURNCODE = 0.
 ENDIF.
ELSE.
 RESULT = COMM_STRUCTURE-GRS_WGT_DL.
 RETURNCODE = 0.
ENDIF.
With rgds,
Anil Kumar Sharma .P

Advanced Update Rules Routine

I have a routine in my update rule that performs a lookup to another ODS. To improve my performance I would like to try writing a temporary variable to memory that can then be referenced when loading each record. For example here's some pseudo code:
1) if vendor already exists then do nothing
2) set AP key and set Purchasing key for performing lookups
(ie: AP key = Company Code + FiscalYearPeriod + AccountingDocumentNumber)
(ie: Purchasing key = Company Code + FiscalYearPeriod + PurchasingDocumentNumber)
3) does temporary AP variable exist and does it match AP key?
     3a) if yes then EXIT and return temporary AP variable
     3b) if no then perform ap lookup based on AP key
     3c) was lookup successful - was vendor found?
if yes then set temporary AP variable and EXIT and return value
if no then continue
4) does temporary Purchasing variable exist and does it match Purchasing key?
     4a) if yes then EXIT and return temporary Purchasing variable
     4b) if no then perform purchasing lookup based on Purchasing key
     4c) was lookup successful - was vendor found?
if yes then set temporary Purchasing variable and EXIT and return value
if no then EXIT (Do nothing - essentially leave blank)
My question is 1) Whether it's indeed possible to pass this temporary variable and 2) can you give me a sample of code that I would use to read/write the variable?
Thanks so much!

You can use Import/Export to cluster database. This way you can share the same variable value between different programs/routine.
EXPORT value TO DATABASE INDX(Indx) ID 'Variable Id'.
IMPORT value FROM DATABASE INDX(Indx) ID 'Variable Id'.
For more details you can refer the following:
http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb3c53358411d1829f0000e829fbfe/frameset.htm
Regards,
RB

Access master data in update rules

Hi,
I try to calculate a weight in my update rules. Therefore I need the product weight and the number of peaces. I try to read the product weight from master data. The problem is, that it always calculates zero as the result. Is it possible to read master data in update rules?
If I try to calculate the weight in the transfer rules, I get the message in the monitor, that the transfer rules don't finish. Do you have an idea what to do?
Regards,
Gabi

Hi Robert,
here is my code in the update rule.
fill the internal table "MONITOR", to make monitor entries
DATA: l_s_errorlog TYPE RSMONITOR.
data: temp_prod_weight type /BIC/PZL2_P_ID.
general values
RESULT = COMM_STRUCTURE-/BIC/ZL2_POTMW. "weight
UNIT = COMM_STRUCTURE-UNIT_OF_WT.
RETURNCODE = 0.
ABORT = 0.
calculate weight from master data, if it is zero
IF COMM_STRUCTURE-/BIC/ZL2_POTMW = 0
or COMM_STRUCTURE-/BIC/ZL2_POTMW = '0'
or COMM_STRUCTURE-/BIC/ZL2_POTMW is initial.
 select single /BIC/ZL2_NETW UNIT_OF_WT
 from /BIC/PZL2_P_ID
 into corresponding fields of temp_prod_weight
 where /BIC/ZL2_P_ID = COMM_STRUCTURE-/BIC/ZL2_P_ID
 and objvers = 'A'.
 if sy-subrc <> 0.
 l_s_errorlog-MSGTY = 'I'.
 append l_s_errorlog to MONITOR.
 RESULT = 0.
abort, if calculation is not possible
 ABORT = 1.
 else.
 RESULT = temp_prod_weight-/BIC/ZL2_NETW
COMM_STRUCTURE-/BIC/ZL2_POTMQ.
 UNIT = temp_prod_weight-UNIT_OF_WT.
 endif.
ENDIF.
convert unit
CALL FUNCTION 'UNIT_CONVERSION_SIMPLE'
 EXPORTING
 INPUT = RESULT
 NO_TYPE_CHECK = 'X'
 ROUND_SIGN = ' '
 UNIT_IN = COMM_STRUCTURE-UNIT_OF_WT
 UNIT_OUT = 'KG'
 IMPORTING
 ADD_CONST =
 DECIMALS =
 DENOMINATOR =
 NUMERATOR =
 OUTPUT = RESULT
 EXCEPTIONS
 CONVERSION_NOT_FOUND = 1
 DIVISION_BY_ZERO = 2
 INPUT_INVALID = 3
 OUTPUT_INVALID = 4
 OVERFLOW = 5
 TYPE_INVALID = 6
 UNITS_MISSING = 7
 UNIT_IN_NOT_FOUND = 8
 UNIT_OUT_NOT_FOUND = 9
 OTHERS = 10
IF SY-SUBRC <> 0.
 l_s_errorlog-MSGTY = 'I'.
 append l_s_errorlog to MONITOR.
 UNIT = COMM_STRUCTURE-UNIT_OF_WT.
 RESULT = COMM_STRUCTURE-/BIC/ZL2_POTMW.
ELSE.
 UNIT = 'KG'.
ENDIF.
I'm loading via PSA, but I have problems to debug the code. If I set a break point in my code (command break-point), I can't stop at it.
Thanks,
Gabi

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

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:
Update Rules (15199 => 0 records) : Errors Occurred
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 for 0SD_C03

Hi,
There are 6 KF in 0SD_C03 infocube which comes from update rules with routines e.g. "Subtotal 1 from Pricing Procedure in Statistics Currency". I cannot understand what the routine brings. anyone have an idea?
Thanks,
the routine is:
DATA: VALUE LIKE COMM_STRUCTURE-NET_VALUE.
DATA: US_RATE_TYPE LIKE COMM_STRUCTURE-RATE_TYPE.
CLEAR RESULT.
IF NOT COMM_STRUCTURE-SUBTOTAL_1 IS INITIAL AND
 COMM_STRUCTURE-DOC_CURRCY NE COMM_STRUCTURE-STAT_CURR.
 US_RATE_TYPE = COMM_STRUCTURE-RATE_TYPE.
 IF US_RATE_TYPE EQ SPACE.
 US_RATE_TYPE = 'M'.
 ENDIF.
ENDIF.
IF COMM_STRUCTURE-DOC_CURRCY NE COMM_STRUCTURE-STAT_CURR.
 CALL FUNCTION 'CONVERT_TO_STAT_CURRENCY'
 EXPORTING
 DATE = COMM_STRUCTURE-ST_UP_DTE
 DOCUMENT_AMOUNT = COMM_STRUCTURE-SUBTOTAL_1
 DOCUMENT_CURRENCY = COMM_STRUCTURE-DOC_CURRCY
 LOCAL_CURRENCY = COMM_STRUCTURE-LOC_CURRCY
 STAT_CURRENCY = COMM_STRUCTURE-STAT_CURR
 LOCAL_RATE = COMM_STRUCTURE-EXCHG_RATE
 STAT_RATE = COMM_STRUCTURE-EXCHG_STAT
 LOCAL_TYPE_OF_RATE = US_RATE_TYPE
 STAT_TYPE_OF_RATE = US_RATE_TYPE
 IMPORTING
 STATISTICAL_AMOUNT = VALUE
 EXCEPTIONS
 LOCAL_RATE_NOT_FOUND = 1
 STAT_RATE_NOT_FOUND = 2.
 CASE SY-SUBRC.
 WHEN 0.
 RESULT = VALUE.
 RETURNCODE = 0.
 WHEN 1.
 CLEAR MONITOR.
 MONITOR-msgno = '005'.
 MONITOR-msgid = 'SDBW'.
 MONITOR-msgty = c_msgty_e.
 MONITOR-msgv1 = COMM_STRUCTURE-DOC_NUMBER.
 MONITOR-msgv2 = COMM_STRUCTURE-ST_UP_DTE.
 MONITOR-msgv3 = COMM_STRUCTURE-DOC_CURRCY.
 MONITOR-msgv4 = COMM_STRUCTURE-LOC_CURRCY.
 append MONITOR.
 RETURNCODE = 4.
 WHEN 2.
 CLEAR MONITOR.
 MONITOR-msgno = '006'.
 MONITOR-msgid = 'SDBW'.
 MONITOR-msgty = c_msgty_e.
 MONITOR-msgv1 = COMM_STRUCTURE-DOC_NUMBER.
 MONITOR-msgv2 = COMM_STRUCTURE-ST_UP_DTE.
 MONITOR-msgv3 = COMM_STRUCTURE-DOC_CURRCY.
 MONITOR-msgv4 = COMM_STRUCTURE-STAT_CURR.
 append MONITOR.
 RETURNCODE = 4.
 ENDCASE.
ELSE.
 RESULT = COMM_STRUCTURE-SUBTOTAL_1.
ENDIF.
IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
 RESULT = RESULT * ( -1 ).
ENDIF.

Is the question what are the subttoal 1-6 or what does the routine do?
Sub totals 1-6 are user defined fields in the SD pricing block - if the SD consultants haven't already used them for their purposes it is a good idea to use them to denote surcharges etc that you want in BW (without having to use the condition extractors or user exits to get the sales order breakdown)
What does the routine do?
Exchange rate conversion then multiple by -1 if it is a credit note (or similar)

Using "Master Data Attribute of" in the Update Rule

Hi,
In my update rule of, i want to replace the master data attribute of my characteristic instead of using its source characteristic. For example. InfoObject ZSTORECODE has an attribute ZSTORENAME. My objective is to use the Store Name instead of a Store Code.
I initially thought of using "Master Data Attribute of" in the update rules. However, I always end of with having an error of "No Values."

Hope you guys can help me with this!
Thanks,
Raomon

DATA: V_NSTC_SN2,
V_KFC_COSTC LIKE RSGENERAL-CHAVL.
V_KFC_COSTC = DATA_PACKAGE-KFC_COSTC.
CALL FUNCTION 'RSAU_READ_MASTER_DATA'
 EXPORTING
 I_IOBJNM = 'KFC_COSTC'
 I_CHAVL = V_KFC_COSTC
* I_T_CHAVL =
* I_DATE =
* I_FLG_WHOLE_TABLE =
 I_ATTRNM = 'NSTC_SN2'
IMPORTING
* E_STRUCTURE =
* E_TABLE =
 E_ATTRVAL = V_NSTC_SN2
 EXCEPTIONS
 READ_ERROR = 1
 NO_SUCH_ATTRIBUTE = 2
 WRONG_IMPORT_PARAMETERS = 3
 CHAVL_NOT_FOUND = 4
 OTHERS = 5
RESULT = V_NSTC_SN2.
Another Example Code:
index on infoObject

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

Fields missing in Update rules

I am creating snap shot DSO for inventory management and after that i created the update rules for it linking it to the info source 2LIS_03_BX. When i do this i am missing the info objects that i created to include in the DSO. How do i solve this issue as those info objects are very important and i have to create the routines for it.
I have got the units for those fields and they are mapped but the info objects itself are missing.
Thanks for any help in advance
Naveen

HI Naveen,
Yes, you can include the missing infoobject in DSO. for that you need to follow bellow steps:
a). Delete the data from DSO.
b). you have to include the infoobject in DSO.
Double click on DSO>select chage mode->select keyfield /data field node--->right click select Infoobject Direct Input.
c). Activate the DSO
Brief Description about 2LIS_03_BX :
The 2LIS_03_BX is used to extract an opening stock balance on a detailed level (material, plant, storage location and so on). At this moment, the opening stock is the operative stock in the source system. "At this moment" is the point in time at which the statistical setup ran for infosource 2LIS_03_BX.Loading the opening stock balance InfoSource 2LIS_03_BX into data target.In the InfoPackage, choose the upload mode u201CCreate opening balanceu201D.
Regards,
Suman.

Update rules import/export

Similar Messages

Maybe you are looking for