Thursday, July 27, 2006

SAP R/3 : Field Exit from Vijayendra Rao

I was searching the SDN forum on field exit for my latest attempt to modify SAP standard screen fields and I found one contribution from Vijay answering a question put forth by another ABAPer.

I find it is worth saving it up for later use so here is the particulars,

OSS NOTES: 29377

Vijay's explained that,

Field exits are frozen on the 4.6C maintenance level and are not further developed. This means that the existing functionality is kept with all restrictions (see also the last item below). Existing exits can be further used and are called at runtime as usual.Existing exits can be maintained using program RSMODPRF (run theprogram using transaction SE38).

more here

is sky the limit... field exit...

SAP R/3 : BADI HRPAD00INFY for PA40 – Org. Key (VDSK1)

It was quite tedious when the requirement was slated to concatenate Personal Area (WERKS) and Cost Center (KOSTL) to be come an Organizational Key (VDSK1). I make one mistake in this issue while performing scoping. I was not careful enough when activating a BADI (Business Add-Ins).

In this issue, I have tried a different user exit that is made available by the main program in PA40 and include a question put forth to SDN forum.

There is one incident during my submission to ABAP Forum, a certain ABAPer told me that this (HRPAD00INFY) would not be call but just HRPAD00MGEACTIVATE. He was quite persistent on that matter that HRPAD00INFY would not be called up by PA40. So I had proof him wrong. Anyway, there is not much to argue in on this issue as I have marked it as “Solve It On My Own”. Not to say that I underestimate him but one should get their facts right before one confidently point out to others.

-wilstroth, development-

Back to the lead, the concatenation was made possible in PA40 with the use of HRPAD00INFTY with one method called After Input. (please refer to 27 July's Correction below) This method will be called when the user have made the necessary changes to the employee position. At this point, the ABAPer will need a little ingenuity in being creativity. In order to make the concatenation a success in this method, the method should update the PA0001 (Org. Assignment) transparent table. Of course, you will need to ensure that is just update once and correctly. As you see, the BADI is not being called once but twice. Therefore, the consultant will need a certain mechanism to prevent twice updating the table.

Finally, I have solve this problem. I found that searching for a BADI is not that difficult at all. A little pinch of patience and a little pinch of time is all you need in order to look for a suitable one. Not to mention a little pinch of carefulness in the work done.
27 July 2006, Correction:
Actually, the method that should solve the problem is "Before Output" in HRPAD00INFY

Is sky the limit… who says HRPAD00INFY cannot work for PA40?!

Friday, July 21, 2006

SAP R/3 : Data Archiving / ArchiveLink® - Part 1

Just this week, I was requested to do a research on using Data Archive and ArchiveLink®. A project was being carried out on this two topic alone. A certain client from US wanted to archive their SAP system’s data.

Both of these feature is the fundamental archiving components in SAP. Data archive allows the writing and storing of collected data from master data into an archive object ready for archiving into a storage medium. On the latter, ArchiveLink® allows the storing of an archive object stored into an external optical storage medium. Not only it acts as a storage device but it enables scanning and storing, retrieval and digitizing of documentation.

These two basic components, as of from 4.6c above, that is the SAP version, these two grouped together as one function in SARA. SARA or SAP Archive Administration includes the above feature from writing, deletion to retrieval. This include management of data tables for archive, information system on archiving process, schedule and job logs related to archiving. Apart from that, SARA include another archive component known as SARI, SAP Archive Information System.

SARI allows a much greater and flexible retrieval of archived objects for later use. In SARI, one of the components are archive explorer which works like any windows explorer displaying archived objects. These archived objects can be visually display out.

In summary, archiving comprises:

1. Basic archiving tool:
- Data Archiving
- ArchiveLink®
2. Support tools that encapsulate above basic tool:
- SARA (SAP Archiving Administration)
- SARI (SAP Archive Information System)

Is sky the limit… SARA wears SARI!...

Thursday, July 20, 2006

SAP R/3 : Jiving and Raving... still alive and kicking!

Yup, i know it has been a two months long of absence from this technical blog whilst i still update my main blog. It has been a experiencing two months for me on my work.

Apart from trying to get more active in ABAP work itself, i have been involve in CMMI certification which have push my technical work to one side. Also fearing of leaving my team alone to their own things. As you know, that i am also assisting in the scoping of ABAP work; many things had happened. Good it is now that i am no longer doing the scoping. It might mean:

1. More work focus on ABAP.

2. More time on my own technical research.

3. CMMI... gosh... no comment!

I will be expecting more of ABAP work coming and some technical updates.

Oh shoot, i had totally forgotten about my whole MiniSAP installation deal. Yup, the two SAP WAS installation CDs and my SQLServer 2000 CD is still sitting on my desk in my study room. I am still figuring out the day i will harrass these CDs with my notebook.

is sky the limit... ABAP, ABAP, ABAP