Document posting (in background input or manual mode) terminates abnormally and the following or similar message is output: "Tuple in MC table xyz exists for an INS operation", where table xyz represents a user-defined matchcode table. OR
This error results when reloading document data after archiving.
When a check is run on table xyz it turns out that this table contains a record which does not have a corresponding record in the BSEG.
Transaction data deletion program SAPF020 or document archiving and its deletion program SAPF040D (up to and incl. 2.2) or SAPF048D (as of 3.0) were started at an earlier point in time. Furthermore, a number of fields were added to table BSEG and matchcodes (ID 9, synchronous) were entered for these fields.
Up to and including Release 3.0a a cluster deletion was always attempted if tables BSEG, BSET, BSED and BSEC had been stored in cluster RFBLG. However, a cluster deletion skips the matchcodes and does not update them.
As of 3.0.b.: In these cases program SAPF020 or SAPF048D must be started with option 'Cluster deletion off'
Up to and including 3.0.a: After program SAPF020 has run, the user-defined matchcode objects are reset manually by means of program SAPMACO. Then: Program code repair and set 'Cluster deletion off' for the next run.
Additional key words
SAPF020 SAPF040D SAPF048D OBR1 matchcode reset program RFBLG BSEG SAPF049 FB01
No comments:
Post a Comment