SAP ABAP IMG Activity HRAS_XI_INTEGRATION (XI Integration)
Hierarchy
☛ EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
   ⤷ PA-AS (Application Component) HR Administrative Services
     ⤷ PAOC_ASR_PROCESS_MODELLING (Package) Modeling Processes
IMG Activity
ID HRAS_XI_INTEGRATION XI Integration  
Transaction Code S_PEN_05000347   (empty) 
Created on 20050609    
Customizing Attributes HRAS_XI_INTEGRATION   XI Integration 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRAS_XI_INTEGRATION    

Use

You use the IMG activities in this section of the Implementation Guide to configure the process start based on XI messages that the e-recruiting system transmits using the SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI).

An XI message or the XI message type that it is based on does not necessarily uniquely identify one specific business process. Depending on what data is transferred, the HireRequest XI message can result in a new hire, a re-hire, or a transfer. In the following sections, the term XI scenario distinguishes between different business processes.

An XI scenario assigns appropriate processes to the respective business processes. When processing an inbound XI message, an administrator selects the appropriate process from these processes.

SAP defines the XI message types and XI scenarios. An example is the New Hire Request from E-Recruiting (NEWHIREREQUEST) XI scenario for the HireRequest XI message type.

Process Flow

When an XI message arrives, the following process runs:

  1. The system receives the XI message and triggers inbound processing.

    The system determines the XI scenario involved and creates a process object, in which the data and attachments received in the XI message are stored. The system then triggers a workflow that contains interactive steps for selecting and starting a process.

  2. An administrator receives a work item with the following information in his or her universal worklist (UWL):
    • A list of possible processes to trigger
    • The attachments received by the XI message and the field values of the XI message, displayed in a generated Adobe form
      • For this view form, you need a form scenario that is used as a reference in the following as a form scenario for the XI message type.

      The administrator selects a process from the list based on this data. The list of possible processes to trigger is assigned to the XI scenario using a process group. If the process group contains only one process, the process selection step is skipped.

  3. Another administrator receives a work item in his or her universal worklist (UWL) for starting the process that the first administrator selected.

    Depending on the configuration of data transfer from the form scenario for the XI message type to the form scenario of the process to be triggered, form fields can be filled with field values from the XI message. The administrator can also have the attachments from the XI message available.

  4. When the work item has been completed, the process workflow starts.
  5. When the process is completed, as a follow-up activity, you can send an additional XI message, for example the HireConfirmation XI message.

Requirements

Standard settings

Activities

To configure the XI integration, proceed as follows:

  1. Set up form scenario for XI message type
  2. Set up process start for XI message type
  3. Specify data transfer from form scenario for XI message type to target process
  4. Activate follow-up activities after process using XI message

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG HRAS_XI_INTEGRATION 0 AEN0000011 HR Administrative Services 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20050610 
SAP Release Created in 600