当前位置：文档之家 › 04_detaillectout

04_detaillectout

  • 格式：doc
  • 大小：88.00 KB
  • 文档页数：5

Chapter 4Carbon and the Molecular Diversity of LifeLecture OutlineOverview: Carbon—The Backbone of Biological Molecules∙Although cells are 70–95% water, the rest consists of mostly carbon-based compounds.∙Carbon enters the biosphere when photosyntheti c organisms use the sun’s energy to transform CO2 into organic molecules, which are transferred to primary consumers.∙Carbon accounts for the diversity of biological molecules, which has made possible the wide variety of living things.∙Proteins, DNA, carbohydrates, and other molecules that distinguish living matter from inorganic material are all composed of carbon atoms bonded to each other and to atoms of other elements.o These other elements commonly include hydrogen (H), oxygen (O), nitrogen (N), sulfur (S), and phosphorus (P).Concept 4.1 Organic chemistry is the study of carbon compounds.∙Organic chemistry focuses on organic compounds containing carbon.o Organic compounds can range from simple molecules, such as CH4, to complex molecules such as proteins, which may have molecular masses greater than 100,000daltons.o Most organic compounds contain hydrogen atoms.∙The overall percentages of the major elements of life (C, H, O, N, S, and P) are quite uniform from one organism to another.∙Because of carbon’s versatility, these few elements can be combined to build an inexhaustible variety of organic molecules.∙Variations in organic molecules can distinguish even individuals of a single species.∙The science of organic chemistry began with attempts to purify and improve the yield of products obtained from organisms.o Initially, chemists learned to synthesize simple compounds in the laboratory but had no success with more complex compounds.∙The Swedish chemist Jons Jacob Berzelius was the first to make a distinction between organic compounds that seemed to arise in only living organisms and inorganic compounds that were found in the nonliving world.∙Early organic chemists proposed vitalism, the belief that physical and chemical laws do not apply to living things.o Support for vitalism waned as organic chemists learned to synthesize complex organic compounds in the laboratory.o In the early 1800s, the German chemist Friedrich Wöhler and his studentssynthesized urea from totally inorganic materials.∙In 1953, Stanley Miller at the University of Chicago set up a laboratory simulation of possible chemical conditions on the primitive Earth and demonstrated the spontaneous synthesis oforganic compounds.o The mixture of gases Miller created probably did not accurately represent the atmosphere of the primitive Earth.o However, similar experiments using more accurate atmospheric conditions also led to the formation of organic compounds.o Spontaneous synthesis of organic compounds may have been an early stage in the origin of life on Earth.∙Organic chemists finally rejected vitalism and embraced mechanism, the belief that the same physical and chemical laws govern all natural phenomena, including the processes of life.∙Organic chemistry was redefined as the study of carbon compounds, regardless of their origin.o Organisms produce the majority of organic compounds.o The laws of chemistry apply to both inorganic and organic compounds.∙The foundation of organic chemistry is not a mysterious life force but rather the unique versatility of carbon-based compounds.Concept 4.2 Carbon atoms can form diverse molecules by bonding to four other atoms.∙ A carbon atom has a total of 6 electrons: 2 in the first electron shell and 4 in the second shell.∙Carbon has little tendency to form ionic bonds by losing or gaining 4 electrons to complete its valence shell.∙Carbon usually completes its valence shell by sharing electrons with other atoms in four covalent bonds, which may include single and double bonds.∙Carbon’s tetravalence makes large, complex molecules possible.o When a carbon atom forms covalent bonds with four other atoms, they are arranged at the corners of an imaginary tetrahedron with bond angles of 109.5°.o In molecules with multiple carbon atoms, every carbon atom bonded to four other atoms has a tetrahedral shape.o When two carbon atoms are joined by a double bond, all bonds around those carbons are in the same plane and have a flat, three-dimensional structure.o The electron configuration of carbon enables it to form covalent bonds with many different elements.∙The valences of carbon and its partners can be viewed as the building code that governs the architecture of organic molecules.∙In carbon dioxide, one carbon atom forms two double bonds with two different oxygen atoms.o In the structural formula, O=C=O, each line represents a pair of shared electrons.This arrangement completes the valence shells of all atoms in the molecule.∙Although CO2 can be classified as either organic or inorganic, its importance to the living world is clear: CO2 is the source of carbon for all organic molecules found in organisms.o CO2 is usually fixed into organic molecules by the process of photosynthesis.∙Urea, CO(NH2)2, is another simple organic molecule in which each atom forms covalent bonds to complete its valence shell.Molecular diversity arises from variations in the carbon skeleton.∙Carbon chains form the skeletons of most organic molecules.o Carbon skeletons vary in length and may be straight, branched, or arranged in closed rings.o Carbon skeletons may include double bonds.o Atoms of other elements can be bonded to the atoms of the carbon skeleton.∙Hydrocarbons are organic molecules that consist of only carbon and hydrogen atoms.∙Hydrocarbons are the major component of petroleum, a fossil fuel that consists of the partially decomposed remains of organisms that lived millions of years ago.∙Fats are biological molecules that have long hydrocarbon tails attached to a nonhydrocarbon component.∙Petroleum and fat are hydrophobic compounds that cannot dissolve in water because of their many nonpolar carbon-hydrogen bonds.∙Hydrocarbons can undergo reactions that release a relatively large amount of energy.∙Isomers are compounds that have the same molecular formula but different structures and, therefore, different chemical properties.∙Structural isomers have the same molecular formula but differ in the covalent arrangement of atoms.o Structural isomers may also differ in the location of the double bonds.∙Geometric isomers have the same covalent partnerships but differ in the spatial arrangement of atoms around a carbon-carbon double bond.o The double bond does not allow the atoms to rotate freely around the bond axis.o The biochemistry of vision involves a light-induced change in the structure of rhodopsin in the retina from one geometric isomer to another.∙Enantiomers are molecules that are mirror images of each other.∙Enantiomers are possible when four different atoms or groups of atoms are bonded to an asymmetric carbon.o The four groups can be arranged in space in two different ways that are mirror images of each other.o They are like left-handed and right-handed versions of the molecule.o Usually one is biologically active, while the other is inactive.∙Even subtle structural differences in two enantiomers may have important functional significance because of emergent properties from specific arrangements of atoms.o For example, one enantiomer of the drug thalidomide reduced morning sickness, the desired effect, but the other isomer caused severe birth defects.Concept 4.3 Characteristic chemical groups help determine how biological molecules function.∙The distinctive properties of an organic molecule depend not only on the arrangement of its carbon skeleton but also on the chemical groups attached to that skeleton.∙If we start with hydrocarbons as the simplest organic molecules, characteristic chemical groups can replace one or more of the hydrogen atoms bonded to the carbon skeleton of a hydrocarbon. ∙These chemical groups may be involved in chemical reactions or may contribute to the shape and function of the organic molecule in a characteristic way, giving it unique properties.o As an example, the basic structure of testosterone (a male sex hormone) andestradiol (a female sex hormone) is the same.o Both are steroids with four fused carbon rings, but the hormones differ in the chemical groups attached to the rings.o As a result, testosterone and estradiol have different shapes, causing them to interact differently with many targets throughout the body.∙In other cases, chemical groups known as functional groups affect molecular function through their direct involvement in chemical reactions.∙Seven chemical groups are most important to the chemistry of life: hydroxyl, carbonyl, carboxyl, amino, sulfhydryl, phosphate, and methyl groups.∙The first six chemical groups are functional groups. They are hydrophilic and increase the solubility of organic compounds in water.∙Methyl groups are not reactive but may serve as important markers on organic molecules.∙In a hydroxyl group (—OH), a hydrogen atom forms a polar covalent bond with an oxygen atom, which forms a polar covalent bond to the carbon skeleton.o Because of these polar covalent bonds, hydroxyl groups increase the solubility of organic molecules.o Organic compounds with hydroxyl groups are alcohols, and their names typically end in -ol.∙ A carbonyl group (>CO) consists of an oxygen atom joined to the carbon skeleton by a double bond.o If the carbonyl group is on the end of the skeleton, the compound is an aldehyde.o If the carbonyl group is within the carbon skeleton, the compound is a ketone.o Isomers with aldehydes and those with ketones have different properties.∙ A carboxyl group (—COOH) consists of a carbon atom with a double bond to an oxygen atom and a single bond to the oxygen atom of a hydroxyl group.o Compounds with carboxyl groups are carboxylic acids.o A carboxyl group acts as an acid because the combined electronegativities of the two adjacent oxygen atoms increase the chance of dissociation of hydrogen as anion (H+).∙An amino group (—NH2) consists of a nitrogen atom bonded to two hydrogen atoms and the carbon skeleton.o Organic compounds with amino groups are amines.o The amino group acts as a base because it can pick up a hydrogen ion (H+) from the solution.o Amino acids, the building blocks of proteins, have amino and carboxyl groups.∙ A sulfhydryl group (—SH) consists of a sulfur atom bonded to a hydrogen atom and to the backbone.o This group resembles a hydroxyl group in shape.o Organic molecules with sulfhydryl groups are thiols.o Two sulfhydryl groups can interact to help stabilize the structure of proteins.∙ A phosphate group (—OPO32−) consists of a phosphorus atom bound to four oxygen atoms (three with single bonds and one with a double bond).o A phosphate group connects to the carbon backbone via one of its oxygen atoms.o Phosphate groups are anions with two negative charges because 2 protons dissociate from the oxygen atoms.o One function of phosphate groups is to transfer energy between organic molecules. ATP is an important source of energy for cellular processes.∙Adenosine triphosphate, or ATP, is the primary energy transfer molecule in living cells.∙ATP consists of an organic molecule called adenosine attached to a string of three phosphate groups.∙When one inorganic phosphate ion is split off as a result of a reaction with water, ATP becomes adenosine di phosphate, or ADP.∙In a sense, ATP ―stores‖ the potential to react with water, releasing energy that can be used by the cell.。

合集下载

SAP系统18种查询表的方法

SAP系统18种查询表的方法

18 T echniques for Locating the Underlying Data of a Screen Field Dennis BarrettDennis Barrett is an applications consultant with SAP America who focuses on Service Management/ Customer Service and the Picture this. An Operations Manager wants a special report of her service orders. She gives you a sketch of what she wants it to look like (columns, rows, headings, grouping, subtotals, totals, and the like), and points to fields on the Service Management transaction screens that have the data she wants you to show in the report.What do you do? Most likely, you would check to find any existing reports delivered with the system (or already written for this client) that provide the information the Operations Manager wants, or that can be copied and revised to fit her needs. If you don’t find any, you might then look into the appropriate reporting system — in this case, the Plant Maintenance Information System (PMIS) — to see if you can adapt it. In this case, however, you can’t find the report, and you can’t cobble one together from existing ones. You must write a report or an ABAP Query to fulfill the requirements.Now, suppose the Operations Manager asks if you can somehow add just one more little function to her Create Measurement Docu-ments transaction: paste the associated sales order number into the MDoc text field. This scenario requires you to create an enhance-ment. In both the first and second scenario, you’ll need access to specific data from the database tables. How do you find that data with just the screen fields as your guide? We all know the information associated with a transaction is stored in several (sometimes many) related tables. So, when you need several fields from a transaction for a report or an enhancement, you may need to find many of the transaction’s tables and establish the links among them. Those links are often not obvious.(complete bio appears on page 18)I’ve come across these very situations on numer-ous occasions while working for several clients with the SD, MM, IM, WM, and Service Management (now called Customer Service) modules. Over time I have gathered suggestions from colleagues and developed some techniques myself to find the data I needed. I will share these techniques — 18 of them in all — with you now.The Starting Gate and Finish Line I will be presenting a wide variety of techniques for reaching the “finish line” of this exercise — namely, locating the table and field that stores the underlying data of a screen field. You’re unlikely to need all of them; you’ll probably be successful within the first four techniques. I include the remaining techniques because some fields can be very hard to chase down, and any one of these other tools just might do the trick.The Starting PointThe starting point for this set of techniques is always the Technical Information screen, because it is here that you learn the screen field’s name, and can dis-cern whether or not the underlying data object is a structure, view, or table.If the underlying data object is a table, your search is over. The field name shown on the Technical Information screen, plus this table name,arm you with the details you need. If the data object is a view, just one more click and you’ve got that table name. If the data object is a structure, you still have to unearth the name of the table. Technique #1:Check the Technical Information ScreenI always start my search for the underlying data object by getting the names of the field and Data Dictionary object from the transaction screen. Call up the Technical Information screen by positioning your cursor in the target screen field and then press-ing F1 or clicking on the ? button. This will bring up the initial Help screen. From within the Help screen, press F9 or click on the Technical info button.Take a look now at Figure 1. It shows the Technical Information screen for the Sold-to party field in the Create Standard (Sales) Order screen for Release 4.0B. You see in the “Field data” block that the Table name is KUAGV and the Field name is KUNNR.1 In Releases 4.0B and below, this screen calls the associated object a “table,” whether it’s a table, view, or structure. Notice in Figure 2 that the 4.5B release (and above) informs you that KUAGV is actually a structure.1The examples herein mention names of tables, structures, and fields that I found in my searches. You may find a different name in the same search — particularly a different structure’s name. For example, the Sold-to party field in the Sales Order initial screen may beKUAGV-KUNNR or RV45S-KUNNR (or maybe something else).I’ll show one name in this article; don’t worry if you find another.It’s a reflection of the continual enhancement of R/3, not (I hope) anerror in the article.In Releases 4.0B and below, to ascertain whether or not an object is a structure you must take one more step. Drill into the Table name field in the Technical Information screen to see the Data Dictionary screen for the object.Figure 3 shows those screens for the table VBAK, the view VIVEDA, and the structure KUAGV. Corresponding screens in Releases 4.5 and 4.6 look very similar. As you can see, the object type is easy to recognize in these screens.If the underlying object is a table, you’re home free. The information is stored in that table in the field with the same name as the one shown on the Technical Information screen. Success! When you write your report or ABAP Query, or when you program your enhancement, you can refer to the data using these table and field names.If the object is a view, then scroll to the View field in the view with the same name as the one shown in the Technical Information screen. See Figure 4; the Table and Field name associated with the View field is your goal. Success again!Figure 3The Release 4.0B Data Dictionary Screens forTable “VBAK,” View “VIVEDA,” and Structure“KUAGV”StructureStructures are Data Dictionary objects that have fields but do not carry data. A structure is Figure 4Locating the “Table” and “Field name” Associated with the “View field”TableTables store data. If your screen field points to a table,or you are able to drill down toTables, Views, and StructuresViewViews used in screens are linked groups of tables. If the field is in a view, you can drill A screen field is associated with a table, view, or structure. While each of these is a Data Dictionary object, only the table actually stores data. This is why the goal of all these techniques is to find the table that actually stores the information that you can see displayed in the screen.Figure 5The Suggested Sequence of TechniquesIf the object is a structure, then you have more digging to do, and you must proceed to one or more of the remaining 17 techniques described here. These techiques follow an order that should get you to the finish line in the fewest number of steps. Remember, as soon as you find the associated table, you’re done with the search. Look at the flowchart in Figure 5 to see my suggested sequence of techniques. Racing Toward the Finish Line: Techniques 2-13Remember, the finish line, or goal, of this exerciseis to locate the table and field names in which the underlying data for a screen field is stored. At this point, we know only that the underlying data object is a structure. Techniques 2-13, which I detailin this section, will most likely hold the answer. If techniques 2-13 do not hold the answer, try tech-niques 14-18 — the measures of last resort! I suggest you hold off trying these last five tactics until you’ve exhausted the other possibilities. If none of these 18 techniques work, you have an unusually difficult problem; I wish you good luck. I hope you find your table quickly and easily.Technique #2: Text FieldsIf the screen label is “Short text”, or the field name is STTXT, or its data element is CO_STTXT, then you are looking for the source of a text field. As Figure 6shows, the Short text field often has a “Maintain long text” icon stuck at the end that may look like a sheet of paper with a pencil. Click on that icon to get to the Long text screen.Texts are stored all over the place in R/3, but frequently in tables STXH and STXL, which are the text header and text line, respectively. Their texts are stored in raw (i.e., non-ASCII) form, so you must use function modules to get them. There are several function modules for processing these texts, including Read_Text, which reads text lines from the database. In the Long text screen, follow GoTo→Header (see Figure 7) to get the Text name, Text ID, and Text object parameters that you’ll need to execute the function module.If the field is not a text field, then you must con-tinue to search.Technique #3: “INCLUDE” TableA structure may contain one or more INCLUDEs. An INCLUDE may actually be a table or another structure. So, if the structure you are working with includes an INCLUDE, and that INCLUDE is a table that contains your field, then you have won again. For example, in a Sales Order Item Overview, the Condition Type is listed as KOMV-KSCHL, but KOMV is a structure. KOMV does contain the INCLUDE KONV, which is a table that contains the field KSCHL. That table and field are your goal, andFigure 7Retrieving the Text Name, Text ID, and Text Object Parameterswe need not go any further. If the structure doesn’t contain an INCLUDE, or if the INCLUDE is not a table, then we must keep searching. The next tech-nique you should apply is described in technique 4 because it’s easy and, quite likely, will get youyour answer.Technique #4: Reports, Queries, Infostructures If you know of any ABAP Queries, already-existing reports, or Infostructures that use the field you need, then you can dig into them to find the source table. Before you started this search, you may have found a report or query that didn’t provide the result that the Operations Manager needs, but that uses the field you are looking for. Now that you have the field name from the Technical Information screen, you can review those reports and queries to see if the search has already been done for you. If you find your field in one of those reports or queries, you can examine the code and find the table that it uses to pull that field; you will have successfully concluded your search.If you don’t find your table and field here, then you must continue searching. Technique 5 is a powerful one for those who know how to use it, and can very often find the result.You may have found a report or querythat uses the field you are looking for.Now that you have the field name, youcan review those reports and queries tosee if the search has already been donefor you. If you find your field in one ofthose reports or queries, you canexamine the code and find the tablethat it uses to pull that field, whichsuccessfully concludes your search.Technique #5: Debug WatchpointIf you are searching in Release 4.0B or above, and want to go to the heavy artillery immediately, then get the Program name (under “Screen data”) from the Technical Information dialog box and debug the program. Go to Tools→ABAP Workbench→ABAP Editor→Program=[the program name]→Debugging. Click on the Watchpoint button on the task bar and enter the program and field names into the Local watchpoint fields, then click on Enter and F8. Any change in the variable triggers the watchpoint, presenting you with the code immedi-ately below the line that changed the variable. Read the code above the watchpoint carefully, and you can probably find the name of the Data Dictionary object that the field is in. Again, it may be a table, view, or structure, but you are getting very close.Ken Greenwood (author of Teach Yourself ABAP/4 in 21 Days) says he always jumps immedi-ately to this technique if the Technical Information screen doesn’t produce the table. Ken further sug-gests that this technique finds the table right away —with the only exception being the IMPORT statement. If the watchpoint doesn’t trigger, then debug again using a breakpoint on IMPORT and you will find it in a maximum of three steps.If you can’t find the table reference you need in the code, then you must continue your search, and the next natural technique for you to use is described in technique 6.Technique #6: Value TableIf debugging didn’t give you what you need or you don’t want to debug a program, then back out to the Technical Information dialog box and double-click on the Data element field under “Field data”. This will show you the value table, if there is one. If you’re just looking for master data like customer name — whose field name is KUNNR — then a value table will probably be defined, and it will give you what you want. You’ll find that transactiondata like Order Quantity — whose field name is KWMENG — has no value table, and you get to keep looking. From here on, techniques 7-13 all have about the same likelihood of revealing your table name. Use them in any order you like. You’llprobably find that you like some more than others, so use those first.If debugging didn’t give you what youneed or you don’t want to debug aprogram, then back out to the TechicalInformation dialog box and double-clickon the Data element field under “Fielddata”. This will show you the value table,if there is one.Technique #7: “Where-Used” Data Element When R/3 moves data from one table (or structure) to another, it often (not always) moves it into a target field having the same data element as the source field. From the Technical Information dialog box, double-click on the Data element field under “Field data” and follow Utilities→Where-used List→ Table fields→Enter (see Figure 8). This will list the tables, views, and structures that use this data element. If your field is a commonly usedFigure 8“Where-used List Data element”Request Screen in Release 4.0Bone, this list may be so large that it’s hard to find your data storage location. For example, KUNNR shows up in 743 objects in Release 4.0B. An infre-quently used field may show up in fewer objects, and you can find your data source in the list.Note also that the list includes structures; some-times, lots of structures. When you drill into a field name in the list, you’ll see the table display that will identify it as a structure or a transparent table. If it’s a structure, you’ll have to keep looking.Technique #8: “Z_DATA_ELEMENT”Since the “Where-used” list for a data element generally contains so many (non-data carrying) structures, the list is not terribly useful for our purpose. Take a look at Figure 9, for example. It has 77 hits.You can create the Data Dictionary viewZ_DATA_ELEMENT, which will show only the data tables that use your data element.Figure 9Data Element “Where-used”ListFigure 10 Components of a View for Searching Data ElementsCreate the view with Tools→ABAP Workbench→ Dictionary→Objectname=Z_DATA_ELEMENT →Views→Create, then enter the values shown in Figure 10.Use this tool with Tools→ABAP Workbench→ Dictionary→Object name=Z_DATA_ELEMENT→Views→Display →Utilities→[Display data or Table contents]→DATA_ELEM=[the name of the data element you are searching for]→[Execute or F8].This view will give you a list of only the tables that use your data element.Technique #9: ViewsTransaction data is normally stored in several hierar-chically connected tables, and R/3 may have one or more views defined for the transaction you’re dealing with. You can search through those views to find other associated tables. Any one of those might store your data. For example, assume you want the Order Quantity data from the Sales order: Single-Line Overview screen. It’s listed as RV45A-KWMENG, but you find that RV45A is a structure. You already know that Order is VBAK-VBELN, so you lookfor views in the Where-used list for VBAK. View VIVEDA connects VBAK, VBUK, and VBAP, and you find KWMENG in the VBAP table. Technique #10: Logical DatabasesTables that are related in a business processare frequently connected in logical databases.The VBAK “Where-used” list for logical databases, for example, includes AAV, which also shows the connection to VBAP.Technique #11: Other Screen FieldsOne or more of the other fields in the same transac-tion may be directly connected to their database tables. If you can discover the Header table of the transaction, it may include the field you want. For example, assume you want the Sold to data from the Sales Order initial screen. It’s listed as RV45S-KUNNR, but you find that RV45S is a structure. Its data element is KUNAG, but Release 4.0B uses that data element in 276 tables, so it would be tough to find it there. On the same screen, the Order or Standard Order is listed as VBAK-VBELN. When you look up the VBAK table, you find that it also includes KUNNR.Technique #12: Application HierarchyIn 4.0B or above, go to Tools→ABAP Workbench →Overview→Data Browser. Press F4 in the empty Table name field, then click on SAP Applica-tions→Application Hierarchy. Drill down through the menu tree to find the tables associated withyour application. Your field may well be in one of those tables.Technique #13: GraphicsIn 4.0B or above, go to Tools→ABAP Workbench → Dictionary, then type in the name of a table you believe is related to your field. Follow the path Display →[Extras or Utilities]→Graphics. You’ll see a graphical representation of the selected table and its links to other tables. You can use this to see the entire family of tables related to a business object, and you may be able to find where your field is located.The Last Resort:Techniques 14-18These are the techniques of last resort, which you should turn to only if you’ve exhausted all other possibilities.Technique #14: Change RecordsR/3 allows for changes that are made to many documents to be recorded in change records, and frequently the change information includes the name of the table and field affected. If change recording is turned on, you can change the field you’re looking for in such a document, and then read the change record to find the table and field name. Depending on theR/3 release, here are some examples of menu paths to change records:•In Plant Maintenance or Service Management Technical Objects: Extras→[Display Changes or Environment]→Display ChangesOrder: Extras→Order documents→[Changes or Extras]→Display ChangesNotification: Extras→Notification documents→ChangesContracts & Planning: Environment→Changes•In Sales and DistributionOrder: Environment→ChangesDelivery: Environment→ChangesIf more than one change is shown, drill into the change you’re interested in (generally the most recent). Tables TCDOB and TCDOBT list allthe available object classes for change document creation. You can get clues there about whether your application supports change documents. Technique #15: Change DocumentsIf you can’t find the change record in your transac-tion, have a look in the change document tables CDHDR and CDPOS (now there’s a mix of English and German naming conventions: “Change Document Header” and “Change Document Position”!) as fol-lows. After you have changed and saved the field you’re searching for, open CDHDR in the ABAP Workbench dictionary, then follow Utilities→Table contents to find the change record. In the selection screen enter today’s date, time range, and your user name. It should pull the one matching record.Ctrl+C (copy) the value of CHANGENR, and use it to pull the appropriate record from CDPOS (Figure 11). This record contains the names of the table and field affected, as well as the new and old values, so you can ensure that you’re looking at the right record.Figure 11Change Table Illustration in Release 4.0BTechnique #16: SQL TraceIf all else fails, it’s time for some serious archeology. In one session, go to your transaction but don’t run it yet. In another session, go into Tools→ABAP Workbench→Test→SQL Trace→Trace On→Ok. Switch to your transaction session and run your transaction. Switch back to the trace session and click Trace off→List trace→[Execute or Ok]. You’ll have a list of all the SQL calls to the tables with their parameters. It may be easier to download it into a word processor document for searching. Use System → List→Save→Local file→unconverted→Enter→Filename=[c:\mypath\filename.doc]→Transfer. Open “filename.doc” in Word, search for your field name, and notice the tables it is associated with. It may involve detective work to determine which table actually stores the data. This approach requires an understanding of SQL commands and principles. Technique #17: Runtime Analysis Alternatively, use runtime analysis withSystem→Utilities→Runtime Analysis→Execute→[Transaction=your_transcode or Program=your_program_name]→F8. Afteryou post the transaction or complete the program, the system will return you to the Runtime Analysis screen. Choose Analyze, then Tables or Table Hit List (F6) to see all the transparent and pool tables that were accessed during the transaction. Hit List (F5) will show you all the program calls and specify the ABAP program that was running. Sometimes the Where-used list from the “Structure” display with Programs checked will list a program in which the field is associated with the database. Compare the programs in that list to those you found in the Runtime Analysis Hit List to narrow your search. Technique #18: Data ContentsFinally, extract some data from the set of tables asso-ciated with your transaction, and copy those records into a text file. Use the “Search” function in your word processor to find data flows by content where the source and destination fields may have different names and data elements. R/3 often uses internal numbers that you’d never think of, such as Object ID and Object Type, to link records. Their values, how-ever, can be quite distinctive, and you may be able to find the path of data flow by searching for the values (ignoring the field names) when you have pulled data from several transactions.For example, to find Measurement documents associated with a service order, we needed to trace the connections shown in Figure 12. There was nothing obvious about which fields linked the data.We created a service order and several Measure-ment documents in R/3. Then we pulled out the records starting with the service order numbers, and chased through the various joins to pull all the associ-ated records. While displaying each table in SE11 we used Utilities→Table contents to extract the data.Figure 12Data Path from Service Order to Measurement DocumentWe exported the records as text documents using System→List→Save→Local file and merged them all into a single Word document. We then used Word’s “Find” function to follow the data through the tables by following the value of the contents. OBJID, OBJNR, and MPOBJ contain internal numbers that “mean” nothing to the transaction, yet they linkedthe records.Helpful Hints✔ Many transactions have header informationand detail or item lines in separate linked tables. Remember that R/3 is a German product. “Kopf” is German for “head,” and “position” can be interpreted in German as “detail” or “item.” You’ll often find header/item table pairs with “K” and “P” in their names, such as VBAK and VBAP. When you are looking for linked tables containing the data for a transaction, this tip may help you identify one ifyou have the other.✔ There are small differences between R/3 Releases 3.1I, 4.0B, 4.5B, and 4.6B for the menu paths and directions used in this article. For example, Release 3.1I menus refer to the ABAP/4 (Workbench, Editor, etc.) whereas higher releases refer to ABAP. The Release 4.0B ABAP Workbench→ABAP Editor menu path shows up in Release 4.6B with the extra step ABAP Workbench→Development→ABAP Editor. The figures in this article were taken from a 4.0B system unless there was an important difference in appearance on another release. Many installations today are still using Release 3.1, and most are running 4.0 or below, so those images are important. The corresponding 4.5 and 4.6 screens are virtually identical to Release 4.0B except for Figure 2, so there’s no need to show the other figures in those releases as well.✔ Release 3.1I and below can’t execute technique 5 because they don’t have the watchpoint functionality in their debuggers, or techniques 12 and 13 because they don’t have the application hierarchy or graphics functions.ConclusionSAP’s three-tiered architecture is the backbone of an R/3 infrastructure. It’s what makes an R/3 system flexible, reliable, and open, all at the same time. It’s also what makes locating underlying data, at times, so inherently difficult. Hopefully the techniques presented here will help. Opt for the ones that you find easiest and most convenient to use. Leave the others as techniques of last resort. Some fields may still resist these techniques; there are no doubt other ways yet to chase them down. If you know of other techniques (or corrections to these techniques), please e-mail me at dennis.barrett@. AcknowledgementsThank you to the many SAP and partner consultants who gave me suggestions and feedback, and to those who reviewed this article.Dennis Barrett is an applications consultantwith SAP America who focuses on Service Management/Customer Service and the Service Provider solution. He has been consulting in computers for over 15 years, always blending applications and programming. He’s a certified ABAP programmer and often facilitates communications between business process owners and programmers. Dennis is the author of “SAP R/3 ABAP/4 Command Reference,” published by Que/MacMillan, and wrote “Customer Service ABAP Tables for Programmers,” published this spring in the PM/CS e-Newsletter, which is sent to all SAP consultants in Plant Maintenance and Customer Service. Dennis maintains a personal Web site at ~dennis.barrett, which includes copies of the PM/CS articles as well as white papers and other items of interest to ABAP programmers and CS consultants. You can reach him at dennis.barrett@.。

欧陆590直流调速器调试步骤

欧陆590直流调速器调试步骤

欧陆590直流调速器调试步骤目录型号说明2操作面板的使用3接线41、主回路接线42、控制端子接线53、查看控制端子配置7默认控制端子基本接线8必要的修改参数10浏览内部设置11系统菜单目录13通电运行15中英文对照报警说明16附录参数表24一、型号说明担号变・t1WMJ^iSr59OP■590—4<?EK."T>zt>■-■|r-^.^=0■I JI _1jn-,凹他#t 磷卑oe JS*4dr 出电握-屉处值运牛竝曰r 丼为坦剩叮产皿蚣肛酋»n ]咗=1牛上L .CHI 壬占=1m A004O-4OA-0070-7OA <3110-]10A,盯15*二卩占启扎01ac»=L 8UA.□2：70=27U-A C380-S80A .OSOO-MIO-A25=725A.O 呂申"■呂3-OAdSOC»~SOO/k1」580—158O/\LZC»e>-1■1■Pg 宀卫二!M-卫二仙几・27<JIJ —27-UUA应翘心己皱脸•1口社i*ft 电i 旦叛血小 220O LC 22OV f±30*i>g ■创血 500(He500V <士JO^.，Nl/石CHz sew IMJC &OOV <±]i>^i.J 50L '«JHZ rIXiJr-Kj 4*5>占閒SDOicrfi.^nv r ±ECF^)<IJi l-C 炎'屯>-1•=*i!目他報m 连i ■內总LW ：日：包齐q 4备以总fJLMirr 帜坦站在饰£扭而〉较备M*勒金证出kHIr 琴挤05CK1_(J4剧叫却用户用必rfj-」-HA.「比曲业工曲IM-讨鼓1食冷第三位揪件舉号aJh ：准<[P20->的悍卩・面战越從 第到仇操作平白 0-尢燥tv T 吿 etui:5 ■»•円血『杓确址阳严帕界Jfrii/i.VUK-& ]-R=SiiFi-OEt-=Lfr v^i K 参nl 」IdFU [嗣好丁-谢7sp-1'if^i^Lft (爭也冃」IJK 务F 唧:iJT=止:比利带£⑥邑冃扌门IDA 务TMIO斥■•+.億了布JW ：忙选的丘蹴类理鞘垃呢cjL'ii-^^/r-■+?<■(>>RAM =lllfl^.屯缶EMV =^P4HS t侍遥捜刑1EWP-^i^S 1卿科丸泮艸维一仃:逸、丨战璃比导汀雏一I ：选!744*•叫僅・」：荷別•韋T MW?麺貳段罠裁的辿顾口=卫柞瑚锻邃J 嗯 E i W-EIAS<-11/l^.ic 如硕屮1吱期<RS46^il ) FROF=pTDrLbUN 切说 LJNK-IJNK L 糙粘1佛垃 H••it三卷牛宇徇堰电了辅助电浙o=z ■J^iH ：W'U^S 1J s i^J 23tov 111；r^ro^t ]5筑歸HE *典宥人：1i 磺A.旳杂型豁4眄115=110V 崔U 22ty\'<11；lflT^.J-S0/MIH.ZZZ4>=ZZU¥i'J 244FV |正琵10%>A-S:-*-三位牛宁鞫规世『特祇工繰选戊羽川=從有牛卜轴i 选宜1二、操作面板的使用。

MTI04CS&MTI04CQ

MTI04CS&MTI04CQ


function
power supply power supply reference voltage input 1 for adjustment of transimpedance of MTIamplifier (pull down) input 2 for adjustment of transimpedance of MTIamplifier (pull down) input 3 for adjustment of transimpedance of MTIamplifier (pull down) switchable frequency range dependend on input capacitance of the photo-sensor (pull down) power down modus (pull down) analog current input of amplifier X analog voltage output of amplifier X
3.3 Switchable Frequency Range
settings of digital input SW4
VDD GND
c.) default by pull down
allowed capacitance of photo-sensor
< 5pF < 80pFc
3.4 Power Down Modus
VDD GND VREF SW1 SW2 SW3 SW4 PD IIN<X> VOUT<X>
a.) analog or digital
typ.
input input input input input input input input input output
鞋业验货英语

鞋业验货英语

UPPER DEFECT CATEGORY - UCOUNTER DEFECTS - CO 後套瑕疵1. Counter sheet not lasted under insole.港寶片未拉到中底上2. Wrinkled counter caused either by poor lasting or by wrinkled chemical sheet.拉幫不良或港寶片皺造成起皺。

3. Soft chemical sheet due to wrong material or wrong primer.港寶片品質不良或處理不良導致港寶片發軟。

4. Crooked chemical sheet.港寶片位置歪斜5. Low positioned chemical sheet.港寶片位置太低6. Blisters on counter.後套有氣泡7. Back height not uniform within pair by 2.0-mm or more.後套高度不一致達2mm或更多8. Other counter defects.其它後套瑕疵CROOKED UPPER DEFECTS - CU鞋面歪斜瑕疵1. Topline crooked or wavy.鞋領口彎曲或呈波浪狀2. Back seam off center, twisted or not vertical to heel seat by 2.0-mm.後套合縫線不正，偏離中線、扭曲或美與底垂直，偏離達2mm3. Back heights not uniform within pair.左右腳後套高度不一致4. Different vamp length of left and right foot over 2.0-mm. 左右鞋面長度不同，相差超過2mm5. Crooked upper caused by mis-stitching of moccasin construction.手縫馬克線跳針造成鞋面不正6. Crooked open toe in sandal construction.涼鞋前趾不正7. Other crooked upper defects.其它鞋面歪斜瑕疵COLOR VARIATION DEFECTS - CV色差瑕疵1. Poor antique treatment.銹色處理不良2. Color variation between different pieces of upper.鞋面不同部位色差3. Color of stitching and upper material not matching(as per conformation sample.)車線顏色與鞋面材料顏色不配4. Wrong color on ornaments and lace.裝飾配件以及鞋帶顏色不對5. Variation between left and right shoe.左右腳色差6. Poor printing and embroidery.鞋面不良印刷或赤繡7. Contrast color of PU coaling and backing fabric.PU裡及布裡呈對比色8. Other color variation defects.其它色差瑕疵DAMAGED UPPER DEFECTS - DU鞋面損壞瑕疵1. Scratch mark on upper.鞋面刮痕2. Visible roughing marks more than 1.5-mm or conspicuous.看得見的磨粗超過1.5mm或顯眼3. Cut upper.鞋面破裂4. Torn upper caused either by high stitch density or poor reinforcement.因不良補強或車線針距太密造成鞋面破裂5. Poor heat embossing.高溫壓花不良6. Toe box collapsing.鞋頭熱熔膠或港寶塌陷7. Missing or incorrect material embossment.鞋頭壓紋消失或不正確8. Loose or missing ornament parts.裝飾配件遺失或松動9. Broken strap.前帶或後帶斷裂10. Other damaged upper defects.其它鞋面損壞瑕疵EYELET AND LACE DEFECTS - EL鞋眼和鞋帶瑕疵1. Punched bigger or smaller than eyelet.鞋眼跟打洞不合2. Poor eyelet attachment.鞋眼釘合不良3. Loose eyelet.鞋眼松脫4. Paint coat peeling off.鞋眼的漆層脫落5. Rust on eyelet or other metal buckles.鞋眼或其它金屬扣生銹6. Laced wrong for easy try on.鞋帶拉力不良7. Wrong length,(need ton lace up the measure for length) 鞋帶長度不對8. Wrong color, wrong material , or wrong type of lace.鞋帶顏色、材質、型式不對9. Broken yam.斷紗10. Eyelet row not uniform by 2.4-mm.鞋眼排列不整齊，偏離2.4mm11. Dirty marks on lace.鞋帶有不潔記號12. Shoelaces tied together.左右腳鞋帶系在一起13. Other eyelet and lace defects.其它鞋眼或鞋帶瑕疵LINING DEFECTS(Includes vamp, sock, and counter lining) - LI內裡瑕疵（包括鞋面、鞋墊、後套裡等）1. Lining dirty, damaged or wrinkled.內裡贓、破損或褶皺2. Trimming damage on topline stitching, causing lining to show gap. 修鞋口裡造成破損導致開口3. Sock lining gap not deeper than 2-mm鞋墊裡位置歪斜達到2mm或超過（鞋墊貼合不良）4. Cementing off, between upper and lining.鞋面與內裡貼合不良5. Poor or unclear markings.不良或不清楚的標記6. Other lining defects.其它內裡瑕疵STITCHING DEFETS-SG 針車瑕疵1. Crooked stitching(out of stitching mark).針車歪斜（偏離港寶片）2. Stitching too close to seam edge.針車太靠近邊距3. High, low, or uneven stitch density.針車太密、太松、或不平均4. Loose or tight stitching.針車太緊或太松5. Skipped stitch on upper.跳針6. Incorrect needle type.不適用的針型7. Incorrect thread size.線的粗細不對8. Open seam.車線接合裂開9. Thread ends.線頭未修剪干淨10. Other stitching defects.其他針車瑕疵UPPER DIRTY-UD鞋面不潔瑕疵1. Glue stain.粘膠痕跡2. Dirty marks.不潔的記號3. High glue line more than 1.5-mm in any area.膠線太高，超過1.5mm或更多4. Frayed edge of PVC/PU upper material. PVC/PU鞋面材料毛邊5. Meld or Mildew.發霉thread residue线头fading, fugitive color 褪色color shade, off shade, color deviation 色差raw edge leans out of seam毛头washing quality is not good洗水不良6. Other upper dirty defects其它鞋面不潔的瑕疵WRINKLED UPPER DEFECTS-WR鞋面皺褶1. Wrinkles caused by poor lasting.拉幫不良造成的皺褶2. Wrinkles caused by poor bottoming.貼底不良造成的皺褶3. Wrinkles caused by distorted upper鞋面變形造成的皺褶4. Other wrinkles upper defects.其它鞋面皺褶瑕疵X-RAY DEFECTS-XR1. X-ray lines on and part of upper showing through due to edge folding, chemical sheet, toe cap, etc. 由於拗邊、港寶片、鞋頭包片等引起的任何鞋面部位的透痕2. X-ray lines of upper lasting allowance showing through on bottom due to improper buffing or filler. 大底拉幫部位不平順有X-ray透痕產生，由於磨粗不平或填腹不良引起3. Other X-ray defects.其它的X-ray透痕SOLE DEFECTS CATEGOTY-SSOLE BOTTOM SIRTY DEFECTS - BD大底不潔瑕疵1. Dirty marks.不潔記號2. Poor outsole printing or paint peels off.大底印刷不良或上漆剝落3. Rough edge of EVA outsole.EVA底邊未磨平均（粗糙）4. Impurities in sole material.大底物料不純5. Other bottom dirty defects.其它大底不潔記號SOLE BOTTOM GAPPING DEFECTS - BG大底縫隙瑕疵1. Any gap or small hole at the bottom edge, where the bottom meets the upper. 大底與鞋面開膠2. Toe or heel bumper peeling off at edges.鞋頭包出後包片剝落3. Gapping between midsole and outsole.中底與大底間縫隙4. Gapping between EVA bottom and welt.EVA大底與沿條間出現縫隙5. Gapping between any layered soles.各層底間出現縫隙6. Other sole gapping defects..Critical significant amount of gapping before pulling.嚴重：未拉幫前已有嚴重裂縫出現Major when pulled on, gaps easily.主要：拉底後裂縫立刻呈現.Minor when pulled hard, some gapping.次要：用力拉底縫隙微現SOLE BOTTOM ADHESION DEFECTS - SA大底貼合瑕疵1. Sole easily pulls away from upper during manual examination.經由手力的檢驗，可將鞋面與大底輕易的拉脫2. Sole failed to meet minimum sole-bond-peeling standard after mechanical pull test.經由機械的拉力測試，大底無法達到最低的大底拉力標准HEEL OR TOPLIFT DEFECTS HT鞋跟與天皮瑕疵1. Leaning heel(where the heal itself crooked).鞋跟傾斜（跟本身歪斜）2. Protruding or nail head on heel seat, inside of shoe. (critical)鞋身跟座上釘頭突3. Loose top lift.天皮松脫4. Protruding of nail on heel stem (sticks out of side heel).鞋跟出釘（由鞋旁突出）5. Blister, scratch mark, dirty mark or cut on heel cover.包跟皮有氣泡、刮痕、不潔或破損6. Other heel or top lift defects.其它鞋跟與天皮瑕疵SOLE PLACEMENT/SIZE DEFECTS-PS 貼底位置/貼合號頭瑕疵1. Crooked positioning of outsole more than 2-mm.貼底位置歪斜超過2mm2. Toe spring too high.鞋頭翹度太高3. Other placement/size defects.其它貼底位置或貼合號頭瑕疵PACKAGING PROBKEM TYPE-PKINFORMATION ACCURACY DEFECTS - PA (Critical unless noted)包裝准確度瑕疵1. Wrong size in case錯誤號頭裝入箱內2. Wrong lot# in case.(critical)錯誤的型體號碼裝入箱內3. Mismate不配雙4. Pair shortage. 短裝5. Other packing accuracy defects.其它包裝不正確的瑕疵PRODUCT MARKING DEFECTS - PM (Minor unless noted)產品標識瑕疵1. Product (batch) code wrong.產品批號錯誤2. Product (batch) code missing產品批碼錯誤3. Lot# wrong on product. (Critical)型體號碼錯誤4. Lot# missing on product. (Critical)型體號碼消失5. Missing or wrong bar code ticket on product. (Major)產品價格標簽消失或錯誤6. Shoe ticket in wrong location.價格標簽不正確7. Ticket upside down/sideways (incidental).價格標簽上下或內外顛倒8. Wrong price. (Critical)價格錯誤9. Price ticket curled up (incidental).價格標卷曲10. Wrong data in bar code. (Major)價格標條碼不正確11. Incorrect product labeling.產品標簽使用不當12. Other product marking defects其它產品標識瑕疵13. Missing “TM”or “R”at brand name.不見“TM”或“R”字樣CASE LABLE MARKING DEFECTS –CL外箱貼紙瑕疵1. Wrong alpha or size. (Critical)錯誤的包裝號頭組合2. Missing/illegible alpha or size. (Major)不見或模糊的包裝號頭組合3. Wrong pair quantity. (Major)錯誤的雙數4. Missing/illegible pair quantity. (Major)不見或模糊的雙數5. Wrong lot#. (Critical)錯誤的型體號碼6. Missing/illegible lot#. (Major)不見或模糊的型體號碼7. Wrong PO #. (Critical)錯誤的訂單號碼8. Missing/illegible PO #. (Major)不見或模糊的訂單號碼9. Less than 2 labels per case. (Major) 每一外箱至少2張貼紙10. Applied in wrong position. (Major)外箱貼紙粘貼錯誤11. Carton tape covering the bar code or quiet zone. (Major)外箱貼紙條碼被透明的封箱帶蓋住12. Bad data in bar code. (Critical)外箱貼紙條碼資料有誤13. Case label bar code not ANSI Grade C or better. (Major)雷射掃描外箱貼紙其結果為非“ANSI Grade”或以上14. Other case label defects. (Minor or Major)其它的外箱貼紙瑕疵SHOE BOX MARKING DEFECTS - SB (Major unless noted) 鞋盒標識瑕疵1. Illegible or wrong lot# on shoe box. (Critical)模糊或錯誤的型號在鞋盒上2. Illegible or wrong size on shoe box.模糊或錯誤的尺碼在鞋盒上3. PCL misplaced.流程控制標貼錯誤.Bottom edge of PCL over-hanging bottom edge of box.流程控制標凸出盒底.Bottom edge of PCL more than 10-mm away from bottom edge of box at any point.流程控制標底緣的任一位置高於盒底邊10mm.PCL skewed 11°(10-mm) or more.流程控制標歪斜超過11°或更多4. Wrinkled or folded PCL.流程控制標皺褶5. Colored exterior layer of box removed, exposing white underlayer in an attempt to reposition an incorrectly applied label. (Minor)因撕掉及重新貼價標的原因而使鞋盒表層脫落而露出白底層6. PCL missing.沒有流程控制標7. Wrong PCL. (Critical)錯誤的流程控制標8. PCL not ANSI Grade C or better.掃描鞋盒控制標為非“ANSI Grade”9. Other shoe box information defects.其它鞋盒資料瑕疵Note: Box tables applied over an existing box label due to rework is not a defect.注意：因翻箱原因而把正確的流程控制標重疊貼在舊的流程控制標上的情況不算瑕疵。