We use Tidal Enterprise Scheduler to launch many ECC/APO/SCM jobs. When using it to launch /SAPAPO/TS_PLOB_MAINTAIN (using a specific variant that creates CVCs from an InfoProvider) on our production box, it fails to create new CVCs. If I use MC62 to run the same variant in a background job using my own ID, it successfully creates new CVCs. Here are some specifics about our problem:
- It does not generate any errors, other than "No new characteristics combinations were loaded" and "No planning objects created"
- This process (running /SAPAPO/TS_PLOB_MAINTAIN via Tidal) works in Q, but it has never worked in P
- Tidal uses an ID that has SAP_ALL & SAP_NEW authority
- The user account that the Tidal job uses has the exact same settings and roles in Q as it does in P
Our in-house security analyst debugged the problem, and could not find a security-related issue. This is what she said about her testing:
"Per our conversation, I wanted to confirm that the TIDAL_APO user in QF1and PF1 match exactly - they both have SAP_ALL & SAP_NEW. I traced the id in Q and PF1, the traces are identical, with no return code errors. I checked SU01 user parameters and they match as well. The issue with the job has to be somewhere else."
- VariantX lives in both Prod and QA.
- When Tidal submits VariantX in QA, it works.
- When Tidal submits VariantX in Prod, it fails.
- When I submit VariantX using my ID in Prod, it works.
Since the Tidal ID has SAP_ALL & SAP_NEW in both Prod and QA, this should work in both environments, but it only works in QA.
Why would this fail to work in production, yet work normally in QA?