{"id":41397,"date":"2020-02-10T20:24:56","date_gmt":"2020-02-10T17:24:56","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/chto-takoe-sap"},"modified":"2020-02-10T20:24:56","modified_gmt":"2020-02-10T17:24:56","slug":"chto-takoe-sap","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/chto-takoe-sap","title":{"rendered":"\u00c7far\u00eb \u00ebsht\u00eb SAP?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"\u00c7far\u00eb
\n
\n\u00c7far\u00eb \u00ebsht\u00eb SAP? Dhe si ka mund\u00ebsi q\u00eb ajo kushton 163 miliard\u00eb dollar\u00eb?<\/p>\n

\u00c7do vit, kompanit\u00eb shpenzojn\u00eb 41 miliard\u00eb dollar\u00eb p\u00ebr softuer p\u00ebr planifikimin e burimeve t\u00eb korporatave<\/b>, i njohur me akronimin ERP<\/b>. Sot, pothuajse \u00e7do biznes i madh ka implementuar nj\u00eb sistem ERP t\u00eb k\u00ebtij apo atij lloji. Por shumica e kompanive t\u00eb vogla zakonisht nuk blejn\u00eb sisteme ERP, dhe shumica e zhvilluesve ndoshta nuk i kan\u00eb par\u00eb ato n\u00eb pun\u00eb. Pra, p\u00ebr ata prej nesh q\u00eb nuk kan\u00eb p\u00ebrdorur ERP, lind pyetja... \u00e7far\u00eb \u00ebsht\u00eb e ve\u00e7anta? Si arrin nj\u00eb kompani si SAP t\u00eb shes\u00eb ERP me 25 miliard\u00eb dollar\u00eb n\u00eb vit? <\/p>\n

Dhe si ndodhi q\u00eb 77% e tregtis\u00eb globale<\/a><\/noindex>, p\u00ebrfshir\u00eb 78% t\u00eb furnizimeve t\u00eb ushqimores, kalon p\u00ebrmes programeve t\u00eb SAP?
\n<\/a><\/noindex>
\nERP \u00ebsht\u00eb vendi ku kompanit\u00eb ruajn\u00eb t\u00eb dh\u00ebnat kryesore operacionale. Po flasim p\u00ebr parashikimet e shitjeve, porosit\u00eb e blerjes, inventaret, si dhe proceset q\u00eb aktivizohen mbi baz\u00ebn e k\u00ebtyre t\u00eb dh\u00ebnave (p.sh., pagesat p\u00ebr furnizuesit kur b\u00ebhen porosit\u00eb). N\u00eb nj\u00eb kuptim, ERP \u00ebsht\u00eb \"truri\" i kompanis\u00eb - ajo ruan t\u00eb gjitha t\u00eb dh\u00ebnat e r\u00ebnd\u00ebsishme dhe t\u00eb gjitha veprimet q\u00eb iniciohen nga k\u00ebto t\u00eb dh\u00ebna n\u00eb proceset e pun\u00ebs.<\/p>\n

Por m\u00eb par\u00eb se t\u00eb pushtoj\u00eb plot\u00ebsisht bot\u00ebn moderne t\u00eb biznesit, si p\u00ebrfundimisht erdhi ky softuer? Historia e ERP fillon me pun\u00ebn serioze t\u00eb automatizimit t\u00eb aktiviteteve zyrtare n\u00eb vitet 1960. M\u00eb par\u00eb, n\u00eb vitet 40 dhe 50, u fokusua kryesisht n\u00eb automatizimin e pun\u00ebve mekanike t\u00eb \"pun\u00ebtor\u00ebve me bluz\u00eb t\u00eb kalt\u00ebr\" \u2014 kujtoni General Motors, e cila krijoi departamentin e saj t\u00eb automatizimit n\u00eb vitin 1947. Nd\u00ebrsa automatizimi i pun\u00ebve t\u00eb \"pun\u00ebtor\u00ebve me bluz\u00eb t\u00eb bardh\u00eb\" ( shpesh me ndihm\u00ebn e kompjuter\u00ebve!) filloi n\u00eb vitet 60.<\/p>\n

Automatizimi i viteve '60: shfaqja e kompjuter\u00ebve<\/h1>\n

\nProceset e para biznesore q\u00eb u automatizuan me ndihm\u00ebn e kompjuter\u00ebve ishin llogaritja e pagave dhe l\u00ebshimi i faturave. M\u00eb par\u00eb, armatat e t\u00eb pun\u00ebsuarve zyrtar\u00eb llogaritnin manualisht or\u00ebt e pun\u00ebs s\u00eb punonj\u00ebsve n\u00eb libra llogarish, i shum\u00ebzonin me norm\u00ebn orare, pastaj llogaritnin manualisht taksat, zbritjet p\u00ebr p\u00ebrfitimet e tjera dhe k\u00ebshtu me radh\u00eb... gjith\u00eb k\u00ebt\u00eb vet\u00ebm p\u00ebr t\u00eb llogaritur pag\u00ebn p\u00ebr nj\u00eb muaj! Ky proces pun\u00eb-intensiv dhe p\u00ebrs\u00ebrit\u00ebs ishte i ndjesh\u00ebm ndaj gabimeve njer\u00ebzore, p\u00ebrve\u00e7 se ishte perfekt p\u00ebr automatizimin e kompjuter\u00ebve.<\/p>\n

N\u00eb vitet '60, shum\u00eb kompani filluan t\u00eb p\u00ebrdorin kompjuter\u00eb IBM p\u00ebr automatizimin e llogaritjes s\u00eb pagave dhe l\u00ebshimit t\u00eb faturave. P\u00ebrpunimi i t\u00eb dh\u00ebnave \u00ebsht\u00eb nj\u00eb term i vjetruar, nga i cili ka mbetur vet\u00ebm kompania Automatic Data Processing, Inc<\/a><\/noindex>. N\u00eb vend t\u00eb tij, sot flasim p\u00ebr \"IT\". N\u00eb at\u00eb koh\u00eb, industria e zhvillimit t\u00eb softuerit ende nuk ishte formuar, prandaj n\u00eb departamentet e IT shpesh merrnin analist\u00eb dhe i m\u00ebsonin t\u00eb programonin n\u00eb vend. Fakulteti i par\u00eb n\u00eb SHBA p\u00ebr Informatik\u00ebn u hap nga Universiteti Purdue n\u00eb vitin 1962, nd\u00ebrsa diplomimi i par\u00eb n\u00eb k\u00ebt\u00eb fush\u00eb ndodhi disa vjet m\u00eb von\u00eb.<\/p>\n

\"\u00c7far\u00eb
\n
\nShkrimi i programeve p\u00ebr automatizimin\/p\u00ebrpunimin e t\u00eb dh\u00ebnave n\u00eb vitet '60 ishte nj\u00eb sfid\u00eb e madhe p\u00ebr shkak t\u00eb kufizimeve t\u00eb memories. Nuk kishte asgj\u00eb si gjuh\u00ebt e nivelit t\u00eb lart\u00eb, as sisteme operimi t\u00eb standardizuara, as kompjuter\u00eb personal\u00eb - vet\u00ebm mainframe t\u00eb m\u00ebdha dhe t\u00eb shtrenjta me nj\u00eb kapacitet t\u00eb vog\u00ebl memorie, ku programet ekzekutoheshin n\u00eb role magnetik! Programuesit shpesh punonin me kompjuterin nat\u00ebn, kur ai ishte i lir\u00eb. P\u00ebr kompani si General Motors ishte e zakonshme t\u00eb shkruanin sisteme operimi t\u00eb veta p\u00ebr t\u00eb marr\u00eb maksimumin nga mainframe-\u00ebt e tyre.<\/p>\n

Sot ne ekzekutojm\u00eb software aplikativ n\u00eb disa sisteme operimi standarde, por kjo nuk ndodhi para viteve 1990. epok\u00ebn mesjetare t\u00eb mainframe<\/a><\/noindex> 90% e t\u00eb gjith\u00eb software-it shkruhej me porosi, dhe vet\u00ebm 10% shitej n\u00eb form\u00eb t\u00eb gatshme. <\/p>\n

Kjo situat\u00eb kishte nj\u00eb ndikim t\u00eb thell\u00eb n\u00eb m\u00ebnyr\u00ebn se si kompanit\u00eb zhvillonin teknologjit\u00eb e tyre. Disa supozonin se e ardhmja do t\u00eb ishte me pajisje t\u00eb standardizuara me nj\u00eb sistem operativ dhe nj\u00eb gjuh\u00eb programimi t\u00eb pandryshueshme, si\u00e7 \u00ebsht\u00eb sistemi SABRE<\/a><\/noindex> p\u00ebr industrin\u00eb e aviacionit (e cila p\u00ebrdoret ende sot!) Shumica e kompanive vazhduan t\u00eb zhvillojn\u00eb softuerin e tyre krejt\u00ebsisht t\u00eb izoluar, shpesh duke shpikur bi\u00e7iklet\u00ebn.<\/p>\n

Lindja e softuerit standard: programi i zgjeruesh\u00ebm SAP<\/h1>\n

\nN\u00eb vitin 1972, pes\u00eb inxhinier\u00eb u larguan nga IBM p\u00ebr t\u00eb n\u00ebnshkruar nj\u00eb kontrat\u00eb p\u00ebr furnizimin e softuerit me nj\u00eb kompani t\u00eb madhe kimike t\u00eb quajtur ICI. Ata themeluan nj\u00eb kompani t\u00eb re t\u00eb quajtur SAP (Analiz\u00eb e Sistemit dhe Zhvillimi i Programeve). Ashtu si shumica e zhvilluesve t\u00eb softuerit n\u00eb at\u00eb koh\u00eb, ata kryesisht merren me konsulenc\u00eb. Punonj\u00ebsit e SAP shkonin n\u00eb zyrat e klient\u00ebve dhe zhvillonin softuerin n\u00eb kompjuter\u00ebt e tyre, kryesisht p\u00ebr menaxhimin e logjistik\u00ebs.<\/p>\n

\"\u00c7far\u00eb
\n
\nBiznesi po shkonte mir\u00eb: SAP p\u00ebrfundoi vitin e par\u00eb me t\u00eb ardhura prej 620,000 markash, q\u00eb \u00ebsht\u00eb pak m\u00eb shum\u00eb se 1 milion dollar\u00eb n\u00eb dollar\u00ebt e sot\u00ebm. Shpejt filluan t\u00eb shisnin softuerin e tyre edhe p\u00ebr klient\u00eb t\u00eb tjer\u00eb, duke e portuar at\u00eb n\u00eb sisteme t\u00eb ndryshme operative kur ishte e nevojshme. Gjat\u00eb kat\u00ebr viteve t\u00eb ardhshme kishin m\u00eb shum\u00eb se 40 klient\u00eb, t\u00eb ardhurat u rrit\u00ebn gjasht\u00ebfish dhe numri i punonj\u00ebsve u rrit nga 9 n\u00eb 25. Ndoshta, kjo \u00ebsht\u00eb pak larg kurb\u00ebs s\u00eb rritjes T2D3<\/a><\/noindex>, por e ardhmja e SAP dukej optimiste.<\/p>\n

Softueri i SAP ishte i ve\u00e7ant\u00eb p\u00ebr disa arsye. N\u00eb at\u00eb koh\u00eb, shumica e programeve punonin gjat\u00eb nat\u00ebs dhe printonin rezultatet n\u00eb shirit\u00eb letre, t\u00eb cilat i kontrollonit m\u00ebngjesin tjet\u00ebr. N\u00eb vend t\u00eb k\u00ebsaj, programet e SAP punonin n\u00eb koh\u00eb reale, duke shfaqur rezultatet jo n\u00eb let\u00ebr, por n\u00eb monitor\u00eb (t\u00eb cil\u00ebt n\u00eb at\u00eb koh\u00eb kushtonin rreth 30,000 dollar\u00eb).<\/p>\n

Porosia kryesore \u00ebsht\u00eb se softueri SAP \u00ebsht\u00eb krijuar q\u00eb n\u00eb fillim p\u00ebr t'u zgjeruar. N\u00eb kontrat\u00ebn fillestare me ICI, SAP nuk krijoi softuerin nga e para, si\u00e7 ndodhte zakonisht n\u00eb at\u00eb koh\u00eb, por shkroi kod mbi nj\u00eb projekt t\u00eb m\u00ebparsh\u00ebm. Kur SAP l\u00ebshoi softuerin e saj p\u00ebr llogaritjen financiare n\u00eb vitin 1974, ajo planifikoi q\u00eb n\u00eb t\u00eb ardhmen t\u00eb shkruante module t\u00eb tjera shtes\u00eb mbi t\u00eb dhe t'i shiste ato. Kjo zgjerueshm\u00ebri u b\u00eb nj\u00eb karakteristik\u00eb p\u00ebrcaktuese p\u00ebr SAP. N\u00eb at\u00eb koh\u00eb, nd\u00ebrveprimi midis konteksteve t\u00eb klient\u00ebve konsiderohej nj\u00eb inovacion radikal. Programet shkruheshin nga e para p\u00ebr \u00e7do klient.<\/p>\n

R\u00ebnd\u00ebsia e integrimit<\/h1>\n

\nKur SAP paraqiti modul\u00ebn e saj t\u00eb dyt\u00eb t\u00eb prodhimit p\u00ebrve\u00e7 modulit t\u00eb par\u00eb financiar, k\u00ebto dy module ishin n\u00eb gjendje t\u00eb nd\u00ebrvepronin leht\u00ebsisht me nj\u00ebri-tjetrin, pasi kishin nj\u00eb baz\u00eb t\u00eb p\u00ebrbashk\u00ebt t\u00eb t\u00eb dh\u00ebnave. Kjo integrim e b\u00ebri kombinimin e moduleve shum\u00eb m\u00eb t\u00eb \u00e7muar se thjesht dy programa t\u00eb ndara.<\/p>\n

P\u00ebr shkak se softuari automatizoi procese t\u00eb caktuara biznesi, influenca e tij n\u00eb mas\u00eb t\u00eb madhe varej nga aksesi n\u00eb t\u00eb dh\u00ebna. T\u00eb dh\u00ebnat e porosive p\u00ebr blerje ruhen n\u00eb modulin e shitjeve, t\u00eb dh\u00ebnat p\u00ebr stoqet e produkteve ruhen n\u00eb modulin e magazin\u00ebs, etj. Dhe p\u00ebr shkak se k\u00ebto sisteme nuk nd\u00ebrveprojn\u00eb, ato duhet t\u00eb sinkronizohen rregullisht, dometh\u00ebn\u00eb nj\u00eb punonj\u00ebs kopjonte manualisht t\u00eb dh\u00ebnat nga nj\u00eb baz\u00eb n\u00eb nj\u00eb tjet\u00ebr.<\/p>\n

Softueri i integruar zgjidh k\u00ebt\u00eb problem, duke leht\u00ebsuar komunikimin midis sistemeve t\u00eb kompanis\u00eb dhe duke mund\u00ebsuar lloje t\u00eb reja automatizimi. Ky lloj integrimi - midis proceseve t\u00eb ndryshme biznesi, si dhe burimeve t\u00eb t\u00eb dh\u00ebnave - \u00ebsht\u00eb nj\u00eb karakteristik\u00eb ky\u00e7e e sistemeve ERP. Kjo \u00ebsht\u00eb b\u00ebr\u00eb ve\u00e7an\u00ebrisht e r\u00ebnd\u00ebsishme me zhvillimin e harduerit, i cili hapi mund\u00ebsi t\u00eb reja p\u00ebr automatizim - dhe sistemet ERP kan\u00eb lul\u00ebzuar.<\/p>\n

Shpejt\u00ebsia e aksesit n\u00eb informacion n\u00eb softuerin e integruar lejon kompanit\u00eb t\u00eb ndryshojn\u00eb plot\u00ebsisht modelet e tyre biznesore<\/a><\/noindex>. Kompania Compaq me ndihm\u00ebn e ERP implementoi nj\u00eb model t\u00eb ri \"prodhimi sipas porosis\u00eb\" (do t\u00eb thot\u00eb montimi i kompjuterit vet\u00ebm pas marrjes eksplicite t\u00eb porosis\u00eb). Ky model kursen para, duke reduktuar stoqet, duke u mb\u00ebshtetur n\u00eb qarkullimin e shpejt\u00eb - pik\u00ebrisht kjo \u00ebsht\u00eb ajo q\u00eb ndihmon ERP e mir\u00eb. Kur IBM ndoqi t\u00eb nj\u00ebjtin shembull, ajo e reduktoi koh\u00ebn e dor\u00ebzimit t\u00eb komponent\u00ebve nga 22 n\u00eb tre dit\u00eb.<\/p>\n

Si duket n\u00eb t\u00eb v\u00ebrtet\u00eb ERP<\/h1>\n

\nFjal\u00ebt \"softuer korporativ\" nuk asociohen me nj\u00eb nd\u00ebrfaqe t\u00eb modshme dhe t\u00eb rehatshme, dhe SAP nuk b\u00ebn p\u00ebrjashtim. Instalimi baz\u00eb i SAP p\u00ebrmban 20,000 tabela t\u00eb DB, 3,000 nga t\u00eb cilat jan\u00eb tabela konfiguracioni. N\u00eb k\u00ebto tabela ka rreth 8,000 zgjidhje konfigurimi q\u00eb duhet t\u00eb merren para fillimit t\u00eb programit. Kjo \u00ebsht\u00eb arsyeja pse Specialisti i Konfigurimit SAP<\/a><\/noindex>\u00a0\u00ebsht\u00eb nj\u00eb profesion i v\u00ebrtet\u00eb!<\/p>\n

Megjith\u00ebse konfigurimi \u00ebsht\u00eb i komplikuar, software SAP ERP siguron nj\u00eb vler\u00eb thelb\u00ebsore - nj\u00eb integrim t\u00eb gjer\u00eb midis disa proceseve t\u00eb biznesit. Ky integrim krijon mij\u00ebra raste p\u00ebrdorimi n\u00eb organizat\u00eb. SAP organizon k\u00ebto raste p\u00ebrdorimi n\u00eb \"transaksione\", t\u00eb cilat p\u00ebrfaq\u00ebsojn\u00eb veprimet e biznesit. Disa shembuj transaksionesh p\u00ebrfshijn\u00eb \"krijimin e porosis\u00eb\" dhe \"shfaqjen e klientit\". K\u00ebto transaksione jan\u00eb organizuar n\u00eb nj\u00eb format katalogu t\u00eb nd\u00ebrlikuar. K\u00ebshtu, p\u00ebr t\u00eb gjetur transaksionin \"Krijo porosi p\u00ebr shitje\", ju shkoni n\u00eb katalogun \"Logjistika\", pastaj \"Shitjet\", pastaj \"Porosit\u00eb\", dhe atje do t\u00eb gjeni transaksionin aktual.<\/p>\n

\"\u00c7far\u00eb
\n
\nN\u00ebse e quajm\u00eb ERP \"shfletues transaksionesh\", do t\u00eb ishte nj\u00eb p\u00ebrshkrim mjaft i sakt\u00eb. Ai \u00ebsht\u00eb shum\u00eb i ngjash\u00ebm me nj\u00eb shfletues, ka nj\u00eb buton \"Kthimi\", butona p\u00ebr zmadhim dhe nj\u00eb fush\u00eb teksti p\u00ebr kodet \u201cTCodes\u201d, ekuivalent i vij\u00ebs adres\u00ebs n\u00eb shfletues. SAP mb\u00ebshtet m\u00eb shum\u00eb se 16,000 lloje transaksionesh<\/a><\/noindex>, prandaj, navigimi n\u00ebpemtree-n\u00eb e transaksioneve mund t\u00eb jet\u00eb i komplikuar pa k\u00ebto kode.<\/p>\n

Megjith\u00ebse ka nj\u00eb num\u00ebr t\u00eb pabesuesh\u00ebm konfiguracionesh dhe transaksionesh t\u00eb disponueshme, kompanit\u00eb p\u00ebrballen ende me raste unike p\u00ebrdorimi dhe duhet t\u00eb p\u00ebrshtatin veprimet e tyre me kujdes. P\u00ebr t\u00eb p\u00ebrpunuar k\u00ebto procese pune unike, SAP ka nj\u00eb mjedis programimi t\u00eb integruar. K\u00ebt\u00eb e b\u00ebjn\u00eb secila pjes\u00eb:<\/p>\n

T\u00eb dh\u00ebnat<\/h3>\n

\nN\u00eb nd\u00ebrfaqen e SAP, zhvilluesit mund t\u00eb krijojn\u00eb tabela t\u00eb veta DB. K\u00ebto jan\u00eb tabela relacionale si bazat e zakonshme SQL: kolona t\u00eb tipave t\u00eb ndrysh\u00ebm, \u00e7el\u00ebsa t\u00eb jasht\u00ebm, kufizime vlerash, si dhe leje p\u00ebr lexim\/shkruar.<\/p>\n

Logjika<\/h3>\n

\nSAP ka zhvilluar nj\u00eb gjuh\u00eb t\u00eb quajtur ABAP (Advanced Business Application Programming, fillimisht Allgemeiner Berichts-Aufbereitungs-Prozessor, n\u00eb gjermanisht \"procesori i p\u00ebrgjithsh\u00ebm i p\u00ebrgatitjes s\u00eb raporteve\"). Ajo u jep zhvilluesve mund\u00ebsin\u00eb t\u00eb ekzekutojn\u00eb logjik\u00eb t\u00eb personalizuar biznesi n\u00eb p\u00ebrgjigje t\u00eb ngjarjeve t\u00eb caktuara ose sipas nj\u00eb programi. ABAP \u00ebsht\u00eb nj\u00eb gjuh\u00eb me sintaks\u00eb t\u00eb pasur, k\u00ebtu ka rreth tri her\u00eb m\u00eb shum\u00eb fjal\u00eb ky\u00e7e se n\u00eb JavaScript (shih implementimin e loj\u00ebs 2048 n\u00eb gjuh\u00ebn ABAP<\/a><\/noindex>). Kur shkruani programin tuaj (n\u00eb SAP ka nj\u00eb redaktues t\u00eb integruar p\u00ebr programim), e publikoni at\u00eb si nj\u00eb transaksion t\u00eb ve\u00e7ant\u00eb, s\u00eb bashku me kodin unik TCode. Mund t\u00eb p\u00ebrshtatni sjelljen ekzistuese me nj\u00eb sistem t\u00eb gjer\u00eb hijesh, t\u00eb quajtur 'shtesa biznesi' (add-ins), ku programi p\u00ebrshtatet p\u00ebr t\u00eb ekzekutuar gjat\u00eb ekzekutimit t\u00eb nj\u00eb transaksioni t\u00eb caktuar \u2014 nj\u00ebsoj si trigger\u2019-at SQL.<\/p>\n

UI<\/h3>\n

\nSAP gjithashtu ofron nj\u00eb nd\u00ebrtues p\u00ebr krijimin e UI. Ai mb\u00ebshtet drag-and-drop dhe vjen me funksione t\u00eb arrira, si formular\u00ebt e gjeneruar mbi baz\u00ebn e tabelave t\u00eb DB. Megjithat\u00eb, \u00ebsht\u00eb mjaft e v\u00ebshtir\u00eb p\u00ebr t'u p\u00ebrdorur. Pjesa ime e preferuar e nd\u00ebrtuesit \u00ebsht\u00eb vizatimi i kolumnave t\u00eb tabel\u00ebs:<\/p>\n

\"\u00c7far\u00eb
\n<\/p>\n

V\u00ebshtir\u00ebsi n\u00eb implementimin e ERP<\/h1>\n

\nERP kushton shtrenjt\u00eb. Nj\u00eb kompani e madhe shum\u00ebkomb\u00ebshe mund t\u00eb shpenzoj\u00eb nga 100 milion deri n\u00eb 500 milion dollar\u00eb p\u00ebr implementimin, duke p\u00ebrfshir\u00eb 30 milion dollar\u00eb p\u00ebr pagesa licencash, 200 milion dollar\u00eb p\u00ebr sh\u00ebrbime k\u00ebshillimi, dhe pjesa tjet\u00ebr p\u00ebr pajisje, trajnimin e menaxher\u00ebve dhe punonj\u00ebsve. Implementimi i plot\u00eb zgjat nga kat\u00ebr deri n\u00eb gjasht\u00eb vjet. CEO i nj\u00eb kompanie t\u00eb madhe kimike<\/a><\/noindex> tha: \u00abAvantazhi konkurrues n\u00eb industrin\u00eb do t\u00eb fitoj\u00eb firma q\u00eb do t\u00eb jet\u00eb n\u00eb gjendje t\u00eb realizoj\u00eb m\u00eb mir\u00eb dhe m\u00eb lir\u00eb pun\u00ebt p\u00ebr zbatimin e SAP\u00bb.<\/p>\n

Dhe \u00e7\u00ebshtja nuk \u00ebsht\u00eb vet\u00ebm te parat\u00eb. Zbatimi i ERP-s\u00eb \u00ebsht\u00eb nj\u00eb nd\u00ebrmarrje e rrezikshme, dhe rezultatet ndryshojn\u00eb shum\u00eb. Nj\u00eb nga rastet e sukseshme \u00ebsht\u00eb konsideruar zbatimi i ERP-s\u00eb n\u00eb Cisco, i cili zgjati 9 muaj dhe kushtoi $15 milion. P\u00ebr krahasim, implementimi n\u00eb korporat\u00ebn Dow Chemical kushtoi $1 miliard dhe zgjati 8 vjet. US Navy harxhoi $1 miliard n\u00eb kat\u00ebr projekte t\u00eb ndryshme ERP, por t\u00eb gjitha d\u00ebshtuan.<\/a><\/noindex>. E gjith\u00eb 65% e drejtuesve<\/a><\/noindex> mendojn\u00eb se zbatimi i sistemeve ERP ka nj\u00eb \u2018shans t\u00eb moderuar p\u00ebr t\u00eb d\u00ebmtuar biznesin\u2019. Kjo nuk \u00ebsht\u00eb zakonisht nj\u00eb vler\u00ebsim q\u00eb d\u00ebgjohet p\u00ebr softuerin!<\/p>\n

Natyr\u00ebn e integruar t\u00eb ERP-s\u00eb do t\u00eb thot\u00eb se p\u00ebr zbatimin e tij k\u00ebrkohen p\u00ebrpjekje t\u00eb gjith\u00eb kompanis\u00eb. Dhe pasi kompanit\u00eb p\u00ebrfitojn\u00eb vet\u00ebm pas zbatimit t\u00eb plot\u00eb, kjo \u00ebsht\u00eb ve\u00e7an\u00ebrisht e rrezikshme! Zbatimi i ERP-s\u00eb nuk \u00ebsht\u00eb thjesht nj\u00eb vendim blerjeje: kjo \u00ebsht\u00eb nj\u00eb angazhim p\u00ebr t\u00eb ndryshuar metodat e menaxhimit t\u00eb operacioneve. Instalimi i softuerit \u00ebsht\u00eb i leht\u00eb, ri-\u00e7aktojm\u00eb procesin e pun\u00ebs s\u00eb gjith\u00eb kompanis\u00eb \u00ebsht\u00eb ajo ku ndodhet puna kryesore.<\/i> \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f, \u044d\u0442\u043e \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0440\u0438\u0441\u043a\u043e\u0432\u0430\u043d\u043d\u043e! \u0412\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 ERP\u00a0\u2014 \u043d\u0435 \u043f\u0440\u043e\u0441\u0442\u043e \u0440\u0435\u0448\u0435\u043d\u0438\u0435 \u043e \u043f\u043e\u043a\u0443\u043f\u043a\u0435: \u044d\u0442\u043e \u043e\u0431\u044f\u0437\u0430\u0442\u0435\u043b\u044c\u0441\u0442\u0432\u043e \u0438\u0437\u043c\u0435\u043d\u0438\u0442\u044c \u0441\u0432\u043e\u0438 \u043c\u0435\u0442\u043e\u0434\u044b \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u044f\u043c\u0438. \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u043d\u043e\u0433\u043e \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f\u00a0\u2014 \u044d\u0442\u043e \u043b\u0435\u0433\u043a\u043e, \u043f\u0435\u0440\u0435\u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0440\u0430\u0431\u043e\u0447\u0435\u0433\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u0430 \u0432\u0441\u0435\u0439 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438\u00a0\u2014 \u0432\u043e\u0442 \u0433\u0434\u0435 \u043e\u0441\u043d\u043e\u0432\u043d\u0430\u044f \u0440\u0430\u0431\u043e\u0442\u0430.<\/p>\n

P\u00ebr t\u00eb implementuar nj\u00eb sistem ERP, klient\u00ebt shpesh angazhojn\u00eb nj\u00eb kompani konsulenc\u00eb si Accenture dhe paguajn\u00eb miliona dollar\u00eb p\u00ebr t\u00eb punuar me departamente t\u00eb ve\u00e7anta t\u00eb biznesit. Analist\u00ebt p\u00ebrcaktojn\u00eb se si t\u00eb integrohet ERP n\u00eb proceset e kompanis\u00eb. Dhe sa her\u00eb q\u00eb integrimi fillon, kompania duhet t\u00eb niset me trajnimin e t\u00eb gjith\u00eb punonj\u00ebsve se si t\u00eb p\u00ebrdorin sistemin. Gartner rekomandon<\/a><\/noindex> t\u00eb rezervoni 17% t\u00eb buxhetit vet\u00ebm p\u00ebr trajnimin!<\/p>\n

Pavar\u00ebsisht t\u00eb gjitha v\u00ebshtir\u00ebsive, shumica e kompanive nga lista Fortune 500 implementuan sisteme ERP deri n\u00eb vitin 1998: procesi u p\u00ebrshpejtua nga frika e Y2K. Tregu i ERP vazhdon t\u00eb rritet edhe sot kalon $40 miliard\u00eb<\/a><\/noindex>. Kjo \u00ebsht\u00eb nj\u00eb nga segmentet m\u00eb t\u00eb m\u00ebdha n\u00eb industrin\u00eb globale t\u00eb software-it.<\/p>\n

Industria moderne e ERP<\/h1>\n

\nAktoret m\u00eb t\u00eb m\u00ebdha jan\u00eb Oracle dhe SAP. Edhe pse t\u00eb dyja jan\u00eb lider\u00eb t\u00eb tregut, produktet e tyre ERP jan\u00eb befasuesh\u00ebm t\u00eb ndryshme. Produkti i SAP \u00ebsht\u00eb nd\u00ebrtuar kryesisht brenda kompanis\u00eb, nd\u00ebrsa Oracle ka bler\u00eb me agresivitet konkurrent\u00ebt, si PeopleSoft dhe NetSuite.<\/p>\n

Oracle dhe SAP jan\u00eb aq dominuese, sa q\u00eb madje Microsoft p\u00ebrdor SAP<\/a><\/noindex> n\u00eb vend t\u00eb produktit t\u00eb tij ERP Microsoft Dynamics.<\/p>\n

Duke sektor\u00ebve t\u00eb shumt\u00eb kan\u00eb nevoja specifike p\u00ebr ERP, Oracle dhe SAP ofrojn\u00eb konfigurime t\u00eb gatshme p\u00ebr shum\u00eb industri, si\u00e7 jan\u00eb ajo ushqimore, automobilistike dhe kimike, si dhe konfigurime vertikale, si proceset e organizat\u00ebs s\u00eb shitjeve. Megjithat\u00eb, gjithmon\u00eb ka vend p\u00ebr lojtar\u00eb t\u00eb ni\u0161\u00ebs, t\u00eb cil\u00ebt zakonisht jan\u00eb t\u00eb orientuar drejt nj\u00eb vertikale t\u00eb caktuar:<\/p>\n