Outbound outsourcing interfaces in mySAP HR

Outbound outsourcing interfaces in mySAP HR

Are there any examples of outbound interfaces for Payroll in the HR Module of SAP? What would be the steps to create a report that outputs the payroll details in the HR module to an outfile? Please advise. Thanks.

    Requires Free Membership to View

    Login

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The standard outbound outsourcing interfaces exist in SAP. It requires minor ALE setup to output the file. The menu path for these programs, assuming you are in the US, is Human Resources->Payroll->America->USA->Outsourcing->Export. The ALE setup simply requires a partner profile and a port for the IDoc type you are trying to get out of the system.

If those don't fit your needs, here's a simple program to read the payroll clusters for an EE. Please note that this can be done in a number of different ways and this is probably the least advanced way but also the easiest to explain.

report zppyro016 no standard page heading line-size 80.
include zpayrolldata.
data: yearper(6).
parameters: p_wt like pa0008-lga01.
start-of-selection.
get pernr.
cd-key-pernr = pernr-pernr.
rp-imp-c2-cu.
concatenate pn-paper-pabrj pn-paper-pabrp into yearper.
read table rgdir with key fpper = yearper
srtza = 'A'.
if sy-subrc <> 0.
message i899(s1) with 'No stored results for' pernr-pernr.
sy-subrc = 8.
endif.
check sy-subrc <> 8.
loop at rgdir.
rx-key-pernr = pernr-pernr.
rx-key-seqno = rgdir-seqnr.
rp-imp-c2-ru.
loop at rt.
if rt-lgart = p_wt.
write: / pernr-pernr, rt-lgart, rt-betrg.
endif.
endloop.
endloop.
commit work.

The include looks like this:
*----------------------------------------------------------------------*
* INCLUDE ZPAYROLLDATA *
*----------------------------------------------------------------------*
tables: pcl1, pcl2, pernr.

include rpc2cd09. "Cluster CD Data-Definition
include rpc2ca00. "Cluster CA Data-Definition "XUJP30K079863
include rpc2ruu0. "Cluster RU Data-Definition
include rpc2rx09. "Cluster RU Data-Definition internat. part
include rpppxd00. "Data befinition buffer PCL1/PCL2
include rpppxd10. "Common part buffer PCL1/PCL2
include: rpppxm00.

Make sure you define PNP as your logical database in the attributes. The tables returned by rp-imp-c2-ru are the same as those in transaction PC_PAYRESULT.

This was first published in August 2004