To find a particular error message below, press Ctrl + F to open the Find dialog and search for the message.
If a documented solution does not fix the problem, contact Infor Technical Support.
Errors may appear in one or more of these places in the system:
| Activity or Process | Error Type | Location |
|---|---|---|
| Get ATP/CTP | Error | Error message displayed on the form when you click the Get ATP/CTP button. |
| Planning activity: preprocessing, planner database reload, or core planning algorithm processes | Error | APS Planning and Scheduling Messages form |
| Planning activity or Get ATP/CTP: preprocessing, planner database reload, or core planning algorithm processes--additional detail | Error | APS Planning and Scheduling Messages form |
| Planning activity or Get ATP/CTP: preprocessing, planner database reload, or core planning algorithm processes--additional detail | Error | apserror.txt file (located in the “CommonApplicationData” directory as queried from the operating system) |
| Planning activity or Get ATP/CTP: core planning algorithm processes--additional detail. Available after planning algorithm completes. | Error | ol_error.txt file (located on the Planning server machine--usually in ..\projects\database name\\ol_log under your Planning Server installation or on the machine where the Planning and Scheduling Service is installed--usually in c:\winnt\system32). |
| Planning activity or Get ATP/CTP: problems related to a parameter causing a date to exceed the Plan Horizon, information about demands being blocked, and other assorted messages etc. Available after planning algorithm completes. | Error, Warning, or Informational | ol_sched.txt file (located on the Planning server machine--usually in ..\projects\database name\ol_log under your Planning Server installation). |
This topic describes the messages displayed on the APS Planning and Scheduling Messages form, and the Get ATP/CTP form.
The errors listed in the table below appear when you click the Get ATP or Get CTP button on certain SyteLine transactions.
| Error Message | Explanation and Solution |
|---|---|
| Availability request requires a demand quantity greater than zero. | You cannot perform Get ATP/CTP on a demand that has a quantity of zero. For example, a customer order line's demand quantity = Qty Ordered - Qty Reserved - Qty Shipped. A forecast's demand quantity = Outstanding Requirement. |
| A batch planning run is in progress. Please try again later. | Another client session is running the APS Planning activity. Wait a few minutes and try again. |
| Cannot be completed within the current planning horizon. | The system did not find sufficient capacity or material to plan an order within the time period specified in the Plan Horizon field (on the Planning Parameters form). You can try reducing the quantity, using a later Due Date, or adding new resource capacity to allow the demand to be planned. Sometimes this error occurs if the resources in a resource group are on mutually exclusive shifts and the operation requires all of those resources. |
| Cannot retrieve planner connection information for the specified alternative. | The alternative 0 record, specified on the APS Sites and Alternative Management form, does not specify valid planner database connection information (port #, host name, etc.). |
| Configured items must be cross-referenced to a job. | You performed the Get ATP/CTP function for a configured order line, but the order line was not cross-referenced to a job. In order to get an ATP or CTP date for a configured item, the item must be cross-referenced to a job. |
| Forecasts for MPS items must be planned using the MPS Processor. | When you enter a forecast for an MPS item on the Forecasts form, the Get ATP/CTP process does not plan the forecast; to plan this demand, you must run the MPS Processor. |
| Flush of gateway table is in progress. Please try again later. | The APS Planning activity was running when the Get ATP/CTP process tried to run it. Wait a few minutes and try again. |
| Flushing of the gateway table was unsuccessful. See ERRORLOG table for details. | Check the ERRORLOG table in the SQL database. Find the detailed error message in the ERRMSG column. ERRORLOG messages are described below in the ERRORLOG Messages section. |
| Item not found in planning database. | There are two possible causes:
|
| Job (number) does not exist. | You performed the Get ATP/CTP function for an order line that is cross-referenced to a job, but the job did not exist in SyteLine. |
| Network communications error. | At some point in the planning or scheduling process, a network connection was lost. There are three possible causes:
|
| Out of memory. | The planner database server does not have enough available system resources to run the program. Close any unnecessary applications or add more memory to the server. |
| Planner database is marked as down. | The planner server service specified for the alternative 0 record is not running. Verify that the database is running in the Server Service Configuration utility. |
| Planner database reload in progress. Please try again later. | Another client session may have been running the APS Planning activity or a Get ATP/CTP process. Wait a few minutes and try again. |
| The cross-referenced job is already scheduled. | You performed the Get ATP/CTP function for an order line that is cross-referenced to a job, and the job has already been scheduled (it has a status other than Firm). SyteLine moves the job's End Date to the order line's Projected field and disables the Get ATP/CTP button. |
| Unable to connect to APS Server. | The APS Server Service Port number, specified on the APS Sites and Alternative Management form, is not valid. Check the Windows Services configuration to verify the port number on which the APS Server Service is running, and correct the entry. |
| Unable to connect to Planner Database Server. | The APS Server Service Host, specified on the APS Sites and Alternative Management form, was not found or was down. |
| Version mismatch | The server and client (or DLL) are not compatible software versions. Contact Technical Support. |
| The firm job for which you are about to check availability may have recently been converted from a PLN with no planning run since its conversion. Under these circumstances, the availability check will return a conservative Projected Date. Use caution if you use the new Projected Date information to change your job End Date. However, if this job was not generated from a PLN, the availability check will be proper. Do you wish to proceed? | If the job on which you are performing Get ATP/CTP was firmed from a planned order, the information is already in the plan and capacity is allocated. If you check availability for this job, you are essentially "double-counting" it, which will result in an artificially conservative Projected date. Click Yes if you are comfortable with this fact. If you do not want to check availability for this job now, click No (and then try it again later after the next run of the APS Planning activity). |