Registry EOM Unvouchered AP GL Entries (sys-start-seomunvchrdap)


Configure Start Create EOM Unvouchered AP GL entries.

Testing Your Registry Entries
The system does not verify the validity of registry entries. Be sure to test your registry entries after completing them to verify that they are functioning correctly.

Setting Values are Uppercase-Lowercase Sensitive:
The Setting Value is case-sensitive: be sure that you enter the value exactly as specified in the documentation. If the documentation specifies a value of true, do NOT enter True or TRUE.

Related Registries:

Enabling this registry to Prevent User from Editing WO Other Tab Lines Imported from a PO will prevent PO Gen lines from be missed from inclusion in the post to GL.

Important Fields:

Id: sys-start-seomunvchrdap

See the Standard Registry section in Registry Viewer for additional Registry Id formats to allow entries for specific Users, Branches, Security, or User Groups to override the main entry.

Skip Report Attachment

Based on results obtained from performance monitoring on this function, generating the Summary and Detail reports and attaching them to the GL Journal Entry may result in performance issues.  The following registry allows the generation / attachment of one or both of these reports to be skipped when the function is run. These registries may be implemented if needed to improve this function's performance.

Setting Key: AttachSummaryDocument   Setting Value: false  (default is true)

Setting Key: AttachDetailDocument   Setting Value:  false   (default is true)

Include Only Open POs

A new registry setting is available for defaulting the Date Closed range field to the appropriate 'sql=' string so that only open PO's will be considered.

Id: sys-start-seomunvchrdap

Setting Key: OpenPOsOnly   Setting Value: true

For example, if this registry is enabled, the following sql statement will generated in the Closed range when the User selects the October 31, 2016 accounting period:

sql=(prchseordr_dte_clsd = '1900-01-01' or prchseordr_dte_clsd > '2016-10-31')

Drop Ship Orders

The purpose of this registry option is to preserve the original behavior of the EOM Unvouchered AP GL starter function, which included drop ship purchase orders. The default behavior of this function was altered in version 6.2 so that unvouchered payables from drop ship PO’s are no longer included in the calculation.

Setting Key: IncludeDropShipCOP Setting Value: true

Controlling Posting Detail

Prior to this release, the EOM-UVP function posted all debits and credits at the PO line item detail level.  This wasn't really necessary for the Credits and caused the resulting GL Journal entries to have nearly doubled the number of lines necessary to accurately reflect UVP dollars. The previous behavior with the credits also posted using GL Entities which isn't normal for Balance Sheet accounts. By default, credits will now be summarized and will not be posting using entities.

You may control level of detail being posted as well as the handling of entities via the following registry options.

Setting Key: SummarizeCredits Setting Value: true or false (the default is now true)

Setting Key: SummarizeDebits Setting Value: true or false (the default is now false)

We strongly suggested discussing these options with your support representative before implementation.

Setting Key: CreditsByEntity Setting Value: true or false (the default is false)

CreditsByEntity must be set to true if Intercompany is enabled.

In Version 9.0 and above, Credit Side Entities will be specified if EITHER of the following registries is enabled:

Id: sys-start-seomunvchrdap

Setting Key: CreditsByEntity  Setting Value: true


Id: sys-ffv-global-settings  

Setting Key: IntercompanyEnabled  Setting Value: true

EOM UVP for Sybase 7 and SQL 2000

The SQL that makes the UVP function run was changed in the spring of 2007 to fix an obscure bug encountered by a customer.  The corrected SQL fixed their problem but is running into what appears to be a bug in SQL 2000 and apparently in Sybase 7.  For users that can't upgrade their database, this case should remove last year's fix for the obscure bug. Revised SQL for Sybase 7 and SQL 2000 is activated by making this registry entry:

Setting Key: UseCase2263SQL Setting Value: true