Saltar al contenido principal

Approval Template

Comentarios

3 comentarios

  • Geoff Booth

    Hey Carla,

    I'm not going to say I understand what you mean by triggering an approval however it appears to me that the >2000 is simply hanging out there by itself without belong to a where clause to indicate what it is being compared to.

     

  • Carla van Zyl

    Hi Geoff,

    When I add the query on SAP, and link it to an approval template, like the above screenshot it does not work. Most probably as you mentioned that its not confined to the IF statement.  How do I write it in an if/case statement that the system know they need to use the result of the sql query to do the check. 

    Also, is there any way I can get a docentry before a Purchase order gets added. So before the draft is even created. I have tried with docnum's dynamic syntax but its not unique. 

    Or alternatively, if I use the B1 Validations to get the Docentry ($[NEWID] ) after its posted, how do I still get it to potentially update the UDF on the docentry just added.

  • Geoff Booth

    It sounds like you are trying to use core SAP approvals. If that is the case here is the SAP logic flow:

    1. You enter data in the Purchase Order and click the add button
    2. SAP now checks to see if an approval is required
    3. If the approval is required SAP creates a draft document using ODRF (this has a DocNum)
    4. Once the document is approved then a Purchase Order is created. Note: the DocNum  on the PO may not be the same as the Draft as some other purchase orders may have been saved.

    Boyum should not be required as you can't have Boyum trigger an approval with using the DiAPI to create the draft document (very complex).

    Your approval logic seems very complex. Is there any way to simplify it?


     

Iniciar sesión para dejar un comentario.