Use the EDI Add'l Doc Info screen to define additional information required to process a document assigned to an EDI trading partner's group profile.
Note: If you are defining additional document information for inbound 845s, you can access the document information in Solar Eclipse from the 845 Contract Upload Queue.
To enter additional EDI document information:
Display a trading partner profile on the EDI Trading Partner Profile Maintenance screen.
Note: If prompted, log on to the character-based system.
Select a group ID and use the Group Profile Maintenance hot key to display the EDI Group Profile Maintenance screen.
Select a document number and use the Add'l Doc Info hot key to display the EDI Add'l Doc Info screen.
The document number you select determines the fields displayed in the EDI Add'l Doc Info screen.
Complete the fields on the EDI Add'l Doc Info screen, as needed.
Note: The fields available for each document are different depending on your document number selection. For example, the system displays different fields if you select an 855 than if you select an 845. See the Field Options on the EDI Add'l Doc Info Screen below for more information.
Press Esc to save the information and return to the EDI Group Profile Maintenance screen.
Field Options on the EDI Add'l Doc Info Screen
The following table describes all the possible fields on the EDI Add'l Doc Info screen:
Field |
Applies To |
Description |
Grp/User to Review Received Document |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Enable Auto-Approve on Invoicing |
Inbound 810 |
Enter Y to have the system reconcile and approve the EDI invoice for payment when the line items match and the dollar amount is within the over/short range. The default is N. |
Create 855/856 Documents From 810 |
Inbound 810 |
Enter Y to have the system generate an 855 P/O Acknowledgment or an 856 Advanced Ship Notice against the P/O. If you enter Y, then press F10 to select the documents. The default is N. This function applies to vendors that are unable to send either the 855 or 856 documents. |
Create Payables for Non-Eclipse PO#s |
Inbound 810 |
Enter Y to create a payable for non-Eclipse purchase order numbers, and to attach a message to the payable stating that it is a non-Eclipse purchase order number. The system checks the vendor's home branch and first authorized branch based on the User Accessible Branches window, if there is no valid G/L branch. When selecting Yes for this field, you can also select which type of document to check: 855, 856, or Both. The default is N. Note: Setting this option to Y can be useful when converting a legacy system to Eclipse. Note: Invoices for either option remain in the EDI 810 Review Queue for processing marked as "No Match." |
Reconcile Invoice Freight Charges |
Inbound 810 |
If you enter Y and the invoice amount differs from the purchase order amount by the freight amount, the system marks that invoice as a perfect match in the 810 Review Queue. The default is N. |
Process Invoices for Directs |
Inbound 810 |
Enter Y to have the system try to match the inbound 810 invoices to the purchase order of a direct order. If a match is found, the system receives that purchase order generation and reconciles the 810 invoices against that generation. The default is N. If the Direct Invoice option in the Order Status Print Status Defaults control maintenance record is blank or set to any status other than No Print, set the Enable Auto Approve on Invoicing field in this screen to Y. The default print status set for the ship via for the order and the setting in the Print Status On Direct When Payable Approved control maintenance record affect whether the print status for the order changes to P when the invoice is approved. If the Direct Invoice option in the Order Status Print Status Defaults control maintenance record is set to No Print, then the print status for the order will not change when the invoice is approved, regardless of how the ship via for the order or the Print Status On Direct When Payable Approved control record are set. Note: The system allows for zero dollar ($0.00)direct orders to process. |
Enable Terms Checking |
Inbound 810 |
Enter Y to have the system verify the terms defined in the 810 with the terms from the purchase order. If the terms do not match, the match code in the 810 Review Queue is T. The default is N. |
Freight Already Posted on Eclipse PO |
Inbound 810 |
Enter Y to indicate that freight is already posted on the Eclipse purchase orders. The customer posts the freight to the purchase order during the receiving process. Direct orders do not have freight included on the purchase order. Vendors may bill for freight and have this put in the freight bucket in AP Entry. The default is N. |
Alternate Interchange ID |
Inbound 850 |
Identify a test ID (or alternate production ID) for your trading partner. It follows the same format as the group number. Use this field instead of setting up a separate profile for the purpose of testing with your partner. Note: When entering EDI Trading Partner Maintenance and entering a Trading Partner ID number, the IDs listed include this Alternate Interchange ID. We recommend that you always choose the main profile and get to the Alternate Interchange ID through the main profile, not by selecting the alternate interchange at this point. |
Check All Unpaid Gens |
Inbound 810 |
If you leave this field blank or enter N, the system checks for matches only at the generation level. The default is N. Enter Y to have the system check for an exact match on one generation and then also check for an exact match by summing all of the received unpaid generations on that purchase order. |
If you enter Yes in this field and the EDI PO Variances For EDI 810 Invoices control maintenance record is also set to Yes, then orders with multiple generations with a variance are auto-matched to an 810 vendor invoice. |
||
If you enter Yes in this field and the Reconcile EDI 810 Open Generations With Partial Matches control maintenance record is set to Yes, then the system automatically reconciles any open generations with partial matches on the defined criteria when received through the EDI 810 invoice. |
||
Use PO Terms |
Inbound 810 |
Enter Y to use the terms, such as discount amount, discount date, and due date, from the purchase order rather than the 810. If you set this field to Y, the system ignores the setting in the Enable Terms Checking field and uses the terms from the purchase order regardless of what is sent in the 810. When set to Yes, the system does not consider the Discount Amount field as being overridden on the payable being created. Enter N to use the terms sent in the 810. If the Enable Terms Checking field is set to Y, the system verifies the terms in the 810 against those in the purchase order. If the terms do not match, the match code in the 810 Review Queue is T. If the terms in the 810 are incomplete, the system places the item in the 810 Review Queue without creating the payable. The default is N. |
Allow Match Invoice in Closed Period |
Inbound 810 |
Enter Y to allow the system to automatically match an 810 vendor invoice and a prior period receipt, regardless of other matched criteria, and the system creates a payable for the invoice. If you enter Y, the system displays the Allow Days After Close prompt. Enter the number of days after the closing date that invoices can still be matched. For example, you enter 30. The system uses this setting if the period close date was in the past 30 days. If this prompt is left blank, then this setting works regardless of when the period was closed. The Create PO Variance for EDI 810 Invoices control maintenance record must also be set to Yes for the payable to apply to the prior period receipt automatically. The system then creates a P/O variance record. |
Allow Match Lot Item Invoice |
Inbound 810 |
You must have the Allow Auto-Matching For Lot Order With EDI set to Yes for this field to display. |
Use Branch Lookup Table |
Inbound 810 |
Enter Y to use the Branch Lookup Table to match store numbers with Eclipse Branch IDs. For more information about this table, see Linking Store Numbers and Eclipse IDs for EDI. |
Use Match Job Management Invoice |
Inbound 810 |
This option works with the Payable Variance Resolution Queue (PVRQ) logic. If you have the the PVRQ enabled and this option is set to Yes, then purchase order created through the Job Management order is reconciled with a payable. |
Enable Auto Freight Debit Memo |
Inbound 810 |
Enter Y to allow the system to create debit memos automatically for this trading partner. For more information, see Automatic 810 Matching for Lot Orders in this documentation or Using Debit Memos in the Accounts Payable documentation. |
Field |
Applies To |
Description |
Initial Order Status |
Inbound 830 |
Enter the default order status. We recommend setting this field as follows:
|
Round Up To Minimum Sales Quantity |
Inbound 830 |
Indicate whether the system should round up the order quantity for a product when a minimum package quantity is defined but the customer didn't order that quantity.
If you leave this field blank, the system uses the setting in the Round Up to Minimum Sales Quantity field on the EDI Group Profile Global Info Table. |
Use Partner's Pricing on Orders |
Inbound 830 |
P/O Enter Y to use the pricing provided by the trading partner in the 850 inbound documents. The default is N. |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
Field |
Applies To |
Description |
Initial Order Status |
Inbound 830 |
Enter the default order status. We recommend setting this field as follows:
|
Default Writer |
Inbound 840 |
Select the user for the system to display in the Written by field in the header of the sales order or quote created by the transaction. |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
Note: Use the Product Matching hot key to define how you want the EDI 845 to determine matching priorities on the product data. This is new in Release 9.0.5.
Field |
Applies To |
Description |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
|
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Alternate Interchange ID |
Inbound 845 |
Identify a test ID (or alternate production ID) for your trading partner. It follows the same format as the group number. Use this field instead of setting up a separate profile for the purpose of testing with your partner. Note: When entering EDI Trading Partner Maintenance and entering a Trading Partner ID number, the IDs listed include this Alternate Interchange ID. We recommend that you always choose the main profile and get to the Alternate Interchange ID through the main profile, not by selecting the alternate interchange at this point. |
Cost/Price Matrix |
Inbound 845 |
Select from the following options for how you want to handle matrix creations based on the incoming document from your trading partner:
|
Default Selling Formula |
Inbound 845 |
Enter the pricing formula, if the vendor always uses the same formula for determining your selling price for 845 pricing contracts. The system populates the Formula column in the Sell Price view on the 845 Contract Detail with this formula. You can override the formula for individual customers in the Formula field on the Contract Upload Settings screen in Customer Maintenance or for individual 845s in the Formula column of the Sell Price view of the 845 Contract Detail. |
Update COMM-COST on Sell Matrix |
Inbound 845 |
Indicate whether the system should upload and update the COMM-cost in addition to the COGS cost. If set to Yes, the system applies the formula and basis for the rebate cost of goods sold (COGS) to the rebate COMM cost, and from the direct COGS to the direct COMM cost. |
Invert Multiplier |
Inbound 845 |
Specify whether the vendor sends straight multipliers or an inverse multiplier in their inbound 845 documents. The multiplier is a number that the vendor sends in the 845 that is used in the pricing matrix formula to calculate the rebated cost that is applied to a product when it is sold. The vendor can send the multiplier in one of two formats:
|
Inbound 845 |
Enter Y to let the system create renewals automatically for special pricing agreements (SPA). The system conducts the same checks as if you were processing it manually through the 845 Contract Upload Queue. |
|
Default Global SPA COGS Basis |
Inbound 845 |
Enter the cost-of-good-sold (COGS) basis you want the system to use when automatically processing SPA agreements. |
Default Global SPA Direct COGS Basis |
Inbound 845 |
Enter the direct cost-of-good-sold (COGS) basis you want the system to use when automatically processing SPA agreements. |
Inbound 845 |
Use the Sell Groups hot key to display the Sell Group Translation screen, where you list the vendor's product groups and map them to Eclipse sell groups.
|
|
Enable Product Matching Priority New in Release 9.0.5 |
Inbound 845 |
Indicate if you want to match your products when receiving EDI 845 documents by other parameters than by UPC or EAN codes. You can decide which options on which to match and in what order giving you more control over your product matching priorities. Set this option to Yes to activate the Product Matching hot key. For more information about this option, see Defining Product Matching Priorities for EDI. By leaving this set to No, the system works as designed prior to Release 9.0.5 using the UPC and EAN codes on 845 documents. Note: Matching options are automatically available for the following EDI documents: 810, 855, 856, and 845. |
Ignore Purpose Code for Auto Creation |
Inbound 845 |
In conjunction with the Auto Create 845 Renewal SPA option above, you can set this option to Yes to only bypass the EDI 845 Contract Review Queue and automatically update the sell matrix records. This requires the second field value in the Beginning Segment for Price Authorization Acknowledgement/Status (BPA) be set to 04. The default is No. |
If this option is set to Yes, the system addresses the following:
|
Field |
Applies To |
Description |
Round Up To Minimum Sales Quantity |
Inbound 830 |
Indicate whether the system should round up the order quantity for a product when a minimum package quantity is defined but the customer didn't order that quantity.
If you leave this field blank, the system uses the setting in the Round Up to Minimum Sales Quantity field on the EDI Group Profile Global Info Table. |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
Field |
Applies To |
Description |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
|
Alternate Interchange ID |
Inbound 849 |
Identify a test ID (or alternate production ID) for your trading partner. It follows the same format as the group number. Use this field instead of setting up a separate profile for the purpose of testing with your partner. Note: When entering EDI Trading Partner Maintenance and entering a Trading Partner ID number, the IDs listed include this Alternate Interchange ID. We recommend that you always choose the main profile and get to the Alternate Interchange ID through the main profile, not by selecting the alternate interchange at this point. |
Disable Payable Creation |
Inbound 849 |
Select at the Trading Partner level to disable the system from creating payables during 849 transaction processing. By disabling the payable creation, all payables are sent to the P/O Variance Queue for review. You can use the EDI Trading Partner Mass 810 Options Settings to load this setting, if needed. |
Field |
Applies To |
Description |
Initial Order Status |
Inbound 830 |
Enter the default order status. We recommend setting this field as follows:
|
Grp/User to Review Received Document |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Use Partner's Pricing on Orders |
Inbound 830 |
P/O Enter Y to use the pricing provided by the trading partner in the 850 inbound documents. The default is N. Note: When set to Yes, partner prices display on all generations of the created order regardless how the transaction is processed: manually or through the phantom processor. |
Alternate Interchange ID |
Inbound 850 |
Identify a test ID (or alternate production ID) for your trading partner. It follows the same format as the group number. Use this field instead of setting up a separate profile for the purpose of testing with your partner. Note: When entering EDI Trading Partner Maintenance and entering a Trading Partner ID number, the IDs listed include this Alternate Interchange ID. We recommend that you always choose the main profile and get to the Alternate Interchange ID through the main profile, not by selecting the alternate interchange at this point. |
EDI Order Entry Discount% |
Inbound 850 |
Enter the percentage discount the system gives to customers who send in orders using EDI. If you leave this field blank, the system does not give a discount. To set up EDI discounts, create a G/L account for EDI discounts and assign this account to the EDI Discount Given autoposting item. |
Round Up To Minimum Sales Quantity |
Inbound 850 |
Indicate whether the system should round up the order quantity for a product when a minimum package quantity is defined but the customer didn't order that quantity.
If you leave this field blank, the system uses the setting in the Round Up to Minimum Sales Quantity field on the EDI Group Profile Global Info Table. |
Remove 'Price Per' Comment Line from Order |
Inbound 850 |
If you enter Y, the price per line item comment that includes pricing information is not included in the printed order. For example, you direct ship to a customer's customer. The shipping ticket that you pack with the order includes the printable line item comments from the order. Using this setting, you can remove the line item comment that contains pricing information so the direct ship customer does not see the prices that your customer is pays for the items on the order. |
Field |
Applies To |
Description |
855 Function Type |
Inbound 855 |
Identify the function the 855 serves:
Note: If the trading partner sends both 855 types, select P/O Ack for this field. The system uses data element 02 from the BAK segment to identify VMI orders. If this code is AP, the system treats this order as though the vendor is trying to create an order for the distributor. The system treats anything other than AP as a P/O Acknowledgment. |
Dflt Lead Time if NO Shp Dt Provided |
Inbound 855 |
Enter the number of days it takes the vendor to send material from their warehouse. The system adds this number to the date of the 855 and uses this calculated date as the expected receive date. The default is a blank field. This field applies to vendors that do not send a ship date in the 855 documents. |
Override Perfect Match Auto-Clearing |
Inbound 855 |
Enter Y to keep inbound purchase orders that have a perfect match in the EDI 855 P/O Acknowledgement Review Queue's Active view until you move them to the Cleared view. If this field is set to N, the system automatically clears any purchase orders with a match level of P from the Active view in the queue and moves them to the Cleared view. |
Process Multiple Stock PO Ack 855s |
Inbound 855 |
Enter Y to enable the system to process multiple 855s per order. The default is N. |
Received Document Notification |
Inbound 855 |
Select who to notify when the system receives an EDI 855. If you leave this field blank, the system does not message a user when it receives an 855.
|
Received Document Reviewer |
Inbound 855 |
Select who to assign in the EDI 855 Review Queue to review the record created for the incoming document. If you leave this field blank, the system does not assign a user.
|
Update Req'd Date with the Ship Date |
Inbound 855 |
Enter Y or N to override the system default defined in the Update The Required Date With The Ship Date Received On An EDI 855 control maintenance record.
|
Use Partner's Pricing on VMI Orders |
Inbound 855 VMI |
Enter Y to use the pricing provided by the trading partner in the 855 inbound documents when creating VMI orders. The default is N, in which case the system creates the order using matrix or price sheet pricing. |
Initial Order Status |
Inbound 830 |
Enter the default order status. We recommend setting this field as follows:
|
Use Receive Code Table on VMI Orders |
Inbound 855 VMI |
Set to Y (Yes) to have Eclipse use the code table for VMI orders. The default is No. When an Inbound 855 VMI order is received from a vendor, the system automatically attempts to create an Eclipse purchase order from the data. By default, the Ship-From is the first vendor account number attached to the EDI Trading Partner Profile. To specify which vendor to user for the purchase orders, set this option to Yes and complete the EDI Group Profile Receive Code Info Table accordingly. |
Send Duplicate VMI 855 to the EDI 855 Review Queue |
Inbound 855 VMI |
Set to Y (Yes) to send duplicate VMI 855 documents to the EDI 855 Review Queue, instead of the EDI Error Queue. The documents have a message indicating that the purchase order already exists in the system. From the EDI 855 Review Queue, users can select the Vendor Item Detail screen for the purchase order and a message displays indicating the 855 was from a duplicate VMI order: VMI 855 FROM VENDOR. PO NUMBER ALREADY EXISTS. REVIEW FOR CHANGES. The default is No. |
Use Next Available PO# for VMI Orders |
Inbound 855 VMI |
New in Release 9.0.1 Set to Y (Yes) to uses the next available purchase order number generated by Eclipse when creating purchase orders for VMI transactions. The VMI transaction program then uses the next available purchase order number and populates the Order ID field on the purchase order Header tab with the vendor's Order ID sent in the 855 document. |
Field |
Applies To |
Description |
Auto-Clear Review Queue Entry |
Inbound 856 |
Set the following options, as needed, to tell the system when to clear the EDI Review Queue of these transactions:
|
Enable Processing for Directs |
Inbound 856 |
Indicate if you want to process direct orders using the 856 inbound document process. You can use this option even if the Enable 856 Processing For Directs control maintenance record is not set to Yes. |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Grp/User to Review Received Document |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
Alternate Interchange ID |
Inbound 856 |
Identify a test ID (or alternate production ID) for your trading partner. It follows the same format as the group number. Use this field instead of setting up a separate profile for the purpose of testing with your partner. Note: When entering EDI Trading Partner Maintenance and entering a Trading Partner ID number, the IDs listed include this Alternate Interchange ID. We recommend that you always choose the main profile and get to the Alternate Interchange ID through the main profile, not by selecting the alternate interchange at this point. |
Field |
Applies To |
Description |
Initial Tracker Status |
Inbound 860 |
Enter the default status the system assigns to the trackers it creates for incoming 860s. |
Received Document Review Hierarchy |
Inbound 860 |
Options let users specify who is responsible for processing the 860 document. You can select Writer, Inside Sales, and Outside Sales in any combination. Eclipse then parses out the Customer purchase order and finds a single sales order with the received customer P/O #. Eclipse uses the hierarchy set in this field to send to users. If no user is set to receive the document, Eclipse sends to the standard User/Msg Group defined in the EDI 860 Add'l Doc Info screen. |
Field |
Applies To |
Description |
Round Up To Minimum Sales Quantity |
Inbound 830 |
Indicate whether the system should round up the order quantity for a product when a minimum package quantity is defined but the customer didn't order that quantity.
If you leave this field blank, the system uses the setting in the Round Up to Minimum Sales Quantity field on the EDI Group Profile Global Info Table. |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
Multiple Inbound Transaction Fields
Field |
Applies To |
Description |
Initial Order Status |
Inbound 830 |
Enter the default order status. We recommend setting this field as follows:
|
Round Up To Minimum Sales Quantity |
Inbound 830 |
Indicate whether the system should round up the order quantity for a product when a minimum package quantity is defined but the customer didn't order that quantity.
If you leave this field blank, the system uses the setting in the Round Up to Minimum Sales Quantity field on the EDI Group Profile Global Info Table. |
Use Partner's Pricing on Orders |
Inbound 830 |
P/O Enter Y to use the pricing provided by the trading partner in the 850 inbound documents. The default is N. |
Default Writer |
Inbound 840 |
Select the user for the system to display in the Written by field in the header of the sales order or quote created by the transaction. |
Grp/User to be Notified of Document |
Inbound docs (except 855) |
Enter the ID of the person or message group to notify when an EDI transaction is received. |
Inbound docs (except 855) |
Enter the ID of the user or message group handling the account. To assign maintenance users by branch for an 845, use the Multi Users hot key to display the Maintenance Users screen. Each user or message group entered can only access contracts for vendors with a home branch in their branch list. |
Field |
Applies To |
Description |
Grp/User to be Notified of 997 |
852 and 855 Outbound 850 and 810 |
Enter the User ID or Group ID who should be notified when an 997 transmission is received. |
Default Outgoing Transmission Status |
852 and 855 Outbound 850 and 810 |
Enter the default status to use for outgoing transmissions, such as SEND or HOLD. |
Alternate Interchange ID |
852 and 855 Outbound 850 and 810 |
Enter the interchange ID to use if the ID is different than the Primary ID listed in the current profile. The same format must be used: XX~ISAID~GSID |
Transmission Method Override |
Outbound 810 Outbound 852 |
Enter an alternate transmission method to override the default transmission method set for the trading partner in EDI Trading Partner Profile Maintenance. For example, if you send invoices through a third party billing company, that company may have a different EDI transmission default than the customer to which the EDI trading partner profile is assigned. Use this field to specify an alternate transmission method for the outbound invoice. |
Send Credit/ Zero Bal Invoices |
Outbound 810 |
Select one of the following options to indicate whether the system sends 810s for invoices with negative balances (credits) or zero balances. The default is Y.
Note: If you select an option that prints zero balance invoices, the Print Paid-In-Full Invoices control maintenance record must be set to Y. These invoices are not necessarily paid in full. The invoice might be for replacement items or there is no charge for some other reason, but the customer still needs to receive the invoice. |
Send Pricing Data in Qty UOM (Y/N) |
Outbound 810 Outbound 850 |
Enter Y to convert the pricing information to the same unit of measure as the quantity information. The default is N. You can define how EDI units of measure are converted to system units of measure in the EDI Pricing UOM Conversion Table control maintenance record. |
Field |
Applies To |
Description |
Grp/User to be Notified of 997 |
852 and 855 Outbound 850 and 810 |
Enter the User ID or Group ID who should be notified when an 997 transmission is received. |
Default Outgoing Transmission Status |
852 and 855 Outbound 850 and 810 |
Enter the default status to use for outgoing transmissions, such as SEND or HOLD. |
Alternate Interchange ID |
852 and 855 Outbound 850 and 810 |
Enter the interchange ID to use if the ID is different than the Primary ID listed in the current profile. The same format must be used: XX~ISAID~GSID |
Send Pricing Data in Qty UOM (Y/N) |
Outbound 810 Outbound 850 |
Enter Y to convert the pricing information to the same unit of measure as the quantity information. The default is N. You can define how EDI units of measure are converted to system units of measure in the EDI Pricing UOM Conversion Table control maintenance record. |
Disable Sending BP/Eclipse Part # |
Outbound 850 |
Enter Y to prevent the generic outbound 850 mapper from sending the BP qualifier followed by the internal Eclipse part number. The default is N. |
Use Purchase Order Date |
Outbound 850 |
Enter Y to use the purchase order's ship date when you create the outbound 850 by changing the purchase order's print status to E for EDI. Leave this field blank or enter N to use the date that the purchase order was entered instead of the order's ship date when you create the outbound 850 by changing the purchase order's print status to E for EDI. The default is N. |
Include Price Branch ID in N1 BT |
Outbound 850 |
Enter Y to include the four-digit pricing branch ID at the end of the EDI ID in the N1 BT 04 segment of the outbound 850 document. |
Include Price Branch ID in N1 BY |
Outbound 850 |
Enter Y to include the four-digit pricing branch ID at the end of the EDI ID in the N1 BY 04 segment of the outbound 850 document. |
Include Ship Branch ID in N1 ST for Directs |
Outbound 850 |
Enter Y to send the DUNS+4 for outbound 850s for direct ship orders. |
Enable Consolidated Drop Point PO |
Outbound 850 |
Enter Y to allow users to consolidate purchase orders by drop point. |
Include Customer Shipping Instructions on Directs |
Outbound 850 |
Indicate whether to include customer shipping instructions for direct sales orders. |
Include Country of Origin on PO1 Seg |
Outbound 850 |
Indicate whether to include the Country of Origin on the line item detail for purchase orders. |
2 or 3 Character Abbreviation |
Outbound 850 |
If you enter Yes in the Include Country of Origin on PO1 Seg field, then use this field to indicate if you need two or three characters for the country abbreviation. For example, the United Kingdom requires two (UK), but the United States requires three (USA). |
Field |
Applies To |
Description |
852 Processing Control File |
Outbound 852 |
Press F10 and select the trading partner-specific control record that determines how the system accumulates 852 data. |
Grp/User to be Notified of 997 |
852 and 855 Outbound 850 |
Enter the User ID or Group ID who should be notified when an 997 transmission is received. |
Default Outgoing Transmission Status |
852 and 855 Outbound 850 |
Enter the default status to use for outgoing transmissions, such as SEND or HOLD. |
Alternate Interchange ID |
852 and 855 Outbound 850 |
Enter the interchange ID to use if the ID is different than the Primary ID listed in the current profile. The same format must be used: XX~ISAID~GSID |
Transmission Method Override |
Outbound 810 Outbound 852 |
Enter an alternate transmission method to override the default transmission method set for the trading partner in EDI Trading Partner Profile Maintenance. For example, if you send invoices through a third party billing company, that company may have a different EDI transmission default than the customer to which the EDI trading partner profile is assigned. Use this field to specify an alternate transmission method for the outbound invoice. |
Include 'Catalog' Items |
Outbound 852 |
Enter Y to accumulate catalog index items and primary index items for the 852 report. The default is N. |
Include 'Tags' |
Outbound 852 |
Enter Y to include transfer quantities for tags sales order items. The default is DFLT. Leave this field set to DFLT to use the settings set in the selected file displayed in the 852 Processing Control File field. |
Field |
Applies To |
Description |
Grp/User to be Notified of 997 |
855 |
Enter the User ID or Group ID who should be notified when an 997 transmission is received. |
Default Outgoing Transmission Status |
855 |
Enter the default status to use for outgoing transmissions, such as SEND or HOLD. |
Alternate Interchange ID |
855 |
Enter the interchange ID to use if the ID is different than the Primary ID listed in the current profile. The same format must be used: XX~ISAID~GSID |
Automatically Send 855 Only One Time |
855 |
Set to Yes to send the 855 document only once. |
Disallow Job Management Outbound 855 |
855 |
Set to Yes to ignore the New Sales Order and EDI Sales Document activity triggers for Job Management orders and disable the E-EDI print status. The default is No. |
Field |
Applies To |
Description |
Grp/User to be Notified of 997 |
856 Advance Ship Notice |
Enter the User ID or Group ID who should be notified when an 997 transmission is received. |
Default Outgoing Transmission Status |
856 Advance Ship Notice |
Enter the default status to use for outgoing transmissions, such as SEND or HOLD. |
Alternate Interchange ID |
856 Advance Ship Notice |
Enter the interchange ID to use if the ID is different than the Primary ID listed in the current profile. The same format must be used: XX~ISAID~GSID |
Send Carton Packing Detail |
856 Advance Ship Notice |
If you generate an EDI 856 Advance Ship Notice from Sales Order Entry on an order in an invoiced status, the system sends carton packing data if found. If no carton packing data is found, the system treats the 856 as if this control maintenance record is set to No. The setting here overrides the Send Carton Packing Detail in EDI 856 control maintenance record. Note: Carton Packing is an Eclipse companion product. Contact your inside salesperson for more information. |
Suppress 856 for Credit Invoice |
856 Advance Ship Notice |
Indicate if you want to send an 856 advance notice for credit invoices. New in Release 8.7.9. |
Include Header Level Tracking Number |
856 Advance Ship Notice |
Set to Yes to include tracking numbers using the following hierarchy: 1. The system first uses tracking numbers posted to the change log in the sales order generation from the Shipping Manifest companion product. If found, the system uses these tracking numbers on the 856 outbound transaction. 2. If no tracking numbers are found in the change log, the system looks for tracking numbers added manually to the Internal Notes field on the sales order. These must be added with asterisks followed by the REF Qualifier, for example *CN1Z1234560300000010. If both are blank, the REF segment for the tracking numbers will not be reported, per EDI standards. Note: Any tracking numbers are sent to the Header for the Outbound 856. These two fields are mutually dependent. You must have both populated. |
REF Qualifier to Use |
856 Advance Ship Notice |
Multiple Outbound Transaction Fields
Field |
Applies To |
Description |
Send Pricing Data in Qty UOM (Y/N) |
Outbound 810 Outbound 850 |
Enter Y to convert the pricing information to the same unit of measure as the quantity information. The default is N. You can define how EDI units of measure are converted to system units of measure in the EDI Pricing UOM Conversion Table control maintenance record. |
Transmission Method Override |
Outbound 810 Outbound 852 |
Enter an alternate transmission method to override the default transmission method set for the trading partner in EDI Trading Partner Profile Maintenance. For example, if you send invoices through a third party billing company, that company may have a different EDI transmission default than the customer to which the EDI trading partner profile is assigned. Use this field to specify an alternate transmission method for the outbound invoice. |
Default Outgoing Transmission Status |
Outbound docs |
Enter one of the following options to define the initial status of the document in the EDI Outgoing Status Queue.
To change the status of a document, do so from the EDI Outgoing Status Queue, not from the group profile. |
Grp/User To Be Notified of 997 |
Outbound docs |
Enter the user or message group handling the account. |
Field |
Applies To |
Description |
Alternate Interchange ID |
All docs |
Enter a test ID or alternate production ID for your trading partner. The ID follows the same format as the group number. Use this field instead of setting up a separate profile for the purpose of testing with your partner. Note: When entering EDI Trading Partner Maintenance and entering a Trading Partner ID number, the IDs listed include this Alternate Interchange ID. We recommend that you always select the main profile and get to the Alternate Interchange ID through the main profile, not by selecting the alternate interchange at this point. |
Field |
Applies To |
Description |
Display 2 Decimals in Rebate Detail |
Outbound 844 Inbound 849 |
Enter Y to display the actual cost, rebate cost, difference amount, and the extended rebate amount for the total quantity sold of the product to two decimal places in outbound 844 rebate reports. The decimal place rounding also applies to inbound 849 rebate responses. Enter Y in this field to display the rebate cost, cost, and rebate amounts to two decimal places. Enter N to round to three decimal places. Note: The system uses standard rounding logic. If the third decimal place is 5 for greater, the second decimal point is rounded up. Amounts on the 849 rebate responses can extend anywhere from two to six digits. When the system compares the vendor cost on the inbound 849 to the cost in Eclipse, rounding may cause the system to see items on the 849 as exceptions. Use this field to indicate how you want the system to handle rounding to avoid rebate items from unnecessarily being considered exceptions. |
See Also:
Defining Documents Exchanged with EDI Groups