Andy's Blog

 
If the field in alv output table is for currency or quantity, we need to do some effort to display it in our alv. you must assign these fields to a currency or unit. There are three ways how you can do this in the field catalog:

• Reference to a Currency or Unit Field
• Value or Unit for the Entire Column
• Format the value field manually

Reference to a Currency or Unit Field

If you define your output table as an structure in DDIC, you need to provide corrsponding reference table and field for currency/quantity field when you activate it. The reference field can be used to display values in the correct user-specific format.

When you read the whole field catalog of the output table using function module ‘REUSE_ALV_FIELDCATALOG_MERGE’, you can automatically fill the field CFIELDNAME or QFIELDNAME in field catalog structure. That means you can fill above two field maually if your output table type is defined in the program not in DDIC.

Demonstrating the value of our customer-focused ecosystem, SAP is collaborating with leading printer manufacturers such as Brother, Canon, Dell, Epson, Fuji Xerox, Hewlett Packard, Konica Minolta, Kyocera Mita, Lexmark, Océ, OKI, Ricoh, Samsung, and Sharp. SAP Printer Vendor program members co-develop solutions for broader support of printer models used with SAP software.

Enabling Best-in-Class Printing for SAP Customers

We recognize that printing is pivotal for business processes – and that the number and capabilities of printer models on the market are growing steadily. SAP and printer manufacturers are cooperating in implementing the best combinations of printer features and SAP technology to benefit our joint customers.

Benefits for Customers

Printing from SAP software can be a critical business activity for SAP customers. They want to know that they can rely on SAP to get the full benefit from their IT investment, including printers. Modern printers offer important new features – such as being able to communicate their status to a central monitor in SAP software, enabling rapid reaction to problems or optimizing cost-effective maintenance.

Now that printer vendors are contributing to the SAP printing environment directly, customers will receive SAP-delivered and -tested software with support included. They will be able to use vendors' printer models out of the box with their SAP software.

Benefits for Printer Vendors

Printer vendors gain access to SAP development systems to develop the optimum support for their devices within SAP landscapes. Vendors can react expeditiously to their own developments – as soon as a new printer model is on the market, they can make it available for SAP customers. Using new enhancements that SAP provides to complement capabilities of today's printers, vendors can add value and differentiate their models from those of competitors.

SAP's Role

In addition to providing the development environment, support channels, and training, SAP is focusing on:

• Infrastructure enhancements to better utilize the capabilities of modern devices
• Joint efforts in identifying and implementing features that benefit business customers

You can get more information from below links:

www.sdn.sap.com/irj/sdn/printing

 
There are several ways to find BADIs in the program.

1. Set a beark-point in method ‘CL_EXITHANDLER=>GET_INSTANCE’. Because old BAID technology will alwasys call this method to get the BADI instance.

2. Search string ‘CL_EXITHANDLER=>GET_INSTANCE’ in the program. This drawback of this method is that the program may call another program in the runtime. In this case, you will be able to find the BADI in another program.

3. You can also go the t-code SPRO, you can also find plenty of BADIs in the related area.

     This article deals with event handling in SAP alv and mechanism behind it. In a nutshell, alv Grid is an implementation of custom control. You must be very familiar with the dynpro programming. In dynpro programming, we general have two events: PBO and PAI. If user have some actions in the frontend screen, the event PAI will be triggered and program can have different reactions according to different function codes. In the custom control, things become a slight different. It will trigger an specific event, if user does some actions in the frontend. There are two types of event: system event and application event.

The only difference of the two events are the sequence of triggering event handler method and the PAI event.

System event: A system event is triggered before any automatic field checks (for example,required fields) have taken place on the screen, and before any field transport. The PAI and PBO events are not triggered. Consequently, you cannot access any values that the user has just changed on the screen. Furthermore, there is no field transport back to the screen after the event, so values that you have changed in the event handling are not updated onthe screen.

Insight of ALV

ALV is an abbreviation of SAP List Viewer. It is a very useful tool for developers to deliver a unified UI to display data. Actually ALV is a custom control which is implemented using SAP control framework. Below is the SAP standard document about the control framework. It is a rare case that you need to develop your custom control, but it is a good way to get the insight view about the ALV.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIGOF/BCCIGOF.pdf

The custom control can be either an ActiveX control or JavaBean. In R/3, we can use ABAP to control to control desktop applications(custom controls). Please find below diagram for detail information about SAP custom control framework.