Oac Versus PCC Differences

Training Guide
Comparing OACs and PCCs

SabreSonic Res
Software Version 3.0
Document Edition 1.0 (07 2018)
This documentation is the confidential and proprietary intellectual

property of the Sabre Airline Solutions® business. Any unauthorized
use, reproduction, preparation of derivative works, performance or
display of this document or software represented by this document,
without the express written permission of Sabre Airline Solutions is
strictly prohibited.
Sabre® , the Sabre logo, Sabre Airline Solutions, the Sabre Airline
Solutions logo, Sabre Travel Network® , the Sabre Travel Network
logo, AirCentre® , AirVision® , SabreSonic® CSS, Sabre Data &
Analytics® are trademarks and/or service marks of an affiliate of
Sabre Corporation. All other trademarks, service marks and trade
names are the property of their respective owners.
© 2018 Sabre GLBL Inc. All rights reserved.

Table of Contents
1 Comparing OACs and PCCs

1.1 Stating the benefits of OAC 1
1.1.1 Setting Up OACs 1
1.2 Listing OAC Impacts 2
1.2.1 Comparing PCC and OAC Record Locators 2
1.2.2 Viewing Your Active Work Area 5
1.2.3 Associating an OAC with your Active Work Area 5
1.2.3.1 Working in your AAA with Another OAC 7
1.2.4 Assigning a Ticket Printer using an OAC 9
1.2.5 Pricing with OAC 11
1.2.6 Ticketing with OAC 12
1.2.7 Viewing the Station Numeric Table 16
1.2.7.1 Viewing a Multi-Airport City Code in the Station Numeric Table 18
1.2.8 OACs in the EPR 19
1.2.8.1 Viewing an EPR With an OAC Assigned 19
1.2.8.2 Viewing an EPR With Multiple OACs Assigned 20
1.2.9 Concerning General Sales Agents with OAC 21
1.2.10 Working with Queues using the OAC Selection Key 21
1.2.10.1 Counting Queue by OAC 21
1.2.10.2 Accessing Queue by OAC 21
1.2.10.3 Moving Queue by OAC 22
1.2.10.4 Selecting OAC to Print from Queue 22
1.2.10.5 Selecting OAC for Interact Queue Sorting 23
1.2.11 OAC within SabreSonic Inventory 24
1.2.12 OAC within Dynamic Schedules 25
A OAC Quick Reference Guide - Interact

A.1 Decoding a PNR Signature Line 1
A.2 Assigning a Ticket Printer 2
A.3 Viewing Authorized OACs in an EPR 3
A.4 Working in a Different AAA 4
A.4.1 Changing your OAC Using the Application Settings 4
A.4.2 Changing your OAC Using the Tools Menu 5
A.5 Working with Queues using the OAC Selection Key 7
A.5.1 Selecting OAC for Interact Queue Sorting 8
B OAC Quick Reference Guide for - Native Sabre

B.1 Decoding a PNR Signature Line 9
B.2 Assigning a Ticket Printer 9
B.3 Viewing Authorized OACs in an EPR 10
B.4 Working in a Different AAA 10
B.5 Working with Queues using the OAC Selection Key 11
B.5.1 Counting Queue by OAC 11
B.5.2 Accessing Queue by OAC 11
B.5.3 Moving Queue by OAC 11
B.5.4 Selecting OAC to Print from Queue 12
Table of Contents
Training Guide iii Confidential and Proprietary Sabre Airline Solutions
Table of Contents
Training Guide iv Confidential and Proprietary Sabre Airline Solutions
Document Revisions
Date Section Description

20 Jun 2018 Throughout Expansion of data and inclusion of SabreSonic® CSS Interact
screenshots (where applicable).
Table of Contents
Training Guide v Confidential and Proprietary Sabre Airline Solutions
Objectives
Item Objective
Objectives By the end of the module, participants will be able to:

l Describe and explain the additional Office Accounting Code components in a PNR signature line.
l Describe the additional components seen when viewing a work area setting.
l Explain the procedure and rationale for using different Office Accounting Codes in different work
areas.
l Describe assigning a ticket printer with an Office Accounting Code.
l Discuss the single base currency per Office Accounting Code and the impact on pricing, ticketing,
and exchanges.
l Describe the additional fields and responses to a Station Number table response.
l Explain the parameters associated with Office Accounting Codes assigned within an Employee
Profile Record (EPR).
l Display an awareness of the impact of Office Accounting Codes upon General Sales Agents (GSAs).
l Explain the purpose of using the Queue Selection Sort option for Office Accounting Codes.
l Demonstrate an awareness of Office Accounting Code options within SabreSonic® CSS Inventory
and Dynamic Schedules.
EPR Duty Code: No specific duty code is required.
Keyword: No specific EPR keyword is required.
Preparation Search for station numbers and applicable cities prior to class session.
Reference For more information, refer to the Focus manuals F*FMH and F*REM (access to REM requires a duty
code 8).
Table of Contents
Training Guide vi Confidential and Proprietary Sabre Airline Solutions
Comparing OACs and PCCs
1
The Sabre®system uses city codes / Pseudo City Code (PCCs) in many applications in support of a variety of
functions. Some of these functions include:
l Tracking / reporting purposes
l Fare security
l Passenger Name Record (PNR) security for General Sales Agents (GSAs)
l Queue placement
Previously, when there was a need to differentiate the work of a specific user group, a unique non-IATA
defined PCC was assigned to these users. However, the available non-IATA PCC’s were being exhausted,
therefore a different solution is required to accommodate the growing demand. The individual Office
Accounting Code (OAC) functionality has been created to address this need.
1.1 Stating the benefits of OAC
The Office Account Code (OAC) solution affords Sabre the opportunity to address the limitations caused by
using 3-letter alpha Pseudo City Codes (PCCs), and affords the capacity to meet current and future business
needs required to support carrier migration and expansion. The OAC solution affords the same level of
functionality as the former alpha PCC solution, with the capacity to handle large numbers of airline office
locations.
Note The Office Accounting Code solution does not replace the use of IATA-defined city codes; the
OAC solution simply addresses the needs and processes that previously required a unique non-IATA
Pseudo City Code (PCC).
The Office Account Code (OAC) solution allows greater granularity in identifying a user's current business
role when they create bookings or issue tickets, because the OAC permits differentiation of users whose EPRs
have the same IATA city code. For example, for two users / agents with the same home office, but who
perform different functions, you can assign each user a unique OAC code. Using differing OAC codes for
each of these users permits separate tracking of the specific functions that each user performs.
OAC provides great flexibility as it permits users to switch to different OACs to perform various functions,
and then to track these actions under the different OACs.
1.1.1 Setting Up OACs
Before defining your initial set up of OAC values, your airline should review the entire process of how your
users / agents / representatives operate.
Before changing the OAC values at the user session level, your airline must plan and implement training for
all your users / agents / representatives, so that they clearly understand the business process they should
follow.

Training Guide 1 Confidential and Proprietary Sabre Airline Solutions
1.2 Listing OAC Impacts
Office Accounting Codes (OACs) impact SabreSonic ® CSS Core Reservations (including Employee Profile
Records (EPRs), Passenger Name Records (PNRs), and queues), SabreSonic® CSS Ticketing, (including
SabreSonic® CSS Branded Fares and SabreSonic® CSS Ticketing AER), and supporting applications such as
SabreSonic ® CSS Dynamic Schedules and SabreSonic® CSS Inventory.
Impacted Program Example Impact
Employee Profile New OAC field in EPR.
Record (EPR)
Native entries HU* and *S* now show OAC data.
Passenger Name PNR security is tied to the city associated to the AAA, as well as the OAC associated to the
Record (PNR) active AAA.
You can sort PNR queues by an OAC selection qualifier.
Ticketing The Station Numeric (WJ) table is expanded to include OAC data.
Electronic tickets (also called Virtual Coupon Records - VCRs) include OAC data added to
the Signature Line and City Code.
Assigning a ticket printer may require OAC data (depending on your airline's settings).
Inventory Accepts OAC for use when determining responses to availability and sell requests.
Dynamic Schedules Accepts OAC for use when determining responses to availability hierarchy.
1.2.1 Comparing PCC and OAC Record Locators
In a Passenger Name Record (PNR) signature line, you can identify where a booking originated by the 3-letter
city code.
Previously, the booking could originate from an actual city code or from a pseudo city code (a PCC: a 3-letter
city code which was not an actual city, instead, it was a designated "city" in your partition, for use by General
Sales Agents or other entities). However, there are now insufficient 3-letter PCCs to meet the demand. The
Office Accounting Code (OAC) offers a solution to this issue by adding additional parameters. The OAC
identifies where the bookings come from throughout all applications. The system retrieves your office code
from your EPR and AAA settings.
In the following example of a PNR made before Office Accounting Code (OAC) was activated, this booking
was made in the Pseudo City Code OHL. As seen in Sabre Net Terminal Emulator (SNTE):
*P6
OHL.HDQ8KLL 1027/25JUN18 ELYTBU H
The signature line shows booking creation information.

Component Description
OHL AAA (Active Agent Area) 3-letter city / station code used when the PNR was created. This can be an
actual city / station code or a PCC code.

HDQ Creating agent's EPR home city.
8 Duty code used when the PNR was created.
KLL 3-character agent identifying sine (also called sign).
1027/25JUN18 Time and date of PNR creation.
ELYTBU System-assigned record locator.
H Indicator that history exists in the PNR.
When viewing the signature line via SabreSonic® CSS Interact using the Interactive PNR, the Received From
response in the Interactive PNR appears below the Contact / Address Info field. Before OAC is activated, this
field only tells you the home station and sine of the booking agent - it does not show where the booking
originated. For example:
To view the booking origination city / PCC code in Interact, you could use the Classic PNR view (which
closely resembles the SNTE view):

With Office Accounting Code active, the Received From field contains more data. In the following example,
the booking was made under the Office Accounting Code MEX-TR:
*P6
PBC-MEX-TR.HDQ5HD2 1319/25JAN18 SSWWKX H
When a PNR is created in an OAC environment, the signature line shows additional booking creation
information.
PBC AAA (Active Agent Area) 3-letter city / station code used when the PNR was created. This can be an
actual city / station code or a PCC code.
MEX-TR The OAC code: the 3-letter OAC city or airport code and the 2-letter OAC office code.
HD2 3-character agent identifying sine (also called sign).
1319/25JAN18 Time and date of PNR creation.
SSWWKX System-assigned record locator.
H Indicator that history exists in the PNR.
The Interact interface captures and returns more information. Within Interact, the OAC information appears in
the Interactive PNR response below the Contact / Address Info field. For example:
The OAC components in the PNR are as follows:

U0 The partition code.
8610210 The OAC station number.

Note Existing city codes (IATA and non-IATA) do not change with OAC; existing city codes continue to be
defined in the Cities Database.
1.2.2 Viewing Your Active Work Area
When you sign in, your active AAA (Agent Assembly Area) reflects your current work area city or pseudo
city code.
NativeSabre entry to view your work area:
*S
Example Native response prior to OAC being activated for your airline:
AUH.HDQ6UKL...B..PNR PRESENT..U0
Item Description
AUH The city associated to the AAA.
HDQ The user's EPR home city.
6 The duty code currently in use (if you do not have rights to a city / PCC, you are signed in with a trainee
"6" duty code).
UKL User's (agent's ) ID sine.
B Current work area identifier code (A-F).
PNR Example activity indicator.

PRESENT
U0 Partition indicator.
1.2.3 Associating an OAC with your Active Work Area
When you sign in, your active AAA (Agent Assembly Area) is mapped to your home city and default OAC.
Note You can associate to a different OAC in each work area session (work area A, B, C, etc.).
When your carrier has this option active, you can see the PCC when viewing your sine and status in your
current work area, similar to the following example.
Native Sabre entry to view your work area:
*S
Example Native response:
AUH.HDQ4UKL...B..PNR PRESENT..U0 U0 DXB TO 8888111
Item Description
AUH The city associated to the AAA.

Item Description
HDQ The user's EPR home city.
4 The duty code currently in use.
UKL User's (agent's ) ID sine.
B Current work area identifier code (A-F).
PNR PRESENT Example activity indicator.
U0 Partition indicator.
DXB TO 8990600 OAC associated to AAA.
Example Interact Change Work Area window and response:

1.2.3.1 Working in your AAA with Another OAC
When you sign in, you will automatically be signed in with your default OAC. However, if you have multiple
OACs in your EPR, you can manually change your OAC settings.
Note You can be associated to different OACs in each of your work areas.
Example Native Sabre formats:
Change into another work area: ¤B
Sign into another work area : SIC
Then, change to an applicable OAC. Example format:

AAAAUH/DXB/UO/8888111
Item Description
AAA Primary action code for Agent Assembly Area
AUH Home city code
/DXB Separator, city code
/UO Separator, account code
/8888111 Separator, station number
Example response:
AAA SET UP FOR AUH DXB UO 8888111
When using the Interact interface, use the Ctrl+W hotkey to access the Change Work Area window.

Select to Change Work Area, select a work area, and click OK.
Then, from the Application Settings (Alt+F3), select Change AAA and OAC options. Fill in the required data
in the OAC AAA Settings window.

Example response:
1.2.4 Assigning a Ticket Printer using an OAC
Prior to OAC, assigning a ticket printer required only the ticket routine code and the printer LNIATA. For
example:
W*2A589GK4
You can designate a printer to a specified OAC. Example Native Sabre entry:
W*2A589GK488881111
Item Description
W* Primary ticketing action code

Item Description
2A Ticket stock type
Note To assign the 2A ticket routine (as well as most other ticket routines), you must be signed in with a
duty code 4 or 5.
589GK4 Example printer line address
88881111 Example station number
Here is example response.
TICKET PRINTER
OK DXBTO OAC-U0 DXB TO 88881111
************************************************************
Using Interact , there are settings determined by your carrier which impact assigning a ticket printer. Your
carrier may have set the option for completely virtual ticket / EMD printing -- if this is the case with your
airline, when assigning a ticket printer, you only need to indicate the type of ticket routine.
If your airline has settings to permit printing a document or to issue a type of transaction that would issue a
paper accountable document (such as a excess baggage coupon, paper voucher, etc.), you need to include the
ticket printer address and the station number.
Example Interact entry:

Example response:
1.2.5 Pricing with OAC
Note The information in this secftion is primarily for the fare filing team at your airline. The most important
points to know are that Cat 15/35 supports OACs, and that select private fares may need updating for
your customer departments to be able to view the fares. Agency private fares are not impacted by
OACs.

A single OAC can only support a single base currency. All Sabre -hosted carriers that use OAC are set up so
that you must change the OAC (AAA) in order to price an itinerary with a different base fare. However, you
can apply a currency override to price a reservation with another currency type. The system converts the base
fare to the equivalent amount paid based on the Bankers Selling Rate (BSR).
For example, let's say you issue tickets with a base fare of EUR currency. The reservation also has a stored
Price Quote record with a currency override qualifier of AED and USD. Any subsequent tickets issued with
the base currency EUR will be converted and displayed as an equivalent amount paid value.
Additionally, let's say you want to issue tickets with no equivalent amount paid, but the ticket needs to be in a
different currency. For example, a call center is managing tickets sales / reissues for more than one country,
and an OAC change (AAA) is required to complete transaction because the guest is from another country. The
base currency will be the only value on the ticket.
Notes
l OAC also drives reporting, so the more OACs that exist in a Sabre -hosted partition, the more granular
OAC reporting is. Whether the parameters used to distinguish OACs are based on currency (POS),
station number, office code, or any other variance, these parameters allow your carrier to drive
reporting in a very specific manner.
l Sabre deploys IATA standards to determine the equivalent amount paid when a currency override is
applied. Sabre also uses both the Bankers Selling Rate (BSR) and ICER conversion methods for
currency overrides.
1.2.6 Ticketing with OAC
When issuing a ticket the base fare of that ticket must reflect the currency of the country where travel
originates. If a ticket is being purchased in a country other than the country of origin, an Equivalent Amount
Paid will appear on the ticket using the Bankers Sell Rate (BSR). if your airline manages ticket sales and
reissues for more than one country, such as from a call center, the ability to change OACs will alleviate the
issue of fluctuating currencies.
Example: LON - NYC - LON / Airline Call Center - Sao Paulo BR
Pricing Response:
The Base Fare appears in Great British Pounds, the currency where travel originates. Since the ticket is being
purchased in Brazil, a Bankers Sell Rate will calculate the Equivalent Amount Paid and Total.
To avoid multiple currencies, using an OAC will allow a more manageable fare line.

Changing your OAC - Original Issue
1. Select the Tools menu from Interact.
2. Click Change OAC City.

The Choose Country window appears.

3. Since travel originates in London, select Great Britain as the new OAC.
4. Click OK.
This action will re-assign the station code and printers in your new location. The interact screen when
redisplayed, will show your new sign location in the upper right side of the screen.
5. Price the itinerary again.

The response is a much simpler fare line without currency adjustments.
Changing OAC - Ticket Exchanges
When exchanging a ticketing using Automated Exchange and Refunds (AER), fluctuating currencies can be an
issue with base fares and international taxes.
Example: GRU - FCO - GRU / Call Center: Rome IT
The passenger has flown the outbound and has changed the return flight.
1. Display the electronic ticket (VCR)
The base tax and total are all shown in Brazilian Reals (BRL). The call center agent in Rome processes the
exchange. Pricing will include Euro's if an add collect or change fee occurs. This would require an
Equivalent Amount and BSR on the Comparison Summary Screen 30. Since the Bankers Sell Rates changes
weekly, this could involve a currency fluctuation with the base tax or total amounts.
2. Go to Tools, and select Change OAC City.
3. Change the OAC to Brazil.
4. Once completed, process the exchange through AER.
The Comparison Summary Screen 30 appears.

Because we changed the OAC to match the country of origin, we kept the currency the same, resulting in a
simple even exchange with change fee. If the OAC is not changed, the new BSR can result in a fare /tax
difference (plus or minus) when only a change fee applies. This would create additional work to either collect
or refund amounts that were not caused by fare changes, but currency fluctuations instead.
1.2.7 Viewing the Station Numeric Table
The Station Numeric table is a list of all cities within a partition. You can view the ticketing abilities of each
station. A number is assigned to each station in the system, you use the station number when you assign a
ticket printer. This station number identifies the station and the ticketing action taken on a daily basis.
Note You can read more about the Station Numeric Table in the Ticketing and Agent Sales Report Database
Training Guide.
Native Sabre entry to view the full Station Numeric Table:
WJ*
Item Description
WJ Primary action code for Station Numeric Table
* Indicator for Display

Before OAC is activated, the Station Numeric table appears in this format, reflecting various setting options.
For example:
STATION CITY TKT BILL NTKT CPT ATAC ASR NAME/CHANNEL

111 11 11 1 VCEHQ YES NO YES NO NO NO ATO
222 22 22 2 VCEAP YES NO YES NO NO NO ATO
333 33 33 3 NAPTR YES NO YES NO NO NO ATO
444 44 44 4 CTATR YES NO YES NO NO NO ATO
555 55 55 5 PMOTR YES NO YES NO NO NO ATO
666 66 66 6 CAGTR YES NO YES NO NO NO ATO
777 77 77 0 HDQTR YES NO YES NO NO NO ATO
888 88 88 1 FCOTR YES NO YES NO NO NO ATO
TOTALS 8 8 0 8 0 0 0
Here is a partial example response for the Station Numeric table when OAC is active:
STATION OFFICE ACCOUNT CODE CHANNEL/OAC NAME

000 00 01 1 U0 JED TO 0000001 ATO
000 00 02 2 U0 FRA TR 0000002 ATO
000 00 03 3 U0 CRC TO 0000003 ATO
000 00 04 4 U0 FCO TO 0000004 ATO
000 00 04 4 U0 FCO TS 0000005 CTO
000 00 05 5 U0 LHR TO 0000006 ATO
000 00 06 6 U0 SGN KK 0000007 RES
Column Example Description

STATION 000 00 01 Station number
1
OFFICE ACCOUNT CODE The Office Account Code consists of the following components:
U0 Carrier code (this will be your airline code, unless you are in a multi-carrier
partition)
JED 3-letter city code
TO 2-character office code
Note The city code and the office code together are the city code location (often
the location's Teletype address).
0000001 Office Accounting Code number
CHANNEL / ATO Ticketing channel designator (indicating the type of ticketing location). Options
OAC NANE include:
l ATO - Airport Ticket Office
l CTO - City Ticket Office
l TBM - Tickets By Mail (also known as Reservations Ticketing)
l GSA - General Sales Agent
l WEB - Web
l IVR - Interactive Voice Recognition
l RES - Reservations Office / Call Center

1.2.7.1 Viewing a Multi-Airport City Code in the Station Numeric Table
You can view the Station Numeric table settings for a specified city code. For example, you might make this
entry for a multi-airport city:
WJ*LON
Item Description
WJ Primary action code for Station Numeric Table
* Indicator for Display
LON City code
The response is a list of the stations available in the specified city code. The followin is an example response
to this entry before OAC is activated:
MULTI-AIRPORT CITY LON

STATION CITY TKT BILL NTKT CPT ATAC ASR NAME/CHANNEL
888 81 13 3 LONTO YES NO YES NO NO YES ATO
TOTALS 1 1 0 1 0 0 0
After OAC is activated, the response to this entry combines data:
MULTI-AIRPORT CITY LON

STATION OFFICE ACCOUNT CODE CHANNEL/OAC NAME
000 00 05 5 U0 LHR TO 0000005 ATO
012 64 21 1 U0 LHR KT 0126421 ATO
888 81 13 3 U0 LON TO 8888113 ATO
-------------------------------------------------------------
STATION CITY TKT BILL NTKT CPT ATAC ASR DEFAULT VXCR
000 00 05 5 LHRTO YES NO YES NO NO YES U0
012 64 21 1 LHRKT YES NO YES NO YES YES U0
888 81 13 3 LONTO YES NO YES NO NO YES U0
TOTALS 3 3 0 3 0 1 3 0 3
The top portion of the response is the same as viewed from the full table entry.
The lower portion of the response contain the station settings for the OACs in the indicated city, the settings
are shown in columns :

STATION 000 00 05 Individual station numeric code.
5
City LHRTO City code location
TKT YES Automated ticketing indicator
BILL NO Accelerated Credit Card Billing (ACCB) setting

NTKT YES Neutral Ticket Stock (allows the Sabre system to assign and print ticket numbers at the time
of issuance).
CPT NO Commission Protected Ticketing (Sabre no longer supports this functionality).
ATAC NO Automated Ticket Agent Check-out function (the precursor to Agent Sales Report)
ASR YES Agent Sales Report function
DEFAULT The default AAA city for this station
VXCR U0 Validating carrier. This setting only has meaning in a multi-carrier partition setting,
otherwise, the validating carrier is always your own carrier code.
1.2.8 OACs in the EPR
Employee Profile Records (EPRs) offer the options for Sign In Access - Limited Access and for additional
access cities. (For more information on these fields, refer to the Employee Profile Record Training Guide.)
Both limited access and additional city access are current options for EPRs.
The Office Accounting Code (OAC) is a new field in the EPR. After OAC is activated for your partition,
every Employee Profile Record (EPR) must have at least one default OAC assigned. You can have multiple
OACs (up to 11 OACs) if the EPR is set up for Limited Sign-in Access (H/LMTY) functionality and has
authorized access to the city referenced in the OAC (H/CTY).
Note For information on adding OACs to EPRs, refer to the Employee Profile Records Training Guide.
1.2.8.1 Viewing an EPR With an OAC Assigned
You can view the OACs associated with your EPR. In the Native Sabre example shown below, the EPR has
one OAC listed.
H*123456U0
T TESTER HDQ-TET 123456U0

GRP-0 OFC-0000 ASO-240
SIGN IN ACCESS - HDQ
DUTY 4 5 7 8 ‡ /
OAC HDQ TC 7777771 DEFAULT DTC-U0
UAT- PTRAGT QUEUES
AUTH-1SM SMITH
STATUS - INACTIVE TEMP PASSCODE
DATE PASSCODE LAST ASSIGNED - 21FEB18
U NEW RECORD
21FEB18 1105A CST
An OAC field in an EPR contains the following components

Example Component Description
OAC Identifier for the Office Accounting Code information section in the
EPR.
HDQ Personal accounting city code.
TC Pesonal account code.
7777771 Office / station code.
DEFAULT This indicates that is the default OAC in this EPR.
DTC-U0 Default Ticketing Carrier (DTC) indicator and the default ticketing
carrier code.
l For details on the other fields in an EPR, refer to the Employee Profile Records Training Guide (for
EPR administrators) or the Viewing Employee Profile Records Training Guide. You can always view
the details of your own EPR. You may be restricted to viewing only the first two lines of other EPRs,
so you would not be able to view their assigned OACs.
l For information on how to access and view an EPR via Interact, refer to the Encode / Decode Training
Guide for SabreSonic® CSS Interact.
1.2.8.2 Viewing an EPR With Multiple OACs Assigned
In this example, the employee’s home station is MAN. The employee has limited sign-in access to the city
LHR, so you can assign an OAC for LHR stations. Notice that the EPR also contains another station in LHR
(LHR U0 0126421).
A default OAC can be a city other than the home AAA. When this employee signs in, the system
automatically maps them to their home station (MAN):
H*654321U0
Q TESTER MAN-MVP* 654321U0

SIGN IN ACCESS - LIMITED TRAVEL
ALSO- DUB HUY LHR
DUTY 4 5 7 8 ‡ /
OAC MAN TO 7878871 DEFAULT DTC-U0
OAC LHR KT 0126421 DTC-U0
OAC LHR CT 0126421 DTC-U0
OAC HUY TO 8990009 DTC-U0
UAT- DIENBR PTRAGT QUEUES
STATUS - ACTIVE 21FEB17 PASSCODE
H U CREATED BY HDQ-MBM 20FEB17 1106A
20MAR18 0221P CST
Component Example Description

SIGN IN LIMITED Indicator that the user of this EPR is able to access cities other than their EPR home
ACCESS - TRAVEL city. (This is existing functionality.)

ALSO - DUB HUY The user of this EPR is able to AAA to cities DUB, HUY, and LHR. (This is existing
LHR functionality.)
OAC This user has a default OAC and three additional OACs listed which they can use.
1.2.9 Concerning General Sales Agents with OAC
With the General Sales Agent (GSA) function, travel agencies can access an airline’s partition. A GSA OAC
Table assigns GSA locations and associates to an OAC.
OAC information entered along with GSA city will include only Accounting city and Accounting code. The
same IATA city code can have multiple GSAs associated to it. (The GSA Table in OAC and non-OAC
environments are different and have no relation.)
GSA agents can access queue items if the OAC in the PNR matches the OAC in the agent’s AAA. The OAC
and the city in the AAA must match the city and OAC key in the queue entry. GSAs will only see their PNRs.
The OC selection key will automatically filter GSA queue items.
Note EPRs for GSAs can only have one OAC.
For more information on EPRs for General Sales Agents, refer to the GSA EPRs Training Guide.
1.2.10 Working with Queues using the OAC Selection Key
The queue OAC selection key (OC) is only applicable for PNR queues, and you can use it with the following
queue functions: Queue Count, Queue Access, Queue Move, and Queue Print. The OC selection key will
filter your search results, so only queues with the specified OAC data will appear.
Note For more information on queues, refer to the Queues Training Guides.
1.2.10.1 Counting Queue by OAC
With the OC selection key, you can perform a Queue Count and see the amount of PNRs with OAC data.
Omitting the queue number will show the results for all queues.
Example Native Sabre entry:
QC/100‡OC-BUE-SCL-AG
Item Description
QC Primary action code for Queue Count.
/100 Example queue number.
‡OC- Cross of Lorraine separator and OAC selection key.
BUE-SCL-AG OAC to sort from queue (data from the signature line of the PNRs).
1.2.10.2 Accessing Queue by OAC
You can access a queue and display PNRs with a specified OAC. Example Native Sabreentry:
Q/SGN100‡OC-HDQ-SGN-AG

Item Description
Q Primary action code for Queue access.
/SGN Example city code.
100 Example queue number.
HDQ-SGN-AG OAC to sort from queue (data from the signature line of the PNRs).
1.2.10.3 Moving Queue by OAC
You can perform a Queue Move with the OC selection key. All PNRs with the specified OAC data will be
moved to the new queue.
Example Native Sabre entry:
QMOV/200/440‡OC-DEL-CCU-TR
Item Description
QMOV Primary action code for Queue Move.
/200 Queue to move from.
/440 Queue to move to.
DEL-CCU-AG OAC to sort from queue for move (data from the signature line of the PNRs).
1.2.10.4 Selecting OAC to Print from Queue
You can print PNRs from queue, selecting by a specified OAC.

Example Native Sabre entries:
QL/300*SQ‡OC-FRA-DUS-TR
Item Description
QL Primary action code for Queue List print.
* Indicator for Display.
SQ PNR action code (Space / Service requested reply only if not available).
FRA-DUS-TR OAC to sort from queue (data from the signature line of the PNRs).
QL/JNB440*SQ‡AL-U0/OC-CPT-DUR-AG

Item Description
/JNB440 Example other city queue number.
‡AL- Cross of Lorraine separator and Airline Code selection key.
U0 Airline code to sort from queue (data from the itinerary field of the PNR).
CPT-DUR-AG OAC to sort from queue (data from the signature line of the PNRs).
1.2.10.5 Selecting OAC for Interact Queue Sorting
The following progression shows Display Queue Count as an example; the Queue Sort Selections process is
similar for other applicable Queue Access options.

1.2.11 OAC within SabreSonic Inventory
OAC is an option for defining a group to be used within a rule, very much like how you would use a PCC for
defining a group.

1.2.12 OAC within Dynamic Schedules
Office Accounting Code is an option for defining a Point of Sale to be used within a rule, very much like how
you would previously use a Pseudo City Code for defining a Point of Sale.

OAC Quick Reference Guide - Interact
A
A.1 Decoding a PNR Signature Line
When viewing the signature line via SabreSonic® CSS Interact using the Interactive PNR, the Received From
response in the Interactive PNR appears below the Contact / Address Info field.
25JAN18 at 1319 Date and time of PNR creation.
MEX TR The OAC code: the 3-letter OAC city or airport code and the 2-letter OAC office code.
How a PNR signature line appears in the OAC setting, when viewed via the classic PNR option:
OAC - U0 MEX TR 8610210

Example Description
OAC Indicator for the OAC portion of the field.

Example Description
PBC AAA (Active Agent Area) 3-letter city / station code used when the PNR was created.
SSWWKX PNR record locator.
H Indicator that history exists on the PNR.
A.2 Assigning a Ticket Printer
Note There are settings determined by your carrier which impact assigning a ticket printer. Your carrier
may have set the option for completely virtual ticket / EMD printing -- if this is the case with your
airline, when assigning a ticket printer, you only need to indicate the type of ticket routine.
If your airline has settings to permit printing a document or to issue a type of transaction that would issue a
paper accountable document (such as a excess baggage coupon, paper voucher, etc.), you need to include the
ticket printer address and the station number.
Example Interact entry:

Example response:
A.3 Viewing Authorized OACs in an EPR
H*654321U0

ALSO- DUB HUY LHR
DUTY 4 5 7 8 ‡ /
20MAR18 0221P CST

LHR functionality.)
MAN Personal accounting city code.
TO Pesonal account code.
DEFAULT This indicates that OAC is the default OAC in this EPR.
DTC-U0 Default Ticketing Carrier (DTC) indicator and the default ticketing carrier code.
A.4 Working in a Different AAA
When you sign in, you will automatically be signed in with your default OAC. If you have multiple OACs in
your EPR, you can manually change your OAC settings.
A.4.1 Changing your OAC Using the Application Settings
From the Application Settings window (Alt+F3), select Change AAA and OAC options. Fill in the required
data in the OAC AAA Settings window.

Example response:
A.4.2 Changing your OAC Using the Tools Menu
Note This is an optional setting. If you do not see this menu option, then this option does not apply to your
iteration of Interact.

1. Select the Tools menu:
2. Click Change OAC City.

The Choose Country window appears.

3. Select the applicable description, AAA city, and currency as the new OAC.
4. Click OK.
This action will re-assign the station code and printers in your new OAC. The interact screen when
redisplayed, will show your new OAC location in the upper right side of the screen.
A.5 Working with Queues using the OAC Selection Key
You can use OAC selection with the following PNR queue functions: Queue Count, Queue Access, Queue
Move, and Queue Print. Sorting by OAC queue details will filter your search results, so only queues with the
specified OAC data will appear.

A.5.1 Selecting OAC for Interact Queue Sorting
The following progression shows Display Queue Count as an example; the Queue Sort Selections process is
similar for other applicable Queue Access options.

OAC Quick Reference Guide for - Native
Sabre
B
B.1 Decoding a PNR Signature Line
How a PNR signature line appears in the OAC setting:
OAC - U0 MEX TR 8610210

Example Description
OAC Indicator for the OAC portion of the field.
PBC AAA (Active Agent Area) 3-letter city / station code used when the PNR was created.
SSWWKX PNR record locator.
H Indicator that history exists on the PNR.
B.2 Assigning a Ticket Printer
Format for assigning a ticket printer in the OAC setting:

W*2A589GK488881111
Item Description
W* Primary ticketing action code.
2A Ticket stock type code.
Note To assign 2A type stock (as well as most other ticket stock), you must be signed in with a duty
code 4 or 5.

Item Description
589GK4 Example printer line address.
88881111 Example station number.
B.3 Viewing Authorized OACs in an EPR
H*654321U0

ALSO- DUB HUY LHR
DUTY 4 5 7 8 ‡ /
20MAR18 0221P CST

LHR functionality.)
MAN Personal accounting city code.
TO Pesonal account code.
DEFAULT This indicates that OAC is the default OAC in this EPR.
DTC-U0 Default Ticketing Carrier (DTC) indicator and the default ticketing carrier code.
B.4 Working in a Different AAA
Format for changing to another AAA and assigning a specific OAC:

AAAAUH/DXB/UO/8888111
Item Description
AAA Primary action code for Agent Assembly Area
AUH Home city code

Item Description
/DXB Separator, city code
/UO Separator, account code
/8888111 Separator, station number
B.5 Working with Queues using the OAC Selection Key
You can use the queue OAC selection key (OC) with the following PNR queue functions: Queue Count,
Queue Access, Queue Move, and Queue Print. The OC selection key will filter your search results, so only
queues with the specified OAC data will appear.
B.5.1 Counting Queue by OAC
QC/100‡OC-BUE-SCL-AG
Item Description
QC Primary action code for Queue Count.
BUE-SCL-AG OAC to sort from queue (data from the signature line of the PNRs).
B.5.2 Accessing Queue by OAC
Q/SGN100‡OC-HDQ-SGN-AG
Item Description
Q Primary action code for Queue access.
/SGN Example city code.
100 Example queue number.
HDQ-SGN-AG OAC to sort from queue (data from the signature line of the PNRs).
B.5.3 Moving Queue by OAC
QMOV/200/440‡OC-DEL-CCU-TR
Item Description
QMOV Primary action code for Queue Move.
/200 Queue to move from.
/440 Queue to move to.

Item Description
DEL-CCU-AG OAC to sort from queue for move (data from the signature line of the PNRs).
B.5.4 Selecting OAC to Print from Queue
QL/300*SQ‡OC-FRA-DUS-TR
Item Description
FRA-DUS-TR OAC to sort from queue (data from the signature line of the PNRs).
QL/JNB440*SQ‡AL-U0/OC-CPT-DUR-AG
Item Description
/JNB440 Example other city queue number.
‡AL- Cross of Lorraine separator and Airline Code selection key.
U0 Airline code to sort from queue (data from the itinerary field of the PNR).
CPT-DUR-AG OAC to sort from queue (data from the signature line of the PNRs).


Oac Versus PCC Differences

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oac Versus PCC Differences

Uploaded by

Copyright:

Available Formats

Training Guide

Comparing OACs and PCCs

Document Edition 1.0 (07 2018)

This documentation is the confidential and proprietary intellectual

© 2018 Sabre GLBL Inc. All rights reserved.

1 Comparing OACs and PCCs

A OAC Quick Reference Guide - Interact

B OAC Quick Reference Guide for - Native Sabre

Date Section Description

Objectives By the end of the module, participants will be able to:

Keyword: No specific EPR keyword is required.

1.1 Stating the benefits of OAC

1.1.1 Setting Up OACs

1 Comparing OACs and PCCs

You can sort PNR queues by an OAC selection qualifier.

1.2.1 Comparing PCC and OAC Record Locators

OHL.HDQ8KLL 1027/25JUN18 ELYTBU H

The signature line shows booking creation information.

1 Comparing OACs and PCCs

8 Duty code used when the PNR was created.

KLL 3-character agent identifying sine (also called sign).

1027/25JUN18 Time and date of PNR creation.

ELYTBU System-assigned record locator.

H Indicator that history exists in the PNR.

1 Comparing OACs and PCCs

PBC-MEX-TR.HDQ5HD2 1319/25JAN18 SSWWKX H

HDQ Creating agent's EPR home city.

5 Duty code used when the PNR was created.

HD2 3-character agent identifying sine (also called sign).

1319/25JAN18 Time and date of PNR creation.

SSWWKX System-assigned record locator.

H Indicator that history exists in the PNR.

The OAC components in the PNR are as follows:

8610210 The OAC station number.

1 Comparing OACs and PCCs

1.2.2 Viewing Your Active Work Area

HDQ The user's EPR home city.

UKL User's (agent's ) ID sine.

B Current work area identifier code (A-F).

PNR Example activity indicator.

1.2.3 Associating an OAC with your Active Work Area

Example Native response:

AUH.HDQ4UKL...B..PNR PRESENT..U0 U0 DXB TO 8888111

1 Comparing OACs and PCCs

4 The duty code currently in use.

UKL User's (agent's ) ID sine.

B Current work area identifier code (A-F).

PNR PRESENT Example activity indicator.

DXB TO 8990600 OAC associated to AAA.

Example Interact Change Work Area window and response:

1 Comparing OACs and PCCs

Then, change to an applicable OAC. Example format:

AUH Home city code

/DXB Separator, city code

/UO Separator, account code

/8888111 Separator, station number

AAA SET UP FOR AUH DXB UO 8888111

1 Comparing OACs and PCCs

1 Comparing OACs and PCCs

1.2.4 Assigning a Ticket Printer using an OAC

1 Comparing OACs and PCCs

88881111 Example station number

Here is example response.