Reading SampleNavigate through your SAP ERP modules with ease! In this reading sample, we provide a glance at some of the most useful transactions in SAP ERP Production Planning (PP), Sales and Distribution (SD), Plant Maintenance (PM), and Quality Management (QM).
Venki Krishnamoorthy, Martin Murray, Norman Reynolds, and Peter Teesdale
SAP Transaction Codes648 Pages, 2016, $49.95 ISBN 978-1-4932-1366-5
www.sap-press.com/4070
First-hand knowledge.
6 “Production Planning (PP)”
7 “Sales and Distribution (SD)”
8 “Plant Maintenance (PM)”
9 “Quality Management (QM)”
Contents
Index
The Authors
217
Chapter 6
6 Production Planning (PP)
This transaction is used to create a master rec-ipe for a finished or semifinished material. Thematerial, plant, version, and profile should beadded on the initial screen. On the Recipe
screen, the resource and the control should beadded. On the Operations screen, the opera-tion, description, and the duration should beentered, and these should be repeated for eachphase of the operation.
This transaction is used to change a masterrecipe for a finished or semifinished material.On the initial screen, you should enter therecipe group. The transaction will display theOperations screen where you can change theexisting operation or add additional opera-tions.
This transaction is used to display a masterrecipe for a finished or semifinished material.On the initial screen, you should enter therecipe group. The transaction will display theOperations screen, where you can review theoperations. You can review the materials inthe recipe by clicking on the Materials tab.Recipe header information and administrativedata can also be reviewed.
This transaction is used to modify productionversions based on certain selection criteria.The initial selection screen requires you to en-ter a plant, but other selection criteria can beentered, such as material, MRP controller, key
date, or production line. The transaction thenwill display the production versions, and youcan modify data for each, such as text, validitydates, lot size, planning group, productionline, receiving storage location, and issuinglocation.
This transaction is used to print master reci-pes. The selection screen allows you to enter amaterial, plant, recipe group, key date, plan-ner group, recipe status, and usage. From theselection screen, the output shows all the rel-evant recipes based on the selection criteria.Each recipe shows the operation details, in-cluding the resource and activity types.
This transaction is used to print the details ofa production version for a material. The selec-tion screen allows you to enter a material,plant, production version, task list type, andtype list group. The transaction output showsthe production versions for each material, in-cluding the detailed planning and bill of mate-rials (BOM) information. The output will alsodisplay warning or error messages if produc-tion versions have discrepancies.
This transaction displays any changes thathave been made to a task list. The initialscreen allows you to enter a material, plant,recipe group, and a date range. The outputshows the changes per object, which can in-clude the item, the date change, and the userwho made the change.
C201 Create Master Recipe
C202 Change Master Recipe
C203 Display Master Recipe
C223 Production Version: Mass Processing
C251 Master Recipe Print List
C252 Print List for Production Versions with Consistency Check
C260 Task List Changes
Production Planning (PP)6
218
This transaction displays the changes made toa recipe group. The initial screen allows youto enter the recipe group, a date range forchanges to be displayed, and the user whomade the change. The output shows the dateand time a change was made, the user whomade the change, and the transaction used tomake the change.
This transaction is used to delete task lists butwithout archiving. The initial selection screenallows you to enter a material, plant, group,status, task list usage, or planner group. Thetransaction will propose a number of relevanttask lists from which you can deselect thosethat do not need to be deleted.
This transaction is used to create a routing,which is a description of which operationsmust be carried out, and in what order, toproduce a material. On the initial screen, youneed to add a material and plant. On the nextscreen, you need to enter a value for the usageand a status. Operations can be added to therouting, including the work center, controlkey, and description.
This transaction is used to change an existingrouting. The initial screen requires you to en-ter a material and plant or a group number.The Operation Overview screen is displayed,where you can add new operations or changeexisting ones.
This transaction is used to display an existingrouting. The initial screen requires you to en-ter a material and plant or a group number.The transaction displays all the operations forthe routing. You can review other aspects ofthe routing, such as production resource/tooland inspection characteristics.
This transaction is used to create, change, ordisplay standard texts. The initial screen al-lows you to enter a new standard text by en-tering a standard text key and a description.The next screen gives you the option of enter-ing a full screen of free-format text. If a stan-dard text exists, then the screen will show theexisting text, which can be changed.
This transaction is used to create a referenceoperation set. The initial screen does not re-quire you to enter a group number. TheHeader Details screen requires you to enterthe task list usage and the status key. Opera-tions can be added in the Operation Over-
view screen. Inspection characteristics can beentered for each operation.
This transaction allows you to change an ex-isting reference operation set. The initialscreen requires you to enter a group number.The Operation Overview screen allows youto enter a new operation or change an exist-ing one. For each operation, the inspectioncharacteristics can be changed or added.
This transaction is used to display an existingreference operation set. The initial screen re-
C261 Display Change Documents for a Recipe Group
C298 Deletion of Task Lists without Archiving
CA01 Create Routing
CA02 Change Routing
CA03 Display Routing
CA10 Standard Text
CA11 Create Reference Operation Set
CA12 Change Reference Operation Set
CA13 Display Reference Operation Set
Production Planning (PP) 6
219
quires you enter a group number. The trans-action shows the operations associated withthe group number. You can review other as-pects of the routing, such as production re-source/tool and inspection characteristics.
This transaction is used to create a rate rout-ing, which is used when you plan on a quan-tity basis, for example, in repetitive manufac-turing. The initial screen does not require youto enter a group number. The Header Details
screen requires you to enter the task list usageand the status key. Operations can be addedon the Operation Overview screen. Inspec-tion characteristics can be entered for eachoperation.
This transaction allows you to change an ex-isting rate routing. The initial screen requiresyou to enter a group number. The Operation
Overview screen allows you to enter a newoperation or change an existing one. For eachoperation, the inspection characteristics canbe changed or added.
This transaction is used to display an existingrate routing. The initial screen requires you toenter a group number. The transaction showsthe operations associated with the groupnumber. You can review other aspects of therouting, such as production resource/tool andinspection characteristics.
This transaction is used to create a referencerate routing, which is used when you plan ona quantity basis, for example, in repetitivemanufacturing. The initial screen does not re-quire you to enter a group number. The
Header Details screen requires you to enterthe task list usage and the status key. Opera-tions can be added with on the Operation
Overview screen. Inspection characteristicscan be entered for each operation.
This transaction allows you to change an ex-isting reference rate routing. The initialscreen requires you to enter a group number.The Operation Overview screen allows youto enter a new operation or change an exist-ing one. For each operation, the inspectioncharacteristics can be changed or added.
This transaction is used to display an existingreference rate routing. The initial screen re-quires you to enter a group number. Thetransaction shows the operations associatedwith the group number. You can review otheraspects of the routing, such as production re-source/tool and inspection characteristics.
This transaction is used to print a task list forany number of SAP-defined task list types.These task list types include routings, refer-ence operation sets, rate routings, referencerate routings, rough-cut planning profiles, in-spection plans, general maintenance task lists,equipment task lists, standard networks, mas-ter recipes, and functional location task lists.The initial screen allows you to enter a tasklist type and a single or range of materialnumbers, plants, groups, and group countersas well as a key date for task list validity.
A number of optional program parameters areavailable, such as component assignment dis-play, various radio buttons for alternative billof materials (BOM) selection as well as a phan-tom assembly explosion option. Additional se-
CA21 Create Rate Routing
CA22 Change Rate Routing
CA23 Display Rate Routing
CA31 Create Reference Rate Routing
CA32 Change Reference Rate Routing
CA33 Display Reference Rate Routing
CA51 Task List Print List
Production Planning (PP)6
220
lection criteria for task list selection includeplant, usage, status, and planner group, to-gether with a number of print options to dis-play other application-specific values andtexts. A variant can be saved for the transac-tion parameters for foreground processing orbackground job scheduling. Executing thetransaction will display the task list print listfor the criteria entered. Additionally, the tasklist can be printed to an output device, savedto a file, or sent to SAP Business Workplace.
This transaction is used to display the changesmade to a task list. The initial screen requiresyou to enter the recipe group. The outputscreen shows each change by object, item, va-lidity date, and user who made the change.
This transaction is used to display the changesfor a routing. The initial screen requires youto enter a routing group as well as an optionaldate range. A specific user name can also beentered for change document identification.The report layout can be output either as achange document overview or as an objectoverview for routings; a number of optionalobject selections for the routings are availableas checkbox selections, for instance, forHeader, Sequence, Components, Operation,CAPP Suboperation, Process Instruction
Char., and so on. The output screen showseach change to the routing group. The detailsof each change per object are shown, includ-ing the change date and time, user who madethe change, change number, date the changeis valid from, and associated transaction codewhere the change was made.
This transaction is used to display the changesfor a reference operation set group. The initialscreen requires you to enter a reference oper-ation set group as well as an optional daterange. The output screen shows each changeto the reference operation set group. The de-tails of each change are shown, including thechange date and time, user who made thechange, and date the change is valid from.
This transaction is used to display the changesfor a rate routing. The initial screen requiresyou to enter a rate routing production linegroup as well as an optional date range. A spe-cific user name can also be entered for changedocument identification. The report layoutcan be output either as a change documentoverview or as an object overview for rateroutings; a number of optional object selec-tions for rate routings are available as check-box selections, for instance for Header, Se-
quence, Components, Operation, and so on.The output screen shows each change to therate routing. The details of each change perobject are shown, including the change dateand time, user who made the change, thechange number, date the change is valid from,and associated transaction code where thechange was made.
This transaction is used to display the changesfor a reference rate routing. The initial screenrequires you to enter a reference rate routingas well as an optional date range. The outputscreen shows each change to the referencerate routing. The details of each change areshown, including the change date and time,
CA60 Task List Changes
CA61 Display Change Documents for a Routing
CA62 Display Change Documents for Reference Operation Set Group
CA63 Display Change Documents for a Rate Routing
CA64 Display Change Documents for a Reference Rate Routing Group
275
Chapter 7
7 Sales and Distribution (SD)
This transaction is used to correct errors thathave resulted from automatic goods move-ments. Automatic goods movement errors oc-cur, for example, when a production order isbeing confirmed and components are back-flushed from a storage location that does nothave the required quantity in inventory. Se-lection criteria include plant, storage location,material, error date from/to range, and otherrelevant inventory document data. The out-put is an aggregated list of goods movementerrors. Once the error has been reviewed andresolved, the inventory movement will beprocessed.
This transaction is used to create a dangerousgoods master, which is an extension of thematerial master. The master record containsinformation required to carry out automaticchecks in the Sales and Distribution (SD) andMaterials Management (MM) processes andgenerate documents required by local regula-tors. Input an existing material master and thedangerous goods regulation code (in Custom-izing, the dangerous goods regulation codecontains the mode of transport and validityarea, for example, Germany). Enter the mas-ter data and save.
Use this transaction to change a dangerousgoods master previously created using Trans-action DGP1.
Use this transaction to display a dangerousgoods master previously created using Trans-action DGP1.
Use this transaction to display a list of danger-ous goods master data from the dangerousgoods master data table DGTMD. Input selec-tion includes material, regulation key, andvalid from/to date range. The output can belisted by material, mode of transport cate-gory, and validity area; all change statuses,which are identified by validity area orchange number, can be read at the item level.The display layout can be changed and savedas a default, according to your requirements.
This transaction is used to create a resource-related billing request, which is a special typeof billing based on resources consumed bythe organization. For example, a consultingcompany agrees to sell services based on timespent on a sales order. Time is recorded to thesales order, and then the customer is billedbased on the hours charged to the sales order.This transaction generates the resource-re-lated billing request, which is followed up byan actual billing document. Input the sales or-der and line items, pricing date, posting date,and posting period and execute.
COGI Automatic Goods Movements: Error Handling
DGP1 Create Dangerous Goods Master
DGP2 Change Dangerous Goods Master
DGP3 Display Dangerous Goods Master
DGR1 Dangerous Goods Master: Display with Descriptions
DP91 Resource-Related Billing Request
Sales and Distribution (SD)7
276
Use this transaction to create an intercom-pany billing document for the purposes ofbilling one company for using the resourcesof another company code in order to bill anend customer. In this scenario, an intercom-pany sales order is generated for using the re-sources. Once time and/or expenses arecharged to a project, the selling companycode can bill the end customer. The next stepis to use this transaction to create the inter-company billing request, which is then fol-lowed by an intercompany billing document.This in turn facilitates the payment from theselling company code to the company codeproviding the resources. Input the intercom-pany sales document, period, fiscal year, andposting to date; choose a sales price; and press(Enter). On the Sales screen, expand theitems and chose the cross-company line itemand then chose Billing Request and thenclick Yes to confirm the billing request cre-ation.
This transaction is used to create a resource-related billing request for multiple resourceusage postings across multiple sales orders.Resource-related billing is a special type ofbilling based on resources consumed by anorganization. For example, a consulting com-pany agrees to sell services based on timespent on a sales order. Time is recorded to thesales order, and then the customer is billedbased on the hours charged to the sales order.This transaction generates a resource-relatedbilling request, which is followed by the ac-tual billing document. Input the sales orderand line items, pricing date, posting date, andposting period and execute.
This transaction uses the sales informationsystem application to report sales activities.This transaction specifically uses informationstructure S001 (Customer). An informationstructure contains characteristics (fields thatare reported on) and key figures (results of thereport). This transaction has the followingstandard delivered characteristics: sold-to,sales organization, division, distribution chan-nel, and material. The standard delivered keyfigures include, for example, sales order val-ues and quantity, open sales order values,sales order cost, returns order values, billingvalues, and sales order subtotal values. Inputcustomer, sales area, and posting period from/to range and execute. Multiple display func-tions are available, including the ability toswitch the drilldown order, the characteristickey and value, and the key figures related totop percentage values.
This transaction is similar to TransactionMCTA but focuses on the material characteris-tic and uses information structure S004 (Ma-terial). An information structure containscharacteristics (fields that are reported on)and key figures (results of the report). Thistransaction has the following standard deliv-ered characteristics: material, sales organiza-tion, division, and distribution channel. Thekey figures include, for example, sales ordervalues and quantity, open sales order values,sales order cost, returns order values, billingvalues, and sales order subtotal values. Inputcustomer, sales area, and posting periodfrom/to range and execute. Multiple displayfunctions are available including the ability toswitch drilldown order, the characteristic keyand value display, and key figures related totop percentage values.
DP93 Resource-Related Billing Request between Company Codes Sales and Distribution
DP96 Collective Processing Resource-Related Billing Request
MCTA Customer Analysis: Selection
MCTC Material Analysis (SIS): Selection
Sales and Distribution (SD) 7
277
This transaction is similar to TransactionMCTA but focuses on the sales organizationcharacteristic and uses information structureS003 (Sales Organization). An informationstructure contains characteristics (fields thatare reported on) and key figures (results ofthe report). This transaction has the followingstandard delivered characteristics: sales orga-nization, division, distribution channel, andsales district. The key figures include, for ex-ample, sales order values and quantity, opensales order values, sales order cost, returns or-der values, billing values, and sales order sub-total values. Input customer, sales area, andposting period from/to range and execute.Multiple display functions are available, in-cluding the ability to switch drilldown order,the characteristic key and value display, andkey figures related to top percentage values.
This transaction is used to maintain pricingcondition records for shipment costs that ac-cess pricing information automatically whencreating a shipment cost document via Trans-action VI01. Input a condition type, for exam-ple “FB00,” and press (Enter). Next select thecondition table to be maintained (each condi-tion type will be customized with an accesssequence and condition tables with the condi-tion fields) and press (Enter). In order to cal-culate freight costs based on scales, you alsoneed to assign the scale to the freight condi-tion type in Customizing (Transaction T_06).Maintain the condition record fields, rate,unit of measure, and valid from/to fields andsave.
Use this transaction to change pricing condi-tion records for shipment costs, which may berequired if you need to change the rate, ex-tend the valid-to date, or place a deletion indi-cator on the condition record. Input the con-dition type, press (Enter), select the condi-tion table that contains the condition fields(note that in Customizing you do have someflexibility to change some of the requiredfields for the purposes of maintenance, whichcan be useful if you want the change multiplecondition records at the same time), and clickExecute. Then maintain the condition recordand click Save.
Use this transaction to display a condition re-cord previously created using TransactionTK11.
This transaction is used to compare customermaster records with general data created, butneither company code data nor sales area datahave been created. Selection criteria includecustomer number, account group, creationdate, company code, and sales area data (salesorganization, distribution channel, and divi-sion). A checkbox indicates if the report looksfor missing company code data (Not Created
in Fin. Accounting) or sales area data (Not
Created in Sale + Distr.). The report outputlists those customers that have either no com-pany code or no sales area.
This transaction is used to display changesmade to the customer master record. Selec-
MCTE Sales Organization Analysis: Selection
TK11 Create Condition Records Shipment Costs
TK12 Change Condition Records Shipment Costs
TK13 Display Condition Records Shipment Costs
OV50 Customer Master Data Comparison
OV51 Display Changes to Customers
Sales and Distribution (SD)7
278
tion options include customer number/range,change date, changer user ID, and sales areadata (sales organization, distribution channel,and division). Checkboxes to display the gen-eral, company code (Not Created in Fin. Ac-
counting) or sales area data (Not Created in
Sale + Distr.). The report output includesdate/time of change, field name, sales areadata, and new and old field values.
Use this transaction to list all sales documentsthat are incomplete according to the incom-plete procedure assigned to the sales documentheader or line item. Check the box for the doc-ument type(s) selected, status code, and salesarea information and execute. The output willlist the incomplete documents with the af-fected follow-on documents and provide theability to select the document, complete themissing data, and save the document.
This transaction is used in the same way asTransaction V.01, except the default field se-lection for the SD transaction group is “0,”which means that all incomplete sales orderswill be selected.
This transaction is used in the same way asTransaction V.01, except the default field se-lection for the SD transaction group is “1,”which means that all incomplete sales inqui-ries will be selected.
This transaction is used in the same way asTransaction V.01 except the default field se-
lection for the SD transaction group is “2,”which means that all incomplete sales quota-tions will be selected.
Use this transaction to report all sales order/contracts blocked for delivery according tothe delivery block indicator. Note that the val-ues are determined from the confirmed quan-tities of the order items. Also note that, by se-lecting the new data selection indicator, theprogram reads the whole database, and so if alarge dataset is being processed, selecting thisindicator is not recommended. Instead, it isrecommended that you save the output. Se-lection criteria include delivery block indica-tor and sales area. The display variant can bechanged, saved, and used as a default at run-time.
This transaction is used for backorder pro-cessing, where you can list the materials thatare on backorder and confirm them manuallyusing available to promise (ATP) inventoryquantities. Input your selection criteria (forexample, the plant, sold-to party, purchase or-der number) and click Execute. The outputdisplays a list of sales order line items and ma-terials. Then you can branch to the sales orderchange function. To process the backorderfrom the list, select your line item and selectEdit � Backorder, select the MRP element,and click Edit � Change Confirmation. Thenin the Sales Requirements section, you candistribute ATP quantities or redistribute con-firmed quantities.
Use this transaction to review a log of the bill-ing collective run, which is generated by col-lective run transactions such as billing run via
V.01 Incomplete SD Documents
V.02 Incomplete SD Documents (Incomplete Orders)
V.03 Incomplete SD Documents (Sales Inquiry)
V.04 Incomplete SD Documents (Sales Quotation)
V.14 Sales Orders/Contracts Blocked for Delivery
V.15 Backorders
V.21 Log of Collective Run
311
Chapter 8
8 Plant Maintenance (PM)
You can use this transaction to replace a workcenter in a task list. In the selection screen,enter the plant, key for the work center, andkey for the new work center. If a key date isnot entered, all operations where the workcenter is used are displayed. You can restrictthe selection by entering additional search cri-teria such as key date, status, usage, plannergroup, and material number.
Transaction CA85 has disadvantages such aspoor performance and lack of background pro-cessing capability; hence, the new TransactionCA85N (Mass Replacement: Work Center) isavailable. While using Transaction CA85N, ifthe target work center is same as the sourcework center but contains different validities forcost centers and activity types, the system is-sues an error message. Refer to SAP Note1454538 – CA85N: Incorrect error message CR061 for information on how to correct this er-ror message. You can refer to SAP Note 543400– New: Mass Replacement Work Center formore details about Transaction CA85N.
You can use this transaction to create, change(edit and maintain), and display the master dataof classes. You can create a new class either di-rectly or with a template. Classification of equip-ment, functional locations, and bills of materials(BOMs) are often used to identify additionaltechnical specifications for maintenance objects.The Product Structure Browser displayswhich objects are assigned to the class. In the ini-tial screen, follow the menu path Environment �Product Structure to display the Product
Structure Browser.
You can use this transaction to create as-builtconfigurations from production data. An as-built configuration describes the structure of aserialized assembly that has been produced orthe history of the individual components usedin the product. An as-built configuration canbe created after each individual order or atthe end of the production of a finished prod-uct.
You can use this transaction to create the datathat identify the maintenance bill of material(BOM). Maintenance BOMs are differentfrom production or engineering BOMs be-cause maintenance BOMs contain only itemsrelevant to maintenance. The maintenanceBOM has two main functions: structuring atechnical object (equipment or functional lo-cation assemblies) and spare parts planning inthe order. While creating the BOM, you canspecify the effective date as well. You can en-ter the plant if you want the BOM to be effec-tive in this specific plant. If the material forwhich you are creating the BOM has a mate-rial type that cannot be combined with theBOM usage, an error message is displayed.
You can use this transaction to edit and main-tain the bill of materials (BOM) data. If theBOM you are maintaining is allocated to mul-tiple plants, the changes are relevant to allplants. If you process a BOM that is part of aBOM group with a change number, you mustuse a change number to process all BOMs inthe group.
CA85 Replace Work Center in Task Lists
CL02 Classes
COIB As-Built for Serialized Material
CS01 Create Material BOM
CS02 Change Material BOM
Plant Maintenance (PM)8
312
You can use this transaction to display a bill ofmaterials (BOM). In the selection screen, youcan enter the plant data as a search filter.Based on the entered search filter, the con-tents of the BOM are displayed.
You can use this transaction to compare twodifferent bills of material (BOMs). This func-tionality is particularly useful, if multipleBOMs exist for a specific material. The com-parison is done per item. In the BOM compar-ison initial screen, enter the primary BOM,secondary BOM, validity dates and then selectthe explosion level (single level or multilevel).If differences between BOMs exist, the BOM
Comparison – Result screen will be dis-played. You can compare different categoriesof BOMs with each other.
You can use this transaction to get a listing ofall the bills of materials (BOMs) in which amaterial is used. The output listing will in-clude the material BOMs and the equipmentBOMs that use the material. The materialwhere-used list can be displayed either as asingle level or in multilevel format. In a sin-gle-level listing, only BOMs where the mate-rial is directly used as components are dis-played. The BOMs will be displayed with ex-plosion level 1. In a multilevel listing, you getan overview of all the levels where the BOMsthat contain the specified material are used.
You can use this transaction to make changesto multiple bills of materials (BOMs) at once.
Using the mass change functionality, you canperform one of the following: Change (chang-ing an item in multiple BOMs at once orchanging an item’s data), Delete (deleting anitem from multiple BOMs at once), and Cre-
ate (creating a new material item in severalBOMs that contain a specific reference object).
If you edit or maintain a bill of material(BOM) without a change number, the systemlogs these changes in a change document. SAPstores the data related to BOMs in differenttables. SAP writes the changes made to theBOM data to the relevant tables, and changedocuments are generated based on these ta-bles. You can use this transaction to displaythe change document for the specified mate-rial BOM. Change documents give an over-view of the old and new field values.
You can use Transaction IB81 (Functional Lo-cation BOM Change Documents) to displaychange documents related to a Functional Lo-cation BOM. You can use Transaction IB80(Change Documents for Equipment BOM) todisplay changes documents related to anequipment BOM.
You can use this report to display a listing ofwork centers. If you want a listing of workcenters in a hierarchy, then in the selectionscreen, enter data in the fields grouped underthe Selection by Hierarchy group.
You can use this report to get a listing of workcenters and the cost centers to which they areassigned.
CS03 Display Material BOM
CS14 BOM Comparison
CS15 Single-Level Where-Used List – Material
CS20 Mass Changes – Material Selection
CS80 Change Documents for Material BOM
CR05 Work Center List
CR06 Work Center Assignment to Cost Center
Plant Maintenance (PM) 8
313
Information about technical objects to bemaintained can also exist in the form of elec-tronic documents (for example, maintenancemanuals, instructions, pictures). Documentsare managed using the SAP logistics commoncomponent “document management system.”These documents are associated with andlinked to various Plant Maintenance (PM) ob-jects. You can use this transaction to create adocument info record. A document info re-cord stores all the data required to processand manage a document. For the specifieddocument number and document type, youcan use Transaction CV03N (Display Docu-ment) to display the document info recordand original application files that belong tothe document.
You can use this transaction to edit and makechanges to a document. Prior to making changesto a document, the following must be consid-ered:
� If the document is in “Locked” or “Original in Process” status, many of the fields in the document cannot be changed. Hence, the document status must be changed prior to making edits to the document info record.
� All changes to the document will generate a workflow event.
� Changes to the document are not histori-cal. If you prefer to maintain historical sta-tus, creating a newer version of the docu-ment is recommended.
� If preferred, during customizing of the cross-application components, you can specify whether change documents must be created for all changes to the document info record.
For the specified document number and doc-ument type, you can use this transaction todisplay the document info record and originalapplication files that belong to the document.
You can use this transaction to search and finddocuments. You can use any of the followingsearch criteria: data from the document inforecord, text elements, signature data, and soon. You can create a task list to describe a se-quence of individual maintenance activitiesthat must be performed at regular intervals.The next few transactions describe how tocreate, maintain, and display equipment tasklist, general task list, and functional locationtask list.
You can use this transaction to create an equip-ment task list. In the initial screen, enter theequipment and, if required, an existing profilenumber. If an equipment task list exists, theTask List overview screen is displayed. If notask list exists, the General Overview screen isdisplayed. Using the equipment task list, youcan define and manage maintenance tasks foryour equipment in one central place. The equip-ment task list can be used to prepare mainte-nance plans and orders as well. You can com-bine several task lists into one group. Within thegroup, a unique sequential number called agroup counter is assigned to each individualequipment task list.
Spare parts and material components can alsobe included in maintenance task lists. The ba-sis for component parts list is the relevantmaintenance bill of materials (BOM) definedin the Assembly field on the task list header. Ifno assembly is referenced on the task list,
CV01N Create Document
CV02N Change Document
CV03N Display Document
CV04N Find Document
IA01 Create Equipment Task List
Plant Maintenance (PM)8
314
then only items with material category L(stock items) can be included as components.
You can use this transaction to edit and main-tain an equipment task list.
You can use this transaction to display anequipment task list. This is a display-onlyscreen, and no maintenance can be per-formed.
You can use this transaction to create a gen-eral maintenance task list. You can create anew general task list by entering an existinggroup number or an existing profile number.You can also create a new general task list bynot entering any data. For the entered data, ifa general task list exists, the Operations
Overview screen is displayed. If no generaltask list exists, then the General Overview
screen is displayed.
General maintenance task lists do not refer toany specific technical object and are insteadused for general maintenance tasks. In thegeneral maintenance task list, you can defineand manage the sequence of maintenancetasks centrally and use them for work sched-uling as well. Within each group, you can cre-ate several individual general task lists.Within the group, a unique sequential num-ber called a group counter is assigned to eachindividual general maintenance task list.
You can use this transaction to edit and main-tain a general maintenance task list.
You can use this transaction to display a generaltask list. This is a display-only view, and nomaintenance can be performed on the task list.
You can use this transaction to generate a list-ing of maintenance task lists or service plans.The report output will display the task listtype, maintenance strategy (if assigned), tasklist group, group counter, and description ofthe task list. From the report output, you cannavigate to the Task List Details screen,where you can edit and maintain the task lists.
You can use this transaction to display a listingof maintenance task lists or service plans. Thedifferent task list types are functional locationtask list, equipment task list, and general tasklist. The report displays the task list type, tasklist group, group counter, task list description,and, where available, maintenance strategy.From the report output, you can navigate tothe Task List Details screen to get an over-view of the task list. This is a display-onlyview, and no maintenance can be performed.
You can use this transaction to generate a mul-tilevel listing of maintenance task lists or ser-vice task lists. In the selection screen, you canselect which objects must be displayed in thelisting. Where required, you can generate thislisting independently of operations and dis-play operations and suboperations separately.
You can use this transaction to create a func-tional location task list. In the initial screen,
IA02 Change Equipment Task List
IA03 Display Equipment Task List
IA05 Create General Task List
IA06 Change General Maintenance Task List
IA07 Display General Task List
IA08 Change PM Task Lists
IA09 Display Task Lists
IA10 Display Task Lists (Multilevel)
IA11 Create Functional Location Task List
337
Chapter 9
9 Quality Management (QM)
You can use this transaction to generate a us-age listing of the task lists where a productionresource/tool (PRT) is used. In the report out-put, you can select a specific task list: to dis-play the PRT general views, use the menupath Go to � Detail; to display the PRT over-views, use the menu path Go to � Choose.
Users can access this transaction only if theparameter ACC_MODE is set to “x” in the userprofile. If this parameter is not set for theuser, you can select an overview variant thatdetermines what task list objects and fields ofthe objects are displayed to the user.
You can use this transaction to start the prod-uct structure browser. For the specified object,this report displays an overview of the prod-uct-defined data. You can navigate within theproduct structure, access data, and performthe required functions. For example, the fol-lowing tasks can be performed in the productstructure browser: you can change and main-tain the statuses or maintain the master data ofthe product from a central point.
A production resource/tool (PRT) is an objectthat denotes a moveable operating resourceused in Plant Maintenance (PM). You can usethis transaction to manually create a new PRTmaster record. You can also create a new PRTmaster record by copying an existing PRT.Enter an existing PRT in the field Copy from
Prod. resource/tool and click on the Basic
Data button. In the displayed dialog box,you can select what components you want to
copy and click on the Copy from icon. TheCreate Production Resource/Tool: Basic
Data screen is displayed, where you canmake the required changes and save the newPRT record. You can create language-depen-dent short text by following the menu pathExtras � Short text.
You can use this transaction to generate a list-ing of service and maintenance orders. Fromthe report output, you can select a specific or-der and navigate to the order general datascreen to get an overview or to make changesto the general data. The report output displaysthe order number, order type, basic start date,and short text of the order.
See Transaction DSAL for details.
See Transaction CT04 for details.
You can use this transaction to create charac-teristics, which describe the properties of ob-jects. Characteristics are created centrally andthen assigned to classes. When a characteristicis assigned to a class, you can overwrite thecharacteristic. In the initial screen, you canenter the change number, if you plan to createa characteristic using engineering changemanagement. You are required to maintainthe basic data of the characteristics; all otherdata, such as values, are optional. You can alsocreate a new characteristic by copying an ex-
CA70 PRT Where-Used Lists
CC04 Display Product Structure
CF01 Create Production Resource/Tool
CF25 PRT: Usage of PRT Master in PM Order
CJ00 Digital Signature – Find
CT01 Create Characteristics
CT04 Characteristics
Quality Management (QM)9
338
isting characteristic. Click on the Create by
copying icon and enter the name of the char-acteristic that you wish to copy. SAP recom-mends using Transaction CT04 to create char-acteristics rather than using TransactionCT01.
You can use this transaction to create a newinspection plan, to create a new task list andassign maintenance packages to it, or to trans-fer Quality Management (QM) data to an SAPsystem. You can perform data transfers ofmaster inspection characteristics, inspectionmethods, and inspection plans.
You can use this transaction to display the dig-ital signatures log. Using the log, you can getan overview and analyze all activities thatwere performed during the signature process.The following data are displayed in the log:for each signature, the header data includesthe date, time, signatory, number of log mes-sages, and reason for the signature. For the se-lected signature record, the signature stepsand other signature data are displayed at thebottom of the screen. Messages displayed inthe log are marked according to the type (in-formation, warning, error, or abandon).
As per SAP Note 586914 – Workaround forprinting signature via CJ00 or DSAL, SAP rec-ommends using Transaction DSAL (DigitalSignature – Logs) instead of Transaction CJ00(Digital Signature – Find).
You can use this transaction to schedule amaintenance plan, which the system will useto generate maintenance call objects, such asmaintenance orders or service orders, for thedefined cycles.
For the specified strategy, you can use this re-port to generate a listing of maintenanceplans in which the strategy is used. The reportoutput displays the maintenance plan, shorttext, strategy, and number of maintenanceitems. From the report output, you can navi-gate to the detail screen of the maintenanceplan.
You can use this report to generate a listing ofmaintenance plans in the system. The reportoutput displays the maintenance plan num-ber, short text and, where available, mainte-nance strategy. From the report output, youcan navigate to the detail screen of the main-tenance plan or the maintenance call objectsfor a maintenance plan.
You can use this report to generate a schedul-ing overview of the maintenance plans in agraphical format. The graph displays themaintenance call date, equipment, and main-tenance call objects for the maintenanceplans. You will be able to simulate changes tothe maintenance plans in the graph as well.
You can use this transaction to generate a list-ing of a scheduling overview for maintenanceplans. The report output contains the mainte-nance item number, maintenance plan, main-tenance strategy, short text of maintenanceitem, call number, and date on which themaintenance call object was generated (listedin the report as start date). From the report,you can navigate to get a detailed overview ofa maintenance plan or maintenance item.
CWBQM
QM – Engineering Workbench
DSAL Digital Signature – Logs
IP10 Schedule Maintenance Plan
IP14 Where-Used List by Strategy
IP16 Display Maintenance Plan
IP19 Maintenance Scheduling Overview
IP24 Scheduling Overview List Form
Quality Management (QM) 9
339
From the report output, you can also display agraphical scheduling overview.
For the specified search filter, you can use thistransaction to select and process notificationsthat exist in the system. To maximize perfor-mance, specifying a layout in the selectionscreen is a recommended best practice.
For the specified search filter, you can thistransaction to select and process tasks for no-tifications that exist in the system. To maxi-mize performance, specifying a layout in theselection screen is a recommended best prac-tice.
You can use this transaction to process spe-cific tasks in a notification. You can processimmediate tasks and corrective tasks as well.In the Process Task screen, you can do thefollowing actions (select menu Task or thedisplayed push buttons): release a task, com-plete a task, set a task as successful, and setuser status. In the Process Task screen, youcan also display the associated notification(the notification that contains the task), asso-ciated objects (reference objects specified inthe notification), or the action log. In the ini-tial screen, the notification number and tasknumber are required fields.
You can use this transaction to create a simpli-fied notification. Based on the Customizingsettings, the notification type is displayed inthe Create Notification initial screen. In theCreate Notification screen, you can performthe following functions: make changes to the
current notification, display a notification orswitch to extended notification processingmode, change the processing status of the no-tification, approve or refuse approval to a no-tification, set user default values, change noti-fication address, and display the current cata-log profile assigned to the notification type.
For the specified Controlling (CO) productionorder or Quality Management (QM) order,you can use this transaction to maintain thegeneral data of the order and verify the de-fault settlement rule as well. Hence, when youcreate a CO production order, a settlementrule is generated automatically by the system.
You can use this transaction to generate a ma-terial withdrawal posting, post a material is-sue, or post the shipment of goods to a cus-tomer. When you post a goods issuance, thewarehouse stock will be reduced simultane-ously.
You can use this report to get an overview ofthe remaining shelf life of batches. In the se-lection screen, if you do not enter a remainingshelf life, the report will display batches withpast expiration dates. For batches to be in-cluded in this report, the shelf life expirationdate/production date must be maintained inthe batch master record.
For the specified analysis period, you can usethis report to get an overview of mean value ofquality score, percentage rejection rate, per-centage skip rate, and lead time of the numberof the inspection lot that is generated. Similar
IQS8 Worklist: Notifications (General)
IQS9 Worklist: Tasks (General)
IQS12 Process Task
IQS21 Create Notification – Simplified View
KKF2 Change CO Production Order
MB1A Goods Withdrawal
MB5M Shelf Life List
MCXA QMIS – Material Analysis (Lot Overview)
Quality Management (QM)9
340
data are displayed against the respective in-spection types as well. You can drill down thereport based on material, plant, quality score,or month as well. You can generate a similarreport based on quantities (rather than per-centages) by executing Transaction MCXI(QMIS – Material Analysis [Quantities]).
For the specified analysis period, you can usethis report to display the notification status atthe plant and material level. The report dis-plays the total number of notifications, notifi-cations outstanding, notifications being pro-cessed, notifications completed, and notifica-tions reset. Analyses about tasks are alsodisplayed. Similar data are displayed againstthe respective notification types as well.
This transaction is used to create and maintainthe internal number range for inspectionplans.
This transaction is used to create and maintainthe internal number range for reference oper-ation sets.
You can use this transaction to get an over-view of the number of outstanding corrective/preventive actions, display all audits, and dis-play all question lists. Using this report, youcan also get a listing of all audit plans andtheir valid time periods. In the selectionscreen, you can select which audit componentyou would like to search for and get an over-
view of. In the report listing, you can select aspecific record and display its general data.
You can use this transaction to perform thefollowing actions: process an audit component(including creating a new audit component,searching an existing audit component, delet-ing a selected audit component, or maintain-ing an existing audit component); process anaudit plan; process a question list; execute anaudit; process corrective/preventive actions;and assign documents to an audit component.
You can use this transaction to display the SAP
Easy Access: Quality Management menu. TheSAP Easy Access menu tree structure displaysthe transactions related to Quality Manage-ment (QM).
You can use this transaction to display theSAP Easy Access: Quality Inspection menu.The SAP Easy Access menu tree structure dis-plays the transactions related to Quality In-spection.
You can use this transaction to manually cre-ate a new inspection lot. For the specified in-spection lot, you can use this transaction todisplay the inspection lot or to edit and main-tain the inspection lot. The other processingthat can be performed are blocking/unblock-ing an inspection lot, cancelling an inspectionlot, creating a new batch in an inspection lot,performing stock transfers in an inspectionlot, making corrections to inspection lotquantities where required, creating a newQuality Management (QM) order, and ap-
MCXV QMIS – Material Analysis Overview Quality Notification
OQ62 Number Ranges for Inspection Plans
OQ63 Number Ranges for Reference Operation Sets
PLM_AUDITMONITOR Start Audit Monitor
PLMD_AUDIT
Audit Management
Q000 Quality Management
QA00 Quality Inspection
QA01 Create Inspection Lot
7
Contents
Introduction ..................................................................................................... 9
1 Financial Accounting (FI) ........................................................... 17
2 Controlling (CO) ........................................................................ 73
3 Inventory Management (IM) ..................................................... 113
4 Materials Management (MM) .................................................. 141
5 Warehouse Management (WM) ............................................... 189
6 Production Planning (PP) .......................................................... 217
7 Sales and Distribution (SD) ....................................................... 275
8 Plant Maintenance (PM) ........................................................... 311
9 Quality Management (QM) ....................................................... 337
10 Project System (PS) ................................................................... 355
11 Human Capital Management (HCM) ........................................ 381
11.1 Organizational Management (OM) ................................................ 38111.2 Personnel Administration .............................................................. 39011.3 Benefits ......................................................................................... 39311.4 Time Management ........................................................................ 39911.5 Personnel Development ................................................................ 41011.6 Enterprise Compensation Management (ECM) ............................... 41311.7 SAP Learning Solution (LSO) .......................................................... 41811.8 Travel Management ....................................................................... 42611.9 Performance Management ............................................................. 43611.10 Succession Management ............................................................... 43811.11 Payroll ........................................................................................... 43911.12 SAP SuccessFactors ........................................................................ 45411.13 Others ........................................................................................... 459
12 Basis System .............................................................................. 461
The Authors ............................................................................................. 493
Index ............................................................................................................... 495
495
Index
1KE4, 731KEK, 732KEU, 732KEV, 736KEA, 737KE1, 737KE2, 739KE9, 73
A
AB01, 17AB02, 17AB03, 17AB08, 17ABAA, 17ABAON, 17ABAP – Extended Program Check (SLIN), 475ABAP Dictionary Display (SE12), 472ABAP Dictionary Maintenance (SE11), 472ABAP Dump Analysis (ST22), 486ABAP Editor (SE38), 473ABAP Keyword Documentation
(ABAPDOCU), 461ABAP Reporting (SA38), 468ABAP/4 Repository Information System
(SE15), 472ABAPDOCU, 461ABAVN, 17ABAW, 18ABC Analysis for Cycle Counting (MIBC), 137ABC Analysis, Requirement-Based
(MC41), 127ABC Analysis, Usage-Based (MC40), 127ABC Indicators, Define (OIAA), 334ABGF, 18ABGL, 18ABMA, 18ABNAN, 18ABNE, 18ABNK, 18Absence Data: Calendar View (PT90), 408
Absence Data: Multiple Employee View (PT91), 408
Absence Quota Information, Display (PT_QTA10), 406
Absence Records, Revaluation of (PT_UPD00), 406
ABSO, 18ABST2, 19ABT1N, 19ABUMN, 19ABZE, 19ABZON, 19ABZP, 19ABZU, 19Access Automatic Cash Concentration Using a
Program (FF74), 55Access: Create/Change Curriculum
(LSO_PVEC_CREATE), 423Account Analysis, Customer: Initial Screen
(FD11), 52Account Assignment Manual (F.53), 28Account Assignment Model (FKMT), 59Account Assignment, List Display of Purchase
Requisitions by (ME5K), 158Account Assignment, Purchasing Documents
per (ME2K), 150Account Assignment, Purchasing Documents
per (ME3K), 154Account Balance and Claims
(HRBENUS02), 397Account Balances, G/L (F.08), 24Account Changes, Customer (FD04), 50Account Changes, Customer (XD04), 70Account Changes, Vendor (FK04), 57Account Changes, Vendor (XK04), 71Account Group, Change (XD07), 70Account Group, Change (XK07), 71Account Interest Scale, G/L (F.52), 28Account List, G/L (F.09), 24Account Statements, Periodic (F.27), 26Accounting Analyses, HR PAY (PR11), 428Accounting Data, Post (PRRW), 431Accounting Documents for Material
(MR51), 139
496
Index
Accounting Editing Options (FB00), 42Accounting, Release Billing Documents for
(VFX3), 294Accounts, Chart of (F.10), 24Accrual/Deferral Doc., Enter: Header Data
(FBS1), 46Accrual/Deferral Documents, Reverse
(F.81), 29Acquisition from Affiliated Company
(ABZP), 19Acquisition from In-House Production
(ABZE), 19Acquisition from Purchase w. Vendor (F-
90), 36Acquisition Tax, Display, (F.19), 25Act. Indirect Acty Alloc.: Overview
(KSC6), 107ACTEXP_APPR_LITE, 426Action for Requirement Profiles (PQ17), 388Actions for Business Event Group (PQ09), 388Actions for Business Event Type (PQ04), 387Actions for Company (PA15), 381Actions for External Instructor (PQ19), 389Actions for External Person (PQ08), 388Actions for Job (PQ03), 387Actions for Location (PQ06), 387Actions for Organizational Unit (PQ10), 388Actions for Position (PQ13), 388Actions for Resource (PQ07), 388Actions for Resource Room (PQ18), 389Actions for Resource Type (PQ12), 388Actions for Task (PQ14), 388Actions for Training Program (PQ02), 387Actions for Work Center (PQ01), 387Actions, Fast Entry for (PA42), 392Actions, Personnel (PA40), 391Actions, Personnel (PRMM), 393Activate Availability Control (KO30), 99Activate Cost Estimate for Production Lot
(CKW4), 227Activate Planned Changes for a Key Date
(MM13), 173Activate Production Lot Cost Estimate
(CKW4), 76Activate/Deactivate SAP Learning Solution
(LSO_ACTIVATE), 418
Activation of Employee’s Planned Compensation Data (HRSFI_COMP_DATA_ACT), 455
Active IDoc Monitoring (WE06), 491Active Parameters, Display (TU02), 490Active RF Monitor (LRF1), 198Active, Garnishment – Pending
(PC00_M10_IPIT1), 444Active->Inactive, Garnishment
(PC00_M10_IPIT0), 444Activities per Payroll Period, Area Menu –
Subsequent (PC00_M99_PAP), 448Activities per Storage Type (LX10), 212Activities, Change (IW64), 332Activities, Display (IW56), 332Activity Allocation – Participation
(LSO_PV18), 422Activity Allocation, Direct, Display
(KB23N), 82Activity Allocation, Direct, Enter (KB21N), 82Activity Allocation, Direct, Reverse
(KB24N), 82Activity Input Planning, Change (KP06), 102Activity Input Planning, Display (KPF7), 104Activity Input, Display (KP07), 102Activity Input, Planning (KPF6), 104Activity Inputs, Change (CJR2), 371Activity Inputs, Display (CJR3), 371Activity List, Change (QM16), 348Activity Monitor, Operating System
(OS06N), 465Activity Monitoring, Remote Operating
System (OS07), 465Activity Monitoring, Remote Operating
System (OS07N), 465Activity Report, Create (IW55), 331Activity Type Group, Change (KLH2), 97Activity Type Group, Create (KLH1), 96Activity Type Group, Display (KLH3), 97Activity Type Price Report (KSBT), 106Activity Type, Change (KL02), 96Activity Type, Create (KL01), 96Activity Type, Delete (KL04), 96Activity Type, Display (KL03), 96Activity Type, Display Change Documents
(KL05), 96
Index
497
Activity Type/Price Planning, Change (KP26), 102
Activity Type/Price Planning, Display (KP27), 103
Activity Types, Delete (KL14), 96Activity Types, Display (KL13), 96Activity Types, Trip, Define
(S_AHR_61000689), 434Actual Assessment Cycle, Change
(FAGLGA12), 38Actual Assessment Cycle, Change
(KSU2N), 108Actual Assessment Cycle, CO-PA, Change
(KEU2), 89Actual Assessment Cycle, CO-PA, Create
(KEU1), 88Actual Assessment Cycle, CO-PA, Delete
(KEU4), 89Actual Assessment Cycle, CO-PA, Execute
(KEU5), 89Actual Assessment Cycle, Create
(FAGLGA11), 38Actual Assessment Cycle, Create (KSU1N), 108Actual Assessment Cycle, Delete
(FAGLGA14), 38Actual Assessment Cycle, Delete (KSU4N), 108Actual Assessment Cycle, Display
(FAGLGA13), 38Actual Assessment Cycle, Display
(KSU3N), 108Actual Assessment Cycle, Execute
(FAGLGA15), 38Actual Assessment Cycle, Execute
(KSU5N), 108Actual Assessment Overview (FAGLGA16), 39Actual Cost Line Items for Cost Centers,
Display (KSB1), 105Actual Cost Line Items for Cost Objects,
Display (KKCS), 92Actual Cost Line Items for Orders, Display
(KOB1), 100Actual Cost Line Items for Orders, Display
(KRMI), 104Actual Cost Line Items, Project, Display
(CJI3), 369Actual Cost Splitting (KSS2), 108
Actual Data from LIS Activity-Dependent Statistical Key Figures, LIS, Transfer (KVD5), 112
Actual Data from LIS Activity-Independent Statistical Key Figures, LIS, Transfer (KVA5), 111
Actual Data, Single Entry of, Control (LT63), 209
Actual Distribution Cycle, Change (FAGLGA32), 40
Actual Distribution Cycle, Change (KSV2N), 109
Actual Distribution Cycle, Create (FAGLGA31), 39
Actual Distribution Cycle, Create (KSV1N), 109
Actual Distribution Cycle, Delete (FAGLGA34), 40
Actual Distribution Cycle, Delete (KSV4N), 109
Actual Distribution Cycle, Display (FAGLGA33), 40
Actual Distribution Cycle, Display (KSV3N), 109
Actual Distribution Cycle, Execute (FAGLGA35), 40
Actual Distribution, Execute (KSV5), 109Actual Distribution: Overview
(FAGLGA36), 40Actual Distribution: Overview (KSV6N), 110Actual Indirect Activity Allocation, Change
Cycle for (KSC2), 106Actual Indirect Activity Allocation, Create
Cycle for (KSC1), 106Actual Indirect Activity Allocation, Delete
Cycle for (KSC4), 106Actual Indirect Activity Allocation, Display
Cycle for (KSC3), 106Actual Indirect Activity Allocation, Execute
Cycle for (KSC5), 106Actual Indirect Activity Allocation: Overview
(KSC6), 107Actual Interest Calculation; Project Collective
Processing (CJZ1), 372Actual Interest Calculation; Project Individual
Processing (CJZ2), 372Actual Line Items, Profit Center (KE5Z), 88
498
Index
Actual Overhead Calculation Collective Processing (CO43), 79
Actual Overhead Calculation: Order (KGI2), 89
Actual Overhead Calculation: Production/Process Orders (CO43), 233
Actual Overhead Calculation: Project/WBS Element/Network (CJ44), 361
Actual Overhead Calculation: Projects/WBS Elements/Networks (CJ45), 361
Actual Overhead: Calculation: Sales Order (VA44), 284
Actual Payment Line Items, Project, Display (CJIA), 370
Actual Periodic Reposting Cycle, Change (KSW2), 110
Actual Periodic Reposting Cycle, Create (KSW1), 110
Actual Periodic Reposting Cycle, Delete (KSW4), 110
Actual Periodic Reposting Cycle, Display (KSW3), 110
Actual Periodic Reposting Cycle, Execute (KSW5), 111
Actual Price Calculation (KSII), 107Actual Report (FMR3), 61Actual Results Analysis: Sales Orders
(KKAK), 91Actual Settlement: Cost Object (KK88), 90Actual Settlement: Cost Object Collective
(KK89), 90Actual Settlement: Order (KO88), 99Actual Settlement: Orders (KO8G), 99Actual Settlement: Product Cost Collector
(KK87), 90Actual Settlement: Production/Process Orders
(CO88), 234Actual Settlement: Project/WBS Element/
Network (CJ88), 362Actual Settlement: Projects/WBS Elements/
Networks (CJ8G), 363Actual Settlement: Sales Orders (VA88), 285Actual to Plan, Copy (KO15), 98Actual to Plan, Copy (KP98), 103Ad Hoc Cost Estimate, Edit (CKECP), 77Add Single Plan (IP41), 325Add Strategy-Controlled Plan (IP42), 325
Addition to Storage Unit, Manual (LT08), 203Additional Data, List Entry of (PA62 ), 392Additive Cost, Change (CK75N), 75Additive Cost, Create (CK74N), 74Additive Cost, Display (CK76N), 75Add-On Installation Tool (SAINT), 468Address Maintenance: Initial Screen \", 163Ad-Hoc Query, Call (PAAH), 393Adjust Compensation Process Records
(PECM_ADJUST_0759), 414Adjusting Requirements, Reorganizing
Independent Requirements (MD74), 263Adjustment Sales-Purchasing (Selection Using
Organizational Data) (VA08), 281Adjustment, Subsequent (MIGO_GS), 138Administer SAP Licenses (SLICENSE), 475Administrate Update Records (SM13), 476Administration of Secure Storage
(SECSTORE), 454Administration Tool, TREX
(TREXADMIN), 490Administration, Archive (SARA), 468Administration, Central User (SCUA), 470Administration, Central User (SCUM), 471Administration, Client (SCC4), 469Administration, Data Medium (FDTA), 439Administration, IGS (SIGS), 474Administration, SAP Connect (SCON/
SCOT), 470Administration, Spool (SPAD), 482Administration, TemSe (SP12), 482Administration, Update Program (SM14), 476Administrator, Cost Center Report
(PC00_MNA_CC_ADM), 450Administrator: Appraisal Document
(LSO_EVAL_ADMIN), 418Advance, Per Payroll Period
(PC00_M10_CDTB), 442Advances, Trip (PR03), 427Advices, Print Zero Net
(PC00_M10_RFFOAVIS), 445AFAB, 20AFAR, 20AFBP, 20Affiliated Company, Acquisition from
(ABZP), 19Aggregate Collective Backflush (MF70), 266
First-hand knowledge.
Venki Krishnamoorthy, Martin Murray, Norman Reynolds, and Peter Teesdale
SAP Transaction Codes648 Pages, 2016, $49.95 ISBN 978-1-4932-1366-5
www.sap-press.com/4070
We hope you have enjoyed this reading sample. You may recommend or pass it on to others, but only in its entirety, including all pages. This reading sample and all its parts are protected by copyright law. All usage and exploitation rights are reserved by the author and the publisher.
Venki Krishnamoorthy is an author, speaker, and an SAP SuccessFactors, SAP ERP HCM consultant. Venki is currently an independent consultant, and has over 15 years of expe-rience as a solution architect, functional lead, and project manager/program manager in the HCM space.
Dr. Peter W. Teesdale is an independent SAP consultant in supply-chain management; he earned a PhD in industrial en-gineering from the University of Witwatersrand in Johannes-burg, South Africa and is a registered Professional Engineer with the Engineering Council of South Africa (ECSA).
Martin Murray was a respected Logistics consultant and worked with IBM for more than 15 years. He joined the computer industry upon his graduation from Middlesex Uni-versity in 1986.
Norman Reynolds is an information technology professional with a passion for process improvement. An expert in SAP functionality, tools, and management techniques required to create first-class process designs quickly and consistently, Norman specializes in helping companies develop practical
solutions to resolve the difficult business process issues that come with complex organizations.
Top Related