FAQ
FAQ on XGLB, proof of arrival, and SAP
Common questions about transport evidence, logistics documentation, and running XGLB on SAP ECC or S/4HANA.
What is proof of arrival and why does it matter in SAP?
Proof of arrival documents that goods arrived at the destination, often required for logistics and tax audits. SAP connects this evidence with deliveries and postings.
Can XGLB run on SAP ECC and S/4HANA?
Yes. XGLB is implemented as an integrated extension so workflows remain inside your SAP landscape, including browser-based web forms for evidence capture.
Do I need extra middleware for proof-of-arrival processes?
Not necessarily. Depending on architecture, you can keep the core workflow in SAP; with XGLB Web, confirmations can additionally be handled in the browser without moving the core process out of ERP.
How does XGLB support forwarding confirmations and reminders?
XGLB supports structured capture and tracking of transport evidence, including escalation when follow-up is needed.
How does XGLB fit existing logistics processes?
It attaches to existing SAP documents and roles and adds evidence-specific steps without replacing your overall logistics design.
Can XGLB use DHL, UPS, or FedEx tracking protocols as evidence documents?
Yes, optionally XGLB can retrieve tracking protocols from express carriers (e.g. DHL, UPS, FedEx), assign them to the evidence case, and process and archive them including PoD letters.