Knowledge Session - Connectors 2016 - 01 - 20

Knowledge Session: Connectors
Angel Garcia– EMEA NEXUS LMS

January 20th, 2016
Purpose of This Presentation
This presentation is for the training of Customer Support

Engineers in Connectors.
These are tips on how to use time management to your advantage. This is from experience of working high volume tickets. Everyone has a different style of
working for me the key was being efficient and letting the outside noise not bother me. There were times where you have to force yourself not to answer
emails
Created Date Delivered Date
Alex Downs 16/02/2015
Angel Garcia 20/01/2016

Pino
© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 2

Agenda
1. What are the Connectors in the LMS and for what we use it for?
2. Different connectors types inside LMS
2.1 Olsa Connector vs Skillsoft Connector
3. Connector Workbooks: Standard Connector, Olsa Connector, Skillsoft Connector and Competency Connector
4. Connectors Configuration LMS
5. SF User Connector – Bizx Integration
5.1 Provisioning
5.2 LMS Configuration
5.3 Adding Custom Columns to Extended Data
6. Connectors: Misc. Settings

7. Connectors Mapping : Mapping / Custom Columns / Transformation Rules
8. PGP Configuration

Agenda
9. Known Issues
10. Known Issues: KBA created for connectors LMS
11. Database relations to Connectors
12. Connector Error Codes
13. A Reminder about Connectors : new features b1411

Description
Connectors are used to import data into the LMS.
Each connector has it’s own specific data structure, so each input data file must
match a predefined format.
There are different types of connectors offered.
Requires license – All are Free except OLSA Connector that it was substitute by
the standard Skillsoft connector in b1508.
Compentency Connector SF has his own connector workbook and it is not found
in the standard connector workbook.

Connector Processing Extract Program
Source
Extracts
Data
Connector SFTP Site

Input File
Each Connector Gets Input File

Launches Per
Schedule
Input Folder
Load Input Into

SF LMS DB Stores
Staging Table
Input
File Archived Input Files
Process Input
Records SF LMS DB
Summary
Email Report
SF LMS DB
Adds or Updates to LMS

Processing Methods for Input Fields

The connectors support to modes of processing the input file:
Position Method: This method requires that all of the fields in the input file are in a specific order. This
method is deprecated. Do not use this method it is deprecated.
Header Method: This method uses the header row to determine the positions of the input data. This is
the only supported method.
Record Rejections
The standard connector and imports will reject a record (not the entire input file) if any of the following
conditions occur:
The input file contains a null value for a field that cannot be null. Check the ‘Req’ column in the data
mapping tables which indicates whether a value for a field is required.
The input file contains a value that does not comply with the data type for that input file column.
The field input value is a reference but the value does not match the reference table.
Null Values
Null values in the input file are accepted by a standard connector unless the field is a required field.
The connectors do not update fields when the input file passes a null value.
Input File Format

The input file produced by customers must have the following characteristics in order to be processed
correctly by the SuccessFactors Connector:
Character Set: SuccessFactors supports only the UTF-8 Character Set in the input file.
Column delimiter character: Will always be a pipe (“|”) character.
Row delimiter character: !##!
Column Headers: Must be included as the first row of the input file.

Input File Format (cont.)

Order of columns: The connector will be set to “header” method for processing the input file. This
means that the order of the headers can vary since the connector reads this header row and uses it to
map data to the connector fields.
Null values (empty fields): All columns indicated in the header row must be supplied in the input file
data. You can indicate null values by using two consecutive pipes.

Connector Description
User - SF Loads and updates users in an integrated environment from the BizX suite. This
connector is used solely for integrated environments.
User Loads new users and updates existing records. Capable of creating references,
such as domains.
Federal Contains all values as the standard user connector, but adds additional fields
User required for Federal agencies.
Domain Loads new domains, updates existing records, and manages the hierarchical
relationship of domains
Item Creates new items in SuccessFactors Learning and updates existing records. It
is most common for the item connector to be used for one-time data migrations,
rather than an ongoing feed.

Learning Records item-based completions for existing users’ completion of existing item
History records. Both the user and the item record must exist within the system for the
record to be accepted. The learning history connector is most commonly used for
one-time data migrations.
Scheduled Schedules instances of existing item records and is typically used for one-time data
Offering migrations.
Registration Updates user registrations in existing scheduled offerings. Both the user and
scheduled offering must already exist in the system. This connector is typically used
for one-time data migrations.
Job Code Formerly known as job position, the job code connector creates new and updates
existing job code values, such as domain, if curricula should be automatically
assigned, and more
Position Similar to the job code connector in that positions are typically instances of job
codes. For example, job code 199 may represent an administrative assistant,
while the position, Phoenix – 199, may represent an administrative assistant in
the Phoenix office. The connector creates new records and updates existing.
User Manages compensation values in the system, such as compensation manager,
Compensation salary, etc. It is recommended that the user connector be run in advance of the
Connector user compensation connector so that the user connector maintains sole
responsibility for creating new users. Has his own connector workbook.
Curriculum Similar to Item Connector, this connector adds new curricula and updates to
existing curricula.

Competency Creates competencies and associated rating scales in in the LMS. Records
SF are created in the BizX environment and loaded to the LMS using the
connector. See section 3 for connector workbook.
Skillsoft We added a Skillsoft connector in Q3 2015 to replace existing OLSA

Connector extensions. By migrating to the Skillsoft connector you gain the support of
(B1511) the product itself, including enhancements and bug fixes. By following the
migration path, you can eventually turn off the OLSA extension and begin to
use the Skillsoft connector. See section 3 for connector workbook.
These are the standard Connectors, then the customers could have their own custom connectors
made by Professional Services and there is also the OLSA Connectors

2.1 OLSA Connector vs Skillsoft Connector
Olsa Connector was a Custom Connector that it was set up and deploy by Professional Services
and if they were an issue on this Connector must of the times Customer had to go to
Professional Services for a fix or revision.
From b1508 a standard skillsoft connector was created, where we troubleshot and give
customer support care without reaching Professional Services.
Olsa Connector customers that deploy this Custom connectors have two custom connectors:
• Olsa Item Connector

• Olsa Subject Area Connector
See Section 3 to download the Olsa Connector Workbook

2.1 OLSA Connector vs Skillsoft Connector
The Skillsoft connector brings your Skillsoft courses into the Learning Management System
(LMS) as learning items.
If you use Skillsoft knowledge center, you can bring the courses into the LMS to track them as
Learning Items. You pull in the data through the Skillsoft Connector.
The Skillsoft connector:

• Creates learning items based on your Skillsoft courses.
• Creates a subject area hierarchy based on your Skillsoft categories.
• For United States Federal customers, you can create an eHRI learning item that includes
Custom Columns in the 1100 range to describe the required eHRI values.

3. Connector Workbook
What are they?

Connector Workbooks provide all the necessary details needed to properly configure the input data
file. If an exception is being reported in the detailed summary report after the connector has ran, the
best option is to reference the Workbook to see what values are allowed.
Where can I find them?

Connector Workbooks can be found on the JAM CS LMS group.
Please find bellow the last standard connector b1511, the Olsa connector b1210, Standard
Competency Connector Workbook b1210 and the new Skillsoft migration connector workbook.

Once you’re in the LMS Admin site, navigate to System Admin>Configuration>System Configuration>Connectors


LMS Tenant ID. Found on SharePoint. This means that the

connector will be expecting user_data_support02.txt as input
file name.

High Level Overview of Connector Process
BizX Employee LMS Connector

Customer HRIS BizX Employee Data Export to picks up file and
system Data Import FTP processes it
(Provisioning)

LMS
Schedule Quartz Job Archives
Schedule LMS picks LMS
Data Export kicks off and input file;
Connector in up file from Processes
Job in places file detailed
LMS FTP File
Provisioning on FTP report made
available*
Notes:
1 - File will be remove from FTP drive once LMS picks it up.
2 - *Must be configured in connector properties in LMS System Configuration

5.1. SF User Connector – Bizx Integration : Provisioning
In Provisioning:
Search for customer by selecting the first letter of their name:
Use browser’s Find function to find customer name.
Click on customer name

Scheduled Jobs run processes for Connector input file:

Click on Manage Scheduled Jobs:
Click on “LMS User Export” or similar named scheduled job

Job Name: This could be anything. Generally
‘LMS User Export’
Job Owner: This is an admin that has the
permissions to manage scheduled jobs
Job Type: Has to be ‘Employees Export’
Job Parameters:
- ‘Valid Users Only’: Checking this will only export

Active Users. (NEVER DO!) INCORRECT!
-’Short Format’: Checking this will only export the

BizX “required fields”.
- ‘Character Encoding’: This should ALWAYS be

UTF-8.

Host Address: Generally
prodftp.successfactors.com:21
FTP Login: Provided by Operations, this the login
ID for the FTP server.
FTP Password: Provided by Operations, click on
“Show Password” to view actual password.
FTP Passive Mode: Generally checked, but
should confirm with DCOPS before selecting.
SFTP Protocol: Check with DCOPS before
selecting
Test Connection: Click this should return: “The This information MUST be used for the SF
ftp connection test is successful.” If it is not User Connector Properties in the LMS
successful, credentials may be incorrect. File
DCOPS JIRA to get correct credentials.
Test File Put Permission – This will place a test
file in the FTP server

File Path: Generally /outgoing
File Name: The file name will be
user_data_xxx.txt, where xxx is decided by
DCOPS (generally the Tenant ID)
Date Format: You can select whether or not the
file should have a timestamp appended to the file
name.
File Encryption: This option will encrypt the input
file. The Connector properties must be configured.

Editing Scheduled Jobs

In order to edit a job, you must first cancel it
• You will then be allowed to edit the
from the Manage Scheduled Jobs page.
Scheduled Job

Editing Scheduled Jobs

Note: When you make the changes, you'll have to change the start date of the job to be
today (if it hasn't run yet) or tomorrow (if the job already ran this morning), otherwise you’ll
get a prompt telling you do so.

5.2 SF User Connector – Bizx Integration : LMS configuration
For SF User Connector, LMS will only process files based on Headers.
Column delimiter character: Will always be a comma ( , ) character.
Row delimiter character: End of line
Null values (empty fields): Indicate null values (empty fields) by using two consecutive commas. Do
not use blank space to indicate null values; as they will be interpreted by the connector as a non-null
data input.
• Correct indication of a null column: ,,
• Incorrect indication of a null column: , ,

5.3 SF User Connector – Bizx Integration : Adding Custom Columns to extended data
6 Simple Steps to Add Custom Columns from BizX to LMS
1. BizX - Update the Customer Data Model with the Custom Fields
2. BizX - Add Extended User Information
3. LMS - Update the Connector Property file with the Custom File Mappings
4. LMS - Add the Custom User Columns to the LMS
5. LMS - Export the Extended User Information
6. LMS - Import the Extended User Data

Step 1: Update the Customer Data Model with the Custom Fields
Login to Provisioning and Export the Data Model:

Step 1: Update the Customer Data Model with the Custom Fields
Update the Data Model with the Custom Fields:
Note: If you want the extra column to be available within the BizX UI, it will need to be added to the form and
permissions. This was not tested as part of this solution.

Step 2: Add Extended User Information
You can see the added column by downloading the Extended Import Template from BizX Admin Tools
> Import Employee Data > Download > Extended Import.
Add the user data in the custom field of the new field.

Step 3: Update the Connector Property file with the Custom Field Mapping(s)
Add the following to the CONNECTORS property file:
sfuser.extendeduser.field.customcolumn.160=ADDL_TEST
*The Custom Column from BizX must be entered in uppercase, even though the BizX ID may not be.

Step 4: Add the Custom User Column(s) to the LMS
System Admin > Custom Columns > User
The column number must match the value in the property file

Step 5: LMS - Export the Extended User Information
In Provisioning, add a Managed Scheduled Job to export the Live Profile Data from BizX.
This is scheduled to run after the BizX User Export. Both files are sent to the same location on the
SFTP server. The User Connector-SF will process both files when it runs.

Step 6: Import the Extended User Data
System Admin > Connectors > User Connector – SF
After the process runs, the data in the custom column displays in the user record:

6. Connectors: Misc. Settings
(System Admin>Configuration>Connector Settings)
To enable archiving of input files, check “Enable Input File

Archive” check box. After connector runs, the file will be
encrypted and stored in database for up to six months
(depending on setting)
To view archive connector file, go to respective connector and

click “Show archived input files”

7. Connectors: Mapping
All mapping follows this format:

<Connector Prefix>.<Entity Type Prefix (if any)>.field.mapping.data.<LMS DB column>=<name specified in header of input file>

Mapping Columns (Continued)
This shows the Curriculum connector and the default values.
This shows column mapping, including custom columns..
When a connector has different input files that it can process, it

refers to them as “entity type prefix”. In this example, the
connector is the Curriculum connector and the “entity type prefix”
are curriculumitem and curriculumparent

Example of column mapping:

7. Connectors: Mapping – Custom Columns
Each connector contains 15 Standard custom columns. They follow the same mapping structure:
<Connector Prefix>.field.mapping.data.<LMS DB column>=<customer’s DB value; specified in first row of headers in input file>
sfuser.field.mapping.data.COL_NUM6_VAL=<customer’s DB value>, which would be in the first row of headers in the input file.
To add additional custom columns, you can use this mapping format:
<connector prefix>.field.customcolumn.<field>=<column_number>
where field is the header value that will appear in the input file and column_number is the user custom column where the value
will be stored.
A secondary file called “Extended User File” can be ran to specify custom columns to feed.
There are advanced configurations that are not covered in this guide (ie., Transform rules that allow the data that the customer
submits to be transformed to something that the LMS will accept/understand), this is covered on this document:

7. Connectors: Mapping – Transformation Rules
There are advanced configurations that are not covered in this guide (ie., Transform rules that allow
the data that the customer submits to be transformed to something that the LMS will
accept/understand), this is covered on this document. However, below is an example.
The LMS Connector has what we call “transformation properties” that essentially help address
mismatches. Locale is one example. The out-of-the-box configuration, transforms incoming “en” and
“en_US” (from BizX – Input file) values to English (corresponding locale value in the LMS):
sfuser.field.transform.data.LOCALE.English=en,en_US
Similarly, if you want to transform a BizX “EST” timezone value to “America/New_York” (corresponding
LMS value), you would specify a setting such as:
sfuser.field.transform.data.TIMEZONE.America/New_York=EST
You can get the advanced connector configuration by double clicking this icon:

Encrypting connector input files in SuccessFactors LMS
The LMS connectors have the ability to process PGP encrypted input files. PGP stands for Pretty
Good Privacy which is a widely used encryption program to encrypt and decrypt files. PGP uses a
variation of the public key (PK) system where each user has a publicly known encryption key and a
private key known only to that user. The message is encrypted using the Public key shared between
the two users and the receiver uses the private key (known only to the user) to decrypt the message.
The PS Technical Services team is responsible for generating the (Public, Private) key pair and the
secret pass phrase. Once the keys are generated, the Public key is shared with the customer to
encrypt the connector files. The customer may choose to use a program/utility of their choice to
encrypt the file(s) using the key provided.
Once the input files are encrypted and ready for connector processing, the Successfactors PS
personnel will need to update the following properties in the LMS Connector configuration.

CONNECTOR CONFIGURATION
# PGP setup for decryption of input files
connector.pgp.enabled=
connector.pgp.public.keyring=
connector.pgp.secret.keyring=
connector.pgp.passphrase=
connector.pgp.file.extension=.pgp
Once the configuration is updated, the customer can proceed with uploading the files to the configured
FTP location and run the connectors.
To Note: - The connector.pgp.secret.keyring and connector.pgp.passphrase values are encrypted by

LMS when the configuration gets saved, hence the values displayed after the update will not match
with the original.
For more information on PGP, please visit the following resource.

http://gso.plateausystems.com/wikipedia/mediawiki/index.php/PGPEncryption (SF Internal)
http://www.gnupg.org/documentation/faqs.html (Official)
9. Known Issues
(System Admin>Connectors)
In this example, we see that the issue is pointing to the file ending “unexpectedly” and it gives you a line
number. If we look at the archive file, we see that the input file has long gaps of blank line spaces, starting at
line 11930. This caused the connector to fail. In this case, a DCOPS JIRA is in order since the Quartz job
failed to produce a correct input file.

9. Known Issues

9. Known Issues
Input file not found / Warn – No Records
We generally see this when:

• Input file has the incorrect name.
• Possible that Staging environment refresh was done and it has same configuration
settings as production environment; and it is grabbing the file before production
environment (two jobs competing for same input file)
• Incorrect format type (position vs headers)

9. Known Issues
Error/Issue Possible Cause
“No Headers” error / File is 0 bytes 2 Provisioning Data Export jobs running at the same time
Inactivating users on BizX does not “Valid Users Only” is checked on Provisioning Scheduled Job
inactivate them on LMS
FTP connection failed Incorrect FTP credentials/Ops Issue
Accented Characters not showing up If Provisioning Quartz job has UTF-8 character encoding, this may be a
correctly on LMS UI Defect.
“File has no content” error PGP Encryption may be misconfigured. LMS processes file but cannot
understand it due to encryption.
Locale on input file is being rejected Locale may not be an actual BizX locale. Go to Provisioning>Company
Settings; confirm locale on input is listed AND checked.
Something to keep in mind: The BizX data validation is different than the LMS. It’s possible that the when importing
data to BizX, some records are not rejected because they are not required, so when these records are imported to
LMS, it will reject if not according to Workbook specifications.

9. Known Issues
Issues Workaround
Connector – Customer wants one Bizx field be mapped in two LMS fields
Connector – Scheduled Offering gets java error ORA-01403 no data found
Connector ticket not showing Apply button

10. Known Issues : KBA Created for connectors LMS
KBA Title – Description

2148513 How to update user custom columns outside of those 15 default custom columns in LMS via Standard User Connectors?
2151758 LMS - How to Batch Update User Role
2153421 LMS: Proper settings for connector configuration
2160607 Exception: "Hire Date cannot be in the future" running User Connector or User Connector SF in SuccessFactors Learning
2161914 What is the updateOnNull syntax for custom columns
2148552 Item connector creates new items when the revision date is not provided for an update of an existing item
2162641 LMS - Curricula Descriptions Not Pulling from Curriculum Connector
2163549 ERROR: "Same source field is configured for multiple fields. Please use copy field mapping for this purpose"
2165339 How to change the e-mail address that receives the Report Notifications for Connectors - Learning Management System
2166405 Message Inactive revisions are not supported when trying to Inactivate Item via Connector - Learning Management
System
2173658 How to map BizX Locale to LMS Locale via User SF Connector-LMS
2074858 How to archive connector’s input files - Learning


2074755 Enabling PGP Encryption for connector files - Learning
2074699 Ensuring proper settings for a connector - Learning
2074298 Changing the file location of a connector - Learning
2074129 Do inactive curricula stay linked to the items on the curricula items tab?
2172463 LMS - Connectors - Java Error in item connector – Unexpected Error.null
2169772 Importing learning history for external events
2169281 How to Associate More Than Three Alternate Supervisors to a User - SF LMS
2169282 User Connector Run Result Exception - Code 1102 - Entity Does Not Exist - CountryID - SF LMS
2168610 How to get the exact time stamp of Item Revision detailed into seconds so you can update the current revision of item
using Item Connector?
2167649 Staging Instance Not Connecting To FTP - SF LMS
2167463 Subject Area for Skillsoft courses showing subject area ID instead of description for certain user locales
2220447 Whether we can use Orgs Connectors to update Organization custom columns rather than the five listed in Connector
Workbooks-LMS
10. Known Issues : KBA Created for connector LMS

2211272 User Connector Failed with error message "There is no current step for Process Instance"
2075199 Position based processing mode VS. Header based processing mode - Learning
2075355 Error - Connector upload is failing due to String or binary data would be truncated error - LMS
2211735 Register multiple users in multiple schedule offerings
2093405 What's CONTENT_WRAPPER_TYPE field for Item Connector? - LMS
2093457 Connector Filed Copy Function - LMS
2093552 LMS - Connector SF – There is not showing “Apply button” - Learning
2241186 ORA-12003: materialized view
2101247 Connector Configuration - Learning
2101266 when a user is turned inactive through connectors , it removes all the items associated with it - Learning
2101872 Removing Alternate Supervisor on the LMS side through Connector - Learning
2101875 Unexpected Error:ElmsCreateException in updateUserPreferences() - Learning


2178650 Learning History Producer failed
2105076 Connector configuration, common and individual settings -Learning
2188805 Connector tab and Connector Administration workflow missing in the LMS Instance
2187228 Connector failed due to error : Cannot get Connection from Datasource: java.sql.SQLException: Listener refused the
connection with the following error: ORA-12528
2185929 HRBP role error in the LMS-Headers are showing changes done in the configuration in user_manager_data-Learning
Management System Connector
2186004 connector exception: Connector admin does not exist in bizx in user connector sf-Learning Management System
2185991 How to use Legacy ID in registration connector
2185911 Nullifying a supervisor
2185416 How to configure user connector sf to ignore certain values coming in the feed file so that the connector so not reject the
record with exception - "entity does not exist'-user connector sf"
2185277 LMS: Troubleshooting tips for competency connector in LMS
2185331 How to correct “Invalid date format” exception coming in for termination date field coming in User Connector SF-
LMS(transformation rule for TERM_DTE)


2185222 Transformation rule to map the values ROLE_ID field which are coming from another system to LMS specific values and
to avoid connector exception "Entity Does Not Exist ROLE_ID"-LMS
2249298 Item connector error :java.sql.SQLException: ORA01403:no data found ORA06512:at "<Tenant
id>_STAGE_TMS.PT_BIU_CPNT_USER", line 7- LMS
2250834 Timezone and Currency field not getting updated in LMS via the SF user connector
2250769 How to question - Learning history data upload with connector with delete mode
2251414 User connector sf failed with the following error : java.lang.UnsupportedOperationException: ElmsEncryption does not
support CipherOutputStreamProvider, please upgrade to com.plateausystems.elms.util.helper.ElmsJceEncryption
2247963 How to map Bizx custom column in LMS?
2208130 How to check the box for "Use AICC Wrapper" when the item connector file processes
2202835 LMS connector template Download
2200538 New Item connector revision setting b1505 turns old items inactive
2199203 Where can I find the latest LMS Connector Workbook ?
2197843 Connector gives Error while importing data.ORA-01400: cannot insert NULL into


2251451 Order ticket are not getting generated for the users while we are registering then using the registration connector-
Learning Management System
2256295 Error: Could not create record! when using item connector
2256304 Adding multiple input files to the connector
2256245 Multiple input files not working with pgp encryption
2257632 Connector Error: com.plateausystems.connector.api.ConnectorException: Error while reading content of file

:user_data.txt. nameMapper array contains duplicate key "JOB_TITLE" cannot map the list
2257597 Creating External users using connectors
2258754 SF User Connector input file missing from sftp folder after LMS clone

Connectors are jobs that run in the connector node, so the information related to the jobs can be found
in the following tables:
PA_SCHEDULED_JOB to check if it is scheduled or not and when it is supposed to run, by JOB_ID

PA_SCHEDULED_JOB_RESULT: you can see connector job results, by JOB_ID
PA_SCHEDULED_JOB_LOCK_HOLDER table needs to be checked in case the global lock was

enabled and is preventing connector jobs (and other jobs) from running. It has to be reported to
Operations.
(If AP Synch is running, connectors won't be able to run. Both connectors and AP Sync may require to
update the very same tables and we don't want both of them updating records at the same time.)
PS_CONFIGURATION contains also connector configurations saved in the Admin>System
Admin>Configuration>System Configuration>CONNECTORS. You will only see the changes from the
original one, not the full configuration (the same as shown using 'view changes')

Connectors place the information in the tables related to the specific connector. For more detail, check
the connector's workbook, as it shows where in the database (field & table) will be
saved/modified each field of the input file, as well as how it will be updated
Other database tables specific for connectors, use the naming convection PA_CONN_...
PA_CONN_ACTIVITY lists the connectors and the last run and it is doing the counting of the entities
that need to be inserted, updated and removed. This is the info showed in the connector report>
activity summary
PA_CONN_ALT_JOB_POS, related to the alternate job code connector
PA_CONN_CBT_CPNT_MOD, related to the online components of the item connector
PA_CONN_CONFIG has the UPDATE_ON_NULL and NO_UPDATE_ON_NULL configurations, as
well as the fields applied to them.

PA_CONN_CONTENT_MOD, related to item connector, content object

PA_CONN_CPNT, related to item connector
PA_CONN_CPNT_CPTY, related to item associated to competency
PA_CONN_CPNT_EVTHST, related to the history of the user
PA_CONN_CPNT_LOCALE_LABEL, item info saved in different locales
PA_CONN_CPNT_SKILL, skills added to the item
PA_CONN_CPNT_USER, contact information associated to an item
PA_CONN_CPTY, competency connector
PA_CONN_CPTY_LOCALE, competency connector
PA_CONN_CPTY_RATING_CRITERIA, competency connector
PA_CONN_CPTY_RATING_LOCALE, competency connector
PA_CONN_DOMAIN, domain connector
PA_CONN_ENROLL, related to Registration connector

PA_CONN_EXCEPTIONS: For each connector (INTERFACE_ID) shows the exceptions and type
found after the execution
PA_CONN_INPUT_DATA: shows the info of the archived connector input file
PA_CONN_JOB_POS, job code connector- info processed
PA_CONN_LOG: It shows a log of the connector executions
PA_CONN_ORG, organization connector
PA_CONN_ORG_DSHBRD, configuring dashboards for organizations
PA_CONN_ORG_INITIATIVES, Organization connector(organizations can have initiatives set by the
org owner)
PA_CONN_ORG_OWNER, Organization connector
PA_CONN_ORG_SUCES_PLNING, Organization connector, to set up the succession planning
PA_CONN_QUAL, Curriculum connector
PA_CONN_QUAL_CPNT, Curriculum connector- assigning items to the curriculum

PA_CONN_QUAL_JOB, Curriculum connector- matching the curricula with the job code and assigning
the curricula settings on the job code screen of the user
PA_CONN_QUAL_LOCALE_LABEL, curricula locale info
PA_CONN_QUAL_PARENT, parent curricula relations: curricula, subcurriculas...
PA_CONN_QUAL_REQ, Curricula connector, requirements
PA_CONN_SCHED, Scheduled Offering Connector
PA_CONN_SF_CPTY, Competency connector: BizX competencies
PA_CONN_SF_CPTY_RTNG_CRITERIA, Competency connector: BizX rating criteria (teasers)
PA_CONN_STUD_ALT_SUPER, User connector, alternate supervisors
PA_CONN_STUD_FEDERAL, User connector federal
PA_CONN_STUD_FEDERAL_ALT_SUPER, User Federal connector, alternate supervisors

PA_CONN_STUD_FEDERAL_SUPER, User connector Federal, alternate supervisors

PA_CONN_STUD_PRIVATE, User connector sensitive data
PA_CONN_STUD_SUPER, It contains the user's supervisors
PA_CONN_STUD_USER, User connector, related user for the admin
PA_CONN_STUDENT, User connector
PA_CONN_USER_PRFL, Admin Connector

Code Severity Message Text 1127 Exception Error while creating Facilty :
1001 Fatal Unexpected Error. 1128 Exception An input file must be provided for the Importer. Please check your configuration.
1002 Fatal Appserver may not be running 1129 Exception Unable to identify the intermediate file as specified in the Imported configuration
1003 Fatal Fatal Error in Delta Process 1130 Exception Improper invocation of non-member related method :
1006 Fatal Error validating XML 1131 Exception Segmentation is required, but segment size is not supplied. Please update your
1007 Fatal ELMSX configuration error configuration.
1008 Fatal Exception loading rule processors 1132 Exception XML Data could not be parsed.
1009 Fatal Error accessing DB packages 1133 Exception Plateau Interface Id was not specified.
1011 Exception Invalid record status 1134 Exception Plateau Interface Message XML was not specified.
1012 Exception Invalid active state 1135 Exception No consumer could be found for Plateau Interface Id
1021 Fatal Error in DB process. 1136 Exception Defined Consumer for Plateau Interface Id is of the wrong type as it can't consume XML
1101 Exception Unable to create entity. DOM Elements. Interface Id :
1102 Exception Entity does not exist. 1137 Exception No Consumable Bean of the Supported type(s) was found in this request: exiting with no
Work Unit to process.
1103 Exception Cannot specify a NULL Key value for reference entity
1138 Exception No InterfaceMessage Consumer Declared for this native Id
1104 Info Entity created.
1139 Exception Error while logging Interface Run Results.
1105 Warning Entity Invalid. So, nullified:
1106 Exception Unsupported Post Process : 1140 Exception NO Plateau Interface Consumable Beans were specified.
1107 Exception No default Data Format Pattern set for : 1141 Exception Message is not of the TextMessage type
1108 Exception No db object specified for getDeltaRecordCount 1142 Exception No such message found in this JMS queue.
1109 Exception No db object specified for performDelta 1143 Exception Using a non JMS destination
1110 Exception This controller does not support Segmentation. Please review your 1144 Exception Can't update Elmsx Posting record: a null Posting was supplied.
configuration. 1145 Exception Posting folder not properly configured: can't create any posting at this time.
1111 Exception Not supported for this implementation. 1146 Exception Could not archive posting file to the archive folder: archive folder.
1112 Exception Entity does not exist. Domain ID Parent: 1147 Exception Error while creating Custom Column reference value.
1113 Exception Entity does not exist. Org Domain: 1148 Exception Unable to find the Plateau LMS application server. Please verify your configuration
1114 Exception Entity does not exist. Org ID Parent: parameters.
1115 Exception Entity does not exist. Org Financial Account: 1149 Exception URL input NOT YET SUPORTED.
1116 Exception Rule Action is NOT SUPPORTED 1150 Exception No reports IDs were specified in the ELMSX configuration file.
1117 Exception Student-only Rule Processor may ONLY be used with an Entity of the 1151 Exception Unrecognized Rule Action.
'StudentType' type. Rule Processor : 1152 Exception Error while getting the Data Base Connection.
1118 Exception Configuration Error: the Student Custom Column Rule Processor 1153 Exception Error while generating reports.
requires the Rule definition to include a valid Custom Column Number. 1154 Exception Error while getting transaction.
1119 Exception Failed to instantiate a (remote) Plateau Interface dispatcher. 1155 Exception Error while committing transaction.
1120 Exception Failed to dispatch Plateau Interface Consumable beans to the JMS
1156 Exception Error while getting delta data from the database and converting to XML.
destination.
1157 Exception Error while creating the InterfaceMessageGenerator object for the associated
1121 Exception Failed to dispatch Plateau Interface XML element to the JMS destination. plateauInterfaceMessageId :
1122 Exception Failed to locate a Connector for Connector Command 1158 Exception Error while Updating the Last Update time for the Interface :
1123 Exception Can not instantiate Connector object(s) for the associated
1159 Exception Error while executing connector Post Process:
connectorCommand :
1160 Exception Error while executing connector Pre Process:
1124 Exception Error while generating Rules and Entities.
1161 Exception Entity invalid.
1125 Exception Error while creating Domain :
1162 Exception Circular Relationship detected while inserting Domain Parent:
1126 Exception No SQL Map specified.
1163 Exception Parent Domain ID and Domain ID should not be the same.

1217 Exception Date is in the future
1164 Exception Error while executing Pre Process DB Optimization scripts - Please contact
1218 Exception Invalid Date format
System Administrator who is maintaining your application.
1165 Exception Error while executing Post Process DB Optimization scripts - Please contact 1219 Exception Error while updateStudentBean. Student ID is null
System Administrator who is maintaining your application. 1220 Exception Error while creating student.
1166 Exception Length of Column exceeds Max. specified length. 1221 Exception Error while creating student financial account.
1167 Exception Invalid Date Format. 1222 Exception Erro while creating student preferences.
1168 Exception Invalid number Format. 1223 Exception Error while creating student joblocation.
1169 Exception Integer Part of number exceeds Max. specified size 1224 Exception Error while creating student country.
1170 Exception Error while importing data. 1225 Exception Error while creating student domain.
1171 Warning Input file not found. 1226 Exception Error while creating student employee status.
1172 Exception Error during reinitialize process. 1227 Exception Error while creating student employee type.
1173 Exception Record received for duplicate entity. 1228 Exception Error while creating student job position.
1174 Exception Entity Invalid. No transformation data configured. 1229 Exception Error while creating student organization.
1175 Exception Entity does not exist. Country: 1230 Exception Error while creating student region.
1176 Warning Potential issue while Importing Data. 1231 Exception Error while creating student alternate job positions.
1177 Warning Unable to process input file. No headers were read from input file. This may be 1232 Exception Error while updating student.
due to empty file or first line may be empty. 1233 Exception Error while updating student financial accounts.
1178 Warning Unable to process input file. No headers were configured. 1234 Exception Error while updating student preferences.
1179 Exception Error occurred while invoking SF API. Please check SF Integration settings. Also 1235 Exception Error while updating student custom columns.
'CONNECTOR' admin should exists in Bizx. 1236 Exception Error while updating student phone numbers.
1180 Exception Entity is Inactive. 1237 Exception Error while updating student alternate job positions.
1181 Exception Error while executing Pre Process DB Optimization Validation scripts - Please 1238 Exception Error: Job position id exists in Alternate Job Positions
contact System Administrator who is maintaining your application. 1239 Exception Entity does not exist. Alternate Job Positions
1182 Warning Error while executing Post Process DB Optimization Validation scripts - Please
1240 Exception Entity cannot be null. 'Alternate Job Positions' Ref entity cannot specify a NULL
contact System Administrator who is maintaining your application.
Key value.
1183 Info This Timezone is updated to display in UI.
1241 Exception Entity does not exist. Financial Account Code Domain:
1184 Warning Problem deleting file from configured input location. Please delete it manually. 1242 Exception Entity does not exist. Job Position Domain:
File Name:
1243 Exception Entity cannot be null. 'Custom columns' Ref entity cannot specify a NULL Key
1201 Info User Deactivated.
value.
1202 Info Administrator roles removed. 1244 Exception Error while setting student security question and answer.
1203 Info Instructor Deactivated 1245 Exception Error while generating password.
1204 Info User removed from Schedules- 1246 Exception Job Position Effective Date cannot be in the future.
1205 Info Supervisor value nullified for subordinates- 1247 Exception Job Position Effective Date cannot be before the existing Job Position Start Date
1206 Info User added as terminated. in the Work History.
1207 Warning Supervisor value not applied. Supervisor ID reference value not found. 1248 Exception Job Position Effective Date must match the existing JP Start Date in the Work
1208 Warning Supervisor value not applied. Supervisor is terminated. History for the same Job Position.
1211 Exception Hire Date cannot be in the future. Hire Date: 1249 Warning Job Position Effective Date should not be in the future.
1212 Exception Term Date cannot be in the future. Term Date: 1250 Warning Job Position Effective Date should not be before the existing Job Position Start
Date in the Work History.
1213 Exception Term Date cannot be before Hire Date
1251 Warning Job Position Effective Date should match the existing JP Start Date in the Work
1214 Warning Supervisor value not applied. Supervisor ID is the same as the user ID. History for the same Job Position.
1215 Warning Circular Supervisor relationship detected. 1252 Warning Student is being reactivated.
1216 Warning Duplicate PhoneNumber found. 1253 Warning Job Position Effective Date is the same for changing Job Position.

1254 Exception Job Position Effective Date is the same for changing Job Position. 1292 Exception User ID cannot contain leading or trailing spaces.
1255 Warning Supervisor value not applied. Supervisor ID cannot be same as one of the 1293 Exception User ID exceeds maximum allowable characters. User ID:
alternate supervisors. 1294 Warning HRBP value not applied. HRBP is same as the user ID.
1256 Warning The Primary Supervisor cannot be removed as the user has alternate supervisors 1295 Warning HRBP value not applied. HRBP reference value not found.
specified.
1296 Warning HRBP value not applied. HRBP is either terminated or inactive.
1257 Warning Primary Supervisor not specified. Alternate Supervisors not applied.
1301 Exception General Exception importing a document record
1258 Warning Alternate Supervisor value not applied. Alternate Supervisor ID reference value
1302 Exception Default value in elmsx-document.xml config file is not legal
not found.
1259 Warning Alternate Supervisor value not applied. Alternate Supervisor ID is the same as the 1303 Exception Unexpected Error while processing folder lookup - see the log file for more
user ID. details
1304 Exception Unexpected Error while preparing small xml files for processing - see the log file
1260 Warning Circular Alternate Supervisor relationship detected.
for more details
1261 Warning Alternate Supervisor value not applied. Alternate Supervisor ID is the same as the
1305 Exception Unexpected Error while validating xml file - see the log file for more details
primary supervisor.
1306 Warning No File found in the Folder
1262 Warning For Organization, Job Code, Job Location, Job Grade, Employee Type, the
values of the Position record is used instead of the passed values. 1307 Warning Record rejected: Incomplete document information
1263 Exception Position ID is Inactive. 1308 Exception Domain value not found in the database
1264 Exception Position ID is already tied to another user. 1309 Exception Document Type reference not found in the database
1265 Exception Error while updating student government reporting information. 1310 Exception Record rejected: Document ID not specified
1266 Exception Error retrieving legal entity 2483 information. 1311 Exception Record rejected: Document ID too long
1267 Exception Error retrieving employee class 2483 information. 1312 Exception Record rejected: Domain ID is null
1268 Exception Legal Entity is required when including in government report. 1313 Exception Record rejected: Document Type reference is null
1269 Exception Error creating student legal entity. 1314 Exception Record rejected: Item references a non-existing entity:
1270 Exception Error creating student employee class. 1316 Info Document not RETIRED because the record did not exist in the database
1271 Exception Error creating student regular temp reference value. 1320 Exception Maximum enrollment cannot be less minimum enrollment
1272 Exception Error retrieving regular temp information. 1321 Exception Inactive revisions are not supported
1273 Exception Duplicate User records detected. 1322 Exception Revision date cannot be in the future
1274 Exception Error creating 2483 Legal Entity record. 2483 Legal Entity Description cannot be 1323 Exception Create date cannot be in the future
null. LGL_ENTITY_2483_ID : 1324 Exception Approval date cannot be in the future
1275 Exception Error creating 2483 Employee Class record. 2483 Employee Class Description 1325 Warning Default Initial Assignments combination Invalid. So
cannot be null. EMP_CLASS_2483_ID : 1326 Warning Default Retraining Assignments combination Invalid. So
1276 Warning Student doesn't have an email address. Initial password is not sent. StudentID: 1327 Exception Item does not exists.
1277 Warning Supervisor value not applied. The new supervisor is already associated with the 1328 Exception Item Type id is null
user's review as a feedback rater.
1329 Exception Item id is null
1278 Exception This Timezone is not displayed in UI. Please use different TimeZone ID.
1330 Exception Title is null
1279 Exception Error creating Disability Classification.
1331 Warning Item Module cannot be processed due to missing data in Item input file.
1280 Exception Date Of Birth cannot be in the future. DOB:
1332 Exception Connector cannot process this Launch Type.
1281 Exception SSN cannot be null.
1333 Exception Build Date cannot be in future.
1285 Exception The User ID does not exist but an old record exist for this User ID. This means
1334 Exception Invalid Mastery Score. The value should be an integer between zero and one
that this User existed at some point and has been deleted. You may not re-use
hundred.
this User ID for a new User.
1335 Exception Legal Entity is required when Including in government reporting.
1290 Warning This Timezone is not displayed in UI. Please add a transformation rule to map it
to new Timezone ID. 1336 Exception Error updating government reporting information for item.
1291 Exception Extended User Data cannot be processed as the user does not exists. 1337 Exception Competency does not exists.
1338 Exception Rating invalid for RatingScaleID :

1339 Exception Competency is inactive. So, it cannot be associated with Item. CompetencyID: 2018 Exception Segment 1 was not found this scheduled offering
1340 Exception The thumbnail image reference does not belong to the supported format. 2019 Exception Multiple Scheduled Offering's exists with same legacy ID (Custom Column 99).
1341 Exception The new revision date must be after the previous revision. Single legacy ID can be mapped to only one Scheduled offering.
1342 Exception Offline file path is invalid. 2020 Exception Scheduled Offering item details doesn't match with provided item details.
1343 Exception Repeat Count is required when failure action is specified. 2101 Exception Record Already exists.
1344 Exception Offline file path is required when offline accessible is enabled. 2102 Exception Duplicate Record in input.
1345 Exception Use AICC wrapper can be applied only when the launch type is AICC. 2103 Exception Schedule Offering Id is null.
1346 Exception Either COMPLETE_ON_LAUNCH or 2104 Exception Schedule Offering Id does not exist or is Invalid.
TRIGGER_CPNT_PASS/TRIGGER_CPNT_FAIL can be applied but not both. 2105 Exception User Id is null.
1347 Exception TRIGGER_CPNT_PASS/TRIGGER_CPNT_FAIL can be specified only for lunch 2106 Exception User Id does not exist.
type AICC, SCORM 1.2 , SCORM 2004 4Ed. 2107 Exception Enrollment Date is after the Scheduled Offering Start Date.
1348 Exception Failure Status is required when failure action is specified. 2108 Exception Enrollment status id is null.
1349 Exception Failure Status is invalid. 2109 Exception Enrollment status id is invalid.
1350 Warning Approval Process ID not specified. Approval Required is set to false 2110 Exception Connector cannot process records with Enrollment Status Type Id 'P'
1351 Exception HTML Text entered did not pass AntiSamy validation. 2111 Exception The scheduled offering is full and waitlisting is not permitted. User ID:
1352 Exception Please specify an item with the proper classification and try again. 2112 Warning The user is added to the waitlist because the registration is full. User ID:
1353 Exception Failure status is required when Trigger Component Failure Status is set for Item 2113 Exception User Id is inactive.
Module.
2301 Exception Record Already exists.
1401 Exception No default value
2302 Exception Duplicate Record in input
1402 Exception Reference not found
2303 Exception Job Position Id is null
1403 Exception Organization Type not found.
2304 Exception Entity cannot be null. 'Custom columns' Ref entity cannot specify a NULL Key
1404 Info Organization Deactivated. value.
1405 Warning Organization not Deactivated. 2305 Exception Invalid value.
1406 Exception Organization ID required. 2306 Exception Salary Range Minimum cannot be greater than Salary Range Maximum.
1407 Exception Incomplete Organization Information 2501 Warning Curriculum cannot be a parent of itself. Parent Qual Nullified
1408 Fatal Fatal Error in Delta process 2502 Warning Curriculum parent does not exists. Parent Qual nullified.
1409 Exception Organization cannot be its own parent 2503 Warning Curriculum hierarchy has cyclic loops. Parent Qual Nullified
1410 Exception Error determining heirarchy in delta 2504 Exception Date cannot be in the future
1411 Exception Organization cannot have two parents 2505 Warning Default Initial Assignments combination Invalid. So
1412 Warning Account code exists more than once 2506 Warning Default Retraining Assignments combination Invalid. So
1413 Warning Org Owner exists more than once 2507 Warning Same display order specified for multiple Items.
2003 Exception Item Id is null 2508 Warning Same display order specified for multiple Requirements.
2004 Exception Item Could not be found 2509 Warning Same display order specified for multiple Sub Curricula.
2008 Exception Max registrations is less than Min Registrations 2510 Warning Curriculum does not exists. Record Ignored.
2011 Exception Invalid Segment end time 2601 Exception No default value
2012 Exception Invalid Segment start time 2602 Exception Reference not found
2013 Exception Segment End Date lesser than segment start date 2603 Info Position Deactivated.
2014 Exception Items must be clasified as Instructor Lead or Blended to be scheduled 2604 Warning Position not Deactivated.
2015 Exception End Date is Null 2605 Exception Position ID required.
2016 Exception Start Date is Null 2606 Exception Incomplete Position Information
2017 Exception Enrollment Cut Off Date is After the start Date of the Scheduled Offering 2607 Fatal Fatal Error in Delta process
2608 Exception Reports To may not be the same position:

2609 Exception Reports To may not create cycle: 4609 Exception Custom Column 1 should be Integer value.
2610 Exception Reports To active must match position 4610 Exception Custom Column 2 should be Integer value.
3100 Warning Entity Invalid. So, defaulted to N: 4611 Exception Custom Column 3 should be Integer value.
3101 Warning INCLUDE_SUB_ORGS cannot be 'Y' as Organization doesn't have any Sub Orgs. 4612 Exception Custom Column 4 should be Integer value.
So, defaulted to N. 4613 Exception Custom Column 5 should be Integer value.
3301 Exception This Competency cannot be changed as there is Assessment History using this 4614 Exception Custom Column 6 should be Integer value.
Competency.
4615 Exception Custom Column 7 should be Integer value.
3351 Exception Minimum Rating needs to be specified.
3352 Exception Minimum Rating should be 1 or greater.
3353 Exception Maximum Rating should be greater or equal to Minimun Rating.
3354 Exception Performance Rating levels were not provided.
3355 Exception Competency Category and Competency Name of Teaser do not match with
Competency details.
3356 Info CompetencyID conflict detected. Competency renamed from 4621 Exception Custom Column 23 should be Integer value.
3357 Exception Rating Scale with the same ID already exists. RatingScaleID : 4622 Exception Custom Column 24 should be Integer value.
3358 Warning Rating scale cannot be updated as it is in use. RatingScaleID : 4623 Exception Custom Column 25 should be Integer value.
3359 Info Rating Scale ID conflict detected. Rating Scale renamed from 4624 Exception Custom Column 16 should be either True or False.
3360 Exception CompetencyID with the same ID already exists. CompetencyID : 4625 Exception Custom Column 17 should be either True or False.
3361 Exception Maximum Rating should be greater or equal to 2. 4626 Exception Custom Column 18 should be either True or False.
3362 Exception Default Rating Scale ID not specified. 4627 Exception Custom Column 19 should be either True or False.
3702 Exception Duplicate Record in input. 4628 Exception Custom Column 20 should be either True or False.
3703 Exception The chosen Job Code cannot be an Alternate Job Code since it is already the 4629 Exception Custom Columns 1 to 30 are not present.
Users current Job Code. 4630 Exception Invalid value.
3704 Warning The Alternate Job Position Removal flag is invalid. So defaulted to 'N'. 4631 Exception Salary Range Minimum cannot be greater than Salary Range Maximum.
4501 Exception Effective Date is null. 4632 Warning For Job Grade,FTE Factor (non-shared positions),Salary Range Mininum,Salary
4502 Exception Base Salary is null. Range Maximum,Salary Range Currency,the values of the Position Number
record is used instead of the passed values.
4503 Exception Transition Code is null.
4633 Exception This compensation manager assignment cannot be done because it creates a
4504 Exception Base Salary should be Positive Integer value.
circular compensation manager relationship for this User. Recommender ID:
4505 Exception STIP Incentive Amount should be Positive Integer value. 4634 Exception Annual factor cannot be negative.
4506 Exception LTIP Incentive Amount should be Positive Integer value. 4635 Exception This compensation manager assignment cannot be done because a user cannot
4507 Exception LTIP Incentive Units should be Positive Integer value. be his own manager.
4508 Exception FTE is null. 4636 Exception Custom column name cannot be null.
4509 Exception FTE should be between 0.01 and 1. 4637 Exception Custom column data type does not match expected type.
4601 Exception User ID is null. 4638 Exception FTE should be between 0.01 and 1.
4602 Exception Invalid User ID. 5501 Exception Error while removing Admin Role's for
4603 Exception Invalid Compensation Manager. 5502 Exception Error while creating Admin.
4604 Exception Compensation Manager is Terminated. 5503 Exception Error while adding Admin Role's for
4605 Exception Entity cannot be null. 'Custom columns' Ref entity cannot specify a NULL Key 5504 Exception Error while updating Admin Preferences.
value. 5505 Exception Error while updating Admin.
4606 Exception Base Salary is null. 5506 Exception Error while generating Admin password.
4607 Exception FTE is null. 5507 Exception Error while creating Admin Domain.
4608 Exception Annualization Factor is null.

5508 Exception Admin ID cannot contain leading or trailing spaces
5509 Warning Role not associated with Admin. Hence no action.
5510 Warning Roles being added and removed are the same. Hence no action.
5511 Warning Role nullified
6010 Exception User id is null
6011 Exception User id does not exist
6012 Exception Item id is null
6013 Exception Item does not exist
6014 Exception Completion Date is null
6015 Exception Completion Date is in the future
6016 Exception Revision Number is null
6017 Exception Credit Hours is null
6018 Exception Credit Hours is less than 0
6019 Exception ScheduledOffering does not exist
6020 Exception Grade is null
6021 Exception Item Type does not exist
6022 Exception Completion Status is null
6023 Exception Completion Status does not exist
6024 Info Record already exists
6025 Exception Item Type id is null
6026 Exception Item id does not
6027 Exception Esignature ID does not exist
6028 Exception Scheduled Offering Details could not be found
6029 Exception Esignature is required /Esignature has be enable in the global properties
6030 Exception Contact Hours is less than 0
6031 Exception CPE Hours is less than 0
6032 Exception Total Hours is less than 0
6033 Exception Mutilple ESignatures are not supported.
6034 Warning Government reporting data not recorded for learning history event
6035 Exception Scheduled Offering item details doesn't match with provided item details.
1150 Exception Error determining Domain hierarchy in delta.
5

13. A Reminder about Connectors
• Only header-based processing mode is supported for new customers

 connector.input.file.processing.mode=header
• Enhancements are supported only for header-based processing
• Position-based processing will be removed as an option from the UI

by 1411

13. A Reminder about Connectors – Connector Template Download
This new feature provides admin with the ability to:
- Download the latest connector template(s) for any connector (“all columns” option).
If custom columns beyond the standard 15 have been configured, they will be
included in the template as well.
- Download connector template(s) for any connector that contains just columns that
have been mapped (per the connector.properties file configurations). This option
(“only mapped columns”) applies only when header-based processing is enabled.





14. A Reminder about Connectors – Minor enhancements included in b1411
Jira Description Enhancement Config Details

Type
LRN-7147 Support the “force sequential completion” Admin Opt-in Use
setting for content objects item.field.mapping.data.FORCE_ORDER=
FORCE_ORDER –OR–
item.itemmodule.field.mapping.data.FOR
CE_ORDER=FORCE_ORDER
LRN-6321 View connector error logs in UI Universal N/A

Connector error logs in UI




15. A Reminder about Connectors –b1502 updates
HR Business Partner (HRBP) – LRN-7912 :
•Add required workflows to HRBP users.
•Setup connectors to import HRBP-User mapping.
SF User Connector for Integrated Customers

•Map HRBP to input HR field: System Admin > Configuration > System Configuration > CONNECTORS >
sfuser.field.mapping.data.HRBP=HR
•Supports mapping a single HRBP to a User.
Standard User Connector and Federal User Connector
•New input data file user_manager_data.txt with fields:

STUD_ID
MANAGER
REMOVE_ALT_SUPER - ‘Y’ = Delete; ‘N’ = Add (default)
ALT_SUPER_TYPE - ‘A’ = Alternate Supervisor; ‘H’ = HRBP
•Supports mapping multiple HRBP and Alternate Supervisors to a User.

Note: The limit on the total number of HRBP and Alternate Supervisors has been increased from 10 to now 40.

HR Business Partner (HRBP) – LRN-8712 :
In earlier versions of the application Online Content in an Item always opened in a new browser window. This
configuration is available at the content object and can be updated or set via:
Item Connectors (Item Data and Content Module Data) :

New browser window will remain the default configuration behavior.
1.Enable usage of the feature in: System Admin > Configuration > Global Variables > Enable Inline Content Launch
Configuration
2.Then, in order to open the content in the same browser window, the value can be set in:
a)Content > Content Objects > Launch Method > Launch in a New Browser Window
b)Content > Tools > Import Content
c)Connector properties:
item.field.mapping.data.LAUNCH_IN_A_NEW_BWSR_WINDOW=LAUNCH_IN_A_NEW_BWSR_WINDOW
-OR-
item.contentmodule.field.mapping.data.LAUNCH_IN_A_NEW_BWSR_WINDOW=LAUNCH_IN_A_NEW_BWSR_WINDOW.


Type
LRN-8920 When the User Connector detects that Universal N/A

you are making a user a primary
supervisor and that user is already an
alternate supervisor, it removes the
alternate supervisor assignment and
adds the user as a primary supervisor in
one action. The enhancement applies to
all User Connectors: user, SF user, and
Federal.
LRN-7086 User connector: Provide option to keep Admin Opt-in user.connector.inactiveRule.cleanDevPlan=
items, curricula, and programs on the N
user’s learning plan when the user is
inactivated


Type
LRN-8155 Learning History connector: provide the Admin Opt-in 1. Populate the new column:
ability to specify timezone for completion COMPL_DTE_TIMEZONE
date -OR-
2. Set a value for:
learninghistory.connector.defaultValue.Com
plDteTimezone=
LRN-8154 Item connector: provide the ability to copy Admin Opt-in Item.connector.defaultValue.revision.copyS
substitutes when revising an item ubstitutes=Y


Type
LRN-7685 Require explicit revision dates to be Admin Opt-in In Enable this restriction via:
passed in order to prevent multiple item.connector.defaultRevDate.currentTime
revisions from getting generated via the stamp=N. This is the default for new
item connector. When this is enabled, the customers.
connector follows these rules: When set to “Y”, the connector follows
•New Item ID + Null Rev Date = Throw error: existing behavior, i.e., the new revision is
“Revision date cannot be null” created with current timestamp as the
•New Item ID + Explicit Rev Date = New item
with rev date per the input file
•Existing Item + Null Rev Date = Throw error:
“Revision date cannot be null”
•Existing Item + Explicit Rev Date that is later
than item's rev date = Revise the item
•Existing Item + Explicit Rev Date that is same
as the item's latest rev date = Update the item
•Existing Item + Explicit Rev Date that is earlier
than item's rev date = Reject the item record


Type
LRN-7305 Support additional fields via the Admin Opt-in Mapping configurations in the Connector
Scheduled Offering connector (shown properties file
below)
Note: Values for the 2483 fields can be

inherited using:
scheduleoffering.connector.defaultValue.i
nherit2483FieldsFromItemsWhenNull=Y


Type
LRN-8975 The limit of total Human Resource Admin Opt-in N/A
Business Partners (HRBP) and alternate
supervisors has been increased. The
User Connector loads up to 200 per
employee. The Manage Alternate
Supervisor dialog now displays all the
associated Alternate supervisors and
HRBPs. As long as the total limit is not
exceeded, new Alternate Supervisors can
be added.


Type
LRN-8701 Government reporting Age field will be Universal N/A
replaced by Birthdate.
•A new government reporting field for
birthdate is available on the
User>Related Government Reporting,
SFSF and User connectors, User import,
and BizX Extended Import for Employee
Data.
•Training Manager export of training
requests will contain
age (computed) and Birthdate.

Commerce: Set Cancellation Policy on Pricing tab of Item or Scheduled
Offering
Connectors: Item or Scheduled Offering Connector is updated to include Cancellation Policy ID.
If blank, when creating an Item the cancelation policy will be set to the system default; when
creating a scheduled offering, the cancellation policy will be set to the that of the parent Item.
When updating an existing Item or Scheduled offering, if blank any existing cancellation policy
will not be deleted.


Type
LRN-8972 Competency connector “competency competency.connector.sf.enableCategor
category” field support ySync=
Default value: “N” for existing customers,
“Y” for new.
When set to “Y”,the connector uses the
BizXcategory column and creates/updates
competency records in the LMS with the
corresponding category ID
NOTE: Competency categories need to
have been createdin the LMS first. The
connector will not create them on the fly.
LRN-9334 Skillsoft connector productization. See Now available under the list of
Migration to Skillsoft connector workbook. connectors.Migration details for existing
customers are being worked out with PS.

Bulk Learning Event Editor (Split costs)
Split costs cannot be recorded through learning history connector or import.
Commerce: Message when re-enroll


Type
LRN-8816 Item Connector: Allow updates to Admin Opt-in item.connector.update.inactiveRevisions
olderinactive revisions =
Defaultvalue: N
Accepted values: Y, N
LRN-9012 ScheduledOffering Connector: Control Admin Opt-in scheduleoffering.connector.defaultValue

“Allow usersto access online content .segmentOnlineAccessAllowed=
without registration property” Defaultvalue: inherit –for new customers;
When set to “inherit”, the segment will set existing customer configurations retained
the value according to the item setting. Accepted values: Y, N,
If the SO connector tries to create a Inherit
segment that does not exist in the item,
ONLINE_ACCESS_ALLOWED will be set
to “N”.
When set to blank, the connector will
treat this as “inherit”.

Thank you
© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Knowledge Session - Connectors 2016 - 01 - 20

Uploaded by

Copyright:

Available Formats

You might also like

Knowledge Session - Connectors 2016 - 01 - 20

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Knowledge Session - Connectors 2016 - 01 - 20

Uploaded by

Copyright:

Available Formats

Knowledge Session: Connectors

Angel Garcia– EMEA NEXUS LMS

This presentation is for the training of Customer Support

Created Date Delivered Date

Alex Downs 16/02/2015

Angel Garcia 20/01/2016

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 2

6. Connectors: Misc. Settings

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 3

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 4

Connectors are used to import data into the LMS.

There are different types of connectors offered.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 5

Connector Processing Extract Program

Connector SFTP Site

Each Connector Gets Input File

Load Input Into

Adds or Updates to LMS

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 6

Processing Methods for Input Fields

Input File Format

Column delimiter character: Will always be a pipe (“|”) character.

Row delimiter character: !##!

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 8

Input File Format (cont.)

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 9

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 10

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 12

Skillsoft We added a Skillsoft connector in Q3 2015 to replace existing OLSA

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 13

• Olsa Item Connector

See Section 3 to download the Olsa Connector Workbook

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 14

The Skillsoft connector:

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 15

What are they?

Where can I find them?

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 16

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 17

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 18

LMS Tenant ID. Found on SharePoint. This means that the

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 19

High Level Overview of Connector Process

BizX Employee LMS Connector

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 20

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 21

Use browser’s Find function to find customer name.

Click on customer name

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 22

Scheduled Jobs run processes for Connector input file:

Click on “LMS User Export” or similar named scheduled job

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 23

- ‘Valid Users Only’: Checking this will only export

-’Short Format’: Checking this will only export the

- ‘Character Encoding’: This should ALWAYS be

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 24

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 25

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Internal 26