|ePortal Scheduled Maintenance Notification
ePortal may be unavailable between 9:00am and 3:00pm EDT for planned maintenance.
During this time documents will be received but not processed. Once the maintenance is
Thank you for selecting eBridge as your provider of business-to-business solutions.
Added optional segments:
N1 ST header level – 850 and 860 Domestic
N1 BG header level – 850 and 860 Domestic
Clarified usage of this data segment:
PO4 01 and 14 – 850, 860 Domestic
Edits were made to the 850 and 860. The latest Implementation Guides are available on the NCM website and are also posted on the Canada POL supplier portal . Please make sure you have the most recent copy of each applicable guide and are prepared to handle these changes as they will take effect on Monday, March 4th, 2013.
If you have any business questions, please contact email@example.com. Thanks!
Canada POL Link:
Target Canada EDI
If you have any questions or comments please don’t hesitate to contact us!
Most people start the New Year with high hopes thinking that this year will be a more successful year than the last. Goals are set and resolutions are made, so if one of your goals or resolutions for 2013 has to do with eCommerce success, than you came to the right blog.
I found three articles that really lay out what eCommerce retailers need to do to be effective in the fast pace tech-industry during 2013. The articles lay out what you need to do to set your eCommerce site apart from others. Shoppers now have the flexibility to shop in a store, online, or through their mobile device, which gives them access to eCommerce stores all over the world. The three articles do a great job providing tips and tricks that range from website layout to unique promotional ideas which I think will give ideas for even the most veteran eCommerce sites.
Perhaps you’ve neglected your 2013 goals or just haven’t gotten around to making the wanted or needed changes to your eCommerce website, well now is your time. Don’t put it off any longer. 2013 is moving quickly, so by following these helpful tips, you could reach success that you once thought was only a dream!
If you have any other great eCommerce articles, please post them in the comments section. I would love to read other tips you have used to help your company succeed in 2013!
13 Tips for Ecommerce Success
Revamp Your Open Source e-Commerce Website for the New Year
What Do Shoppers Think of Your Ecommerce Site?
If you have any other great eCommerce articles, please post them in the comments section. I’m sure that there are tons more effective tips that may help your fellow e-retailer!
Similar to the saying ‘Call Before You Dig’ we would like to remind all of our customers to ‘Call Before You Upgrade’. A lot of companies are upgrading their ERP systems or adjusting their eCommerce, EDI or CRM applications so that their company can be using the best and most intuitive software available. eBridge Connections is a firm believer in staying on top of innovative technology but when it comes to making upgrades that may affect your integration, you should always call your eBridge Integration Specialist before making any changes. This will ensure that the upgrade does not interfere with your solution because that ends up creating headaches for both us and you.
The aftermath of upgrading without letting your Integration Specialist know beforehand can vary. Sometimes nothing changes and it’s business as usual, but unfortunately, it usually ends with your integration needing some work done so that it can run properly again.
Here are the most common issues eBridge runs into when you make upgrades without letting us know:
- The integration adapters often have a version check, so while there may not be changes at the database level from version to version, upgrading can cause the solution to fail based on this alone
- An old version of Windows or SQL server may not be compatible with the adapter, however, if the ERP officially supports a particular version of Windows or SQL, this shouldn’t be an issue
- If the customer updates and we haven’t released that version of the adapter, they can be production down for several days…or weeks
- If the customer forgets or isn’t aware they have customized their ERP database in a way that required a customized adapter, this could compound the delays
- It’s possible that the integration will appear to work but some of the data fields will not map to the correct location anymore
If you have any questions about your current solution or are planning an upgrade during the new year I advise you to call your eBridge Connections representative right away. This is because if any changes need to be made to your solution, it can be scheduled ahead of time to avoid any down-time or problems with your integration. If you are not sure which representative you should contact about your integration, please email me at firstname.lastname@example.org and I will forward your inquiry to your proper specialist.
CRM Integration, EDI - Our Customers Trading Partner Series, EDI Buyers Guide, EDI Integration, EDI Tips and Tricks, Education, General EDI, Integration, Support, Webstore Integration, eBRIDGE Blog, eCommerce
One of the most common questions we get asked from customers when building them an integration solution between their ERP system and their eCommerce sites is, “How are you going to be able to match data between our platforms?” When matching data between the two platforms, there is no golden rule or single solution. The answer to this question usually varies from integration to integration because it often depends on which ERP system you are using and which eCommerce site you are running. When eBridge Connections deploys an integration, they have to decipher between customer and product information before deciding which data matching approach is the most appropriate.
Since this question of matching data has come up so often, eBridge connections decided to run a webinar which was hosted by our Technical Sales Engineer, Mike Catalfamo. The webinar Best Practices For Matching Data Between Your eCommerce And ERP Systems was presented on December 12th 2012 and it talked about the best practices and considerations customers need to contemplate when matching data between their systems. Mike explained different product (item) and customer complexities that potential customers have to overcome before an integration project starts. He also went through a few examples on how eBridge Connections rectifies these data matching issues.
Here are some approaches Mike discussed during the webinar and some potential caveats eBridge encounters when using these approaches:
|Use cross-reference tables within the ERP||Many ERP systems don’t have this functionality|
|Change the customer numbers in the ERP to match the web store||Usually can’t (or don’t want to) change this value|
|Orphan all customers in the ERP system and create them new in the ERP the first time they order on the web store||Need to maintain customer history in the ERP|
|Use an external cross-reference table to explicitly link the customers||Can be time consuming to set up|
If you follow this link ->Best Practices For Matching Data Between Your eCommerce And ERP Systems you will be able to view the full 20 minute presentation plus a 10 minute question and answer period at the end. If you have any questions about data matching or if you have any other questions regarding an integration project please feel free to email me at email@example.com and I would be happy to discuss these questions with you.
Hello and Good Morning, Here at eBridge we strive to keep our readers and clients up to date on the latest updates and changes from the integration industry. We recently received a notice from the Costco Wholesale EDI department informing us of changes that will be put into effect November 30th. The notice we received read as follows:
Costco Wholesale is currently involved in a project to implement an ERP software solution provided by SAP. Because you are currently an EDI partner with Costco this will impact you as our EDI requirements must change to accommodate the SAP model. Please see the information below for more details regarding the new requirements that must be followed along with our compliance date. Costco’s new requirements:
- Product identification number transmitted on Costco’s 850/860 Purchase Order/Change must be used on your 810 Invoice.
- All Item level discounts (excluding rebates) transmitted on Costco’s 850/860 Purchase Order/Change must be included on your 810 Invoice.
What we need from you: All of the below bolded information transmitted to you on the 850/860 Purchase Order/Change must be included on the 810 Invoice you transmit to Costco Wholesale. This includes the PO number, PO date, PO terms, quantity, price, product identification number (Costco item number, Supplier item number, UPC, GTIN, etc.) and all item level discounts (excluding rebates). Your compliance is required by November 30, 2012. If you are already in compliance, we thank you and no action is required. Thank you for your help in this process. Should you need to contact us please email EDI@costco.com or call our EDI hotline at 425-313-6791. Costco Wholesale EDI Department
As more companies update their current ERP systems or change specific documentation formats, eBridge will continue to update their clients and customers about the changes being made as soon as possible. Please don’t forget that the effective date for these changes is November 30th, 2012. If you require any additional info or clarification, please contact us or leave a comment below.
From time to time Support Services will request a Versions Report for your eBridge software.
Providing the Versions Report ultimately saves us time in troubleshooting the issue you are experiencing with your integration solution.
The Versions Report, amongst other things, allows us to see which Application Adapter is in use, exactly which eBridge components are installed, and where the installation itself is located.
This can be a vital piece of our investigation, and the good news is that it is a relatively simple piece of documentation to retrieve.
Open the Bridge
Navigate to the HELP file menu
From the drop down select BRIDGE VERSION REPORT
Click on the ENVELOPE icon
You will be presented with the option to print the report to a variety of different file formats. Please choose text or .pdf format and then choose the location for the file to be saved to from the LOCATION drop down
The file will be created in the specified format and saved to the exact location specified
I am sure that over time many of our valued eBridge Connections customers will find this to be very useful information.
Our goal in Support is to arrive at prompt resolutions and to maximize the leverage gained through your integration solution. We understand the need to stay competitive in this market, and we fully relate to the fact that your time-spent is an important part of that mix.
If you require any assistance at all, please do not hesitate to call the eBridge Help Desk at 1-800-755-6921.
Our experienced Support Services staff are standing by to guide you through these processes and arrive at positive outcomes.
Take care for now!
eBridge Help Desk Administrator
This week in our Support Services blog we would like to continue our discussion about the most common documents which are exchanged between Support Services and our valued eBridge customers.
Just to re-cap: we have in previous weeks looked at the ‘export only’ function which allows the user to extract the raw data used for the EDI document; and we have also outlined the steps required for retrieving a log report, which details the process the application runs to retrieve and send documents, and highlights any possible errors in the process.
Both sets of documentation are essential for troubleshooting issues you may have with your outbound and inbound profiles; but the most vital documentation required for troubleshooting are the maps!
In EDI, document maps determine what specific business data is to be transmitted between trading partners, and the mapping logic defines exactly how, and under what circumstances, that data should be used. Essentially, the maps provide logic and instruction to the translator based on the agreed-to system and business requirements of each trading partner.
Mapping issues can occur for a variety of reasons: Sometimes your trading partner’s system requirements change; other times the data has undergone some subtle change; and in some cases, accepted EDI protocols have changed. Finally, mapping issues may occur where a business scenario arises which is not covered by the current mapping logic.
Whatever the case has happens to be, if a document fails to process or is rejected by your trading partner, Support Services will almost always request a copy of your current document map, corresponding with the document type you are sending or receiving (orders, invoices, ASNs, etc.).
Retrieving the map is a fairly straightforward process:
The maps reside in the mapper folder. This is typically located at: C:\Program Files\eBridgesoft\eBridge200x\Mapper, for eBridge 2004 and 2006; and C:\Program Files\eBridgesoft\Mapper for eBridge 4.1.
For standard EDI, the map names are based on trading partner, document type, and eBridge application version.
For example: Target, 810 (invoice), Version 4010, would be: TAR81041.map
For ePortal users, the trading partner is most often not specified, as the same document map is used for each trading partner. In this instance, for example, an inbound order map would be labeled ‘850’ and the trading partner with which you are having the issue is inconsequential.
For webstore integration, map names vary and determining the correct map may require some dialogue with Support Services.
That is why we are always here to help!
If you have any issues, mapping or otherwise, please do not hesitate to give me a call at the Help Desk at 905-631-8057 or 1-800-755-6921 ext. 224
Have a great week and I will check in soon!
Help Desk Administrator
eBridge Support Services
This week in our Support blog we will continue to highlight some of the central documents which are exchanged between the eBridge Help Desk and our clients.
Last week we highlighted the importance of the ‘export only’ function, which allows us to view the raw data being sent from your ERP – we use this data to troubleshoot a compromised transmission.
The log report is similarly vital: it tracks the entire process from start to finish and will provide a snapshot of any errors or anomalies which could be halting the process, both inbound and outbound.
If there should ever be an issue with either your inbound or outbound profiles, providing a log report to the Help Desk is a fundamental first step for launching an investigation.
Below are the steps for retrieving a log report:
Open the eBridge application:
Navigate to Reports on the File menu:
Highlight the process that you wish to export:
Double click on the process and the report will appear, click ‘OK’:
Click on the ENVELOPE icon:
You will be presented with the option to print the report to a variety of different file formats. Please choose text or .pdf format and then choose the location for the file to be saved to from the LOCATION drop down. Click ‘OK’:
You are now ready to send the report to firstname.lastname@example.org!
I hope that you have found this information helpful.
Please do not hesitate to contact us if you have any issues with your integration solution.
You can call me directly at 905-631-8057.
Have a great week!
Help Desk Administrator
Over the next few weeks in our Support blog, we would like to highlight and clarify some of the documentation which is typically requested of our valued customers when they log a Support Case with the eBridge Help Desk.
For some, logging a Support Case can be a somewhat stressful exercise, and we take very seriously the fact that we are dealing with our clients’ vital business documents – which can be subject to strict timelines, and involve significant sums of money which are dependent on sound relationships.
We also appreciate that the issues which arise can be fairly technical in nature, and their solutions are oftentimes no less simple. It is because of this fact, however, that our Support Specialists sometimes require a range of technical documentation to troubleshoot an issue and come to a prompt resolution to the satisfaction of you and your trading partner.
One of the main pieces of documentation which is often requested is referred to as an ‘export only’.
An export only is usually requested when there is an issue mapping business data from your accounting package out to your trading partner. Accordingly, an export only is usually only requested if there is an issue with an outbound profile (exporting invoices, purchase order acknowledgements, shipping notices, etc.).
The issue is often caught by our ePortal system, which will recognize non-compliant data and send it to your non-compliant outbox, triggering an email notification which is sent to you informing you of the problem. Secondarily, the issue will sometimes be brought to you by your trading partner. If the relationship is primarily EDI, you will most likely receive an 864 text document indicating a document you sent was non-compliant according to their protocols, or the accepted EDI standards. In other instances, your trading partner will contact you directly via email.
An issue with the data being sent, or the map being used to send it, is usually the culprit; although a document can be rejected for a variety of reasons – including changes in the EDI standards accepted by your trading partner, a change in the business relationship, or changes in taxation, pricing, discounts, and other promotional details which are subject to change.
An export only allows our Support Specialists to view the raw data being sent from your accounting package. This data is evaluated independently for errors or inconsistencies, and it is also compared against the map being used, the data which arrives on ePortal, and the standards insisted upon by your trading partner.
The process for retrieving an ‘export only’ of raw data from your accounting package is quite simple.
The process is executed through the eBridge desktop application through the outbound profile, ‘export only’. Please find the steps below:
- Open the bridge program.
- Choose process from the file menu.
- Select outbound run from the drop down menu.
- You will see a Profile ID dropdown-please select the export only or export profile id.
- Then run the outbound profile.
- Select the document type for the type of documents you wish to export (810, 855, 856, etc.)
- Put in any other criteria you wish for retrieving these documents (date range, trading partner, etc).
- Click the retrieve button.
- You will see your screen start to process and then it will populate with data.
- Please highlight the documents you wish to export.
- Then click export.
- The file will export to C:\Program Files\eBridgesoft\eBridge200x\Data\export.txt – please email this file
This documentation is essential to the troubleshooting required to determine what the issue is and to locate a resolution as quickly as possible.
We hope that you have found this information useful and that you will now have some background on the rationale behind our requests from the Help Desk.
Thank you for reading and make sure to check in next week for more information about the nuts and bolts of your interaction with the Help Desk and Support Services generally.
Take care for now,
Help Desk Administrator