cancel
Showing results for 
Search instead for 
Did you mean: 

Synching SAP Business One Invoice Numbers to WBTLs Orders

Former Member
0 Kudos

Hello.

Our client has requested that all Sales Orders in the Web App should display all the relevant SAP B1 Invoice Doc Numbers on the BP Order History Report page one sales ord can generate many Invoices.

The only relationship we have is between Sales Order line item and the Invoice being that of an Outsourced ref no.( they do not create Deliveries these are outsourced :>) <b> so we cannot use base and target documents</b>

We have a decision to make either extend the Current API to search for this realtionship at point of replication ( they are processing RATHER a lot of Transactions a month OR Write a stored procedure to retrieve that information and place on a Z table in Netpoint DBase say every 10 mins.

What are you views on this if we consider performance, upgrading and flexibility in terms of additonal fields.

Tech info

Webtools 5.9

B1 2005 Sp1

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Richard,

For custom fields in NetPoint we recommend creating a table rather then adding fields to existing tables. (The performance hit for this should be negligible, and you will not need to worry about upgrades affecting your custom data.)

I am assuming by "point of replication" you are referring to writing a synch plugin. A stored proc wil be faster than a synch plugin, but there may be concurrancy issues if the stored proc fires prior to the synchronization of the invoices.

You could use a synch plugin to fire your proc to avoid this or put an insert trigger on the ordermaster table and look for records with a CartType of "I".

The synch plugin is a dynamically loaded assembly, so there is some processing involved in using them.

The order history page is one of the slower pages in the application, so your biggest hit will probably be here. If you intend to modify this page to include your custom fields you will need to hit the database for every record in the order history. To avoid this you would have to re write the page.