cobi.shipping
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cobi.shipping [2025/08/22 13:33] – [Installation] thuth | cobi.shipping [2025/08/22 13:40] (current) – [Installation] thuth | ||
---|---|---|---|
Line 82: | Line 82: | ||
* Open Barcode Shipping → File → Settings. | * Open Barcode Shipping → File → Settings. | ||
- | | + | * General: |
* Default shipper: *Einfacher Versender* | * Default shipper: *Einfacher Versender* | ||
Line 88: | Line 88: | ||
* Enable *Mouse Mode* | * Enable *Mouse Mode* | ||
* Default shop: *Connector* | * Default shop: *Connector* | ||
- | * Connector: | + | * Connector: |
- | + | * API URL: http://< | |
- | * API URL: http://< | + | |
- | * (example: `http:// | + | |
- | * API Version: `V2` | + | |
- | * API Key: `Y29iaXNoaXBwaW5nOkRoNUchNnM=` (Base64 of `cobishipping: | + | |
- | + | ||
- | **4. Configure COBI.shipping in SAP Business One** | + | |
- | + | ||
- | * Go to **Extras → User-Defined Windows → @CMP\_CONFIG**. | + | |
- | * Set the configuration values as documented (see sections *UDFs* and *Optional toggles*). | + | |
- | * Mark shipping methods as “Barcode Shipping enabled”: | + | |
- | **Administration → Definition → Inventory Management → Shipping Methods**. | + | |
- | + | ||
- | ⚠️ **Note:** Configuration values are only loaded at service startup. | + | |
- | After making changes, always restart the COBI.shipping Windows service. \\ | + | |
- | + | ||
- | ===== Optional toggles (Boolean, 0/1) ===== | + | |
- | + | ||
- | All of the following configuration keys are stored in **@CMP\_CONFIG** and are read **on service start** (restart the COBI.shipping service after changes). | + | |
- | + | ||
- | ^ Key ^ Meaning (EN) ^ | + | |
- | | `cobi-shipping_companyFromCardName` | + | |
- | | `cobi-shipping_firstLastNameFromContacts` | + | |
- | | `cobi-shipping_firstNameLastNameFromCardName` | + | |
- | | `cobi-shipping_companyFirstNameLastNameFromAddress3` | Pull **company / first / last name** from **Address3** field. | + | |
- | | `cobi-shipping_addressFromAddress2` | + | |
- | | `cobi-shipping_companyAddressFromAddress2` | + | |
- | | `cobi-shipping_privateAddressFromAddress2` | + | |
- | | `cobi-shipping_createInvoiceAfterFullyPacked` | + | |
- | | `cobi-shipping_invoiceDateEqDeliveryNoteDate` | + | |
- | | `cobi-shipping_displayClosedDeliveryNotes` | + | |
- | + | ||
- | ===== Related non-boolean keys (for reference) ===== | + | |
- | + | ||
- | These are **not** toggles, but often configured alongside the above: | + | |
- | + | ||
- | ^ Key ^ Type / Example | + | |
- | | `cobi-shipping_trackingInHeaderFieldName` | Text (UDF name in Delivery header) | + | |
- | | `cobi-shipping_alarmGroupId` | + | |
- | | `cobi-shipping_oitmCommodityCodeField` | Text (UDF name on `OITM`) | + | |
- | | `cobi-shipping_alternativeRecipient` | Text (UDF name) | Alternative recipient field. | + | |
- | + | ||
- | > Note: Address field mappings like `cobi-shipping_firstNameField`, | + | |
- | + | ||
- | ===== Coresuite Print configuration ===== | + | |
- | + | ||
- | If the system is configured for automatic invoice creation, COBI.shipping can trigger a Coresuite Print job right after the invoice is generated. | + | |
- | This requires that the COBI.wms Printservice is installed and reachable. | + | |
- | + | ||
- | ^ Key ^ Type / Example ^ Purpose ^ | + | |
- | | cobi-shipping_printService | URL (e.g. http:// | + | |
- | | cobi-shipping_printDefinition | Text / ID (e.g. DeliveryNoteLayout) | Print Definition ID to be used for output | | + | |
- | | cobi-shipping_layoutId | Text / ID (e.g. 1001) | Layout ID for the document | | + | |
- | | cobi-shipping_printMode | Text (Print or Email) | Determines whether the invoice is printed or sent by email | | + | |
cobi.shipping.1755862425.txt.gz · Last modified: by thuth