How to add standard infotype to PPOME tab

So we have standard infotype which is not shown in PPOME transaction. We want to add standard infotype to PPOME tab to help users enter data. Let’s take infotype 1039 “Shift group” for our example. Usually, we use it for shift planning in time management (transaction PP61). It’s recorded for Organizational units (object type “O”). So it’s easier to enter this infotype in PPOME than in PP01 as SAP advise.

There are three steps to make it happen. We need to create a new screen, it’s logic and enter it in customizing tables.

Read More


SAP Change Pointers in 4 steps

Today we will talk about SAP change pointers. Change pointers are that thing, which registers all object changes, which you need to send over ALE to other SAP or non-SAP system. For example, you have changed SAP HR infotype (let’s say infotype number 0002), the system records these changes internally, creates change pointer object. Then according to your ALE settings it sends updated record immediately or based on the scheduled job. So it sends only that one 0002 infotype record, not every record, not the whole bunch of infotypes. It saves a lot of time, increases SAP performance and decreases network load. Very convenient and smart in other words. There are just four steps to configure SAP change pointers for HCM or any other SAP ECC (Enterprise Central Component) module.

You can set up change pointers very easily with these 4 steps

  1. How to activate change pointers in SAP? With transaction code BD61 SAP activates change pointers across the whole system. It’s a best practice to activate change pointers only in these systems you have and manage data (like test or quality system and a production system).
    Activate Change Pointers in bd61

    Activate Change Pointers in BD61 transaction

  2. BD50 transaction activates change pointers for specific message type (or object). For SAP HCM it would be HRMD_A.
    Activate Change Pointers for HRMD_A IDOC

    Activate Change Pointers for HRMD_A IDOC

  3. Schedule RBDMIDOC program periodically to send IDOCs (the outcome of the change pointer) over ALE integration layer. The program reads change pointers tables, creates IDOCs with changed data and pushes them to ALE layer.
    RBDMIDOC

    RBDMIDOC

  4. It’s recommended to clean change pointers tables periodically. You can do this manually in BD22 transaction or automatically with RBDCPCLR program scheduled.

If you want to track specific fields, I mean, when a specific field in infotype is changed, then in SE11 in ABAP Dictionary select needed data element, switch to ‘Further characteristics’ and tick ‘Change document’ checkbox. Now changing this field in any infotype will cause a new change pointer and data change sending through ALE. Configuring change pointers is a one step in a whole SAP ALE configuration procedure.

Don’t forget to setup the whole SAP ALE landscape to send change pointers over. You can find step-by-step SAP ALE configuration guide in my other post here: 


Working with OS level from SAP

We have a task – manage OS level requests from SAP job scheduling tool (SM36 transaction). You know, there are a lot of tools to perform OS level tasks, that are built into OS or some 3rd party tools, which support command line access.

For example, I’ve created a simple executable file with just one command:

echo “SAP running” >> sap.log

We want to run this script from OS level locally on the server where SAP is running. Then, remotely, where no SAP system is installed.

Read More


Data conversion in SAP ALE

Some time ago we discussed SAP ALE, what it is, how it works. Here is the link. Today I want to share with you how we can change data on-fly when we need to do some conversion during the integration process.

Usually, we need conversion in heterogeneous landscapes, where different systems presented with miscellaneous settings, types, architectures. Let’s say you want to include a new SAP ERP during company acquisition into your landscape. There will be another business unites codes or personnel numbers, which differ from your present system. Or you want to send some flag depending on your conditions in the source system. Here data conversion rules come into place.

When you do SAP ALE configuration, you usually use IDOC conversion rules. So to start with conversions, have a look at these three IMG paths. Run SALE transaction and scroll down to our menu.

Read More


How SAP ALE works

What is SAP ALE?

SAP ALE – Application Link Enabling – data exchange technology, developed by SAP AG. It’s a technology because it has a set of tools, protocols, formats which allow exchanging data in real-time or offline between SAP or non-SAP systems. It’s a huge layer of settings, functionality, and opportunities which we rarely use. Let’s have a look at this stack and short SAP ALE configuration guide.

SAP ALE communication stack

CPIC – Common Programming Interface for Communication – low level communication protocol. You can read further here https://www-01.ibm.com/software/network/commserver/windows/library/cpic.htm
RFC – Remote Function Call – high level communication protocol to call remote functions
tRFC (transaction RFC) / qRFC (queued RFC) / aRFC (asynchronous RFC) / sRFC (synchronous RFC) – a way to deliver messages to the receiver with confirmation
IDOC – Intermediate DOCument / BAPI (Business Application Programming Interface) – message format
EDI – Electronic Data Interchange – data exchange procedure between SAP-nonSAP systems. International standard by chance.
ALE – Application Link Enabling – data exchange procedure between SAP-SAP.

Here is what I suggest you to discuss.

The CORE of SAP integration in SAP ALE layer

RFC – Remote Function Call, is a mechanism to call functions remotely. The idea is simple and works this way. We know some functionality exists on the remote server. ‘Hey, server, I know you have this function, I know the parameters. I want you to run it on my behalf but on your side Here is my authorization. Give me the result.’ Server spins hard drives and once it makes sure I’m not a little theft, it runs the requested function with my login.  Any other program can run the same function on that same server locally. A checkbox in SE37 transaction makes the difference if it could be run remotely.

Read More


SAP BUILD and a new reality for functional consultants

I like to embellish events when it comes to SAP, business, and future, but usually, it comes true in a while. Everything goes simple and complex simultaneously. Business rules go to ease, underlying systems and mechanisms go to complexity. I’m looking at SAP SuccessFactors and wondering how business discards their on-premise strong and robust solutions for SAP SF, which is that simple, like a child and adult. It’s not about reliability, user experiences, but more about processes, that business know-how, and best practices which make you unique on the market. The lyrics are over. The trend to SF dictates new rules for classic SAP consultants and developers. There is almost no ABAP, custom reports, SmartForms, and user-exits. New functional paradigm is to become a technical support and developer guy in a one person, who supports already made up decision by vendor, and develops extentions for business customers. Open-source techniques came to SAP world in terms on clouds, Angular, WebIDE, Splash, Build, jScript, jQuery, REST, LESS, etc. These are the commons we need to learn to be able to serve customers.

I spent some hours to understand my future and here is what I see. This is a microprototype for my microunderstanding what I was trying to say in the paragraph above.

Read More


Setup data audit in SAP HCM with couple clicks

Hello, my friends.

I’m quite confident you have met this situation quite a lot when somebody has changed something and there is no trace. SAP data audit in SAP HCM can help you a lot with this. HR data audit will track all data changes made by end-users to help you easily find what had happened. As an experienced professional I personally setup data audition the first-day end-users start working with the system. Right after HR data migration is over.

Setup data audit for organizational management objects (Organization Chart)

Customizing is performed in T77CDOC_CUST view

To view data use report RHCDOC_DISPLAY

Setup data audit for employee management objects

Customizing is performed in views:

V_T585A – include infotype into audit

V_T585B – include specific fields into audit

V_T585C – define field groups for audit. There is a checkbox to define storage period. It allows defining for what reason we store data changes history. If it’s ‘L’ then this information works best for audit and Long-term storage. If ‘S’ – short-term – SAP recommends using this data to transfer to other systems. Some sort of IDOC, frankly speaking, but very cheap and lazy.

Audit data can be viewed in the RPUAUD00_PNPCE report.

If you want to develop your own change doc use transaction SCDO.

Detailed explanation could be found at http://help.sap.com


Archiving HR data with SARA to comply with GDPR

Hello, everyone.

Most of you know about archiving HR data, that there are a number of layers to backup your information system. For ERP class systems there is operating system level backup, database backup and sometimes ERP itself can do a backup.

In SAP functional consultants usually, mix backuping and data archiving. Backups stand for system copy and data copy that basis guys do regularly to prevent data loss in case of crash or incident. In my 15 years career, I’ve not met even one consultant who was about data archiving. They think it’s a basis scope of work and don’t want to dive into it. But actually archiving is not only about archiving itself, it’s more about data management, performance management, data integration. Who knows if you want to use data archiving technology to transfer data to another SAP or other system.

Let’s setup data archiving for HR change docs. Assume change docs themselves are set already and we can see data changes in S_AHR_61016380 transaction.

Everything could be setup in SARA transaction in 3 steps:

  1. Setup archive paths, logical and physical files
  2. Setup archiving programms variants
  3. Schedule archiving programms

Read More


Assign permission roles through organisation chart

Here we have a position and employee holding it. An employee has 0105 infotype record with system username. Boom, we have everything to set up automatic permission roles assignment to this user based on his position or job in the organizational chart. If that Vasya was hired to a manager role, he’ll get manager role assigned to him the same time we have 0001 infotype created. When he moves to HR Director his manager role is revoked and a new one assigned to HR Director. Once he gets terminated all permissions are revoked immediately. Information Security Officer will adore you. Here is a standard solution to assign permission roles in SAP HR.

Should we do this?

Read More


Watching SAP Query

I think you’ve read SAP courses very carefully with attention. And you know SAP Query logging abilities for sure. I didn’t know that. I’ve read some courses and have found curious things I’d like to share with you.

For example, we can log everything user runs in ad-hoc query or SAP Query. Let’s set it up.
Open SQ02, menu Extras – Set Logs.
sq02 logging

Here we add infosets and info areas (like standard and global). The first column is for the area (space for standard and G for global). Second is for Infoset or asterisk.

Read More