As we all know the Controlling Data Sources delta data load work with a default safety time interval of 2 hours.

However, the customer wants to see the latest possible data in the BI/BO reports. Which requires changes to be made to the extractor with the standard safety time interval to bring the latest data from ECC and to be updated in the BW system.

Caution : As this is the standard behavior of the extractor SAP does not recommend in changing the control table parameter settings.

Control Table settings changes are performed at own risk.

The below table values are defined to over come the 2 hours extraction safety belt to 60 Mins.

This would be of great help for the Finance team/Business users when they are running their MEC (Month End Closure) Process.

Control Table settings for CO Data sources are little different than the FI data sources when implementing custom safety interval extraction/minute based extraction.

Transaction Code and Table

SE11 - BWOM_SETTINGS.

Parameter Values

The last parameter value  "MOSTRECENT =X" which is not applicable for the FI data sources this is the key difference between FI and CO when changing the extraction time limits.

PS : Relevant SAP Notes - 578417,416265,553561 and 836740

Hope this helps...

The moment you think of setting up an online store for selling the preferred products / services, your mind is crowded with various questions and obstacles. Initially you will have to plan about the inventory and the excess stock and then about the resources to be utilized for the products. Eventually, when it comes to an open source eCommerce website, the major decision to be made is – Which platform should be used?

While selecting an eCommerce software, it is crucial to keep the following things in mind:

The software that you decide to use will be the foundation of your entire eCommerce website.

This software will not be subjected to many changes in the future. 

Thereby, it is extremely important that you are aware of all the best softwares available before you make the final decision. A little effort in the initial phase will make sure that you won’t regret later. In this article, we would like to bring some of the selective and the most efficient free open source shopping carts available on the internet to your attention. See what they have to offer, check the demo, play around with the functionality and see if it suits your business requirements and then go for the best one.

Here we go:

OsCommerce (PHP/MySQL)

OsCommerce is a free open source online store eCommerce solution that is available through the General Public License (GNU). It incorporates an elegant set of unique online shopping cart functionalities that enable the online store owners to setup the online stores and maintain them with minimum effort and affordable price. Therefore, if you would like to set up your online store with OsCommerce, there are no limitations to your creativity and planning with OsCommerce.

Zen Cart (PHP/MySQL)

Zen cart is truly a state-of-art eCommerce software that is user-friendly and free. The most fascinating thing about this software is that it is developed by a group of like minded online store owners, designers and programmers who believe that an eCommerce website design can be done differently.

PrestaShop (PHP/MySQL)

PrestaShop is an executive eCommerce shopping cart software that can be downloaded and used for free. It has an extremely powerful back-end support. The online store administrators can manage the orders, inventory and payments easily. This is one of the most popular shopping cart softwares and it is easily available with any eCommerce hosting packages. The system never restricts you with any limits as it supports unlimited categories, sub-categories and images.

CubeCart (PHP/MySQL)

CubeCart is created in such a way so that it can be operated on the servers that have PHP and MySQL support. CubeCart enables you to setup an online store within a short span of time. This store can be used for selling digital or tangible products to the customers from any location.

Magento Commerce (PHP/MySQL)

Magento is a great eCommerce platform that is enriched with a wide range of features and built on an open source technology. This platform provides the online store owners with unprecedented flexibility and complete control over the content, functionality and look of the online store. Magento comprises of an intuitive administration interface through which tasks like search engine optimization, catalogue management and marketing are simplified. This provides the merchants the power to create eCommerce websites that are customized in accordance with their business requirements.

Opencart (PHP/MySQL)

Opencart is a robust eCommerce software for the website owners. It provides them with the capacity of creating their own website with an affordable price and minimum effort. Opencart is carefully crafted in a way to offer maximum features and ease of use along with an easy and appealing interface.

ZeusCart (PHP/MySQL)

The ZeusCart shopping cart is created on the basis of PHP application and it is used as a scripting language that facilitates the developer for making dynamic websites. It has a simple interface and it is easy to understand and therefore it can be a smart choice if you want to start your online store within a short span of time. ZeusCart can be customized in accordance with your requirements and that’s the reason why it is one of the most commonly used shopping cart softwares.

AgoraCart (Pearl/MySQL)

AgoraCart presents with a wide range of features that enable you to setup an online store starting from a simple template based online shop to the integration of the most complex eCommerce design concepts. AgoraCart is a superficial online shopping cart that is suitable for every online website owner.

VirtueMart (PHP/MySQL)

This is the complete online store solution provided by Joomla. Many store owners around the world make the use of this shopping cart software. It can be operated in-store and in catalogue mode as well. Through its powerful administration tools, you can manage a wide range of categories, orders, products, discounts, customers and shopper groups. VirtueMart can be accessed through both Joomla and Mambo CMS.

WordPress E-Commerce (PHP/MySQL)

This is a WordPress based shopping cart plugin that is tried and tested and it is truly amazing. It is easy to use and feature-rich that is suitable for selling any kind of products or services online.

CS-Cart (PHP/MySQL)

CS-Cart is an exceptional eCommerce software that has a user-friendly interface through which you can start selling online right away. It comprises of a unique feature-set that is suitable for business of any size ranging from a small single product shop to a multi-utility online storefront. It is specifically designed for ensuring complete flexibility. The latest eCommerce innovations such as one-page checkout, block manager, AJAX based web interface etc. are incorporated in CS-Cart and thereby it is one of the most robust shopping cart softwares.

Interspire (PHP/MySQL)

Interspire comprises of complete search engine optimization within a single page checkout. Business intelligence reports and track-able coupon codes are provided and therefore it is considered that no other shopping cart software can support the increase of your online sales like Interspire does. Complete guarantee is offered or you will get your money back. Through Interspire, you can either opt for a PHP-powered shopping cart or a fully managed eCommerce software depending on your preference.

These shopping cart softwares comprise of the basic functionalities and some addon features depending on their configuration.

The selection of the appropriate shopping cart software should be done on the basis of the type of online store you would like to establish. The functioning of an online store website is also dependent on the hosting platform chosen. Refer MilesWeb eCommerce solutions for selecting the most appropriate shopping cart software for your eCommerce website.

Hello

Some of the SAP LO extractors do not allow to fill setup table for multiple single values.

E.g. for application area Sales order - 11,Delivery - 12, Billing - 13

You can see above, there is no option to enter multiple single value.

So if we have few hundred documents  to be filled in setup table which are not in one single range, then it is tedious task. You will have to fill in setup table multiple times.

But this problem can be solved, but running this progam in debug mode.

Enter mandatory fields and enter /H (debug mode) and execute the program. Enter termnination date and time properly. Otherwise program will give error.

Here we are using program to fill in setup table for Sales Orders (11). But this same method works for Sales order , Delivery and Billing also.

In debug mode search for below string and add breakpoint there.

Press F8 and program will stop at this step.

Presss F5 and get inside the form "select_option_fill"

This form assigns the range entered in selection screen to internal table dd_belnr.

We can replace the contents of internal dd_belnr through flat file upload. This is standard feature of ABAP debugger. It is possible that, in production system , updating internal table in debug mode may not be allowed. In such case, special permission may have to taken to allow such update in  debug mode.

You can use following option of ABAP debugger to upload file. It should have 3 columns (or 4 if you set of multiple ranges)

In case of multiple singe values contents will be. I have attached test file in the document. I have created it in Tab Delimited format.

I      EQ     Docnumber1

I      EQ     Docnumber5

I      EQ     Docnumber7

For multiple ranges, it will be

I      EQ     Docnumber1     Docnumber5

I      EQ     Docnumber9     Docnumber10

I      EQ     Docnumber15   Docnumber22

Entire content of table dd_belnr will be replaced with content of file.

Press F8 to continue the program.

Run RSA3, to see if your Setup table is properly filled in.

BW-Delta Extraction for Treasury

Andreas Martin

April 2, 2006

Abstract

This guide gives an introduction to the extraction of treasury data to the business warehouse with the extractors

• 0CFM INIT POSITIONS

• 0CFM DELTA POSITIONS.

The text assumes that the reader is accustomed to the SAP business warehouse on the level of course SAP BW 310 and knows how to work

with transaction RSA1 the Administrator Workbench. We concentrate on the data source system and on the first set up.

This text is still a draft. Please send remarks and comments to Andreas Martin by andreas.martin@sap.com.

1 Treasury Transaction Manager

The position management in the treasury transaction manager manages the creation and change of the business positions. The main information is the set of position values at key dates and the flows which create these values. These position values are not saved at certain key dates, but are always calculated dynamically. Therefore the information system has the duty to report for requested key dates the set of position values, the flows which correspond to them and enhance this information with additional attributes.

The information system of the position management has three different levels:

1. The set of position values for a single position or a limited amount of positions can be reported by transactions TPM12 and TPM13 in R3.

2. Position values and additional attributes of a medium and large amount of business positions can be reported by the standard reports of the information system and the logical database of the treasury via the reporting tools queries and drill down reports. This is still in R3.

E-mail: andreas.martin@sap.com. Adress: SAP AG, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany.

3. Position values and additional attributes of a large scale of business positions in combination with other data can be reported in the SAP

business warehouse.

The extraction of data from the treasury position management to the business warehouse is done mainly by the extractors

• 0CFM INIT POSITIONS

• 0CFM DELTA POSITIONS.

In the business warehouse there is the standard content 0CFM POSITIONS which refers to these extractors. The extractors work only on the key date reference valuta date. Extraction for the key date reference posting date is in development. Reports with key date reference posting date are available on the first two levels of the information system.

2 The First Set Up

Before the periodic extraction to the business warehouse is in process, both the R3 source system which carries the treasury transaction manager and the business warehouse system have to be prepared.

2.1 Business Warehouse

In the business warehouse the business content you want to use has to be activated. You can use the standard business content 0CFM POSITIONS, copy this content and enhance it or even create your own business content.

Important! The treasury position management extractors are designed to pull data for a position cube like the info cubes given in the standard

content 0CFM POSITIONS. This is essential when you create your own content. Moreover, the treasury position cube uses an initial extraction and a periodic delta extraction.

When the business content is active you can extract the basic data and texts for the info objects which carry the characteristics. This is a common extraction process from the source system to the business warehouse like described in detail in course BW310 or any literature on the SAP business warehouse.

2.2 The Logical Database of Treasury

The CFMposition extractors and the logical database of the treasury work on the same set of functions to pull the position values and common attributes from the position management. In detail

• 0CFM INIT POSITIONS corresponds to FTI TR POSITIONS

• 0CFM DELTA POSITIONS corresponds to FTI TR PERIODS

both with key date reference valuta.

To get used to the data pulled by the initialization, the messages and errors for the extraction of the data and to determine the key date for the

initialization tests with reports on the logical database FTI TR POSITIONS should be performed. The extraction structure of 0CFM INIT POSITIONS can be displayed with transaction RSA2. We recommend to use queries as reporting tool. Similar you should get used to 0CFM DELTA POSITIONS with reports on FTI TR PERIODS.

While performing the tests the warnings and errors should be investigated carefully, because they would later cause the extraction to finish with warnings or errors, respectively.

2.3 Multitasking

The CFM position extraction as well as the logical databases can use multitasking to pull data. We recommend to use this functionality when large amounts of data is pulled. The customizing is done with transaction SM30 in table FTIC MTASKING.

2.4 Customizing of the Source System

The customizing for the business warehouse extraction in the source system which carries the treasury transaction manager has to be created and  checked. Please start transaction SPRO and navigate to

Corporate Finance Management -> Transaction Manager -> General Settings

-> Information System -> Business Information Warehouse.

At item Define InfoSources for Position Initialization the following customizing has to be given:

• InfoSource for Position Initialization 0CFM INIT POSITIONS; This is the table key and determines the info source for which the settings

are valid.

• Date of Position Initialization This is the key date for which the set of position values is calculated with key date reference valuta.

• InfoSource for Delta Position 0CFM DELTA POSITIONS; This is the info source which is used for the delta extraction after the initial extraction

was done.

• DataSource for Position Initialization 0CFM INIT POSITIONS; This is the data source which is used by the info source.

The date of position initialization is the key date with whom the initial load is done to the business warehouse. In the following process the delta extraction loads in update mode C Initialization for the delta transfer flows up to this key date and in the first run in update mode D Transfer of the Delta since the last Request flows with valuta date at and after this key date.

At item Define InfoSources for Delta Position the customizing for the periodic delta extraction has to be entered. For 0CFM DELTA POSITIONS

the following setting has to be given and checked:

• InfoSource for Delta Position 0CFM DELTA POSITIONS; This is the table key and determines the info source for which the settings are

valid.

• Technical Date From This key figure is not used and should remain empty.

• Pure Delta InfoSource This must not be set. The this delta extractor is not a pure info source and uses 0CFM INIT POSITIONS for

initialization. Please confer the F1-help for more information.

When the information above is given, the customizing is complete. The BWExtraction Log contains the list of extractions done from the source system.The last item Delete Time Stamp for InfoSource is needed when for a key date or time period the extraction has to be done again, for example if you want to delete an extraction with 0CFM INIT POSITIONS and do it again.

We come back to this example later.

2.5 Extractor Checker

Before the extraction to the business warehouse is done, the extraction process should be checked with the extractor checker transaction RSA3. However, you should have worked through subsection 2.2 carefully and completed the customizing in subsection 2.4. The extractor checker pulls and displays only a sample of the data extracted to the business warehouse. It is mainly used to check if the technical process for extraction works. The data should have been check before via reports on the logical database of the treasury.

Extractor 0CFM INIT POSITIONS is checked in update mode I Transfer of an opening balance for non-cumulative values. This check must be

done before the check of the delta info source.

Extractor 0CFM DELTA POSITIONS can only be checked when the initial load to the business warehouse is done. It is checked in update modes

C Initialization for the delta transfer and D Transfer of the Delta since the last Request. Update mode pulls flows with valuta data up to the initialization key data and update mode D pulls flows with valuta data at and after the key date.

Please check in every case the log which contains informations for the extraction check.

2.6 Extraction to the Business Warehouse

Finally we can change to the business warehouse system. Most of the work can be done with transaction RSA1 the administrator work bench. With the scheduler requests for info packages are created and scheduled. With the monitor the loading process is monitored.

The first task is to load the initial position data in update model with extractor 0CFM INIT POSITIONS. Then with the delta extractor

0CFM DELTA POSITIONS the initial delta with update mode C can be pulled. Now we are prepared to do the periodic delta extraction in update

mode D.

3 Deleting an Initial Extraction

In the process of testing the extraction it can be necessary to delete an initial extraction which was done by 0CFM INIT POSITIONS. To do that,

you have to the three steps:

1. Delete with the Infoprovider all requests belonging to the extraction. This deletes the data from the basis cubes where the data is extracted

to.

2. Delete with the scheduler the time stamp for the info package at drop down list · drop down list.

3. Delete in the source system at item Delete Time Stamp for InfoSource the time stamp for the info source for the position initialization

0CFM INIT POSITIONS. Flag the time stamps you want to delete and press save.

The similar action you have to perform when deleting an extraction with 0CFM DELTA POSITIONS.

4 Error Handling

Please inform us at andreas.martin@sap.com at errors and questions which were experienced during the process to set up the extraction for the CFM position extractor. We will add information on the error handling and answers to these questions to this text.

Source : Document on Treasury by Andreas.Martin@sap.com All Credits to Andreas.

Since such a detailed explanation on this data sources are not available , posting it here for knowledge sharing purpose.

BW Data Extraction for CFM Step by step

Instructions for extracting data

The two extractors

• 0CFM_INIT_POSITIONS
• 0CFM_DELTA_POSITIONS

are designed for extracting data from a non-cumulative InfoCube that is first initialized with an initial non-cumulative and is then provided with data in a delta procedure. Both extractors are required for the initialization. Only the 0CFM_DELTA_POSITIONS extractor is used for the subsequent extraction in the delta procedure.

You can execute the initialization using the following two methods:

1. Initialization with a time-related evaluation for the initialization key date.

2. Initialization with a period-based evaluation for the period up to the initialization key date.

We recommend that you carry out the first procedure with an initialization using a time-related evaluation. This procedure has the advantage of a shorter runtime and a smaller data volume compared with the second procedure. In addition, data inconsistencies before the key date are not so important. On the other hand, you cannot execute an evaluation before the initialization key date although you can do this using the second procedure. If you want to use the first procedure, you must therefore choose an initialization date early enough.

You can find Customizing for both extractors in Customizing for Treasury and Risk Management under 'Transaction Manager' -> 'General Settings' -> 'Business Information Warehouse.'
Choose 'Define InfoSources for Position Initialization' and create an entry for the 0CFM_INIT_POSITIONS InfoSource. The 'Date of Position Initialization' is the initialization key date. Enter 0CFM_DELTA_POSITIONS in the 'InfoSource for Delta Position' column and enter 0CFM_INIT_POSITIONS in the 'DataSource for Position Initialization' column.

Note that only one entry is allowed to exist for 0CFM_INIT_POSITIONS.

Under 'Define InfoSources for Delta Position', make an entry for the 0CFM_DELTA_POSITIONS InfoSource. The 'DataSource for Delta Position' is 0CFM_DELTA_POSITIONS and you must enter the date of the position initilization from 'Define InfoSources for Position Initialization' in the 'Technical Date From' field.

If you execute the initialization with a time-related evaluation, do not set the 'Pure Delta InfoSource' indicator. However, if you want to use the second procedure, you must set the indicator. If you set the indicator, the 0CFM_INIT_POSITIONS extractor does not deliver any data and only sets a time stamp for the time stamp management that controls the delta procedure.
Note that only one entry is allowed to exist for 0CFM_DELTA_POSITIONS.

You can choose 'Delete Time Stamp for InfoSource' to remove the time stamp. We recommend that you use parallel processing for the extractors under 'Parallel Processing Control: Information System and BW Extraction'. Choose mode 1 (FTI_LDB_PB_SEL_POSITIONS) for the extractor 0CFM_INIT_POSITIONS and mode A (0CFM_DELTA_POSITIONS) mode for the extractor 0CFM_INIT_POSITIONS. Synchronize your settings with your basis or hosting team and restrict one setting to one user if necessary.

For the initialization with a time-related evaluation for the initialization key date, proceed as follows:

3. Request an InfoPackage for 0CFM_INIT_POSITIONS in 'Generate Initial Position for Non-Cumulative InfoCube' mode.  You must define the company code and the valuation area. The InfoPackage delivers position values for the initialization key date for the data selection specified.

4. Request an InfoPackage for 0CFM_DELTA_POSITIONS in 'Initialization of the Delta Method' mode and set the 'Initialize Without Data Transfer' indicator. The system does not deliver any data in the InfoPackage.

5. Request an InfoPackage for 0CFM_DELTA_POSITIONS in 'Delta Update' mode.  The InfoPackage contains non-cumulative value changes between the initialization key date and the system date. You can also define the additional delta process.

The initialization with a time-related evaluation for the periods up to the initialization key date expires as follows:

6. Request an InfoPackage for 0CFM_INIT_POSITIONS in 'Generate Initial Position for Non-Cumulative InfoCube' mode.  You must define the company code and the valuation area. The InfoPackage does not contain any data because the 'Pure Delta InfoSource' indicator is set in the source system. However, a time stamp is set and this is important for further processing.

7. Request an InfoPackage for 0CFM_DELTA_POSITIONS in 'Initialization of the Delta Method' mode.  The InfoPackage contains all non-cumulative changes up to the initialization key date. You can use this to evaluate the non-cumulative for the key date.

8. Request an InfoPackage for 0CFM_DELTA_POSITIONS in 'Delta Update' mode.  The InfoPackage contains non-cumulative value changes between the initilization key date and the system date. You can also define the additional delta process for this procedure.

After the initialization key date, both procedures deliver the same result for evaluations. You can use SAP queries on the FTI_TR_POSITIONS and FTI_TR_PERIODS logical databases to check the extracted data. If the system issues error messages or if there is missing data, we recommend that you first use an SAP query to reproduce the error.

Source SAP Note : 1021346 - BW TRM Initializing a TRM non-cumulative InfoCube

Hello All, this is my first ever document on SDN so pardon me if I miss anything and your valuable suggestions are welcome.

I would like to share some knowledge about the various datasources that can be used to extract data into multiple systems let's say SAP BW system and other be Informatica System. I will try to shed some light on the how the delta mechanism works in this case of all datasources. Also I will try to be as simple as I can.

Scenario: Two systems ‘SAP BW’ and ‘Informatica’ are connected to a single source system SAP ECC.

While working on this kind of scenario I could classify the datasources in some broad categories depending on their Delta Mechanism or if they are FULL loads.

1. Change Pointer Based Datasources- These are mostly master datasources like 0CUSTOMER_ATTR, 0MATERIAL_ATTR, 0MATERIAL_TEXT and follow the change pointer based delta mechanism (i.e. tables BDCP2 or BDCPV in older version). The delta mechanism these follow is of type 'E or NEWE' (You can find it in table ROOSOURCE)
2. Setup Table Based Datasources- Mainly LO extractors which deal with setup tables, ideally application area datasources in LBWE and follow delta mechanism of ABR etc. For example, 2LIS_18_I0NOTIF is one such kind and almost all datasources starting with 2LIS
3. Time Stamp Based Datasources- These are the datasources which follow the time stamp table logic i.e. with delta mechanism of AIE, ADD etc. A few examples of these datasources are 0FI_GL_4, 0CO_OM_OPA_6. These datasources have special timestamp table BWOM2_TIMEST which mainly manages the delta mechanism.
4. Custom Datasources or Generic Datasources- These datasources which we create of our own and we provide our generic delta fields in RSO2.
5. FULL load datasources- Most of the master datasources are full loads and do not follow delta mechanism.

Good News: All of the above type of datasource work very well when these are extracted in multiple target system even when the delta extraction is running in parallel or in sequence.

So how does this work basically, answer to this is simple Delta Queues.

However, this is little tricky when it comes to extract data into multiple systems when running the delta in parallel as datasources have specific characteristics that they follow based on their kind.

In this section I will discuss only change pointer based datasources and in coming sections I will try to explain functioning of others too.

We will go through system configuration and necessary steps that need to perform before we could even start the extractions. Briefly we will go through following:

1. System Configuration understanding in case of two target system
2. Understanding of Change pointer based datasources functioning
3. Initialization of datasource from two systems and its effect on source system
4. Delta Extraction from two Systems

System Configuration: Ideally this is the basis activity and I will only provide some tcode information. To extract the data into multiple systems we will have to establish communication between the two systems which would involve following:

     a) Logical system creation (tcode - SALE)

     b) RFC destination creation (tcode - SM59)

     c) saprfc.ini file settings (in case of Informatica this is done on Informatica app server side) - we faced a lot of issues with saprfc.ini file entries so make sure these are correct

     d) ALE idoc configuration (tcode - WE31, WE30, WE21, WE20, BD64)

When the two systems are connected to one source system there will be two logical systems, one for each. For example, let's say we are connecting SAP BW and Informatica system to SAP ECC. Then in SAP ECC there will be two logical systems, let's say logical system names are BQ1CLNT100 and INFACONTNT (we will use these names in rest of the document below).

Change Pointer Based Datasources: These datasources work based on change pointers which are stored in table BDCP2 (BDCPV in older versions). In table BDCP2, all the change pointers are stored based on Message Types and Change Pointer ID (the key fields of this table). The Message Types are associated with each logical system. For example, if we have SAP BW system connected to SAP ECC then we will have exactly one message type between two systems. The message type linking with the logical systems can be found in table ROOSGEN.

So whenever we create/change any customer the change pointer is stored in table BDCP2 for this particular message type. Like if I create a new customer then in BDCP2 the entry would be like this:

Important field in BDCP2 table:

a)      MESTYPE – This field holds the message type related to the target system. So do we manually have to create this message type? Well, answer to that is No. For any datasource working on message type and change pointer mechanism the message type is system generated. It is generated as soon as we create the logical system and replicate the datasource from target system for the first time. In above case, RS0059 was created when we replicated the datasource from SAP BW system for the first time.

b)      ‘PROCESS’ – This field has indicator if the data is already extracted to target system or not. Basically if the value in this field is blank then it is not extracted in SAP BW system and will be considered for next extraction and as soon as this field is set to ‘X’ then that particular record will not be considered for next extraction.

Initialization of datasource from two systems and its effect on source system: Let us assume that we have all the communications established between all 3 systems. And we have replicated the datasource from both systems: BQ1CLNT100 and INFACONTNT from source system SAP ECC.

As we all know for delta extraction the pre-requisite is INITIALIZATION. When we initialize the datasource will have separate delta queues for both the target systems in RSA7.

Delta Extraction from two Systems: Remember, we saw that message type gets created after we replicate the datasource in source system. So if the change pointers are activated for this datasource in source system then right after replication the new/changed data gets stored in table BDCP2 for both the message types of both target system.

In below screen, we have two message types created for respective systems. Here note that we have only replicated 0CUSTOMER_ATTR in both system but 0CUSTOMER_TEXT is only present in SAP BW system. So for 0CUSTOMER_TEXT we have only one message type.

Now whenever we create new data we will have 3 records in BDCP2 table for respective message types.

Let’s create a new customer:

Check BDCP2 Table:

In BDCP2 table we have 3 records for respective message types. Here since we have 0CUSTOMER_ATTR for two different target systems so we have individual records.

For, BQ1CLNT100 --> RS0130         and                  INFACONTNT --> RS0147

And PROCESS is blank.

For 0CUSTOMRER_TEXT we don't have multiple message types so we have only one change record for it's message type.

Now, when we extract the delta data into any system they will relate to their own delta queues and message types. And data will be extracted in both systems equally without missing any data.

Summarizing - It will work in following cases:

1.      Extract data from BW system regularly and not from Informatica– In this case BW will only extract data from its own message type and delta queue without disturbing data for Informatica. And when Informatica extract data after a period of time it will not miss any data that is already extracted to BW.

2.      Data Recovery: For this type of datasource we generally do the data recovery by resetting the PROCESS field back to ‘ ‘. So if we need to recover data for only BW system then it will be independent from Informatica extraction as BW system data recovery will deal with only its own message type.

3.      Delta in Parallel: Since message type is different so if extractions from both target system access the source system for same datasource then SAP handles the locking mechanism of base tables and it do not fail for any system.

Take away from above discussion:

·         Change Pointer datasources work perfectly for multiple system extraction even in parallel delta extractions.

·         Multiple target systems have separate logical systems and hence separate delta queues.

·         Data recovery is safe for one system without affecting other target system

I will discuss more datasources in subsequent documents as I believe this document has grown very long. I don’t really know where to stop

Please share your thoughts and let me know if you need more information on this.

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

Enter SE03 Tcode and double click on “Change object Directory Entries” under "Object directory" folder.

Enter the user name in "Person Responsible" field (user who created the object) and press execute button.

Here you have to expand your system ID (e.g PBZ)  and  you will get your object details.

Select the object which you want to change to transportable object. After that click on object Directory.

It shows below pop up screen.

In the below screen change the package name. e.g. from $TMP to ZBW.

After that it will ask for request no. You can save the previous
request number or you can create new request number.

After changing pachage name you can see same object in SE01 Tcode under the same
package name.

Subject: Activation of Data Source for Services Procurement 

Applies to:

SAP BW 3X, SAP BI 7.0, ECC 6.0 EHP 3.

Summary:

This document has 2 parts. First part explains about the activation of the data source 2lis_02_SRV

& second part explains about enhancing it for adding the services line items to be made available to identify multiple service items.

Author: ShreeshBhat

Company: JSW Group

Date: 15 Oct 2014

Author Bio

Shreesh is a senior SAP BI consultant working with JSW Group. He has over 8 years’ experience in implementations & Consulting with SAP BI/BO tools.

Table of Contents

          1. Introduction...............................................................................................................3    

         2. Step-by-step Solution:  Activating 2LIS_02_SRV........................................................3        

                        2.2 Maintain transaction key for SAP BW.........................................................4

                        2.3 Activate EHP3 switch..................................................................................4

                        2.4 Activate data source of Appl. Comp. 02 in LBWE........................................5

         3. Step by step for enhancement....................................................................................6

                        3.1 Enhancing the data source 2LIS_02_SRV.....................................................6

                        3.2 Create an append structure for MC02M_3SRV...........................................7

                        3.3 Filling/ Deletion of setup table....................................................................8

         4. Conclusion..................................................................................................................9

1. Introduction:

Data Source 2LIS_02_SRV used for extraction of (Services Procurement) service line data to BW is made available with ECC 6.0 EHP 3. Though its name seems similar to the LO Cockpit extractors, it will not be visible in the transaction LBWE. Hence there has to be some special configurations maintained to be made available for data extraction. Next we will see when there're multiple line items or records for one service entry sheet, in T-Code RSA3 result, they would have the same purchase order (EBELN) and the same item number (EBELP) and except these there's no unique key to distinguish them. So we will have to enhance it to include a unique key so that if there are many line items in a service they can be displayed along with their quantities & values.

2. Step-by-step Solution:  Activating 2LIS_02_SRV

2.1 Create relevant entries in table TMCEXACT

Check if any entry exists in the table TMCEXACT for MC02M_0SRV.  MC02M_0SRV is the extract structure for the data source 2LIS_02_SRV. If not maintain the data as below. Also note TMCEXACT can be maintained by using the transaction SE16N.

2.2 Maintain transaction key for SAP BW

In transaction SBIW -> Settings for Application-Specific Data Sources (PI) -> Logistics -> Settings: Purchasing -> Transaction Key Maintenance for SAP BW as:

2.3 Activate EHP3 switch:

Search for business function in ENTERPRISE_BUSINESS_FUNCTIONS ->LOG_MM_CI_2  in T Code SFW5. If it’s off, please switch on LOG_MM_CI_2.  While doing so make sure dependencies were off.

Go to T code SFW2 & give the business function LOG_MM_CI_2 & click display.  Check if these switches MM_SFWS_SC2 and MM_SFWS_UI_1P2P are off. If so please turn on both Switches as well as the Business Function.

This will activate the code that fills the structure.

2.4 Activate data source of Appl. Comp. 02 in LBWE

Make sure at least one of the below data sources belonging to purchasing application is activated in transaction LBWE, 2lis_02_acc / 2lis_02_hdr / 2lis_02_itm / 2lis_02_scl. But still the data source 2LIS_02_SRV will not be visible in LBWE, but is activated & will be visible in RSA3.

3. Step by step for enhancement

3.1 Enhancing the data source 2LIS_02_SRV

Thus activated data source doesn't have unique key to distinguish the multiple line items in a service entry sheet. So if this is updated into the DSO then, the values will be overwritten. In the below figure a purchase order has a single service entry sheet against a single line item. But the service entry sheet 1000283729 has 6 different records with the different quantity.

So to identify them we will need some unique keys. The values come from the table ESLL. So PACKNO and INTROW from the ESLL table can be used as unique keys to identify the values. As they don’t exist in standard extraction structure MC02M_0SRV, we will have to add fields PACKNO & INTROW to our own data structure, such as ZMC02M_3SRV, and append this structure to the standard extraction structure MC02M_3SRV. 

3.2 Create an append structure for MC02M_3SRV.

Add the below mentioned fields as shown below

3.3 Filling/ Deletion of setup table

After this we need to re-fill setup table for 2LIS_02_SRV by T-Code OLI3BW, then we'll see fields PACKNO (package number) & INTROW (line number) in T-Code RSA3 result as below.

Note: For all other data sources of LO Cockpit you can delete the setup table data in the T Code LBWG. But for the data source 2LIS_02_SRV this doesn’t hold true as this data source in not in LBWE.

To clear data from setup table MC02M_0SRVSETUP of 2LIS_02_SRV we have to manually in SE14 as below.

4 Conclusion :

In any Industry Procurement of services is also an important part just as procurement of materials. This is the only data source which deals with the services part. This is made available from ECC 6.0 EHP3 only. And also care has to be taken to activate it in a different way than other LO Data sources.

This is a very common error which can drive you nuts.

Symptoms:

You have executed the infopackage and it is showing number of records transferred. Now this number is not increasing but request is in still yellow state.

Actions:

1- Check ST22 in BW system.

2- Please check If there is any recent "CX_SY_OPEN_SQL_DB"  dump having short text "SQL error in the database when accessing a table".

3- Select "Information on where terminated " option from your left in ST22 transaction.

4- Please check if you receive following information regarding termination.

Termination occurred in the ABAP program "GPD9MD1Y7LHYIY4YXUTXTHJ9VM8" - in

"INSERT_ODS".

The main program was "SAPMSSY1 ".

ORA-01502: index 'SAPSR3./BIC/B0000XXXXXX~0' or partition of such index is in unusable state

Solution:

If your answer to all points mentioned in above "Actions" is YES then following solution is for you.

1- Goto : SE14 on BW Side

2- Adjust and activate you PSA Table.

3- Adjust and activate primary/secondary index of this table.

Done.

The reports includes standart datasources developments like a append structure for LO Data Extraction. An example is implemented belowed for 2LIS_02_ITM datasource.

Business Requirement

Some fields does not exist in datasource so a lot of reason like a items data , header data etc. But projects customers demand to report the fields. To get solution developer has to append structure.

Process and Prerequisites

Firstly , check standart extraction structure. -> LBWE tcode.

For instance ; ERNAM is appended to 2LIS_02_ITM

To add field to structure , we have to find extraction structure for this go to RSO2 tcode. For this example ; MC02M_0ITM related with us.

Solution

To add field to extraction structure following belowed paths.

a) Append structure

b) Enhancement of datasource

--> SE11 tcode for a part.

Append structure creation ;

ZZAPPEND_MC02M_0ITM is defined and component ZZERNAM is added with types.

*Please be carefull if you add a quantity/currency so currency/quantity fields definition.

Enhancement of data source

RSAP0001 enhancement is used for this aim. Create a project with CMOD tcode like a ZBI to follow related projects.

Function exit --> EXIT_SAPLRSAP_001

INCLUDE ZXRSAU01.

Project can be coded like a belowed.

******************************************************************************************************************************************

Finally, you can get this field in your datasource.

Simulation with RSA3 tcode.

In this way , you can utilize requirements like a Created by (ZZERNAM) column is added and filled.

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.

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.

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

Introduction:

This document explains the enhancement approach for the New Financial General Ledger (Leader Ledger) data source – 0FI_GL_10.

Standard Approach:

Normally in the general practices the extract structure is enhanced with the required fields and the data is populated using the external logic in the CMOD. New FL leader ledger will follow a different approach in populating the data and the same is explained in the further sections.

Prerequisites:

In the Source system, you have activated new General Ledger Accounting in Customizing for Financial Accounting under Financial Accounting Global Settings.

Steps Involved:

New GL Leader Ledger is based out of the table FAGLFLEXT– General Ledger – Totals

If the requirement is to include the additional fields then the fields has to be included in the Customer Include using the transaction: FAGL_GINS or using the following Navigation from SPRO:

SPRO --> SAP Customizing Implementation Guide --> Financial Accounting (New) --> Financial Accounting Global Settings (New) --> Ledger --> Fields --> Customer Fields --> Include Fields in Totals Table

This will take you to the transaction FAGL_GINS to enhance the Total Table – FAGLFLEXT.

Next screen will allow you to add the required Customer fields which will further added to the Totals table.

Totals Table – FAGLFLEXT will be automatically enhanced with the Customer Enhancement – CI_FAGLFLEX04.

Once this is done, in order to extract the customer fields in the data source 0FI_GL_10, the Customer Include CI_COBL needs to be added as an Append in the Extract structure - FAGL_EXTSTRUCT_LEAD

TCode: RSA6 --> Select data source 0FI_GL_10 --> Double click to see the details of the data source.

Coding Block has to be added in the above extract structure as an Append Structure in order to pull the data.

Coding Block CI_COBL can be found as below:

This contains two sections, one for the standard Account Assignments fields and the other one is for the customer fields.

Extract structure – has to be enhanced with the Coding block as an Include or using the Append Structure:

Using Append Structure at the extract structure level with the same name CI_COBL:

Or   --  Using Include CI_COBL:

Preferred one is to use the Append Structure.

Once this is done then, unhidden the fields from the data source in RSA6 and inverse option. Once done, extract can be used to extract the enhanced fields. The fields of the APPEND structure are then filled automatically without any additional logic.

Replicate the data source changes in BW and add the corresponding IOBJ’s in the data flow in order to use it for further reporting.

References:

Help.sap.com - Link

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