Enterprise Systems: SAP, FAS & Insurance Technology

The question asks which statement is NOT true. Option D states that modification of rated premium does not require re-rating, which is false - any change to premium would require the Ratabase rating engine to recalculate. Options A, B, and C describe true facts about the PLUS rating system: users can modify premiums for certain coverage levels after rating, modifications require re-rating, and Ratabase performs the rating.

In the PLUS insurance system, maj_line_cd is a major line code field. When this code is set to "19", it triggers the system to load the Home details screen on clicking NEXT. Line code 19 likely corresponds to homeowners or property insurance. The other screens (Driver details, Vehicle details, Rating) would be associated with different line codes for auto insurance or other product types.

Ratabase is all of the above: it's a third-party tool that holds rules and tables, is invoked from RBOS2LNK program, and calculates premium with discounts/surcharges/taxes.

Standard endorsements are endorsements that remain active until the policy expiration and are considered part of the policy at renewal time. Unlike temporary endorsements (which apply for only a portion of the policy period), standard endorsements continue through the entire policy term and carry over when the policy renews. They don't extend the policy period but remain in force until natural expiration.

Cover Note is the document issued as acceptance of Reinsurance. Option A refers to quotation acceptance, option C to new business acceptance, and option D to cancellation acceptance.

FAS stands for Financial Accounting System. It's middleware that bridges financial systems and processes financial data between applications like GOALD, Axsone, and OGIS. The other options either misspell 'System' or are incorrect acronyms.

FAS acts as middleware between GOALD and other systems including Axsone, OGIS, and Computron. The correct answer is 'all the above' because FAS supports integration with multiple downstream systems for data processing and transfer.

Validating data in GOALD is not an FAS functionality. FAS focuses on extracting data from GOALD, processing it in FAS, and FTPing files to downstream systems like Axsone and OGIS. The validation occurs before the data reaches FAS, not within it.

FAS runs consist of all three components: stored procedures, COBOL modules, and batch programs. These work together to process financial data and ensure smooth operation of the financial accounting system.

FAS database should be on the same server as GOALD data to ensure efficient data transfer and minimize network latency. This proximity allows for faster processing and reduces the risk of data synchronization issues between the two systems.

The S% error code can be corrected in FAS, representing system or syntax errors that can be resolved within the FAS processing environment. The other error codes (G%, E%, D%) either represent different types of errors or cannot be corrected within FAS.

CDCS posting is processed before validation completes. The validation process typically occurs after CDCS posting, where data is checked for accuracy and completeness before being sent to subsequent processing stages.

tmw_prcsctrl_eur is not an FAS transaction table, while tmw_clmtrxn, tmw_postmsg, and tmw_ogiswork are valid FAS transaction tables. The prcsctrl_eur table appears to be a control or processing table rather than a transaction table.

For ADE, the frontend connects to both the ADE database and GOALD. This dual connection allows the frontend to access policy data from both systems while maintaining integration between ADE and the underlying GOALD data source.

Policies booked through ADE can be enquired through PLUS application. This follows the standard workflow where PLUS provides policy inquiry and management functionality for policies processed through ADE.

When stage status is 5, it means the policy is 'Booked'. This status indicates successful completion of the booking process in the ADE system, moving from processing stages to finalization.

Employee communication details are stored in infotype 0105. This SAP HR infotype is specifically designed to store contact and communication information for employees, including phone numbers, email addresses, and other contact details.

Employee qualification details are stored in infotype 0024 in SAP HR systems. The other infotypes (0022, 0023, 0021) are used for different employee data like personal details, addresses, and basic information respectively.

Employee address details are stored in infotype 0006 in SAP HR systems. Infotype 0007 is for bank details, 0002 for personal data, and 0009 for addresses but 0006 is the correct specific infotype for address storage.

Employee bank details are stored in infotype 0009 in SAP HR systems. Infotype 0007 is for address details, not bank information. The other options (1009, 1007) are not valid infotypes for bank data storage.