Listing optional parameters of a table or structure

Listing optional parameters of a table or structure

I would like to list the optional parameters of a table or structure of a particular BAPI. I have tried using is Optional method but in vain.

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.


Can you tell me if there any other way to know whether the Field in the table is optional or not?


Beyond looking at the inbound parameter/table structures through the 'Display' mechanism in the Function Builder there is no other way to check whether a field is optional or not. Unfortunatly, the only way to really know the status of a given field is to test, test, test. However, this also means that you must have a good set of test data up front and this is always important when developing software.

The value of test cases or scenarios is highly underrated as developers begin a software process. By having a validated test scenario in the beginning (one that works every time through Function Builder) you can be more assured of your development effort as you begin to access BAPIs from the outside world. If you are constantly questioning whether your application has a problem or if you simply have bad test data, the development effort becomes abortive and true progress harder and harder to make.


This was first published in April 2002