2444508 - ONB-EC Integrations Concepts Simplified - Onboarding 1.0

ONB 1.0-EC Integrations Concepts.

SAP SuccessFactors Onboarding 1.0

1.With Respect To National Information Portlet:
 
 We can use any data type in Onboarding 1.0 (picklist, lookup, string) ,it should be multipanel and only pre-requisite is based on regular expression defined in a country specific Data model xml should be same as of validation for National ID in panels in Onboarding 1.0 side.

2.With Respect To Personal Information Portlet:

 A)Field Name:Gender. Gender is foundation object in EC side.

Case 1:In panel Gender is  dropdown, lookup in  data dictionary and foundation object in EC Side(no picklist id in data model xml for gender field):(Advisable Scenario for configuration).
  
        In this scenario RCM2KMS Lookup Mapping will come into picture and data will flow between ONB 1.0-EC without any issues.

Case 2:In panel Gender is picklist, picklist in data dictionary and Picklist in EC side(picklist id defined in data model xml for gender field):
    
        In this scenario, Mapping will not work and gender will not flow between ONB 1.0-EC.

Case 3:In panel Gender is dropdown, picklist in datadictionary and foundation object in EC side(no picklist id in data model xml for gender field):

        In this scenario, code mentioned in data list should match with external code for gender field in Picklist file, so that data will flow between ONB 1.0-EC without any issues.
  
        In this scenario, code mentioned in data list is maintained and external code for gender field in Picklist file is Empty, so that also data will flow between ONB 1.0-EC without any issues.(This Case Applicable Only to Gender Field).

OverAll Concept:

1.Panel(picklist)+DataDictionary(picklist)+Picklist in EC(picklist file)=Smooth Data Flow will Happen between ONB 1.0-EC.
2.Panel(dropdown list)+DataDictionary(picklist)+Picklist in EC(picklist file)=Ito make Data Flow, Code in Data List should match with External Code in Picklist File.
3.Panel(dropdown list)+DataDictionary(Lookup)+Picklist in EC(picklist file)= to make Data Flow, RCM2KMS LookupMapping should be in place.

3.With Respect To Dependent and Emergency Portlet:

  It should be multipanel, start index should not be 0, field in data dictionary should be repeatable in ONB 1.0 side and respective picklist id should defined properly in EC side.
 
4.With Respect To Home Address Portlet:

  A)Field name:State

Case 1:For United states, state will flow without any issues because since it is used in federal panels and EC has been pre-configured so that data will flow without any issues.

Case 2:In case you want to achieve it for International Process(state flow btw RCM-ONB 1.0 -EC), there are 2 possibilities.

       Example:If Suppose i want to flow states of India between RCM-ONB 1.0 -EC, it can be possible in 2 below ways:

1.RCM(state picklist)+Onboarding 1.0 (data dictionary--State field is Lookup)+State_IND is picklist in EC=In RCM2KMSLookupMapping file, you should maintain state picklist mapping field (since maintained in RCM) as well as State_IND picklist mapping field(since maintained in EC).

2.RCM(state picklist)+Onboarding 1.0 (data dictionary--State field is Lookup)+State_IND is picklist in EC=In RCM2KMSLookupMapping file, you can maintain only state picklist mapping field(but pre-requisite is Label for  State in picklist file should match with Label for State_IND in picklist file)

Above(2)option is most approachable method can be suggested to partner since it is Time consuming if you are using International Process.

EC, personal information, emergency information, dependent information, Home Address, gender, state   , KBA , LOD-SF-OBD-INT , Integrations with Onboarding , How To