- ERP manages internal business processes.
- IT Inventory converts ERP data into customs-compliant formats (MANDATORY).
- IT Inventory transmits data to CEISA 4.0 / INSW.
- Category A: ERP + IT Inventory within a single system (fully integrated).
- Category B: ERP is separate, while IT Inventory is connected via an interface/mirroring mechanism.
- Category C: ERP and IT Inventory operate independently without integration.
- Category D: Manual (not recommended).
- Does IT Inventory have to be part of a single application?
Logically, this cannot be implemented as a single application,
because the core functions of ERP and IT Inventory are different.
- Yes, it can operate because its supporting tools may be provided through other means, such as Excel.
:: Does H2H Always Have to Use an API? ::
H2H does not necessarily always use an API — however, in modern practice, APIs are the safest, most stable, and recommended approach.
H2H (Host-to-Host) is essentially a mechanism for exchanging data between systems. There are several possible communication methods:
- API (REST/JSON, XML) → most common, secure, and modern
- File-based integration → CSV/XML files pushed or pulled via SFTP
- Database-to-database → direct queries, views, or stored procedures
- Message Queue → Kafka, RabbitMQ, MQ Series
- Socket/Custom Protocol → rarely used today
Why Are APIs More Recommended?
Better security (token, HMAC, JWT)
Real-time (no need to wait for file uploads)
Easier to maintain
Preferred by IT teams because they are clear, structured, and minimize errors
Aligned with CEISA 4.0 integration standards
When Should You Not Use an API?
There are several situations where non-API integration is still used:
Legacy systems that do not have an API
Small companies that can only send CSV/XML files
Daily batch integrations that do not require real-time processing
Unstable internet connections where SFTP may be more reliable
It is still possible, but more complex, slower, and more prone to errors.
