EDI ADHOC | Multiflex Help

📄 AdHoc EDI POLLEX-Integration (EDIWheel)

Überblick

POLLEX-LC unterstützt das Senden und Empfangen von EDIWheel AdHoc Nachrichten.

Unterstützte Funktionen

Zuordnung von Käufer, Besteller und Lieferadresse
Ermittlung des Lagers für Lagerbestands-Rückmeldungen
Erweiterungen des EDIWheel-Standards:
- Freie Lieferadressen
- Artikelzuordnung
- Auslieferungslager
Dynamische Konvertierung beim Export (Werte-Übersetzer)

Nachrichtentypen

Typ	Beschreibung
inquiry_A2	Bestellanfrage
inquiry_response_A2	Antwort auf Bestellanfrage
order_A2	Bestellung
order_response_A2	Bestellbestätigung
quote_A2	Bestandsinformation

Partner-Zuordnung

Die Zuordnung erfolgt über:

<BuyerParty />
<OrderingParty />
<Consignee />

AgencyCode

Code	Bedeutung
9	EAN (GLN)
91	Lieferantennummer (Standard)
92	Käufernumer

👉 Empfohlen: 91 (Lieferantennummer)

Lagerermittlung

Standard: Summe aller Lager mit Eigenschaft „AdHoc“
Optional: Einschränkung über <StockNumber>
Maximalbestände werden berücksichtigt (Abrundung)

Freie Lieferadresse

<DeliveryAddress>
  <Name1 />
  <Name2 />
  <Attn />
  <Street />
  <POBox />
  <CountryCode />
  <PostCode />
  <CityName />
</DeliveryAddress>

Artikelzuordnung

Standard:

<EANUCCArticleID />

Alternative:

<ManufacturersArticleID />

Auslieferungslager (optional)

<DeliveryFromStockNo>
  <StockNo>1</StockNo>
</DeliveryFromStockNo>

⚠️ Wichtig:

Muss abgestimmt sein
Falsche Lagernummer → Bestellung wird abgelehnt

Kommunikation

Über Webservices (HTTP / HTTPS)
Zugangsdaten werden abgestimmt

Dynamischer Werte-Übersetzer

Funktionen

Funktion	Beispiel	Beschreibung
`@GetVar(name)`	`@GetVar("request.StockNumber")`	Liefert interne Variable

Erweiterte Konfiguration

Sektion	Key	Gültig für	Beispiel	Beschreibung
WebRequest	Timeout	AdHocOrder	600	Timeout in Sekunden (Standard: 100)

Trigger

Trigger	Beschreibung
PurchaseOrder.Update	Erfolgreiche Bestellung (inkl. Lieferdatum oder Fremdnummer)
PurchaseOrderResponse.Imported	Immer nach Bestellung (egal ob erfolgreich oder nicht)

Sonderfunktionen (StringFunctions)

Funktion	Beschreibung
`@GetTransactionInx()`	Transaktionsindex
`@GetRequestContent()`	Gesendetes XML (Logging)
`@GetResponseContent()`	Antwort-XML (Logging)

Inquiry XML (Beispiel)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE inquiry_A2 SYSTEM "inquiry_A2.dtd"[]>
<inquiry_A2>
  <CustomerReference>
    <DocumentID>Version A2 Inquiry</DocumentID>
  </CustomerReference>
  <BuyerParty>
    <PartyID>2</PartyID>
    <AgencyCode>91</AgencyCode>
  </BuyerParty>
  <OrderLine>
    <LineID>1</LineID>
    <OrderedArticle>
      <ArticleIdentification>
        <EANUCCArticleID>8808563338118</EANUCCArticleID>
        <Matchcode/>
        <POLLEXItemNumber>P-5653</POLLEXItemNumber>
      </ArticleIdentification>
      <RequestedQuantity>
        <QuantityValue>1</QuantityValue>
      </RequestedQuantity>
    </OrderedArticle>
  </OrderLine>
</inquiry_A2>

Order XML (Beispiel)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE order_A2 SYSTEM "order_A2.dtd">
<order_A2>
  <DocumentID>A2</DocumentID>
  <CustomerReference>
    <DocumentID>2015076</DocumentID>
  </CustomerReference>

  <DeliveryAddress>
    <Name1 />
    <Name2 />
    <Attn />
    <Street />
    <POBox />
    <CountryCode />
    <PostCode />
    <CityName />
  </DeliveryAddress>

  <BuyerParty>
    <PartyID>857244</PartyID>
    <AgencyCode>91</AgencyCode>
  </BuyerParty>

  <DeliveryFromStockNo>
    <StockNo>1</StockNo>
  </DeliveryFromStockNo>

  <OrderLine>
    <LineID>1</LineID>
    <OrderedArticle>
      <ArticleIdentification>
        <EANUCCArticleID>8714692282089</EANUCCArticleID>
        <Matchcode/>
        <POLLEXItemNumber>20003</POLLEXItemNumber>
        <BePosInx>477</BePosInx>
      </ArticleIdentification>
      <RequestedQuantity>
        <QuantityValue>4</QuantityValue>
      </RequestedQuantity>
      <AdditionalText/>
      <RequestedDeliveryDate>20190417</RequestedDeliveryDate>
    </OrderedArticle>
  </OrderLine>
</order_A2>

Reifenhersteller (Auszug)

Hersteller	Besonderheiten
MICHELIN	Version A2.5, echtes Lieferdatum
FALKEN	EDI Webservice verfügbar

💡 Hinweise

Erweiterungen sind kompatibel mit gängigen Reifenherstellern
Dynamischer Werte-Übersetzer ermöglicht flexible Anpassung
Logging-Funktionen sind für Debugging essenziell

Sonderfälle

Falken

Beim Hersteller FALKEN ist es für die erfolgreiche Übermittlung der AdHoc Anfragen und Bestellungen einen Eintrag im dynamischen Werte Übersetzer zu erstellen. Dazu am besten die folgende Datei im dynamischen Werte Übersetzer importieren:

AdHocFalken.xml

Probleme/Fehlercodes

Fehleranalyse bei EDI ADHOC.

Logging bei ADHOC aktivieren
select * from grundlagen_werte;

Logging deaktivieren
delete from grundlagen_werte where name like 'LogDirAdHocSendWebRequest%';

Logging aktivieren
Ordner muss vorhanden sein!
insert into grundlagen_werte (name,wert) values ( 'LogDirAdHocSendWebRequest','C:\inetpub\wwwroot\LC.NET\Company\LogFiles\XXX' );

Fehlercodes ADHOC

Bei der Übermittlung einer ADHOC EDI Nachricht werden bei Problemen Fehlercodes von der Gegenseite übermittelt.

Anbei die Liste von Michelin und Bridgestone.

Lösung

Error code	Michelin	Bridgestone
0	No errors occurred	No errors occurred
1	At least one item is incorrect. Details are distinctive in the error field on item level	something wrong in one of the items
301	No connection to ERP system (order)	No connection to ERP system (order)
302	No connection to ERP system (inquiry)	No connection to ERP system
303	No connection to ERP system	Timeout to ERP system
304	Request to ERP - System disconnected
399	Miscellaneous - connection error	Miscellaneous - connection error
401	Timeout during inquiry processing in ERP	Timeout during inquiry processing in ERP
402	Error during inquiry processing in ERP
403	Error during order processing in ERP	Error during order processing, connection broken
404	Order only processed partially	Order only processed partially. Item could not be created.
405	Timeout during processing in ERP system
405	Timeout during processing in ERP system
499	Miscellaneous - processing error	Miscellaneous - processing error
901	Document number invalid [identification number of document, blanket order reference, customer reference, additional customer reference number]	Docu ID invalid
902	Too many items (order lines, despatch note lines)	Too many items in the order (supplier specific)
903	Invalid article identification code
904	Quantity value invalid, must be greater than 0
905	No items in message	No items in message
906	Customer reference number already used - (valid only for orders where the reference MUST be unique)	Reference number already used - (valid only for Orders where the ref.MUST be unique)
907	Invalid consignee (ship-to) party ID number
908	No authority to select consignee (ship-to)	No authority to select ship-to
909	The mandatory customer reference number is missing in the order	Reference nr. is empty - mandatory for orders only
910	Internal error in ad hoc system	Internal error in ad hoc System
911	Incorrect EAN number (not known on supplier side)	? Ev. Artikel nicht erkannt, Ev. Herstellerartikelnummer nicht übergeben
912	Requested delivery date invalid	Delivery date invalid
913	Invalid consignee (ship-to) party ID number	Ship-to party invalid
914	Missing buyer (sold-to) identification number	Missing sold-to number in message
915	Buyer (sold-to) party ID number invalid	customer code invalid
916	Adhoc version number incorrect (document ID or variant)	adhoc version number incorrect
917	Incorrect ad hoc message type	Incorrect message type
918	No authority to specify earliest requested (header level) or requested (item level) delivery date	No authority to specify delivery due date
919	No authority for brand/sales organisation	No authority for Brand/sales organisation
920	Account not activated for this buyer (sold-to) party ID number	Sold-to customer not activated
921	Access permission password is expired	Access permission password is expired
922	Incorrect/invalid blanket order (contract) number	Incorrect/invalid contract number
924	Incorrect buyer (sold-to) agency code qualifier	Incorrect sold-to qualifier
925	Incorrect consignee (ship-to) agency code qualifier	Incorrect ship-to qualifier
926	Missing mapping for the customer assigned buyer (sold-to) party ID	Missing mapping for the sold-to external number
927	Missing mapping for the customer assigned consignee (shipto) party ID	Missing mapping for the ship-to external number
928	Mandatory EAN code missing for this line
929	Incorrect promotion (campaign) code (wrong value)	Incorrect promotion code (wrong value)
930	Incorrect payment method code	incorrect payment method code
931	Material definition error in supplier system (sales view, plant view, prices etc)
932	Buyer (sold-to) definition error in supplier system (sales area, deletion indicator etc.)	Sold-to definition error in supplier system. (sales area, deletionindicator etc)
933	This material can not be ordered via ad hoc EDI EDI (In this case a substituting article can be proposed if the substitution indicator has been flagged in the inquiry).
934	Customer not allowed to create backorders	Customer not allowed to create backorders
935	Order can not be created, at least one line is in error	Order can not be created, at least one line is in error
936	Wrong buyer - consignee combination (sold-to/ship-to combination)	Wrong sold-to ship-to combination
937	Consignee (ship-to) definition error in supplier system (sales area, deletion indicator etc.)	Ship-to definition error in supplier system. (sales area, deletionindicator etc)
938	All items in error, no sales order created	All items in error, no sales order created
939	Wrong or not allowed order type (transport priority)	Order type wrong or not allowed
940	Incorrect supplier material number (not known on supplier side)
941	Wrong EAN/supplier material number combination
942	Maximum allowed quantity overpassed
943	Error in ERP system during creation of sales order	Error in ERP system during creation of sales order
944	Promotion (campaign) code validity period expired	Promotion code validity expired
945	Material status set to not sellable (material can not be purchased anymore) ( In this case a substituting article can be proposed if the substitution indicator has been flagged in the inquiry).
946	Ad hoc version number missing
950	No authority to use this message type
970	Manufacturers order number invalid or not found
971	Customers order number invalid or not found
972	Requested delivery date out of authorised period horizon
973	Material is temporarily orderable only by phone. For more details contact the call centre ( In this case a substituting article can be proposed if the substitution indicator has been flagged in the inquiry).
974	The ordered quantity is not equal to he content of the packaging, or does not correspond to the multiple of the packaging content.
975	Quantity value invalid. Must be an integer value.
999	Miscellaneous	Miscellaneous content error

Testmodus

In den AdHoc Einstellungen gibt es den Haken “Testmodus”. Ist dieser aktiv, wird eine Bestellung wie bei einem echten AcHoc erstellt, diese aber dann nicht an die URL die eingetragen ist gesendet sondern an eine lokale Url: http://appsrv1.pol.local:6460/LCWebServices/LC.EdifactService/AdHocTestForm.aspx

Dort sieht man in einem Drop Down die Hersteller, für die der Test Modus funktioniert. Der Service antwortet dann je nach Hersteller mit dem entsprechenden Response.