Portfolio Achievments 2025

Developed and implemented 8 major integrations for transportation-logistics systems and electronic document management, automated 90%+ of business processes for counterparty interactions, and created a comprehensive analytical reporting system. Total workload: ~1,800 hours of development.

Databases

• Oracle Database 12c+: PL/SQL, Packages, Types, DBMS_SCHEDULER, XMLTABLE, JSON, MERGE
• Optimization: Indexes, partitioning, CTE, FORALL, Bulk Collect
• Integrations: Database Links (@OTM), REF CURSOR, Scalar wrappers

API and Integrations

• REST API: UTL_HTTP, JSON parsing, OAuth, asynchronous calls
• XML Processing: XMLTABLE, XPath, dynamic structures
• Web Services: SOAP, JSON-RPC, HTTP polling

BI and Reporting

• Oracle BI 12c: Repositories, analyses, dashboards, drill-down
• ETL: Aggregation procedures, star schema (facts/dimensions)
• Visualization: Filters, prompts, conditional formatting

External APIs

• CDEK API: Asynchronous processing, city directories (135K records)
• Avito API: Advertisement management, statistics, reports
• DADATA: Address validation, geocoding
• Google Sheets API: OAuth2, read/write operations
• Delovye Linii API: Cost calculator, address book, orders

Infrastructure (AI-assisted)

• Apache HTTP Server: Proxy, ModSecurity (DDOS/SQL-injection protection)
• SSL/TLS: Let's Encrypt, automatic certificate renewal
• Python/Flask: Microservices (token generation, mobile application)
• Linux: Server configuration, SFTP, cron jobs

In 2025, implemented 8 major integrations for transportation-logistics systems and electronic document management with full development cycle: from API documentation analysis to creating user interfaces and BI reports.

Key Achievements:

• ✅ Automated 80%+ of processes for transport company interactions and document management
• ✅ Processed millions of transactions worth tens of millions of rubles
• ✅ Optimized 5+ critical processes (up to 70% performance improvement)
• ✅ Created a centralized address system for all integrations
• ✅ Fully automated electronic document workflow via Diadoc

Technology Profile: Oracle PL/SQL, REST API, JSON/XML, BI Development, ETL, Linux/Apache, Python.

Work Approach: Independent full-cycle development, proactive problem-solving, focus on code quality and documentation, continuous learning and best practices application.

Technical Expertise

✅ Oracle PL/SQL: packages, types, collections, dynamic SQL
✅ API Integration: REST, SOAP, JSON, XML, OAuth, asynchronous processing
✅ Optimization: Indexes, partitioning, bulk operations, refactoring
✅ ETL Processes: Schema design, aggregation, transformation
✅ BI Development: Oracle BI 12c (repositories, reports, dashboards)
✅ Linux/Apache: Server configuration, security, SSL

Soft Skills

✅ Independence: Full development cycle (from analysis to deployment)
✅ Documentation: MD files, code comments, user manuals
✅ Communication: Collaboration with logistics, marketing, suppliers
✅ Troubleshooting: Rapid localization and resolution of critical issues
✅ Code Review: Legacy code refactoring, architecture improvements

Feb-March 2025: Professional Development Course (Specialist)

• Topics: Oracle BI 12c Build Repositories, Oracle BI 12c Create Analyses and Dashboards
• Outcome: Application of new knowledge in current projects (BI reports creation)

1. CDEK Integration (September-October)

Objective: Full automation of order creation and submission to CDEK with asynchronous API response processing.

Implementation:

• Asynchronous order processing architecture (initial validation → status polling)
• Automatic address verification via CDEK directory (~135K records)
• Address synchronization using KLADR and FIAS codes
• Multi-account: support for multiple CDEK accounts
• Automatic tariff selection based on cargo dimensions and weight
• Courier call functionality (make_intake_order, get_intake_info)

Technologies: PL/SQL, JSON API, DBMS_SCHEDULER (parallel processing), XMLTABLE

Result: Production-ready integration, full CDEK workflow automation.

2. Baikal Service Integration (Year-round, primary support)

Objective: Support and expansion of inter-branch transportation integration with transition to address strings (FIAS codes).

Key Enhancements:

• Critical ORA-04061 Fix: Resolved package unavailability after recompilation (global variable refactoring, agent with retry logic)
• FIAS Code Migration: create_order_fias procedure for universal order submission to any destination
• Multi-entity Support: Adaptation for Techservice and ContractService (different INN/KPP)
• Automatic Payer Detection: Based on transportation type (inter-warehouse → TSK, others → Client)
• Date Validation: Auto-selection of valid dates during holidays/weekends (6-day work week)
• Insurance Calculation Optimization: From 9 seconds to 3-4 seconds (moved to PROD, join optimization)

Processed: 42+ support hours in October alone, dozens of invoices worth millions of rubles.

Result: Stable integration operation, 95% order automation, minimal manual intervention.

3. Avito Integration (July-October)

Objective: Automate heavy equipment advertisement placement (~20K+ positions) with cost control and analytics.

Implementation:

• Auto-mapping: Automatic equipment matching with Avito catalog (104 models)
• XML Generation: Dynamic ad creation with ~50 parameters
• Multi-source: Data merging from OEBS and Google Sheets
• Image Management: Auto-upload photos to web server, category processing
• TOP-500 Ranking: Prioritization algorithm considering regional limits
• Error Control: Avito response parsing, placement issue categorization
• BI Report Functionality: ETL process for analytics (statuses, costs, drill-down)
• API Management: Stop advertisements from BI (Action → REST API → DB procedure)

Optimization: Parallel processing via DBMS_SCHEDULER (from 7+ hours to <2 hours).

Technologies: PL/SQL, REST API, JSON, HTML/CSS (descriptions), Apache, Google Sheets API

Result: 979 of 983 ads successfully placed (99.6% success rate), full process automation.

4. Drom.ru Integration (July-October)

Objective: Expand sales channels through new marketplace.

Implementation:

• XML directory parsing (models, cities, categories)
• Parameter database creation (XXT_DROM_PARAMS, ~50 XML tags)
• Data merging from OEBS and Google Sheets (custom ads)
• Model and category mapping (42 of 104 matched automatically)
• handle_ads procedure for advertisement lifecycle management
• XML publication to web server (publish_xml)

Result: Production-ready integration, expanded market coverage.

5. Delovye Linii Shipping Cost Calculator (July-August)

Objective: Replace Excel matrix with API calculator integrated into quotations.

Implementation:

• API Integration: JSON calculator with dynamic response structure processing
• Table Function: dellin_calc_func returns rates for all delivery types
• Asynchronous Processing: run_shipping_calculations procedure via DBMS_SCHEDULER
• Cargo Parameters: Automatic calculation of dimensions, volume, weight, packaging
• Auto-date: Selection of nearest valid pickup date
• BI Report: Calculator comparison with current calculation method
• Directories: Loading counterparties, service types, cargo types (UIDs)

Problems and Solutions:

• Dynamic XML structure → Universal parser development
• API asynchronicity → Polling with intervals

Result: Automated cost calculation for all destinations, discrepancy analytics.

6. OTM Location Address System (July-October)

Objective: Centralize address data for all integrations with validation via DADATA and carrier APIs.

Implementation:

• Delovye Linii Address Book Integration: Procedures for counterparty, address, and contact retrieval
• xxt_dellin_locations Table: Storage of ~6K addresses with FIAS codes
• DADATA Validation: check_address_equality procedure (FIAS + coordinate verification)
• Custom OTM Form: Address editing interface with auto-verification
• OTM Agents: Automatic address verification on change (trigger + JOB)
• KLADR/FIAS Synchronization: CDEK and Delovye Linii directory matching with our locations

Processed: ~6,000 addresses, 80% of branches updated.

Result: Unified address data source, 88%+ recognition quality, user documentation.

7. "Invoices from Diadoc" Report (June)

Objective: Analytical system for reconciling invoices from transport companies with OTM and OEBS data.

Implementation:

• ETL Process: xxt_otm_invoice package (4 fact/dimension tables)
• XML/JSON Parsing: Documents from Diadoc, Baikal API, Delovye Linii API, Major registries
• Data Matching: OTM Invoices ↔ Diadoc Invoices ↔ OEBS Vouchers
• Planning Control: Additional shipment requirement flags
• BI Report: Dashboard with drill-down, filters (supplier, period, status)
• Key Carrier Support: Baikal, Major, Delovye Linii, CDEK, etc.

Problems Resolved:

• Diadoc XML structure change (field migration)
• Services for different legal entities in one document
• Duplicate waybills in different invoices

Result: Full transparency of carrier settlements, automated document reconciliation worth millions of rubles.

8. Diadoc Document Workflow Integration (Year-round, critical infrastructure)

Objective: Automate receipt and processing of electronic documents (invoices, UPD) from transport companies via Diadoc system.

Implementation:

• Diadoc API Integration: Document metadata retrieval, XML invoice download
• XML Document Parsing: Processing various UPD/invoice formats (multiple 1C export versions)
• Automatic Processing: Scheduled new document loading, processing statuses
• Change Adaptation: Critical issue resolution during XML structure changes (signer field migration: НомерСЧ → НомерДок)
• Edge Case Handling: Documents with ReceiptStatus "HaveToCreateReceipt", unprocessed documents on API failure
• Major/Baikal Integration: Automatic Diadoc invoice linking with carrier integration data
• Notifications: Alerts for new document arrivals, processing issues

Problems Resolved:

• Critical failure on XML structure change → Rapid parser adaptation
• Missing metadata for some documents → Backup data retrieval mechanisms
• Different XML versions from 1C → Universal parser supporting multiple formats

Technologies: PL/SQL, XMLTABLE, XPath, REST API, DBMS_SCHEDULER

Result: Fully automated invoice receipt process, hundreds of documents worth millions of rubles processed monthly.

9. Major Integration (Year-round, regular support)

Objective: Transportation registry processing, invoice creation automation.

2025 Enhancements:

• Data Update Optimization: From 3+ hours to <1 hour (loop replacement with XMLTABLE, log partitioning)
• Automatic Waybill Linking: Shipment identification by release reference numbers
• Additional Shipment Processing: Automatic parent-invoice creation
• Notification Distribution: Automatic aggregation of unplanned objects

Processed: Monthly registries of ~3K+ waybills, invoices worth tens of millions of rubles.

Result: 90%+ registry processing automation, minimized manual logistician work.