Configuring BW to Report Change Requests and Change Documents

We upgraded to Solution Manager 4.0 on DB2 and need to extract the Change Request and Change Document tables to BW for reporting. We know that there is an internal Transaction Monitor, but we need to also report using BEx Analyzer for users who will not log into Solution Manager.
We found one table CRMD_ORDERADM_H for some Change Request fields, but cannot find the tables for the rest. Does someone know the tables where these fields reside? Thank you.
CHANGE REQUEST
Screen Name Table
Priority
Category
Description CRMD_ORDERADM_H
Sold-to Party
Requester COMT_PARTNER_TO_DISPLAY
Change Manager
Change Advisory Board
Ibase
Product
Subject
External Reference CRMD_SALES
Date
Change Request ID CRMD_ORDERADM_H
Decision Date
Implementation Date
Time of Entry
Change Request Log
Description of Change
Change Request Status
CHANGE DOCUMENT
Screen Name Table
Change Document ID
Status
Description
IT Operator
Implementation Date
Time of Entry
Overview

Similar Messages

Report for Support Message, Change Request and Change in one overview?

Is there a report that shows the relation between the support message, change request and the change in one overview? I am already aware of the Change Management Reporting via SOLAR_EVAL, but this does not show the whole document flow in one overview.
The incident message processors want to have a quick overview of the status of the changes that are created on the basis of the support message.
If there is no report, could you point me in the right direction... Do I have to create a query or are you using BW for service desk/charm reporting?

Hi
chk te sap note
[Note 1466131 - ChaRM Reporting: Performance of data update|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1466131]
jansi

ChaRM Change Request and Change Documents if withdraw

Hi groupies,
my problem is this:
we did copy the standard transaction sdcr etc. to zdcr etc.
If I release a zdcr a new transaction zdmi (normal correction) will be created. I switch into the new transaction type zdmi and withdraw the transaction zdmi. Now I go back into the transaction zdcr. In the Standard SDCR you must release the SDCR again. But in my case the status is still "released". What is the problem? Know anyone the problem?
nico

Hi.
Search for customizing section "Make settings for Change Transaction Types"
Select ZDMI and assign the following:
Assign Action: SET_PREDOC for user status "withdrawn" (check table TJ30 or the corresponding status profile via customizing). It's something like "E0xx"
Specify Status Attributes: Fill in the appropriate information, especially user status ("E0xx" - same as above), transaction type (ZDCR), Statusprofile (status profile used for ZDCR, i.e. ZDCRHEAD) and user status which ZDCR should be reset to (i.e. "E0001 to be approved" or "E0003 rejected")
If you just want to be able to create another ZDMI you could also add an action condition to your ZDCR.
(Tx: SPPFCADM -> CRMD_ORDER -> Condition Configuration)
Hope this helps.
/cheers

Change Request Vs Change Order

Hi,
What is the difference between change request and change orders. When to use Change request and when to use Change order. Both allow impacts on work & financial plans
Thanks
Govind

Change requests are initiated to estimate possible changes to a project. Once approved, a change request can be converted into a change order.
Both can have independent approval work flow.
Also, you can combine multiple change requests into one change order.
For more details, see http://download.oracle.com/docs/cd/E18727_01/doc.121/e13623/T185673T185681.htm
Hope this helps,
Sandeep Gandhi

What is meant by change pointer and change request

hi,
what is meant by change pointer and change request in sap r3
plz can u any one notes or link on this , or if possible briefly tell about this..
i am looking for clear idea on this..
thanks
Ruban

With respect to Dictionary Change pointers means all the changes done to dictionary objects.
All the change logs with respect to tables are stored in CDHDR and CDPOS table
Change Pointers in broad sense are used with respect to IDOC
Change Pointers & Reduction of IDOCs.
Applications, which write change documents, will also try to write change
pointers for ALE operations. These are log entries to remember all modified
data records relevant for ALE.
Following Steps must be followed in case of Change Pointer.
1) Goto Transaction BD60.
Note down the Details of the Message Type for which change pointer has to activate. Details like Function Module, Classification Object, ALE object Type etc.
E.g. ZDEBP3
2) Next step is goto transaction BD53
Click on change button.
First select the segment for which the fields has to modified (either remove or
add ).
It will show the fields in a pop-up window where the user can select, deselect the respective fields.
Save the settings for the Message type. Dont forget to activate the change pointers by clicking Activate Change pointers button on the main screen.
3) Once the activation is done system will reset the settings for the Message type in Change pointers (BD60). Maintained the old settings for the Message type.
Check this FAQ
. Do you really need change pointers?
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61.
2. Do you really need to activate change pointers for this messages type?
If some messages types are no longer to be distributed by change pointers, you can deactivate change pointers for this messages type.
You can deactivate change pointers for the message type
and reactivate them again.
For reduced message types, deactivate the change pointer with the
Reduction tool (transaction BD53).
3. Are there still too many change pointers to be processed?
The change pointers are analyzed with the transaction BD21 or the report RBDMIDOC in ALE and flagged as processed. If the change pointers are created periodically, this report should also run periodically.
4. Are no longer required change pointers reorganized in time?
The report RBDCPCLR (transaction BD22) to reorganize the change pointer should run periodically. Depending on how many change pointers are created or processed, you can schedule the background job hourly, daily or weekly. You should delete all obsolete and processed change pointers. You can also use this report for specified message types.
We come across change pointer technique while dealing with master data distribution thru ALE/IDOCs
When we want to reflect changes made to master data(i.e customer master, vendor master, material master ...) visible to other clients listed in customer distribution model, we follow change pointer technique.
What is customer distribution model?
A customer model depicts various messages (master data, transactional data) exchanged between the systems and establishes a sender and receiver of data
A customer model is always maintained on any system for the entire distributed network of SAP systems, so it must be distributed to various systems in the distributed network.
These r some details regarding change pointer technique which u may find it usefull.............
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master, vendor master & sales orders. changes made to a document are recorded in the change document header table CHDHR, and additional change pointers are written in the BDCP table for changes relevant to ALE. BDCPS table stores the status of changed documents processed or not.
The process for distributing master data using change pointers involves the following steps.
The application writes change documents. SAP maintains change documents for
several objects in the system, such as materials, customers, invoices, and bank data, to provide an audit trail for changes made to an object. A change document object represents a set of tables for which changes are recorded. For example, the change document for the material master is named MATERIAL and it contains the various tables of the material master object, such as MARA and MARC.
When an application transaction makes changes to an object, the application writes change documents, which are stored in the CDHDR and CDPOS tables for each change made to an object.
Tip
Execute transaction SCDO to see a list of change document objects and
their tables.
The SMD (Shared Master Data) tool writes change pointers. When changes are made to an object, the SMD tool checks the ALE settings and consults the ALE distribution model to determine whether a receiver is interested in the object that was changed. If the system finds an appropriate receiver, the system creates change pointers in the BDCP table that point to change documents in the CDHDR table.
The ALE programs analyze change pointers and generate IDocs. SAP provides
standard function modules that read the change pointer table and generate IDocs for the objects that were changed. These programs are designed to ignore multiple changes and create only one IDoc. For example, if a material is changed four times before the function module is invoked, only one IDoc with the latest data from the material master data is created. The function modules are invoked by a standard report, RBDMIDOC. The selection parameters of this report allow you to specify the message type for which change pointers are to be analyzed. Configuration
you must carry out the following configuration steps to enable master data
distribution based on changes to the object.
Step 1: Enable Change Pointers Globally
Transaction: BD61
This option enables the change pointer process globally. Make sure that the flag is checked.
Step 2 :Enable Change Pointers for a Message Type
Transaction: BD50
This setting is required for activating change pointers for a specific message type.
make sure that the Active flag is checked for your message type.
Step 3 :Specify the Fields for Which Change Pointers Are to Be Written
Transaction: BD52
For standard master data objects such as the material, customer, and vendor objects, SAP already provides a list of fields for which change pointers are written. If you are satisfied with the standard set of fields, you can skip this step. If you want to add new fields, you must add entries for the required fields. If you are not interested in IDocs being generated for changes to a particular field, you can remove it from the list. For example, if you do not want to distribute the
material master for changes made to the Catalog Profile (RBNRM) field, you can delete this entry from the table.
Step 4: Changing a Field in the Master Data
Change a field in the master data object for which the change pointer is enabled. For example, if you change the net weight of a material in the material master data, a change pointer is written.
Tip : You can verify a change document and change pointer by viewing entries in
tables CDHDR and BDCP, respectively.
Step 5 :Executing Program RBDMIDOC to Process Change Pointers
Execute program RBDMIDOC to initiate the process of generating an IDoc. On the selection screen, specify the message type. For example, you can specify MATMAS. After you execute the process, it displays the number of entries processed.
Note :
Normally, you schedule this program to run frequently and start IDoc
generation for different message types.
Step 6 : View the idocs in WE02/05

Difference between task request and change request

What is the difference between task request and change request during sap implementation. In general how many tasks will generate during a normal company inmplementation by any functional consultant?

Hi,
Change request and task request are same.But generally change request is generated during newly created objects or reports that are transported and task request is used when u regenerate the change request by modifying that object again and transporting it in new change request.
A particular change request may contain multiple number of task request but that number depends upon number of objects u transfer during generation and transportation.
Pls do reward points if ans is useful.
Regards,
Suhas.

Personnel Change Request And HCMPF.

Hi All,
Please kindly provide me the difference between Personnel Change Request and HCMPF,
Technically, i heard PCR works on java script window and HCMPF on Adobe forms with Webdynpro Environment. (correct me if i'm wrong).
Please update me with other differences, advantages and Disadvantages of the both.
Currently our system is in ECC 5.0, analyzing on implementing PCR or HCMPF.
So, kindly advise me on the difference between these two with its pros and cons.
Thanks a lot for your help..
Regards,
Nathan.

Hi,
PCR (Pers Chnage Request) is also available in interactive Adobe UI from ECC 5.0, however from ECC 6.0 SAP introduced HCMPF that has more flexibility and can handle more complex sceanrios. SAP recommends (documention exist both in IMG and online help) customers to use HCMPF going forward.
There is some good documentation available on SAP service market place if you have access.
Few of the advantages HCMPF are :
Capability to handle attachments
Allows "Save as draft"
Updates EE's master data in the background mode
Employee also can be included in the process
Search iView provides ability for HR to track the status on form
BI content is available to support reporting
Now in EhP4 HCMPF supports processes in PD (Positions, Org units, Jobs etc)
Hope this helps
regards
Sridhar Kandisetty

Difference between Change request and Service request

HI All,
Can any body tell me the actual difference between Change request and Service Request. Does it have any difference ? Or they are same.

Are you referring to the project Specific Terms ??? If yes, then following are the differences.
Change Request - Suppose user is using a Sales Report which displays Revenue by Customer. Now the user wants to see the same by Product as well which is not available in the current report. So the user raises a Change request and the development team works on it to include the same and make it avaialable for the user.
Service Request - These kind of requests are more likely raised when the user needs access to some system (raise service request to Security team), wants to move a transport to the Production box (raise Service request to Basis Team)..etc.

Changing of iBase in Change Requests and Corrections being processed

Good day!
After going SP18 with Solution Manager our iBase component system has gone "mad": number for productive ERP-system has changed several times.
Because of this change, a number of already approved change requests and corrections in processing can't be modified correctly. I can't change their status by regular operations from system document. Multiple correction/ change request change also won't work. And I can't change the iBase component in this documents, because the field is read only.
How can I close all Change Requests and corrections with old iBase component number?
Is there a way to change the iBase number in already approved Change Requests and Corrections, so i can perform operations with this system documents.

Hello Raguraman!
Thank you for your answer.
Anyway I implemented the note to which you refer, and still can't change iBase component in corrections and change requests which are in process. The "iBase/Component" field is still read only and contains components which do not exist anymore.
Do you know how can I change this values?

Restrictions belonging relation between Change Request and Corrections?

Hi all,
In standard change process I only can create one change document (correction) to one change request.
Releation 1:1.
Is there a technical restriction belonging the relation between the change request and the corrections?
Does anyone has experience with a 1:n relation in the change process?
Thanks for your help in advance.
Regards,
Alex
Edited by: Alexander Barth on Mar 16, 2009 11:24 AM

Hi Prakhar,
what you described is a process-restriction. It is not a technical restriction.
E.g.: I have a change belonging BI. Therefore I have to change things in BI and ERP 6.0. Why not using one change request with two corrections? One for BI and one for ERP 6.0.
So you are right if you want to create for that situation two change requests. There is no relation between them. How do you control them?
Administration and documentation is important. But it should be useful.
And I am able to set up more than one corrections to one change request technicaly in SolMan.
But is there a deeper technical restriction inside which raise problems later?
For me it seems that SAP wants that a 1:1 relation is used. But why?
Does anyone have an idea?
Thanks.
Regards,
Alex

Ifference between change request and release request and transport request

what is the difference between change request and release request and transport request and customization request?

Please refer to this link :
http://help.sap.com/saphelp_nw2004s/helpdata/en/57/38e1824eb711d182bf0000e829fbfe/frameset.htm
Regards,
Praveen
Pl reward if helpful

What's the difference between transport request and change request

Hi, I am reading TMS part of TADM12-1 now, and confused about two terms mentioned in this book, transport request and change request.
Is there any difference with them? Please advise. Thanks
James

In the context of course tadm12 transport request = change request

Last changed on and changed by

Hi Experts,
I Have added last changed on and changed by fields on account identification screen of left side panel, its working properly.now my requirement is to move these fields from left side panel to right side panel. now the issue is i cannot find option to make 8 columns to 16 columns.I could able to find the same option on customer default configuration but not on BPCATEGACCOUNT on customer configuration screen.Thanks in Advance.
Regards
Krish

Hi krishna,
In CRM 2007 it is possible to chnage the layout from 8 to 16. Please recheck the configuration tab. Go to edit mode and then you will be able to convert this into 16 one.
Regards,
Harshit

MM02 - Enable options change number, change overview and change documents

I am with the following problem: I enter the transaction MM02, I enter the material 1000765, I select the view "Classification". Later I access the environment option from the menu bar and options for change number, change overwiew and change documents are disabled.
How do I enable these options change number, change overview and change documents?
Regards,
Sérgio Salomã

Hi Sergio,
If we activate the change documents for classification data, then we will be able to see the CHANGE DOCUMENTS for characteristic values through CL20N transaction (CL20N via menu ENVIRONMENT --> Change Documents) or MM02.
For reference please check SAP Note 65124.
For enabling change documents for classification data in SPRO --> Cross-Application Components --> Classification System --> Classes --> Maintain Object Types and Class Types.
In this enter into MARA table entry. Inside that corresponding to the respective CLASS TYPE (say 001) enable the CHANGE DOCS check box in Classifications part (For enabling this please check SAP Note 65124). Then for this CLASS TYPE (say 001) inside the OBJECTS folder, enable the CHANGE DOCS CLASS checkbox also.
Now in MM02 and in CL20N under menu Environment --> Change Documents you can view all the changes done to that characteristic values.
Once the change documents is activated, then we can get the change documents details in CDHDR and CDPOS tables. The OBJECTCLAS may be "CLASSIFY". We can also use the "CLLA_CHANGE_DOC_CLASSIFICATION" function module to fetch the data from these tables.
Hope this helps in solving your issue.
Thanks and Regards,
Harish kumar.

ECH - ECM -- Change leaders and change packages using alternative dates

Our company is an engineer to order business. The Engineering Managers would like to be able to see all the work/changes to objects that occurred for a customer project. So, the use of a change leader and change packages seems to make sense to allow the managers to see all the objects related to a project, but at the same time allow various sub-assemblies be released at different dates.
I was planning to set the change leader with the date of the final erection of the piece of equipment and then use the change packages with alternative dates to release the drawings and sub-assemblies as needed to ensure the appropriate delivery time.
However, even though I can use alternative dates in the change package, I don't get a pop-up window when assigning the change package to the document or BOM for selecting the appropriate date for the object.
Is there a setting I need to enable for this to work?
Thanks!
-J

I didnt understand what your requirement exactly is....
but if you are trying to shift all BOM data from 4.6 C to some higher version of SAP , to my knowledge ...
SAP does not support upward compatibility......

Configuring BW to Report Change Requests and Change Documents

Similar Messages

Maybe you are looking for