This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TI-API: Xceptor slow to process HARMAN 178612 Remittances

Part Number: TI-API

Hello,

I have been having a hard time getting my Harman 178612 remittances submitted through the new Xceptor/ DU process that we were recently testing that use PDF submissions. This morning at 8:28am CST I submitted Harman 178612 remittance (email subject: REMADV DU PAYER 178612, to: topc@list.ti.com; cust_documents Service Account).

I have not yet received the confirmation that Xceptor has either posted or failed. FBL5N does not show that the remittance was posted either. Lastly, I checked Xceptor website to see the status of this submission (Data Item ID 136049) and it shows that the execution succeeded. I do not know why if it succeeded, that it has not told me that it has posted and it has not updated SAP FBL5N to show the remittance as posted.

Please let me know if you need more information. 

  • Megan,

    Sorry for the  delay in responding.  Did you get the confirmation?

  • Hi Faye, I did end up getting the confirmation later that afternoon, but I received it about 7 hours after I had sent it. I am still curious why there is such a long delay before the remittance actually posts in SAP if Xceptor says that it was completed at the time of submission. 

  • Hi Megan,

    I'll check to see if there is a reason for this.  I may not get a response until Monday.

    Regards,

    Faye

  • Megan,

    This is still being investigated.  Sorry for the delay.

    Regards,

    Faye

  • Megan,

    One of our analyst is discussing this with the developers and has your contact information.  They will reach out to you directly when then have more information on this.   I am moving forward with closing this thread.

    Regards,

    Faye

  • Hi Megan,

    I wanted to close this out and document what had happened, for future reference:

    Currently one of our Xceptor processes only runs on one machine.  When the process tried to run on other machines, it was getting a fault error and would retry on a different machine, causing the delay.  Our developer is working to resolve this and should have a fix deployed by Monday.  Thanks for your patience.

    Regards,

    Faye

**Attention** This is a public forum