Oracle's products are often built by thousands of developers across the globe over several years. There is no one person who knows the product inside out who can churn out a solution on the spot. So how do we go about solving a problem in a timely manner? I'd like to list out an approach using a few use cases.
The mystery of HDL (HCM Data Loader)
By the time an implementer had figured out to use FBL (File Based Loader), Oracle had changed everything and brought in HDL. We are in the middle of an engagement and I could see that the HDL file was properly created. However, during the load, we faced two error messages:
1. "Enter Logical Start Date"
2. "You cannot update this record because the SourceSystemId <value> and the SourceSystemOwner <value> are invalid"
Clearly, Oracle's development team expects you to know Greek and Latin based on the above error messages. But the one person who I knew would understand this is My Oracle Support (MOS).
For the first issue, I used the search expression "Logical Start date" in MOS, I found a document which mentioned that the issue is because I'm trying to load an object with a different date from an earlier load. This means that the object already exists with a different date and is causing the issue. The solution would then be to delete the previous object to avoid issues in the current load - Problem solved.
For the second issue, I used the search expression "You cannot update this record because the SourceSystemID" gave me a hit, essentially it told me I would have to use a unique name for the object being loaded. This means, for some reason an object with the same name already exists. A search on the database proved my theory. The object of the same name was deleted and the current load went through - Problem solved.
Oracle does not expect you to know Greek and Latin, but it is a crime if you don't use the vast knowledge available in MOS.
The mystery of HDL (HCM Data Loader)
By the time an implementer had figured out to use FBL (File Based Loader), Oracle had changed everything and brought in HDL. We are in the middle of an engagement and I could see that the HDL file was properly created. However, during the load, we faced two error messages:
1. "Enter Logical Start Date"
2. "You cannot update this record because the SourceSystemId <value> and the SourceSystemOwner <value> are invalid"
Clearly, Oracle's development team expects you to know Greek and Latin based on the above error messages. But the one person who I knew would understand this is My Oracle Support (MOS).
For the first issue, I used the search expression "Logical Start date" in MOS, I found a document which mentioned that the issue is because I'm trying to load an object with a different date from an earlier load. This means that the object already exists with a different date and is causing the issue. The solution would then be to delete the previous object to avoid issues in the current load - Problem solved.
For the second issue, I used the search expression "You cannot update this record because the SourceSystemID" gave me a hit, essentially it told me I would have to use a unique name for the object being loaded. This means, for some reason an object with the same name already exists. A search on the database proved my theory. The object of the same name was deleted and the current load went through - Problem solved.
Oracle does not expect you to know Greek and Latin, but it is a crime if you don't use the vast knowledge available in MOS.
