Frequently Asked Questions on logistics

Dat_Aan de slag met AFAS Online (Startpagina) (10)

Stock

 

 

 

 

Message: An RC sales cost price was not entered for the Stock integration type

The message appears because you are tracking the stock in administration A but journalising this invoice/packing slip in administration B.
For this, you must set up the integration (for stock) between the two administrations. This is because the financial entries must in fact end up in the correct administration.

Solution:

  • For integration type 7 (Stock in admin. A) you must enter an account for CA sales cost price.

    The is for the CA sales cost price entry TO Geleverde artikelen in administration A.

  • You must enter integration type 13 (Voorraad Rekening Courant) for the entries in admin. A with a CA sales cost price.

    This is for the Kostprijs verkoop entry TO CA sales cost price in administration A.

See also:

  • Configure integration types for multiple administrations, one of which with stock

Extra:

Do you believe that the message was given in error? If so, then check your configuration and procedure:

  1. View the Stock overview. If data comes from this, then you are working with stock.
  2. In the properties of the article, check that the Track stock check box is selected.
  3. Check that the Contains stock items check box is selected in the article group properties.
  4. Check that Stock and/or Journalise stock have been activated. You check this from the Activation tab in the properties of the environment.
  5. If it appears that you are working with stock, then you must adjust the configuration. If not, then submit an incident.

See also:

  • Change the integration type

The journal entry of the stocktaking (stock entry) has the system date as the entry date. Can I enter this date myself?

The message appears because you are tracking the stock in administration A but journalising this invoice/packing slip in administration B.
For this, you must set up the integration (for stock) between the two administrations. This is because the financial entries must in fact end up in the correct administration.

Solution:

  • For integration type 7 (Stock in admin. A) you must enter an account for CA sales cost price.

    The is for the CA sales cost price entry TO Geleverde artikelen in administration A.

  • You must enter integration type 13 (Voorraad Rekening Courant) for the entries in admin. A with a CA sales cost price.

    This is for the Kostprijs verkoop entry TO CA sales cost price in administration A.

See also:

  • Configure integration types for multiple administrations, one of which with stock

Extra:

Do you believe that the message was given in error? If so, then check your configuration and procedure:

  1. View the Stock overview. If data comes from this, then you are working with stock.
  2. In the properties of the article, check that the Track stock check box is selected.
  3. Check that the Contains stock items check box is selected in the article group properties.
  4. Check that Stock and/or Journalise stock have been activated. You check this from the Activation tab in the properties of the environment.
  5. If it appears that you are working with stock, then you must adjust the configuration. If not, then submit an incident.

See also:

  • Change the integration type

 

 

 

 

Dat_Aan de slag met AFAS Online (Startpagina) (40)

Sales

 

 

 

Message: Report not found

This message is shown if in the sales contact profile you did not link a report, or if you linked the wrong report or one that does no longer exist. In order to resolve the cause of the message, link the correct report for the (draft) invoice, purchase order, sales order and/or packing slip in the sales contact profile.

Detailed message:
======================================================================

Number.................: -2147202898 #800448AE [ANTA]
Description............: An error has occurred while running the report
Init state.............: Raised
Source.................: AntaReportGen
Version................: 8.400.300
Location...............: C:\Program Files (x86)\Profit\AFAS Windows\Kernel\Bin
Source descr...........: ANTA Report Generator (C/S)
Time...................: 13-05-2013 17:25:16.570
DLL/EXE file...........: AntaReportGen
Session................: AOL\35217.ADMIN on AOL\TSNL023 (TS)
-----------------------
Landmark...............: AntaReportGen.Report.PrepareFromID [042B0B0C]
PAR: parReportId.......: DC1A53114BBBB3C455DB9EA245127D03
-----------------------
Landmark...............: AfasFbCeWizardFunc.PrintProvExecute [6ECC1ECD]
etc.

======================================================================

Description..........: [ANTA WARNING]
Init state...........: Raised
Source...............: AntaRprt
Version..............: 8.400.100
Location.............: C:\Program Files (x86)\Profit\AFAS Windows\Kernel\Bin
Source descr.........: ANTA Report (C/S)
Time.................: 13-05-2013 17:25:16.555
DLL/EXE file.........: AntaRprt
Session..............: AOL\_ProfitComNL on AOL\TSNL023 (NoTS)
---------------------
WARN.................: Report not found in database: DC1A53114BBBB3C455DB9EA245127D03
Landmark.............: AntaReport.ASOMain.ReadDocumentData [672F0DB2]
PAR: parReportID.....: DC1A53114BBBB3C455DB9EA245127D03
---------------------
etc.


See also

  • Sales contact profile

 

 

Message during journalising: Value entered for the Account number field does not occur in the environment

Depending on what you are journalising, you must check the integration types:

  • If you journalise project invoices, then check the Automatic project invoice integration type.
  • If you journalise logistics sales invoices and stock, then check the Stock and Logistics sales invoices integration types.

This message can appear for the following reasons:

  • In the integration types, one of the entered ledger accounts is incorrect, has not been completed or does not exist (anymore).
  • In the properties of the article group, one of the entered ledger accounts is incorrect, has not been completed or does not exist (anymore).
  • In the Stock integration type, the settlement account field is not completed.
    Example: you create invoices in administration 3, but the stock is tracked in adm. 1.

In the detailed message of the error message, you can view the account number in question. You must change this account number to a correct account number.

See also:

  • Change the integration type
  • View/change an article group

 

Can I change the decimal places for the price or the price list?

You can change the number of decimal places in the price in the currency.

Note: 

Once you have changed the number of decimal places for the currency, you cannot change it back! Even if you have not made any entries at all yet. However, you can delete the currency if there have not been any entries and then add another currency with a different number of decimal places.

 

Message: No valid lines found to copy the order over

Message:

No valid lines found to copy order ‘123444’ over.

You get this message, for instance, when you create a packing slip from the sales orders.

Troubleshooting:

The message could have the following causes:

  1. There is an actual stock shortage.
  2. There is in fact stock, but a warehouse without stock is indicated on the line.
  3. The article for the sales order is in a pending order.
  4. The article/assembled item goes through the order proposal (purchase process).
  5. The sales order has an assembled item and it must be assembled first before you can deliver it.

You can read the possible solutions for each cause below.

 

A. There is actually a stock shortage.

  1. Go to: Order Management / Item / Article.
  2. Open the properties of the article.
  3. Go to the tab: Stock overview.
  4. Check the amount of stock.

    It may be that more articles are reserved (by a sales order/assembly preparation) than are in stock.

    Here, take the following into account:

    For the debtor for whom the sales order was created, it is indicated that the sales order must be delivered in full. If the delivery condition is set to Deliver line completely or Deliver order completely and there is not enough stock to deliver the entire order line/order, then the following message appears:

    See also: Allow short-supplies for a sales contact

    Solution:

    In the existing sales order, if applicable, you can deviate from these settings by including the Delivery conditions field in the header of the entry layout.

    See also: Deviate from the delivery condition for each sales order

    The order may be for an assembled item, rather than an article. For an assembled item, the above description also applies. From Logistics / Item / Assembled item, action Assembled item information / tab Stock overview, you can see the number of articles in stock.

     

B. In the header/line of the sales order, you selected a warehouse other than the one where the stock is located.

  1. Go to: Order Management / Item / Article.
  2. Open the properties of the article.
  3. Go to the tab: Stock overview.
  4. Check which warehouse the stock is located in.

    If a different warehouse is selected for an order and there is no stock at that warehouse, then the following message appears:

    Solution:

    Delete the order line from the order and add a new line with the correct warehouse

    Or, if the stock was entered on the wrong warehouse, then transfer the stock entry to the correct warehouse.

    In the case of an assembled item:

    1. Go to: Order Management / Item / Assembled item.
    2. Open the properties of the assembled item.
    3. Click on the action: Assembled item information.
    4. Go to the tab: Stock overview.
    5. Check the stock of the assembled item for each warehouse.

3. The article for the sales order is in a pending order.

This depends on a number of settings and conditions. You can read more on this from the links below. You should read all of these links through carefully so you know how pending orders work. It also describes how to deactivate the pending order:

  • Pending order
  • Configure a pending order
  • Backorder line

4. The article/assembled item goes through the order proposal (purchase process)

  1. Go to: Order Management / Item / Article.
  2. Open the properties of the article.
  3. Go to the tab: Order proposal.
  4. In Order proposal with sales, enter whether the order line should go through the purchase order in certain situations.
    For the assembled item, you can set this from Order Management / Item / Assembled item, assembled item properties / Order proposal tab.

    See also:
    • Order proposal and stock check
    • Set up an order proposal line from a sales order
    • Set up a Sales entry layout for an Order proposal

5. The sales order has an assembly/assembled item which must be assembled first before you can deliver.

This is based on the setting in the Stock replenishment method  field.

  1. Go to: Order Management / Item / Article.
  2. Open the properties of the article.
  3. Go to the tab: Order proposal.

    See also:

    • Create an assembly proposal

Can I correct an invoice that was entered with the wrong entry date?

After the invoices and credit notes have been journalised in the accounting, you can no longer change or delete them.

If you still want to change the entry date, for instance, then you must credit the relevant invoice. Next, you add a positive invoice manually. You can then journalise the invoices. Here, pay careful attention to the entry date that you entered during both of the journalising operations.

The packing slips are not being collected, how can I do that?

If packing slips are not getting collected, this may have several causes:

  • Invoices added manually are never collected. Only with automatic generation does Profit collect packing slips/different invoices on a single invoice for a sales contact. In this case, collection must in fact be configured in the sales contact profile.
  • The packing slips/invoices must also meet a number of conditions. Check these.

 

 

 

 

 

 

Dat_Aan de slag met AFAS Online (Startpagina) (40)

Other

 

 

Message when printing a report: En error occurred while running the report/Can’t run report. PageHeader/Footer height is larger than page height?

This message is shown because the report is outside the printing range. This can have two causes:

  • The page settings of your report are incorrect

    Check the format, the print orientation and the margins of the report.

  • Incorrect printer settings

    This message can be displayed if the (margin) settings for your printer are incorrect. Solve this problem by setting another printer as the default printer or by modifying the settings of your printer so that it can work with the margins specified in the report. Refer to the printer documentation or to information about this Active Report message via this link.

    Note:

    The AFAS Support Centre does not provide support for the configuration of reports and analyses, because each AFAS contact can configure his own custom layout. For assistance in configuring reports or analyses, please contact your consultant. If you do not know who your consultant is or if you do not know his telephone number, please contact the Custom Service department at: 033 43 43 881.

     

Detailed message:
Number..........: -2147202898 #800448AE [ANTA]
Description.....: An error has occurred while running the report
Init state......: Raised
Source..........: AntaRpEn
Version.........: 7.500.100

Location........: C:\Program Files\Profit\AFAS Windows\Kernel\Bin
Source descr....: Anta Report Engine (C/S)
Time............:
Active control..: frmPreview.ARViewer - "Afdrukvoorbeeld"
DLL/EXE file....: C:\Program Files\Profit\AFAS Windows\Kernel\Bin\AntaRpEn.dll [7.500.0.100]
Landmark........: AntaRepEng.EReport.mobjAReport_Error [052A09FB]
Landmark........: AntaRepEng.ERunResult.ResumeError [10C12280]
Landmark........: AntaRepView.frmPreview.ARViewer_LoadCompleted [68BE127F]
======================================================================
Number..........: 2019 #7E3 [VB]
Description.....: Can't run report. PageHeader/Footer height is larger than page height.
Init state......: Saved

 

See also

  • Report management