Publish of KSB1/KSB2 Includes Incorrect Values

Publish of KSB1/KSB2 Includes Incorrect Values


When you publish transaction KSB1/KSB2, the contents of the file contains incorrect values (e.g. rep.cur. is 1575 instead of 225).


The report variant was saved incompletely.
Hence, execution via selection screen/in foreground may lead to different results than in background.


Verify that the used report variant was saved completely (including all screens):

    • Related Articles

    • Error Message "no ALV table imported from memory"

      Symptom When you publish a report, error message /DPS/RET 104 - "Error Message "no ALV table imported from memory" is issued/written in the job log and nothing is published. The issue may occur both in foreground and background execution or only in ...
    • How Can I Restrict Setting of Default ALV Layout In Rainbow?

      Requirement You want to restrict some users from setting a default ALV layout in Rainbow reports. Solution SAP offers standard authorization objects to control whether a user is allowed to set default ALV layouts. 1. Authorization object S_ALV_LAYO ...
    • Runtime Error SET_HANDLER_FOR_NULL In Transaction FBL3H

      Symptom When you run transaction FBL3H via Publisher/Rainbow, runtime error SET_HANDLER_FOR_NULL occurs in method CL_SALV_TREE_ADAPTER=>CREATE_TREE. Reason By default, transaction FBL3H displays an ALV tree of History. Submit of transaction with ALV ...
    • Dump (Runtime Error)

      In case of dump (runtime error), please attach the complete dump to the ticket (as described in the OSS note 1896868 – How to save a short dump in text format: When a user receives a short dump at runtime mode, pay attention to the fact that the dump ...