How to handle [object Object] in textArea (Flex 4.5)
Hello
My code:
protected function myDG_selectionChangeHandler(event:GridSelectionEvent):void
var selItems:Vector.<Object> = event.currentTarget.selectedItems;
var numItems:Number = selItems.length;
for (var i:Number = 0; i<numItems; i++)
selectedItemsTA.text = selectedItemsTA.text + selItems[i] + "\n";
Currently I'm just trying to make multiple selections in a datagrid and reflect those in a text area control.
My selections just come across as [object Object]. So, obviously I don't know for sure what data is behind that.
It's really not much different from the example here: http://help.adobe.com/en_US/flex/using/WSc2368ca491e3ff923c946c5112135c8ee9e-7fff.html but their textarea is reset to empty each time through, and I'm using a datagrid vs. their list, and of course the event type.
Thanks
Kristin
Hi again
Okay, I got it.
See, there are these little nuances that are hard to pick up sometimes.
Thanks
KRistin
Similar Messages
-
How to handle lock object in BDC call transcation method?
Hi,
how to handle lock object in BDC call transcation method?
Thanks In advances.If you are updating Z-fields then you need to create a lock entry, before you use call transaction.
After creating lock object, please use FM Enqueue_<lockname> before CALL transaction and FM Dequeue_<lockname> after you have commited your data.
Thanks,
Kartavya -
How to Handle Business Object event in ABAP class
Hello Everybody,
I wanted to know if it was possible to reference BOR objects in ABAP class and handle BOR events in ABAP Objects.
Thanks in advance.Hi,
Catch the et_VALIDATE event, when InnerEvent = False and ItemChanged = True.
If pVal.EventType = BoEventTypes.et_VALIDATE Then
If pVal.InnerEvent = False And pVal.ItemChanged Then
'TODO Your code here...
End If
End If
Regards,
Vítor Vieira -
How to handle EDI object in upgrade?
Hi experts,
we are using standart message types in EDI of our 4.6c version .how can we handle these EDI while upgrade from 4.6c to ECC 6.0.
If any one worked in this please help us.
Thank you.
regds,
devika.https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/818a20be-0601-0010-e3b8-ac3d5f975319
plz go this link.
Hope you get ur answer there itself.
regards,
rewards point. -
How to handle plsql Object and Table type inside BPEL
Hi All,
I have a procedure with 5 IN and 4 OUT parameters. Out of 4, One is Object type and remaining 3 are Table type. Now in my bpel, i am calling this proc from DB Adapter. The DB Adapter wizard created XSD with proper structure. But when i am testing this i am not getting these out parameters values in the payload of Invoke DBAdapter activity. I am neither getting errors nor output.
What could be the issue.?
Thanks in advance,
SudheerArik,
JDev is not creating any wrapper packages as such. It simply created a XSD with same as my procedure name.
My XSD looks like this...
<element name="OutputParameters">
<complexType>
<sequence>
<element name="P_OBJ_H_INFO_O" type="db:APPS.H_OBJ_TYPE" db:index="6" db:type="Struct" minOccurs="0" nillable="true"/>
<element name="P_TAB_L_INFO_O" type="db:APPS.L_TAB_TYPE" db:index="7" db:type="Array" minOccurs="0" nillable="true"/>
<element name="P_TAB_M_INFO_O" type="db:APPS.M_TAB_TYPE" db:index="8" db:type="Array" minOccurs="0" nillable="true"/>
<element name="P_TAB_A_INFO_O" type="db:APPS.A_TAB_TYPE" db:index="9" db:type="Array" minOccurs="0" nillable="true"/>
</sequence>
</complexType>
</element>
And again the 3 table types internally referring object types.
Thanks for reply. Awaiting response...
Sudheer -
Handling 3d objects using JavaScript for Acrobat 3D Annotations API
I am trying to learn how to handle 3d objects with this manual: http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/js_3d_api_reference.pdf
When I execute some code, for example,
myTimeHandler= new TimeEventHandler();
myTimeHandler.onEvent= function( event )
console.print( "Current simulation time is:" + event.time );
console.print( " second(s)" );
runtime.addEventHandler( myTimeHandler );
I get an error like this:
TimeEventHandler is not defined
Why?
P.S. I have 3d object in the document, and can get it with function getAnnots3D.You have to run the code in the context of the 3D annotation (by attaching the script to the annotation's properties panel, or by right-clicking the active 3D scene and choosing "run a javascript". You cannot run it in the console.
-
How to handle the call transaction in method of a custom business object
Hello all,
There is a custom report " RPTCORAPP" for approving leaves . As per my requirement i have develop a copy of leave workflow and for approval process i have call "RPTCORAPP" in Custom method of custom object. i have made a transaction for this custom report for approving attendances. I am calling this method though call transaction statement within method.
Problem: while approving the attendance workitem is not disappearing from the portal. Problem is due to call transaction statement.
once workitem come to the user, user click on it. control goes to the report, which display all the leave to approve on
the portal.
If after approving/ rejecting attendance user close the screen.workflow remain in the "process" status.Control wont come back after call transaction statement in the method.
At the same time if user clicks on back button inspite of closing the screen. it is working fine. workitem disappears from the portal.
How to handle the scenarion. if after approving/rejecting, i want the control to come back to the NEXT STATEMENT after call transactionstatement in my method.
Please help it out........:)Hi swami,
thanks for reply. but i am not using BDC in my method. iam just calling a custom transaction thriugh statement
Call transaction 'ZHR_APPROVE_CLINOUT'. This transaction directly run the report RPTCORAPP and display all the request. -
How to handle the Exception in GP using executable callabel object.
Hi all,
I handled an exception in GP using Background callable Object. That is working fine.
(Ex: Exception_No_User_Found). The Problem is I am not able to handle the exceptions for normal callable object. I have done the same thing as i did in background callable object except implementing IGPBackgroundCallableObject Class. I have created an WebDynpro DC Project where in getDescription method i declared an Exception and in execute method of component controller I caught the exception if no user found.
Then i created an callable object for this simple DC project. but that is not working i could not catch the exception. when i execute the process it is asking the User ID if i give the wrong userId it is not refreshing back to the user id input form.
But if i test that simple callable object separately it is throwing an Exception when I give the wrong input..
but the same thing is working fine using background callable object.
I couldn't handle the exception for the simple callable object or executable callable object.
Please If anyone bring me the solution that would be appreciated.
Thanks in advance.
Regards,
Malar.Hi Shikhil
Thanks for your reply
Please have a look below for exceptions which i am getting in GP and let me know how to handle these exceptions.
1) "Activity could not be read"
2) "Action has been stopped"
3) error while processing the item can not be displayed
if you give any idea/clue how to handle these exceptions then it would be great help to me
Thanks
Sunil -
How to make a handling unit object (packing) automatically generate from inbound
Hi guru,
I just have a question which I am sure sure and puzzle, and hope you can give me an accurate information.
Background:
We are using EDI communication so that vendor can send us advance shipping notification and will lead to inbound delivery creation automatically.
Question:
We would like the vendor, when deliver the shipment for us to be packed base on our instruction, and we want the handling unit object to be created automatically upon inbound delivery creation from the EDI. How to do this in SAP?
Thanks.
Danielif you are using message type DESADV / SHPCON then vendor needs to send the HU information in the E1EDL37(HU Header) / E1EDL44 (HU Item) segment and during Inbound delivery creation system will update the IBD with HU . Have a look on the below standard Link to get more detail
Delivery Interface - Shipping (LE-SHP) - SAP Library -
How to call request object of IPortalComponent in KM Scheduler application
Hi
We are reading RFC Table data using JCO Connection Pool(JCOClientPoolEntry. Please find the below teo line code.If we put this code in KM Scheduler application then its throwing error for the request objecct of IPortalComponenetRequest.
IJCOClientPoolEntry jcoPoolEntry = null;
jcoPoolEntry = clientService.getJCOClientPoolEntry(sysId, request);
Can you please let me know how to use request object of IPortalComponent in KM Scheduler application?
Thanks,
SusmitaHello GopalY,
In my experience its not possible to call OLE object in Webui. Maybe customer 3 party application will be supply some web service to handle credit card payments. I think this is the simple way to access 3party application.
Regards,
Zafer, -
HOw to make an Object oriented alv respond to double click
Hi all,
HOw to make an Object oriented alv respond to double click.SAmple code will be helpful.
Thanks in advance,
Alex.Hi,
1. Create a Control (for Custom and Split Containers only)
2. Instantiate a Container Object (in case of Custom and Split Containers, specify the control which is created by us in Screen painter) CREATE OBJECT
3. Instantiate an Object of the kind of report that has to be displayed (List, Grid or Tree). CREATE OBJECT . Here we need to specify the Parent Container as the so that it sits in that container.
4. Call appropriate methods to display the report on the screen. CALL METHOD ->
DATA : g_dock TYPE REF TO cl_gui_docking_container,
g_split TYPE REF TO cl_gui_easy_splitter_container,
g_cont1 TYPE REF TO cl_gui_container,
g_cont2 TYPE REF TO cl_gui_container,
g_grid1 TYPE REF TO cl_gui_alv_grid,
g_grid2 TYPE REF TO cl_gui_alv_grid.
i_mara is an internal table of structure MARA
SELECT * FROM mara INTO TABLE i_mara.
i_kna1 is an internal table of structure KNA1
SELECT * FROM kna1 INTO TABLE i_kna1.
To create an Object of type Docking Container
CREATE OBJECT g_dock
EXPORTING
side = cl_gui_docking_container=>dock_at_top
extension = 200 .
To Create an Object of Type Split Container. Here we can see that the Docking *Container Created above has been used as a parent .
CREATE OBJECT g_split
EXPORTING
parent = g_dock
orientation = 1 .
Easy Split container splits one Control into 2 manageable controls, each of them is used * to handle one GUI Container each
g_cont1 = g_split->top_left_container.
g_cont2 = g_split->bottom_right_container.
To Create an Object of type Grid . Here we can see that the Left Split Container * Created above has been used as a parent .
CREATE OBJECT g_grid1
EXPORTING
i_parent = g_cont1 .
To Create an Object of type Grid . Here we can see that the Right Split Container * Created above has been used as a parent .
CREATE OBJECT g_grid2
EXPORTING
i_parent = g_cont2 .
The method of Grid Control Object is used to display the Data.
CALL METHOD g_grid1->set_table_for_first_display
EXPORTING
i_structure_name = 'MARA'
CHANGING
it_outtab = i_mara[] .
The method of Grid Control Object is used to display the Data.
CALL METHOD g_grid2->set_table_for_first_display
EXPORTING
i_structure_name = 'KNA1'
CHANGING
it_outtab = i_kna1[] .
Regards
Hari -
How to remove the Object from memory.
Hello.
Flash file that i made with Flex Builder uses memory too
much.
Look at the next example source code.
var testCan:Canvas = new Canvas();
this.addChild(testCan);
this.removeChild(testCan);
testCan = null;
but just memory usage still goes up, is not freed instantly.
so if i load the large flash files on my web browser,
after 5 munites or something, the web browser is down.
How to remove the object from memory immediately without
delay?It's all about the Garbage Collector ..
There is a nice write up here :
http://www.gskinner.com/blog/archives/2006/06/as3_resource_ma.html -
How to migrate the Objects from 3.1c to BI7
Hi,
We are in Functional Upgradation.
How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
Please help me to doing this....
regards,
anilBW Upgrade tasks (BW 3.1C to BI 7.0)
Prepare Phase:
Task How-To Who
Review BI 7.0 feature lists Review BI 7.0 feature lists for possible inclusion in developments. Basis/BW
Obtain the BI 7.0 upgrade guide Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
Basis/BW
Review all upgrade SAP notes In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
BI 7.0 Upgrade notes
SAP Web Application Server 6.40 upgrade notes
OS and DB specific upgrade notes
SAP BW Add-on upgrade notes
(e.g. SAP SEM, ST-PI, etc)
Plug-In upgrade SAP notes
Other notes identified in above notes and/or upgrade guides.
Basis/BW
Check DB and OS requirements for the target SAP BW release Check DB version/patch level and OS version/patch level required for upgrade
First check the most current information from the SAP BW homepage http://Service.sap.com/BW -> <SAP BW release> -> Availability
Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
Basis
Check SAP BW Add-on upgrade requirements Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
Basis
Check SAP BW upgrade requirements Minimum Support Package and kernel levels for upgrade
SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
Source system Plug-In requirements Basis
Check compatibility requirements with 3rd party software 3rd Party Reporting tools (example: Crystal)
ETL Tools (example: Ascential, DataStage, etc)
Scheduling tools (example. Control-M, Maestro, etc)
Monitoring tools (example: HP OpenView, Patrol, etc)
Other OS or DB related tools Basis
Check new component requirements for BI 7.0 If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
The IGS chart migration will also be required after the SAP BW web report conversion.
If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0. (ArcView 8.2?).
If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides -> SAP NetWeaver).
Basis
Test and distribute new SAP BW Frontend
Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
Basis
Alpha Conversion:
Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool) Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
Transaction RSMDCNVEXIT
Check the system status:
u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
u201CNo Check yet/Inconsistent Internal Vales existu201D:
The Alpha converter check has not been executed.
u201CCharacteristics have Inconsistent Internal Valuesu201D:
The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
BW
Upgrade SAP Note updates Check for newer versions of your SAP notes for the Upgrade.
Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
Basis/BW
Confirm SAP BW support package, kernel and DB/OS configuration Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
Basis
Alignment of SAP BW objects within your SAP BW system landscape Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
Basis/BW
Confirm all developments are deployed. Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
For SAP BW developments not already collected in the transport collector, a decision must be made:
Deploy the developments or wait until the upgrade has completed to deploy.
o Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
o Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
BW
Implement BI 7.0 Business Explorer Frontend Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
Basis/BW
Pre-upgrade Process:
Download required BI 7.0 support package Stack for inclusion in the upgrade Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
Basis
Apply latest Support Package tool patch Apply latest SPAM patch before executing PREPARE Basis
Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency Check Database consistency
Transaction DB02:
o Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
o Check missing database objects (indices, tables, etc)
o Missing indices may identify erred data loads or process problems
Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
Note: check for running data loads before executing a repair!
o Check DDIC/DB consistency
Verify database objects and consistency
(e.g. SAPDBA check for offline data files)
BW
Remove unnecessary SAP BW temporary database objects Delete all SAP BW temporary database objects:
Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
This reduces the numbers of database objects that need to be copied during the upgrade.
Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
BW
Validate your SAP BW Objects for correctness prior to your upgrade Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
Note: this test should be repeatable so you can re-validate after the upgrade!
Ensure that any inconsistencies are identified and corrected
RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
BW
Ensure DB Statistics are up to date prior to the upgrade Check DB statistics for all tables.
Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
Check DB statistics for missing Indexes for InfoCubes and Aggregates
o User transaction RSRV to check BW
Check SAP BW Support Package status Check the status of all support packages (via transaction SPAM)
Ensure the Support Package queue is empty
Confirm all applied Support Packages Basis
Check all u2018Repairsu2019 Check for unreleased repair transports
Release all unreleased transports
In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
BW
Check InfoObject status Check for revised (modified) InfoObjects that have not been activated.
All InfoObjects should be active or saved (not activate):
o Check all inactive InfoObjects:
Transaction RSD1 (Edit InfoObjects),
click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
Modified InfoObjects are denoted by yellow triangles!
o Determine if revision should be activated or removed.
'Reorgu2019 or u2018Repairu2019 all InfoObjects
This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
BW
All ODS data loads must be activated. Activate all inactivated ODS Object requests.
All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
o Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
BW
All Transfer and Update rules should be active Check for inactive Update and Transfer Rules
o All update rules and transfer rules should be active or deleted.
o Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure. BW
All InfoCubes should be active Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
o All InfoCubes should be activated or deleted.
o Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
BW
All Web Report objects should be consistent prior the upgrade. Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
o For Original release SAP BW 3.x:
A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
Please see SAP note 484519 for details.
BW
Backup your system before starting PREPARE Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
Database admin
Address any instructions/errors generated by PREPARE Address any issues listed in log files Checks. Log generated by PREPARE.
o Repeat PREPARE until all checks are successful. Basis
Complete any Logistic V3 data extractions and suspend V3 collection processes Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
o The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
BW
Complete any data mart data extractions and suspend any data mart extractors Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
o The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
BW
Check that your customer defined data class definitions conform to SAP standards Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
o Check your data class definitions as detailed in SAP Notes 46272 and 500252.
o Incorrect data classes could create activation errors during the upgrade.
BW
Remove unnecessary SAP BW temporary database objects Delete all SAP BW temporary database objects:
Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
This reduces the numbers of database objects that need to be copied during the upgrade.
Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
Basis/BW
Backups! Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
Database Admin
Before Execution:
All SAP BW administration tasks should have ceased Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
- timing depends on the type of upgrade selected
Basis/Admin
Remove unnecessary SAP BW temporary database objects Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
- timing depends on the type of upgrade selected
BW
Check system parameters Check OS, DB, and Instance profile parameters.
Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
Check for any DB specific parameters for BI 7.0
Check for any new OS parameters Basis
Check Database archiving mode Turn database archive log mode back on if it was disabled during the upgrade!
Database Admin
After Execution:
Check the systemu2019s installation consistency Execute Transaction SICK to check installation consistency
BW
Check the system logs Perform a technical systems check.
Example: Check system and all dispatcher logs (inc. ICM logs)
Basis
Apply latest executable binaries Apply the latest 6.40 Basis Kernel for all executables
Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
Basis
Review BI 7.0 Support Packages for follow-up actions. Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
o Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o Follow any required instructions identified in the SAP Notes
Basis
Apply latest patches Apply the latest SPAM patch
Apply any required support packages that were not bound into the upgrade.
Basis
Apply additional BI 7.0 Support Packages
(if required) SAP recommends that customer remain current on SAP Support Packages.
Review SAP Notes for all SAP BW Support packages applied in previous task.
o Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o Follow any required instructions identified in the SAP Notes
Basis
Resolve any modified SAP delivered Role issues If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
Review and implement SAP note 569128 as required Basis
Configuring Information Broadcasting EP/KMC Connections
If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
Basis
Re-check SAP BW Object and consistency Execute RSRV to check SAP BW Object consistency
Repeat tests that we executed prior to the upgrade.
Validate results BW
Check InfoCube views for consistency Check consistency of InfoCube fact table views
It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
BW
Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
o Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
Check that all other Source Systems are active.
o Activate as required. Basis/BW
Check SAP BW Personalization is implemented (SAP BW 2.X upgrades will have performed this in the previous task).
Validate that personalization has been activated in your SAP BW system.
Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
To activate highlighted Personalization, click Execute. BW
For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert ODS secondary indexes to new standard For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
Re-create all indexes in the ODS Object definition screen in transaction RSA1.
ODS indexes must conform to the new naming convention
BW
Converting IGS chart settings
Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
o Test via transaction RSRT
Execute the conversion process as directed the BI 7.0 upgrade guide.
Note: This step is required for all BI 7.0 upgrades Basis
Backup your SAP BW system Perform a full database backup (including the File system)
Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
Database Admin -
Exception Handling in Object Oriented Design
I am developing a huge web based project using Object Oriented design and java,srvlets ,jsp etc ,I am using 3-tier archtecture.I dont understand,how i should handle exceptions in my project.ie.If there is some exception in the base modules how should it be handled.What kind of excpetion Structure should i use,How many exception classes should be made etc,
Can someone help me in this regardA couple things I have found to be good practices for exception handling in an n-tier architecture:
1. Don't expose all the internal exceptions of a tier to the client of the tier. Create a more useful, descriptive set of exceptions (or use the appropriate predefined exceptions) to throw up to the client.
For example, on one project, we are doing database access among other things in the "service" tier, which is accessed by the web tier. We catch the SQLExceptions, PersistenceExceptions (a custom exception), and others, and throw a more useful exception that the client will know how to handle such as a NoMeasurementResultsException if the client asks for measurement results when we have none.
2. Chain your exceptions and/or log the root cause in the tier that re-throws a different exception. There is nothing more aggravating than not knowing why, when you are debugging a problem, you are getting a NoMeasurementResultsException when you know that there ARE results in the database.
Hope these ideas help in your design.
Cheers,
Colin -
Salmple at How to Create Dynamical Object for RTTC
Hi all, I need a sample at How to Create Dynamical Object for RTTC.
you can help me?.Hello Martinez,
I have attached a sample for structure types. With the Where-Used-List on the Create() Method of the various RTTC classes one may find more samples. If you meant with object on OO Type then it is to mention that this is not possible yet.
Regards
Klaus
PROGRAM sample.
DATA: sdescr1 TYPE REF TO cl_abap_structdescr,
sdescr2 TYPE REF TO cl_abap_structdescr,
tdescr1 TYPE REF TO cl_abap_tabledescr,
tdescr2 TYPE REF TO cl_abap_tabledescr,
tref1 TYPE REF TO data,
tref2 TYPE REF TO data,
comp TYPE abap_component_tab,
wa TYPE t100,
xbuf TYPE xstring.
FIELD-SYMBOLS: <tab1> TYPE table,
<tab2> TYPE table.
sdescr1 ?= cl_abap_typedescr=>describe_by_name( 'T100' ).
comp = sdescr1->get_components( ).
sdescr2 = cl_abap_structdescr=>create( comp ).
tdescr1 = cl_abap_tabledescr=>create( sdescr2 ).
tdescr2 = cl_abap_tabledescr=>create( sdescr2 ).
CREATE DATA: tref1 TYPE HANDLE tdescr1,
tref2 TYPE HANDLE tdescr2.
ASSIGN: tref1->* TO <tab1>,
tref2->* TO <tab2>.
wa-sprsl = 'E'. wa-arbgb = 'SY'. wa-msgnr = '123'. wa-text = 'first text'. INSERT wa INTO TABLE <tab1>.
wa-sprsl = 'D'. wa-arbgb = 'SY'. wa-msgnr = '456'. wa-text = 'second text'. INSERT wa INTO TABLE <tab1>.
wa-sprsl = 'D'. wa-arbgb = 'XY'. wa-msgnr = '001'. wa-text = 'third text'. INSERT wa INTO TABLE <tab1>.
wa-sprsl = 'D'. wa-arbgb = 'ZZ'. wa-msgnr = '123'. wa-text = 'fourth text'. INSERT wa INTO TABLE <tab1>.
wa-sprsl = 'E'. wa-arbgb = 'SY'. wa-msgnr = '123'. wa-text = 'ABAP is a miracle'. INSERT wa INTO TABLE <tab1>.
EXPORT tab = <tab1> TO DATA BUFFER xbuf.
IMPORT tab = <tab2> FROM DATA BUFFER xbuf.
LOOP AT <tab2> INTO wa.
WRITE: / wa-sprsl, wa-arbgb, wa-msgnr, wa-text.
ENDLOOP.
Maybe you are looking for
-
Sharepoint 2013 Upload documents error
I have users in Europe that are unable to upload their documents to Sharepoint, we hare just going LIVE with Sharepoint and have come across this issue, any help would be appriciated. [Forced due to logging gap, cached @ 02/14/2014 09:11:11.46, Origi
-
Firefox won't load homepage when launched and crashes when closed.
Last night, while I was in Firefox, a notification popped up that updater.exe had been downloaded. I could easily take a guess: a new version of Firefox was out. I closed Firefox and then had the updater do its thing. When Firefox then launched & cam
-
Item of sales order is so repeated post goods issue that stock is negative
dear expert: the stock value of sales order is negative ,because the goods is post twice,i donn't know what' cause of question .in schedule line of sales order ,order quantity is 1, confirmed qty 1,deliveried qty :2. so mska-KALAB is -1. please hel
-
Quantity control when creating from reference document
Hi, When creating a follow-up document, is there a configuration that the quantity in the follow up document cannot exceed it's parent document. For example, I have a Quotation with one line item that contain Product A 10 units. Now, when I create a
-
Good night, I am just starting in bussines design, i am not rich enough to buy photoshop license, but i'm loved to use photoshop, could i use photoshop cs2 for free version? Thanks alot for your attention.