SAP easy learning

Om Shanti Baap Dada Madhuban Sweet Children - Father has come from far away to do foundation of one religion and one kingdom. It is deity religion and deity kingdom, none other. Ques : In Satyug, all are pure souls, no one is impure, what is the sign of that? Ans : There is no illness there. The illness here indicates that soul is suffering due to its own bad karma. This is the past account souls have to clear. Ques: What signs of Baba only children can understand? Ans : Father gives sign to apply mind towards him. Keep remembering him with love then we become flowers of his garland. Your tears which fall in love become beads of rosary. Song: Finally that day has come... Om Shanti Children listened to the song. Do you understand the meaning of it?  India is very big. Whole of it can't be taught. This is study - colleges keep opening. This is the university of unlimited Father. This is called Pandav government. Government is the name of Sovereignty. Now you children know, Sovereign...

 Sweet Children You have to practice being soul conscious and then do service. You are benefactors of all human beings. You have to benefit many. Father is concerned that children should not get trapped in anyone's name or form. Maya creates many obstacles. Father tells, do not be afraid of Maya. Become victorious by having remembrance of the Father. Om Shanti It is Baba's shreemat to remember him alone, no one else. This is to be "manmanabhav". Father (Baba) is Almighty Authorigy. Brahma Baba is not so. Baba is bodiless and we souls too are bodiless. You conquer Ravan through Father help and claim royal status once again. You now know the knowledge and hence become sensible. You receive very high status through this knowledge, you become Narayan from ordinary human. This is the study of Raja Yoga. Your aim and objective are in front of you, and it depends on how much effort you put. Your home is shanti dhaam, remember it you are going there. The soul becomes bodiless...

 Semantic groups can be set in DTP in the extraction tab. These are the fields from the source which are available for selection as semantic keys. The BW system while doing the loads will

 In Account receivables , there is a due date on which the outstanding amount has to be paid by the customer. If the due date is passed and the customer has still not paid, the amount becomes overdue and bucket calculation starts

 While loading the data from source to SAP BW system, the amount can be in local currency. If the user wants to see those amounts in USD in the BI reports, you can do the currency conversion either in the BI query designer or while loading the data to the cube. Steps for currency conversion in the data load- There is amount field in the source which is Amount type key figure and there is 0LOC_CURRCY field in source which holds the unit of this amount key figure like EUR or INR etc. Define a target info object say ZAMNT_LC for this field in the BW system with amount type key figure and unit as local currency- Map these objects as one to one from the source Define a new key figure in the target to hold the amounts in USD. Say for example, ZAMNT_USD. Go to tcode RSCUR and create a currency translation type say ZAM_USD- Give a description, go to the Exchange rate tab and give the exchange rate type. ( Exchange rate types are standard exchange rates available in the SAP system. You can ...

 The exchange rate in the BW system may not be updated one. Also the business wants to see the amounts according to the exchange rates in the source. In such cases, you have to update the exchange rate in the BW system via process chain. Include the step ‘Execute ABAP Program’ in the process chain. Give the program name as ‘RSIMPCURR’. Create a variant for the program.

 While loading data to a standard DSO, a key figure can be updated as ‘Overwrite’ or ‘Summation’. With an overwrite option, the previous value of the key figure which is already there in the active table of the DSO will be overwritten with the new value. Whereas with the ‘Summation’ option, the values will be

 Navigational attributes are discussed a lot of times in BW. They have an advantage as these attributes can be used for navigation in a query. However there are lot many more advantages of navigational attributes. I will discuss today one such scenario where navigational attributes has saved a week’s time. The Scenario is like this- There are 2 characteristics used in a cube. One characteristic is an attribute of another and both the info objects are included in the cube. Info object           Is Attribute of Country                                Region Region Both country and region are included in the cube as separate characteristics and country is an attribute of Region. Hence the master data of REGION info object will look like below- Region Country North America USA Asia Pacific ...

 The query designer formulas sometimes involve if then else kind of conditions or case statement type of logic. These type of logic can be easily given in the query designer, however the procedure is little tricky as you cannot write simple if statements in the query designer. Scenario – Suppose you have Amount and Net due date characteristics in the cube. The user gives the key date as query input. Based on the difference between the net due date and the key date, the query should return whether the amount is Due (i.e. net due date is in future as compared to key date) or Overdue (i.e. the net due date is passed as compared to key date). The query should also return the bucket information if the amount is overdue. Which means that the query should tell that the overdue amount falls in which bucket (>90, 61-90, 31-60 or 1-30). These buckets are assigned based on the number of days calculated earlier which is the difference between the net due date stored in the cube and t...

 Looking up a table while doing data load is a common scenario in SAP BW. Here the look up table can be active table of some other DSO. You can note a point here that cube cannot be used for look up. This is because, a cube has a fact table which is based on star schema. Hence the primary keys in a fact table will be dimension ids instead of the primary key values. Now coming to our scenario, suppose data is loaded from DSO1 to CUBE1.

 The number of times users have seen the BI reports can be analyzed in BW. All of this information is recorded as BW statistics automatically by the system provided the setting is activated for the targets. The data where the information is stored is the cube 0TCT_C01 [Front-End and OLAP Statistics (Aggregated)]. This cube is SAP standard cube and holds the usage statistics data. This comes under Technical Content info area in BW. The main info objects in the cube and their functions / meanings are summarized below-

  1. Managing Change Control and Transports This blog post addresses standards and guidelines related to changing and transporting objects within the SAP BI landscape.   1.1. General Standards and Guidelines Do not create BW objects and leave them in the $TMP package. If you need to prototype or experiment, you should do so in the Sandbox or Temporary TR created for that purpose. If you cannot use the sandbox, contact your development manager and the BI Platform Health team to discuss options. As you create objects, assign them the proper package (development class) and put them into the correct transport request, based on the standards described below. 1.1.1. Object Grouping and Sequencing Group objects logically, and release transports in the following order to minimize errors:

  1.1.  Querying 1. All queries should be built on multi-providers – even if it is to be built on a single InfoProvider. Multi-providers provide flexibility for the reporting layer.  Additional InfoCubes/DSO’s can be added in the future without much impact to the existing reports built. In cases where data needs to be combined using “joins,” InfoSets can be created. However, multiproviders should still be built on top of InfoSets for reporting. No end user reports should be built directly on InfoCubes, DSO’s or InfoSets. Any reports built directly on InfoCubes/DSO’s should be utilized from an IT perspective for data quality or support inquiries. 2. For reporting, standards will be set as it relates to the information stored within each data warehousing layer. InfoCubes should be used to access summarized information and, DSO’s or additional detailed InfoCubes should be used to access detailed information. Since the data warehousing architecture should include a DSO l...

 This post describes the standard methods and architecture for extracting data from source systems and into the first ­level Data Targets. The preferred extraction method varies depending on the source system technology. The standard extraction methods appear in descending order from most to least desired. Developers must attempt to use the methods at the top of these lists before proceeding down to the less preferred methods.

 This post describes standards for building process chains in SAP BW at any generic development project.   Process Chain Names & Attributes Standards: Process chain technical names should begin with Z or as per your client naming conventions.   Guidelines Descriptions for meta chains (parent process chains that execute sub-­chains) should include “Meta” or “Parent.”   Display Groupings:  Standards Never leave a process chain under the default, “Not Assigned,” Display Grouping. Use the Display Components toolbar button ( ) to assign new process chains to the appropriate display grouping. Refer your client's SAP BW Naming Convention document for Display Grouping technical names Guidelines: If you have a large application composed of multiple logical subsystems, you may create multiple display groupings for your application. Doing so can help you organize your process chains by subsystem. Just make sure the name and descript...

 The standards and guidelines in this post apply to situations where you must move flat files into the BW environment and load them through the BW flat file interface. You may only load from flat files when you absolutely cannot use the BW Service API, the DB Connect interface, or the Universal Data Connect interface to extract data into BW. File Locations on the BW System: As part of your solution implementation, you need to ask the Basis team to create at least one file system directory for your application’s flat files. You should request a folder under the following path; /usr/sap/interfaces/….. NOTE: Refer your client's SAP BW Naming Convention document for the details to follow naming convention. Managing Flat Files in BW Process Chains The BI Technology group has developed four custom process types to help you manage flat files in BW. You can find these process types under “General Services” in the Process Chain Maintenance tool. Their icons and desc...

 This post describes best practices for building appropriate secondary indexes on DataStore Objects. General guidelines for placing secondary indexes on DataStore Objects: The presence of secondary indexes on an DataStore Object can greatly improve query performance, but it may slow down load performance. If your application does not have routine, frequent reads or reports on a DataS­tore Object, do not build secondary indexes on it.   Designing Secondary Indexes: Apply these general guidelines when determining the number and structure of secondary indexes on DataStore Objects:

 This post provides guidelines for managing space in the SAP BW Production environment in general. It describes these guidelines in the context of generic business intelligence goals, principles, and architecture.   Principles of Data Warehousing Data Retention: Data warehouses exist to serve as the “information memory” of an enterprise. Data warehouses record all the critical business transactions conducted by an enterprise, so decision makers and business strategists can leverage the information to meet their goals and objectives.   The Value of Historical Information: The business intelligence team must ensure that information captured in the data warehouse supports both the current, known requirements for analyses, but also supports the future, unknown requirements. Low ­level, historical transaction data captures information about past behavior of the enterprise that no other source of information provides. When we delete this data, we eliminate forever the ability o...

  Write ­Optimized DataStore Objects Consider the following important facts in mind before you choose to use a Write Optimized DataStore Object: The primary unique key to a WODS Object consists of Request ID, Data Packet ID, and Record Number. The system does not use the semantic key as the primary, unique key to the data. This means that each time you load a particular semantic key into a WODS Object, you get a new, unique record. Write ­Optimized DataStore Objects do not aggregate data. If you extract and load two records with the same logical key (or extract and load the same record twice,) both records appear in the WODS Object. No delta detection or extraction function exists for WODS Objects. When forwarding data to subsequent data targets, the system will forward the requests (loads) that have not yet moved to those targets. Note, however, that this can result in duplicate rows going to the subsequent target.   Use as the Enterprise Data Warehouse Layer – First Level Da...

 This post describes generic standards and guidelines that apply to the use of standard BI objects delivered by SAP as part of the BI business content. Again, these may change as per your client's BW system standards. Activating Business Content Anyone with access to the sandbox may activate business content there. If you activate content in sandbox, make sure that you do not activate the content in the background (batch mode.) Instead, activate the content in the foreground and always keep any existing customization for the objects you activate. No one except the people allowed may activate business content in SAP BW development system.   If you need business content activated, contact one of those people and explain what you need activated.