Design consideration document for HCM

Hi guru,
Greetings for the day,
I facing a problem here in creation of design consideration document for the HCM project, where any one can help me out by sending a sample HCM design consideration document for my project.
Thanks in advance for you reply.
You can send the document to my mail id of babusaphr @ gmail.com
Regards,
Babu.A

Hi..
It is Client Specific..

Similar Messages

Best Practice & BPP for HCM

Hi,
Can anyone please advise me the link for the following:
Business Process Procedure document for HCM (Best Practice Scenarios).[Module wise PA,OM,TIME,Payroll,Benefits etc]
Config document for HCM (Best Practice Scenarios).[[Module wise PA,OM,TIME,Payroll,Benefits etc]]
Regards
Manish

Hi ,
There are no specific set of steps / practices for batch loading contents to ucm . It would be very much dependent on how many contents does the user have to load to UCM and how well the server is configured in terms of performance .
You can get more details from the following documentation link : http://docs.oracle.com/cd/E21043_01/doc.1111/e10792/c02_settings009.htm
Thanks,
Srinath

Design Document for SAP Workflow

Hi I am looking for a design document for SAP Workflow. A template for design document for the SAP workflow will also be fine

Hi,
Have a look at these good links-
Workflows
http://www.sap-img.com/workflow/sap-workflow.htm
http://www.sapgenie.com/workflow/index.htm
https://sapneth9.wdf.sap.corp/workflow
http://help.sap.com/saphelp_webas620/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
/people/ginger.gatling/blog/2005/12/01/link-workflow-business-objects-to-your-collaboration-tasks
http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm
http://www.sap-press.com/product.cfm?account=&product=H950
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://www.sapgenie.com/workflow/index.htm
For examples on WorkFlow...check the below link..
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
Mark useful answers.
Regards,
Tanuja.

Design and Sizing Document for CUCM 8.x

HI Team,
Guys i need Sizing and Design Document for CUCM 8.x.
There is a new client and we need to do the sizing and design for that client on CUCM 8.x platform.
Request you to assist me with document. I need a document which will give me the sizing and design viewpoints.
I am sure there would so many guys who would have done this already.
Awaiting your reply asap.
Rgds,
JF

Cisco Unified Communications System 8.x SRND
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/uc8x.html
HTHjavaIf this helps, please ratewww.cisco.com/go/pdihelpdesk

Design considerations for mobile version of website

My company has just implemented a new version of our coporate website using Oracle Portal, and ADF. However we do not have comprehensive mobile support but it is required. From my research I've learned we should be using ADF mobile. However, the resources I have found have been geared more at developers and I work as a Business Analyst. Can you point me to online resources (white papers, tutorials etc.) that deal with requirements and design considerations for porting over to a mobile version?
Thanks in advance.

My apologies for lateness in checking this thread.
Here is an article I wrote that might help. Most of the paper is geared toward developer, but the first few sections talks about best practices for mobile browser app in general, not just for iPhone. http://www.oracle.com/technology/pub/articles/huang-iphone.html
You can also check out this link: http://www.orato cle.com/technology/tech/wireless/adf_mobile.html.
As for design consideration, a few rules of thumb:
- First, obviously use ADF Mobile and Trinidad components. We put a lot of effort in adding rendering support for different mobile devices.
- Next, figure out what devices you want to support. Browsers found in smartphones varies greatly, and in consumer/feature phones, the support is even less consistent. In general you should be able create one app/set of screens for all mobile devices, but you should plan on having ability to test it out on different devices.
- Determine what information is really needed by mobile user. Not all information available in desktop application may be applicable for mobile users
- Design your mobile screens based on a few key principals:
- Display data as user needs it, instead of trying to display everything. For example, instead of displaying master-detail data on the same screen, break it out into 2 screens. Master data may be a list, and user would click on a particular piece of data to look at the details of that master record.
- Provide navigation buttons on each screen, and ensure they are easy to get to on a page. For example, using the iPhone paradigm, there is a navigation bar at the top of the page where you can go between views.
- Place command buttons at location where it's easy for user to get to. For example, if you need to allow user to modify a long list of fields, you may want to place save button on top and button of the screen, so user can easily get to it without having to scroll around too much.
- Use style sheets to achieve mobile-platform optimized UI. For example, if you intend to support touch screen devices (iPHone, BB Storm, etc), then style your application so buttons, command links, etc, are big enough so it's easy to get to. For non-touch screen devices, then it's OK to compress the UI, but ensure user can easily flow between controls to get to the functionality they need. For example, using a trackball to scroll to a button.
Thanks,
Joe Huang

How to make design document for OLAP

Hi all,
I want to make design documents for my several cubes.
Does anybody know any template/example (or maybe just Table of Contents) that I can use?
Many thanks,
Albertus
Edited by: Albertus on Oct 13, 2010 2:42 PM
Edited by: Albertus on Oct 13, 2010 2:43 PM

<moved from Adobe Creative Cloud to Creating, Editing & Exporting PDFs - kglad>
people here can better help you.

BW reporting for HCM

Hi All,
we are planning to do HCM reporting in BW and i need the information for the below mentioned points and also if any documents or links are there please do send it to me and your help is highly awarded.
ECC 6.0 compatibility with BW 3.0B
Ø       Is BW 3.0B compatible with ECC 6.0, the platform used for HCM?
Ø       If so, what extractors, objects, etc. are available to support reporting in BW 3.0B?
Ø       What would the sizing requirements be for the current box to support existing BW functionality and new functionality for HCM reporting?
§                                                         BW version compatibility with ECC 6.0
Ø                                                       If 3.0B is not compatible with ECC 6.0, what is the next version of BW needed to support HCM reporting (3.5 or 2004s)?
Ø                                                       What extractors, objects, etc. are available to support reporting in the recommended version?
Ø                                                       What would the sizing requirements be to support the upgrade from BW 3.0B to either 3.5 or 2004staking into consideration the existing functionality in BW 3.0B and the new functionality for HCM reporting?
Thanks in advance,
Jay

Hi,
You can find some of the best practise documents about HCM reporting in BW at:
http://help.sap.com/bp_biv170/html/bw.htm
http://help.sap.com/bp_biv170/html/BW/D26_EN_DE.htm
http://help.sap.com/bp_biv170/html/BW/D28_EN_DE.htm
http://help.sap.com/bp_biv170/html/BW/D40_EN_DE.htm
http://help.sap.com/bp_biv170/html/BW/D42_EN_DE.htm
Hope this helps...

Creating an Architecture Document For a Portal

I have been asked to come up with an Architecture Document for a public facing SharePoint 2010 site. I am familiar with the SharePoint 2010 technologies, however I need a starting point on where and how to start the Architecture document. Is there any Architecture Template Document that exists so that I can use them?

Hi
I cannot share the full and final doc with you but following Index will help you creating the Architecture document from the scratch
1     Document Overview............................................................................................................ 7
1.1     Scope............................................................................................................................... 7
1.2     Audience......................................................................................................................... 7
2     Logical Architecture............................................................................................................ 9
2.1     Overview.......................................................................................................................... 9
2.2     Diagram........................................................................................................................... 9
2.3     Component Description.............................................................................................. 9
3     Physical Architecture....................................................................................................... 11
3.1     Overview....................................................................................................................... 11
3.2     Production Environment.......................................................................................... 11
3.2.1     Diagram................................................................................................................... 11
3.2.2     Component Description....................................................................................... 12
3.2.3     Hardware Requirements...................................................................................... 14
3.2.4     Software Requirements........................................................................................ 14
3.3     Staging Environment................................................................................................. 14
3.3.1     Diagram................................................................................................................... 15
3.3.2     Component Description....................................................................................... 15
3.3.3     Hardware Requirements...................................................................................... 15
3.3.4     Software Requirements........................................................................................ 16
3.4     Development & Test Environment......................................................................... 16
3.4.2     Diagram................................................................................................................... 16
3.4.3     Component Description....................................................................................... 17
3.4.4     Hardware Requirements...................................................................................... 17
3.4.5     Software Requirements........................................................................................ 18
4     Non-Functional Requirements....................................................................................... 19
4.1     Security......................................................................................................................... 19
4.1.1     Requirements......................................................................................................... 19
4.1.2     Authentication........................................................................................................ 19
4.1.3     Authorization.......................................................................................................... 19
4.2     Availability..................................................................................................................... 21
4.2.1     Requirements......................................................................................................... 21
4.2.2     Hardware Redundancy and Failover................................................................. 22
4.2.3     Scaling Logical SharePoint Components......................................................... 22
4.2.4     Disaster Recovery.................................................................................................. 22
4.3     Performance................................................................................................................. 23
4.3.1     Requirements......................................................................................................... 23
4.3.2     Performance & Capacity Expectations.............................................................. 23
4.3.3     Size and Volume Assumptions.......................................................................... 23
4.3.4     Performance Testing Approach.......................................................................... 25
4.3.5     Performance Tuning Approach.......................................................................... 25
4.3.6     Monitoring and Reporting.................................................................................... 26
4.4     Accessibility................................................................................................................. 26
4.4.1     Requirements......................................................................................................... 26
4.4.2     Internal Access....................................................................................................... 26
4.4.3     Remote Access...................................................................................................... 26
4.5     Auditing & Reporting................................................................................................. 27
4.5.1     Requirements......................................................................................................... 27
4.5.2     Approach................................................................................................................. 27
4.5.3     Audit Reports.......................................................................................................... 27
4.5.4     Diagnostic Logging............................................................................................... 28
4.5.5     Portal Usage Reporting........................................................................................ 28
4.6     Exception Handling & Logging............................................................................... 28
4.6.1     Exception Handling............................................................................................... 28
       Application..................................................................................................................... 29
4.6.2     Logging.................................................................................................................... 29
4.7     Caching......................................................................................................................... 29
4.7.1     Disk based caching for BLOBs........................................................................... 29
4.7.2     Client-side caching............................................................................................... 30
4.7.3     Object Caching...................................................................................................... 30
4.8     Maintainability.............................................................................................................. 31
4.8.1     Backup and Restore.............................................................................................. 31
4.8.2     Archiving & Purging.............................................................................................. 32
4.9     Regional Deployment................................................................................................ 32
4.9.1     Conceptual Diagram............................................................................................. 32
4.9.2     Feature Summary.................................................................................................. 33
4.10      Service Management.............................................................................................. 35
5     Search Architecture.......................................................................................................... 36
5.1     Introduction.................................................................................................................. 36
5.2     Key Design Considerations..................................................................................... 37
5.2.1     Distributed Geographical Deployment............................................................... 37
5.2.2     Content Sources.................................................................................................... 37
5.2.3     Availability & Performance................................................................................... 37
5.2.4     Physical Infrastructure.......................................................................................... 38
5.2.5     Search as a Shared Service................................................................................ 38
5.3     Search Architecture in portal..................................................................................... 38
6     Content Deployment Architecture................................................................................ 41
6.1     Introduction.................................................................................................................. 41
6.2     Key Design Considerations..................................................................................... 41
6.2.1     Distributed Geographical Deployment............................................................... 41
6.2.2     Security.................................................................................................................... 42
6.2.3     Availability............................................................................................................... 42
6.2.4     Publishing Frequency.......................................................................................... 42
6.2.5     Physical Infrastructure.......................................................................................... 42
6.2.6     User Contributed Content.................................................................................... 42
6.3     Content Deployment in portal................................................................................... 43
7     References.......................................................................................................................... 45
8     Key Decisions.................................................................................................................... 46
9     Dependencies.................................................................................................................... 47
10      Key Contacts................................................................................................................... 48
11      Appendix A – Active Directory Requirements........................................................ 49
12      Appendix B – Capacity Sizing Model........................................................................ 51
13      Appendix C – Hardware & Software Requirement Summary............................. 53
14      Appendix D – Site Architecture................................................................................... 55
Regards
Deepak Aggarwal

Oracle OSM: MetadataException: There is no entity found in document for...

Some fields was addicted to dictionary and when I deploy the cartridge, the following exception appear. Anyone can help me!
com.mslv.oms.metadatahandler.operation.MetadataException: There is no entity found in document for: element matching the key Tipo_Ordem not found; error code: 108
at com.mslv.oms.metadatahandler.operation.ImportOperation.handleSequenceException(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.processEntity(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.processEntity(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.processEntity(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.doProcess(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.deploy(Unknown Source)
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.c(Unknown Source)
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.a(Unknown Source)
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
<02/01/2013 10h06min27s BRST> <Error> <oms> <BEA-000000> <cartridgemgmt.DeployCartridgeMDB: Cartridge deployment failed:
com.mslv.oms.metadatahandler.operation.MetadataException: There is no entity found in document for: element matching the key Tipo_Ordem not found; error code: 108
at com.mslv.oms.metadatahandler.operation.ImportOperation.handleSequenceException(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.processEntity(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.processEntity(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.processEntity(Unknown Source)
at com.mslv.oms.metadatahandler.operation.ImportOperation.doProcess(Unknown Source)

This indicates OSM has detected a problem with the consistency of the cartridge that is being deployed. Likely this means that Design Studio itself had a problem building the cartridge that went undetected until the cartridge was deployed.
I would suggest you try the following:
1. Shutdown and restart Design Studio.
2. Do a clean-build of your cartridge.
3. Redeploy the cartridge.
If you are redeploying your cartridge over an existing cartridge version, then try changing the cartridge version number, follow steps 1-3 above and see if that makes any difference.
If the above doesn't resolve your problem, then suggest you contact Oracle Support.
Regards,
Brian.

Export and import change document for user master data

Dear Gurus,
I have two queries on change document for user master data:
1. Are there any approaches to export and import change document for user master data?
We often do system copy from PRD to QAS for UAT and troubleshooting. Before system copy we export the user master data from QAS and then import after the copy process. We would like to keep the change document for user master data on QAS from being refreshed from PRD for security reason.
2. Change document for Role change in QAS
When the role is created or modified in DEV and then transported to QAS, the role change document doen't include this change log. The role change document in QAS only records those role changes directly made in QAS.
Could you advise this is by SAP design or are there any approaches to record this transported role change in the role change document in QAS?
Thanks
YBY

1. Perhaps you want to consider a system copy to a "virtual system" for UAT?
2. Changes in QAS (as with PROD as well) will give you the delta. They should ideally be clean... You need to check the source system.
Another option is to generate the profiles in the target system. But for that your config has to be sqeaky clean and in sync, including very well maintained and sync'ed Su24 data.
Cheers,
Julius

Need a document for field exit....urgent

Can any one please send a document for field exit or have a simple document on how to work on a field exit with screen shots. pls send it ...its urgent
Thanks and regards
Nandha kumar R

Hi,
A field exit is a type of user exit.
A user exit is a hook where you can inject your own add-on functionality or behavior to SAPs standard business applications without having to modify the original applications.
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
Note that you can write any code that satisfy your needs.                                                     ****
But in this case, this was wrote as a sample code for reference sake.                                    ****
And you can test it.                                                                                ****
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.
Field exits (SMOD/CMOD) Questions and Answers
1. Field exit was created with CMOD, but is not processed when calling the screen.
- Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
- Set profile parameter abap/fieldexit to YES and restart the system.
- After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
- Do not work on different application servers since there may be some delay before the field exit is activated.
- The profile parameter must be set on all or none of the application servers.
- If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen
      number (take care with subscreens).
- Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit use the name of the data element and not the field name.
- After transport, field exits are marked as active but will not be processed.
   Tip: First try deactivating the field exit once more and then afterwards, activate it again.
2. How is performance affected by setting abap/fieldexit?
- If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an
update. The user should not notice any difference because screen generation is very fast.
3. Can you read the contents of other screen fields in the field exit?
- In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them
available to other field exits. Note here that field exits are always called and not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
4. How does the field exit behave on step loop fields ?
- After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system
variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
5. Can field exits be debugged ?
- No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.
6. What can you do if the field contents are no longer transported to to ABAP/4.
- Check whether a value is assigned to the field OUTPUT.
7. When is the field exit called if a conversion exit is attached to the
   data element ?
- The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the
ABAP/4 program also receives it.
8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@)
- This is an error in the kernel which no longer occurs as of 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
9. Field exit is not visible in CMOD, although created.
- If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_. This
function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix,
the data element is not displayed in CMOD.
10. Field exit is not executed although it is active.
- Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an
extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the         application by LOOP AT SCREEN.
This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is
invisible.
- Field exits can only be executed for fields that are directly related tothe dictionary. If the relation is indirect, i.e. via an       ABAP declaration ( LIKE ), no field exit can be executed.
11. Field exits on check buttons do not work
- Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on
them.
12. Field exits do not work on selection screens
SAP Field Exits
From 4.6c onwards, Field exits will no more be supported by SAP. They removed the function of field exit but they had given lot of flexibility through userexit.
However, if you still required it, here is how to activate it :-
First called up transaction CMOD.
Then called up transaction PRFB.
or
Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank). If required, new field exits can be created using program RSMODPRF (see the program documentation).
REFER THIS LINK ALSO.
defining screen fields using FIELD-SYMBOL
Thanks,
Shankar

Can anyone give me some documents for data cluster

Hi,
can anyone give me some documents for data cluster?
ths!
regards!

Hi ,
The following is a documentation on the Data Cluster:
Data clusters are specific to ABAP. Although it is possible to read a cluster database using SQL statements, only ABAP can interpret the structure of the data cluster.
You can store data clusters in special databases in the ABAP Dictionary. These are called ABAP cluster databases, and have a prescribed structure:
Cluster Databases ( I have explained the cluster databse below )
This method allows you to store complex data objects with deep structures in a single step, without having to adjust them to conform to the flat structure of a relational database. Your data objects are then available systemwide to every user. To read these objects from the database successfully, you must know their data types.
You can use cluster databases to store the results of analyses of data from the relational database. For example, if you want to create a list of your customers with the highest revenue, or an address list from the personnel data of all of your branches, you can write ABAP programs to generate the list and store it as a data cluster. To update the data cluster, you can schedule the program to run periodically as a background job. You can then write other programs that read from the data cluster and work with the results. This method can considerable reduce the response time of your system, since it means that you do not have to access the distributed data in the relational database tables each time you want to look at your list.
Cluster Database :
 Cluster databases are special relational databases in the ABAP Dictionary that you can use to store data clusters. Their line structure is divided into a standard section, containing several fields, and one large field for the data cluster.
Creating a Directory of a Data Cluster
To create a directory of a data cluster from an ABAP cluster database, use the following statement:
Syntax
IMPORT DIRECTORY INTO <dirtab>
 FROM DATABASE <dbtab>(<ar>)
 [CLIENT <cli>] ID <key>.
This creates a directory of the data objects belonging to a data cluster in the database <dbtab> in the internal table <dirtab>. You must declare <dbtab> using a TABLES statement.
To save a data cluster in a database, use the EXPORT TO DATABASE statement .
For <ar>, enter the two-character area ID for the cluster in the database. The name <key> identifies the data in the database. Its maximum length depends on the length of the name field in <dbtab>. The CLIENT <cli> option allows you to disable the automatic client handling of a client-specific cluster database, and specify the client yourself. The addition must always come directly after the name of the database.
The IMPORT statement also reads the contents of the user fields from the database table.
If the system is able to create a directory, SY-SUBRC is set to 0, otherwise to 4.
The internal table <dirtab> must have the ABAP Dictionary structure CDIR.
******** Sample Program illustrating the data cluster .
PROGRAM Zdata_cluster.
TABLES INDX.
******to save data objects in cluster databases
DATA: BEGIN OF ITAB OCCURS 100,
 COL1 TYPE I,
 COL2 TYPE I,
 END OF ITAB.
DO 3000 TIMES.
ITAB-COL1 = SY-INDEX.
ITAB-COL2 = SY-INDEX ** 2.
APPEND ITAB.
ENDDO.
INDX-AEDAT = SY-DATUM.
INDX-USERA = SY-UNAME.
INDX-PGMID = SY-REPID.
EXPORT ITAB TO DATABASE INDX(HK) ID 'Table'.
WRITE: ' SRTF2',
 AT 20 'AEDAT',
 AT 35 'USERA',
 AT 50 'PGMID'.
ULINE.
SELECT * FROM INDX WHERE RELID = 'HK'
 AND SRTFD = 'Table'.
WRITE: / INDX-SRTF2 UNDER 'SRTF2',
 INDX-AEDAT UNDER 'AEDAT',
 INDX-USERA UNDER 'USERA',
 INDX-PGMID UNDER 'PGMID'.
ENDSELECT.
****To create a directory of a data cluster from an ABAP ****cluster database
DATA DIRTAB LIKE CDIR OCCURS 10 WITH HEADER LINE.
IMPORT DIRECTORY INTO DIRTAB FROM DATABASE
 INDX(HK) ID 'Table'.
IF SY-SUBRC = 0.
WRITE: / 'AEDAT:', INDX-AEDAT,
 / 'USERA:', INDX-USERA,
 / 'PGMID:', INDX-PGMID.
WRITE / 'Directory:'.
LOOP AT DIRTAB.
 WRITE: / DIRTAB-NAME, DIRTAB-OTYPE, DIRTAB-FTYPE,
 DIRTAB-TFILL, DIRTAB-FLENG.
ENDLOOP.
ELSE.
WRITE 'Not found'.
ENDIF.
*******run this program and see the result.
Hope this documentation will give you an idea of data cluster.
if useful, do reward with the points.
Regards,
Kunal.

Upload Document for report in WAD/Bex

Dear All,
Any clue on attaching/uploading the document for a report in Web Application designer/BEx with BW 3.5 ?
Can't ask an end-user to go to RSA1 => Document
Please share your expertise / prior experience on same.
Thanks in advance.
Regard,
Pal.

Hello Pal,
this is standard functionality.
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/22/14163be70a9839e10000000a114084/frameset.htm">Create/Upload Documents</a>
Regards
Marc
SAP NetWeaver RIG

Set of document for approval.

I have to send set of documents for approval to my client which are PDF format. For example :-
1) Project A - Total 5 Documents (PDF format)for Approval
2) Project B - Total 6 Documents (PDF format) for Approval
Like this daily I have to send 6 o 8 projects document to my client for approval in one set. I think I can use Document set for approval but not sure. Please advice.

Thanks Redecca,
I've created the document set and its working fine. Only I'm facing issue with Permission.
I've created Document Set in Document Library in SharePoint 2013. Here for this document set I've created
OOTB workflow from SharePoint Ribbon. So here User A will upload the document and User B will review put comment and approve or reject.
I've admin access so in the Document Library Setting "Permissions for this document library " I
clicked on "Inherit the Permission" and added these users A & B with Design access.
Now user A is able to login and upload the files in document set but to create or use the Document Set which
I've created he is getting error "Sorry, you don't have access to this page".
Now here I want to give access to user A and B only for the Document Library so they can access/use the Document
Set which I've created, Upload the Document and user B can approve it. Also here in Left Navigation I want to show user A & B "Task" option which is also not showing to view the "Approval Status".
Before your post I posted this issue on below link as its look like different request. Could you please have a look and advice please.
https://social.msdn.microsoft.com/Forums/en-US/0d460adb-c914-45d6-a637-61fc3fea5595/how-to-provide-access-only-for-document-set-to-upload-and-approve-the-documents?forum=sharepointadmin

PDF or MS Word Document for Query7.0 ?

Hello,
How Can I realize this...
PDF or MS Word Document for Query7.0 ?
THANKS

Hi skinny_Will,
The coded UI test would have some limitations for the Word/office controls by design.
To really read and compare the text value, I'm afraid that we would use certain extension tool/add-in and custom code for it.
Please check the Visual Studio Coded UI for Word Add-In.
Reference:
https://social.msdn.microsoft.com/Forums/en-US/b12f1cf8-322f-4b3a-ad8f-011065d91356/comparing-word-documents-in-coded-ui?forum=vstest
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Design consideration document for HCM

Similar Messages

Maybe you are looking for