Collection of materials related to SAP BW 7.3

My plan is regularly adding materials which are related to new version of BW: 7.3 at this blog post. This goes along my blog related to BW history posted here.


Documentation:
help.sap.com 1
help.sap.com 2



Documents:

What’s new with SAP NetWeaver BW 7.30 and BW Accelerator 7.20
SAP NW BW 7.3 Overview & Roadmap SAP BW Product Management April 2011
What’s new with SAP NetWeaver BW 7.3 Product Management March 2011

SDN Blogs:

BW 7.3 beta is available

BW 7.3: Define Delta in BW and no more Init-InfoPackages

BW 7.3: Simple modeling of simple data flows
Creation of New Data flow trough Wizard tool in SAP BW 7.3
BW 7.3: Input ready formulas in BW Integrated Planning
BW 7.3: Simple supervision of process chains 
BW 7.3: The New Planning Modeler  
BW 7.3: Transport support in BW landscapes
BW 7.3 dataflow modeller: What do I need to know?  
BW 7.3 hierarchy framework
BW 7.3: Data Validations and Performance Improvements for Planning Applications 
BW 7.3: Semantically Partitioned Objects (SPOs) built from BAdI – Consistent, Rule Based Modeling of Logical Partitions 
BW 7.3: Troubleshooting Real-Time Data Acquisition
BW 7.30: Data Flow Copy Wizard
Dataflow Copy Tool: How to use Dataflow Copy tool to speed up the development activity
Enhanced data flows in BI 7.3
BW 7.30: Graphical Data Flow Modeling
upgrade in less than 3 hours
Performance Improvements for DataStore Objects 
My favourite BW 7.3 and BI 4.0 blogs
SAP BW Developers SDN Blog series accompanying the BW 7.3 Ramp-Up phase
Basic features of BW 7.3 compared to BW 7.0 
What's New in the SAP BW Near-Line Storage Solution
Modeling integration between SAP Business Objects Data Services and BW | Part 1 of 2 – Connect Source System
Performance Improvements in Master-Data related scenarios and DTP Processing 
Modeling integration between SAP Business Objects Data Services and BW | Part 2 of 2 - Create DataSource  
New MDX test environment
Remodeling in SAP BI 7.00 
HANA and BW 7.30 - Part 1
HANA and BW 7.30 - Part 2
Remodeling on DSO
Restricting the value help in the variables screen of a query
Need a magician to connect JAVA to BW 7.30 after the installation … ?  
BW 7.3 news from BI at Amsterdam 
'Force Delta' in BW Dataflows
User Interface for Hybrid Providers
Hybrid Provider in a Nutshell
Précis about the HybridProvider
Simple supervision of process chains 
Data Flow Migration tool: Migrating 3.x flows to 7.3 flows and also the recovery to 3.X flow
Exporting Hierarchy using Open Hub Destination into Flat file from BW 7.3
Hierarchy Framework – a real-life example
Hierarchy loading becomes easier with the help of new framework
Easy queries on SAP NetWeaver BW
Different ways to delete Master data 

BW 7.3: Process Chain and the art of Wizardry

Pattern-based Partitioning using the SPO BAdI
Part 1: Introduction
Part 2: BAdI Managed Maintenance 
Part 3: Partitioning Patterns
Part 4: Use Cases


New DSO activation logic: 
Performance Improvements for DataStore Objects
BW Fine Tuning on Netweaver BW 730 - Part 1
BW Fine Tuning on Netweaver BW 730 - Part 2

LSA Data Flow Templates Series:
I. Introduction 
II. Basics for Data Flow Templates
III. Layering data & logic
IV. Flow extensions - Corporate Memory (CM) & Harmonization InfoSOurce
V. Tactical Scalability - Flow split usingsemantic partitioning
VI. Scalability – Flow split and infosources
VII. Scalability – infosourecs & single ERP source
VIII. Scalability – Entire data flow split
IX. Scalability – Data flow split using a pass thru Datastore object
X. Scalability & Data domains – Strategic semantic partitioning of entire BW (SPLIT)
XI. Scalability & Data domains – Strategic semantic partitioning of entire BW (COLLECT)
XII. Scalability & Data domain – Business transformation layer



Upgrade to 7.3:
A BW 7.3 Upgrade this Summer?
The diary of a BW 7.3 Ramp-Up project (Part 1)
The diary of a BW 7.3 Ramp-Up project (Part 2)
The diary of a BW 7.3 Ramp-Up project (Part 3)
The diary of a BW 7.3 Ramp-Up project (Part 4)
The diary of a BW 7.3 Ramp-Up project (Part 5)

Upgrading to NetWeaver BW 7.3 - our story - Part 1, a brief history of mankind
Upgrading to NetWeaver BW 7.3: Our story part 2 - the long hard road 
Upgrading to NetWeaver BW 7.3 - Our story part 3, getting through cutover 
Upgrading to NetWeaver BW 7.3 - Our story part 4, how Project Santa became Project Valentine
Upgrading to BW7.3 the unconventional way

Othet blogs:

New transaction codes in BW 73

-    Update 25/01/2012 –
See Features of SAP BW 7.3

Finally there is a list of RSADMIN table parameters

Have you ever wondered why there is no some collective SAP Note describing all the parameters available in system for RSADMIN table? For me it would be logical to have such a note. In some of SDN forum’s it is mentioned that was such a note but over the years it became internal and therefore not accessible for SAP’s customers and event no for partners. If you imagine that according google there are 364 pages on the internet referencing to this note it would be very appreciated by SAP community that this note would be is available again. Might be that after lobbing of BW folks in SDN forums people at SAP decided to release it back to customers. That happen precisely on 20^th of August 2010 when version 25^th of this note suddenly appeared on OSS. 

Ladies and gents here it comes:

912367 - Composite Note: RSADMIN Parameter

P.S.: Many thank to Colum Cronin to announce that at this SDN forum thread.

- Update 20/02/2016 -

Adding one more SAP Note related to parameters of RSADMIN table this time there are parameters related to BEx like Business Explorer Tools BEx Precalculation Server

1878949 - Collective Note: RSADMIN parameters

- Update 20/MAR/2022 –

For BW4/HANA based systems see SAP Note 2769125 (Composite Note: RSADMIN Parameter for SAP BW/4HANA) to get an overview on valid RSADMIN params.

Related posts:

Parameters of RSADMINC table

Parameters of RSADMINA table

How to work with RSADMINA, RSADMINC and RSADMINS tables

How to work with RSADMIN table

BW4 - Parameters of RSADMIN table

How to properly design process chains

There are sometimes doubts regarding how to set up processes within the process chains. Process chain is structural and logical grouping of processes , jobs or steps involved within loading of data into BW. Proper design of chain has effects on its performance and consequently on performance of whole BW system. Therefore kind of best practice I can recommend following sequence for designing process chains:

a.    Delete Index

b.    Data Transfer Process / Execute InfoPackage – optimally in parallel

c.    Generate Index

d.    Construct Database Statistics

e.    Compress cube

f.     Delete PSA (aged data requests)

g.    Delete Change Log (aged data requests)

Here’s quite obsolete picture from SAP presentation material depicting loading process in BW 3.0.

Grey rating for Earlywatch Alert report

Sometimes it is common situation that you receive the latest Earlywatch Alert (EWA) report from SAP and some of checks included have grey ratings. Usually there are suppose to be just three types of ratings:

Green – no major problems with systems observed, hurray :-)

Yellow – improvements to the system were detected

Red – severe problems were detected, you should take corrective actions immediately

Then what is going on while grey traffic lights are delivered? Simply this means that automated system that was generated this EWA report had no enough data to analyze the system. E.g. situation occurred in your system that it wasn’t recognized, connection into system was down, system as itself was down etc. There is an SAP Note discussing such situations here:

Note 762696 - Grey rating for Earlywatch Alert

Where to see code for Business Content SAP exit variable?

SAP exit variable are type of BEx variables processed during BEx Query runtime by replacement path predefined in SAP exit. SAP exit is like customer exit it is just delivered by standard SAP BW Business Content. Comparison to customer exit is right since there is also ABAP code which is in particular performing the replacement of variable value.

This might seems to be tricky for first look: Where to see ABAP code for BEx variables a type of SAP exit? Actually again comparing to user exits variable it is stored in ABAP repository but in include just in function modules:

In our case for variable 0P_SYSID there is the function module called RSVAREXIT_0P_SYSID where all the variable logic is coded:

update - 27-09-2012-

Older business content variables (e.g. 0CWD) are coded in FM RREX_VARIABLE_EXIT. 

Difference between DB and BW statistics

Terms like database (DB) and BW statistics are often referred in SAP documentation, Notes or even in SDN forums. We always hear that it is important to maintain statistics in order to achieve good performance of SAP systems. Especially in BW area performance topic is very important. Here it is often discussed that we must keep the DB statistics all the time for SAP BW. Then we hear that BW statistics mull be keep up to date as well. You can get easily confused with mixing a meaning of those two terms.

So basically what DB statistics is all about? Underlying database systems are using sophisticated algorithms to determine “a path” how to execute SQL statements. In detail a path is comprised of type of DB access (index access, full table scan, join types, memory requirements, table stats, index stat, column stat, histogram, partitioning, parallelism, clustering, etc.) how particular SQL statement is performed. In order to determine it DB engine is evaluating DB statistics which is basically about evaluation of how many I/O DB operations would take to perform DB statement with different DB access. The DB access with the fewest I/O DB operations is then executed to fulfill SQL statement. DB statistics is depended on type of used DB platform. E.g. in ORACLE there is a component of DB engine called Cost-Based SQL optimizer (CBO). Therefore sometime we call this type of statistics as an Optimizer statistics. This tool is in charge of SQL statement execution governing. This component is evaluating DB statistics. On other DB platform such a component is commonly called Query optimizer.

Now the questions would be how can we build DB stat? DB statistics can be build from BW perspectives within process chains via process called “Construct Database Statistics”. From basis point of view most common is to use BRTOOLs to build this statistics in case of ORACLE DB. Another option is to use transaction DB20 or report RSANAORA.

For more information about DB statistics see SAP Note 588668 - FAQ: Database statistics.

What about other term - BW statistics? It is a part of technical Business Content which helps to evaluate performance of SAP BW system. There are two main areas of performance evaluation: OLAP processor and Warehouse Management (WM).

Within OLAP processor gives an information how BW reporting is performing. A way how statistics data is collected If is like following. Every navigational step within the reporting that requests data from the database is saved in transparent table in BW backend (tables RSDDSTATHEADER, RSDDSTATINFO, RSDDSTATEVDATA). This includes characteristics, navigation attributes and hierarchies were involved. Here an event concept is used. Event is uniquely identifying each step in the process. From DB tables statistics data are loaded into BW statistics InfoCubes via technical process chains.

In case of WM statistics or Data Load statistics it is determining performance of loading, transforming the data and all the others staging operations. In principle system is gathering the data about process chains, DTPs and InfoPackages. Here e.g. time of execution is stored along other data load statistics data. Table where data is written is RSDDSTATWHM. WM statistics is customized via transaction RSDDSTAT.

BW statistics is a part of BI Administration Cockpit. See 934848 - Collective note: (FAQ) BI Administration Cockpit, for BW 3.x see: 309955 - BW statistics - Questions, answers and errors.

Notice that BW statistics was redesigned in BW version 7.x and it does use different tables comparing to BW 3.x.

More information:

588668 - FAQ: Database statistics

555030 - Deactivating BW-initiated DB statistics

1013912 - FAQ: Oracle BW performance

CCMSBISUITE Reporting Suite

There is a new tool for BW performance monitoring available as of BI_CONT 703 Support Package 8 for NetWeaver 7.0 or with SAP_BW Support Package 4 for NetWeaver 7.10.

Source of data is Central Performance History (CPH) which is a part of SAP’s CCMS. Same tool is includes in Solution Manager’s under node "IT Performance Reports". Directly in BW system you can access it via transaction CCMSBISUITE.

Tool needs to be installed first by using transaction CCMSBISETUP in BW system. 

The Suite is currently having following reports:

·         overview on the availability of instances

·         CPU utilization,

·         database growth

·         user logons

·         Java key figures such as garbage collection and sessions

See following notes for details:

1065835 - Reporting Suite

1119686 - CCMS Reporting Suite scenario

979581 - Installing and configuring the CCMS BI Content

Reserved ABAP keywords

Sometime it is little bit tricky to find out a name for new variable in ABAP until you do not break into a set of reserved ABAP keyword. Basically such a set of reserved words are all the ABAP statements key words, logical operators, data types, predefined functions, etc. According official SAP documentation (see TA ABAPDOCU -> ABAP - By Theme -> ABAP syntax -> ABAP Statements ->ABAP Words) usage of those key words is not forbidden (see picture) we should try avoiding using them. It might happen that there will be some new key words added and your code will not be compatible with further new version of SAP ABAP/Basis/WAS component. 

Therefore while you designing new variable names consider following names as those which are forbidden and you cannot use them as variable names:

ABAP-SOURCE	ABBREVIATED	ABS	ABSTRACT	ACCEPT
ACCEPTING	ACCORDING	ACOS	ACTIVATION	ACTUAL
ADD	ADD-CORRESPONDING	ADJACENT	AFTER	ALIASES
ALL	ALLOCATE	ANALYSIS	ANALYZER	AND
ANY	APPEND	APPENDAGE	APPENDING	APPLICATION
ARCHIVE	AREA	ARITHMETIC	AS	ASCENDING
ASIN	ASSERT	ASSIGN	ASSIGNED	ASSIGNING
AT	ATAN	ATTRIBUTES	AUTHORITY	AUTHORITY-CHECK
AVG	BACK	BACKGROUND	BACKUP	BACKWARD
BADI	BEFORE	BEGIN	BETWEEN	BIG
BINARY	BIT	BIT-AND	BIT-NOT	BIT-OR
BIT-XOR	BLACK	BLANK	BLANKS	BLOCK
BLOCKS	BLUE	BOUND	BOUNDARIES	BOUNDS
BREAK-POINT	BT	BUFFER	BY	BYPASSING
BYTE	BYTE-CA	BYTE-CN	BYTE-CO	BYTE-CS
BYTE-NA	BYTE-NS	BYTE-ORDER	C	CA
CALL	CALLING	CASE	CASTING	CATCH
CEIL	CENTERED	CHAIN	CHAIN-INPUT	CHAIN-REQUEST
CHANGE	CHANGING	CHAR-TO-HEX	CHARACTER	CHARLEN
CHECK	CHECKBOX	CIRCULAR	CLASS	CLASS-CODING
CLASS-DATA	CLASS-EVENTS	CLASS-METHODS	CLASS-POOL	CLEANUP
CLEAR	CLIENT	CLIKE	CLOCK	CLOSE
CN	CO	CODE	CODEPAGE	CODING
COL_BACKGROUND	COL_GROUP	COL_HEADING	COL_KEY	COL_NEGATIVE
COL_NORMAL	COL_POSITIVE	COL_TOTAL	COLLECT	COLOR
COLUMN	COMMENT	COMMENTS	COMMIT	COMMON
COMMUNICATION	COMPARING	COMPONENT	COMPONENTS	COMPRESSION
COMPUTE	CONCATENATE	CONDENSE	CONDITION	CONNECT
CONNECTION	CONSTANTS	CONTEXT	CONTEXTS	CONTINUE
CONTROL	CONTROLS	CONVERSION	CONVERT	COPIES
COPY	CORRESPONDING	COS	COSH	COUNT
COUNTRY	COVER	CP	CPI	CREATE
CS	CSEQUENCE	CURRENCY	CURRENT	CURSOR
CURSOR-SELECTION	CUSTOMER-FUNCTION	D	DATA	DATABASE
DATAINFO	DATASET	DATE	DAYLIGHT	DBMAXLEN
DD/MM/YY	DD/MM/YYYY	DDMMYY	DEALLOCATE	DECIMALS
DEFAULT	DEFERRED	DEFINE	DEFINING	DEFINITION
DELETE	DELETING	DEMAND	DEPARTMENT	DESCENDING
DESCRIBE	DESTINATION	DETAIL	DIALOG	DIRECTORY
DISCONNECT	DISPLAY	DISPLAY-MODE	DISTANCE	DISTINCT
DIV	DIVIDE	DIVIDE-CORRESPONDING	DO	DUMMY
DUPLICATE	DUPLICATES	DURING	DYNAMIC	DYNPRO
E	EDIT	EDITOR-CALL	ELSE	ELSEIF
ENABLED	ENABLING	ENCODING	END	END-ENHANCEMENT-SECTION
END-LINES	END-OF-DEFINITION	END-OF-FILE	END-OF-PAGE	END-OF-SELECTION
ENDAT	ENDCASE	ENDCATCH	ENDCHAIN	ENDCLASS
ENDDO	ENDENHANCEMENT	ENDEXEC	ENDFORM	ENDFUNCTION
ENDIAN	ENDIF	ENDING	ENDINTERFACE	ENDLOOP
ENDMETHOD	ENDMODULE	ENDON	ENDPROVIDE	ENDSELECT
ENDTRY	ENDWHILE	ENHANCEMENT	ENHANCEMENT-POINT	ENHANCEMENT-SECTION
ENHANCEMENTS	ENTRIES	ENTRY	ENVIRONMENT	EQ
ERRORMESSAGE	ERRORS	ESCAPE	ESCAPING	EVENT
EVENTS	EXCEPTION	EXCEPTION-TABLE	EXCEPTIONS	EXCLUDE
EXCLUDING	EXEC	EXECUTE	EXISTS	EXIT
EXIT-COMMAND	EXP	EXPAND	EXPIRATION	EXPLICIT
EXPONENT	EXPORT	EXPORTING	EXTENDED	EXTENSION
EXTRACT	F	FETCH	FIELD	FIELD-GROUPS
FIELD-SYMBOLS	FIELDS	FILE	FILTER	FILTERS
FINAL	FIND	FIRST	FIRST-LINE	FIXED-POINT
FKEQ	FKGE	FLOOR	FLUSH	FONT
FOR	FORM	FORMAT	FORWARD	FOUND
FRAC	FRAME	FRAMES	FREE	FRIENDS
FROM	FTO	FUNCTION	FUNCTION-POOL	GAPS
GE	GENERATE	GET	GIVING	GKEQ
GKGE	GLOBAL	GREEN	GROUP	GROUPS
GT	HANDLE	HANDLER	HASHED	HAVING
HEAD-LINES	HEADER	HEADERS	HEADING	HELP-ID
HELP-REQUEST	HIDE	HIGH	HINT	HOLD
HOTSPOT	I	ICON	ID	IDENTIFICATION
IDENTIFIER	IDS	IF	IGNORING	IMMEDIATELY
IMPLEMENTATION	IMPLEMENTATIONS	IMPORT	IMPORTING	IN
INCLUDE	INCLUDES	INCLUDING	INCREMENT	INDEX
INDEX-LINE	INFOTYPES	INHERITING	INIT	INITIAL
INITIALIZATION	INNER	INOUT	INPUT	INSERT
INSTANCES	INTENSIFIED	INTERFACE	INTERFACE-POOL	INTERFACES
INTERNAL	INTERVALS	INTO	INVERSE	INVERTED-DATE
IS	JOB	JOIN	KEEP	KEEPING
KERNEL	KEY	KEYS	KEYWORDS	KIND
LANGUAGE	LAST	LATE	LAYOUT	LE
LEADING	LEAVE	LEFT	LEFT-JUSTIFIED	LEGACY
LENGTH	LEVEL	LEVELS	LIKE	LINE
LINE-COUNT	LINE-SELECTION	LINE-SIZE	LINEFEED	LINES
LIST	LIST-PROCESSING	LISTBOX	LITTLE	LOAD
LOAD-OF-PROGRAM	LOCAL	LOCALE	LOG	LOG-POINT
LOG10	LOGFILE	LOOP	LOW	LOWER
LPI	LT	M	MAIL	MAIN
MAJOR-ID	MARGIN	MARK	MASK	MATCH
MATCHCODE	MAX	MAXIMUM	MEMORY	MESSAGE
MESSAGE-ID	MESSAGES	METHOD	METHODS	MIN
MINIMUM	MINOR-ID	MM/DD/YY	MM/DD/YYYY	MMDDYY
MOD	MODE	MODIF	MODIFIER	MODIFY
MODULE	MOVE	MOVE-CORRESPONDING	MULTIPLY	MULTIPLY-CORRESPONDING
N	NA	NAME	NAMETAB	NATIVE
NB	NE	NESTING	NEW	NEW-LINE
NEW-PAGE	NEW-SECTION	NEXT	NO	NO-DISPLAY
NO-EXTENSION	NO-EXTENSIONS	NO-GAP	NO-GAPS	NO-GROUPING
NO-HEADING	NO-SCROLLING	NO-SIGN	NO-TITLE	NO-TOPOFPAGE
NO-ZERO	NODE	NODES	NON-UNICODE	NON-UNIQUE
NOT	NP	NS	NULL	NUMBER
NUMERIC	NUMOFCHAR	O	OBJECT	OBJECTS
OBLIGATORY	OCCURRENCE	OCCURRENCES	OCCURS	OF
OFF	OFFSET	OLE	ON	ONLY
OPEN	OPTION	OPTIONAL	OPTIONS	OR
ORDER	OTHERS	OUT	OUTER	OUTPUT
OUTPUT-LENGTH	OVERFLOW	OVERLAY	P	PACK
PACKAGE	PADDING	PAGE	PAGES	PARAMETER
PARAMETER-TABLE	PARAMETERS	PART	PATTERN	PERCENTAGE
PERFORM	PERFORMING	PERSON	PF	PF-STATUS
PINK	PLACES	POOL	POSITION	PRECOMPILED
PREFERRED	PRESERVING	PRIMARY	PRINT	PRINT-CONTROL
PRIORITY	PRIVATE	PROCEDURE	PROCESS	PROGRAM
PROPERTY	PROTECTED	PROVIDE	PUBLIC	PUSHBUTTON
PUT	QUEUE-ONLY	QUICKINFO	RADIOBUTTON	RAISE
RAISING	RANGE	RANGES	READ	READ-ONLY
RECEIVE	RECEIVED	RECEIVER	RECEIVING	RED
REDEFINITION	REF	REFERENCE	REFRESH	REGEX
REJECT	RENAMING	REPLACE	REPLACEMENT	REPLACING
REPORT	REQUEST	REQUESTED	RESERVE	RESET
RESOLUTION	RESPECTING	RESPONSIBLE	RESULT	RESULTS
RETURN	RETURNCODE	RETURNING	RFC	RIGHT
RIGHT-JUSTIFIED	ROLLBACK	ROUND	ROWS	RUN
SAP	SAP-SPOOL	SAVING	SCAN	SCREEN
SCROLL	SCROLL-BOUNDARY	SCROLLING	SEARCH	SECONDS
SECTION	SELECT	SELECT-OPTIONS	SELECTION	SELECTION-SCREEN
SELECTION-SET	SELECTION-SETS	SELECTION-TABLE	SELECTIONS	SEND
SEPARATE	SEPARATED	SET	SHARED	SHIFT
SHORTDUMP-ID	SIGN	SIMPLE	SIN	SINGLE
SINH	SIZE	SKIP	SKIPPING	SMART
SOME	SORT	SORTABLE	SORTED	SOURCE
SPECIFIED	SPLIT	SPOOL	SPOTS	SQL
SQRT	STABLE	STAMP	STANDARD	START-OF-SELECTION
STARTING	STATE	STATEMENT	STATEMENTS	STATIC
STATICS	STATUSINFO	STEP-LOOP	STOP	STRING
STRLEN	STRUCTURE	STRUCTURES	SUBKEY	SUBMATCHES
SUBMIT	SUBROUTINE	SUBSCREEN	SUBSTRING	SUBTRACT
SUBTRACT-CORRESPONDING	SUFFIX	SUM	SUMMARY	SUMMING
SUPPLIED	SUPPLY	SUPPRESS	SWITCH	SWITCHSTATES
SYMBOL	SYNCPOINTS	SYNTAX-CHECK	SYNTAX-TRACE	SYSTEM-CALL
SYSTEM-EXCEPTIONS	SYSTEM-EXIT	T	TAB	TABBED
TABLE	TABLES	TABLEVIEW	TABSTRIP	TAN
TANH	TASK	TEST	TESTING	TEXT
TEXTPOOL	THEN	TIME	TIMES	TITLE
TITLE-LINES	TITLEBAR	TO	TOKENIZATION	TOKENS
TOP-LINES	TOP-OF-PAGE	TRACE-FILE	TRACE-TABLE	TRAILING
TRANSACTION	TRANSFER	TRANSFORMATION	TRANSLATE	TRANSPORTING
TRMAC	TRUNC	TRUNCATE	TRUNCATION	TRY
TYPE	TYPE-POOL	TYPE-POOLS	TYPES	ULINE
UNASSIGN	UNDER	UNICODE	UNIQUE	UNIT
UNIX	UNPACK	UNTIL	UP	UPDATE
UPPER	USER	USER-COMMAND	USING	UTF-8
VALID	VALUE	VALUE-REQUEST	VALUES	VARY
VARYING	VERIFICATION-MESSAGE	VERSION	VIA	VISIBLE
WAIT	WARNING	WHEN	WHENEVER	WHERE
WHILE	WIDTH	WINDOW	WINDOWS	WITH
WITH-HEADING	WITH-TITLE	WITHOUT	WORD	WORK
WRITE	X	XML	XSEQUENCE	XSTRING
XSTRLEN	YELLOW	YYMMDD	Z	ZONE