FC Sales Interface - ERP MRD

Introduction
Glossary of Terms
Term Description
FC Flying Cargo
SE SolarEdge
3PL 3PL company for inventory management and shipping of products to customers
Priority SolarEdge ERP system
WMS The 3PL internal system serves as a gateway for data exchange with SE
WS Web Service
SEIL FC warehouse name in the Priority system
ASN Advance Shipment Notification
WO Work Order
ETA Estimated Time of Arrival
PN Part number
Generic PN A part number that is not shipped to customers. This PN can be converted to different Marketing PN's by using Fulfilment station.
Marketing PN
The part number that is actually shipped to the customer, can also be converted into different marketing PNs

Mega Excel Excel sheet that is exported from Agile that contains the information based on which part number can be fulfilled into which part number

Motivation
SolarEdge will use FC 3PL Company for inventory management and shipping of products to customers.

The inventory-related processes, which are executed by 3PL, are managed in SolarEdge ERP

System. Therefore needed to be synced with the transactions in SolarEdge ERP.

General Process
Interfaces:
ASN (Advanced Shipment Notification)

The ASN interface is an outgoing interface to FC - its purpose is to alert FC that goods are on their way to FC warehouses (SEIL).

ASN Receipt

Once inventory is received in FC, they will transmit a message to SE in order to inform SE that the inventory has arrived and the receipt is closed in FC WMS system.

Outbound work order creation

In order to open a Work order in the WMS for outbound shipments, SE will transmit outbound order request to FC. Everyday SE will transmit the outbound orders to be fulfilled tomorrow (target date in Priority is tomorrow). The 3PL company will provide the outbound WO WSDL to SE.

Packing List creation

After finishing the pick & pack of the goods, palletizing and closing the work order, 3PL should provide the relevant information to SE, so SE will do the customer shipment document. Customer shipment is the Inventory transaction that reduces the parts inventory. The parts are physically sent to the customer

Logistic Data Interface (ship confirmation: ETA, POD, forwarder)

This interface will add operational data on customer shipment.

A request from FC to SE) SE will provide the WSDL to 3PL)

Parts Interface

The parts interface will send FC all new and updated part numbers from SE's Priority.

The information that will be sent will include the part number, description, UOM, family and more.

Inventory Interface

This interface is required in order to compare the inventory in Priority and the inventory in 3PL WMS.

3PL will provide to SE a daily CSV file with the part number and its quantity and status.

Business flow chart

Technical Process
All messages will be transmitted using a BI ETL tool that will extract messages from SE to FC from priority using Priority's API, convert the files to XML, and upload them to an FTP folder provided by FC.

Messages that will be transmitted from FC to Priority will be sent to an FTP folder, as XML files, from which the ETL tool will upload the data to Priority using API.

Prior Infrustructure -Prioriry Dev:

FC Sales - Prior Infrastructure - Priority Dev

ASN (Advanced Shipment Notification)

General
1. Inbound/Outbound: Inbound
2. Purpose:
The ASN interface is an outgoing interface to FC- its purpose is to replenish FC warehouses (SEIL).
The interface is designed to alert FC that the manufacturer is about to send them the goods by sending a request to open inbound order in FC WMS system.
3. How it works:
3.1. The request will be activated automatically from Priority:
3.1.1. when TR (warehouse transfer document) in LTD is finalized and Receiving warehouse = TRN, Bin: SEIL
3.1.2. When updating ETA after the TR was sent to FC already
3.2. BI Integration tool will convert the request to an XML file that will be transferred to FC FTP folder (In 'SE' sub-folder)
3.2.1. If they were able to insert the file successfully it will be count as Technical Acknowledgement => Success
3.2.2. If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
3.3. XML Filename: concatenation ('InBoundASN-',<ORDERID>)
3.4. XML Fields:

‫סוג‬ Form Constant Value / Calculation Priority - ETL -

‫שם סגמנט חובה‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬ Form Field name Priority Source
‫סגמט‬ Type Logic Done Done
SE Message ID

‫כן‬ DATA ‫כותרת‬ <MESSAGEID>114388<MESSAGEID> string ‫מזהה ייחודי של המסר‬ Form SOL_FCSALESLOG MESSAGEID Priority 

‫ יישמרו את‬FC ‫המספר בצד‬


‫כן‬ DATA ‫כותרת‬ <CONSIGNEE>SOLAREDGE</CONSIGNEE> string ‫ קבוע‬- ‫מאחסן‬ Constant SOLAREDGE 

‫מזהה ייחודי של המחסן המקבל בפריוריטי‬

:‫תאור מחסן‬ SE ‫ תשלח‬FC‫ל‬

‫כן‬ DATA ‫כותרת‬ <TOWAREHOUSE>614 </TOWAREHOUSE> Form DOCUMENTS_T TOWARHS Priority
WH: SEIL ‫רשימת קודי מחסנים מראש‬

Bin: Sales
‫תעודת העברה בין מחסנים בפריוריטי‬

‫כן‬ DATA ‫כותרת‬ <ORDERID>TRL2013638</ORDERID> string Form DOCUMENTS_T DOCNO Priority 
(#TRL)
 
‫כן‬ DATA ‫כותרת‬ <ORDERTYPE>REPL</ORDERTYPE> string ‫ קבוע‬- ‫מאחסן‬ ‫מילוי מחסן‬ Constant REPL 

‫פורמט‬
‫התאריך שבו התעודת העברה בין מחסנים‬ 
‫כן‬ DATA ‫כותרת‬ <CREATEDATE>2020-07-29</CREATEDATE> date YYYY-MM-DD Form DOCUMENTS_T CURDATE Priority 
‫נוצרה לראשונה‬


DATA ‫כותרת‬ <NOTES>From Jbl-TRL2013638</NOTES> string ‫הערות כלליות על התעודה‬ Form DOCUMENTS_T DETAILS Priority 

‫פורמט‬

‫כן‬ DATA ‫כותרת‬ <REQUESTDATE>2020-07-29</REQUESTDATE> datetime ‫תאריך שבו המסר נשלח‬ Form SOL_FCSALESLOG DATETIME Priority 
YYYY-MM-DD
‫מזהה ייחודי של המחסן השולח בפריוריטי‬

:‫ דוגמא למחסן‬SE ‫ תשלח‬FC‫ל‬


DATA ‫כותרת‬ <WAREHOUSE>41</WAREHOUSE> string Form DOCUMENTS_T WARHS Priority 
WH: Jbl ‫רשימת קודי מחסנים מראש‬

Bin: 0
‫שם המדינה שממנה המוצרים המיוצרים‬ ‫לצורך תיעוד סיריאלים שמיוצרים‬ Country Name for Sending 
DATA ‫כותרת‬ <WHCOUNTRY>Hong Kong</WHCOUNTRY> string Form WAREHOUSES COUNTRYNAME Priority 
‫מגיעים‬ ‫שאר העולם‬/‫באירופה‬ WH in Doc
‫אם התעודה נשלחה‬
ETA

DATA ‫כותרת‬ <EXPECTEDDATE>2020-07-29</EXPECTEDDATE> datetime ‫עודכן‬ETA‫ ו‬Form WAREHOUSES SLR_ETA Priority 
‫זמן משוער שהפריטים אמורים להגיע למחסני‬
FC
‫אז המסר יישלח שוב‬

‫כן‬ DATA\LINES\LINE ‫שורות‬ <ORDERLINE>1</ORDERLINE> string ‫מספר השורה בתעודה‬ Form TRANSORDER_T OLINE Priority 


‫כן‬ DATA\LINES\LINE ‫שורות‬ <REFERENCEORDLINE>10207822</REFERENCEORDLINE> string ‫מזהה ייחודי של השורה בתעודה‬ Form TRANSORDER_T TRANS Priority 


‫כן‬ DATA\LINES\LINE ‫שורות‬ <SKU>HOTWTR-SENS-RW-S1</SKU> string ‫מק"ט‬ Form TRANSORDER_T PARTNAME Priority 


‫כן‬ DATA\LINES\LINE ‫שורות‬ <QTYORDERED>10</QTYORDERED> string ‫כמות לקבלה‬ Form TRANSORDER_T TQUANT Priority 

4. ASN Inbound Acknowledgement: After the ASN inbound was processed at FC WMS system, they will send us an acknowledgement file (to subfolder 'SE')
4.1. XML Filename: concatenation ('InBoundASNACK-',<ORDERID>)
4.2. In phase 1 -
0. Success -it was agreed that FC will send us the same ASN Inbound request that was sent to them
1. Fail - FC will send to SE E-mail address (Will be given later) the error in the following format:
4.2.1.1. Mail Subject: concatenation ('InBoundASNACK',<ORDERID>, 'Errors received while processing ASN Inbound' )
4.2.1.2. Mail Content: Message Description
4.3. In Phase 2 - FC will send us an acknowledgement file in the following format:
4.4. XML Fields:

‫שם סגמנט חובה‬ ‫ שם השדה סוג סגמט‬XML ‫הסבר סוג דטה‬ ‫הערות‬
SE Message ID

‫כן‬ DATA ‫כותרת‬ <MESSAGEID>114388<MESSAGEID> string ‫נשלח בהודעה המקורית מזהה ייחודי של‬

‫המסר המקורי‬
‫סטטוס עיבוד המסר‬

‫כן‬ DATA ‫כותרת‬ <Status>False<Status> string ‫ אם המסר עובד בהצלחה‬- TRUE

‫ אם התגלו שגיאות בעיבוד‬- FALSE

‫תעודת העברה בין מחסנים בפריוריטי‬
‫כן‬ DATA ‫כותרת‬ <ORDERID>TRL2013638</ORDERID> ‫נשלח בהודעה המקורית‬
(#TRL)
‫כן‬ DATA\LINES\LINE ‫שורות‬ <REFERENCEORDLINE>10207822</REFERENCEORDLINE> string ‫מזהה ייחודי של השורה בתעודה‬ ‫נשלח בהודעה המקורית‬
‫כן‬ DATA\LINES\LINE ‫שורות‬ <Message>Part_Number_unknown</Message> string ‫ = תאור ההודעה במידה וסטטוס‬FALSE

5. According to the acknowledgement Mail/XML that was sent, BI will check if the <ORDERID> exists in SE DB. If not, will send back XML file as follows: (to the subfolder 'FC')
5.1. XML Filename: concatenation ('InBoundASNACK-',<ORDERID>)
5.2. XML Fields:

‫ שם השדה סוג סגמט שם סגמנט חובה‬XML ‫הסבר סוג דטה‬ ‫הערות‬

‫תעודת העברה בין מחסנים בפריוריטי‬
‫כן‬ DATA ‫כותרת‬ <ORDERID>TRL2013638</ORDERID> string ‫נשלח בהודעה המקורית‬

‫כן‬ DATA ‫כותרת‬ <Status>Fail</Status> string ‫סטטוס בדיקת המסר‬

‫כן‬ DATA ‫כותרת‬ <StatusDesc>Request ID <ORDERID> does not exist in SE DB Or was cancelled Please check the request again</StatusDesc> string ‫תיאור השגיאה‬

6. If they were able to insert the file successfully to FTP file it will be count as Technical Acknowledgement => Success
7. If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
8. BI will update the status of this request in our FC Interface Control table and will send E-mail to Sales, Operations and WH about this error.
9. If the Request was cancelled in SE → mail will be sent to FC with Document No. and Message-ID indication
10. The system will not allow cancelling ASN Document in Priority in case the Receipt was received.
Actions - Priority Dev
ASN (Advanced Shipment Notification) - Priority Dev

Actions - ETL
ASN (Advanced Shipment Notification) - BI

Example for XML file

ASN Receipt
General
1) Inbound/Outbound: Inbound
2) Purpose:
The ASN Receipt interface is an ingoing interface from FC- its purpose is to inform SE that the goods were received in FC warehouses (SEIL).
3) How it works:
a)
i) FC will send an XML file to FC FTP Folder (In 'FC' sub-folder)
(1) XML Filename: concatenation ('ASNReceipt-', <ORDERID>)
(2) XML Fields:

‫סוג‬ Form Field name Constant Value / Calculation Priority - ETL -

‫שם סגמנט חובה‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬ Form Source
‫סגמט‬ Type Priority Logic Done Done
SE Message ID
‫ התקבל במסר של‬ASN (b)
‫כן‬ DATA ‫כותרת‬ <MESSAGEID>114388<MESSAGEID> string ‫מזהה ייחודי של המסר‬ Form SOL_FCSALESLOG MESSAGEID Priority (a)
Inbound

‫מזהה ייחודי של המחסן המקבל‬

‫בפריוריטי‬

:‫ התקבל במסר של תאור מחסן‬ASN (d)

‫כן‬ DATA ‫כותרת‬ <WAREHOUSE>614 </WAREHOUSE> string Form DOCUMENTS_T TOWARHS Priority (c)
Inbound
WH: SEIL

Bin: Sales
‫תעודת העברה בין מחסנים בפריוריטי‬
‫ התקבל במסר של‬ASN
‫כן‬ DATA ‫כותרת‬ <ORDERID>TRL2012182</ORDERID> string Form DOCUMENTS_T PDOCNO Priority
Inbound
(#TRL)
‫פורמט‬
‫התאריך שבו הקבלה נסגרה במערכת של‬ (f)
DATA ‫כותרת‬ <CLOSERECEIPTDATE>2020-03-19</CLOSERECEIPTDATE> datetime YYYY-MM-DD Form DOCUMENTS_T DOCNO Priority (e)
FC

(h)
‫כן‬ DATA\LINES\LINE ‫שורות‬ <CONSIGNEE>SOLAREDGE</CONSIGNEE> string ‫ קבוע‬- ‫מאחסן‬ Constant SOLAREDGE (g)

(j)
‫כן‬ DATA\LINES\LINE ‫שורות‬ <ORDERLINE>1</ORDERLINE> string ‫מספר השורה בתעודה‬ Form TRANSORDER_T OLINE Priority (i)

(l)
‫כן‬ DATA\LINES\LINE ‫שורות‬ <REFERENCEORDLINE>10207822</REFERENCEORDLINE> string ‫מזהה ייחודי של השורה בתעודה‬ Form TRANSORDER_T TRANS Priority (k)

(n)
‫כן‬ DATA\LINES\LINE ‫שורות‬ <SKU>HOTWTR-SENS-RW-S1</SKU> string ‫מק"ט‬ Form TRANSORDER_T PARTNAME Priority (m)

(p)
‫כן‬ DATA\LINES\LINE ‫שורות‬ <QTYRECEIVED>10</QTYRECEIVED> string ‫כמות שהתקבלה‬ Form TRANSORDER_T TQUANT Priority (o)

ii) BI ETL Tool will:

(1) check if the <ORDERID> exists in SE DB. If not, will send back XML file as follows: (to the subfolder 'FC')
1. XML Filename: concatenation ('InBoundASNACK-',<ORDERID>)
2. XML Fields:

‫חובה‬ ‫שם סגמנט‬ ‫סוג סגמט‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬
‫תעודת העברה בין מחסנים בפריוריטי‬
‫כן‬ DATA ‫כותרת‬ <ORDERID>TRL2013638</ORDERID> string ‫נשלח בהודעה המקורית‬

‫כן‬ DATA ‫כותרת‬ <Status>Fail</Status> string ‫סטטוס בדיקת המסר‬

‫כן‬ DATA ‫כותרת‬ <StatusDesc>'Order ID <ORDERID> does not exist in SE DB Or was cancelled Please check the request again'</StatusDesc> string ‫תיאור השגיאה‬

3. If they were able to insert the file successfully to FTP file it will be count as Technical Acknowledgement => Success
4. If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
(2) If ORDERID (TRL#) exists, BI will take the XML file will open a new Warehouse Transfer Doc where:
0. Source Document = ASN Document number (First TRL# that was sent as part of ASN Interface)
1. Sending WH = TRN, Bin: SEIL
2. Receiving WH = SEIL Bin: Sales
(3) If BI successfully manage to finalize this doc → the system will send an e-mail to:
0. Fulfilment team
1. Logistic team
2. WH team
(4) If not, System will send Error description to the users above
 (5) BI will update the status of this request in our FC Interface Control table.
iii) Exceptions:
If the actual quantity received does not match the quantity from the request sent by SE → Do not receive partial quantity.
iv) FC will send an email to SE with the actual amount they received
v) SE will cancel the original Document sent in the ASN Inbound message

Actions - Priority Dev

ASN Receipt - Priority Dev

Actions - ETL
ASN Receipt - BI

Send Outbound WO
General
1.
1. Inbound/Outbound: Outbound
2. Purpose:
1. Once an order is set for a customer in SE – there is a need to place the order in WMS – FC warehouse system – in order to prepare for shipping the goods for the customer.
2. Every order in WMS is carried in a unique Work Order Number
3. In order to open a Work order in the WMS for outbound shipments, SE will transmit outbound order request to FC.
4. Everyday SE will transmit the outbound orders to FC→ In case of Inverters that their actual PN does not have enough balance in FC WH, there is an option to fulfil them in FC Fulfillment stations to other Marketing PN or Generic PN.
5. Fulfilment is an operation in which an inverter (That is currently located at the WH) is converted into another inverter (This inverter needs to ship but there is not enough balance in WH).
6. The decision as to whether it is necessary to fulfil and if so from which PN it will be made will be received in Outbound WO request under 'PICK_PART'
3. Definition of a WO (SE Outbound work order):
1. WO is a unique number that is created by SolarEdge (SE WO number) in order to group together specific open sales order lines in the Priority ERP system. Open sales order lines with same conditions (sent from the same warehouse and same target date to the same site and same pick up
address) need to be fulfilled together so they are grouped by a common number - that is SE WO number.
2. Each WO and its lines will be transmitted separately. Each file transmission contains a single WO (a WO can have multiple lines)
3. SE WO number format – SE WO is comprised of:
 SE (a prefix stands for ‘SolarEdge’)
 Target date in this format: DDMMYY
 ORD – sales order unique number
 WARHS – sales order sending warehouse unique number
 DESTCODE – Customer Address unique number
 PICKCODE - Customer Pick up Address unique number
4. How it works:
5. The request will be activated from Priority by 'Transmit WO to FC-Sales' (For inverters there is a need to run "Calculate FC Sales Pick" before)
1. By Target Date - will send all WO's that have the same Target Date for FC WH
2. By WO - by a specific WO
6. BI Integration tool will convert the request to an XML file that will be transferred to FC FTP folder (In 'SE' sub-folder)
1. If they were able to insert the file successfully it will be count as Technical Acknowledgement => Success
2. If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
7. XML Filename: concatenation ('OutboundWO-', <ORDERID>)
8. XML Fields:

Priority ETL -
‫חובה‬ ‫שם סגמנט‬ ‫ שם השדה סוג סגמט‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬ Form Field name Priority Source Constant Value / Calculation Logic
- Done Done
SE Message ID

‫מזהה ייחודי של המסר‬ 

‫כן‬ DATA ‫כותרת‬ <MessageID>114388</MessageID> string SOL_FCSALESLOG MESSAGEID Priority 

‫יישמרו את‬
FC ‫המספר בצד‬
SELECT ORDERS.ORDNAME

FROM ORDERS, ORDERITEMS, SOL_FCSALESLOG

‫בהזמנה יכולים‬
‫תעודת הזמנת לקוח‬ WHERE 
‫כן‬ DATA ‫כותרת‬ <OrderID>SOL2007186</OrderID> string ‫להיות מספר‬ ORDERS ORDNAME Priority 
‫בפריוריטי‬
WO'S
ORDERS.ORD = ORDERITEMS.ORD

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER
- ‫מאחסן‬ 
‫כן‬ DATA ‫כותרת‬ <Consignee>SOLAREDGE</Consignee> string Constant SOLAREDGE 
‫קבוע‬
‫מזהה ייחודי של‬
‫המחסן השולח‬
SELECT DISTINCT ORDERITEMS.SLR_SENDWARHS
‫בפריוריטי‬
SE ‫ תשלח‬FC‫ל‬
FROM ORDERITEMS, SOL_FCSALESLOG
‫כן‬ DATA ‫כותרת‬ <Warehouse>614 </Warehouse> string :‫תאור מחסן‬ ORDERITEMS SLR_SENDWARHS Priority
‫רשימת קודי‬
‫מחסנים מראש‬ WHERE SOL_FCSALESLOG.KEY =
WH: SEIL
ORDERITEMS.SOL_WONUMBER
Bin: Sales
‫מספר ייחודי‬
‫שמבטא את מספר‬
‫כן‬ DATA ‫כותרת‬ <SEWONumber>SE290720287417611147</SEWONumber> string SE WO number SOL_FCSALESLOG KEY Priority
‫העבודה‬
FC‫שייפתח ב‬
 SELECT CUSTOMERS.CUSTNAME

FROM ORDERS, ORDERITEMS, SOL_FCSALESLOG,

CUSTOMERS

WHERE
‫מספר הלקוח שביצע‬
‫את ההזמנה‬ 
‫כן‬ DATA ‫כותרת‬ <CustomerNum>1220299</CustomerNum> string CUSTOMERS CUSTNAME Priority ORDERS.ORD = ORDERITEMS.ORD 

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER

AND CUSTOMERS.CUST = ORDERS.CUST

SELECT CUSTOMERS.CUSTDES

FROM ORDERS, ORDERITEMS, SOL_FCSALESLOG,

CUSTOMERS

WHERE
‫שם הלקוח שביצע את‬ 
‫כן‬ DATA ‫כותרת‬ <CustomerName>SolarEdge Support<CustomerName> string CUSTOMERS CUSTDES Priority 
‫ההזמנה‬
ORDERS.ORD = ORDERITEMS.ORD

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER

AND CUSTOMERS.CUST = ORDERS.CUST

SELECT DISTINCT DESTCODES.ADDRESS

FROM SOL_FCSALESLOG, ORDERITEMS, DESTCODES

‫שם הרחוב ומספר‬ WHERE 

DATA ‫כותרת‬ <CustomerAddress>Z.I. Le Flacher</CustomerAddress> string DESTCODES ADDRESS Priority 
‫הבית של הלקוח‬
DESTCODES.DESTCODE = ORDERITEMS.DESTCODE

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER
SELECT DISTINCT DESTCODES.STATE

FROM SOL_FCSALESLOG, ORDERITEMS, DESTCODES

‫העיר בה נמצאת‬
WHERE 
DATA ‫כותרת‬ <CustomerCity>Felines (Lyon)</CustomerCity> string ‫כתובת המשלוח‬ DESTCODES STATE Priority 
‫ללקוח‬.
DESTCODES.DESTCODE = ORDERITEMS.DESTCODE

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER
SELECT DISTINCT DESTCODES.ZIP

FROM SOL_FCSALESLOG, ORDERITEMS, DESTCODES

‫המיקוד של כתובת‬ WHERE 

DATA ‫כותרת‬ <CustomerZipCode>07340</CustomerSiteCode> string DESTCODES ZIP Priority 
‫המשלוח‬.
DESTCODES.DESTCODE = ORDERITEMS.DESTCODE

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER
SELECT DISTINCT STATES.STATENAME

FROM
SOL_FCSALESLOG, ORDERITEMS, DESTCODES, STATES

WHERE
‫שם המדינה של כתובת‬ 
DATA ‫כותרת‬ <CustomerState /> string STATES STATENAME Priority 
‫הלקוח למשלוח‬
DESTCODES.DESTCODE = ORDERITEMS.DESTCODE

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER

AND DESTCODES.STATEID = STATES.STATEID

SELECT DISTINCT COUNTRIES.COUNTRYNAME

FROM SOL_FCSALESLOG, ORDERITEMS, DESTCODES,

COUNTRIES

WHERE
‫שם הארץ של כתובת‬ 
DATA ‫כותרת‬ <CustomerCountry>France</CustomerCountry> string DESTCODES ADDRESS Priority 
‫הלקוח למשלוח‬
DESTCODES.DESTCODE = ORDERITEMS.DESTCODE

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER

AND COUNTRIES.COUNTRY = DESTCODES.COUNTRY

 SELECT DISTINCT PHONEBOOK.NAME

FROM
SOL_FCSALESLOG, ORDERITEMS, DESTCODES, PHONEBOOK
‫איש קשר לכתובת‬
WHERE
‫למשלוח‬ 
DATA ‫כותרת‬ <DeliverToContact /> string PHONEBOOK NAME Priority 
DESTCODES.DESTCODE = ORDERITEMS.DESTCODE

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER

AND PHONEBOOK.PHONE = DESTCODES.PHONEB

SELECT DISTINCT PHONEBOOK.PHONENUM

FROM
SOL_FCSALESLOG, ORDERITEMS, DESTCODES, PHONEBOOK
‫מספר הטלפון העיקרי‬
WHERE
‫ כלומר‬,‫של איש הקשר‬ 
DATA ‫כותרת‬ <ContactPhone /> string PHONEBOOK PHONENUM Priority 
‫המספר בו הכי קל‬
DESTCODES.DESTCODE = ORDERITEMS.DESTCODE
‫להשיג אותו‬
AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER

AND PHONEBOOK.PHONE = DESTCODES.PHONEB

‫במידה ויש כאן‬
‫ערך‬

‫יש לקחת בחשבון‬

‫כתובת לאיסוף‬ ‫את הנתון הזה‬ 
DATA ‫כותרת‬ <PickUpAddress>Morag Street 21</PickUpAddress> string SOL_PICKUPSITE PICKADDRESS Priority Form still not developed 
‫המשלוח‬ ‫ככתובת למשלוח‬

)‫להתעלם‬
‫מהכתובת של‬
‫)הלקוח‬
‫במידה ויש כאן‬
‫ערך‬

‫יש לקחת בחשבון‬

‫העיר בה נמצאת‬
‫את הנתון הזה‬ 
DATA ‫כותרת‬ <PickUpCity>Kannot</PickUpCity> string ‫כתובת האיסוף‬ SOL_PICKUPSITE PICKCITY Priority Form still not developed 
‫ככתובת למשלוח‬
‫למשלוח‬.
)‫להתעלם‬
‫מהכתובת של‬
‫)הלקוח‬
‫במידה ויש כאן‬
‫ערך‬

‫יש לקחת בחשבון‬

‫המיקוד של כתובת‬ ‫את הנתון הזה‬ 
DATA ‫כותרת‬ <PickUpZipCode>7985000</PickUpZipCode> string SOL_PICKUPSITE SOL_PICKUPSITE Priority Form still not developed 
‫האיסוף‬. ‫ככתובת למשלוח‬

)‫להתעלם‬
‫מהכתובת של‬
‫)הלקוח‬
‫במידה ויש כאן‬
‫ערך‬

‫יש לקחת בחשבון‬

‫את הנתון הזה שם המדינה של כתובת‬
DATA ‫כותרת‬ <PickUpState /> date time SOL_PICKUPSITE STATENAME Priority Form still not developed
‫ככתובת למשלוח האיסוף למשלוח‬

)‫להתעלם‬
‫מהכתובת של‬
‫)הלקוח‬
‫במידה ויש כאן‬
‫ערך‬

‫יש לקחת בחשבון‬

‫שם הארץ של כתובת‬ ‫את הנתון הזה‬
DATA ‫כותרת‬ <PickUpCountry>Israel</PickUpCountry> string SOL_PICKUPSITE COUNTRYNAME Priority Form still not developed
‫האיסוף של המשלוח‬ ‫ככתובת למשלוח‬

)‫להתעלם‬
‫מהכתובת של‬
‫)הלקוח‬
SELECT DISTINCT ORDERITEMS.DUEDATE
‫פורמט‬
FROM ORDERITEMS, SOL_FCSALESLOG
‫תאריך לאספקה של‬
‫כן‬ DATA ‫כותרת‬ <DeliveryDate>2020-07-29T00:00:00</DeliveryDate> string ORDERITEMS DUEDATE Priority
‫המשלוח‬ YYYY-MM-
WHERE
DDThh:mm:ss
SOL_FCSALESLOG.KEY = ORDERITEMS.SOL_WONUMBER
 SELECT ORDERS.REFERENCE

FROM ORDERS, ORDERITEMS, SOL_FCSALESLOG

‫מספר הזמנת הרכש‬ WHERE

DATA ‫כותרת‬ <CustPO>2020-700699</CustPO> string ORDERS REFERENCE Priority
‫של הלקוח‬
ORDERS.ORD = ORDERITEMS.ORD

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER
SELECT DISTINCT SHIPTYPES.STDES

FROM ORDERITEMS, SOL_FCSALESLOG, SHIPTYPES

‫אופן משלוח הסחורה‬
DATA ‫כותרת‬ <ShipMode>Ground</ShipMode> string ‫המוזמנת בהזמנה‬ SHIPTYPES STDES Priority
WHERE SOL_FCSALESLOG.KEY =
‫הנוכחית‬
ORDERITEMS.SOL_WONUMBER

AND ORDERITEMS.SHIPTYPE = SHIPTYPES.SHIPTYPE

SELECT DISTINCT IMPTERMS.IMPTERMNAME

FROM ORDERITEMS, SOL_FCSALESLOG, IMPTERMS

DATA ‫כותרת‬ <IMPTERMDES>Delivery Duty Paid</IMPTERMDES> string ‫תנאי יבוא‬ IMPTERMS IMPTERMNAME Priority
WHERE SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER

AND ORDERITEMS.SLR_IMPTERM= IMPTERMS.IMPTERM

SELECT ORDERS.SOL_SLSREMARKS

FROM ORDERS, ORDERITEMS, SOL_FCSALESLOG

WHERE
DATA ‫כותרת‬ <CustomerRemarks /> string ‫הערות קבועות ללקוח‬ ORDERS SOL_SLSREMARKS Priority
ORDERS.ORD = ORDERITEMS.ORD

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER
SELECT ORDERS.SOL_REMARKS

FROM ORDERS, ORDERITEMS, SOL_FCSALESLOG

<SalesRemarksGen>Pre-advise shipments min 24 hrs before WHERE

DATA ‫כותרת‬ string ‫הערות של ההזמנה‬ ORDERS SOL_REMARKS Priority
delivery</SalesRemarksGen>
ORDERS.ORD = ORDERITEMS.ORD

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER
SELECT PART.PARTNAME

FROM ORDERITEMS, SOL_FCSALESLOG, PART

WHERE
‫כן‬ DATA\LINES\LINE ‫שורות‬ <PartNumber>P401-5RM4MRM-NA30</PartNumber> string ‫מק"ט לשליחה‬ PART PARTNAME Priority
PART.PART= ORDERITEMS.PART

AND SOL_FCSALESLOG.KEY =
ORDERITEMS.SOL_WONUMBER
SELECT ORDERITEMS.TQUANT

FROM ORDERITEMS, SOL_FCSALESLOG

‫כן‬ DATA\LINES\LINE ‫שורות‬ <QuantityRequested>400</QuantityRequested> string ‫כמות‬ TQUANT ORDERITEMS Priority
WHERE

SOL_FCSALESLOG.KEY = ORDERITEMS.SOL_WONUMBER
SELECT ORDERITEMS.ORDI

FROM ORDERITEMS, SOL_FCSALESLOG

‫מזהה ייחודי של‬
‫כן‬ DATA\LINES\LINE ‫שורות‬ <OrdI>1233517</OrdI> string ORDERITEMS ORDI Priority
‫השורה‬
WHERE

SOL_FCSALESLOG.KEY = ORDERITEMS.SOL_WONUMBER
SELECT ORDERITEMS.SIV_EU
‫בממשק מילוי‬
‫מחסן אנחנו‬
‫האם המקט המוזמן‬ FROM ORDERITEMS, SOL_FCSALESLOG
‫מתעדים את‬
‫כן‬ DATA\LINES\LINE ‫שורות‬ <MADE_IN_EU>N</MADE_IN_EU> string ‫יגיע ממדינת ייצור‬ ORDERITEMS SIV_EU Priority
‫המדינה שממנה‬
‫?ארופאית‬ WHERE
‫הסחורה המיוצרת‬
‫הגיעה‬
SOL_FCSALESLOG.KEY = ORDERITEMS.SOL_WONUMBER
SELECT ORDERITEMS.PICKPN
‫במידה ויש לבצע‬
Fulfilment FROM ORDERITEMS, SOL_FCSALESLOG
DATA\LINES\LINE ‫שורות‬ <PICK_PARTNO /> string ‫פה יתועד המקט שיש‬ ORDERITEMS PICKPN Priority
‫להמיר אותו כדי להגיע‬ WHERE
‫למקט המוזמן‬
SOL_FCSALESLOG.KEY = ORDERITEMS.SOL_WONUMBER
 SELECT ORDERITEMS.SLR_SAREMARKS

FROM ORDERITEMS, SOL_FCSALESLOG

‫הערות ברמת שורת‬
DATA\LINES\LINE ‫שורות‬ <SalesLineRemarks /> string ORDERITEMS SLR_SAREMARKS Priority
‫ההזמנה‬
WHERE

SOL_FCSALESLOG.KEY = ORDERITEMS.SOL_WONUMBER

9. Cancel/change outbound order:

Manually. If a WO change is needed, it’s required to cancel the WO manually in SE and FC side also and then transmit the WO again from Priority.
Once the change in WO was done in Priority, Sales operation will have the responsibility to alert FC with the changes before Packing list will be received from FC.
Mail of WO cancellation will be sent to FC as well from the system.

2. Outbound WO Acknowledgement: After the Outbound WO was processed at FC WMS system, they will send us an acknowledgement file. this will be sent after the PN's were collected in Warehouse
If all ordered PN's are recognized and available in FC stock → FC will send us acknowledgement with Status = 'True' and with 3PL WO number (FC WO after transmission) – Example: FCSE300417323661205
1. XML Filename: concatenation ('OutBoundWOACK-', <SEWONumber>)
2. XML Fields:

‫שם סגמנט חובה‬ ‫ שם השדה סוג סגמט‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬
SE Message ID

‫כן‬ DATA ‫כותרת‬ <MESSAGEID>114388<MESSAGEID> string ‫נשלח בהודעה המקורית מזהה ייחודי של‬

‫המסר המקורי‬
‫סטטוס עיבוד המסר‬

‫כן‬ DATA ‫כותרת‬ <WOStatus>False</WOStatus> string ‫ אם המסר עובד בהצלחה‬- TRUE

‫ אם התגלו שגיאות בעיבוד‬- FALSE

‫כן‬ DATA ‫כותרת‬ <DeliveryDate>2020-07-29T00:00:00</DeliveryDate> date time ‫תאריך ושעה בעת שליחת המסר‬
‫כן‬ DATA ‫כותרת‬ <SEWONumber>SE290720287417611147</SEWONumber> string ‫ מספר ייחודי שמבטא את מספר העבודה‬FC‫שייפתח ב‬ ‫נשלח בהודעה המקורית‬
‫במידה והמסר עובד בהצלחה‬

(TRUE ‫)קיבלנו סטטוס‬

‫כן‬ DATA ‫כותרת‬ <FCWONumber>FC_SE290720287417611147</FCWONumber> string
‫יחזירו את המס עבודה‬FC

+ ‫ קידומת‬FC
‫סטטוס עיבוד השורה‬

‫כן‬ DATA\LINES\LINE ‫שורות‬ <LineStatus>False</LineStatus> string ‫ אם השורה עברה בהצלחה‬- TRUE

‫ אם התגלו שגיאות בעיבוד‬- FALSE

DATA\LINES\LINE ‫שורות‬
‫כן‬ DATA\LINES\LINE ‫שורות‬
‫כן‬ DATA\LINES\LINE ‫שורות‬
‫כן‬ DATA\LINES\LINE ‫שורות‬
DATA\LINES\LINE ‫שורות‬
<FCMessage>NOT FOUND/AVAILABLE ON STOCK</FCMessage> string ‫הסבר השגיאה‬
<PartNumber>P401-5RM4MRM-NA30</PartNumber> string ‫מק"ט‬ ‫נשלח בהודעה המקורית‬
<QuantityRequested>400</QuantityRequested> string ‫כמות בהזמנה‬ ‫נשלח בהודעה המקורית‬
<OrdI>1233517</OrdI> string ‫מזהה ייחודי של השורה‬ ‫נשלח בהודעה המקורית‬
‫ במידה ויש לבצע‬Fulfilment
<PICK_PARTNO /> string ‫נשלח בהודעה המקורית‬
‫פה יתועד המקט שיש להמיר אותו כדי להגיע למקט המוזמן‬

3. BI ETL Tool will fisrt check if the <ORDERID> exists in SE DB. If not, will send back XML file as follows: (to the subfolder 'FC')
0. XML Filename: concatenation ('OutBoundWOACK-', <SEWONumber>)
1. XML Fields:

‫חובה‬ ‫שם סגמנט‬ ‫סוג סגמט‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬
‫תעודת העברה בין מחסנים בפריוריטי‬
‫כן‬ DATA ‫כותרת‬ <SEWONumber>SE290720287417611147</SEWONumber> string ‫נשלח בהודעה המקורית‬

‫כן‬ DATA ‫כותרת‬ <Status>Fail</Status> string ‫סטטוס בדיקת המסר‬

‫כן‬ DATA ‫כותרת‬ <StatusDesc>Order ID/WO# <SEWONumber> does not exist in SE DB Or was cancelled Please check the request again</StatusDesc> string ‫תיאור השגיאה‬

2. If they were able to insert the file successfully it will be count as Technical Acknowledgement => Success
3. If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
4. If WO exists, BI will update the status of this request in our FC Interface Control table and will send E-mail to Sales, Operations and WH in case of Fail
3. In the case of TRUE BI will update Order lines with FC WO number

Sales Development Details (For customer)

Send Outbound WO - Sales Development Details

Actions - Priority Dev

Send Outbound WO - Priority Dev

Actions - ETL
Send Outbound WO - BI

Example for XML file

Packing list creation
General
1. Inbound/Outbound: Outbound
2. Purpose:
1. The Packing list creation interface is an Outgoing interface from FC- its purpose is to alert SE that the goods are on the way to the customer and to open customer shipments in the system.
2. After finishing the pick & pack of the goods, palletizing and closing the work order, FC should provide the relevant information to SE, so SE will do the customer shipment document.
3. Customer shipment is the Inventory transaction that reduces the parts from SEIL inventory and changes the status of the Serial Numbers to be associated with the customer.
4. Packing List needs to be created and printed to accompany the physical shipment.
3. How it works:
1.
1. FC will send an XML file to FC FTP Folder (to 'FC' sub-folder)
2. XML Filename: concatenation ('OutBoundWOPL' + <FCWONumber>)
3. XML Fields:

‫סוג‬ Form Constant Value / Priority - ETL -

‫שם סגמנט חובה‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬ Form Field name Priority Source
‫סגמט‬ Type Calculation Logic Done Done
‫ התקבל במסר של תעודת הזמנת לקוח‬Outbound 
‫כן‬ DATA ‫< כותרת‬ORDERID>SOL2007186</ORDERID> string Form DOCUMENTS_D SIV_ORDNAME Priority 
‫ בפריוריטי‬WO
‫מזהה ייחודי של המחסן‬
‫המקבל בפריוריטי‬

:‫תאור מחסן‬
‫ התקבל במסר של‬Outbound
‫כן‬ DATA ‫< כותרת‬WarehouseCode>61</WarehouseCode> string Form DOCUMENTS_D WARHS Priority
WH: SEIL WO

Bin: Sales

‫ התקבל במסר של‬FC

‫מספר ייחודי שמבטא את‬
Outbound WO ACK 
‫כן‬ DATA ‫< כותרת‬FCWONumber>FC_SE290720287417611147</FCWONumber> string ‫מספר העבודה‬ Form DOCUMENTS_D SOL_WONUMBER Priority 
FC‫שנפתח ב‬

‫פורמט‬
‫תאריך השליחה של‬ 
‫כן‬ DATA ‫< כותרת‬CurrentDATE>2020-03-12 14:28:10</CurrentDATE> datetime 
‫המסר‬ YYYY-MM-DD
HH:MM:SS
‫ התקבל במסר של‬Outbound 
‫כן‬ DATA\LINES\LINE ‫שורות‬ <OrdI>1233517</OrdI> string ‫מזהה ייחודי של השורה‬ Form TRANSORDER_D ORDI Priority 
WO

‫כן‬ DATA\LINES\LINE ‫שורות‬ <PartNumber>P401-5RM4MRM-NA30</PartNumber> string ‫מק"ט‬ Form TRANSORDER_D PARTNAME Priority 


‫כן‬ DATA\LINES\LINE ‫שורות‬ <Quantity>400</QuantityRequested> string ‫כמות שנשלחה‬ Form TRANSORDER_D TQUANT Priority 

If type = 'PALLET'

Then go
to SLR_PALLETDOC
form with
Field: PALLETNUM
SLR_PALLETDOC PALLETNUM
If type = 'BOX'
‫פירוט‬ 
DATA\LINES\LINE\BOX_SN_LEVEL <Type>SERIAL</Type> string ‫סוג פירוט שורת השילוח‬ SERIAL/BOX/PALLET Form SERNTRANS BOXNAME Priority 
‫שורה‬ Then go
to SLR_PALLETDOC
SERNUM
form with
Field: BOXNAME

If type = 'SERIAL'

Then go to SERNTRANS
form
SLR_PALLETDOC PALLETNUM
‫פירוט‬ <Pallet_Box_SerialNumber>SJ1820-07E098BFA- ‫מספר‬
DATA\LINES\LINE\BOX_SN_LEVEL string SERNTRANS BOXNAME
‫שורה‬ 0C</Pallet_Box_SerialNumber> Pallet/Box/Serial
SERNUM
‫פרטי‬
DATA\PACKAGEDETAILES <NetWeight>45.89</NetWeight> string ‫משקל אריזה נטו‬
‫אריזה‬
‫פרטי‬
DATA\PACKAGEDETAILES <GrossWeight>789.90</GrossWeight> string ‫משקל אריזה ברוטו‬
‫אריזה‬
‫פרטי‬
DATA\PACKAGEDETAILES <WeightUnit>kg</WeightUnit> string ‫יחידת מידה של המשקל‬ ‫קבוע‬
‫אריזה‬
‫פרטי‬
DATA\PACKAGEDETAILES <Length>89.56</Length> string ‫אורך החבילה‬
‫אריזה‬
‫פרטי‬
DATA\PACKAGEDETAILES <Width>58.11</Width> string ‫רוחב החבילה‬
‫אריזה‬
‫פרטי‬
DATA\PACKAGEDETAILES <Height>156.77</Height> string ‫גובה החבילה‬
‫אריזה‬
 ‫פרטי‬ ‫יחידה מידה של גודל‬
DATA\PACKAGEDETAILES <SizeUnit>cm</SizeUnitt> string ‫קבוע‬
‫אריזה‬ ‫החבילה‬
‫פרטי‬
DATA\PACKAGEDETAILES <Volume>45.66</Volume> string ‫נפח החבילה‬
‫אריזה‬
‫פרטי‬ ‫יחידת מידה של נפח‬
DATA\PACKAGEDETAILES <VolumeUnit>cu</VolumeUnit> string ‫קבוע‬
‫אריזה‬ ‫החבילה‬

4. BI will check if the <FCWONumber> exists in SE DB. If not, will send back XML file as follows: (to the subfolder 'FC')
3.1.4.1. XML Filename: concatenation ('OutBoundPL-',<ORDERID>)
3.1.4.2. XML Fields:

‫חובה‬ ‫שם סגמנט‬ ‫סוג סגמט‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬
‫תעודת העברה בין מחסנים בפריוריטי‬
‫כן‬ DATA ‫כותרת‬ <FCWONumber>FC_SE290720287417611147</FCWONumber> string ‫נשלח בהודעה המקורית‬

‫כן‬ DATA ‫כותרת‬ <Status>Fail</Status> string ‫סטטוס בדיקת המסר‬

‫כן‬ DATA ‫כותרת‬ <StatusDesc>FC WO Number <FCWONumber> was not received in SE. Solution: Please send Outbound WO ack and then send the PL again</StatusDesc> string ‫תיאור השגיאה‬

3.1.4.3. If they were able to insert the file successfully it will be count as Technical Acknowledgement => Success
3.1.4.4. If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
3.1.5. If FC WO Number exists, BI ETL Tool will take the XML file and run SP that will check that the request is proper - Validations:

Validation Error message

Mandatory fields are filled <Field Name> is missing data
CS doc was already opened in Priority for FC WO number Packing List already created in SE ERP System for <FCWONumber>
Ship Items are not listed in Request → No details of shipped goods in request Ship Items are not listed in Request for FC WO number
Qty in Pallet/Box/Serial is equal to Quantity in request Qty <Quantity> in PL ship item <ORDI> is not the same as the quantity that actually exists in the warehouse
The part number <PartNumber> does not exist in this company.
Check if Part Number exists in solar DB
Solution: Please send SE the TRL source and picture of the serial.
The part number <PartNumber> is missing a Serial\Box\Pallet.
Part Number is missing Box/Serial /Pallet level
Solution: Please check the serial definition at FC side.
For Type = 'BOX'. Box No. <Pallet_Box_SerialNumber> does not exist in this company.
Check if the box exists in the DB Solution: Please send SE the TRL source and picture of the Box.
For Type = 'BOX'.
Check warehouse and part number for serials in box <Pallet_Box_SerialNumber>.
Solution: Please check the box definition at FC side
Check that SN's in Box are located in SEIL WH and are linked to PN in ship item
For Type = 'PALLET'.
Pallet No. <Pallet_Box_SerialNumber> does not exist in this company.
Solution: Please send SE the TRL source and picture of the Pallet.
Check if the Pallet exists in the DB
For Type = 'PALLET'.
Check warehouse and part number for serials in Pallet <Pallet_Box_SerialNumber>.
Solution: Please check the Pallet definition at FC side
Check that SN's in Pallet are located in SEIL WH and are linked to PN in ship item
For Type = 'SERIAL'.
Serial No. <Pallet_Box_SerialNumber> does not exist in this company.
Solution: Please send SE the TRL source and picture of the Serial.
Check if the Serial exists in the DB
For Type = 'SERIAL'. The serial number <Pallet_Box_SerialNumber> does not exist in the warehouse.
Check that SN is located in SEIL WH Solution: Please verify that it was not scanned to another shipping docs OR verify that this serial shouldn’t be on hold.
Scanned PN <Pallet_Box_SerialNumber> doesn't match associated PN <PartNumber>
For Type = 'SERIAL'.
Check that SN is located in SEIL WH
Solution: please verify that the serial and the order PN are exactly the same.

3.1.6. PL Acknowledgement:
3.1.6.1. XML Filename: concatenation ('OutBoundWOPLACK' + <FCWONumber>)
3.1.6.2. XML Fields:

‫שם‬ ‫סוג‬ ‫סוג‬

‫חובה‬ ‫ שם השדה‬XML ‫הסבר‬
‫סגמנט‬ ‫סגמט‬ ‫דטה‬
SE Message ID

‫כן‬ DATA ‫כותרת‬ <MESSAGEID>114388<MESSAGEID> string ‫מזהה ייחודי של‬

‫המסר המקורי‬
‫מספר ייחודי שמבטא את מספר העבודה‬
‫כן‬ DATA ‫כותרת‬ <FCWONumber>FC_SE290720287417611147</FCWONumber> string
FC‫שנפתח ב‬
‫סטטוס עיבוד המסר‬

‫כן‬ DATA ‫כותרת‬ <StatusDesc>FALSE</StatusDesc> string ‫ אם המסר עובד בהצלחה‬- TRUE

‫ אם התגלו שגיאות בעיבוד‬- FALSE

<ErrorDesc>The serial number does not exist in the warehouse. SJ1720-112205B48-D5. Solution: Please verify that it was not scanned to another shipping docs OR verify that this serial shouldn't be on
‫כן‬ DATA ‫כותרת‬ string ‫תיאור השגיאה‬
hold.</ErrorDesc>

3.1.6.3.
3.1.6.4. If the request is proper →
3.1.6.5. BI will create an XML file for PL Acknowledgement with status 'TRUE'.
 3.1.6.6. And will open Customer Shipment Document (If the Order is internal will open WH Transfer) in the system.
3.1.6.6.1. If BI successfully manage to finalize this doc → the system will send an e-mail + PL print
3.1.6.6.1.1. Fulfilment team
3.1.6.6.1.2. Logistic team
3.1.6.6.1.3. WH team
3.1.6.6.1.4. FC team
3.1.6.7. If not, System will send Error description to the users above (Without FC)
3.1.7. If the request is not proper →
3.1.7.1. BI will create an XML file for PL Acknowledgement with status 'FALSE' and description of error as described above and will not enable the creation of the packing list.
3.1.7.2. If they were able to insert the file successfully it will be count as Technical Acknowledgement => Success
3.1.7.3. If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
3.1.8. BI will update the status of this request in our FC Interface Control table.
3.2. Exceptions:
If the actual quantity sent does not match the quantity from the request sent by SE → Send Partial QTY

Actions - Priority Dev

Actions - ETL

Logistic Data
General
1. Inbound/Outbound: Outbound
2. Purpose: This interface will add operational data on the Packing List that was sent to the customer.
3. How it works:
1.
1. FC will send an XML file to FC FTP Folder (to 'FC' sub-folder)
2. XML Filename: concatenation ('LogisticDataPL-' + <DOCID>)
3. XML Fields:

‫סוג‬ Form Constant Value / Calculation Priority - ETL -

‫שם סגמנט חובה‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬ Form Field name Priority Source
‫סגמט‬ Type Logic Done Done
‫מספר תעודת המשלוח‬SE ‫שנפתחה‬
‫ נשלח‬- ‫כאשר התעודה נסגרה בהצלחה במערכת‬
‫ב‬
FC‫מייל ל‬ 
‫כן‬ DATA ‫כותרת‬ <DOCID>SHL2053521</DOCID> string Form CHNGDOCUMENTS_D DOCNO Priority 
‫על בסיס‬
‫עם הדפסת התעודה‬
PL Request

‫כן‬ DATA ‫כותרת‬ <TrackingNo>TLB0233478</TrackingNo> string ‫ מספר מעקב אצל‬FC Form CHNGDOCUMENTS_D AIRWAYBILL Priority 

‫פורמט‬
<CurrentDATE>2020-03-12 
‫כן‬ DATA ‫כותרת‬ datetime ‫תאריך השליחה של המסר‬ Flying Cargo 
14:28:10</CurrentDATE>
YYYY-MM-DD HH:MM:SS

‫כן‬ DATA ‫כותרת‬ <FORWARDER>Flying Cargo</FORWARDER> string ‫ קבוע‬- ‫מאחסן‬ Form CHNGDOCUMENTS_D DOCREF Priority 


DATA ‫כותרת‬ <ETA>2020-08-18</ETA> string Estimated Arrival Time Form CHNGDOCUMENTS_D SLR_ETA Priority 


DATA ‫כותרת‬ <POD>2020-08-18</POD> string Proof of Delivery Form CHNGDOCUMENTS_D SLR_POD Priority 

CHNGDOCUMENTS_D

DATA ‫כותרת‬ <PICKDATE>2020-08-18</PICKDATE> string Pick Up Date Form SIV_PICKUPDATE Priority 

CHNGDOCUMENTS_D
DATA ‫כותרת‬ <DEPARTURE>2020-08-18</DEPARTURE> string Departure date Form SLR_DEPARTUREDATE Priority

4. BI will check if the <DOCID> exists in SE DB. If not, will send back XML file as follows: (to the subfolder 'SE')
5. XML Filename: concatenation ('LogisticDataPL-',<DOCID>)
6. XML Fields:

‫חובה‬ ‫שם סגמנט‬ ‫סוג סגמט‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬

‫כן‬ DATA ‫כותרת‬ <DOCID>SHL2053521</DOCID> string ‫נשלח בהודעה המקורית‬
‫כן‬ DATA ‫כותרת‬ <Status>Fail</Status> string ‫סטטוס בדיקת המסר‬
‫כן‬ DATA ‫כותרת‬ <StatusDesc>CS no. @Key does not exist in SE DB Or was cancelled. Please check CS doc again OR Contact SE</StatusDesc> string ‫תיאור השגיאה‬

1. If they were able to insert the file successfully it will be count as Technical Acknowledgement => Success
2. If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
7. If <DOCID> exists, then BI ETL Tool will update the PL logistic data in Revision of Final Shipping Doc form.
0. If the update was done successfully: the system will send an e-mail to:
1. Fulfilment team
2. Logistic team
3. WH team
4. FC Team
1. If not, System will send Error description to the users above (Without FC)
8. BI will update the status of this request in our FC Interface Control table.

Part Interface
General
1) Inbound/Outbound: Inbound
2) Purpose:
This interface is required in order to add new/Update SE products to FC WMS.
When a new part number is created or Updated in SE a request will be transmitted to DBS.
3) How it works:
a) The request will be activated automatically from Priority:
i) when Part Number is Created in Priority
ii) when Part Number is Updated in Priority
b) The request will be transmitted to FC for Parts that meet the following conditions:
i) Type <> ‘O’
ii) Product group NOT IN(US, EMP)
iii) Family type = 'Inverters','Optimizers','Spares','Options', 'Accessories' OR family = 'Others','Zigbee'
c) BI Integration tool will convert the request to an XML file that will be transferred to FC FTP folder (In 'SE' sub-folder)
i) If they were able to insert the file successfully it will be count as Technical Acknowledgement => Success
ii) If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
d) XML Filename: concatenation ('PartInterface-',<PartNumber>)
e) XML Fields:

‫שם‬ ‫סוג‬ ‫סוג‬ Form Field name Priority - ETL -

‫חובה‬ ‫ שם השדה‬XML ‫הסבר‬ ‫הערות‬ Form Source Constant Value / Calculation Logic
‫סגמנט‬ ‫סגמט‬ ‫דטה‬ Type Priority Done Done
SE Message ID

‫כן‬ DATA ‫כותרת‬ <MESSAGEID>114388<MESSAGEID> string ‫מזהה ייחודי של המסר‬ Form SOL_FCSALESLOG MESSAGEID Priority 

‫ יישמרו את‬FC ‫המספר בצד‬

- ‫מאחסן‬ 
‫כן‬ DATA ‫כותרת‬ <CONSIGNEE>solaredge</CONSIGNEE> string Constant SOLAREDGE 
‫קבוע‬
‫פורמט‬
‫תאריך שבו המסר נשלח‬
<SENTTIMESTAMP>2020-07-
‫כן‬ DATA ‫כותרת‬ string YYYY-MM-DD Form SOL_FCSALESLOG DATETIME Priority
29</SENTTIMESTAMPE>


‫כן‬ DATA ‫כותרת‬ <SKU>SE10K-RWHDCBNN4</SKU> string ‫מק"ט‬ Form SOL_FCSALESLOG KEY Priority 

SELECT PART.PARTDES

FROM PART, SOL_FCSALESLOG


‫כן‬ DATA ‫כותרת‬ <SKUDESC>Inverter, 10KVA, BE, MC4</SKUDESC> string ‫תיאור מק"ט‬ Form PART PARTDES Constant 
WHERE

SOL_FCSALESLOG.KEY = PART.PARTNAME
SELECT UNIT.UNITNAME

FROM PART, SOL_FCSALESLOG, UNIT

SE ‫ תשלח‬FC‫ל‬

‫כן‬ DATA ‫כותרת‬ <UNIT>pc</UNIT> string ‫יחידת מידה‬ Form UNIT UNITNAME Priority WHERE 
‫רשימת יחידות מידה מראש‬
SOL_FCSALESLOG.KEY = PART.PARTNAME

AND UNIT.UNIT = PART.UNIT

SELECT PARTSTATS.STATDES

FROM PART, SOL_FCSALESLOG, PARTSTATS

‫ = אם סטטוס‬Inactive
‫כן‬ DATA ‫כותרת‬ <STATUS>In Use</STATUS> string ‫סטטוס המוצר‬ PARTSTATS STATDES Priority WHERE
‫מקט זה לא יהיה בשימוש‬
FC
SOL_FCSALESLOG.KEY = PART.PARTNAME

AND PARTSTATS.PARTSTAT= PART.PARTSTAT

SELECT PARTSPEC.SPEC6

FROM PART, SOL_FCSALESLOG, PARTSPEC


DATA ‫כותרת‬ <SKUGROUP>Jupiter Plus ROW HP LX</SKUGROUP> string Sub-Group Form PARTSPEC SPEC6 Priority WHERE 

SOL_FCSALESLOG.KEY = PART.PARTNAME

AND PARTSPEC.PART= PART.PART

SELECT PARTPARAM.INVFLAG

FROM PART, SOL_FCSALESLOG, PARTPARAM

‫כן‬ DATA ‫כותרת‬ <MAINTAININV>Y</MAINTAININV> string ‫?מנוהל מלאי‬ Form PARTPARAM INVFLAG Priority WHERE

SOL_FCSALESLOG.KEY = PART.PARTNAME

AND PARTSPEC.PART= PARTPARAM.PARTPARAM

 SELECT PART.SERNFLAG

FROM PART, SOL_FCSALESLOG


‫כן‬ DATA ‫כותרת‬ <MAINTAINSN>Y</MAINTAINSN> string ‫?מנוהל סיריאלים‬ Form PART SERNFLAG Priority 
WHERE

SOL_FCSALESLOG.KEY = PART.PARTNAME
SELECT FAMILY.SIV_WEIGHT

FROM PART, SOL_FCSALESLOG, FAMILY


DATA ‫כותרת‬ <WEIGHT/> string ‫משקל‬ Form FAMILY_LOG SIV_WEIGHT Priority WHERE 

SOL_FCSALESLOG.KEY = PART.PARTNAME

AND FAMILY.FAMILY = PART.FAMILY

SELECT FAMILYTYPES.FTNAME

FROM PART, SOL_FCSALESLOG, FAMILY, FAMILYTYPES

WHERE

‫כן‬ DATA ‫כותרת‬ <FAMILYTYPE>Optimizers</FAMILYTYPE> string ‫טיפוס משפחה‬ Form FTNAME FAMILYTYPES Priority 
SOL_FCSALESLOG.KEY = PART.PARTNAME

AND FAMILY.FAMILY = PART.FAMILY

AND FAMILYTYPES.FAMILYTYPE
= FAMILY.FAMILYTYPE

4) Part Interface Acknowledgement: After the Part Interface was processed at FC WMS system, they will send us an acknowledgement file (to subfolder 'SE') Part Interface ACK XML
a) XML Filename: concatenation ('PartInterfaceACK-',<SKU>)
b) In phase 1 -
0. Success -it was agreed that FC will send us the same ASN Inbound request that was sent to them
1. Fail - FC will send to SE E-mail address (Will be given later) the error in the following format:
(1) Mail Subject: concatenation ('PartInterfaceACK',<SKU>, 'Errors received while processing Part Interface' )
(2) Mail Content: Message Description
c) In Phase 2 - FC will send us an acknowledgement file in the following format:
d) XML Fields:

‫שם סגמנט חובה‬ ‫ שם השדה סוג סגמט‬XML ‫הסבר סוג דטה‬ ‫הערות‬
SE Message ID

‫כן‬ DATA ‫כותרת‬ <MESSAGEID>114388<MESSAGEID> string ‫נשלח בהודעה המקורית מזהה ייחודי של‬

‫המסר המקורי‬
‫סטטוס עיבוד המסר‬

‫כן‬ DATA ‫כותרת‬ <Status>False<Status> string ‫ אם המסר עובד בהצלחה‬- TRUE

‫ אם התגלו שגיאות בעיבוד‬- FALSE

‫תעודת העברה בין מחסנים בפריוריטי‬
‫כן‬ DATA ‫כותרת‬ <ORDERID>TRL2013638</ORDERID> ‫נשלח בהודעה המקורית‬
(#TRL)
‫כן‬ DATA\LINES\LINE ‫שורות‬ <REFERENCEORDLINE>10207822</REFERENCEORDLINE> string ‫מזהה ייחודי של השורה בתעודה‬ ‫נשלח בהודעה המקורית‬
‫כן‬ DATA\LINES\LINE ‫שורות‬ <Message>Part_Number_unknown</Message> string ‫ = תאור ההודעה במידה וסטטוס‬FALSE

5) According to the acknowledgement Mail/XML that was sent,

6) BI will check if the <ORDERID> exists in SE DB.
a) If not, will send back XML file as follows: (to the subfolder 'FC')
b) XML Filename: concatenation ('InBoundASNACK-',<ORDERID>)
c) XML Fields:

‫חובה‬ ‫שם סגמנט‬ ‫סוג סגמט‬ ‫ שם השדה‬XML ‫סוג דטה‬ ‫הסבר‬ ‫הערות‬
‫תעודת העברה בין מחסנים בפריוריטי‬
‫כן‬ DATA ‫כותרת‬ <ORDERID>TRL2013638</ORDERID> string ‫נשלח בהודעה המקורית‬

‫כן‬ DATA ‫כותרת‬ <Status>Fail</Status> string ‫סטטוס בדיקת המסר‬

‫כן‬ DATA ‫כותרת‬ <StatusDesc>Request ID <ORDERID> does not exist in SE DB Or was cancelled Please check the request again</StatusDesc> string ‫תיאור השגיאה‬ ‫חובה‬

d) If they were able to insert the file successfully to FTP file it will be count as Technical Acknowledgement => Success
e) If not, BI will try to insert the file 3 times → If the operation is not completed successfully it will be count as Technical Acknowledgement => Fail and will send to FC distribution mail about the Failure
7) if the <ORDERID> exists in SE DB, BI will update the status of this request in our FC Interface Control table and will send E-mail to Sales, Operations and WH about this error.

Actions - Priority Dev

ASN (Advanced Shipment Notification) - Priority Dev

Actions - ETL
ASN (Advanced Shipment Notification) - BI

Example for XML file

Inventory Interface
General
1. Inbound/Outbound: Inbound
2. Purpose:
This interface is required in order to compare the inventory in Priority and the inventory in 3PL WMS.
3. How it works:
1. FC will provide to SE a daily CSV/XML file with Warehouse the part number and its quantity.
2. BI will Will pull the inventory information from SE ERP system as well
3. BI will build a dashboard to SE Sales users that will compare inventory levels and control inventory levels.
4. CSV/XML Filename: concatenation ('Inventory-',<Current Date>)
5. CSV/XML Fields:

‫שם סגמנט חובה‬ ‫סוג סגמט‬ ‫ שם השדה‬XML ‫הסבר סוג דטה‬ ‫הערות‬ Form Type Form Field name Priority Source Constant Value / Calculation Logic Priority - Done ETL - Done
‫פורמט‬
‫תאריך שבו המסר נשלח‬

‫כן‬ DATA ‫כותרת‬ <SENTTIMESTAMP>2020-07-29</SENTTIMESTAMPE> string YYYY-MM-DD Form Current Date 

‫מזהה ייחודי של המחסן בפריוריטי‬

:‫ תאור מחסן‬SE ‫ תשלח‬FC‫ל‬


‫כן‬ DATA ‫כותרת‬ <Warehouse>614 </Warehouse> string Form WARHSBAL WARHS Priority 
WH: SEIL ‫רשימת קודי מחסנים מראש‬

Bin: Sales
SELECT PART.PARTNAME

‫כן‬ DATA ‫כותרת‬ <SKU>SE10K-RWHDCBNN4</SKU> string ‫מק"ט‬ Form PART PARTNAME Priority FROM WARHSBAL, PART 

WHERE PART.PART = WARHSBAL.PART

‫כן‬ DATA ‫כותרת‬ <BALANCE>20</BALANCE> string ‫יתרה במחסן‬ Form WARHSBAL TBALANCE Priority