| ||
CF01 1. Prod.resources/tools: Is a resources required to do some operations such as tools, crane or other instruments for quality inspection. (M) 2. Press enter to continue. 1. Description: Explain about the PRT you want to create. 2. Status: The PRT status, e.g. 01 (Created on), 02 (Released for PRT usage planning), 03 (Released for production) 3. Task list usage: Explain what task list is used for the PRT. 000 no task list categories 001 only routings 002 only inspection plans 003 only networks 004 only maintenance task lists 005 Production rate planning 007 Only rate routings 008 Master recipe + Process Order 009 All task list types 010 Rough-cut planning 4. Base unit of measure: The unit of measure for the PRT. Click “Default” after you have filled the required information. Click enter and CTRL+S to save the PRT Master. |
Friday, April 15, 2011
SAP PM - PRT table creation
SAP SD Tables
Here you can find a list of SAP SD tables for various TCODE, I hope it will be useful for you.
Table Table Description
VBAK Sales Document: Header Data
VBAP Sales Document: Item Data
VBKD Sales Document: Business Data
VBPA Sales Document: Partner
VBFA Sales Document Flow
TROLZ Routes: Determination in Deliveries
KNA1 General Data in Customer Master
KNVV Customer Master Sales Data
KNVP Customer Master Partner Functions
KNKK Customer master credit management: Control area data
KNKA Customer master credit management: Central data
KNKKF1 Credit Management: FI Status Data
KNKKF2 Credit Management: Open Items by Days in Arrears
LIKP SD Document: Delivery Header Data
LIPS SD Document: Delivery: Item data
VBRK Billing Document: Header Data
VBRP Billing Document: Item Data
KONP Conditions (Item)
KONV Conditions (Transaction Data)
VBUK Sales Document: Header Status and Administrative Data
VBUP Sales Document: Item Status
KNBK Customer Master (Bank Details)
TKUKL Customers: Customer Classifications
T016 Industries
TBRC Industry Code (Customer Master)
TVGF Legal Status (Customer Master)
KNVA Customer Master Loading Points
KNVK Customer Master Contact Partner
T502T Marital Status Designators
T171 Customers: Sales Districts
TVBUR Organizational Unit: Sales Offices
TVBVK Organizational Unit: Sales Groups per Sales Office
T151 Customers: Customer Groups
TCURC Currency Codes
TCURV Exchange rate types for currency translation
TVKD Customer Pricing Procedures
T188 Conditions: Groups for Customer Classifications
T189 Conditions: Price List Categories
TVSD Customers: Statistics groups
TPAR Business Partner: Functions
Creating Search Help In SAP
Today we will learn how to create search help in SAP, so what is search help? Search help is an object that we create using tcode se11, it’s one of the data dictionaries object in SAP. Using search help we can make a search to a particular data much easier, because it will create a pop up window that contains all the data related with our search.
There are 2 types of search help, the first one is elementary and the second one is collective, elementary search help usually only requires one table to create it, while the collective search help is a collection of more than one search helps.
Now we want to create an elementary search help.
Let’s execute tcode se11. Choose the Search help option and Type in the search help name that we want to create, in this example I’ll name it as ZSEARCHHELP, after that click create button.
In the popup window selection, choose the Elemetary search help, click ok.
Type in the search help description, in this case I named it as Customer search help.
Click the selection method button and choose search for database tables because we want to display data from the customer table.
Now type the KNA1 table on the given textbox.
Now you only need to determine which columns from the KNA1 table that you want to display in your search help, in this case I want to display 3 columns, KUNNR, NAME1, STRAS. You also have to set the IMP, EXP, LPOS, SPOS columns, just do it as the pictures illustrated below.
Save, Activate and test (F8) Your search help is ready to use.
Insert Update and Delete Row In Transparent Table
Insert Update and Delete Row In Transparent TableHere’s a sample code to insert, update and delete row in transparent table. This syntax is relatively simple, remember that this is a transparant table and not internal table so the changes will be directly reflected on your tables. But first you have to create a transparent table first. Here’s the Abap code sample. REPORT Z_TransparentTable_SQL. data wa type ztable1. START-OF-SELECTION. "Insert new row to transparant table. wa-custid = '0001'. wa-custnm = 'ABC'. insert ztable1 from wa. "Modify data in transparant table "Using modify statement, the system will "automatically search the index key "if found similar key then it will update "the value and not adding new row wa-custid = '0001'. wa-custnm = 'CDE'. Modify ztable1 from wa. "delete row from transparant table wa-custid = '0001'. delete ztable1 from wa. |
SAP Authorization Object Tables
SAP Authorization Object Tables List
Here’s a list of SAP authorization Object tables for your reference.
You can execute TCODE SE11 and see more details of each table, such as column description, field type, etc.
Table Name Description
TOBJ Authorization Objects
TACT Activities which can be Protected
TACTZ Valid Activities for each authorization object
TDDAT Maintenance Areas for tables
TSTC SAP Transaction Codes
TPGP ABAP/4 Authorization groups
USOBT Relation transaction > Authorization Object
USOBX Check table for table USOBT
USOBT_C Relation Transaction > Auth. Object (Customer)
USOBX_C Check table for table USOBT_C
You can execute TCODE SE11 and see more details of each table, such as column description, field type, etc.
Table Name Description
TOBJ Authorization Objects
TACT Activities which can be Protected
TACTZ Valid Activities for each authorization object
TDDAT Maintenance Areas for tables
TSTC SAP Transaction Codes
TPGP ABAP/4 Authorization groups
USOBT Relation transaction > Authorization Object
USOBX Check table for table USOBT
USOBT_C Relation Transaction > Auth. Object (Customer)
USOBX_C Check table for table USOBT_C
SAP Purchasing Tables
SAP Purchasing Tables
Here’s the list of SAP Purchasing Tables, use this as your reference. Use TCODE SE11 for more details of the table.
Table Name | Table Description |
A501 | Plant/Material |
EBAN | Purchase Requisition |
EBKN | Purchase Requisition Account Assignment |
EKAB | Release Documentation |
EKBE | History per Purchasing Document |
EKET | Scheduling Agreement Schedule Lines |
EKKO | Purchasing Document Header |
EKPO | Purchasing Document Item |
IKPF | Header- Physical Inventory Document |
ISEG | Physical Inventory Document Items |
LFA1 | Vendor Master (General section) |
LFB1 | Vendor Master (Company Code) |
NRIV | Number range intervals |
RESB | Reservation/dependent requirements |
T024 | Texts for Purchasing Document Types |
T156 | Movement Type |
T157H | Help Texts for Movement Types |
•SAP MM Tables
SAP MM Tables – List Of MM Tables
Here’s the list of SAP Material Management (MM) tables, use this as your reference. You can use TCODE SE11 to see more details information of the table.
Here’s the list of SAP Material Management (MM) tables, use this as your reference. You can use TCODE SE11 to see more details information of the table.
Table Name | Table Description |
EINA | Purchasing Info Record- General Data |
EINE | Purchasing Info Record- Purchasing Organization Data |
MAKT | Material Descriptions |
MARA | General Material Data |
MARC | Plant Data for Material |
MARD | Storage Location Data for Material |
MAST | Material to BOM Link |
MBEW | Material Valuation |
MKPF | Header- Material Document |
MSEG | Document Segment- Material |
MVER | Material Consumption |
MVKE | Sales Data for materials |
RKPF | Document Header- Reservation |
T023 | Mat. groups |
T024 | Purchasing Groups |
T156 | Movement Type |
T157H | Help Texts for Movement Types |
•SAP PM Tables
SAP PM Tables – List Of SAP PM Tables
Here the list of SAP Plant Maintenance (PM) Tables, use this as your reference and you can also use TCODE SE11 to see more detail information of the table.
Here the list of SAP Plant Maintenance (PM) Tables, use this as your reference and you can also use TCODE SE11 to see more detail information of the table.
|
SAP Finance Tables
SAP Finance Tables – List of SAP Finance TablesHere’s the list of SAP Finance tables, use this list as your reference. You can also use TCODe Se11 to see more information about the table.
|
SAP Tables
Table maintenance generator in SAP:
Today I want to teach you how to create table maintenance generator in SAP, if you never heard about table maintenance generator, it’s actually used to maintain table values by using TCODE SE54 and after you create the table maintenance then you can display the values by using SM30.
Follow these steps to create table maintenance generator.
1. Execute TCODE SE54.
2. Enter the table name. Select “Generated Objects.” Click Create.
3. Click “Yes“
4. Now enter these following settings, just like shown in pictures below.
5. Select “Generated Objects > Create“.
Follow these steps to create table maintenance generator.
1. Execute TCODE SE54.
2. Enter the table name. Select “Generated Objects.” Click Create.
3. Click “Yes“
4. Now enter these following settings, just like shown in pictures below.
5. Select “Generated Objects > Create“.
SAP Table Maintenance Display
In previous tutorial, you’ve learned how to create table maintenance generator by using TCODE SE54, today you will learn how to create the table display that utilizes TCODE SM30 to maintain the table values.
1. Execute TCODE SE93.
Enter the TCODE name, start with Z or Y.
Choose “Transaction with parameters (Parameter transaction).
Click “OK”
2. Now you need to fill in these values:
Default Values For:
-Transaction: SM30
-Check “Skip Initial Screen”
Classification:
-Check “Inherit GUI attributes”
Default Values:
VIEWNAME -> Transparent Table Name
UPDATE -> X
See below picture for reference.
3. Click the Save button.
4. Execute the TCODE you just created. Now you can maintain the tables values, such as Adding new entries, delete row.
1. Execute TCODE SE93.
Enter the TCODE name, start with Z or Y.
Choose “Transaction with parameters (Parameter transaction).
Click “OK”
2. Now you need to fill in these values:
Default Values For:
-Transaction: SM30
-Check “Skip Initial Screen”
Classification:
-Check “Inherit GUI attributes”
Default Values:
VIEWNAME -> Transparent Table Name
UPDATE -> X
See below picture for reference.
3. Click the Save button.
4. Execute the TCODE you just created. Now you can maintain the tables values, such as Adding new entries, delete row.
Wednesday, April 6, 2011
SAP Interview Questions
1. What is SAP?
SAP is the name of the company founded in 1972 under the German name (Systems, Applications, and Products in Data Processing) is the leading ERP (Enterprise Resource Planning) software package.
SAP Basics feature
* Configuration of the SAP modules
o Transaction SPRO - this is the main tree for all the configuration.
* Function Key
o F1 - Help
o F4 - Possible entries or matchcode for the field you are accessing
o F5 - Selection screen
o F7 - Previous screen
o F8 - Next screen
o F9 - Technical info
o CTRL+X - Cut
o CTRL+C - Copy
o CTRL+V - Paste
* Navigation
o /n Skip to the next record if you are processing one batch input session
o /bend Cancel a batch input foreground process
o /nend Close all R/3 sessions and logoff
o /nxxx x Call the transaction xxxx in the same session
o /o Generate a session list
o /oxxx x Call the transaction xxxx in an additional session
o /i Delete the current session
o /h Turn the debug mode on
o /$tab Reset all buffers (for System Administrators)
o /$syn c Synchronize instances buffers (for System Administrators)
In 4.x, you can have long SAP transaction code up to a maximum of 20 character
2. Different types of ERP?
SAP, BAAN, JD Edwards, Oracle Financials, Siebel, PeopleSoft. Among all the ERP’s most of the companies implemented or trying to implement SAP because of number of advantages aver other ERP packages.
3. What is ERP?
ERP is a package with the techniques and concepts for the integrated management of business as a whole, for effective use of management resources, to improve the efficiency of an enterprise. Initially, ERP was targeted for manufacturing industry mainly for planning and managing core business like production and financial market. As the growth and merits of ERP package ERP software is designed for basic process of a company from manufacturing to small shops with a target of integrating information across the company.
4. Explain the concept of “Business Content” in SAP Business Information Warehouse?
Business Content is a pre-configured set of role and task-relevant information models based on consistent Metadata in the SAP Business Information Warehouse. Business Content provides selected roles within a company with the information they need to carry out their tasks. These information models essentially contain roles, workbooks, queries, InfoSources, InfoCubes, key figures, characteristics, update rules and extractors for SAP R/3, mySAP.com Business Applications and other selected applications.
5. Why do you usually choose to implement SAP?
There are number of technical reasons numbers of companies are planning to implement SAP. It’s highly configurable, highly secure data handling, min data redundancy, max data consistency, you can capitalize on economics of sales like purchasing, tight integration-cross function.
6. Can BW run without a SAP R/3 implementation?
Certainly. You can run BW without R/3 implementation. You can use pre-defined business content in BW using your non-SAP data. Here you simply need to map the transfer structures associated with BW data sources (InfoCubes, ODS tables) to the inbound data files or use 3rd part tool to connect your flat files and other data sources and load data in BW. Several third party ETL products such as Acta, Infomatica, DataStage and others will have been certified to load data in BW.
7. What is IDES?
International Demonstration and Education System. A sample application provided for faster learning and implementation.
8. What is WF and its importance?
Business Work Flow: Tool for automatic control and execution of cross-application processes. This involves coordinating the persons involved, the work steps required, the data, which needs to be processed (business objects). The main advantage is reduction in throughput times and the costs involved in managing business processes. Transparency and quality are enhanced by its use.
9. What is SAP R/3?
A third generation set of highly integrated software modules that performs common business function based on multinational leading practice. Takes care of any enterprise however diverse in operation, spread over the world. In R/3 system all the three servers like presentation, application server and database server are located at different system.
10. What are presentation, application and database servers in SAP R/3?
The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server. All the data are stored in a centralized server. This server is called database server.
11. What should be the approach for writing a BDC program?
Convert the legacy system data to a flat file and convert flat file into internal table. Transfer the flat file into sap system called “sap data transfer”. Call transaction(Write the program explicitly) or create sessions (sessions are created and processed ,if success data will transfer).
12. Explain open SQL vs native SQL?
ABAP Native SQL allows you to include database-specific SQL statements in an ABAP program. Most ABAP programs containing database-specific SQL statements do not run with different databases. If different databases are involved, use Open SQL. To execute ABAP Native SQL in an ABAP program, use the statement EXEC. Open SQL (Subset of standard SQL statements), allows you to access all database tables available in the R/3 System, regardless of the manufacturer. To avoid conflicts between database tables and to keep ABAP programs independent from the database system used, SAP has generated its own set of SQL statements known as Open SQL.
13. What are datasets?
The sequential files (processed on application server) are called datasets. They are used for file handling in SAP.
14. What are internal tables check table, value table, and transparent table?
Internal table: It is a standard data type object, which exists only during the runtime of the program. Check table: Check table will be at field level checking. Value table: Value table will be at domain level checking ex: scarr table is check table for carrid. Transparent table: - Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.
15. What are the major benefits of reporting with BW over R/3? Would it be sufficient just to Web-enable R/3 Reports?
Performance — Heavy reporting along with regular OLTP transactions can produce a lot of load both on the R/3 and the database (cpu, memory, disks, etc). Just take a look at the load put on your system during a month end, quarter end, or year-end — now imagine that occurring even more frequently. Data analysis — BW uses a Data Warehouse and OLAP concepts for storing and analyzing data, where R/3 was designed for transaction processing. With a lot of work you can get the same analysis out of R/3 but most likely would be easier from a BW.
16. How can an ERP such as SAP help a business owner learn more about how business operates?
In order to use an ERP system, a business person must understand the business processes and how they work together from one functional area to the other. This knowledge gives the student a much deeper understanding of how a business operates. Using SAP as a tool to learn about ERP systems will require that the people understand the business processes and how they integrate.
17. What is the difference between OLAP and Data Mining?
OLAP - On line Analytical processing is a reporting tool configured to understand your database schema ,composition facts and dimensions . By simple point-n-clicking, a user can run any number of canned or user-designed reports without having to know anything of SQL or the schema. Because of that prior configuration, the OLAP engine “builds” and executes the appropriate SQL. Mining is to build the application to specifically look at detailed analyses, often algorithmic; even more often misappropriate called “reporting.
18. What is “Extended Star Schema” and how did it emerge?
The Star Schema consists of the Dimension Tables and the Fact Table. The Master Data related tables are kept in separate tables, which has reference to the characteristics in the dimension table(s). These separate tables for master data is termed as the Extended Star Schema.
19. Define Meta data, Master data and Transaction data
Meta Data: Data that describes the structure of data or MetaObjects is called Metadata. In other words data about data is known as Meta Data. Master Data: Master data is data that remains unchanged over a long period of time. It contains information that is always needed in the same way. Characteristics can bear master data in BW. With master data you are dealing with attributes, texts or hierarchies. Transaction data: Data relating to the day-to-day transactions is the Transaction data.
20. Name some drawbacks of SAP
Interfaces are huge problem, Determine where master data resides, Expensive, very complex, demands highly trained staff, lengthy implementation time.
21. What is Bex?
Bex stands for Business Explorer. Bex enables end user to locate reports, view reports, analyze information and can execute queries. The queries in workbook can be saved to there respective roles in the Bex browser. Bex has the following components: Bex Browser, Bex analyzer, Bex Map, Bex Web.
22. What are variables?
Variables are parameters of a query that are set in the parameter query definition and are not filled with values until the queries are inserted into workbooks. There are different types of variables which are used in different application: Characteristics variables, Hierarchies and hierarchy node, Texts, Formulas, Processing types, User entry/Default type, Replacment Path.
23. What is AWB?. What is its purpose?
AWB stands for Administrator WorkBench. AWB is a tool for controlling, monitoring and maintaining all the processes connected with data staging and processing in the business information whearhousing.
24. What is the significance of ODS in BIW?
An ODS Object serves to store consolidated and debugged transaction data on a document level (atomic level). It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or InfoSet Query. The data of an ODS Object can be updated with a delta update into InfoCubes and/or other ODS Objects in the same system or across systems. In contrast to multi-dimensional data storage with InfoCubes, the data in ODS Objects is stored in transparent, flat database tables.
25. What are the different types of source system?
SAP R/3 Source Systems, SAP BW, Flat Files and External Systems.
26. What is Extractor?
Extractors is a data retrieval mechanisms in the SAP source system. Which can fill the extract structure of a data source with the data from the SAP source system datasets. The extractor may be able to supply data to more fields than exist in the extract structure.
27. Describe how SAP handles Memory Management?
ST02 / ST03 In general via table buffers, you could go into the whole Work Process, roll in, roll out, heap (private) memory, etc. However just as a Unix or DBA admin would know, is you look this up when needed for the exact specifics.
28. Describe where they would look at the buffer statistics, and what steps they would use to adjust them?
ST02, RZ10 ...
29. Describe how to setup a printer in SAP or where they would look to research why a user/users can not print?
SPAD, SP01, SM50, SU01 ...
30. Can you create a table with fields not referring to data elements?
YES. eg:- ITAB LIKE SPFLI.here we are referening to a data object(SPFLI) not data element.
What are the different types of data dictionary objects? tables, structures, views, domains, data elements, lock objects, Match code objects.
31. What should be the approach for writing a BDC program?
STEP 1: CONVERTING THE LEGACY SYSTEM DATA TO A FLAT FILE to internal table CALLED "CONVERSION".
STEP 2: TRANSFERING THE FLAT FILE INTO SAP SYSTEM CALLED "SAP DATA TRANSFER".
STEP 3: DEPENDING UPON THE BDC TYPE
i)call transaction(Write the program explicity)
ii) create sessions (sessions are created and processed.if success data will transfer).
32. What are the problems in processing batch input sessions and How is batch input process different from processing online?
PROBLEMS: i) If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it manually.
ii)if session processing fails data will not be transferred to SAP database table.
33. What does an extract statement do in the ABAP program?
Once you have declared the possible record types as field groups and defined their structure, you can fill the extract dataset using the following statements: EXTRACT. When the first EXTRACT statement occurs in a program, the system creates the extract dataset and adds the first extract record to it. In each subsequent EXTRACT statement, the new extract record is added to the dataset EXTRACT HEADER. When you extract the data, the record is filled with the current values of the corresponding fields. As soon as the system has processed the first EXTRACT statement for a field group , the structure of the corresponding extract record in the extract dataset is fixed. You can no longer insert new fields into the field groups and HEADER. If you try to modify one of the field groups afterwards and use it in another EXTRACT statement, a runtime error occurs. By processing EXTRACT statements several times using different field groups, you fill the extract dataset with records of different length and structure. Since you can modify field groups dynamically up to their first usage in an EXTRACT statement, extract datasets provide the advantage that you need not determine the structure at the beginning of the program.
34. Can a transparent table exist in data dictionary but not in the data base physically?
NO. TRANSPARENT TABLE DO EXIST WITH THE SAME STRUCTURE BOTH IN THE DICTIONARY AS WELL AS IN THE DATABASE,EXACTLY WITH THE SAME DATA AND FIELDS.
35. What is the step by step process to create a table in data dictionary?
step 1: creating domains(data type, field length, range).
step 2: creating data elements(properties and type for a table field).
step 3: creating tables(SE11).
More Else
SAP is the name of the company founded in 1972 under the German name (Systems, Applications, and Products in Data Processing) is the leading ERP (Enterprise Resource Planning) software package.
SAP Basics feature
* Configuration of the SAP modules
o Transaction SPRO - this is the main tree for all the configuration.
* Function Key
o F1 - Help
o F4 - Possible entries or matchcode for the field you are accessing
o F5 - Selection screen
o F7 - Previous screen
o F8 - Next screen
o F9 - Technical info
o CTRL+X - Cut
o CTRL+C - Copy
o CTRL+V - Paste
* Navigation
o /n Skip to the next record if you are processing one batch input session
o /bend Cancel a batch input foreground process
o /nend Close all R/3 sessions and logoff
o /nxxx x Call the transaction xxxx in the same session
o /o Generate a session list
o /oxxx x Call the transaction xxxx in an additional session
o /i Delete the current session
o /h Turn the debug mode on
o /$tab Reset all buffers (for System Administrators)
o /$syn c Synchronize instances buffers (for System Administrators)
In 4.x, you can have long SAP transaction code up to a maximum of 20 character
2. Different types of ERP?
SAP, BAAN, JD Edwards, Oracle Financials, Siebel, PeopleSoft. Among all the ERP’s most of the companies implemented or trying to implement SAP because of number of advantages aver other ERP packages.
3. What is ERP?
ERP is a package with the techniques and concepts for the integrated management of business as a whole, for effective use of management resources, to improve the efficiency of an enterprise. Initially, ERP was targeted for manufacturing industry mainly for planning and managing core business like production and financial market. As the growth and merits of ERP package ERP software is designed for basic process of a company from manufacturing to small shops with a target of integrating information across the company.
4. Explain the concept of “Business Content” in SAP Business Information Warehouse?
Business Content is a pre-configured set of role and task-relevant information models based on consistent Metadata in the SAP Business Information Warehouse. Business Content provides selected roles within a company with the information they need to carry out their tasks. These information models essentially contain roles, workbooks, queries, InfoSources, InfoCubes, key figures, characteristics, update rules and extractors for SAP R/3, mySAP.com Business Applications and other selected applications.
5. Why do you usually choose to implement SAP?
There are number of technical reasons numbers of companies are planning to implement SAP. It’s highly configurable, highly secure data handling, min data redundancy, max data consistency, you can capitalize on economics of sales like purchasing, tight integration-cross function.
6. Can BW run without a SAP R/3 implementation?
Certainly. You can run BW without R/3 implementation. You can use pre-defined business content in BW using your non-SAP data. Here you simply need to map the transfer structures associated with BW data sources (InfoCubes, ODS tables) to the inbound data files or use 3rd part tool to connect your flat files and other data sources and load data in BW. Several third party ETL products such as Acta, Infomatica, DataStage and others will have been certified to load data in BW.
7. What is IDES?
International Demonstration and Education System. A sample application provided for faster learning and implementation.
8. What is WF and its importance?
Business Work Flow: Tool for automatic control and execution of cross-application processes. This involves coordinating the persons involved, the work steps required, the data, which needs to be processed (business objects). The main advantage is reduction in throughput times and the costs involved in managing business processes. Transparency and quality are enhanced by its use.
9. What is SAP R/3?
A third generation set of highly integrated software modules that performs common business function based on multinational leading practice. Takes care of any enterprise however diverse in operation, spread over the world. In R/3 system all the three servers like presentation, application server and database server are located at different system.
10. What are presentation, application and database servers in SAP R/3?
The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server. All the data are stored in a centralized server. This server is called database server.
11. What should be the approach for writing a BDC program?
Convert the legacy system data to a flat file and convert flat file into internal table. Transfer the flat file into sap system called “sap data transfer”. Call transaction(Write the program explicitly) or create sessions (sessions are created and processed ,if success data will transfer).
12. Explain open SQL vs native SQL?
ABAP Native SQL allows you to include database-specific SQL statements in an ABAP program. Most ABAP programs containing database-specific SQL statements do not run with different databases. If different databases are involved, use Open SQL. To execute ABAP Native SQL in an ABAP program, use the statement EXEC. Open SQL (Subset of standard SQL statements), allows you to access all database tables available in the R/3 System, regardless of the manufacturer. To avoid conflicts between database tables and to keep ABAP programs independent from the database system used, SAP has generated its own set of SQL statements known as Open SQL.
13. What are datasets?
The sequential files (processed on application server) are called datasets. They are used for file handling in SAP.
14. What are internal tables check table, value table, and transparent table?
Internal table: It is a standard data type object, which exists only during the runtime of the program. Check table: Check table will be at field level checking. Value table: Value table will be at domain level checking ex: scarr table is check table for carrid. Transparent table: - Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.
15. What are the major benefits of reporting with BW over R/3? Would it be sufficient just to Web-enable R/3 Reports?
Performance — Heavy reporting along with regular OLTP transactions can produce a lot of load both on the R/3 and the database (cpu, memory, disks, etc). Just take a look at the load put on your system during a month end, quarter end, or year-end — now imagine that occurring even more frequently. Data analysis — BW uses a Data Warehouse and OLAP concepts for storing and analyzing data, where R/3 was designed for transaction processing. With a lot of work you can get the same analysis out of R/3 but most likely would be easier from a BW.
16. How can an ERP such as SAP help a business owner learn more about how business operates?
In order to use an ERP system, a business person must understand the business processes and how they work together from one functional area to the other. This knowledge gives the student a much deeper understanding of how a business operates. Using SAP as a tool to learn about ERP systems will require that the people understand the business processes and how they integrate.
17. What is the difference between OLAP and Data Mining?
OLAP - On line Analytical processing is a reporting tool configured to understand your database schema ,composition facts and dimensions . By simple point-n-clicking, a user can run any number of canned or user-designed reports without having to know anything of SQL or the schema. Because of that prior configuration, the OLAP engine “builds” and executes the appropriate SQL. Mining is to build the application to specifically look at detailed analyses, often algorithmic; even more often misappropriate called “reporting.
18. What is “Extended Star Schema” and how did it emerge?
The Star Schema consists of the Dimension Tables and the Fact Table. The Master Data related tables are kept in separate tables, which has reference to the characteristics in the dimension table(s). These separate tables for master data is termed as the Extended Star Schema.
19. Define Meta data, Master data and Transaction data
Meta Data: Data that describes the structure of data or MetaObjects is called Metadata. In other words data about data is known as Meta Data. Master Data: Master data is data that remains unchanged over a long period of time. It contains information that is always needed in the same way. Characteristics can bear master data in BW. With master data you are dealing with attributes, texts or hierarchies. Transaction data: Data relating to the day-to-day transactions is the Transaction data.
20. Name some drawbacks of SAP
Interfaces are huge problem, Determine where master data resides, Expensive, very complex, demands highly trained staff, lengthy implementation time.
21. What is Bex?
Bex stands for Business Explorer. Bex enables end user to locate reports, view reports, analyze information and can execute queries. The queries in workbook can be saved to there respective roles in the Bex browser. Bex has the following components: Bex Browser, Bex analyzer, Bex Map, Bex Web.
22. What are variables?
Variables are parameters of a query that are set in the parameter query definition and are not filled with values until the queries are inserted into workbooks. There are different types of variables which are used in different application: Characteristics variables, Hierarchies and hierarchy node, Texts, Formulas, Processing types, User entry/Default type, Replacment Path.
23. What is AWB?. What is its purpose?
AWB stands for Administrator WorkBench. AWB is a tool for controlling, monitoring and maintaining all the processes connected with data staging and processing in the business information whearhousing.
24. What is the significance of ODS in BIW?
An ODS Object serves to store consolidated and debugged transaction data on a document level (atomic level). It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or InfoSet Query. The data of an ODS Object can be updated with a delta update into InfoCubes and/or other ODS Objects in the same system or across systems. In contrast to multi-dimensional data storage with InfoCubes, the data in ODS Objects is stored in transparent, flat database tables.
25. What are the different types of source system?
SAP R/3 Source Systems, SAP BW, Flat Files and External Systems.
26. What is Extractor?
Extractors is a data retrieval mechanisms in the SAP source system. Which can fill the extract structure of a data source with the data from the SAP source system datasets. The extractor may be able to supply data to more fields than exist in the extract structure.
27. Describe how SAP handles Memory Management?
ST02 / ST03 In general via table buffers, you could go into the whole Work Process, roll in, roll out, heap (private) memory, etc. However just as a Unix or DBA admin would know, is you look this up when needed for the exact specifics.
28. Describe where they would look at the buffer statistics, and what steps they would use to adjust them?
ST02, RZ10 ...
29. Describe how to setup a printer in SAP or where they would look to research why a user/users can not print?
SPAD, SP01, SM50, SU01 ...
30. Can you create a table with fields not referring to data elements?
YES. eg:- ITAB LIKE SPFLI.here we are referening to a data object(SPFLI) not data element.
What are the different types of data dictionary objects? tables, structures, views, domains, data elements, lock objects, Match code objects.
31. What should be the approach for writing a BDC program?
STEP 1: CONVERTING THE LEGACY SYSTEM DATA TO A FLAT FILE to internal table CALLED "CONVERSION".
STEP 2: TRANSFERING THE FLAT FILE INTO SAP SYSTEM CALLED "SAP DATA TRANSFER".
STEP 3: DEPENDING UPON THE BDC TYPE
i)call transaction(Write the program explicity)
ii) create sessions (sessions are created and processed.if success data will transfer).
32. What are the problems in processing batch input sessions and How is batch input process different from processing online?
PROBLEMS: i) If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it manually.
ii)if session processing fails data will not be transferred to SAP database table.
33. What does an extract statement do in the ABAP program?
Once you have declared the possible record types as field groups and defined their structure, you can fill the extract dataset using the following statements: EXTRACT. When the first EXTRACT statement occurs in a program, the system creates the extract dataset and adds the first extract record to it. In each subsequent EXTRACT statement, the new extract record is added to the dataset EXTRACT HEADER. When you extract the data, the record is filled with the current values of the corresponding fields. As soon as the system has processed the first EXTRACT statement for a field group , the structure of the corresponding extract record in the extract dataset is fixed. You can no longer insert new fields into the field groups and HEADER. If you try to modify one of the field groups afterwards and use it in another EXTRACT statement, a runtime error occurs. By processing EXTRACT statements several times using different field groups, you fill the extract dataset with records of different length and structure. Since you can modify field groups dynamically up to their first usage in an EXTRACT statement, extract datasets provide the advantage that you need not determine the structure at the beginning of the program.
34. Can a transparent table exist in data dictionary but not in the data base physically?
NO. TRANSPARENT TABLE DO EXIST WITH THE SAME STRUCTURE BOTH IN THE DICTIONARY AS WELL AS IN THE DATABASE,EXACTLY WITH THE SAME DATA AND FIELDS.
35. What is the step by step process to create a table in data dictionary?
step 1: creating domains(data type, field length, range).
step 2: creating data elements(properties and type for a table field).
step 3: creating tables(SE11).
More Else
SAP Interview Questions and Answers
- What is ERP? - ERP is a package with the techniques and concepts for the integrated management of business as a whole, for effective use of management resources, to improve the efficiency of an enterprise. Initially, ERP was targeted for manufacturing industry mainly for planning and managing core business like production and financial market. As the growth and merits of ERP package ERP software is designed for basic process of a company from manufacturing to small shops with a target of integrating information across the company.
- Different types of ERP? - SAP, BAAN, JD Edwards, Oracle Financials, Siebel, PeopleSoft. Among all the ERP’s most of the companies implemented or trying to implement SAP because of number of advantages aver other ERP packages.
- What is SAP? - SAP is the name of the company founded in 1972 under the German name (Systems, Applications, and Products in Data Processing) is the leading ERP (Enterprise Resource Planning) software package.
- Explain the concept of “Business Content” in SAP Business Information Warehouse? - Business Content is a pre-configured set of role and task-relevant information models based on consistent Metadata in the SAP Business Information Warehouse. Business Content provides selected roles within a company with the information they need to carry out their tasks. These information models essentially contain roles, workbooks, queries, InfoSources, InfoCubes, key figures, characteristics, update rules and extractors for SAP R/3, mySAP.com Business Applications and other selected applications.
- Why do you usually choose to implement SAP? - There are number of technical reasons numbers of companies are planning to implement SAP. It’s highly configurable, highly secure data handling, min data redundancy, max data consistency, you can capitalize on economics of sales like purchasing, tight integration-cross function.
- Can BW run without a SAP R/3 implementation? - Certainly. You can run BW without R/3 implementation. You can use pre-defined business content in BW using your non-SAP data. Here you simply need to map the transfer structures associated with BW data sources (InfoCubes, ODS tables) to the inbound data files or use 3rd part tool to connect your flat files and other data sources and load data in BW. Several third party ETL products such as Acta, Infomatica, DataStage and others will have been certified to load data in BW.
- What is IDES? - International Demonstration and Education System. A sample application provided for faster learning and implementation.
- What is WF and its importance? - Business Work Flow: Tool for automatic control and execution of cross-application processes. This involves coordinating the persons involved, the work steps required, the data, which needs to be processed (business objects). The main advantage is reduction in throughput times and the costs involved in managing business processes. Transparency and quality are enhanced by its use.
- What is SAP R/3? - A third generation set of highly integrated software modules that performs common business function based on multinational leading practice. Takes care of any enterprise however diverse in operation, spread over the world. In R/3 system all the three servers like presentation, application server and database server are located at different system.
- What are presentation, application and database servers in SAP R/3? - The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server. All the data are stored in a centralized server. This server is called database server.
- What should be the approach for writing a BDC program? - Convert the legacy system data to a flat file and convert flat file into internal table. Transfer the flat file into sap system called “sap data transfer”. Call transaction(Write the program explicitly) or create sessions (sessions are created and processed ,if success data will transfer).
- Explain open SQL vs native SQL? - ABAP Native SQL allows you to include database-specific SQL statements in an ABAP program. Most ABAP programs containing database-specific SQL statements do not run with different databases. If different databases are involved, use Open SQL. To execute ABAP Native SQL in an ABAP program, use the statement EXEC. Open SQL (Subset of standard SQL statements), allows you to access all database tables available in the R/3 System, regardless of the manufacturer. To avoid conflicts between database tables and to keep ABAP programs independent from the database system used, SAP has generated its own set of SQL statements known as Open SQL.
- What are datasets? - The sequential files (processed on application server) are called datasets. They are used for file handling in SAP.
- What are internal tables check table, value table, and transparent table? - Internal table: It is a standard data type object, which exists only during the runtime of the program. Check table: Check table will be at field level checking. Value table: Value table will be at domain level checking ex: scarr table is check table for carrid. Transparent table: - Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.
- What are the major benefits of reporting with BW over R/3? Would it be sufficient just to Web-enable R/3 Reports? - Performance — Heavy reporting along with regular OLTP transactions can produce a lot of load both on the R/3 and the database (cpu, memory, disks, etc). Just take a look at the load put on your system during a month end, quarter end, or year-end — now imagine that occurring even more frequently. Data analysis — BW uses a Data Warehouse and OLAP concepts for storing and analyzing data, where R/3 was designed for transaction processing. With a lot of work you can get the same analysis out of R/3 but most likely would be easier from a BW.
- How can an ERP such as SAP help a business owner learn more about how business operates? - In order to use an ERP system, a
business person must understand the business processes and how they work together from one functional area to the other. This knowledge gives the student a much deeper understanding of how a business operates. Using SAP as a tool to learn about ERP systems will require that the
people understand the business processes and how they integrate. - What is the difference between OLAP and Data Mining? - OLAP - On line Analytical processing is a reporting tool configured to understand your database schema ,composition facts and dimensions . By simple point-n-clicking, a user can run any number of canned or user-designed reports without having to know anything of SQL or the schema. Because of that prior configuration, the OLAP engine “builds” and executes the appropriate SQL. Mining is to build the application to specifically look at detailed analyses, often algorithmic; even more often misappropriate called “reporting.
- What is “Extended Star Schema†and how did it emerge? - The Star Schema consists of the Dimension Tables and the Fact Table. The Master Data related tables are kept in separate tables, which has reference to the characteristics in the dimension table(s). These separate tables for master data is termed as the Extended Star Schema.
- Define Meta data, Master data and Transaction data - Meta Data: Data that describes the structure of data or MetaObjects is called Metadata. In other words data about data is known as Meta Data. Master Data: Master data is data that remains unchanged over a long period of time. It contains information that is always needed in the same way. Characteristics can bear master data in BW. With master data you are dealing with attributes, texts or hierarchies. Transaction data: Data relating to the day-to-day transactions is the Transaction data.
- Name some drawbacks of SAP - Interfaces are huge problem, Determine where master data resides, Expensive, very complex, demands highly trained staff, lengthy implementation time.
- What is Bex? - Bex stands for Business Explorer. Bex enables end user to locate reports, view reports, analyze information and can execute queries. The queries in workbook can be saved to there respective roles in the Bex browser. Bex has the following components: Bex Browser, Bex analyzer, Bex Map, Bex Web.
- What are variables? - Variables are parameters of a query that are set in the parameter query definition and are not filled with values until the queries are inserted into workbooks. There are different types of variables which are used in different application: Characteristics variables, Hierarchies and hierarchy node, Texts, Formulas, Processing types, User entry/Default type, Replacment Path.
- What is AWB?. What is its purpose? - AWB stands for Administrator WorkBench. AWB is a tool for controlling, monitoring and maintaining all the processes connected with data staging and processing in the business information whearhousing.
- What is the significance of ODS in BIW? - An ODS Object serves to store consolidated and debugged transaction data on a document level (atomic level). It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or InfoSet Query. The data of an ODS Object can be updated with a delta update into InfoCubes and/or other ODS Objects in the same system or across systems. In contrast to multi-dimensional data storage with InfoCubes, the data in ODS Objects is stored in transparent, flat database tables.
- What are the different types of source system? - SAP R/3 Source Systems, SAP BW, Flat Files and External Systems.
- What is Extractor? - Extractors is a data retrieval mechanisms in the SAP source system. Which can fill the extract structure of a data source with the data from the SAP source system datasets. The extractor may be able to supply data to more fields than exist in the extract structure.
Tuesday, April 5, 2011
SAP PS Transaction codes
Here is a list of PS transactions. (Excluding the S_ALR** series(reports)
CJ** are mainly Project Definition and WBS related,
CN** are mainly Network and activity related and the
OP** are mainly PS Configuration / Customization related.
There are other which is not on the list, but this is a good platform to start and build up your own list of PS transactions as per your requirements:
CJ01 Create Work Breakdown Structure CJ02 Change Work Breakdown Structure CJ03 Display Work Breakdown Structure CJ06 Create Project Definition CJ07 Change Project Definition CJ08 Display Project Definition CJ11 Create WBS Element CJ12 Change WBS Element CJ13 Display WBS Element CJ14 Display WBS Element (From DMS) CJ20 Structure planning CJ20N Project Builder CJ21 Change Basic Dates CJ22 Display Basic Dates CJ23 Change Forecast Dates CJ24 Display Forecast Dates CJ25 Change Actual Dates CJ26 Display Actual Dates CJ27 Project planning board CJ29 Update WBS (Forecast) CJ2A Display structure planning CJ2B Change project planning board CJ2C Display project planning board CJ2D Structure planning CJ30 Change Project Original Budget CJ31 Display Project Original Budget CJ32 Change Project Release CJ33 Display Project Release CJ34 Project Budget Transfer CJ35 Budget Return from Project CJ36 Budget Supplement to Project CJ37 Budget Supplement in Project CJ38 Budget Return in Project CJ3A Change Budget Document CJ3B Display Budget Document CJ40 Change Project Plan CJ41 Display Project Plan CJ42 Change Project Revenues CJ43 Display Project Revenues CJ44 Act. overhd: Projects, ind. process. CJ45 Act. ovhd: Projects, coll. process. CJ46 Plnd ovrhd: Projects, ind. process. CJ47 Pld Overhead: Projects, Coll.Procssg CJ48 Change Payment Planning: Init.Screen CJ49 Display Payment Planning: Init.Scrn CJ70 Maintain Project Settlement LIs CJ72 Project: Act. amt. line item settlmt CJ74 Project Actual Cost Line Items CJ76 Project Commitment Line Items CJ7E Plan Data Transfer: Projects CJ7G Plan Data Transfer: Projects CJ7M Project Plan Cost Line Items CJ7N Maint. DRG inv.projects for retmt. CJ80 Availability Control - Overview CJ81 Update Report List CJ88 Settle Projects and Networks CJ8A Act.-setlmt: Proj. retirmt. from IM CJ8G Actual Settlement: Projects/Networks CJ8V Period Close for Project Selection CJ91 Create Standard WBS CJ92 Change Standard WBS CJ93 Display Standard WBS CJ9B Copy WBS Plan to Plan (Collective) CJ9B_OLD Copy Project Cost Planning (old) CJ9BS Copy WBS Plan to Plan (Indiv.) CJ9C Copy WBS Actual to Plan (Collective) CJ9C_OLD Copy Project Revenue Planning (old) CJ9CS Copy WBS Actual to Plan (Indiv.) CJ9D Copy Plan Versions CJ9E Plan Settlement: Projects CJ9ECP Project System: Easy Cost Planning CJ9F Copy Project Costing (Collective) CJ9FS Copy Project Costing (Indiv.) CJ9G Plan Settlement: Projects CJ9K Network Costing CJ9L Forecast Costs: Individual Projects CJ9M Forecast Costs: Coll.Project Proc. CJ9Q Integrated Planning for Ntwks(Coll.) CJ9QS Integrated Planning for Ntwks (Ind.) CJA1 Proj.Rel.Order Receipts: Coll.Proc. CJA2 Proj.Rel. Order Receipts: Ind.Proc. CJAL Send project CJB1 Generate Settmt Rule: Coll.Proc. CJB2 Generate Settmt Rule: Indiv.Proc. CJBBS1 Planning Board Report Assignment CJBBS2 Structure Overview Report Asst CJBN Reconstruct Availability Control CJBV Activate Project Availabilty Control CJBW Deactivate Project Availabilty Cntrl CJC1 Maintenance Dialog for Stat.by Per. CJC2 Maintain Planned Status Changes CJCD Change documents: WBS CJCF Carry Forward Project Commitments CJCO Carry Forward Project Budget CJCS Standard WBS CJE0 Run Hierarchy Report CJE1 Create Hierarchy Report CJE2 Change Hierarchy Report CJE3 Display Hierarchy Report CJE4 Create Project Report Layout CJE5 Change Project Report Layout CJE6 Display Project Report Layout CJEA Call Hierarchy Report CJEB Background Processing, Hier.Reports CJEC Maintain Project Crcy Trans.Type CJEK Copy Interfaces/Reports CJEM Project Reports: Test Monitor CJEN Reconstruct: Summarized Proj.Data CJEO Transport Reports CJEP Transport Forms CJEQ Import Reports from Client CJET Translation Tool - Drilldown CJEV Maintain Global Variable CJEX Reorganize Drilldown Reports CJEY Reorganize Report Data CJEZ Reorganize Forms CJF1 Create Transfer Price Agreement CJF2 Change Transfer Price Agreement CJF3 Display Transfer Price Agreement CJF4 Transfer Price Agreement List CJFA Analysis of Data Trans. into PS Cash CJFN CBM Payment Converter CJG1 Enter Transfer Price Allocation CJG3 Display Transfer Price Allocation CJG4 Enter Trsfr Price Allocation: List CJG5 Cancel Transfer Price Allocation CJH1 Reconstruct Project Inheritance CJH2 Project Inheritance Log CJI1 Project Budget Line Items CJI2 Budget Line Items: Document Chain CJI3 Project Actual Cost Line Items CJI4 Project Plan Cost Line Items CJI5 Project Commitment Line Items CJI8 Project Budget Line Items CJI9 Project Struct.Pld Costs Line Items CJIA Project Actual and Commt Paymt LIs CJIB Project Plan Payment Line Items CJIC Maintain Project Settlement LIs CJID Display Project Settlement Line Itms CJIE Projects: Retirement LI Settlement CJIF Projects: Profitability Analysis LI CJIG Display PS Cash Documents CJJ2 Change Statistical Key Figures CJJ3 Display Statistical Key Figures CJK2 Change Statistical Key Figures CJK3 Display Statistical Key Figures CJL2 Collective Agreement CJN1 Reval. ACT: Projects Ind.Pro. CJN2 Reval. ACT: Projects Col.Pro. CJNO Number range maintenance: FMCJ_BELNR CJO8 Overhead COMM: Projects Ind.Pro. CJO9 Overhead COMM: Projects Col.Pro. CJP1 Create Project Plan Adjustment CJP2 Change Project Plan Adjustment CJP3 Display Project Plan Adjustment CJP4 Delete Project Plan Adjustment CJPN Number Range Maintenance: Proj.Items CJPU Execute Project Plan Adjustment CJR2 PS: Change plan CElem/Activ. input CJR3 PS: Display plan CElem/Activ. input CJR4 PS: Change plan primary cost element CJR5 PS: Display plan primary cost elem. CJR6 PS: Change activity input planning CJR7 PS: Display activity input planning CJR8 PS: Change revenue type planning CJR9 PS: Display Revenue Element Planning CJS2 PS: Change stat. key figure planning CJS3 PS: Display stat. key fig. planning CJS4 PS: Change stat. key figure planning CJS5 PS: Display stat. key fig. planning CJSA Data Transfer to SAP-EIS CJSB Select Key Figure and Characteristic CJSG Generate WBS Element Group CJSN Number Range Maintenance: Projects CJT2 Project Actual Payment Line Items CJV1 Create project version (simulation) CJV2 Change project version (simulation) CJV3 Display project version (simulation) CJV4 Transfer project CJV5 Delete simulation version CJV6 Maintenance: Version administration CJV7 Display transfer log CJVC Value Category Checking Program CJW1 EURO: Adjust Project Budget CJZ1 Act. Int Calc.: Projects Coll. Proc. CJZ2 Actual Int.Calc.: Project Indiv.Prc. CJZ3 Plan Int.Calc.: Project Indiv.Prc. CJZ5 Plan Int.Calc.: Project Coll.Prc. CJZ6 Actual Int.Calc.: Indiv.CO Order Prc CJZ7 Planned Int.Calc: Indiv.CO Ord.Proc. CJZ8 Actual Int.Calc.: Coll.CO Order Prc. CJZ9 Plan Int.Calc.: Coll.CO Order Prc.
Network and activity related transaction codes:
CN01 - Create Standard Network CN02 - Change Standard Network CN03 - Display Standard Network CN04 - Edit PS Text Catalog CN05 - Display PS Text Catalog CN06 - MPX Download: Standard Network CN07 - MPX Upload: Standard Network CN08 - Allocate material -> stand. network CN09 - Allocate material -> stand. network CN11 - Create standard milestone CN12 - Change standard milestone CN13 - Display standard milestone CN19 - Display Activity (From DMS) CN20 - Dsply network/act.bsc data init.scrn CN21 - Create Network CN22 - Change Network CN23 - Display Network CN24 - Overall Network Scheduling CN24N Overall Network Scheduling CN25 - Confirm Completions in Network CN26 - Display Mat.Comp/Init: Ntwk,Acty,Itm CN26N Display Mat. Components (From DMS) CN27 - Collective confirm. CN28 - Display Network Confirmations CN29 - Cancel Network Confirmation CN2X - Confirm Completions in Network CN30 - Processing PDC error records CN33 - PDM-PS interface CN34 - Maintain release table TCNRL CN35 - Control stock / account assignment CN36 - BOM Transfer Profile CN37 - BOM Allocation Field Selection CN38 - Maintain Flexible Reference Point CN40 - Project Overview CN41 - Structure Overview CN42 - Overview: Project Definitions CN42N Overview: Project Definitions CN43 - Overview: WBS Elements CN43N Overview: WBS Elements CN44 - Overview: Planned Orders CN44N Overview: Planned Orders CN45 - Overview: Orders CN45N Overview: Orders CN46 - Overview: Networks CN46N Overview: Networks CN47 - Overview: Activities/Elements CN47N Overview: Activities/Elements CN48 - Overview: Confirmations CN48N Overview: Confirmations CN49 - Overview: Relationships CN49N Overview: Relationships CN50 - Overview: Capacity Requirements CN50N Overview: Capacity Requirements CN51 - Overview: PRTs CN51N Overview: PRTs CN52 - Overview: Components CN52N Overview: Components CN53 - Overview: Milestones CN53N Overview: Milestones CN54N Overview: Sales Document CN55N Overview: Sales and Dist. Doc. Items CN60 - Change Documents for Projects/Netw. CN61 - Standard network CN65 - Change documents order /network CN70 - Overview: Batch variants CN71 - Create versions CN72 - Create Project Version CN80 - Archiving project structures CN81 - PS: Archiving project - preliminary CN82 - PS: Archiving project structures CN83 - PS: Archiving project - Info System CN84 - PS: Archiving project - admin. CN85 - PS: Delete operative structures CN98 - Delete Standard Networks CN99 - Archiving Standard Networks CNB1 - Purchase requisitions for project CNB2 - Purchase orders for project CNC4 - Consistency checks for WBS CNC5 - Consistency checks sales order/proj. CNE1 - Project Progress (Individual Proc.) CNE2 - Project Progress (Collective Proc.) CNE5 - Progress Analysis CNG1 - Netw./Hier.: Maintain frame types CNG2 - Netw./Hier.: Maintain form def. CNG3 - Netw./hier.: maintain color definit. CNG4 - Netw./Hier.: Maintain graph. profile CNG5 - Netw./Hier: Maintain options profile CNG6 - Netw./hier.: Maintain node type CNG7 - Netw./Hier.: Maintain link types CNG8 - Netw./Hier.: Maintain field def. CNG9 - Graph. Cust. Netw./Hierarchy Graph. CNL1 - Create delivery information CNL2 - Change delivery information CNL3 - Display delivery information CNMASS Mass Changes in Project System CNMASSPROT - Display log f. mass changes PS CNMM - Project-Oriented Procurement CNMT - Milestone Trend Analysis CNN0 - Number Range for Library Network CNN1 - Number range maint.: ROUTING_0 CNPAR Partner Overview CNPRG Network Progress CNR1 - Create Work Center CNR2 - Change Work Center CNR3 - Display Work Center CNS0 - Create deleivry from project CNS40 Project Overview CNS41 Structure Overview CNS42 Overview: Project Definitions CNS43 Overview: WBS Elements CNS44 Overview: Planned Orders CNS45 Overview: Orders CNS46 Overview: Networks CNS47 Overview: Activities/Elements CNS48 Overview: Confirmations CNS49 Overview: Relationships CNS50 Overview: Capacity Requirements CNS51 Overview: PRTs CNS52 Overview: Components CNS53 Overview: Milestones CNS54 Overview: Sales Document CNS55 Overview: Sales and Dist. Doc. Items CNS60 Change Documents for Projects/Netw. CNS71 Create versions CNS83 PS: Archiving project - Info System CNSE5 Progress Analysis CNVL - Variable Overviews CNW1 - WWW: Confirmation CNW4 - Project Documents
PS Configuration / Customization related Transactions codes:
OP00 - Maintain Operation Control Key OP01 - Customizing Routing/Work Center OP03 - Factory Calendar C OP04 - Word Processing OP07 - Standard Text OP08 - Standard Text OP09 - Maintain Alternative Activity Desc. OP10 - Maintain Person Responsible OP11 - Maintain Period Pattern Key OP12 - Maintain Location OP13 - Maintain Screen Sequence OP14 - Maintain Type of Std. Value Determin OP15 - Production User Profile OP16 - Maintain Period Pattern OP17 - Formula Parameters OP18 - Maintain Setup Group/Setup Group Cat OP19 - Standard Value Key OP20 - Maintain Setup Type Key OP21 - Define Formula OP22 - Maintain Wage Groups OP23 - Maintain Location OP24 - Maintain period dependent oper. val. OP26 - Maintain suitability OP28 - Maintain Perf. Efficiency Rate Key OP30 - Maintain Move Time Matrix OP31 - Maintain Time Segment (Per. Pattern) OP32 - Maintain Capacity Category OP34 - Maintain Work Center Planner Group OP35 - Maintain Perf. Efficiency Rate Key OP36 - Maintain Capacity Default Values OP37 - Maintain Available Capacity Version OP38 - Maintain Setup Type Key OP39 - Maintain Graphics Profile OP40 - Maintain Work Center Category OP41 - Matchcode for work center OP42 - Default work center OP43 - Maintain Setup Group Categories OP44 - Maintain Task List Usage OP45 - Maintain Usage OP46 - Maintain Task List Status OP47 - Maintain PRT Usage OP48 - Maintain Planner Group OP49 - Matchcode for Routings/Ref. Op. Sets OP4A - Maintain Shift Sequences OP4B - Overview variant: Routing OP4C - Overview variant: Ref. oper. set OP4D - Overview variant: Rate routing OP4E - Overview variant: Ref. rate routing OP4F - Overview var.:Scheduling of routings OP4G - Overview var.:Scheduling ref.op.set OP4H - Overview var.:Scheduling of rate rtg OP4I - Overview var.:Scheduling RefRateRtgs OP50 - Assign Material Types OP51 - Formula Parameters OP52 - Formula Parameters OP53 - Formula Parameters OP54 - Define Formula OP55 - Define Formula OP56 - Define Formula OP57 - Define Formula OP58 - Maintain Default Value Profiles OP59 - Formula Parameters OP5A - Field Selection: Task List Overview OP5B - Field Selection: Task List Header OP5C - Field Selection: Task List Sequence OP5D - Field Selection: Task List Details OP5E - Field selection task list overview OP5F - Field selection std network -> PRT OP5H - Field sel. insp.plan characteristics OP61 - Number range maintenance: ROUTING_3 OP62 - Number ranges for routings OP63 - Number Ranges for Ref.Operation Sets OP64 - Maintain Setup Group Key OP65 - Formula Parameters OP66 - Maintain Location Group OP67 - Maintain Operation Control Key OP68 - Maintain Move Time Matrix OP69 - Maintain wage type OP70 - Maintain PRT Control Key OP71 - Maintain Wage Group OP72 - PRT Control Key OP73 - PRT Authorization Group OP74 - Maintain PRT Group Key OP76 - Define suitability OP77 - Engineering Workbench for Task Lists OP78 - Maintain Type of Std. Value Determin OP7A - Customizing matchcode for PRTs OP7B - Define Parameters OP80 - Maintain PRT Status OP82 - Define Formula OP84 - Profiles: Default Values for Rtgs. OP85 - Profiles: Default Values for QM OP87 - Maintain Routing/Ref.Op.Set Usage OP88 - Maintain Assignmt. of Task List Type OP8A - Maintain operation value description OP8B - Maintain standard value texts OP8C - Record layout for background (APL) OP8D - Data transfer APL OP8E - Command file task lists Rel. 2.2A OP8F - Maintain production scheduler OP8H - Profiles: Default Values for Rtgs. OP91 - Maintain Object Overview Version OP95 - Assign Work Center Cat. to Applicatn OP96 - Maintain Work Center Category OP97 - Maintain Performance Efficiency Rate OP98 - Maintain Validity of Perf.Effic.Rate OPA0 - Status selection profiles OPA1 - Maintain combination definitions OPA2 - Define selection profile OPA3 - Define option profile OPA4 - Define list profile OPA5 - Define graphics profile OPA6 - Define overall profile OPA7 - Define columns OPA9 - Maintain selection profiles OPB1 - Define list versions OPB2 - Define distribution function OPB3 - Specify distribution functions OPB4 - Specify distribution strategies OPB5 - Specify distribution key OPC0 - Axis representation selection OPC1 - Maintain axis representation OPC2 - Curve representation selection OPC3 - Maintain curve representation OPC5 - Max. no. of data records OPCD - Capacity category OPCE - Capacity planner OPCF - Time units OPCG - Maintain Operation Control Key OPCH - Maintain production scheduler OPCI - Setup group key/category OPCL - Scheduling type OPCM - Standard value key OPCN - Maintain move time matrix OPCQ - Efficiency rate OPCR - Formula parameters OPCS - Define formula OPCT - Strategies OPCU - Strategy levels OPCW - Planned order parameters OPCX - Formula parameters OPCY - Define formula OPD0 - Resource planning overall profile OPD1 - Resource planning selection profile OPD2 - Capacity leveling - time profile OPD3 - Resource planning evaluation profile OPD4 - Resource planning period profile OPD5 - Flow control definition OPD6 - Flow control control table OPD7 - Flow control statuses OPD8 - Flow Control Actions OPD9 - Flow Control Messages OPDA - Transition matrix (setup matrix) OPDB - Capacity Leveling Strategy Profile OPDD - Factory calendar OPDE - Resource planning control profile OPDF - Define requirements grouping OPDH - Capacity leveling - list profile OPDJ - Define layout OPDK - Define standard overview OPDL - Cap. plan. detailed cap.list maint. OPDM - Define detail list (leveling) OPDQ - Profile for planning table (tab.) OPDR - Define layout key OPDT - Define detail list OPDU - Maintain perf. efficiency rate key OPDV - Com-file (Rel-Info/OLPK) KOP. Set´s OPDW - Com-file (Rel-Info/OLPK) KOP. Set´s OPE0 - Maintain Sort String OPE1 - Maintain Value Type OPE2 - Maintain Machine Type OPE3 - Maintain Planner Group OPE4 - Maintain Control Parameters OPE5 - Maintain rounding categories OPE6 - Maintain Rounding Category OPE7 - Maintain overhead key OPE8 - Maint. Roundg. and Add.Val.Key (Def) OPE9 - Maintain User Profile OPEA - User selection OPEB - Automatic selection OPEC - PP user fields OPENPS Download Activities to Palm Pilot OPF0 - Maintain User OPF1 - Authorizations for CAPP OPFA - Field selection: Work center OPFP - Configuring the Fixed Price Version OPFR01 RPUCORF0PBS : IMG Link OPG0 - Profile for planning table OPG1 - Chart sequence - selection OPG2 - Line representation OPG3 - Scale time axis OPG4 - Time scale profile OPG5 - Graphic obj.type sel./repr.profile OPG6 - Transition matrix setup fam.key OPG7 - Line display selection OPG9 - Graphical object type/obj.represent. OPGD - Ref. Oper. Set-All Task Lists (PP) OPGE - Ref. Oper. Set - Rate Routings (PP) OPGF - Work Center - All Task Lists (PP) OPGG - Work Center - Rate Routings (PP) OPGH - Document PRT - All Task Lists OPGI - Equipment PRT - All Task Lists OPGJ - Material PRT - All Task Lists OPGK - Misc. PRT - All Task Lists OPGL - Resource - Master Recipes (PI) OPGM - Process Instr. Cat. - Master Recipe OPGN - Document PRT - Maintenance Task List OPGO - Equipment PRT-Maintenance Task Lists OPGP - Material PRT - Maintenance Task List OPGQ - Misc. PRT - Maintenance Task Lists OPGR - Work Center - Standard Network (PS) OPGS - Document PRT - Standard Network (PS) OPGT - Equipment PRT - Standard Network(PS) OPGU - Material PRT - Standard Network (PS) OPGV - Misc. PRT - Standard Network (PS) OPH1 - CO Cash Bgt Mgmt: Delete Actual Data OPH2 - PS Cash Management: Delete Plan Data OPH3 - CO Cash Bgt Mgmt: Delete Master Data OPH4 - CO Cash Bgt Mgmt: MM Data Transfer OPH5 - CO CBM: Successive FI Data Transfer OPH6 - CO CBM: Take Over FI Completely OPH7 - CO-CBM: Take Over All Data OPI1 - Maintain Value Categories OPI2 - Value Categories for Cost Elements OPI3 - Update Control: File RPSCO OPI4 - Commitment Item Value Categories OPI5 - Value Categories for Stag.Key Figs OPI6 - Activate CO Cash Budget Management OPI8 - Display Value Category OPIA - Interest Profile for Projects OPIB - Maintain Interest Profile OPIC - Intrst Relevance: Cost Els/Cmmt Itms OPID - Proj.Int Calc: Account Determination OPIE - Interest Indicator OPIF - View Maintenance:Compound Int.Cont. OPIG - View Maint.: Compound Int. Periods OPIH - Interest Scale, General Conditions OPIN - Number range maintnce: VHU_PINST OPJ2 - Production order stock determination OPJ4 - Schedule batch function request OPJ6 - Maintain Status Profiles OPJ7 - Maintain Routing Usage OPJ8 - Maintain Operation Control Key OPJ9 - Maintain prod. scheduler group OPJA - Maintain setup group/group category OPJB - Specify system messages OPJC - Maintain Wage Groups OPJD - Item Categories OPJE - User Selection OPJF - Automatic Selection OPJG - Maintain Default Values OPJH - Order types production order OPJI - BOM Usage Priorities OPJJ - Maintain Scope of Check OPJK - Maintain Control OPJL - Maintain Checking Rule OPJM - Application-Specific Criteria OPJN - Maintain Scheduling Type OPJO - C MM-BD units of measurement OPJP - Maint. acct.assgnm.types for orders OPJQ - Standard Value Key OPJR - Maintain move time matrix OPJS - PP: Maintain reduction strategies OPJT - Maintain Strategy Levels OPJU - Production order control parameters OPJV - Maintain Capacity Category OPJW - Maintain Capa.Planr.Grp for WrkCentr OPJX - Factory Calendar C OPJY - Maintain perf. efficiency rate key OPJZ - Maintain Release Periods OPK0 - Confirmation Parameters PP OPK0T Confirmation Parameters OPK1 - Confirmation Parameters PP-PI OPK1T Confirmation Parameters OPK2 - Formula Parameters OPK3 - Define Formula OPK4 - Confirmation Parameters OPK5 - Maintain variances OPK6 - List Layout OPK7 - Accessing Customizing PDC transfer OPK8 - Maintain print control prod. orders OPK9 - Maintain Goods Receipt Valuation OPKA - Maintain Movement Types OPKB - Control parallel confirmation OPKC - Control confirmation process chain OPKD - Control confirmation process chain OPKE - Screen Sequence for Components OPKF - Control parallel confirmation OPKG - Maintain Messages OPKH - Maintain Breakpoints OPKI - Maintain Collective Confirmation OPKJ - Maintain PRT Control Key OPKK - Standard Text OPKL - Formula Parameters OPKM - Define Formula OPKN - Overview variant production control OPKO - Command File for Production Orders OPKP - Shop floor control profile OPKQ - Customizing: Matchcode for Proc.Ord. OPKR - Print flag OPKS - Maintain Origins for CO Object OPKT - Initial Screen: Settlement Structure OPKU - Maintain Collective Confirmation OPKV - Print Flag OPKW - Print shop papers OPKX - Deletion Flag/Indicator OPKZ - Customizing Matchcode for ProdOrder OPL1 - Costing Variants: PP Prod. Order OPL2 - Maintain trigger point group OPL3 - Trigger point usage OPL4 - Profile for missing parts list OPL5 - Order type LIS parameters OPL6 - Profile for documented goods mvmts OPL7 - Order change management profile OPL8 - Order type parameters: Overview OPL9 - Parameters for order change mgmt OPLA - Conditions: V_T682F for H CO OPLB - CondTab: Create (batch, prod.) OPLC - CondTab: Change (batchs, prod.) OPLD - CondTab: Display (batches, prod.) OPLE - Strategy types: Batch determ. (prod) OPLF - Access: Maintain batch determ.(prod) OPLG - Batch determ.: Procedure for prod. OPLH - Overview variant - production orders OPLI - Background job for goods movements OPLJ - Job "Fast entry confirmation" OPLK - Overall profile for order prog. rep. OPLL - Order progress: Displayed fields OPLM - Order progress: Displayed fields OPLO - maintain selection profile OPLP - Job "Convert planned order" OPLQ - maintain filter for control keys OPLR - Maintain filter for capacity version OPLS - Parallel processing control OPLT - Target System for Data Transfer OPLV - Maintain Filter for Task List Usage OPLW - Maintain Filter for Task List Status OPLX - Maintain Filter for BOM Usage OPLY - Maintain Filter for BOM Status OPLZ - Maintain POI Planned Order Selection OPM0 - Maintain profile - field selection OPM1 - Costing Variants - Production Order OPM2 - Maintain Detail Screen Control Oper. OPM3 - Maintain Detail Scrn Control Header OPMF - Field Selection - BOM Transfer OPMI - Import models activities OPMJ - Determine progress values OPN0 - Master Recipe Profile OPN1 - Maintain Profiles for Master Recipes OPN2 - Valuation Variants - Prod. Order OPN3 - Overv.Var.: Master Recipe Scheduling OPN5 - Field Seln: Std Network Overview OPN6 - Field Selection Standard Network Hdr OPN7 - Field Sel.:Std Ntwk Activity Detail OPN8 - Field Sel.:Std.Ntwk Comp.Overview OPN9 - Field Sel. Std Ntwk Comp.Detail OPO1 - Create Cost Element Planning Layout OPO2 - Change Cost Element Planning Layout OPO3 - Display Cost Element Planning Layout OPO4 - Create Stat. KF Planning Layout OPO5 - Change Stat. KF Planning Layout OPO6 - Display Stat. KF Planning Layout OPO7 - View Maintenance V_TCJ41_7 OPO8 - View Maintenance V_TCJ41_8 OPO9 - View Maintenance V_TCJ41_9 OPOA - View Maintenance V_T003O_N0 OPOB - View Maintenance V_T003O_N1 OPOC - View Maintenance V_T399X_N0 OPOD - View Maintenance V_T399X_N1 OPOE - View Maintenance T_T399X_N2 OPP1 - Customizing MRP OPP2 - MPS OPP3 - Customizing Repetitive Manufacturing OPP5 - List Profile Component List OPPA - PP/MRP Customizing Explosion OPPB - Direct Procurement OPPC - Period Grouping OPPD - Customizing Planning Time Fence OPPE - Conversion Plnnd Order -> Prod.Order OPPE01 General iPPE Customizing OPPE02 Define iPPE Node Type OPPE03 Define iPPE Variant Types OPPE04 Define iPPE Alternative Types OPPE05 Define iPPE Relationship Types OPPE06 Customer-Spec. Model Assgts (iPPE) OPPE07 Time Analysis: Partner Products iPPE OPPE11 Profiles: iPPE WB Professional OPPE12 Tabs: iPPE Workbench Professional OPPE13 User Assgmt: iPPE WB Professional OPPE14 Define Reports for iPPE WB Prof. OPPE15 Define Interface for iPPE Workbench OPPE20 Profile Maintenance iPPE PS OPPEACT01 - - Define Std Val. Determin. Type OPPEACT02 - - Object Dependency in Process Struct. OPPECHK01 - - Customizing: Consistency Check OPPEDOK Documentation OPPELUI01 - - Profile Definition: iPPE WB Express OPPELUI02 - - User Assignment: iPPE WB Express OPPERES01 - - Customizing for Production Resources OPPESCMPV - - Object Dependent Status Management OPPESTATUS - Cross-Application Status Management OPPF - Customizing for Order Report OPPH - Customizing Purchase Req. Conversion OPPI - Available Stock OPPJ - MRP Checking Rule OPPK - Hierarchy Element OPPL - MRP OPPM - Evaluation Profiles OPPN - Layout OPPO - Hierarchy Element OPPP - Customizing Direct Procurement OPPQ - C M MRP Plant Parameters for MRP OPPR - C M MRP MRP Group OPPS - Strategy OPPT - Strategy Group OPPU - Strategy Group for MRP Group OPPZ - MRP Group OPR1 - Area of Responsibility <-> Message OPR3 - Definition of Breakpoints OPR4_ACT - - Multilevel Actual Settlement OPR4_CK Material Cost Estimate OPR4_CKMC - - Mass Costing - Sales Documents OPR4_CKML - - Closing and Calc. of Periodic Price OPR4_CKPF - - Price Update OPR4_FCO - - Collective Processing: Variances OPR4_KKA - - WIP Calculation OPR4_KKP - - Repetitive Mfg and Process Mfg OPR4_KKS - - Collective Processing: Variances OPR4_KKS1 - - Individual Processing: Variances OPR4_PPCO - - Production Order: Cost Calculation OPR5 - Definition of Error Mgmt IDs (SAP) OPR6 - Definition of Object IDs (SAP) OPR7 - Def. of Areas of Responsibility OPR8 - Def. of Minimum Message Types (SAP) OPR9 - Def. of Reference Objects (SAP) OPRCMFE User-Defined Messages OPRF - Maintain Quotation Prefixes OPS - Customizing for Project System OPS0 - Maintain print control for networks OPS1 - Maintain User Fields OPS2 - Maintain Relationship Texts OPS3 - Maintain PS Text Types OPS4 - maintain simulation profile OPS5 - Maintain Standard Network Profile OPS6 - Maintain Project Manager OPS7 - Maintain Applicant OPS8 - Materialflow network OPS9 - Budget Management Profile OPSA - Maintain Project Profile OPSB - Cost Planning Profile OPSC - Create network types OPSCAS Command File Payments (PS) OPSCOS Command File Costs (PS) OPSD - Maintain Profile for Report Lines OPSE - Maintain Report Groups OPSF - Maintain Report Variations OPSG - Order change management profile OPSH - Maintain ctrl. key for activity (PS) OPSI - Edit PS validation rules OPSINS Command File Info System (PS-F) OPSJ - Maintain Project Coding OPSK - Maintain Special Characters OPSL - Project Info System Overview Maint. OPSM - Maintain Overall Profile PS InfoSys OPSN - Edit PS substitution rules OPSO - Maintain Project Types OPSP - Capacity availability check OPSPAR1 Maintain Partner Functions OPSPAR2 Define Lang.-Dep.Partner Functions OPSPAR3 WBS Partner Profile OPSQ - Intervals for Cost/Revenue Types OPSR - Maintain milestones OPSREV Command File Revenues (PS) OPSS - Maintain milestones OPST - Network Confirmation Parameters OPSU - Maintain Activity Control Key OPSV - Cost object ind. OPSW - Info System Profile OPSX - PS: Reset "Budgeted" Status OPT1 - Maintain PS Transaction Types OPT2 - Matchcode for project definition OPT3 - Matchcode for WBS elements OPT4 - Matchcode for standard network OPT5 - Customizing matchcode for network OPT6 - Maintain std. milestone group OPT7 - Project planning board profile OPT8 - Maintain hierarchy graphic / dates OPT9 - Network parameters for PS-SD OPTA - Command file for PS -> FI area OPTB - Command file for WBS OPTC - Command file for network OPTD - Command file for standard network OPTE - Command file for PS info system OPTF - Command file for PS graphic OPTG - Maintain PS Info Summztn Criteria OPTH - PS info system maintenance OPTI - Maintain Progrss Analysis Overview OPTJ - Maintain PS Info Unit Conversion OPTK - Exclude Cost Elems from Avlbty Cntrl OPTL - Maintain PS Info Comparison Criteria OPTM - Fincl Budgeting Profile for Projects OPTN - Maintain priorities OPTO - Change costing variants OPTP - Sub-network parameters OPTQ - Maintain WBS scheduling parameters OPTR - Strategies for settlement rules OPTS - Maintain project version profile OPTT - Maint. acct.assgnm.types for orders OPTU - Maint. PS Info System field settings OPTV - Maint. PS Info System sort criteria OPTW - Maint.PS Info System group. criteria OPTX - Maint. PS Info System database set. OPTY - Capacity leveling - Time profile/PS OPTZ - Matchcode for standard WBS elements OPU0 - Matchcode for standard project def. OPU3 - Production order control parameters OPU4 - Maintain Capacity Planning (SOP) OPU5 - Parameter long term planning PlndOrd OPU6 - Production order control parameters OPU7 - Control parameters plant maintenance OPU8 - Overview Var.: Header Line Info Sys. OPU9 - Overview Variant: Item Line OPUA - Field selection: Network: Header OPUB - Field selection: Network: Overview OPUC - Field selection: Network: Details OPUD - Field selection:Network confirmation OPUH - Field sel: Std. project definition OPUI - Field selection: Std. WBS elements OPUJ - Field selection: Project definition OPUK - Field selection: WBS element OPUL - PS: Maintain reduction strategies OPUM - Maintain Subprojects OPUN - Capacity overviews OPUO - Project schedule overviews OPUP - Subnetwork schedule overview OPUQ - Overall network scheduling overview OPUR - Info System: Structure overview OPUS - Maintain Version Number Entry Mask OPUT - Maintain overview variants OPUU - Maintain Network Profile OPUV - Network Type Parameters OPUW - Standard Network Status OPUX - Maintain overview variants std netwk OPUY - Overview var.:Std.ntwrk scheduling OPUZ - Control parameters plant maintenance OPVC - Convert Avlability Cntrl Tol.Limits OPVP - Collective availibility checkProfile
Subscribe to:
Posts (Atom)