05-06-2010 12:23 PM
Hi,
The employee is chaging trip records in already exist trip number from portal. The problem is that the trip number is saving in XX cluster and TE cluster also. could you please tell me why it is storing in XX cluster? I have seen that XX cluster doesn't exists in SAP but still it is storing, It is because of buffering? If we delete XX cluster, it is going to create any problem?
Thanks and Regards,
Thilotham.
05-06-2010 10:31 PM
When I search forum, I see that XX is simply the value of a key field of PCL1 cluster table. I don't understand what you mean by "it stores in XX but it does not exist in SAP"?
05-07-2010 7:10 AM
Hi Rossi,
When we check in PCL1 table, we can see TE, TX, cluster etc, but not XX cluster.
When employee changes trip records in already exists trip numbers before saving(exists in buffer) he will be checking the report that what entries he had made( for this XX cluster at backend is used for buffering not saving). The output will be show in report by using macro RP-IMP-C1-TE-SHB(this macro is used to capture buffer records from portal). The problem we are facing is some of the trip numbers are saving in XX cluster.
Thanks and Regards,
Thilotham.