Call Transaction Program with CTU_PARAMS-NOBINPT = 'X'

[ronaldo_aparecido]

Hello Community

I have a 'call transaction' program that has the parameter :CTU_PARAMS-NOBINPT = 'X' .

When I run it in QA it doesn't make the call transaction (FBRA) but if I run it in production it works even with CTU_PARAMS-NOBINPT = 'X'

.If in dev I remove X via debug it runs. Does anyone know how it can work in production even with CTU_PARAMS-NOBINPT = 'X'?

FORM Z_EXECUTA TABLES T_BDC STRUCTURE T_BDC
                      T_MSG STRUCTURE T_MSG
                      USING P_CODE    LIKE V_TCODE
                            P_RACOMMIT LIKE CTU_PARAMS-RACOMMIT
                      CHANGING
                            P_ALV STRUCTURE T_ALV.

  W_CTU_PARAMS-DEFSIZE = C_DEFSIZE.
  W_CTU_PARAMS-DISMODE = C_MODE.
  W_CTU_PARAMS-UPDMODE  = C_UPD.
  W_CTU_PARAMS-NOBINPT = 'X'.

  REFRESH T_MSG.

  CALL TRANSACTION V_TCODE  USING T_BDC  OPTIONS FROM W_CTU_PARAMS
                            MESSAGES INTO T_MSG.

ENDFORM.                    " Z_EXECUTA

[Sandra_Rossi]

First of all, you must ask yourself what means CTU_PARAMS-NOBINPT = 'X' compared to ' ': it just means that the system variable SY-BINPT is set respectively to ' ' or 'X' while the programs run in the transaction code.

Now debug the program and see where it checks the value of SY-BINPT. I'm joking, it would be extremely difficult.

Instead, do a SAT recording without aggregation, in both QA and production, on the same data (or almost same), and compare the two traces (via SAT export/import trace + comparison buttons), it will indicate all the differences.

Good luck!