Overview of Account Based COPA

► list of proposed additional characteristics

► standard characteristics
► organizational data
► transaction based

► derive additional data

► referencing the source document
► Item category on the line item of billing document
► reference a field on applicable master data
► country from the customer address of the end user customer
► determine a completely new field
► continent from the country of the end user customer

OpenText Project Mercury | Page 1

New Characteristics to be added
► supplement the existing characteristics with:
► country assigned to company code
► end user customer - CR is approved
► end user country – CR is approved
► main account exec – CR is approved
► cost center
► vendor – will be blank unless manually populated
► heritage – CR is approved
► reseller, implementer, OEM, influencer - CR is approved
► customer group

OpenText Project Mercury | Page 2

Reporting Fields

► fixed fields that must exist in the table and are typically the
organizational structure that has been defined and cannot be
changed
► document the values and how they are populated

► optional characteristics
► additional fields and how they will be determined based on key process
flows

OpenText Project Mercury | Page 3

Standard Fields

► document type
► fixed field with values based on the source process
► invoice from the logistics module
► manual posting from financials
► CO process reposting
► settlement – close a project and repost the expenses into PA (AUC postings cannot
be reported in this module)
► assessment – a process where cost center costs can be allocated into PA

OpenText Project Mercury | Page 4

Standard Fields

► document date

► reference document number

► either the invoice number, accounting document number or the CO
document number based on the process used to post the document
► period
► fiscal period from FI
► year
► fiscal year from FI

OpenText Project Mercury | Page 5

Standard Fields

► controlling area
► only one value as defined in the organization
► systematically populated
► company code
► legal entity current understanding approx. 140
► systematically populated during billing and accounting postings
otherwise optional

OpenText Project Mercury | Page 6

Standard Fields

► sales organization
► 1:1 relationship to company code
► systematically populated during billing otherwise optional
► distribution channel
► required for invoice creation examples include:
► Direct
► Indirect
► systematically populated during billing otherwise optional
► division
► required for invoice creation
► systematically populated during billing otherwise optional

OpenText Project Mercury | Page 7

Standard Fields

► plant
► many:1 relationship to company code
► systematically populated during billing otherwise optional
► business area - not used
► cost element
► P&L accounts only
► systematically populated

OpenText Project Mercury | Page 8

Standard Fields

► work breakdown structure (WBS) – requires a settlement of the

WBS with real postings
► systematically populated during settlement
► If entered directly when posting a financial entry PA is real and PS is statistical
► cannot be derived from the customer invoice
► try to defer it’s use until phase 2
► billing type -types of invoices (regular invoice, CM, DM etc)
► every billing platform will have a separate billing type
► invoices from SAP will have fewer billing types
► systematically populated during billing

OpenText Project Mercury | Page 9

Standard Fields

► sold to customer
► systematically populated during billing
► financial posting with updates to COPA and an offset to the AR subledger
populated manually
► otherwise optional update
► material
► systematically populated during billing
► financial posting with updates to COPA and an offset to the MM
subledger populated manually
► otherwise optional update

OpenText Project Mercury | Page 10

Standard Fields

► profit center (PC)

► assigned on the material master sales/plant view
► all salable items will be required to have a value
► based on the revenue stream different rules will be accessed
► sales orders entered directly
► the value copied from the material master is sufficient
► sales orders created via SFDC
► Profit center assigned directly)

► mandatory assigned to the cost center copied to P&L posting

► proposal to write an additional rule that will block the financial posting if
the default value is going to be used (still to be decided)
► systematically populated

OpenText Project Mercury | Page 11

Standard Fields

► functional area
► used to develop the external financial statements
► assigned directly to certain accounts and derived from the cost center for
others
► dependent on the nature of the transaction

OpenText Project Mercury | Page 12

Proposed Characteristics

► product hierarchy
► define the three separate levels of:
► master product family
► product family
► master product
► product
► country booking the revenue – derived from the country on the
company code address
► systematically populated during billing otherwise optional

OpenText Project Mercury | Page 13

Proposed Characteristics

► customer end user – should be a partner on the billing document

(estimated 135000 end users)
► for the 40? large accounts from the billers a default end user customer
will be defined
► systematically populated during billing otherwise optional
► country of the end user
► based on the address of the end user determine the country code
► systematically populated during billing otherwise optional

OpenText Project Mercury | Page 14

Proposed Characteristics

► vendor - the calculation of 3rd party license accruals will be

done in OTBI
► the accrual will be posted manually in SAP charged to a material /
country level
► automated entry from winshuttle
► Manually entered value defaulted from OTBI
► cost centre
► many:1 relationship to profit centers and additional for internal
departments
► dependent on the nature of the posting (settlement vs assessment and the
sender cost centre or WBS)
► the business unit ID still needs to be stored (options to be reviewed in the
future)

OpenText Project Mercury | Page 15

Proposed Characteristics

► two values stored on the configuration class taxonomy in VC

► heritage
► business unit
► systematically populated on the sales order with the approval of the CR
they will populate COPA

OpenText Project Mercury | Page 16

Proposed Characteristics

► main account executive

► with the approval of the CR the main AE can be a characteristic in COPA

► additional partners to be passed into COPA include

► reseller, OEM, implementer and influencer

OpenText Project Mercury | Page 17

Parked Characteristics

► material group (dropped)

► material type (dropped)
► cost center hierarchy
► profit center hierarchy
► account assignment group – (dropped)
► account assignment group – (dropped)
► sales order type (dropped)
► billing number (dropped)
► industry code – SIC code – (dropped)
► business unit 5 – (dropped)
► product hierarchy – (dropped)

OpenText Project Mercury | Page 18