Skip to Content
avatar image
Former Member

PI Collecting - job postings

Hi all - our requirement is that we need to replicate out job postings (SAP E-Recruit) to an external job site. The external job site needs to receive ALL relevant postings in one message (i.e. for each message they receive from us, they wipe out their existing postings list and add whatever we give them), so all postings have to be in any message we give them.

SAP's E-Recruit standard solution (standard service) to replicate out job postings is 'one at a time". Our functional folks are verifying this. Additionally, the postings are sent out using a periodic service (e.g. every 3 minutes).

So, it seems to me like we need to collect the E-Recruit messages into PI, and then (when complete), consolidate and send as one to the external site.  Example: 5 relevant postings, so 5 messages get sent to PI, and then PI sends 1 message with the 5 postings, to the external site.

The issue for me is that it seems I only have an option of using a 'time' dependency (collectwithtime pattern?) in PI. E-Recruit appears to not send any type of flag, etc. to indicate the final message, thus it appears the only option is to have an PI integration process that receives the messages in, and if nothing received for say 15 seconds, the process bundles them up and sends them to external.

This is a proxy->PI->http (or maybe ftp) scenario.  I am using PI 7.3.

I would be interested to hear from anyone who has worked with this type of scenario to find out if (a) there is some other way to accomplish, (b) if any issues regarding timing (e.g. is there ever a case where the periodic service does not get all postings given the timing of when it runs).

Any thoughts appreciated.

Regards,

Keith

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 27, 2012 at 08:11 AM

    Hi Keith,

    Please have a look to:

    Collecting and Bundling Messages - One Interface

    You can define several conditions to stop collecting and send a message, a time interval or/and the number of messages and/or after receiving a certain "final" message. The next messages will be processed by the next process instance. ccBPM is of course only possible if your system has an ABAP stack, otherwise you would need to use "new" BPM.

    Regards,

    Udo

    Add comment
    10|10000 characters needed characters exceeded