Ir al contenido principal

How to create an additional line text (ACLOB) on purchase orders for internal notes


Kyle Klinger
Sin conexiónhace 1 día
I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to. 
If you have a better way, please share.   
  1.  Add column to PORDERQ; YLINTEX2, Type TXC 
    1.  Save and validate table
    2. This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX
  2.  On screen POH2
    1. Add column YLINTEX2, to Block 1.
    2. Most likely you will want this field to be hidden.
    3. On column NBLIG add a button action ACLOB2, description "Text internal"
    4. This button action will require an action parameter "CODE2", it will not be available until after save.
    5. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added. 
    6. Save and validate the screen
  3. Custom code in SPEPOH
$ACTION
  Case ACTION
    When "ABANDON" : Gosub ABANDON # YK001 kklinger@lucidconsulting.com
    When "INICRE_LIG" : Gosub INICRE_LIG # YK001 kklinger@lucidconsulting.com 
    When "INIMOD_LIG" : Gosub INIMOD_LIG # YK001 kklinger@lucidconsulting.com 
    When Default
  Endcase
Return
$INICRE_LIG
  Gosub CHARG_TEXT_LIGNE
Return
$INIMOD_LIG
  Gosub CHARG_TEXT_LIGNE
Return
$ABANDON
For I=0 To [M:POH2]NBLIG-1
  If left$([M:POH2]YLINTEX2(I),3)="POQ" & [M:POH2]CREFLG(I)=0
  Call SUP_CLOB([M:POH2]YLINTEX2(I),WRETOUR) From TRTX3TEX
Endif
Next I
Return
$CHARG_TEXT_LIGNE
If [M:POH2]YLINTEX2(nolign-1)<>""
  If left$([M:POH2]YLINTEX2(nolign-1),3)="POQ"
    Call CRE_CLOB([M:POH2]YLINTEX2(nolign-1),GOK) From TRTX3TEX
    If GOK<1 Return : Endif
  Elsif !find(left$([M:POH2]YLINTEX2(nolign-1),3),"ITM","ITP")
    Call DUP_CLOB("POQ",[M:POH2]YLINTEX2(nolign-1),GOK) From TRTX3TEX
    If GOK<1 Return : Endif
  Endif
  [F:POQ]YLINTEX2=[M:POH2]YLINTEX2(nolign-1)
Endif
Return

Entradas populares de este blog

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...
Leer más

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

How To Add a Custom Selector for the Screen Field

Fuente original del artículo:   https://www.rklesolutions.com/blog/how-to-add-a-custom-selector-for-the-screen-field January 5, 2022 By RKL Team Leave a Comment There may be times when you want to add a pop-up window to select a field for a screen. Sometimes this can be handled automatically if the field is a standard X3 object field (i.e. when selecting a product with a type of ITM from the ITMMASTER table). There may be other times where a standard look-up is not available, and some custom code is required to do the selection window. We'll show you how to add a custom selector of your choosing to the screen field. ADD SELECT ON SCREEN FIELD The first step is to add the appropriate code to the field on the screen in Sage X3: Go to  Development > Script Dictionary > Screens Select Your Screen Select the field to have the lookup for  by moving your cursor to it on the screen. The field should show with a blue background. Select a type of "Selection" , and an  ac...
Leer más