SAP HR: ALE

Introduction

The following is a short summary of the key areas within SAP for getting ALE to work when linking HR to FI and vice versa. This document is based on the config required in the HR system. In certain instances the identical reciprocal config needs to take place in the linked FI system.

Configuration

The transaction code SALE takes you to the IMG for ALE.

The first step is to set up the logical systems. Specify the Logical System name - short and long.

The next step is to set up the RFC connections which are required in ALE.

When you get to the detail for the RFC connection, check that the RFC user has wide enough authorisations.

The next step is to determine the RFC Destinations for Method Calls

This can also be called by transaction code BD97. Make sure that the entries are all there.

The simplest way of doing things is to replicate the important FI data on the HR system. In addition, consider all of the FI data and objects that are required to be created on the HR system. This will include amongst others: company codes, chart of accounts, fiscal year variants, controlling areas etc. The data should be transferred exactly as it was on the FI system.

The next step is the creation of Cross-System Company Codes

In SALE you will see the menu path:

Modelling and Implementing Business Processes arrow Cross-Application Settings arrow Global Organizational Units arrow Cross-System Company Codes

The next step is to "Assign Cross-System Company Code to Chart of Accounts"

Then you need to "Assign Company Code to Cross-System Company Code"

You then have to set up the "Distribution Models"

You can get to this by using transaction code BD64. You need to make sure that the partner profiles exist. You can create them using the menu path: Environment arrow Generate Partner Profiles. You just need to make sure you get the "from" and "to" systems the right way around.

You may need to add or delete certain entries. If you add or delete the entries, you have to distribute the model views to the partner system. You can do this by using the menu path:

Edit arrow Model View arrow Distribute

Choose the relevant client (should be the FI one if you are currently logged in to the HR system).

Once having set up the partner profiles you can modify them by using a similar menu path: Environment arrow Change Partner Profiles. The important part is the outbound parameters from the HR system.

The opposite will be true in the FI system.

The next step is the "Sending Documents from FI"

Once the documents have been sent from FI, you can monitor them using transaction code BD87. Choose a message type if you wish to filter out the relevant values.

You can dig into the error messages here and you can re-process the documents either as a bunch or individually.

The next step is the "Posting from HR"

Post in the usual manner. The difference is that the final screen should tell you that the documents have been posted to the ALE layer. The resultant screen is shown after the FI documents have been posted. You should see a mention of the ALE layer etc.

Additional Notes

The transaction code to send Idocs is BD16.

No comments:

Post a Comment