![]() No part of this publication may be reproduced in any form without the prior written consent of Epicor Software Corporation. Copyright Epicor Software Corporation All rights reserved. All other trademarks mentioned are the property of their respective owners. Epicor is a registered trademark and/or trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. Additionally platform or product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs released by third parties after the date of publication of this document. All statements of platform and product compatibility in this document shall be considered individually in relation to the products referred to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible with both of the products running at the same time on the same platform or environment. All laws and requirements are subject to varying interpretations as well as to change and accordingly Epicor cannot guarantee that the software will be compliant and up to date with such changes. Where any software is expressed to be compliant with local laws or requirements in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws and requirements. Usage of the solution(s) described in this document with other Epicor software or third party products may require the purchase of licenses for such other products. ![]() The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. We welcome user comments and reserve the right to revise this publication and/or make improvements or changes to the products or programs described in this publication at any time, without notice. All information contained herein is subject to change without notice and changes to this document since printing and other important information about the software product are made or published in release notes, and you are urged to obtain the current release notes for the software product. As each user of Epicor software is likely to be unique in their requirements in the use of such software and their business processes, users of this document are always advised to discuss the content of this document with their Epicor account manager. However, Epicor Software Corporation makes no guarantee, representations or warranties with regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a particular purpose, merchantability, satisfactory quality or reasonable skill and care. This document and its contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its date of publication. This snippet will check for a CheckBox01 field equal to 'true' in User Maintenance, but you can tweak that "find first" statement / the "if" statement to do lookup whatever you prefer.1 Epicor ERP Epicor ERP Accounts Receivable Transaction Hierarchy 10Ģ Disclaimer This document is for informational purposes only and is subject to change without notice. ![]() Add a new action to synchronously execute 4GL code with the following code:įind first UserFile where UserFile.DcdUserID = DCD-USERID no-lock.įor each InvcHead where InvcHead.Company = ttInvcGrp.Company and InvcHead.GroupID = ttInvcGrp.GroupID and InvcHead.CreditMemo = true no-lock: Name it whatever you like and give it a group name.ģ. Establish a new BPM on the InvcGrp.PrePostInvoices method at Pre-Processing.Ģ. ![]() This is an example of the many practical ways simple BPMs can be utilized within Epicor® to modify system behavior.ġ. If you would like to restrict at a user level which users are allowed to post credit memos a very simple BPM can be established to control this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |