Conclusiones extraídas del análisis de las encuestas

Once you have duplicated an existing report data definition (for example, EDIPckSl) in Report Data Maintenance, and have modified the duplicated record to your satisfaction, you then associate it with a specific type of document using Report Style Maintenance.

You use Report Style Maintenance to identify the different report styles that are available to a user when they print user-customizable reports and forms. You can define variations on each report you make available for specific companies within the Epicor application.

When you are using EDI, you must associate customized EDI-compatible versions of the report data definitions (you duplicated and modified in Report Data Maintenance) to a specific type of document to make them available for selection when you use certain programs in the Epicor application. You also designate what type of output (plain text or XML) should be generated, and the destination server folder in which the resulting output files should be stored for transmission via EDI to your customer trading partner. For example,

• Report data definitions that cause the Epicor application to generate document records that support outbound

EDI 810 (AR Invoice) transactions would generally be associated with Invoices. The user-customized version of these report data definitions should be added to the ARForm report. This makes them available for selection when printing invoices in AR Invoice Entry.

• Report data definitions that cause the Epicor application to generate document records that support outbound

EDI 855 (Order Acknowledgement) transactions would generally be associated with Sales Order Acknowledgements. The user-customized version of these report data definitions should be added to the

OrderAck report. This makes them available for selection when printing sales order acknowledgements in Sales Order Entry.

• Report data definitions that cause the Epicor application to generate document records that support outbound

EDI 856 (Advanced Shipping Notice) transactions would generally be associated with Packing Slips. The user-customized version of these report data definitions should be added to the PackSlip or MastPack

reports. This makes them available for selection when you produce packing slips in Customer Shipment Entry or Master Pack Shipment Entry (see below).

When selected, the report data definitions cause the Epicor application to generate text or XML-based document records that support outbound EDI 856 (ASN) transactions. Refer to EDI 856 Transactions (Outbound Advance Shipping Notices) for more details.

Menu Path

Navigate to this program from the Main Menu: • System Management > Reporting > Report Style

Important This program is not available in the Epicor Web Access.

To associate a report data definition with a selected type of document, use the Report ID field to enter the identification number for the report with which the report data definition is being associated (for example, Packing Slip), or click Report ID to search for the report ID. To create a new report style and associate a report data definition to the selected document or report, click New Report Style to access the Styles > Detail sheet. Use the Styles > Detail sheet to define the primary attributes of the customized report. The controls on this sheet let you create a new custom report or find and select an existing report. These are the values you can modify for the item:

• Style Number - Displays a system-assigned identification number for the report style. This is for display only. • Description - Specifies an identification number (for example, ASN - Text) for the report style. Referring to the example on the previous page, this is the description that appears when you print packing slips in Customer Shipment Entry or Master Pack Shipment Entry.

• Report Type - Specifies the type of report style being defined. For outbound EDI transactions, select Outbound EDI.

• Data Definition - Specifies the report data definition being associated with the selected document. Select the report data definition you previously created in Report Data Maintenance (for example, EDIASN). • Output Location - Identifies the pathname of the destination folder (for

example,c:\epicordata\edi_data\outbound\ASNs) on your server in which the Epicor application places outbound EDI files it generates when this report style is selected in a program such as Customer Shipment Entry or Master Pack Shipment Entry.

Once the Epicor application has deposited the file in the designated destination folder on your server, the third party TIE KINETIX eVision software retrieves the outbound document record and transmits it as an EDI transaction to your customer trading partner.

• Output EDI - Specifies the type of output (for example, Plain or XML File) that should be created when the Epicor application generates the EDI document record when this report style is selected. You select an output file type based on the mappings that will be used by TIE KINETIX eVision to create the actual EDI raw data. • Plain Text - Specifies that the EDI output for this report style should be generated in plain text format

• XML File - Specifies that the EDI output for this report style should be generated in XML format and stored in a .XML file. XML file formats contain the same output as in a plain text file, but in a more sophisticated output complete with XML tags and associated schema, but are generally far larger than standard text files.

• Company List - Specifies the companies for which this is a valid report style. Select the Valid check box in this grid if this is a valid report style for the corresponding company.

• Default - Indicates that this style is the default should be used when you print this form/report for the listed company. Only one style can be selected as the default for a company.

The following is an example of EDI-compatible report styles that would be associated with Sales Order

Acknowledgements in Report Style Maintenance. The Epicor application uses them to generate document records that support outbound EDI 855/865/ORDRSP (Order Acknowledgement) transactions:

The following is an example of EDI-compatible report styles that would be associated with Invoices in Report Style Maintenance. The Epicor application uses them to generate document records that support outbound EDI 810/INVOIC (AR Invoice) transactions: