Where the feedback content is stored

hi,
if a user is giving feedback for a document. where the content of the feedback will be stored in KM.
can anyone give the path for that.
all helps will be appriciated
Regards,
Shanthakumar.

There is no place in Portal to see the FeedBack content .We provide a folder path for the Discussion/Discussion Group/Km Discussion iVIew in iVIew property "path to root folder " .This is for reference .Suppose we can provide "/documents/discussions/New Discussion" as the folder path where the posts and feedback are supposed to get stored .However the content is actually in stored in the database and not seen in Portal . As correctly provided in the previous reply,study the article to see where it is actually stored . I hope this suffices your answer .
Edited by: Arijit Bhattacharya on Apr 30, 2008 10:55 AM

Similar Messages

Where the Forum informations are stored?

Hi all,
i need to know, where the forum contents are stored in the KM?
regards,
Kathiresan R

Hi,
Did you press the Advanced mode when you are under repository manager?
If the forums repository is not present, then you did not install Forums Application.
Check this:
http://help.sap.com/saphelp_nw70/helpdata/EN/46/9ca6594e903ef4e10000000a1553f7/frameset.htm
Regards,
Praveen Gudapati

Where the posted threads are stored

Hi All,
Where the posted threads are stored. In which repository i is storing.
Regards
Krishnamurthy K

Hi,
You can read the documentation about [Content Management Configuration|http://help.sap.com/saphelp_nw70/helpdata/EN/69/d96b7aa84611d5993600508b6b8b11/frameset.htm] , where you can find a lot of information about [Repository Managers |http://help.sap.com/saphelp_nw70/helpdata/EN/69/d96b7da84611d5993600508b6b8b11/frameset.htm] .
Repositories are used for storing and/or retrieving content and metadata.
The KM standard configuration uses several internal repositories that are controlled by CM. They are used for storing and staging various content and metadata and for navigating in this data. These repositories are preconfigured and preactivated in the KM standard configuration. You do not normally need to modify their configuration.
In addition to the aforementioned internal repositories, you can integrate additional external repositories into CM, such as a WebDAV or file system repository. You can establish a connection to these repositories by configuring appropriate repository managers.
Regards,
Lubi
*Hope it will be helpful for you.

Table where the Delivery date is stored in Confirmation tab on Me23n

Hello ABAB Gurus,
Can anyone give me the table name where the Delivery date is stored in Confirmation tab in Item in ME23n.
If anyone is aware of it then please let me know .
Sagar

Hi,
Check the table EKES and field name is EINDT..
Thanks,
Naren

Changing where the sent messages are stored

Hi, I was wondering is there any way you can change where the sent messages are stored. I have switched from a few programs.. and there is a 'sent' folder and ' sent messages' folder on my folder list in addition to that of what mail is putting them in. I just want one folder.

Sounds like you are accessing an IMAP type account.
If so, is this the only email account and account type you are accessing with the Mail.app?

How to find where the screen field is stored in table

Hi all,
How to find where the screen field is stored in the table .
for some transactions if i press F1 on the field and after checking for the technical help.
I can only find the struture for the screen field, but whereas i need table name for it.
Can anybody help me how to find the table name where the field is stored.
Regards,
Madhavi

Hi,
Just hitting a F1 on screen field and getting structure name will not help in getting table name.
First you need to know the flow of data in the reqd module, which will help you know all the tables in that module with there most of the fields with the data flow, now you need to work on your own to figure out that in which actual tables that value is stored.
Hope this helps you.
Regards,
Tarun

Tables where the XI Data is stored

Dear all,
Can you let me know all the tables in XI in which the data is stored.
Like where the asyncronous messages are stored(which table and what is the abap program name which gets executed to store the message id's etc in the table).
Pl list out all the tables,programs related to XI.
Also pls let me know where IDOC,Proxy,RFC related tables programs.
my mailid is srinivas5780@gmailcom

Hi,
Please go through the below weblog:
/people/gourav.khare2/blog/2007/12/12/interesting-abap-tables-in-xi-150-part-i
Look at the below thread for SXMB_MONI tables and Function module:
In Which Database Table the Messages are Stored in XI
Message Monitoring --> corresponding tables?
For IDOC:
tables are EDIDC control record table and EDIDD-data record table.
Thnx
Chirag

Where the Report info is stored.

Can anyone tell me where the reports logs are stored. I am asking for those which are displayed in showjobs comand.
I am not talking about those which are stored in log folder.

Hello,
The information displayed by the showjobs command is stored in memory and in the "persist file"
http://download-uk.oracle.com/docs/cd/B14099_17/bi.1012/b14048/pbr_conf.htm#i1007034
Regards

Where the session id is stored in server/JVM in java

hi all,
please tell me where the session id is stored in server or JVM in java.
regards
Mohan kumar

Which session ID are your taking about?
Are you doing J2EE development?
-Alexis

Anybody know where the default templates are stored?

I'd like to access the location where the default templates are stored. I've checked in: "Macintosh HD/Library/Application Support/Logic" but did not find anything.
I see that user templates are in: "Macintosh HD/Users/PROFILE/Library/Application Support/Logic/Project Templates"
Thanks in advance!
Rydah

alienimplant wrote:
The assigned solution to this problem is false. The answer is that they are stored here:
/Users/[username]/Music/Audio Music Apps/Project Templates
That is not correct.
User Project templates are stored in the location you stated but the Default Project templates, which is what the OP asked about, are stored within the app as Blueberry stated....
Note the path I highlighted......

Where should itunes content be stored?

on the operations drive or a separate data drive? I routinely run both Adobe Photoshop and iTunes, and my impresseion is that iTunes seems to work more smoothly when songs and video are stored on the operations drive, but Photoshop runs more smoothly when the iTunes content is stored on a separate data drive? Also, keeping iTunes content on the operations drive seems to reduce the number of issues related to updating itunes and syncing itunes-dependent playlists and the like.
I've got a new PC with clean drives, and I'd like to get this right the first time.

If the boot drive is used for things like scratch drives, it can slow the system down (a bit or a lot) because the OS uses the boot drive for swap files and such.
Do you mean to imply that when itunes accesses content on the 'operations' drive, it does not compromise the performance of other, open applications that are using the c drive for on-going programming operations?
iTunes does read/write from the HD all the time but it should not noticeably slow down anything.

Table where the VAT value is stored

Hello!
Could any one tell me where the VAT value is stored for the particular matnr. I am searching the table KONH- KSCHL where the value is stored at JVAT. but there was 40% of the matnr only having JVAT value.I am taking the price from KONH.So from where i have to take the VAT value.
-M.Suba

For excise details you will have to use J_1iexchdr, J_1iexcdtl,
For Tax related data use KONV
Thanks & Regards
JP

Where the interrupt routine vectors stored in if I disable the AXI interrupt controller fast interrupt option?

In an IPI system, I have several IPs connected their interrupt output with AXI interrupt controller. In the software part, I can create several interrupt callback functions for different interrupts. I wonder Where the interrupt routine vectors stored in if I disable the AXI interrupt controller fast interrupt option? Are they stored inside the specific IP?
E.g.: if I have an VDMA and setup its callback function for general and error, then the callback function starting addresses are stored inside VDMA registers?
Thank you.

>> The address of the ISR is stored in this table", so is the table stored inside the interrupt controller on inside ARM cpu? But when I used microblaze, it seems there is no interrupt controller inside the microblaze
No, that table is in a memory which implements the processor's address space. If you use MB, you can add an interrupt controller to it but that's not relevant. Interrupt controllers cause processors to jump to a fixed location in their address space. At this point in time there are two main options: either some program has registered to respond to this interrupt or not. In the latter case, the OS, bare-metal app etc takes a decision on what to do: ignore the interrupt, crash, just turn off that interrupt and return etc. If an interrupt has been registered to respond to that interrupt, the address of the interrupt service routine is in table belonging to the OS, bare-metal app etc so the code at the fixed offset jumps to the address inside that table ie it jumps to the ISR.

Where the task payload is stored in the dehydration store

Hi All,
I wanted to get the taskPayload from the BPEL dehydration store. I have gone thru the WFTASK table but I didn't see any column which conains the taskpaylod.
I need this payload to do the following..
- Get the taskPayload
- Modify it so that I can get modifications in the BPEL process when I submitted the task back to BPEL.
Can the above be done from the bpel dehydration store? If yes please help me in finding the exact table for this task payload.
If not guide me how can I access and modify the task payload.
Thank you.

Payloads are generally stored as BLOBS. Here is a definition of all the tables. You can make the payload editable withing the human task if required, so you don't need to go to the DB.
Main tables used by the BPEL engine
cube_instance – stores instance metadata, eg. instance creation date, current state, title, process identifier
cube_scope – stores the scope data for an instance … all the variables declared in the bpel flow are stored here, as well as some internal objects to help route logic throughout the flow.
work_item – stores activities created by an instance … all BPEL activities in a flow will have a work_item created for it. This work item row contains meta data for the activity … current state, label, expiration date (used by wait activities) … when the engine needs to be restarted and instances recovered, pending flows are resumed by inspecting their unfinished work items.
document - stores large XML variables. If a variable gets to be larger than a specific size (configurable via the largeDocumentThreshold property via the domain configuration page) then the variable is stored in this table to alleviate loading/saving time from the cube_scope table.
audit_trail - stores the audit trail for instances. The audit trail viewed from the console is modelled from an XML document. As the instance is worked on, each activity writes out events to the audit trail as XML which is compressed and stored in a raw column. Querying the audit trail via the API/console will join the raw columns together and uncompress the contents into a single XML document.
audit_details - audit details can be logged via the api … by default activities such as assign log the variables as audit details (this behavior can be set via the auditLevel property on the domain configuration page). Details are separated from the audit trail because they tend to be very large in size … if the user wishes to view a detail they click a link from the audit trail page and load the detail separately. There is a threshold value for details too … if the size of a detail is larger than a specific value (see auditDetailThreshold) then it is place in this table, otherwise it is merged into the audit trail row.
dlv_message – callback messages are stored here. All non-invocation messages are saved here upon receipt. The delivery layer will then attempt to correlate the message with the receiving instance. This table only stores the metadata for a message. (eg. current state, process identifier, receive date).
dlv_message_bin – stores the payload of a callback message. The metadata of a callback message is kept in the dlv_message table, this table only stores the payload as a blob. This separation allows the metadata to change frequently without being impacted by the size of the payload (which is stored here and never modified).
dlv_subscription – stores delivery subscriptions for an instance. Whenever an instance expects a message from a partner (eg. receive, onMessage) a subscription is written out for that specific receive activity. Once a delivery message is received the delivery layer attempts to correlate the message with the intended subscription.
invoke_message – stores invocation messages, messages which will result in the creation of a instance. This table only stores the metadata for an invocation message (eg. current state, process identifier, receive date).
invoke_message_bin – stores the payload of an invocation message. Serves the same purpose the dlv_message_bin table does for dlv_message.
task – stores tasks created for an instance. The TaskManager process keeps its current state in this table. Upon calling invoking the TaskManager process, a task object is created, with a title, assignee, status, expiration date, etc… When updates are made to the TaskManager instance via the console the underlying task object in the db is changed.
schema_md – (just added via patch delivered to Veerle) contains metadata about columns defined in the orabpel schema. Use case driving this feature was how to change the size of a custom_key column for a cube_instance row? Changing the db schema was simple but the engine code assumed a certain length and truncated values to match that length to avoid a db error being thrown. Now, column lengths are defined in this table instead of being specified in the code. To change a column length, change the column definition in the table, then change the value specified in this table, then restart the server.
Column-by-column description:
table ci_id_range
- next_range (integer) – instance ids in the system are allocated on a block basis … once all the ids from a block have been allocated, another block is fetched, next_range specifies the start of the next block.
table cube_instance
- cikey (integer) – primary key … foreign key for other tables
- domain_ref (smallint) – domain identifier is encoded as a integer to save space, can be resolved by joining with domain.domain_ref.
- process_id (varchar) – process id
- revision_tag (varchar) – revision tag
- creation_date (date)
- creator (varchar) – user who created instance … currently not used
- modify_date (date) – date instance was last modified
- modifier (varchar) – user who last modified instance … currently not used
- state (integer) – current state of instance, see com.oracle.bpel.client.IInstanceConstants for values
- priority (integer) – current instance priority (user specified, has no impact on engine)
- title (varchar) – current instance title (user specified, no engine impact)
- status (varchar) – current status (user specified)
- stage (varchar) – current stage (user specified)
- conversation_id (varchar) – extra identifier associated with instance, eg. if passed in via WS-Addressing or user specified custom key.
- root_id (varchar) – the conversation id of the instance at the top of the invocation tree. Suppose A -> B -> C, root( B ) = A, root( C ) = A, parent( B ) = A, parent( C ) = B. This instance, instance at the top of the tree will not have this set.
- parent_id (varchar) – the conversation id of the parent instance that created this instance, instance at the top of the tree will not have this set.
- scope_revision (integer) – internal checksum of scope bytes … used to keep caches in sync
- scope_csize (integer) – compressed size of instance scope in bytes
- scope_usize (integer) – uncompressed size of instance scope in bytes
- process_guid (varchar) – unique identifier for the process this instance belongs to … if changes need to be made for all instances of a process, this column is used to query (eg. stale process).
- process_type (integer) – internal
- metadata (varchar) – user specified
table cube_scope
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- modify_date (date) – date scope last modified
- scope_bin (blob) – scope bytes
table work_item
- cikey (integer) – foreign key
- node_id (varchar) – part of work item composite key, identifier for bpel activity that this work item created for
- scope_id (varchar) – part of work item composite key, identifier for internal scope that this work item created for (note this is not the scope declared in bpel, the engine has an internal scope tree that it creates for each instance, bpel scopes will map to an internal scope but there will be other internal scopes that have no mapping to the bpel definition).
- count_id (integer) – part of work item composite key, used to distinguish between work items created from same activity in the same scope.
- domain_ref (integer) – domain identifier
- creation_date (date)
- creator (varchar) – user who created work item … currently not used
- modify_date (date) – date work item was last modified
- modifier (varchar) – user who last modified work item … currently not used
- state (integer) – current state of work item, see com.oracle.bpel.client.IActivityConstants for values
- transition (integer) – internal use, used by engine for routing logic
- exception (integer) – no longer used
- exp_date (date) – expiration date for this work item; wait, onAlarm activities are implemented as expiration timers.
- exp_flag (integer) – set if a work item has been called back by the expiration agent (ie. expired).
- priority (integer) – priority of work item, user specified, no engine impact
- label (varchar) – current label (user specified, no engine impact)
- custom_id (varchar) – custom identifier (user specified, no engine impact)
- comments (varchar) – comment field (user specified, no engine impact)
- reference_id (varchar) -
- idempotent_flag (integer) – internal use
- process_guid (varchar) – unique identifier for the process this work item belongs to … if changes need to be made for all instances of a process, this column is used to query (eg. stale process).
table document
- dockey (varchar) – primary key for document
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- classname (varchar) – no longer used
- bin_csize (integer) – compressed size of document in bytes
- bin_usize (integer) – uncompressed size of document in bytes
- bin (blob) – document bytes
- modify_date (date) – date document was last modified
table audit_trail
- cikey (integer) – foreign key
- domain_ref – domain identifier
- count_id (integer) – many audit trail entries may be made for each instance, this column is incremented for each entry per instance.
- block (integer) – when the instance is dehydrated, the batched audit trail entries up to that point are written out … this block ties together all rows written out at one time.
- block_csize (integer) – compressed size of block in bytes
- block_usize (integer) – uncompressed size of block in bytes
- log (raw) – block bytes
table audit_details
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- detail_id (integer) – part of composite key, means of identifying particular detail from the audit trail
- bin_csize (integer) – compressed size of detail in bytes
- bin_usize (integer) – uncompressed size of detail in bytes
- bin (blob) – detail bytes
table dlv_message
- conv_id (varchar) – conversation id (correlation id) for the message…this value is used to correlate the message to the subscription.
- conv_type (integer) – internal use
- message_guid (varchar) – unique identifier for the message…each message received by the engine is tagged with a message guid.
- domain_ref (integer) – domain identifier
- process_id (varchar) – identifier for process to deliver the message to
- revision_tag (varchar) – identifier for process revision
- operation_name (varchar) – operation name for callback port.
- receive_date (date) – date message was received by engine
- state (integer) – current state of message … see com.oracle.bpel.client.IDeliveryConstants for values
- res_process_guid (varchar) – after the matching subscription is found, the process guid for the subscription is written out here. – res_subscriber (varchar) – identifier for matching subscription once found.
table dlv_message_bin
- message_guid (varchar) – unique identifier for message
- domain_ref (integer) – domain identifier
- bin_csize (integer) – compressed size of delivery message payload in bytes
- bin_usize (integer) – uncompressed size of delivery message payload in bytes
- bin (blob) – delivery message payload
table dlv_subscription
- conv_id (varchar) – conversation id for subscription, used to help correlate received delivery messages.
- conv_type (integer) – internal use
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- process_id (varchar) – process identifier for instance
- revision_tag (varchar) – revision tag for process
- process_guid (varchar) – guid for process this subscription belongs to
- operation_name (varchar) – operation name for subscription (receive, onMessage operation name).
- subscriber_id (varchar) – the work item composite key that this subscription is positioned at (ie. the key for the receive, onMessage work item).
- service_name (varchar) – internal use
- subscription_date (date) – date subscription was created
- state (integer) – current state of subscription … see com.oracle.bpel.client.IDeliveryConstants for values
- properties (varchar) – additional property settings for subscription
table invoke_message
- conv_id (varchar) – conversation id for message, passed into system so callbacks can correlate properly.
- message_guid (varchar) – unique identifier for message, generated when invocation message is received by engine.
- domain_ref (integer) – domain identifier
- process_id (varchar) – identifier for process to deliver the message to
- revision_tag (varchar) – revision tag for process
- operation_name (varchar) – operation name for receive activity
- receive_date (date) – date invocation message was received by engine
- state – current state of invocation message, see com.oracle.bpel.client.IDeliveryConstants for values
- priority (integer) – priority for invocation message, this value will be used by the engine dispatching layer to rank messages according to importance … lower values mean higher priority … messages with higher priority are dispatched to threads faster than messages with lower values.
- properties (varchar) – additional property settings for message
table invoke_message_bin
- message_guid (varchar) – unique identifier for message
- domain_ref (integer) – domain identifier
- bin_csize (integer) – compressed size of invocation message payload in bytes
- bin_usize (integer) – uncompressed size of invocation message payload in bytes
- bin (blob) – invocation message bytes
table task
- domain_ref (integer) – domain identifier
- conversation_id (varchar) – conversation id for task instance … allows task instance to callback to client
- title (varchar) – current title for task, user specified
- creation_date (date) – date task was created
- creator (varchar) – user who created task
- modify_date (date) – date task was last modified
- modifier (varchar) – user who last modified task
- assignee (varchar) – current assignee of task, user specified, no engine impact
- status (varchar) – current status, user specified, no engine impact
- expired (integer) – flag is set if task has expired
- exp_date (date) – expiration date for task, expiration actually takes place on work item in TaskManaged instance, upon expiration task row is updated
- priority (integer) – current task priority, user specified, no engine impact
- template (varchar) – not used
- custom_key (varchar) – user specified custom key
- conclusion (varchar) – user specified conclusion, no engine impact

Where the word document is stored.

Hi Friends,
Using web dynpro they stored word document in SAP. where/how is it stored sap. and how is it retrive via SAP.
Thanks & Regards,
Vallamuthu.M

If you use ST05 to implement at trace on your userid, and then save a document through the web dynpro, you should be able to see where in the database the document is being stored.
If you drill down to the underlying source, you should be able to find the area of code performing the save.

Where the feedback content is stored

Similar Messages

Maybe you are looking for