О системах планирования ресурсов предприятия Scala, iScala
“ How to integrate iScala and supplier's ERP - step by step description
  • Главная
    • О проекте
      • Разъяснение о проекте и его участниках
      • Заявление / Memorandum
    • Новости проекта
    • Список опубликованных материалов основного раздела
    • Информация, перенесённая из старых форумов
    • Подписаться на новостную рассылку
  • Наши услуги
  • Статьи
    • Статьи
    • Избранное
    • Мысли вслух
  • Процедуры
  • Доходчиво о сложном
    • Обучение
    • Как сделать?
    • iScala «для чайников»
    • Оч.умелые ручки
  • Структура таблиц
    • Scala 5.1 SR13
    • iScala 2.2 HF 2.3318
    • Tables structure changes history from iScala 2.2 SR2 to iScala 3.0 FSP4
    • Epicor iScala 2.3 — 2.03.3363
    • Epicor iScala 2.3 SR1
    • Epicor iScala 2.3 SR2
    • Epicor iScala 2.3 SR3
    • Epicor iScala 3.00 FSP 2 — 3.00.02254
    • Epicor iScala 3.0 FSP4 — 3.0.4267
    • Изменение структуры таблиц iScala 3.1 по сравнению с iScala 3.0 FSP4 / Table structure changes between iScala 3.0 FSP4 and iScala 3.1
    • Epicor iScala 3.1 — 3.1.0511
    • Epicor iScala 3.2 — 3.2.0317
    • Epicor iScala 3.3 — 3.3.0419
    • Epicor iScala 3.4 — 3.4.0399
    • Epicor iScala 3.5 — 3.5.0.0429
    • Изменение полей в таблицах БД iScala 3.4 по сравнению с iScala 3.2 / Difference between DB structure of iScala 3.4 and iScala 3.2
    • Изменение полей в таблицах БД iScala 3.5 по сравнению с iScala 2.2 / Difference between DB structure of iScala 3.5 and iScala 2.2
  • Материалы по модулям iScala
    • Главная Книга
    • Основные Средства
    • Книга Закупок
    • Книга Продаж
    • Заказы на Закупку
      • Требования
    • Заказы на Продажу
    • Управление Запасами
    • Установка, Администрирование
      • Настройка определений документов MSRS
    • Заработная плата
    • Структура базы данных
    • Отчётность SSRS
    • Отчётность AFR
    • Примеры отчётов
    • Примеры отчётов AFR
    • Интеграция с другими системами
    • Epicor Service Connect
  • English
  • Контакты
  • Поиск
Главная  »»»  For English speaking people  »»»  Sent PO electronically to Supplier’s FTP site

Sent PO electronically to Supplier’s FTP site

09.02.2016 Автор Алексей Васильев

How to integrate iScala and supplier’s ERP

Статья по-русски: «Отправить Заказ на Закупку поставщику в электронном виде»

1. Output channel “99 — Send PO to Supplier” has been created:
POtoFTP001

2. DDF template PC00HB00ENG has been created in Custom->DDF2->PC folder:
Sent PO electronically to Supplier's FTP site: Step 2Sent PO electronically to Supplier's FTP site: Step 2.1

3. New User Schema has been created:
Sent PO electronically to Supplier's FTP site: Step 3

Schema Content:
Sent PO electronically to Supplier's FTP site: Step 3.1

4. Work Flow Package “PO_To_FTP” has been created:
Sent PO electronically to Supplier's FTP site: Step 4

5. “SendCSVtoFTP” Work Flow content:
Sent PO electronically to Supplier's FTP site: Step 5

6. New message type has been added:
Sent PO electronically to Supplier's FTP site: Step 6Sent PO electronically to Supplier's FTP site: Step 6.1

7. New Message Map has been added:Sent PO electronically to Supplier's FTP site: Step 7Sent PO electronically to Supplier's FTP site: Step 7.1

8. New Service Connect Input Channel has been added:
Sent PO electronically to Supplier's FTP site: Step 8

9. Input channel settings:

Sent PO electronically to Supplier's FTP site: Step 910. Configuration:

Sent PO electronically to Supplier's FTP site: Step 10Sent PO electronically to Supplier's FTP site: Step 10.1Conversion Configuration:
Sent PO electronically to Supplier's FTP site: Step 10.2

11. ToSupplierSaveToHistory Service Connect Output channel has been added:
Sent PO electronically to Supplier's FTP site: Step 11

12. ToSupplierSaveToHistory Service Connect Output channel settings:
Sent PO electronically to Supplier's FTP site: Step 12

Configuration:
Sent PO electronically to Supplier's FTP site: Step 12.1

Conversion Config:
Sent PO electronically to Supplier's FTP site: Step 12.2

13. “SendFileToFTP” Service Connect FTP output channel has been created:
Sent PO electronically to Supplier's FTP site: Step 13

14. FTP output channel settings:
Sent PO electronically to Supplier's FTP site: Step 14

Configuration:
Sent PO electronically to Supplier's FTP site: Step 14.1Sent PO electronically to Supplier's FTP site: Step 14.2

Conversion Config:
Sent PO electronically to Supplier's FTP site: Step 14.3

15. Work Flow Details:
Choice:
Sent PO electronically to Supplier's FTP site: Step 15

Work Flow “Choice” element configuration:
Sent PO electronically to Supplier's FTP site: Step 15.1Sent PO electronically to Supplier's FTP site: Step 15.2

Transformation to Output Format Element
Sent PO electronically to Supplier's FTP site: Step 15.3

“SaveToHistory” Work Flow Element (Poster):
Sent PO electronically to Supplier's FTP site: Step 15.4

Configuration:
Sent PO electronically to Supplier's FTP site: Step 15.5Sent PO electronically to Supplier's FTP site: Step 15.6

Fixed Channel configuration:
Sent PO electronically to Supplier's FTP site: Step 15.7

Mask:
Sent PO electronically to Supplier's FTP site: Step 15.8

Conversion:
Sent PO electronically to Supplier's FTP site: Step 15.9

Conversion Config:
Sent PO electronically to Supplier's FTP site: Step 15.10

“SendToFTP” Work Flow Element (Poster):
Sent PO electronically to Supplier's FTP site: Step 15.11

“SendToFTP” Work Flow Element settings:
Sent PO electronically to Supplier's FTP site: Step 15.12Sent PO electronically to Supplier's FTP site: Step 15.13

Fixed Channel Configuration:
Sent PO electronically to Supplier's FTP site: Step 15.14

Mask:
Sent PO electronically to Supplier's FTP site: Step 15.15

Conversion:
Sent PO electronically to Supplier's FTP site: Step 15.16

Conversion Configuration:
Sent PO electronically to Supplier's FTP site: Step 15.17

16. User’s steps in iScala:
1) User Enters Purchase Order for Supplier with Supplier Code “********11”
2) User enters selection criteria to print selected Purchase Order:
Sent PO electronically to Supplier's FTP site: Step 16-2

3) When iScala asks to select output channel, user selects special output channel:
Sent PO electronically to Supplier's FTP site: Step 16-3

4) iScala creates file in the folder associated with output channel
5) Service Connect starts working
17. Administrators can check results using Document Tracking in iScala Administration Console:
Sent PO electronically to Supplier's FTP site: Step 17

18. Process Details:
Sent PO electronically to Supplier's FTP site: Step 18

19. Step Details:
Sent PO electronically to Supplier's FTP site: Step 19

20. Result in “History” folder:
Sent PO electronically to Supplier's FTP site: Step 20Sent PO electronically to Supplier's FTP site: Step 20.121. Result in FTP folder:
Sent PO electronically to Supplier's FTP site: Step 21

22. Another process (User prints Purchase Order with different supplier code):
Sent PO electronically to Supplier's FTP site: Step 22

23. Process Details:
Sent PO electronically to Supplier's FTP site: Step 23

No file created yet.

Рубрика: For English speaking people, Заказы на Закупку Метки: Service Connect, интеграция, поставщик
VK Telegram Про канал в WhatsApp

Copyright © 2025 О системах планирования ресурсов предприятия Scala, iScala.

Gammapolis WordPress Theme by ERP & Business Consulting

Прокрутка вверх