Failed Jobs

Enqueued 74,309 / 3 Scheduled 0 Processing 0 Succeeded 34,17,577 Failed 22,294 Deleted 1,31,383 Awaiting 0

Failed jobs do not become expired to allow you to re-queue them without any time pressure. You should re-queue or delete them manually, or apply AutomaticRetry(OnAttemptsExceeded = AttemptsExceededAction.Delete) attribute to delete them automatically.

Id	Job	Failed
#4295212	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. Fewer details...	4/9/2026 5:30:10 PM
#4295212	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295191	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 4:55:08 PM
#4295191	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295190	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 4:55:07 PM
#4295190	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295172	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 4:30:00 PM
#4295172	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295171	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 4:30:00 PM
#4295171	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295152	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 3:53:50 PM
#4295152	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295151	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 3:58:48 PM
#4295151	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295136	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 3:30:19 PM
#4295136	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295135	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 3:30:19 PM
#4295135	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295120	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 2:59:21 PM
#4295120	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295119	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 2:59:21 PM
#4295119	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295102	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 2:30:10 PM
#4295102	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295101	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 2:30:10 PM
#4295101	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295085	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 2:00:08 PM
#4295085	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295084	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 2:00:09 PM
#4295084	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295064	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 1:30:08 PM
#4295064	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295063	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 1:30:08 PM
#4295063	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295042	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 1:00:07 PM
#4295042	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295041	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 1:00:07 PM
#4295041	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4295021	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 12:30:06 PM
#4295021	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4295020	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 12:30:06 PM
#4295020	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294999	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 12:00:05 PM
#4294999	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294998	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 12:00:05 PM
#4294998	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294978	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 11:23:40 AM
#4294978	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294977	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 11:23:40 AM
#4294977	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294958	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 10:53:29 AM
#4294958	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294957	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 10:53:29 AM
#4294957	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294952	PostSapJobs.PostOrderToSap An exception occurred during performance of the job. More details...	4/9/2026 10:53:44 AM
#4294952	System.InvalidOperationException The 'Areacode' property on 'SP_GetPostOrder_head_Result' could not be set to a 'System.Int32' value. You must set this property to a non-null value of type 'System.String'. System.InvalidOperationException: The 'Areacode' property on 'SP_GetPostOrder_head_Result' could not be set to a 'System.Int32' value. You must set this property to a non-null value of type 'System.String'. at System.Data.Entity.Core.Common.Internal.Materialization.Shaper.ErrorHandlingValueReader`1.GetValue(DbDataReader reader, Int32 ordinal) at lambda_method(Closure , Shaper ) at System.Data.Entity.Core.Common.Internal.Materialization.Coordinator`1.ReadNextElement(Shaper shaper) at System.Data.Entity.Core.Common.Internal.Materialization.Shaper`1.SimpleEnumerator.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at OOP.BackgroundTask.Orders.PostOrderToSap.<>c__DisplayClass34_0.<PostOrderToSapDivisionWise>b__1(PostOrderToSapDto post) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Orders\PostOrderToSap.cs:line 131 at System.Collections.Generic.List`1.ForEach(Action`1 action) at OOP.BackgroundTask.Orders.PostOrderToSap.PostOrderToSapDivisionWise(Int32 OrderId, Int32 DivisionOrderID, Int32 OrderAmendmentID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Orders\PostOrderToSap.cs:line 110
#4294951	OrderJobs.SendOrderConfirmationMail An exception occurred during performance of the job. More details...	4/9/2026 3:12:54 PM
#4294951	System.Data.Entity.Core.MetadataException Schema specified is not valid. Errors: The relationship 'OOPDBModel.FK__AUTH_Role__Creat__4C0144E4' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__AUTH_Role__Modif__4CF5691D' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__52AE4273' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__567ED357' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__54968AE5' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__5772F790' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__558AAF1E' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__595B4002' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__CFG_BPCat__Creat__5F141958' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__CFG_BPCat__Modif__60083D91' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__Discount___Creat__63D8CE75' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__Discount___Modif__65C116E7' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__MST_Addre__Creat__76226739' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__MST_Addre__Modif__77168B72' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__MST_BP_Ba__Creat__094A4A46' was not loaded because the type 'OOPDBModel.MST_BP_Bank' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Bank'. The relationship 'OOPDBModel.FK__MST_BP_Ba__Modif__0A3E6E7F' was not loaded because the type 'OOPDBModel.MST_BP_Bank' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Bank'. The relationship 'OOPDBModel.FK__MST_BP_Bi__Creat__2B0043CC' was not loaded because the type 'OOPDBModel.MST_BP_BillShipTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_BP_BillShipTo'. The relationship 'OOPDBModel.FK__MST_BP_Pa__Creat__0F03239C' was not loaded because the type 'OOPDBModel.MST_BP_PayTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_PayTerms'. The relationship 'OOPDBModel.FK__MST_BP_Pa__Modif__0FF747D5' was not loaded because the type 'OOPDBModel.MST_BP_PayTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_PayTerms'. The relationship 'OOPDBModel.FK__MST_BPGro__Creat__12D3B480' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__MST_BPGro__Modif__14BBFCF2' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__MST_City__Create__1C5D1EBA' was not loaded because the type 'OOPDBModel.MST_City' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_City'. The relationship 'OOPDBModel.FK__MST_City__Modifi__00750D23' was not loaded because the type 'OOPDBModel.MST_City' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_City'. The relationship 'OOPDBModel.FK__MST_Conta__Creat__025D5595' was not loaded because the type 'OOPDBModel.MST_Contact' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Contact'. The relationship 'OOPDBModel.FK__MST_Conta__Creat__0539C240' was not loaded because the type 'OOPDBModel.MST_ContactMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_ContactMapping'. The relationship 'OOPDBModel.FK__MST_Conta__Modif__035179CE' was not loaded because the type 'OOPDBModel.MST_Contact' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Contact'. The relationship 'OOPDBModel.FK__MST_Count__Creat__062DE679' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__MST_Count__Creat__090A5324' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__MST_Count__Modif__07220AB2' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__MST_Count__Modif__09FE775D' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__MST_Curre__Creat__0BE6BFCF' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__MST_Curre__Modif__0CDAE408' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__MST_Emplo__Creat__147C05D0' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Emplo__Modif__15702A09' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Emplo__UserI__16644E42' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Logo__Modifi__2B7F66B9' was not loaded because the type 'OOPDBModel.MST_Logo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_Logo'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__184C96B4' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__1FEDB87C' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__1A34DF26' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__21D600EE' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__MST_MAP_L__Modif__33208881' was not loaded because the type 'OOPDBModel.MST_MAP_Logo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_Logo'. The relationship 'OOPDBModel.FK__MST_State__Creat__25A691D2' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__MST_State__Modif__269AB60B' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__MST_UOM__Created__297722B6' was not loaded because the type 'OOPDBModel.MST_UOM' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_UOM'. The relationship 'OOPDBModel.FK__MST_UOM__Modifie__2A6B46EF' was not loaded because the type 'OOPDBModel.MST_UOM' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_UOM'. The relationship 'OOPDBModel.FK__ORG_Busin__Creat__2B5F6B28' was not loaded because the type 'OOPDBModel.ORG_Business_Entity' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Entity'. The relationship 'OOPDBModel.FK__ORG_Busin__Creat__2E3BD7D3' was not loaded because the type 'OOPDBModel.ORG_Business_Unit' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Unit'. The relationship 'OOPDBModel.FK__ORG_Busin__Modif__2C538F61' was not loaded because the type 'OOPDBModel.ORG_Business_Entity' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Entity'. The relationship 'OOPDBModel.FK__ORG_Busin__Modif__30242045' was not loaded because the type 'OOPDBModel.ORG_Business_Unit' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Unit'. The relationship 'OOPDBModel.FK__PR_PriceL__Creat__36D11DD4' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__PR_PriceL__Modif__37C5420D' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__PROD_Appl__Creat__3AA1AEB8' was not loaded because the type 'OOPDBModel.PROD_Applicability' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Applicability'. The relationship 'OOPDBModel.FK__PROD_Appl__Modif__3B95D2F1' was not loaded because the type 'OOPDBModel.PROD_Applicability' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Applicability'. The relationship 'OOPDBModel.FK__PROD_Attr__Creat__3E723F9C' was not loaded because the type 'OOPDBModel.PROD_Attribute' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Attribute'. The relationship 'OOPDBModel.FK__PROD_Attr__Creat__405A880E' was not loaded because the type 'OOPDBModel.PROD_AttributeSet' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_AttributeSet'. The relationship 'OOPDBModel.FK__PROD_Attr__Modif__3F6663D5' was not loaded because the type 'OOPDBModel.PROD_Attribute' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Attribute'. The relationship 'OOPDBModel.FK__PROD_Attr__Modif__414EAC47' was not loaded because the type 'OOPDBModel.PROD_AttributeSet' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_AttributeSet'. The relationship 'OOPDBModel.FK__PROD_BPPr__Creat__4242D080' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__PROD_BPPr__Modif__4336F4B9' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__PROD_Bran__Creat__442B18F2' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__PROD_Bran__Modif__451F3D2B' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__PROD_Cate__Creat__46136164' was not loaded because the type 'OOPDBModel.PROD_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Category'. The relationship 'OOPDBModel.FK__PROD_Cate__Modif__47FBA9D6' was not loaded because the type 'OOPDBModel.PROD_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Category'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__01741E54' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__5EDF0F2E' was not loaded because the type 'OOPDBModel.PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__65C116E7' was not loaded because the type 'OOPDBModel.PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGallery'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__68A8708A' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__699C94C3' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6A90B8FC' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6B84DD35' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6C79016E' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6D6D25A7' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6E2152BE' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6E6149E0' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6F1576F7' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6F556E19' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70099B30' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70499252' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70FDBF69' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__004002F9' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__007FFA1B' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__01342732' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__02284B6B' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0268428D' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__031C6FA4' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__041093DD' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0504B816' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__05F8DC4F' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__15FA39EE' was not loaded because the type 'OOPDBModel.PROD_ProductTax' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductTax'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__5FD33367' was not loaded because the type 'OOPDBModel.PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__67A95F59' was not loaded because the type 'OOPDBModel.PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGallery'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__750E476F' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__76026BA8' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__76F68FE1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__77EAB41A' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__78DED853' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Size__Creat__072CF7AA' was not loaded because the type 'OOPDBModel.PROD_SizeGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SizeGroup'. The relationship 'OOPDBModel.FK__PROD_Size__Modif__08211BE3' was not loaded because the type 'OOPDBModel.PROD_SizeGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SizeGroup'. The relationship 'OOPDBModel.FK__PROD_Styl__Creat__0915401C' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__PROD_Styl__Modif__0A096455' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__SC_BpCate__Creat__0DD9F539' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_BpCate__Modif__0ECE1972' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_BpExcl__Creat__10B661E4' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpExcl__Modif__11AA861D' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpIncl__Creat__1486F2C8' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__SC_BpIncl__Modif__157B1701' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__SC_Policy__Creat__1C281490' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__SC_Policy__Modif__1D1C38C9' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__SC_ProdAl__Creat__1E105D02' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdAl__Modif__1F04813B' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdEx__Creat__23C93658' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__Creat__563FA78C' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_ProdEx__Modif__24BD5A91' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__Modif__5733CBC5' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__1AC9DC03' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__2B6A5820' was not loaded because the type 'OOPDBModel.SC_ProdGroupAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupAlternate'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__302F0D3D' was not loaded because the type 'OOPDBModel.SC_ProdGroupDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDirectDiscount'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__1E9A6CE7' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__2C5E7C59' was not loaded because the type 'OOPDBModel.SC_ProdGroupAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupAlternate'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__321755AF' was not loaded because the type 'OOPDBModel.SC_ProdGroupDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDirectDiscount'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__461E4E5C' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__4CCB4BEB' was not loaded because the type 'OOPDBModel.SC_ProductMappingHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMappingHeader'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__4E7E8A33' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__480696CE' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__4EB3945D' was not loaded because the type 'OOPDBModel.SC_ProductMappingHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMappingHeader'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__5066D2A5' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SC_StateM__Creat__509BDCCF' was not loaded because the type 'OOPDBModel.SC_StateMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_StateMapping'. The relationship 'OOPDBModel.FK__SC_StateM__Modif__51900108' was not loaded because the type 'OOPDBModel.SC_StateMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_StateMapping'. The relationship 'OOPDBModel.FK__SET_Banne__Creat__02D256E1' was not loaded because the type 'OOPDBModel.SET_Bannerdivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Bannerdivision'. The relationship 'OOPDBModel.FK__SET_Banne__Creat__63CEACD4' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__SET_Banne__Modif__04BA9F53' was not loaded because the type 'OOPDBModel.SET_Bannerdivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Bannerdivision'. The relationship 'OOPDBModel.FK__SET_Banne__Modif__64C2D10D' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__SET_MenuP__Creat__69727791' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Creat__6A669BCA' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Modif__6F2B50E7' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Modif__701F7520' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_NewLa__Creat__15BB0E23' was not loaded because the type 'OOPDBModel.SET_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunch'. The relationship 'OOPDBModel.FK__SET_NewLa__Creat__198B9F07' was not loaded because the type 'OOPDBModel.SET_NewLaunchDetail' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunchDetail'. The relationship 'OOPDBModel.FK__SET_NewLa__Modif__16AF325C' was not loaded because the type 'OOPDBModel.SET_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunch'. The relationship 'OOPDBModel.FK__SET_NewLa__Modif__1B73E779' was not loaded because the type 'OOPDBModel.SET_NewLaunchDetail' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunchDetail'. The relationship 'OOPDBModel.FK__SET_Sales__Creat__1DE63FD0' was not loaded because the type 'OOPDBModel.SET_SalesPersonLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_SalesPersonLink'. The relationship 'OOPDBModel.FK__SET_Sales__Modif__1FCE8842' was not loaded because the type 'OOPDBModel.SET_SalesPersonLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_SalesPersonLink'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__324172E1' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__5A054B78' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__3429BB53' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__5BED93EA' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__MST_Sales__Creat__19218AB3' was not loaded because the type 'OOPDBModel.MST_SalesPerson' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_SalesPerson'. The relationship 'OOPDBModel.FK__MST_Sales__Modif__1A15AEEC' was not loaded because the type 'OOPDBModel.MST_SalesPerson' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_SalesPerson'. The relationship 'OOPDBModel.FK__SET_Proje__Creat__5E169ED5' was not loaded because the type 'OOPDBModel.SET_Projects' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Projects'. The relationship 'OOPDBModel.FK__SET_Proje__Modif__5FFEE747' was not loaded because the type 'OOPDBModel.SET_Projects' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Projects'. The relationship 'OOPDBModel.FK__SET_Relea__Creat__63CF782B' was not loaded because the type 'OOPDBModel.SET_ReleaseNote' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_ReleaseNote'. The relationship 'OOPDBModel.FK__SET_Relea__Modif__65B7C09D' was not loaded because the type 'OOPDBModel.SET_ReleaseNote' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_ReleaseNote'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__0955373E' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__100234CD' was not loaded because the type 'OOPDBModel.MST_Privacy_Details' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__0A495B77' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__10F65906' was not loaded because the type 'OOPDBModel.MST_Privacy_Details' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details'. The relationship 'OOPDBModel.FK__TRAN_BuyN__UserI__70FDBF69' was not loaded because the type 'OOPDBModel.TRAN_BuyNow' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_BuyNow'. The relationship 'OOPDBModel.FK__TRAN_Cart__Creat__17236851' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_Cart__UserI__041B80D5' was not loaded because the type 'OOPDBModel.TRAN_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Cart'. The relationship 'OOPDBModel.FK__TRAN_Cart__UserI__0ABD916C' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_Comp__UserI__07EC11B9' was not loaded because the type 'OOPDBModel.TRAN_Compare' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Compare'. The relationship 'OOPDBModel.FK__Tran_Orde__Creat__30A4D9E0' was not loaded because the type 'OOPDBModel.Tran_OrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderEmployeeDetails'. The relationship 'OOPDBModel.FK__TRAN_Orde__Creat__54B68676' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__Modif__569ECEE8' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__UserI__4D1564AE' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__29C206D0' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__2F7AE026' was not loaded because the type 'OOPDBModel.TRAN_Privacy_AgreedPolicy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_AgreedPolicy'. The relationship 'OOPDBModel.FK__TRAN_Priv__UserI__2BAA4F42' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response'. The relationship 'OOPDBModel.FK__TRAN_Rece__UserI__08E035F2' was not loaded because the type 'OOPDBModel.TRAN_RecentSearchTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_RecentSearchTerms'. The relationship 'OOPDBModel.FK__TRAN_Rece__UserI__24B26D99' was not loaded because the type 'OOPDBModel.TRAN_RecentViews' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_RecentViews'. The relationship 'OOPDBModel.FK__TRAN_Sale__Creat__09D45A2B' was not loaded because the type 'OOPDBModel.TRAN_Sales_Promotion' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Sales_Promotion'. The relationship 'OOPDBModel.FK__TRAN_Sale__Modif__0AC87E64' was not loaded because the type 'OOPDBModel.TRAN_Sales_Promotion' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Sales_Promotion'. The relationship 'OOPDBModel.FK__Tran_Temp__Creat__328D2252' was not loaded because the type 'OOPDBModel.Tran_TempOrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_TempOrderEmployeeDetails'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__1451E89E' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__15460CD7' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__163A3110' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Creat__54B68676' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Modif__569ECEE8' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__UserI__4D1564AE' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_Wish__UserI__257C74A0' was not loaded because the type 'OOPDBModel.TRAN_WishList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_WishList'. The relationship 'OOPDBModel.FK__SET_UserC__UserI__795DFB40' was not loaded because the type 'OOPDBModel.SET_UserCustomSettings' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.SET_UserCustomSettings'. The relationship 'OOPDBModel.FK__PROD_SubB__Creat__0AFD888E' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__PROD_SubB__Modif__0BF1ACC7' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__Tran_Prod__Creat__3E5EC7B1' was not loaded because the type 'OOPDBModel.Tran_Productcataloguedownloadqueue' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Productcataloguedownloadqueue'. The relationship 'OOPDBModel.FK__TRAN_Adva__Creat__6855017D' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__TRAN_Adva__Modif__6A3D49EF' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__5D8338A6' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__5F6B8118' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__UserI__5B9AF034' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__1FDB0BE8' was not loaded because the type 'OOPDBModel.SC_ProdGroupMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupMapping'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__21C3545A' was not loaded because the type 'OOPDBModel.SC_ProdGroupMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupMapping'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__11F700E5' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__12EB251E' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__Tran_Orde__Creat__0F3A8FCB' was not loaded because the type 'OOPDBModel.Tran_OrderitemProposedQty' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderitemProposedQty'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__3AD6B8E2' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__44CB02C7' was not loaded because the type 'OOPDBModel.PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__3CBF0154' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__46B34B39' was not loaded because the type 'OOPDBModel.PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK_Tran_Loginlink_AUTH_User' was not loaded because the type 'OOPDBModel.Tran_Loginlink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Loginlink'. The relationship 'OOPDBModel.FK__SC_Divisi__Creat__185783AC' was not loaded because the type 'OOPDBModel.SC_DivisionMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_DivisionMapping'. The relationship 'OOPDBModel.FK__SC_Divisi__Modif__1A3FCC1E' was not loaded because the type 'OOPDBModel.SC_DivisionMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_DivisionMapping'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__63456846' was not loaded because the type 'OOPDBModel.MST_Privacy_Details1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details1'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__64398C7F' was not loaded because the type 'OOPDBModel.MST_Privacy_Details1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details1'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__6621D4F1' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy1'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__6715F92A' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy1'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__680A1D63' was not loaded because the type 'OOPDBModel.TRAN_Privacy_AgreedPolicy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_AgreedPolicy1'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__6BDAAE47' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response1'. The relationship 'OOPDBModel.FK__TRAN_Priv__UserI__6DC2F6B9' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response1'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__5205CDAB' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__52F9F1E4' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__53EE161D' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__16F0C02C' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__17E4E465' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__25132BA3' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__18D9089E' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__19CD2CD7' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__26FB7415' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__BO_PROD_P__Creat__71B44E85' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Creat__72A872BE' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Modif__739C96F7' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Modif__7490BB30' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Creat__65C116E7' was not loaded because the type 'OOPDBModel.BO_PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductGallery'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Modif__15FA39EE' was not loaded because the type 'OOPDBModel.BO_PROD_ProductTax' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductTax'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Modif__67A95F59' was not loaded because the type 'OOPDBModel.BO_PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductGallery'. The relationship 'OOPDBModel.FK__BO_PROD_S__Creat__01EAB64E' was not loaded because the type 'OOPDBModel.BO_PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_SearchTags'. The relationship 'OOPDBModel.FK__BO_PROD_S__Modif__02DEDA87' was not loaded because the type 'OOPDBModel.BO_PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_SearchTags'. The relationship 'OOPDBModel.FK__Emp_Categ__Creat__50679DFC' was not loaded because the type 'OOPDBModel.Emp_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Emp_Category'. The relationship 'OOPDBModel.FK__Emp_Categ__Modif__524FE66E' was not loaded because the type 'OOPDBModel.Emp_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Emp_Category'. The relationship 'OOPDBModel.FK__ExcelFail__Creat__35E8B1EA' was not loaded because the type 'OOPDBModel.ExcelFailedFile' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.ExcelFailedFile'. The relationship 'OOPDBModel.FK__Map_BpCon__Creat__544ED427' was not loaded because the type 'OOPDBModel.Map_BpContactDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDetails'. The relationship 'OOPDBModel.FK__Map_BpCon__Modif__5542F860' was not loaded because the type 'OOPDBModel.Map_BpContactDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDetails'. The relationship 'OOPDBModel.FK__MAP_Deale__Creat__57F3B12B' was not loaded because the type 'OOPDBModel.MAP_Dealer_Distributor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Dealer_Distributor'. The relationship 'OOPDBModel.FK__MAP_Deale__Modif__59DBF99D' was not loaded because the type 'OOPDBModel.MAP_Dealer_Distributor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Dealer_Distributor'. The relationship 'OOPDBModel.FK__MAP_Distr__Creat__50528F63' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__MAP_Distr__Modif__523AD7D5' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__MAP_Inter__Creat__47B3F318' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__MAP_Inter__Modif__499C3B8A' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__Map_Menu___Creat__0D324BC8' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__Map_Menu___Modif__0E267001' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__Map_Order__UserI__25F24143' was not loaded because the type 'OOPDBModel.Map_Order_Approval' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Map_Order_Approval'. The relationship 'OOPDBModel.FK__Map_UserR__Creat__3FF2D5BF' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__Map_UserR__Modif__40E6F9F8' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__Map_UserR__UserI__42CF426A' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__010AD557' was not loaded because the type 'OOPDBModel.MRKT_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunch'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__04DB663B' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchProductMap' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchProductMap'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__0B8863CA' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSection' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSection'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__0E64D075' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSectionImage' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSectionImage'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__01FEF990' was not loaded because the type 'OOPDBModel.MRKT_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunch'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__141DA9CB' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSection' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSection'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__1605F23D' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSectionImage' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSectionImage'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__2D1E61BF' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__2FFACE6A' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__32D73B15' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__2E1285F8' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__30EEF2A3' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__33CB5F4E' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_BP_Ar__Creat__47D257FB' was not loaded because the type 'OOPDBModel.MST_BP_Division_AreaCodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Division_AreaCodeMapping'. The relationship 'OOPDBModel.FK__MST_BP_Ar__Modif__49BAA06D' was not loaded because the type 'OOPDBModel.MST_BP_Division_AreaCodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Division_AreaCodeMapping'. The relationship 'OOPDBModel.FK__MST_Desig__Creat__271B6FA6' was not loaded because the type 'OOPDBModel.MST_Designation' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Designation'. The relationship 'OOPDBModel.FK__MST_Desig__Modif__280F93DF' was not loaded because the type 'OOPDBModel.MST_Designation' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Designation'. The relationship 'OOPDBModel.FK__MST_EMP_D__Creat__42A38E8A' was not loaded because the type 'OOPDBModel.MST_EMP_Division_AreacodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_EMP_Division_AreacodeMapping'. The relationship 'OOPDBModel.FK__MST_EMP_D__Modif__457FFB35' was not loaded because the type 'OOPDBModel.MST_EMP_Division_AreacodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_EMP_Division_AreacodeMapping'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__04508AFF' was not loaded because the type 'OOPDBModel.PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__0FC30902' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__10B72D3B' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__11AB5174' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0544AF38' was not loaded because the type 'OOPDBModel.PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK__PROD_Sear__Creat__33414F69' was not loaded because the type 'OOPDBModel.PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SearchTags'. The relationship 'OOPDBModel.FK__PROD_Sear__Modif__343573A2' was not loaded because the type 'OOPDBModel.PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SearchTags'. The relationship 'OOPDBModel.FK__Quota_Are__Creat__4A3B5A08' was not loaded because the type 'OOPDBModel.Quota_AreaMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_AreaMapping'. The relationship 'OOPDBModel.FK__Quota_Are__Modif__4C23A27A' was not loaded because the type 'OOPDBModel.Quota_AreaMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_AreaMapping'. The relationship 'OOPDBModel.FK__Quota_BpE__Creat__51DC7BD0' was not loaded because the type 'OOPDBModel.Quota_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BpExclution'. The relationship 'OOPDBModel.FK__Quota_BpE__Modif__53C4C442' was not loaded because the type 'OOPDBModel.Quota_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BpExclution'. The relationship 'OOPDBModel.FK__Quota_BPM__Creat__5A71C1D1' was not loaded because the type 'OOPDBModel.Quota_BPMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BPMapping'. The relationship 'OOPDBModel.FK__Quota_BPM__Modif__5C5A0A43' was not loaded because the type 'OOPDBModel.Quota_BPMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BPMapping'. The relationship 'OOPDBModel.FK__Quota_Emp__Creat__630707D2' was not loaded because the type 'OOPDBModel.Quota_EmployeeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_EmployeeMapping'. The relationship 'OOPDBModel.FK__Quota_Emp__Modif__64EF5044' was not loaded because the type 'OOPDBModel.Quota_EmployeeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_EmployeeMapping'. The relationship 'OOPDBModel.FK__Quota_Pro__Creat__6AA8299A' was not loaded because the type 'OOPDBModel.Quota_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_ProductMapping'. The relationship 'OOPDBModel.FK__Quota_Pro__Modif__6C90720C' was not loaded because the type 'OOPDBModel.Quota_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_ProductMapping'. The relationship 'OOPDBModel.FK__Quota_Rol__Creat__733D6F9B' was not loaded because the type 'OOPDBModel.Quota_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_RoleMapping'. The relationship 'OOPDBModel.FK__Quota_Rol__Modif__7525B80D' was not loaded because the type 'OOPDBModel.Quota_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_RoleMapping'. The relationship 'OOPDBModel.FK__QuotaHead__Creat__41A61407' was not loaded because the type 'OOPDBModel.QuotaHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.QuotaHeader'. The relationship 'OOPDBModel.FK__QuotaHead__Modif__438E5C79' was not loaded because the type 'OOPDBModel.QuotaHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.QuotaHeader'. The relationship 'OOPDBModel.FK__SC_MultiG__Creat__28449E09' was not loaded because the type 'OOPDBModel.SC_MultiGroupHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.SC_MultiGroupHeader'. The relationship 'OOPDBModel.FK__SC_RoleMa__Creat__4B03CA61' was not loaded because the type 'OOPDBModel.SC_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_RoleMapping'. The relationship 'OOPDBModel.FK__SC_RoleMa__Modif__4BF7EE9A' was not loaded because the type 'OOPDBModel.SC_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_RoleMapping'. The relationship 'OOPDBModel.FK__SET_Quota__Creat__78F648F1' was not loaded because the type 'OOPDBModel.SET_QuotaAllocatedTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_QuotaAllocatedTo'. The relationship 'OOPDBModel.FK__SET_Quota__Modif__7ADE9163' was not loaded because the type 'OOPDBModel.SET_QuotaAllocatedTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_QuotaAllocatedTo'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__04508AFF' was not loaded because the type 'OOPDBModel.BO_PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__3AD6B8E2' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColor'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__5EDF0F2E' was not loaded because the type 'OOPDBModel.BO_PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__0544AF38' was not loaded because the type 'OOPDBModel.BO_PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__3CBF0154' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColor'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__5FD33367' was not loaded because the type 'OOPDBModel.BO_PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK_EventWise_Notification_AUTH_User' was not loaded because the type 'OOPDBModel.EventWise_Notification' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.EventWise_Notification'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__324172E1' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__5A054B78' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__5BED93EA' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK__MST_Color__Creat__31ED387D' was not loaded because the type 'OOPDBModel.MST_Color' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Color'. The relationship 'OOPDBModel.FK__MST_Color__Modif__32E15CB6' was not loaded because the type 'OOPDBModel.MST_Color' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Color'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__17A5B89A' was not loaded because the type 'OOPDBModel.TRAN_UserReleaseNotes' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserReleaseNotes'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0313E4B1' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__040808EA' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0BA92AB2' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0C9D4EEB' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__77A23205' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__7896563E' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__MST_Divis__Creat__0DCF0841' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__MST_Divis__Modif__10AB74EC' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Orde__Revis__09AB0850' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__23C176BC' was not loaded because the type 'OOPDBModel.TRAN_UserNewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserNewLaunch'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__269DE367' was not loaded because the type 'OOPDBModel.TRAN_UserNewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserNewLaunch'. The relationship 'OOPDBModel.FK__REV_Tran___Accep__3AED5E29' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__REV_Tran___Creat__3BE18262' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__TRAN_Temp__Creat__3F747E29' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__Modif__415CC69B' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__37D35C61' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__1E6F845E' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Division'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__2057CCD0' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Division'. The relationship 'OOPDBModel.FK__EG_Docume__Creat__12C1D343' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__EG_Docume__Modif__13B5F77C' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK_UsersID' was not loaded because the type 'OOPDBModel.EG_DocumentUserMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentUserMapping'. The relationship 'OOPDBModel.FK__Map_BpCon__Creat__666D8462' was not loaded because the type 'OOPDBModel.Map_BpContactDivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDivision'. The relationship 'OOPDBModel.FK__Map_BpCon__Modif__6855CCD4' was not loaded because the type 'OOPDBModel.Map_BpContactDivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDivision'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__4EDDB18F' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__4FD1D5C8' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__50C5FA01' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__634568461' was not loaded because the type 'OOPDBModel.MST_Privacy_Details1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details1'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__64398C7F1' was not loaded because the type 'OOPDBModel.MST_Privacy_Details1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details1'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__6621D4F11' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy1'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__6715F92A1' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy1'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__680A1D631' was not loaded because the type 'OOPDBModel.TRAN_Privacy_AgreedPolicy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_AgreedPolicy1'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__6BDAAE471' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response1'. The relationship 'OOPDBModel.FK__TRAN_Priv__UserI__6DC2F6B91' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response1'. The relationship 'OOPDBModel.FK__AUTH_Role__Creat__4C0144E41' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__AUTH_Role__Modif__4CF5691D1' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__4EDDB18F1' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__5205CDAB1' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__52AE42731' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__567ED3571' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__4FD1D5C81' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__52F9F1E41' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__54968AE51' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__5772F7901' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__50C5FA011' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__53EE161D1' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__558AAF1E1' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__595B40021' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__16F0C02C1' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__17E4E4651' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__25132BA31' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__18D9089E1' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__19CD2CD71' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__26FB74151' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__BO_PROD_P__Creat__71B44E851' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Creat__72A872BE1' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Modif__739C96F71' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Modif__7490BB301' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Creat__65C116E71' was not loaded because the type 'OOPDBModel.BO_PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductGallery'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Modif__15FA39EE1' was not loaded because the type 'OOPDBModel.BO_PROD_ProductTax' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductTax'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Modif__67A95F591' was not loaded because the type 'OOPDBModel.BO_PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductGallery'. The relationship 'OOPDBModel.FK__BO_PROD_S__Creat__01EAB64E1' was not loaded because the type 'OOPDBModel.BO_PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_SearchTags'. The relationship 'OOPDBModel.FK__BO_PROD_S__Modif__02DEDA871' was not loaded because the type 'OOPDBModel.BO_PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_SearchTags'. The relationship 'OOPDBModel.FK__CFG_BPCat__Creat__5F1419581' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__CFG_BPCat__Modif__60083D911' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__Discount___Creat__63D8CE751' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__Discount___Modif__65C116E71' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__EG_Docume__Creat__2866FB9F' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__EG_Docume__Creat__295B1FD8' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__EG_Docume__Modif__2A4F4411' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__EG_Docume__Modif__2B43684A' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__Emp_Categ__Creat__50679DFC1' was not loaded because the type 'OOPDBModel.Emp_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Emp_Category'. The relationship 'OOPDBModel.FK__Emp_Categ__Modif__524FE66E1' was not loaded because the type 'OOPDBModel.Emp_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Emp_Category'. The relationship 'OOPDBModel.FK__ExcelFail__Creat__35E8B1EA1' was not loaded because the type 'OOPDBModel.ExcelFailedFile' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.ExcelFailedFile'. The relationship 'OOPDBModel.FK__Map_BpCon__Creat__544ED4271' was not loaded because the type 'OOPDBModel.Map_BpContactDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDetails'. The relationship 'OOPDBModel.FK__Map_BpCon__Creat__666D84621' was not loaded because the type 'OOPDBModel.Map_BpContactDivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDivision'. The relationship 'OOPDBModel.FK__Map_BpCon__Modif__5542F8601' was not loaded because the type 'OOPDBModel.Map_BpContactDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDetails'. The relationship 'OOPDBModel.FK__Map_BpCon__Modif__6855CCD41' was not loaded because the type 'OOPDBModel.Map_BpContactDivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDivision'. The relationship 'OOPDBModel.FK__MAP_Deale__Creat__76DA8D03' was not loaded because the type 'OOPDBModel.MAP_Dealer_Distributor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Dealer_Distributor'. The relationship 'OOPDBModel.FK__MAP_Deale__Modif__78C2D575' was not loaded because the type 'OOPDBModel.MAP_Dealer_Distributor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Dealer_Distributor'. The relationship 'OOPDBModel.FK__MAP_Distr__Creat__50528F631' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__MAP_Distr__Modif__523AD7D51' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__MAP_Inter__Creat__47B3F3181' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__MAP_Inter__Modif__499C3B8A1' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__Map_Menu___Creat__0D324BC81' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__Map_Menu___Modif__0E2670011' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__Map_Order__UserI__25F241431' was not loaded because the type 'OOPDBModel.Map_Order_Approval' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Map_Order_Approval'. The relationship 'OOPDBModel.FK__Map_UserR__Creat__3FF2D5BF1' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__Map_UserR__Modif__40E6F9F81' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__Map_UserR__UserI__42CF426A1' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__010AD5571' was not loaded because the type 'OOPDBModel.MRKT_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunch'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__04DB663B1' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchProductMap' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchProductMap'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__0B8863CA1' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSection' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSection'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__0E64D0751' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSectionImage' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSectionImage'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__01FEF9901' was not loaded because the type 'OOPDBModel.MRKT_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunch'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__141DA9CB1' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSection' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSection'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__1605F23D1' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSectionImage' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSectionImage'. The relationship 'OOPDBModel.FK__MST_Addre__Creat__762267391' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__MST_Addre__Modif__77168B721' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__2D1E61BF1' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__2FFACE6A1' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__32D73B151' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__2E1285F81' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__30EEF2A31' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__33CB5F4E1' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_BP_Ar__Creat__47D257FB1' was not loaded because the type 'OOPDBModel.MST_BP_Division_AreaCodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Division_AreaCodeMapping'. The relationship 'OOPDBModel.FK__MST_BP_Ar__Modif__49BAA06D1' was not loaded because the type 'OOPDBModel.MST_BP_Division_AreaCodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Division_AreaCodeMapping'. The relationship 'OOPDBModel.FK__MST_BP_Ba__Creat__094A4A461' was not loaded because the type 'OOPDBModel.MST_BP_Bank' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Bank'. The relationship 'OOPDBModel.FK__MST_BP_Ba__Modif__0A3E6E7F1' was not loaded because the type 'OOPDBModel.MST_BP_Bank' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Bank'. The relationship 'OOPDBModel.FK__MST_BP_Bi__Creat__2B0043CC1' was not loaded because the type 'OOPDBModel.MST_BP_BillShipTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_BP_BillShipTo'. The relationship 'OOPDBModel.FK__MST_BP_Pa__Creat__0F03239C1' was not loaded because the type 'OOPDBModel.MST_BP_PayTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_PayTerms'. The relationship 'OOPDBModel.FK__MST_BP_Pa__Modif__0FF747D51' was not loaded because the type 'OOPDBModel.MST_BP_PayTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_PayTerms'. The relationship 'OOPDBModel.FK__MST_BPGro__Creat__12D3B4801' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__MST_BPGro__Modif__14BBFCF21' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__MST_City__Create__1C5D1EBA1' was not loaded because the type 'OOPDBModel.MST_City' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_City'. The relationship 'OOPDBModel.FK__MST_City__Modifi__00750D231' was not loaded because the type 'OOPDBModel.MST_City' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_City'. The relationship 'OOPDBModel.FK__MST_Color__Creat__31ED387D1' was not loaded because the type 'OOPDBModel.MST_Color' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Color'. The relationship 'OOPDBModel.FK__MST_Color__Modif__32E15CB61' was not loaded because the type 'OOPDBModel.MST_Color' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Color'. The relationship 'OOPDBModel.FK__MST_Conta__Creat__025D55951' was not loaded because the type 'OOPDBModel.MST_Contact' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Contact'. The relationship 'OOPDBModel.FK__MST_Conta__Creat__0539C2401' was not loaded because the type 'OOPDBModel.MST_ContactMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_ContactMapping'. The relationship 'OOPDBModel.FK__MST_Conta__Modif__035179CE1' was not loaded because the type 'OOPDBModel.MST_Contact' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Contact'. The relationship 'OOPDBModel.FK__MST_Count__Creat__062DE6791' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__MST_Count__Creat__090A53241' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__MST_Count__Modif__07220AB21' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__MST_Count__Modif__09FE775D1' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__MST_Curre__Creat__0BE6BFCF1' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__MST_Curre__Modif__0CDAE4081' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__MST_Desig__Creat__271B6FA61' was not loaded because the type 'OOPDBModel.MST_Designation' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Designation'. The relationship 'OOPDBModel.FK__MST_Desig__Modif__280F93DF1' was not loaded because the type 'OOPDBModel.MST_Designation' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Designation'. The relationship 'OOPDBModel.FK__MST_Divis__Creat__0DCF08411' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__MST_Divis__Modif__10AB74EC1' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__MST_EMP_D__Creat__42A38E8A1' was not loaded because the type 'OOPDBModel.MST_EMP_Division_AreacodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_EMP_Division_AreacodeMapping'. The relationship 'OOPDBModel.FK__MST_EMP_D__Modif__457FFB351' was not loaded because the type 'OOPDBModel.MST_EMP_Division_AreacodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_EMP_Division_AreacodeMapping'. The relationship 'OOPDBModel.FK__MST_Emplo__Creat__147C05D01' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Emplo__Modif__15702A091' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Emplo__UserI__16644E421' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Logo__Modifi__2B7F66B91' was not loaded because the type 'OOPDBModel.MST_Logo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_Logo'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__184C96B41' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__1E6F845E1' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Division'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__1FEDB87C1' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__1A34DF261' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__2057CCD01' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Division'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__21D600EE1' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__MST_MAP_L__Modif__332088811' was not loaded because the type 'OOPDBModel.MST_MAP_Logo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_Logo'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__0955373E1' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__100234CD1' was not loaded because the type 'OOPDBModel.MST_Privacy_Details' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__0A495B771' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__10F659061' was not loaded because the type 'OOPDBModel.MST_Privacy_Details' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details'. The relationship 'OOPDBModel.FK__MST_Sales__Creat__19218AB31' was not loaded because the type 'OOPDBModel.MST_SalesPerson' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_SalesPerson'. The relationship 'OOPDBModel.FK__MST_Sales__Modif__1A15AEEC1' was not loaded because the type 'OOPDBModel.MST_SalesPerson' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_SalesPerson'. The relationship 'OOPDBModel.FK__MST_State__Creat__25A691D21' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__MST_State__Modif__269AB60B1' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__MST_UOM__Created__297722B61' was not loaded because the type 'OOPDBModel.MST_UOM' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_UOM'. The relationship 'OOPDBModel.FK__MST_UOM__Modifie__2A6B46EF1' was not loaded because the type 'OOPDBModel.MST_UOM' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_UOM'. The relationship 'OOPDBModel.FK__ORG_Busin__Creat__2B5F6B281' was not loaded because the type 'OOPDBModel.ORG_Business_Entity' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Entity'. The relationship 'OOPDBModel.FK__ORG_Busin__Creat__2E3BD7D31' was not loaded because the type 'OOPDBModel.ORG_Business_Unit' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Unit'. The relationship 'OOPDBModel.FK__ORG_Busin__Modif__2C538F611' was not loaded because the type 'OOPDBModel.ORG_Business_Entity' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Entity'. The relationship 'OOPDBModel.FK__ORG_Busin__Modif__302420451' was not loaded because the type 'OOPDBModel.ORG_Business_Unit' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Unit'. The relationship 'OOPDBModel.FK__PR_PriceL__Creat__36D11DD41' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__PR_PriceL__Modif__37C5420D1' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__PROD_Appl__Creat__3AA1AEB81' was not loaded because the type 'OOPDBModel.PROD_Applicability' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Applicability'. The relationship 'OOPDBModel.FK__PROD_Appl__Modif__3B95D2F11' was not loaded because the type 'OOPDBModel.PROD_Applicability' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Applicability'. The relationship 'OOPDBModel.FK__PROD_Attr__Creat__3E723F9C1' was not loaded because the type 'OOPDBModel.PROD_Attribute' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Attribute'. The relationship 'OOPDBModel.FK__PROD_Attr__Creat__405A880E1' was not loaded because the type 'OOPDBModel.PROD_AttributeSet' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_AttributeSet'. The relationship 'OOPDBModel.FK__PROD_Attr__Modif__3F6663D51' was not loaded because the type 'OOPDBModel.PROD_Attribute' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Attribute'. The relationship 'OOPDBModel.FK__PROD_Attr__Modif__414EAC471' was not loaded because the type 'OOPDBModel.PROD_AttributeSet' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_AttributeSet'. The relationship 'OOPDBModel.FK__PROD_BPPr__Creat__4242D0801' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__PROD_BPPr__Modif__4336F4B91' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__PROD_Bran__Creat__442B18F21' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__PROD_Bran__Modif__451F3D2B1' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__PROD_Cate__Creat__461361641' was not loaded because the type 'OOPDBModel.PROD_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Category'. The relationship 'OOPDBModel.FK__PROD_Cate__Modif__47FBA9D61' was not loaded because the type 'OOPDBModel.PROD_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Category'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__01741E541' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__04508AFF1' was not loaded because the type 'OOPDBModel.PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__0FC309021' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__10B72D3B1' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__11AB51741' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__324172E11' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__3AD6B8E21' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__44CB02C71' was not loaded because the type 'OOPDBModel.PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__5A054B781' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__5EDF0F2E1' was not loaded because the type 'OOPDBModel.PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__65C116E71' was not loaded because the type 'OOPDBModel.PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGallery'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__68A8708A1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__699C94C31' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6A90B8FC1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6B84DD351' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6C79016E1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6D6D25A71' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6E2152BE1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6E6149E01' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6F1576F71' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6F556E191' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70099B301' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__704992521' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70FDBF691' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__004002F91' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__007FFA1B1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__013427321' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__02284B6B1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0268428D1' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__031C6FA41' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__041093DD1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0504B8161' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0544AF381' was not loaded because the type 'OOPDBModel.PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__05F8DC4F1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__15FA39EE1' was not loaded because the type 'OOPDBModel.PROD_ProductTax' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductTax'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__3429BB531' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__3CBF01541' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__46B34B391' was not loaded because the type 'OOPDBModel.PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__5BED93EA1' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__5FD333671' was not loaded because the type 'OOPDBModel.PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__67A95F591' was not loaded because the type 'OOPDBModel.PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGallery'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__750E476F1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__76026BA81' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__76F68FE11' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__77EAB41A1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__78DED8531' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Sear__Creat__33414F691' was not loaded because the type 'OOPDBModel.PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SearchTags'. The relationship 'OOPDBModel.FK__PROD_Sear__Modif__343573A21' was not loaded because the type 'OOPDBModel.PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SearchTags'. The relationship 'OOPDBModel.FK__PROD_Size__Creat__072CF7AA1' was not loaded because the type 'OOPDBModel.PROD_SizeGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SizeGroup'. The relationship 'OOPDBModel.FK__PROD_Size__Modif__08211BE31' was not loaded because the type 'OOPDBModel.PROD_SizeGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SizeGroup'. The relationship 'OOPDBModel.FK__PROD_Styl__Creat__0915401C1' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__PROD_Styl__Modif__0A0964551' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__PROD_SubB__Creat__0AFD888E1' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__PROD_SubB__Modif__0BF1ACC71' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__Quota_Are__Creat__4A3B5A081' was not loaded because the type 'OOPDBModel.Quota_AreaMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_AreaMapping'. The relationship 'OOPDBModel.FK__Quota_Are__Modif__4C23A27A1' was not loaded because the type 'OOPDBModel.Quota_AreaMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_AreaMapping'. The relationship 'OOPDBModel.FK__Quota_BpE__Creat__51DC7BD01' was not loaded because the type 'OOPDBModel.Quota_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BpExclution'. The relationship 'OOPDBModel.FK__Quota_BpE__Modif__53C4C4421' was not loaded because the type 'OOPDBModel.Quota_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BpExclution'. The relationship 'OOPDBModel.FK__Quota_BPM__Creat__5A71C1D11' was not loaded because the type 'OOPDBModel.Quota_BPMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BPMapping'. The relationship 'OOPDBModel.FK__Quota_BPM__Modif__5C5A0A431' was not loaded because the type 'OOPDBModel.Quota_BPMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BPMapping'. The relationship 'OOPDBModel.FK__Quota_Emp__Creat__630707D21' was not loaded because the type 'OOPDBModel.Quota_EmployeeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_EmployeeMapping'. The relationship 'OOPDBModel.FK__Quota_Emp__Modif__64EF50441' was not loaded because the type 'OOPDBModel.Quota_EmployeeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_EmployeeMapping'. The relationship 'OOPDBModel.FK__Quota_Pro__Creat__6AA8299A1' was not loaded because the type 'OOPDBModel.Quota_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_ProductMapping'. The relationship 'OOPDBModel.FK__Quota_Pro__Modif__6C90720C1' was not loaded because the type 'OOPDBModel.Quota_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_ProductMapping'. The relationship 'OOPDBModel.FK__Quota_Rol__Creat__733D6F9B1' was not loaded because the type 'OOPDBModel.Quota_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_RoleMapping'. The relationship 'OOPDBModel.FK__Quota_Rol__Modif__7525B80D1' was not loaded because the type 'OOPDBModel.Quota_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_RoleMapping'. The relationship 'OOPDBModel.FK__QuotaHead__Creat__41A614071' was not loaded because the type 'OOPDBModel.QuotaHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.QuotaHeader'. The relationship 'OOPDBModel.FK__QuotaHead__Modif__438E5C791' was not loaded because the type 'OOPDBModel.QuotaHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.QuotaHeader'. The relationship 'OOPDBModel.FK__REV_Tran___Accep__3AED5E291' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__REV_Tran___Creat__3BE182621' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__SC_BpCate__Creat__0DD9F5391' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_BpCate__Modif__0ECE19721' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_BpExcl__Creat__10B661E41' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpExcl__Modif__11AA861D1' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpIncl__Creat__1486F2C81' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__SC_BpIncl__Modif__157B17011' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__SC_Divisi__Creat__185783AC1' was not loaded because the type 'OOPDBModel.SC_DivisionMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_DivisionMapping'. The relationship 'OOPDBModel.FK__SC_Divisi__Modif__1A3FCC1E1' was not loaded because the type 'OOPDBModel.SC_DivisionMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_DivisionMapping'. The relationship 'OOPDBModel.FK__SC_MultiG__Creat__28449E091' was not loaded because the type 'OOPDBModel.SC_MultiGroupHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.SC_MultiGroupHeader'. The relationship 'OOPDBModel.FK__SC_Policy__Creat__1C2814901' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__SC_Policy__Modif__1D1C38C91' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__SC_ProdAl__Creat__1E105D021' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdAl__Modif__1F04813B1' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdEx__Creat__23C936581' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__Creat__563FA78C1' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_ProdEx__Modif__24BD5A911' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__Modif__5733CBC51' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__1AC9DC031' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__2B6A58201' was not loaded because the type 'OOPDBModel.SC_ProdGroupAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupAlternate'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__302F0D3D1' was not loaded because the type 'OOPDBModel.SC_ProdGroupDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDirectDiscount'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__3C94E422' was not loaded because the type 'OOPDBModel.SC_ProdGroupMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupMapping'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__1E9A6CE71' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__2C5E7C591' was not loaded because the type 'OOPDBModel.SC_ProdGroupAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupAlternate'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__321755AF1' was not loaded because the type 'OOPDBModel.SC_ProdGroupDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDirectDiscount'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__3E7D2C94' was not loaded because the type 'OOPDBModel.SC_ProdGroupMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__461E4E5C1' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__4CCB4BEB1' was not loaded because the type 'OOPDBModel.SC_ProductMappingHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMappingHeader'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__4E7E8A331' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__480696CE1' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__4EB3945D1' was not loaded because the type 'OOPDBModel.SC_ProductMappingHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMappingHeader'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__5066D2A51' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SC_RoleMa__Creat__4B03CA611' was not loaded because the type 'OOPDBModel.SC_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_RoleMapping'. The relationship 'OOPDBModel.FK__SC_RoleMa__Modif__4BF7EE9A1' was not loaded because the type 'OOPDBModel.SC_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_RoleMapping'. The relationship 'OOPDBModel.FK__SC_StateM__Creat__509BDCCF1' was not loaded because the type 'OOPDBModel.SC_StateMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_StateMapping'. The relationship 'OOPDBModel.FK__SC_StateM__Modif__519001081' was not loaded because the type 'OOPDBModel.SC_StateMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_StateMapping'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__11F700E51' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__15C791C9' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__74F0ADE3' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__12EB251E1' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__16BBB602' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__76D8F655' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__UserI__14D36D90' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__UserI__77CD1A8E' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SET_Banne__Creat__02D256E11' was not loaded because the type 'OOPDBModel.SET_Bannerdivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Bannerdivision'. The relationship 'OOPDBModel.FK__SET_Banne__Creat__63CEACD41' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__SET_Banne__Modif__04BA9F531' was not loaded because the type 'OOPDBModel.SET_Bannerdivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Bannerdivision'. The relationship 'OOPDBModel.FK__SET_Banne__Modif__64C2D10D1' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__SET_MenuP__Creat__0D1BA681' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Creat__0E0FCABA' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Modif__10EC3765' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Modif__11E05B9E' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_NewLa__Creat__15BB0E231' was not loaded because the type 'OOPDBModel.SET_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunch'. The relationship 'OOPDBModel.FK__SET_NewLa__Creat__198B9F071' was not loaded because the type 'OOPDBModel.SET_NewLaunchDetail' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunchDetail'. The relationship 'OOPDBModel.FK__SET_NewLa__Modif__16AF325C1' was not loaded because the type 'OOPDBModel.SET_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunch'. The relationship 'OOPDBModel.FK__SET_NewLa__Modif__1B73E7791' was not loaded because the type 'OOPDBModel.SET_NewLaunchDetail' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunchDetail'. The relationship 'OOPDBModel.FK__SET_Proje__Creat__3C2B9B25' was not loaded because the type 'OOPDBModel.SET_Projects' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Projects'. The relationship 'OOPDBModel.FK__SET_Proje__Modif__3E13E397' was not loaded because the type 'OOPDBModel.SET_Projects' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Projects'. The relationship 'OOPDBModel.FK__SET_Quota__Creat__78F648F11' was not loaded because the type 'OOPDBModel.SET_QuotaAllocatedTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_QuotaAllocatedTo'. The relationship 'OOPDBModel.FK__SET_Quota__Modif__7ADE91631' was not loaded because the type 'OOPDBModel.SET_QuotaAllocatedTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_QuotaAllocatedTo'. The relationship 'OOPDBModel.FK__SET_Relea__Creat__41E4747B' was not loaded because the type 'OOPDBModel.SET_ReleaseNote' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_ReleaseNote'. The relationship 'OOPDBModel.FK__SET_Relea__Modif__43CCBCED' was not loaded because the type 'OOPDBModel.SET_ReleaseNote' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_ReleaseNote'. The relationship 'OOPDBModel.FK__SET_Sales__Creat__1DE63FD01' was not loaded because the type 'OOPDBModel.SET_SalesPersonLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_SalesPersonLink'. The relationship 'OOPDBModel.FK__SET_Sales__Modif__1FCE88421' was not loaded because the type 'OOPDBModel.SET_SalesPersonLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_SalesPersonLink'. The relationship 'OOPDBModel.FK__SET_UserC__UserI__795DFB401' was not loaded because the type 'OOPDBModel.SET_UserCustomSettings' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.SET_UserCustomSettings'. The relationship 'OOPDBModel.FK__TRAN_Adva__Creat__1078CCC7' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__TRAN_Adva__Modif__12611539' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__TRAN_BuyN__UserI__70FDBF691' was not loaded because the type 'OOPDBModel.TRAN_BuyNow' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_BuyNow'. The relationship 'OOPDBModel.FK__TRAN_Cart__Creat__172368511' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_Cart__UserI__041B80D51' was not loaded because the type 'OOPDBModel.TRAN_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Cart'. The relationship 'OOPDBModel.FK__TRAN_Cart__UserI__0ABD916C1' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_Comp__UserI__07EC11B91' was not loaded because the type 'OOPDBModel.TRAN_Compare' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Compare'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0313E4B11' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__040808EA1' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0BA92AB21' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0C9D4EEB1' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__77A232051' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__7896563E1' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__Tran_Orde__Creat__30A4D9E01' was not loaded because the type 'OOPDBModel.Tran_OrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderEmployeeDetails'. The relationship 'OOPDBModel.FK__Tran_Orde__Creat__3EE9A2ED' was not loaded because the type 'OOPDBModel.Tran_OrderitemProposedQty' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderitemProposedQty'. The relationship 'OOPDBModel.FK__TRAN_Orde__Creat__54B686761' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__Modif__569ECEE81' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__Revis__09AB08501' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__TRAN_Orde__UserI__4D1564AE1' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__29C206D01' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__2F7AE0261' was not loaded because the type 'OOPDBModel.TRAN_Privacy_AgreedPolicy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_AgreedPolicy'. The relationship 'OOPDBModel.FK__TRAN_Priv__UserI__2BAA4F421' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response'. The relationship 'OOPDBModel.FK__Tran_Prod__Creat__004264FE' was not loaded because the type 'OOPDBModel.Tran_Productcataloguedownloadqueue' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Productcataloguedownloadqueue'. The relationship 'OOPDBModel.FK__TRAN_Rece__UserI__08E035F21' was not loaded because the type 'OOPDBModel.TRAN_RecentSearchTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_RecentSearchTerms'. The relationship 'OOPDBModel.FK__TRAN_Rece__UserI__24B26D991' was not loaded because the type 'OOPDBModel.TRAN_RecentViews' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_RecentViews'. The relationship 'OOPDBModel.FK__TRAN_Sale__Creat__09D45A2B1' was not loaded because the type 'OOPDBModel.TRAN_Sales_Promotion' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Sales_Promotion'. The relationship 'OOPDBModel.FK__TRAN_Sale__Modif__0AC87E641' was not loaded because the type 'OOPDBModel.TRAN_Sales_Promotion' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Sales_Promotion'. The relationship 'OOPDBModel.FK__Tran_Temp__Creat__328D22521' was not loaded because the type 'OOPDBModel.Tran_TempOrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_TempOrderEmployeeDetails'. The relationship 'OOPDBModel.FK__TRAN_Temp__Creat__442424AD' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__Modif__451848E6' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__1451E89E1' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__15460CD71' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__163A31101' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__47009158' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Creat__54B686761' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Modif__569ECEE81' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__UserI__4D1564AE1' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__00ED3BCB' was not loaded because the type 'OOPDBModel.TRAN_UserNewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserNewLaunch'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__0DB23A0C' was not loaded because the type 'OOPDBModel.TRAN_UserReleaseNotes' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserReleaseNotes'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__63BC0040' was not loaded because the type 'OOPDBModel.TRAN_UserReleaseNotes' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserReleaseNotes'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__7FF91792' was not loaded because the type 'OOPDBModel.TRAN_UserNewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserNewLaunch'. The relationship 'OOPDBModel.FK__TRAN_Wish__UserI__257C74A01' was not loaded because the type 'OOPDBModel.TRAN_WishList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_WishList'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__04508AFF1' was not loaded because the type 'OOPDBModel.BO_PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__324172E11' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__3AD6B8E21' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColor'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__5A054B781' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__5EDF0F2E1' was not loaded because the type 'OOPDBModel.BO_PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__0544AF381' was not loaded because the type 'OOPDBModel.BO_PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__3CBF01541' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColor'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__5BED93EA1' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__5FD333671' was not loaded because the type 'OOPDBModel.BO_PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK_EventWise_Notification_AUTH_User1' was not loaded because the type 'OOPDBModel.EventWise_Notification' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.EventWise_Notification'. The relationship 'OOPDBModel.FK_Tran_Loginlink_AUTH_User1' was not loaded because the type 'OOPDBModel.Tran_Loginlink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Loginlink'. The relationship 'OOPDBModel.FK_UsersID1' was not loaded because the type 'OOPDBModel.EG_DocumentUserMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentUserMapping'. The relationship 'OOPDBModel.FK__AUTH_User__RoleI__5C37ACAD' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__BO_PROD_P__Divis__7F79F4A5' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__CFG_MenuP__RoleI__61F08603' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__EG_Docume__Heade__17868860' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__Discount_B__BPID__66B53B20' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__Map_Order___BPID__28CEADEE' was not loaded because the type 'OOPDBModel.Map_Order_Approval' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Map_Order_Approval'. The relationship 'OOPDBModel.FK__MST_MAP_BP__BPID__1B29035F' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_BP__BPID__23BE4960' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__SC_BpExclu__BPID__1392CE8F' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpInclu__BPID__17635F73' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__TRAN_Advan__BPID__13553972' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__TRAN_TempO__BPID__38C7809A' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrder__BPID__4E0988E7' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK_Tran_Loginlink_MST_BusinessPartner' was not loaded because the type 'OOPDBModel.Tran_Loginlink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Loginlink'. The relationship 'OOPDBModel.FK__SET_MenuP__MenuI__6D430875' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__MenuI__6E372CAE' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__Map_Menu___MenuI__05912A00' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__REV_Tran___FairI__4D2DA0A3' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__5C8F146D' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__5D8338A6' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__5E775CDF' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__6153C98A' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__6247EDC3' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__633C11FC' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Cart__TaxGr__6CE315C2' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__NotifyCon__RoleI__774DF7A1' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__Order_Rea__Divis__4B504529' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__Order_Rea__Divis__4D388D9B' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK_ProductRating_Product' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK_ProductRating_ProductColor' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__ProdG__3D9E16F4' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__ProdS__3E923B2D' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__PROD_Prod__Divis__7D91AC33' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__PROD_Prod__ProdS__4277DAAA' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__SC_ProdAl__ProdS__20ECC9AD' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdEx__ProdS__288DEB75' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__ProdS__5B045CA9' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_Produc__ProdS__49EEDF40' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__ProdS__6A90B8FC' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SET_Banne__ProdS__61E66462' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__PROD_Prod__ProdS__011F1899' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Cart__ProdS__0E8E2250' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__ProdS__011F1899' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK__PR_Price__Curren__33008CF0' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__PR_Price__PriceL__34E8D562' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__REV_TRAN___Produ__5AF01967' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__REV_TRAN___ProdG__5CD861D9' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__REV_TRAN___PSize__5FB4CE84' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__REV_TRAN___ProdS__5DCC8612' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__REV_TRAN___Order__5813ACBC' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__REV_TRAN___Distr__371CCD45' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__REV_TRAN___Order__59FBF52E' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__REV_TRAN___Revis__2E878744' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__REV_Tran___Order__4382A42A' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__REV_Tran___Order__4476C863' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__REV_Tran___Order__3FB21346' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__REV_Tran___Polic__456AEC9C' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__REV_Tran___Order__428E7FF1' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__REV_Tran___Order__6A325CF7' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__REV_Tran___Revis__419A5BB8' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__4E00329D' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__4A2FA1B9' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__4D0C0E64' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__4B23C5F2' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__REV_Tran___Distr__4EF456D6' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__493B7D80' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__REV_Tran___Order__7A68C4C0' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__CFG_BPCat__BPCat__5E1FF51F' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__MST_BPGro__BPCat__11DF9047' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__SC_BpCate__BPCat__0CE5D100' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_ProdGr__BPCat__18E19391' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__BO_PR_Pri__BPCat__241F076A' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__MAP_Inter__BPCat__45CBAAA6' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__Map_Order__BPCat__2C9F3ED2' was not loaded because the type 'OOPDBModel.Map_Order_Approval' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Map_Order_Approval'. The relationship 'OOPDBModel.FK__TRAN_Orde__BPCat__53B90BF3' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__SET_Busin__Addre__6E2C3FB6' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__SET_BU_Nu__Divis__55FFB06A' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_BU_Nu__Divis__56F3D4A3' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_BU_Nu__Divis__57E7F8DC' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_BU_Nu__Divis__583CFE97' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_Numbe__Divis__71FCD09A' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_Users__RoleI__01F34141' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__SET_Users__RoleI__02E7657A' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__SET_Users__RoleI__03DB89B3' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__SET_Users__RoleI__04CFADEC' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__SE_VisitB__Mappi__17AFDA3B' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__TRAN_Attc__Order__7E794CC6' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Cart__Divis__12356159' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Cart__CartI__11413D20' was not loaded because the type 'OOPDBModel.TRAN_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Cart'. The relationship 'OOPDBModel.FK_TRAN_CartItemDiscount_TRAN_CartItem' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_MyCa__Produ__5EDF0F2E' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_MyCa__ProdG__5FD33367' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__TRAN_MyCa__ProdS__60C757A0' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.Fk_Cart_id' was not loaded because the type 'OOPDBModel.TRAN_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Cart'. The relationship 'OOPDBModel.FK_TRAN_CartItem_TRAN_MyCart' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_MyCa__Divis__48A5B54C' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK_TRAN_DivisionPaymentSummary_TransactionID' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Invo__Divis__7B72C2E9' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Offl__OOP_O__4F950C02' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Temp__Offli__36DF3828' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Orde__Divis__253C7D7E' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__48D1692C' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__Tran_Orde__Order__2FB0B5A7' was not loaded because the type 'OOPDBModel.Tran_OrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderEmployeeDetails'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__5B638405' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__REV_Tran___Divis__3EBDEF0D' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__TRAN_Orde__Produ__66D536B1' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Orde__ProdG__68BD7F23' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__TRAN_Orde__PSize__6B99EBCE' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__TRAN_Orde__ProdS__69B1A35C' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__64ECEE3F' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__Distr__5BC4420F' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__7BC6FD4D' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__435886F8' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Paym__Trans__06E47595' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Paym__Trans__07D899CE' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Paym__Trans__0F79BB96' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Paym__Trans__106DDFCF' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Prin__Order__33F7DE85' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__Tran_Sche__Order__57E7F8DC' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__Tran_Sche__Distr__654DAC49' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__Tran_Sche__Order__4BADD5D7' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__Tran_Sche__Order__7EA369F8' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__Tran_Self__Count__37DBE754' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__Tran_Self__Distr__35F39EE2' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__Tran_Self__State__36E7C31B' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__Tran_Self__Emplo__499219E9' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__TRAN_Slid__State__2BC02932' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__TRAN_Slid__BPPro__26074FDC' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__TRAN_Slid__Brand__26FB7415' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__TRAN_Slid__Produ__76B698BF' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Slid__ProdS__28E3BC87' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__TRAN_Slid__Divis__27EF984E' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Temp__BillT__385D6C46' was not loaded because the type 'OOPDBModel.MST_BP_BillShipTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_BP_BillShipTo'. The relationship 'OOPDBModel.FK__TRAN_Temp__ShipT__3951907F' was not loaded because the type 'OOPDBModel.MST_BP_BillShipTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_BP_BillShipTo'. The relationship 'OOPDBModel.FK__TRAN_Temp__Divis__3398B729' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Temp__Order__32A492F0' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__Distr__737E3214' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__TRAN_Temp__Divis__5F773967' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Temp__Produ__5E83152E' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Temp__Produ__653012BD' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__TRAN_Temp__ProdG__615F81D9' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__TRAN_Temp__PSize__643BEE84' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__TRAN_Temp__ProdS__6253A612' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__TRAN_Temp__Order__5C9ACCBC' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Divis__253C7D7E' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Order__5B638405' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__Tran_Temp__Order__3198FE19' was not loaded because the type 'OOPDBModel.Tran_TempOrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_TempOrderEmployeeDetails'. The relationship 'OOPDBModel.FK_Tran_TempOrderDivisionJSON_TRAN_TempOrder' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__Tran_Temp__Order__34812313' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Produ__66D536B1' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__ProdG__68BD7F23' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__PSize__6B99EBCE' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__ProdS__69B1A35C' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Order__64ECEE3F' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__Distr__5F94D2F3' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK_Tran_TempOrderItemJSON_TRAN_TempOrder' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__Tran_Temp__Distr__5DAC8A81' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__TRAN_Temp__CartI__766C7FFC' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__Distr__636563D7' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. System.Data.Entity.Core.MetadataException: Schema specified is not valid. Errors: The relationship 'OOPDBModel.FK__AUTH_Role__Creat__4C0144E4' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__AUTH_Role__Modif__4CF5691D' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__52AE4273' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__567ED357' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__54968AE5' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__5772F790' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__558AAF1E' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__595B4002' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__CFG_BPCat__Creat__5F141958' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__CFG_BPCat__Modif__60083D91' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__Discount___Creat__63D8CE75' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__Discount___Modif__65C116E7' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__MST_Addre__Creat__76226739' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__MST_Addre__Modif__77168B72' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__MST_BP_Ba__Creat__094A4A46' was not loaded because the type 'OOPDBModel.MST_BP_Bank' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Bank'. The relationship 'OOPDBModel.FK__MST_BP_Ba__Modif__0A3E6E7F' was not loaded because the type 'OOPDBModel.MST_BP_Bank' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Bank'. The relationship 'OOPDBModel.FK__MST_BP_Bi__Creat__2B0043CC' was not loaded because the type 'OOPDBModel.MST_BP_BillShipTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_BP_BillShipTo'. The relationship 'OOPDBModel.FK__MST_BP_Pa__Creat__0F03239C' was not loaded because the type 'OOPDBModel.MST_BP_PayTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_PayTerms'. The relationship 'OOPDBModel.FK__MST_BP_Pa__Modif__0FF747D5' was not loaded because the type 'OOPDBModel.MST_BP_PayTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_PayTerms'. The relationship 'OOPDBModel.FK__MST_BPGro__Creat__12D3B480' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__MST_BPGro__Modif__14BBFCF2' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__MST_City__Create__1C5D1EBA' was not loaded because the type 'OOPDBModel.MST_City' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_City'. The relationship 'OOPDBModel.FK__MST_City__Modifi__00750D23' was not loaded because the type 'OOPDBModel.MST_City' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_City'. The relationship 'OOPDBModel.FK__MST_Conta__Creat__025D5595' was not loaded because the type 'OOPDBModel.MST_Contact' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Contact'. The relationship 'OOPDBModel.FK__MST_Conta__Creat__0539C240' was not loaded because the type 'OOPDBModel.MST_ContactMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_ContactMapping'. The relationship 'OOPDBModel.FK__MST_Conta__Modif__035179CE' was not loaded because the type 'OOPDBModel.MST_Contact' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Contact'. The relationship 'OOPDBModel.FK__MST_Count__Creat__062DE679' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__MST_Count__Creat__090A5324' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__MST_Count__Modif__07220AB2' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__MST_Count__Modif__09FE775D' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__MST_Curre__Creat__0BE6BFCF' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__MST_Curre__Modif__0CDAE408' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__MST_Emplo__Creat__147C05D0' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Emplo__Modif__15702A09' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Emplo__UserI__16644E42' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Logo__Modifi__2B7F66B9' was not loaded because the type 'OOPDBModel.MST_Logo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_Logo'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__184C96B4' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__1FEDB87C' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__1A34DF26' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__21D600EE' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__MST_MAP_L__Modif__33208881' was not loaded because the type 'OOPDBModel.MST_MAP_Logo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_Logo'. The relationship 'OOPDBModel.FK__MST_State__Creat__25A691D2' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__MST_State__Modif__269AB60B' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__MST_UOM__Created__297722B6' was not loaded because the type 'OOPDBModel.MST_UOM' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_UOM'. The relationship 'OOPDBModel.FK__MST_UOM__Modifie__2A6B46EF' was not loaded because the type 'OOPDBModel.MST_UOM' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_UOM'. The relationship 'OOPDBModel.FK__ORG_Busin__Creat__2B5F6B28' was not loaded because the type 'OOPDBModel.ORG_Business_Entity' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Entity'. The relationship 'OOPDBModel.FK__ORG_Busin__Creat__2E3BD7D3' was not loaded because the type 'OOPDBModel.ORG_Business_Unit' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Unit'. The relationship 'OOPDBModel.FK__ORG_Busin__Modif__2C538F61' was not loaded because the type 'OOPDBModel.ORG_Business_Entity' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Entity'. The relationship 'OOPDBModel.FK__ORG_Busin__Modif__30242045' was not loaded because the type 'OOPDBModel.ORG_Business_Unit' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Unit'. The relationship 'OOPDBModel.FK__PR_PriceL__Creat__36D11DD4' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__PR_PriceL__Modif__37C5420D' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__PROD_Appl__Creat__3AA1AEB8' was not loaded because the type 'OOPDBModel.PROD_Applicability' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Applicability'. The relationship 'OOPDBModel.FK__PROD_Appl__Modif__3B95D2F1' was not loaded because the type 'OOPDBModel.PROD_Applicability' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Applicability'. The relationship 'OOPDBModel.FK__PROD_Attr__Creat__3E723F9C' was not loaded because the type 'OOPDBModel.PROD_Attribute' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Attribute'. The relationship 'OOPDBModel.FK__PROD_Attr__Creat__405A880E' was not loaded because the type 'OOPDBModel.PROD_AttributeSet' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_AttributeSet'. The relationship 'OOPDBModel.FK__PROD_Attr__Modif__3F6663D5' was not loaded because the type 'OOPDBModel.PROD_Attribute' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Attribute'. The relationship 'OOPDBModel.FK__PROD_Attr__Modif__414EAC47' was not loaded because the type 'OOPDBModel.PROD_AttributeSet' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_AttributeSet'. The relationship 'OOPDBModel.FK__PROD_BPPr__Creat__4242D080' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__PROD_BPPr__Modif__4336F4B9' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__PROD_Bran__Creat__442B18F2' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__PROD_Bran__Modif__451F3D2B' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__PROD_Cate__Creat__46136164' was not loaded because the type 'OOPDBModel.PROD_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Category'. The relationship 'OOPDBModel.FK__PROD_Cate__Modif__47FBA9D6' was not loaded because the type 'OOPDBModel.PROD_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Category'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__01741E54' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__5EDF0F2E' was not loaded because the type 'OOPDBModel.PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__65C116E7' was not loaded because the type 'OOPDBModel.PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGallery'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__68A8708A' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__699C94C3' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6A90B8FC' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6B84DD35' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6C79016E' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6D6D25A7' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6E2152BE' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6E6149E0' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6F1576F7' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6F556E19' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70099B30' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70499252' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70FDBF69' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__004002F9' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__007FFA1B' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__01342732' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__02284B6B' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0268428D' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__031C6FA4' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__041093DD' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0504B816' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__05F8DC4F' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__15FA39EE' was not loaded because the type 'OOPDBModel.PROD_ProductTax' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductTax'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__5FD33367' was not loaded because the type 'OOPDBModel.PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__67A95F59' was not loaded because the type 'OOPDBModel.PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGallery'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__750E476F' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__76026BA8' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__76F68FE1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__77EAB41A' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__78DED853' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Size__Creat__072CF7AA' was not loaded because the type 'OOPDBModel.PROD_SizeGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SizeGroup'. The relationship 'OOPDBModel.FK__PROD_Size__Modif__08211BE3' was not loaded because the type 'OOPDBModel.PROD_SizeGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SizeGroup'. The relationship 'OOPDBModel.FK__PROD_Styl__Creat__0915401C' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__PROD_Styl__Modif__0A096455' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__SC_BpCate__Creat__0DD9F539' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_BpCate__Modif__0ECE1972' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_BpExcl__Creat__10B661E4' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpExcl__Modif__11AA861D' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpIncl__Creat__1486F2C8' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__SC_BpIncl__Modif__157B1701' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__SC_Policy__Creat__1C281490' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__SC_Policy__Modif__1D1C38C9' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__SC_ProdAl__Creat__1E105D02' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdAl__Modif__1F04813B' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdEx__Creat__23C93658' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__Creat__563FA78C' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_ProdEx__Modif__24BD5A91' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__Modif__5733CBC5' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__1AC9DC03' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__2B6A5820' was not loaded because the type 'OOPDBModel.SC_ProdGroupAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupAlternate'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__302F0D3D' was not loaded because the type 'OOPDBModel.SC_ProdGroupDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDirectDiscount'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__1E9A6CE7' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__2C5E7C59' was not loaded because the type 'OOPDBModel.SC_ProdGroupAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupAlternate'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__321755AF' was not loaded because the type 'OOPDBModel.SC_ProdGroupDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDirectDiscount'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__461E4E5C' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__4CCB4BEB' was not loaded because the type 'OOPDBModel.SC_ProductMappingHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMappingHeader'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__4E7E8A33' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__480696CE' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__4EB3945D' was not loaded because the type 'OOPDBModel.SC_ProductMappingHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMappingHeader'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__5066D2A5' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SC_StateM__Creat__509BDCCF' was not loaded because the type 'OOPDBModel.SC_StateMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_StateMapping'. The relationship 'OOPDBModel.FK__SC_StateM__Modif__51900108' was not loaded because the type 'OOPDBModel.SC_StateMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_StateMapping'. The relationship 'OOPDBModel.FK__SET_Banne__Creat__02D256E1' was not loaded because the type 'OOPDBModel.SET_Bannerdivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Bannerdivision'. The relationship 'OOPDBModel.FK__SET_Banne__Creat__63CEACD4' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__SET_Banne__Modif__04BA9F53' was not loaded because the type 'OOPDBModel.SET_Bannerdivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Bannerdivision'. The relationship 'OOPDBModel.FK__SET_Banne__Modif__64C2D10D' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__SET_MenuP__Creat__69727791' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Creat__6A669BCA' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Modif__6F2B50E7' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Modif__701F7520' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_NewLa__Creat__15BB0E23' was not loaded because the type 'OOPDBModel.SET_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunch'. The relationship 'OOPDBModel.FK__SET_NewLa__Creat__198B9F07' was not loaded because the type 'OOPDBModel.SET_NewLaunchDetail' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunchDetail'. The relationship 'OOPDBModel.FK__SET_NewLa__Modif__16AF325C' was not loaded because the type 'OOPDBModel.SET_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunch'. The relationship 'OOPDBModel.FK__SET_NewLa__Modif__1B73E779' was not loaded because the type 'OOPDBModel.SET_NewLaunchDetail' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunchDetail'. The relationship 'OOPDBModel.FK__SET_Sales__Creat__1DE63FD0' was not loaded because the type 'OOPDBModel.SET_SalesPersonLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_SalesPersonLink'. The relationship 'OOPDBModel.FK__SET_Sales__Modif__1FCE8842' was not loaded because the type 'OOPDBModel.SET_SalesPersonLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_SalesPersonLink'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__324172E1' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__5A054B78' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__3429BB53' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__5BED93EA' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__MST_Sales__Creat__19218AB3' was not loaded because the type 'OOPDBModel.MST_SalesPerson' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_SalesPerson'. The relationship 'OOPDBModel.FK__MST_Sales__Modif__1A15AEEC' was not loaded because the type 'OOPDBModel.MST_SalesPerson' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_SalesPerson'. The relationship 'OOPDBModel.FK__SET_Proje__Creat__5E169ED5' was not loaded because the type 'OOPDBModel.SET_Projects' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Projects'. The relationship 'OOPDBModel.FK__SET_Proje__Modif__5FFEE747' was not loaded because the type 'OOPDBModel.SET_Projects' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Projects'. The relationship 'OOPDBModel.FK__SET_Relea__Creat__63CF782B' was not loaded because the type 'OOPDBModel.SET_ReleaseNote' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_ReleaseNote'. The relationship 'OOPDBModel.FK__SET_Relea__Modif__65B7C09D' was not loaded because the type 'OOPDBModel.SET_ReleaseNote' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_ReleaseNote'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__0955373E' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__100234CD' was not loaded because the type 'OOPDBModel.MST_Privacy_Details' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__0A495B77' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__10F65906' was not loaded because the type 'OOPDBModel.MST_Privacy_Details' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details'. The relationship 'OOPDBModel.FK__TRAN_BuyN__UserI__70FDBF69' was not loaded because the type 'OOPDBModel.TRAN_BuyNow' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_BuyNow'. The relationship 'OOPDBModel.FK__TRAN_Cart__Creat__17236851' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_Cart__UserI__041B80D5' was not loaded because the type 'OOPDBModel.TRAN_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Cart'. The relationship 'OOPDBModel.FK__TRAN_Cart__UserI__0ABD916C' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_Comp__UserI__07EC11B9' was not loaded because the type 'OOPDBModel.TRAN_Compare' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Compare'. The relationship 'OOPDBModel.FK__Tran_Orde__Creat__30A4D9E0' was not loaded because the type 'OOPDBModel.Tran_OrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderEmployeeDetails'. The relationship 'OOPDBModel.FK__TRAN_Orde__Creat__54B68676' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__Modif__569ECEE8' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__UserI__4D1564AE' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__29C206D0' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__2F7AE026' was not loaded because the type 'OOPDBModel.TRAN_Privacy_AgreedPolicy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_AgreedPolicy'. The relationship 'OOPDBModel.FK__TRAN_Priv__UserI__2BAA4F42' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response'. The relationship 'OOPDBModel.FK__TRAN_Rece__UserI__08E035F2' was not loaded because the type 'OOPDBModel.TRAN_RecentSearchTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_RecentSearchTerms'. The relationship 'OOPDBModel.FK__TRAN_Rece__UserI__24B26D99' was not loaded because the type 'OOPDBModel.TRAN_RecentViews' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_RecentViews'. The relationship 'OOPDBModel.FK__TRAN_Sale__Creat__09D45A2B' was not loaded because the type 'OOPDBModel.TRAN_Sales_Promotion' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Sales_Promotion'. The relationship 'OOPDBModel.FK__TRAN_Sale__Modif__0AC87E64' was not loaded because the type 'OOPDBModel.TRAN_Sales_Promotion' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Sales_Promotion'. The relationship 'OOPDBModel.FK__Tran_Temp__Creat__328D2252' was not loaded because the type 'OOPDBModel.Tran_TempOrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_TempOrderEmployeeDetails'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__1451E89E' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__15460CD7' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__163A3110' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Creat__54B68676' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Modif__569ECEE8' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__UserI__4D1564AE' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_Wish__UserI__257C74A0' was not loaded because the type 'OOPDBModel.TRAN_WishList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_WishList'. The relationship 'OOPDBModel.FK__SET_UserC__UserI__795DFB40' was not loaded because the type 'OOPDBModel.SET_UserCustomSettings' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.SET_UserCustomSettings'. The relationship 'OOPDBModel.FK__PROD_SubB__Creat__0AFD888E' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__PROD_SubB__Modif__0BF1ACC7' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__Tran_Prod__Creat__3E5EC7B1' was not loaded because the type 'OOPDBModel.Tran_Productcataloguedownloadqueue' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Productcataloguedownloadqueue'. The relationship 'OOPDBModel.FK__TRAN_Adva__Creat__6855017D' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__TRAN_Adva__Modif__6A3D49EF' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__5D8338A6' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__5F6B8118' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__UserI__5B9AF034' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__1FDB0BE8' was not loaded because the type 'OOPDBModel.SC_ProdGroupMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupMapping'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__21C3545A' was not loaded because the type 'OOPDBModel.SC_ProdGroupMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupMapping'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__11F700E5' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__12EB251E' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__Tran_Orde__Creat__0F3A8FCB' was not loaded because the type 'OOPDBModel.Tran_OrderitemProposedQty' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderitemProposedQty'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__3AD6B8E2' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__44CB02C7' was not loaded because the type 'OOPDBModel.PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__3CBF0154' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__46B34B39' was not loaded because the type 'OOPDBModel.PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK_Tran_Loginlink_AUTH_User' was not loaded because the type 'OOPDBModel.Tran_Loginlink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Loginlink'. The relationship 'OOPDBModel.FK__SC_Divisi__Creat__185783AC' was not loaded because the type 'OOPDBModel.SC_DivisionMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_DivisionMapping'. The relationship 'OOPDBModel.FK__SC_Divisi__Modif__1A3FCC1E' was not loaded because the type 'OOPDBModel.SC_DivisionMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_DivisionMapping'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__63456846' was not loaded because the type 'OOPDBModel.MST_Privacy_Details1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details1'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__64398C7F' was not loaded because the type 'OOPDBModel.MST_Privacy_Details1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details1'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__6621D4F1' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy1'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__6715F92A' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy1'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__680A1D63' was not loaded because the type 'OOPDBModel.TRAN_Privacy_AgreedPolicy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_AgreedPolicy1'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__6BDAAE47' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response1'. The relationship 'OOPDBModel.FK__TRAN_Priv__UserI__6DC2F6B9' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response1'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__5205CDAB' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__52F9F1E4' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__53EE161D' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__16F0C02C' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__17E4E465' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__25132BA3' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__18D9089E' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__19CD2CD7' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__26FB7415' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__BO_PROD_P__Creat__71B44E85' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Creat__72A872BE' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Modif__739C96F7' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Modif__7490BB30' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Creat__65C116E7' was not loaded because the type 'OOPDBModel.BO_PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductGallery'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Modif__15FA39EE' was not loaded because the type 'OOPDBModel.BO_PROD_ProductTax' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductTax'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Modif__67A95F59' was not loaded because the type 'OOPDBModel.BO_PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductGallery'. The relationship 'OOPDBModel.FK__BO_PROD_S__Creat__01EAB64E' was not loaded because the type 'OOPDBModel.BO_PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_SearchTags'. The relationship 'OOPDBModel.FK__BO_PROD_S__Modif__02DEDA87' was not loaded because the type 'OOPDBModel.BO_PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_SearchTags'. The relationship 'OOPDBModel.FK__Emp_Categ__Creat__50679DFC' was not loaded because the type 'OOPDBModel.Emp_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Emp_Category'. The relationship 'OOPDBModel.FK__Emp_Categ__Modif__524FE66E' was not loaded because the type 'OOPDBModel.Emp_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Emp_Category'. The relationship 'OOPDBModel.FK__ExcelFail__Creat__35E8B1EA' was not loaded because the type 'OOPDBModel.ExcelFailedFile' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.ExcelFailedFile'. The relationship 'OOPDBModel.FK__Map_BpCon__Creat__544ED427' was not loaded because the type 'OOPDBModel.Map_BpContactDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDetails'. The relationship 'OOPDBModel.FK__Map_BpCon__Modif__5542F860' was not loaded because the type 'OOPDBModel.Map_BpContactDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDetails'. The relationship 'OOPDBModel.FK__MAP_Deale__Creat__57F3B12B' was not loaded because the type 'OOPDBModel.MAP_Dealer_Distributor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Dealer_Distributor'. The relationship 'OOPDBModel.FK__MAP_Deale__Modif__59DBF99D' was not loaded because the type 'OOPDBModel.MAP_Dealer_Distributor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Dealer_Distributor'. The relationship 'OOPDBModel.FK__MAP_Distr__Creat__50528F63' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__MAP_Distr__Modif__523AD7D5' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__MAP_Inter__Creat__47B3F318' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__MAP_Inter__Modif__499C3B8A' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__Map_Menu___Creat__0D324BC8' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__Map_Menu___Modif__0E267001' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__Map_Order__UserI__25F24143' was not loaded because the type 'OOPDBModel.Map_Order_Approval' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Map_Order_Approval'. The relationship 'OOPDBModel.FK__Map_UserR__Creat__3FF2D5BF' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__Map_UserR__Modif__40E6F9F8' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__Map_UserR__UserI__42CF426A' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__010AD557' was not loaded because the type 'OOPDBModel.MRKT_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunch'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__04DB663B' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchProductMap' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchProductMap'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__0B8863CA' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSection' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSection'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__0E64D075' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSectionImage' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSectionImage'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__01FEF990' was not loaded because the type 'OOPDBModel.MRKT_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunch'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__141DA9CB' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSection' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSection'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__1605F23D' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSectionImage' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSectionImage'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__2D1E61BF' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__2FFACE6A' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__32D73B15' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__2E1285F8' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__30EEF2A3' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__33CB5F4E' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_BP_Ar__Creat__47D257FB' was not loaded because the type 'OOPDBModel.MST_BP_Division_AreaCodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Division_AreaCodeMapping'. The relationship 'OOPDBModel.FK__MST_BP_Ar__Modif__49BAA06D' was not loaded because the type 'OOPDBModel.MST_BP_Division_AreaCodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Division_AreaCodeMapping'. The relationship 'OOPDBModel.FK__MST_Desig__Creat__271B6FA6' was not loaded because the type 'OOPDBModel.MST_Designation' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Designation'. The relationship 'OOPDBModel.FK__MST_Desig__Modif__280F93DF' was not loaded because the type 'OOPDBModel.MST_Designation' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Designation'. The relationship 'OOPDBModel.FK__MST_EMP_D__Creat__42A38E8A' was not loaded because the type 'OOPDBModel.MST_EMP_Division_AreacodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_EMP_Division_AreacodeMapping'. The relationship 'OOPDBModel.FK__MST_EMP_D__Modif__457FFB35' was not loaded because the type 'OOPDBModel.MST_EMP_Division_AreacodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_EMP_Division_AreacodeMapping'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__04508AFF' was not loaded because the type 'OOPDBModel.PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__0FC30902' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__10B72D3B' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__11AB5174' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0544AF38' was not loaded because the type 'OOPDBModel.PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK__PROD_Sear__Creat__33414F69' was not loaded because the type 'OOPDBModel.PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SearchTags'. The relationship 'OOPDBModel.FK__PROD_Sear__Modif__343573A2' was not loaded because the type 'OOPDBModel.PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SearchTags'. The relationship 'OOPDBModel.FK__Quota_Are__Creat__4A3B5A08' was not loaded because the type 'OOPDBModel.Quota_AreaMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_AreaMapping'. The relationship 'OOPDBModel.FK__Quota_Are__Modif__4C23A27A' was not loaded because the type 'OOPDBModel.Quota_AreaMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_AreaMapping'. The relationship 'OOPDBModel.FK__Quota_BpE__Creat__51DC7BD0' was not loaded because the type 'OOPDBModel.Quota_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BpExclution'. The relationship 'OOPDBModel.FK__Quota_BpE__Modif__53C4C442' was not loaded because the type 'OOPDBModel.Quota_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BpExclution'. The relationship 'OOPDBModel.FK__Quota_BPM__Creat__5A71C1D1' was not loaded because the type 'OOPDBModel.Quota_BPMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BPMapping'. The relationship 'OOPDBModel.FK__Quota_BPM__Modif__5C5A0A43' was not loaded because the type 'OOPDBModel.Quota_BPMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BPMapping'. The relationship 'OOPDBModel.FK__Quota_Emp__Creat__630707D2' was not loaded because the type 'OOPDBModel.Quota_EmployeeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_EmployeeMapping'. The relationship 'OOPDBModel.FK__Quota_Emp__Modif__64EF5044' was not loaded because the type 'OOPDBModel.Quota_EmployeeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_EmployeeMapping'. The relationship 'OOPDBModel.FK__Quota_Pro__Creat__6AA8299A' was not loaded because the type 'OOPDBModel.Quota_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_ProductMapping'. The relationship 'OOPDBModel.FK__Quota_Pro__Modif__6C90720C' was not loaded because the type 'OOPDBModel.Quota_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_ProductMapping'. The relationship 'OOPDBModel.FK__Quota_Rol__Creat__733D6F9B' was not loaded because the type 'OOPDBModel.Quota_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_RoleMapping'. The relationship 'OOPDBModel.FK__Quota_Rol__Modif__7525B80D' was not loaded because the type 'OOPDBModel.Quota_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_RoleMapping'. The relationship 'OOPDBModel.FK__QuotaHead__Creat__41A61407' was not loaded because the type 'OOPDBModel.QuotaHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.QuotaHeader'. The relationship 'OOPDBModel.FK__QuotaHead__Modif__438E5C79' was not loaded because the type 'OOPDBModel.QuotaHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.QuotaHeader'. The relationship 'OOPDBModel.FK__SC_MultiG__Creat__28449E09' was not loaded because the type 'OOPDBModel.SC_MultiGroupHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.SC_MultiGroupHeader'. The relationship 'OOPDBModel.FK__SC_RoleMa__Creat__4B03CA61' was not loaded because the type 'OOPDBModel.SC_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_RoleMapping'. The relationship 'OOPDBModel.FK__SC_RoleMa__Modif__4BF7EE9A' was not loaded because the type 'OOPDBModel.SC_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_RoleMapping'. The relationship 'OOPDBModel.FK__SET_Quota__Creat__78F648F1' was not loaded because the type 'OOPDBModel.SET_QuotaAllocatedTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_QuotaAllocatedTo'. The relationship 'OOPDBModel.FK__SET_Quota__Modif__7ADE9163' was not loaded because the type 'OOPDBModel.SET_QuotaAllocatedTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_QuotaAllocatedTo'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__04508AFF' was not loaded because the type 'OOPDBModel.BO_PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__3AD6B8E2' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColor'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__5EDF0F2E' was not loaded because the type 'OOPDBModel.BO_PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__0544AF38' was not loaded because the type 'OOPDBModel.BO_PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__3CBF0154' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColor'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__5FD33367' was not loaded because the type 'OOPDBModel.BO_PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK_EventWise_Notification_AUTH_User' was not loaded because the type 'OOPDBModel.EventWise_Notification' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.EventWise_Notification'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__324172E1' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__5A054B78' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__5BED93EA' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK__MST_Color__Creat__31ED387D' was not loaded because the type 'OOPDBModel.MST_Color' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Color'. The relationship 'OOPDBModel.FK__MST_Color__Modif__32E15CB6' was not loaded because the type 'OOPDBModel.MST_Color' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Color'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__17A5B89A' was not loaded because the type 'OOPDBModel.TRAN_UserReleaseNotes' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserReleaseNotes'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0313E4B1' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__040808EA' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0BA92AB2' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0C9D4EEB' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__77A23205' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__7896563E' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__MST_Divis__Creat__0DCF0841' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__MST_Divis__Modif__10AB74EC' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Orde__Revis__09AB0850' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__23C176BC' was not loaded because the type 'OOPDBModel.TRAN_UserNewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserNewLaunch'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__269DE367' was not loaded because the type 'OOPDBModel.TRAN_UserNewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserNewLaunch'. The relationship 'OOPDBModel.FK__REV_Tran___Accep__3AED5E29' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__REV_Tran___Creat__3BE18262' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__TRAN_Temp__Creat__3F747E29' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__Modif__415CC69B' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__37D35C61' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__1E6F845E' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Division'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__2057CCD0' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Division'. The relationship 'OOPDBModel.FK__EG_Docume__Creat__12C1D343' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__EG_Docume__Modif__13B5F77C' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK_UsersID' was not loaded because the type 'OOPDBModel.EG_DocumentUserMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentUserMapping'. The relationship 'OOPDBModel.FK__Map_BpCon__Creat__666D8462' was not loaded because the type 'OOPDBModel.Map_BpContactDivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDivision'. The relationship 'OOPDBModel.FK__Map_BpCon__Modif__6855CCD4' was not loaded because the type 'OOPDBModel.Map_BpContactDivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDivision'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__4EDDB18F' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__4FD1D5C8' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__50C5FA01' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__634568461' was not loaded because the type 'OOPDBModel.MST_Privacy_Details1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details1'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__64398C7F1' was not loaded because the type 'OOPDBModel.MST_Privacy_Details1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details1'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__6621D4F11' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy1'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__6715F92A1' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy1'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__680A1D631' was not loaded because the type 'OOPDBModel.TRAN_Privacy_AgreedPolicy1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_AgreedPolicy1'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__6BDAAE471' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response1'. The relationship 'OOPDBModel.FK__TRAN_Priv__UserI__6DC2F6B91' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response1' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response1'. The relationship 'OOPDBModel.FK__AUTH_Role__Creat__4C0144E41' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__AUTH_Role__Modif__4CF5691D1' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__4EDDB18F1' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__5205CDAB1' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__52AE42731' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__Creat__567ED3571' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__4FD1D5C81' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__52F9F1E41' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__54968AE51' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__Modif__5772F7901' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__50C5FA011' was not loaded because the type 'OOPDBModel.AUTH_User_Map_BP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_BP'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__53EE161D1' was not loaded because the type 'OOPDBModel.AUTH_User_Map_OTP' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_OTP'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__558AAF1E1' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Division'. The relationship 'OOPDBModel.FK__AUTH_User__UserI__595B40021' was not loaded because the type 'OOPDBModel.AUTH_User_Map_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.AUTH_User_Map_Role'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__16F0C02C1' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__17E4E4651' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Creat__25132BA31' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__18D9089E1' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__19CD2CD71' was not loaded because the type 'OOPDBModel.BO_PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PR_PriceList'. The relationship 'OOPDBModel.FK__BO_PR_Pri__Modif__26FB74151' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__BO_PROD_P__Creat__71B44E851' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Creat__72A872BE1' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Modif__739C96F71' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_P__Modif__7490BB301' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Creat__65C116E71' was not loaded because the type 'OOPDBModel.BO_PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductGallery'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Modif__15FA39EE1' was not loaded because the type 'OOPDBModel.BO_PROD_ProductTax' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductTax'. The relationship 'OOPDBModel.FK__BO_PROD_Prod__Modif__67A95F591' was not loaded because the type 'OOPDBModel.BO_PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductGallery'. The relationship 'OOPDBModel.FK__BO_PROD_S__Creat__01EAB64E1' was not loaded because the type 'OOPDBModel.BO_PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_SearchTags'. The relationship 'OOPDBModel.FK__BO_PROD_S__Modif__02DEDA871' was not loaded because the type 'OOPDBModel.BO_PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_SearchTags'. The relationship 'OOPDBModel.FK__CFG_BPCat__Creat__5F1419581' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__CFG_BPCat__Modif__60083D911' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__Discount___Creat__63D8CE751' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__Discount___Modif__65C116E71' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__EG_Docume__Creat__2866FB9F' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__EG_Docume__Creat__295B1FD8' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__EG_Docume__Modif__2A4F4411' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__EG_Docume__Modif__2B43684A' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__Emp_Categ__Creat__50679DFC1' was not loaded because the type 'OOPDBModel.Emp_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Emp_Category'. The relationship 'OOPDBModel.FK__Emp_Categ__Modif__524FE66E1' was not loaded because the type 'OOPDBModel.Emp_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Emp_Category'. The relationship 'OOPDBModel.FK__ExcelFail__Creat__35E8B1EA1' was not loaded because the type 'OOPDBModel.ExcelFailedFile' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.ExcelFailedFile'. The relationship 'OOPDBModel.FK__Map_BpCon__Creat__544ED4271' was not loaded because the type 'OOPDBModel.Map_BpContactDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDetails'. The relationship 'OOPDBModel.FK__Map_BpCon__Creat__666D84621' was not loaded because the type 'OOPDBModel.Map_BpContactDivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDivision'. The relationship 'OOPDBModel.FK__Map_BpCon__Modif__5542F8601' was not loaded because the type 'OOPDBModel.Map_BpContactDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDetails'. The relationship 'OOPDBModel.FK__Map_BpCon__Modif__6855CCD41' was not loaded because the type 'OOPDBModel.Map_BpContactDivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_BpContactDivision'. The relationship 'OOPDBModel.FK__MAP_Deale__Creat__76DA8D03' was not loaded because the type 'OOPDBModel.MAP_Dealer_Distributor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Dealer_Distributor'. The relationship 'OOPDBModel.FK__MAP_Deale__Modif__78C2D575' was not loaded because the type 'OOPDBModel.MAP_Dealer_Distributor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Dealer_Distributor'. The relationship 'OOPDBModel.FK__MAP_Distr__Creat__50528F631' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__MAP_Distr__Modif__523AD7D51' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__MAP_Inter__Creat__47B3F3181' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__MAP_Inter__Modif__499C3B8A1' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__Map_Menu___Creat__0D324BC81' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__Map_Menu___Modif__0E2670011' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__Map_Order__UserI__25F241431' was not loaded because the type 'OOPDBModel.Map_Order_Approval' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Map_Order_Approval'. The relationship 'OOPDBModel.FK__Map_UserR__Creat__3FF2D5BF1' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__Map_UserR__Modif__40E6F9F81' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__Map_UserR__UserI__42CF426A1' was not loaded because the type 'OOPDBModel.Map_UserRole_BIDashbord' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Map_UserRole_BIDashbord'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__010AD5571' was not loaded because the type 'OOPDBModel.MRKT_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunch'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__04DB663B1' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchProductMap' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchProductMap'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__0B8863CA1' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSection' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSection'. The relationship 'OOPDBModel.FK__MRKT_NewL__Creat__0E64D0751' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSectionImage' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSectionImage'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__01FEF9901' was not loaded because the type 'OOPDBModel.MRKT_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunch'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__141DA9CB1' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSection' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSection'. The relationship 'OOPDBModel.FK__MRKT_NewL__Modif__1605F23D1' was not loaded because the type 'OOPDBModel.MRKT_NewLaunchSectionImage' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MRKT_NewLaunchSectionImage'. The relationship 'OOPDBModel.FK__MST_Addre__Creat__762267391' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__MST_Addre__Modif__77168B721' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__2D1E61BF1' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__2FFACE6A1' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Creat__32D73B151' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__2E1285F81' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__30EEF2A31' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_Areac__Modif__33CB5F4E1' was not loaded because the type 'OOPDBModel.MST_Areacode' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.MST_Areacode'. The relationship 'OOPDBModel.FK__MST_BP_Ar__Creat__47D257FB1' was not loaded because the type 'OOPDBModel.MST_BP_Division_AreaCodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Division_AreaCodeMapping'. The relationship 'OOPDBModel.FK__MST_BP_Ar__Modif__49BAA06D1' was not loaded because the type 'OOPDBModel.MST_BP_Division_AreaCodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Division_AreaCodeMapping'. The relationship 'OOPDBModel.FK__MST_BP_Ba__Creat__094A4A461' was not loaded because the type 'OOPDBModel.MST_BP_Bank' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Bank'. The relationship 'OOPDBModel.FK__MST_BP_Ba__Modif__0A3E6E7F1' was not loaded because the type 'OOPDBModel.MST_BP_Bank' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_Bank'. The relationship 'OOPDBModel.FK__MST_BP_Bi__Creat__2B0043CC1' was not loaded because the type 'OOPDBModel.MST_BP_BillShipTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_BP_BillShipTo'. The relationship 'OOPDBModel.FK__MST_BP_Pa__Creat__0F03239C1' was not loaded because the type 'OOPDBModel.MST_BP_PayTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_PayTerms'. The relationship 'OOPDBModel.FK__MST_BP_Pa__Modif__0FF747D51' was not loaded because the type 'OOPDBModel.MST_BP_PayTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BP_PayTerms'. The relationship 'OOPDBModel.FK__MST_BPGro__Creat__12D3B4801' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__MST_BPGro__Modif__14BBFCF21' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__MST_City__Create__1C5D1EBA1' was not loaded because the type 'OOPDBModel.MST_City' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_City'. The relationship 'OOPDBModel.FK__MST_City__Modifi__00750D231' was not loaded because the type 'OOPDBModel.MST_City' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_City'. The relationship 'OOPDBModel.FK__MST_Color__Creat__31ED387D1' was not loaded because the type 'OOPDBModel.MST_Color' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Color'. The relationship 'OOPDBModel.FK__MST_Color__Modif__32E15CB61' was not loaded because the type 'OOPDBModel.MST_Color' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Color'. The relationship 'OOPDBModel.FK__MST_Conta__Creat__025D55951' was not loaded because the type 'OOPDBModel.MST_Contact' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Contact'. The relationship 'OOPDBModel.FK__MST_Conta__Creat__0539C2401' was not loaded because the type 'OOPDBModel.MST_ContactMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_ContactMapping'. The relationship 'OOPDBModel.FK__MST_Conta__Modif__035179CE1' was not loaded because the type 'OOPDBModel.MST_Contact' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Contact'. The relationship 'OOPDBModel.FK__MST_Count__Creat__062DE6791' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__MST_Count__Creat__090A53241' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__MST_Count__Modif__07220AB21' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__MST_Count__Modif__09FE775D1' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__MST_Curre__Creat__0BE6BFCF1' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__MST_Curre__Modif__0CDAE4081' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__MST_Desig__Creat__271B6FA61' was not loaded because the type 'OOPDBModel.MST_Designation' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Designation'. The relationship 'OOPDBModel.FK__MST_Desig__Modif__280F93DF1' was not loaded because the type 'OOPDBModel.MST_Designation' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Designation'. The relationship 'OOPDBModel.FK__MST_Divis__Creat__0DCF08411' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__MST_Divis__Modif__10AB74EC1' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__MST_EMP_D__Creat__42A38E8A1' was not loaded because the type 'OOPDBModel.MST_EMP_Division_AreacodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_EMP_Division_AreacodeMapping'. The relationship 'OOPDBModel.FK__MST_EMP_D__Modif__457FFB351' was not loaded because the type 'OOPDBModel.MST_EMP_Division_AreacodeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_EMP_Division_AreacodeMapping'. The relationship 'OOPDBModel.FK__MST_Emplo__Creat__147C05D01' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Emplo__Modif__15702A091' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Emplo__UserI__16644E421' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__MST_Logo__Modifi__2B7F66B91' was not loaded because the type 'OOPDBModel.MST_Logo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_Logo'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__184C96B41' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__1E6F845E1' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Division'. The relationship 'OOPDBModel.FK__MST_MAP_B__Creat__1FEDB87C1' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__1A34DF261' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__2057CCD01' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Division'. The relationship 'OOPDBModel.FK__MST_MAP_B__Modif__21D600EE1' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__MST_MAP_L__Modif__332088811' was not loaded because the type 'OOPDBModel.MST_MAP_Logo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_Logo'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__0955373E1' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy'. The relationship 'OOPDBModel.FK__MST_Priva__Creat__100234CD1' was not loaded because the type 'OOPDBModel.MST_Privacy_Details' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__0A495B771' was not loaded because the type 'OOPDBModel.MST_Privacy_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Policy'. The relationship 'OOPDBModel.FK__MST_Priva__Modif__10F659061' was not loaded because the type 'OOPDBModel.MST_Privacy_Details' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Privacy_Details'. The relationship 'OOPDBModel.FK__MST_Sales__Creat__19218AB31' was not loaded because the type 'OOPDBModel.MST_SalesPerson' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_SalesPerson'. The relationship 'OOPDBModel.FK__MST_Sales__Modif__1A15AEEC1' was not loaded because the type 'OOPDBModel.MST_SalesPerson' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_SalesPerson'. The relationship 'OOPDBModel.FK__MST_State__Creat__25A691D21' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__MST_State__Modif__269AB60B1' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__MST_UOM__Created__297722B61' was not loaded because the type 'OOPDBModel.MST_UOM' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_UOM'. The relationship 'OOPDBModel.FK__MST_UOM__Modifie__2A6B46EF1' was not loaded because the type 'OOPDBModel.MST_UOM' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_UOM'. The relationship 'OOPDBModel.FK__ORG_Busin__Creat__2B5F6B281' was not loaded because the type 'OOPDBModel.ORG_Business_Entity' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Entity'. The relationship 'OOPDBModel.FK__ORG_Busin__Creat__2E3BD7D31' was not loaded because the type 'OOPDBModel.ORG_Business_Unit' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Unit'. The relationship 'OOPDBModel.FK__ORG_Busin__Modif__2C538F611' was not loaded because the type 'OOPDBModel.ORG_Business_Entity' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Entity'. The relationship 'OOPDBModel.FK__ORG_Busin__Modif__302420451' was not loaded because the type 'OOPDBModel.ORG_Business_Unit' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.ORG_Business_Unit'. The relationship 'OOPDBModel.FK__PR_PriceL__Creat__36D11DD41' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__PR_PriceL__Modif__37C5420D1' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__PROD_Appl__Creat__3AA1AEB81' was not loaded because the type 'OOPDBModel.PROD_Applicability' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Applicability'. The relationship 'OOPDBModel.FK__PROD_Appl__Modif__3B95D2F11' was not loaded because the type 'OOPDBModel.PROD_Applicability' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Applicability'. The relationship 'OOPDBModel.FK__PROD_Attr__Creat__3E723F9C1' was not loaded because the type 'OOPDBModel.PROD_Attribute' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Attribute'. The relationship 'OOPDBModel.FK__PROD_Attr__Creat__405A880E1' was not loaded because the type 'OOPDBModel.PROD_AttributeSet' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_AttributeSet'. The relationship 'OOPDBModel.FK__PROD_Attr__Modif__3F6663D51' was not loaded because the type 'OOPDBModel.PROD_Attribute' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Attribute'. The relationship 'OOPDBModel.FK__PROD_Attr__Modif__414EAC471' was not loaded because the type 'OOPDBModel.PROD_AttributeSet' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_AttributeSet'. The relationship 'OOPDBModel.FK__PROD_BPPr__Creat__4242D0801' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__PROD_BPPr__Modif__4336F4B91' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__PROD_Bran__Creat__442B18F21' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__PROD_Bran__Modif__451F3D2B1' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__PROD_Cate__Creat__461361641' was not loaded because the type 'OOPDBModel.PROD_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Category'. The relationship 'OOPDBModel.FK__PROD_Cate__Modif__47FBA9D61' was not loaded because the type 'OOPDBModel.PROD_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Category'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__01741E541' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__04508AFF1' was not loaded because the type 'OOPDBModel.PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__0FC309021' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__10B72D3B1' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__Prod_Prod__Creat__11AB51741' was not loaded because the type 'OOPDBModel.Prod_ProductchangeLog' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.Prod_ProductchangeLog'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__324172E11' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__3AD6B8E21' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__44CB02C71' was not loaded because the type 'OOPDBModel.PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__5A054B781' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__5EDF0F2E1' was not loaded because the type 'OOPDBModel.PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__65C116E71' was not loaded because the type 'OOPDBModel.PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGallery'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__68A8708A1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__699C94C31' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6A90B8FC1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6B84DD351' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6C79016E1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6D6D25A71' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6E2152BE1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6E6149E01' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6F1576F71' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__6F556E191' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70099B301' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__704992521' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Creat__70FDBF691' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__004002F91' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__007FFA1B1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__013427321' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__02284B6B1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0268428D1' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__031C6FA41' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__041093DD1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0504B8161' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__0544AF381' was not loaded because the type 'OOPDBModel.PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__05F8DC4F1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__15FA39EE1' was not loaded because the type 'OOPDBModel.PROD_ProductTax' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductTax'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__3429BB531' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__3CBF01541' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__46B34B391' was not loaded because the type 'OOPDBModel.PROD_ProductColorMaster' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColorMaster'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__5BED93EA1' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__5FD333671' was not loaded because the type 'OOPDBModel.PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__67A95F591' was not loaded because the type 'OOPDBModel.PROD_ProductGallery' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGallery'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__750E476F1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__76026BA81' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__76F68FE11' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__77EAB41A1' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__Modif__78DED8531' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Sear__Creat__33414F691' was not loaded because the type 'OOPDBModel.PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SearchTags'. The relationship 'OOPDBModel.FK__PROD_Sear__Modif__343573A21' was not loaded because the type 'OOPDBModel.PROD_SearchTags' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SearchTags'. The relationship 'OOPDBModel.FK__PROD_Size__Creat__072CF7AA1' was not loaded because the type 'OOPDBModel.PROD_SizeGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SizeGroup'. The relationship 'OOPDBModel.FK__PROD_Size__Modif__08211BE31' was not loaded because the type 'OOPDBModel.PROD_SizeGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SizeGroup'. The relationship 'OOPDBModel.FK__PROD_Styl__Creat__0915401C1' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__PROD_Styl__Modif__0A0964551' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__PROD_SubB__Creat__0AFD888E1' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__PROD_SubB__Modif__0BF1ACC71' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__Quota_Are__Creat__4A3B5A081' was not loaded because the type 'OOPDBModel.Quota_AreaMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_AreaMapping'. The relationship 'OOPDBModel.FK__Quota_Are__Modif__4C23A27A1' was not loaded because the type 'OOPDBModel.Quota_AreaMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_AreaMapping'. The relationship 'OOPDBModel.FK__Quota_BpE__Creat__51DC7BD01' was not loaded because the type 'OOPDBModel.Quota_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BpExclution'. The relationship 'OOPDBModel.FK__Quota_BpE__Modif__53C4C4421' was not loaded because the type 'OOPDBModel.Quota_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BpExclution'. The relationship 'OOPDBModel.FK__Quota_BPM__Creat__5A71C1D11' was not loaded because the type 'OOPDBModel.Quota_BPMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BPMapping'. The relationship 'OOPDBModel.FK__Quota_BPM__Modif__5C5A0A431' was not loaded because the type 'OOPDBModel.Quota_BPMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_BPMapping'. The relationship 'OOPDBModel.FK__Quota_Emp__Creat__630707D21' was not loaded because the type 'OOPDBModel.Quota_EmployeeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_EmployeeMapping'. The relationship 'OOPDBModel.FK__Quota_Emp__Modif__64EF50441' was not loaded because the type 'OOPDBModel.Quota_EmployeeMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_EmployeeMapping'. The relationship 'OOPDBModel.FK__Quota_Pro__Creat__6AA8299A1' was not loaded because the type 'OOPDBModel.Quota_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_ProductMapping'. The relationship 'OOPDBModel.FK__Quota_Pro__Modif__6C90720C1' was not loaded because the type 'OOPDBModel.Quota_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_ProductMapping'. The relationship 'OOPDBModel.FK__Quota_Rol__Creat__733D6F9B1' was not loaded because the type 'OOPDBModel.Quota_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_RoleMapping'. The relationship 'OOPDBModel.FK__Quota_Rol__Modif__7525B80D1' was not loaded because the type 'OOPDBModel.Quota_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Quota_RoleMapping'. The relationship 'OOPDBModel.FK__QuotaHead__Creat__41A614071' was not loaded because the type 'OOPDBModel.QuotaHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.QuotaHeader'. The relationship 'OOPDBModel.FK__QuotaHead__Modif__438E5C791' was not loaded because the type 'OOPDBModel.QuotaHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.QuotaHeader'. The relationship 'OOPDBModel.FK__REV_Tran___Accep__3AED5E291' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__REV_Tran___Creat__3BE182621' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__SC_BpCate__Creat__0DD9F5391' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_BpCate__Modif__0ECE19721' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_BpExcl__Creat__10B661E41' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpExcl__Modif__11AA861D1' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpIncl__Creat__1486F2C81' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__SC_BpIncl__Modif__157B17011' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__SC_Divisi__Creat__185783AC1' was not loaded because the type 'OOPDBModel.SC_DivisionMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_DivisionMapping'. The relationship 'OOPDBModel.FK__SC_Divisi__Modif__1A3FCC1E1' was not loaded because the type 'OOPDBModel.SC_DivisionMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_DivisionMapping'. The relationship 'OOPDBModel.FK__SC_MultiG__Creat__28449E091' was not loaded because the type 'OOPDBModel.SC_MultiGroupHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.SC_MultiGroupHeader'. The relationship 'OOPDBModel.FK__SC_Policy__Creat__1C2814901' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__SC_Policy__Modif__1D1C38C91' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__SC_ProdAl__Creat__1E105D021' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdAl__Modif__1F04813B1' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdEx__Creat__23C936581' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__Creat__563FA78C1' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_ProdEx__Modif__24BD5A911' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__Modif__5733CBC51' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__1AC9DC031' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__2B6A58201' was not loaded because the type 'OOPDBModel.SC_ProdGroupAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupAlternate'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__302F0D3D1' was not loaded because the type 'OOPDBModel.SC_ProdGroupDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDirectDiscount'. The relationship 'OOPDBModel.FK__SC_ProdGr__Creat__3C94E422' was not loaded because the type 'OOPDBModel.SC_ProdGroupMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupMapping'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__1E9A6CE71' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__2C5E7C591' was not loaded because the type 'OOPDBModel.SC_ProdGroupAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupAlternate'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__321755AF1' was not loaded because the type 'OOPDBModel.SC_ProdGroupDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDirectDiscount'. The relationship 'OOPDBModel.FK__SC_ProdGr__Modif__3E7D2C94' was not loaded because the type 'OOPDBModel.SC_ProdGroupMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__461E4E5C1' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__4CCB4BEB1' was not loaded because the type 'OOPDBModel.SC_ProductMappingHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMappingHeader'. The relationship 'OOPDBModel.FK__SC_Produc__Creat__4E7E8A331' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__480696CE1' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__4EB3945D1' was not loaded because the type 'OOPDBModel.SC_ProductMappingHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMappingHeader'. The relationship 'OOPDBModel.FK__SC_Produc__Modif__5066D2A51' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SC_RoleMa__Creat__4B03CA611' was not loaded because the type 'OOPDBModel.SC_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_RoleMapping'. The relationship 'OOPDBModel.FK__SC_RoleMa__Modif__4BF7EE9A1' was not loaded because the type 'OOPDBModel.SC_RoleMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_RoleMapping'. The relationship 'OOPDBModel.FK__SC_StateM__Creat__509BDCCF1' was not loaded because the type 'OOPDBModel.SC_StateMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_StateMapping'. The relationship 'OOPDBModel.FK__SC_StateM__Modif__519001081' was not loaded because the type 'OOPDBModel.SC_StateMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_StateMapping'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__11F700E51' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__15C791C9' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__Creat__74F0ADE3' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__12EB251E1' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__16BBB602' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__Modif__76D8F655' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__UserI__14D36D90' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SE_Schedu__UserI__77CD1A8E' was not loaded because the type 'OOPDBModel.SE_ScheduleHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleHeader'. The relationship 'OOPDBModel.FK__SET_Banne__Creat__02D256E11' was not loaded because the type 'OOPDBModel.SET_Bannerdivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Bannerdivision'. The relationship 'OOPDBModel.FK__SET_Banne__Creat__63CEACD41' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__SET_Banne__Modif__04BA9F531' was not loaded because the type 'OOPDBModel.SET_Bannerdivision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Bannerdivision'. The relationship 'OOPDBModel.FK__SET_Banne__Modif__64C2D10D1' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__SET_MenuP__Creat__0D1BA681' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Creat__0E0FCABA' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Modif__10EC3765' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__Modif__11E05B9E' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_NewLa__Creat__15BB0E231' was not loaded because the type 'OOPDBModel.SET_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunch'. The relationship 'OOPDBModel.FK__SET_NewLa__Creat__198B9F071' was not loaded because the type 'OOPDBModel.SET_NewLaunchDetail' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunchDetail'. The relationship 'OOPDBModel.FK__SET_NewLa__Modif__16AF325C1' was not loaded because the type 'OOPDBModel.SET_NewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunch'. The relationship 'OOPDBModel.FK__SET_NewLa__Modif__1B73E7791' was not loaded because the type 'OOPDBModel.SET_NewLaunchDetail' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_NewLaunchDetail'. The relationship 'OOPDBModel.FK__SET_Proje__Creat__3C2B9B25' was not loaded because the type 'OOPDBModel.SET_Projects' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Projects'. The relationship 'OOPDBModel.FK__SET_Proje__Modif__3E13E397' was not loaded because the type 'OOPDBModel.SET_Projects' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_Projects'. The relationship 'OOPDBModel.FK__SET_Quota__Creat__78F648F11' was not loaded because the type 'OOPDBModel.SET_QuotaAllocatedTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_QuotaAllocatedTo'. The relationship 'OOPDBModel.FK__SET_Quota__Modif__7ADE91631' was not loaded because the type 'OOPDBModel.SET_QuotaAllocatedTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_QuotaAllocatedTo'. The relationship 'OOPDBModel.FK__SET_Relea__Creat__41E4747B' was not loaded because the type 'OOPDBModel.SET_ReleaseNote' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_ReleaseNote'. The relationship 'OOPDBModel.FK__SET_Relea__Modif__43CCBCED' was not loaded because the type 'OOPDBModel.SET_ReleaseNote' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_ReleaseNote'. The relationship 'OOPDBModel.FK__SET_Sales__Creat__1DE63FD01' was not loaded because the type 'OOPDBModel.SET_SalesPersonLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_SalesPersonLink'. The relationship 'OOPDBModel.FK__SET_Sales__Modif__1FCE88421' was not loaded because the type 'OOPDBModel.SET_SalesPersonLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_SalesPersonLink'. The relationship 'OOPDBModel.FK__SET_UserC__UserI__795DFB401' was not loaded because the type 'OOPDBModel.SET_UserCustomSettings' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.SET_UserCustomSettings'. The relationship 'OOPDBModel.FK__TRAN_Adva__Creat__1078CCC7' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__TRAN_Adva__Modif__12611539' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__TRAN_BuyN__UserI__70FDBF691' was not loaded because the type 'OOPDBModel.TRAN_BuyNow' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_BuyNow'. The relationship 'OOPDBModel.FK__TRAN_Cart__Creat__172368511' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_Cart__UserI__041B80D51' was not loaded because the type 'OOPDBModel.TRAN_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Cart'. The relationship 'OOPDBModel.FK__TRAN_Cart__UserI__0ABD916C1' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_Comp__UserI__07EC11B91' was not loaded because the type 'OOPDBModel.TRAN_Compare' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Compare'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0313E4B11' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__040808EA1' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0BA92AB21' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__0C9D4EEB1' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__77A232051' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Onli__Creat__7896563E1' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__Tran_Orde__Creat__30A4D9E01' was not loaded because the type 'OOPDBModel.Tran_OrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderEmployeeDetails'. The relationship 'OOPDBModel.FK__Tran_Orde__Creat__3EE9A2ED' was not loaded because the type 'OOPDBModel.Tran_OrderitemProposedQty' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderitemProposedQty'. The relationship 'OOPDBModel.FK__TRAN_Orde__Creat__54B686761' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__Modif__569ECEE81' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__Revis__09AB08501' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__TRAN_Orde__UserI__4D1564AE1' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__29C206D01' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response'. The relationship 'OOPDBModel.FK__TRAN_Priv__Creat__2F7AE0261' was not loaded because the type 'OOPDBModel.TRAN_Privacy_AgreedPolicy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_AgreedPolicy'. The relationship 'OOPDBModel.FK__TRAN_Priv__UserI__2BAA4F421' was not loaded because the type 'OOPDBModel.TRAN_Privacy_Response' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Privacy_Response'. The relationship 'OOPDBModel.FK__Tran_Prod__Creat__004264FE' was not loaded because the type 'OOPDBModel.Tran_Productcataloguedownloadqueue' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Productcataloguedownloadqueue'. The relationship 'OOPDBModel.FK__TRAN_Rece__UserI__08E035F21' was not loaded because the type 'OOPDBModel.TRAN_RecentSearchTerms' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_RecentSearchTerms'. The relationship 'OOPDBModel.FK__TRAN_Rece__UserI__24B26D991' was not loaded because the type 'OOPDBModel.TRAN_RecentViews' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_RecentViews'. The relationship 'OOPDBModel.FK__TRAN_Sale__Creat__09D45A2B1' was not loaded because the type 'OOPDBModel.TRAN_Sales_Promotion' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Sales_Promotion'. The relationship 'OOPDBModel.FK__TRAN_Sale__Modif__0AC87E641' was not loaded because the type 'OOPDBModel.TRAN_Sales_Promotion' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_Sales_Promotion'. The relationship 'OOPDBModel.FK__Tran_Temp__Creat__328D22521' was not loaded because the type 'OOPDBModel.Tran_TempOrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_TempOrderEmployeeDetails'. The relationship 'OOPDBModel.FK__TRAN_Temp__Creat__442424AD' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__Modif__451848E6' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__1451E89E1' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__15460CD71' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__163A31101' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__UserI__47009158' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Creat__54B686761' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Modif__569ECEE81' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__UserI__4D1564AE1' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__00ED3BCB' was not loaded because the type 'OOPDBModel.TRAN_UserNewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserNewLaunch'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__0DB23A0C' was not loaded because the type 'OOPDBModel.TRAN_UserReleaseNotes' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserReleaseNotes'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__63BC0040' was not loaded because the type 'OOPDBModel.TRAN_UserReleaseNotes' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserReleaseNotes'. The relationship 'OOPDBModel.FK__TRAN_User__UserI__7FF91792' was not loaded because the type 'OOPDBModel.TRAN_UserNewLaunch' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_UserNewLaunch'. The relationship 'OOPDBModel.FK__TRAN_Wish__UserI__257C74A01' was not loaded because the type 'OOPDBModel.TRAN_WishList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_WishList'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__04508AFF1' was not loaded because the type 'OOPDBModel.BO_PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__324172E11' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__3AD6B8E21' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColor'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__5A054B781' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Creat__5EDF0F2E1' was not loaded because the type 'OOPDBModel.BO_PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__0544AF381' was not loaded because the type 'OOPDBModel.BO_PROD_ProductSubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductSubBrand'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__3CBF01541' was not loaded because the type 'OOPDBModel.BO_PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductColor'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__5BED93EA1' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__Modif__5FD333671' was not loaded because the type 'OOPDBModel.BO_PROD_ProductAttrVal' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_ProductAttrVal'. The relationship 'OOPDBModel.FK_EventWise_Notification_AUTH_User1' was not loaded because the type 'OOPDBModel.EventWise_Notification' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.EventWise_Notification'. The relationship 'OOPDBModel.FK_Tran_Loginlink_AUTH_User1' was not loaded because the type 'OOPDBModel.Tran_Loginlink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Loginlink'. The relationship 'OOPDBModel.FK_UsersID1' was not loaded because the type 'OOPDBModel.EG_DocumentUserMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentUserMapping'. The relationship 'OOPDBModel.FK__AUTH_User__RoleI__5C37ACAD' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__BO_PROD_P__Divis__7F79F4A5' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__CFG_MenuP__RoleI__61F08603' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__EG_Docume__Heade__17868860' was not loaded because the type 'OOPDBModel.EG_DocumentHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.EG_DocumentHeader'. The relationship 'OOPDBModel.FK__Discount_B__BPID__66B53B20' was not loaded because the type 'OOPDBModel.Discount_BP_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Discount_BP_Division'. The relationship 'OOPDBModel.FK__Map_Order___BPID__28CEADEE' was not loaded because the type 'OOPDBModel.Map_Order_Approval' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Map_Order_Approval'. The relationship 'OOPDBModel.FK__MST_MAP_BP__BPID__1B29035F' was not loaded because the type 'OOPDBModel.MST_MAP_BP_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_Brand'. The relationship 'OOPDBModel.FK__MST_MAP_BP__BPID__23BE4960' was not loaded because the type 'OOPDBModel.MST_MAP_BP_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_MAP_BP_SubBrand'. The relationship 'OOPDBModel.FK__SC_BpExclu__BPID__1392CE8F' was not loaded because the type 'OOPDBModel.SC_BpExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpExclution'. The relationship 'OOPDBModel.FK__SC_BpInclu__BPID__17635F73' was not loaded because the type 'OOPDBModel.SC_BpInclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpInclution'. The relationship 'OOPDBModel.FK__TRAN_Advan__BPID__13553972' was not loaded because the type 'OOPDBModel.TRAN_AdvancePaymentLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_AdvancePaymentLink'. The relationship 'OOPDBModel.FK__TRAN_TempO__BPID__38C7809A' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrder__BPID__4E0988E7' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK_Tran_Loginlink_MST_BusinessPartner' was not loaded because the type 'OOPDBModel.Tran_Loginlink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_Loginlink'. The relationship 'OOPDBModel.FK__SET_MenuP__MenuI__6D430875' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__SET_MenuP__MenuI__6E372CAE' was not loaded because the type 'OOPDBModel.SET_MenuProductLink' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.SET_MenuProductLink'. The relationship 'OOPDBModel.FK__Map_Menu___MenuI__05912A00' was not loaded because the type 'OOPDBModel.Map_Menu_Category' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.Map_Menu_Category'. The relationship 'OOPDBModel.FK__REV_Tran___FairI__4D2DA0A3' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__5C8F146D' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__5D8338A6' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__5E775CDF' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__6153C98A' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__6247EDC3' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__MST_MAP_A__Alter__633C11FC' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Cart__TaxGr__6CE315C2' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__NotifyCon__RoleI__774DF7A1' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__Order_Rea__Divis__4B504529' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__Order_Rea__Divis__4D388D9B' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK_ProductRating_Product' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK_ProductRating_ProductColor' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__PROD_Prod__ProdG__3D9E16F4' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__PROD_Prod__ProdS__3E923B2D' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__PROD_Prod__Divis__7D91AC33' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__PROD_Prod__ProdS__4277DAAA' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__SC_ProdAl__ProdS__20ECC9AD' was not loaded because the type 'OOPDBModel.SC_ProdAlternate' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdAlternate'. The relationship 'OOPDBModel.FK__SC_ProdEx__ProdS__288DEB75' was not loaded because the type 'OOPDBModel.SC_ProdExclution' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclution'. The relationship 'OOPDBModel.FK__SC_ProdEx__ProdS__5B045CA9' was not loaded because the type 'OOPDBModel.SC_ProdExclutionOffer' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdExclutionOffer'. The relationship 'OOPDBModel.FK__SC_Produc__ProdS__49EEDF40' was not loaded because the type 'OOPDBModel.SC_ProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductMapping'. The relationship 'OOPDBModel.FK__SC_Produc__ProdS__6A90B8FC' was not loaded because the type 'OOPDBModel.SC_ProductDirectDiscount' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProductDirectDiscount'. The relationship 'OOPDBModel.FK__SET_Banne__ProdS__61E66462' was not loaded because the type 'OOPDBModel.SET_BannerProductMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SET_BannerProductMapping'. The relationship 'OOPDBModel.FK__PROD_Prod__ProdS__011F1899' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Cart__ProdS__0E8E2250' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK_BO_PROD_Prod__ProdS__011F1899' was not loaded because the type 'OOPDBModel.BO_PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.BO_PROD_Product'. The relationship 'OOPDBModel.FK__PR_Price__Curren__33008CF0' was not loaded because the type 'OOPDBModel.MST_Currency' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Currency'. The relationship 'OOPDBModel.FK__PR_Price__PriceL__34E8D562' was not loaded because the type 'OOPDBModel.PR_PriceList' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PR_PriceList'. The relationship 'OOPDBModel.FK__REV_TRAN___Produ__5AF01967' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__REV_TRAN___ProdG__5CD861D9' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__REV_TRAN___PSize__5FB4CE84' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__REV_TRAN___ProdS__5DCC8612' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__REV_TRAN___Order__5813ACBC' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__REV_TRAN___Distr__371CCD45' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__REV_TRAN___Order__59FBF52E' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__REV_TRAN___Revis__2E878744' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__REV_Tran___Order__4382A42A' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__REV_Tran___Order__4476C863' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__REV_Tran___Order__3FB21346' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__REV_Tran___Polic__456AEC9C' was not loaded because the type 'OOPDBModel.SC_Policy' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_Policy'. The relationship 'OOPDBModel.FK__REV_Tran___Order__428E7FF1' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__REV_Tran___Order__6A325CF7' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__REV_Tran___Revis__419A5BB8' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__4E00329D' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__4A2FA1B9' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__4D0C0E64' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__4B23C5F2' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__REV_Tran___Distr__4EF456D6' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__REV_Tran___Offer__493B7D80' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__REV_Tran___Order__7A68C4C0' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__CFG_BPCat__BPCat__5E1FF51F' was not loaded because the type 'OOPDBModel.CFG_BPCategory' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.CFG_BPCategory'. The relationship 'OOPDBModel.FK__MST_BPGro__BPCat__11DF9047' was not loaded because the type 'OOPDBModel.MST_BPGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_BPGroup'. The relationship 'OOPDBModel.FK__SC_BpCate__BPCat__0CE5D100' was not loaded because the type 'OOPDBModel.SC_BpCategoryMapping' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_BpCategoryMapping'. The relationship 'OOPDBModel.FK__SC_ProdGr__BPCat__18E19391' was not loaded because the type 'OOPDBModel.SC_ProdGroupDiscountSlab' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SC_ProdGroupDiscountSlab'. The relationship 'OOPDBModel.FK__BO_PR_Pri__BPCat__241F076A' was not loaded because the type 'OOPDBModel.BO_PR_Price' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.BO_PR_Price'. The relationship 'OOPDBModel.FK__MAP_Inter__BPCat__45CBAAA6' was not loaded because the type 'OOPDBModel.MAP_InternalUsers_Notifications' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_InternalUsers_Notifications'. The relationship 'OOPDBModel.FK__Map_Order__BPCat__2C9F3ED2' was not loaded because the type 'OOPDBModel.Map_Order_Approval' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Map_Order_Approval'. The relationship 'OOPDBModel.FK__TRAN_Orde__BPCat__53B90BF3' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__SET_Busin__Addre__6E2C3FB6' was not loaded because the type 'OOPDBModel.MST_Address' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Address'. The relationship 'OOPDBModel.FK__SET_BU_Nu__Divis__55FFB06A' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_BU_Nu__Divis__56F3D4A3' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_BU_Nu__Divis__57E7F8DC' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_BU_Nu__Divis__583CFE97' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_Numbe__Divis__71FCD09A' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__SET_Users__RoleI__01F34141' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__SET_Users__RoleI__02E7657A' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__SET_Users__RoleI__03DB89B3' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__SET_Users__RoleI__04CFADEC' was not loaded because the type 'OOPDBModel.AUTH_Role' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.AUTH_Role'. The relationship 'OOPDBModel.FK__SE_VisitB__Mappi__17AFDA3B' was not loaded because the type 'OOPDBModel.SE_ScheduleDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.SE_ScheduleDetails'. The relationship 'OOPDBModel.FK__TRAN_Attc__Order__7E794CC6' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Cart__Divis__12356159' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Cart__CartI__11413D20' was not loaded because the type 'OOPDBModel.TRAN_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Cart'. The relationship 'OOPDBModel.FK_TRAN_CartItemDiscount_TRAN_CartItem' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_MyCa__Produ__5EDF0F2E' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_MyCa__ProdG__5FD33367' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__TRAN_MyCa__ProdS__60C757A0' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.Fk_Cart_id' was not loaded because the type 'OOPDBModel.TRAN_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_Cart'. The relationship 'OOPDBModel.FK_TRAN_CartItem_TRAN_MyCart' was not loaded because the type 'OOPDBModel.TRAN_CartItem' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.TRAN_CartItem'. The relationship 'OOPDBModel.FK__TRAN_MyCa__Divis__48A5B54C' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK_TRAN_DivisionPaymentSummary_TransactionID' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Invo__Divis__7B72C2E9' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Offl__OOP_O__4F950C02' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Temp__Offli__36DF3828' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Orde__Divis__253C7D7E' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__48D1692C' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__Tran_Orde__Order__2FB0B5A7' was not loaded because the type 'OOPDBModel.Tran_OrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_OrderEmployeeDetails'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__5B638405' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__REV_Tran___Divis__3EBDEF0D' was not loaded because the type 'OOPDBModel.REV_Tran_OrderRevision' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.REV_Tran_OrderRevision'. The relationship 'OOPDBModel.FK__TRAN_Orde__Produ__66D536B1' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Orde__ProdG__68BD7F23' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__TRAN_Orde__PSize__6B99EBCE' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__TRAN_Orde__ProdS__69B1A35C' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__64ECEE3F' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Orde__Distr__5BC4420F' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__7BC6FD4D' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__TRAN_Orde__Order__435886F8' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__TRAN_Paym__Trans__06E47595' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Paym__Trans__07D899CE' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Paym__Trans__0F79BB96' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Paym__Trans__106DDFCF' was not loaded because the type 'OOPDBModel.TRAN_OnlinePayment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User6' does not exist on the type 'OOPEntities.OOPModels.TRAN_OnlinePayment'. The relationship 'OOPDBModel.FK__TRAN_Prin__Order__33F7DE85' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__Tran_Sche__Order__57E7F8DC' was not loaded because the type 'OOPDBModel.TRAN_OrderHeader' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderHeader'. The relationship 'OOPDBModel.FK__Tran_Sche__Distr__654DAC49' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__Tran_Sche__Order__4BADD5D7' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__Tran_Sche__Order__7EA369F8' was not loaded because the type 'OOPDBModel.TRAN_OrderAmendment' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.TRAN_OrderAmendment'. The relationship 'OOPDBModel.FK__Tran_Self__Count__37DBE754' was not loaded because the type 'OOPDBModel.MST_Country' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Country'. The relationship 'OOPDBModel.FK__Tran_Self__Distr__35F39EE2' was not loaded because the type 'OOPDBModel.MST_County' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_County'. The relationship 'OOPDBModel.FK__Tran_Self__State__36E7C31B' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__Tran_Self__Emplo__499219E9' was not loaded because the type 'OOPDBModel.MST_Employee' is not available. The following information may be useful in resolving the previous error: The required property 'EmployeeID' does not exist on the type 'OOPEntities.TrackerDB.MST_Employee'.The required property 'PhotoPath' does not exist on the type 'OOPEntities.OOPModels.MST_Employee'. The relationship 'OOPDBModel.FK__TRAN_Slid__State__2BC02932' was not loaded because the type 'OOPDBModel.MST_State' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_State'. The relationship 'OOPDBModel.FK__TRAN_Slid__BPPro__26074FDC' was not loaded because the type 'OOPDBModel.PROD_BPProductName' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_BPProductName'. The relationship 'OOPDBModel.FK__TRAN_Slid__Brand__26FB7415' was not loaded because the type 'OOPDBModel.PROD_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Brand'. The relationship 'OOPDBModel.FK__TRAN_Slid__Produ__76B698BF' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Slid__ProdS__28E3BC87' was not loaded because the type 'OOPDBModel.PROD_SubBrand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_SubBrand'. The relationship 'OOPDBModel.FK__TRAN_Slid__Divis__27EF984E' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Temp__BillT__385D6C46' was not loaded because the type 'OOPDBModel.MST_BP_BillShipTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_BP_BillShipTo'. The relationship 'OOPDBModel.FK__TRAN_Temp__ShipT__3951907F' was not loaded because the type 'OOPDBModel.MST_BP_BillShipTo' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.MST_BP_BillShipTo'. The relationship 'OOPDBModel.FK__TRAN_Temp__Divis__3398B729' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Temp__Order__32A492F0' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__Distr__737E3214' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__TRAN_Temp__Divis__5F773967' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_Temp__Produ__5E83152E' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_Temp__Produ__653012BD' was not loaded because the type 'OOPDBModel.PROD_ProductColor' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductColor'. The relationship 'OOPDBModel.FK__TRAN_Temp__ProdG__615F81D9' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__TRAN_Temp__PSize__643BEE84' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__TRAN_Temp__ProdS__6253A612' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__TRAN_Temp__Order__5C9ACCBC' was not loaded because the type 'OOPDBModel.TRAN_TempOfflineOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOfflineOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Divis__253C7D7E' was not loaded because the type 'OOPDBModel.MST_Division' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MST_Division'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Order__5B638405' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__Tran_Temp__Order__3198FE19' was not loaded because the type 'OOPDBModel.Tran_TempOrderEmployeeDetails' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User1' does not exist on the type 'OOPEntities.OOPModels.Tran_TempOrderEmployeeDetails'. The relationship 'OOPDBModel.FK_Tran_TempOrderDivisionJSON_TRAN_TempOrder' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__Tran_Temp__Order__34812313' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Produ__66D536B1' was not loaded because the type 'OOPDBModel.PROD_Product' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User4' does not exist on the type 'OOPEntities.OOPModels.PROD_Product'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__ProdG__68BD7F23' was not loaded because the type 'OOPDBModel.PROD_ProductGroup' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User26' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductGroup'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__PSize__6B99EBCE' was not loaded because the type 'OOPDBModel.PROD_ProductSize' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_ProductSize'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__ProdS__69B1A35C' was not loaded because the type 'OOPDBModel.PROD_Style' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.PROD_Style'. The relationship 'OOPDBModel.FK__TRAN_TempOrde__Order__64ECEE3F' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__TRAN_Temp__Distr__5F94D2F3' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK_Tran_TempOrderItemJSON_TRAN_TempOrder' was not loaded because the type 'OOPDBModel.TRAN_TempOrder' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_TempOrder'. The relationship 'OOPDBModel.FK__Tran_Temp__Distr__5DAC8A81' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. The relationship 'OOPDBModel.FK__TRAN_Temp__CartI__766C7FFC' was not loaded because the type 'OOPDBModel.TRAN_Temp_Cart' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User3' does not exist on the type 'OOPEntities.OOPModels.TRAN_Temp_Cart'. The relationship 'OOPDBModel.FK__TRAN_Temp__Distr__636563D7' was not loaded because the type 'OOPDBModel.MAP_Distributer_Brand' is not available. The following information may be useful in resolving the previous error: The required property 'AUTH_User2' does not exist on the type 'OOPEntities.OOPModels.MAP_Distributer_Brand'. at System.Data.Entity.Core.Metadata.Edm.ObjectItemCollection.LoadAssemblyFromCache(Assembly assembly, Boolean loadReferencedAssemblies, EdmItemCollection edmItemCollection, Action`1 logLoadMessage) at System.Data.Entity.Core.Metadata.Edm.ObjectItemCollection.ImplicitLoadAssemblyForType(Type type, EdmItemCollection edmItemCollection) at System.Data.Entity.Core.Metadata.Edm.MetadataWorkspace.ImplicitLoadAssemblyForType(Type type, Assembly callingAssembly) at System.Data.Entity.Core.Objects.ObjectContext.<ExecuteStoreQueryReliablyAsync>d__70`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Data.Entity.Utilities.TaskExtensions.CultureAwaiter`1.GetResult() at System.Data.Entity.Internal.LazyAsyncEnumerator`1.<FirstMoveNextAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Data.Entity.Infrastructure.IDbAsyncEnumerableExtensions.<ForEachAsync>d__5`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at OOP.BackgroundTask.Repository.OrderRepository.<GetContactDetails>d__24.MoveNext() in D:\OneDrive - ENES TEXTILE MILLS\Downloads\OOP (1)\OOP\OOP.BackgroundTask\Repository\OrderRepository.cs:line 908 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.GetResult() at OOP.BackgroundTask.Orders.SentOrderNotification.<SentOrderNotificationEmail>d__2.MoveNext() in D:\OneDrive - ENES TEXTILE MILLS\Downloads\OOP (1)\OOP\OOP.BackgroundTask\Orders\SentOrderNotification.cs:line 149 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at OOP.BackgroundJobsManager.Jobs.OrderJobs.<SendOrderConfirmationMail>d__1.MoveNext() in D:\OneDrive - ENES TEXTILE MILLS\Downloads\OOP (1)\OOP\OOP.BackgroundJobsManager\Jobs\OrderJobs.cs:line 24 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
#4294937	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 10:30:02 AM
#4294937	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294936	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 10:30:02 AM
#4294936	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294915	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 10:00:01 AM
#4294915	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294914	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 10:00:01 AM
#4294914	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294894	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 9:30:00 AM
#4294894	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294893	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 9:30:00 AM
#4294893	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294872	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 9:00:14 AM
#4294872	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294871	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 9:00:15 AM
#4294871	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294851	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 8:30:13 AM
#4294851	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294850	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 8:30:14 AM
#4294850	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294829	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 8:00:12 AM
#4294829	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294828	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 8:00:12 AM
#4294828	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294808	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 7:30:11 AM
#4294808	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294807	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 7:30:11 AM
#4294807	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294786	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 7:00:10 AM
#4294786	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294785	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 7:00:10 AM
#4294785	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294765	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 6:30:09 AM
#4294765	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294764	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 6:30:09 AM
#4294764	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294743	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 6:00:08 AM
#4294743	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116
#4294742	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 6:00:08 AM
#4294742	System.Net.Http.HttpRequestException Response status code does not indicate success: 400 (Bad Request). `System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 61`
#4294722	PaymentJobs.PostPayment_RazorPay An exception occurred during performance of the job. More details...	4/9/2026 5:30:07 AM
#4294722	System.Exception Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty System.Exception: Unable to process the Post Payment Data To SAP -TransactionID : 9492 Transaction Details is empty at OOP.BackgroundTask.Payment.PostPaymentDataToSap.PaymentDataPostToSap(Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentDataToSap.cs:line 120 at OOP.BackgroundTask.Payment.PostPaymentToRazorPay.paymentToRazorPay(String RazorPayPaymentID, Int32 TransactionID) in D:\OneDrive - ENES TEXTILE MILLS\D-Drive\Source\Git\OOP\OOP\OOP.BackgroundTask\Payment\PostPaymentToRazorPay.cs:line 116

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.InvalidOperationException

System.Data.Entity.Core.MetadataException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception

System.Net.Http.HttpRequestException

System.Exception