Attributes (OSCAR) List

Other systems like RW, PeopleSoft, PM, PM Partner, SLU, Selfservice, etc. extract/filter
information based on the OSCAR attributes configured for the products. Here is the list of
different attributes being used for the products :

(PS : This needs to be updated as and when the new attributes are created. The list contains the
OSCAR attributes present till date).

RW Attributes

1, ALWAYS_SHOW

This attribute is used if a particular is supposed to be shown all the time even when it is
incompatible with other selected products. In RW when you select the products and some
products are incompatible then those products are not shown. But if at all it is needed to show
them even the products incompatible to it are selected, then this attribute is used. The attribute is
used by RW.

2, UI_GROUP

This attribute is used for all the products which are supposed to be shown in RW. It is a very
important attribute to be configured for the products because if they are not configured then the
products will not be visible in the RW screens.

3, UI_PRIORITY

This attribute is used by RW to set the Priority between the products in RW screens.

4, USE_FULL_PRICE

This attribute is used by RW to determine whether the device's upfront cost is its full price for the
selected combination. This attribute is added on 0 mån binding period (both SE and DK).

PM Attributes

1, SLU_ACTIVATION_ID

This attribute is used for the products which are activated through the system SLU. For SLU
products this attribute should be added. The value of the attribute is the billing id of the product.

2, NOTICE_PERIOD

This attribute is used for the PM products so that the products should not be disconnected
immediately rather should be disconnected after the notice period. The value of the attribute is
the number days in number. That will determine of after how many days the product will get
disconnected.

3, PRICE

This attribute is mainly used by the PM, PM Partner, TLA products. This contains the price of the
product to be shown. For the PM and PM Partner products the attribute value will always be
including VAT value. The attribute is used by PM system.
4, PRICE_PERIOD

This attribute determines the period for the which the price of the product is applicable. It can be
configured in two values: Month or Day. Month means the price is applicable on monthly basis
and Day means the price is applicable on daily basis.

5, PM_AUTO_ADD

This attribute adds the product automatically to its parent product when the parent product is
selected through PM. The products to which this attribute is configured is generally the discount
products and their parent product being the Addon product. In order to work this attribute, there
should exist a Only If and Recommended If rule with the corresponding addon product.

6, PM_SHOW

This attribute is added to all the PM products. This attribute helps to show the product in PM. If
the attribute is not there then the product will not be visible at all. So for all the PM products it is
obligatory to have this attribute unless there is any special requirement to not to have it.

7, TLA

This attribute is an attribute for all the Time Limited Access i.e TLA products.

8, INCLUDED_IN

This attribute is used to let the PM system know about the parent-child relationship between the
products. Say, if there are two products A and B with B having a higher cost than A and it is
allowed to upgrade from A to B, then this attribute is configured for the product A. The value for
the attribute will be the product id of B. This is used mainly to tell the PM that the product can be
upgraded directly from A to B without any Notice Period.

SESAM3 Attributes

1, CHANGE_TARIFF

This attribute is added in the 'Source' price plan from which Change Tariff should happen. The
value will be the possible 'Target' price plans id separated by ' | ' symbol.

2, SELLABLE

This attribute is added in the 'Target' price plan to determine whether the price plan can be
changed to from Mitt3.

Hardware Attributes

1, ACCESSORY

This attribute is added by the Accessory Sync procedure for all the products which are classified
as Accessories in ERP system. This is used only by the Accessory Sync.

2, DATACARD

This attribute is added by the Accessory Sync procedure for all the products which are classified
as Datacard’s in ERP system. This is used only by the Accessory Sync.
3, DYNAMIC_CATEGORY

This attribute is in cases where certain items such as DEVICE are needed to be set as Dynamic
Items. Generally when any Device is needed to be set up as Dynamic items, we cannot set them
directly. Instead we need to create a dummy product and add the attributes to that dummy
product (Details about this are present in Offline Sales document under ‘Device as Dynamic
Items’). This attribute is one of the attributes added to that Dummy product. This attribute is used
by RetailWeb to populate the itemcategory and itemsubcategory tags in the ItemPriceList and
Stock response.

4, DYNAMIC_PRODUCT_ID

This attribute will contain the product id of the device that needs to be set as a Dynamic item.

5, FREIGHT

This attribute is added by the Accessory Sync procedure for all the products which are classified
as Freight’s in ERP system. This is used only by the Accessory Sync.

6, IMEI

This is a very important attribute configured for all the devices. It contains the IMEI series values
for the Device products. The attribute should NEVER be added manually to the devices. This
attribute is added automatically by the ERP sync job to all the Device products.

7, MAXIMUM_ACCESSORY

This attribute is referred by RW to restrict the selection of the accessories on the RW hardware
page (Pris) to one when there are more than one accessories are available as dynamic items with
lesser costs for the same combination. The attribute value must be same for the accessories that
share the same combination.

8, NOT_RETURNABLE

This attribute is used for mainly the Dynamic items. It is added on those products which are not
returnable once they are sold. The information about the items which are returnable or not
returnable will be provided by the stakeholders in the requirement. Alternatively, the same
information can also be obtained from ERP Database too.

9, NOT_VISIBLE

This attribute is used mainly for the Marketing Materials which are mandatory and sold as
Dynamic items. It is added on those products which should be added automatically, just like
included in the subscription and no user intervention is needed. When a product is set with this
attribute then it must be a Mandatory Dyanmic Item for the combination.

10, SELL_OUT_OF_STOCK

This attribute is added for the Dynamic items that are to be sold even if the stocks become zero.

11, SERIALIZED

This attribute is added on those products(Accessories) which require the input as serial numbers.
Mainly this attribute is added on the Dynamic items and for those products which need Serial
Number as input (similar to the IMEI’s of devices)
12, ORDER_EMAIL_SE

This attribute is mainly used by RW to determine if the e-mail field should be mandatory or not. If
this attribute field is set on any Device then it becomes mandatory for the user to input the
customer’s e-mail id in RetailWeb.

Prepaid Voucher/Top Up Attributes

1, Amount

This attribute contains the amount/price of the product. Mainly used by the PM products or by
Prepaid voucher products. Used by the systems like PM, PM Partner, Self Service.

Note: Price value must be Inclusive of VAT for both Consumer and Business.

2, GL_AccountCode, GL_CustomerType, GL_ProductService, GL_SpecCode, VAT,

VoucherType, Assettype

These attributes are mainly used for the Prepaid Voucher products. These attributes are used by
Billing, RW, etc. The value of the attribute depends on what SIU has been told to configure.

Retention Downgrade Attributes

1, DOWNGRADE_TYPE

This attribute is used for all the tariff plans which are considered for Retention Downgrades. The
attribute will have two values: POTT or NORMAL. Depending on what type of tariff plan it is, the
attribute value has to be configured accordingly. If the tariff plan is applicable for Retention
Downgrade then it is imperative to configure this attribute. This attribute is used by PSFT to know
if the downgrade type is POTT Downgrade or NORMAL downgrade.

2, DOWNGRADE_PRODUCT

This attribute is configured to provide the RET_NORMAL product of the tariff plan when it moves
to any NORMAL tariff plan. The value to this attribute will be the product id of the RET_NORMAL
product of that particular tariff plan. The attribute is used by PSFT to know which product they will
have to add to the customer’s portfolio during Retention Downgrade.

3, TARIFF_PLAN_VALUE_EX_VAT

This attribute is used by the tariff plans which are considered for the Retention Downgrades. The
value of the attribute is the excluding VAT value of the tariff plan. This attribute is used by both
RW and PSFT. RW uses this for Danish tariff plans, in order to show only those tariff plans during
Retention which have a higher attribute value than the installed one when the retention is being
done before the end of the binding end date. PSFT uses it to find the difference between the
source tariff plan and the target tariff plan.

4, POTT_VALUE_EX_VAT

This attribute is used by all the products with the product category RET_POTT. It is imperative
that the RET_POTT products have this attribute. The value for this attribute is the excluding VAT
value of the POTT value. The attribute is used PSFT to get the difference product and add it to
the customer’s portfolio during POTT downgrades.
Minimum Price/Customer Confirm Attributes

1, TIME_PERIOD_MONTHS

This attribute determines the duration of the product. It is mainly used by Minimum Price
Webservice and by the Monthly Installment dummy products. For Minimum Price Webservice it is
used by adding the attribute on the Binding Period products. And for monthly installment products
it is used to generate the duration of the product in the contracts.

2, MINIMUM_PRICE_CATEGORY

This attribute is used for the Minimum Price Webservice. This attribute is used to classify the
products into various categories such as:

ADDON, BINDING_PERIOD, CMP_SUBSCR_DISC, HW_MONTHLY_PAYMENT,

UNLIM_SUBSCR_DISC, PROLONGATION_DISCOUNT, PROLONGATION,
STARTUP_DISCOUNT, STARTUP, RC, MC, INSTALLMENT_AMOUNT. Minimum Price
Webservice will use these attributes to classify the products during its calculation.

3, CUSTOMER_CONFIRM_HIDDEN

This attribute is referred by Customer Confirm Webservice to determine which product should be
hidden on the Customer Confirm page. This attribute currently applies to Denmark products.

External Financing Attributes

1, EXT_FINANCING

This attribute is added only to the Delfinansiering products. The value for this attribute would be
the name of the Partner Bank.

2, EXT_FINANCING_INFO

This attribute is used only on the Delfinansiering products. The value of the attribute is the contact
number of the customer service of the Partner bank. The value is used by RetailWeb in order to
display it in the message that is triggered when the credit check for the customer fails.

3, EXT_FINANCING_AMOUNT

This attribute is added on the ‘Avdrag partnerfinansiering’ products. The value is the entire
amount of the discount given to the customer for the entire binding period.

Monthly Installment Attributes

1, MAPPING

This attribute is used for the Monthly installment dummy products. It is used to provide the
product id’s of the real products that get installed on the Installment Subscription.

2, EPOS_INST

This is the attribute added on the dummy products that are created for EPOS-Monthly Installment
solution. For more details please read the Offline Sales document.

3, INITIAL_COST_OPTION
This is the attribute added on Initial Cost products (logical products) that help in calculating
Monthly Installment value dynamically based on the upfront cost of the device in combination with
a tariff plan.

Final Bill Attributes

1, BINDING_REFERENCE, NOTICE_REFERENCE

This attribute is used for 'Final Bill Settlement'. The attribute is added to the product to identify
and calculate final bill duration for settlement before Retire.

SIM Card Attributes

1, CASE_DETAIL, CASE_SUBTYPE

The attributes are used for storing the CASE_TYPE and CASE_SUB_TYPE for the SIM to
support the 'Order New SIM' call process from Self Service (3IS) for SE.

2, DOCUMENT_ID

The attribute is used for storing the DOC_ID for the SIM to support the 'Order New SIM' call
process from Self Service (3IS) for DK.

3, CONTRACT_SIM

The attribute is used for storing the logical value to determine which 'Change SIM Card Letter'
should be add to the Customer Contract. This attribute is fetched by RW for Retention ISL flow
when there is a change in the SIM.

Other Attributes

1, FAX_LIMIT, HUNT_LIMIT, MAIN_LIMIT

These are attributes used by the Mega Switch tariff plans (the tariff plans used to create a mega
switch). These attributes determine the maximum number of Fax subscriptions, Hunt
subscriptions, Main subscription that can be created in RW. The attribute value is the maximum
number allowed. The attribute is mainly used by RW.

2, FCA

This attribute is used only by the first call activation products. It is to determine that it is the First
Call Activation product.

3, NR_VISIBILITY

This attribute is used for all the number visibility products.

4, DIR_SERVICE

This attribute is used for all the directory visibility products.

5, COMMON_FIXED_NUMBER

This attribute is used in Fixed Number Familj product.

6, CONTRACT_CATEGORY
This attribute is used to classify products to be printed in the appropriate blocks of Sweden
Subscription Contracts.