Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The import process adds transactions to the AGRIS V9 system.

  • The import process sets a standard format for all reords being imported.

  • The import process is the only way a transaction can be updated in the V9 AGRIS database from outside the application.

...

  • The file name will always be AGEXPIMP, so you will know that it represents a file layout. Go to any package > report manager > select report type > standard reports > look for the file name if AGEXPIMP. That is an export setup to print in exact format of the file layouts for import.

    Image RemovedImage Added
  • The file can be a fixed position file (AGEXPIMP.FIL) where each field must start in an exact position.

  • The file can be a spreadsheet (AGEXPIMP.CSV) where each field gets its own column.

    Package

    Import Description

    Standard Report

    ACP

    VOUCHERS

    A/P VOUCHER EXPORT FILE OR SPREADSHEET

    ACP

    DISBURSEMENTS

    A/P DISBURSEMENT EXPORT FILE OR SPREADSHEET

    ACR

    INVOICES

    INVOICE EXPORT FILE OR SPREADSHEET

    ACR

    PAYMENTS

    A/R PAYMENT EXPORT FILE OR SPREADSHEET

    BNK

    BANK TRANSACTIONS

    BANK TRANSACTION EXPORT FILE OR SPREADSHEET

    GRN

    CONTRACT

    CONTRACT EXPORT FILE OR SPREADSHEET

    GRN

    TICKETS

    COMMODITY TICKET EXPORT FILE OR SPREADSHEET

    GRN

    DELIVERY SHEETS

    DELIVERY SHEET EXPORT FILE OR SPREADSHEET

    GRN

    DISCOUNT TABLES

    DISCOUNT TABLE EXPORT SPREADSHEET

    GRN

    COMMODITY PRICES

    COMMODITY PRICES EXPORT SPREADSHEET

    GRN

    FUTURE PRICES

    FUTURES PRICES EXPORT SPREADSHEET

    GRN

    MARKET BASIS

    MARKET BASIS EXPORT SPREADSHEET

    INV

    INVENTORY FORMULAS

    FORMULA/COMPONENT EXPORT FILE OR SPREADSHEET

    INV

    ORDERS

    ORDER EXPORT FILE OR SPREADSHEET

    INV

    INVENTORY ACTIVITY

    INVENTORY ACTIVITY EXPORT/IMPORT FILE OR SPREADSHEET

    INV

    INVENTORY ITEMS

    INVENTORY ITEM EXPORT FILE OR SPREADSHEET

    INV

    DELIVERY TICKETS

    DELIVERY TICKET EXPORT SPREADSHEET

    INV

    PHYSICAL COUNT

    NONE

    INV

    CUSTOMER CARDS

    CUSTOMER CARDS EXPORT SPREADSHEET

    LDG

    BUDGETS

    NONE

    LDG

    JOURNAL ENTRIES

    JOURNAL ENTRY EXPOR FILE OR SPREADSHEET

    NAM

    NAME/ADDRESS

    NAME/ADDRESS EXPORT FILE OR SPREADSHEET

    ONE

    AUTO ID

    AUTO-ID EXPORT SPREADSHEET

    ONE

    LAST HAULED PRODUCTS

    PRODUCT EXPORT SPREADSHEET

    PAT

    PATRON ACTIVITY

    PATRONAGE ACTIVITY EXPORT FILE OR SPREADSHEET

    PAT

    DISTRIBUTION TRANSACTIONS

    PATRONAGE DISTRIBUTION EXPORT FILE OR SPREADSHEET

    PAT

    PASS THROUGH CREDITS

    NONE

    PAY

    HOURS WORKED

    HOURS WORKED EXPORT FILE OR SPREADSHEET

    PAY

    LABOR DISTRIBUTIONS

    LABOR DISTRIBUTION EXPORT FILE OR SPREADSHEET

    SJI

    EXECUTION SJI

    EXECUTION ID DETAIL SPREADSHEET

    Anchor
    _Toc393291295
    _Toc393291295
    AGRIS > Maintenance > File Layouts for Imports

    Below are the layouts required for importing name address records into the system. The same format is used to accept new name ID's or change existing name ID's. As you review the document below notice the (star), (#) and (warning) notices listed next to each field. These fields will identify / require certain rules when importing those individual data fields of a record.

    Image RemovedImage Added
  • Spreadsheet column or use Positions for fixed files

  • Note the special requirement need flags (look to bottom of layout for definition.

  • Len - represents how large the field can be

  • Type - represents the data type such as number or letter (look to bottom of layout for definition)

  • Comments – special notes about field.

  • Below – Update field/select option – how to only update a single field in a record and protect all other data.

...

  1. oneWeigh station keys in grain tickets all throughout the day.

  2. While the oneWeigh stations is entering tickets a file is being created and appended to for each of the tickets keyed. This is the file you will import.ONE > Setup > Workstation Information > Interface button > Export Files section

  3. At the end of the day or multiple times during the day, this file can be imported to update your live dataset with active tickets.

  4. Note above that there are multiple record types to import from this file.INVT0 tells AGRIS this is a delivery ticket.ACPV0 tells AGRIS this is a stock addition voucher.GRNT0 tells AGRIS this is a grain shipment. The first 5-characters of each record type identify it to AGRIS as to the type of record being imported.It also determines what rules (AGRIS import file layouts) must be meet for this record to import.

  5. You go into AGRIS > Imports > Import Procedures to bring this file and its records into AGRIS.

  6. Note: If you will key an "R" in the "End of Processing Option" AGRIS will provide you a listing of all the possible rejection codes this file could encounter.

  7. When you finally read the file to import, AGRIS will display the number of records and file types that you will be importing.You can say No to each type and leave it in the reject file or yes to import.

  8. The screen for the import of each record type will flash by showing you records read, updated, and rejected.

  9. Once the file is processed and rejects or skips are saved to the Alt. Output File, then you go into the report spool to verify the import and deal with rejections. We are going to focus on the GRN Ticket Import report.

    Image RemovedImage Added
  10. Every import report will show each record read and then there will be a column to tell you what records were rejected, if any.Almost to the bottom of the report will give a summary of the rejection codes.Then at the very bottom the number of records read, skipped, updated, and rejected.So after EVERY import or at the end of EVERY day, you should be reviewing these import reports for rejects. This is why you save them to the spool; to review.

  11. Now we know that there were rejected tickets. C = INVALID OR INACTIVE CUSTOMER NAME/ID NUMBER G = TICKET NUMBER ALREADY s = INVALID OR INACTIVE APPLICATION NAME/ID NUMBERStart with the first code on the list and solve and import it. Usually the codes below it will go away once the first code is solved.

  12. So we'll start with C = INVALID OR INACTIVE CUSTOMER NAME/ID NUMBERTicket 47 rejected due to C and s.The report says BLAY for customer name id.Verify that BLAY is setup in the system by going to name/address and keying in that name id.We find that he is not in our live dataset. Talk to the scale and verify how he got into their system and then decide if he should be added to your system or if the scale used the wrong name id.In this case, he needs to be added to our system. Key in his name id and pertinent information and re-import the reject file.

  13. The re-import of the file showed only 2-rejects now with our Ticket 100-0000047 importing in now that the name id was setup.

  14. Now we move on to the next rejection code.G = TICKET NUMBER ALREADY USEDTickets I-999-0000034 and I-999-0000043 say they are already used and in the AGRIS system.So go verify if these tickets are in the system and if they match the import records.GRN > Shipments > View ShipmentsIn our case we find that the two tickets are in the system. One is a voided transfer and one is an inbound for corn to name id Z89871.So we call the scale and ask what happened with these two.It was concluded that the scale set their document numbers back, so our only option is to key these tickets using control numbers by hand.No import.

...

  1. You complete your work in the outside accounting system.The Store Manager completes their Daily Close.The Energy Force completes their daily invoicing.All of these "end of day" functions create a file that contains information on invoices and payments for customers.(just like the oneWeigh created a file to import)

  2. Process the CFT (Custom File Translation)AGRIS > CFT > Communications or File translation > Process or TranslateWe'll focus on Store Manger

  3. The import is happening behind the scenes.

    Image RemovedImage Added
  4. Even though the import is happening behind the scenes and you do NOT see the record count being added, there is still an import report with records read, skipped, updated, and rejected being created in the report spool.

  5. The A/R Invoice Import Report will show all the rejections and the records that imported.Near the bottom of the report is all the rejection codes.Then the total records read, skipped, added, and Rejected will print at the bottom.

  6. To solve the rejects, start with the first one in the list.B = Invoice Location Code not FoundLooking at the report, we can see that invoice location is V17.Verify if that is setup in the dataset. Correct and re-import.

  7. To re-import, you have to know the file name and location of the rejects.You didn't start the import, it happened behind the scenes. With the CFT imports, each option has its own default of reject file names written into the coding.And the reject files are saved to the dataset folder.For Store Manager, the file the stores_name_yymmdd_hhmmss.fil.The point is that there ALWAYS a reject file. ALWAYS!AGRIS > Reports > Import Procedures > select file and import manually.

  8. Review the report for the next set of rejections.

    Image RemovedImage Added
  9. Take the first one on the list and solve for that rejection.C = BILL TO NAME/ID NUMBER NOT FOUND OR INACTIVESo Bill To Name id "000000018" is not setup in the live dataset or they are using the wrong number in at the store. We are going to set this one up in AGRIS and re-import.Just solve the first rejection code and try again.

  10. Review the import report for the next set of rejections.

    Image RemovedImage Added
  11. Take the first on the list and solve for that rejection.H = ITEM NUMBER NOT FOUND OR INACTIVE So we have 1-invoice rejected because the inventory line items are not in AGRIS.The inventory displays on the report. Verify the items and what they should be.In this case we are going to set them up in AGRIS, Item 100-6002387 the "930-HOOCHIE MAMA ELK CALL" sporting whistle.Just solve the first rejection code and try again.

  12. Review the import report for the next set of rejections in the report spool.

  13. Take the first rejection code on the list.L = Invoice Type Not Found or Blank when required. There are several ways to handle this. (a) remove the requirement. (b) edit the raw data file and fill in invoice type (c) fill in the import default for invoice type in ACR setup (d) Use the Modify function of the import.

...

  • Name the new report something that will be easily identifiable.

    Image RemovedImage Added
  • Value selection criteria page – Selecting account only 90 days or greater by entering a 3 = Greater than.

  • Additional options page – To mark the Print Comments, Product license numbers and relationship info to "N"= No

  • Report Designer Screen (detail line #1) –NAMA1- Adjust the first forty Yes NO flags to all NO except the Sales Credit Limit. (see reference of which field based on column count on the Name Address import File layout report)

...

  1. Once changes are complete you can save and run the new User Defined report and review the results. In this case it is a fast easy adjustment to take all Sales Credit Limits to Zero will be as easy as a drag of the mouse to populate the column with a zero balance.

    Image RemovedImage Added
  2. Once changes are made and reviewed you may now bring save the CSV file and prepare to import using the standard import format found under Reports\ Import Procedures. If you have rejects from this process the following are suggested steps to identify why a rejection occurred.

  3. Review the Name Address import log for rejection codes and reasons.

  4. Double check the number of No's and Yes's are accurate for your import. In the case above the import required a "Y" at the 35th position of the 40 YN's.

...