kitsants
Member
Hi,
Our functional analyst has asked me to refresh the PY environment from PD to troubleshoot an issue. This is the first time that I'll be doing this task so I want to understand first some concepts behind data/environment refresh before doing it and I have a few questions which I know that you great guys here in JDE List can enlighten. Actually, I have created a case with Oracle but I'm really not satisfied with their answers so I have to run to the real experts.
Here are my questions:
1.) Is it possible to refresh just the data (business data) in PY from PD and not refreshing the entire environment (data + objects)? Can I accomplish this by refreshing just the Business Data tables (using R98403|XJDE0021) or after refreshing business data, do I also have to refresh Control Tables (using R98403|XJDE0022) to prevent any possible integrity issue(s)? Is there any caveat for E1 812 TR 8.96.1.1 ?
2.) What is the main difference between Load Demo Data and Load Production Data. The meaning of these load options are a bit confusing based on a couple of documents from Oracle. See these articles below:
From SOLUTION 20104733:
*Do Not Load Data -- This option does not create any tables nor does it load any data for the environment being upgraded or installed. This option is not used to upgrade typical environments.
*Load Production Data -- This option loads JD Edwards EnterpriseOne configuration and control data. Created application transaction tables, such as Accounts Payable tables, remain empty. This is the default option for all environments except Pristine, Development and Production.
*Load Demo Data -- This option loads JD Edwards EnterpriseOne demonstration data into the control and application tables that are created. Use this option if you want to add sample data (such as mock inventory) to the environment you are upgrading. This is the default option for the Pristine and Development environments but not Production.
From Solution 200783116
Processing option 3 determines whether or not data will be copied. The value you enter here does not really determine if PROD or demonstration data is to be loaded. The value determines whether or not the data from the source location will be copied to the target location. A value of `2' will copy the data. A value of `1' will be cross-referenced with the Copy Data object code value (discussed in more detail later) on the Object Librarian record for the table being processed.
As you can see, Loading Options were defined differently from the 2 Solutions above, specially loading Demo Data.
3.) After running R98403|XJDE0019 to copy Central Objects tables (in a test environment), I found a discrepancy that I suspect is an issue. The PDF output file for the report states there were 11,570 records inserted in the F983051 table in the "Central Objects - PY812" data source. However, after the report ended the PY812.F983051 table only contained 11,537 records. So, the table seems to be missing 33 records based on the information in the PDF output file. Has anyone of you experienced this issue?
Any tips or advise when refreshing data or environement would be greatly appreciated.
Thank you very much in advance for your help.
Our functional analyst has asked me to refresh the PY environment from PD to troubleshoot an issue. This is the first time that I'll be doing this task so I want to understand first some concepts behind data/environment refresh before doing it and I have a few questions which I know that you great guys here in JDE List can enlighten. Actually, I have created a case with Oracle but I'm really not satisfied with their answers so I have to run to the real experts.
Here are my questions:
1.) Is it possible to refresh just the data (business data) in PY from PD and not refreshing the entire environment (data + objects)? Can I accomplish this by refreshing just the Business Data tables (using R98403|XJDE0021) or after refreshing business data, do I also have to refresh Control Tables (using R98403|XJDE0022) to prevent any possible integrity issue(s)? Is there any caveat for E1 812 TR 8.96.1.1 ?
2.) What is the main difference between Load Demo Data and Load Production Data. The meaning of these load options are a bit confusing based on a couple of documents from Oracle. See these articles below:
From SOLUTION 20104733:
*Do Not Load Data -- This option does not create any tables nor does it load any data for the environment being upgraded or installed. This option is not used to upgrade typical environments.
*Load Production Data -- This option loads JD Edwards EnterpriseOne configuration and control data. Created application transaction tables, such as Accounts Payable tables, remain empty. This is the default option for all environments except Pristine, Development and Production.
*Load Demo Data -- This option loads JD Edwards EnterpriseOne demonstration data into the control and application tables that are created. Use this option if you want to add sample data (such as mock inventory) to the environment you are upgrading. This is the default option for the Pristine and Development environments but not Production.
From Solution 200783116
Processing option 3 determines whether or not data will be copied. The value you enter here does not really determine if PROD or demonstration data is to be loaded. The value determines whether or not the data from the source location will be copied to the target location. A value of `2' will copy the data. A value of `1' will be cross-referenced with the Copy Data object code value (discussed in more detail later) on the Object Librarian record for the table being processed.
As you can see, Loading Options were defined differently from the 2 Solutions above, specially loading Demo Data.
3.) After running R98403|XJDE0019 to copy Central Objects tables (in a test environment), I found a discrepancy that I suspect is an issue. The PDF output file for the report states there were 11,570 records inserted in the F983051 table in the "Central Objects - PY812" data source. However, after the report ended the PY812.F983051 table only contained 11,537 records. So, the table seems to be missing 33 records based on the information in the PDF output file. Has anyone of you experienced this issue?
Any tips or advise when refreshing data or environement would be greatly appreciated.