Search Engine: Elastic

Article ID: 112180, created on Sep 2, 2011, last review on Oct 15, 2014

  • Applies to:
  • Business Automation 5.5
  • Business Automation 5.4


The table below describes common types of issues related to the orders processing functionality in PBA-E along with the suggestion on where to start searching for the relevant information.

Type Description Actions and relevant logs
Order stuck in ‘WP’Order stuck in “Waiting for Payment” StatusTwo possible cases: 1)Order is waiting for Payment (before provisioning) -> Check Payment 2)Order is waiting to be consolidated.
Order stuck in ‘NP’Order stuck in “No Payment Method attached” StatusThere is no Payment Method selected for automatic payments on customer’s account. Suggest customer to use one.
Order stuck in ‘WA’or ‘SS’Order stuck in “Waiting for Approval” or “Suspected” StatusesCheck Payment -> Fraud screening results. Reconfigure Fraud Filter if necessary.
Order stuck in ‘PR’Order stuck in “Provisioning” Status Event Log: Check if the necessary “Submit Event” was posted. BM.log: Check submit event handler

Following system components have direct influence on the orders processing functionality:

BM, TASKMAN, PEMGATE, [Payment plugin], [Fraud plugin] containers on the PBA-E application server.

Log files could be found as below:

BM.log -- Linux: /usr/local/bm/log/BM.log; Windows: C:\Program Files\Parallels\PBA\log\BM.log

Event Log -- PBA-E Control Panel, Configuration Director, Event Manager, Event Log

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 210d017ddc3a076d22f0f865b1cf0730 92711db0799e8aefe8e51f12dace0496 801221f8cd76fba7300d1e6817c8e08b e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF