<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MAPADOC - Sage EDI Solution</title>
	<atom:link href="http://www.mapadoc.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mapadoc.com/blog</link>
	<description>Join in on the discussion</description>
	<lastBuildDate>Wed, 29 Feb 2012 17:42:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Sage ERP X3 &#8211; MAPADOC EDI the Hot Add-on Solution in 2012</title>
		<link>http://www.mapadoc.com/blog/sage-erp-x3-mapadoc-edi-the-hot-add-on-solution-in-2012/</link>
		<comments>http://www.mapadoc.com/blog/sage-erp-x3-mapadoc-edi-the-hot-add-on-solution-in-2012/#comments</comments>
		<pubDate>Wed, 29 Feb 2012 17:42:54 +0000</pubDate>
		<dc:creator>scytron</dc:creator>
				<category><![CDATA[Hellene Thurston]]></category>
		<category><![CDATA[EDI]]></category>
		<category><![CDATA[MAPADOC EDI]]></category>
		<category><![CDATA[Sage EDI]]></category>
		<category><![CDATA[Sage ERP]]></category>
		<category><![CDATA[Sage ERP X3]]></category>
		<category><![CDATA[Sage ERP X3 EDI]]></category>
		<category><![CDATA[Sage X3]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=619</guid>
		<description><![CDATA[Sage ERP X3 – The new way to ERP, is looking to make 2012 another great year for this mid-market/upper mid-market ERP solution.  After an amazing 2011, our SWK Technologies Sage ERP X3 team is excited to share several new add-on solutions for our existing and future clients. These new add-on solutions are just the [...]]]></description>
			<content:encoded><![CDATA[<p><a title="Sage ERP X3" href="http://www.swktech.com/products/erp-accounting/sage-erp-x3">Sage ERP X3</a> – The new way to ERP, is looking to make 2012 another great year for this mid-market/upper mid-market ERP solution.  After an amazing 2011, our SWK Technologies Sage ERP X3 team is excited to share several new add-on solutions for our existing and future clients.</p>
<div>
<p>These new add-on solutions are just the beginning to what will hopefully be many new extensions offered by SWK and other solution providers in the coming years.  Today, SWK is thrilled to offer the next level in the area of EDI, Business Intelligence Reporting, and Document Management. In this blog we wanted to speak to you only about MAPADOC EDI for Sage ERP X3.</p>
<p>MAPADOC EDI for Sage ERP X3</p>
<p><a href="http://www.mapadoc.com/">MAPADOC EDI</a> is now available for Sage ERP X3; in fact, MAPADOC for Sage ERP X3 adds a fully functional EDI suite to the standard application tools.</p>
<p>MAPADOC EDI for Sage ERP X3 is designed for companies that have anywhere from moderate to sophisticated EDI requirements, and allows any level of transaction volume to be more easily managed. MAPADOC EDI for Sage ERP X3 is built on the X3 SAFE development platform, so it seamlessly integrates to the application.<strong> </strong>As a result, even smaller or lower-volume EDI environments can benefit from a greater ease of use and faster processing times. In addition, MAPADOC EDI for Sage ERP X3 is a fully integrated EDI solution that sits inside Sage ERP X3 product.</p>
<p>As always, MAPADOC EDI can help you mange your EDI requirements when using Sage ERP X3, Sage MAS 90, Sage MAS 200, Sage MAS 500, Sage 100 ERP, and Sage 500 ERP.  For more information on our MAPADOC EDI solutions, call Hellene Thurston at (866) 627-2362 extension 137.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/sage-erp-x3-mapadoc-edi-the-hot-add-on-solution-in-2012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What’s New With MAPADOC</title>
		<link>http://www.mapadoc.com/blog/what%e2%80%99s-new-with-mapadoc/</link>
		<comments>http://www.mapadoc.com/blog/what%e2%80%99s-new-with-mapadoc/#comments</comments>
		<pubDate>Thu, 19 Jan 2012 13:00:18 +0000</pubDate>
		<dc:creator>Marthe Chensel</dc:creator>
				<category><![CDATA[Marthe Chensel]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=613</guid>
		<description><![CDATA[There is a new release for MAPADOC version 4.40 (4.40.10) &#38; 4.50 (4.50.01). This release includes these additions: 810 In: Create PO Invoices &#8211; NEW item cost mismatch reporting This option was modified to report differences between the cost on the PO and the cost on the incoming invoice. Picking Sheet Printing (MAPADOC enhanced version) [...]]]></description>
			<content:encoded><![CDATA[<p><strong>There is a new release for MAPADOC version 4.40 (4.40.10) &amp; 4.50 (4.50.01). This release includes these additions:</strong></p>
<p><strong> </strong></p>
<p><strong>810 In: Create PO Invoices &#8211; NEW item cost mismatch reporting</strong><strong> </strong></p>
<p>This option was modified to report differences between the cost on the PO and the cost on the incoming invoice.</p>
<p><strong> </strong></p>
<p><strong>Picking Sheet Printing (MAPADOC enhanced version) &#8211; New Customer PO selection criteria</strong><strong> </strong></p>
<p>This option was modified to add Customer PO as an available selection field.</p>
<p><strong> </strong></p>
<p><strong> </strong></p>
<p><strong>Coming soon in the next releases:</strong></p>
<p><strong> </strong></p>
<p><strong>Select EDI Invoices from History, Select Invoices to Consolidate, and Select EDI 850 Purchase orders – selection criteria now mandatory</strong><strong> </strong></p>
<p>These options will be modified to ensure at least one selection criteria value has been entered before documents can be selected.</p>
<p><strong>ASN Mapping – NEW fields available in mapping</strong></p>
<p>This option will be modified to allow mapping from all Sales Order Header and Sales Order Detail fields. Currently, only UDFs are available for mapping from these files.</p>
<p><strong> </strong></p>
<p><strong>Receive Inbound EDI and All Outbound Document Creation options &#8211; FTP directory to exception report</strong><strong> </strong></p>
<p>These options will be modified to add the FTP directory being used to the exception report (if using MAPADOC FTP options).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/what%e2%80%99s-new-with-mapadoc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>2012: What’s Hot for EDI?</title>
		<link>http://www.mapadoc.com/blog/2012-what%e2%80%99s-hot-for-edi/</link>
		<comments>http://www.mapadoc.com/blog/2012-what%e2%80%99s-hot-for-edi/#comments</comments>
		<pubDate>Thu, 12 Jan 2012 13:00:44 +0000</pubDate>
		<dc:creator>James Payne</dc:creator>
				<category><![CDATA[EDI]]></category>
		<category><![CDATA[Jimmy Payne]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=606</guid>
		<description><![CDATA[Data Volume Buyers and suppliers will be reviewing EDI data to plan for the 2012 season. EDI providers will be offering solutions, one being an 852 product sales activity report. 852 data can give weekly sales and inventory by SKU, sell thru and supply on hand. For example, if you are in fashion, you can [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Data Volume</strong></p>
<p>Buyers and suppliers will be reviewing EDI data to plan for the 2012 season. EDI providers will be offering solutions, one being an 852 product sales activity report. 852 data can give weekly sales and inventory by SKU, sell thru and supply on hand. For example, if you are in fashion, you can see how well your units sold by style, color or size between retail stores. You can also view which parts of the country are driving your sales to increase. With the successful 2011 season, suppliers have gained confidence to do more and increase their data visibility.</p>
<p><strong>Out With the Old, In with the New</strong></p>
<p>EDI providers will need to increase their integration capabilities due to ERP software upgrades and switches. With some ERP software providers, support will cease for old systems, forcing a shift in the market. Moving data from one system to another, while keeping up with current EDI transactions, will be a challenge. The right EDI system with flexibility and a proven support team will make these changes be less painful.</p>
<p><strong>Faster Sales Cycle</strong></p>
<p>With increased sales and higher EDI transaction volumes, suppliers are always looking to reduce steps for a faster order to cash flow. Rip and read manual entries are common with growing companies and can be very costly due to the nature of human errors. The right EDI solution will significantly reduce the steps to process multiple line items EDI Purchase Orders, ASNs (Advance Ship Notices) and Invoices. In some cases a 50% to 70% reduction of time spent processing orders is plausible.</p>
<p><strong>MAPADOC</strong></p>
<p><a href="http://www.mapadoc.com" target="_blank">MAPADOC</a> is a powerful, flexible, yet remarkably easy to use EDI software solution built especially for Sage MAS 90, Sage MAS 200, Sage MAS 500 and Sage ERP X3. Since it&#8217;s a scalable solution, you can start at any point and add the functionality you need – when you need it. No matter what the trend, MAPADOC is the right EDI solution for your business.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/2012-what%e2%80%99s-hot-for-edi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New MAPADOC Release for MAS 90/200 4.40</title>
		<link>http://www.mapadoc.com/blog/new-mapadoc-release-for-mas-90200-4-40/</link>
		<comments>http://www.mapadoc.com/blog/new-mapadoc-release-for-mas-90200-4-40/#comments</comments>
		<pubDate>Thu, 01 Dec 2011 13:00:24 +0000</pubDate>
		<dc:creator>Marthe Chensel</dc:creator>
				<category><![CDATA[Marthe Chensel]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=602</guid>
		<description><![CDATA[There is a new release for MAPADOC version 4. 40 (4.40.10).  This release includes the following changes/fixes/additions: 11/21/2011 &#8211; Ship To Address Lookups &#8211; correction for Sage Product Update 6 The Ship to Address Lookups in the following tasks were corrected to work with the PU 6 lookup change: Ship To Cross Reference, ASN Selection, [...]]]></description>
			<content:encoded><![CDATA[<p>There is a new release for MAPADOC version 4. 40 (4.40.10).  This release includes the following changes/fixes/additions:</p>
<p><strong>11/21/2011 &#8211; Ship To Address Lookups &#8211; correction for Sage Product Update 6</strong></p>
<p>The Ship to Address Lookups in the following tasks were corrected to work with the PU 6 lookup change: Ship To Cross Reference, ASN Selection, and Master Bill of Lading Selection.</p>
<p><strong>11/10/11 &#8211; Label Printing &#8211; Warehouse address fields</strong></p>
<p>Label printing has been modified to correctly print the warehouse name and address fields.</p>
<p><strong>10/13/11 &#8211; Sales Journal Update &#8211; Factor Invoice Selection correction</strong></p>
<p>This option has been modified to correct factor invoices not being selected properly.</p>
<p><strong>10/04/2011 &#8211; ASN Selection/ASN Auto Select &#8211; PRO Number/tracking number</strong></p>
<p>These options have been modified to correct the PRO Number not being filled with the tracking number from Shipping Data Entry properly if the first package assigned to the invoice was not Package &#8220;0001.&#8221;</p>
<p><strong>09/10/2011 &#8211; Edit Order Package &amp; Label Data &#8211; Over-shipping</strong></p>
<p>This option has been modified to allow a new case to be created if all of the items have been packed AND the option to allow over shipments is checked.</p>
<p><strong>08/10/2011 &#8211; 810 In: Create PO Invoices &#8211; NEW item cost mismatch reporting</strong></p>
<p>This option has been modified to report differences between the cost on the PO and the cost on the incoming invoice.</p>
<p><strong>08/09/2011 &#8211; 810 In: Create PO Invoices &#8211; Invoice Due Date assignment correction</strong></p>
<p>This option has been modified to correct the invoice due date being recalculated if populated from the map/EDI data.</p>
<p><strong>08/09/2011 &#8211; Trading Partner Setup options &#8211; TP Exceeded message</strong></p>
<p>All Trading Partner Setup options have been modified to correct the &#8220;Number of TP Exceeded&#8221; message if more than 9,999 trading partners are set up.</p>
<p><strong>08/05/2011 &#8211; Picking Sheet Printing (MAPADOC enhanced version) &#8211; New Customer PO selection criteria</strong></p>
<p>This option has been modified to add Customer PO as an available selection field.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/new-mapadoc-release-for-mas-90200-4-40/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Retailer Compliance News</title>
		<link>http://www.mapadoc.com/blog/retailer-compliance-news/</link>
		<comments>http://www.mapadoc.com/blog/retailer-compliance-news/#comments</comments>
		<pubDate>Thu, 03 Nov 2011 13:00:10 +0000</pubDate>
		<dc:creator>mapadocweb</dc:creator>
				<category><![CDATA[EDI]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=596</guid>
		<description><![CDATA[Family Dollar Notification of EDI Translator Change for Family Dollar – October 2011 During October 2011, the Family Dollar eCommerce Team is converting our existing EDI translator to the new IBM/Sterling Integrator 5.1. The conversion will require minimal changes from the partner community. The new platform and version will provide Family Dollar with greater throughput [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Family Dollar</strong></p>
<p><strong>Notification of EDI Translator Change for Family Dollar – October 2011</strong></p>
<p><strong> </strong>During October 2011, the Family Dollar eCommerce Team is converting our existing EDI translator to the new IBM/Sterling Integrator 5.1. The conversion will require minimal changes from the partner community. The new platform and version will provide Family Dollar with greater throughput and reporting capacity required to support the increasing transaction volume. Please read below to determine if any action is required on your behalf to successfully complete the migration.</p>
<p><strong>If you utilize a VAN or 3rd Party Processing Service</strong> (SPS, Edict, TrueCommerce, etc.): For partners who utilize a VAN or other 3rd party service, there is <strong>no change</strong> required to complete the migration to the new Family Dollar system. We do ask partners to be vigilant in monitoring for expected transactions and 997 acknowledgments during this period.</p>
<p><strong>If you have Direct AS2 Communication with Family Dollar</strong>: For partners with a direct AS2 connection to Family Dollar, our communication team will coordinate connectivity testing to the new production system. The conversion will <strong>require a new URL</strong> and the installation of a <strong>new certificate</strong>.</p>
<p><strong>Questions or Concerns?</strong> Please feel free to reach out to the EDI team for any questions or concerns you may have: <a href="mailto:EDI@Familydollar.com">EDI@Familydollar.com</a></p>
<p>We will continue to send updated communications to inform you of the conversion status throughout the migration period. Thank you for your continued support of the Family Dollar eCommerce initiatives.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/retailer-compliance-news/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ALLiGACOM and SWK Technologies Partner to Offer Best-of-Breed End-to-End EDI Solution</title>
		<link>http://www.mapadoc.com/blog/alligacom-and-swk-technologies-partner-to-offer-best-of-breed-end-to-end-edi-solution/</link>
		<comments>http://www.mapadoc.com/blog/alligacom-and-swk-technologies-partner-to-offer-best-of-breed-end-to-end-edi-solution/#comments</comments>
		<pubDate>Thu, 27 Oct 2011 13:00:41 +0000</pubDate>
		<dc:creator>scytron</dc:creator>
				<category><![CDATA[Gary Berman]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=591</guid>
		<description><![CDATA[ALLiGACOM, a leading Supply Chain Management solution provider with a cloud-based EDI integration environment for ERP platforms and business applications announced today a partnership with SWK Technologies Inc., a Sage gold-certified development partner and an award-winning Sage business partner for more than 20 years. ALLiGACOM will become one of SWK’s managed EDI partners for SWK’s [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.alligacom.com" target="_blank">ALLiGACOM</a>, a leading Supply Chain Management solution provider with a cloud-based EDI integration environment for ERP platforms and business applications announced today a partnership with SWK Technologies Inc., a Sage gold-certified development partner and an award-winning Sage business partner for more than 20 years.</p>
<p>ALLiGACOM will become one of SWK’s managed EDI partners for SWK’s award-winning <a href="http://www.mapadoc.com" target="_blank">MAPADOC EDI</a> solution, which currently integrates with Sage ERP MAS 90, Sage ERP MAS 200, Sage ERP MAS 500 and Sage ERP X3.</p>
<p>“ALLiGACOM was a logical partner for us because they offer complementary cloud technology and committed global support for our Sage ERP X3 customers and partners,&#8221; said Andrew M. Nunez, Executive Vice President of Sales for SWK Technologies, Inc. &#8220;Our Sage ERP X3 customers can benefit from ALLiGACOM’s cloud network while leveraging MAPADOC, a premier integrated EDI solution for Sage’s mid-market ERPs.”</p>
<p>“We are very pleased to partner with SWK Technologies. This partnership furthers ALLiGACOM’s overall channel position globally; SWK’s aggressive business development initiatives are in line with ALLiGACOM’s continued growth strategy”, highlights Jacques Vigneault, Vice-President Sales &amp; Marketing at ALLiGACOM.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/alligacom-and-swk-technologies-partner-to-offer-best-of-breed-end-to-end-edi-solution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EDI Going Mobile</title>
		<link>http://www.mapadoc.com/blog/edi-going-mobile/</link>
		<comments>http://www.mapadoc.com/blog/edi-going-mobile/#comments</comments>
		<pubDate>Thu, 20 Oct 2011 13:00:55 +0000</pubDate>
		<dc:creator>garyberman</dc:creator>
				<category><![CDATA[EDI]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=586</guid>
		<description><![CDATA[Moving EDI data around the globe is old hat to most of the folks reading this ec-bp newsletter. Managing the connections and translations can get complex and picky when it comes to the details of the files and the changes that need to be incorporated into translators to make processes flow properly. For most EDI [...]]]></description>
			<content:encoded><![CDATA[<table border="0" cellspacing="15" cellpadding="0" align="center">
<tbody>
<tr>
<td>
<table border="0" cellspacing="0" cellpadding="0" align="center">
<tbody>
<tr>
<td>
<table border="0" cellspacing="10" cellpadding="0">
<tbody>
<tr>
<td>Moving EDI data around the globe is old hat to most of the folks reading this ec-bp newsletter. Managing the connections and translations can get complex and picky when it comes to the details of the files and the changes that need to be incorporated into translators to make processes flow properly. For most EDI practitioners, their roles are fairly well defined and fit well with established concepts. But as computing devices become more pervasive and processing power more available, I think the line between what is EDI and what is associated with end user interaction is changing.&nbsp;</p>
<p>Our survey about using portable devices from a couple months ago indicated some interesting trends. Like the rest of the population, the majority (76%) of respondents indicated that they carried some kind of smart phone or tablet with them when they were away from their work location. That means that those folks have at least the capacity to access their data and applications if it were important to do so.</p>
<p>At the same time, 88% indicated that they did not connect to their supply chain systems using these devices. It could be that they never found it necessary to do so, or that they didn&#8217;t want to be bothered with work issues while they were away. But I believe the issue has more to do with having the proper applications in place to easily and quickly connect to their systems.</p>
<p>In fact, the survey asked respondents if they thought their mobile devices would be good tools to connect to their EDI systems, and 51% indicated that if a appropriate application were available, they would make use of it. Interestingly, an additional 28% said that if their EDI systems were Internet-based, they would access them via their portable devices. Taken together, 79% would consider accessing their supply chain systems if they had access to the proper tools.</p>
<p>But is there really a reason to extend access beyond the company firewall? If every transaction processes correctly, and all systems work as they should, there is little reason to access these systems. But the reality is that there are always issues to be managed. 68% of respondents to his survey said yes to the question, &#8220;Do you believe there are advantages to accessing EDI/supply chain information when you&#8217;re away from your desk?&#8221;</p>
<p>As mobile apps become more commonplace, forward thinking EDI providers and the companies that use them will see the demand for these apps from their users. Even if the apps deliver low levels of functionality for status checking and minor management tasks, not having these extensions to their systems will eventually be seen as missing features.</p>
<p>Source: Scott Koegler, <a href="http://www.ec-bp.org/" target="_blank">ec-bp eCommerce Best Practices</a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/edi-going-mobile/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>816 Organizational Relationship (Store Listings)</title>
		<link>http://www.mapadoc.com/blog/816-organizational-relationship-store-listings/</link>
		<comments>http://www.mapadoc.com/blog/816-organizational-relationship-store-listings/#comments</comments>
		<pubDate>Thu, 13 Oct 2011 13:00:57 +0000</pubDate>
		<dc:creator>garyberman</dc:creator>
				<category><![CDATA[Gary Berman]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=581</guid>
		<description><![CDATA[The 816 Organizational Relationship Integration for MAPADOC Sage ERP MAS 90 and 200 allows companies to update or add ship-to locations to the AR Customer Master ship to files. The integration will handle two types of 816 documents: Store Listings and DC/Store Relationship Listings. Store Listings will be used to add new ship-to codes to [...]]]></description>
			<content:encoded><![CDATA[<p>The 816 Organizational Relationship Integration for MAPADOC Sage ERP MAS 90 and 200 allows companies to update or add ship-to locations to the AR Customer Master ship to files.</p>
<p>The integration will handle two types of 816 documents: Store Listings and DC/Store Relationship Listings. Store Listings will be used to add new ship-to codes to the system or update existing ones. Store Listing processing will also add cross-reference records if this customer is using a ship-to cross-reference table. If the end user has each store location set up as a different customer in AR, this integration will set up each store location as its own customer. The DC/Store Relationship listing will be used to update existing ship to codes with their corresponding DC (either using the UDF_DC or the fax number field).</p>
<p>The 816 setup options will allow the user to enter the next 4-digit ship-to code to be used, which will be incremented each time a new to location is added. If the user has each store location setup as its own AR account, the set up options will allow the user to enter a 3-digit customer number prefix. This will be used to assign the customer number. The 3-digit prefix assigned, combined with the 4-digit store number assigned, will be the new AR account number.</p>
<p>During processing, a report will be generated detailing the changes and/or additions made. We currently have clients using this document for their Walmart and BBB trading partners.</p>
<p>For more information contact <a href="mailto:gary.berman@swktech.com">Gary Berman</a> or call 973.758.6104.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/816-organizational-relationship-store-listings/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ask Tina &#8211; Invoices Via EDI</title>
		<link>http://www.mapadoc.com/blog/ask-tina-invoices-via-edi/</link>
		<comments>http://www.mapadoc.com/blog/ask-tina-invoices-via-edi/#comments</comments>
		<pubDate>Thu, 29 Sep 2011 13:00:16 +0000</pubDate>
		<dc:creator>Tina Zak</dc:creator>
				<category><![CDATA[Tina Zak]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=574</guid>
		<description><![CDATA[Q &#8211; Is it possible to send invoices via EDI if the orders were faxed to us? A &#8211; Yes, it is possible. First determine whether or not the invoice (810) map is using user defined fields (UDFs). If your 810 map is using UDFs these fields will be missing from the 810 document. The [...]]]></description>
			<content:encoded><![CDATA[<p>Q &#8211; Is it possible to send invoices via EDI if the orders were faxed to us?</p>
<p>A &#8211; Yes, it is possible. First determine whether or not the invoice (810) map is using user defined fields (UDFs). If your 810 map is using UDFs these fields will be missing from the 810 document. The UDFs will need to be created in custom office in either the sales order header or sales order detail sections. Then the UDF&#8217;s will need to be placed on the sales order entry screen through customizer in custom office on the appropriate screen (either detail or header). When manually entering the sales order, these fields will need to be filled in as well.</p>
<p>For example, if you need the customer&#8217;s SKU number on the invoice. You would create a sales order detail UDF called SKU, this would be set up as a multi line string with 30 digits. Add this field to the sales order detail (line) screen. Enter the sales order, enter the line item. With the line item highlighted, enter the SKU number in the new SKU UDF spot on the order entry form. This SKU number will now be available to the invoice (810).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/ask-tina-invoices-via-edi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Backing Up Your System</title>
		<link>http://www.mapadoc.com/blog/backing-up-your-system/</link>
		<comments>http://www.mapadoc.com/blog/backing-up-your-system/#comments</comments>
		<pubDate>Thu, 22 Sep 2011 13:00:32 +0000</pubDate>
		<dc:creator>Tina Zak</dc:creator>
				<category><![CDATA[Tina Zak]]></category>

		<guid isPermaLink="false">http://www.mapadoc.com/blog/?p=569</guid>
		<description><![CDATA[When backing up your MAS system, name the backup alpha-numerically after your live company code to avoid having your incoming documents go into the backup company by mistake. MAPADOC searches through the available company codes listed in alpha numerical order, if you name the company something before the live company, all data will go to [...]]]></description>
			<content:encoded><![CDATA[<p>When backing up your MAS system, name the backup alpha-numerically after your live company code to avoid having your incoming documents go into the backup company by mistake. MAPADOC searches through the available company codes listed in alpha numerical order, if you name the company something before the live company, all data will go to the other/backup company.</p>
<p>For example: Your live company code is MAP and you want to copy all company files to a backup for the end of 2005. If you use company code ABC, all EDI files will go to ABC company code. Name it anywhere between MAQ &#8211; ZZZ and this problem will not arise. If you do need to name the company code something before your live company, you must go into MAPADOC/Setup/Customer Trading Partner Maintenance and remove all inbound interface IDs for each of your trading partners.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mapadoc.com/blog/backing-up-your-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

