Интеграция «1С 8” с «Comarch EDI» со следующими возможностями:
Загрузка с «Комарч EDI»;
Загрузка заказов от сетей - файл ORDER;
Выгрузка в «Комарч EDI»;
Выгрузка подтверждений заказов - файл ORDRSP;
Выгрузка расходных накладных - файл DESADV;
Выгрузка каталога товаров и данных о его наличии – файл PRICAT.
IndustryATP, transport managementPrinting housesWholesaleMedical clinics, medical institutionsRent of equipment for rentService station, car service, sale of spare parts and carsOnline storeTourism CategoryAdditional settingsCommon forms TypeManagement Accounting CofigurationsTrade managementManufacturing enterprise managementTrade Management2.3Accounting for Ukraine1.2
Integration of "1C 8" with «Comarch EDI» with the following options:
Download from "Comarch EDI";
Load orders from networks - ORDER file;
Upload to Comarch EDI;
Uploading Order Confirmations - ORDRSP;
Downloading invoice upload - DESADV file;
Uploading the product catalog and its availability data - PRICAT file.
What networks does it work with?
The solution works and is debugged at work with networks:
For other networks, loading orders from customers works, uploading should also work, you need to check, if not, then the structure of the uploaded files is easily and quickly adjusted.
Orders from "Comarch EDI" customers fall into "1C 8" automatically . In Fig. 1 shows a fragment of the magazine "Orders of customers", where orders received from "EDI" are marked with the corresponding icon.
Fig. 1. The magazine "Orders of customers" with the downloaded orders from "EDI"
When downloading orders from "Comarch EDI", the counterparty and the nomenclature are automatically detected. In addition, the task is formed for the responsible manager or the sales manager about the receipt of new orders with EDI.
More about the functionality
Fig.2. Added an "EDI" button on the top panel of the Customer Orders document log.
Fig.3. Form processing. Filling in the initial settings on the "Settings" tab.
Fig.4. Selecting a directory for storing files and specifying the person in charge on the "Settings" tab of the processing form.
Fig.5. On the tab "Loading", processing forms, the button "Automatic loading" is located for automatic loading of documents.
Fig.6. Installation of compliance of the loaded nomenclature with the nomenclature in 1C.
Fig.7. The indication of compliance of the loaded nomenclature with the 1C nomenclature (reference book "Nomenclature").
Fig.8. Filling the counterparty field (our organization), data type - directory "Organizations".
Fig.9. Filling the counterparty field, data type - reference book "Counterparties".
Fig.10. Filling the counterparty (customer) by GLN code.
Fig.11. Counterparty identification when filling out the GLN code.
Fig.12. Specify the place of delivery (the "Address" field) when identifying the counterparty.
Fig.13. Formed document "Buyer's order", the commentary contains data that was entered in the processing form.
Fig.14. Processing form, on the tab "Counterparty correspondence" can add, change or view data on counterparties.
Fig.15. Corrected data on counterparties,bookmark "Counterparty correspondences", processing forms.
Fig.16. Finish filling in the settings for automatic loading.
Fig.17. For counterparties - networks mapping codes GLN. Also for networks is set the appropriate type of bar code.
Fig. 18. For nomenclature, set up mappings to EAN code, our nomenclature, vendor code, counterparty code.
Fig. 19. The subordination structure of the Order document with the automatically created, on the basis of this document, the order of the buyer.
Ordrsp Document - Customer Order Confirmation.
Fig.20. Product sales journal, a note that the expenditure invoice has been sent to EDI.
In the subordinate structure, the file DESADV is visible, sent to “Comarch EDI”.
It can be integrated into configurations on common forms 1C:
Manufacturing enterprise management;
Trade Management, Revision 2.3;
Accounting, edition 1.2
Solution cost, UAH.
The cost of the integration module "1C 8" with "Comarch EDI"
Work on the integration into the configuration of the customer (2 hours if the base
customer configuration is one of the typical configurations listed above)