Updating Batches via BOI

Question

Hello all! 
 I'm working on a script to auto approve batches but I am running into some issues. I looked through the BOI course and there is an example in there that updates the SalesOrder so I adapted my code from that. I'm not sure if I'm setting it to the right module or not. I'm a little confused on if I should be updating the Receipt Register or the GL. We run SAGE 100 MAS 90. Below is the code I currently have.

oGLPost = "" 
 Set oScript = CreateObject ( " ProvideX.Script " ) 
 oScript. Init ( " C:\sage\Sage 100 Advanced\MAS90\Home " ) 
 Set oSS = oScript. NewObject ( " SY_Session " ) 
 
 retVal = oSS. nLogon () 
 If retVal = 0 then 
 retVal = oss. nSetUser ( "user " , "password " ) 
 End If 
 
 retVal = oss. nSetCompany ( " TST " ) 
 retVal = oSS. nSetDate ( " P/O " , " 20200715 " ) 
 retVal = oSS. nSetModule ( " P/O " ) 
 
 oGLUI = oSS. nSetProgram ( oSS. nLookUpTask ( " PO_ReceiptRegister_UI " )) 
 
 WScript.Echo oSS. sLastErrorMsg & " Line 17 PO UPDATE UI set " 
 Set oGLPost = oScript. NewObject ( " PO_ReceiptRegister_upd " , oSS ) 
 
 WScript.Echo " Line 20 PO UPD set " 
 
 ' WScript.Echo "oGLPost set to new object" 
 
 If retVal = 0 Then 
 WScript.Echo oSS.sLastErrorMsg 
 'MessageBox.Show(oSS.sLastErrorMsg) 
 End If 
 
 retVal = oGLPost. nSelectBatch ( " 07864 " ) 
 WScript.Echo " Batch number set " 
 
 If CBool ( oGLPost. nProcessReport ( " DEFERRED " )) Then 
 retVal = oGLPost. nUpdate () 
 Select Case retVal 
 Case 0 
 WScript.Echo oGLPost.sLastErrorMsg 
 'MessageBox.Show(oGLPost.sLastErrorMsg) 
 Case 1 
 'MessageBox.Show("GL Updated Successfully!") 
 WScript.Echo " GL Updated Successfully! " 
 End Select 
 Else 
 'MessageBox.Show(oGLPost.sLastErrorMsg) 
 WScript.Echo oGLPost. sLastErrorMsg & " nProcessReport Else Statement Fired! " 
 End If 
 
 oGLPost. DropObject ()

Any help pointing me in the right direction is greatly appreciated!

js-goose · Accepted Answer

Hello David! Batching is enabled but that wasn't the issue. 
 We found the issues was in part, that we were missing some files from the 2018 version. Copying over the pvxwin32.config.exe and renaming it ending up solving the issue. 
 The other developer (much more experienced in SAGE than I am) said it had something to do with the Crystal Reports viewer version we were using. 
 
 Thank you again for all of your help and patience. It is greatly appreciated!

David Speck · Answer

Before nProcessReport, you need nSetPostingDate. 
 Make sure that the pvxwin32.exe.config file has been copied from the server's MAS90\Home directory to the workstation running the script's C:\Program Files (x86)\Common Files\Sage\Common Components directory as well as the server's C:\Program Files (x86)\Common Files\Sage\Common Components directory, then rename it from pvxwin32.exe.config to pvxcom.exe.config. 
 If you want to leverage paperless office instead of DEFERRED, copy the [Paperless] section from the server's MAS90\Launcher\SOTA.ini to the workstation running the script's MAS90\Home\PVX.ini file and it wouldn't hurt to also copy it to the server's MAS90\Home\PVX.ini. 
 You can search the forum for "_upd" and "*_upd" for more examples. 
 Here are two notable posts. 
 https://www.sagecity.com/support_communities/sage100_erp/f/sage-100-business-object-interface/152114/error-0-in-method-updateint/398520#398520 
 https://www.sagecity.com/support_communities/sage100_erp/f/sage-100-business-object-interface/111925/boi-upd-object---paperless-office/329553#329553

David Speck · Answer

Is batching enabled for PO Receipts? 
 Usually, you'll want to check the nBatchEnabled property, if 1, it is enabled and you should use nSelectBatch, if 0, it is not enabled and you should not use nSelectBatch. 
 Check if paperless office is set up for the PO journals/registers specifically or for all journals/registers for the target company, if it is enabled, you will need to copy the [Paperless] section from MAS90\Launcher\SOTA.ini to all instances of the PVX.ini file which should be found in MAS90\Home

Sage 100

Updating Batches via BOI

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING