Oracle Business Intelligence Applications for SAP Release Notes for Oracle Data Integrator Users, Version 7.9.7.2

E18922-03

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Contents

Oracle® Business Intelligence Applications for SAP. 1

Audience. 5

Documentation Accessibility. 5

Accessibility of Code Examples in Documentation. 6

Accessibility of Links to External Web Sites in Documentation. 6

TTY Access to Oracle Support Services. 6

Audience

This document is intended for BI managers and implementers of Oracle Business Intelligence Applications for SAP Version 7.9.7.2

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

Release Notes

These release notes describe known issues and workarounds for Oracle Business Intelligence Applications for SAP, and contain the following sections:

· Section 1.1, "How to Use These Release Notes"

· Section 1.2, "General Issues and Workarounds"

· Section 1.3, "Oracle Business Intelligence Applications: General"

1.1 How to Use These Release Notes

These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest version of the release notes, check the Oracle Business Intelligence Applications Documentation Web site:

http://www.oracle.com/technetwork/middleware/bi-applications/documentation/index.html

1.2 General Issues and Workarounds

This section describes general issues and workarounds for Oracle Business Intelligence Applications products. It contains the following topics:

· Section 1.2.1, “Certification Information”

· Section 1.2.2, "Installation "

1.2.1 Certification Information

For certification information, refer to Certification Matrix (Formerly System Requirements and Supported Platforms) for Oracle Business Intelligence Applications for SAP 7.9.7.2 document. It is available from the following location:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

1.2.2 Installation

This section provides release notes on installing Oracle Business Intelligence Applications for SAP. It contains the following topics:

· Installer cannot be launched in Non-English Platforms

Installer cannot be launched in Non-English Platforms

The BIApps7.9.7.2 installer cannot be launched in non-English platforms.

Workaround

Run the following command to launch BIApps7.9.7.2 installer.

%JAVA_HOME%\bin\java.exe -cp <PATH_TO_7.9.7.2_BI_APPS_INSTALLER>\setup.jar

-Dtemp.dir="%TEMP%" -Dis.jvm.home="%JAVA_HOME%" -Dis.jvm.temp="1"

-Dis.external.home="<PATH_TO_7.9.7.2_BI_APPS_INSTALLER>" -Xms64m -Xmx128m run

1.3 Oracle Business Intelligence Applications for SAP: General

This section provides release notes for Oracle Business Intelligence Applications for SAP version 7.9.7.2. It contains the following topics:

1.3.1, "Incorrect Name for SA System Presentation Column Prevents Delivery of iBots to Applications Users"

1.3.2, "Lack of Time Zone Setting Prevents Delivery of iBots to Applications Users"

1.3.3, "Issue with Exchange Rates and Transaction Currencies"

1.3.4, "Incorrect Username Displayed in the Greetings Message in Oracle Business Intelligence Interactive Dashboards"

1.3.5, "Installation Errors with Oracle Applications Server Advanced Security Option"

1.3.6, "In the Execution Plans Administration Page, Focus Does Not Shift to the Newly Copied Execution Plan Record"

1.3.7, "Column Heading Not Aligned When Editing Parameters"

1.3.8, "Sort Order Does Not Work Correctly on the Application Specific Tab of the Parameters Administration Page"

1.3.9, "Not All Execution Plans Visible in Execution Plans Dropdown on Execute Package Structure Dialog on Monitor Executions Page"

1.3.10, "Oracle BI Applications Configuration Manager Connects to First Connection in Connection Dropdown on First Login"

1.3.11, GL Budget is not supported

1.3.12, “PLP maps which populate GL balance using GL other facts as source has issues”

1.3.13, “Read only user for SAP and Warehouse”

1.3.14, “Additional csv files packaged with the installer”

1.3.15, “Restartability issue in SDE_SAP_SECURITY package”

1.3.16, “Duplicates not allowed for Custom UOM conversion”

1.3.17, “UOM Conversion values rounded off”

1.3.18, “Issue in Identification of PO required spend”

1.3.19, “Missing details in Supplier Performance – Supplier AP transaction SA”

1.3.20, “Consigned-Consumed metric is not supported for SAP”

1.3.21,” Exchange rate considerations for Purchase Order Leakage in SAP”

1.3.22, “Configuration of Other AP and AR accounts in SAP”

1.3.23, “Association of SAP roles to OBIA roles”

1.3.24, “Suppress RPD warnings”

1.3.25, “GL_ACCT DUPLICATES DUE TO MULTIPLE COA - COMPANY CODE ASSIGNMENT”

1.3.26, “Default value for GL_ACCOUNT_CAT_CODE in W_GL_ACCOUNT dimension”

1.3

1.3.1 Incorrect Name for SA System Presentation Column Prevents Delivery of iBots to Applications Users

The Oracle Business Intelligence Delivers iBots use a predefined query against the SA System subject area to retrieve a list of applications users who are associated with the iBot's Recipient Group. When an iBot is run, this predefined query will fail with an error message that is similar to the following one:

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 27005] Unresolved column: "Time Zone".

The query error prevents the Oracle BI Delivers iBot from generating and delivering any content for the applications users that are associated with the iBot's Recipient Group. This impacts all iBot destination types including Interactive Dashboards and Emails and Disconnected Application cache generation for Oracle Business Intelligence Disconnected Analytics. The issue occurs because the 'Time Zone' presentation column name is incorrectly spelled as 'Timezone' in the SA System subject area.

To work around this issue use the Oracle Business Intelligence Administration Tool to change the name of the existing 'Timezone' presentation column in the SA System presentation catalog to 'Time Zone'.

For information on the SA System subject area, see the Oracle Business Intelligence Server Administration Guide.

1.3.2 Lack of Time Zone Setting Prevents Delivery of iBots to Applications Users

The Oracle BI Delivers iBots use a predefined query against the SA System subject area to retrieve a list of applications users who are associated with the iBot's Recipient Group. When an iBot is run, users who do not have a time zone specified in user preferences are considered invalid users and iBots are not delivered to them.

This issue occurs because the join type for the S_TIMEZONE join in the S_USER Logical Table Source in the SA System Business Model is defined as INNER when it should be defined as RIGHT OUTER.

To work around this issue, perform these steps:

1. Display the Oracle Business Intelligence Administration Tool.

2. In the Business Model and Mapping layer, expand the SA System Business Model and the USER Logical Table.

3. Double-click the S_USER Logical Table Source under Sources in the USER Logical Table.

4. In the Logical Table Source - S_USER Dialog Box, change the type to RIGHT OUTER from INNER for the S_TIMEZONE join in the Joins section of the General tab.

For information on the SA System subject area, see the Oracle Business Intelligence Server Administration Guide.

1.3.3 Issue with Exchange Rates and Transaction Currencies

Current design and support of multiple currencies within the Oracle BI Applications and the data warehouse assumes that the transactional system (or OLTP system) provides exchange rates and table structures that store exchange rates.

If the OLTP system does not provide exchange rates from the 'transaction currency' to the chosen 'one or more data warehouse currencies', then the Fact table will have a null exchange rate value for 'transaction' currency to 'Global1' currency, and hence, analysis based on Global currencies will not be possible for these transactions. It also impacts the correctness of the data for data that resides in various aggregate tables. This issue is also seen in the other two supported currencies (Global2 and Global3).

To work around this issue, ensure that the OLTP system has all currency exchange rates from all possible transaction currencies added to all the three chosen data warehouse currencies, up front. If this is not taken care of beforehand and you encounter a missing exchange rate issue, then you can rerun transactions in 'full' mode after you have fixed the missing exchange rate issue in the OLTP system.

1.3.4 Incorrect Username Displayed in the Greetings Message in Oracle Business Intelligence Interactive Dashboards

The user name that appears in the Greetings message in the Oracle Business Intelligence Interactive Dashboards does not display correctly. The variable DISPLAY_ NAME used in the Greetings message in the dashboard header gets populated through an Initialization Block called LOGIN Properties. Out of the box, the connection pool and SQL statements used in this init block point to the Siebel OLTP. You need to change the Connection pool and data source SQL for the Initialization Block: LOGIN Properties for SAP as a source, as described below. For SAP source, we will display only the user login as the username in Greetings Message.

The solution to this issue is:

1. Open the EnterpriseBusinessAnalytics.rpd file using Oracle BI Administration Tool.

2. Navigate to Manage > Variables to open the Variables Manager.

3. Under Session > Initialization Block, select the 'LOGIN Properties' initialization block.

4. Double-click to open the properties dialog box.

5. Click on the Edit Data Source button.

6. Click on the Browse button.

7. In the Select Connection Pool window, select Oracle Data Warehouse Connection Pool.

8. In the Default Initialization String box on the 'Session Variable Initialization Block Data Source - LOGIN Properties' window, enter the SQL as appropriate for your source system application and the database platform it is running on.

Table 1–1 Required SQL Strings For Each Source System Application And Database Combination

Source System Application (and Database Platform)	SQL required for Default Initialization String
SAP (Oracle RDBMS)	Select USER_NAME from W_SAP_SEC_USR_TMP WHERE W_SAP_SEC_USR_TMP.USER_NAME= ‘:USER’

1.3.5 Installation Errors with Oracle Applications Server Advanced Security Option

When installing the Oracle Business Intelligence Applications on top of an installation of the Oracle Business Intelligence Enterprise Edition that was installed using the Oracle Applications Server advanced security option, the following error message will be displayed:

"Password length is less than the required minimum, 8"

Oracle Business Intelligence Applications installation will abort and the

EnterpriseBusinessAnalytics.rpd file will be corrupted.

The error happens because the MINIMUM_PASSWORD_LENGTH setting in the NQSConfig.ini file was set to 8 by the OBIEE installation. The workaround is to change the value of MINIMUM_PASSWORD_LENGTH to 0 in NQSConfig.ini, install Oracle Business Intelligence Applications, then change the value back to 8.

1.3.6 In the Execution Plans Administration Page, Focus May Not Shift to the Newly Copied Execution Plan Record

In Oracle BI Applications Configuration Manager > Administer Execution Plans, create a new Execution Plan record by copying an existing Execution Plan. The focus may not shift to the newly copied Execution Plan record.

1.3.7 Column Heading Not Aligned When Editing Parameters

In Oracle BI Applications Configuration Manager > Administer ELT Parameters, the column headings may not be aligned to the columns displayed in the Parameters table when a user double-clicks on a Parameter record to edit the value. This mis-alignment does not prevent editing of the Parameter value.

1.3.8 Sort Order Does Not Work Correctly on the Application Specific Tab of the Parameters Administration Page

The Sort Order functionality in Oracle BI Applications Configuration Manager> Parameters Administration > Application Specific tab does not work correctly. Clicking on the sort icons in the column headings does not sort the rows in either ascending or descending order.

1.3.9 Not All Execution Plans Visible in Execution Plans Dropdown on Execute Package Structure Dialog on Monitor Executions Page

In Oracle BI Applications Configuration Manager > Monitor Executions page, click on the Create New Session icon. The Execute Package Structure dialog displays a dropdown box with the list of Execution Plans to select from. The Execution Plans dropdown displays a maximum of 25 Execution Plans. If there are more than 25 Execution Plans defined in the Administer Execution Plans page, the additional execution plans do not display in the dropdown.

To workaround this limitation, start the executions from the Administer Execution Plans page

> Package Structure tab by selecting the desired Execution Plan record in the Execution Plans top pane and clicking on the Execute icon in the Package Structure tab of the bottom pane.

1.3.10 Oracle BI Applications Configuration Manager Connects to First Connection in Connection Dropdown on First Login

In Oracle BI Applications Configuration Manager, create multiple connections to different environments in the Manage Connections page. Log out of Oracle BI Applications Configuration Manager, and log in.

In the login page, specify user, password and select any connection except the first from the Connection dropdown. Oracle BI Applications Configuration Manager attempts to connect to the first connection in the list.

Users may receive invalid logon errors as Oracle BI Applications Configuration Manager attempts to authenticate the supplied username and password against the first environment.

If the credentials can be authenticated, Oracle BI Application Configuration Manager will connect to the first environment, instead of the environment selected in the dropdown.

This behavior happens only for the first login after multiple connections have been defined.

In order to workaround the issue, close the browser if an invalid logon error is received, or log out of Oracle BI Application Configuration Manager if the connection was made to the first environment. Open a new browser window, launch Oracle BI Applications Configuration Manager and select the desired connection from the dropdown.

1.3.11 GL Budget is not supported

GL Budget fact in finance is not supported in this release.

1.3.12 PLP maps which populate GL balance using GL other facts as source has issues.

There are two ways of populating GL Balance Fact

1. Using the balance information from SAP

2. Compute the GL balance using the GL information that is populated in W_GL_OTHER_F

The 1st option is the preferred way of populating the GL balance, and the product is configured to use the first option out of box.

The 2nd way of populating the GL balance is given as an alternate option. In this process, there are series of PLP maps which run to populate GL balance fact using W_GL_OTHER_F as the source. Some of the PLP maps which has joins to Calendar table fails.

1.3.13 Read only user for SAP and Warehouse.

From the security point of view, it is suggested that a read only user privilege is used for extracting data from SAP.

For reporting purpose, when connecting from the reports and dashboard to the Oracle BI Applications warehouse database, it is advisable to use a read only warehouse database user. This is just to ensure that the data cannot be manipulated using this database user.

1.3.14 Additional csv files packaged with the installer

Following are some csv files packaged with the installer. These files are not required for the SAP adaptor and can be ignored:

CSV Files in lkpfiles folder

domainValues_Employee_Ethnic_Group_Code_ora11i.csv

domainValues_Employee_Sex_MF_ora11i.csv

domainValues_Employee_Veteran_Status_Code_ora11i.csv

domainValues_Employment_Cat_ora11i.csv

domainValues_Employment_Exempt_Flg_ora11i.csv

domainValues_Employment_Full_Time_Flg_ora11i.csv

domainValues_Employment_Status_ora11i.csv

domainValues_EventTypes_ora11i.csv

domainValues_HRPosition_Active_Pos_Flg_ora11i.csv

domainValues_HRPosition_Exempt_Flg_ora11i.csv

domainValues_InvoiceStatus_ora11i.csv

domainValues_InvoiceTypes_ora11i.csv

domainValues_InvSrcTypes_ora11i.csv

domainValues_Job_Eeo_Cat_Code_ora11i.csv

domainValues_Job_Flsa_Stat_Code_ora11i.csv

domainValues_Movement_Types_ora11i.csv

domainValues_OrderOverallStatus_ora11i.csv

domainValues_OrderTypes_ora11i.csv

domainValues_Pay_Type_Flg_ora11i.csv

domainValues_Pay_Type_Grp_Code_ora11i.csv

domainValues_PayMethodCode_ora11i.csv

domainValues_Perf_Ranking_Ind_ora11i.csv

domainValues_PickStatus_ora11i.csv

domainValues_PickTypes_ora11i.csv

domainValues_ShipmentType_ora12.csv

domainValues_Status_Purch_Approve_ora11i.csv

domainValues_Status_Purch_Cycle_ora11i.csv

domainValues_Xact_Types_DocTypes_ora11i.csv

domainValues_Xact_Types_PO_Line_Type_CODE1_ora11i.csv

domainValues_Xact_Types_PO_Line_Type_ora11i.csv

domainValues_Xact_Types_Purch_Orders_ora11i.csv

domainValues_Xact_Types_Purch_Requisitions_ora11i.csv

file_comp_pension_taxable_flg_ora11i.csv

CSV Files in srcfiles folder

ACCT_STATUS.CSV

file_accnt_rnk_ds.csv

file_acct_doc_status.csv

file_ap_trxtypes_ora.csv

file_ar_trxsubtypes_ora.csv

file_ar_trxtypes_ora.csv

file_cogs_trxtypes_ora11i.csv

file_Consigned_Type.csv

file_event_type_ora11i.csv

file_fin_stmt_item_names_ora11i.csv

file_fin_sub_codes_ora11i.csv

file_fin_sub_names_ora11i.csv

file_gl_hierarchy_assignment_ora11i.csv

file_glacct_segment_config_ora.csv

file_group_acct_codes_ora.csv

file_group_acct_names.csv

file_others_trxtypes_ora.csv

file_rev_trxtypes_ora.csv

file_status_order_line_block.csv

file_status_schedule_line.csv

file_tax_trxtypes_ora.csv

1.3.15 Re-startability issue in SDE_SAP_SECURITY package

If the Security package fails in the middle of execution of the package, it will not be possible to restart the package execution from the failed task.

Workaround:

Restart the package from the beginning.

1.3.16 Duplicates not allowed for Custom Unit of Measure (UOM) conversion

In SAP Standard conversions for UOM and Custom defined UOM and its conversion are maintained in same table (T006, T006D). When loading data from multiple clients the data loaded from the last ETL Run (client) will be available in the BI Applications warehouse. In Multi Client environment of SAP, Standard UOM Conversions will fail if there is custom defined UOM code across clients have same name but conversion rate is different.

1.3.17 UOM Conversion values rounded off

UOM Conversion values rounded off

Workaround

The Field T006. DECAN holds the value for round off. In W_UOM_CONVERSION_GS the value of T006. DECAN is used for rounding off the values in calculation. If the value is not maintained in SAP for T006. DECAN

i.e. = 0 or is more than 6 which the warehouse does not support, The round off will be defaulted to 6, otherwise the value will be the value of is T006. DECAN.

1.3.18 Issue in Identification of PO required spend

Payables Leakage is that portion of the Spend where Invoices are created against Suppliers with no PO, but should have been matched to PO. The PO Required Flag is decided based on the Invoice Match Option in Supplier Master. This is not supported for SAP. All Spend is classified as PO Required Spend (for PO Matched Spend) and PO Not Required Spend.

1.3.19 Missing details in Supplier Performance – Supplier AP transaction Subject Area

All Purchase Info such as Purchasing Organization, Purchase Order Number, Purchase Order Item are not mapped and not populated in Supplier Performance - Supplier AP Transactions SA. This is due to the difference in the grain of the fact tables, W_AP_XACT_F and W_AP_INV_DIST_F

1.3.20 Consigned-Consumed metric is not supported for SAP

In SAP consignment orders are places directly to the Vendor and goods are received against the order. SAP supports CONSIGNED and Not CONSIGNED-CONSUMED. Metrics on CONSIGNED-CONSUMED will not be supported.

1.3.21 Exchange rate considerations for Purchase Order Leakage in SAP

In SAP the exchange rate can be fixed in the purchase order. Fixed exchange rate is not considered in the current release for calculation of Leakage price.

1.3.22 Configuration of Other AP and AR accounts in SAP

In SAP there is no specific indicator to identify other payables and other receivables. Based on account group you can identify whether it is income, expense or asset account, each account group will contain a number range. Based on number you will identify if a particular GL belongs to an Asset, Liability, Income or Expense account, since account groups and number ranges are user specific.

Field status group (G019) is used to identify other payables and receivables, it controls the screen layout during posting (required, optional or suppress). During GL master creation you should select the correct field status group (G019), only then you can extract records for other payables and receivables.

If a user creates GL account (other payable or receivable) with field status group which is not suggested by SAP (other than G019) then those records can’t be captured into AP and AR.

SAP has provided some standard field status groups.

Ex: cost accounts (G004), Material accounts (G006), other payables& receivables (G019), reconciliation account (G067).

1.3.23 Association of SAP roles to Oracle BI Applications roles

SAP roles for ECC6 and 4.6C are not mapped to corresponding Oracle BI Application roles in this release. This association helps in deciding the access to different objects within Oracle BI Applications dashboards for the logged in user.

Workaround

Add the SAP roles, association between SAP roles and Oracle BI Application roles using OBIEE em.

1.3.24 Suppress RPD warnings

Oracle BI EE 11g is more stringent in reporting metadata repository errors
and warnings than in Oracle BI EE 10g. Oracle BI EE might report errors and warnings that were not reported previously.

OBIEE provides a warning suppression patch 11810367 on 11.1.1.5.0 version to
selectively suppress the warnings reported by OBIEE Admin Tool. This patch
11810367 is released in controlled mode and available on support.oracle.com
for download. Metalink note 1365964.1 contains more information on
downloading and applying this patch.

When Applied, following warning are suppressed by default through this Patch,
a. 39009 , 39054, 39055, 39057, 39059

Using this patch, following warning can be suppressed if it’s related to
Out-of-the-Box content. If the same warnings are appearing on the customized
content then we suggest reviewing and fixing the same.
a. 39062, 39008, 39028, 39008

You can add more warnings to the exclusion list in the Consistency Check
Warnings dialog by following the instructions in the Metalink note 1365964.1

1.3.25 GL_ACCT duplicates due to multiple COA - Company Code Assignment

As per the SAP standard, one Chart of Account can be assigned to multiple company codes, but one company code should be assigned to only one chart of account. If any company code has more than one chart of accounts it will be functionally incorrect. The data should be treated it as bad data.

If SDE_SAP_GLACCOUNTDIMENSION_EXTRACT or SDE_SAP46C_GLACCOUNTDIMENSION_EXTRACT package gets failed in incremental load due to unique constraint violation issue then the duplicate records have to be deleted from the I$ table and the failed package has to be restarted from the operator. Once the package gets completed, the End to End execution can be triggered again from the config. manager.

1.3.26 Default value for GL_ACCOUNT_CAT_CODE in W_GL_ACCOUNT dimension

The columns GL_ACCOUNT_CAT_CODE and GL_ACCOUNT_CAT_NAME in GL Account Dimension is assigned a default value of NULL, it should be assigned a default value of 'Profit & Loss Account'.

Workaround

Please make the following modifications, before the full load to ensure that

GL_ACCOUNT_CAT_CODE and GL_ACCOUNT_CAT_NAME are set with correct default value.

1. Open interface

SDE_SAP_GLAccountDimension_Extract_Full.W_GL_ACCOUNT_PS_Full.

2. Go to diagram and select the mapping of GL_ACCOUNT_CAT_CODE.

3. In the expression editor replace the existing expression with below expression:

DECODE_4(W_GROUP_ACCT_FIN_STMT_D_TMP.GL_ACCT_CAT_CODE,NULL,'PL',

W_GROUP_ACCT_FIN_STMT_D_TMP.GL_ACCT_CAT_CODE)

4. select the mapping of GL_ACCOUNT_CAT_NAME and in the expression editor replace the existing expression with below expression:

DECODE_4(W_GROUP_ACCT_FIN_STMT_D_TMP.GL_ACCT_CAT_CODE,

'BS','Balance Sheet Account', 'Profit & Loss Account')

5. Click on apply.

6. Make the above changes to below interfaces also:

· SDE_SAP_GLAccountDimension_Extract.W_GL_ACCOUNT_PS

· SDE_SAP46C_GLAccountDimension_Extract_Full.W_SAP_GL_ACCOUNT_PS_Full

· SDE_SAP46C_GLAccountDimension_Extract.W_SAP_GL_ACCOUNT_PS

7. Regenerate scenario of the packages SDE_SAP_GLAccountDimension_Extract and SDE_SAP46C_GLAccountDimension_Extract, if the scenarios have already been generated for these packages.