Update Routine & Start Routine in BI 7.0

Hi Experts,
We have recently upgraded from BI 7.0 , I am confused about where to write start routine & update routine in transformations of BI 7.0?
Please mention any pointers?
Thanks.
Sharat.

Hi
When you open the start routine you will see a routines info which gives you help on this.
A summary would be:
Update routine in transformation.
RESULT = source_field-material.
Basically you can acess the value of the record by using source_field.
Start routine.
The data comes in the form of an internal table with name SOURCE_PACKAGE.
You can access the values by looping into a work area.
LOOP AT SOURCE_PACKAGE assigning <source_fields>.
ENDLOOP.
End routine(This is a new feature in BI 7.0 where you can modify data when transformations are complete and before data is updated to info-providers)
The data comes in the form of an internal table with name RESULT_PACKAGE.
You can access the values by looping into a work area.
LOOP AT RESULT_PACKAGE assigning <result_fields>.
ENDLOOP.
Hope this helps you to understand the basics of the abap used in the transformations .
Regards
Samarpita

Similar Messages

Is difference between update routine,start routine and transfer routine

Hi All,
What is difference between transfer routine and update routine.

Hi Venkat,
Routine is a set of ABAP code which is used to select a record or transform the field value at the time of loading the data.
Types of routines:
Tranfer Routines in Transfer Rules:
Start Routines in Transfer Rules:
Update Routines in Update Rules:
Start Routines in Update Rules:
Transfer/Update routine:
It's the set of ABAP code used in Transfer/Update rules. Transfer/Update routine is used to change the value of a particular field/object at the time of loading data.
Ex: Populate the amount/discount field by using Price and Quantity based on the given conditions.
Start Routine:
Start routine can be used in both Transfer Rules and Update Rules. Start routine is used to determine whether to load a particular record or not.
Ex: From the data related to the year 2005, we can select only the records which belong to a particular month or fiscal period.
Ultimately Transfer/Update routines are to update the value of a particular field. Start routines are used to select entire record.
You can get more details about routines at :
Routines
ROUTINES
Routines and Examples
Start Routines
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/60cecb1d-0a01-0010-8289-b14fd99062fa
take a look this doc for abap used in bw
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4493c4a6-0301-0010-62a2-efd6ded61e04
ABAP book that always mentioned :
http://cma.zdnet.com/book/abap/
assign points if useful ***
Regards
CSM Reddy

How to determine InfoCube name within the update rule start routine?

We are attempting to delete all the records where all key figure values are zeroes. We have about 15% of such records and we really don't need them.
We have yearly InfoCubes. We copy the InfoCube and update rules at the end of every year. So, we don't want to hard code any field names within the update rules.
If I could determine the target InfoCube name within the update rule start routine, I can find out all the key figures dynamically. But, I don't see a way of finding out the InfoCube name.
If you would share any ideas, I would really appreciate.
Thanks.
Sudhi Karkada.

Hi Sudhi,
I dont know if this is what you are looking for.
if you want to delete a record from being inserted when all the Key figure values are ZERO then you can use a Update Routine for some characteristic in the below way
If looking for the InfoCube:
if COMM_STRUCTURE-KF1 = 0 and COMM_STRUCTURE-KF2 AND....
RETURNCODE = 4.
else
RESULT = COMM_STRUCTURE-ChanracteristicObject.
endif.
If it is to an ODS / InfoCube in the start routine.
DELETE DATAPACKAGE where KF1=0 and kf2=0 and .....
Hope it helps.
Regards,
Praveen.
ENDLOOP.
Message was edited by: Praveen

Calculations in Update rules/Start routine/End Routine

Hi Friends,
I have loaded data to a DSO and i have three fields in to it. Lets say Filed1, Filed2 and Field3. Field1 and Field2 are being populated through an update rule in transformation. Aggregation type for these two fields are "Summation".
Now, after the transformation executed, the Field1 and Field2 are filled with values. I want to calculate the value of Field3 as follows:
Field3 = Field1 - Field2
Can anyone tell me where can i do this calculation? I know we can do this in End routine and in Query but i want to know if there is any other place i can do this calculation in transformation? In try to do this calculation in the update rule for Field3 in transformation, i dont see Field1 and Field2 as these are not source fields. I can not write formula also because we can write formula only on source fields not the data target fields.
Your help will be appreciated in terms of points.
Thanks,
manmit

Hi,
in the start routine in the global section define the two fields:
data: g_amount1 type /bic/oi<your keyfigure name>,
g_amount2 type /bic/oi<your keyfigure name>.
in the routines to your 2 keyfigures store the result in that fields too.
routine for field1.
g_amount1 = result.
routine for field2.
g_amount2 = result.
and in the routine to field3
result = g_amount1 - g_amount2." or whatever calculation/derivation has to be done.
kind regards
Siggi
Message was edited by:
Siegfried Szameitat

BW 3.5 Start Routine Start Routine Code

Hi,
I am writing a Start Routine in BW 3.5 and the logic we have seems to be working but not updating the target ods. We are adding a date field to the target ODS and need to source it from another ODS. The key structures for each ods is different
Taget ODS:
Header
Line ITem
Schedule Line
Source ODS:
Header
Line Item
When we run the start routine the date field will not update for the schedule lines, it will create a new record in the target ods with the Header Line ITem and Date.
Has anyone had to code this logic before in a 3.5 Start Routine, where you needed to update a date field with ODS with different key strucutures.
Thanks for any help on this issue.

Its difficult in BW 3.5 to include this logic in START_ROUTINE as you cannot add the extra to_date field to the DATA_PACKAGE table.
You need to create a new global internal table with the same structure of DATA_PACKAGE with additional field to_date. then use the logic to fill in the global internal table
define a internal table new_data_package with the required structure like (docno, eventtype, fromdate todate)
data: l_w_datapkg_001 type data_package,
data: l_w_newdatapkg type new_data_package,
data: l_w_datapkg_011 type data_package
LOOP AT DATA_PACKAGE INTO l_w_datapkg_001 WHERE event_type = '001'.
l_w_newdatapkg-docno = l_w_datapkg_001-docno.
l_w_newdatapkg-event_type = l_w_datapkg_001-event_type.
l_w_newdatapkg-fromdate = l_w_datapkg_001-date.
MOVE CORRESPONDING FIELDS OF l_w_datapkg_001 INTO l_w_newdatapkg.
READ TABLE data_package INTO l_w_datapkg_011
WITH KEY docno = l_w_datapkg_001-docno
event_type = '011'.
l_w_newdatapkg-to_date = l_w_datapkg_011-date.
APPEND l_w_newdatapkg TO new_data_package
ENDLOOP.
Now the new datapackage contains the ODS2 data that u needed

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

Calculate working dates - start routine or characteristic routine?

Dear all
I need to fill key figure with number of working dates in transformation
There is a key figure START_DATE in and I need to populate WORK_DAYS like CURRENT_DATE - START_DATE excluding holidays and weekends
I checked this thread and read some sample code:
/message/10006808#10006808 [original link is broken]
But where I need to add sample code of working days calculation - in start routine and characteristics routine or only at characteristic routine?

Hello there,
In the characteristic routine.
start routine will be executed before the characteristic assignment, and is better for instance to add records or remove records, etc. The characteristic assignment comes after with characteristic routines, and for each record this assignment and characteristic routine is done. If you have already the START_DATE and CURRENT_DATE you can proceed with the calculation on each record (with the characteristic routine assignment).
Hope this helps,
Regards,
Diogo

Start Routine in Update Rule

I want to replace all '# ' values showing up in a report with space. For this I plan to write a Start Routine in the Update Rules which should scan all the data coming in into the cube and replace all null or '' with space.
What is the best way to write this routine. It should check all data in all the fields of the data load coming in.
Thanks

Hi,
     The space is shown as # in the BW Reports, to confirm check the value in the cube for this field, so
      you need to change that to some other character like X or Y or explain your end users that SAP
      designates a space as # and it will be displayed that way in the reports.
Regards,
Raj

Start routine to update some fields of a ODS based on the another ODS

Hi I know i have to do abap coding at the start routine to update a ODS based on another ODS. I have tried doing the code for quite some time now and i have not been successful. I think I havenu2019t followed the definition required for this routine.
I have 2 ODS, ODS1 has 3 key fields and ODS2 has 1 key field
I have to map the ODS based on a 1:3 relation.
I am writing this start routine for the update rules from ODS2 to ODS1.
The logic is if the key field of ODS2 is equal to either Key field 1 or Key field 2 or Key field 3 of ODS1 then that record from ODS2 has to be updated to the corresponding matching record of ODS1, else no update. The 3 key fields of ODS1 have different character length and character types and the key field of ODS2 has a different character length and type when compared to the any of the key fields of ODS2 can match any of those.
Like key field 1 of ODS1 has length 10. Key field 2 of ODS1 has length 10 and key field 3 of ODS1 has length 20 and all these fields are not alpha converted, but the key field of ODS2 has length 60 and it is alpha converted.
Can anyone please help me in this code.
My Code is as below.
ITAB1-T_BOL = DATA_PACKAGE-/BIC/ZLBOL.
***********NISTEVO SELECT******************************
SELECT /BIC/ZLBOL FROM /BIC/AWLONST0100 INTO ITAB1-T_BOL
              WHERE /BIC/ZLBOL = ITAB1-T_BOL .
**************R/3 SELECT*******************************
    SELECT /BIC/ZLRDELNU /BIC/ZLRSHIPNU /BIC/ZLREXTID
              FROM /BIC/AWLOR3O0400
              INTO CORRESPONDING FIELDS OF ITAB1
              WHERE
              /BIC/ZLRDELNU = ITAB1-T_BOL OR
               /BIC/ZLRSHIPNU = ITAB1-T_BOL OR
               /BIC/ZLREXTID = ITAB1-T_BOL .
      SORT ITAB1 BY T_DELNU T_SHIPNU T_EXTID .
      LOOP AT DATA_PACKAGE.
        READ TABLE ITAB1 WITH KEY T_DELNU = DATA_PACKAGE-/BIC/ZLBOL.
        IF SY-SUBRC = 0.
          EXIT.
        ENDIF.
        READ TABLE ITAB1 WITH KEY T_SHIPNU = DATA_PACKAGE-/BIC/ZLBOL.
        IF SY-SUBRC = 0.
          EXIT.
        ENDIF.
        READ TABLE ITAB1 WITH KEY T_EXTID = DATA_PACKAGE-/BIC/ZLBOL.
        IF SY-SUBRC = 0.
          EXIT.
        ENDIF.
        DELETE DATA_PACKAGE .
      ENDLOOP.
    ENDSELECT.
ENDSELECT.
Points will be awarded.
Edited by: satish rajaram on Nov 6, 2008 4:51 PM
Edited by: satish rajaram on Nov 7, 2008 11:40 AM
Edited by: satish rajaram on Nov 7, 2008 11:43 AM

The logic is if the key field of ODS2 is equal to either Key field 1 or Key field 2 or Key field 3 of ODS1 then that record from ODS2 has to be updated to the corresponding matching record of ODS1, else no update. The 3 key fields of ODS1 have different character length and character types and the key field of ODS2 has a different character length and type when compared to the any of the key fields of ODS2 can match any of those.
Can you try below logic :
Below is not code it needs to be manipulated as per requirement.
ODS2 ---> ODS1
SELECT <key fields of ODS1>
FROM /BIC/A<ODS1>00
INTO ITAB
FOR ALL ENTRIES IN DATA_PACKAGE
WHERE
keyfield1 = data_package-key1
or
keyfield2 = data_package-key2
or
keyfield3 = data_package-key3
**Now itab has all entries which neednot be deleted from data_package.****
if sy-subrc=0.
***Check Itab and delete only those records not present in itab from data_package****
endif.
Hope this helps.

How to debug start routines of update rules from ODS to InfoCube

Dear gurus,
I have an update rule from ODS to InfoCube. I wrote a start routine in the update rule. Now I want to debug it. I went to monitor and simulate update the data package and only got the prompt "No data exists in the corresponding PSA table". So how can I debug this start routine?
Thanks in advance.
Jin Ming

Jin,
In order to use PSA between ODS and InfoCube, you may have to use an exclusive InfoPackage and load separately. In that InfoPackage, choose the radio button to use a PSA.
I think you are currently updating the InfoCube directly without using a separate InfoPackage.
Look for an InfoSource under DataMarts (search for 8<ODS Technical name>) and create your InfoPackage there.
Good luck.

Deleting rows with missing values in field in start routine of update rule

Hello experts,
how can I delet rows with missing values in a specific field in the start routine of update rules?
I think ABAP code should look something like this:
delete ... from DATA_PACKAGE where Z_NO = ''.
thanks in advance for any suggestions!
hiza

Write:
delete data_package where field = value.
Hope it helps.
Regards

ABAP Help at start routine of Update rule

Good After Noon All,
My requirement is that cube ZAPO_C24M theres an UPDR flowing from 8ZAPO_C24M back to itself so to speak.The request is to change the data in the cube from Fiscal Year Variant Z3 to Z4.
But in start routine i have to take the existing record and reverse all of the key figures, and also change the RECORDMODE of the record to indicate it is a reversal record. This for specific Country KR and for these country the Fiscal variant is Z3. Again in the start routine, create a new record identical to the existing record that has Fiscal Year Variant Z4 instead of Z3.
So the idea is wed load from the cube and send back to the cube one record that reverses out the existing data, and another record that contains the same data but with Fiscal Variant Z4 instead of Z3.
Please Help me.
Points will be awarded for the right answer

Hi Vaishali,
In the start routine copy the DATA_PACKAGE to a local table.
Select the records where the specific country is KR.
Delete all other records.
Then read the records in loop, Keep one record same and just change the fiscal year variant.
And for the same multiply all the key figures by -1.
Transfer the content of the local table back to DATA_PACKAGE.
maintain one to one mapping in the update rule.
I am sure it will update, but you need to be sure that if you change Fiscal year variant then probably your fiscal period value should change. In that case you have to update it accordingly in the start routine.
Regards.

How to get used InfoPackage name in SAP BW 3.5 in update/ start routine?

Hello Experts,
according to the Infopackage (weekly load ord monthly) the update rule should change.
In BI 7.0 helps the method P_R_REQUEST. Is there any similar for BW 3.5? =Or is there a possiblility to get the request nr in the startroutine with accordant mapping table to InfoPackage?
Best regards,
Stephan Wagner

Hi Experts,
thank you for your answers. Now, I have got the mapping table InfoPackage/ Request-ID.
But, how can I get the actual Request ID in the start routine in BW 3.5?
The tables MONITOR and MONITOR_RECNO don´t store it and they needs to be filled.
MONITOR_RECNO
MSGID
MSGTY
MSGNO
MSGV1
MSGV2
MSGV3
MSGV4
DETLEVEL
RECNO
MONITOR
MSGID
MSGTY
MSGNO
MSGV1
MSGV2
MSGV3
MSGV4
DETLEVEL
Best Regards,
Stephan

ABAP assistance - start routine logic in update rule

I have used an existing update rule and have based my logic around the same. The purpose of the rule is to look up customer master data and get a subset of customer numbers from the transaction records so that the values for customer number from the transactional data will not be updated if it does not match with existing master data customer numbers.
The loads are full and we drop the data before we load.
I have listed the logic below (the number at the front is to be considered as the line number) and a list of open questions that I have thereafter:
Start routine logic:
1 DATA: l_index LIKE sy-tabix.
2 DATA: BEGIN OF ls_customer,
3        customer TYPE /BI0/OICUSTOMER,
4        objver TYPE RSOBJVERS,
5     END OF ls_customer,
6      lt_customer LIKE TABLE OF ls_customer.
7 REFRESH: lt_customer.
8 LOOP AT DATA_PACKAGE.
all customers from data package
9    ls_customer-custno = DATA_PACKAGE-custid.
10 ls_customer-objver = 'A'
11    APPEND ls_customer TO lt_customer.
12   ENDLOOP.
12 SORT lt_customer.
13 DELETE ADJACENT DUPLICATES FROM lt_customer.
14   IF NOT lt_customer[] IS INITIAL.
15    SELECT /BI0/OICUSTOMER RSOBJVERS
16      FROM /BI0/PCUSTOMER
17      INTO CORRESPONDING FIELDS OF TABLE lt_customer
18      FOR ALL ENTRIES IN lt_customer
19      WHERE ls_customer-custno = DATA_PACKAGE-custid
20      AND ls_customer-objver = 'A'
21    SORT lt_customer BY customer ASCENDING
22 ENDIF.
Questions
Line
1 - what is the purpose of this line? What is it that is being declared
2 - in some code I have seen this line with OCCURS 0 at the end what does this mean with and without the term?
4 - I am using the Data Element name is this correct or should I use the field name?
3 - 5 here I declare an internal structure/table is that correct?
6 - here I declare a work area based on the internal table is that correct?
7 - What would happen if I avoided using the REFRESH statement?
8 - 12 - Is this syntactically correct, I am trying to get a set of data which is the customer numbers which match the master data customers and the master data record is án active version and than appendíng to the work area?
13 - My understanding is this will reduce the number of records in the work area is this correct and needed?
14 - 22 I am trying to identify my required set of data but feel I am repeating myself, could someone advise?
Finally what logic would I actually need to write in the key figure object, could I use something like:
Result = lt_customer.
Thanks
Edited by: Niten Shah on Jun 30, 2008 8:06 PM

1. This line is not required
2. OCCURS 0 is the OLD way of defining an internal table with that structure. As it is, it just defines a flat structure.
3. Data element is usually best
3-5 Yes
6. No. Here you are declaring a table of the type of the flat structure. Just as the ABAP says!
7. Nothing. But by putting this in, you ensure that you know the state of the table (empty) before you start looping through the data package
8-12. You can tell if it is syntactically correct by pressing Ctrl-F2 when in the editor. Looks ok.
13. Ensures your list of customers contains no duplicated. The code up to this point is building a list of all the unique customers in the data package.
14-22. Goes to the database and brings back ONLY those customers which are found in the master data. Looks ok.
This is a start routine (that's why you've got a data package). You don't use result. You should update the datapackage. But this you haven't done. Double click on the table name /BIC/PCUSTOMER to get the correct field names.
So you have to loop through the data package again, and check if the customer in the datapackage is lt_customer. If it is, fine, otherwise you blank it and report an error, or set an error message or whatever.
I wouldn't do it like this. I'd do something like this:
STATICS: st_customer TYPE HASHED TABLE OF TYPE /bi0/oicustomer
                              WITH UNIQUE KEY TABLE_LINE.
* st_customer retains its value between calls, so only populate if empty
* In one run of the infopackage, this will mean you do only one read of
* the master data, so very efficient.
IF st_customer IS INITIAL.
SELECT customer FROM /BI0/PCUSTOMER
                          INTO TABLE st_customer
                          WHERE objvers EQ 'A'. " Only active values
ENDIF.
* Go through data package
LOOP AT DATA_PACKAGE.
* Check whether the customer exists.
READ TABLE st_customer TRANSPORTING NO FIELDS
              WITH TABLE KEY table_line = DATA_PACKAGE-custid.
CHECK sy-subrc IS NOT INITIAL.
* If you get here, the customer isn't valid. So I'm just setting it blank
CLEAR DATA_PACKAGE-custid.
MODIFY DATA_PACKAGE. " Updates the datapackage record
ENDLOOP.
Even this is not fully optimised, but it's not bad.
I strongly suggest that you get yourself sent on the basic ABAP programming course if you're going to do a lot of this. Otherwise, read the ABAP documentation in the help.sap.com, and, from the editor, get the cursor on each ABAP keyword and press F1 to read the ABAP help.
matt

How to get the PSA name in a Start Routine in the Update Rules of a Cube.

Hi all.
I have an InfoSource that loads data directly in an Infocube.
In the Start Routine of the Update Rules I need to retrieve the PSA table name for that InfoSource, to access it and check some data.
I can't use the PSA name you seen in the DataFlow because it will change once the update rules are transported to another system.
Please advice.
Thanks!!!

Hi,
we do it as follows:
first get the request ID:
DATA: tp_request(30) VALUE 'REQUEST'.
FIELD-SYMBOLS: <wa> TYPE ANY, <tp_req> TYPE ANY, <tp_dtp> TYPE ANY.
READ TABLE datapak ASSIGNING <wa> INDEX 1.
IF sy-subrc <> 0. ABORT = 4. ENDIF.
ASSIGN COMPONENT tp_request OF STRUCTURE <wa> TO <tp_req>.
IF sy-subrc <> 0. ABORT = 4. ENDIF.
requnr = <tp_req>.
then we get the table with
SELECT odsname_tech FROM rstsodspart WHERE request = requnr.
you may need to adjust this code, I've just pasted the relevant parts...
another way is to get this info from RSTSODS where the different versions are maintained...
let me know if you need further detail about this stuff...
hope this helps...
Olivier.
Message was edited by:
Olivier Cora

Update Routine & Start Routine in BI 7.0

Similar Messages

Maybe you are looking for