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: 

tabkey in cdpos

Former Member
0 Kudos

high expert,

normaly the tabkey in cdpos is filled with something like this:

- first six (6) digits is line item no

- last four (4) characters are condition record

- three (3) digits after line number is "Step number (STUNR)". This numer determines the sequesnce of the condition within a procedure.

- the next two (2) digits is "Condition counter (ZAEHK)". This is a access number of the conditions within a step in the pricing procedure.

Now i have some fields in a table to be viewed on changes or new inserts. when i look into cdpos in se16, looking for that table, the tabkey-field is filled with something like:

82B93D4736ADCB62E1000000C0A80A20

which has nothing to do with line-items and so on. the other table-entries look like mandantorynr+somethingelse.

so, i don't know where the fm builds the tabkey or how it is built. if someone knows, plz let me know!!!!

thanks, harry schlichte

1 REPLY 1

Former Member
0 Kudos

Look at these fm's that should help! Function Group(SCD1)

INCLUDE LSCD1U01. "CHANGEDOCUMENT_READ_HEADERS

INCLUDE LSCD1U02. "CHANGEDOCUMENT_READ_POSITIONS

INCLUDE LSCD1U03. "CHANGEDOCUMENT_PREPARE_POS

INCLUDE LSCD1U04. "CHANGEDOCU_ARCHIVE_HANDLE_SET

INCLUDE LSCD1U05. "CHANGEDOCUMENT_UNICODE_CHECK

INCLUDE LSCD1U06. "CHANGEDOCU_GUID_READ

INCLUDE LSCD1U07. "CHANGEDOCU_CDPOS_READ

INCLUDE LSCD1U08. "CHANGEDOCU_READ_PREP_POS_W_UID

INCLUDE LSCD1U09. "CHANGEDOCU_READ_POS_W_UID

INCLUDE LSCD1U10. "CHANGEDOCU_HAS_GUID

INCLUDE LSCD1U11. "CHANGEDOCUMENT_PREPARE_DISPLAY

Rajeev