Skip to Content
Former Member
Jan 18, 2006 at 08:01 AM

Setting up the HR-PDC interface to ext. system without direct RFC



Setting up the HR-PDC interface to external system without direct RFC - Uploading time events

Following note number 647145, I tried to set up connection to external time collection system. As the external system isn't able to work with RFC, I setup a fileport using transaction WE21. When an outbound IDOC is created with transaction PT80, it will be stored at the outbound path. The IDOC then will be transfered to the external system with a unix script triggered by event.

For inbound IDOCS, the fileport cannot be used as I don't see any way to configure it as the time events that should come in via RFC port, will be uploaded and processed according the ALE distribution model. The BOR object "PTManagerExtPEvent" of type "BUS7014" with method "Insert" is used to insert the time events into the interface table CC1TEV from an HR-PDC certified subsystem. The message type is "HRCC1UPTEVEN".

As standard process won't work in our case, I'd need alternative solution. Actually the time events are send via ftp to the SAP directory that points to incoming IDOC path setup on WE21.

Maybe there should some way to setup RFC connection to own SAP system that points to the SAP directory where the inbound files are stored.

Maybe using the FM IDOC_INPUT_HRCC1UPTEVEN can be used to trigger the upload manually but first the files have to be uploaded from file similiar to report RSEINB00. Testing this report using the SAP directory and port where the inbound files are located I get error message that IDOC control record is missing, that seems to be understandable as this report is used to upload IDOCS from file but HR-PDC upload file HRCC1UPTEVEN01 has no specific IDOC segments in this moment as it was created according specific HR-PDC interface description. The IDOC in the standard process will be created with the BAPI.

As I'm new in HR and ALE, I'd be grateful for any help on this matter.

Best regards