Hi Joyce,
It was my original idea that there is something wrong with the TIME scope. But you told me that correct records are generated and even provide some log...
The empty log of the script with badi was also confusing - no errors and significant time to run (10.17 s).
Only after some tests on the real system I understood the effect:
If you have a parameter in the badi call like:
DIMENSION SOMEDIM=<ALL>
and in the calling script you reference the default scope variable like:
*XDIM_MEMBERSET SOMEDIM=%SOMEDIM_SET%
then you will get an empty script log and the script will not run.
If you don't use the default scope variable - the script will run and the log will appear.
I never have this issue with my scripts because I always provided the full scope in the badi parameters.
By the way, it's possible to correct your calling script to support multiple TIME periods with FOR/NEXT or to use CHANGED parameter in the badi call:
CHANGED=TIME
to calculate multiple periods.
B.R. Vadim