Facilities EDI News

IN PRICAT

General

• Link to the interface document

• To-do in the projects:

  • Functionality for updating EANs with new credit item no.
    • Option: Manually via the system
    • Possibility: Provide "comfort function", which e.g. does print jobs for relabeling the goods etc.
  • Definition of update fields that should be updated by PRICAT

Example setup IN PRICAT: --> information can be copied to text file and adjusted accordingly, as test data can be generated

BTEPRI;PRICAT;ID_Empfänger;ID_Sender
PRICAT;;;;GLN_Lieferant;;GLN_Käufer;;;;;;;;EAN;LieferantenArtikelnummer;;Größe1;;Farbbezeichnung;;;;Lieferanten_Artikelbezeichnung;;;;Listenpreis_EK;Währung;empf.VK_Preis;Währung;;;;;;;;;Farbnummer;;;;;;;;;;;;;;;Saisonkennzeichen

Note: The general procedure for importing EDI messages is described in General Procedure IN Documents .

Necessary facilities

Master data

• GLNs müssen vorhanden sein und zu den entsprechenden Kreditoren zugeordnet sein

• The EDI partner code must be stored at the vendor (GLN vendor).

• Recipient ID must correspond to the "Own GLN" for the client, i.e. the GLN must exist and be assigned as "Own GLN"

EDI Partner

• Maintenance of the furnishings/properties at the EDI partner

Field	Description
No mandatory field check IN PRICAT	Do not check whether mandatory fields are filled
IN PRICAT Lief.-Color equals int. color code	- The color codes of the supplier are adopted when the PRICAT is processed and, if necessary, created in the system. - If the checkmark is set, then the color code from the PRICAT will be created in the color table and in the "assigned color table".

IN ORDRSP

• Link to the interface document with a description of the functionality

• "IN ORDRSP" processing was realized for a chain store with direct delivery to the stores

• To-do in the projects if required:

  • Adaptation to processing with central warehouse would have to be done with slight adjustment when creating purchase orders

Example setup IN ORDRSP: --> information can be copied to text file and adjusted accordingly, as test data can be generated

BTERSP;ORDRSP;ID_EMPFÄNGER;ID_ABSENDER
ORDRSP;;;DATUM_DER_BESTELLBESTÄTIGUNG;AUFTRAGSNR_LIEFERANT;;AUFTRAGSNUMMER_KÄUFER;LIEFERDATUM_VON;;;GLN_LIEFERANT;;;;WÄHRUNG;;;;;;EAN;;;;;;;BESTELLMENGE;;;;;NETTOPREIS;;;GLN_FILIALE_WARENENDEMPFÄNGER;;

Note: The general procedure for importing EDI messages is described in General Procedure IN Documents .  

Necessary facilities

Master data

• GLNs must exist and be associated with the appropriate vendors

• The EDI partner code must be stored at the vendor (GLN vendor).

• Empfänger ID muss der „Eigenen GLN“ für den Mandanten entsprechen, d.h. die GLN muss existieren und als „Eigene GLN“ zugeordnet sein

• The "GLN Final Recipient (Store)" must exist in the system and be assigned to a storage location

EDI Partner

• Pflege der Einrichtung/Eigenschaften am EDI Partner

Field	Description
IN ORDRSP Create automat. EK – Order	If the box is checked, an purchase order is automatically generated from the ORDRSP if one does not yet exist.
Use purchase price from IN ORDRSP	Adopts the purchase prices of the IN ORDRSP when creating/updating the purchase order.
Use retail price from IN ORDRSP	When creating/updating the purchase order, adopts the retail prices of the IN ORDRSP.

IN DESADV

• Link to the interface document

• "IN DESADV" processing was carried out for a chain store with direct delivery to the stores

• To-do in the projects if required:

  • Processing of VERPAC data records (import has been implemented, but the information is not processed  there is no use case for this so far)
  • Adaptation to processing with central warehouse would have to be done with minor adjustments when creating purchase orders/WE's (identification of the storage location code)
  • Processing has been realized exclusively in the event that the message is sent from the wholesaler to the retailer

Example setup IN DESADV: --> information can be copied to text file and adjusted accordingly, as test data can be generated

BTEDES;DESADV;ID_EMPFÄNGER;ID_ABSENDER
VERPAC;;;;;;;;;;;;NVE_VON;NVE_BIS (optional)
DESADV;;AUFTRAGSNR_LIEFERANT;LIEFERSCHEINNR;LIEFERSCHEINDATUM;;AUFTRAGSNUMMER_KÄUFER;;;;GLN_LIEFERANT;GLN_WARENEMPFÄNGER;EAN;;;;;;LIEFERMENGE;;;;;;;;;

Note: The general procedure for importing EDI messages is described in General Procedure IN Documents .

Necessary facilities

Master data

• GLNs must exist and be associated with the appropriate vendors

• The EDI partner code must be stored at the vendor (GLN vendor).

• Recipient ID must correspond to the "Own GLN" for the client, i.e. the GLN must exist and be assigned as "Own GLN"

• The "GLN Goods Consignee" must exist in the system and be assigned to a storage location

EDI Partner

• Maintenance of the furnishings/properties at the EDI partner

Field	Description
Filling was running. Quantity in WE from IN DESADV	If the "quantity act. Delivery" with the quantity that is delivered at item level in the IN DESADV.
Create automat. PURCHASE order from IN DESADV	If no purchase order is found, creates an purchase order from the IN DESADV.
Book automatically. Goods receipts from IN DESADV	Posts the goods receipt that has been created from the IN DESADV.

IN INVOIC

• Link to the interface document with a description of the functionality

• To-do in the projects if required:

  • Processing has been realized exclusively in the event that the message is sent from the wholesaler to the retailer

Example setup IN INVOIC: --> information can be copied to text file and adjusted accordingly, as test data can be generated

BTEINV;INVOIC;ID_EMPFÄNGER;ID_ABSENDER
INVKOP;DOKUMENTENART;RECHNUNGSNUMMER;DATUM_DER_RECHNUNG;;;;;;;GLN_LIEFERANT;;GLN_WARENEMPFÄNGER;;;;;;WÄHRUNG;;;;;;;;;;;;;;;;;;;;;;;;;;;;
INVKO2;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OUT_SLSRPT_REFERENZ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
INVPOS;1;;EAN;;;;;;;;;BERECHNETE_MENGE;;;;;;;NETTOPREIS;;;;LIEFERSCHEINNR;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
INVSUM;;;;;ZAHLBAHRER_BETRAG;;;;;;;;;;;;

Note: The general procedure for importing EDI messages is described in General Procedure IN Documents .

Necessary facilities

Master data

• GLNs must exist and be associated with the appropriate vendors

• The EDI partner code must be stored at the vendor (GLN vendor).

• Recipient ID must correspond to the "Own GLN" for the client, i.e. the GLN must exist and be assigned as "Own GLN"

• The "GLN Goods Consignee" must exist in the system and be assigned to a storage location

EDI Partner

• Maintenance of the furnishings/properties at the EDI partner

Field	Description
Use purchase prices from IN INVOIC	Use the purchase prices sent in the IN INVOIC.
Book automatically. Purchase invoice/purchase credit note from IN INVOIC	If processed successfully, posts the purchase invoice/purchase credit note, which has been created from the IN INVOIC.
IN INVOIC Document Type Invoice	Document type of INVOIC for the creation of an invoice. Is matched with the "INVOIC Document Type" field of the IN INVOIC.
IN INVOIC Document Type Credit Note	Document type of INVOIC for the creation of a credit note. Is matched with the "INVOIC Document Type" field of the IN INVOIC.
# IN ORDERS
## General

• Link to the interface document with a description of the functionality

• To-do in the projects if required:

  • Totals line (ENDORD) can still be implemented if required

Example setup IN ORDERS: --> information can be copied to text file and adjusted accordingly, as test data can be generated --> (... Consignee) is used if "GLN Consignee" is empty

BTEEDI;ORDERS;D;93A;EmpfängerID;;
KOPORD;Auftragsart;Bestellnummer;;;Bestelldatum;LieferdatumVon;;;;GLNKäufer;GLNRechungsempfänger;GLNWarenempfänger;;;WährungCodiert;;;;;;;;(NameWarenempfänger);(StraßeWarenempfänger);(OrtWarenempfänger);(PLZWarenempfänger);
POSORD;;;EAN;;;;;;;Bestellmenge;PCE;Nettopreis;;;;;;;;

Note: The general procedure for importing EDI messages is described in General Procedure IN Documents .

Necessary facilities

Master data

• GLNs must exist and be assigned to the corresponding customers (sales to/invoice to) and shipping addresses (delivery to)

• The EDI partner code must be stored on the "Sale to Customer" (GLN buyer)

image.png  

EDI Partner and EDI Partner "Order Types (IN ORDERS)"

• Setup of the order type via "Order types "IN ORDERS"

• The order type is determined as soon as the IN ORDERS documents are read into the system or when "Check Document" is clicked in the IN ORDERS document.

• Optional facilities see master data EDI partner link

EDI Setup

• Define the "Cancellation reason for unavailable quantities": The cancellation reason is stored in a sales line if order quantities are not available after checking availability (check "Check availability IN ORDERS" in EDI partner) and these are entered as cancellation.

image.png  

IN SLSRPT

General

• Link to the interface document with a description of the functionality

Example setup IN SLSRPT:

BTEEDI;SLSRPT;D;96A;ID_EMPFÄNGER;ID_ABSENDER
KOPSLS;NUMMER_DES_VERKAUFSBERICHTES;DOKUMENTENDATUM;;ENDE_VERKAUFSPERIODE;GLN_NACHRICHTENSENDER/VERKÄUFER;GLN_NACHRICHTENEMPFÄNGER/LIEFERANT;WÄHRUNG;
ORTSLS;GLN_VERKAUFSORT;;ENDE_VERAKUFSPERIODE;POSITIONSNUMMER;GTIN;;;;;;VERKAUFSMENGE;MASSEINHEIT;ERZIELTER_VK-Preis;;;;;

Note: The general procedure for importing EDI messages is described in General Procedure IN Documents .

Necessary facilities

Master data

• GLNs must exist and be assigned to the corresponding customers (sales to/invoice to) and shipping addresses (delivery to)

• The EDI partner code must be stored for the "Sale to Customer" (GLN buyer).

EDI Partner

• Maintenance of necessary facilities/properties for processing the IN SLSRPT messages at the "EDI Partner"

Field	Description
SLSRPT Processing Type	Selection of: statistics only (only statistics items are written) Delivery (a sales order/sales complaint is created and posted to "to be delivered") Delivery and invoice (a sales order/sales complaint is created and posted to "to be delivered" and then the delivery is invoiced) Article posting only (sales/customer returns are processed via article book sheet posting)
Create invoice per sale to Debtor	Per IN SLSRPT several "Verk. to debtors". When activated, the "Verk. to customer".
SLSRPT Invoice Posting Date
Realized retail price incl. VAT
Realized retail price incl. VAT
Always create sales return for customer returns	Creates a sales complaint for a customer return.
Pricing on the sales report	Selection of Customer Price Group (Sales Price Determination) or Costing
Price calculation on the sales report	If you select the option parameter "Costing" for "Pricing on Sales Report", this value is used to calculate the sales price.
# IN INVRPT
## General

• Link to the interface document with a description of the functionality

Example setup IN INVRPT:

BTEEDI;INVRPT;D;96A;EMPFÄNGER_ID;ABSENDER_ID
KOPINR;Nummer_des_Lagerbestandsberichts;DOKUMENTENDATUM;DATUM_DES_BESTANDSBERICHTES;;;GLN_VERKÄUFER;GLN_LIEFERANT;GLN_BERICHTERSTATTER;;GLN_LAGERNUMMER;DOKUMENTENART;GLN_VERSENDER_FILIALE;GLN_EMPFÄNGER_FILIALE;UMLAGERDATUM;;
POSINR;EAN;;;;;;LAGERBESTAND;BESTANDSENTNAHMEMENGE;;;;BESTANDSBEWEGUNGSMENGE;;BESTANDSKORREKTURMENGE;;;KUNDENRETOURE;RETOURE_ZENTRALLAGER;;;

Note: The general procedure for importing EDI messages is described in General Procedure IN Documents .

Necessary facilities

Master data

• GLNs must exist and be assigned to the corresponding customers (sales to/invoice to) and shipping addresses (delivery to)

• The EDI partner code must be stored for the "Sale to Customer" (GLN buyer).

"IN INVRPT Document Types"

• Setup of associated "IN INVRPT document types" at the EDI partner
• Specification per document type of what is to be carried out

• "Process Inventory Notification":
  • Creation of inventory order
  • Possible facilities at the EDI partner:
    • "Book INVRPT inventories immediately"
    • "Allow rows without inventory notification"
    • "Multiple INVRPT messages allowed"
• „Umlagerung verarbeiten“
  • Posting stock transfers without transit warehouses
• "Process transit transfer"
  • Post Stock Transfers without Dispensing/Receiving Branch
  • Possible facilities at the EDI partner:
    • "Transit warehouse location branch relocation"
    • "Transit storage location central warehouse"
• „Bestandskorrektur verarbeiten“
  • Posting inventory adjustments
  • Possible facilities at the EDI partner:
    • "Process INVRPT inventory adjustment as a sale"
• "Process returns"
  • Posting returns to the supplier
  • Possible facilities at the EDI partner:
    • „INVRPT Retouren (an Lieferant) sofort buchen
• "Process Inventory Withdrawals"
  • Abverkäufe und Kundenretouren verarbeiten
  • Possible facilities at the EDI partner:
    • "Create sales complaint for neg. Inventory withdrawals"

OUT ORDERS

General

• Link zum Schnittstellendokument

Necessary facilities

• Assignment of an "EDI Partner Code" to the vendor
• Check the "Create OUT Order" box on the "EDI Partner Code":

• Define assigned order types for which OUT ORDERS must also be generated
• Define whether OUT ORDERS should be created when the purchase order is released or manually

image.png  

Steps to create OUT ORDERS

• Entry of an purchase order
• When validating
  • "Eink. From vendor no."
  • "Order type (variable)"

• When the purchase order is released, it is checked whether an OUT ORDER can be generated if necessary facilities are available
• The "Export Containers" has the following values after creation
  • "Status" = "Status"::"Create"
  • "EDI document type" = "OUT ORDERS"
  • "Type of origin" = 38
  • "Subspecies of origin" = 1
  • "Origin No." = Document No. purchase order

The further processing of the export containers is the same for all OUT documents and is summarized under General Procedure OUT Documents .

OUT SLSRPT

General

• Link to the interface document

Necessary facilities

• Assignment of an "EDI Partner Code" to the vendor

• Check the box for "Create OUT SLSRPT" on the "EDI Partner Code" and define an "Assigned Export Planning OUT SLSRPT":

Field	Description
Build OUT SLSRPT	When posting article journal lines, when the value entry is created, it is checked whether OUT SLSRPT is to be created for the main supplier of the article. If so, then an "EDI Export Item" is written (see EDI Export Item).
Assigned Export Planning OUT SLSRPT	Defines which export planning template is used to create the OUT SLSRPTs (see Export Planning).

Steps to create OUT SLSRPTs

• Bei Verbuchung der Artikelbuchblattzeile wird, falls notwendigen Einrichtungen vorhanden sind, ein „EDI Export Posten“ mit der „EDI Export Postenart“ = „EDI Export Postenart“::“OUT SLSRPT“ erstellt
• Alternatively, you can create "EDI Export Item" with "EDI Export Item Type" = "EDI Export Item Type"::"OUT SLSRPT" on the vendor card via button (actions  "Initialize OUT SLSRPT item") if the facilities are available.

• The NAS CU 5407706 – Export Schedule Mgt. runs at periodic intervals and creates "EDI Export" documents for the assigned "EDI Partner" documents

• "Export Container Items" are created from the "EDI Export" documents

image.png - The "Export Containers" has the following values after creation - „Status“ = „Status“::“Erstellen“ - "EDI document type" = "OUT SLSRPT" - "Type of origin" = 5407711 - "Subspecies of origin" = 1 - "Origin No." = Document No. of the "EDI Export" document

OUT INVRPT

General

• Link to the interface document

Necessary facilities

• Assignment of an "EDI Partner Code" to the vendor

 

• On the "EDI Partner Code", tick the box for "Create OUT INVRPT Stock Transport" or "Create OUT INVRPT Stock" and define an "Assigned Export Planning OUT INVRPT":

Field	Description
Create OUT INVRPT Stock Transfer	When posting item journal lines, when the value entry is created, it is checked whether OUT INVRPT for stock transfers is to be created for the main supplier of the item. If yes, then an "EDI Export Item" is written (see EDI Export Item).
Create OUT INVRPT stock	When posting item journal lines, when the value entry is created, it is checked whether OUT INVRPT for stock transfers is to be created for the main supplier of the item. If yes, then an "EDI Export Item" is written (see EDI Export Item).
Assigned Export Planning OUT INVRPT	Defines which export planning template is used to create the OUT SLSRPTs (see Export Planning).
OUT INVRPT Document Type Transfer	The value that should be in the Document Type field in the OUT INVRPT.
OUT INVRPT Document Type Physical Inventory	The value that should be in the Document Type field in the OUT INVRPT when posting from Physical Inventory Order or Physical Inventory Book Sheet.
OUT INFROZEN Dokumentenart Bearing File Message	The value that should be in the Document Type field in the OUT INVRPT when creating a periodic inventory report.
Creation of OUT INVRPT transfer from transit warehouses	If when posting transfer orders via transit warehouses, an OUT INVRPT for the receipt posting on the transit warehouse and an OUT INVRPT for the departure posting from the transit warehouse should be reported. Prerequisite: Use of the transfer order The transit warehouse must have its own GLN If there is no GLN of its own, do not check the box and an OUT INVRPT is only reported for the departure posting from the origin warehouse ("transfer by code") and receiving warehouses ("transfer by code").

Steps to create OUT INVRPTs

• When posting the article journal line, if the necessary setups have been made, an "EDI Export Item" is created with the "EDI Export Item Type" = "EDI Export Item Type"::"OUT INVRPT"
• The NAS CU 5407706 – Export Schedule Mgt. runs at periodic intervals and creates "EDI Export" documents for the assigned "EDI Partner" documents
• "Export Container Items" are created from the "EDI Export" documents

The further processing of the export containers is the same for all OUT documents and is summarized under General Procedure OUT Documents .  

OUT PRICAT

General

• Link to the interface document

Necessary facilities

• Assignment of an "EDI Partner Code" to the "Verk. To Customer of a Sales Quote or Sales Order

image.png - In the EDI Partner, check the box "Set up OUT PRICAT"

Field	Description
Errichte OUT PRICAT	General criterion whether a PRICAT should be created for this EDI partner.
Additional Partner ID. of the buyer	An additional identification number for the EDI partner can be entered. This value is displayed in the lines of the OUT PRICAT under "Additional Partnerid. of the buyer".
Use Season Conversion	Uses the EDI partner's season recoding to determine the correct season. If transcoding is not enabled, the item season is used.
Use article hierarchy decoding	Uses the item hierarchy decoding (commodity group) of the EDI partner to determine the correct commodity group of the customer. If the conversion is not activated, the customer's product group is not used.
Use product group recoding	Uses the EDI partner's product group conversion to determine the correct product group. If conversion is not enabled, the product group is not used.
Rec. Retail price mandatory	If this field is activated, the field "empf. VK – Price" in the sales offer lines.

• At the EDI Partner, via "Order Types Setup": Setting the time when an OUT PRICAT is to be created. NOTE: a PRICAT can always be created manually via a sales quote. This does not have to be set up here.

image.png  

Optional facilities

• At the EDI Partner, the checkmarks for product group, season, or article hierarchy encryption can be set.

• The EDI partner can be used to store whether a "rec. retail price" must be indicated. Control by checking the box "empf. retail price mandatory".
• Furthermore, an "additional partner ID. of the buyer" as an identifier.

Steps to create an OUT PRICAT

• An OUT PRCAT can be created manually or automatically from several places in the system.
• Manual creation is done via a sales quote.
• In order to be able to create a complete price catalogue for certain article categories/seasons/etc., the function "build PRICAT catalogue" can be used.
  • The "PRICAT Catalogue" box is ticked on the retail offer. It has no controlling property, but only serves as information for the user. It can also be set manually, e.g. if rows are manually created for a PRICAT.
  • It can also be determined whether the PRICAT should be built and exported directly afterwards (only if the test is error-free)

• To create quote lines for a PRICAT based on previous sales or stock transfers, you can use the "Suggestion item for PRICAT" function
  • Depending on a posting period, all item variants for the "Sales to Customer" specified in the sales quotation are searched for in the value ledger entries
  • All variants are then created with the quantity 1 in the sales line. The prices are determined with the help of standard pricing.

• The "Create OUT PRICAT" function can be used to create the OUT PRICAT from a retail offer.

• With the help of the "OUT PRICAT" action under NAVIGATE, the export container with all associated OUT PRICAT entries is displayed (cancelled as well).

• Depending on the setup in the EDI Partner under "Order Types", an OUT PRICAT is automatically created after a sales order has been released or the goods issue has been posted.

• The automatic and/or manual creation from a sales delivery or the sales archive is already provided for in the EDI export routine in the source code, but must still be triggered at the appropriate points in the system, if desired.

• The "EDI Export Container" has the following values after creation

  • "Status" = "Status"::"Create"
  • "EDI document type" = "OUT PRICAT"
  • "Type of origin" = 36
  • "Subspecies of Origin" = 0 (Offer) , 1 (Order)
  • "Origin No." = Document No. of the offer/order

The further processing of the export containers is the same for all OUT documents and is summarized under General Procedure OUT Documents .

OUT ORDRSP

General

• Link zum Schnittstellendokument

Necessary facilities

• Assignment of an "EDI Partner Code" to the customer

image.png   - Check the box "Create OUT ORDRSP" on the EDI partner

Field	Description
Build OUT ORDRSP	General criterion whether an ORDRSP should be created for this EDI partner.

• Assignment of the order types for the creation of the OUT ORDRSP and at what point in time they are to be created

Steps to create OUT ORDRSPs

• Entry of a sales order and validation of the "Verk. to debtor no."
• The "EDI Partner" belonging to the customer must have set the "create OUT ORDRSP" indicator
• In addition, the order type of the sales order must be maintained in the "Order types setup" at the EDI partner, and the time at which the OUT ORDRSP is to be created must be defined under "Create OUT ORDRSP"
• Depending on the setup, the sales order must now be released or the goods issue must be created and released so that the process for creating the OUT ORDRSP is started

• "EDI Export Items" are created from the released sales order or WA document

• The "Export Containers" has the following values after creation

  • "Status" = "Status"::"Create"
  • "EDI document type" = "OUT ORDRSP"
  • "Type of origin" = 36 (UK order)
  • "Subspecies of origin" = 1 (Vk order)
  • "Origin No." = Document No. of the "UK order"

The further processing of the export containers is the same for all OUT documents and is summarized under General Procedure OUT Documents .

OUT DESADV

General

• Link to the interface document

Necessary facilities

• Assignment of an "EDI Partner Code" to the customer

image.png   - Check the box "Create OUT DESADV" on the EDI partner and define how parcel data is to be sent (only when creating the OUT DESADV from the outgoing goods issue)

Field	Description
Build OUT DESADV	General criterion for creating a DESADV for this EDI partner.
Send parcel data	Selection of: -no package: No package information will be shipped. -Simple: The package information is summarized in one line. No assignment of items to packages. -Detailed: The packages are broken down in detail. The items are allocated per package.

• Maintenance in EDI setup when OUT DESADV is to be created (for sales delivery or goods issue)

Steps to create OUT DESADVs

• Entry of a sales order and validation of the "Verk. to debtor no."
• Release "Sales Order"  Create WA  Release WA  Post WA
• The "EDI Partner" belonging to the customer must have set the indicator "create OUT DESADV"

• "EDI Export Items" are created from the released VA document

• The "Export Containers" has the following values after creation

  • "Status" = "Status"::"Create"
  • "EDI document type" = "OUT DESADV"
  • "Type of origin" = 7322 (born goods issue header)
  • "Subspecies of origin" = 0
  • "Origin No." = Document No. of the goods issue document

OUT INVOIC

General

• Link zum Schnittstellendokument

Necessary facilities

• Assignment of an "EDI Parter Code" to the "Verk. To debtor"

image.png   - In the EDI Partner, check the box "Set up OUT INVOIC for invoice" and/or "Set up OUT INVOIC for credit note"

Field	Description
Create OUT INVOIC for invoice	General criterion for whether an INVOIC should be created for this EDI partner from sales invoices.
Create OUT INVOIC for credit	General criterion whether an INVOIC should be created for this EDI partner from sales credit notes.

Optional facilities

• In the EDI Partner, a different "EDI message recipient INVOIC" applies. This is used instead of the "EDI message recipient" for the creation of an INVOIC.

Field	Description
EDI message recipient type INVOIC	Type of message recipient to whom the INVOIC is to be sent (customer/vendor). This can be different from the general EDI message recipient type.
EDI Message Recipient INVOIC	Number of the message recipient.

• If discounts are used, a "Discount surcharge/discount indicator" must be stored in the EDI setup.

• The table "EDI Surcharge/Discount Indicators" is used to define the surcharge/discount indicators.

• If resources are used, "EDI surcharge/discount indicators" must also be defined for the resources. These can be stored directly in the resource card under "EDI surcharge/discount indicator code".

Steps to create an OUT INVOIC

• An OUT INVOIC arises from a posted sales invoice or a posted sales credit memo.
• This can be done manually via the "Create OUT INVOIC" function directly on the card of the issued retail invoice or retail credit.

• The automatic creation of an INVOIC takes place when a sales invoice or sales credit note is posted
• The result is the creation of an "EDI Export Item". The "Export Container" has the following values after creation:
  • „Status“ = „Status“::“Erstellen“
  • "EDI document type" = "OUT INVOIC" "Type of origin"
  • 112: born VK-invoice
  • 114: born VK credit note
  • „Herkunftsunterart“ = 0
  • "Origin No." = Document No. of the born VK-Rechnung/geb.. VK Credit