Professional Documents
Culture Documents
C.Bianco, B.Niang
April, 2008
Summary
3. Mapping of BP vs BW AP fields
Appendix
2 | Presentation Title | Month 2007
Multicube ZXFIAPM01
Multicube ZFIGLAPM1
Analysis can be done for all account payable amounts at vendor level.
Example of what is
loaded in the AP
cube from an
invoice posted in
BP.
Inside this info cube there are data coming from AP and GL info-cubes:
all AP reconciliation accounts data (BSEG-KOART = K);
data coming from B/S and PL accounts (BSEG-KOART = S and M) (ex. VAT
accounts coming from GL).
Analysis can be done for all account payable amounts both at vendor & GL
account level.
Example of what is
loaded in the APGL cube from an
invoice posted in
BP.
Note: information related to the split of Balance sheet readjustment are not available (no link with table BFOK_A).
6 | Presentation Title | Month 2007
The SAP tables interfaced with AP and AP-GL info-cubes are the following:
BSEG = Actual line items of document (GL+AP)
BKPF = Accounting Document Header (GL+AP)
BSIS = Open items GL
Note: not all the data available in each SAP table are transferred from BP to BW.
Multiple sources & availability of data are explained in next pages.
In order to have
Vendor item &
customer item
available , the
0FI_GL_4 extraction
have to be done (SAP
Architecture
dependency).
BW AP and AP-GL solutions are covering the Account Payables process deployed
in Blue Planet.
Cube Vendor
Line Item BP
ZXFIAPC04
NA - Cube Vendor
Line Item BP
ZNFIAPC04
Cube Vendor
Line Items: BA/PC
Adjustment
ZXFIAPC05
NA - Cube Vendor
Line Items: BA/PC
Adjustment
ZNFIAPC05
BP
Vendors: Linte Items
(Extraction Linked to
0FI_GL_4)
0FI_AP_4
11 | Presentation Title | Month 2006
2007
y FI_AP Item
y Organizational
y Time.
Characteristic
Used to analyze the key figure data (they are regrouped in dimensions):
y FI_AP Item: doc number, item status (O/C), clearing doc, payment block
y Vendor dimension: name, country, reconc. account,
12 | Presentation Title | Month 2007
Dimension example:
VENDOR
Dimension example:
VENDOR
Dimension example:
VENDOR
Cash Amounts:
y Discount base (amount eligible for cash discount) in
DOCUMENT Currency
y Cash discount amount in:
DOCUMENT Currency
LOCAL Currency
17 | Presentation Title | Month 2007
y Debit amount in
DOCUMENT Currency
LOCAL Currency
y Credit amount in
DOCUMENT Currency
LOCAL Currency
Note: Third local currency (ZX_DMBE3) is NOT used today in BP
In the case below the Amount FAS doubtful is limited to the range of GL accounts that concerned
the doubtful and the restriction FAS rate is based to the FAS rate Conversion that take form
Conversion table the rate FAS.
y FI_AP Item
y Organizational
y Time.
Characteristic
Used to analyze the key figure data (they are regrouped in dimensions):
y FI_AP Item: doc number, item status (O/C), clearing doc, payment block
y Vendor dimension: name, country, reconc. account,
22 | Presentation Title | Month 2007
Dimension example:
Line item
Dimension example:
Line item
Tax Amount:
y Base amount (taxable amount):
DOCUMENT Currency
LOCAL Currency
y Tax amount in
DOCUMENT Currency
LOCAL Currency
Cash Amounts:
y Discount base (amount eligible for cash
discount) in DOCUMENT Currency
y Debit amount in
DOCUMENT Currency
LOCAL Currency
2nd LOCAL Currency
y Credit amount in
DOCUMENT Currency
LOCAL Currency
2nd LOCAL Currency
BW AP & AP-GL
All Dimensions & Key figures
Here attached the excel file with all the Dimensions & Key Figures available in:
MultiCube
AP_ZXFIAPM01
MultiCube
AP-GL_ZFIGLAPM1
In each file, list of local queries created by countries are available like example
of possible reports on AP & AP-GL solutions.
1/3
Super users (also called Key users or Power users) can create local queries to
cover specific local requirements of AP department using the Multi-Cubes of AP
3
and AP-GL:
1
2/3
5
IMPORTANT STATEMENT/ADVISE: it is
recommended to not create a new query directly
from Multi-Cube (as the new query will be empty)
but to create a copy of one of existing query on AP
Multi-Cube.
Pay attention to the restrictions or conditions
defined! If content of query not very clear, create
from new.
30 | Presentation Title | Month 2007
3/3
5
IMPORTANT STATEMENT/ADVISE: it is
recommended to not create a new query directly
from Multi-Cube (as the new query will be empty)
but to create a copy of one of existing query on AP
Multi-Cube.
Pay attention to the restrictions or conditions
defined! If content of query not very clear, create
from new.
31 | Presentation Title | Month 2007
Item is overdue
Item is not due
Item is due
Free Characteristics
report
available for
drill-down
Report Layout
to display amounts
preview
in the report
With:
With:
ZFIRSTDY First day of the month: from first day of the month to key due date
ZXFISCPER Due Fiscal Year/period -12: variable Offset goes from 1 to 12 for Due period
previous to entered Key due date
37 | Presentation Title | Month 2007
ZFIRSTDY First day of the month: from first day of the month to key due date
ZXFISCPER Due Fiscal Year/period: deriving from Net due date
drill-down
displayed in the
report
Characteristics
Report Layout
displayed in the
preview
report
Condition defined in
the report
Free Characteristics
displayed in the
available for
report
drill-down
Characteristics
Report Layout
displayed in the
preview
report
Mapping of BP vs BW AP fields
IMPORTANT:
- file to be updated by BI A&S team
with new fields activated for NAR
FINANCE PROJECT
Appendix
BW Main concepts
BW structures
BW (Business Warehouse) is a data extractor.
Within Alcatel-Lucent there are two different data sources: Blue Planet or
Orion.
There are 2 structures of information :
Local
Central team
Cubes
Cubes (Infoproviders) :
aggregate information of ODS into facts
+ dimensions (according to a star
scheme)
BW
R/3
BW Query design
Naming Convention for new Local queries
First part:
Second part:
Third part:
Counter:
Fourth part:
Q###
US_ZXFIAPM01_Q002__Due_amounts_follow-up
Note: NAR BW Leads can create protected local queries with technical codification starting with U1_
50 | Presentation Title | Month 2007
Separate
each part
with an _
BW Authorization Variables
Authorization variables
Due to the new authorization philosophy in BW Version 7.0, when an
authorization relevant object is inserted in an infoprovider, it is automatically
activated for all solutions based on this infoprovider.
The authorization checks activated for one solution (ex. For InfoObject
Company code)
will become homogeneous FOR ALL INFOPROVIDERS and for ALL QUERIES
(cubes/multicubes/ODS) based on the same solution.
51 | Presentation Title | Month 2007
BW Authorization Variables
Authorization variables in new Local queries
BW Authorization Variables
1st Option - Local query like a copy of the Template of Query
- 1/2
1st OPTION : Create a local query like a copy of the Template of Query
BW Authorization Variables
1st Option - Local query like a copy of the Template of Query
- 2/2
BW AP solution
Authorization objects activated in
AP infoprovider
Note: only Company code is Visible in Selection screen. If you want to make the other
authorization visibles, you can change them in your local query.
BW Authorization Variables
2nd Option - Local query like copy of Central Report
2nd OPTION: Create a new local query like a copy of existing Central
=> With this option, all authorization variables are already included in the
Central reports.
Note: all the filters, conditions, restricted key figures, etc. will be copied as well from Central reports.
Pay attention to them!
BW Authorization Variables
3rd Option - Creation from InfoProvider - 1/3
3st OPTION: Create a new local query directly from the infoprovider and
AUTHORIZATION OBJECTS:
AP solution
BW Authorization Variables
3rd Option - Creation from InfoProvider - 2/3
The list of authorization objects activated for each BW financial solution and the
list of authorization variables that can be used are listed in this excel file:
Author
variables_v4
BW Authorization Variables
3rd Option - Creation from InfoProvider - 3/3
If authorization variables are not inserted in the local queries, the following error
message will be displayed: NO AUTHORIZATION
BW AP & AP-GL
ERs and Functional specification
For more detailed information on technical BW AP & AP-GL solutions, the
Functional and Technical specification documents are available in the
following Enhancement Request (Ers) database in Lotus Notes:
BW AP:
ER#2109 Hub Roll-out BW reporting : Solution Account payable
ER#2435 WAVE2 : BW HUB--FR-- AP new fields link to ER 2109
ER#3572 NAR Fin - BI031 - Verification of current EDW coverage in BW
BW AP-GL solution
ER#2110 Hub Roll-out BW reporting : Solution Account payable & GL conterpart
ER#2423 WAVE2 BW HUB - FR -INTE- : Central Report VAT Open items for cleared Vendor Line
and Central report Journal des pices comptables (link to ER 2110) FR-GAP282
ER#3572 NAR Fin - BI031 - Verification of current EDW coverage in BW
with target currency corresponding to the company code currency (Local currency).
www.alcatel-lucent.com