{"id":95021,"date":"2020-09-24T19:42:23","date_gmt":"2020-09-24T17:42:23","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/ekstrakcziya-dannyh-iz-sap-hcm-v-non-sap-hranilishha-dannyh"},"modified":"2020-09-24T19:42:23","modified_gmt":"2020-09-24T17:42:23","slug":"ekstrakcziya-dannyh-iz-sap-hcm-v-non-sap-hranilishha-dannyh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/ekstrakcziya-dannyh-iz-sap-hcm-v-non-sap-hranilishha-dannyh","title":{"rendered":"Extrac\u021bia datelor din SAP HCM \u00een stoc\u0103ri de date non-SAP","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dup\u0103 cum se \u0219tie, compania SAP ofer\u0103 o gam\u0103 complet\u0103 de software, at\u00e2t pentru gestionarea datelor de tranzac\u021bie, c\u00e2t \u0219i pentru procesarea acestor date \u00een sistemele de analiz\u0103 \u0219i raportare. \u00cen special, platforma SAP Business Warehouse (SAP BW) reprezint\u0103 un instrument pentru stocarea \u0219i analiza datelor, av\u00e2nd capacit\u0103\u021bi tehnice extinse. Cu toate avantajele sale obiective, sistemul SAP BW are un dezavantaj semnificativ: costurile ridicate de stocare \u0219i procesare a datelor, mai ales \u00een utilizarea SAP BW pe Hana \u00een cloud. <\/p>\n

\u0218i ce s-ar \u00eent\u00e2mpla dac\u0103 am \u00eencepe s\u0103 utiliz\u0103m un produs non-SAP \u0219i ideal, OpenSource, ca stocare? Noi, la X5 Retail Group, am ales GreenPlum. Acest lucru ajut\u0103 cu siguran\u021b\u0103 la reducerea costurilor, \u00eens\u0103 apar imediat \u00eentreb\u0103ri pe care utilizarea SAP BW le rezolv\u0103 practic de la sine.<\/p>\n

\"Extrac\u021bia
\n<\/a><\/noindex>
\n\u00cen special, cum putem extrage datele din sistemele surs\u0103, care, \u00een cea mai mare parte, sunt solu\u021bii SAP?<\/p>\n

Proiectul \u201eHR-metrice\u201d a fost primul \u00een care a trebuit s\u0103 abord\u0103m aceast\u0103 problem\u0103. Scopul nostru a fost s\u0103 cre\u0103m un depozit de date HR \u0219i s\u0103 construim raport\u0103ri analitice pe tema managementului resurselor umane. Principala surs\u0103 de date este sistemul de tranzac\u021bii SAP HCM, \u00een care sunt gestionate toate activit\u0103\u021bile legate de personal, organiza\u021bie \u0219i salarii. <\/p>\n

Extrac\u021bia datelor<\/h3>\n

\n\u00cen SAP BW pentru sistemele SAP exist\u0103 extractori standard de date. Ace\u0219ti extractori pot colecta automat datele necesare, monitoriz\u00e2ndu-le integritatea \u0219i determin\u00e2nd delfele schimb\u0103rilor. De exemplu, un standard de surs\u0103 de date pentru atributele angajatului 0EMPLOYEE_ATTR:<\/p>\n

\"Extrac\u021bia
\n
\nRezultatul extrac\u021biei de date din acesta pentru un singur angajat:<\/p>\n

\"Extrac\u021bia
\n
\nDac\u0103 este necesar, un astfel de extractor poate fi modificat pentru cerin\u021bele proprii sau poate fi creat un extractor personalizat. <\/p>\n

Prima idee a fost posibilitatea reutiliz\u0103rii acestora. Din p\u0103cate, s-a dovedit a fi o sarcin\u0103 imposibil\u0103. Mare parte din logic\u0103 este implementat\u0103 pe partea SAP BW \u0219i nu a fost posibil s\u0103 separ\u0103m f\u0103r\u0103 durere extractorul de surs\u0103 de SAP BW. <\/p>\n

A devenit evident c\u0103 va fi necesar\u0103 dezvoltarea unui mecanism propriu de extragere a datelor din sistemele SAP. <\/p>\n

Structura de stocare a datelor \u00een SAP HCM<\/h3>\n

\nPentru a \u00een\u021belege cerin\u021bele pentru un astfel de mecanism, trebuie mai \u00eent\u00e2i s\u0103 definim ce date ne vor fi necesare.<\/p>\n

Cele mai multe date din SAP HCM sunt stocate \u00een tabele SQL plate. Pe baza acestor date, aplica\u021biile SAP vizualizeaz\u0103 utilizatorului structurile organiza\u021bionale, angaja\u021bii \u0219i alte informa\u021bii HR. De exemplu, iat\u0103 cum arat\u0103 structura organiza\u021bional\u0103 \u00een SAP HCM:<\/p>\n

\"Extrac\u021bia
\n
\nFizic, acest arbore este stocat \u00een dou\u0103 tabele \u2013 \u00een hrp1000 obiectele \u0219i \u00een hrp1001 rela\u021biile dintre aceste obiecte. <\/p>\n

Obiectele \u201eDepartament 1\u201d \u0219i \u201eConducere 1\u201d:<\/p>\n

\"Extrac\u021bia
\n
\nRela\u021bia dintre obiecte:<\/p>\n

\"Extrac\u021bia
\n
\nAt\u00e2t tipurile de obiecte, c\u00e2t \u0219i tipurile de rela\u021bii dintre acestea pot fi extrem de variate. Exist\u0103 at\u00e2t rela\u021bii standard \u00eentre obiecte, c\u00e2t \u0219i personalizate pentru nevoile specifice. De exemplu, rela\u021bia standard B012 \u00eentre unitatea organiza\u021bional\u0103 \u0219i func\u021bia de personal indic\u0103 managerul departamentului.<\/p>\n

Afi\u0219area managerului \u00een SAP:<\/p>\n

\"Extrac\u021bia
\n
\nStocarea \u00een tabel\u0103 Baza de date:<\/p>\n

\"Extrac\u021bia
\n
\nDatele angaja\u021bilor sunt stocate \u00een tabelele pa*. De exemplu, datele despre activit\u0103\u021bile de personal pentru un angajat sunt stocate \u00een tabela pa0000.<\/p>\n

\"Extrac\u021bia
\n
\nAm decis c\u0103 GreenPlum va prelua datele \u201ebrute\u201d, adic\u0103 va copia pur \u0219i simplu din tabelele SAP. Iar \u00een GreenPlum acestea vor fi prelucrate \u0219i transformate \u00een obiecte fizice (de exemplu, Departament sau Angajat) \u0219i metrici (de exemplu, num\u0103rul mediu de angaja\u021bi).<\/p>\n

Au fost identificate aproximativ 70 de tabele ale c\u0103ror date trebuie transmise \u00een GreenPlum. Dup\u0103 care am \u00eenceput s\u0103 lucr\u0103m la metoda de transfer al acestor date.<\/p>\n

SAP ofer\u0103 un num\u0103r considerabil de mecanisme de integrare. Dar cea mai simpl\u0103 metod\u0103 \u2013 accesul direct la baza de date este interzis din cauza restric\u021biilor de licen\u021biere. Astfel, toate fluxurile de integrare trebuie implementate la nivelul server<\/a> aplica\u021biilor.
\nUrm\u0103toarea problem\u0103 a fost absen\u021ba datelor despre \u00eenregistr\u0103rile \u0219terse din baza de date SAP. Atunci c\u00e2nd o linie este \u0219tears\u0103 din baza de date, aceasta este eliminat\u0103 fizic. Adic\u0103, generarea unei delta a modific\u0103rilor \u00een func\u021bie de momentul modific\u0103rii nu era posibil\u0103.<\/p>\n

Desigur, \u00een SAP HCM exist\u0103 mecanisme pentru \u00eenregistrarea modific\u0103rilor datelor. De exemplu, pentru transmiterea ulterioar\u0103 \u00een sistemele primitoare, exist\u0103 puncte de modificare (change pointer), care \u00eenregistreaz\u0103 orice modificare \u0219i pe baza c\u0103rora se formeaz\u0103 Idoc (obiect pentru transmiterea \u00een sisteme externe).<\/p>\n

Exemplu de modificare a infotype-ului 0302 pentru angajatul cu num\u0103rul de \u00eenregistrare 1251445:<\/p>\n

\"Extrac\u021bia
\n
\nSau \u00eenregistrarea jurnalului modific\u0103rilor de date \u00een tabela DBTABLOG.<\/p>\n

Exemplu de jurnal pentru \u0219tergerea \u00eenregistr\u0103rii cu cheia QK53216375 din tabela hrp1000:<\/p>\n

\"Extrac\u021bia
\n
\n\u00cens\u0103 aceste mecanisme nu sunt disponibile pentru toate datele necesare, iar procesarea lor la nivelul serverului de aplica\u021bii poate consuma destul de multe resurse. Prin urmare, activarea \u00een mas\u0103 a jurnaliz\u0103rii pentru toate tabelele necesare poate duce la o degradare semnificativ\u0103 a performan\u021bei sistemului. <\/p>\n

Urm\u0103toarea problem\u0103 serioas\u0103 a fost tabelele cluster. Datele privind evaluarea timpului \u0219i calculul salariului \u00een RDBMS versiunea SAP HCM sunt stocate sub form\u0103 de set de tabele logice pentru fiecare angajat pentru fiecare calcul. Aceste tabele logice sunt stocate sub form\u0103 de date binare \u00een tabela pcl2.<\/p>\n

Clusterul pentru calculul salariului:<\/p>\n

\"Extrac\u021bia
\n
\nDatele din tabelul cluster nu pot fi citite cu comenzi SQL, ci este necesar\u0103 utilizarea macrocomenzilor SAP HCM sau modulelor func\u021bionale speciale. Prin urmare, viteza de citire a acestor tabele va fi destul de mic\u0103. Pe de alt\u0103 parte, \u00een aceste clustere sunt stocate date care sunt necesare doar o dat\u0103 pe lun\u0103 \u2013 calculul final al salariului \u0219i evaluarea timpului. Astfel, viteza \u00een acest caz nu este at\u00e2t de critic\u0103. <\/p>\n

Evalu\u00e2nd op\u021biunile pentru generarea delta-ului de modificare a datelor, s-a decis, de asemenea, s\u0103 se examineze op\u021biunea cu export complet. Op\u021biunea de a transfera zilnic gigaocte de date neschimbate \u00eentre sisteme nu poate p\u0103rea pl\u0103cut\u0103. Cu toate acestea, are \u0219i o serie de avantaje \u2013 nu este necesar\u0103 implementarea delta-ului pe partea surs\u0103, precum \u0219i implementarea integr\u0103rii acestui delta pe partea receptorului. Prin urmare, costurile \u0219i termenele de implementare scad, iar fiabilitatea integr\u0103rii cre\u0219te. A fost determinat c\u0103 aproape toate modific\u0103rile \u00een SAP HR au loc \u00een orizontul de trei luni p\u00e2n\u0103 la data curent\u0103. Astfel, s-a decis s\u0103 ne oprim la exportul zilnic complet al datelor din SAP HR pentru N luni \u00eenainte de data curent\u0103 \u0219i la exportul complet lunar. Parametrul N depinde de tabela specific\u0103
\n \u0219i variaz\u0103 de la 1 la 15.<\/p>\n

Pentru extragerea datelor a fost propus urm\u0103torul plan:<\/p>\n

\"Extrac\u021bia
\n
\nSistemul extern formeaz\u0103 o solicitare \u0219i o trimite c\u0103tre SAP HCM, unde aceast\u0103 solicitare este verificat\u0103 pentru completitudinea datelor \u0219i pentru permisiunile de acces la tabele. \u00cen cazul unei verific\u0103ri reu\u0219ite, \u00een SAP HCM ruleaz\u0103 un program care colecteaz\u0103 datele necesare \u0219i le transmite \u00een solu\u021bia de integrare Fuse. Fuse determin\u0103 topicul necesar \u00een Kafka \u0219i transmite datele acolo. Apoi, datele din Kafka sunt transmise \u00een Stage Area GP.<\/p>\n

\u00cen aceast\u0103 lan\u021b de procese, ne intereseaz\u0103 problema extragerii datelor din SAP HCM. S\u0103 ne oprim mai \u00een detaliu asupra acestui subiect. <\/p>\n

Schema de interac\u021biune SAP HCM-FUSE.<\/p>\n

\"Extrac\u021bia
\n
\nSistemul extern determin\u0103 timpul ultimei solicit\u0103ri reu\u0219ite c\u0103tre SAP.
\nProcesul poate fi ini\u021biat de un temporizator sau de un alt eveniment, inclusiv un timeout pentru a\u0219teptarea r\u0103spunsului cu date de la SAP \u0219i ini\u021bierea unei noi solicit\u0103ri. Dup\u0103 aceea, formeaz\u0103 o solicitare de tip delta \u0219i o trimite c\u0103tre SAP.<\/p>\n

Datele solicit\u0103rii sunt transmise \u00een corp \u00een format json.
\nMetoda http: POST.
\nExemplu de cerere:<\/p>\n

\"Extrac\u021bia
\n
\nServiciul SAP efectueaz\u0103 un control al solicit\u0103rii pentru completitudine, conformitate cu structura curent\u0103 SAP, \u0219i verifica existen\u021ba permisiunii de acces la tabelul solicitat. <\/p>\n

\u00cen cazul unor erori, serviciul returneaz\u0103 un r\u0103spuns cu codul \u0219i descrierea corespunz\u0103toare. \u00cen cazul unui control reu\u0219it, acesta creeaz\u0103 un proces \u00een fundal pentru generarea selec\u021biei, genera \u0219i returna sincronizat un id unic al sesiunii. <\/p>\n

Sistemul extern, \u00een cazul unei erori, o \u00eenregistreaz\u0103 \u00een jurnal. \u00cen cazul unui r\u0103spuns reu\u0219it, transmite id-ul sesiunii \u0219i numele tabelului pentru care a fost efectuat\u0103 solicitarea.<\/p>\n

Sistemul extern \u00eenregistreaz\u0103 sesiunea curent\u0103 ca fiind deschis\u0103. Dac\u0103 exist\u0103 alte sesiuni pentru acest tabel, acestea sunt \u00eenchise cu \u00eenregistrarea unui avertisment \u00een jurnal.<\/p>\n

Sarcina de fundal SAP formeaz\u0103 un cursor pe baza unor parametrii specifica\u021bi \u0219i un pachet de date de dimensiune specificat\u0103. Dimensiunea pachetului este num\u0103rul maxim de \u00eenregistr\u0103ri pe care procesul le cite\u0219te din baza de date. \u00cen mod implicit, se accept\u0103 ca fiind 2000. Dac\u0103 \u00een selec\u021bia bazei de date exist\u0103 mai multe \u00eenregistr\u0103ri dec\u00e2t dimensiunea pachetului utilizat, dup\u0103 transmiterea primului pachet se formeaz\u0103 urm\u0103torul bloc cu offset-ul corespunz\u0103tor \u0219i num\u0103rul pachetului incrementat. Numerele sunt incrementate cu 1 \u0219i trimise strict \u00een ordine. <\/p>\n

Apoi, SAP trimite pachetul c\u0103tre serviciul web al sistemului extern. Acesta din urm\u0103 efectueaz\u0103 verific\u0103ri asupra pachetului recep\u021bionat. \u00cen sistem trebuie s\u0103 fie \u00eenregistrat\u0103 o sesiune cu ID-ul primit \u0219i aceasta trebuie s\u0103 se afle \u00een stare deschis\u0103. Dac\u0103 num\u0103rul pachetului > 1, \u00een sistem trebuie s\u0103 fie \u00eenregistrat\u0103 primirea cu succes a pachetului anterior (package_id-1).<\/p>\n

\u00cen cazul unui control reu\u0219it, sistemul extern analizeaz\u0103 \u0219i salveaz\u0103 datele din tabel.<\/p>\n

\u00cen plus, dac\u0103 pachetul con\u021bine flag-ul final \u0219i serializarea a avut loc cu succes, se trimite o notificare modulului de integrare despre finalizarea reu\u0219it\u0103 a proces\u0103rii sesiunii, iar modulul actualizeaz\u0103 starea sesiunii.<\/p>\n

\u00cen cazul unei erori la verific\u0103ri\/analiz\u0103, eroarea este \u00eenregistrat\u0103, iar pachetele pentru aceast\u0103 sesiune vor fi respinse de sistemul extern.<\/p>\n

De asemenea, \u00een cazul invers, c\u00e2nd sistemul extern returneaz\u0103 o eroare, aceasta este \u00eenregistrat\u0103 \u0219i transmiterea pachetelor este oprit\u0103.<\/p>\n

Pentru solicitarea datelor din partea SAP HCM a fost realizat un serviciu de integrare. Serviciul este implementat pe cadrul ICF (SAP Internet Communication Framework - help.sap.com\/viewer\/6da7259a6c4b1014b7d5e759cc76fd22\/7.01.22\/en-US\/488d6e0ea6ed72d5e10000000a42189c.html<\/a><\/noindex>). Acesta permite trimiterea de solicit\u0103ri pentru date din sistemul SAP HCM pe anumite tabele. La formarea solicit\u0103rii de date, exist\u0103 posibilitatea de a defini un set specific de c\u00e2mpuri \u0219i parametrii de filtrare pentru a ob\u021bine datele necesare. Implementarea serviciului nu presupune nicio logic\u0103 de afaceri. Algoritmii de calcul al delta, parametrii cererii, verificarea integrit\u0103\u021bii etc., sunt implementa\u021bi \u00een sistemul extern.<\/p>\n

Acest mecanism permite colectarea \u0219i transmiterea tuturor datelor necesare \u00een c\u00e2teva ore. Aceast\u0103 vitez\u0103 se afl\u0103 la limita acceptabilit\u0103\u021bii, de aceea aceast\u0103 solu\u021bie este considerat\u0103 temporar\u0103 \u0219i a \u00eenchis necesitatea unui instrument de extrac\u021bie \u00een cadrul proiectului.
\n\u00cen imaginea \u021bint\u0103 pentru solu\u021bia de extrac\u021bie a datelor sunt analizate op\u021biuni de utilizare a sistemelor CDC, precum Oracle Golden Gate, sau instrumente ETL cum ar fi SAP DS.
\n
Sursa: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041a\u0430\u043a \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e, \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u044f SAP \u043f\u0440\u0435\u0434\u043b\u0430\u0433\u0430\u0435\u0442 \u043f\u043e\u043b\u043d\u044b\u0439 \u0441\u043f\u0435\u043a\u0442\u0440 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u043d\u043e\u0433\u043e \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f, \u043a\u0430\u043a \u0434\u043b\u044f \u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u043e\u043d\u043d\u044b\u0445 \u0434\u0430\u043d\u043d\u044b\u0445, \u0442\u0430\u043a \u0438 \u0434\u043b\u044f \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u044d\u0442\u0438\u0445 \u0434\u0430\u043d\u043d\u044b\u0445 \u0432 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u0445 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0438 \u043e\u0442\u0447\u0435\u0442\u043d\u043e\u0441\u0442\u0438. \u0412 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 SAP Business Warehouse (SAP BW) \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u043e\u0431\u043e\u0439 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u0430\u0440\u0438\u0439 \u0434\u043b\u044f \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0434\u0430\u043d\u043d\u044b\u0445, \u043e\u0431\u043b\u0430\u0434\u0430\u044e\u0449\u0438\u0439 \u0448\u0438\u0440\u043e\u043a\u0438\u043c\u0438 \u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u043c\u0438 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044f\u043c\u0438. \u041f\u0440\u0438 \u0432\u0441\u0435\u0445 \u0441\u0432\u043e\u0438\u0445 \u043e\u0431\u044a\u0435\u043a\u0442\u0438\u0432\u043d\u044b\u0445 \u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0430\u0445 \u0441\u0438\u0441\u0442\u0435\u043c\u0430 SAP BW \u043e\u0431\u043b\u0430\u0434\u0430\u0435\u0442 \u043e\u0434\u043d\u0438\u043c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":95022,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-95021","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Extrac\u021bia datelor din SAP HCM \u00een depozite de date non-SAP | ProHoster","description":"Dup\u0103 cum se \u0219tie, compania SAP ofer\u0103 o gam\u0103 complet\u0103 de software pentru gestionarea at\u00e2t a datelor tranzac\u021bionale, c\u00e2t \u0219i a prelucr\u0103rii acestor date \u00een sistemele de analiz\u0103 \u0219i raportare.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/ekstrakcziya-dannyh-iz-sap-hcm-v-non-sap-hranilishha-dannyh","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u042d\u043a\u0441\u0442\u0440\u0430\u043a\u0446\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445 \u0438\u0437 SAP HCM \u0432 non-SAP \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430 \u0434\u0430\u043d\u043d\u044b\u0445 | ProHoster","og:description":"\u041a\u0430\u043a \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e, \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u044f SAP \u043f\u0440\u0435\u0434\u043b\u0430\u0433\u0430\u0435\u0442 \u043f\u043e\u043b\u043d\u044b\u0439 \u0441\u043f\u0435\u043a\u0442\u0440 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u043d\u043e\u0433\u043e \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f, \u043a\u0430\u043a \u0434\u043b\u044f \u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u043e\u043d\u043d\u044b\u0445 \u0434\u0430\u043d\u043d\u044b\u0445, \u0442\u0430\u043a \u0438 \u0434\u043b\u044f \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u044d\u0442\u0438\u0445 \u0434\u0430\u043d\u043d\u044b\u0445 \u0432 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u0445 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0438 \u043e\u0442\u0447\u0435\u0442\u043d\u043e\u0441\u0442\u0438.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/ekstrakcziya-dannyh-iz-sap-hcm-v-non-sap-hranilishha-dannyh","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-09-24T17:42:23+00:00","article:modified_time":"2020-09-24T17:42:23+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"95021","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 11:13:39","updated":"2026-02-22 15:29:41","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/95021","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=95021"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/95021\/revisions"}],"predecessor-version":[{"id":162188,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/95021\/revisions\/162188"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/95022"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=95021"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=95021"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=95021"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}