Skip to Content

PCL1-TE Cluster Structure USER/PTK99 leads to inconcistencies

Hi guys,

System Information: ECC 6.0 EHP4 SP Level 46.

today I made a discovery which makes me feel uneasy. In the PCL1-TE Cluster, there is the Structure PTK99, respectively called "USER". This strucutre is designed for customer enhancements. I did use this possibility to add fields to the whole TRV-Process which were a requirement of our special department.

Everything worked out so far. After some time, I got additional requirements from the special department for more fields which I added per enhancement again.

Now here's what shocks me:

Whenever A Trip or Separation Allowance (PR05, TGANL, TGMOD, etc.) which has been created before the point of time of my alteration of PTK99 is tried to be accessed, changed, deleted, there is a dump. More detailed, whenever the standard macro "rp-imp-c1-te" is called and the trip/SA is older than my adjustment, it dumps for CONNE_IMPORT_WRONG_STRUCTURE, CX_SY_IMPORT_MISMATCH_ERROR.

The consequence I understand from this behaviour is: Whenever I change the cluster structure, old entries can't be accessed in any way anymore. This would be a catastrophy since alteration of PTK99 could also happen after GO-Live when requirements Change and it would corrupt all present entries.

What can be done to avoid this? What can be done to rectify this subsequently?

Best regards,


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Jun 20, 2012 at 11:15 AM

    Hello Lukas

    Hope your well! Yes, this is indeed a known issue 😉 and it is quite a well known error that can occur after SP upgrade with custom appends because additional fields were added due to EU Directives regarding VAT refunds to various structures such as PTK99 PTK05, PTK03 (BELEG) etc and these are delivered with new support packages.

    Delivering new fields causes no problems with old trips except if there has been an additional modification in the structure like in your case.

    Once you modify a data cluster structure, then the order of the fields must then stay the same and the new fields must be added to the end of the structure so as SAP delivers new fields to the standard automatically the customer fields are moved to the end of the structure. For example:

    Before the supportpackage:

    Standardfield 1
    Standardfield 2
    Customer Append

    After the supportpackage:

    Standardfield 1
    Standardfield 2
    Standardfield 3 (new delivered field)

    So to avoid this dump, the structure must now be sorted in this way:

    Standardfield 1
    Standardfield 2
    Customer Append
    Standardfield 3

    Otherwise the dump appears because when reading the old trip the data does not fit any more to the order of the fields in the new structure definition!

    One of my colleagues wrote a report that can re-sort the structure for you with the custom append re-inserted to avoid the dump and its the only way to avoid this scenario I'm afraid. If you want this sample report, please let me know.

    Hope the info helps you out in the meantime!

    All the best


    Message was edited by: Sally Redmond

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Lukas

      Certainly alot to consider there... 😉

      probably the report wont help therefore but at least it can give you an idea as to how you could re-sort the custom append within the new structure (this will be in the case of displaying OLD trips should be ok?)

      Hope its useful!