ABAP ALV Hirarchical Report Sample Code in sap Programming

ABAP programming report for alv hierarchical report in sample code gives you a real time report that tells you in detail with example coding how to write the abap programming report.

&---------------------------------------------------------------------
*& Report Z_HIERARCHIAL_ALV *
*& *
&---------------------------------------------------------------------
*& *
*& *
&---------------------------------------------------------------------

REPORT ZGDEMO_HIERARCHIAL_ALV_9AM .
TYPE-POOLS SLIS.
DATA : IT_EKKO TYPE TABLE OF EKKO,
IT_EKPO TYPE TABLE OF EKPO.

DATA WA_KEYINFO TYPE SLIS_KEYINFO_ALV.

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

• START-OF-SELECTION. *

****************************************
START-OF-SELECTION.
PERFORM READ_DATA.

PERFORM FILL_KEYINFO.

PERFORM DISPLAY_DATA.

&---------------------------------------------------------------------
*& Form READ_DATA
&---------------------------------------------------------------------
form READ_DATA .

SELECT * INTO TABLE IT_EKKO FROM EKKO UP TO 20 ROWS.

IF NOT IT_EKKO IS INITIAL.
SELECT * INTO TABLE IT_EKPO FROM EKPO
FOR ALL ENTRIES
IN IT_EKKO
WHERE EBELN = IT_EKKO-EBELN.
ENDIF.

endform. " READ_DATA

&---------------------------------------------------------------------
*& Form FILL_KEYINFO
&---------------------------------------------------------------------

• text

----------------------------------------------------------------------
form FILL_KEYINFO .
WA_KEYINFO-HEADER01 = 'EBELN'.
WA_KEYINFO-ITEM01 = 'EBELN'.
WA_KEYINFO-ITEM02 = 'EBELP'.

endform. " FILL_KEYINFO
&---------------------------------------------------------------------
*& Form DISPLAY_DATA
&---------------------------------------------------------------------

• text

----------------------------------------------------------------------

• --> p1 text
• <-- p2 text

----------------------------------------------------------------------
form DISPLAY_DATA .
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
EXPORTING

• I_INTERFACE_CHECK = ' '

I_CALLBACK_PROGRAM = SY-REPID

• I_CALLBACK_PF_STATUS_SET = ' '
• I_CALLBACK_USER_COMMAND = ' '
• IS_LAYOUT =
• IT_FIELDCAT =
• IT_EXCLUDING =
• IT_SPECIAL_GROUPS =
• IT_SORT =
• IT_FILTER =
• IS_SEL_HIDE =
• I_SCREEN_START_COLUMN = 0
• I_SCREEN_START_LINE = 0
• I_SCREEN_END_COLUMN = 0
• I_SCREEN_END_LINE = 0
• I_DEFAULT = 'X'
• I_SAVE = ' '
• IS_VARIANT =
• IT_EVENTS =
• IT_EVENT_EXIT =

i_tabname_header = 'IT_EKKO'
i_tabname_item = 'IT_EKPO'
I_STRUCTURE_NAME_HEADER = 'EKKO'
I_STRUCTURE_NAME_ITEM = 'EKPO'
is_keyinfo = WA_KEYINFO

• IS_PRINT =
• IS_REPREP_ID =
• I_BYPASSING_BUFFER =
• I_BUFFER_ACTIVE =
• IMPORTING
• E_EXIT_CAUSED_BY_CALLER =
• ES_EXIT_CAUSED_BY_USER =

tables
t_outtab_header = IT_EKKO
t_outtab_item = IT_EKPO

• EXCEPTIONS
• PROGRAM_ERROR = 1
• OTHERS = 2

.
IF sy-subrc 0.

• MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
• WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

endform. " DISPLAY_DATA

Using SAP MDM for number generation

Using SAP MDM for number generation

MDM Solution landscape-
MDM is integrated with ECC using XI in a CMDM scenario, Enterprise Portal is used as UI and we have an Approval workflow for new creations as well as edit requests. Requirement is to generate the numbering from SAP MDM for any newly created records. Users are not allowed to create any new record in ECC directly. MDM offers 2 standard ways(A & B) for generating numbers- 
A.    Define a calculated field based on Auto ID to match the number ranges defined in ECC
To illustrate in ECC for different material type we have a different number ranges assigned. This can be replicated in MDM by defining a calculated field Material number and the calculation expression will be (Auto ID+100000000-1). This will ensure that Materials created in MDM are matching the ECC number range. The above expression can be changed using conditions (If then else) IF (Mat Type='PROD', Auto ID+100000000-1, Auto ID+200000000-1).This can be further nested if we have more material types and they have different numbering ranges in ECC. 
Key challenges faced:
•1.    Losing the numbers on performing a match base search from Portal-
Since we are using EP as the user interface JAVA APIs are used for connecting to MDM repository. Requestor logs in portal, does a search for the record based on matching strategy defined in MDM. Duplicates can be found against both records that exist in repository as well records that do not exist in the repository (empty record).There are two API available for executing the matching strategy in MDM and for continuity of numbers driven by MDM we should use the 2nd API.
•a.     ExecuteMatchingStrategyCommand (for records that are present in the repository)-
This inserts a record in MDM with the calculated field on which the matching strategy is run. After getting the duplicate results the inserted record is deleted. In the process we lose a number in MDM.
•b.     ExecuteMatchingStrategyForNewRecordValuesCommand (for new Records that are not present in the repository)-
This API will not insert a record in MDM repository and hence the numbers will not be lost. Limitation for using this API- Will not work if we have any calculated field in the MDM data model which is also part of the Matching strategy

•2.    Initial data loads for already existing data present in ECC to MDM. 
Since the numbers have to be matched utmost care is required during data migration. Let me explain this with some examples-

• a. ECC has materialsin range100000- 199999 and say there are some missing numbers in production. After 100007 we have next material as 100012 in ECC.
• b. to replicate this in MDM we need to insert 5 dummy records in MDM from 100008 to 100011 so that nubers in MDM matches with ECC

B. Use of Key generation property for the ECC remote system. 
This means the numbers will be generated when the records are syndicated to ECC from MDM and it will also update the remote key mapping in data manager. See the following blog for more details.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807ce1ba-94c0-2a10-a398-afdfd8135ebd?QuickLink=index&overridelayout=true
This has limitations since the number generated are not directly visible in record details but can be seen only via edit key mapping. 
Suggested Way: Instead we can define the Material Number field as Text and from EP we do a RFC lookup in ECC to get the number depending upon Material Type which can be assigned to the text field in MDM. This way we don't lose any numbers because of search (Matching based) conducted from Portal UI and synchronizing the numbers between ECC and MDM for initial data loads can be managed very easily.

SAP Programming Report Back Order Processing

SAP programming report for back order processing is related to the Missing Parts Info System,this report displays all requirements for a given material and allows you to change prior commitment quantities.A planner would use this report to quickly assess demands and reallocate materials among manufacturing orders based on changing priorities and inventory availability.

The data displayed in backorder processing is based on commitments which are generally done automatically during order creation or release. Additional demand information will be reflected based on SD order allocations and the last MRP/MPS run. Consequently, backorder processing needs to consider this to ensure visibility of all potential demands. Backorder processing relies on the availability checking rules maintained in configuration and referenced on the MRP and sales view of the material master.

You can run backorder processing from the Missing Parts Info System, or call it up directly from the menu.

You can change the commitment quantity from the first screen within backorder processing. The menu options let you:

1. Branch to the stock overview
2. Display the individual demand element from MRP
3. Peg to upper-level demand
4. Drill down to dependent requirements

The first screen prompts you for material, plant, and the availability checking rule to be used, typically PP in production planning. This screen provides a vertical listing of demands in date sequence, with columns displaying the required quantity, committed quantity, and the cumulative ATP balance.

From the first screen, you can change the commitment quantity for a given demand either by choosing Change confirmation, or by choosing Edit → Change confirmation.

Other actions which may be taken from the menus or icons are as follows:

1. Save all changed commitment quantities (reallocations) (Backorder processing →Save).
2 Display Scope of Check to verify sources of demand and supply being considered in the check (Goto → Display scope of check; icon also available).
3. Filter the demands to show only SD requirements, reservations for production orders, or both (Settings menu).
4. Switch to columns reflecting receipts, demands, etc. by period (Settings →Period totals; icon also available).
5. Branch to the Stock Overview screen for the material (Settings → Stock overview).
6. Display the individual demand element (MRP element) (Environment → Disp MRP element).
7. Display pegging to upper-level demand or lower-level dependent requirements (Environment → Pegging or Order report; icons available).

To access the first screen for this report, choose Logistics → Production → Production control → Control → Backorder processing → Material
1. Enter 100-100 in Material.
2. Enter 3000 in Plant.
3. Enter PP in Checking rule.Checking rule PP is typically used for manufacturing orders.
4. Choose Enter.

This screen shows a recap of the total receipts, issues, and confirmed issues:

A Demand by date and source
B Committed quantity
C Cumulative ATP quantity
5. Choose Period totals to reformat the screen.

The screen is reformatted to bucket demand and supply by time periods.Time buckets may be changed using the icons provided on the toolbar.

D The Scope of check may be displayed using the icon.

Parameters defined in configuration for the checking rule are displayed here. This report is different from the Backorders report in that it focuses on production planning instead of sales and delivery.

SAP MDM Jobs Mahindra Satyam

We are Mahindra Satyam (NYSE: SAY), a leading information, communications and technology (ICT) company providing top-class business consulting, information technology and communication services. Leveraging deep industry and functional expertise, leading technology practices and a global delivery model, we enable companies achieve their business goals and transformation objectives. 

We are powered by a pool of talented IT and consulting professionals across enterprise solutions, client relationship management, business intelligence, business process quality, operations management, engineering solutions, digital convergence, product lifecycle management, and infrastructure management services, among other capabilities. Our development and delivery centers in the US, Canada, Brazil, the UK, Hungary, Egypt, UAE, India, China, Malaysia, Singapore and Australia serve numerous clients, including several Fortune 500 companies. 

We are part of the $7.1 billion Mahindra Group, a global industrial conglomerate and one of the top 10 industrial firms based in India. The Group’s interests span financial services, automotive products, trade, retail and logistics, information technology and infrastructure development. 

Designation	SAP MDM Consultant
Job Description	 Role - SAP MDM Consultant  Experience -7 - 12 Years  Work Location – Bangalore/Hyderabad/Chennai  Type of Position – Permanent   Lead time to Join – ASAP Roles & Responsibilities:  Should have 7 – 12 Years of SAP MDM experience.  Consultant should have handled minimum 1 – 4 End – End implementation in SAP MDM.  Candidate should be a quick learner.  Ideally the candidate should be flexible to travel for short term durations.
Desired Profile	 Role - SAP MDM Consultant  Experience -7 - 12 Years  Work Location – Bangalore/Hyderabad/Chennai  Type of Position – Permanent   Lead time to Join – ASAP Roles & Responsibilities:  Should have 7 – 12 Years of SAP MDM experience.  Consultant should have handled minimum 1 – 4 End – End implementation in SAP MDM.  Candidate should be a quick learner.  Ideally the candidate should be flexible to travel for short term durations.
Experience	7 - 12 Years
Industry Type	IT-Software/ Software Services
Role	Project Lead
Functional Area	ERP, CRM
Education	UG - Any Graduate - Any Specialization,Graduation Not Required  PG - Any PG Course - Any Specialization,Post Graduation Not Required
Location	Bengaluru/Bangalore, Chennai
Keywords	SAP MDM
Contact	Vijayanath siddhareddy  Satyam Computer Services Ltd
Telephone	9962090069
Email	Vijayanath_Siddhareddy@mahindrasatyam.com
Website	http://www.mahindrasatyam.com
Job Posted	30 Mar

Purchase Order BAPI SAP ABAP

If you wish to transfer Purchase Order related Data to SAP, you can do so by using the following BAPI.

BAPI_PO_CREATE

Many a times there is a requirement to transfer purchase order data from a third party to SAP, it can be done by the following methods.

1) BAPI
3) BDC
3) EDI

This this tutorial we will see how to create a Purchase Order using the above mentioned BAPI.

Please note that if you wish to create Real Time Purchase Orders from an external system into SAP R/3 then you need to use either the JCO connector, .NET connector or XI. The example below shows creation of a single purchase order, if you have data required to create purchase orders then you first need to upload it into an internal table and then pass the table to the BAPI.

Please find the code below to create a Purchase order using the BAPI BAPI_PO_CREATE

REPORT ZEX_POCREATE .



Data: int_pohead like BAPIEKKOC,
      int_poitem like BAPIEKPOC occurs 0 with header line,
      int_posched like BAPIEKET occurs 0 with header line,
      int_ret like BAPIRETURN occurs 0 with header line.
Data: d_purchord like BAPIEKKOC-PO_NUMBER.

Move: 'NB' to int_pohead-DOC_TYPE,
      '1000' to int_pohead-PURCH_ORG,
      '001' to int_pohead-PUR_GROUP,
      '0000001234' to int_pohead-vendor,


      '00010' to int_poitem-po_item,
      'Material' to int_poitem-material,
      'Material' to int_poitem-pur_mat,
      '1000' to int_poitem-plant,


      '00010' to int_posched-PO_ITEM,
      '20080531' to int_posched-DELIV_DATE,
      '2'        to int_posched-QUANTITY.


Append int_poitem.
Clear int_poitem.
APPEND int_posched.
CLEAR int_posched.

CALL FUNCTION 'BAPI_PO_CREATE'
  EXPORTING
   PO_HEADER                        = int_pohead
*   PO_HEADER_ADD_DATA               =
*   HEADER_ADD_DATA_RELEVANT         =
*   PO_ADDRESS                       =
    SKIP_ITEMS_WITH_ERROR            = 'X'
*   ITEM_ADD_DATA_RELEVANT           =
 IMPORTING
   PURCHASEORDER                     = d_purchord
  TABLES
    PO_ITEMS                         = int_poitem
*   PO_ITEM_ADD_DATA                 =
    PO_ITEM_SCHEDULES                = int_posched
*   PO_ITEM_ACCOUNT_ASSIGNMENT       =
*   PO_ITEM_TEXT                     =
    RETURN                           = int_ret
*   PO_LIMITS                        =
*   PO_CONTRACT_LIMITS               =
*   PO_SERVICES                      =
*   PO_SRV_ACCASS_VALUES             =
*   PO_SERVICES_TEXT                 =
*   PO_BUSINESS_PARTNER              =
*   EXTENSIONIN                      =
*   POADDRDELIVERY                   =
          .

If sy-subrc = 0.
  Write:/ 'Purchase Order Number is', d_purchord.
endif.

Five key factors for Data Migration Success

Authored by Ashvinder Rana, Data Migration Lead, Utopia, Inc.









Many of us have been a part of various data migration projects at some point or the other. We all know data is important. But can we name at least five key factors that will ensure a successful go live? Well, here is my two cents (although I believe it's worth a lot more ). Though, I know there are more than just these five key factors the following are my top five.

• Understanding Data - it is absolutely imperative for the data team to understand the legacy data and how it exists in the legacy systems. Along with how the data is structured in the legacy systems.

• Resource Scheduling - now of course, you want the right resources with the right skill sets and knowledge to do your data migration project! Imagine, calling a plumber to fix your AC at home!! I'm sure we would never think to do that. Just the same, we should ensure the data team houses resources with appropriate data skill sets as required for the project.

• Scoping the Requirements Accurately and On Time - not too early, not too late. You know how the saying goes: "there's a time and place for everything!" You don't want to scope out the data requirements before the business blueprint requirements are signed-off on. If you do, then just be prepared for those "change orders" to start rearing their ugly heads well into the beginning of the development phase. Unfortunately we've all run into these way to frequently!!

• Data Quality Framework - ensuring that a data quality framework is in place is equally important among other things that will lead to a successful data conversion. This implies not just having means/tools to perform data profiling and analysis, but also a plan to identify data bottlenecks and recommended solutions and/or data cleansing plan of actions as well.

• Data Validation vs. Data Testing Strategy - projects need to ensure an effective data migration testing strategy is in place and is part of the data migration project. The clear demarcation should be also be made between data validation and data migration testing. Wherein, data validation can comprise random sampling methods to ensure that the data is converted accurately as per the data mapping rules. However, a data migration testing strategy should comprise a series of iterative "mock conversion runs" for all objects in scope where the converted data is utilized by the business process / functional teams to thoroughly test the integration points/transactions as well. In addition, these iterative "mock conversion runs" also allow for validation or conversion programs, conversion error analysis and fixes that will eventually lead to a "zero-error" data migration!

SAP MDM Training-SAP MDM Tutorials,SAP MDM Jobs,SAP MDM Resumes-SAP MDM

We are Mahindra Satyam (NYSE: SAY), a leading information, communications and technology (ICT) company providing top-class business consulting, information technology and communication services. Leveraging deep industry and functional expertise, leading technology practices and a global delivery model, we enable companies achieve their business goals and transformation objectives. 

We are powered by a pool of talented IT and consulting professionals across enterprise solutions, client relationship management, business intelligence, business process quality, operations management, engineering solutions, digital convergence, product lifecycle management, and infrastructure management services, among other capabilities. Our development and delivery centers in the US, Canada, Brazil, the UK, Hungary, Egypt, UAE, India, China, Malaysia, Singapore and Australia serve numerous clients, including several Fortune 500 companies. 

We are part of the $7.1 billion Mahindra Group, a global industrial conglomerate and one of the top 10 industrial firms based in India. The Group’s interests span financial services, automotive products, trade, retail and logistics, information technology and infrastructure development. 

Designation	SAP MDM Consultant
Job Description	 Role - SAP MDM Consultant  Experience -7 - 12 Years  Work Location – Bangalore/Hyderabad/Chennai  Type of Position – Permanent   Lead time to Join – ASAP Roles & Responsibilities:  Should have 7 – 12 Years of SAP MDM experience.  Consultant should have handled minimum 1 – 4 End – End implementation in SAP MDM.  Candidate should be a quick learner.  Ideally the candidate should be flexible to travel for short term durations.
Desired Profile	 Role - SAP MDM Consultant  Experience -7 - 12 Years  Work Location – Bangalore/Hyderabad/Chennai  Type of Position – Permanent   Lead time to Join – ASAP Roles & Responsibilities:  Should have 7 – 12 Years of SAP MDM experience.  Consultant should have handled minimum 1 – 4 End – End implementation in SAP MDM.  Candidate should be a quick learner.  Ideally the candidate should be flexible to travel for short term durations.
Experience	7 - 12 Years
Industry Type	IT-Software/ Software Services
Role	Project Lead
Functional Area	ERP, CRM
Education	UG - Any Graduate - Any Specialization,Graduation Not Required  PG - Any PG Course - Any Specialization,Post Graduation Not Required
Location	Bengaluru/Bangalore, Chennai
Keywords	SAP MDM
Contact	Vijayanath siddhareddy  Satyam Computer Services Ltd
Telephone	9962090069
Email	Vijayanath_Siddhareddy@mahindrasatyam.com
Website	http://www.mahindrasatyam.com
Job Posted	30 Mar

SAP ABAP Editor Icons

If the help of the icons in the SAP ABAP Editor you can do the following from the initial screen.




Check the Program:

The program is checked for syntax errors. One the program is free of Syntax errors you can activate it.

Activate the Program:

Only activated version of the Program can be executed. You can have 2 versions of the program, Active and Inactive. 

Run the Program

The program can be executed by this Icon.

Check the where used list.

You can check where all the current program is used in the SAP system. This can be useful for Includes and Function Modules.

Do the Environment Analysis

Gives a list of Objects used in the Program along with short description and development class.

Online Manual

Gives online documentation for ABAP Statements, Keywords, Objects

Delete the Program

Deletes the Program. Make sure that you have a backup of the program before deleting it. If you have transported the program to Quality or Production then it is possible to retrieve the program. As a general rule always back up the program.

Copy the Program

Makes a copy of the Program.

Rename the Program

Renames the Program

Start Debugging

You can start the debugger from here.

Execute the Program with a Variant

Execute the Program with a variant. You need to create a Variant first. 

Get the Variant List.

If you have created a Variant you can get a list and choose the desired Variant.

LSMW in SAP ABAP

LSMW means Legacy System Migration Work Bench .

SAP offers the Legacy System Migration (LSM) Workbench. The LSM Workbench is a SAP tool that facilitates the process of data transfer from non-SAP system (also called Legacy system) without additional programming to do data conversion. Wecan define the rules for the conversion. The LSM Workbench then generates an ABAP program and thus supports an important step in the process of data transfer.

It is a cross-application component (CA) of the SAP R/3 System and, therefore, is independent from the platform. The tool has interfaces with the Data Transfer Center and with batch input and direct input processing in R/3. The tool can be used in each of the different R/3 releases.

By combining the Data Transfer (DX) Workbench and the Legacy System Migration (LSM) Workbench in SAP Basis component Release 4.6, SAP has made substantial progress towards tackling one of the most costly and time-consuming implementation activities - the migration of legacy systems and the data transfer from ERP systems that are being replaced.

Data migration with the DX Workbench and the LSM Workbench guarantees maximum quality and consistency of your data in the SAP business solution. When data is imported, the system performs the same checks as it does during online entry. The update in your database is performed through the Standard Batch Input Program, Standard Direct Input Program and BAPIs.

Features of LSMW:

Instead of individual tables or field contents, the tool transfers complete business data objects (also called object class) such as Material Master, Supplier Master data. A migration object class is a unit combined from the business point of view, which can be used to transfer the data of all the legacy systems defined in the LSMW to the R/3 System.

The migration object class comprises the R/3 structures as well as the program used for data import. The batch and direct input technique is used to ensure consistency of data. For each migration object, a batch or direct input program has to be available in the SAP R/3 System.

The LSMW main functions are :

• Definition of the legacy system structures and fields

• Definition of object dependencies and assignment of conversion rules
  The structure and field relationships between the legacy system and the R/3 System are defined in data mapping. The way how data is being processed during migration is determined by the conversion rules.

• Data conversion
  From the object dependencies, the LSMW generates conversion programs that translate the legacy system data.

• Data import
  Batch or direct input is used to import the data to the SAP R/3 System.

The additional functions of LSMW are :

• Spreadsheet interface
  Legacy system data in spreadsheet format can be processed.

• Host interface
  Legacy system data in a structured data format (that is, with record identifiers and correct sequence) can be processed.

• Batch input recorder
  The LSMW allows you to use the batch input recorder (shipped with the SAP R/3 standard system) in order to create user-specific classes of migration objects.

• Automatic check functions
  This function generates and performs value checks against check tables and fixed values specified in the Data Dictionary.

Combining SAP ABAP and Visual Composer

Wouldn't it be nice to combine the output from the quick design and code free modeling environment of Visual Composer with the output from a full coding environment like Web Dynpro ABAP or BSP? Actually you can do just such a thing thanks to Portal Eventing.

Let's take a look at just such an example.

 < br>Figure 1: Sample Application

What you see in Figure 1 is the final application running within the SAP NetWeaver Portal. There are two separate iViews within this page. The top iView is a Visual Composer created report. It is displaying summarized data from SAP NetWeaver Business Intelligence combined with some details from SAP NetWeaver Master Data Management.

If you are interested in the inner workings of this Visual Composer report and how it is accessing SAP NetWeaver MDM via the Java APIs, you can find a break down of this part of the application at - Extending Visual Composer through Web Services Vol. 1.

The second iView is actually a Web Dynpro ABAP Component. The purpose of this iView is to show additional details about the selected record. It reads these details from SAP MDM using the ABAP APIs.

Creating a secondary index

There are two types of indexes: Primary index and secondary index. Primary index is automatically created using the primary keys defined. 

Secondary index could be created as per the user requirement. This article discusses about creating a secondary index. 

Go to transaction SE11. 

 

For our demo purpose, we have considered the table ZAUTHOR. 

To know if there are any secondary indexes available, click on Goto à Indexes

 

Following popup appears:

 

From the above screenshot, it is evident that there are no secondary indexes already created. 

Click on Create à Create Index 

 

Enter the name of the index. 

 

Fill in the details – Short description and the fields in the index. 

 

Save and activate. 

Now you can observe the index created above in the list now:

  

Maximum number of secondary indexes we can have are 9.

How to make SELECT statement to make use of any particular secondary index? 

Consider the following example:
SELECT * FROM SPFLI
  %_HINTS ORACLE 'INDEX("SPFLI" "SPFLI~001")'
.......
ENDSELECT.

In the above example, 001 is the secondary index of the table SPFLI. It's a well-known fact that the efficient way of retrieving data from the database tables is by using secondary indexes. Many database vendors provide the optimizer hints for the same. From SAP® v4.5, optimizer hints can be provided by the %_HINTS parameter. This is dependent on the database systems that support optimizer hints. The point to be noted here is these optimizer hints are not standardized by the SQL standards. Each database vendor is free to provide the optimizer hints.
Now to know which index to use for our table:
1. Go to SE11 and there specify the table name
2. Now from the menu, goto --> indexes
3. select the required index.

Now suppose that the identifier 001 represents a non-unique secondary index comprising of the columns CITYFROM and CITYTO. The index name should be defined as:

 <tablename>~<Index Identifier>
like SPFLI~001 in the above example.

The sequence of fields in the WHERE condition is of no relevance in using this optimizers index. If you specify hints incorrectly, ABAP^TM ignores them but doesn't return a syntax error or runtime error.
The code was written in R/3 4.6C.

Code

Consider the following example:

REPORT Suresh_test.

TABLES: spfli.

DATA : t_spfli LIKE spfli OCCURS 0 WITH HEADER LINE.

SELECT * FROM spfli
  INTO TABLE t_spfli
  %_HINTS ORACLE 'INDEX("SPFLI" "SPFLI~001")'.

LOOP AT t_spfli.
  WRITE :/ t_spfli.
ENDLOOP.

SOURCE:http://www.saptechnical.com/Tips/ABAP/SecondaryIndexes.htm

Creating Search Helps (Elementary and Secondary) -- PAGE 2

The Collective Search Help is like this. 

Goto T-Code Se11.

Provide name. Select collective search help button.

Press enter.

Provide the Values

Select include search help.

Then provide search help name, which is already define by the same fields.

Then save it, activate it & execute it. 

Press F4 we can see the output like this.

 

Diff Between Elementary search helps & Collective search helps 

1) Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).

2) Collective search helps combine several elementary search helps. Collective search help thus can offer several alternative search paths.

3) An elementary search help defines the standard flow of an input help.

4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with collective search help.

5) A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field.

6) Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in collective search help, they are expanded to the level of the elementary search helps when the input help is called.

Creating Search Helps (Elementary and Secondary) -- PAGE 1

Go To SE11 T-code.

 

Select the radio button of search help.

 

Provide the search help name. Select the create button. 

 

Select ELEMENTARY search help.

 

Press Enter. 

Provide the short description, the selection method.

Provide the fields.

Save it, Check It & Activate it.

Then execute it.

We can see the screen like this, and then press F4 in this page.

Then press F4 View the output like this.

This is the output for elementary search help.

NOTE: CHECK CONTINUATION ON NEXT POST

Creating a Structure in ABAP Dictionary

Go to transaction SE11 and select the radio button "Data type". Enter a structure name starting with Y or Z. 

Press create button. 

A pop-up screen appears with 3 different options. Select the radio button structure. 

 The screen will be displayed like this.

Provide the description and also components.

Then press SAVE, CHECK and ACTIVATE.

Structure Created Successfully.

Why SAP Customer Relationship Management is the Best Choice?

SAP CRM is one of the leading CRM software in the present time. It has been successfully used by numerous companies all over the world. This software was founded in 1972 and is now still continuing their vision of making their client businesses to become best-run companies, as well as provide services that could help reduce cost, optimize performance and gain knowledge for quick and effective solutions. As of now, it has helped companies from more than 26 industries to be one of the best-run businesses. SAP aids the needs of different businesses whether it's small, medium or a global organization.  There are different CRM providers but why is SAP CRM the best choice?

First, their company is formed by competent, skilled and broad minded people who can guide their clients on the whole process. Your conditions and needs will be analyzed and relevant features may be recommended to you. SAP CRM software is made to provide the information that the company needs to come up with unique and effective strategies that builds a better customer relationship. SAP CRM enables ease and rapid deployment. It is deployed step-by –step that can easily adapt to create a better customer service.

SAP CRM can also help the company to take advantage of every part of customer cycle. It assures that the company makes the most out of every step of the way. It provides end-to-end business process that builds a stronger customer loyalty. This software can be very useful for the different departments of the company such as the sales, marketing and finance department.

Feedbacks on the services of the company were positive. Implementation went smoothly and maintenance cost is low. Some companies that are using it for a long time now had achieved increase in customer retention, repurchasing rate and number of customers. They were also able to lessen abandoned calls for customer service.  Database is very accurate which means problems concerning multiple customer account never occurred.

SAP CRM provides 100% tracking which ensures customer knowledge is provided. It is the key for sale process support. SAP CRM can also be deployed anywhere around the world. So wherever you are, you can trust SAP CRM to aid your need to achieve customer loyalty.

SAP CRM had achieved their vision for some of their client, and if you want your business to be one of them, you should not waste any more time and take some action. Plan all the way through the whole process and focus on your goals. SAP CRM can be your perfect guide to climb the ladder of success.


http://www.freesaptutorial.com/why-sap-customer-relationship-management-is-the-best-choice/