Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

issue related CDHDR and CDPOS

Former Member
0 Kudos
965

Hello.

I have three 'z' fields used in LIKP for updating POD(proof of delivery)information.

the three fields are : zz_podat, zz_uname, zz_datum

this fields are updated to DB(LIKP table) using Modify command.

But when modify command is used, the revelant changes are not updated to standard tables CDHDR(change document header), CDPOS(change doucment item).

May i know, how to get information of change doucment histroy of a field. When modify command is used.

1 ACCEPTED SOLUTION

brunobex
Active Participant
0 Kudos
136

Hi EDUKULLA SIDDHARTHA,

Make sure your data element in the tab: "Further Characteristics" if FLAG is set to "Change Document".

Regards

Bruno Xavier.

6 REPLIES 6

brunobex
Active Participant
0 Kudos
137

Hi EDUKULLA SIDDHARTHA,

Make sure your data element in the tab: "Further Characteristics" if FLAG is set to "Change Document".

Regards

Bruno Xavier.

raymond_giuseppi
Active Contributor
0 Kudos
136

Theoretically you should never use MODIFY statement on a standard table, as those are pure-customer fields, (and if you replace this awful MODIFY by an UPDATE statement) I will not insist.

The change documents are programmatically generated. LIKP table is managed with object LIEFERUNGX (look via SCDO, or use SE16 on table TCDOB) -> In your custom program you could call FM LIEFERUNG_WRITE_DOCUMENT (Also insure the change document flag is set on related data element)

But there are many more FM that are executed in update task when a deliverry is update...

Regards,

Raymond

0 Kudos
136

Hi,

I agree with the points mentioned by Raymond, further down the line one more important point to be noticed those three Z fields mentioned by you Log Changes checkboxes ('X') should be activated which is available at Data Element level.

Thanks & regards

Suresh Krishnan

Former Member
0 Kudos
136

Hi Edukulla,

As Raymond has mentioned, the change documents are generated programatically.

What it means that:

a) if we use our own SQLs independently for updating any table, then change documents will not get generated.

b) So in your case, since it is a standard table, we should not update it directly with SQLs.

c) Rather, we should use some standard FM/BAPI for updating the 3 Z fields. That will ensure that the standard logic for change documents is called in the standard FM/BAPI and accordingly the CDHDR and CDPOS will contain data. Also make sure the data elements for these 3 fields have been appropriately flagged TICKED for change documents.

Regards,

Amit Mittal.

former_member214857
Contributor
0 Kudos
136

Hi

You need to define "Change Document" flag in Data element used to define your customer fields. You can check this in SE11

Data element -> Further characteristics

Best regards

former_member591546
Participant
0 Kudos
136

Hi Edukulla. If you need save log in these tables (CDHDR and CDPOS), this is configured in transaction SCDO. This is different from the called "table logging" (Trx SCU3 - Tables DBTABLOG/DBTABPRT).

A short instructive for change documents log (CDHDR and CDPOS):

Change documents

The logging of master and transaction data is realized through change documents. They are created, when master or transaction data are changed, to which change document objects exist (only change u2013 not create).

In SAP all changes to master and transaction data in the financial accountancy are automatically logged. The underlying structure is a change document object.

With the help of the transaction SCDO these objects are controlled.

The maintained information are stored in the table TCDOB (Objects for change document creation). The reference of the object to the tables is saved here e.g..

Usually only selected table fields are logged. This is maintained via transaction SE11.

For evaluation the transaction AUT01 can be recommended. In this transaction the configuration related to logging can be reviewed.

A selection according to Transaction, Change document object, Table or data element is possible.

The table fields that are logged are listed for the individual tables together with the change document object.