Thursday, November 12, 2009
Information Rights Management (IRM)
Here's an interesting article from Fahim Siddiqui, EVP of Intralinks, Inc. His article can help organizations in understanding the complexity of applying encryption and permissioning to corporate information. Read article here
Tuesday, November 10, 2009
Revenue and Expense Deferral
What is Revenue and Expense Deferral (RED)?
Revenue Deferral is considered a liability until it becomes relevant to the business at hand, such as a payment received for work that has not yet been performed. opposite of deferred charge. Expense Deferral refers to an item that will initially be recorded as an asset but is expected to become an expense over time and/or through the normal operation of the business.
Who can use this module?
Dynamics GP RED (Revenue and Expense Deferral) was designed for any company that needs to defer revenue or expense.
Let's say you're a media company with business in magazine publishing. You're offering your magazine subscription on a yearly, semi-annually or monthly (one-time) basis. When somebody subscribes to your magazine and pay a year subscription, you'll need to defer part of this subscription. At the end of the subscription period, you will have fulfilled your responsibility and the subscription will be fully realized as earned income.
How do I book a deferred entry from a Sales Invoice in Dynamics GP?
Once you have the sales invoice created, open the Distribution window select the account you want to defer then go to Extras>Additional>Deferral. Enter your Start and End dates, billing recognition account and choose your deferral method (Days Period, Equal Period and Miscellaneous).
Things to note when using this module:
- Deferred entries are always valued at functional currency
- You can only defer one invoice at a time
- Void Deferral Transactions can be utilize to void deferred entries only and have the original document like a Sales Invoice unvoided
There's room for improvement with this module including:
- Mass document deferral
- Audit-trail from a GL entry
- Multi-currency reporting based on originating document currency
To learn more about Revenue and Expense Deferral, you can visit RevenueRecognition.com
Revenue Deferral is considered a liability until it becomes relevant to the business at hand, such as a payment received for work that has not yet been performed. opposite of deferred charge. Expense Deferral refers to an item that will initially be recorded as an asset but is expected to become an expense over time and/or through the normal operation of the business.
Who can use this module?
Dynamics GP RED (Revenue and Expense Deferral) was designed for any company that needs to defer revenue or expense.
Let's say you're a media company with business in magazine publishing. You're offering your magazine subscription on a yearly, semi-annually or monthly (one-time) basis. When somebody subscribes to your magazine and pay a year subscription, you'll need to defer part of this subscription. At the end of the subscription period, you will have fulfilled your responsibility and the subscription will be fully realized as earned income.
How do I book a deferred entry from a Sales Invoice in Dynamics GP?
Once you have the sales invoice created, open the Distribution window select the account you want to defer then go to Extras>Additional>Deferral. Enter your Start and End dates, billing recognition account and choose your deferral method (Days Period, Equal Period and Miscellaneous).
Things to note when using this module:
- Deferred entries are always valued at functional currency
- You can only defer one invoice at a time
- Void Deferral Transactions can be utilize to void deferred entries only and have the original document like a Sales Invoice unvoided
There's room for improvement with this module including:
- Mass document deferral
- Audit-trail from a GL entry
- Multi-currency reporting based on originating document currency
To learn more about Revenue and Expense Deferral, you can visit RevenueRecognition.com
Saturday, October 10, 2009
Get Customers with more than one address
Here's a simple SQL statement that I've used to help me resolve some of our issues be it customer, vendor or item master files:
Select custnmbr, Count(ADRSCODE) As AddressCount
From RM00102
Group By custnmbr
Having Count(ADRSCODE) > 1
or if you want detail use this
Select *
From RM00102
Inner Join (
Select CUSTNMBR, Count(ADRSCODE) As AddressCount
From RM00102
Group By CUSTNMBR
Having Count(ADRSCODE) > 1
) As A
On RM00102.CUSTNMBR = A.CUSTNMBR
Select custnmbr, Count(ADRSCODE) As AddressCount
From RM00102
Group By custnmbr
Having Count(ADRSCODE) > 1
or if you want detail use this
Select *
From RM00102
Inner Join (
Select CUSTNMBR, Count(ADRSCODE) As AddressCount
From RM00102
Group By CUSTNMBR
Having Count(ADRSCODE) > 1
) As A
On RM00102.CUSTNMBR = A.CUSTNMBR
Tuesday, September 15, 2009
SQL script to show last invoice detail of every customer
Copy and paste this to SQL Server Enterprise Manager:
select distinct a.custnmbr,a.LSTTRXDT,a.lsttrxam,b.sopnumbe
from rm00103 a
join sop30200 b
on a.custnmbr = b.custnmbr and
a.LSTTRXDT = b.docdate
/* show in ascending order */
order by custnmbr asc
select distinct a.custnmbr,a.LSTTRXDT,a.lsttrxam,b.sopnumbe
from rm00103 a
join sop30200 b
on a.custnmbr = b.custnmbr and
a.LSTTRXDT = b.docdate
/* show in ascending order */
order by custnmbr asc
Friday, April 24, 2009
Planning SQL Upgrade
So you finally decided to upgrade to SQL Server 2008 but it's been awhile since you looked at options for your Raid configurations. Here's a summary of what your options are:
Raid 0 - data is spread in different disk (disk stripping) but lacks redundancy
PROS - performs well on read and write
CONS - Failure of disk means data is lost
Raid 1 - known as disk mirroring no disk stripping. Data is hosted on a single drive then copied to another drive for fault tolerance. Recommended for Transaction Logs.
PROS - Redundant so failure of a drive will not stop database access
CONS - Cost since you'll need to double the size of your disk.
Raid 5 - uses disk stripping with parity. Data is spread but also stores parity information so it can be used in case of disk failure. Best for read-based not many write operations. Also avoid for transaction log because it's primarily sequential write.
PROS - Fault Tolerance at a low price.
CONS - Write Performance. Additional time is required to compute parity info before it's written to disk.
Raid 10 - cross between Raid 0 and 1. Data is striped evenly accross all drives then mirrored.
PROS - Write performance is far superior than Raid 5 and read performance is similar to Raid 5. Offers Fault Tolerance.
CONS - Cost since you'll need twice the number of disk like Raid 1.
Raid 0 - data is spread in different disk (disk stripping) but lacks redundancy
PROS - performs well on read and write
CONS - Failure of disk means data is lost
Raid 1 - known as disk mirroring no disk stripping. Data is hosted on a single drive then copied to another drive for fault tolerance. Recommended for Transaction Logs.
PROS - Redundant so failure of a drive will not stop database access
CONS - Cost since you'll need to double the size of your disk.
Raid 5 - uses disk stripping with parity. Data is spread but also stores parity information so it can be used in case of disk failure. Best for read-based not many write operations. Also avoid for transaction log because it's primarily sequential write.
PROS - Fault Tolerance at a low price.
CONS - Write Performance. Additional time is required to compute parity info before it's written to disk.
Raid 10 - cross between Raid 0 and 1. Data is striped evenly accross all drives then mirrored.
PROS - Write performance is far superior than Raid 5 and read performance is similar to Raid 5. Offers Fault Tolerance.
CONS - Cost since you'll need twice the number of disk like Raid 1.
Monday, April 20, 2009
SQL Wildcards
We implemented Multicurrency module and part of this implementation is changing the naming convention of our customers in Great Plains. We want to easily identify what kind of customer are they. Currently, our customer id ends in 001 so we decided to change it to whatever the contract currency is. So let's say ABC has a EURO contract with us then their customer id will then be ABCEUR instead of ABC001.
Our database is shared to other systems like our BI team to create relational DBs. A question came to my lap on the easiest way to segregate the customers based on their contract currency. We don't want to give them the Currency ID field as it's not consistent with other system. So I provided them with this Select statement:
Select * from RM00101
where custnmbr like '%[EUR]'
Our database is shared to other systems like our BI team to create relational DBs. A question came to my lap on the easiest way to segregate the customers based on their contract currency. We don't want to give them the Currency ID field as it's not consistent with other system. So I provided them with this Select statement:
Select * from RM00101
where custnmbr like '%[EUR]'
Thursday, March 26, 2009
Proud Uncle
I'm so proud of my niece, Guia del Prado, that I wanted to congratulate her in my blog for being featured in her schools website - University of Nevada, Reno : www.unr.edu .
She's currently the news editor for the campus magazine - Insight.
She's currently the news editor for the campus magazine - Insight.
Subscribe to:
Posts (Atom)