Solution : https://service.sap.com/sap/support/notes/1455417 (SAP Service marketplace login required)
Summary :
In scenarios where process chains experience interruptions, such as the error "Variant * does not exist" (DB 612), two main issues are identified. For Scenario 1, inconsistencies post-system copy or transport lead to this error. Implementation of SAP Note 1371225 and executing reports (RS_FIND_JOBS_WITHOUT_VARIANT and Z_FIND_JOBS_WITHOUT_V line) corrects these inconsistencies. In Scenario 2, improper settings in transaction SM59 or the scheduling of specific CCMS jobs are pinpointed as the root causes, requiring verification and adjustment of system, client, and authentication details for remote destinations and proper timing of job schedules.
Key words :
message_type_x dump generated, ccms job running, ccms job sap_ccms_moni_batch_dp, inconsistent job entries, process chain stops, z-report z_find_jobs_without_variant, remote process chain, inconsistent entries, process chain, remote chain
Related Notes :
| 1371225 | No report for finding jobs without program variant |
| 1147768 | Correction: BI-CCMS dispatcher runs in the incorrect client |
| 538052 | Maintenance of Myself destination in BW |