Forum Replies Created

  • Denis Prokopenko

    Member
    02/28/2024 at 10:32 AM in reply to: Closing Shipper/Shipments with SQL

    Thank you Warren, this really helped me with my automation. Now I can have the program close the shippers at the end of day and have it trigger the invoice creation with the status change.

    I was also able to convert that whole thing into just plain text in my vb.net application and execute it successfully like so: “declare c qc_utl_pkg.cursor_type; begin c:=qc_sm_pkg.spu_sm_header_status(151836,20.00,’Y’); close c; end;”

    I will just need to create variables to have it switch the SHM_AUTO_KEY and the SMS_AUTO_KEY to the shippers

    If anyone else finds this useful, here is a recap.

    The task was to try and close the shipper with SQL and also have it trigger invoice creation.

    An SQL command for something like this would be something like this:

    declare

    c qc_utl_pkg.cursor_type;

    begin

    c:=qc_sm_pkg.spu_sm_header_status(151836,20.00,’Y’);

    close c;

    end;

    151836 = SMH_AUTO_KEY

    20.00 = SMS_AUTO_KEY

    ‘Y’ = COMMIT

  • Denis Prokopenko

    Member
    02/28/2024 at 8:45 AM in reply to: Closing Shipper/Shipments with SQL

    I found in our 17-year old bridge that this is what it was executing :

    Sqlcmd = “EXECUTE PROCEDURE SPU_SM_HEADER_STATUS(” + lcSMH_KEY + “,” + lcSMS_Key + ” )”

    SqlStat = sqlExec(sqlHand, SqlCmd, “curSMH”)

    What is actually being executed is this: qc_sm_pkg.spu_sm_header_status(152883,20.00,’Y’);

    152883= smh_auto_key

    20.00 = sms_auto_key

    ‘Y’= commit

    But this was built with FoxPro and I can’t seem to find the correct syntax for modern language

  • Denis Prokopenko

    Member
    04/10/2018 at 7:25 AM in reply to: DOCUMENT AND IMAGING (IDEAS)

    You’re welcome!

    If you run into any questions during your testing, feel free to reach out.

  • Denis Prokopenko

    Member
    02/28/2024 at 9:57 AM in reply to: Closing Shipper/Shipments with SQL

    This did the trick and creates the invoice as the shipment is closed! This has been bothering me for about a month now.

    So the cursor needs to be created for the package? That is whats been missing from my attempts.

  • Denis Prokopenko

    Member
    02/28/2024 at 9:30 AM in reply to: Closing Shipper/Shipments with SQL

    When I run this with qc_sm_pkg amd without it: qc_sm_pkg.spu_sm_header_status(151833,20.00,’Y’)

    I get Error:ORA-00900: invalid SQL statement

    When I try to encapsulate it in begin/end, I get this:

    Error:ORA-06550: line 2, column 1: PLS-00201: identifier ‘SPU_SM_HEADER_STATUS’ is not a procedure or is undefinable.

    Bottom line, I just don’t know the correct syntax for executing procedures/functions from packages. Is there a specific keyword that I should be using? Once I can get it to work in Quantum’s interactive SQL, I should be able to apply the same principle to my vb.net application that will be executing it to close shipments/shippers.

  • Denis Prokopenko

    Member
    02/28/2024 at 8:54 AM in reply to: Closing Shipper/Shipments with SQL

    vb.net but I’ll be fine with just getting it to a valid SQL that I can execute in Quantum to make sure it works. Whatever I try I just get an error after an error.

  • Denis Prokopenko

    Member
    10/23/2023 at 8:19 AM in reply to: Exchange 365 Online Email from Event Manager

    We currently use 10.10.23 and we are able to use SMTP to send out emails.

    You just need to contact Microsoft to enable the legacy smtp setting for you: smtp-legacy.office365.com

    This way you can still authorize services that only use TLS 1.0 to send emails as long as you have the mailbox use app password for its password authentication.

    Here is the link if you know how to do this yourself: https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/opt-in-exchange-online-endpoint-for-legacy-tls-using-smtp-auth