Sage X3

  Fuente original: Greytrix https://www.greytrix.com/blogs/sagex3/2012/03/31/accessing-sage-erp-x3-using-rf-radio-frequency-devices-vt220-terminals/ By  Greytrix   |   March 31, 2012 0 Comment Sage ERP X3 provides the ability to create stock transactions and production follow-up through Radio Frequency Terminals (RFT). RFT Devices connect to Sage ERP X3 using Terminal Server. Check Product :  Sage Enterprise Management Development Services Pre-requisites for accessing Sage ERP X3 using RF Devices Activate the Activity Code “ADC” Install Apache HTTP Server. Install Safe X3 Web Server. Configure Safe X3 Web Server using Sage X3 Console. Validating/Testing the Terminal Server Connection After successful installation of Safe X3 Web Server, start the Web Administration tool. In the Web Administration tool, go to the Terminal Server Tab and click on Configuration. This will list the Port and Host information for Terminal Server. In the Web Administration tool, go to the Terminal Server Tab a

Fuente original: SAGE https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=222924350018644  Creado el  15 diciembre 2021  | Última modificación el  15 diciembre 2021 Resumen What Ports are being used by the Sage X3 Solution Descripción Causa Ports or network traffic may be blocked by an anti-virus Ports can be blocked by the router or firewall Solución   CAUTION:   This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not  responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions.   The X3 Console will also typically display port information for each X3 component. Some commonly used ports are listed in the table below Port Service Managed By  Server(typical 1433 SQL Instance Local System Database Server 80 Apache(X3

  Fuente original: SAGE https://soporte.es.sage.com/selfservice/viewdocument.do?noCount=true&externalId=106267&sliceId=1&noCount=true&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=16322&cmd=displayKC&dialogID=724025&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true Created on 08-06-2020 / Last modified on 08-06-2020 Resumen Entorno: desde la versión 11. En este documento es una breve guía para adaptar un fichero EDI (de importación) donde viene un campo no previsto en la funcionalidad estándar y queremos incorporarlo a Sage X3. Por ejemplo, se recibe en una posición determinada del fichero CABPED.txt un código de 5 caracteres correspondiente al Departamento de Compra. Dicho código se quiere guardar en un campo llamado YDEPARTAMENT dentro de la Tabla SORDER. Además, este campo antes de introducirse en Sage X3 es necesario tratarlo de tal forma que se incorporará de esta forma: [

 Fuente origen del documento: https://lvexpertisex3.com/x3help/FRA/V7DEV/developer-guide_managing-asynchronous-operations.html Definition Because an operation is stateless and handles a list of parameters, it is possible to launch it asynchronously. When this happens: A temporary process executes the operation and receives the parameters. The user who launches the operation can take control and continue to work in his/her session while monitoring the execution progress. The temporary process ends automatically when the operation ends or if the server stops. To allow the user to control the asynchronous running task, a set of APIs is available and described below. The Context of execution An operation is stateless. The code that is executed during the operation run has access to  this , but the instance is empty. However, it can be filled using the AREAD or AINIT method. The parameters sent when calling the method are available as local variables. Because this execution is asynchronous,