MétaCan
Menu
Back to cohort
Record W2085569051 · doi:10.4018/jeis.2010040101

An Exploratory Study of the Key Skills for Entry-Level ERP Employees

2010· article· en· W2085569051 on OpenAlexaff
Alan R. Peslak, Todd A. Boyle

Bibliographic record

VenueInternational Journal of Enterprise Information Systems · 2010
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsSt. Francis Xavier University
Fundersnot available
KeywordsKnowledge managementKey (lock)Enterprise resource planningBusinessExploratory factor analysisExploratory researchSkills managementScale (ratio)Entry LevelProcess managementResource (disambiguation)MarketingComputer scienceMedical education

Abstract

fetched live from OpenAlex

This research identifies the key skills (e.g., business, team, communication) that industries expect for entry level positions involving enterprise resource planning (ERP) systems. Based on a review of the literature, a number of possible core skills that ERP entry level employees should possess are identified. To identify the relative importance of these specific skills, a web-based survey involving IT professionals from 105 organizations is conducted. Analyzing the findings using exploratory factor analysis and scale reliability analysis indicates four specific and significant factors representing the major key skills that industry expects from entry level ERP positions labeled for this study such as systems analysis and integration, team skills, project management, and business and application understanding. Various common technical skills (e.g., programming, networks) were found to be significantly less important than the business and team skills. This study should assist companies in developing criteria for evaluating potential candidates for entry level positions in ERP systems, as well as universities for evaluating the relevancy of their IT and Business programs.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.008
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.004
Threshold uncertainty score0.017

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.008
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0030.001
Scholarly communication0.0020.001
Open science0.0000.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0040.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.026
GPT teacher head0.305
Teacher spread0.279 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designQualitative
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations8
Published2010
Admission routes1
Has abstractyes

Explore more

Same venueInternational Journal of Enterprise Information SystemsSame topicERP Systems Implementation and ImpactFrench-language works237,207