Configuration

Note

This configuration guide refers to PreBilt transactions beginning 'PB2_' and details the standard process without additional features or enhancements. You should copy these transactions with a different prefix to maintain a backup and protect the originals.

The guide displays the standard PreBilt screens and gives details of the structures in which the on screen fields can be found. Fields within these structures can be used to customise and enhance the screen. For instructions on how to use structures to find fields, please see Available data structures. For instructions on how to maintain the configuration elements in AMD, please see General configuration elements.

PB2_CHECK_LIST

Configuration element	Description
FE_APP	Frontend class to use in running the transaction. Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.
PROCESSING_OPTIONS	Defines the parameters and configuration options required by the processing class. The text for the title of the email is obtained from the TITLE field. If text needs to be included on the email, this should be maintained in the BODY_TEXT field so that the text will be added at the top of the Check List email before the questions and answers. If text needs to be included on the email, this should be maintained in the FOOTER_TEXT field so that text will be added to the bottom of the Check List email. If RECIPIENT_INT is maintained the checklist answers, this will be sent to the defined user’s business workplace inbox. Setting the ‘Value’ to ‘SY:UNAME’ will send the email to the relevant user’s inbox. If RECIPIENT_EXT is maintained, the checklist answers this will be sent to the defined external email address. Note: If text is added to any of these fields, including if specific email addresses are maintained in either RECIPIENT_INT or RECIPIENT_EXT, it must be contained within double quotes.
PROCESSING_CLASSES	Defines the class that processes the answers in SAP. The default supplied class creates an email.
SIGNATURE	Configure whether a signature is required.
INPUT_QUESTIONS	Controls which fields are needed for inputting/validating on the screen, and which fields will be display only. Fields that can be display only can be any from the available structures list mentioned above, some examples of which are shown below with Suggested Input Types of ‘N/A’.
INPUT_QUESTIONS_ACTIONS	Controls which actions and options are available in the header and footer sections of the screen and, where applicable, which other apps are called.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.

PB2_CHECK_LIST_IDEAS

Configuration element	Description
FE_APP	Frontend class to use in running the transaction. Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.
PROCESSING_CLASSES	Defines the class that processes the answers in SAP. The default supplied class creates an email.
PROCESSING_OPTIONS	Defines the parameters and configuration options required by the processing class. The text for the title of the email is obtained from the TITLE field. If text needs to be included on the email, this should be maintained in the BODY_TEXT field so that the text will be added at the top of the Check List email before the questions and answers. If text needs to be included on the email, this should be maintained in the FOOTER_TEXT field so that text will be added to the bottom of the Check List email. If RECIPIENT_INT is maintained the checklist answers, this will be sent to the defined user’s business workplace inbox. Setting the ‘Value’ to ‘SY:UNAME’ will send the email to the relevant user’s inbox. If RECIPIENT_EXT is maintained, the checklist answers this will be sent to the defined external email address. Note: If text is added to any of these fields, including if specific email addresses are maintained in either RECIPIENT_INT or RECIPIENT_EXT, it must be contained within double quotes.
SIGNATURE	Configure whether a signature is required.
INPUT_QUESTIONS	Controls which fields are needed for inputting/validating on the screen, and which fields will be display only. Fields that can be display only can be any from the available structures list mentioned above, some examples of which are shown below with Suggested Input Types of ‘N/A’.
INPUT_QUESTIONS_ACTIONS	Controls which actions and options are available in the header and footer sections of the screen and, where applicable, which other apps are called.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.

PB2_CHECK_LIST_MHE

Configuration element	Description
FE_APP	Frontend class to use in running the transaction. Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.
PROCESSING_CLASSES	Defines the class that processes the answers in SAP. The default supplied class creates an email.
PROCESSING_OPTIONS	Defines the parameters and configuration options required by the processing class. The text for the title of the email is obtained from the TITLE field. If text needs to be included on the email, this should be maintained in the BODY_TEXT field so that the text will be added at the top of the Check List email before the questions and answers. If text needs to be included on the email, this should be maintained in the FOOTER_TEXT field so that text will be added to the bottom of the Check List email. If RECIPIENT_INT is maintained the checklist answers, this will be sent to the defined user’s business workplace inbox. Setting the ‘Value’ to ‘SY:UNAME’ will send the email to the relevant user’s inbox. If RECIPIENT_EXT is maintained, the checklist answers this will be sent to the defined external email address. Note: If text is added to any of these fields, including if specific email addresses are maintained in either RECIPIENT_INT or RECIPIENT_EXT, it must be contained within double quotes.
SIGNATURE	Configure whether a signature is required.
INPUT_QUESTIONS	Controls which fields are needed for inputting/validating on the screen, and which fields will be display only. Fields that can be display only can be any from the available structures list mentioned above, some examples of which are shown below with Suggested Input Types of ‘N/A’.
INPUT_QUESTIONS_ACTIONS	Controls which actions and options are available in the header and footer sections of the screen and, where applicable, which other apps are called.
****_LIST	Allows a static list of answers to be maintained. There can be as many list options as required. XXXX will be replaced with a word that makes sense for the list maintained. For example, USER_LIST could be a maintained list of possible SAP usernames. The value and description of the answers are displayed as set up; no validation will take place until the data is submitted to SAP.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.

PB2_CHECK_LIST_MSG

Configuration element	Description
FE_APP	Frontend class to use in running the transaction. Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.
PROCESSING_CLASSES	Defines the class that processes the answers in SAP. The default supplied class creates an email.
PROCESSING_OPTIONS	Defines the parameters and configuration options required by the processing class. The text for the title of the email is obtained from the TITLE field. If text needs to be included on the email, this should be maintained in the BODY_TEXT field so that the text will be added at the top of the Check List email before the questions and answers. If text needs to be included on the email, this should be maintained in the FOOTER_TEXT field so that text will be added to the bottom of the Check List email. If RECIPIENT_INT is maintained the checklist answers, this will be sent to the defined user’s business workplace inbox. Setting the ‘Value’ to ‘SY:UNAME’ will send the email to the relevant user’s inbox. If RECIPIENT_EXT is maintained, the checklist answers this will be sent to the defined external email address. Note: If text is added to any of these fields, including if specific email addresses are maintained in either RECIPIENT_INT or RECIPIENT_EXT, it must be contained within double quotes.
SIGNATURE	Configure whether a signature is required.
INPUT_QUESTIONS	Controls which fields are needed for inputting/validating on the screen, and which fields will be display only. Fields that can be display only can be any from the available structures list mentioned above, some examples of which are shown below with Suggested Input Types of ‘N/A’.
INPUT_QUESTIONS_ACTIONS	Controls which actions and options are available in the header and footer sections of the screen and, where applicable, which other apps are called.
TYPE_OF_NOTIFICATION	Settings for the type of notification.
URGENCY	Settings for the urgency of the notification.
LOCATION	Settings for the location of the issue.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.

PB2_CHECK_LIST_SHIFT

Configuration element	Description
FE_APP	Frontend class to use in running the transaction. Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.
PROCESSING_CLASSES	Defines the class that processes the answers in SAP. The default supplied class creates an email.
PROCESSING_OPTIONS	Defines the parameters and configuration options required by the processing class. The text for the title of the email is obtained from the TITLE field. If text needs to be included on the email, this should be maintained in the BODY_TEXT field so that the text will be added at the top of the Check List email before the questions and answers. If text needs to be included on the email, this should be maintained in the FOOTER_TEXT field so that text will be added to the bottom of the Check List email. If RECIPIENT_INT is maintained the checklist answers, this will be sent to the defined user’s business workplace inbox. Setting the ‘Value’ to ‘SY:UNAME’ will send the email to the relevant user’s inbox. If RECIPIENT_EXT is maintained, the checklist answers this will be sent to the defined external email address. Note: If text is added to any of these fields, including if specific email addresses are maintained in either RECIPIENT_INT or RECIPIENT_EXT, it must be contained within double quotes.
SIGNATURE	Configure whether a signature is required.
INPUT_QUESTIONS	Controls which fields are needed for inputting/validating on the screen, and which fields will be display only. Fields that can be display only can be any from the available structures list mentioned above, some examples of which are shown below with Suggested Input Types of ‘N/A’.
INPUT_QUESTIONS_ACTIONS	Controls which actions and options are available in the header and footer sections of the screen and, where applicable, which other apps are called.
****_LIST	Allows a static list of answers to be maintained. There can be as many list options as required. **** will be replaced with a word that makes sense for the list maintained. For example, USER_LIST could be a maintained list of possible SAP usernames. The value and description of the answers are displayed as set up; no validation will take place until the data is submitted to SAP.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.

PB2_CHECK_LIST_VNC

Configuration element	Description
FE_APP	Frontend class to use in running the transaction. Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.
PROCESSING_CLASSES	Defines the class that processes the answers in SAP. The default supplied class creates an email.
PROCESSING_OPTIONS	Defines the parameters and configuration options required by the processing class. The text for the title of the email is obtained from the TITLE field. If text needs to be included on the email, this should be maintained in the BODY_TEXT field so that the text will be added at the top of the Check List email before the questions and answers. If text needs to be included on the email, this should be maintained in the FOOTER_TEXT field so that text will be added to the bottom of the Check List email. If RECIPIENT_INT is maintained the checklist answers, this will be sent to the defined user’s business workplace inbox. Setting the ‘Value’ to ‘SY:UNAME’ will send the email to the relevant user’s inbox. If RECIPIENT_EXT is maintained, the checklist answers this will be sent to the defined external email address. Note: If text is added to any of these fields, including if specific email addresses are maintained in either RECIPIENT_INT or RECIPIENT_EXT, it must be contained within double quotes.
SIGNATURE	Configure whether a signature is required.
INPUT_QUESTIONS	Controls which fields are needed for inputting/validating on the screen, and which fields will be display only. Fields that can be display only can be any from the available structures list mentioned above, some examples of which are shown below with Suggested Input Types of ‘N/A’.
INPUT_QUESTIONS_ACTIONS	Controls which actions and options are available in the header and footer sections of the screen and, where applicable, which other apps are called.
****_LIST	Allows a static list of answers to be maintained. There can be as many list options as required. **** will be replaced with a word that makes sense for the list maintained. For example, USER_LIST could be a maintained list of possible SAP usernames. The value and description of the answers are displayed as set up; no validation will take place until the data is submitted to SAP.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.