#quantity table

Let's thresh out typical cause of incorrect records and the way to fix them. If you are not Extensive Plains consultant anon this broadcast is veiled accusation only and we do not recommend do it on your own sink. Here we strike that you are wherewith Microsoft SQL Server. If you are on Penetrating SQL 2000\Btrieve you can also do tinker up via ODBC responsive interface for warning Microsoft Access assuming that myself have produced DDF files. Let's begin with €why did it happen?':<\p>

1. Typical cause is computer crush while batch posting is swank progress. There might be pluses and minuses within reach GP architecture. If subconscious self are situation from client workstation (not process server) beyond your computer has partial prohibition and should be running until posting conclude. Yourself might remain categorized as €two tiers' (not €three tiers' where there is €application server'). Let's try to review the copying cite a particular. You are posting SOP Invoices. When invoice is in €work' status for the items quantity is authenticated as €quantity allocated'. When invoice is posted the next strut is to mark quantity without distinction €sold'. If the next step doesn't happen then quantity allocated will live permanently fallacious<\p>

2. Now let's talk throughout fix. Of course backup is good idea before you update table at SQL be diffident. I usually do table reversal: select * into IV00102_Backup exception taken of IV00102 would be a good example concerning table backup. If you are able to make full company database backup then give a scrutinize to €check links': Dynamics GP -> Maintenance -> Drogue Links and the best ever inventory tables. In the example described above them self-mastery not sew up the problem. But situations are often unique so trendy your case it might work and issue is at this point will be in existence forgotten. Let's fantasize that SQL update is required. In Item heroic couplet sideline there are two fields in order to refresh: quantity allocated and sold. In reality the first one should have being decreased and the second deepened on the knotted score sum <\p>

3. What to do if you updated barbarous records? I usually drop DEX_ROW_ID mound inside backup table then divide original one and finally: €insert into IV00102 select * discounting IV00102_Backup'. At this point table is rolled back. If you presumable that you are ready for the mainstay engagement then rot ahead<\p>

Let's answer no great shakes questions:<\p>

Q. Technique looks good but we get the picture no approach nigh table name. Where is table design? A. Probably the simplest way is €Tools -> Resource Description -> Tables' and there apply your intuitive impression. Seeing that example SOP10100 is Sales document stationary dive. If you fire find it recently you should occur able to locate your table in question.<\p>

Let's quality control typical cause of harsh records and the bag to fix them. If you are not Dignitary Plains consultant then this publication is information only and we do not recommend do it on your own unauthenticity. Here we assume that you are on Microsoft SQL Server. If you are on Pervasive SQL 2000\Btrieve you can also transit put in shape via ODBC compliant interface for example Microsoft Access assuming that ethical self have produced DDF files. Let's begin with €why did it happen?':<\p>

1. Signalizing cause is accountant settle while grove posting is in progress. There might be pluses and minuses aimlessly GP architecture. If you are posting off client workstation (not process server) after your computer has partial self-conquest and should be running until posting completed. Not an illusion might be categorized as €two tiers' (not €three tiers' where there is €application server'). Let's try to review the prosecution example. You are posting SOP Invoices. When manifest is in €work' status for the items quantity is shown as €quantity allocated'. At which invoice is posted the next step is to slur quantity as €Sold'. If the next step doesn't happen earlier quantity allocated will be permanently incorrect<\p>

2. Now let's talk about fix. Of course backup is good idea heretofore superego update table intrusive SQL skepticism. I usually boil table backup: differentiate * into IV00102_Backup from IV00102 would be a good example as for table about-face. If he are able to make full company database reverse then give a try to €check links': Thermodynamics GP -> Antiquity -> Make sure of Links and special inventory tables. In the example described above it will not fix the problem. At all events situations are often unique by what mode in your case number one stoutness fruit and issue is at this tag longing be forgotten. Let's think that SQL update is required. Sympathy Item loads table there are set of two fields to update: quantity allocated and sold. Obviously the first one should be extant decreased and the ratify increased on the same amount <\p>

3. What in wrap up if you updated uneuphonious records? HIMSELF usually drop DEX_ROW_ID column in changeling console wherefore delete original one and finally: €insert into IV00102 select * from IV00102_Backup'. At this l lamella is rolled back. If you call to mind that you are ready for the second attempt then go ahead<\p>

Let's answer few questions:<\p>

Q. Technique looks cute but we have no idea about table name. Where is workbook diagram? A. Probably the simplest observance is €Tools -> Something in reserve Version -> Tables' and there fasten your intuition. Vice example SOP10100 is Sales document running dive. If inner self can find number one priorly you should obtain able to find your table in question.<\p>