Skip to Content
author's profile photo Former Member
Former Member

Change Documents

Hi Friends,

Could any body tell me Clearly What are change Documents and how to track changes in change documents ? How to activate the change documents ?

Thank you,

Ayyappa

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Posted on Feb 01, 2008 at 04:00 AM

    Hi Ayyapa

    Business data objects are changed frequently. We recommend that you log these changes for objects that are critical or susceptible to audits. You may find it helpful, and sometimes necessary, to be able to trace or reconstruct such changes later, for example for investigating or auditing purposes. SAP Systems log changes to business data objects in change documents.

    SAP Systems do not automatically use change documents for business objects. You must activate the process yourself.

    To activate a change document for an object, perform the following steps:

    ...

    1. Create the change document. (Use the transaction SCD0.)

    2. Activate the change document for the object. (Use data element maintenance: transaction SE11.)

    3. Generate an update for the object. (Use the transaction SCD0.)

    4. Insert the appropriate calls in the corresponding programs.

    To view change documents for an object, also use the transaction SCD0.

    check the link:

    http://help.sap.com/saphelp_nw2004s/helpdata/en/2a/fa015b493111d182b70000e829fbfe/content.htm

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2008 at 04:02 AM

    Hi,

    For changes to a commercial object to be able to be logged in a change document, the object must have been defined in the system as a change document object. A change document object definition contains the tables which represent a commercial object in the system. The definition can also specify whether the deletion of individual fields is to be documented. If a table contains fields whose values refer to units and currency fields, the associated table, containing the units and currencies, can also be specified.

    It must be specified for each table, whether a commercial object contains only one (single case) or several (multiple case) records. For example, an order contains an order header and several order items. Normally one record for the order header and several records for the order items are passed to the change document creation when an order is changed.

    The name under which a change document object is created is an object class.

    The object class BANF was defined for the change document object "Purchase requisition", which consists of the tables EBAN (purchase requisition) and EBKN (purchase requisition account assignment).

    Changes to this commercial object can then be saved in the system under the object values of this change document object, i.e. the object ID and a change document number. The object ID is the key to the object value, i.e. all records which are defined as belonging to a given change document object.

    All changes to a commercial object constitute an object value under this key. This is for example the order number for orders or the number range object name for number range objects. All changes to a given order or to a given number range object can be accessed in this way.

    The object value BANF with the object ID "3000000000" consists of the records of the tables EBAN and EBKN with the order number "3000000000".

    If changes are not yet to be made, but are planned, they can be logged as planned changes. A planned date for the changes can be specified. The planned changes can be analyzed and copied into the tables. You must program the copy yourself.

    All logging functions are supported by SAP function modules. The application development must contain certain INCLUDE programs. Old and new status are passed to the change document creation. The included function modules determine the changes for all table fields which are flagged as being change-relevant in the Dictionary.

    Change document

    A change document logs changes to a commercial object. The document is created independently of the actual database change. The change document structure is as follows:

    Change document header

    The header data of the change to an object ID in a particular object class are stored in the change document header. The change document number is automatically issued.

    Change document item

    The change document item contains the old and new values of a field for a particular change, and a change flag.

    The change flag can take the following values:

    U(pdate)

    Changed data. (Log entry for each changed field which was flagged in the Dictionary as "change document-relevant")

    I(nsert)

    Data inserted.

    Changes: Log entry for the whole table record

    Planned changes: Log entry for each table record field

    D(elete)

    Data were deleted (log entry for the whole table record)

    I(ndividual field documentation)

    Delete a table record with field documentation

    1 log entry per field of the deleted table entry, the deleted text is saved

    Change document number

    The change document number is issued when a change is logged, i.e. when the change document header is created by the change document creation function module (function group SCD0).

    The change number is not the same as the change document number. The change document number is issued automatically by the function group SCD0 function modules when a change document is created for a change document object. The change number is issued by the user when changes are planned. The same change number can be used for various change document objects.

    Internal processing

    When the object-specific update is called, the object-specific change document creation is called. The object-specific change document header is written with a change document number. The Dictionary is searched for which fields are to be logged for each table in the object definition. The log records for these fields are then created as change document items according to the object definition.

    Procedure

    http://help.sap.com/saphelp_nw2004s/helpdata/en/2a/fa0182493111d182b70000e829fbfe/frameset.htm

    Regards,

    Renjith Michael.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2008 at 04:03 AM

    Hi,

    Check out the below link, here you will get all the information about Change Documents.

    http://help.sap.com/saphelp_47x200/helpdata/en/2a/fa015b493111d182b70000e829fbfe/frameset.htm

    Regards,

    Chandru

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2008 at 04:05 AM

    Check this link. U can find all the information abt change documents

    http://help.sap.com/saphelp_47x200/helpdata/en/2a/fa015b493111d182b70000e829fbfe/frameset.htm

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2008 at 04:15 AM

    Hi

    Hope it will help you,.

    Pls Reward if help.

    For changes to a commercial object to be able to be logged in a change document, the object must have been defined in the system as a change document object. A change document object definition contains the tables which represent a commercial object in the system. The definition can also specify whether the deletion of individual fields is to be documented. If a table contains fields whose values refer to units and currency fields, the associated table, containing the units and currencies, can also be specified.

    It must be specified for each table, whether a commercial object contains only one (single case) or several (multiple case) records. For example, an order contains an order header and several order items. Normally one record for the order header and several records for the order items are passed to the change document creation when an order is changed.

    The name under which a change document object is created is an object class.

    The object class BANF was defined for the change document object "Purchase requisition", which consists of the tables EBAN (purchase requisition) and EBKN (purchase requisition account assignment).

    Changes to this commercial object can then be saved in the system under the object values of this change document object, i.e. the object ID and a change document number. The object ID is the key to the object value, i.e. all records which are defined as belonging to a given change document object.

    All changes to a commercial object constitute an object value under this key. This is for example the order number for orders or the number range object name for number range objects. All changes to a given order or to a given number range object can be accessed in this way.

    The object value BANF with the object ID "3000000000" consists of the records of the tables EBAN and EBKN with the order number "3000000000".

    If changes are not yet to be made, but are planned, they can be logged as planned changes. A planned date for the changes can be specified. The planned changes can be analyzed and copied into the tables. You must program the copy yourself.

    All logging functions are supported by SAP function modules. The application development must contain certain INCLUDE programs. Old and new status are passed to the change document creation. The included function modules determine the changes for all table fields which are flagged as being change-relevant in the Dictionary.

    Change document

    A change document logs changes to a commercial object. The document is created independently of the actual database change. The change document structure is as follows:

    Change document header

    The header data of the change to an object ID in a particular object class are stored in the change document header. The change document number is automatically issued.

    Change document item

    The change document item contains the old and new values of a field for a particular change, and a change flag.

    The change flag can take the following values:

    U(pdate)

    Changed data. (Log entry for each changed field which was flagged in the Dictionary as "change document-relevant")

    I(nsert)

    Data inserted.

    Changes: Log entry for the whole table record

    Planned changes: Log entry for each table record field

    D(elete)

    Data were deleted (log entry for the whole table record)

    I(ndividual field documentation)

    Delete a table record with field documentation

    1 log entry per field of the deleted table entry, the deleted text is saved

    Change document number

    The change document number is issued when a change is logged, i.e. when the change document header is created by the change document creation function module (function group SCD0).

    The change number is not the same as the change document number. The change document number is issued automatically by the function group SCD0 function modules when a change document is created for a change document object. The change number is issued by the user when changes are planned. The same change number can be used for various change document objects.

    Internal processing

    When the object-specific update is called, the object-specific change document creation is called. The object-specific change document header is written with a change document number. The Dictionary is searched for which fields are to be logged for each table in the object definition. The log records for these fields are then created as change document items according to the object definition.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.