Please enable JavaScript to view this site.

Estate Forums

Invantive Estate

The import of concept invoices to King is described here. A background script is available for the invoicing of hours to processes and projects and fixed price processes. This ensures that the invoice data will be stored as concept invoice lines. The daily process is as follows:

•Go to the screen 'Submit Background Job'.

•Select the background script ‘Invoicing: Process all parts’.

•Enter the parameters as follows:

Screen Web Frontend Interface King: Invoicing Process all Parts

•Wait until the process is successfully completed in the screen Background Jobs.

•Now you can check the concept invoices in the screen Concept Invoice Lines.

Import concept invoice lines in King

A background script is available for the invoicing of hours to processes and projects and fixed price processes. This ensures that the invoice data will be stored as concept invoice lines. The daily process is as follows:

•Go to the screen 'Submit Background Job'.

•Select the background script ‘King: Extraction sales orders’.

•Wait until the process is successfully completed in the screen Background Jobs.

•The output file is an XML file, such as:

Xml Order File

•You can now retrieve the XML file as an attachment of the background job and import it into KING using the following menu:

King Interface Screen: Import concept invoice lines in King

•The XML file can be saved, for example, in the folder ‘out’ of the server.

•Change the options for import as follows:

King Interface Screen: Options import XML

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer