{"id":101113,"date":"2026-10-17T13:00:38","date_gmt":"2026-10-17T13:00:38","guid":{"rendered":"https:\/\/skyplanner.ai\/?page_id=101113"},"modified":"2026-10-17T13:00:38","modified_gmt":"2026-10-17T13:00:38","slug":"ghid-de-integrare","status":"publish","type":"page","link":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/","title":{"rendered":"Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei"},"content":{"rendered":"\n<div class=\"wp-block-group sp-industry-page sp-industry sp-page sp-erp-page\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<section class=\"wp-block-group fx-hero\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-hero__grid\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-hero__copy sp-min0\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-eyebrow ind-crumbs\"><span><a href=\"\/ro\/integrari\/\">Integr\u0103ri<\/a> \/ <a href=\"\/ro\/integrari\/erp\/\">ERP<\/a> \/ SAP Business One<\/span><\/p>\n\n\n<h1 class=\"wp-block-heading fx-hero__title\">Ghid de integrare SAP Business One <span class=\"hl\">cu SkyPlanner APS pentru programarea produc\u021biei<\/span><\/h1>\n\n\n<div class=\"wp-block-group fx-hero__sub ind-hero__intro\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p>Acest ghid le arat\u0103 partenerilor SAP Business One \u0219i echipelor IT cum s\u0103 conecteze B1 la SkyPlanner APS. Explic\u0103 ce API-uri s\u0103 folosi\u021bi, ce obiecte se transfer\u0103 \u00een fiecare direc\u021bie \u0219i unde apar probleme \u00een proiectele B1. SkyPlanner se integreaz\u0103 bidirec\u021bional cu SAP Business One prin Service Layer:<\/p>\n\n\n<ul class=\"wp-block-list fxv-deliver__bul\">\n\n<li>\u00cen SkyPlanner se import\u0103 comenzi de produc\u021bie, etape ale fluxului tehnologic, resurse, articole \u0219i comenzi de achizi\u021bie.<\/li>\n\n\n<li>Datele planificate de \u00eencepere \u0219i de finalizare sunt retransmise c\u0103tre B1 \u0219i \u00eenscrise \u00een comenzile de produc\u021bie.<\/li>\n\n\n<li>Pontajele operatorilor sunt \u00eenregistrate ca Receipt and Issue for Production.<\/li>\n\n\n<li>Webhook-urile SkyPlanner transmit modific\u0103rile programului pe m\u0103sur\u0103 ce apar.<\/li>\n\n<\/ul>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-buttons fx-hero__actions is-layout-flex wp-block-buttons-is-layout-flex\">\n\n<div class=\"wp-block-button sp-btn sp-btn--green sp-btn--lg\"><a class=\"wp-block-button__link wp-element-button\" href=\"\/ro\/proba\/\">\u00cencepe\u021bi testarea gratuit\u0103<\/a><\/div>\n\n\n<div class=\"wp-block-button sp-btn sp-btn--outline sp-btn--lg\"><a class=\"wp-block-button__link wp-element-button\" href=\"\/ro\/contact-vanzari\/\">Programa\u021bi o demonstra\u021bie<\/a><\/div>\n\n<\/div>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group fx-hero__media sp-min0\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<figure class=\"fx-shot\"><div class=\"fx-shot__bar\" aria-hidden=\"true\"><i><\/i><i><\/i><i><\/i><span>skyplanner.ai \u00b7 Programarea produc\u021biei<\/span><\/div><img fetchpriority=\"high\" decoding=\"async\" loading=\"eager\" width=\"1024\" height=\"685\" src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/features-v2\/20-d7d44cbc-5430-4f97-99f5-fca4632862ef.png\" alt=\"Diagrama Gantt din SkyPlanner APS, cu lucr\u0103ri programate pe centre de lucru \u0219i o list\u0103 de comenzi dedesubt.\"><\/figure>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section ind-sec--intro\" id=\"overview\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group ind-prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p>SAP Business One p\u0103streaz\u0103 articolele, BOM-urile, comenzile de produc\u021bie, stocurile \u0219i datele financiare, iar modulul dumneavoastr\u0103 de produc\u021bie r\u0103m\u00e2ne neschimbat. Echipa SkyPlanner configureaz\u0103 integrarea cu obiectele standard B1 \u00een etapa de implementare \u0219i asigur\u0103 asisten\u021b\u0103 dup\u0103 punerea \u00een func\u021biune. Etapele fluxului tehnologic, grupurile de resurse, c\u00e2mpurile definite de utilizator \u0219i extensiile difer\u0103 de la o baz\u0103 de date de companie la alta. Configurarea stabile\u0219te coresponden\u021bele pentru aceste particularit\u0103\u021bi.<\/p>\n\n\n<p><a href=\"\/ro\/customers\/laboratory-allied\/\">Laboratory &amp; Allied<\/a> folose\u0219te SkyPlanner cu SAP Business One pe HANA. Pentru argumentele economice, consulta\u021bi <a href=\"\/ro\/integrari\/erp\/sap-business-one\/\">pagina despre programarea produc\u021biei cu SAP Business One<\/a>.<\/p>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section ind-sec--alt\" id=\"sap-business-one-integration-options\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-head ind-head--prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<h2 class=\"wp-block-heading\">Op\u021biuni de integrare cu SAP Business One<\/h2>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group ind-prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p>SAP Business One ofer\u0103 trei interfe\u021be de integrare. Pentru o aplica\u021bie de programare \u00een cloud, op\u021biunea implicit\u0103 este Service Layer.<\/p>\n\n\n<figure class=\"wp-block-table ind-table ind-table--wide\"><table><thead><tr><th>Op\u021biune<\/th><th>Descriere<\/th><th>Utilizare pentru integrarea cu APS<\/th><\/tr><\/thead><tbody><tr><td><strong>Service Layer<\/strong><\/td><td>API REST\/OData. <code>\/b1s\/v1<\/code> folose\u0219te OData v3, iar <code>\/b1s\/v2<\/code> folose\u0219te OData v4. Func\u021bioneaz\u0103 pe versiunea SAP Business One pentru SAP HANA \u0219i, \u00eencep\u00e2nd cu 10.0 PL01, pe Microsoft SQL Server.<\/td><td>Varianta principal\u0103. Folose\u0219te HTTP \u0219i JSON \u0219i poate fi accesat\u0103 dintr-un serviciu cloud.<\/td><\/tr><tr><td><strong>DI API<\/strong><\/td><td>Bibliotec\u0103 COM pentru Windows. Comenzile de produc\u021bie sunt reprezentate de obiectul <code>ProductionOrders<\/code>, stocat \u00een tabelul OWOR (tip de obiect 202).<\/td><td>Pentru middleware existent sau instalat local. Necesit\u0103 o gazd\u0103 Windows.<\/td><\/tr><tr><td><strong>Integration Framework (B1if)<\/strong><\/td><td>Solu\u021bia middleware SAP pentru scenarii de integrare la nivel de document.<\/td><td>Util\u0103 dac\u0103 partenerul ruleaz\u0103 deja scenarii B1if.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n<h3 class=\"wp-block-heading\">Autentificare<\/h3>\n\n\n<p>Service Layer folose\u0219te autentificarea pe baz\u0103 de sesiune. Trimite\u021bi <code>POST \/b1s\/v1\/Login<\/code> cu <code>CompanyDB<\/code>, <code>UserName<\/code> \u0219i <code>Password<\/code> \u0219i primi\u021bi un cookie <code>B1SESSION<\/code> (plus un <code>ROUTEID<\/code> op\u021bional pentru configura\u021biile cu echilibrarea \u00eenc\u0103rc\u0103rii). Valoarea implicit\u0103 pentru <code>SessionTimeout<\/code> este de 30 de minute de inactivitate. Apela\u021bi explicit <code>Logout<\/code> la \u00eencheierea fiec\u0103rei sincroniz\u0103ri. Crea\u021bi un utilizator B1 dedicat integr\u0103rii, astfel \u00eenc\u00e2t fiecare modificare transmis\u0103 din SkyPlanner s\u0103 poat\u0103 fi urm\u0103rit\u0103 \u00een jurnalul de modific\u0103ri.<\/p>\n\n\n<h3 class=\"wp-block-heading\">Entit\u0103\u021bi Service Layer pentru programarea produc\u021biei<\/h3>\n\n\n<figure class=\"wp-block-table ind-table\"><table><thead><tr><th>Date<\/th><th>Entitate Service Layer<\/th><\/tr><\/thead><tbody><tr><td>Articole \u0219i date de planificare<\/td><td><code>Items<\/code><\/td><\/tr><tr><td>Liste de materiale \u0219i etape ale fluxului tehnologic<\/td><td><code>ProductTrees<\/code> (Lines, Stages)<\/td><\/tr><tr><td>Utilaje, for\u021b\u0103 de munc\u0103, alte resurse<\/td><td><code>Resources<\/code>, <code>ResourceGroups<\/code><\/td><\/tr><tr><td>Comenzi de produc\u021bie<\/td><td><code>ProductionOrders<\/code> (Lines, Stages)<\/td><\/tr><tr><td>Stocuri pe depozite<\/td><td>Date de stoc din <code>Items<\/code>, <code>Warehouses<\/code><\/td><\/tr><tr><td>Comenzi de achizi\u021bie deschise \u0219i date de livrare<\/td><td><code>PurchaseOrders<\/code> (DocumentLines: cantitate r\u0103mas\u0103 de livrat, <code>ShipDate<\/code>)<\/td><\/tr><tr><td>Recep\u021bii de m\u0103rfuri aferente comenzilor de achizi\u021bie<\/td><td><code>PurchaseDeliveryNotes<\/code> (Goods Receipt PO, tip de obiect 20)<\/td><\/tr><tr><td>Issue for Production<\/td><td><code>InventoryGenExits<\/code><\/td><\/tr><tr><td>Receipt from Production<\/td><td><code>InventoryGenEntries<\/code><\/td><\/tr><tr><td>Configurarea webhook-urilor<\/td><td><code>EventSubscriptions<\/code>, <code>EventNotifications<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n<p>Dimensiunea implicit\u0103 a paginii este de 20 de \u00eenregistr\u0103ri. M\u0103ri\u021bi-o prin antetul <code>Prefer: odata.maxpagesize<\/code> (sau prin <code>PageSize<\/code> \u00een <code>b1s.conf<\/code>) \u0219i urma\u021bi <code>odata.nextLink<\/code>. Folosi\u021bi <code>$expand<\/code> pentru a prelua liniile \u0219i etapele comenzilor de produc\u021bie \u00eentr-un singur apel, iar pentru actualiz\u0103rile masive \u00een sistemul surs\u0103, grupa\u021bi cererile \u00een loturi.<\/p>\n\n\n<h3 class=\"wp-block-heading\">Evenimente \u0219i webhookuri<\/h3>\n\n\n<p>\u00cencep\u00e2nd cu SAP Business One 10.0 FP 2602, Service Layer accept\u0103 webhook-uri. Acestea sunt dezactivate implicit. Le activa\u021bi pentru fiecare companie prin <code>CompanyService_UpdateAdminInfo<\/code> (<code>EnableWebhook = tYES<\/code>). Apoi trimite\u021bi <code>POST EventSubscriptions<\/code> cu trei componente:<\/p>\n\n\n<ul class=\"wp-block-list\">\n\n<li>un <code>WebhookURL<\/code><\/li>\n\n\n<li>un <code>AuthenticationType<\/code>: None, Basic, HMAC sau OAuth, cu HMAC ca valoare implicit\u0103<\/li>\n\n\n<li>un <code>EventCollection<\/code> cu obiecte de business \u0219i tipuri de tranzac\u021bii<\/li>\n\n<\/ul>\n\n\n<p><code>WebhookURL<\/code> trebuie s\u0103 foloseasc\u0103 HTTPS \u0219i un certificat care corespunde numelui gazdei. <code>EventSubscriptionsService_GetEventCatalog<\/code> listeaz\u0103 evenimentele la care v\u0103 pute\u021bi abona. Serviciul Webhook Messenger Service trebuie s\u0103 fie pornit.<\/p>\n\n\n<p>Pe versiunile mai vechi, interoga\u021bi periodic sistemul (vede\u021bi mai jos problema legat\u0103 de <code>UpdateDate<\/code>). <code>SBO_SP_TransactionNotification<\/code> este un mecanism de validare la nivelul bazei de date, nu un canal de transmitere a evenimentelor.<\/p>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section\" id=\"data-mapping-sap-business-one-to-skyplanner\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-head ind-head--prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<h2 class=\"wp-block-heading\">Maparea datelor din SAP Business One \u00een SkyPlanner<\/h2>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group ind-prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<figure class=\"wp-block-table ind-table ind-table--wide\"><table><thead><tr><th>SAP Business One (Service Layer)<\/th><th>Obiect SkyPlanner<\/th><th>Direc\u021bie<\/th><th>Frecven\u021b\u0103<\/th><\/tr><\/thead><tbody><tr><td><code>Items<\/code> (articole fabricate, Procurement Method)<\/td><td>Produse<\/td><td>B1 \u2192 SkyPlanner<\/td><td>\u00cenc\u0103rcare ini\u021bial\u0103, apoi la intervale programate<\/td><\/tr><tr><td>Lines din <code>ProductTrees<\/code> (linii de articole)<\/td><td>Materialele produselor<\/td><td>B1 \u2192 SkyPlanner<\/td><td>\u00cenc\u0103rcare ini\u021bial\u0103, apoi la modificare<\/td><\/tr><tr><td>Stages \u0219i linii de resurse din <code>ProductTrees<\/code><\/td><td>Etape de proces \u0219i timpi de execu\u021bie<\/td><td>B1 \u2192 SkyPlanner<\/td><td>\u00cenc\u0103rcare ini\u021bial\u0103, apoi la modificare<\/td><\/tr><tr><td><code>Resources<\/code> (Machine, Labor, Other)<\/td><td>Centre de lucru \u0219i personal<\/td><td>B1 \u2192 SkyPlanner<\/td><td>\u00cenc\u0103rcare ini\u021bial\u0103, modific\u0103ri rare<\/td><\/tr><tr><td><code>ResourceGroups<\/code><\/td><td>Grupuri de centre de lucru<\/td><td>B1 \u2192 SkyPlanner<\/td><td>\u00cenc\u0103rcare ini\u021bial\u0103<\/td><\/tr><tr><td><code>ProductionOrders<\/code> (Planned, Released)<\/td><td>Comenzi \u0219i opera\u021bii<\/td><td>B1 \u2192 SkyPlanner<\/td><td>Webhook (FP 2602+) sau interogare la fiecare c\u00e2teva minute<\/td><\/tr><tr><td>Stages din <code>ProductionOrders<\/code><\/td><td>Etapele opera\u021biilor \u0219i ordinea lor<\/td><td>B1 \u2192 SkyPlanner<\/td><td>Odat\u0103 cu comanda<\/td><\/tr><tr><td>Stocul din <code>Items<\/code> pe <code>Warehouses<\/code><\/td><td>Stocuri de materiale<\/td><td>B1 \u2192 SkyPlanner<\/td><td>La intervale programate, de exemplu orar<\/td><\/tr><tr><td>Linii deschise din <code>PurchaseOrders<\/code> (tip de obiect 22), cu data de livrare<\/td><td>Comenzi de achizi\u021bie \/ materiale de primit, cu data estimat\u0103 de livrare<\/td><td>B1 \u2192 SkyPlanner<\/td><td>La intervale programate, de exemplu orar<\/td><\/tr><tr><td>Linii din <code>PurchaseDeliveryNotes<\/code> (Goods Receipt PO) cu <code>BaseType<\/code> 22<\/td><td>Cantitatea recep\u021bionat\u0103 pe linia comenzii de achizi\u021bie, stoc actualizat<\/td><td>B1 \u2192 SkyPlanner<\/td><td>La intervale programate, de exemplu orar<\/td><\/tr><tr><td>\u00cenceput \u0219i sf\u00e2r\u0219it programate<\/td><td><code>PATCH ProductionOrders({DocEntry})<\/code>: <code>StartDate<\/code>, <code>DueDate<\/code>, plus <code>StartDate<\/code> \u0219i <code>EndDate<\/code> pe linia de resurs\u0103<\/td><td>SkyPlanner \u2192 B1<\/td><td>Webhook SkyPlanner la modificarea programului<\/td><\/tr><tr><td>Cantit\u0103\u021bi \u00eenregistrate<\/td><td><code>InventoryGenEntries<\/code> (Receipt from Production)<\/td><td>SkyPlanner \u2192 B1<\/td><td>La confirmare sau \u00een loturi<\/td><\/tr><tr><td>Ore \u0219i consum de materiale \u00eenregistrate<\/td><td><code>InventoryGenExits<\/code> (Issue for Production)<\/td><td>SkyPlanner \u2192 B1<\/td><td>La confirmare sau \u00een loturi<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n<p>Calendarele de schimburi, personalul \u0219i absen\u021bele sunt gestionate \u00een SkyPlanner. Valorile capacit\u0103\u021bii zilnice din B1 nu sunt incluse \u00een transfer (vede\u021bi prima capcan\u0103 de mai jos).<\/p>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section ind-sec--alt\" id=\"integration-patterns\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-head ind-head--prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<h2 class=\"wp-block-heading\">Modele de integrare<\/h2>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group ind-prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p><strong>1. \u00cenc\u0103rcarea ini\u021bial\u0103 a nomenclatoarelor.<\/strong> Prelua\u021bi <code>Resources<\/code>, <code>ResourceGroups<\/code>, <code>Items<\/code> cu Procurement Method setat la Make \u0219i structurile <code>ProductTrees<\/code> aferente, cu etapele lor. Asocia\u021bi fiecare resurs\u0103 de tip utilaj unui centru de lucru SkyPlanner. Verifica\u021bi lista \u00eempreun\u0103 cu planificatorii \u00eenainte de prima sincronizare a comenzilor.<\/p>\n\n\n<p><strong>2. Sincronizarea comenzilor.<\/strong> Citi\u021bi <code>ProductionOrders<\/code> cu starea Planned \u0219i Released, folosind <code>$expand<\/code> pentru linii \u0219i etape. Comenzile de produc\u021bie B1 con\u021bin etapele fluxului tehnologic preluate din BOM, iar planificatorii pot modifica o comand\u0103 dup\u0103 creare. Folosi\u021bi etapele comenzii, nu pe cele din BOM. O comand\u0103 de produc\u021bie realizeaz\u0103 un singur produs, deci pentru un produs cu structur\u0103 pe mai multe niveluri se folose\u0219te c\u00e2te o comand\u0103 de produc\u021bie pentru fiecare nivel. Lega\u021bi comenzile \u00eentre ele, astfel \u00eenc\u00e2t SkyPlanner s\u0103 programeze subansamblele \u00eenaintea produsului de nivel superior.<\/p>\n\n\n<p>Sincroniza\u021bi \u0219i liniile deschise din <code>PurchaseOrders<\/code>, cu cantitatea r\u0103mas\u0103 de livrat \u0219i data de livrare, folosind endpoint-urile SkyPlanner pentru comenzi de achizi\u021bie. SkyPlanner consider\u0103 materialul comandat disponibil la data de livrare a comenzii de achizi\u021bie. \u00cen B1, stocul se modific\u0103 la \u00eenregistrarea unei recep\u021bii Goods Receipt PO (<code>PurchaseDeliveryNotes<\/code>). Integrarea cite\u0219te aceste recep\u021bii, marcheaz\u0103 cantitatea recep\u021bionat\u0103 ca livrat\u0103 \u00een SkyPlanner \u0219i p\u0103streaz\u0103 deschis\u0103 cantitatea r\u0103mas\u0103. Recep\u021biile par\u021biale sunt luate \u00een calcul o singur\u0103 dat\u0103, iar verific\u0103rile de disponibilitate a materialelor acoper\u0103 at\u00e2t stocul, c\u00e2t \u0219i aprovizion\u0103rile \u00een curs.<\/p>\n\n\n<p><strong>3. Transmiterea programului c\u0103tre B1.<\/strong> Webhook-urile SkyPlanner se declan\u0219eaz\u0103 la modificarea programului. Integrarea trimite <code>PATCH \/b1s\/v1\/ProductionOrders({DocEntry})<\/code> cu noile valori <code>StartDate<\/code> \u0219i <code>DueDate<\/code>, precum \u0219i cu <code>StartDate<\/code> \u0219i <code>EndDate<\/code> pe liniile de resurse ale comenzii (<code>ProductionOrderLines<\/code>), astfel \u00eenc\u00e2t fiecare etap\u0103 s\u0103 aib\u0103 intervalul programat. Corpul cererii con\u021bine doar c\u00e2mpurile gestionate de SkyPlanner, iar mai multe comenzi sunt trimise \u00eentr-o singur\u0103 cerere <code>$batch<\/code>. Utilizatorii B1 v\u0103d apoi datele programate pe comanda de produc\u021bie \u0219i \u00een fereastra Resource Capacity. \u00cen instal\u0103rile \u00een care Service Layer nu este disponibil, aceea\u0219i actualizare se face dintr-un serviciu local prin obiectul <code>ProductionOrders<\/code> din DI API (<code>GetByKey<\/code>, setarea datelor, <code>Update<\/code>).<\/p>\n\n\n<p><strong>4. Confirm\u0103ri din atelier.<\/strong> Operatorii \u00eenregistreaz\u0103 activitatea \u00een SkyPlanner prin <a href=\"\/ro\/functionalitati\/\">Mobile Confirmations sau Production Timer<\/a>. Fiecare \u00eenregistrare de timp genereaz\u0103 un <code>POST \/b1s\/v1\/InventoryGenEntries<\/code> pentru cantitatea finalizat\u0103 (Receipt from Production) \u0219i un <code>POST \/b1s\/v1\/InventoryGenExits<\/code> pentru componente \u0219i timpul de utilizare a resurselor (Issue for Production).<\/p>\n\n\n<p>Fiecare linie de document are <code>BaseType<\/code> 202 \u0219i <code>BaseEntry<\/code> setat la valoarea <code>DocEntry<\/code> a comenzii de produc\u021bie; liniile de ie\u0219ire includ \u0219i <code>BaseLine<\/code> al liniei de component\u0103 sau de resurs\u0103. Cantit\u0103\u021bile par\u021biale sunt contabilizate pe m\u0103sur\u0103 ce sunt \u00eenregistrate, numerele de lot \u0219i de serie sunt ad\u0103ugate pentru articolele urm\u0103rite astfel, iar comanda trebuie s\u0103 aib\u0103 starea Released.<\/p>\n\n\n<p>ID-ul pontajului din SkyPlanner este stocat \u00een documentul B1, astfel \u00eenc\u00e2t un eveniment retrimis nu genereaz\u0103 niciodat\u0103 o \u00eenregistrare dubl\u0103. Dac\u0103 o \u00eenregistrare e\u0219ueaz\u0103, se re\u00eencearc\u0103 \u0219i se raporteaz\u0103 eroarea, \u00een loc s\u0103 fie abandonat\u0103.<\/p>\n\n\n<p><strong>5. Reguli privind sistemul responsabil \u0219i rezolvarea conflictelor.<\/strong> Stabili\u021bi-le \u00eenainte de a scrie cod:<\/p>\n\n\n<ul class=\"wp-block-list\">\n\n<li>B1 gestioneaz\u0103 articolele, BOM-urile, cantit\u0103\u021bile, depozitele \u0219i crearea comenzilor.<\/li>\n\n\n<li>SkyPlanner gestioneaz\u0103 succesiunea opera\u021biilor, momentele de \u00eencepere \u0219i de finalizare \u0219i alocarea la centrele de lucru.<\/li>\n\n\n<li>Dac\u0103 datele unei comenzi sunt modificate \u00een ambele sisteme, urm\u0103toarea rulare SkyPlanner are prioritate, cu excep\u021bia cazului \u00een care planificatorii au blocat opera\u021bia \u00een SkyPlanner.<\/li>\n\n\n<li>Comenzile cu starea Closed sau Cancelled \u00een B1 duc la eliminarea opera\u021biei din program.<\/li>\n\n<\/ul>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section\" id=\"what-the-project-contains\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-head ind-head--prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<h2 class=\"wp-block-heading\">Ce include proiectul<\/h2>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group ind-prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p>Implementarea se finalizeaz\u0103 \u00een mod normal \u00een c\u00e2teva s\u0103pt\u0103m\u00e2ni de la \u00eenceperea etapei de configurare ini\u021bial\u0103. \u00cenainte de aceasta, pute\u021bi folosi propriile date \u00een perioada de testare gratuit\u0103 de 30 de zile. Exporta\u021bi articolele, resursele \u0219i comenzile de produc\u021bie deschise din B1 \u00een CSV sau Excel \u0219i \u00eenc\u0103rca\u021bi-le cu func\u021bia de import de date din SkyPlanner. Planificatorii v\u0103d un program real \u00eenainte s\u0103 se scrie codul de integrare.<\/p>\n\n\n<p>Un proiect SAP Business One obi\u0219nuit include:<\/p>\n\n\n<ul class=\"wp-block-list\">\n\n<li><strong>Maparea nomenclatoarelor.<\/strong> Resursele \u0219i grupurile de resurse din B1 sunt asociate centrelor de lucru, etapele fluxului tehnologic sunt asociate etapelor de proces, iar articolele de tip Make sunt asociate produselor.<\/li>\n\n\n<li><strong>\u00cenc\u0103rcarea ini\u021bial\u0103.<\/strong> Articole, Product Trees cu etape \u0219i pozi\u021bii de articole, resurse \u0219i stocuri pe depozit.<\/li>\n\n\n<li><strong>Sincronizarea comenzilor de produc\u021bie \u0219i de achizi\u021bie.<\/strong> Comenzi de produc\u021bie deschise, cu pozi\u021bii \u0219i etape, precum \u0219i comenzi de achizi\u021bie deschise, cu datele de livrare aferente.<\/li>\n\n\n<li><strong>Transmiterea programului c\u0103tre B1.<\/strong> Datele de \u00eenceput \u0219i termenele programate sunt transmise c\u0103tre <code>ProductionOrders<\/code>.<\/li>\n\n\n<li><strong>Confirm\u0103ri din produc\u021bie.<\/strong> Receipt and Issue for Production sunt \u00eenregistrate pe baza pontajelor din SkyPlanner.<\/li>\n\n\n<li><strong>Testarea \u00een paralel cu planul actual.<\/strong> Planificatorii compar\u0103 programul SkyPlanner cu modul \u00een care planific\u0103 \u00een prezent.<\/li>\n\n\n<li><strong>Punerea \u00een func\u021biune.<\/strong> Programul SkyPlanner devine planul de referin\u021b\u0103.<\/li>\n\n<\/ul>\n\n\n<p>Resursele \u0219i etapele fluxului tehnologic bine definite \u00een B1 reduc timpul necesar map\u0103rii. La Laboratory &amp; Allied, integrarea a fost una dintre cele mai simple p\u0103r\u021bi ale proiectului. Echipa IT intern\u0103 a realizat integrarea cu SAP Business One pe HANA \u00een mare parte pe cont propriu. Echipa SkyPlanner a intervenit \u00een cazurile cele mai complexe, cum ar fi produsele care se combin\u0103 pe parcursul unor procese cu mai multe etape.<\/p>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section ind-sec--alt\" id=\"sap-business-one-pitfalls\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-head ind-head--prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<h2 class=\"wp-block-heading\">Capcane la integrarea cu SAP Business One<\/h2>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group fx-pain ind-cards\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<article class=\"wp-block-group fx-pain__card\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-pain__t\">Capacitatea zilnic\u0103 nu este un model de lucru \u00een schimburi.<\/p>\n\n\n<p class=\"fx-pain__b\">B1 stocheaz\u0103 Daily Internal Capacity \u0219i Single Run Capacity pentru fiecare resurs\u0103, pentru fiecare zi (\u201eThese capacities are defined on a daily basis,\u201d (Aceste capacit\u0103\u021bi sunt definite pe zi), conform <a href=\"https:\/\/learning.sap.com\/courses\/managing-logistics-in-sap-business-one\/working-with-resources-in-sap-business-one\">SAP Learning<\/a>). Ghidul SAP precizeaz\u0103 c\u0103 la calculul Required Days se presupune c\u0103 \u201ea single production order can be produced on a single machine\u201d (o singur\u0103 comand\u0103 de produc\u021bie poate fi executat\u0103 pe un singur utilaj) (<a href=\"https:\/\/help.sap.com\/doc\/08da4f4af99f4fc5a4fbb0249a6698a6\/9.3\/en-US\/How%20to%20Work%20with%20Resources%20and%20Production%20in%20SAP%20Business%20One.pdf\">ghidul practic SAP<\/a>). Nu copia\u021bi aceste valori pentru a le folosi drept capacitate finit\u0103. Defini\u021bi schimburile, personalul \u0219i eficien\u021ba centrelor de lucru \u00een SkyPlanner.<\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group fx-pain__card\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-pain__t\">Fluxul tehnologic este definit \u00een BOM.<\/p>\n\n\n<p class=\"fx-pain__b\">Nu exist\u0103 un nomenclator separat de fluxuri tehnologice. Liniile Route Stage din Product Tree stabilesc succesiunea, iar valorile Waiting Days se introduc manual. Citi\u021bi Stages din <code>ProductTrees<\/code> \u0219i Stages din <code>ProductionOrders<\/code> \u0219i verifica\u021bi c\u0103 fiecare linie de resurs\u0103 apar\u021bine unei etape. Comenzile f\u0103r\u0103 etape nu ofer\u0103 sistemului de programare o succesiune a opera\u021biilor.<\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group fx-pain__card\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-pain__t\">Cantit\u0103\u021bile din pozi\u021biile de resurse trebuie convertite.<\/p>\n\n\n<p class=\"fx-pain__b\">Quantity dintr-o pozi\u021bie BOM reprezint\u0103 necesarul pentru a produce cantitatea din antetul BOM, nu o singur\u0103 unitate. Additional Quantity se adaug\u0103 la timpul planificat \u201eregardless of the quantity of the parent item produced\u201d (indiferent de cantitatea produs\u0103 din articolul p\u0103rinte) (<a href=\"https:\/\/help.sap.com\/doc\/08da4f4af99f4fc5a4fbb0249a6698a6\/9.3\/en-US\/How%20to%20Work%20with%20Resources%20and%20Production%20in%20SAP%20Business%20One.pdf\">ghidul practic SAP<\/a>). Trata\u021bi aceast\u0103 valoare ca pe un timp fix pe comand\u0103, similar timpului de preg\u0103tire. \u00cemp\u0103r\u021bi\u021bi la cantitatea din antet \u00eenainte de a calcula timpii de execu\u021bie pe unitate; altfel, durata fiec\u0103rei opera\u021bii va fi eronat\u0103 cu un factor multiplicativ.<\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group fx-pain__card\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-pain__t\">Nomenclatorul de resurse este rareori lipsit de erori.<\/p>\n\n\n<p class=\"fx-pain__b\">Resursele sunt de tip Machine, Labor sau Other. Utilajele pot fi asociate mijloacelor fixe, iar manopera, angaja\u021bilor. Unei resurse i se poate asocia \u0219i un articol nestocabil pentru achizi\u021bionarea sau v\u00e2nzarea acesteia. Niciuna dintre aceste informa\u021bii nu indic\u0103 ce resurse sunt utilaje reale care pot fi programate. Corecta\u021bi grupurile de resurse \u0219i elimina\u021bi resursele duplicate \u00eenainte ca acestea s\u0103 devin\u0103 lista centrelor de lucru.<\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group fx-pain__card\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-pain__t\">Confirm\u0103rile pot e\u0219ua din cauza regulilor de gestiune a stocurilor.<\/p>\n\n\n<p class=\"fx-pain__b\">Recep\u021biile \u0219i ie\u0219irile sunt documente de stoc. Erorile obi\u0219nuite sunt confundarea <code>InventoryGenEntries<\/code> cu <code>InventoryGenExits<\/code>, lipsa numerelor de lot sau de serie pentru articolele urm\u0103rite astfel ori \u00eenregistrarea documentelor pe o comand\u0103 cu starea Planned.<\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group fx-pain__card\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-pain__t\">Sesiuni \u0219i paginare.<\/p>\n\n\n<p class=\"fx-pain__b\">O sesiune expirat\u0103 returneaz\u0103 \u201eInvalid session or session already timeout.\u201d (Sesiune nevalid\u0103 sau deja expirat\u0103.) Autentifica\u021bi-v\u0103 din nou c\u00e2nd apare aceast\u0103 eroare. Paginarea implicit\u0103 la 20 de \u00eenregistr\u0103ri trunchiaz\u0103 f\u0103r\u0103 avertisment sincroniz\u0103rile care ignor\u0103 <code>odata.nextLink<\/code>.<\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group fx-pain__card\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-pain__t\"><code>UpdateDate<\/code> nu con\u021bine ora.<\/p>\n\n\n<p class=\"fx-pain__b\">\u00cen tabelul OWOR, <code>UpdateDate<\/code> este un c\u00e2mp de tip dat\u0103; ora actualiz\u0103rii se afl\u0103 separat \u00een <code>UpdateTS<\/code>. O interogare periodic\u0103 filtrat\u0103 doar dup\u0103 <code>UpdateDate<\/code> preia la fiecare rulare toate comenzile modificate \u00een ziua respectiv\u0103. Combina\u021bi cele dou\u0103 c\u00e2mpuri sau elimina\u021bi duplicatele \u00een integrarea dumneavoastr\u0103.<\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group fx-pain__card\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"fx-pain__t\">Webhookurile garanteaz\u0103 livrarea cel pu\u021bin o dat\u0103.<\/p>\n\n\n<p class=\"fx-pain__b\">Webhook Messenger re\u00eencearc\u0103 o livrare e\u0219uat\u0103 de p\u00e2n\u0103 la cinci ori (2, 4, 8, 16 \u0219i 32 de secunde), apoi o marcheaz\u0103 ca e\u0219uat\u0103. Re\u00eencerc\u0103rile pot produce duplicate, iar ordinea este garantat\u0103 doar \u00een cadrul aceleia\u0219i companii. Implementa\u021bi procesarea idempotent\u0103 pe baza ID-ului evenimentului \u0219i p\u0103stra\u021bi o interogare de reconciliere \u00een fiecare noapte.<\/p>\n\n<\/div><\/article>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section\" id=\"the-sap-business-one-integration-who-sets-it-up\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-head ind-head--prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<h2 class=\"wp-block-heading\">Cine configureaz\u0103 integrarea cu SAP Business One<\/h2>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group ind-prose\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p>Lucr\u0103rile includ maparea etapelor fluxului tehnologic, a resurselor \u0219i a configura\u021biei B1, precum \u0219i definirea constr\u00e2ngerilor de care B1 nu \u021bine cont la programare: matricea timpilor de preg\u0103tire, sculele, num\u0103rul de operatori \u0219i resursele alternative.<\/p>\n\n\n<ol class=\"wp-block-list\">\n\n<li><strong>Echipa SkyPlanner configureaz\u0103 integrarea \u00een etapa de implementare \u0219i asigur\u0103 asisten\u021b\u0103 dup\u0103 punerea \u00een func\u021biune.<\/strong> Fiecare companie folose\u0219te B1 diferit, iar aceast\u0103 experien\u021b\u0103 este valorificat\u0103 \u00een configurare. Aceasta este varianta implicit\u0103.<\/li>\n\n\n<li><strong>Partenerul dumneavoastr\u0103 SAP Business One poate participa.<\/strong> Partenerii care cunosc baza de date a companiei, extensiile \u0219i c\u00e2mpurile definite de utilizator pot dezvolta integrarea folosind Service Layer \u0219i API-ul REST SkyPlanner (<a href=\"https:\/\/integration.skyplanner.app\/api\/swagger\">documenta\u021bia API<\/a>).<\/li>\n\n\n<li><strong>Propriii dezvoltatori pot realiza integrarea.<\/strong> API-ul REST SkyPlanner permite citirea \u0219i scrierea comenzilor, produselor, materialelor, etapelor de proces, comenzilor de achizi\u021bie \u0219i pontajelor. Folose\u0219te autentificare cu token JWT bearer \u0219i este documentat \u00een Swagger\/OpenAPI, cu documenta\u021bie public\u0103 disponibil\u0103 \u00een <a href=\"\/ro\/docs\/tutorial-de-integrare\/\">documenta\u021bia SkyPlanner<\/a>. Webhookurile transmit \u00een timp real modific\u0103rile de program \u0219i de stare. Ave\u021bi nevoie doar de o cheie API SkyPlanner pentru a \u00eencepe dezvoltarea (<a href=\"\/ro\/docs\/tutorial-de-integrare\/\">tutorial de integrare<\/a>), iar echipa SkyPlanner v\u0103 ofer\u0103 asisten\u021b\u0103 la nevoie. Aceasta este varianta aleas\u0103 de echipa IT intern\u0103 a Laboratory &amp; Allied.<\/li>\n\n<\/ol>\n\n\n<p>Valida\u021bi mai \u00eent\u00e2i programul \u00een perioada de testare gratuit\u0103 de 30 de zile, astfel \u00eenc\u00e2t integrarea s\u0103 porneasc\u0103 de la un program deja adaptat fabricii.<\/p>\n\n\n<h3 class=\"wp-block-heading\">De ce aleg echipele tehnice SkyPlanner pentru B1<\/h3>\n\n\n<ul class=\"wp-block-list\">\n\n<li><strong>Alege\u021bi SkyPlanner c\u00e2nd dori\u021bi o integrare restr\u00e2ns\u0103, bine definit\u0103.<\/strong> Se import\u0103 obiecte standard B1 (comenzi de produc\u021bie, Product Trees, Resources, Items) \u0219i se trimit \u00eenapoi date calendaristice, plus Issue and Receipt from Production. F\u0103r\u0103 modific\u0103ri ale modulului de produc\u021bie B1 \u0219i f\u0103r\u0103 migrarea datelor.<\/li>\n\n\n<li><strong>Alege\u021bi SkyPlanner c\u00e2nd proiectul trebuie s\u0103-\u0219i demonstreze valoarea de la \u00eenceput.<\/strong> Perioada de testare gratuit\u0103 de 30 de zile folose\u0219te un export CSV, cu p\u00e2n\u0103 la 20 de centre de lucru, f\u0103r\u0103 card de credit. Compania \u00ee\u0219i vede propriul program \u00eenainte de \u00eenceperea integr\u0103rii.<\/li>\n\n\n<li><strong>Alege\u021bi SkyPlanner c\u00e2nd programul trebuie s\u0103 respecte constr\u00e2ngerile reale.<\/strong> Timpii de schimbare de fabrica\u021bie, sculele comune, opera\u021biile cu mai mul\u021bi operatori, resursele alternative, stocurile \u0219i comenzile de achizi\u021bie deschise sunt toate modelate \u00een SkyPlanner. Integrarea doar furnizeaz\u0103 datele din B1.<\/li>\n\n\n<li><strong>Alege\u021bi SkyPlanner c\u00e2nd dori\u021bi un singur sistem pentru planificatori \u0219i operatori.<\/strong> Motorul Arcturus genereaz\u0103 programul \u00een c\u00e2teva secunde, iar Autopilot \u00eel reface automat c\u00e2nd apar schimb\u0103ri \u00een produc\u021bie. Operatorii \u00eenregistreaz\u0103 activitatea pe telefon sau tablet\u0103, iar integrarea transmite aceste confirm\u0103ri c\u0103tre B1, unde sunt \u00eenregistrate.<\/li>\n\n\n<li><strong>Alege\u021bi SkyPlanner c\u00e2nd costurile trebuie s\u0103 fie previzibile.<\/strong> <a href=\"\/ro\/preturi\/\">Pre\u021burile<\/a> pornesc de la 199 \u20ac pe lun\u0103, cu 5 centre de lucru incluse, facturare lunar\u0103 \u0219i posibilitatea de a renun\u021ba oric\u00e2nd. Oferta pentru integrare este stabilit\u0103 de la \u00eenceput, \u00een func\u021bie de procesul \u0219i nevoile dumneavoastr\u0103, \u00eempreun\u0103 cu abonamentul, astfel \u00eenc\u00e2t s\u0103 cunoa\u0219te\u021bi costul total \u00eenainte de a \u00eencepe.<\/li>\n\n<\/ul>\n\n\n<p>Citi\u021bi <a href=\"\/ro\/integrari\/erp\/sap-business-one\/cu-capacitate-finita\/\">explica\u021bia program\u0103rii cu capacitate finit\u0103 pentru SAP Business One<\/a> pentru a \u00een\u021belege ce lipse\u0219te din planificare \u0219i consulta\u021bi <a href=\"\/ro\/integrari\/erp\/\">pagina integr\u0103rilor ERP<\/a> pentru alte sisteme ERP.<\/p>\n\n\n<div class=\"wp-block-buttons ind-prose__actions is-layout-flex wp-block-buttons-is-layout-flex\">\n\n<div class=\"wp-block-button sp-btn sp-btn--green\"><a class=\"wp-block-button__link wp-element-button\" href=\"\/ro\/proba\/\">\u00cencepe\u021bi testarea gratuit\u0103<\/a><\/div>\n\n\n<div class=\"wp-block-button sp-btn sp-btn--outline\"><a class=\"wp-block-button__link wp-element-button\" href=\"\/ro\/contact-vanzari\/\">Programa\u021bi o demonstra\u021bie<\/a><\/div>\n\n<\/div>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section ind-sec--alt\" id=\"customers\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-head fx-head--center\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<h2 class=\"wp-block-heading\">P\u0103rerile produc\u0103torilor despre SkyPlanner<\/h2>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group ind-custs\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<article class=\"wp-block-group ind-cust ind-cust--photo\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<figure class=\"ind-cust__photo\"><img src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/customers-v1\/08-35ce8dff-f7d0-4cf3-9e71-0fe7e7ff88d3.jpg\" alt=\"Operatori \u00een echipamente pentru camere curate la o linie de umplere a flacoanelor \u00een fabrica farmaceutic\u0103 Laboratory &amp; Allied din Nairobi\" loading=\"lazy\" decoding=\"async\"><\/figure><div class=\"ind-cust__top\"><img class=\"ind-cust__logo\" src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/customers-v1\/09-8c2deb57-ac1c-468b-ad64-fafb9debd7eb.png\" alt=\"Laboratory &amp; Allied\" width=\"71\" height=\"44\" loading=\"lazy\" decoding=\"async\"><p class=\"ind-cust__metric\"><b>+90%<\/b><span>eficien\u021b\u0103 \u00een produc\u021bie<\/span><\/p><\/div>\n\n\n<p class=\"ind-cust__quote\">\u201eEficien\u021ba \u00een produc\u021bie a crescut cu 90%.\u201d<\/p>\n\n\n<p class=\"ind-cust__who\"><b>Abdul Rucyinga, director IT<\/b><br>Laboratory &amp; Allied \u00b7 Produc\u021bie farmaceutic\u0103<\/p>\n\n\n<p class=\"ind-cust__result\">Eficien\u021ba \u00een produc\u021bie a crescut cu 90%, iar realizarea unui plan optimizat pe trei luni pentru toate centrele de lucru dureaz\u0103 mai pu\u021bin de 30 de minute.<\/p>\n\n\n<p class=\"ind-cust__go\"><a href=\"\/ro\/customers\/laboratory-allied\/\">Citi\u021bi p\u0103rerea Laboratory &amp; Allied<\/a><svg class=\"ind-cust__arrow\" viewBox=\"0 0 20 20\" fill=\"none\" aria-hidden=\"true\"><path d=\"M4 10h11M11 5l5 5-5 5\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path><\/svg><\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group ind-cust ind-cust--photo\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<figure class=\"ind-cust__photo\"><img src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/customers-v1\/22-d7d6bcdf-ecf7-48d2-9750-66253ccf9aa7-crop.jpg\" alt=\"Kalle Kalliom\u00e4ki, specialist \u00een lan\u021bul de aprovizionare la UTU, \u00een hala de produc\u021bie a tablourilor electrice din Ulvila\" loading=\"lazy\" decoding=\"async\"><\/figure><div class=\"ind-cust__top\"><img class=\"ind-cust__logo\" src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/customers-v1\/23-beca6df2-3fa2-4315-80e8-7c38a9e3d2e1.png\" alt=\"UTU\" width=\"69\" height=\"59\" loading=\"lazy\" decoding=\"async\"><p class=\"ind-cust__metric\"><b>2 h<\/b><span>economisite s\u0103pt\u0103m\u00e2nal<\/span><\/p><\/div>\n\n\n<p class=\"ind-cust__quote\">\u201eCu SkyPlanner, am trecut de la planificarea produc\u021biei \u00een foi de calcul Excel la optimizarea produc\u021biei \u00een timp real.\u201d<\/p>\n\n\n<p class=\"ind-cust__who\"><b>Kalle Kalliom\u00e4ki, specialist \u00een lan\u021bul de aprovizionare<\/b><br>UTU \u00b7 Tablouri electrice \u0219i aparataj de comuta\u021bie<\/p>\n\n\n<p class=\"ind-cust__result\">Planificarea produc\u021biei economise\u0219te 2 ore de lucru \u00een fiecare s\u0103pt\u0103m\u00e2n\u0103, iar o nou\u0103 list\u0103 de opera\u021bii ajunge la linia de produc\u021bie \u00een c\u00e2teva secunde.<\/p>\n\n\n<p class=\"ind-cust__go\"><a href=\"\/ro\/customers\/utu\/\">Citi\u021bi recenzia UTU<\/a><svg class=\"ind-cust__arrow\" viewBox=\"0 0 20 20\" fill=\"none\" aria-hidden=\"true\"><path d=\"M4 10h11M11 5l5 5-5 5\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path><\/svg><\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group ind-cust ind-cust--photo\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<figure class=\"ind-cust__photo\"><img src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/customers-v1\/13-9cbf2d28-08ef-49a1-94e3-0095e107df55.jpg\" alt=\"Anu J\u00e4rvinen, directoare de produc\u021bie la Fredman Operations, l\u00e2ng\u0103 o celul\u0103 robotizat\u0103 de paletizare din Rauma\" loading=\"lazy\" decoding=\"async\"><\/figure><div class=\"ind-cust__top\"><img class=\"ind-cust__logo\" src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/customers-v1\/10-2fd983ec-02a7-440d-b77d-281f37545c8d.png\" alt=\"Fredman Operations\" width=\"137\" height=\"48\" loading=\"lazy\" decoding=\"async\"><p class=\"ind-cust__metric\"><b>6 luni<\/b><span>pentru care echipa de v\u00e2nz\u0103ri vede capacitatea disponibil\u0103<\/span><\/p><\/div>\n\n\n<p class=\"ind-cust__quote\">\u201eSkyPlanner ofer\u0103 o baz\u0103 solid\u0103 \u0219i siguran\u021b\u0103 pentru \u00eentreaga planificare a produc\u021biei.\u201d<\/p>\n\n\n<p class=\"ind-cust__who\"><b>Anu J\u00e4rvinen, directoare de produc\u021bie<\/b><br>Fredman Operations \u00b7 H\u00e2rtie pentru ambalaje destinat\u0103 contactului cu alimentele<\/p>\n\n\n<p class=\"ind-cust__result\">Echipa de v\u00e2nz\u0103ri vede capacitatea disponibil\u0103 pentru urm\u0103toarele \u0219ase luni, iar solicit\u0103rile de modificare a programului, care necesitau o or\u0103 sau mai mult, primesc acum r\u0103spuns \u00een c\u00e2teva secunde.<\/p>\n\n\n<p class=\"ind-cust__go\"><a href=\"\/ro\/customers\/fredman-operations\/\">Citi\u021bi recenzia Fredman Operations<\/a><svg class=\"ind-cust__arrow\" viewBox=\"0 0 20 20\" fill=\"none\" aria-hidden=\"true\"><path d=\"M4 10h11M11 5l5 5-5 5\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path><\/svg><\/p>\n\n<\/div><\/article>\n\n\n<article class=\"wp-block-group ind-cust ind-cust--photo\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<figure class=\"ind-cust__photo\"><img src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/customers-v1\/02-3a675468-ac30-4369-b781-b03bbf3f9d21.jpg\" alt=\"Vedere aerian\u0103 a fabricii Piristeel de sisteme de siguran\u021b\u0103 pentru acoperi\u0219uri din Kauhava\" loading=\"lazy\" decoding=\"async\"><\/figure><div class=\"ind-cust__top\"><img class=\"ind-cust__logo\" src=\"\/wp-content\/themes\/generatepress-child\/assets\/img\/customers-v1\/07-cec60b32-3b28-48a8-9520-1f12fd8061ee.png\" alt=\"Piristeel\" width=\"96\" height=\"46\" loading=\"lazy\" decoding=\"async\"><p class=\"ind-cust__metric\"><b>99,2%<\/b><span>respectarea termenelor de livrare<\/span><\/p><\/div>\n\n\n<p class=\"ind-cust__quote\">\u201eSkyPlanner ne-a oferit vizibilitatea necesar\u0103 pentru a identifica blocajele \u0219i a adus mai mult\u0103 claritate \u00een gestionarea produc\u021biei.\u201d<\/p>\n\n\n<p class=\"ind-cust__who\"><b>Toni Tuori, director de produc\u021bie<\/b><br>Piristeel \u00b7 Sisteme de siguran\u021b\u0103 pentru acoperi\u0219uri \u0219i sisteme pluviale<\/p>\n\n\n<p class=\"ind-cust__result\">Rata de respectare a termenelor de livrare a ajuns la 99,2% anul acesta, iar programarea produc\u021biei economise\u0219te p\u00e2n\u0103 la patru ore de lucru pe zi.<\/p>\n\n\n<p class=\"ind-cust__go\"><a href=\"\/ro\/customers\/piristeel\/\">Citi\u021bi recenzia Piristeel<\/a><svg class=\"ind-cust__arrow\" viewBox=\"0 0 20 20\" fill=\"none\" aria-hidden=\"true\"><path d=\"M4 10h11M11 5l5 5-5 5\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path><\/svg><\/p>\n\n<\/div><\/article>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n\n<section class=\"wp-block-group sp-section\" id=\"faq\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group sp-container\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<div class=\"wp-block-group fx-head fx-head--center\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<h2 class=\"wp-block-heading\">\u00centreb\u0103ri frecvente<\/h2>\n\n<\/div><\/div>\n\n\n<div class=\"wp-block-group sp-faq fx-faq\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<details class=\"wp-block-details sp-faq__item is-layout-flow wp-block-details-is-layout-flow\"><summary>Cine realizeaz\u0103 integrarea cu SAP Business One?<\/summary>\n<p class=\"sp-faq__a\">Echipa SkyPlanner configureaz\u0103 integrarea bidirec\u021bional\u0103 \u00een etapa ini\u021bial\u0103 de implementare \u0219i asigur\u0103 asisten\u021b\u0103 dup\u0103 punerea \u00een func\u021biune. \u00cen SkyPlanner sunt importate comenzile de produc\u021bie, etapele fluxului tehnologic, resursele, comenzile de achizi\u021bie \u0219i recep\u021biile de m\u0103rfuri. Datele programate \u0219i documentele Issue and Receipt from Production sunt transmise \u00eenapoi. Partenerul dumneavoastr\u0103 B1 sau propriii dezvoltatori pot realiza integrarea \u0219i folosind Service Layer \u0219i API-ul REST al SkyPlanner. Pentru a \u00eencepe, este suficient\u0103 o cheie API.<\/p>\n<\/details>\n\n\n<details class=\"wp-block-details sp-faq__item is-layout-flow wp-block-details-is-layout-flow\"><summary>C\u00e2t dureaz\u0103 implementarea SkyPlanner cu SAP Business One?<\/summary>\n<p class=\"sp-faq__a\">Implementarea se finalizeaz\u0103 de obicei \u00een c\u00e2teva s\u0103pt\u0103m\u00e2ni de la \u00eenceperea etapei ini\u021biale. Echipa stabile\u0219te coresponden\u021bele pentru resurse \u0219i etapele fluxului tehnologic, conecteaz\u0103 comenzile de produc\u021bie \u0219i de achizi\u021bie \u0219i verific\u0103 programul \u00een raport cu planul dumneavoastr\u0103 actual \u00eenainte de punerea \u00een func\u021biune.<\/p>\n<\/details>\n\n\n<details class=\"wp-block-details sp-faq__item is-layout-flow wp-block-details-is-layout-flow\"><summary>Service Layer sau DI API?<\/summary>\n<p class=\"sp-faq__a\">Pentru integr\u0103rile noi, alege\u021bi Service Layer. Acesta folose\u0219te HTTP, ruleaz\u0103 pe HANA \u0219i SQL Server \u0219i este potrivit pentru un sistem de programare \u00een cloud. Folosi\u021bi DI API doar dac\u0103 solu\u021bia middleware existent\u0103 depinde deja de acesta.<\/p>\n<\/details>\n\n\n<details class=\"wp-block-details sp-faq__item is-layout-flow wp-block-details-is-layout-flow\"><summary>Am nevoie de SAP Business One 10.0 FP 2602?<\/summary>\n<p class=\"sp-faq__a\">Doar pentru webhook-uri. Versiunile 10.0 anterioare se integreaz\u0103 prin interog\u0103ri periodice programate.<\/p>\n<\/details>\n\n\n<details class=\"wp-block-details sp-faq__item is-layout-flow wp-block-details-is-layout-flow\"><summary>Cum sunt transmise \u00eenapoi \u00een SAP Business One datele programate?<\/summary>\n<p class=\"sp-faq__a\">Prin <code>PATCH \/b1s\/v1\/ProductionOrders({DocEntry})<\/code>, set\u00e2nd <code>StartDate<\/code> \u0219i <code>DueDate<\/code> pe comand\u0103 \u0219i <code>StartDate<\/code> \u0219i <code>EndDate<\/code> pe liniile ei de resurse. Actualizarea este declan\u0219at\u0103 de webhook-ul SkyPlanner pentru modificarea programului. Cantit\u0103\u021bile produse \u0219i timpul sunt transmise \u00eenapoi prin <code>InventoryGenEntries<\/code> \u0219i <code>InventoryGenExits<\/code>, legate de comand\u0103 prin <code>BaseType<\/code> 202 \u0219i <code>BaseEntry<\/code>.<\/p>\n<\/details>\n\n\n<details class=\"wp-block-details sp-faq__item is-layout-flow wp-block-details-is-layout-flow\"><summary>Avem nevoie de o extensie pentru produc\u021bie \u00een B1?<\/summary>\n<p class=\"sp-faq__a\">Nu. Integrarea folose\u0219te doar obiecte standard B1: comenzi de produc\u021bie, Product Trees, Resources, Items, comenzi de achizi\u021bie \u0219i documente de stoc. Nu se migreaz\u0103 nimic \u00eentr-un nou model de date pentru produc\u021bie.<\/p>\n<\/details>\n\n\n<details class=\"wp-block-details sp-faq__item is-layout-flow wp-block-details-is-layout-flow\"><summary>Putem testa SkyPlanner cu datele noastre din B1 \u00eenainte de integrare?<\/summary>\n<p class=\"sp-faq__a\">Da. Perioada de prob\u0103 de 30 de zile include p\u00e2n\u0103 la 20 de centre de lucru, cu import din CSV sau Excel, f\u0103r\u0103 a fi necesar un card de credit. <a href=\"\/ro\/proba\/\">\u00cencepe\u021bi proba gratuit\u0103<\/a> sau <a href=\"\/ro\/contact-vanzari\/\">discuta\u021bi cu echipa de v\u00e2nz\u0103ri<\/a> despre configura\u021bia dumneavoastr\u0103 B1.<\/p>\n<\/details>\n\n<\/div><\/div>\n\n<\/div><\/div>\n\n<\/div><\/section>\n\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Integr\u0103ri \/ ERP \/ SAP Business One Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei Acest ghid le arat\u0103 partenerilor SAP Business One \u0219i echipelor IT cum s\u0103 conecteze B1 la SkyPlanner APS. Explic\u0103 ce API-uri s\u0103 folosi\u021bi, ce obiecte se transfer\u0103 \u00een fiecare direc\u021bie \u0219i unde apar probleme \u00een proiectele &#8230; <a title=\"Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei\" class=\"read-more\" href=\"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/\" aria-label=\"Read more about Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei\">Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"parent":100786,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"_uag_custom_page_level_css":"","footnotes":""},"class_list":["post-101113","page","type-page","status-publish"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.3 (Yoast SEO v28.7) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>SAP Business One: integrare pentru programare APS | SkyPlanner<\/title>\n<meta name=\"description\" content=\"Integra\u021bi SkyPlanner APS cu SAP Business One: entit\u0103\u021bi Service Layer, autentificare, webhookuri, maparea datelor \u0219i capcane la programarea cu capacitate finit\u0103.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/\" \/>\n<meta property=\"og:locale\" content=\"ro_RO\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei\" \/>\n<meta property=\"og:description\" content=\"Integra\u021bi SkyPlanner APS cu SAP Business One: entit\u0103\u021bi Service Layer, autentificare, webhookuri, maparea datelor \u0219i capcane la programarea cu capacitate finit\u0103.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/\" \/>\n<meta property=\"og:site_name\" content=\"SkyPlanner\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Timp estimat pentru citire\" \/>\n\t<meta name=\"twitter:data1\" content=\"19 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/integrari\\\/erp\\\/sap-business-one\\\/ghid-de-integrare\\\/\",\"url\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/integrari\\\/erp\\\/sap-business-one\\\/ghid-de-integrare\\\/\",\"name\":\"SAP Business One: integrare pentru programare APS | SkyPlanner\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/#website\"},\"datePublished\":\"2026-10-17T13:00:38+00:00\",\"description\":\"Integra\u021bi SkyPlanner APS cu SAP Business One: entit\u0103\u021bi Service Layer, autentificare, webhookuri, maparea datelor \u0219i capcane la programarea cu capacitate finit\u0103.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/integrari\\\/erp\\\/sap-business-one\\\/ghid-de-integrare\\\/#breadcrumb\"},\"inLanguage\":\"ro-RO\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/integrari\\\/erp\\\/sap-business-one\\\/ghid-de-integrare\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/integrari\\\/erp\\\/sap-business-one\\\/ghid-de-integrare\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Integr\u0103ri de software ERP \u0219i MES cu SkyPlanner\",\"item\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/integrari\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"SkyPlanner APS pentru sistemul dumneavoastr\u0103 ERP\",\"item\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/integrari\\\/erp\\\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"SkyPlanner APS pentru SAP Business One: programarea produc\u021biei cu capacitate finit\u0103\",\"item\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/integrari\\\/erp\\\/sap-business-one\\\/\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/#website\",\"url\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/\",\"name\":\"SkyPlanner\",\"description\":\"AI-powered production scheduling and planning software\",\"publisher\":{\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ro-RO\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/#organization\",\"name\":\"Skycode Oy\",\"url\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/skyplanner.ai\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/Skyplanner-logo-2.svg\",\"contentUrl\":\"https:\\\/\\\/skyplanner.ai\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/Skyplanner-logo-2.svg\",\"width\":223,\"height\":43,\"caption\":\"SkyPlanner APS\"},\"image\":{\"@id\":\"https:\\\/\\\/skyplanner.ai\\\/ro\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"legalName\":\"Skycode Oy\",\"alternateName\":[\"Skycode\",\"SkyPlanner\",\"SkyPlanner APS\"],\"description\":\"Skycode Oy is the Finnish software company that develops and publishes SkyPlanner APS, AI production scheduling and advanced planning and scheduling (APS) software for manufacturers worldwide. Founded in 1997 as a sole proprietorship and incorporated as Skycode Oy in 2008.\",\"foundingDate\":\"1997\",\"taxID\":\"2204947-0\",\"vatID\":\"FI22049470\",\"telephone\":\"+358407000002\",\"email\":\"support@skyplanner.ai\",\"address\":{\"@type\":\"PostalAddress\",\"streetAddress\":\"Rantakatu 2 G 11\",\"postalCode\":\"65100\",\"addressLocality\":\"Vaasa\",\"addressCountry\":\"FI\"},\"brand\":{\"@type\":\"Brand\",\"name\":\"SkyPlanner\"},\"knowsAbout\":[\"Production Scheduling\",\"Advanced Planning and Scheduling\",\"Manufacturing AI\",\"Finite Capacity Scheduling\",\"ERP Integration\",\"MES Integration\"],\"areaServed\":\"Worldwide\",\"contactPoint\":[{\"@type\":\"ContactPoint\",\"contactType\":\"sales\",\"url\":\"https:\\\/\\\/skyplanner.ai\\\/contact-sales\\\/\",\"areaServed\":\"Worldwide\"},{\"@type\":\"ContactPoint\",\"contactType\":\"customer support\",\"email\":\"support@skyplanner.ai\",\"telephone\":\"+358407000002\",\"areaServed\":\"Worldwide\"}],\"sameAs\":[\"https:\\\/\\\/www.wikidata.org\\\/wiki\\\/Q141672132\",\"https:\\\/\\\/skycode.fi\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/skycodeoy\\\/\",\"https:\\\/\\\/www.finder.fi\\\/IT-konsultointi+IT-palvelut\\\/Skycode+Oy\\\/Vaasa\\\/yhteystiedot\\\/1934882\"]}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SAP Business One: integrare pentru programare APS | SkyPlanner","description":"Integra\u021bi SkyPlanner APS cu SAP Business One: entit\u0103\u021bi Service Layer, autentificare, webhookuri, maparea datelor \u0219i capcane la programarea cu capacitate finit\u0103.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/","og_locale":"ro_RO","og_type":"article","og_title":"Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei","og_description":"Integra\u021bi SkyPlanner APS cu SAP Business One: entit\u0103\u021bi Service Layer, autentificare, webhookuri, maparea datelor \u0219i capcane la programarea cu capacitate finit\u0103.","og_url":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/","og_site_name":"SkyPlanner","twitter_card":"summary_large_image","twitter_misc":{"Timp estimat pentru citire":"19 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/","url":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/","name":"SAP Business One: integrare pentru programare APS | SkyPlanner","isPartOf":{"@id":"https:\/\/skyplanner.ai\/ro\/#website"},"datePublished":"2026-10-17T13:00:38+00:00","description":"Integra\u021bi SkyPlanner APS cu SAP Business One: entit\u0103\u021bi Service Layer, autentificare, webhookuri, maparea datelor \u0219i capcane la programarea cu capacitate finit\u0103.","breadcrumb":{"@id":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/#breadcrumb"},"inLanguage":"ro-RO","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/ghid-de-integrare\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skyplanner.ai\/ro\/"},{"@type":"ListItem","position":2,"name":"Integr\u0103ri de software ERP \u0219i MES cu SkyPlanner","item":"https:\/\/skyplanner.ai\/ro\/integrari\/"},{"@type":"ListItem","position":3,"name":"SkyPlanner APS pentru sistemul dumneavoastr\u0103 ERP","item":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/"},{"@type":"ListItem","position":4,"name":"SkyPlanner APS pentru SAP Business One: programarea produc\u021biei cu capacitate finit\u0103","item":"https:\/\/skyplanner.ai\/ro\/integrari\/erp\/sap-business-one\/"},{"@type":"ListItem","position":5,"name":"Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei"}]},{"@type":"WebSite","@id":"https:\/\/skyplanner.ai\/ro\/#website","url":"https:\/\/skyplanner.ai\/ro\/","name":"SkyPlanner","description":"AI-powered production scheduling and planning software","publisher":{"@id":"https:\/\/skyplanner.ai\/ro\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skyplanner.ai\/ro\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ro-RO"},{"@type":"Organization","@id":"https:\/\/skyplanner.ai\/ro\/#organization","name":"Skycode Oy","url":"https:\/\/skyplanner.ai\/ro\/","logo":{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/skyplanner.ai\/ro\/#\/schema\/logo\/image\/","url":"https:\/\/skyplanner.ai\/wp-content\/uploads\/2022\/05\/Skyplanner-logo-2.svg","contentUrl":"https:\/\/skyplanner.ai\/wp-content\/uploads\/2022\/05\/Skyplanner-logo-2.svg","width":223,"height":43,"caption":"SkyPlanner APS"},"image":{"@id":"https:\/\/skyplanner.ai\/ro\/#\/schema\/logo\/image\/"},"legalName":"Skycode Oy","alternateName":["Skycode","SkyPlanner","SkyPlanner APS"],"description":"Skycode Oy is the Finnish software company that develops and publishes SkyPlanner APS, AI production scheduling and advanced planning and scheduling (APS) software for manufacturers worldwide. Founded in 1997 as a sole proprietorship and incorporated as Skycode Oy in 2008.","foundingDate":"1997","taxID":"2204947-0","vatID":"FI22049470","telephone":"+358407000002","email":"support@skyplanner.ai","address":{"@type":"PostalAddress","streetAddress":"Rantakatu 2 G 11","postalCode":"65100","addressLocality":"Vaasa","addressCountry":"FI"},"brand":{"@type":"Brand","name":"SkyPlanner"},"knowsAbout":["Production Scheduling","Advanced Planning and Scheduling","Manufacturing AI","Finite Capacity Scheduling","ERP Integration","MES Integration"],"areaServed":"Worldwide","contactPoint":[{"@type":"ContactPoint","contactType":"sales","url":"https:\/\/skyplanner.ai\/contact-sales\/","areaServed":"Worldwide"},{"@type":"ContactPoint","contactType":"customer support","email":"support@skyplanner.ai","telephone":"+358407000002","areaServed":"Worldwide"}],"sameAs":["https:\/\/www.wikidata.org\/wiki\/Q141672132","https:\/\/skycode.fi\/","https:\/\/www.linkedin.com\/company\/skycodeoy\/","https:\/\/www.finder.fi\/IT-konsultointi+IT-palvelut\/Skycode+Oy\/Vaasa\/yhteystiedot\/1934882"]}]}},"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"betterdocs-category-thumb":false},"uagb_author_info":{"display_name":"Jussi M\u00e4ntyl\u00e4","author_link":"https:\/\/skyplanner.ai\/ro\/author\/jussi\/"},"uagb_comment_info":0,"uagb_excerpt":"Integr\u0103ri \/ ERP \/ SAP Business One Ghid de integrare SAP Business One cu SkyPlanner APS pentru programarea produc\u021biei Acest ghid le arat\u0103 partenerilor SAP Business One \u0219i echipelor IT cum s\u0103 conecteze B1 la SkyPlanner APS. Explic\u0103 ce API-uri s\u0103 folosi\u021bi, ce obiecte se transfer\u0103 \u00een fiecare direc\u021bie \u0219i unde apar probleme \u00een proiectele&hellip;","_links":{"self":[{"href":"https:\/\/skyplanner.ai\/ro\/wp-json\/wp\/v2\/pages\/101113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skyplanner.ai\/ro\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/skyplanner.ai\/ro\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/skyplanner.ai\/ro\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/skyplanner.ai\/ro\/wp-json\/wp\/v2\/comments?post=101113"}],"version-history":[{"count":0,"href":"https:\/\/skyplanner.ai\/ro\/wp-json\/wp\/v2\/pages\/101113\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skyplanner.ai\/ro\/wp-json\/wp\/v2\/pages\/100786"}],"wp:attachment":[{"href":"https:\/\/skyplanner.ai\/ro\/wp-json\/wp\/v2\/media?parent=101113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}