Overview of XXP and its SAP Implementation
April 2, 2003, Glenn Booker
Warning – lists of acronyms appear later…you’ll need them!
Scope of XXP
The Extremely Expensive Program (XXP) is designed to perform several key logistics services for its
customer. They are summarized in Table 1, and connected to their respective SAP modules (see later
for more details) and what kind of processes are involved in each. Table based on the Services
Description Document (SDD) Navigation Tool on the XXP web site. (Note: XXP is a fake program
name, to avoid conflict with any actual system.)
Table 1. XXP Services
XXP Service(s)
Demand and
Distribution
SAP Modules
Acquisition &
Distribution (A&D)
Types of Processes or Activities
Acquisition; Distribution
Inventory Management
Warehouse Management
Environment, Health, and Safety (EH&S)
Single Stock Fund Milestone 3 (SSF MS3)
Supply
Industrial Base
Manufacturing Execution
Operations (IBO)
Remanufacturing Execution
Quality Management
Human Resources
General Service Workload
Availability
Supply Chain
Manufacturing Planning
Planning (SCP)
Remanufacturing Planning
Global Available-To-Promise (GATP)
Finance
Budget &
General Accounting
Finance (B&F)
DFAS and Funds Management
Cost management
Budget Formulation
Projects
Product Support Product Lifecycle
Provisioning
Management (PLM) Cataloging
Packaging and Freight
Maintenance Engineering
Ammunition Support
Bill of Materials
Decision Support Business Information Reports for A&D, IBO, SCP, and B&F
Warehouse (BW)
Statutory and Regulatory Reports
Balanced Scorecard
Key Performance Indicators
Sustainment
none
Three-tier Help Desk
Continuous Improvement Program
Requirements Traceability
1
Their connection to the various suppliers, depots (warehouses), users, etc are shown in Figure 1.
Figure 1. XXP Modernized Services
Suppliers and
Vendors
Demand
AMC
Management
Decision
Support
d
an
m
De
) )
ow re
( n tu
ly (fu
pp lity
Su labi
ai
Av
Distribution
Depot
Finance
(from all
actors)
AMC Finance
Staff
AMC
Analysts
End User
(Battalion,
etc.)
Product Support and Sustainment are
performed at the PDC, COOP, and NOC.
In order to perform various services, each facility is broken down into work or cost centers. Personnel
within a work center are divided into resource groups (kind of like departments). Their activities are
described in routings or task lists (essentially procedures), which describe how to assemble a product,
overhaul a product, put together a shipment, etc. Every product is defined by a bill of materials, which
lists the parts which go into assembly of that product. Those products and/or parts are in turn cited by
the routings. These relationships are shown in Figure 2. A plant may be identified by its DODAAC
code. Parts may also be identified by their National Stock Number (NSN).
Figure 2. Connections between Plants and Products
has
y
man
Plant
(Facility)
Product
Work Center
(Cost Center)
co
ns
of ists
Resource
Groups
is
de
f
by ined
Bill of Materials
(BOM)
2
has
many
perfor
m
s
Routing
(Task List)
ed
uc
d
o
pr by
is
Part Number
(NIIN)
XXP Architecture
The XXP solution (a euphemism for the system developed and used to provide the services mentioned
above) is based on conversion of two huge legacy information systems into an integrated SAP R/3-based
system. To allow for scalability and help reliability, the solution is structured in a multi-tier clientserver manner, where most of the server side is shown in Figure 3.
Each type of function is given its own dedicated servers, so that the number of servers for any function
can be easily changed to accommodate more users and more data. The number of servers of each type
ranges from two (for the database servers), to over a hundred. The system is designed to handle a few
terabytes of active data, and tens of thousands of users.
The types of servers include:









Database servers, which house the online data and the central instance of R/3
Servers to run the main SAP modules APO, BW, and KW
Backup servers and a tape library
Terminal servers, for clients who need terminal access across the government’s private network
Application servers, for all the other SAP components, and other commercial software
Web servers, since many clients will access the system across an internet protocol network
SeeBeyond servers, which manage the interfaces to external systems
Network servers, which run Cisco software to manage the network configuration
Security servers, to validate users and manage security certificates
For this system, SAP runs on top of an Oracle database, and the whole mess uses Sun servers connected
with Gigabit Ethernet on fiber optic cables and Cisco networking equipment. A firewall within the
network prevents outside users from directly accessing the database, backup, and SAP servers.
Figure 3. XXP Functional Architecture (partial)
Dual SAP R/3
Database
Server and
Central
Instance
Internet
Ext. Interfaces
iPlanet Web
Portal,
Security, and
SeeBeyond
Servers
APO, BW,
and KW
Servers
Application
Servers
Gigabit Fiber Optic Bus
3
Backup
Servers and
Tape Library
Citrix
Terminal
Servers
Internal
Firewall
External interfaces are handled using middleware called SeeBeyond. SeeBeyond acts as a central point
of contact for all external systems. Messages intended for those systems are packaged in an IDOC
(intermediate document). The IDOC tells SeeBeyond what kind of message it is (content format) and
where it needs to go (routing information). SeeBeyond then unwraps the IDOC, and sends the message
to the correct external system. This relationship is shown in Figure 4. In this case, the document is a
Document Identifier Code (DIC) for some transaction, and the external system is the Defense Automatic
Address System Center (DAASC). The reverse process is then followed when the external system needs
to send information to SAP.
Figure 4. Communication Between SAP and External Systems
IDOC
DIC
LMP (SAP)
- Defines DIC
- Wraps DIC in IDOC
DIC
SeeBeyond
- Extracts DIC
- Sends to DAASC
DAASC
(Trading Partner)
- Processes DIC
Scenarios
Each way in which someone might need to perform a function on XXP is defined using a scenario.
There are three types of scenarios.



Integrated Scenario (IS) – a series of many steps which follows some activity from start to finish;
similar to a use case.
Independent Scenario (IND) – a short set of steps which perform a useful function, but generally
isn’t a complete user activity like an integrated scenario.
Process Scenario (SCN) – a task which is generally one step in a larger integrated or independent
scenario.
Like use cases, IS and IND scenarios form the basis for all levels of integration and system testing, and
they are used to manage the contents of each deployment (release). In other words, the functions to be
implemented with each deployment are defined by the scenarios which will be implemented.
4
Technical Objects
Each piece of code, screen, report, table, or other code-related thing in SAP is called a technical object
(TO). The connections among scenarios and technical objects are shown in Figure 5. Technical objects
can be standard or custom.


Standard (or vanilla or SAP native) objects are defined primarily by SAP. They are customized
for use on a particular system by the activity called SAP Configuration. They include all of the
standard screens and transactions which have a two-letter, two-digit name format, like MM02,
CF28, etc. Changes to standard objects, beyond the predefined configurable options, is extremely
discouraged by SAP.
Custom objects are created by SAP development programmers using the ABAP language.
Pronounced “A-bop”, it is unique to SAP, but looks like a blend between Basic and Pascal. The
names of custom objects generally start with “Y” or “Z”, like the custom transactions ZFUND
and ZIGO.
o Some forms (FRM tech objects) are coded using a horrendous scripting language called
“SAPScript”. No one ever admits to knowing how to program in SAPScript.
Each type of scenario and object is described in Table 2, and their sources are described in Table 3. The
XXP portals merged on 3/10/2003, hence only one portal is shown.
Technical objects (TO) are the source code unit in SAP. There are dozens of types of technical objects,
with an elaborate naming convention to identify the type of each technical object. The types of objects
and scenarios are described in Table 4, along with an idea of how many of each are in the XXP system
so far.
 83% of TO are INF, ISP, JOB, REP, TAB, TRX, and USX objects
 17% of TO are all the other types (DTX, FRM, IDC, INP, MOD, MTC, OSS, OUT, RTN, SCR,
UTL, and WFL objects)
A technical object (“TO”) is a piece of custom programming that has been created to enhance the SAP
package, such as a custom report, interface, or user exit (special processing embedded into the standard
SAP code); a FIT object is a process scenario or set of business processes that users perform. The FIT
objects may or may not have custom programming (TOs) embedded within them.
Other things described in Figure 5 include the following:
Testing
The types of testing include:







Unit and String tests, and Interface String tests
Integrated Scenario Test (IST)
pre-SIT tests on the QAS environment
System Integration Tests (SIT)
Internal Quality Review (IQR)
Regression Test
Mock Go-Live
5


Process Trials
End-to-End (E2E) Tests
Interfaces
The interface objects (INF) are further defined by the Interface Configuration Database (ICDB), which
captures their physical connection characteristics, security needs, cutover needs, and point of contact.
Connection to each external interface is also defined by the Bridges and Uniques (B/U), which specifies
the communication format and contents of each physical interface.
Table 2. Types of Data, Objects, and Scenarios
Type
B/U - Bridges and
Uniques
BI - Business Issues
BPML - Business
Process Master List
BPP – Business
Processes and
Procedures?
CI - Configuration
Information
CR - Change
Requests
Description
Detailed external interface message structure
FIT object
Process scenarios (a set of related business processes
performed by users)
Interface technical descriptions
ICDB - Interface
Configuration
Database
IND - Independent
Scenarios
IS - Integrated
Scenarios
PTR – Program
Trouble Reports
RTM - Requirements
Traceability Matrix
SCN – Process
Scenarios (a.k.a. PS)
Test data
TO - Technical
Objects
White papers
Mechanism for resolving scope or technical approach issues
Master requirements list
Source or Owner
Portal, under tech dev
work products
Q&ADB on SAP
Portal
Process descriptions
Portal
Interface configuration info, cited by the BPML
Located in the Q&ADB
Main mechanism for discussing problems which affect
multiple parts of the system
Old CR database from
Eileen Miller; new one
from Steve Hopkins
Portal, under FIT Work
Products
Owned by Ginny Farri
Execution of an independent technical object which is not
normally performed within a set of user tasks.
Series of user actions with embedded technical objects,
which perform a significant function using the system
The main mechanism for reporting problems during data load
or testing.
Traces from requirements sources to SAP modules and CCSS
functions
Scenarios which are tested as part of SIT which were not
included in the larger integrated scenarios. Each SCN
contains a single PS. Process descriptions are under FIT
work products on the portal.
Test scripts, results
Custom programming; may include custom data elements,
tables, function modules, reports, forms, user exits, pricing
routines, interfaces, etc.
Discussion and analysis of issues
6
Portal
Portal
Portal
Was on the Portal…not
updated in many months
Portal
Located in master file for
each scenario in D1/326.
Portal
Portal
Table 3. XXP Data Sources
Source Name
CR Database
CRDB
Description
Change Requests (old), an Access application
Change Requests (new), an Oracle app.
Interface Configuration
Database (ICDB)
Issues Database
XXP Portal
Interface connectivity needs and contacts
Q&ADB
Test data
Business Issues (BI)
Home of the PTR, PS, IS/IND, and TO
databases, BPML, white papers, and BPPs
Home to Configuration Information
(CI) and Issues database
Test scripts, results
Source or Owner
Obtain access from Eileen Miller
Web application owned by Steve
Hopkins
Owned by Ginny Farri
Q&ADB on SAP
Portal
SAP database installed on
desktop
Located in the master file for
each scenario in HD1/326.
Requirements
The Requirements Traceability Matrix (RTM) maps each requirement from its source to the SAP
module which will implement it (APO, MM, etc.) and to the CCSS application number or unique which
used to perform that function. It also identifies whether each process is manual or automated.
There might be a connection between the RTM and the BPML. For example, the RTM has “PERFORM
PARTS EXPLOSION”, which could correspond to the BPML’s “Change BOM Explosion Numbers”,
which is done in transaction MDSP.
The RTM maps the requirements sources, which include CONOPS, CSLA, RIA, and SBCCOM task
orders, SSF MS3, and the IDEF process model. There is no direct connection between the RTM and
scenarios or objects.
SAP Transactions
The transaction codes generally follow a two-letter, two-digit sequence (e.g. ‘MM02’). Prefixes FO
(Real Estate Management functions), MC (Logistics Information System (LIS) functions), and ME
(pertaining to procurement records) account for about 17% of the 2976 unique SAP transaction names,
while another 21% are from the list {CG, CJ, CO, FB, FM, IM, IW, KB, KK, V-, or VL}, with from 40
to 70 codes having each of those prefixes.
SAP Modules
SAP modules are discussed in the next section.
7
Figure 5. Scenario and Object Relationships
ate
ar
in e
co
ns
i
of sts
consists
Technical
of
Objects (TO)
p
con hysica
figu
l
rati
on
3%
are
RPTxxxx,
IFCxxxx,
and
DTFxxxx
con
sist
of s
Interface
Objects
8
support
SAP
Modules
Interface
Configuration
Database
(ICDB)
ma
inclu y
de
BPML
(main
requirements
list)
re
la
to? ted
?
ted
rela ?
to?
Requirements
Traceability
Matrix (RTM)
traces
from
Process
Scenario
SCNxxxx
SAP
Transaction
Codes
(nearly 3000
of them)
Independent
Scenario
INDxxxx
INF
cts
obje
FIT
Object
97
ar %
e
consis
ts
of
Integrated
Scenario
ISxxxx
use
or one
mo
re
sist
con
of
consists
of
e
at
u
al
ev
eva
lu
co
ns
of ist
Tests
Configuration
Information (CI)
n
Deployment 1, 2, or 3
(or interim releases)
BPP (business
processes and
procedures)
w
do
ks o
ea int
br
ts
en
m
ple
im
ma
p
to s
PTR, Change Request (CR),
or Business Issue (BI) Could be written against any
process, scenario, object,
data load, or transaction
Requirements
Sources
Bridges and
Uniques
Table 4. Scenario and Technical Object Types
Prefix
Type
Number in
XXP
Meaning
DTF
Data conversion
record
Data Type file.
DTX
Tech. Object
<30
Data element
FO
Transaction
241
SAP transaction code prefix for Real Estate Management
FRM
Tech. Object
<40
Form
IDC
Tech. Object
>50
Interface – SeeBeyond side
IFC
FIT object
IND
Scenario
INF
Tech. Object
870
Interface – SAP side
INP
Tech. Object
<10
Loads a table
Interface?
Independent scenario
Integrated scenario – analogous to a use case
IS
Scenario
ISP
Tech. Object
140
Custom internal interface
JOB
Tech. Object
115
SAP Batch Job
MOD
Tech. Object
<10
Unknown
MTC
Tech. Object
<20
Match code (search help for SAP data)
OSS
Notes
90+
SAP patches for identified bugs in the standard SAP code from the
Online Service System (OSS).
OUT
Tech. Object
2
REP
Tech. Object
>100
RPT
FIT object
RTN
Tech. Object
SCN
Scenario
SCR
Tech. Object
68
Custom screen
TAB
Tech. Object
560
Custom table
TRX
Tech. Object
150
Custom Transaction (must start with the letter Z)
USX
Tech. Object
>190
User exit
UTL
Tech. Object
40
Utility
WFL
Tech. Object
50+
Workflow
Extract data internally
Report
Report?
36
Routine
Process scenario – often one step within an IS
9
SAP Modules
The structure of SAP is huge and complex. And to make it worse, they reuse acronyms in different parts
of the system (e.g. PP can be Production Planning or Project Planning).
SAP is composed of the core module, called R/3, and may use other modules called “bolt-ons” if your
system needs those functions. A web-based version of SAP is called “mySAP”, and it either lives as a
stand-alone system, or is supported by the full version of R/3. The structure and contents of mySAP and
SAP R/3 are shown in Figures 6 and 7, and the abbreviations are defined in Table 5. Other SAP and
XXP-related terms are defined in Table 6.
Figure 6. “mySAP” Modules
mySAP
CRM
SEM
E-procurement
EBP
BI
KM
BW
SCM
APO
Based on mySAP Technology Solution Fundamentals
10
Figure 7. SAP Modules
SAP
Bolt-ons are labeled
in bold italics
Core R/3
System
IBO Team
B&F
CS Module
PS
HR
SEM
A&D
SCP
MM
APO
Bolt-ons
R&M
BW
PLM
IM/WM
DP
CO-PA
OM
CPM
SD
SNP
BW
TEM
BPS
EHS
PP
SEM
PM
PP
CO
(see below)
FI
DS
CO
FI
(see below)
PC
FM
SL
GL
PA
MRP
OM
RE
CCA
AA
PLM
PCA
CEL
AR
QM
Based on LearningGateway course
11
AP
Table 5. SAP and mySAP Modules
Acronym
ABAP
A&D
AA or
TV
AP
APO
AR
B&F
BI
BPS
BW
CCA
CEL
CO
CPM
CRM
CS
DB
DP
DS
E2E
EBP
EH&S
FI
FM
GATP
GL or
G/L
GW
HR
IBO
ICM
IDOC
IM
IS
Term
Advanced Business Application
Programming
Acquisition & Distribution
Asset Accounting
Definition
SAP’s proprietary programming language
Accounts Payable
Advance Planning and
Optimization or Advanced
Planner and Optimizer
Accounts Receivable
Budget & Finance
Business Intelligence
Business Planning and Simulation
Business (Information)
Warehouse
Cost Center Accounting
Cost and revenue elements
Controlling
Corporate Performance Monitor
Customer Relationship
Management
Customer Service
Database
Demand Planning
Detailed Scheduling
End to End
Enterprise Buyer something??
Environment, Health, and Safety
Financial Accounting
Funds Management
Global Available-To-Promise
General Ledger
Part of FI module
SAP standalone system used as a bolt-on
Gateway Server
Human Resources
Industrial Base Operations
Internet Communication Manager
Intermediate Document
Inventory Management
Industry Solutions
Part of Web AS
Module within IBO team
Team within R/3 (and XXP)
Part of Web AS
Used by SeeBeyond
Module within A&D team
Customized versions of SAP prepared by SAP AG for use by
customers, e.g. Public Sector IS & Aerospace and Defense IS (a
combination of which was used for XXP)
Part of mySAP
Module in SAP used by all modules and configured by the IBO
team at XXP
Part of PP module
KM
MM
Knowledge Management
Materials Management
MRP
Materials Requirements Planning
Team within R/3 (and XXP)
Part of FI module
Part of FI module
Team within R/3 (and XXP)
Part of mySAP; includes BW, SEM, and KM
Part of SEM module
SAP standalone system used as a bolt-on
Part of CO module
Part of CO module
Module within B&F team
Part of SEM module
Part of mySAP
Module within IBO team
Core database for mySAP
Part of APO module
Part of APO module
Test which uses full live interfaces
Part of mySAP
Module within A&D team
Module within B&F team
Part of FI module; creates master data
Part of IM/WM processes
Part of FI module
12
Acronym
MS
MySAP
OM
OM-CEL
PA
Term
Message Server
Organizational Management
Cost element accounting
Profitability Analysis
PC
PCA
PLM
PM
PP
PP
PS
QM
R&M
Product cost controlling
Profit Center Accounting
Product Lifecycle Management
Plant Maintenance
Production Planning
Project Planning
Project Systems
Quality Management
Analytical Reporting and
Performance Management
Real time three tiered
Real Estate
System, Application, Products
R/3
RE
SAP
SCM
SCP
SD
SEM
SL
SNP
TEM
TV or
AA
WM
Definition
Part of Web AS
Internet-based front end for SAP
Part of HR module
Part of CO module
A bolt-on module within B&F team;
both cost- or account-based
Part of CO module
Part of CO module – or is it FI?
A bolt-on module within IBO team
Module within IBO team
Part of APO module
Module within IBO team
Module within B&F team
Module within IBO team
Team within R/3 (and XXP)
Supply Chain Management
Supply Chain Planning
Sales & Distribution
Strategic Enterprise Management
??????
Supply Network Planning
Training & Event Management
Asset Accounting
Product name for SAP’s core functionality
Part of FI and CO modules
Company who makes R/3 and
related systems.
Part of mySAP
Team within R/3 (and XXP)
Module within A&D team
Bolt-on related to B&F team
Part of FI module
Part of APO module
Part of HR module
Part of FI module
Warehouse Management
Module within A&D team
13
Table 6. Other SAP or XXP Terms
Acronym
AAA
ABAP
ACID
AEPS
AKO
AMSCO
AS
BC
BOM
CATS
CC
CCSS
CIF
COCP
COOP
DAAS
Term
Army Audit Agency
Advanced Business Application
Programming
Atomic Consistent Isolated
Durable
Army Electronic Product Support
Army Knowledge Online
Army Management Structure Code
Application Server
Business Connector
Bill of Materials
Cross Application Time Sheet
Card Column
Commodity Command Standard
System
Core Interface
Customer order control point
Continuity of Operations center
DIC
DLA
DODAAC
DODAAF
Defense Automatic Addressing
System
Defense Automatic Addressing
System Center
Defense Finance and Accounting
Service
Document identifier code
Defense Logistics Agency
DOD Activity Address Code
DOD Activity Address File
DOF
ESS
Depot Overhaul Factor
Employee Self Service
FOP
GUI
I/F
ILSO
IQR
ITS
Found on Post
Graphic User Interface
Interface
Industrial Logistics Support Office
Internal Quality Review
Internet Transaction Server
KPI
LAISO
Key Performance Indicators
Lead AMC Integration Support
Office
Logistics Support Agency
Logistics System Support Office
DAASC
DFAS
LOGSA
LSSO
Definition
Validates how financial transactions are handled.
Programming language for SAP
Desirable characteristics of a transaction
An external system to XXP, based at Rock Island, IL.
The Army’s Portal
Relates FI planning, budgeting, staffing, and accounting
Web runtime environment for mySAP
Data exchange middleware in mySAP
List of what parts go into making something bigger
Column number for ASCII-based data records
Legacy system
Used to communicate between APO and R/3
A subsystem within CCSS
Backup production site, used for system testing of fixes and
new features
Defined by DoD 4000.25-10-M
Part of DLA.
Notice that this supports the whole DOD, not just the Army.
Tells what kind of document is being processed
Coordinates logistics support across the DOD.
Customer code assigned by the customer master
The customer master is a master data record which contains
the basic data for a customer with which an organization
conducts business
What % of incoming parts can’t be overhauled
SAP end user tool, e.g. the eStub system for accessing a
payroll system
Thing which didn’t show up via a sales order or PO
Informal test by Government personnel
Middleware between SAP and external systems (like
SeeBeyond)
Used by CPM
A subcommand under AMC
A subcommand under AMC
14
Acronym
Term
MDR
Master Data Record
MILSBILLS Military Standard Billing System
MILSTRAP Military Standard Transaction
Reporting and Accounting
Procedures
MILSTRIP
Military Standard Requisitioning
and Issue Procedures
NOC
Network Operations Center
O/P
P&L
PDC
PO
PRON
PT
RIC
SDD
Ownership purpose
Profit & Loss
Primary Data Center
Purchase Order
Purchase Request Order Number
Process Trials
SDS
SIT
SSF MS3
Standard Depot System
System Integration Test
Single Stock Fund Milestone 3
SSO
WIP
Single Sign-On
Work in Process
Services Description Document
Definition
Defined by DoD 4000.25-7-M
Defined by DoD 4000.25-2-M
Defined by DoD 4000.25-1-M
The main facility for developing fixes and new features for
XXP (MT)
Intended use of some stocked material
Type of statement generated by FI
The main production site for the system
Predefined system testing by end users
A vision document for XXP, describing the scope and
approach for providing logistics services.
Legacy system
Scenario test witnessed by customer
A major feature of XXP, not in the original scope of the
system.
Universal login
15