Search results for query: *

Done. Output results are complying with required. Many thanks for your great support.

I found the problem. It is in the region_view view because of to_number(region_pack.get_emp_id) which should return a varchar2 and not number. Now, I am requering and waiting for the end results.

By the way, I must add the field of TRANSACTION_ID to each record. This transaction_id is the only field that is unique and will be used for further relations in other queries.

I have completed all necessary updates to make the region field compatible with your requirements. I requeried the data, but I still get the error of ORA-01722: Invalid number. Any suggestions to find the any incompatible records?

I wish to make the logic changes necessary to adjust the REGION_PACK package.

I think I have to make standardize all previous and future entries to be as follows: Dave PARIS1-11,PARIS2-102,30,CANNE2-40,C22 AMR Toulouse-1,3,44,CANNE-6,D44,PARIS1-13 That is to separate between the prefix and the IDs with '-' whatever the prefix was. This means that...

Also, is it possible to BYPASS records with transaction_reference that do not start with a character?

I found that I have too many of the following: SUBINVENTORY_NAME TRANSACTION_REFERENCE ----------------- ----------------------------------------- Dave PARIS1-11,PARIS2-102,30,CANNES2-40,C22 This was because PARIS was actually divided into 2 regions. Could this be considered...

For the entry like that of Tarek '002027050', this is a valid entry, but the user entered the region in its region number rather than in its code. The region represents a telephone number, so the user entered the phone number instead of its representing code. Is there a way to accept such...

I think it would be reasonable to standardize the previous entered data from using different delimiters ',' or'&' or '/' or '-' into one single ','. Then, we can apply the view you supplied. If this is way is easier, then I will need to know how to replace the different delimiter into one...

Yes, the select you provided is working for TEST. It seems that this error comes from unexpected data in the field like this: Dave PARIS11,30,CANNES40,C22,TOULOUSE1 Amr PARIS11,30,CANNES40,C22,TOULOUSE1 Barb CAEN14,37,55,DIJON,21,D33,LIMOGES12 Tarek...

I am getting ORA-01722: Invalid number, after a while from quering the region_view. Any idea on how to debug the error?

Regarding the sys.all_tab_columns table. I found this table present in the Oracle Application database and filled with many data. Should this table be used? Also, I am connecting to the database using APPS/APPS, while the schema used for this table is sys. Is this correct and should be kept...

Many thanks for your support. Please allow me some time to test. I just have one question regarding the sample output above. I can see 18 Rows selected, while the expected output should be 21. Am I right?

The actual name of the table is MTL_TRANS. This is actually a VIEW. The field representing the employee is SUBINVENTORY_NAME and it a branch under ORGANIZATION_NAME. That is the ORGANIZATION_NAME has many SUBINVENTORY_NAME. Each employee is represented by a SUBINVENTORY_NAME that has many items...

The describe output is (2 columns): Name Type INVENTORY_ITEM_ID NUMBER ACTUAL_COST NUMBER TRANSACTION_ID NUMBER TRANSACTION_TYPE_NAME VARCHAR2(30) TRANSACTION_ACTION VARCHAR2(29) TRANSACTION_SOURCE_TYPE_NAME VARCHAR2(30) TRANSACTION_SOURCE_ID NUMBER...

Sorry for my late reply. 1- All of the regions from each of the Maintenance employees, along with the source employee's employee ID. 2- It is true for both that Region must not be null and the first subfield is always a complete region. For null regions, this does not belong to the required...

Yes, I am GMT+2. I may still have a week to finish this task. Please let know when you can provide a solution so that I may reschedule my plans.

The problem of correcting old data is that the tables belong to the Oracle Application (the ERP package). I am not sure this could be done because each line in the transaction table is unique and this correction will need specific identifier for each row which I do not know from where the...

I can put the rule as follows: 1- sub-fields separator is ',' (comma). 2- if sub-field data begins with character and total length greater than 4, this is a complete information. 3- if sub-field data begins with character and total length equal or less than 4, this must be concatenated with the...