There are three basic types of Configurator: * Product Selection – this is a method of filtering the Products, either with fixed filters, or depending on some questions asked. We may allow…Description complète
Introduction à la gestion d'immobilisations avec Sage X3Description complète
Description complète
Sage X3 securityDescription complète
Support de Formation. Finance Advanced Global. Version 6 SAGE ERP X3 FINANCE ADVANCED GLOBAL
Safe Profile Manual
Sage Profile Volume 2
Sage Profile Volume 3
Full description
Smart Plant User GuideDescription complète
User Guide to the optimization code OptistructFull description
pipesimDescripción completa
rwetrkjhgFull description
VodiaFull description
Wastewater Network Analysis and Design Software Product. SewerGEMS is a fully dynamic, multi-platform, sanitary and combined sewer modeling solution. Engineers can analyze sanitary or combi…Description complète
Descripción completa
C:\AVEVA\Plant\PDMS12.0.SP6\Manuals\Docs
This is the official instruction manual for the Motorola-brand Model GM 338 Professional Mobile Radio for Conventional System. This version of the manual was published in 2010, and was scanned f...Full description
SaludosFull description
For inspiration to conduct investigationsFull description
Descrição: rwetrkjhg
Fibersim 15 userguide
“ How To… To…”” Guide EDI Pro Process cessin ing g EDI Outbound - Functionality ........................................................................................................ 2 EDI BP Setup ................................................... ........................................................ ........................................................................... ................... 5 EDI Inbound – Functionality .......................................................................................................... 6 Inbound EDI Parameters P arameters ..................................................... ............................................................................................................. ........................................................ 6 EDI Status Monitor .................................................... ........................................................................................................... ................................................................. .......... 6 Inbound EDI Processing Flow .................................................................................................... 7
EDI EDI Outbound - Functi Functi onality X3 supports the following outbound EDI transactions: •
810 – Sales Invoices
•
850 – Purchase Orders
•
855 – Sales Acknowledgment
•
856 – Ship Notice
After all setup is complete, the outbound EDI processing EDI processing performs automatically as shown in the flowchart below for the 855 Sales Acknowledgement transaction. All outbound EDI transactions follow a similar flow depending on the entered document. Purchase Order entry entry will trigger the 850, 850, Shipment entry will trigger the 856, 856, Sales Sales Invoi ce entry ce entry will trigger the 810. 810.
The current EDI status for any Sales Sales Order, Purch ase Order, Shipment, or Sales Sales Invoice can Invoice can be viewed on the corresponding document. A Misc. tab Misc. tab displays the EDI status. status . See examples below.
EDI BP Setup The EDI BP Setup (GESXBG) function is used to enable specific business partners for particular EDI transactions. An overarching “EDI Active” flag can be set for the selected BP. In addition, each of the four supported EDI transactions can be activated separately for a given BP.
The second tab of the EDI BP Setup function can be used to hold specific identification parameters for use with EDI.
EDI Inbound – Functionality X3 supports the following inbound EDI transactions: •
810 – Purchase Invoices
•
850 – Sales Orders
Inbou nd EDI Parameters Parameters The Inbound EDI Parameters (GESXBF) function is used to link the EDI import templates and set the directory to be used with each. The templates entered here here can be controlled with the Active flag. Note: when the activity flag is changed for a given template, the EDI Status Monitor must be restarted for the change to take effect.
EDI Status Monitor The EDI Status Monitor (XBEDI) function is used to start and stop the inbound EDI processing. This function is found under the ADMIN the ADMIN menu menu at Usage > Batch Server > EDI Status Monitor.
The EDI Status Monitor displays the active inbound EDI transactions and their statuses. EDI EDI Status Status Moni tor f ields: Task Status – Indicates the current status of the task. Possible values are: Inactive o Active o •
Shutting Down Restart in Progress Query – The request number as shown in the Task Management function Status – Indicates – Indicates the current status of inbound EDI processing: Standby o In Progress o Finished o Held o Kill o Aborted o Error o Immediate o Warning o Processes – The – The process number for the EDI monitoring process o o
• •
•
EDI EDI Status Status Monitor b utton s: Run Now – Starts the inbound EDI monitor processing Stop – Stops the inbound EDI monitor processing Refresh – Refreshes – Refreshes the EDI Status Monitor fields • • •
EDI EDI Status Status Monito r line opti on: Log – Used to view the EDI monitor processing trace file •
Inbound EDI Processing Processing Flow •
•
•
July
When the EDI Status Monitor is started, a new process for each active EDI template is launched in batch mode called XBEDI. In the example above, an XBEDI task is created for XBIMP810 and XBIMP850.
The XBEDI process will periodically search the EDI directories defined in “Inbound EDI Parameters” for any EDI files that match the format 810_# or 850_#. When a file is found, that file is copied from the EDI EDI directory to the import directory located on the corresponding template (see below). NOTE: NOTE: the EDI EDI directory and t emplate directory m ust be different.
The files are copied in batches of 10 for efficiency. Once the files have been copied, a new batch batch task is submitted to import the corresponding EDI files. If the import is successful, a Purchasing Invoice (810) or Sales Order (850) is created. If the import is not successful, the Status of the EDI task will be “Error” on the EDI Status Monitor. The import file containing the error will be moved to the ERROR ERROR directory. It will maintain its same name with “.err” added as the extension. An error in one EDI file does NOT block the processing of other files.
To view view the errors, go to the Request Management (AREQUETE) function and select the corresponding EDI IMPORT process. Right click the line and select the Lo g button to display the import log file.
Once an error has been fixed, the file may be renamed (the .err extension removed) and copied back to the EDI directory for the EDI Status Monitor to reprocess. Or, the Import function may be run manually by selecting the error file to be reprocessed. Removing the the error file(s) from the error directory resets the EDI Status Monitor status for that task back from Error to to In Progress.