Error in EC-CS Data Monitor

Hi experts,
We have run the normal EC-CS posting after the month end closing. However data Monitor returns us an error for our parent unit in consolidation group. The error is "Item1&/Subitem &2: Discrepancy btw. Chgs in investee equity and totals DB" (error no GK 266)
I have read from SAP Note 673705, it seems like program error and I need to download the correction to fix it. Any other way to resolve this problem?
Thanks

Hello -
The consolidation ledger currency (group currency, I assume) is USD. The Consol Unit in question is EUR.
I checked the currency translation settings in the consol unit. There are four other units in the group, all with various currencies, which are working fine. We have another unit in another group that is EUR and it is working fine. We just added this one. I have compared it to the unit in EUR that works but can't find any differences.

Similar Messages

Error - While activation of Data in DSO

Hi Experts,
I'm facing following error message when tried to activate the data in DSO - The data went through fine in PSA and when triggered DTP to load data in DSO; the monitor showed green but when activated in DSO it's giving following error message. I transfered the global settings but facing the same following error message:
Diagnosis
     An exception wrong_date was raised while executing function module
     RST_TOBJ_TO_DERIVED_TOBJ .
System Response
     Processing the corresponding record has been terminated.
Procedure
     To analyze the cause, set a break point in the program of the
     transformation at the call point of function module
     RST_TOBJ_TO_DERIVED_TOBJ . Simulate the data transfer process to
     investigate the cause.
Procedure for System Administration
Any idea that why it's generating this error message while activating data in DSO. I checked those records in error stack and seems to be a date issue but I checked the factory calendar and check the validity and that's fine and is within the factory calendar data range.
Thanks in advance - you response will be really appreciated.

hi,
as you said the global settings were done,
try the global settings once again then delete the PSA(if records were less) nd load from source and then load to target.
this may solve if all settings were fine.
if records were huge in PSA, try correcting the records in error stack after allowing the good records to the target.
Ramesh

SQL Service Broker 2012: the connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)'

Anyone can help with the below issue please? Much appreciated.
We have about 2k+ messages in sys.transmission_queue
Telnet to the ports 4022 is working fine.
Network connectivity has been ruled out.
The firewalls are OFF.
We also explicitly provided the permissions to the service account on Server A and Server B to the Service broker end points.
GRANT
CONNECT ON
ENDPOINT <broker> <domain\serviceaccount>
Currently for troubleshooting purposes, the DR node is also out of the Availability Group, which means that we right now have only one replica the server is now a traditional cluster.
Important thing to note is when a SQL Server service is restarted, all the messages in the sys.transmission queue is cleared immediately. After about 30-40 minutes, the errors are continued to be seen with the below
The
connection was
closed by the
remote end,
or an
error occurred while
receiving data:
'64(The specified network name is no longer available.)'

We were able to narrow down the issue to an irrelevant IP coming into play during the data transfer. We tried ssbdiagnose runtime and found this error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>SSBDIAGNOSE -E RUNTIME -ID 54F03D35-1A94-48D2-8144-5A9D24B24520 Connect to -S <SourceServer> -d <SourceDB> Connect To -S <DestinationServer> -d <DestinationDB>
Microsoft SQL Server 11.0.2100.60
Service Broker Diagnostic Utility
An internal exception occurred: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
P 29830 Could not find the connection to the SQL Server that
corresponds to the routing address tcp://XX.XXX.XXX.199:4022. Ensure the tool is connected to this server to allow investigation of runtime events
The IP that corresponds to routing address is no where configured within the SSB. We are yet unsure why this IP is being referred despite not being configured anywhere. We identified that this IP belongs to one of nodes other SQL Server cluster, which has
no direct relation to the source server. We failed over that irrelevant SQL Server cluster and made another node active and to our surprise, the data from sys.transmission_queue started flowing. Even today we are able to reproduce the issue, if we bring
back this node [XX.XXX.XXX.199] as active. Since, its a high business activity period, we are not investigating further until we get an approved downtime to find the root cause of it.
When we get a approved downtime, we will bring the node [XX.XXX.XXX.199] as active and we will be running Network Monitor, Process Monitor and the SSB Diagnose all in parallel to capture the process/program that is accessing the irrelevant IP.
Once, we are able to nail down the root cause, I will share more information.

36 duplicate record found. -- error while loading master data

Hello BW Experts,
Error while loading master data
( green light )Update PSA ( 50000 Records posted ) No errors
( green light )Transfer rules ( 50000 ³ 50000 Records ): No errors
( green light )Update rules ( 50000 ³ 50000 Records ): No errors
( green light ) Update ( 0 new / 50000 changed ): No errors
( red light )Processing end: errors occurred
     Processing 2 finished
Þ     36 duplicate record found. 15718 recordings used in table /BIC/PZMATNUM
Þ     36 duplicate record found. 15718 recordings used in table /BIC/XZMATNUM
This error repeats with all the data-packets.
what could be the reason of the error. how to correct the error.
Any suggestions appreciated.
Thanks,
BWer

BWer,
We have exactly the same issue when loading the infoobject 0PM_ORDER, the datasource is 0PM_ORDER_ATTR.
The workaround we have been using is 'Manual push' from the details tab of the monitor. Weirdly we don't have this issue in our test and dev systems, even in Production, this doesn't occur somedays. We have all the necessary settings enabled in the infopackage.
Did you figure out a solution for your issue, if so please let me know and likewise I will.
-Venkat

Caller-70 Error while loading master data into infoobject

hi ,
I am getting following error while loading master data into infoobject (0tb-account). I am loading this master data in production environment for the first time. there are about 300000 records. All have got loaded upto PSA. Infopackage settings were PSA and then into data target.
Short dump in the Warehouse
Diagnosis
The data update was not finished. A short dump has probably been logged in BI. This provides information about the error.
System Response
"Caller 70" is missing.
ST22 dump analysis is as below:
Termination occurred in the ABAP program "GP476CZYBEF2WX53UZ8TXFG6XOS" - in
"VALUE_TO_SID_CONVERT_DB".
The main program was "RSMO1_RSM2 ".
Please help as soon as you can..Production problem....
Regards
Rakesh

Hi rakesh,
May be IDOCs not processed completely,
Idoc Problem, Either wait till time out & process Idoc from detail monitor screen, or go to BD87 & process Idoc with status = YELLOW ( be careful while processing IDOCS from BD87, choose only relevant Idocs
Cheers
Raj

Error occured in the data selection while extract data from Source system

Hello Friends
i am facing Problem while extracting data to Biw System from SAP R/3 system
The error mesage is 'Error occured in the data selection '
i.e. Monitoring - Details tab - Extraction - With error

Hi
The delta wil take the Last init selection for loading data in to the BW...
Did u check the IP at the Update tab is it the correct delta only.. or its a full..
better to go to the RSA3 and check the extractor in the Delta mode .. if u give ur delta mode it automatically takes the selction options.. so please try in RSA3..
regards
CK
PS: CHECK THE INIT SELECTIONS TOO or do an init with outdatatransfer and perform the delta...
Message was edited by:
BW Star

Error in data loads-Error occured in the data seletion

Hi,
We have to do an init load for Period 10 from data source 0EC_PCA_3.
When the period changes we usually copy the previous infopack and change the fiscal yesr period and do an init load.
This time we have to change the fiscal period to 010, we created a new info pack but the fiscal year period we forgot to change and was 009 and scheduled a init load.
The load failed with error mesg IN EXTRACTION PART:
1) syntax error in RSCDELTA
2) Error occured in the data selection -RSM 340
REQUEST part in monitor screen is green.
TRANSFER part in monitor screen is green
EXTRACTION shows:
Data request received ---green
Data selection scheduled -
green
Error occurred in the data selection -
RED
Processing (data packet): No data ---RED
We deleted the red request in the ods , deleted the init load in scheduled -init for source system --- chnaged the fiscal yesr period to 010 and triggered a new load but again it gives the same error mesg.
How to rectify this and do loads to the target successfully.
Please suggest

Please check the job log in the source system. It will give you the exact reason why extraction is failing. You need to act accordingly.
Thanks..
Shambhu

OCI Error ORA-01403: no data found in oracle goldengate replication after tts instaniation

I recently migrated our tg core system from sun solaris(11.1.0.7) to linux (11.2.0.3) environment using goldengate method (transportable tablespace method used for instantiation).
The initial replication worked with HANDLECOLLISIONS and after I monitor the lag finished, I took Handlecollisions off and noticed discarded report with OCI Error ORA-01403: no data found in two replications.
I followed every step in the tts migration steps provided by oracle best practice.
Can anybody provide any clue how do I fix this issue?
Thank you in advance.

extract and replicat are on schema level.
DO I have to do anything for replication on schema level?
Basic trandata logging enabled on source.

Error loading 0employee master data

Hello
I am facing some weird kind of probelm when i try to load data of 0EMPLOYEE_ATTR. im trying to load data of first 100 employes. data size is very small. in data monitor after few seconds it display the error message with caller09. it seems to me like somebody is trying to change data in ecc but i have chked it on the weekend when nobody was accessing the ecc system and tried to upload but unseccessful.
there are no trfc in the source system, i have also check the prcoess overview and job overview but nothing is helpful. in job overview in the log i just get memory parameters and nothing else. memory parameters are fine as othere datasources are loading data even with 1 milllion records but 0empoyee_attr i am facing for the first 100 records.
i have chked though slg1, rsdmd and me_del, its k.
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.

Hi,
If you are loading from flatfile then check the file for the two fields Date from and date to.
Or you can see the problem with the records in PSA also...
Check whether the date format is correct and also the date to should be more that the date from..
Cheers
Siva Reddy
Edited by: Siva Reddy S on Jul 10, 2008 3:29 PM
Edited by: Siva Reddy S on Jul 10, 2008 3:30 PM

Error while loading master data attribute

Hi Guru's
I am getting below mention error while loading master data attribute.
0MANU_MATNR : Data record 1035 ('000000000000229058 '): Version 'BDM755s ' is not valid
Please sugggest how to resolve ?
Regards
Karan

Hi,
I think there is problem with "0MANU_MATNR" Data, check the records 1033 to 1036 and find the differnce between 1035 record and other records, some values is giving problem so by looking at other reocrds i.e 1033,1034,1036. Check in PSA in Monitor.
Note: If any problem with Upper/Lowe case then use TOUPPER in Transfer Rules
If need use Conversion exits in transfer rules.
ALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    INPUT         = 0MANU_MATNR
IMPORTING
   OUTPUT        =   Result .
or
ALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
EXPORTING
    INPUT         = 0MANU_MATNR
IMPORTING
   OUTPUT        =   Result .
Thanks
Reddy
Edited by: Surendra Reddy on Mar 3, 2009 11:46 AM

Attribute change run fails - "Error when deleting the data record /B05/X.."

Hello,
I get the error message "Error when deleting the data record /B05/X.." on doing the change run.
I have already done RSRV on this objects and found no errors, but still the activation fails.
please give your suggestions ASAP to fix the issue as it is on production system.
Thanks.

Attribute change run could fails due to 2 reasons-
(1) attribute xchange run is already runnnig for any toher object(monitor lock) (check by thi prog-RSDDS_CHANGERUN_MONITOR)
(2) data is loading deleting from the object on which attribut changerun is running.(go in a manage tab and check)
check this two conditions and rerun the attribute changrun again from program - RSDDS_AGGREGATES_MAINTAIN and give the master data name in the selection.
Hope it helps you.

Trap syntax error in trap-schedule.dat alert; possibly SMC related

Receiving many ID xxxxxx daemon.alert events every hour. The message is:
[ID xxxxxx daemon.alert] syslog Nov 10 14:00:10 trap syntax error in trap-schedule.dat(200) at token '???'
followed immediately (same timestamp) with:
[ID yyyyyy daemon.alert] syslog Nov 10 14:00:10 trap *** aborting execution ***
I coudn't find anything on the web specifically for this message but several hits that looked similar seemed to indicate that this might be a problem in SMC. If it is not I apologize in advance.
System is an ldom:
Solaris 10;
SunOS clsol8 5.10 Generic_127127-11 sun4v sparc SUNW,T5140
Current situation is:
# /opt/SUNWsymon/sbin/es-validate
This script will help you in validation of Sun (TM) Management Center.
Validation Tool Version : 4.0
Host name : clsol8
Number of CPUs : 24
Platform : SUNW,T5140
Operating System : SunOS 5.10
Memory size : 2048 Megabytes
Swap space : 595480k used, 3727296k available
JAVA VERSION : "1.5.0_14"
Sun Management Center Production Environment Installation.
Following layers are installed : SERVER, AGENT, CONSOLE
Installation location : /opt/SUNWsymon
Sun Management Center installation status:
PRODUCT : Production Environment
INSTALLATION STATUS : Setup.
DATABASE SETUP : Setup.
COMPLETELY INSTALLED PACKAGES : SUNWescom,SUNWesbui,SUNWesbuh,SUNWenesi,
: SUNWesdb,SUNWesagt,SUNWessrv,SUNWessa,
: SUNWesjp,SUNWesaxp,SUNWesse,SUNWesclt,
: SUNWesjrm,SUNWmeta,SUNWenesf,SUNWesmdr,
: SUNWesgui,SUNWesweb,SUNWessvc,SUNWesasc,
: SUNWescix,SUNWsuagt,SUNWsusrv,SUNWesval,
: SUNWesmc,SUNWessms,SUNWessdv,SUNWescdv,
: SUNWlgsmc,SUNWeslac,SUNWesodbc,SUNWesmib,
: SUNWesken,SUNWesmod,SUNWesae,SUNWesaem,
: SUNWesmcp,SUNWesafm,SUNWescon,SUNWsucon,
: SUNWescli,SUNWesclb
<NOTE: I had to cut out a bunch of installed components to hit character limit>
Sun Management Center Add-Ons and Versions:
PRODUCT VERSION
Production Environment 4.0
Advanced System Monitoring 4.0_Build15
Sun Fire Entry-Level Midrange S 3.5-v6
Service Availability Manager 4.0_Build15
Performance Reporting Manager 4.0_Build15
Solaris Container Manager 4.0_Build15
Sun Fire Midrange Systems Platf 3.5-v6
System Reliability Manager 4.0_Build15
Sun Management Center Integrati 4.0_Build15
Workgroup Server 3.6
Generic X86/X64 Config Reader 4.0_Build15
Sun Management Center Patch installation details:
No Sun Management Center patch is installed.
Sun Management Center disk-space consumption:
PRODUCT APPROXIMATE DISK SPACE CONSUMED
Production Environment : 54452 kB
Advanced System Monitoring : 2391 kB
Sun Fire Entry-Level Midrange S : 1738 kB
Service Availability Manager : 1838 kB
Performance Reporting Manager : 3371 kB
Solaris Container Manager : 3688 kB
Sun Fire Midrange Systems Platf : 3270 kB
System Reliability Manager : 970 kB
Sun Management Center Integrati : 540 kB
Workgroup Server : 3707 kB
Generic X86/X64 Config Reader : 608 kB
TOTAL : 76573 kB
Database is located at : /var/opt/SUNWsymon/db/data/SunMC
Free space available on this partition is : 6493142 kB
Following locales are installed :
Information about upgrade from old versions is not available.
Sun Management Center Ports:
SUNMC COMPONENT PORT_ID
agent service 1161
trap service 162
event service 163
topology service 164
cfgserver service 165
cstservice service 167
metadata service 168
platform service 166
grouping service 5600
rmi service 2099
webserver_HTTP service 8080
webserver_HTTPS service 8443
You are currently running SNMPDX.
Sun Management Center Server Hosts definitions in domain-config.x:
SUNMC COMPONENT SERVER_HOST
agent service clsol8
trap service clsol8
event service clsol8
topology service clsol8
cfgserver service clsol8
cstservice service clsol8
metadata service clsol8
platform service clsol8
Sun Management Center Processes:
SUNMC SERVICE STATUS
Java Server Running.
Database services Not Running.
Grouping service Running.
Event-handler service Running.
Topology service Not Running.
Trap-handler service Not Running.
Configuration service Running.
CST service Not Running.
Metadata Services Running.
Hardware service Not Running.
Web server Running.
Sun Management Center Agent Running.
Platform Agent Not Running.
Privilege level for Sun Management Center users :
CATEGORY USERS
esadm : smcadmin
esdomadm : smcadmin
esops :
ALL USERS : smcadmin
server is local host
Web server package is installed correctly.
Web Server is up and responding.
Web Server servlet engine is up and responding.
I have also read that patching SMC has caused problems for some people so I don't really want to try that until I get some feedback.

Hi Mike,
Tried your suggestion to rename the .dat and let SMC recreate it but I can't get the SMC database service to launch. So it looks like I am having trouble with the database. Any suggestions?
To back up, you nailed it with the loss of power - we lost both power supplies on a Sunday night with no warning and nothing in /var/adm/messages (since we send them to a loghost.) It was determined that chips within each power supply in the T5140 failed. So we replaced both power supplies and fired the server up. That is when we started getting the trap errors and only those two errors on clsol8.
I did check http://sun.com/msg/SMF-8000-KS but am not sure how that helps.
What I tried:
On clsol8 as root:
# cd /opt/SUNWsymon/sbin
# ls
{db-memconfig.sh   es-details        es-imagetool      es-setup
db-start          es-device         es-inst           es-start
db-stop           es-dt             es-keys.sh        es-stop
es-apps           es-gui-imagetool es-lic            es-tool
es-backup         es-guiinst        es-load-default   es-trapdest
es-chelp          es-guisetup       es-makeagent      es-uninst
es-cli            es-guistart       es-platform       es-validate
es-common.sh      es-guistop        es-restore        esmultiip
es-config         es-guiuninst      es-run            ports.config}
# ./es-stop -A
{Stopping metadata component
Stopping cfgserver component
Stopping topology component
Stopping event component
Stopping grouping service
Stopping trap component
Stopping java server
Stopping webserver
Stopping agent component
Stopping platform component}
<attempting Mike's solution suggestion>
# cd /var/opt/SUNWsymon/cfg
# ls
trap-schedule.dat
# mv trap-schedule.dat trap-schedule.dat.maybeCorrupted
# /opt/SUNWsymon/sbin/es-start -Ac
{Some of the SunMC services are in maintenace state.
Please check the corresponding SMF service log in /var/svc/log directory.
Please disable the services in maintenance state and re-start the services again.}
# svcs -vx
svc:/application/management/sunmcdatabase:default (SunMC database service)
State: maintenance since November 6, 2009 3:50:51 PM CST
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/application-management-sunmcdatabase:default.log
Impact: This service is not running.
svc:/application/management/sunmcwebserver:default (SunMC webserver service)
State: maintenance since November 12, 2009 2:45:50 PM CST
Reason: Start method failed repeatedly, last exited with status 103.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/application-management-sunmcwebserver:default.log
Impact: This service is not running.}
# svcadm disable sunmcdatabase
# svcadm disable sunmcwebserver
# svcs -vx
# svcadm enable sunmcdatabase
# svcadm enable sunmcwebserver
# /opt/SUNWsymon/sbin/es-start -Ac
{Failed to successfully perform Database Startup.}
# svcs -vx
svc:/application/management/sunmcdatabase:default (SunMC database service)
State: maintenance since November 12, 2009 2:49:50 PM CST
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/application-management-sunmcdatabase:default.log
Impact: This service is not running.}
# cd /
# svcadm disable sunmcdatabase
# shutdown -y -g0 -i6
(after reboot, I logged into clsol8 and su'd to root)
# svcs -xv
svc:/application/management/sunmcdatabase:default (SunMC database service)
State: disabled since November 12, 2009 3:02:11 PM CST
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
Impact: 1 dependent service is not running:
svc:/application/management/sunmctopology:default}
# svcadm enable sunmcdatabase
# svcadm disable sunmcdatabase
# svcadm clear sunmcdatabase
svcadm: Instance "svc:/application/management/sunmcdatabase:default" is not in a maintenance or degraded state.
# svcadm refresh sunmcdatabase
# svcadm enable sunmcdatabase
# svcs -xv
svc:/application/management/sunmcdatabase:default (SunMC database service)
State: offline since November 12, 2009 3:09:25 PM CST
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: /var/svc/log/application-management-sunmcdatabase:default.log
Impact: 1 dependent service is not running:
svc:/application/management/sunmctopology:default
# svcs -xv
svc:/application/management/sunmcdatabase:default (SunMC database service)
State: maintenance since November 12, 2009 3:10:30 PM CST
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/application-management-sunmcdatabase:default.log
Impact: 1 dependent service is not running:
svc:/application/management/sunmctopology:default
[ Nov 12 15:08:37 Leaving maintenance because disable requested. ]
[ Nov 12 15:08:37 Disabled. ]
[ Nov 12 15:09:07 Rereading configuration. ]
[ Nov 12 15:09:25 Enabled. ]
[ Nov 12 15:09:25 Executing start method ("/lib/svc/method/es-svc.sh start datab
ase") ]
execution of verifyDatabaseUp failed
exiting........................
[ Nov 12 15:10:30 Method "start" exited with status 95 ]

Error in visualizing a Data Form "WDEFGenerator.cpp"

Hi,
I have migrated an HFM application from version 4.01 SP2 to version 11.1.2.1
Everything works fine appart from an error in visualizing a Data Form:
In the previous version of HFM this error was not verified.
If I disable the option SuppressNoDataRows I get no errors but I would like to keep this option enabled.
Does anyone know what could be the problem?
The error I'm getting is:
Error Reference Number: {3783BC27-A47D-463A-9F21-5E1C2B55A775};User Name: hypadmin@Native Directory
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:11 PM;Svr: BMI-2K8-HFMPA;File: WDEFGenerator.cpp;Line: 1407;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:12 PM;Svr: BMI-2K8-HFMPA;File: WDEFGenerator.cpp;Line: 3284;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:12 PM;Svr: BMI-2K8-HFMPA;File: WDEFGenerator.cpp;Line: 3166;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:12 PM;Svr: BMI-2K8-HFMPA;File: CHsvWebFormGeneratorACM.cpp;Line: 3687;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:12 PM;Svr: BMI-2K8-HFMPA;File: CHsvWebFormGeneratorACM.cpp;Line: 3389;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:11 PM;Svr: BMI-2K8-HFMPW;File: CHsvWebFormsACV.cpp;Line: 569;Ver: 11.1.2.1.103.3505;
And the data form script is:
ReportType=WebForm
ReportLabel=1_1_12_1
ReportDescription=Trade Receivables > 12 months
BackgroundPOV=S#ACT.w#<Scenario View>.V#<Entity Currency>.A#[None].I#[ICP None].C1#[None].C2#[None].C3#[None].C4#[None]
SelectablePOVList=Y{[Hierarchy]}.P{[Second Generation]}.E{GRBRA000.[Base]}
C1=C1{FL_CURR.[Base]}
R1=A#3_03_01.I#[ICP Entities],AddMember:I{CONS}
R2=A#3_03_01.I{CONS}
R3=A#3_03_02.I#[ICP Entities],AddMember:I{ASS}
R4=A#3_03_02.I{ASS}
R5=A#3_03_03.I#[ICP Entities],AddMember: I{PARENT}
R6=A#3_03_03.I{PARENT}
R7=A#3_03_04,NoSuppress
R8=A#3_03_1.I#[ICP Top],CustomHeaderStyle:font: bold,NoSuppress
FormRowHeight=20 px
PrintNumRowsPerPage=10
PrintNumDataColsPerPage=3
SuppressNoDataRows=True
ShowLabels=True
SuppressColHeaderRepeats=False
HeaderOptionAccount=ShowLabel,ShowDescription,Length:50
HeaderOptionICP=ShowDescription
HeaderOptionCustom1=ShowDescription
HeaderOptionCustom2=ShowDescription
Thanks
Best Regards

Hi
Check they have the "Data Form Write Back from Excel" role in Shared Services.
See p.133 of the security guide for more info -
http://docs.oracle.com/cd/E17236_01/epm.1112/hss_admin_1112200.pdf
Regards
jpr

Error while Activating DSO Data

Hello
I am having a problem, I am getting an Error while activating DSO Data, Data is loaded in DSO succefully but can not be activated with this error
"Activation of M records from DataStore object 0FIAR_O03 terminated"
Thanks

Hi,
The activation would have failed due to varies reasons..
It would be a short dump,check in ST22.
check the job log in SM37 for better understanding of the issue.
Have you loaded the respective master data?
if it is a transaction data load,then the SID is checked at the time of activation and not during loading.
So if the master data is not loaded then the activation would fail.
It can also be due to the system performance at that moment.
Even if the data volume is huge ,there are chances of the activation failing..
Try repeating the activation once again.it might succeed..
Else check the logs to understand the actual issue.

Getting an error while viewing a data in owb

Hi,
I created an External table based on a flat file. But I am not able to view the data in the external table while the flat file has the data.
I am using this external table as a source in my mapping but no data is getting loaded even after the successful execution of the mapping.I am getting the following error while viewing the data
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-29400: data cartridge error
KUP-04040: file ATLAS in ATLAS_LOCATION1 not found
Please help me regarding this. I am new to the owb 11g.

Thanks for you reply. Still I can't view the data. Actually what i did is imported a .csv file using files then created a external table configured , validated and deployed.In next step created a mapping with this excel this using table operator validated and genrated code. In next step using the control center manager i deployed it. But i can't view the data still in the external table.
Is this procedure is correct for loading the excel sheet in to databse. My client environment is on windows xp and database is on linux environment.
Please help me regarding this.I am new to owb.

Error in EC-CS Data Monitor

Similar Messages

Maybe you are looking for