Skip to Content
avatar image
Former Member

Approved Purchase Order Causing Integration Error with iVend

Hello Support,

I am running:

  1. SBO 9.2 PL 03 in one test environment, integrated with iVend Retail 6.5.3
  2. SBO 9.2 PL 08 in a 2nd test environment, integrated with iVend Retail 6.5.3, and
  3. SBO 9.2 PL 09 in a 3rd test environment, integrated with iVend Retail 6.5.3

In all 3 test envs, I test the following.

  1. Set up an approval procedure to approve any purchase order less then $500. If $500 or more, no approval required.
  2. I raise a PO destined for a specific iVend Retail store (SBO warehouse) and approve it as the same user (manager). So I am the originator and authoriser.
  3. The PO is integrated into iVend.
  4. I login onto the designated iVend store and raise a Goods Receipt PO against the PO that was raised in SBO
  5. At the integration point, where the SAP DI API is invoked, the iVend-SAP integration service falls over.
  6. Stuck at the integration point are:
  • update transaction for the PO
  • add transaction for the GRPO
  1. When I raise a PO that is more than $500 and does not require approval, it goes through to iVend and back again with a matching GRPO no problems whatsoever.
  2. Only when its an Approved PO, that the integration service falls over.
  3. Upon investigation with Citixsys, they have found no error in their code and the code is doing what it is supposed to do for integrated inventory transaction documents.

As extra information, I also found the following:

  1. There is a flag called WddStatus in table OPOR
  2. For a normal PO created in SAP, WddStatus = ‘-‘
  3. For an Approved PO created in SAP, WddStatus = ‘P’
  4. This is the key difference between the 2 types of records being passed to iVend and iVend trying to process at integration point
  5. When the WddStatus = ‘-‘, iVend processes the GRPO & PO records successfully
  6. When the WddStatus = ‘P’, iVend-SAP integration service fails and cannot process the GRPO & PO for integration.

I have uninstalled and reinstalled the SAP DI API, both 32-bit and 64-bit but still no luck.

Any suggestions as to what the cause might be from the SBO perspective pls?

Thank you


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers