Thirsty of ABAP

Web Dynpro - Navigation Link

2017-05-08T18:47:00.002-07:00

SAP Webdynpro has its own properties when comes to navigating from windows to windows or views.

First, it'll start from the WD application - interface view - then plug name. From Plug name, that is where the initial process takes place within the interface view. Specifically, it is found in the inbound plug. From The that plug, there is a handler method that calls the outbound plug. From the navigation link (switch window editor view), you will see the navigation link in outbound plug only. That is where the next target view and target plug is defined.

SAP Transaction Code Authorization

2017-03-01T17:59:00.002-08:00

Hello!

Are you wondering if your transaction code is accessible by anybody or not? The answer is very simple. Just make sure that in PFCG the roles or at least one of its role of a certain user (can be accessed through SU01) has the Authorization class AAAB (Cross-Application Authorization Objects) and with Auth. Obj S_TCODE. That is, that S_TCODE should have the value of the transaction code in Auth. field TCD that you would like the user to have access to. This is the first check the system will do before any other authorization checks you have. From S_TABU_DIS to S_USER_GRP.

Thanks!

New Experience It Was

2013-12-19T01:30:00.003-08:00

Hello folks! Wow! It has been a long time since April when I wrote my last blog post about my ABAP Certification. Here we are again to a new beginning - I mean new company, experience, people, and learning. I am looking forward for the task that is assigned to me which will commence by early next year and it will be a knowledge transfer of the new product feature that they have here in my new company. In fact, I have gained a lot of experiences and new skills during that period like CHARM (SAP Change Request Management), HCM, more on Object Oriented Concept, configurations, and the new ABAP Enhancements which I would like to share with you after this topic. But, before that, allow me to share with you first my SAP implementation experience that happened after that April. That was a very surprising
experience after receiving an email from my manager, after two months of smirking without having any project to keep doing busy with, informing me to meet up with my new project's team leader. When I saw that email, of course, I was excited and hurriedly got up, fixed myself, and arrived at the office less than two hours since I read my manager's email. I was a little bit nervous, because in fact, I was not really prepared to go to work that day. The first thing I did, was to look for the room where I had to meet with our team lead and surprisingly there she was smiling, shook my hand, and we started to talk. After hours of discussing about the project, I found out that I will be handling one of the CHARM functionalities and that caused me too much pressure because I will be presenting my design to the client in two days (given Sat and Sun if I opt to be working on that day). So, I went home and immediately shared the story to my wife just to let out the bad feelings that I am starting to experience with the project.

I was with the project for two months. I was involved in creating the functional and technical design of CHARM. My part was for me to implement the what they so called preliminary import of change request objects that will be transported to various SAP landscapes. Our design and proposals as our solution were being discussed with the client in Germany through conference calls. We had encountered a lot of issues and difficulties in dealing with our clients during that time. As on my part, I had difficulties in understanding and dealing with the communications especially with the client because first of all, I do not have any experience in for example initiating the conference calls and to be the host. Being a newbie on the given situation, I just tried to do my best and to make sure that the deliverables and relevant information should be heard clearly by the client and with the whole team. Secondly, our leads or let's say our Solutions Architect. That was very unfortunate, because they were not experts in CHARM. They just pulled out from other teams to fill up the role in order for the project to push through.

To make the story short, we were able to finish the project on time and we got no any issues received from the changes that I made. Despite of the difficulties and challenges we'd faced, I have a lot of lessons learned during the brief duration of that project. I learned deeply the concept of object oriented and the characteristics of being a leader. I learned how narrow and wide casting are important in ABAP object oriented as well as the concept of BOL (business object layer) concept of CRM. On the other hand, I learned also that everyone can be a leader. I mean, leadership skills can be exercised by anyone regardless of your duty or position in a given situation or work.

For me, this is brief enough just to describe the detailed experienced that I had encountered in our CHARM project, but what I am trying to imply here is just to give you at least an insight or idea and the important lessons being learned here.

Thanks for reading folks! Till next time!

Finally Paid Off! - My SAP ABAP Certification

2013-04-16T18:52:00.000-07:00

Already a week has passed in passing my certification in SAP ABAP before I received my hard copy certificate and this is how it looks like:

It took me at least 2 months of reviewing and learning other topics which I did not encounter in my job.

I took the SAP ABAP Certification in Makati office of SAP Philippines in Citibank Tower in April of 2013. I felt nervous, excited and worried that day. I can not help myself but my head keep throbbing and it was very unfortunate time as my father had been rushed to hospital few days before the examination. Prior to the examination month, I had already prepared myself by reviewing various TAW ebooks - thanks to my colleagues in HP (Hewlett-Packard) who shared me their copies of the reviewers.

Every night, I took at least two to three hours of reviewing the TAW ebooks one or two topic each day. I started with the first part of the TAW which is the Netweaver Architecture followed by Memories and Data Dictionaries. I had also spent a lot of time in learning the concept of ABAP Object Oriented Concept. I had also filed a vacation leave on the week of exam and I was spending my time reviewing in McDonald branch or Coffee Bean morning or afternoon while enjoying a cup of coffee with cupcake of course.

Workflow Debugging with Break-Point

2013-02-14T00:44:00.001-08:00

All through out my career in SAP as an ABAP developer, I admit that programming or debugging in SAP Workflow was very rare and seldom that I encountered it in my work. It was then a fortunate time, after 2 years, when one of my projects is using workflow to process its asset posting. I was so lucky then that one of our programmers is an expert in working with workflow which I did not hesitate to take the opportunity to ask so many questions with regards to Workflow especially in debugging. Many of us for sure, especially for first timers, who were assigned to debug a Workflow came across a situation where debugging of workflow was not an easy task or I say at least your break-point was triggered as an attempt to be able to have a peek if what is really happening on the variable that you think is the culprit of your problem! If you are currently looking for the solution, I can say that you landed to the correct page and you are very fortunate since, I was able to perfect and master this debugging dilemma in Workflow environment.

So to start with, there are two types of debugging techniques that I know so far at least in a faster way especially for beginners. These are:

1. Through tcode SWI1 logs and

2. Through background process deactivation

Okay, without any further ado, let's begin with no. 1 - debugging through SWI1:

The first thing that we need to do is to see it that the transaction that needs to be checked includes workflow process, otherwise there will be no logs available in SWI1 for that specific process you are supposed to debug. Okay, so assume that you have a valid workflow process, you may now run tcode SWI1 after running your process or transaction. Below is the screenshot of SWI1 log initial screen:

Then, you may enter the IDentification if you know it, otherwise just proceed if you are just minutes away before landing on SWI1.

So, let us say that you are aware of the item that you are looking for, you should then select it and proceed by clicking the workflow log icon :

Below, depending on your default setting, a workflow log will appear as the below view:

As with my preference, I usually view this on a List with Technical details and this can be found by clicking the second icon on the taskbar.

While on the technical detail screen, you may look for the particular task that you may want to debug. Usually, the last task item appears on the tree is the item where the error occurs. For sure, there are a lot of reasons where the root of your problem may happen within the workflow tasks, but it is likely that the first thing that you may do is through an object debugging. In my example above, let us say we will debug item with the task id TS91000121. So, what we are going to do next is by clicking that task ID with the underline for us to be able to go to its method and to put a break-point as shown on the following screens:

Double click the object type to view the class methods as shown below:

In our example, double click the read_step_occurence to view the ABAP code and you may now look for the line of codes that you may want to put the break-point into.

Okay, I can see now the smile on your face, if not don't worry as we are not yet finished! :)

To start with the actual debugging, let's go back to the workflow log with technical details and look for the request ID generated. This can be found in the container tab and this request id assignment in the workflow container varies from the design of your application:

Once, you have now the necessary parameters, we may now start debugging the workflow class by creating the instance as shown below:

After the instance has been created, you may now run the method of the task and make sure it is where you put your break-point on.

By clicking the above icon, you are then required to enter some parameters to process your debugging correctly.

You may now generate the debugging screen by clicking any one of the clock icons above.

ABS_REQ_EE can be found also in the container together with the REQID.

Then, voila! your break-point is now triggered.

Enjoy and please don't forget to share or like!

Background process: In this case, the break-point should be triggered when running your actual tcode or program and not inside SWI1 unlike the other process above.

1. Put a breakpoint to the method in BOR where being processed by the workflow

2. Double check the particular task where you set the break-point and where the method belongs to.

3. Inside the task, uncheck the background processing

3b. Uncheck the dialog check box when you double click the method in bor

4. Click binding or as long as the agent will become editable. 5. Change the agent fields to User then put your account ID adjacent.

6. Save and Activate the workflow.

Test:

To test, perform your project and after processing it, there should be a workflow item in your inbox - click it and the debugging window should now appear and stop to your break point.

NOTE:

1. If agent field still not editable when unchecking the background check box then you may run swu_obuf to refresh, log-off - log-on or to uncheck and check other checkboxes.

2. Make sure to edit the updated workflow version.

SAP Payment through DMEE

2013-02-04T00:38:00.003-08:00

Follow the bellow steps:

1. Create your DMEE mapping in DMEE tcode:

a. Usually payment is done under tree type PAYM and type the name of your format tree then click create:

b. You should provide proper node hierarchy and the basic should look like the one below:

c. For each node, you should provide a level number depending on how the level is printed in the file
d. You should also determine the proper sorting per level:

e. You may also create the segment to group the element (field in the file).
f. Each element can be mapped in variety of ways as shown in the mapping procedure:

d. Aggregation is usually used in summation

e. Atom is used usually when you want to concatenate nodes.

f. Exit module if there is a special procedure needed before showing the data such as this standard function modules

g. The best exit module that can be used is the "DMEE_EXIT_TEMPLATE_EXTEND_ABA"
    In this module, you may filter the reference node, format tree and other filters you may want to add     based on table FPAYH, FPAYHX, and FPAYP.

h. You may also consider adding a parameter table for each field. In our example below we used country code, country key, reference field, and format tree as parameters:

    SELECT SINGLE SUBR FROM YFIDMESUBR INTO l_wa_subr-subr
      WHERE bland    = wa_item-FPAYP-bland       AND
            bukrs    = wa_item-FPAYP-bukrs       AND
            tree_id  = wa_extension-node-tree_id AND
            ref_name = wa_extension-node-ref_name.

SUBR field will contain your subroutine that you may use to filter specific logic inside the function module exit specific for each country, country key, etc.

2. Determine your enhancement in what category in order to locate the appropriate data in tcode FBZP.

EX:

a. Selecting Payment methods by country in FBZP:

b. Create an entry that should be look like this:

c. Enter the appropriate setup based on the requirements and don't forget to fill up the Payment Medium area:

Notes: Put "DMEE" as node reference for reference type element for type 4 and 5.

SAP Sessions and Memories

2013-01-30T20:38:00.002-08:00

There are different kind of SAP Sessions and Memories that you may use in your programming techniques. In every user or login in SAP, the system creates several so called EXTERNAL Session which contains and has an access in so called SAP Memory through get/set parameter (will discuss this vividly later). Inside the external session, there is another session called INTERNAL Session which composes of different running programs and an ABAP Memory. Each of these programs inside the internal session may access data in the ABAP Memory whereas, SAP Memory may access by the programs within the internal session of the external session.

Sessions and program relationship:

Confused of SAP LUW and DB LUW?

2013-01-28T18:53:00.001-08:00

First of all, let's define LUW ( Logical Unit of Work). LUW as it name implies, it is a series of processes or work in an SAP system which are logically related. For example, one of the processes requires to add the name and employee number in a separate table at the same time or in one instance. Therefore, it is critical to the process to save (commit work) both the name and the employee number at one instance or do nothing at all (roll back).

DB LUW (Database Logical Unit of Work) is simply a generic term being used in referring to database maintenance in logical way i.e commit and roll-back done synchronously or asynchronously.

SAP LUW (SAP Logical Unit of Work) comprises of more than one dialog steps and this is the way SAP handles its DB LUW. To ensure the consistency of database changes, commit and roll back command should be included in the program. There is a technique to ensure consistency of data update within SAP LUW by bundling.

Three type of bundling techniques being used in SAP LUW:

1. Bundling using Function Modules for Updates by using CALL FUNCTION... IN UPDATE TASK
2. Bundling Using Subroutines by using PERFORM ON COMMIT
3. Bundling Using Function Modules in Other R/3 Systems by using CALL FUNCTION... IN BACKGROUND TASK DESTINATION...

I got my ITIL Certificate!

2013-01-14T19:13:00.003-08:00

ITIL Certification is based on the IT Best Practice on Service Management. Advantages of having this are:

based on ITIL Official Site

improved IT services
reduced costs
improved customer satisfaction through a more professional approach to service delivery
improved productivity
improved use of skills and experience
improved delivery of third party service.

An electronically signed certificate :

Value and Check Table

2013-01-13T23:08:00.002-08:00

Value and Check tables are both transparent tables and differs only on the context in where they are being used. An SAP table being used in a domain is called value table and it can be found in the value range tab as shown below:

In an ALV grid, if you want to create a drill down help popup window or F4 function, you may either choose Single Values (limited to 10 characters), Intervals, or Value table. In choosing Value table, you need first to create you transparent table, usually contains columns for the value you want to display in your ALV and the description of that particular value, and populate your records or entries as shown below:

Typically, in ALV F4 function, the popup window being shown will contain the Single values unless you made your transparent table as the check table of your ALV table as shown below:

So, the question is, how this value table becomes a check table. The answer is simply making the component or the field of the table above as foreign key by clicking the button that looks like a key:

Below is the window to make the table as check table and you may also add the columns in the F4 popup by making it as primary key.

In my case, MANDT, ACTION, and DESCR fields are the primary keys. Therefore, if the user clicks the drill down or F4 button, the below window should appear:

NOTE: Check table is used to validate the data being inputted - foreign key table level. Value table will contain the data for check table - domain level. Search help should contain the values of the table specified on the parameters. Therefore, if there are check table and search help, search help's table values will be shown and check table will be used as look up for the value being inputted in either selection screen or alv grid cell.

Until next time!

Have a great day!

Important ABAP Questions Usually Missed Out!

2012-12-14T02:41:00.001-08:00

Hi folks! Below are some of the questions that I encountered during my interviews. It is very hard to face the interviewer if you do not know how to answer those questions as they appear as basic. So, what I did, was to write down what I have remembered and add them on this list.

NOTE: Don't forget to memorize all the important FMs used in ABAP development.

1. What is needed to add a custom field to a standard table. -custom includes staring in CI or append structure button

2. What is the type needed for a table field to accept a negative and positive symbol and what are the steps.
- The data type of integers, i, has a value range of -2147483648 to +2147483647 and contains integers only. You can specify integers as numeric literals directly in the program.

3. Difference between a BAPI and FM. - bapi is stored in bor, remote enabled, pre-defined standard processes from SAP while standard FM is the opposite.
sample BAPI - BAPI_FIXEDASSET_CREATE1

4. Difference between a BAPI and RFC. -BAPI in BOR and call standard sap process while RFC is the gateway to call a remote-enabled FM like BAPI.

5. The different kind of exits.
- menu exits
- screen exits
- FM exits
- field exits

6. Steps in creating a BADI
- you need to put a break point inside class ‘CL_EXITHANDLER’

CALL METHOD CL_EXITHANDLER=>GET_CLASS_NAME_BY_INTERFACE’

of method get_instance
SE19 you will create a new copy of badi method you have detected (starting in Z) or in oop concept you will redefine(polymorphism) it. Then, in SE18, there you will see the actual coding of the method you are copying. In there you can copy paste the FM being called by the standard method and put it on your redefined badi method.

**Advantage of BADI**

The main advantage of this concept is the capacity for reuse. Once implemented, a Business Add-In

can be reimplemented by other links in the software chain**TAW10

7. Difference between a BADI and user exits.
- badi is more of OOP while user exits are the usual abap exit using FMs.

8. How to convert Smartforms/Sapscript to PDF
- get the otf file
- convert the otf file to pdf by using a certain FM
- then call an FM to download the file

9. How to format a currency using WRITE in classic list.
set country 'US' or character. If 'US' or any character the represents it is blank, then it will used what it is defined in master record or sap sytem config, otherwise it will search the one in t005x table.
set currency will override set country

10. Difference between layout and fieldcat setup in ALV.
-layout, will affect the whole alv functionality
- fieldcat for each specific field

11. How to read file and what is the FM used.

12. Difference between a GUI download and OPEN Dataset FMs.

GUI_DOWNLOAD - download file to local/presentation server, while OPEN Dataset from applicaiton server.

Running ABAP Program in batch mode is capable only of handling file from application server thus the abap statement below are the only means for you to handle data transfer running in batch mode:

OPEN DATASET
CLOSE DATASET
DELETE DATASET
READ DATASET
TRANSFER

13. What are the sample BAPIs.
- BAPI_fixedasset_create1

14. Define field-symbols.
- placeholder to a certain variable. they do not reserve space but pointing the variable value to it after referencing.

15. Logical DB advantage and disadvantage.
Advantage: Centralized authorization check, Own pre-defined selection screen, Faster retrieval of data through its hierarchal design
Event of logical DB is get. It invokes the pull event handler in LDB program (created in SE36)
Event get late - is performed after all the tables in the lower part of the hierarchy have been processed

16. How to create text fields.

17. How to create a text table - Create ID table then the Text Table by linking their keys by making it foreign.

18. What are the implications of mandt - client dependecy such that if not included in a table, data is visible across boxes/clients.
- usually not including mandt is used in SAP system tables wherein that table data will be used accross clients

19. Ways to add data to a database tabale
- modify, will update the data, if not found it will insert the data
- update - it will only update existing data otherwise error
- insert - add the new record which is not existing, otherwise error

20. Ways to add data to abap internal table
-
21. Types of SAP Dialog events
- Process Before Output (PBO) - triggered before screen is displayed
- Process After Input (PAI) - triggered after the screen is displayed
- Process On-Help Request (POH) - F1
- Process On-Value Request (POV) - F4
----------------------ADDITIONAL QUESTIONS--------------------

22. Types of ABAP tables:
- Index tables and hashed table
- Index tables are standard table and sorted table
- Hashed table is only hashed table
- Standard table can be accessed by using an index or key
- Sort table can be accessed using an index or key and sorted in ascending order by default

23. ALE, EDI, IDOC
- ALE- Application link Enabling, enables linking between two systems
- 3 Layers of ALE are Application layer, Distribution layer, and Communication layer
   - Application layer - refers to the applicaiton data such as SD, MM, FI, HR etc
   - Distribution layer - wherein data is determined to whom it will be distributed and formatted
   - communication layer - this is where the transfer of data takes place through RFC, TCP etc

- EDI is a translator of IDOC data. Usually it is a third party component.
- it is comprised of outbound and inbound process

IDOC - is a transporter of the data being passed to ALE. te data being hold is arranged in a structured format.

24. How SAP table handles uppercase/lowercase queries?
- this can be done in domain level. By default, the domain data type will convert any characters to uppercase unless the it is selected in the domain lowercase tick box.

25. SAP Memory types
- ABAP Memory -> can be accessed by the programs within internal session using import and export parameters
- SAP Memory -> can be accessed by different programs across external sessions using GET/SET(GPA/SPA) Parameters

Authorization Check (FM)

2012-06-07T18:37:00.000-07:00

After our QA checked our program, she found out that we are not checking auhtorization before calling a tcode. Upon checking the program, other "CALL TRANSACTION" statement is using function module " AUTHORITY_CHECK_TCODE" to check the authority before calling a tcode. This is very simple to use by just passing the tcode you want to call and make sure to declare the exception parameters for you to be able to handle the appropriate returned error code.

      CALL FUNCTION 'AUTHORITY_CHECK_TCODE'
        EXPORTING
          tcode  = [tcode]
        EXCEPTIONS
          ok     = 1
          not_ok = 2
          OTHERS = 3.
      IF sy-subrc NE 1.
        wa_errmsg-type = c_error.
        wa_errmsg-message = 'No authorization for Transaction'(031).
        APPEND wa_errmsg TO p_tb_errmsg.
      ELSE.

Happy coding everyone!!

SAP SpecialTables

2012-04-10T23:06:00.001-07:00

I came across this topic "SAP Special Tables" upon reading my SAP ABAP Certification ebook. SAP Special Tables are very common table types of SAP that we as ABAPERs encounter from our day to day ABAP development. SAP Special Tables are very common in ABAP and very important as far as SAP technology is concerned. They are simply tables that contain the business data needed by everyone using SAP technology.

These special tables are called Transparent, Cluster, and Pooled tables. You may find various definitions and comparisons in the internet if you like but, I noticed that those definitions are described commonly based on textbook type of explanations which for me I found it difficult to understand quickly esp. by the newbies. So, I decided to write this down immediately after compiling my own understanding and figuring out how I am going to plot and describe it here through my blog.

First, I will explain one by one the definition and how these tables are used and how to create one of them in SAP. Let's start with Transparent table:

Transparent table - is a type of table in SAP with a direct relation to the database itself. meaning every time you create a transparent table, there should always a corresponding instance as one to one physical relationship in a database table. The below picture shows how ABAP tables relate to the database tables from dictionary logical view relationship.

Creating transparent table can be done in SE11. Changing the type can be done by clicking extras and Change Table Category.

Cluster table - is a special table contains many cluster tables and grouped them into one table by combining each of their keys whichever is identical otherwise create a new key field. As you can see on the above picture, cluster table is composed of various cluster tables in dictionary logical view but it is made of only one physical database table.

Pooled table - simply a combination of various tables regardless of the key combination. Meaning keys are not combined but rather treated them independently for each table being pooled.

The below picture how pooled and cluster table differentiate to each other by means of UNION.

The letter shows the keys, if you noticed, in cluster same keys are combined to produced only one key in the database table while in pooled keys are treated independently.

Alv events for real time scenario

2012-03-08T00:26:00.002-08:00

It has been so long that I have not been able to update my blog. I was quite busy with left to right projects to one of our clients.

Today, I want to share with you on how to handle oop alv using events specifically if front-end data has been changed. I.e sorted, deleted or filtered. On the following scenario below, I am going to present to you my own approach on how to deal with issues regarding alv front-end changes.

Steps:

1. Create a wrapper class for " set_table_for_first_display " method of cl_gui_alv_grid to handle "changing" internal table - meaning every time there are changes on the alv front-end, we will be able to capture and to read the appropriate record or data being clicked (hotpost_click event), changed (user_command event), etc.

2. Create a constructor (class' method called during creation of an object - typically for initialization of attributes) for your wrapper class for us to be able to send the cl_gui_alv_grid object coming from our main program. Our main program should act as a caller for the wrapper class by passing the appropriate parameters for "set_table_for_first_display_ method as shown below:

  variant-report = sy-repid. "to save the alv layout
  variant-username = sy-uname. "to save the alv layout
  variant-variant = alv_var. "layout name

  CREATE OBJECT obj_alv_pir01
    EXPORTING
      i_object = grid1
      .

  CALL METHOD obj_alv_pir01->set_table_for_first_display
    EXPORTING
      is_layout       = wa_alv_layout
      is_variant      = variant "to show the alv layout button
      i_save          = 'A' "to show the alv layout button
    CHANGING
      it_outtab       =   tb_final
      it_fieldcatalog = tb_fieldcat

3. In our wrapper class, declare a static attribute for our internal table that will handle the it_outtab of "set_table_for_first_display" method. Note: parameter "changing" means that changes of an it_table inside the called method will reflect also to the it_table of the calling program.

4. Inside our event, let us take event USER_COMMAND, we should do the below code in ordfer for us to capture the appropriate line of records being selected from the ALV front-end. "NO matter what happens to the front-end data will also reflect to our static table as shown below":

  DATA lt_selected_rows TYPE lvc_t_roid .
  DATA ls_selected_row TYPE lvc_s_roid .

  CALL METHOD grid_object->get_selected_rows
  IMPORTING
  et_row_no = lt_selected_rows .
  READ TABLE lt_selected_rows INTO ls_selected_row INDEX 1 .

  IF sy-subrc ne 0 .
    MESSAGE s000(su) WITH 'Select a row!'(203) .
    EXIT.
  ENDIF .

  READ TABLE ZCL_ALV_PIR01=>tb_final INDEX ls_selected_row-row_id INTO l_wa_final.

That's it! If you have any clarification, please don't hesitate to post a comment.

Have a nice day!

TAW review season 1

2011-12-17T10:03:00.000-08:00

Hello Guys, hope you are doing well this coming holiday season.

I would like to let you know that I will be posting some topic with regards to TAW reviewer in this coming days. TAW reviewer helped me a lot in passing my ABAP certification as well as helps me in my day to day ABAP job.

If you have any suggestions or topic that want to discuss I would be happy to cover them up!

Until next time. Please don't forget to check out my posts soon.

Happy Holidays everyone!

(For a complete copy of TAW reviewers, please email me at awesome_nope@yahoo.com)

Adding standard ALV toolbar button in OOP

2011-11-28T21:02:00.000-08:00

Below are the simple steps in adding a standard ALV button using OOP.

1. Create a class that will handle the TOOLBAR event and insert the code for the particular button

2. Include the event in your main program:

SET HANDLER obj_EH_ALV_FORECAST->HANDLE_TOOLBAR FOR grid1.

Translating your SAP text

2011-09-26T00:38:00.000-07:00

Have you ever encountered language translation problem or any SAP related problem with regards to language? In this topic, we are going to address that issue of yours. Just follow the below simple steps:

1. In your ABAP editor or any editor that you are currently on as long as it has a toolbar above and you can find this path:

GOTO-> TRANSLATION.

then put the corresponding language you may want to translate. On the example below we are going to translate german to english:

then locate the program by double clicking it then you will see the text that you might need to translate in order to show in your SAP application when you run:

In our case, we will double click FBAS row then just change the text that you may want to translate then SAVE!

And that's it!

Converting a SAPSCRIPT to PDF

2011-09-14T01:56:00.000-07:00

Below are some of the things that you need to do in order for the sapscript to be converted into a pdf file. (We need to convert the spool instead of otf)

1. Make sure to move values to the ff. fields of OPTIONS parameter of FM OPEN_FORM:

                           TDCOPIES     = 1.
                            tdpreview   = ''.
                            TDNOPRINT = ''.
                            tdnewid     = X.
                           TDIMMED = ''.
                            TDPREVIEW = ''. "to avoid showing the sapscript

  CALL FUNCTION 'OPEN_FORM'
       EXPORTING FORM = XFORMULAR
                 LANGUAGE = EKKO-SPRAS
                 OPTIONS = ITCPO
                 ARCHIVE_INDEX  = TOA_DARA
                 ARCHIVE_PARAMS = ARC_PARAMS
                 DEVICE = XDEVICE
                 DIALOG = XDIALOG
            MAIL_SENDER        = LVS_SENDER
            MAIL_RECIPIENT     = LVS_RECIPIENT
       EXCEPTIONS CANCELED = 01.

2. Get the RESULT-TDSPOOLID of CLOSE_FORM and move to FM "CONVERT_OTFSPOOLJOB_2_PDF" to convert to pdf as shown below:

      CALL FUNCTION 'CONVERT_OTFSPOOLJOB_2_PDF'
        EXPORTING
          src_spoolid              = RESULT-TDSPOOLID
        TABLES
          pdf                      = it_pdf_lines
        EXCEPTIONS
          err_no_otf_spooljob      = 1
          err_no_spooljob          = 2
          err_no_permission        = 3
          err_conv_not_possible    = 4
          err_bad_dstdevice        = 5
          user_cancelled           = 6
          err_spoolerror           = 7
          err_temseerror           = 8
          err_btcjob_open_failed   = 9
          err_btcjob_submit_failed = 10
          err_btcjob_close_failed  = 11
          OTHERS                   = 12.

3. You may then transfer the pdf file to your local directory directly

        CALL METHOD cl_gui_frontend_services=>gui_download
        EXPORTING
              filename          = l_AFILENAME
            filetype             = 'BIN'
           append                = 'X'
           CHANGING
            data_tab             = it_pdf_lines[]
        EXCEPTIONS
            OTHERS               = 1.

OR you may opt to save in a different location

          CALL FUNCTION 'DOWNLOAD'
               EXPORTING
                    FILENAME     = l_filename_d
                    FILETYPE     = 'BIN'
               IMPORTING
                    ACT_FILENAME = AFILENAME
               TABLES
                    DATA_TAB     = it_pdf_lines[].

4. Make sure to get the file in the location were you saved the pdf file for the FM below will function properly:

** this will open the pdf file in PDF reader like ADOBE ACROBAT READER, etc.

            CALL FUNCTION 'WS_EXECUTE'
                  EXPORTING
                    document           = c_x
                    program            = l_AFILENAME
                  EXCEPTIONS
                    frontend_error     = 1
                    no_batch           = 2
                    prog_not_found     = 3
                    illegal_option     = 4
                    gui_refuse_execute = 5
                    OTHERS             = 6.

Then you are done!!

Cost Center and HR master exits and BADIs

2011-09-13T22:25:00.000-07:00

FOR COST CENTER master

1. Determine the receiving Partner Profile to receive.
2. Put COSMAS as message type on the receiving partner (only specified partner will have the extended sgment)
3. include YCOSMA01 as the extended idoc for COSMAS mess type basic idoc COSMAS01
4. add additional code in badi :
   implementation name: ZCOOM_CI_CSKS_IDOC
   definition name: COOM_CI_CSKS_IDOC
   interface name: IF_EX_COOM_CI_CSKS_IDOC
   implementing class: ZCL_IM_COOM_CI_CSKS_IDOC

       CODE: upload data to segment as long as cost center date is valid.

FM: MASTERIDOC_CREATE_SMD_COSMAS <--- exits can be found here

FOR HR master

1. Determine the receiving Partner Profile to receive.
2. Put HRMD_A as message type on the receiving partner (only specified partner will have the extended sgment)
3. include YHRM_AEX1 as the extended idoc for HRMD_A mess type basic idoc *****
4. add additional code in badi :
   implementation name: ZCOOM_CI_CSKS_IDOC
   definition name: COOM_CI_CSKS_IDOC
   interface name: IF_EX_COOM_CI_CSKS_IDOC
   implementing class: ZCL_IM_COOM_CI_CSKS_IDOC

FM: MASTERIDOC_CREATE_SMD_HRMD - use BADI HRALE00OUTBOUND_IDOC or EXIT_SAPLRHAL_001 EXIT_SAPLRHAL_003
in smod -> RHALE001

in this case use: here put the values:EXIT_SAPLRHAL_001 here modify segments: EXIT_SAPLRHA0_001.

take note also of :EXIT_SAPLRHA0_004

RH_MASTER_IDOC_DISTRIBUTE_HRMD -> this is where the main loop happens including badi

PROGRAM for first hr run: RHALESMD (in se38)

NOTE: idoc filtering is done only in BD64 and it includes only direct comparison of values. Programming is done in BADIs

Configuration for message type HRMD_A change pointer

2011-09-13T22:20:00.000-07:00

1. Use message type hrmd_a (Your custom IDoc should have a Message Type and the Change Pointer should be activated for this Message Type. You can activate this via transaction SALE)
2. Use bd59 to define ALE obj
3. Activate change pointer globally in bd61

4. Activate change pointer of message type in BD50
5. then BD52 - Activate Change pointers for the custom fields
6. BD60 for FM
7. BD66 (Segment Field-Change Document field)
8. bd64 model view (this is critical for activating any IDOC process)
- for filtering, use bd66 and bd95 to add the field that will be used in filtering

Please let me know if you have any question or clarification. I am willing to help you.

Just a checklist for ALE change pointer configuration

2011-09-13T01:39:00.000-07:00

I want to share the steps in ALE/IDOC/EDI configuration.

Below are the steps to look at in creating change pointer. The ff. steps are standard all across SAP IDOC/EDI/ALE related projects. No matter what you are aiming for as long as change pointer or IDOC is concerned, you are required to consider the steps below:

1. SM59(Create RFC destination)
2. WE21(Create TRFC-PORT)

3. WE81(Create Basic type IF required)
4. WE31(Create Segment,IF required)
5. WE30(Create Basic type, IF required)
6. WE82(ATTACH BASIC TYPE WITH MESSAGE TYPE, IF required)
7. SCDO(Create Change Document, IF required)
8. BD50(Activate Change Pointers for the Message type,IF required)
9. BD52(Create Change Document Items for message type,IF required)
10. BD60(Attach FM,Basic type and Message type,IF required)
11. BD61(Activate Change pointers globally)
12. WE20(Create Partner Profiles , specify the reciver logical system)->In the Outbound Parameters , specify the message type, basic type, port information…)
13. BD64(Create model view)
- for filtering, use bd66 and bd95 to add the field that will be used in filtering
14. BD21(To Create the idocs) or run program RBDMIDOC.

Hope you find it useful. More IDOC related topic to come! So watch out for it!

Change pointer in IDOC (when data was changed)

2011-07-07T00:35:00.000-07:00

Change pointer is the process in SAP IDOC triggered every time there are changes on master tables for both fields and records. Thus, for example you add or edit any information with your customer information and once change pointer program has been triggered, then that is also the time it will be populated and will create an IDOC. Change pointer can also be setup in a customized IDOC or message type.

Change pointer is similar to document change that is updated in tables CDPOS and CDHDR, while CP is in BDCPS and BDCP.

Usually, standard master tables have already designed by SAP to have their own configured change pointers or IDOC/EDI/ALE related setup. So, if you are planning to create a customized IDOC, you need to consider various configurations and setup in order for your change pointer and IDOC to work properly in SAP.

Below are the list of tcodes for change pointer setup:

1. SM59 (Create RFC Destination)
2. WE21 (Create TRFC Port)
3. WE81 (Create IDOC Basic type if required)
4. WE31 (Create segment if required)
5. WE30 (Create Basic Type, If required)
6. WE82 (Attach Basic type with Message type, if required)
7. SCDO (Create change document if required)
8. BD50 (Activate Change Pointers for the Message type,IF required)
9. BD52 (Create Change Document Items for message type,IF required)
10. BD60 (Attach FM,Basic type and Message type,IF required)
11. BD61 (Activate Change pointers globally)
12. WE20 (Create Partner Profiles , specify the receiver logical system)->In the Outbound Parameters , specify the message type, basic type, port information…)
13. BD64 (Create model view) - This is where IDOC filter setup is done (BD56 for segment filtering)
14. BD21 (To Create the idocs) or run program RBDMIDOC.

Tricky steploop in screen painter (SE51)

2011-06-28T01:35:00.000-07:00

Recently, we have a problem in our standard transaction regarding the pop up dialog being shown. The dialog is originally created by SAP called POPUP_TO_DECIDE_LIST. The dialog shows only 25 radio buttons that when displayed, it is exactly as tall as the monitor screen.

One of the business requirements is to enhance the dialog to be able to show at least 200 rows or all the records in the master table of credit cards as this is related to a credit card transactions. We have contacted SAP and they tell us that this was already addressed by OSS note 1108382. Meaning, there is no need for us to do coding anymore as we just only need to apply the OSS note. But, there is a problem as we've
discovered after applying it using tcode sNote that it is only applicable for SAP BASIS version 7and we have only version 46c or lower. So, SAP expert told us that we can opt for a work around, by supplying a key, for us to be able to edit the said FM. So, below were the steps that I want to share with you on how we able to do it:

BEFORE:

AFTER:

1. Go to SE51 (screen painter)

Type the program name and the screen number to edit. SAPLSPO5 and 0101 for example then change

2. Go to attributes tab and change the mainten. edit field to 200. This will increase the length of dialog screen.

3. Then click the layout button above.

4. While on the layout screen, click edit/change then highlight all the group with radio button and text box then change the height to 196. This can be found at the upper right corner after highlighting.

5. Make sure to turn off the ASSISTANT in edit->modification operation->switch off assistant before changing the step loop to variable or fix.

6. Change your step loop to fix when you want to show the dialog with a scroll bar and variable if you want your dialog can be adjusted. They can be found in edit->grouping-steploop->define/fix/variable/dissolve.

That's all! Hope you find this interesting and useful!! Please don't forget to like us and follow us. Thank you!

Maintaining a table hastle free

2011-06-28T00:28:00.000-07:00

Maintaining your customized table with your own tcode and program did ever cross your mind?

There's a very easy way to address your problem by creating a TCODE in se93 and choosing the parameter type tcode. By calling SM30, skipping initial screen then at the bottom part, you may include the table name (add VIEWNAME under name of screen field) and assign whether it can be updated (X) or not (blank) (add UPDATE under name of screen field).

To start with, in SE11 after creating your table, tech settings, etc. go to Utilities->table maintenance generator. Save your changes.

Prerequisite: Make sure that the below where assigned to table:

If you want to add new fields, you may go to se11--> change--> utilities--> table maintenance generator-->generated objects--change-->new fields table and press enter and generate (click key or normal fields as well as click the screens to regenerate new)

Note: Put &NC& in Authorization Group and the table name in function group field if you don't assign any authorization..

Don't forget to adjust and activate your db in se14. then generate again.You may want also to modify your generated function group codes i.e changing screen layout, column names, etc.

Hope you find this useful. If you have questions or comments, please don't forget to put. Thanks!

Transferring/receiving data from SAP r/3 to other box or third party software

2011-06-23T21:57:00.000-07:00

Many existing organizations run their business from a different systems or platforms. This may include SAP R/3, JAVA J2EE, .NET or legacy systems such as Mainframe/COBOL.

In legacy systems, transferring data is usually done through a dump file or a txt file which has been formatted according to agreed format with the handler system.

In SAP, transferring data is done through IDOC using ALE and EDI technology.

IDOC stands for intermediate document comprises of a segment and fields that forms a certain file layout. In non-SAP system, their IDOC is commonly referred as the input and output dump file or simply text file. In SAP, it is quite more sophisticated and intact. IDOC in SAP world is used as a medium of transferring data to one box or to a third party software.

IDOC will work only by configuring it with ALE and EDI technologies. ALE stands for Application Link Enabling or a technology incorporated by SAP to synchronize and to manage the changes done between data of separate boxes within SAP only.

EDI stands for Electronic Data Interchange. This serves as the medium to transfer or to communicates the IDOC to other system outside SAP in order for them to be transferred and delivered successfully.

Thus, without ALE and EDI, IDOC will not work properly. These three entity should always be observed and maintain properly in order to address sending and receiving of SAP file or data to and fro within and outside SAP.

SAP EDI bounderies:

SAP ALE outbound process

Sending receiving architecture/workflow

You may want to visit also: http://wiki.sdn.sap.com/wiki/display/ABAP/ALE,IDOC