This is a simple document which gives step by step method of how to create a logical filename which can be used to generate file in an application server.

Where it can be used: we can use these logical filenames in Open HUBS, APDs.

Step 1: Go to FILE transaction.

            First the logical file path needs to be created.

Step 2: The next step follows assignment of the physical path to logical file path created in step 1.

In the above image you can see syntax group which is Key for a group of operating systems with a common syntax for file and
path names.

In the physical path it is mandatory to specify <FILENAME> which is a reserved word as a placeholder for the file name. Without the reserved word it will throw an error

There are many other reserved words available. You can give extension as per the requirement.

Step 3: In the final step you need to create logical file name which will be used in open HUBS or APDs.

            - need to specify Logical File which is a platform-independent name for a file to be stored in the file system.

            - physical file name created in step 2

            - Logical path name created in step 1

the highlighted Logical File is the name which you pass in your Open HUBS or APDs.

Business Content is nothing but a collective term for the pre-configured objects which is provided by SAP . Business content has almost all the objects which can be relevant for business warehouse. It speed up the implementation in SAP business ware house.

Step by step procedure to install objects  from Business content. Here I am taking an example of Info Objects.

SAP Recommend us to install the objects from business content in two cases:-

• After a Content release upgrade
• After installing a Content Support Package

But it can also be useful in case of migration / Carve out project. Where instead of moving all the objects from existing system to new system , We can install the 0objects(System Provided) from business contents.

1. Go to T code RSA1 in BW System or Modeling from the SAP Menu.

2. Choose  Business Content.

3. Assign Relevant source System

4. Object Type :- By choosing the object type we are getting ensured that the objects in the next frame will be categorised by types of objects.

For example infoObjects, Query,InfoCube etc.

5. Info Object

Here as i am taking an example of infoObjects so i will go to infoObjects in the middle area of the screen and then i will click on select object . And i can search or select our required objects from the list.

6. Select your required Info Object and the click on transfer button to move it to the 3rd frame.Here we can select as many info Objects as required. It can be of any no.

7. Now check Grouping , Collection mode & Display.

Grouping - We can be ensured about the related objects which is required along with the main objects. Here i am taking a case where i required only necessary objects. So grouping will be as Only necessary objects.

Collection mode - are of 2 types one is Automatic and other is manual. I am taking it here automatic collection

Display- are of two types hierarchy & List . We can take it as per our convenient. List is more preferable .

10. Correct Errors if there is any. We can check this by clicking on install stimulation. It gives info about errors n warning if there is any.

11. Install.

After checking the stimulation. We can install the required object.By clicking on install icon. Now the installed object will be active in RSA1 of the system.

And the object is installed. After installing the objects the status will change to green. For Example 0Material. Similarly for other objects also the status will change to green from grey  after installing.

Thanks,

Note:- The object used in the screen if just for refrence. Here the 0material wa already installed in the system.

BI Content 737/747 SP10 + BI Content 757 SP03 released to customers

The latest BI Content support packages have now been released to customers:

• BI Content 7.37 SP 10
• BI Content 7.47 SP 10
• BI Content 7.57 SP 03

Read what's new with BI Content 7.37/7.47  SP10 + 7.57 SP03.

For content release details please see the following:

• BI Content Release Strategy Note: 153967
• BI_CONT 737/747 Add-on SP Note: 1808103.
• BI_CONT 757 Add-on SP Note: 1985663.

Posted date: September 03, 2014

SAP HANA-Optimized BI Content delivered to customers

SAP HANA-optimized BI Content combines enterprise data warehouse capabilities of SAP BW running on SAP HANA with explorative and interactive real-time analytics using the SAP HANA in-memory database. The new data model follows the recommendations for the layered scalable architecture LSA++, which is optimized for SAP BW running on SAP HANA.

SAP delivered for the first time SAP HANA-optimized BI Content in the following business areas

• SAP ERP Financial Accounting – Accounts Receivable
• SAP ERP Financial Accounting – Accounts Payable
• SAP ERP Financial Accounting – General Ledger
• SAP ERP Enterprise Controlling – Profit Center Accounting
• SAP ERP Sales and Distribution
• SAP SCM Procurement
• SAP SCM Invoice Verification
• SAP ERP Controlling – Product Costing Forecast & Simulation (SCN Blog)

This BI Content is included in the latest BI Content support packages that are released to customers:

• BI Content 7.37 SP 04, SP 05, SP 06, SP07
• BI Content 7.47 SP 04, SP 05, SP 06, SP07
• BI Content 7.57 SP 00

Read more about SAP HANA-optimized BI Content: Overview Presentation, Online Documentation

Updated date: March 06, 2014

"NEW" BI Content 757 SP 00 now available for NW7.40-SR1 (SPS05 and higher).

A new BI Content release also the software component version 'SAP Netweaver 7.40 BI Content Add-on 7.57' has now been released for NW7.40-SR1 (SPS05 and higher):

• Following new Software Component Versions are now available for NW7.40-SR1:
  • SAP Netweaver 7.40 BI Content Add-on 7.57 SP00
  • BI Content Extension for BI Content 7.57 SP00

For details please see the following:

• BI Content Release Strategy Note: 153967
• BI_CONT 757 Installation/Upgrade Note: 1943931
• NW740-SR1 Master Guides:
  • Installation: Read Chapter:3.1 (on Page 43)
  • Upgrade: Read Chapter: 4.1.2.2 (on Page 52)

Read what's new with BI Content 7.57 SP 00.

Posted date: December 19, 2013

Business Content is nothing but a collective term for the pre-configured objects which is provided by SAP . Business content has almost all the objects which can be relevant for business warehouse. It speed up the implementation in SAP business ware house.

Step by step procedure to install objects  from Business content. Here I am taking an example of Info Objects.

SAP Recommend us to install the objects from business content in two cases:-

• After a Content release upgrade
• After installing a Content Support Package

But it can also be useful in case of migration / Carve out project. Where instead of moving all the objects from existing system to new system , We can install the 0objects(System Provided) from business contents.

1. Go to T code RSA1 in BW System or Modeling from the SAP Menu.

2. Choose  Business Content.

3. Assign Relevant source System

4. Object Type :- By choosing the object type we are getting ensured that the objects in the next frame will be categorised by types of objects.

For example infoObjects, Query,InfoCube etc.

5. Info Object

Here as i am taking an example of infoObjects so i will go to infoObjects in the middle area of the screen and then i will click on select object . And i can search or select our required objects from the list.

6. Select your required Info Object and the click on transfer button to move it to the 3rd frame.Here we can select as many info Objects as required. It can be of any no.

7. Now check Grouping , Collection mode & Display.

Grouping - We can be ensured about the related objects which is required along with the main objects. Here i am taking a case where i required only necessary objects. So grouping will be as Only necessary objects.

Collection mode - are of 2 types one is Automatic and other is manual. I am taking it here automatic collection

Display- are of two types hierarchy & List . We can take it as per our convenient. List is more preferable .

10. Correct Errors if there is any. We can check this by clicking on install stimulation. It gives info about errors n warning if there is any.

11. Install.

After checking the stimulation. We can install the required object.By clicking on install icon. Now the installed object will be active in RSA1 of the system.

And the object is installed. After installing the objects the status will change to green. For Example 0Material. Similarly for other objects also the status will change to green from grey  after installing.

Thanks,

Note:- The object used in the screen if just for refrence. Here the 0material wa already installed in the system.

Hi All,

While working on Invoice Verification i identified business content data source available for TRCS 2LIS_06_INV -> ODSO 0LIV_DS01 but not available for  RSDS 2LIS_06_INV -> TRCS 2LIS_06_INV we need to do manual mapping .

I suggest below list will help you for quick mapping.

Thanks

Applies to:

SAP NetWeaver Business Warehouse (formerly BI) - SAP BW 3.5 & 7.x. Versions.

Summary:

The article explains the step by step procedure for the DataSource Enhancement without using ABAP Code for the standard FI_GL/AR/AP extractors.

Table of Contents:

1. Introduction

2. Test Scenario for adding the extra fields of base table into the standard 0FI_GL_4 extractor

3. Describing the Test Scenario

4. Related content

Introduction:

In many BW Projects, we have seen that most of the time we need to enhance the standard FI_GL/AR/AP extractors and pull the data for additional fields of the base/origin tables. In this scenario, enhancing the 0FI_GL_4 DataSource and adding the extra fields from the BSEG table. Since the extra/additional fields are not available in the standard extractor.

Test Scenario:

Below are the simple steps to achieve the DataSource Enhancement without ABAP code.

The DataSource 0FI_GL_4  has already the standard INCLUDE "CI_BSIS" is available in the standard structure. Likewise, we can add/append the additional fields from their base table for the following Extractors using Customer Include.

Note: In this case we don't need to write any ABAP Code for pulling the data for the extra/additional fields. Since we are pulling the data from the base/origin table of the Extractor.

Now adding the two fields in the extract structure from the BSEG table below.

Go to T-Code: RSA6

Select the DataSource and go inside the extract structure.

Then,

Select the include "CI_BSIS" and

Add the MATNR & MENGE fields from BSEG Table.

After adding the MENGE field in the structure, probably you will face a following error.

"CI_BSIS-MENGE (specify reference table AND reference field)"

To overcome from this error we need to specify reference tables and reference fields for the fields which containing the currencies, amounts or quantity etc...

The Structure/Table name would be the same if unit or currency field is already available in the table. If not, then define for example:
ZZMEINS and refer it to standard MEINS (which is a standard domain).

Or refer to original/base Structure/Table:

Again Go to: RSA6 and select the DataSource in edit mode.

Unchecked the additional fields, which is newly added in the structure.

Save & Activate the DataSource.

Go to: RSA3 and Extract the Data.

Replicate/Import the DataSource in the BW/etc. Targets  (Destination) and load the data into respectively Data Targets.

Related content:

https://scn.sap.com/

https://help.sap.com/

Applies to:

SAP NetWeaver Business Warehouse (formerly BI) - SAP BW 3.5 & 7.x. Versions.

Summary:

The article explains the step by step procedure for DataSource Enhancement using ABAP Code for FI_GL/AR/AP Extractors through Business Transaction Event (BTE).

Table of Contents:

1. Introduction

2. Test Scenario for adding the extra fields into the standard 0FI_GL_4 extractor

3. Describing the Test Scenario

4. Related content

Introduction:

In many BW Projects, we have seen that most of the time we need to enhance the standard FI_GL/AR/AP extractors and pull the data apart from the base/origin tables on certain Business logic/requirement. In this scenario, enhancing the 0FI_GL_4 DataSource and adding the extra fields from the EKKO, EKPO, MEBW tables.

Test Scenario:

Following are the simple steps to achieve the DataSource Enhancement through BTE.

Below details of extra fields.

Fields:

Vendor:                   EKKO-LIFNR                   into                ZZGR_LIFNR           (Extractor Field)

Plant in Stock:        EKKO-RESWK                into                ZZGR_RESWK         (Extractor Field)

Receiving Plant:     EKPO-WERKS                into                ZZGR_WERKS         (Extractor Field)

PO Quantity:          EKPO-MENGE               into                ZZGR_MENGE        (Extractor Field)

PO Price:                 EKPO-NETPR                 into                ZZGR_NETPR          (Extractor Field)

Standard Price:      MBEW-STPRS               into                ZZGR_STPRS           (Extractor Field)    

Now Go to T-Code: RSA6 and select the DataSource.

Select the DataSource and go inside the extract structure.

Then,

Select the include "CI_BSIS"

Append the additional fields.

Note: Don't forget to specify the reference table (DTFIGL_4/CI_BSIS) and reference fields for Quantity, Currency and Unit field.

Or

Again, Go to: RSA6 and select the DataSource in edit mode.

Unchecked the additional fields, which is newly added in the structure.

Save & Activate the DataSource.

Now Coding Part to populate the data through BTE.

Go to T-Code: SE80 and copy the standard Function Module (Template) "SAMPLE_PROCESS_00005021" from the Function Group "BFFMSMPL3" with a new name for example:

Then Go to: SE37 and open the FM in edit mode ZBWFI_FILL_CI_00005021.

Write the code in Source code Tab:

"Details from EKKO:Purchasing Document Header

          SELECT  SINGLE          lifnr AS zzgr_lifnr

                                                reswk AS zzgr_reswk

          INTO  CORRESPONDING FIELDS OF <fs_dtfigl_4>

          FROM  ekko

          WHERE      ebeln = wa_bseg-ebeln.

"Details from EKPO:Purchasing Document Item

       SELECT  SINGLE           werks AS zzgr_werks

                                               menge AS zzgr_menge

                                               netpr AS zzgr_netpr

          INTO  CORRESPONDING FIELDS OF <fs_dtfigl_4>

          FROM  ekpo

          WHERE      ebeln = wa_bseg-ebeln

               AND      ebelp = wa_bseg-ebelp.

"Details from MBEW:Material Valuation

        SELECT  SINGLE           stprs AS zzgr_stprs

          INTO  CORRESPONDING FIELDS OF <fs_dtfigl_4>

          FROM  mbew

          WHERE      matnr = wa_bseg-matnr  "BSEG-MATNR

               AND      bwkey = wa_bseg-werks. "BSEG-WERKS

Save & Activate the FM.

And now test the DataSource in RSA3. And collect all objects into TR.

Then,

Replicate/Import the DataSource in the BW/etc. Targets  (Destination) and load the data into respectively Data Targets.

Related content:

https://scn.sap.com/

https://help.sap.com/

Comparison between 0FI_AR/AP_4 and 0FI_AR/AP_30 Datasources

Background/Scope of Document

Demonstrating the Delta functionality and differences between 0FI_AR/AP_4 and 0FI_AR/AP_30 Datasources.

We came across a scenario, where we were using the ECC DS 0FI_AR_30 at the back-end level for BODS development Project. However, after performing the initial load in BODS, we are not able to fetch the Delta records/data from the DataSource.

About the DataSources

The DataSources FI_AR_4 and FI_AR_30 extracts Accounts Receivable Accounting line items from tables BSID (open items) and BSAD (cleared items) in the R/3 source system.

Also, both the DS FI_AR_4 and FI_AR_30 extractors are referring a same extract structure “DTFIAR_3” and having the same number of fields in the structure.

• Source structure: BSID, BSAD
• Extract structure OLTP: DTFIAR_3

Differences

• The 0FI_AR_30 DataSource doesn't support 'DELTA INIT' highlighting the difference below.

• Delta INIT Simulation extraction mode ”1” is possible for 0FI_AR_4 not for 0FI_AR_30. (This indicator contains the information about whether the extractor for a DataSource controls the 'DELTAINIT Simulation' extraction mode).
• Delta Test possible mode ”X” allow for 0FI_AR_4 only. (This indicator contains information on whether, for test purposes, the extractor for a DataSource can be called in the modes 'DELTAINIT', 'Delta' and 'Repeat').

• Both are having different datasource extractor (FM). However the function modules are performing the different extraction procedure.
  • 0FI_AR_4 is based on FM (BWFID_GET_FIAR_ITEM): It is using a time stamp method instead of the BW Delta queue in the R/3 source system in order to determine the Delta dataset. And minutes based delta also possible using sapnote (991429).
  • 0FI_AR_30 is based on FM (SREP_FIAR_30): is refereeing/calling the datasource extractor FM (FBW4_DATA_TRANSFER_AR_3) and which is the engine of obsolete extractor 0FI_AR_3.
    
    

• The DataSources 0FI_AR_3 and the 0FI_AP_3 are based on the (FBW4_DATA_TRANSFER_*_3) which extract the line items from accounts receivable accounting and accounts payable accounting were delivered (see Note 200576). With BW Plugin 2001.1 (BW Release 3.0A) the consistent data extraction into the BW system with the Delta update procedure is now delivered for the line items of the G/L accounting (FI-GL), of the accounts receivable accounting (FI-AR) and of the accounts payable accounting (FI-AP). The new datasources 0FI_GL_4, 0FI_AR_4 and 0FI_AP_4 use a time stamp method instead of the BW Delta queue in the R/3 source system in order to determine the Delta dataset. This note describes the transfer from the old extraction procedure (datasources 0FI_AP_3 and 0FI_AR_3) to the new extraction procedure (datasources 0FI_GL_4, 0FI_AP_4 and 0FI_AR_4). Please refer sapnote(410797).
  

• Direct Access allowed for 0FI_AR_30 and can be use for Remote Cubes and but Direct access not supported to 0FI_AR_4.
  

• DataSource 0FI_AR_30 does not support Delta handling, refer SAP Note (1429650 - Queue delta for sub ledger documents in Simplified Reporting) 1266262 (AR) & 1390113 (AP).

Conditions to be able to use 0FI_AR/AP_30

If we are implementing the 0FI_AR_30, then it is mandatory to have SAP enhancement package 3 for SAP ERP 6.0, business function Reporting Financials (FIN_REP_SIMPL_1).

Refer SAP Note (1429650 and 1451341) which talks about the corrections/essentials required.

Conclusion

We can implement the 0FI_AR/AP_4 DataSources flow instead of 0FI_AR/AP_30 to get the regular delta records/load in BW, BODS etc… Sources and 0FI_AR/AP_30 can use for BW Remote Cubes/data transfer process based Direct Access.

Related Links:

http://fmis.minfin.bg/help/EN/9a/5b165c46c84eb7bcee1f25bdd11049/content.htm
http://fmis.minfin.bg/help/EN/9a/5b165c46c84eb7bcee1f25bdd11049/frameset.htm

Applies to:

SAP NetWeaver Business Warehouse (formerly BI) - SAP BW 3.5 & 7.x. Versions.

Summary:

The article articulates the step by step procedure for the generation of the COPA DataSource at the ECC R/3 back-end level along with Delta mechanisms and talk about the few challenges faced while extracting the data during implementation.

Table of Contents:

1. Introduction

2. Following is the Scenarios with explanation:

     a. Generating the COPA DataSource,

     b. Issues/Errors faced while extraction and building the Summarization Levels,

     c. Transporting the Summarization Levels to the next level,

     d. Delta mechanism and how it works, and

     e. How to change the safety interval limit for COPA DataSource

3. Describing the Test Scenarios

4. Related content

    
Introduction:

In one of the project we had implemented the COPA DataSource at ECC back-end. The main purpose is to extract the data and feed to a BODS interface.

Initially we had generated the COPA DataSource using the standard procedure and while extracting the data in RSA3, unable to extract the data due to few issues at ECC R/3 back-end level. Therefore describing the such scenarios in this document. 

Test Scenario:

Part - A). Generating the COPA DataSource:

Below are the simple steps for generating the COPA DataSource.

Basically COPA DataSource generation is a generic extraction and we can create the generic DataSource depending on the KPI's for the Profitability Analysis.

Go to T-Code:

SBIW--> Settings for Application-Specific DataSources (PI) --> Profitability Analysis --> Create Transaction Data DataSource --> Create a DatSource.

or

KEB0 --> define the DataSource with the necessary details as below.

Generally, we use the naming convention for the COPA DataSource is: {1_CO_PA_(SYSTEM ID)_(CLIENT)_(OPERATING CONCERN)}.

Select the Operating concern and choose the option Costing/Account-based (as per the business requirement), execute (F8).

If the COPA DataSource is "Costing based" then it will extract the data from below four tables:

CE1XXXX - Actual line items

CE2XXXX - Plan line items

CE3XXXX - Summary table

CE4XXXX - Segment table

where "XXXX" is the Operating Concern.

Or if the COPA DataSoure is "Account based" then it will pull the data from the following tables:

COEP & COBK - CO Object: (Line Items (by Period) & Document Header)

COEJ - CO Object: Line Items (by Fiscal Year)

COSP & COSS - CO Object: (Cost Totals for Internal & External Postings)

CE4XXXX - Segment table

Select the below fields which you want to display/as a part of the DataSource.

Note: When we generate the COPA DataSource basically the Data Structure (Characteristics and Value fields) is based on/proposed by the Operating Concern (OC).

{If we want to check/view the total number of fields based on the Operating Concern and other etc. details. Then, Go to the T-Code: KEA0.

The T-Code: KEA0 is used for to maintain/create the Operating Concern.}

After field selection, check & choose the InfoCatalog (F7) option for the DataSource generation. 

Then provide the Transport Request number and select the fields for the input selection.

Click on Save button.

DataSource "1_CO_PA_COEP" created successfully.

Note:  After generating the COPA DataSource, we will not be able to edit/enhance the COPA DataSource. In-case if we need to add the new fields, then we need to delete and recreate the DataSource again using the same naming convention.

Go to the T-Code: RSA3 and try to extract the data.

Part - B). Issues/Errors faced while extraction and building the Summarization Levels:

In some situations, you might get the following issues during the data extraction in RSA3:

Case. 1: During the data extraction probably you will get "0" records in RSA3. Or

Case. 2:  The DataSource is giving an below error while extracting the data in RSA3.

'Errors occurred during the extraction' (Message no. RJ012).

or check the error logs.

In order to overcome from this error, we need to define/maintain the following few steps.

Go to the T-Code: KEB0 and check if the Summarization Levels are maintained or not using option (CTRL+F3).

Or directly Go to the T-Code: KEDV (CO-PA: Maintain Summarization Levels). Select the Operating Concern.

And then, check the Summarization levels are maintained or not. If not, then choose the option to create entries (F5).

While creating the Summ. Levels, kindly consult with your functional consultant for more details/about the requirement.

Come back and select your Summ. Levels.

Choose the Characteristics option and assign the characteristic Values '*' or  'etc... value' as below.

Save the entries and assign the TR.

Now, the status of Summ. levels are Active, without data.

Then, Go to the T-Code: KEDU (CO-PA: Build Summarization Levels) refill the same using below option.

Select your Operating Concern (AA00), Type of Profitability Analysis "Costing-based (1) or Account-based" (2) and Choose Summarization Level (1 to 2).

Choose the option Rebuild/Build new levels and Execute (F8).

Again Go to the T-Code: KEDV and check the status of Summ. levels. now the status is Active with data.

After refilling the Summarization levels, Go to the T-Code: RSA3 and extract the data.

If still issue occurs then, Go to the T-Code: SE38 and run the Report program “RKETREGN” (Summarization Levels: Generate Tables for Summarization Levels) generate the same.

And again Go to the T-Code: RSA3 and extract the data.

Now data are available.

Part-C). Transporting the Summarization Levels to the next level:

Now transporting the changes/settings to the other system/next level. Go to the T-Code: KE3I (CO-PA: Transport tool) to collect all settings in the TR.

Execute (F8) it and mention your both TR Customizing and Workbench TR.

Select the relevant object classes and continue (OK).

Release the TR from SE09. Go to the T-Code: SCC1 (Client Copy - Special Selections), basically this T-Code is used for to import the TR from one client to another client within a system, for example: ECCCLNT800 (Pre-DEV) to ECCCLNT900 (DEV/QUA system).

Note: Check if the above transport procedure is applicable in your case. Otherwise, follow the normal transport procedure for transporting the objects from one system to another system, for example: from development (DEVCLNT100) to quality (QUACLNT500) system.

Part-D).Delta mechanism and how it works:

The COPA DataSource is based BW Delta process type: "CUBE" (InfoCube Extraction).

Note: The BW Delta process type “CUBE” is exactly similar as “ADD”.

Explaining the Delta mechanism of “ADD/CUBE” with below example and how it works.

Example:

When BW Delta process type: ADD--> which provides the additive Image.

A simple Doc Number as below: Existing Target document's quantity value is 30.

Now let’s assume the quantity has changed from 30 to 40 in the SAP ECC source.

If the DataSource is based on ADD/CUBE: it will bring only additive image i.e. quantity as 10.

In the final target it will reflect as below: adding the value (30+10 = 40).

Note: If the data that fills the BI system with an additive (ADD/CUBE) image, the data can be written to an InfoCube or a DataStore object.

However, in-case of DataStore object, the update type of key figures must be set to add and not overwrite.

Part-E). How to change the Delta safety interval limit for COPA DataSource:

When data is extracted from the COPA DataSource, a “safety delta” of half an hour (30 minutes) is used with the initialization and the delta upload. This always ensures that only records that are already half an hour old, since the start of the upload are loaded into SAP BW. Half an hour was chosen as the safety delta to overcome any time differences between the clocks on the different application servers.

The above standard upper limit for COPA is already set to: 1800 i.e. (30 Mins) provided by SAP.

Steps for changing the Delta Safety intervals for the COPA DataSource:

Note: It is not recommended to change the safety intervals. But sometimes we need to change the Intervals based on the Business/Project requirements.

Go to the T-Code: RSA2, check the existing value.

The DataSource safety upper limit is: 1800.

Also, we can check the interval values for individual DataSource in the table "ROOSOURCE" where the field "DELTASAFE2" holds the Safety Upper limit Value and "DELTASAFE1" holds Lower limit.

Below are the simple steps for changing the safety interval limit value.

Now, again Go to the T-Code: SE11, open the table "ROOSOURCE" and select the DataSource, click on display button.

Then we will use the ABAP Debugging trick to change the interval value.

Select the relevant field and press Enter button --> Double Click on the CODE and replace the word "SHOW" with "EDIT" --> press ENTER --> Execute (F8).

It will open in edit mode, then change the value based on the requirement (for example: here replacing 1800 Seconds with 600), save and go back to check the changed value in the table/Go to the T-Code: RSA2.

Refer SAP Note: (0000392876 - Safety delta for extraction from the CO-PA)for more details.

Replicate/Import the DataSource in the BW/etc. Targets (Destination) and load the data into respective Data Targets.

Related content:

https://scn.sap.com/

https://help.sap.com/