SAP easy learning

 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 of the enterpri

  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 Data Acquis

 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.

 Both Ranges and Select-Options are used for maintaining Ranges. Select-Options are used for taking input from user on selection screen In case of Select-Options system itself creates an internal table In case of Ranges, the internal table should be defines explicitly The internal table contains four fields- Sign, Option, Low and High . Special operator IN is used in comparisons. SIGN The data type of SIGN is C with Lengh 1. Possible values are I and E. I stands for "inclusive" (operators are not inverted) E stands for "exclusive" (operators are inverted) OPTION The data type of OPTION is C with length 2. OPTION contains the selection operator. The following operators are available: if HIGH is empty, you can use EQ, NE, GT, LE, LT, CP and NP. if HIGH is filled, you can use BT (Between) and NB (Not Between) LOW To maintain lower limit of range. HIGH To maintain higher limit of range. Ex: SELECT-OPTIONS range_ex FOR sy-index. SELECT-OPTIONS matno FOR mara-matnr. RANG

 All the below system fields belong to the data dictionary (DDIC) Structure - SYST . SY-INDEX for loop counting SY-SUBRC condition of previous statement SY-FDPOS position of substring in main string (works with SEARCH) SY-ABCDE a string of 26 characters     SY-ULINE for horizontal lines of any length SY-VLINE for only one vertical character     SY-DATUM for application server's date SY-UZEIT for application server's current time SY-DATLO for Presentation server's date SY-TIMLO for Presentation server's current time     SY-DBSYS backend database name SY-HOST name of application server SY-SYSID name of the R/3 system SY-OPSYS name of application server's operating system     SY-MANDT Logon client number SY-UNAME Logon User name SY-LANGU Logon language     SY-MSGID message class name SY-MSGNO message number SY-MSGTY message type SY-MSGV1 message variable 1 SY-MSG