Circles.png

  until the 2018 eoStar User Forum and Technology Conference (August 13-16)
Click here for details

AB BudNet Plugin

From Wiki-eostar.com
Jump to: navigation, search

The ABBudNet Plugin provides data imports and exports for Anheuser-Busch.

For more information, view the AB BudNet Video Tutorials.

eoStar supports importing the following AB files:

  • AB Standard Codes (ABC)
  • National Chain Accounts (NCA)
  • Product Container (PDCN)
  • Purchase Orders (PLN162C)

eoStar supports exporting the following AB files:

  • Inventory (INV)
  • Sales (WID)
  • Pricing (VIPR)
  • Customers (RPF)

AB BudNet Setup

Configuring the BudNet Panel on the Customer Record

AB validates some of the information under the BudNet panel. This information will be populated when the AB Standard Codes (ABC) file is imported, but it can technically be changed using the following process (not recommended).

  1. Go to Records > Customer > Records.
  2. Click on the Customer.
  3. Go to the BudNet panel.
    BN1.png
  4. Check the Is BudNet customer box to include the customer in the BudNet export.
  5. Select the Customer account type.
  6. Select the Chain account status. The assigned chain needs to have a BudNet NCA assigned to it if the chain is a National/Regional chain. Local and Independent chains do not need an NCA code assigned to them.
    • The NCA will need to be set up under Records > Customer > Chains > BudNet panel.
  7. If the customer is a seasonal customer, select the Seasonal open date and Seasonal close date.
  8. Select the Open/closed status.
  9. Select the Consumption type - primary, Consumption type - package, and Consupmption type - draught.
  10. Select the Neighborhood store, Age, Occupation, Race, and Contemp. adult/high end classifications.
  11. Select the Retail account classification.
  12. Select the Licensed account status, Display account status, Point of sale status, Selling method - package, Selling method - draught, Performance pays account status, Industry volume, and Language of owner.
  13. Select any relevant Quick Data information.
  14. Click Post.

Configuring the BudNet Panel on the Product Record

The information on this screen is used for the BudNet exports. AB assigns a unique PDCN to every item in their wholesaler network. When Budnet exports are performed, only items with a PDCN assigned are reported. AB validates some of the information under the BudNet panel.

  1. Go to Records > Product > Records.
  2. Select a Product.
  3. Open the BudNet panel.
    BudNETProductRecordSetup.png
  4. Select the Product container code (PDCN) that corresponds to the selected product.
  5. Click Update product with PDCN data to populate the PDCN information.
  6. Additional PDCNs for the selected product may be managed here:
    a. Select the PDCN.
    b. Click Add.
    c. To delete a secondary PDCN, highlight the row and click Delete selected mapping.
  7. Click Post.

Configuring the BudNet Panel on the Chains Record

The information on this panel is based on the AB National Chain Accounts. AB assigns a unique code for each National/Regional Chain account in their network. This information will be populated when the National Chain Accounts (NCA) file is imported, but it can technically be changed using the following process (not recommended).

  1. Go to Records > Customer > Chains.
  2. Click on the Chain.
  3. Go to the BudNet panel.
    BN3.png
  4. Select the BudNet National Chain Account.
  5. Click Post.

Configuring the BudNet Panel on the Write-Off Reasons Record

The information on this panel assigns AB Transaction Type Codes to Write-Off Reasons. These are used when exporting inventory data to AB so that they have an adequate view of the distributor's inventory.

  1. Go to Records > Product > Write-Off Reasons.
  2. Click on the Write-Off Reason.
  3. Go to the BudNet panel.
    BN4.png
  4. Select the Transaction Type.
  5. Click Post.

Transaction Type Assignments

The following type codes exist in eoStar based on AB's definition for the type:

  • Warehouse Transfer - The movement of product to another wholesaler subject to AB policy. This is not the result of a wholesaler selling product to another wholesaler. This is non-sales movement of beer.
  • Dump - Non-salable beer, not previously written off, which is being disposed of.
  • Spoilage / Breakage - Salable beer which becomes non-salable due to container damage, age, heat, or other environmental factors.
  • Samples - Salable beer for which the customer was not charged.
  • Inventory Hold - Inventory on hold (as instructed by AB) that is not available for sale.
  • Inventory Release - Allows inventory that was previously on hold to be sold.
  • Over / Short - An accounting transaction to adjust inventory when, after the reconciliation process, there is no other explanation for a discrepancy between the book inventory and the physical count.
  • Other - Transactions not covered in one of the above categories, excluding sales and retailer returns.
    • Note: To reduce discrepancies between AB's view of inventory and eoStar's, all write-off reasons should be assigned a BudNet transaction type.

Configuring the BudNet Panel on the Plants Record

Plants can be set up to be automatically assigned to purchases as they are imported from BudNet.

See the BudNet panel on the Plants record for instructions.

BudNet Export

The BudNet Export interface allows the user to export Inventory, Sales, VIPR pricing, and RPF files to BudNet reporting.

  • Inventory - This is sometimes referred to as the INV file. This file reports movement of PDCN associated items within the warehouse via purchases, transfers, write-offs, etc.
  • Sales - This is sometimes referred to as the WID file. This file reports the sales of PDCN associated items to retail.
  • VIPR Pricing - This file reports future pricing information to AB. The data is then validated and provided to national chains like Walmart.
  • RPF - This file contains the Retailer Profile Information that AB requests to be populated for any customer that buys PDCN associated items.

Exporting BudNet Files

  1. Go to File > BudNet > Interface > Export.
  2. Select the file to export at the top:
    • Inventory
    • Sales
    • VIPR Pricing
    • RPF
    BudNETExport1Ver2.png
  3. Select the Warehouse.
    BudNETExport2Ver3.png
  4. Check Item Override to enable a product filter.
    • Not available for the RPF file.
  5. Click Select Products to filter the products included in the export.
  6. Check Include non-BudNET customers to send information on customers not marked for BudNET on the BudNET panel.
    • Only available for the Sales file.
  7. Select the date(s) to export:
    • Target Date - Export information for a specific date.
      • Not available for the RPF file.
    • Date Range - Export information for a specific range of dates.
      • Requires both a From and Thru date.
      • Not available for the VIPR or RPF files.
    • Monthly - Export information for the previous month.
      • Not available for the Sales, VIPR, or RPF files.
  8. Select if the RPF file should include all information or only the changes since the prior file.
    • Changes - Only send information that is new since the prior file was sent.
    • Refresh - Send all information.
    BudNETExport3.png
  9. Use the calendar(s) to select the specific date(s) to run.
  10. Check Report on to roll-up the selected date (or date range) into a specific date.
    • Not available for the VIPR or RPF files.
  11. Use the calendar to select the Report on date.
  12. Check Test Data to mark the file as a test.
    • The Header.TESTPROD field will contain a T (Test) instead of a P (Production).
  13. Click Load to generate and display the results.
  14. Use the Values in selected field search box to filter the results for specific information.
    BudNETExport4.png
  15. Selecting the value from the list will scroll-to and highlight it in the results.
  16. Click Save to create the file.

Viewing the BudNet Export History

The BudNet Export History allows you to view the BudNet exports for a date range. It includes the export date and time, export type, and warehouse.

  1. Go to File > BudNet > Interface > Export History.
  2. Select the From date.
    ABBudNetExportHistory2.jpg
  3. Select the Thru date.
  4. Click Load.
  5. To view details about an export, click on that export in the list.
  6. Click View Selected Export.

BudNet Import

The BudNet Import interface allows the user to import files provided by AB via the Send/Receive client: AB Standard Codes, National Chain Accounts, Product Containers, and Purchase Orders.

  • AB Standard Codes (ABC) - ABCODES.### - These are the valid values for the BudNet RPF export. Importing this file populates all of the fields on the Customer Record BudNet panel.
  • National Chain Accounts (NCA) - NCACODES.### - These are the AB assigned National Chain Accounts. Importing this file populates the values for the NCA selector on the Chains BudNet panel.
  • Product Container (PDCN) - PDCNFILE.### - These are the Product Container values, often referred to as PDCNs. Importing this file populates the values for the PDCN selector on the Product Record BudNet panel.
  • Purchase Orders (PLN162C) - PLN162C-.### - These are Purchase Orders (also known as Order Logs). Importing this file adds purchase orders to the Purchase Tracker.

Importing BudNet Files

  1. Go to File > BudNet > Interface > Import.
    BN8.png
  2. Click Import.
  3. Click Post.

Setting Up Scheduled Tasks for Importing BudNet Files

Rather than performing BudNet tasks manually, they should typically be performed as scheduled tasks. Scheduled tasks automate the process of importing BudNet data. Each of the scheduled events allow you to define the parameters of the events, the time of day and frequency with which they occur.

Go to Records > Scheduled Tasks > Additional Tasks and click on BudNet Import to set up these scheduled tasks. These tasks can be set up to import the following files:

  • PLN162C-51 files - These are Purchase Orders (also known as Order Logs). Importing this file adds purchase orders to the Purchase Tracker.
  • PDCN files - These are the Product Container values, often referred to as PDCNs. Importing this file populates the values for the PDCN selector on the Product Record BudNet panel.
  • NCACODE files - These are the AB assigned National Chain Accounts. Importing this file populates the values for the NCA selector on the Chains BudNet panel.
  • ABCODES files - These are the valid values for the BudNet RPF export. Importing this file populates all of the fields on the Customer Record BudNet panel.

Common Import Issues

If eoStar experiences issues interpreting the data being imported, a message similar to this will appear: The BudNET import has been run. While running, the task detected errors and warnings.

One issue that can cause PLN imports to fail is the detection of duplicated Purchase numbers within the file. When this happens, the message: Invalid line (###): multiple headers for order "#####". If you are running an eoStar version older than v17.9.12.1103, please reach out to your CSM as this issue may be resolved with an upgrade.