\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={ERP Security Based on Web Services},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2020-01-15 (revised: 15 January 2020)}
\def\TheID{\makeatother }
\def\TheDate{2020-01-15}
\title{ERP Security Based on Web Services}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Mamoun  Hadidi}

             \author[2]{Saleh  Hadidi}

\renewcommand\Authands{ and }

\date{\small \em Received: 10 December 2019 Accepted: 3 January 2020 Published: 15 January 2020}

\maketitle


\begin{abstract}
        


The ERP system is one of the most important systems implemented by organizations in Jordan, whether governmental or private organizations. Because of the numerous development in Internet services and the increasing dependence on web services, this has led to the appearance of many types of ERP systems that depend on web services and use the web interface as the main interface for the system, and because of this development in the ERP system and its dependence on web services, this has led to problems in security with ERP system, especially since this system will be vulnerable to a hacker attack because it contains important data for organizations because the ERP system is a large database that serves all departments of organizations such as the finance, administrative, and marketing departments. This makes it a major target through which hackers seek access to organization data, which makes the security of an ERP system based on Web services an important topic that must be studied. Therefore, this paper will focus on the topic of ERP Security and will address the basic principles, properties, main requirements, and challenges of ERP system security based on Web services.

\end{abstract}


\keywords{}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
rganizations in the world are using a wide variety of information systems to Support their products and services to growing business and improve organizational performance (Al-Dhaafri et al, 2016).\par
ERP systems in large and medium-sized organizations contribute to the management and use of their resources (materials, human resources, financing, etc.) in effective ways, by providing integrated solutions to the organization's information processing needs.  {\ref (Olson DL et al., 2012)} ERP systems are a key component of government or private organizations. The ERP system contains important data that is exposed to many threats both external and internal, has a significant impact on the failure of the Organization's work. Therefore, all security aspects such as Integrity, confidentiality and availability are critical in the ERP system \hyperref[b2]{(Gupta et al., 2017)}. 
\section[{The other important benefits of an ERP as following as:}]{The other important benefits of an ERP as following as:}\par
? Lower operational cost by defined and more streamlined business processes (oracle, 2017).  
\section[{Principles of ERP System Security based on Web Services}]{Principles of ERP System Security based on Web Services}\par
Security principles for system designers are considered as guidelines in the design and implementation of systems security.\par
There are many security principles will be mentioned as follows: 
\section[{a) Security Defense in depth}]{a) Security Defense in depth}\par
This principle is based on the imposition of security policies on every layer of the system and the architecture of this system, which prevents the hacker from infiltrating the system  {\ref (Kumar,2014)}. In addition, enterprises apply this principle by using the firewall as the first line of defense, the second line is using Web server security, the third line operating system security, database security level and other levels as the customer needs. 
\section[{b) Patch the weakest link}]{b) Patch the weakest link}\par
This principle depends on the designers of the systems to identify weaknesses in the security of the system in various components by conducting tests of the system and try to penetrate this system \hyperref[b4]{(Kumar, 2014)}. Also strengthen any weak layer can be penetrated. 
\section[{c) Classifications}]{c) Classifications}\par
This principle classifies all system resources and functions into different security classifications, limiting access to users with appropriate roles and privileges \hyperref[b4]{(Kumar, 2014)}. In addition to preventing accidental access to system confidential data and preventing unauthorized access to the system. 
\section[{d) Single entrance point of entry}]{d) Single entrance point of entry}\par
The ERP system should allow users only through a single authentication point and should avoid other points of entry and URL shortcuts. However, the importance of this principle reduces the chances of penetration to secret data and unauthorized access to data  {\ref (Kumar,2014)}. It also has all the web pages protected and automatically redirected to the login page that performs as a single entry point. The system does not allow access to system data through pages other than the login page. 
\section[{e) User data validation}]{e) User data validation}\par
The data inserted by the user should be validated and cleaned at various levels in the system. Data must also be properly encrypted when saved and transported into different layers \hyperref[b4]{(Kumar, 2014)}. However, the importance of this principle is to prevent attacks caused by the introduction of malicious contents into system data. The security mechanism checks the data entered by the user in the client layer and on the server layer using different verification methods. 
\section[{III. Properties of ERP System Security based on Web Services}]{III. Properties of ERP System Security based on Web Services}\par
There are five security properties as follows (Messaoud and Diouri, 2014): 
\section[{a) Confidentiality}]{a) Confidentiality}\par
This property includes preventing unauthorized persons from reading the information and allowing only those authorized to read the information from the system. 
\section[{b) Integrity}]{b) Integrity}\par
This feature does not allow unauthorized users to allow modification of data in the system, and only allow modification of data to authorized users. 
\section[{c) Authenticity}]{c) Authenticity}\par
This property ensures that the person using the system is the same person who is allowed to use the system. 
\section[{d) Non-repudiation}]{d) Non-repudiation}\par
This property ensures that the appropriate proof is logged in the user transaction log so that the user is not allowed to deny the transaction. 
\section[{e) Availability}]{e) Availability}\par
This property ensures that users can access the information in the system at any time without any obstacles preventing this property. 
\section[{IV. Security challenges of ERP System}]{IV. Security challenges of ERP System}\par
Security based on Web Services ERP systems are of critical nature because of the value of the data they contain and the need to adopt the complete confidentiality of these data .also what may be dangerous to all department of the organization because of any security breach of data, representing security challenges is a real problem for organizations using the ERP system.\par
The main of the security challenges facing the ERP system is as follows: 1. Passwords are used in the default database or default applications. 2. Access to the system from outside the place of the organization using this system. 3. Direct access to the database system by users of this system inside the organization. 4. The bad design of the security system of the ERP system by the providers, which leads to security problems in this system. 5. Not using a data encryption system in the ERP system that prevents any data leaks during data transfers and update information. 6. Weak passwords and the inability to control them because of the use of many machine passwords. 
\section[{V. Security Requirement of ERP System Security based on Web Services}]{V. Security Requirement of ERP System Security based on Web Services}\par
Data-level transactions are performed securely from one end to the other during transport and data storage. Requirements for providing comprehensive security for web services are summarized in following table (Messaoud and Diouri, 2014): 
\section[{Requirement}]{Requirement} 
\section[{Clarifications}]{Clarifications} 
\section[{Authentication}]{Authentication}\par
There is an urgent need for the system to verify the identity of the user. Especially in the case of mutual authentication because users may have indirect contact with the system. Therefore, multiple authentication methods are used and can be grouped together. These methods include password and Lightweight directory access protocols (LDAP) 
\section[{Authorization}]{Authorization}\par
Authorization: This requirement is necessary to control the process of authorizing access to information about the system, and determining the mechanisms of delegation for the system Data Integrity and Data Confidentiality\par
Data integration technology guarantees that data has not been changed during the transmission process. This technique also includes data confidentiality using various encryption and digital signature technologies. 
\section[{Audit Trails}]{Audit Trails}\par
This requirement includes the audit process and tracking user access and behaviour. In order to reduce the occurrence of any violations and check the accounts to ensure that this violation does not occur and repair any gap may lead to any violation VI. 
\section[{Conclusions}]{Conclusions}\par
This paper focused on ERP security based on web services where this study explained the ERP system in terms of its definition and indicated the extent of its importance for governmental and private organizations as this system is one of the most important systems that organizations seek to implement due to the great benefits that this system provides to organizations.\par
The implementation of the ERP based on web services faces many challenges and difficulties and the most important of these challenges, which this study focused on are security challenges, so the study clarified the basic principles upon which the security systems that used in ERP based on web services, where the study found that the most important safety principles that should be present are Security defence-in-depth, Patch the weakest link, Classifications, Single entrance point of entry and User data validation.\par
Also, the study explained the most important security characteristics of the ERP based on web services that must be contained in the security system, which are Non-repudiation, Authenticity, Confidentiality and Availability.\par
Nevertheless, the implementation of the ERP system faces many challenges, so the study explained the most important of these challenges that face the implementation of the system, and there are many requirements that the security application requires in the ERP system based on web services, so this study explained the most important system requirements that must exist In order to activate security with high efficiency, the most important of these requirements are Authentication, Authorization, Data Integrity, Audit Trails.			\footnote{Year 2020 ( ) E © 2020 Global Journals ERP Security Based on Web Services} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Kumar (2014)]{b4}\label{b4} 	 		\textit{Architecting High Performing, Scalable and Available Enterprise Web Applications},  		 			S S Kumar 		.  		2014. 8 February 2019. San Francisco: Elsevier Science \& Technology.  	 	 (Available from: ProQuest Ebook Central) 
\bibitem[Olson et al.]{b6}\label{b6} 	 		\textit{Case of development of a small business ERP consultant knowledge base. Advances in Enterprise Information Systems II 2012},  		 			D L Olson 		,  		 			V Van Huy 		,  		 			N M Tuan 		.  		p. 81.  	 
\bibitem[Link and Back ()]{b5}\label{b5} 	 		‘Classifying systemic differences between Software as a Service-and On-Premise-Enterprise Resource Planning’.  		 			B Link 		,  		 			A Back 		.  		 \xref{http://dx.doi.org/10.1108/JEIM-07-2014-0069}{10.1108/JEIM-07-2014-0069}.  	 	 		\textit{Journal of Enterprise Information Management}  		2015. 28  (6)  p. .  	 
\bibitem[Gupta ()]{b2}\label{b2} 	 		‘Identification of challenges and their ranking in the implementation of cloud ERP: A comparative study for SMEs and large organizations’.  		 			S Gupta 		.  		 \xref{http://dx.doi.org/10.1108/IJQRM-09-2015-0133}{10.1108/IJQRM-09-2015-0133}.  	 	 		\textit{International Journal of Quality and Reliability Management}  		2017. 34  (7)  p. .  	 
\bibitem[Farrington (2017)]{b1}\label{b1} 	 		\textit{Oracle ® E-Business Suite},  		 			R Farrington 		.  		2017. August.  	 
\bibitem[Al-Dhaafri and Al-Swidi ()]{b0}\label{b0} 	 		‘The impact of total quality management and entrepreneurial orientation on organizational performance’.  		 			H S Al-Dhaafri 		,  		 			A Al-Swidi 		.  	 	 		\textit{International Journal of Quality and Reliability Management}  		2016.  	 
\bibitem[Houssain ()]{b3}\label{b3} 	 		\textit{Web Service Security Overview, analysis and challenges},  		 			E Houssain 		.  		2014. 11 p. .  	 
\bibitem[Thomas ()]{b7}\label{b7} 	 		‘What is ERP? Definition and FAQs -ProQuest’.  		 			W Thomas 		.  		 \url{https://search-proquestcom.ezproxy.napier.ac.uk/docview/1919042734?rfr\textunderscore id=info\%3Axri\%2Fsid\%3Aprimo}  	 	 		ERP Systems  		2017. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
