SQL statements that contains PL/SQL calls

When SQL statements contain embedded PL/SQL statements, the performance will be poorer since each call require a context switch.

Violating this rule will affect the performance of the code.The severity is minor which means that the code probably works, but should be corrected at first opportunity.

Note:   This rule is subject to a white-list that is maintained by the product managers collectively.Code that violates this rule must either be fixed or put on the appropriate white-list.See appendixes for currently white-listed objects.

Correct this if it is possible, possible solutions could be table joins or retreiving value in a cursor loop.

In this example a Get function is used to get the site description. 

SELECT part_no part_no, contract contract, Site_API.Get_Company(contract) company
FROM Part_Cost_Tab;

In this case we can get the company by using an join instead. 

SELECT pc.part_no part_no, pc.contract contract, s.company company
FROM Part_Cost_Tab pc, Site_Tab s
WHERE pc.contract = s.contract;

Appendix 1: White-list of approved objects in Financials.

Appendix 2: White-list of approved objects in Human Resources.

Appendix 3: White-list of approved objects in Manufacturing.

Appendix 4: White-list of approved objects in Service and Asset.

Appendix 5: White-list of approved objects in Supply Chain.

Appendix 6: White-list of approved objects in Technology.

Appendix 7: White-list of approved objects in Projects.

This page is generated from IFS Developer Studio at 2021-08-13 08:40.