Last week, we hit a weird default OTM (Oracle Transportation Management) error whereby LTL (Less Than Truckload) transport mode shipment does not tender out with the standard secure resources status. Instead, secure resources status was changed to SECURE RESOURCE_PICKUP NOTIFICATION. As a result, the service provider cannot accept the tender for this status. Thankfully, OTMFAQ forum give us the clue to resolve this. I will explain the rationale here instead.
OTM Default Workflow
The “issue” is actually due to a default business scenario in United States (US). In layman terms, LTL means loose cargo. Thus, service provider is expected to pickup the loose cargo rather than the need to accept the tender request. This is why the status is called SECURE RESOURCE_PICKUP NOTIFICATION. In a way, the request is auto accepted. The way to fix it is to amend the workflow configuration by adding LTL into the TENDER%MODES values.
OTM and its Culture
Debugging in OTM is a challenging task and can consume lots of unproductive hours. Historically, this product was tested widely in US and Europe and very less for Asia. There are many default values that are catered to the American and European audiences. The key tip is to understand and know which are defaulted. If you manage to find this configuration, we usually cross our fingers and hope that the default values can be amended.
All product are designed by humans. Unknowingly, cultures are factored into its design. A good product should always configuration of these default cultural values. One way to do so is to test its localisation features.