ENFOCADO A LAS PELÍCULAS

Use the Documents sheet to define the processing parameters for inbound EDI documents you accept from this customer trading partner when sent to you, and the outbound EDI documents you generate and then send back to the customer trading partner.

The Demand Management functionality in the Epicor application uses these definitions to recognize the specific Electronic Data Interchange (EDI) documents (such as Advanced Shipping Notices, sales order acknowledgments, invoices) that are generated in the Epicor application. The document processing parameters you enter for your customer trading partner in this sheet include:

• Assigning a unique identification number to the document.

• Specifying the type of document (for example, forecast, unfirm release, ASN, invoice) being defined. • Specifying the Map ID number and whether this is an inbound document you receive from this customer

trading partner, or is an outbound document you send to this customer trading partner. If it is an outbound document, you can specify if the Epicor application should automatically generate a document record that is deposited in a destination folder (for transmission to the customer trading partner via EDI) with no manual intervention required on the part of a user.

• Specifying the part hierarchy that the Epicor application should use to validate internal part, customer part, manufacturer part, EAN, GTIN or UPC codes on the inbound demand document when received from this customer trading partner.

Note Refer to Appendix C: Part Lookup and UOM Determination Flowchart for a graphical flowchart of this process.

• Specifying how incoming demand transactions for the document will be processed (Always Accept, Accept If No Errors, Manually Accept).

• Identifying an alternate trading partner ID (if any) being used for the document.

Programs and Their Modifiers

The following section describes the Customer Maintenance values you can change.

To access the Documents sheet and create a new document for a customer trading partner, select New Customer Document. These are the values you can modify for the sheet:

• Document - Specifies the identification number or name for this document. This is the number direct EDI import process or optionally, Service Connect references when it retrieves this inbound EDI document from, or sends to this outbound document through TIE KINETIX or another EDI application. This value should be unique per trading partner.

Tip For inbound Forecast, Unfirm Release and Incoming Shipping documents, the entry in this field must be the agreed upon document identifier used by both you and your customer trading partner for this particular document. For example, your customer trading partner may refer to an incoming shipping schedule as an ISS or a FIRM document on an inbound EDI transaction. You must enter the agreed upon value (or identifier), or the value you decide to use in your TIE KINETIX mappings, in this field.

• Test Record - This check box is only used for custom programming. When selected, the data for this document will not interact with your customer trading partner's data. This feature lets you test the document to ensure it works with your custom program. Normally, you should leave this check box cleared.

• Type - Specifies the type of inbound/outbound document being defined. For inbound documents, it also indicates the type of demand suggestion that the Epicor application will generate for the document. Select the type that applies to this document. Note that there can only be one document per document type per customer trading partner.

• Forecast - This inbound document allows you to receive projected quantities of parts from this customer trading partner. You then review and accept/reject these forecasts using Demand Entry; when accepted, the Epicor application creates forecast records in Forecast Entry. A forecast is a projected quantity of parts needed to satisfy demand. They are first calculated by part, then by customer, and are used by the MRP module to anticipate the demand from your customers.

• Unfirm Releases - This inbound document allows you to receive potential, or unfirm, order releases from this customer trading partner. You then review and accept/reject these unfirm releases using Demand Entry.

• Incoming Shipping Schedule - This inbound document allows you to receive firm order releases from this customer trading partner. You will then review and accept/reject these firm releases using Demand Entry. A firm order release is an order release that is definitely being shipped to your customer trading partner. When a release is firm, its quantity can then be turned into a job that can used to manufacture the parts, pull the parts from stock, or both.

• Advanced Shipping Notice - This outbound EDI 856/DESADV document is the Advanced Shipping Notice (ASN) that you send to this customer trading partner via EDI. It is used to track the progress of your shipments, and lets your customer trading partner know when order releases have been shipped from your company. You can also use it to reconcile differences between your shipped quantities and the actual quantities (received by your customer trading partner) using Demand Reconciliation. To learn more about reconciling quantities, refer to the Demand Reconciliation topic in the Application Help.

• Invoice - An outbound EDI 810/INVOIC document that sends an AR invoice to the customer trading partner. To learn more about invoicing, review the AR Invoice Entry topic in the Application Help. • Sales Order Acknowledgement - An outbound EDI 855/ORDRSP document that confirms that the

The Epicor application produces this when it generates a sales order for inbound demand received from the customer trading partner.

• Response to a Sales Order Charge - An outbound document that allows you to respond to your customer trading partner's request for a change to an existing sales order. The customer can accept the sales order with the change, accept the sales order without the change, or reject the sales order. The Epicor application produces this when it updates an existing sales order that was generated from inbound demand received from the customer trading partner.

• Order Status - An outbound document that reports the current state of a sales order. The Epicor application produces this when it generates a new sales order or updates an existing sales order created from inbound demand received from the customer trading partner.

• Direction - Specifies whether this is an inbound document you receive from this customer trading partner, or is an outbound document you send to this customer trading partner:

• Inbound - This is an inbound document you receive from this customer trading partner. • Outbound - This is an outbound document you send to this customer trading partner.

• Options Available - Displays the options available for selection for use by the Epicor application when it processes part number numbers and product codes this incoming EDI document when received from this customer trading partner. Refer to Options Selected for directions on how you select options and construct a hierarchical part number processing list.

• Check For Part - When selected, it denotes that the Epicor application should validate that corresponding part records exist for the part numbers listed on this inbound demand document when received from this customer trading partner. If a part record does not exist, a warning will automatically appear within the Demand Log for your review.

By performing this validation, it helps to ensure that the Epicor application is not accepted invalid part numbers on inbound EDI transactions received from this customer trading partner. However, by skipping this validation, you cannot ensure that invalid part numbers on inbound EDI transactions are not being accepted from this customer trading partner.

• Use Customer Part - When selected, this causes the Epicor application to search for and use customer part numbers in order to retrieve the corresponding internal part numbers. You create this customer part number cross reference using Customer Part Maintenance in the Epicor application.

• Manufacturer Part - When selected, this causes the Epicor application to search for and use manfacturer's part numbers in order to retrieve the corresponding internal part numbers. You create this manufacturer part number cross reference using Manufacturer Part Maintenance in the Epicor application.

• Use Part UPC - When selected, this causes the Epicor application to search for and use Universal Product Codes (UPC) in order to retrieve the corresponding internal part. You create this cross reference between UPC codes and internal part numbers in the Part Maintenance > Part - UOMs sheet.

Product codes are unique registered numbers that identify a specific part and UOM. An example of a product code is the UPC-12 (Universal Product Code) bar code found on most consumer items purchased in the USA and Canada. Other product codes (for example, GTIN-14, EAN-13) that can be entered in the UOMs sheet are used in various circumstances in different regions but are all similar to the UPC bar code. All part entry fields in the Epicor application allow entry or scanning of codes in lieu of entering an actual part number. If one of the codes is entered or scanned in a part field, the Epicor application replaces it with the part number and the correct UOM. The appropriate product code can also be printed on transaction documents, such as a receiving transaction.

• UPC-12 - This option operates in the same manner as Use Part UPC, but instead processes only UPC product codes of up to 12 digits in length.

• GTIN-14 - This option operates in the same manner as Use Part UPC, but instead processes GTIN-14 (Global Trade Item Number) product codes of up to 14 digits in length. It is the newest of the product codes and is used for both standard bar codes and as part of the data encoded on RFID tags.

• EAN-13 - This option operates in the same manner as Use Part UPC, but instead processes EAN-13 (European Article Number) product codes, 13 digits in length. It is referred to as a Japanese Article Number (JAN) in Japan. These codes are used worldwide for marking retail goods.

• EAN-14 - This option operates in the same manner as EAN-13, but instead processes EAN product codes 14 digits in length.

• EAN-8 - This option operates in the same manner as EAN-13, but instead processes EAN product codes eight digits in length.

• Options Selected - Specifies the hierarchical order in which the Epicor application should process part numbers and product codes contained on EDI transactions received from this customer trading partner. You construct the hierarchical processing list by selecting part options displayed in the Options Available field, and then clicking the appropriate directional buttons.

• For example, if you would want the Epicor application to first perform a Check For Part validation process, you select Check For Part in the Options Available field, then click the single right arrow button. • If you want it to next perform a Use Customer Part validation process, you then select Use Customer

Part in the Options Available field, then click the single right arrow button. Use the remaining buttons as follows:

• To move all options from the Options Available to Options Selected fields in the order in which they appear, click the double right arrow button.

• To move a selected option up in the hierarchy, select the option being moved in the Options Selected

field, then click the up arrow button. For example, if Use Part UPC is the fifth option listed, but you wish to make it the second option, select it, then click the up arrow button.

• To move a selected option down in the hierarchy, select the option being moved in the Options Selected

field, then click the down arrow button.

• To remove a single option from the Options Selected field, select the option being removed, then click the single left arrow button. For example, if you selected GTIN-14 but wish to remove it, select it, then click the single left arrow button.

• To remove all selected options from the Options Selected field, click the double left arrow button.

• Accept Type - Specifies if demand on this inbound EDI document should automatically be accepted or rejected for this customer trading partner:

• Always Accept - The Epicor application should automatically process demand for this customer trading partner, regardless of whether there are errors in the inbound EDI document.

This automatically creates demand entries in the Epicor application and immediately generates sales order and forecast entries at the time the inbound EDI file is successfully processed. This eliminates the need to manually use the Process selection in the Demand Header section of the Demand Entry Actions menu to process the demand.

In cases where the inbound EDI transaction does contain errors (for example, a Date Change action request is received with insufficient lead time, and a Stop or Warning condition would normally be applied), the Epicor application automatically overrides any System Rejection flags, processes the demand and subsequent sales order and forecast entries despite the error condition.

Refer to the Customer Maintenance > Customer > Demand section for more details on error conditions are how they are handled for a customer trading partner.

Note The manner in which Epicor ERP handles rejections (error conditions) while processing inbound EDI transactions depends on where the error occurs within the record:

• If it occurs at the Demand Header row level (for example, a duplicate PO error), the associated sales order and all attached order lines/order ship schedules generated from the demand header row are placed on hold.

• If it occurs at the Demand Detail row level (for example, a price mismatch error), only the associated order line and the attached order ship schedules generated from that demand detail row are placed on hold.

• If it occurs at the Demand Schedule row level (for example, a lead time error), only the order ship schedule generated from that demand schedule row are placed on hold.

Refer to Inbound EDI Transaction File Mappings for more details.

• Accept If No Errors - The Epicor application should automatically process demand for this customer trading partner only if there are no errors in the inbound EDI document. This eliminates the need to manually use the Process selection in the Demand Header section of the Demand Entry Actions menu to process the demand.

In the case of inbound EDI transactions, this automatically creates demand entries in the Epicor application and immediately generates sales order and forecast entries at the time an error-free inbound EDI file is successfully processed. This eliminates the need to manually use the Process selection in the Demand Header section of the Demand Entry Actions menu.

In cases where the inbound EDI transaction does contain errors (for example, a Date Change action request is received with insufficient lead time), the Epicor application handles in the normal manner - it applies Stop (with System Rejection) or Warning conditions, depending on the settings for the customer trading partner in the Customer Maintenance > Customer > Demand or Ship To > Demand sheets. It does not immediately generate sales order and forecast entries in these situations.

Refer to the Customer Maintenance > Customer > Demand section for more details on error conditions are how they are handled for a customer trading partner.

• Manually Accept - Demand from this incoming document for this customer trading partner should only be manually processed. In this case, the Epicor application or Service Connect creates demand entries but you must manually process them using the Process selection of the Demand Header section in the Demand Entry Actions menu. Order releases and forecast entries are only created at the time you perform this manual processing.

• Map ID - Specifies the program identifier for the document. This value is used during custom program development; it identifies the document for use with a custom program. Otherwise, this is a display-only field. • Outbound Document - If this is an outbound document, specify what processing should occur in the Epicor

application when the document is sent to this customer trading partner:

• Required / Document / Manual - These selections are not currently used and are reserved for future use.

• Automatic - When selected, this check box indicates that the Epicor application should automatically generate a supporting document record when the associated transaction is confirmed. If you select automatic generation, you do not have to manually generate the supporting document record when you process a transaction.

A document record similar to the following example is generated internally and supports subsequent printing of the associated document. It contains schema information (top portion of the record) and the actual information printed on the document (lower portion of the record). This is the information generated for an Advanced Shipping Notice (EDI 856/DESADV):

Example If you are defining the characteristics for the outbound Sales Order Acknowledgement document and you select this check box:

• It designates that the Epicor application will automatically generate the Sales Order Acknowledgement

document record soon as a sales order release is generated for inbound demand received from this customer trading partner. Refer to EDI 855/865/ORDRSP Transactions (Outbound Order Acknowledgements) for more details.

• Correspondingly, if you do the same thing for an Advanced Shipping Notice (ASN), it designates that the Epicor application will automatically generate the ASN document record as soon as a sales order is marked as shipped. Refer to EDI 856/DESADV Transactions (Outbound Advanced Shipping Notices) for more details.

• For an Invoice, it designates that the Epicor application will automatically generate the AR invoice document record as soon it is successfully posted to the General Ledger. Refer to EDI 810/INVOIC Transactions (Outbound Invoices) for more details.

Note: You must also use Business Activity Manager to enable auto-generation of outbound EDI files when triggered by specific processing actions or events that take place in within the Epicor application and database. Refer to Defining Outbound EDI Report Formats for more details.

• Alt Trading Partner - Specifies the trading partner identifier (ID) used with this document. Enter an alternate trading partner identification number into this field if the trading partner associated with the document is different than the identifier entered into the Trading Partner field on the Customer > Demand sheet. This indicates that another trading partner can receive data from this document.

Important To enable automatic processing for a document using the Automatic check box, a value must be entered into the Alt Trading Partner field! If an alternate trading partner is not associated with your customer trading partner, simply enter the trading partner identifier for your customer in this field.