m
mobinkashif

Mobin K

@mobinkashif

SAP B1 Integration Developer

Pakistán
Inglés, Urdu
Parte de la información aparece en idioma inglés.
Sobre mí
I am a software developer and SAP Business One integration specialist focused on turning complex business processes into reliable software. I specialize in ERP integrations, C# .NET, and REST APIs to automate workflows and help businesses maximize their technology. I enjoy solving problems that lack out-of-the-box solutions by building practical, maintainable platforms.... Lee más

Habilidades

m
mobinkashif
Mobin K
desconectado • 
Tiempo medio de respuesta: 1 hora

Revisa mis servicios

Desarrollo de CRM y ERP
I will build single license desktop and web sap business one app with di API

Experiencia laboral

Alpha_Container Industries

SAP ERP Implimentation

Alpha Container Industries • Freelance

Mar 2026 - Present • 6 mos

SAP Business One implementation for manufacturing companies, focused on how the departments actually run, not on generic ERP screens. I work across the operations that sit on SAP: store and warehouse, supply chain and purchasing, production, quality, and sales. I already know how these teams hand work to each other — requisition to purchase, receipt into store, issue to production, quality hold and release, and finished goods back to sales — and I map that flow onto SAP Business One so the documents, stock, and approvals stay in SAP. The build is done through the SAP DI API. Users work in a custom application shaped to the client’s process. Transactions are created, updated, and posted in SAP through the DI API, so stock, documents, and master data remain the system of record. The custom layer adds the controls the client needs: department-wise steps, approvals, and checks that standard SAP does not fit to their shop floor. Reporting is part of the same work. I build custom operational reports for store, supply chain, production, quality, and management, and I use Crystal Reports where the client needs formatted, printable documents and formal reports drawn from SAP and the custom application. This cuts licensing cost. Staff who only run store, supply chain, production, or quality work do not each need a full SAP user license. They use the custom application, and SAP is updated through the DI API. Operations get tighter at the same time, because each department follows the client’s own controls and reports instead of working around standard SAP screens. Result for the client: SAP Business One as the backbone, department operations running the way the plant works, custom controls and Crystal Reports matched to the company, and lower license spend.

Freelance

SAP B1 Integration Developer | C# .NET & SAP DI API

Freelance • Freelance

Jan 2021 - Present • 5 yrs 8 mos

Specializing in SAP Business One integrations and ERP workflows. Responsible for developing custom desktop and web applications using C#, .NET, and the MERN stack. Focuses on connecting frontend, backend, and databases with ERP systems through SAP DI API and REST API integrations to automate manual business processes and improve operational efficiency.

Alpha_Container Industries

FBR API Integration with Desktop And Web applications

Alpha Container Industries • Freelance

Sep 2025 - Nov 2025 • 2 mos

FBR digital invoicing for multiple companies. I built the applications that sales and accounts use to raise invoices and submit them to the Federal Board of Revenue, so each company stays compliant without posting invoices by hand on the FBR portal. I know how invoicing runs in a trading or manufacturing company: the sale is recorded, tax is calculated, the invoice is issued to the customer, and the same invoice must be registered with FBR before it is a valid tax invoice. I mapped that flow into software and connected it to the FBR API, so invoice data is sent, validated, and stored with the FBR response against the company’s own record. Delivery is on two fronts. .NET desktop applications for teams that work inside the office, and web applications in Next.js for companies that need access in the browser. The same FBR invoice integration is set up per company, each with its own registration, so one product line serves multiple businesses. Staff raise the invoice in the application they already use. The FBR API submits it, and the result comes back onto that invoice. If a submission fails, it stays visible so accounts can correct it and send it again. Sales and accounts do not re-enter the same invoice on the FBR site. Result for the client: FBR-compliant invoicing across multiple companies, on desktop and on the web, with tax submission handled through the FBR API as part of normal billing.