SAP Solution Manager 7.2 · Component-Based Test Automation (CBTA)

What is a composite script in CBTA, and how does parameter exchange work in it?

It combines 2+ CBTA scripts into one end-to-end composite test configuration; entry is in Solution Documentation, Test Tool dropdown → Composite Test.

Adding scripts enables parameter exchange — e.g. an FB60 invoicing script outputs a document number in the message bar; expose its export parameter and import it into an FB03 display-document script (both in the composite → can be Local parameters). Composite parameters are defined in the SECATT script (double-click interface CIF1_1).

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in Component-Based Test Automation (CBTA)

What three parts make up a CBTA test configuration?
What generation of test-automation tool is CBTA, and how does its modular approach cut maintenance?
What is a Test Data Container (TDC) in eCATT, and why is test data kept separate from the test script?
What are the key best practices when recording a CBTA script?
How do you choose between CBTA versus a third-party automation tool?
Why must SAP GUI scripting be TRUE before recording a CBTA script for a SAP GUI app?