| Inhaltsverzeichnis anzeigen |  |
|
|
|
CBL file order exporter (scheduled task)
Instead of sending orders by e-mail, in this case they are written to the hard drive as a file and can be processed from there, e.g. by ERP systems.
This task is closely related to the CBL e-mail order exporter .
“Individual” or “generic” can be selected as a Type.
- If "generic" is selected, the task sends all orders for which the "CBL file order exporter 2.0r3" (or cbl ecos1) ordering method has been selected in the basic contract.
- If you select "individual" orders are sent to the set supplier if "individual" has been selected as the order dispatch method in the associated basic contract.
Parameters
Parameter |
Description |
|---|---|
Path |
First of all, specify the data path where the data is to be saved, using "\" between the directories. The export directory used, e.g. d:/orderexport, must contain the following directories: d:/orderexport d:/orderexport/todo d:/orderexport/done d:/orderexport/error After the 'Export', the CBL file order exporter also searches in the ToDo directory for files with the format: <Name>_poh_id123454.xml – for further processing. As some suppliers have to rename this file for their ERP systems, the files can have any file names; however in this case the first line of the file must contain the original file name. |
Write mode |
If the destination directory already contains files and orders are exported again, for example, this specifies whether or not files of the same name (same order ID) can be overwritten or whether the new information is to be appended to the files. |
Supplier |
You have the option of setting a supplier; as normal, if no supplier is set the task applies to all suppliers |
File name |
Specifies how the file is to be named (it is then created in the directory specified above). In addition, further information such as the buyer reference number and any supplier reference number can be added here. For parameter numbers see CBL e-mail order exporter. The ending in the form of "POH_" with consecutive order ID is always added and does not therefore need to be specified |
Version |
As for e-mails, two CBL versions are supported |
Also export control structures
This must be selected if set cost centres,types of cost or projects starting from the order items are to be included when exporting.
Send normal catalog order
If this option is selected, orders are exported from the catalogs of the set supplier
Send free form orders
If this option is selected, free form orders for this supplier are sent
Caution : One of these two options must be selected for any orders to be exported.
Send orders with attachment
If this option is not selected, orders with a file attachment (e.g. comments) are not exported.
Caution: If the option is selected, orders with no file attachment are also exported using this exporter. Selecting it does not exclude them.
Request confirmation of receipt
This option is slightly more complicated than in the case of e-mails. For this option to take effect, a ToDo directory and a Done directory must be created. Once the order has been exported and has been processed elsewhere (e.g. by an ERP system), it is placed in the ToDo directory. The system uses this to identify that the file has been processed and only then sets the status of the order to "Sent, receipt confirmed" . The file is moved to "Done". Without this option, the order is set to this status immediately within the system
Partial delivery allowed
If this option is selected, the supplier is notified that partial deliveries are allowed
Recommended execution interval
Depending on the order payment and ordering behaviour of the ordering company.
Dependencies on other scheduled tasks
This task should run after the "Create orders task" as it directly depends on it. If should not be run at the same time as other exports to other suppliers; a sensible series resulting in consecutive processing is recommended.
Caution: You must ensure that the path name and version are correctly set, to guarantee that subsequent processing runs smoothly.
Note: The file order exporter also sends an e-mail to the administrator in case of an error that does not lead to the task being stopped. This kind of error could be if a received file does not contain a valid order ID. In such cases, the file is copied to the 'Error' sub-directory, the user is informed by e- mail and the exporter continues running normally. As result, the user knows that he has to take action even though the task is not marked as faulty.
In case of problems, check the write privileges for the system in the destination directory. In the "Do not overwrite" write mode, remove any problematic files to ensure that the task runs smoothly.
See also |