We have a custom abap program that generates a report from a combination of a custom table and standard master data changes. We made a change to the program to add the plant as a parameter. This works in our dev environment. We then send the transport to two QA boxes. The code arrives in both systems and shows up as active but the plant field displays on one system but not on the other. The code looks like this (with the new field in bold)
SELECT-OPTIONS: s_dispo FOR ztffalert-dispo. " MRP controllers
PARAMETERS: p_werks like ztffalert-zzwerks,
p_rdate LIKE ztffalert-ersda
DEFAULT sy-datum, " Date to be run
p_cdate LIKE ztffalert-ersda. " comparision date
I verified that
1. Transports went to both QA systems with status 0 (no errors or warnings).
2. Remote compare of code matches from Dev to both QA boxes
3. Ran in debug mode in QA boxes and then scrolled up to confirm that the code is there and when I enter the p_werks to display values, the debugger does recognize that the field exists.
4. Code is active in both systems.
Both QA systems are copies of production so the tables are identical with the only difference being that one has more data then the other.
Why would the parameter show up in one QA system and not the other?
Could you cross check whether the transport Layer is defined for the 2 QA system
Your program's package will be assigned to Devclass which inturn has Destination (Target)
i think the target system for other QA system might not be defined under that package,
even though the transport release does not show any warinings or Errors.