We use the LATEST_SHIP_DATE field which is available in the standard report view. This will then print the actual ship date if the line is shipped complete or the date of the last delivery against the order line.
Here are more details with screen shots.In the Employee File screen in the Qualifications > Certificates tab.When I add a certificate manually against the employee the date, I add it is used as the start date and the during set against the certificate is used to calculate the end date.Here is the certificate ACCIWhen I enter the information manually against the employee the dates display as:I have added Job Certificates against roles to allow for all of the required certificates to be added against employees based on there job role. Here is what is added against the driver job role.If I delete the manually entered certificate against this employee and use the right mouse button “Copy certificates from primary job requirements” and save the record, then all of the correct certificates are added but the duration set against each certificate is not used.It appears valid to and from dates set against the job certificates is used in place of the system adding the duration automatically.
Is there a reason that you are looking to do this under IFS Connect rather than in the Batch Queue Configuration? Unless I am misunderstanding your request, it looks like you really want a new Batch Queue to be set up under Sol Man / Background Processing / Background Jobs / Batch Queue Configuration, with just 1 Process assigned to it to ensure serial job processing. Once you have that new Batch Queue in place you would then add the <API>.<METHOD> (looks like Customer_Order_Inv_Head_API.Print_Invoices) to that queue using the RMB / Add option. I guess you could use IFS Connect if you wanted to duplicate the PROCESSING_PRINT_JOBS Task Template, then only include the Invoice printer device in that, but I don’t know if that is the best way to go in general... You would want to have a dedicated logical printer called “Invoice” in that case that only gets added to that Task Template and not the normal printing Task Template. That new Task Template with just the Invoice logi
Identify the API.Method handling the print functionality, RMB on BATCH_INVOICE and Add the API.Method to the new queue. Once you finish adding, save the change and RMB Init Queue. You can identify the API.Method by checking the background jobs screen. I have identified the API from the print invoice background job. From IFS connect there is no RMB to add. The options are shown below. You can add from the batch queue configuration screen but this message queue is not shown there?
Can you try to define a custom event to overtake the standard printing order to bypass result key order I am not sure what action I could fire the custom event from here. If I use pdf created it would be too late as the invoice batch would already be instigated. What would you suggest?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
