Articles Tagged ‘SAP Payroll’

Basic ALE connection when using separate instances for FI/HCM

Have you ever arrived at a project and been given the news that HCM will be implemented as a standalone system? The FI team is long gone, the HCM team is there and the client wants to use their own IT team to perform Basis and ABAP work. This is not unusual nor is it a problem, until something needs to be done that did not happen when other SAP modules were implemented.  One of those common instances is when FI/CO and HCM will not be in the same system. When the decision has been made to have your FI/CO and HCM components in separate systems you may not have instant access to an experienced IT member that knows how to help an inexperienced IT team make this work.  These basic steps on how to set up an ALE connection between FI/CO and HCM modules will help you work with the IT team to accomplish your objective.  Some common transfers of information examples from HCM to FI/CO are data for General Ledger Postings, Travel & Expense, and 3rd Party Remittance. 

Step 1: Create users for ALE transfer in both the receiving and sending client/systems.

·         Create users giving them the same user name and authorizations. This will allow logon through the remote connection and perform the IDOC transfers.

Step 2: Create logical systems in both the receiving and sending systems.

a.       Log on to Sending client and go to transaction “SALE”

b.      Expand both the Sending and Receiving systems

c.       Expand logical systems and click on Define Logical System

d.      Click on New Entries and use a naming convention identified by your IT/Basis group. Example - “system name + CLNT  + client number.  Save and “go back” (sending = HCMCLNT105/ receiving = FICCLNT800)

e.      Save and go back. Now click on Assign client 105 to logical system HCMCLNT105

f.        Now log onto receiving system and repeat a-c

g.       Save and go back. Now click on Assign client 800 to logical system FICCLNT800

Step 3: Create the RFCs

a.      In your sending client go to transaction code SM59 and expand the R/3 connections

b.      Enter RFC name as HCMCLNT105 (use the same name as the logical name created in step 1 so that the ports are automatically created)

c.       Enter Connection Type as “3” and Language as “EN”

d.      Give the logon details for client 800 (it is best to create a new user with proper authorizations for this ALE data transfer).

e.      Click on Remote long on button to test the RFC

f.        Now go to the receiving client and repeat a-e and give logon credentials to client 105

Step 4: Create customer distribution Model.

·         This is usually created in the sending system and then is distributed to the other system.  The actual creation of the model requests that you mention a technical name for the model (this needs to be a unique identifier in the systems landscape), a sender system, a receiver system, and message types to exchange between those systems.

a.       In the sending client go to transaction code BD64 and client on Change and Create model view button

b.      Enter the short text and technical name as ZHCM_FIC

c.       Select the model and click on Add Message Type button

d.      Give the sender as HCMCLNT105 and receiver as FICCLNT800

e.      Give Message type as required. Example- “HRMD_A” for HR Module. This is usually the message types given by SAP are available for a particular module, see using transaction code WE81, if not create a message type first (See step 7).

f.        Select the above model view and click on Environment >Generate Partner Profiles

g.       Select Transfer IDOC Immediately and Trigger Immediately radio buttons

h.       Click on Execute.  You should get a list in green which means it executed successfully.

i.         Now back on the main screen you should select the model view

j.        Click Edit> Model view> Distribute

k.       Click on Continue. You should get a list saying model view is distributed successfully.

Step 5: Checking the Port

a.       In the sending client go to transaction code WE21

b.      Expand the transactional RFC

c.       Find the port from the list which is created using BD64 for FICCLNT800 (the receiving system) RFC destination

Step 6: Checking the Partner Profiles

a.       In the sending client go to transaction code WE20

b.      Expand Partner Type LS

c.       Select the partner profile FICCLNT800

d.      Double click on the Message Type. Example- In HR Module, HRMD_A in Outbound parameters

e.      Check Receiver Port is assigned correctly

f.        Check the Basic type as your Basic IDOC object.

g.       In the sending system, select the option to transfer IDOCs Immediately

h.      By default in the receiving system IDOCs are bunched together and received.

Step 7: Creating the message type

a.       Message type defines the meaning of data.  It is just a logical entity that gets  connected to the IDOC type, in transaction WE82, or gets connected to the distribution model, in transaction code BD64. If necessary create a new message type.

b.      In the sending client go to transaction code WE81

c.       Click on Change > Continue

d.      Select the New Entries button

e.      Give message type in customer namespace “Z” and description

f.        Save and go back

Tags: ALE, ALE 3rd Party Remittance, ALE General Ledger Posting, ALE HCM to FI, Cross Industry, HCM, HCM Help, how to, Payroll, Payroll Integration, RFC Connections, sap, SAP HCM, SAP HCM Blog, SAP Payroll, SAP Tips and Tricks, Symphony Consulting, Symphony Consulting Blog, Tips and Tricks

Posted in Tips and Tricks | No Comments »

Advanced Vacation Payout

Question

Our Company is three weeks from go-live SAP HCM. We have a union rule that requires us to pay union members in advance for vacation. Many of them take five weeks all at once. We have a weekly payroll. It appears that the way to do this in SAP is to process each vacation request manually through each of the next 5 payrolls (for each employee requesting vacation). This is a huge pain for our payroll department in our legacy environment, and soon to be in SAP. Do you have any suggestions?

 

Answer

Step 1 - In Time Management, enter the Vacation hours for the five weeks, then run Time Evaluation for the five weeks.

Step 2 -  In Payroll, there is an Off-cycle/On-Demand Payroll run option, where it can be run for the next five pay periods for the employee, so their taxes, etc. , will be calculated and taken correctly. (On the actual production payroll for the next 5 pay periods, Payroll will know and exclude the employee from the Regular Production run).

 

An enhancement that may be explored post go-live would involve a custom solution utilizing a combination of forms, workflow, and custom programming to automate the entry part of the process.  The Time Evaluation and Off-cycle steps will already be a part of your new SAP Payroll procedure and not require any further adjustments. 

 

Either way, we recommend you move forward with go-live and only consider a custom solution after go-live and stabilization. Waiting until after you are stabilized will allow you to have a better understanding of your new system and help you to be better prepared when you begin to make adjustments or expand your HCM solution.

 

Tags: ask the experts, Custom Solution, Forms, Go-Live, HCM, HCM Implementation, how to, Implementation, Off-Cycle/On-Demand Payroll, Pay Period, Payroll, Payroll processing, sap, SAP HCM, SAP HCM Blog, sap hcm help, SAP HCM Tips & Tricks, SAP Payroll, symphony, Symphony Consulting, Symphony Consulting Blog, Time Evaluation, Time Management, Workflow

Posted in Ask the Experts | No Comments »

Configuring IT 0008 (Basic Pay) for automatic loading of pay scales

Question

I have hourly employee’s that are on Hourly Pay Scale and salaried employees on pay grade. How do I configure my IT0008 to make this automatic when I am creating a record for a specific employee?

Answer

This is controlled in the feature TARIF where the return value must have the form xx/yy/z, in which xx is the pay scale type, yy the pay scale area, and z the planned remuneration type. The planned remuneration type can be ‘S’ to enable selection of pay grade values from table T710, ‘P’ to enable default values from the Planned Compensation Infotype  of the EE’s position. If a there is no value selected for the planned remuneration type in the feature, the selection will come from table T510 which is the Pay Scale table.

Tags: automatic entry on IT0008, Basic Pay Infotype, Hourly Employees, Hourly Payscale, IT0008, Salaried Employees, Salary pay grade, SAP HCM, SAP Payroll, TARIF

Posted in Ask the Experts | No Comments »

Testing Payroll Process

Question

How to test payroll process model once we created? Hoping to hear reply from you.

Answer

To test payroll process model the following would be the test scripts I would apply. 1. Run a regular payroll run in the dev system with the process model name. When running the process model you will be able to see the process steps running. There is a tab in the process model that allows you to check the files when running. 2. Once finished running through all the steps that you configured to run through then you can spot check results for several employees RT. 3. Then if you run the process model thru fico transfer and direct deposit, check those transfers with the finance people or run those reports for Direct Deposit. On the finance side they will have reports that transfer that information. 4. Then I would run the process model for an Offcycle to make sure that if you have a process model set up for offcyle that it works the same way and it is working well.

Tags: HCM, Payroll, process model, sap, SAP HCM, sap hcm help, SAP Payroll, SAP Payroll Testing, Testing

Posted in Ask the Experts | No Comments »