Hi Experts,
Built-in functionality of Copy Version copies one version to another version for all the years. So, that can't work for me. I created my own rule and put everything in FIX with an option of variable for year. My own rule was taking too much time. I got curious how the built-in functions of Copy Data and Copy Version work. So I ran both rules one by one and checked the hsp_audit_records to see what kind of script is being used. Following script I found:
Copy Data:
SET CREATENONMISSINGBLK ON;
FIX ("HSP_InputValue","HSP_InputCurrency","Jan","No Inter-company","CWIP","No Entity","FY18","Local","USD","AED","PKR","Currency","No Statistical","Finance","No Product","Budget")
DATACOPY "Working" TO "Version 1";
ENDFIX;
Copy Version:
FIX ("Local","HSP_InputValue","HSP_InputCurrency","Confiz Limited","No Entity","PAK Motors","UAE Motors","Unspecified Entity","US Motors")
DATACOPY "Budget"->"Working" TO "Budget"->"Version 1";
ENDFIX;
My questions are:
- Why Oracle has added "SET CREATENONMISSINGBLK ON;" in Copy Data but not in Copy Version?
- If I use the same script as used in Copy Version (DATACOPY) my own business rule take a lot more time than Oracle built-in function. My expectation are correct?
- What is the impact if I use both set frmlbottomup and set createnonmissingblk together? As per my understanding, frmlbottomup starts from the bottom and so doesn't allow to create blocks. I'm actually confused here.
- Set Calcparallel command always work and it actually reduces the time of business rule exactly as per number e.g if "set calcparallel 20" is added a script would that reduce the execution duration 20 times?
Note: I don't use HSP_InputValue in FIX. I hope it has no impact.