Update Table via ABL

DEFINE buffer bUD04 FOR UD04.

for each ttInvcHead where ttInvcHead.InvoiceNum > 0 no-lock:

		find first bUD04 where
  	bUD04.Company = cur-comp and
  	bUD04.Key2 = string(ttInvcHead.OrderNum) and
		bUD04.Key1 = ttInvcHead.TermsCode and
		bUD04.Key3 = ttInvcHead.Character01 exclusive-lock.

		If available bUD04 then do:

				 /*if ttInvcHead.InvoiceNum > 0 then do: */
						ASSIGN bUD04.Number03 = ttInvcHead.InvoiceNum.

						RELEASE bUD04.
				/*end.*/
		end.
end.

How to create a UBAQ for PlantWhse – Primary Bin

Solution:

1. Add tables: Part, PartWhse, PlantWhse.  Display the key fields for these tables.

2. Check update for PlantWhse.PrimBin field.

3. Use the PartBO.

4. In Tables to Update check: ttPart and ttPartWhse 5. In Column Mapping add:

a. For ttPartWhse add an expresssion of ttResults.PlantWhse_Plant b.

DBTableName=ttPartWhse

DBFieldName=PrimBinNum

DataType=Character

Expression=ttREsults.PlantWhse_PrimBin

 

6. Regenerate BPM Directives.

7. Analyze > Get List.

8. Double click on a row to make the change 9. Update 10. Clear Grid 11. Get List to confim the change.

12. Also checked Part Maintenance to verify that it looks good.

Epicor Progress Licenses

Product License Addendum(s): 

                        Progress Software Corporation ('PSC') License Addendum

   License Notice:

       Entering the control codes listed on this license addendum into the computer
       system indicates your understanding and acceptance of the terms and conditions
       contained in the End User Product License Agreement ("the Agreement") located
       in this package, in the software download program, on the inside cover of the
       media box, in the "Read this First" book, or in the "Welcome to Progress" book.
       Please carefully read these terms and conditions before entering in the control
       codes.  If you do not agree with them, promptly return the media (all copies
       thereof) to Progress Software Corporation or the supplier from whom it was
       acquired for a full refund.  The Agreement is the entire agreement between the
       parties.  No modifications or additions to the Agreement will be binding,
       whether proposed via a purchase order or otherwise, unless agreed to in a
       writing executed by authorized representatives of the parties.

       The information below reflects Progress' current records.  Please verify and
       report any discrepancies to your supplier.

   Progress    Licensed Products as of June 18, 2009 for WIN 64-bit:

       Bill To:    10013263                      Shipped To:    10013263
           Epicor Software Corp.                     Epicor Software Corp.
           18200 Von Karman Ave Ste 1000             18200 Von Karman Ave Ste 1000
           IRVINE, CA 92612-1061                     IRVINE, CA 92612-1061
           USA                                       USA
           USA                                       USA
           Phone # 800-999-1809                      Phone # 800-999-1809
             Fax # 619-546-9777                        Fax # 619-546-9777

  Product                   Ship      Units  Release  MediaID Title          Maint Exp
  PSC Order #               Ord. Date
  ------------------------- --------- ------ -------- ------- -------------- ---------
   OE Development Server    06/18/09      1 10.2A    0212     10.2A Media    12/31/10
      SO450333        06/18/09 PO: Win 64 bit - D
      OE Development Ser Serial #:004021705 Rel: 10.2A Control#:Y8FRH TPJTM 54C?8
      Unit Type: Named User Based Pricing        Maint.:  OE Extended 24x7

   OE Enterprise RDBMS      06/18/09    500 10.2A    0212     10.2A Media    12/31/10
      SO450333        06/18/09 PO: Win 64 bit - D
      OE Enterprise RDBM Serial #:004021706 Rel: 10.2A Control#:XSB8Z 2P2XS K4MY8
      Unit Type: Named User Based Pricing        Maint.:  OE Extended 24x7

   OE DataServer for Oracle 06/18/09    500 10.2A    0212     10.2A Media    12/31/10
      SO450333        06/18/09 PO: Win 64 bit - D
      OE DataServer for  Serial #:004021707 Rel: 10.2A Control#:XGB8G TP2TR 24RY4
      Unit Type: Named User Based Pricing        Maint.:  OE Extended 24x7

                                          Page    1 of    2
   OE DataServer MS SQL Svr 06/18/09    500 10.2A    0212     10.2A Media    12/31/10
      SO450333        06/18/09 PO: Win 64 bit - D
      OE DataServer MS S Serial #:004021708 Rel: 10.2A Control#:YGB9Z TQ2XR KMM?4
      Unit Type: Named User Based Pricing        Maint.:  OE Extended 24x7

   OE Application Svr Ent   06/18/09    500 10.2A    0212     10.2A Media    12/31/10
      SO450333        06/18/09 PO: Win 64 bit - D
      OE Application Svr Serial #:004021709 Rel: 10.2A Control#:XSB9Z 6Q26R 3MRY4
      Unit Type: Named User Based Pricing        Maint.:  OE Extended 24x7

   NameServer Load Balance  06/18/09      1 10.2A    0212     10.2A Media    12/31/10
      SO450333        06/18/09 PO: Win 64 bit - D
      NameServer Load Ba Serial #:004021710 Rel: 10.2A Control#:XZBS? 6QJXC MMC?9
      Unit Type: Machine Based Pricing           Maint.:  OE Extended 24x7

Description Search Fix for Progress Databases

Summary:
SEARCH – No results returned from “where part description contains” with PG
Details:
PAGE 12207MPS

PROBLEM DESCRIPTION:
When I try to do a “where part description contains” search in my Progress database, it doesn’t return any results.

PROBLEM RESOLUTION:
There are two possible procedures to resolve this error. The procedures should be attempted in the order they are listed below.
NOTE: A full, recent, known good backup of your Progress database needs to be created before going through any/all of the procedures below.

PLEASE NOTE: If you are using the 64bit version of OpenEdge, you need to backup of your database and restore it on a machine with the 32bit version of OpenEdge installed to complete these steps. Afterwards, backup that database and restore it back on your live 64bit server.

PROCEDURE ONE:
With a UNICODE Database version, the Index rebuild needs to include the -cpinternal UTF-8 switch as part of the command line.

With the appservers and database stopped from the Explorer Tool:
1. Open the Proenv command window. Go to [Start] > All Programs > OpenEdge > Proenv
2. At the Proenv prompt, type the word:
prompt
and press enter.
3. Change directory into the folder with the db.
4. In the Proenv Command window, type the following command to change the word-break rules
Type: proutil mfgsys -C word-rules 254 <press enter>
Answer ” Y ” for yes
5. Go to [Start] > All Programs > OpenEdge > Data Administration
a. Database > Connect
b. Click browse and select the mfgsys.db file in your db folder > click Open
c. Click OK
d. Admin > Load Data and Definitions > Data Definitions (.df)
e. Click on Files and navigate to oe102a\prolang\utf; highlight _tran.df, click Open then click OK twice
f. Database > Disconnect; Are you sure? Click yes
6. From your ProEnv prompt, type the following command to rebuild the indexes.
proutil mfgsys -C idxbuild -cpinternal UTF-8 -TM 32 -TB 24 -B 60000
5. After the index rebuild completes, restart the database and appservers then log into database and retest issue

PROCEDURE TWO:
If the above solution didn’t resolve the “where part description contains” issue, an ascii dump and load of the database will be needed. Please contact support for the most recent dump and load kit.

VERSION:
8.03
9.04
9.05

KEYWORDS:
index
rebuild
full text
where part description

Create Different Colors by Company

  1. Options -> Style Fiter Manager
  2. Create a new style based on default for the company
  3. Name it with the company name
  4. Select the filter type Company and choose the company you want to fitlter on
  5. Save this to a file.
  6. Use the run tie styler to modify the style
  7. Select the company in the resource drop down before modifying the style
  8. Once styling is complete save the style file
  9. Open Theme Maintenance
  10. Import the new style file
  11. Mark it as distributable
  12. Actions -> Set Default
  13. Restart the epicor client.

How to set default schema in ODBC Connection to Progress – UPS

Goals:  How to set the default SQL-92 Schema on Windows for ODBC Connection ? How to avoid specifying the “PUB” schema in a SQL query
Facts:  Progress 9.x OpenEdge 10.x Windows NT 32 Intel/Windows 2000
Fixes:  Edit the Windows registry and depending if you are using a User or System DSN, add the default schema from the following entry:
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\<your DSN name>
or
HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\<your DSN name> For 64 bit Windows systems, you can find these keys under: HKEY_CURRENT_USER\Software\Wow6432Node\ODBC\ODBCI.INI or
HKEY_LOCAL_MACHINE\Software\Wow6432Node\ODBC\ODBCI.INI

To add the Default Schema (typically PUB if it is a 4GL Table): – Select the DSN Name, – In the right side of the Window, right-click – Select “New” – Select “String Value” – Type “DefaultSchema” – Enter – Double-Click on the newly added entry “DefaultSchema” – Enter the Default Schema (example : PUB)

Open4 – Epicor 9 interface

Summary: OPEN4 – Epicor/Vantage/Vista Interface Details
Book: Support Solutions
Page: 5139ESC

PAGE: 5139ESC Revised 5/06/2011

The Interface from Open4 to Vantage / Epicor 9 is setup so that for each Open4 database there is a corresponding Vantage/Epicor 9 database. Within that database several companies can be defined. It is a one to one relationship between each ERP database and the corresponding Open4 database.

There are three touch points in Open4. The first is defined in the desktop icon. Either in the properties, target line directly, or if you are running Vantage / Epicor 9 on SQL, in the .pf file. See Answerbook 3208ESC for more details on that. The second touch point is in the Epicor Master screen, which can be found in the menu path:

Human Resources > Open4 Interfaces > EPICOR Interface > Epicor Master

This is where you tell the system:

1. Which company or companies in Vantage / Epicor 9 you are connecting to.

2. What is the effective date of the connection for that company.

3. Which information to pull from Vantage / Epicor 9 for the payroll hours (from the labor header or the labor detail). The labor summary shows 40 hours for the week, whereas labor detail shows 8 hours on Monday, 8 hours on Tuesday, etc. for that company.

4. Which hours codes to use as default for that company. This MUST be completed if you are pulling time from Vantage / Epicor 9 into Open4.

5. Whether to update the Vantage / Epicor 9 labor rates based on pay changes in Open4 for that company. Most people check this checkbox so that the burdened labor rates in Vantage / Epicor 9 do not get updated by the Open4 pay rates.

IMPORTANT NOTE: The pay rate that is passed to Vantage Epicor 9 will be:

The Base pay rate for the employee PLUS the shift premium. The shift premium is based on the “home shift” which is in the employee’s Job category, Job Desc tab, Shift field.

6. What are the overtime rules used by that company (State rules may differ from the Federal rules).

There is also a process Pay Burden Rate Maintenance. The menu path is:

Human Resources > OPEN4 Interfaces> EPICOR Interface > Pay Rate Burden Maintenance

This allows you to setup a burden rate percentage by Division, Branch and Department. You must fill in each of the three values, none can be left blank. Open4 will then multiply the pay rate by the percentage that you entered and put it into Vantage / Epicor 9.

The third touch point is in the Employee Detail, under the category EPICOR, under the EPICOR Interface tab. Here when you set this record up it will pull certain date directly from Vantage / Epicor 9. The fields on the screen are:

Payroll Class – Set these up in Vantage / Epicor 9 in the Payroll Class maintenance program in Payroll, Setup (4 characters max).
Direct Labor Expense – Set these up in Vantage / Epicor 9 in the Indirect Labor Account maintenance in Job Management, Setup (16 characters max).
G/L Department – Set these up in Vantage in the Department maintenance program in General Ledger Setup in Vantage (not used in Epicor 9).
JC Department – Set these up in Vantage / Epicor 9 in the Department maintenance in Job Management, Setup (8 characters max).
Employee photo setup in Vantage / Epicor 9.

The first four will come in from Vantage / Epicor 9 initially and then get updated back to Vantage / Epicor 9 later if changed in Open4. The photo only comes in from Vantage / Epicor 9.

IMPORTANT NOTE:
The OPEN4 Division, Branch, and Department fields do not interface to Vantage/Epicor 9 as they have no corresponding entity in Vantage/Epicor 9.

In the Roles tab, if you check the Active Shop Employee checkbox, the system will create the Shop Floor employee record in Vantage / Epicor 9 (if it does not already exist).

The employee information in Open4 gets updated into Vantage / Epicor 9 based on the following tables and fields:

PREmpMas (Payroll Employee table) FIELDS Interfaced

PREmpMas.Company
PREmpMas.EmpID
PREmpMas.Address
PREmpMas.Address2
PREmpMas.BirthDate
PREmpMas.CanOverrideJob
PREmpMas.CanReportNCQty
PREmpMas.CanReportQty
PREmpMas.CanReportScrapQty
PREmpMas.CanRequestMaterial
PREmpMas.City
PREmpMas.ClassID
PREmpMas.Country
PREmpMas.CountryNum
PREmpMas.EMailAddress
PREmpMas.ExpenseCode
PREmpMas.FirstName
PREmpMas.GLDept
PREmpMas.HireDate
PREmpMas.JCDept
PREmpMas.LaborRate (Latest releases allow this as an option)
PREmpMas.LastName
PREmpMas.MaterialHandler
PREmpMas.MiddleInitial
PREmpMas.Name
PREmpMas.PayFrequency
PREmpMas.PayType
PREmpMas.Phone
PREmpMas.PhotoFile
PREmpMas.ProductionWorker
PREmpMas.ServTech
PREmpMas.Shift (Shift Field is NOT interfaced currently)
PREmpMas.ShipRecv
PREmpMas.ShopEmployee
PREmpMas.ShopSupervisor
PREmpMas.SocSecNum
PREmpMas.State
PREmpMas.SupervisorID
PREmpMas.Terminated
PREmpMas.TerminatedDate
PREmpMas.WorkCompCode (Interfaced only if available in OPEN4)
PREmpMas.ZIP

PREmpMas.EmgContact
PREmpMas.EmgPhone

EmpBasic (Shop Floor Employee table) FIELDS Interfaced

EmpBasic.Company
EmpBasic.EmpID
EmpBasic.PRSetupReq
EmpBasic.Address
EmpBasic.Address2
EmpBasic.CanOverrideJob
EmpBasic.CanReportNCQty
EmpBasic.CanReportQty
EmpBasic.CanReportScrapQty
EmpBasic.CanRequestMaterial
EmpBasic.City
EmpBasic.Country
EmpBasic.CountryNum
EmpBasic.EMailAddress
EmpBasic.EmgContact
EmpBasic.EmgPhone
EmpBasic.EmpStatus
EmpBasic.ExpenseCode
EmpBasic.FirstName
EmpBasic.JCDept
EmpBasic.LaborRate (Latest releases allow this as an option)
EmpBasic.LastName
EmpBasic.MaterialHandler
EmpBasic.MiddleInitial
EmpBasic.Name
EmpBasic.Phone
EmpBasic.PhotoFile
EmpBasic.ProductionWorker
EmpBasic.ServTech
EmpBasic.Shift (Shift Field is NOT interfaced currently)
EmpBasic.ShipRecv
EmpBasic.ShopSupervisor
EmpBasic.State
EmpBasic.SupervisorID

Interface Enhancements for the new (not yet available) interface (Vantage Connection) for Open4 will also include:

Pay category, Pay Change tab
Pay changes

NOTES:
1. If an employee has been assigned a supervisor in Open4 then both the employee and the supervisor records need to be in the Vantage / Epicor 9 Shop Floor Employee file. This is because Vantage / Epicor 9 will not allow changes to employees with a non-existing supervisor.

2. The labor hours that come in currently from Vantage DO NOT include Indirect time.

3. Writing records to Vantage / Epicor 9

Open4 writes the records to the Vantage tables PREMPMAS (Vantage / Epicor 9 Payroll Employee table) and EMPBASIC (Shop Floor Employee table) using checks for locks and either waits or produces an error message if it can’t write them. There is no added security for writing to these tables from Open4 and it is not subject to the Vantage / Epicor 9 security. It uses the “Trigger” logic.