Is it bad to have some common methods in POCO entities?
Is it bad design to have some common functions in POCO entities in Asp.NET MVC 3 + EF CF project?
Let's say i need function to get next record code generated by entity properties :

	public class Warehouse	{
		public string ReceivingRecordCodeFormat { get; set; }
		public int ReceivingRecordCodeNextNumber { get; set; }

		#region functions

		public string GetNextReceivingRecordCode()
		{
		    return ...
		}

		#endregion
	}
Is it bad to have some common methods in POCO entities?
===

Is it bad design to have some common functions in POCO entities in Asp.NET MVC 3 + EF CF project?
Let's say i need function to get next record code generated by entity properties :

	public class Warehouse	{
		public string ReceivingRecordCodeFormat { get; set; }
		public int ReceivingRecordCodeNextNumber { get; set; }

		#region functions

		public string GetNextReceivingRecordCode()
		{
		    return ...
		}

		#endregion
	}