Ir al contenido principal

Entradas

Mostrando entradas de febrero, 2022

Creating a Function to Call a Requester in Sage X3 V7 and After - Ejecución peticionario desde un menú

  Creating a Function to Call a Requester in Sage X3 V7 and After By:  Net at Work Team   | Category:  ERP Fuente origen: https://www.netatwork.com/creating-a-function-to-call-a-requester-in-sage-x3-erp-v7-and-after/ Saving a few clicks to open something is a good opportunity to showcase the capabilities of a system like  Sage X3 , so when a client asked us to create a function to call a requester, we took on the challenge. After you create your requester in Sage X3, you can go to the set-up function where you built the requester and click ‘Run.’ You can also go to Reports > View queries, search for the appropriate query, and run it. To avoid searching for records or giving access to the view queries function, you can follow the steps below to create a function that will call a requester. The first step is to create a function in the development area. While it sounds complicated, it’s really very straightforward and requires very few pieces of information. In our example, we’ll crea

Launch a batch execution request

  The following subprogram launches the execution of a V6 batch request from V7 native code. Main principles of a V6 batch task A V6 batch task is associated with an X3 function that executes an action using the  Standard processing  template. A criteria window with associated masks is then defined. You need to provide all the required parameters for the batch task execution by filling in all the fields for these masks. For these reasons, calling the  ASYRMNGTREQ.CRERQT  subprogram requires you to define the mask fields by filling in the corresponding values. Subprogram definition The API is called with the corresponding funprog: Func ASYRMNGTREQ.CRERQT(ACTX,FOLD,USER,TASK,DAT,TIM,ARYPAR,ARYVAL,NBPAR,REQUEST,MESSAGE) The parameters are the following: *  ACTX  is the current context. *  FOLD  is the folder name. *  USER  is the user code for execution. *  TASK is the task name. *  DAT is the date of the requested execution, and TIM is a string containing the requested time with the  hh: