From 67a2bcbdcc98c97de512b23b574a7255f2d026b0 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 22:12:58 +0300
Subject: [PATCH 001/126] Create README.md

---
 database-standards-guidelines/README.md | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 database-standards-guidelines/README.md

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
new file mode 100644
index 0000000..4d3a358
--- /dev/null
+++ b/database-standards-guidelines/README.md
@@ -0,0 +1 @@
+# Database Standards Guidelines

From cb47025c73634c4abe4ee6f506c5c165b2166844 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 22:15:42 +0300
Subject: [PATCH 002/126] Add "Database Standards Guidelines" Link

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 96be5cf..696a2d5 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@
 
 - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/customization-standards-guidelines">**Customization Standards Guidelines**</a>
 - Oracle AOL Standards Guidelines
-- Database Standards Guidelines
+- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**Database Standards Guidelines**</a>
 - OA Framework Standards Guidelines
 - Report Standards Guidelines
 - Workflow Standards Guidelines

From 80a3c711ddabc55d52eb65d7cbb825cd898226ef Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 22:39:54 +0300
Subject: [PATCH 003/126] Add "General Syntax" section

---
 database-standards-guidelines/README.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 4d3a358..8bdd53c 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -1 +1,13 @@
 # Database Standards Guidelines
+
+- Create Database Custom Objects
+- Database Custom Objects Naming Conventions
+
+<br>
+
+## Create Database Custom Objects
+
+##### General Syntax 
+
+> **{custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]**
+

From 95fb59a2bac3c138a97c25aec800eca0b84cf38d Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 22:42:22 +0300
Subject: [PATCH 004/126] add "Syntax Elements" section

---
 database-standards-guidelines/README.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 8bdd53c..18b7fab 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -11,3 +11,15 @@
 
 > **{custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]**
 
+<br>
+
+##### Syntax Elements
+The **Syntax Elements** section that presents elements syntax and describes it.
+ | SEQ | Element Syntax    | Element Name                  | Description |
+ | :-: | :---              | :--                           | :--------   |
+ | 1   | {custom_schema}   | Custom Database Schema        | Database custom ORACLE schema name |
+ | 1   | {separator}       | Separator                     | Must use underscore “_” in database objects|
+ | 1   | {app_short_name}  | Application/Product Short Name| This is the application/product short name |
+ | 1   | {prefix}          | Prefix                        |  |
+ | 1   | {object_name}     | Database Object Name          |  |
+ | 1   | {suffix}          | Suffix                        |  |

From 4e600c499b9866cf7b7698289c76b00e18ba38a4 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 22:48:03 +0300
Subject: [PATCH 005/126] Add "General Standards" section

---
 database-standards-guidelines/README.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 18b7fab..f670afb 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -23,3 +23,15 @@ The **Syntax Elements** section that presents elements syntax and describes it.
  | 1   | {prefix}          | Prefix                        |  |
  | 1   | {object_name}     | Database Object Name          |  |
  | 1   | {suffix}          | Suffix                        |  |
+
+<br>
+
+
+### General Standards
+- Never modify Oracle standard database objects.
+- In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
+- Include header information when you create your objects.
+- You must follow standard naming conventions for creating new database objects.
+- You must create new tables, sequences, and types, in the custom schema.
+- You must create new views and package objects in the APPS schema.
+- You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.

From 64c8567c4c190377afb119305a92abc6bc4e3da1 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 22:52:30 +0300
Subject: [PATCH 006/126] Reorder "General Standards" points

---
 database-standards-guidelines/README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index f670afb..bbac735 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -29,9 +29,10 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ### General Standards
 - Never modify Oracle standard database objects.
-- In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
-- Include header information when you create your objects.
 - You must follow standard naming conventions for creating new database objects.
 - You must create new tables, sequences, and types, in the custom schema.
 - You must create new views and package objects in the APPS schema.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
+- In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
+- Include header information when you create your objects.
+

From 1218826feacde8d4fe8027dd322ca826cfc1a8e3 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 22:59:42 +0300
Subject: [PATCH 007/126] Add "Header Information" reference

---
 database-standards-guidelines/README.md | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index bbac735..59cd154 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -34,5 +34,24 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You must create new views and package objects in the APPS schema.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
 - In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
-- Include header information when you create your objects.
+- Include header information[^1] when you create your objects.
 
+<br>
+
+###### [^1]: Header Information
+
+```SQL
+/*
+ Name: XXD Create GL Journals
+ Purpose: This is the main package to create GL journals
+ Arguments
+  Arg1 Describe arg1
+  Arg2 Describe arg2
+ Notes
+  1. Special usage notes
+  2. Special usage notes
+ History
+ 13–NOV–2022 Ahmed Demasy Created
+*/
+
+```

From 14dd9c2d02cb4e124006c5b51028fc0be222670b Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 23:01:14 +0300
Subject: [PATCH 008/126] Add [^1] reference

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 59cd154..b7e5713 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -34,7 +34,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You must create new views and package objects in the APPS schema.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
 - In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
-- Include header information[^1] when you create your objects.
+- Include header information when you create your objects. [^1]
 
 <br>
 

From fc6aea37c45ddb63919aa144247c716d871d035b Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 23:03:05 +0300
Subject: [PATCH 009/126] Update "Header Information" reference

---
 database-standards-guidelines/README.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index b7e5713..768f618 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -34,11 +34,13 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You must create new views and package objects in the APPS schema.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
 - In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
-- Include header information when you create your objects. [^1]
+- Include header information[^1] when you create your objects.
 
 <br>
 
-###### [^1]: Header Information
+[^1]:
+
+###### Header Information
 
 ```SQL
 /*

From df076df8050064362e842d8193112d131d8c916b Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 23:08:09 +0300
Subject: [PATCH 010/126] Update "Header Information"

---
 database-standards-guidelines/README.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 768f618..125cfa3 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -34,12 +34,10 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You must create new views and package objects in the APPS schema.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
 - In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
-- Include header information[^1] when you create your objects.
+- Include header information when you create your objects.
 
 <br>
 
-[^1]:
-
 ###### Header Information
 
 ```SQL
@@ -55,5 +53,4 @@ The **Syntax Elements** section that presents elements syntax and describes it.
  History
  13–NOV–2022 Ahmed Demasy Created
 */
-
 ```

From b96b9a681bd407f27020a2b74520627111376eb7 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 23:47:33 +0300
Subject: [PATCH 011/126] Add "Oracle Applications Tables Standards" section

---
 database-standards-guidelines/README.md | 40 +++++++++++++++++++++++++
 1 file changed, 40 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 125cfa3..b38bc1f 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -54,3 +54,43 @@ The **Syntax Elements** section that presents elements syntax and describes it.
  13–NOV–2022 Ahmed Demasy Created
 */
 ```
+
+<br>
+
+## Oracle Applications Tables Standards
+
+##### Syntax 
+
+> {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
+
+<br>
+
+### Table Naming Convention
+
+ | SEQ  | Object Name         | Length | Schema | Prefix | Suffix | Example |
+ | :-:  | :----               | :-:    | :--:   | :---   | :---   | :----   |
+ | 1    | Table               | 20     | XXR    |        |        |  |
+ | 2    | Temporary Table     | 20     | XXR    |        | \_tmp  |  |
+ | 3    | Data Upload Table   | 20     | XXR    | tmp_   |        | For data upload and migrations ONLY | 
+ 
+<br>
+
+### Table Naming Standards
+
+- The custom table name must start with a custom schema name such as "XXD". [^1]
+- The object name “{object_name}“ should be plural.
+- The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
+- You must place the new tables in the custom ORACLE schema and grant privileges to the APPS schema.
+- You must create private synonyms for custom tables in APPS.
+- You must add special WHO columns to your tables.
+- You must add concurrent program WHO Columns to your table.
+- You must create the table handler package for each table.
+- New tables containing Flex-Fields or Oracle Alert columns must be registered with Oracle Application Object Library.
+- You should register your custom tables with Oracle AOL using the table registration API called AD_DD.
+  - AD_DD. REGISTER_TABLE
+  - AD_DD. REGISTER_COLUMN
+
+<br>
+
+##### References
+[^1]: "**XXD**" is the custom database ORACLE schema association to the custom application called "Demasy Custom Applications".

From b5aec85f0ca1623e3caf84d195de19991bc8a074 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Thu, 15 Sep 2022 23:49:28 +0300
Subject: [PATCH 012/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index b38bc1f..12b827d 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -27,7 +27,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 <br>
 
 
-### General Standards
+## General Standards
 - Never modify Oracle standard database objects.
 - You must follow standard naming conventions for creating new database objects.
 - You must create new tables, sequences, and types, in the custom schema.

From 09b8e93ab1292ddd3223891ca3bafffff99875d0 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:05:08 +0300
Subject: [PATCH 013/126] Update "Table Naming Convention"

---
 database-standards-guidelines/README.md | 21 ++++++++++++++-------
 1 file changed, 14 insertions(+), 7 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 12b827d..5586915 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -67,17 +67,17 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ### Table Naming Convention
 
- | SEQ  | Object Name         | Length | Schema | Prefix | Suffix | Example |
- | :-:  | :----               | :-:    | :--:   | :---   | :---   | :----   |
- | 1    | Table               | 20     | XXR    |        |        |  |
- | 2    | Temporary Table     | 20     | XXR    |        | \_tmp  |  |
- | 3    | Data Upload Table   | 20     | XXR    | tmp_   |        | For data upload and migrations ONLY | 
+ | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
+ | :-:  | :----                  | :-:    | :--:   | :---   | :---   | :----   |
+ | 1    | Table                  | 20     | XXR    |        |        | XXD_PO_LC_DOCUMENTS |
+ | 2    | Temporary Table        | 20     | XXR    |        | \_tmp  | XXD_PO_LC_DOCS_TMP |
+ | 3    | Data Upload Table [^1] | 20     | XXR    | tmp_   |        | XXD_TMP_LC_DOCS | 
  
 <br>
 
 ### Table Naming Standards
 
-- The custom table name must start with a custom schema name such as "XXD". [^1]
+- The custom table name must start with a custom schema name such as "XXD". [^2]
 - The object name “{object_name}“ should be plural.
 - The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
 - You must place the new tables in the custom ORACLE schema and grant privileges to the APPS schema.
@@ -90,7 +90,14 @@ The **Syntax Elements** section that presents elements syntax and describes it.
   - AD_DD. REGISTER_TABLE
   - AD_DD. REGISTER_COLUMN
 
+<br>
+
+ | Better   | Bad        |
+ | :---  | :---        |
+ | - XXD_PO_LC_DOCUMENTS | - XXD_PO_LC_DOCUMENT <br> - PO_LC_DOCUMENTS       |
+
 <br>
 
 ##### References
-[^1]: "**XXD**" is the custom database ORACLE schema association to the custom application called "Demasy Custom Applications".
+[^2]: "**XXD**" is the custom database ORACLE schema association to the custom application called "Demasy Custom Applications".
+[^1]: This is a custom table for data upload and migrations **only**.

From ff10085dc832033eb01d03c9a834cd6729c1f337 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:09:01 +0300
Subject: [PATCH 014/126] Update "Syntax Elements"

---
 database-standards-guidelines/README.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 5586915..95ebaf5 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -18,11 +18,11 @@ The **Syntax Elements** section that presents elements syntax and describes it.
  | SEQ | Element Syntax    | Element Name                  | Description |
  | :-: | :---              | :--                           | :--------   |
  | 1   | {custom_schema}   | Custom Database Schema        | Database custom ORACLE schema name |
- | 1   | {separator}       | Separator                     | Must use underscore “_” in database objects|
- | 1   | {app_short_name}  | Application/Product Short Name| This is the application/product short name |
- | 1   | {prefix}          | Prefix                        |  |
- | 1   | {object_name}     | Database Object Name          |  |
- | 1   | {suffix}          | Suffix                        |  |
+ | 2   | {separator}       | Separator                     | Must use underscore “_” in database objects|
+ | 3   | {app_short_name}  | Application/Product Short Name| This is the application/product short name |
+ | 4   | {prefix}          | Prefix                        |  |
+ | 5   | {object_name}     | Database Object Name          |  |
+ | 6   | {suffix}          | Suffix                        |  |
 
 <br>
 

From 7a4a4642b23021f4cd45547e0f5cef3bbfc46c72 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:16:42 +0300
Subject: [PATCH 015/126] Add "General Syntax"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 95ebaf5..3d879cc 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -9,7 +9,7 @@
 
 ##### General Syntax 
 
-> **{custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]**
+> {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
 
 <br>
 

From 97b0633ff926d32bbefc282ac3f52af9d426d504 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:23:22 +0300
Subject: [PATCH 016/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 3d879cc..d1515eb 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -1,11 +1,17 @@
 # Database Standards Guidelines
 
 - Create Database Custom Objects
+  - General Standards
+  - Oracle Applications Tables Standards
+  - Sequences Standards
+  - View Standards
+  - Packages Standards
 - Database Custom Objects Naming Conventions
 
 <br>
 
-## Create Database Custom Objects
+## General Standards
+
 
 ##### General Syntax 
 
@@ -26,8 +32,8 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 <br>
 
+### General Standards
 
-## General Standards
 - Never modify Oracle standard database objects.
 - You must follow standard naming conventions for creating new database objects.
 - You must create new tables, sequences, and types, in the custom schema.

From 335e56977d634bad3e70f38f4960462f4999b644 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:25:30 +0300
Subject: [PATCH 017/126] Update "General Standards" link

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index d1515eb..ace50e9 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -1,7 +1,7 @@
 # Database Standards Guidelines
 
 - Create Database Custom Objects
-  - General Standards
+  - <a href="#general-standards">**General Standards**</a>
   - Oracle Applications Tables Standards
   - Sequences Standards
   - View Standards

From 26b8b307cfb906122586166ec130320e834c5d50 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:27:22 +0300
Subject: [PATCH 018/126] Add "Oracle Applications Tables Standards" link

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index ace50e9..230a2c1 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -2,7 +2,7 @@
 
 - Create Database Custom Objects
   - <a href="#general-standards">**General Standards**</a>
-  - Oracle Applications Tables Standards
+  - <a href="#oracle-applications-tables-standards">**Oracle Applications Tables Standards**</a>
   - Sequences Standards
   - View Standards
   - Packages Standards

From b702c3c02b903c65bd011c25b86f8dc1a8958a0b Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:30:57 +0300
Subject: [PATCH 019/126] Add "General Standards" content

---
 database-standards-guidelines/README.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 230a2c1..2ace3b5 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -12,8 +12,15 @@
 
 ## General Standards
 
+- General Syntax
+- General Standards
 
-##### General Syntax 
+<br>
+
+### General Syntax
+
+
+##### Syntax 
 
 > {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
 

From b831846908280bb199835e8248425fd476b2e1eb Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:32:39 +0300
Subject: [PATCH 020/126] Update "Header Information"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 2ace3b5..c7da446 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -64,7 +64,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
   1. Special usage notes
   2. Special usage notes
  History
- 13–NOV–2022 Ahmed Demasy Created
+ 13–NOV–1986 Ahmed Demasy Created
 */
 ```
 

From 47c9ab1df33e7c7e4d8c28a3458e52fdc05d0328 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:34:00 +0300
Subject: [PATCH 021/126] Add "Table Naming Example"

---
 database-standards-guidelines/README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index c7da446..7f21f4a 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -102,9 +102,11 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You should register your custom tables with Oracle AOL using the table registration API called AD_DD.
   - AD_DD. REGISTER_TABLE
   - AD_DD. REGISTER_COLUMN
-
+  
 <br>
 
+### Table Naming Example
+
  | Better   | Bad        |
  | :---  | :---        |
  | - XXD_PO_LC_DOCUMENTS | - XXD_PO_LC_DOCUMENT <br> - PO_LC_DOCUMENTS       |

From e6fee48b64d0873b253daeaadbe19419ef4567b1 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:36:11 +0300
Subject: [PATCH 022/126] Add "Tables Standards" content

---
 database-standards-guidelines/README.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 7f21f4a..9e64ba5 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -72,6 +72,11 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ## Oracle Applications Tables Standards
 
+- Table Naming Syntax
+- Table Naming Convention
+- Table Naming Standards
+- Table Naming Example
+
 ##### Syntax 
 
 > {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]

From ffbaa1a1eef11eb31e265833d27401454bc249c9 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:38:54 +0300
Subject: [PATCH 023/126] add "Table Syntax"

---
 database-standards-guidelines/README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 9e64ba5..6a30685 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -70,13 +70,17 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 <br>
 
-## Oracle Applications Tables Standards
+## Tables Standards
 
 - Table Naming Syntax
 - Table Naming Convention
 - Table Naming Standards
 - Table Naming Example
 
+<br>
+
+### Table Syntax
+
 ##### Syntax 
 
 > {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]

From 1e59694e131e4801ff7e3b4f450c3b66af7b628d Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:43:11 +0300
Subject: [PATCH 024/126] Update "Tables Standards" content links

---
 database-standards-guidelines/README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 6a30685..e6fbf9e 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -72,10 +72,10 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ## Tables Standards
 
-- Table Naming Syntax
-- Table Naming Convention
-- Table Naming Standards
-- Table Naming Example
+- <a href="#table-syntax">**Table Naming Syntax**</a>
+- <a href="#table-naming-convention">**Table Naming Convention**</a>
+- <a href="#table-naming-standards">**Table Naming Standards**</a>
+- <a href="#table-naming-example">**Table Naming Example**</a>
 
 <br>
 

From f54157faefa5c0de9dc0b60beaadf58f2d424b7c Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 00:46:33 +0300
Subject: [PATCH 025/126] Update "Tables Standards"

---
 database-standards-guidelines/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index e6fbf9e..c1fb7f1 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -2,9 +2,9 @@
 
 - Create Database Custom Objects
   - <a href="#general-standards">**General Standards**</a>
-  - <a href="#oracle-applications-tables-standards">**Oracle Applications Tables Standards**</a>
+  - <a href="#tables-standards">**Tables Standards**</a>
   - Sequences Standards
-  - View Standards
+  - Views Standards
   - Packages Standards
 - Database Custom Objects Naming Conventions
 

From d9c2f9f0624d1c7016ff383eeeee45176e19f18c Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:21:43 +0300
Subject: [PATCH 026/126] Add "WHO columns" and "Concurrent Program Columns"

---
 database-standards-guidelines/README.md | 25 ++++++++++++++++++++++++-
 1 file changed, 24 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index c1fb7f1..344d8bc 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -111,7 +111,30 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You should register your custom tables with Oracle AOL using the table registration API called AD_DD.
   - AD_DD. REGISTER_TABLE
   - AD_DD. REGISTER_COLUMN
-  
+
+<br>
+
+##### WHO columns
+
+ | Column Name       | Type       | Null?    | Foreign Key? | Value | 
+ | :--               | :----      | :-:      | :--          | :---   | 
+ | CREATED_BY        | NUMBER(15) | NOT NULL | FND_USER     | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) |
+ | CREATION_DATE     | DATE       | NOT NULL |              | SYSDATE |
+ | LAST_UPDATED_BY   | NUMBER(15) | NOT NULL |              | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) | 
+ | LAST_UPDATE_DATE  | DATE       | NOT NULL |              | SYSDATE |
+ | LAST_UPDATE_LOGIN | NUMBER(15) |          |              | TO_NUMBER (FND_ PROFILE.VALUE (’LOGIN_ ID’)) |
+ 
+<br>
+
+##### Concurrent Program WHO Columns
+
+ | Column Name             | Type       | Null? | Foreign Key to Table?   |  
+ | :--                     | :----      | :-:   | :--                     | 
+ | REQUEST_ID              | NUMBER(15) |       | FND_CONCURRENT_REQUESTS | 
+ | PROGRAM_APPLICATION_ ID | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
+ | PROGRAM_ID              | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
+ | PROGRAM_UPDATE_DATE     | DATE.      |       | ROGRAM_UPDATE_DATE      | 
+ 
 <br>
 
 ### Table Naming Example

From 9622b407ad0690951207cb59b819cec4488ab78c Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:22:33 +0300
Subject: [PATCH 027/126] Update "Concurrent Program WHO Columns"

---
 database-standards-guidelines/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 344d8bc..2fb89c2 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -131,9 +131,9 @@ The **Syntax Elements** section that presents elements syntax and describes it.
  | Column Name             | Type       | Null? | Foreign Key to Table?   |  
  | :--                     | :----      | :-:   | :--                     | 
  | REQUEST_ID              | NUMBER(15) |       | FND_CONCURRENT_REQUESTS | 
- | PROGRAM_APPLICATION_ ID | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
+ | PROGRAM_APPLICATION_ID  | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
  | PROGRAM_ID              | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
- | PROGRAM_UPDATE_DATE     | DATE.      |       | ROGRAM_UPDATE_DATE      | 
+ | PROGRAM_UPDATE_DATE     | DATE       |       | ROGRAM_UPDATE_DATE      | 
  
 <br>
 

From 360be271b9429a6c412a96270bce5c685f005ac3 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:25:17 +0300
Subject: [PATCH 028/126] Add "Table Naming Convention"

---
 database-standards-guidelines/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 2fb89c2..fff7b71 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -91,9 +91,9 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
  | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
  | :-:  | :----                  | :-:    | :--:   | :---   | :---   | :----   |
- | 1    | Table                  | 20     | XXR    |        |        | XXD_PO_LC_DOCUMENTS |
- | 2    | Temporary Table        | 20     | XXR    |        | \_tmp  | XXD_PO_LC_DOCS_TMP |
- | 3    | Data Upload Table [^1] | 20     | XXR    | tmp_   |        | XXD_TMP_LC_DOCS | 
+ | 1    | Table                  | 20     | XXD    |        |        | XXD_PO_LC_DOCUMENTS |
+ | 2    | Temporary Table        | 20     | XXD    |        | \_TMP  | XXD_PO_LC_DOCS_TMP |
+ | 3    | Data Upload Table [^1] | 20     | XXD    | TMP_   |        | XXD_TMP_LC_DOCS | 
  
 <br>
 

From c14523ccec57e3149679d18bea8d433dd67fb500 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:28:01 +0300
Subject: [PATCH 029/126] Update "Tables Standards"

---
 database-standards-guidelines/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index fff7b71..63fce85 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -72,14 +72,14 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ## Tables Standards
 
-- <a href="#table-syntax">**Table Naming Syntax**</a>
+- <a href="#table-naming-syntax">**Table Naming Syntax**</a>
 - <a href="#table-naming-convention">**Table Naming Convention**</a>
 - <a href="#table-naming-standards">**Table Naming Standards**</a>
 - <a href="#table-naming-example">**Table Naming Example**</a>
 
 <br>
 
-### Table Syntax
+### Table Naming Syntax
 
 ##### Syntax 
 

From 82b878c2bf643f15ded91238b176917176abeb45 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:31:19 +0300
Subject: [PATCH 030/126] Add "General Standards"

---
 database-standards-guidelines/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 63fce85..ff2711e 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -12,8 +12,8 @@
 
 ## General Standards
 
-- General Syntax
-- General Standards
+- <a href="#general-syntax">**General Syntax**</a>
+- <a href="#">**General Standards**</a>
 
 <br>
 

From 110d08da206cce5ce7f260a74e70e2910842e2f0 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:34:34 +0300
Subject: [PATCH 031/126] Add "Sequences Standards" content

---
 database-standards-guidelines/README.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index ff2711e..5e9b092 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -143,6 +143,16 @@ The **Syntax Elements** section that presents elements syntax and describes it.
  | :---  | :---        |
  | - XXD_PO_LC_DOCUMENTS | - XXD_PO_LC_DOCUMENT <br> - PO_LC_DOCUMENTS       |
 
+<br>
+
+## Sequences Standards
+
+- Sequence Naming Syntax
+- Sequence Naming Convention
+- Sequence Naming Standards
+- Sequence Naming Example
+
+
 <br>
 
 ##### References

From 90172334189a2f808e56221f18077aba43252873 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:43:59 +0300
Subject: [PATCH 032/126] Add "Sequences Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 5e9b092..4a17853 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -150,7 +150,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - Sequence Naming Syntax
 - Sequence Naming Convention
 - Sequence Naming Standards
-- Sequence Naming Example
+- Sequence Naming Examples
 
 
 <br>

From 3809d7800990e7cfd76e545248ba3ec08b0b9141 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:47:11 +0300
Subject: [PATCH 033/126] Update "Sequences Standards"

---
 database-standards-guidelines/README.md | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 4a17853..d14a6fd 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -147,10 +147,20 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ## Sequences Standards
 
-- Sequence Naming Syntax
-- Sequence Naming Convention
-- Sequence Naming Standards
-- Sequence Naming Examples
+- <a href="#">**Sequence Naming Syntax**</a>
+- <a href="#">**Sequence Naming Convention**</a>
+- <a href="#">**Sequence Naming Standards**</a>
+- <a href="#">**Sequence Naming Examples**</a>
+
+<br>
+
+### Sequence Naming Syntax
+
+### Sequence Naming Convention
+
+### Sequence Naming Standards
+
+### Sequence Naming Examples
 
 
 <br>

From de198e8902acff8afd23408e878590956b326cbe Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:48:43 +0300
Subject: [PATCH 034/126] Update "Sequences Standards" Links

---
 database-standards-guidelines/README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index d14a6fd..225f08e 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -147,10 +147,10 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ## Sequences Standards
 
-- <a href="#">**Sequence Naming Syntax**</a>
-- <a href="#">**Sequence Naming Convention**</a>
-- <a href="#">**Sequence Naming Standards**</a>
-- <a href="#">**Sequence Naming Examples**</a>
+- <a href="#sequence-naming-syntax">**Sequence Naming Syntax**</a>
+- <a href="#sequence-naming-convention">**Sequence Naming Convention**</a>
+- <a href="#sequence-naming-standards">**Sequence Naming Standards**</a>
+- <a href="#sequence-naming-examples">**Sequence Naming Examples**</a>
 
 <br>
 

From 83fa2f614a87f2b55bc190bcd0983e9009c849a4 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:51:26 +0300
Subject: [PATCH 035/126] Update "Sequences Standards" link

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 225f08e..f6dbce0 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -3,7 +3,7 @@
 - Create Database Custom Objects
   - <a href="#general-standards">**General Standards**</a>
   - <a href="#tables-standards">**Tables Standards**</a>
-  - Sequences Standards
+  - <a href="#sequences-standards">**Sequences Standards**</a>
   - Views Standards
   - Packages Standards
 - Database Custom Objects Naming Conventions

From 284e13ac129c9a333006d09ca6b6335502e1954a Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:53:13 +0300
Subject: [PATCH 036/126] make "XXD" bold

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index f6dbce0..9bdebc1 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -99,7 +99,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ### Table Naming Standards
 
-- The custom table name must start with a custom schema name such as "XXD". [^2]
+- The custom table name must start with a custom schema name such as "**XXD**". [^2]
 - The object name “{object_name}“ should be plural.
 - The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
 - You must place the new tables in the custom ORACLE schema and grant privileges to the APPS schema.

From ecb0614d811ba6725e54a4f34ba6cf10d20fc1d2 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 01:56:53 +0300
Subject: [PATCH 037/126] Update "{object_name}" format

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 9bdebc1..1188ac2 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -100,7 +100,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 ### Table Naming Standards
 
 - The custom table name must start with a custom schema name such as "**XXD**". [^2]
-- The object name “{object_name}“ should be plural.
+- The object name “*{object_name}*“ should be plural.
 - The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
 - You must place the new tables in the custom ORACLE schema and grant privileges to the APPS schema.
 - You must create private synonyms for custom tables in APPS.

From 5765e8d05d2c3c7b9db8e773cfa7f72a77b88b09 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 02:01:44 +0300
Subject: [PATCH 038/126] Format "Element Syntax"

---
 database-standards-guidelines/README.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 1188ac2..6d26c73 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -28,14 +28,14 @@
 
 ##### Syntax Elements
 The **Syntax Elements** section that presents elements syntax and describes it.
- | SEQ | Element Syntax    | Element Name                  | Description |
- | :-: | :---              | :--                           | :--------   |
- | 1   | {custom_schema}   | Custom Database Schema        | Database custom ORACLE schema name |
- | 2   | {separator}       | Separator                     | Must use underscore “_” in database objects|
- | 3   | {app_short_name}  | Application/Product Short Name| This is the application/product short name |
- | 4   | {prefix}          | Prefix                        |  |
- | 5   | {object_name}     | Database Object Name          |  |
- | 6   | {suffix}          | Suffix                        |  |
+ | SEQ | Element Syntax      | Element Name                  | Description |
+ | :-: | :---                | :--                           | :--------   |
+ | 1   | *{custom_schema}*   | Custom Database Schema        | Database custom ORACLE schema name |
+ | 2   | *{separator}*       | Separator                     | Must use underscore “_” in database objects|
+ | 3   | *{app_short_name}*  | Application/Product Short Name| This is the application/product short name |
+ | 4   | *{prefix}*          | Prefix                        |  |
+ | 5   | *{object_name}*     | Database Object Name          |  |
+ | 6   | *{suffix}*          | Suffix                        |  |
 
 <br>
 

From 027f2c991fe82c68803005ff1506118e0974d087 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 02:07:50 +0300
Subject: [PATCH 039/126] Format "Create Database Custom Objects" title

---
 database-standards-guidelines/README.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 6d26c73..cb8e650 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -1,6 +1,6 @@
 # Database Standards Guidelines
 
-- Create Database Custom Objects
+- **Create Database Custom Objects**
   - <a href="#general-standards">**General Standards**</a>
   - <a href="#tables-standards">**Tables Standards**</a>
   - <a href="#sequences-standards">**Sequences Standards**</a>
@@ -145,6 +145,10 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 <br>
 
+___
+
+<br>
+
 ## Sequences Standards
 
 - <a href="#sequence-naming-syntax">**Sequence Naming Syntax**</a>
@@ -162,6 +166,8 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ### Sequence Naming Examples
 
+___
+
 
 <br>
 

From 7e694900585b8f1f66d25129d799affed1aae2a0 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 02:18:29 +0300
Subject: [PATCH 040/126] Add "Views Standards"

---
 database-standards-guidelines/README.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index cb8e650..ee0ae57 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -169,6 +169,30 @@ ___
 ___
 
 
+<br>
+
+## Views Standards
+
+
+- <a href="#views-naming-syntax">**Views Naming Syntax**</a>
+- <a href="#views-naming-convention">**Views Naming Convention**</a>
+- <a href="#views-naming-standards">**Views Naming Standards**</a>
+- <a href="#views-naming-examples">**Views Naming Examples**</a>
+
+<br>
+
+### Views Naming Syntax
+
+### Views Naming Convention
+
+### Views Naming Standards
+
+### Views Naming Examples
+
+___
+
+
+
 <br>
 
 ##### References

From 5f683c7bc6ff8cd3e4e441ed1d6f3648209d1ae3 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 02:21:53 +0300
Subject: [PATCH 041/126] Add "Packages Standards"

---
 database-standards-guidelines/README.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index ee0ae57..f17efd0 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -191,6 +191,29 @@ ___
 
 ___
 
+<br>
+
+## Packages Standards
+
+
+- <a href="#packages-naming-syntax">**Packages Naming Syntax**</a>
+- <a href="#packages-naming-convention">**Packages Naming Convention**</a>
+- <a href="#packages-naming-standards">**Packages Naming Standards**</a>
+- <a href="#packages-naming-examples">**Packages Naming Examples**</a>
+
+<br>
+
+### Packages Naming Syntax
+
+### Packages Naming Convention
+
+### Packages Naming Standards
+
+### Packages Naming Examples
+
+___
+
+
 
 
 <br>

From 01b46fd11390b586ab94341f842f9fc95fe186a3 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 14:52:16 +0300
Subject: [PATCH 042/126] Update "Create Database Custom Objects" content

---
 database-standards-guidelines/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index f17efd0..cdf0efb 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -4,8 +4,8 @@
   - <a href="#general-standards">**General Standards**</a>
   - <a href="#tables-standards">**Tables Standards**</a>
   - <a href="#sequences-standards">**Sequences Standards**</a>
-  - Views Standards
-  - Packages Standards
+  - <a href="#views-standards">**Views Standards**</a>
+  - <a href="#packages-standards">**Packages Standards**</a>
 - Database Custom Objects Naming Conventions
 
 <br>

From 39aa154155ea8cd9af105ce889f99d0c679ae08a Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:16:23 +0300
Subject: [PATCH 043/126] Add "Sequence Naming Standards"

---
 database-standards-guidelines/README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index cdf0efb..9147780 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -163,6 +163,12 @@ ___
 ### Sequence Naming Convention
 
 ### Sequence Naming Standards
+- The Sequence name “*{object_name}*“ should be 30 characters or less and end with "_SEQ".
+- Use each sequence to supply unique ID values for one column of one table.
+- Do not design sequences that wrap using the CYCLE option or have limited ranges using MAXVALUE.
+- Use a NUMBER datatype to store sequence values within PL/SQL.
+- Do Not Use the FND_UNIQUE_IDENTIFIER_CONTROL Table.
+
 
 ### Sequence Naming Examples
 

From 8279e147d935da937ddcf46fb8aa10fed579edab Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:17:12 +0300
Subject: [PATCH 044/126] Update "Sequence Naming Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 9147780..34a468b 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -163,7 +163,7 @@ ___
 ### Sequence Naming Convention
 
 ### Sequence Naming Standards
-- The Sequence name “*{object_name}*“ should be 30 characters or less and end with "_SEQ".
+- The sequence name “*{object_name}*“ should be 30 characters or less and end with "_SEQ".
 - Use each sequence to supply unique ID values for one column of one table.
 - Do not design sequences that wrap using the CYCLE option or have limited ranges using MAXVALUE.
 - Use a NUMBER datatype to store sequence values within PL/SQL.

From 56b49801b16b57f8f96c6f3e6ed8dbe0271c35fa Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:31:23 +0300
Subject: [PATCH 045/126] Add "Views Naming Standards"

---
 database-standards-guidelines/README.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 34a468b..bc4c1e6 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -192,6 +192,12 @@ ___
 ### Views Naming Convention
 
 ### Views Naming Standards
+- The first column your view should select is the ROWID for the root table, and the view should alias it to ROW_ID.
+- You only need to include the ROWID column if an Oracle Forms block is based on this view.
+- The view name “*{object_name}*“ should be 30 characters or less and end with "_V" for view and "_VM" for materialized views.
+
+
+<br>
 
 ### Views Naming Examples
 
@@ -215,6 +221,8 @@ ___
 
 ### Packages Naming Standards
 
+<br>
+
 ### Packages Naming Examples
 
 ___

From 2314a19eedf47757571b14c8c99435bd6c6bf675 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:32:03 +0300
Subject: [PATCH 046/126] update "Views Naming Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index bc4c1e6..4bc8cf4 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -192,9 +192,9 @@ ___
 ### Views Naming Convention
 
 ### Views Naming Standards
+- The view name “*{object_name}*“ should be 30 characters or less and end with "_V" for view and "_VM" for materialized views.
 - The first column your view should select is the ROWID for the root table, and the view should alias it to ROW_ID.
 - You only need to include the ROWID column if an Oracle Forms block is based on this view.
-- The view name “*{object_name}*“ should be 30 characters or less and end with "_V" for view and "_VM" for materialized views.
 
 
 <br>

From efe0c2e7b5f35e1634f412a9ec594f773615adb9 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:37:12 +0300
Subject: [PATCH 047/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 4bc8cf4..71faf53 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -42,6 +42,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 ### General Standards
 
 - Never modify Oracle standard database objects.
+- The custom database objects must start with a **custom schema name** such as "XXD". [^1]
 - You must follow standard naming conventions for creating new database objects.
 - You must create new tables, sequences, and types, in the custom schema.
 - You must create new views and package objects in the APPS schema.
@@ -93,7 +94,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
  | :-:  | :----                  | :-:    | :--:   | :---   | :---   | :----   |
  | 1    | Table                  | 20     | XXD    |        |        | XXD_PO_LC_DOCUMENTS |
  | 2    | Temporary Table        | 20     | XXD    |        | \_TMP  | XXD_PO_LC_DOCS_TMP |
- | 3    | Data Upload Table [^1] | 20     | XXD    | TMP_   |        | XXD_TMP_LC_DOCS | 
+ | 3    | Data Upload Table [^2] | 20     | XXD    | TMP_   |        | XXD_TMP_LC_DOCS | 
  
 <br>
 
@@ -233,5 +234,5 @@ ___
 <br>
 
 ##### References
-[^2]: "**XXD**" is the custom database ORACLE schema association to the custom application called "Demasy Custom Applications".
-[^1]: This is a custom table for data upload and migrations **only**.
+[^1]: "**XXD**" is the custom database ORACLE schema association to the custom application called "Demasy Custom Applications".
+[^2]: This is a custom table for data upload and migrations **only**.

From 2ccde80b97b1a15c04a9e0abdf4d688f40bbe80e Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:40:25 +0300
Subject: [PATCH 048/126] Add new point in "General Standards"

---
 database-standards-guidelines/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 71faf53..eeeba71 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -46,6 +46,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You must follow standard naming conventions for creating new database objects.
 - You must create new tables, sequences, and types, in the custom schema.
 - You must create new views and package objects in the APPS schema.
+- Never create new stand alone functions and procedures. shold be implemented as part of a package.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
 - In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
 - Include header information when you create your objects.

From 5991ce9a8abd572fa76ef7d826109c2908772cbd Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:41:25 +0300
Subject: [PATCH 049/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index eeeba71..bec109c 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -42,11 +42,11 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 ### General Standards
 
 - Never modify Oracle standard database objects.
-- The custom database objects must start with a **custom schema name** such as "XXD". [^1]
 - You must follow standard naming conventions for creating new database objects.
+- The custom database objects must start with a **custom schema name** such as "XXD". [^1]
 - You must create new tables, sequences, and types, in the custom schema.
 - You must create new views and package objects in the APPS schema.
-- Never create new stand alone functions and procedures. shold be implemented as part of a package.
+- Never create new stand alone functions and procedures. should be implemented as part of a package.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
 - In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
 - Include header information when you create your objects.

From 5e2578f1e1bf2c427acc397d77154d345a9ebc5b Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:43:48 +0300
Subject: [PATCH 050/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index bec109c..b5c09a3 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -44,9 +44,9 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - Never modify Oracle standard database objects.
 - You must follow standard naming conventions for creating new database objects.
 - The custom database objects must start with a **custom schema name** such as "XXD". [^1]
-- You must create new tables, sequences, and types, in the custom schema.
-- You must create new views and package objects in the APPS schema.
-- Never create new stand alone functions and procedures. should be implemented as part of a package.
+- You must create new database tables, sequences, and types, in the custom schema.
+- You must create new database views and packages in the APPS schema.
+- Never create new stand-alone functions and procedures. Should be implemented as part of a package.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
 - In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
 - Include header information when you create your objects.

From 1f8cc04c703ab0eacd5bd1ab6f31478bae244afa Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:45:37 +0300
Subject: [PATCH 051/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index b5c09a3..ce3bee6 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -48,7 +48,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You must create new database views and packages in the APPS schema.
 - Never create new stand-alone functions and procedures. Should be implemented as part of a package.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
-- In general, make names meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
+- The database objet name must be meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
 - Include header information when you create your objects.
 
 <br>

From 31ba89d51bf60a29381a005ce006f9a0b90eb0d0 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 15:55:31 +0300
Subject: [PATCH 052/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index ce3bee6..8f1681d 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -43,12 +43,14 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 - Never modify Oracle standard database objects.
 - You must follow standard naming conventions for creating new database objects.
+- The database objet name "*{object_name}*" must be meaningful and brief.
+- Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the database objet name "*{object_name}*".
+- The application/product Short Name “*{app_short_name}*“ is a foreign key from Oracle standard table called "FND_APPLICATIONS".
 - The custom database objects must start with a **custom schema name** such as "XXD". [^1]
 - You must create new database tables, sequences, and types, in the custom schema.
 - You must create new database views and packages in the APPS schema.
 - Never create new stand-alone functions and procedures. Should be implemented as part of a package.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
-- The database objet name must be meaningful and brief. Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the name.
 - Include header information when you create your objects.
 
 <br>
@@ -101,7 +103,6 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ### Table Naming Standards
 
-- The custom table name must start with a custom schema name such as "**XXD**". [^2]
 - The object name “*{object_name}*“ should be plural.
 - The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
 - You must place the new tables in the custom ORACLE schema and grant privileges to the APPS schema.

From d71a556688553fe8568ab53d44f657c2b15d736d Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:00:37 +0300
Subject: [PATCH 053/126] Update "Table Naming Standards"

---
 database-standards-guidelines/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 8f1681d..235a8c6 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -107,8 +107,8 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
 - You must place the new tables in the custom ORACLE schema and grant privileges to the APPS schema.
 - You must create private synonyms for custom tables in APPS.
-- You must add special WHO columns to your tables.
-- You must add concurrent program WHO Columns to your table.
+- You should add special WHO columns to your tables.
+- You should add concurrent program WHO Columns to your table.
 - You must create the table handler package for each table.
 - New tables containing Flex-Fields or Oracle Alert columns must be registered with Oracle Application Object Library.
 - You should register your custom tables with Oracle AOL using the table registration API called AD_DD.

From ee430f1c17ded81d1129e351416e09882d05303c Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:03:11 +0300
Subject: [PATCH 054/126] Update "Table Naming Standards"

---
 database-standards-guidelines/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 235a8c6..9156215 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -103,6 +103,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ### Table Naming Standards
 
+- You MUST follow create database custom objects general standards.
 - The object name “*{object_name}*“ should be plural.
 - The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
 - You must place the new tables in the custom ORACLE schema and grant privileges to the APPS schema.

From f6ca11263f5ac8db14029bf845a3abe3dbc2e5b3 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:07:08 +0300
Subject: [PATCH 055/126] Add "descriptive flexfield attribute" point

---
 database-standards-guidelines/README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 9156215..cc56818 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -110,7 +110,8 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You must create private synonyms for custom tables in APPS.
 - You should add special WHO columns to your tables.
 - You should add concurrent program WHO Columns to your table.
-- You must create the table handler package for each table.
+- You should add concurrent program WHO Columns to your table.
+- You should add descriptive flexfield attribute Columns to your table.
 - New tables containing Flex-Fields or Oracle Alert columns must be registered with Oracle Application Object Library.
 - You should register your custom tables with Oracle AOL using the table registration API called AD_DD.
   - AD_DD. REGISTER_TABLE

From 0a0748c98addd580da1641e80308e753de382d72 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:08:08 +0300
Subject: [PATCH 056/126] update "descriptive flexfield"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index cc56818..ec013b0 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -111,7 +111,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You should add special WHO columns to your tables.
 - You should add concurrent program WHO Columns to your table.
 - You should add concurrent program WHO Columns to your table.
-- You should add descriptive flexfield attribute Columns to your table.
+- You should add descriptive flexfield (DFF) attribute Columns to your table.
 - New tables containing Flex-Fields or Oracle Alert columns must be registered with Oracle Application Object Library.
 - You should register your custom tables with Oracle AOL using the table registration API called AD_DD.
   - AD_DD. REGISTER_TABLE

From 2afde102777e9ff78205588fbe60ebe5b588474e Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:09:12 +0300
Subject: [PATCH 057/126] Update "References"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index ec013b0..2cc6b93 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -238,5 +238,5 @@ ___
 <br>
 
 ##### References
-[^1]: "**XXD**" is the custom database ORACLE schema association to the custom application called "Demasy Custom Applications".
+[^1]: "**XXD**" is the custom database ORACLE schema association to my custom application called "Demasy Custom Applications".
 [^2]: This is a custom table for data upload and migrations **only**.

From 27cf35357a24704704174f6503219fbf62541d04 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:22:46 +0300
Subject: [PATCH 058/126] Update "Sequence Naming Standards"

---
 database-standards-guidelines/README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 2cc6b93..3e2b09a 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -106,7 +106,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You MUST follow create database custom objects general standards.
 - The object name “*{object_name}*“ should be plural.
 - The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
-- You must place the new tables in the custom ORACLE schema and grant privileges to the APPS schema.
+- You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
 - You must create private synonyms for custom tables in APPS.
 - You should add special WHO columns to your tables.
 - You should add concurrent program WHO Columns to your table.
@@ -169,6 +169,7 @@ ___
 
 ### Sequence Naming Standards
 - The sequence name “*{object_name}*“ should be 30 characters or less and end with "_SEQ".
+- You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
 - Use each sequence to supply unique ID values for one column of one table.
 - Do not design sequences that wrap using the CYCLE option or have limited ranges using MAXVALUE.
 - Use a NUMBER datatype to store sequence values within PL/SQL.

From 7fadfc7baea68ede5fa1c13c403a9ecb67ca2b94 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:25:04 +0300
Subject: [PATCH 059/126] Update "Sequence Naming Standards"

---
 database-standards-guidelines/README.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 3e2b09a..63efb36 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -169,15 +169,18 @@ ___
 
 ### Sequence Naming Standards
 - The sequence name “*{object_name}*“ should be 30 characters or less and end with "_SEQ".
-- You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
+- You must place the new sequence in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
 - Use each sequence to supply unique ID values for one column of one table.
 - Do not design sequences that wrap using the CYCLE option or have limited ranges using MAXVALUE.
 - Use a NUMBER datatype to store sequence values within PL/SQL.
 - Do Not Use the FND_UNIQUE_IDENTIFIER_CONTROL Table.
 
+<br>
 
 ### Sequence Naming Examples
 
+<br>
+
 ___
 
 

From 36e6b75cd49cf5580ef7b9b509202e76cc9f4525 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:30:06 +0300
Subject: [PATCH 060/126] Update "Views Naming Convention"

---
 database-standards-guidelines/README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 63efb36..78acc23 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -200,6 +200,13 @@ ___
 
 ### Views Naming Convention
 
+ | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
+ | :-:  | :----                  | :-:    | :--:   | :---:  | :---   | :----   |
+ | 1    | Views                  | 30     | APPS   |   -    |  _V    | XXD_PO_LC_DOCUMENTS_V |
+ | 2    | Materialized Views     | 30     | APPS   |   -    |  _MV   | XXD_PO_LC_DOCUMENTS_MV |
+  
+<br>
+
 ### Views Naming Standards
 - The view name “*{object_name}*“ should be 30 characters or less and end with "_V" for view and "_VM" for materialized views.
 - The first column your view should select is the ROWID for the root table, and the view should alias it to ROW_ID.

From c83b4d28f66407c379ae11f7cedcf534948a13f1 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 16:35:11 +0300
Subject: [PATCH 061/126] Update "Sequence Naming Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 78acc23..1a960a9 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -168,7 +168,7 @@ ___
 ### Sequence Naming Convention
 
 ### Sequence Naming Standards
-- The sequence name “*{object_name}*“ should be 30 characters or less and end with "_SEQ".
+- The sequence name `{object_name}` should be 30 characters or less and end with `_SEQ`.
 - You must place the new sequence in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
 - Use each sequence to supply unique ID values for one column of one table.
 - Do not design sequences that wrap using the CYCLE option or have limited ranges using MAXVALUE.

From 0e12c7a8d376262bbbe5bf0ee94bad39d8c2a941 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 17:16:10 +0300
Subject: [PATCH 062/126] Add "Packages Naming Convention"

---
 database-standards-guidelines/README.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 1a960a9..9ce377c 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -233,8 +233,26 @@ ___
 
 ### Packages Naming Syntax
 
+<br>
+
 ### Packages Naming Convention
 
+
+ | SEQ  | Object Name              | Length | Prefix | Suffix | Example |
+ | :-:  | :----                    | :-:    | :---:  | :---   | :----   |
+ | 1    | Table Handlers Packages  | 27     |  -     | PKG    |   |
+ | 1.1  | Insert Procedures        |        |  ins   | -      |   |
+ | 1.2  | Update Procedures        |        |  upd   | -      |   |
+ | 1.3  | Delete Procedures        |        |  del   | -      |   |
+ | 1.3  | Lock Procedures          |        |  loc   | -      |   | 
+ | 3    | Public Packages          | 27     |  -     | API    |   | 
+ | 4    | Private Packages         | 27     |  -     | PVT    |   | 
+ | 5    | Unit Testing Packages    | 30     |  UT    | -      |   | 
+ 
+<br>
+
+
+
 ### Packages Naming Standards
 
 <br>

From 8e0c20c66f39e9d7f513c79e2838072c59287503 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 17:58:02 +0300
Subject: [PATCH 063/126] Update "Packages Naming Convention"

---
 database-standards-guidelines/README.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 9ce377c..4dc0a40 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -202,8 +202,8 @@ ___
 
  | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
  | :-:  | :----                  | :-:    | :--:   | :---:  | :---   | :----   |
- | 1    | Views                  | 30     | APPS   |   -    |  _V    | XXD_PO_LC_DOCUMENTS_V |
- | 2    | Materialized Views     | 30     | APPS   |   -    |  _MV   | XXD_PO_LC_DOCUMENTS_MV |
+ | 1    | Views                  | 30     | APPS   |   -    |  \_V    | XXD_PO_LC_DOCUMENTS_V |
+ | 2    | Materialized Views     | 30     | APPS   |   -    |  \_MV   | XXD_PO_LC_DOCUMENTS_MV |
   
 <br>
 
@@ -240,14 +240,14 @@ ___
 
  | SEQ  | Object Name              | Length | Prefix | Suffix | Example |
  | :-:  | :----                    | :-:    | :---:  | :---   | :----   |
- | 1    | Table Handlers Packages  | 27     |  -     | PKG    |   |
- | 1.1  | Insert Procedures        |        |  ins   | -      |   |
- | 1.2  | Update Procedures        |        |  upd   | -      |   |
- | 1.3  | Delete Procedures        |        |  del   | -      |   |
- | 1.3  | Lock Procedures          |        |  loc   | -      |   | 
- | 3    | Public Packages          | 27     |  -     | API    |   | 
- | 4    | Private Packages         | 27     |  -     | PVT    |   | 
- | 5    | Unit Testing Packages    | 30     |  UT    | -      |   | 
+ | 1    | Table Handlers Packages  | 27     |  -     | PKG    |         |
+ | 1.1  | Insert Procedures        |        |  INS   | -      |         |
+ | 1.2  | Update Procedures        |        |  UPD   | -      |         |
+ | 1.3  | Delete Procedures        |        |  DEL   | -      |         |
+ | 1.4  | Lock Procedures          |        |  LOCK  | -      |         | 
+ | 3    | Public Packages          | 27     |  -     | API    |         | 
+ | 4    | Private Packages         | 27     |  -     | PVT    |         | 
+ | 5    | Unit Testing Packages    | 30     |  UT    | -      |         | 
  
 <br>
 

From 433752b2a650788b6e68eb55898f07d9aba2cc63 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:05:19 +0300
Subject: [PATCH 064/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 4dc0a40..a331ed3 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -41,11 +41,11 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ### General Standards
 
-- Never modify Oracle standard database objects.
+- NEVER modify Oracle standard database objects.
 - You must follow standard naming conventions for creating new database objects.
-- The database objet name "*{object_name}*" must be meaningful and brief.
+- The database objet name `{object_name}` must be meaningful and brief.
 - Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the database objet name "*{object_name}*".
-- The application/product Short Name “*{app_short_name}*“ is a foreign key from Oracle standard table called "FND_APPLICATIONS".
+- The application/product Short Name `{app_short_name}` is a foreign key from Oracle standard table called "FND_APPLICATIONS".
 - The custom database objects must start with a **custom schema name** such as "XXD". [^1]
 - You must create new database tables, sequences, and types, in the custom schema.
 - You must create new database views and packages in the APPS schema.
@@ -59,8 +59,8 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 ```SQL
 /*
- Name: XXD Create GL Journals
- Purpose: This is the main package to create GL journals
+ Name: Create & Post GL Journals
+ Purpose: This is the main package to create & post GL journals
  Arguments
   Arg1 Describe arg1
   Arg2 Describe arg2
@@ -68,7 +68,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
   1. Special usage notes
   2. Special usage notes
  History
- 13–NOV–1986 Ahmed Demasy Created
+ 13–NOV–1986 Ahmed El-Demasy Created
 */
 ```
 

From 2d6cd280eb23b2ef839d951feee07549196c62ee Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:06:18 +0300
Subject: [PATCH 065/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index a331ed3..7e47a2c 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -43,7 +43,7 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 - NEVER modify Oracle standard database objects.
 - You must follow standard naming conventions for creating new database objects.
-- The database objet name `{object_name}` must be meaningful and brief.
+- The database object name `{object_name}` must be meaningful and brief.
 - Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the database objet name "*{object_name}*".
 - The application/product Short Name `{app_short_name}` is a foreign key from Oracle standard table called "FND_APPLICATIONS".
 - The custom database objects must start with a **custom schema name** such as "XXD". [^1]

From e8f7329f3aae214026fc77ec5af8b9f70e124082 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:08:06 +0300
Subject: [PATCH 066/126] Updated "General Standards"

---
 database-standards-guidelines/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 7e47a2c..2122f0b 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -45,8 +45,8 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 - You must follow standard naming conventions for creating new database objects.
 - The database object name `{object_name}` must be meaningful and brief.
 - Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the database objet name "*{object_name}*".
-- The application/product Short Name `{app_short_name}` is a foreign key from Oracle standard table called "FND_APPLICATIONS".
-- The custom database objects must start with a **custom schema name** such as "XXD". [^1]
+- The application/product short name `{app_short_name}` is a foreign key from Oracle standard table called "FND_APPLICATIONS".
+- The custom database objects must start with a custom database schema name for example "**XXD**". [^1]
 - You must create new database tables, sequences, and types, in the custom schema.
 - You must create new database views and packages in the APPS schema.
 - Never create new stand-alone functions and procedures. Should be implemented as part of a package.

From c238597382174ec359a21c6d8217834f5ae63513 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:15:32 +0300
Subject: [PATCH 067/126] Update "Syntax for data upload tables ONLY"

---
 database-standards-guidelines/README.md | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 2122f0b..99b1336 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -89,15 +89,23 @@ The **Syntax Elements** section that presents elements syntax and describes it.
 
 > {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
 
+<br>
+
+##### Syntax for data upload tables ONLY
+
+> {prefix}{separator}{app_short_name}{separator}{object_name}
+
+
+
 <br>
 
 ### Table Naming Convention
 
  | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
  | :-:  | :----                  | :-:    | :--:   | :---   | :---   | :----   |
- | 1    | Table                  | 20     | XXD    |        |        | XXD_PO_LC_DOCUMENTS |
- | 2    | Temporary Table        | 20     | XXD    |        | \_TMP  | XXD_PO_LC_DOCS_TMP |
- | 3    | Data Upload Table [^2] | 20     | XXD    | TMP_   |        | XXD_TMP_LC_DOCS | 
+ | 1    | Table                  | 20     | XXD    |  -     | -      | XXD_PO_LC_DOCUMENTS |
+ | 2    | Temporary Table        | 20     | XXD    |  -     | TMP    | XXD_PO_LC_DOCS_TMP |
+ | 3    | Data Upload Table [^2] | 20     | XXD    | TMP    | -      | TMP_PO_LC_DOCS | 
  
 <br>
 

From 055c3e269c5d98242ef0b4cc4a3f3cd7e7079c39 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:20:04 +0300
Subject: [PATCH 068/126] Update "References" number 2

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 99b1336..08ddb3d 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -276,4 +276,4 @@ ___
 
 ##### References
 [^1]: "**XXD**" is the custom database ORACLE schema association to my custom application called "Demasy Custom Applications".
-[^2]: This is a custom table for data upload and migrations **only**.
+[^2]: This is a custom table for data upload and migrations **ONLY** and should drop these tables after the upload data process finish.

From 0ab181796ce3c2da4cf3cd83cf2e4c0b965c6a02 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:29:06 +0300
Subject: [PATCH 069/126] Update "Packages Naming Standards"

---
 database-standards-guidelines/README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 08ddb3d..42272e0 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -263,6 +263,13 @@ ___
 
 ### Packages Naming Standards
 
+- You MUST follow custom database objects general standards.
+- You MUST place the new packages in the **APPS** schema.
+- The packages name must be 27 characters or less for table handlers packages, and end with `PKG`.
+- The packages name must be 27 characters or less for public packages, and end with `API`. 
+- The packages name must be 27 characters or less for private packages, and end with `PVT`. 
+- The packages name must be 30 characters or less for unit testing packages, and start with `UT`. 
+
 <br>
 
 ### Packages Naming Examples

From 3d405712a82645b55e5beeaecfaf0c8ed098166e Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:32:04 +0300
Subject: [PATCH 070/126] Update "Packages Naming Standards"

---
 database-standards-guidelines/README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 42272e0..4c82403 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -265,10 +265,10 @@ ___
 
 - You MUST follow custom database objects general standards.
 - You MUST place the new packages in the **APPS** schema.
-- The packages name must be 27 characters or less for table handlers packages, and end with `PKG`.
-- The packages name must be 27 characters or less for public packages, and end with `API`. 
-- The packages name must be 27 characters or less for private packages, and end with `PVT`. 
-- The packages name must be 30 characters or less for unit testing packages, and start with `UT`. 
+- The packages name `{object_name}` must be 27 characters or less for table handlers packages, and end with `PKG`.
+- The packages name `{object_name}` must be 27 characters or less for public packages, and end with `API`. 
+- The packages name `{object_name}` must be 27 characters or less for private packages, and end with `PVT`. 
+- The packages name `{object_name}` must be 30 characters or less for unit testing packages, and start with `UT`. 
 
 <br>
 

From 6c2f4aa08c508847f75dd6546684446473af852d Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:33:59 +0300
Subject: [PATCH 071/126] Update "Database Custom Objects Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 4c82403..32df0af 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -1,6 +1,6 @@
 # Database Standards Guidelines
 
-- **Create Database Custom Objects**
+- **Database Custom Objects Standards**
   - <a href="#general-standards">**General Standards**</a>
   - <a href="#tables-standards">**Tables Standards**</a>
   - <a href="#sequences-standards">**Sequences Standards**</a>

From b9bc525ea549245c1f91ea25a2c330da3d2f49f9 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:35:04 +0300
Subject: [PATCH 072/126] Add "Oracle PL/SQL Objects Standards"

---
 database-standards-guidelines/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 32df0af..c220cc0 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -6,6 +6,7 @@
   - <a href="#sequences-standards">**Sequences Standards**</a>
   - <a href="#views-standards">**Views Standards**</a>
   - <a href="#packages-standards">**Packages Standards**</a>
+- Oracle PL/SQL Objects Standards
 - Database Custom Objects Naming Conventions
 
 <br>

From ef10c299ab57ab9c809ad0b2f6a6de8e0a4a2cea Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:43:09 +0300
Subject: [PATCH 073/126] Add "Oracle PL/SQL Objects Code Standards"

---
 database-standards-guidelines/README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index c220cc0..6886170 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -6,7 +6,7 @@
   - <a href="#sequences-standards">**Sequences Standards**</a>
   - <a href="#views-standards">**Views Standards**</a>
   - <a href="#packages-standards">**Packages Standards**</a>
-- Oracle PL/SQL Objects Standards
+- Oracle PL/SQL Objects Code Standards
 - Database Custom Objects Naming Conventions
 
 <br>
@@ -277,7 +277,9 @@ ___
 
 ___
 
+<br>
 
+## Oracle PL/SQL Objects Code Standards
 
 
 <br>

From a9cd37a6b988e182ac54422bcc528b658e6b77cd Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 18:59:00 +0300
Subject: [PATCH 074/126] Add "PL/SQL Objects Naming Convention"

---
 database-standards-guidelines/README.md | 40 +++++++++++++++++++++++--
 1 file changed, 38 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 6886170..d3711a1 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -6,7 +6,7 @@
   - <a href="#sequences-standards">**Sequences Standards**</a>
   - <a href="#views-standards">**Views Standards**</a>
   - <a href="#packages-standards">**Packages Standards**</a>
-- Oracle PL/SQL Objects Code Standards
+- Oracle PL/SQL Coding Standards
 - Database Custom Objects Naming Conventions
 
 <br>
@@ -279,7 +279,43 @@ ___
 
 <br>
 
-## Oracle PL/SQL Objects Code Standards
+## Oracle PL/SQL Coding Standards
+
+<br>
+
+### Syntax 
+
+> {scope}{prefix}{separator}{identifier_name}{separator}{suffix}
+
+<br>
+
+### PL/SQL Objects Naming Convention
+
+ | SEQ | Object Name       | Length | scope | Prefix | Suffix | Example           |
+ | :-  | :----             | :-:    | :--   | :---   | :--    | :----             |
+ | 1   | **Variables**     |        |       |        |        |                  |
+ | 1.1 | Global Variable   |        | g     |    _   |        | g_enterprise_id   | 
+ | 1.2 | Local Variable    |        | l     |    _   |        | l_customer_id     | 
+ | 2   | **Constants**     |        |       |        |       |                  |
+ | 2.1 | Global Constants  |        | g     |  c     |        | gc_max_discount   | 
+ | 2.2 | Local Constants   |        | l     |  c     |        | lc_max_discount   | 
+ | 3   | **Parameters**    |  -     |       |  -     |  -     |    -              |
+ | 3.1 | Cursor Parameters |        |       | p      |        | p_customer        |
+ | 3.2 | In Parameters     |        |       | p      |        | p_customer_id     | 
+ | 3.3 | Out Parameters    |        |       | x      |        | x_customer_id     | 
+ | 3.4 | In/Out Parameters |        |       | px     |        | px_customer_id    | 
+ | 4   | **Other Objects** |  -     |       |   -    |   -    |     -             | 
+ | 4.1 | Cursors           |        |       | cur    |        | cur_customers     |
+ | 4.2 | Record            |        |       | r      |  type  | r_customer_type   | 
+ | 4.3 | Array / Table     |        |       | t      |  type  | t_customers_type  |    
+ | 4.4 | Objects           |        |       | o      |  type  | o_customers_type  |
+ | 4.5 | Exceptions        |        |       | e      |        | e_customer_exists |
+ | 4.6 | Exception Number  |        |       | en     |        | en_customer_exists|
+ 
+ 
+<br>
+
+### PL/SQL Objects Naming Standards
 
 
 <br>

From cac2783a287c3b2a9e0ca5fa285cdaef5f5347b5 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:05:29 +0300
Subject: [PATCH 075/126] Update "Oracle PL/SQL Coding Standards"

---
 database-standards-guidelines/README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index d3711a1..0c0de63 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -317,6 +317,10 @@ ___
 
 ### PL/SQL Objects Naming Standards
 
+<br>
+
+### PL/SQL Objects Coding Standards
+- 
 
 <br>
 

From 5cd9621d790db2beed125123e95d495320fbf76f Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:10:53 +0300
Subject: [PATCH 076/126] Update "Database Objects Naming Conventions"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 0c0de63..a82cd3a 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -7,7 +7,7 @@
   - <a href="#views-standards">**Views Standards**</a>
   - <a href="#packages-standards">**Packages Standards**</a>
 - Oracle PL/SQL Coding Standards
-- Database Custom Objects Naming Conventions
+- Appendix: Database Custom Objects Naming Conventions
 
 <br>
 

From e8d12f6872294ac521eec2e38163cf75e23747b2 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:16:05 +0300
Subject: [PATCH 077/126] Create "Database Objects Naming Conventions"

Create "Database Custom Objects Naming Conventions"
---
 .../appendix/database-objects-naming-conventions/README.md     | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 database-standards-guidelines/appendix/database-objects-naming-conventions/README.md

diff --git a/database-standards-guidelines/appendix/database-objects-naming-conventions/README.md b/database-standards-guidelines/appendix/database-objects-naming-conventions/README.md
new file mode 100644
index 0000000..045de6e
--- /dev/null
+++ b/database-standards-guidelines/appendix/database-objects-naming-conventions/README.md
@@ -0,0 +1,3 @@
+# Database Custom Objects Naming Conventions
+
+<br>

From c9743e6c7471ca36fe5597b38541b33c21890c90 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:28:37 +0300
Subject: [PATCH 078/126] Create "Naming Conventions Syntax Description"

Naming Conventions Syntax Elements Description
---
 .../appendix/syntax-elements-description.md      | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 database-standards-guidelines/appendix/syntax-elements-description.md

diff --git a/database-standards-guidelines/appendix/syntax-elements-description.md b/database-standards-guidelines/appendix/syntax-elements-description.md
new file mode 100644
index 0000000..331576e
--- /dev/null
+++ b/database-standards-guidelines/appendix/syntax-elements-description.md
@@ -0,0 +1,16 @@
+#  Naming Conventions Syntax Elements
+
+This appendix presents naming conventions and database syntax elements and describes them.  
+
+<br>
+  
+## Syntax Elements
+  
+ | SEQ | Element Syntax      | Element Name                  | Description |
+ | :-: | :---                | :--                           | :--------   |
+ | 1   | *{custom_schema}*   | Custom Database Schema        | Database custom ORACLE schema name |
+ | 2   | *{separator}*       | Separator                     | Must use underscore “_” in database objects|
+ | 3   | *{app_short_name}*  | Application/Product Short Name| This is the application/product short name |
+ | 4   | *{prefix}*          | Prefix                        |  |
+ | 5   | *{object_name}*     | Database Object Name          |  |
+ | 6   | *{suffix}*          | Suffix                        |  |

From 27c86724a5f3186fb29537c98e46a2375efb40a7 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:30:45 +0300
Subject: [PATCH 079/126] move document to appendix folder

---
 .../README.md => database-objects-naming-conventions.md}          | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename database-standards-guidelines/appendix/{database-objects-naming-conventions/README.md => database-objects-naming-conventions.md} (100%)

diff --git a/database-standards-guidelines/appendix/database-objects-naming-conventions/README.md b/database-standards-guidelines/appendix/database-objects-naming-conventions.md
similarity index 100%
rename from database-standards-guidelines/appendix/database-objects-naming-conventions/README.md
rename to database-standards-guidelines/appendix/database-objects-naming-conventions.md

From dc99d7c463c8bbbfcdf6be8627913a6e98edcb60 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:32:19 +0300
Subject: [PATCH 080/126] remove Syntax Elements to appendix

---
 database-standards-guidelines/README.md | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index a82cd3a..b01d7d9 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -27,19 +27,6 @@
 
 <br>
 
-##### Syntax Elements
-The **Syntax Elements** section that presents elements syntax and describes it.
- | SEQ | Element Syntax      | Element Name                  | Description |
- | :-: | :---                | :--                           | :--------   |
- | 1   | *{custom_schema}*   | Custom Database Schema        | Database custom ORACLE schema name |
- | 2   | *{separator}*       | Separator                     | Must use underscore “_” in database objects|
- | 3   | *{app_short_name}*  | Application/Product Short Name| This is the application/product short name |
- | 4   | *{prefix}*          | Prefix                        |  |
- | 5   | *{object_name}*     | Database Object Name          |  |
- | 6   | *{suffix}*          | Suffix                        |  |
-
-<br>
-
 ### General Standards
 
 - NEVER modify Oracle standard database objects.

From a5590a24b013ddc0009a36c287bd220aba65d252 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:36:35 +0300
Subject: [PATCH 081/126] Create "Appendix"

---
 database-standards-guidelines/appendix/README.md | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 database-standards-guidelines/appendix/README.md

diff --git a/database-standards-guidelines/appendix/README.md b/database-standards-guidelines/appendix/README.md
new file mode 100644
index 0000000..fd73849
--- /dev/null
+++ b/database-standards-guidelines/appendix/README.md
@@ -0,0 +1,3 @@
+# Appendix
+- Naming Conventions Syntax Elements
+- Database Custom Objects Naming Conventions

From 70f13a1c5987eafde739b0b76521b9f5f7d5b243 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:38:10 +0300
Subject: [PATCH 082/126] Create "Tables Standards"

---
 database-standards-guidelines/tables-standards/README.md | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 database-standards-guidelines/tables-standards/README.md

diff --git a/database-standards-guidelines/tables-standards/README.md b/database-standards-guidelines/tables-standards/README.md
new file mode 100644
index 0000000..1919680
--- /dev/null
+++ b/database-standards-guidelines/tables-standards/README.md
@@ -0,0 +1 @@
+# Tables Standards

From b57c04ea34ceeddda06d7b16e9d50bc8b1a5010f Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:42:41 +0300
Subject: [PATCH 083/126] Move tables standards to separate folder

---
 database-standards-guidelines/README.md | 88 -------------------------
 1 file changed, 88 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index b01d7d9..5b3ac4c 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -62,94 +62,6 @@
 
 <br>
 
-## Tables Standards
-
-- <a href="#table-naming-syntax">**Table Naming Syntax**</a>
-- <a href="#table-naming-convention">**Table Naming Convention**</a>
-- <a href="#table-naming-standards">**Table Naming Standards**</a>
-- <a href="#table-naming-example">**Table Naming Example**</a>
-
-<br>
-
-### Table Naming Syntax
-
-##### Syntax 
-
-> {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
-
-<br>
-
-##### Syntax for data upload tables ONLY
-
-> {prefix}{separator}{app_short_name}{separator}{object_name}
-
-
-
-<br>
-
-### Table Naming Convention
-
- | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
- | :-:  | :----                  | :-:    | :--:   | :---   | :---   | :----   |
- | 1    | Table                  | 20     | XXD    |  -     | -      | XXD_PO_LC_DOCUMENTS |
- | 2    | Temporary Table        | 20     | XXD    |  -     | TMP    | XXD_PO_LC_DOCS_TMP |
- | 3    | Data Upload Table [^2] | 20     | XXD    | TMP    | -      | TMP_PO_LC_DOCS | 
- 
-<br>
-
-### Table Naming Standards
-
-- You MUST follow create database custom objects general standards.
-- The object name “*{object_name}*“ should be plural.
-- The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
-- You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
-- You must create private synonyms for custom tables in APPS.
-- You should add special WHO columns to your tables.
-- You should add concurrent program WHO Columns to your table.
-- You should add concurrent program WHO Columns to your table.
-- You should add descriptive flexfield (DFF) attribute Columns to your table.
-- New tables containing Flex-Fields or Oracle Alert columns must be registered with Oracle Application Object Library.
-- You should register your custom tables with Oracle AOL using the table registration API called AD_DD.
-  - AD_DD. REGISTER_TABLE
-  - AD_DD. REGISTER_COLUMN
-
-<br>
-
-##### WHO columns
-
- | Column Name       | Type       | Null?    | Foreign Key? | Value | 
- | :--               | :----      | :-:      | :--          | :---   | 
- | CREATED_BY        | NUMBER(15) | NOT NULL | FND_USER     | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) |
- | CREATION_DATE     | DATE       | NOT NULL |              | SYSDATE |
- | LAST_UPDATED_BY   | NUMBER(15) | NOT NULL |              | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) | 
- | LAST_UPDATE_DATE  | DATE       | NOT NULL |              | SYSDATE |
- | LAST_UPDATE_LOGIN | NUMBER(15) |          |              | TO_NUMBER (FND_ PROFILE.VALUE (’LOGIN_ ID’)) |
- 
-<br>
-
-##### Concurrent Program WHO Columns
-
- | Column Name             | Type       | Null? | Foreign Key to Table?   |  
- | :--                     | :----      | :-:   | :--                     | 
- | REQUEST_ID              | NUMBER(15) |       | FND_CONCURRENT_REQUESTS | 
- | PROGRAM_APPLICATION_ID  | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
- | PROGRAM_ID              | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
- | PROGRAM_UPDATE_DATE     | DATE       |       | ROGRAM_UPDATE_DATE      | 
- 
-<br>
-
-### Table Naming Example
-
- | Better   | Bad        |
- | :---  | :---        |
- | - XXD_PO_LC_DOCUMENTS | - XXD_PO_LC_DOCUMENT <br> - PO_LC_DOCUMENTS       |
-
-<br>
-
-___
-
-<br>
-
 ## Sequences Standards
 
 - <a href="#sequence-naming-syntax">**Sequence Naming Syntax**</a>

From 8488b7ef607b3264aa9b2cd13d9efb3001fb6a0c Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:43:46 +0300
Subject: [PATCH 084/126] Update "Tables Standards"

---
 .../tables-standards/README.md                | 84 +++++++++++++++++++
 1 file changed, 84 insertions(+)

diff --git a/database-standards-guidelines/tables-standards/README.md b/database-standards-guidelines/tables-standards/README.md
index 1919680..1226067 100644
--- a/database-standards-guidelines/tables-standards/README.md
+++ b/database-standards-guidelines/tables-standards/README.md
@@ -1 +1,85 @@
 # Tables Standards
+
+<br>
+
+- <a href="#table-naming-syntax">**Table Naming Syntax**</a>
+- <a href="#table-naming-convention">**Table Naming Convention**</a>
+- <a href="#table-naming-standards">**Table Naming Standards**</a>
+- <a href="#table-naming-example">**Table Naming Example**</a>
+
+<br>
+
+## Table Naming Syntax
+
+##### Syntax 
+
+> {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
+
+<br>
+
+##### Syntax for data upload tables ONLY
+
+> {prefix}{separator}{app_short_name}{separator}{object_name}
+
+
+
+<br>
+
+## Table Naming Convention
+
+ | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
+ | :-:  | :----                  | :-:    | :--:   | :---   | :---   | :----   |
+ | 1    | Table                  | 20     | XXD    |  -     | -      | XXD_PO_LC_DOCUMENTS |
+ | 2    | Temporary Table        | 20     | XXD    |  -     | TMP    | XXD_PO_LC_DOCS_TMP |
+ | 3    | Data Upload Table [^2] | 20     | XXD    | TMP    | -      | TMP_PO_LC_DOCS | 
+ 
+<br>
+
+## Table Naming Standards
+
+- You MUST follow create database custom objects general standards.
+- The object name “*{object_name}*“ should be plural.
+- The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
+- You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
+- You must create private synonyms for custom tables in APPS.
+- You should add special WHO columns to your tables.
+- You should add concurrent program WHO Columns to your table.
+- You should add concurrent program WHO Columns to your table.
+- You should add descriptive flexfield (DFF) attribute Columns to your table.
+- New tables containing Flex-Fields or Oracle Alert columns must be registered with Oracle Application Object Library.
+- You should register your custom tables with Oracle AOL using the table registration API called AD_DD.
+  - AD_DD. REGISTER_TABLE
+  - AD_DD. REGISTER_COLUMN
+
+<br>
+
+##### WHO columns
+
+ | Column Name       | Type       | Null?    | Foreign Key? | Value | 
+ | :--               | :----      | :-:      | :--          | :---   | 
+ | CREATED_BY        | NUMBER(15) | NOT NULL | FND_USER     | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) |
+ | CREATION_DATE     | DATE       | NOT NULL |              | SYSDATE |
+ | LAST_UPDATED_BY   | NUMBER(15) | NOT NULL |              | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) | 
+ | LAST_UPDATE_DATE  | DATE       | NOT NULL |              | SYSDATE |
+ | LAST_UPDATE_LOGIN | NUMBER(15) |          |              | TO_NUMBER (FND_ PROFILE.VALUE (’LOGIN_ ID’)) |
+ 
+<br>
+
+##### Concurrent Program WHO Columns
+
+ | Column Name             | Type       | Null? | Foreign Key to Table?   |  
+ | :--                     | :----      | :-:   | :--                     | 
+ | REQUEST_ID              | NUMBER(15) |       | FND_CONCURRENT_REQUESTS | 
+ | PROGRAM_APPLICATION_ID  | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
+ | PROGRAM_ID              | NUMBER(15) |       | FND_CONCURRENT_PROGRAMS | 
+ | PROGRAM_UPDATE_DATE     | DATE       |       | ROGRAM_UPDATE_DATE      | 
+ 
+<br>
+
+## Table Naming Example
+
+ | Better   | Bad        |
+ | :---  | :---        |
+ | - XXD_PO_LC_DOCUMENTS | - XXD_PO_LC_DOCUMENT <br> - PO_LC_DOCUMENTS       |
+
+<br>

From 206236bbce7e6d7fc092fe5ad5317ab34d2c87d1 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:46:28 +0300
Subject: [PATCH 085/126] Create "Views Standards"

---
 .../views-standards/README.md                 | 37 +++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 database-standards-guidelines/views-standards/README.md

diff --git a/database-standards-guidelines/views-standards/README.md b/database-standards-guidelines/views-standards/README.md
new file mode 100644
index 0000000..d44e2ca
--- /dev/null
+++ b/database-standards-guidelines/views-standards/README.md
@@ -0,0 +1,37 @@
+# Views Standards
+
+<br>
+
+- <a href="#views-naming-syntax">**Views Naming Syntax**</a>
+- <a href="#views-naming-convention">**Views Naming Convention**</a>
+- <a href="#views-naming-standards">**Views Naming Standards**</a>
+- <a href="#views-naming-examples">**Views Naming Examples**</a>
+
+
+
+<br>
+
+## Views Naming Syntax
+
+<br>
+
+## Views Naming Convention
+
+ | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
+ | :-:  | :----                  | :-:    | :--:   | :---:  | :---   | :----   |
+ | 1    | Views                  | 30     | APPS   |   -    |   V    | XXD_PO_LC_DOCUMENTS_V |
+ | 2    | Materialized Views     | 30     | APPS   |   -    |   MV   | XXD_PO_LC_DOCUMENTS_MV |
+  
+<br>
+
+## Views Naming Standards
+- The view name “*{object_name}*“ should be 30 characters or less and end with "_V" for view and "_VM" for materialized views.
+- The first column your view should select is the ROWID for the root table, and the view should alias it to ROW_ID.
+- You only need to include the ROWID column if an Oracle Forms block is based on this view.
+
+<br>
+
+## Views Naming Examples
+
+<br>
+

From a375a7dac0c9787c161a29c559d6e2c305d9e8bf Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:46:51 +0300
Subject: [PATCH 086/126] Move views standards to separate folder

---
 database-standards-guidelines/README.md | 36 -------------------------
 1 file changed, 36 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 5b3ac4c..d2a2c6a 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -91,42 +91,6 @@
 
 ___
 
-
-<br>
-
-## Views Standards
-
-
-- <a href="#views-naming-syntax">**Views Naming Syntax**</a>
-- <a href="#views-naming-convention">**Views Naming Convention**</a>
-- <a href="#views-naming-standards">**Views Naming Standards**</a>
-- <a href="#views-naming-examples">**Views Naming Examples**</a>
-
-<br>
-
-### Views Naming Syntax
-
-### Views Naming Convention
-
- | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
- | :-:  | :----                  | :-:    | :--:   | :---:  | :---   | :----   |
- | 1    | Views                  | 30     | APPS   |   -    |  \_V    | XXD_PO_LC_DOCUMENTS_V |
- | 2    | Materialized Views     | 30     | APPS   |   -    |  \_MV   | XXD_PO_LC_DOCUMENTS_MV |
-  
-<br>
-
-### Views Naming Standards
-- The view name “*{object_name}*“ should be 30 characters or less and end with "_V" for view and "_VM" for materialized views.
-- The first column your view should select is the ROWID for the root table, and the view should alias it to ROW_ID.
-- You only need to include the ROWID column if an Oracle Forms block is based on this view.
-
-
-<br>
-
-### Views Naming Examples
-
-___
-
 <br>
 
 ## Packages Standards

From 355ea722da878d85bfc7c199f672b0ae62934b2f Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:54:57 +0300
Subject: [PATCH 087/126] Create "Packages Standards"

---
 .../packages-standards/README.md              | 41 +++++++++++++++++++
 1 file changed, 41 insertions(+)
 create mode 100644 database-standards-guidelines/packages-standards/README.md

diff --git a/database-standards-guidelines/packages-standards/README.md b/database-standards-guidelines/packages-standards/README.md
new file mode 100644
index 0000000..c51c64f
--- /dev/null
+++ b/database-standards-guidelines/packages-standards/README.md
@@ -0,0 +1,41 @@
+# Packages Standards
+
+- <a href="#packages-naming-syntax">**Packages Naming Syntax**</a>
+- <a href="#packages-naming-convention">**Packages Naming Convention**</a>
+- <a href="#packages-naming-standards">**Packages Naming Standards**</a>
+- <a href="#packages-naming-examples">**Packages Naming Examples**</a>
+
+<br>
+
+## Packages Naming Syntax
+
+<br>
+
+## Packages Naming Convention
+
+
+ | SEQ  | Object Name              | Length | Prefix | Suffix | Example |
+ | :-:  | :----                    | :-:    | :---:  | :---   | :----   |
+ | 1    | Table Handlers Packages  | 27     |  -     | PKG    |         |
+ | 1.1  | Insert Procedures        |        |  INS   | -      |         |
+ | 1.2  | Update Procedures        |        |  UPD   | -      |         |
+ | 1.3  | Delete Procedures        |        |  DEL   | -      |         |
+ | 1.4  | Lock Procedures          |        |  LOCK  | -      |         | 
+ | 3    | Public Packages          | 27     |  -     | API    |         | 
+ | 4    | Private Packages         | 27     |  -     | PVT    |         | 
+ | 5    | Unit Testing Packages    | 30     |  UT    | -      |         | 
+ 
+<br>
+
+## Packages Naming Standards
+
+- You MUST follow custom database objects general standards.
+- You MUST place the new packages in the **APPS** schema.
+- The packages name `{object_name}` must be 27 characters or less for table handlers packages, and end with `PKG`.
+- The packages name `{object_name}` must be 27 characters or less for public packages, and end with `API`. 
+- The packages name `{object_name}` must be 27 characters or less for private packages, and end with `PVT`. 
+- The packages name `{object_name}` must be 30 characters or less for unit testing packages, and start with `UT`. 
+
+<br>
+
+## Packages Naming Examples

From 6f4261e393c6dc2d66710aa1da7ba2ba171d5c94 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 19:55:32 +0300
Subject: [PATCH 088/126] Move packages standards to separate folder

---
 database-standards-guidelines/README.md | 48 -------------------------
 1 file changed, 48 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index d2a2c6a..f7b0c35 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -91,54 +91,6 @@
 
 ___
 
-<br>
-
-## Packages Standards
-
-
-- <a href="#packages-naming-syntax">**Packages Naming Syntax**</a>
-- <a href="#packages-naming-convention">**Packages Naming Convention**</a>
-- <a href="#packages-naming-standards">**Packages Naming Standards**</a>
-- <a href="#packages-naming-examples">**Packages Naming Examples**</a>
-
-<br>
-
-### Packages Naming Syntax
-
-<br>
-
-### Packages Naming Convention
-
-
- | SEQ  | Object Name              | Length | Prefix | Suffix | Example |
- | :-:  | :----                    | :-:    | :---:  | :---   | :----   |
- | 1    | Table Handlers Packages  | 27     |  -     | PKG    |         |
- | 1.1  | Insert Procedures        |        |  INS   | -      |         |
- | 1.2  | Update Procedures        |        |  UPD   | -      |         |
- | 1.3  | Delete Procedures        |        |  DEL   | -      |         |
- | 1.4  | Lock Procedures          |        |  LOCK  | -      |         | 
- | 3    | Public Packages          | 27     |  -     | API    |         | 
- | 4    | Private Packages         | 27     |  -     | PVT    |         | 
- | 5    | Unit Testing Packages    | 30     |  UT    | -      |         | 
- 
-<br>
-
-
-
-### Packages Naming Standards
-
-- You MUST follow custom database objects general standards.
-- You MUST place the new packages in the **APPS** schema.
-- The packages name `{object_name}` must be 27 characters or less for table handlers packages, and end with `PKG`.
-- The packages name `{object_name}` must be 27 characters or less for public packages, and end with `API`. 
-- The packages name `{object_name}` must be 27 characters or less for private packages, and end with `PVT`. 
-- The packages name `{object_name}` must be 30 characters or less for unit testing packages, and start with `UT`. 
-
-<br>
-
-### Packages Naming Examples
-
-___
 
 <br>
 

From 1e25c79c9626030432ae780876d7f9312c36636d Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:00:07 +0300
Subject: [PATCH 089/126] Create "Sequences Standards"

---
 .../sequences-standards.md                    | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 database-standards-guidelines/sequences-standards.md

diff --git a/database-standards-guidelines/sequences-standards.md b/database-standards-guidelines/sequences-standards.md
new file mode 100644
index 0000000..9d0db28
--- /dev/null
+++ b/database-standards-guidelines/sequences-standards.md
@@ -0,0 +1,29 @@
+# Sequences Standards
+- <a href="#sequence-naming-syntax">**Sequence Naming Syntax**</a>
+- <a href="#sequence-naming-convention">**Sequence Naming Convention**</a>
+- <a href="#sequence-naming-standards">**Sequence Naming Standards**</a>
+- <a href="#sequence-naming-examples">**Sequence Naming Examples**</a>
+
+<br>
+
+## Sequence Naming Syntax
+
+<br>
+
+
+## Sequence Naming Convention
+
+<br>
+
+
+## Sequence Naming Standards
+- The sequence name `{object_name}` should be 30 characters or less and end with `_SEQ`.
+- You must place the new sequence in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
+- Use each sequence to supply unique ID values for one column of one table.
+- Do not design sequences that wrap using the CYCLE option or have limited ranges using MAXVALUE.
+- Use a NUMBER datatype to store sequence values within PL/SQL.
+- Do Not Use the FND_UNIQUE_IDENTIFIER_CONTROL Table.
+
+<br>
+
+## Sequence Naming Examples

From a29a7e2a413016906d86df671363228524e6428b Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:00:36 +0300
Subject: [PATCH 090/126] Move sequences standards to separate folder

---
 database-standards-guidelines/README.md | 31 -------------------------
 1 file changed, 31 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index f7b0c35..0df2e61 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -60,37 +60,6 @@
 */
 ```
 
-<br>
-
-## Sequences Standards
-
-- <a href="#sequence-naming-syntax">**Sequence Naming Syntax**</a>
-- <a href="#sequence-naming-convention">**Sequence Naming Convention**</a>
-- <a href="#sequence-naming-standards">**Sequence Naming Standards**</a>
-- <a href="#sequence-naming-examples">**Sequence Naming Examples**</a>
-
-<br>
-
-### Sequence Naming Syntax
-
-### Sequence Naming Convention
-
-### Sequence Naming Standards
-- The sequence name `{object_name}` should be 30 characters or less and end with `_SEQ`.
-- You must place the new sequence in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
-- Use each sequence to supply unique ID values for one column of one table.
-- Do not design sequences that wrap using the CYCLE option or have limited ranges using MAXVALUE.
-- Use a NUMBER datatype to store sequence values within PL/SQL.
-- Do Not Use the FND_UNIQUE_IDENTIFIER_CONTROL Table.
-
-<br>
-
-### Sequence Naming Examples
-
-<br>
-
-___
-
 
 <br>
 

From 643730a34096ed190aa7b9491f682f478b969191 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:03:02 +0300
Subject: [PATCH 091/126] Update "Appendix"

---
 database-standards-guidelines/README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 0df2e61..10e4a78 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -7,7 +7,9 @@
   - <a href="#views-standards">**Views Standards**</a>
   - <a href="#packages-standards">**Packages Standards**</a>
 - Oracle PL/SQL Coding Standards
-- Appendix: Database Custom Objects Naming Conventions
+- **Appendix**
+  - Naming Conventions Syntax Elements
+  - Database Custom Objects Naming Conventions
 
 <br>
 

From d8892b8c6c55af33eda710f0d074107de0b87a0a Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:06:05 +0300
Subject: [PATCH 092/126] Create "Oracle PL/SQL Coding Standards"

---
 .../plsql-coding-standards/README.md          | 44 +++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 database-standards-guidelines/plsql-coding-standards/README.md

diff --git a/database-standards-guidelines/plsql-coding-standards/README.md b/database-standards-guidelines/plsql-coding-standards/README.md
new file mode 100644
index 0000000..b241ffe
--- /dev/null
+++ b/database-standards-guidelines/plsql-coding-standards/README.md
@@ -0,0 +1,44 @@
+# Oracle PL/SQL Coding Standards
+
+<br>
+
+## Syntax 
+
+> {scope}{prefix}{separator}{identifier_name}{separator}{suffix}
+
+<br>
+
+## PL/SQL Objects Naming Convention
+
+ | SEQ | Object Name       | Length | scope | Prefix | Suffix | Example           |
+ | :-  | :----             | :-:    | :--   | :---   | :--    | :----             |
+ | 1   | **Variables**     |        |       |        |        |                  |
+ | 1.1 | Global Variable   |        | g     |    _   |        | g_enterprise_id   | 
+ | 1.2 | Local Variable    |        | l     |    _   |        | l_customer_id     | 
+ | 2   | **Constants**     |        |       |        |       |                  |
+ | 2.1 | Global Constants  |        | g     |  c     |        | gc_max_discount   | 
+ | 2.2 | Local Constants   |        | l     |  c     |        | lc_max_discount   | 
+ | 3   | **Parameters**    |  -     |       |  -     |  -     |    -              |
+ | 3.1 | Cursor Parameters |        |       | p      |        | p_customer        |
+ | 3.2 | In Parameters     |        |       | p      |        | p_customer_id     | 
+ | 3.3 | Out Parameters    |        |       | x      |        | x_customer_id     | 
+ | 3.4 | In/Out Parameters |        |       | px     |        | px_customer_id    | 
+ | 4   | **Other Objects** |  -     |       |   -    |   -    |     -             | 
+ | 4.1 | Cursors           |        |       | cur    |        | cur_customers     |
+ | 4.2 | Record            |        |       | r      |  type  | r_customer_type   | 
+ | 4.3 | Array / Table     |        |       | t      |  type  | t_customers_type  |    
+ | 4.4 | Objects           |        |       | o      |  type  | o_customers_type  |
+ | 4.5 | Exceptions        |        |       | e      |        | e_customer_exists |
+ | 4.6 | Exception Number  |        |       | en     |        | en_customer_exists|
+ 
+ 
+<br>
+
+## PL/SQL Objects Naming Standards
+
+<br>
+
+## PL/SQL Objects Coding Standards
+- 
+
+<br>

From e7326b05bd753b0104b2b657c3155aedbfe19da5 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:06:48 +0300
Subject: [PATCH 093/126] Move coding standards to separate folders

---
 database-standards-guidelines/README.md | 44 -------------------------
 1 file changed, 44 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 10e4a78..2f9d85d 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -65,50 +65,6 @@
 
 <br>
 
-## Oracle PL/SQL Coding Standards
-
-<br>
-
-### Syntax 
-
-> {scope}{prefix}{separator}{identifier_name}{separator}{suffix}
-
-<br>
-
-### PL/SQL Objects Naming Convention
-
- | SEQ | Object Name       | Length | scope | Prefix | Suffix | Example           |
- | :-  | :----             | :-:    | :--   | :---   | :--    | :----             |
- | 1   | **Variables**     |        |       |        |        |                  |
- | 1.1 | Global Variable   |        | g     |    _   |        | g_enterprise_id   | 
- | 1.2 | Local Variable    |        | l     |    _   |        | l_customer_id     | 
- | 2   | **Constants**     |        |       |        |       |                  |
- | 2.1 | Global Constants  |        | g     |  c     |        | gc_max_discount   | 
- | 2.2 | Local Constants   |        | l     |  c     |        | lc_max_discount   | 
- | 3   | **Parameters**    |  -     |       |  -     |  -     |    -              |
- | 3.1 | Cursor Parameters |        |       | p      |        | p_customer        |
- | 3.2 | In Parameters     |        |       | p      |        | p_customer_id     | 
- | 3.3 | Out Parameters    |        |       | x      |        | x_customer_id     | 
- | 3.4 | In/Out Parameters |        |       | px     |        | px_customer_id    | 
- | 4   | **Other Objects** |  -     |       |   -    |   -    |     -             | 
- | 4.1 | Cursors           |        |       | cur    |        | cur_customers     |
- | 4.2 | Record            |        |       | r      |  type  | r_customer_type   | 
- | 4.3 | Array / Table     |        |       | t      |  type  | t_customers_type  |    
- | 4.4 | Objects           |        |       | o      |  type  | o_customers_type  |
- | 4.5 | Exceptions        |        |       | e      |        | e_customer_exists |
- | 4.6 | Exception Number  |        |       | en     |        | en_customer_exists|
- 
- 
-<br>
-
-### PL/SQL Objects Naming Standards
-
-<br>
-
-### PL/SQL Objects Coding Standards
-- 
-
-<br>
 
 ##### References
 [^1]: "**XXD**" is the custom database ORACLE schema association to my custom application called "Demasy Custom Applications".

From 83f85681392154f32d67efca11dd6917346b85e4 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:19:00 +0300
Subject: [PATCH 094/126] Rename
 database-standards-guidelines/sequences-standards.md to
 database-standards-guidelines/sequences-standards/README.md

---
 .../{sequences-standards.md => sequences-standards/README.md}     | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename database-standards-guidelines/{sequences-standards.md => sequences-standards/README.md} (100%)

diff --git a/database-standards-guidelines/sequences-standards.md b/database-standards-guidelines/sequences-standards/README.md
similarity index 100%
rename from database-standards-guidelines/sequences-standards.md
rename to database-standards-guidelines/sequences-standards/README.md

From 75910c508219df333c434131f25a1b7cf91c602c Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:23:03 +0300
Subject: [PATCH 095/126] Update "Database Standards Guidelines"

---
 database-standards-guidelines/README.md | 36 +++++++++----------------
 1 file changed, 13 insertions(+), 23 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 2f9d85d..ce53a09 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -1,40 +1,22 @@
 # Database Standards Guidelines
 
-- **Database Custom Objects Standards**
-  - <a href="#general-standards">**General Standards**</a>
-  - <a href="#tables-standards">**Tables Standards**</a>
-  - <a href="#sequences-standards">**Sequences Standards**</a>
-  - <a href="#views-standards">**Views Standards**</a>
-  - <a href="#packages-standards">**Packages Standards**</a>
-- Oracle PL/SQL Coding Standards
-- **Appendix**
-  - Naming Conventions Syntax Elements
-  - Database Custom Objects Naming Conventions
-
-<br>
-
-## General Standards
-
 - <a href="#general-syntax">**General Syntax**</a>
-- <a href="#">**General Standards**</a>
+- <a href="#general-standards">**General Standards**</a>
 
 <br>
 
-### General Syntax
-
-
-##### Syntax 
+## General Syntax
 
 > {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
 
 <br>
 
-### General Standards
+## General Standards
 
 - NEVER modify Oracle standard database objects.
 - You must follow standard naming conventions for creating new database objects.
 - The database object name `{object_name}` must be meaningful and brief.
-- Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the database objet name "*{object_name}*".
+- Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the database object name `{object_name}`.
 - The application/product short name `{app_short_name}` is a foreign key from Oracle standard table called "FND_APPLICATIONS".
 - The custom database objects must start with a custom database schema name for example "**XXD**". [^1]
 - You must create new database tables, sequences, and types, in the custom schema.
@@ -61,10 +43,18 @@
  13–NOV–1986 Ahmed El-Demasy Created
 */
 ```
+<br>
 
+## Database Custom Objects Standards by Type
+- **Database Custom Objects Standards**
+  - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/tables-standards">**Tables Standards**</a>
+  - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/sequences-standards">**Sequences Standards**</a>
+  - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/views-standards">**Views Standards**</a>
+  - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/packages-standards">**Packages Standards**</a>
+- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/plsql-coding-standards">**Oracle PL/SQL Coding Standards**</a>
 
-<br>
 
+<br>
 
 ##### References
 [^1]: "**XXD**" is the custom database ORACLE schema association to my custom application called "Demasy Custom Applications".

From e08283dcffe790f8daf0af52cf3ec4ecf4e073f9 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:28:19 +0300
Subject: [PATCH 096/126] Add "Syntax Elements"

---
 database-standards-guidelines/README.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index ce53a09..0b897cc 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -11,6 +11,22 @@
 
 <br>
 
+#### Syntax Elements
+  
+ | SEQ | Element Syntax      | Element Name                  | Description |
+ | :-: | :---                | :--                           | :--------   |
+ | 1   | *{custom_schema}*   | Custom Database Schema        | Database custom ORACLE schema name |
+ | 2   | *{separator}*       | Separator                     | Must use underscore “_” in database objects|
+ | 3   | *{app_short_name}*  | Application/Product Short Name| This is the application/product short name |
+ | 4   | *{prefix}*          | Prefix                        |  |
+ | 5   | *{object_name}*     | Database Object Name          |  |
+ | 6   | *{suffix}*          | Suffix                        |  |
+
+
+<br>
+
+
+
 ## General Standards
 
 - NEVER modify Oracle standard database objects.

From d9319e819cc160225bf7bdf7aad1e1bf06d1ce41 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:39:47 +0300
Subject: [PATCH 097/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 0b897cc..ec43a0b 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -30,12 +30,13 @@
 ## General Standards
 
 - NEVER modify Oracle standard database objects.
-- You must follow standard naming conventions for creating new database objects.
+- You must follow standard naming conventions and syntax for creating new database objects.
 - The database object name `{object_name}` must be meaningful and brief.
 - Do not use generic, all-purpose phrases like ”COMMON”, ”MISC”, ”OTHER”, or ”UTILITY” in the database object name `{object_name}`.
-- The application/product short name `{app_short_name}` is a foreign key from Oracle standard table called "FND_APPLICATIONS".
+- You must use the underscore “\_” as a separator `{separator}` between each word in the database object name.
 - The custom database objects must start with a custom database schema name for example "**XXD**". [^1]
-- You must create new database tables, sequences, and types, in the custom schema.
+- The application/product short name `{app_short_name}` is a foreign key from Oracle standard table called "FND_APPLICATIONS".
+- You must create new database tables, sequences, and types, in the custom schema for example "**XXD**". [^1]
 - You must create new database views and packages in the APPS schema.
 - Never create new stand-alone functions and procedures. Should be implemented as part of a package.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.

From e050323eb7ada0a255aa66d7b79559bd78f8278f Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:42:02 +0300
Subject: [PATCH 098/126] Update "General Standards"

---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index ec43a0b..9a02227 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -37,7 +37,7 @@
 - The custom database objects must start with a custom database schema name for example "**XXD**". [^1]
 - The application/product short name `{app_short_name}` is a foreign key from Oracle standard table called "FND_APPLICATIONS".
 - You must create new database tables, sequences, and types, in the custom schema for example "**XXD**". [^1]
-- You must create new database views and packages in the APPS schema.
+- You must create new database views and packages in the "**APPS**" schema.
 - Never create new stand-alone functions and procedures. Should be implemented as part of a package.
 - You must use grants and synonyms to allow other ORACLE schemas to access your custom objects and to enable your custom ORACLE ID access to Oracle Applications objects.
 - Include header information when you create your objects.

From 4f27ff48656383a3d75f12a768657a7d63030aee Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:53:24 +0300
Subject: [PATCH 099/126] Update "Table Naming Standards"

---
 .../tables-standards/README.md                | 30 ++++++++++---------
 1 file changed, 16 insertions(+), 14 deletions(-)

diff --git a/database-standards-guidelines/tables-standards/README.md b/database-standards-guidelines/tables-standards/README.md
index 1226067..f2f71d2 100644
--- a/database-standards-guidelines/tables-standards/README.md
+++ b/database-standards-guidelines/tables-standards/README.md
@@ -31,25 +31,24 @@
  | :-:  | :----                  | :-:    | :--:   | :---   | :---   | :----   |
  | 1    | Table                  | 20     | XXD    |  -     | -      | XXD_PO_LC_DOCUMENTS |
  | 2    | Temporary Table        | 20     | XXD    |  -     | TMP    | XXD_PO_LC_DOCS_TMP |
- | 3    | Data Upload Table [^2] | 20     | XXD    | TMP    | -      | TMP_PO_LC_DOCS | 
+ | 3    | Data Upload Table [^1] | 20     | XXD    | TMP    | -      | TMP_PO_LC_DOCS | 
  
 <br>
 
 ## Table Naming Standards
 
-- You MUST follow create database custom objects general standards.
-- The object name “*{object_name}*“ should be plural.
-- The table name should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
-- You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
-- You must create private synonyms for custom tables in APPS.
+- You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
+- The table name `{object_name}` should be plural.
+- The table name `{object_name}` should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
+- You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the "**APPS**" schema.
+- You must create private synonyms for custom tables in "**APPS**" schema.
 - You should add special WHO columns to your tables.
-- You should add concurrent program WHO Columns to your table.
-- You should add concurrent program WHO Columns to your table.
-- You should add descriptive flexfield (DFF) attribute Columns to your table.
-- New tables containing Flex-Fields or Oracle Alert columns must be registered with Oracle Application Object Library.
-- You should register your custom tables with Oracle AOL using the table registration API called AD_DD.
-  - AD_DD. REGISTER_TABLE
-  - AD_DD. REGISTER_COLUMN
+- You should add concurrent program WHO columns to your table.
+- You should add descriptive flexfield (DFF) attribute columns to your table.
+- New tables containing flexfield or Oracle Alert columns must be registered with Oracle Application Object Library (AOL).
+- You should register your custom tables with Oracle AOL using the table registration API called "**AD_DD**".
+  - `AD_DD.REGISTER_TABLE`
+  - `AD_DD.REGISTER_COLUMN`
 
 <br>
 
@@ -59,7 +58,7 @@
  | :--               | :----      | :-:      | :--          | :---   | 
  | CREATED_BY        | NUMBER(15) | NOT NULL | FND_USER     | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) |
  | CREATION_DATE     | DATE       | NOT NULL |              | SYSDATE |
- | LAST_UPDATED_BY   | NUMBER(15) | NOT NULL |              | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) | 
+ | LAST_UPDATED_BY   | NUMBER(15) | NOT NULL | FND_USER     | TO_NUMBER (FND_ PROFILE.VALUE (’USER_ID’)) | 
  | LAST_UPDATE_DATE  | DATE       | NOT NULL |              | SYSDATE |
  | LAST_UPDATE_LOGIN | NUMBER(15) |          |              | TO_NUMBER (FND_ PROFILE.VALUE (’LOGIN_ ID’)) |
  
@@ -83,3 +82,6 @@
  | - XXD_PO_LC_DOCUMENTS | - XXD_PO_LC_DOCUMENT <br> - PO_LC_DOCUMENTS       |
 
 <br>
+
+##### References
+[^1]: This is a custom table for data upload and migrations **ONLY** and should drop these tables after the upload data process finish.

From 1685da9f6dcb547da66bef8134043f11f343814e Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 20:56:58 +0300
Subject: [PATCH 100/126] Update "Packages Standards"

---
 .../packages-standards/README.md                         | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/database-standards-guidelines/packages-standards/README.md b/database-standards-guidelines/packages-standards/README.md
index c51c64f..e3be809 100644
--- a/database-standards-guidelines/packages-standards/README.md
+++ b/database-standards-guidelines/packages-standards/README.md
@@ -1,15 +1,10 @@
 # Packages Standards
 
-- <a href="#packages-naming-syntax">**Packages Naming Syntax**</a>
 - <a href="#packages-naming-convention">**Packages Naming Convention**</a>
 - <a href="#packages-naming-standards">**Packages Naming Standards**</a>
-- <a href="#packages-naming-examples">**Packages Naming Examples**</a>
 
 <br>
 
-## Packages Naming Syntax
-
-<br>
 
 ## Packages Naming Convention
 
@@ -29,7 +24,7 @@
 
 ## Packages Naming Standards
 
-- You MUST follow custom database objects general standards.
+- You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
 - You MUST place the new packages in the **APPS** schema.
 - The packages name `{object_name}` must be 27 characters or less for table handlers packages, and end with `PKG`.
 - The packages name `{object_name}` must be 27 characters or less for public packages, and end with `API`. 
@@ -37,5 +32,3 @@
 - The packages name `{object_name}` must be 30 characters or less for unit testing packages, and start with `UT`. 
 
 <br>
-
-## Packages Naming Examples

From 2b323ef0f7f2d882944366b1474eada79dd62813 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:01:06 +0300
Subject: [PATCH 101/126] Remove schema column from "Naming Convention"

Remove schema column from "Naming Convention" table
---
 .../tables-standards/README.md                         | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/database-standards-guidelines/tables-standards/README.md b/database-standards-guidelines/tables-standards/README.md
index f2f71d2..5e20bcc 100644
--- a/database-standards-guidelines/tables-standards/README.md
+++ b/database-standards-guidelines/tables-standards/README.md
@@ -27,11 +27,11 @@
 
 ## Table Naming Convention
 
- | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
- | :-:  | :----                  | :-:    | :--:   | :---   | :---   | :----   |
- | 1    | Table                  | 20     | XXD    |  -     | -      | XXD_PO_LC_DOCUMENTS |
- | 2    | Temporary Table        | 20     | XXD    |  -     | TMP    | XXD_PO_LC_DOCS_TMP |
- | 3    | Data Upload Table [^1] | 20     | XXD    | TMP    | -      | TMP_PO_LC_DOCS | 
+ | SEQ  | Object Name            | Length | Prefix | Suffix | Example |
+ | :-:  | :----                  | :-:    | :---   | :---   | :----   |
+ | 1    | Table                  | 20     |  -     | -      | XXD_PO_LC_DOCUMENTS |
+ | 2    | Temporary Table        | 20     |  -     | TMP    | XXD_PO_LC_DOCS_TMP |
+ | 3    | Data Upload Table [^1] | 20     | TMP    | -      | TMP_PO_LC_DOCS | 
  
 <br>
 

From eaeed7dab1aeb0022a5fde2b06b3754b908821a0 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:02:52 +0300
Subject: [PATCH 102/126] Update "Table Naming Examples"

---
 database-standards-guidelines/tables-standards/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/database-standards-guidelines/tables-standards/README.md b/database-standards-guidelines/tables-standards/README.md
index 5e20bcc..a8cbdf5 100644
--- a/database-standards-guidelines/tables-standards/README.md
+++ b/database-standards-guidelines/tables-standards/README.md
@@ -5,7 +5,7 @@
 - <a href="#table-naming-syntax">**Table Naming Syntax**</a>
 - <a href="#table-naming-convention">**Table Naming Convention**</a>
 - <a href="#table-naming-standards">**Table Naming Standards**</a>
-- <a href="#table-naming-example">**Table Naming Example**</a>
+- <a href="#table-naming-examples">**Table Naming Examples**</a>
 
 <br>
 
@@ -75,11 +75,11 @@
  
 <br>
 
-## Table Naming Example
+## Table Naming Examples
 
  | Better   | Bad        |
  | :---  | :---        |
- | - XXD_PO_LC_DOCUMENTS | - XXD_PO_LC_DOCUMENT <br> - PO_LC_DOCUMENTS       |
+ | - `XXD_PO_LC_DOCUMENTS` | - `XXD_PO_LC_DOCUMENT` <br> - `PO_LC_DOCUMENTS`       |
 
 <br>
 

From 761c15451a82dc9796b501f531dea336fd8b8c2e Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:04:56 +0300
Subject: [PATCH 103/126] Update "Sequence Naming Convention"

---
 .../sequences-standards/README.md              | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/database-standards-guidelines/sequences-standards/README.md b/database-standards-guidelines/sequences-standards/README.md
index 9d0db28..55f95e1 100644
--- a/database-standards-guidelines/sequences-standards/README.md
+++ b/database-standards-guidelines/sequences-standards/README.md
@@ -1,29 +1,29 @@
 # Sequences Standards
-- <a href="#sequence-naming-syntax">**Sequence Naming Syntax**</a>
 - <a href="#sequence-naming-convention">**Sequence Naming Convention**</a>
 - <a href="#sequence-naming-standards">**Sequence Naming Standards**</a>
-- <a href="#sequence-naming-examples">**Sequence Naming Examples**</a>
 
-<br>
-
-## Sequence Naming Syntax
 
 <br>
 
-
 ## Sequence Naming Convention
 
+<br>
+
+ | SEQ  | Object Name            | Length | Prefix | Suffix | Example |
+ | :-:  | :----                  | :-:    | :---   | :---   | :----   |
+ | 1    | Sequence               | 30     |  -     | SEQ    | `DOCUMENT_ID_SEQ` |
+ 
+ 
 <br>
 
 
 ## Sequence Naming Standards
+- You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
 - The sequence name `{object_name}` should be 30 characters or less and end with `_SEQ`.
-- You must place the new sequence in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the APPS schema.
+- You must place the new sequence in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the "**APPS**" schema.
 - Use each sequence to supply unique ID values for one column of one table.
 - Do not design sequences that wrap using the CYCLE option or have limited ranges using MAXVALUE.
 - Use a NUMBER datatype to store sequence values within PL/SQL.
 - Do Not Use the FND_UNIQUE_IDENTIFIER_CONTROL Table.
 
 <br>
-
-## Sequence Naming Examples

From 25190729017e1e2bb5ac5a9a5ff32f4d182ef0d8 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:14:41 +0300
Subject: [PATCH 104/126] Update "Views Naming Examples"

---
 .../views-standards/README.md                 | 23 ++++++++++++++-----
 1 file changed, 17 insertions(+), 6 deletions(-)

diff --git a/database-standards-guidelines/views-standards/README.md b/database-standards-guidelines/views-standards/README.md
index d44e2ca..d1df567 100644
--- a/database-standards-guidelines/views-standards/README.md
+++ b/database-standards-guidelines/views-standards/README.md
@@ -13,25 +13,36 @@
 
 ## Views Naming Syntax
 
+> {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
+
+
 <br>
 
 ## Views Naming Convention
 
- | SEQ  | Object Name            | Length | Schema | Prefix | Suffix | Example |
- | :-:  | :----                  | :-:    | :--:   | :---:  | :---   | :----   |
- | 1    | Views                  | 30     | APPS   |   -    |   V    | XXD_PO_LC_DOCUMENTS_V |
- | 2    | Materialized Views     | 30     | APPS   |   -    |   MV   | XXD_PO_LC_DOCUMENTS_MV |
+ | SEQ  | Object Name            | Length | Prefix | Suffix | Example |
+ | :-:  | :----                  | :-:    | :---:  | :---   | :----   |
+ | 1    | Views                  | 30     |   -    |   V    | `XXD_PO_LC_DOCUMENTS_V` |
+ | 2    | Materialized Views     | 30     |   -    |   MV   | `XXD_PO_LC_DOCUMENTS_MV` |
   
 <br>
 
 ## Views Naming Standards
-- The view name “*{object_name}*“ should be 30 characters or less and end with "_V" for view and "_VM" for materialized views.
-- The first column your view should select is the ROWID for the root table, and the view should alias it to ROW_ID.
+- The view name `{object_name}` should be 30 characters or less and end with "**V**" for view and "**VM**" for materialized views.
+- The first column your view should select is the ROWID for the root table, and the view should alias it to "**ROW_ID**".
 - You only need to include the ROWID column if an Oracle Forms block is based on this view.
 
 <br>
 
 ## Views Naming Examples
 
+<br>
+
+ | Better   | Bad        |
+ | :---  | :---        |
+ | - `XXD_PER_EMPLOYEE_INFO_V` <br>  - `XXD_PO_ORDERS_APPROVED_V` <br>  - `XXD_PO_ORDERS_REJECTED_V` <br>  - `XXD_INV_ALL_ITEMS_MV` |     |
+
+<br>
+
 <br>
 

From 64648c0cd668fccb8b044dd2acfc4a4c45e72bd0 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:16:46 +0300
Subject: [PATCH 105/126] Update "Views Naming Syntax"

---
 database-standards-guidelines/views-standards/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/views-standards/README.md b/database-standards-guidelines/views-standards/README.md
index d1df567..41f690a 100644
--- a/database-standards-guidelines/views-standards/README.md
+++ b/database-standards-guidelines/views-standards/README.md
@@ -13,7 +13,7 @@
 
 ## Views Naming Syntax
 
-> {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{suffix}]
+> {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{criteria}][Optional {separator}{suffix}]
 
 
 <br>

From 5a389de986590c2ee4a9719bea1b833b47775897 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:17:52 +0300
Subject: [PATCH 106/126] Add "general standards" point

---
 database-standards-guidelines/views-standards/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/database-standards-guidelines/views-standards/README.md b/database-standards-guidelines/views-standards/README.md
index 41f690a..4d6d873 100644
--- a/database-standards-guidelines/views-standards/README.md
+++ b/database-standards-guidelines/views-standards/README.md
@@ -28,6 +28,7 @@
 <br>
 
 ## Views Naming Standards
+- You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
 - The view name `{object_name}` should be 30 characters or less and end with "**V**" for view and "**VM**" for materialized views.
 - The first column your view should select is the ROWID for the root table, and the view should alias it to "**ROW_ID**".
 - You only need to include the ROWID column if an Oracle Forms block is based on this view.

From 4280c5dc109da25f85472c934dfb1b5162f3ee70 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:20:20 +0300
Subject: [PATCH 107/126] Update bad examples

---
 database-standards-guidelines/views-standards/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/views-standards/README.md b/database-standards-guidelines/views-standards/README.md
index 4d6d873..efdfc33 100644
--- a/database-standards-guidelines/views-standards/README.md
+++ b/database-standards-guidelines/views-standards/README.md
@@ -41,7 +41,7 @@
 
  | Better   | Bad        |
  | :---  | :---        |
- | - `XXD_PER_EMPLOYEE_INFO_V` <br>  - `XXD_PO_ORDERS_APPROVED_V` <br>  - `XXD_PO_ORDERS_REJECTED_V` <br>  - `XXD_INV_ALL_ITEMS_MV` |     |
+ | - `XXD_PER_EMPLOYEE_INFO_V` <br>  - `XXD_PO_ORDERS_APPROVED_V` <br>  - `XXD_PO_ORDERS_REJECTED_V` <br>  - `XXD_INV_ALL_ITEMS_MV` |  - `PER_EMPLOYEE_INFO_V` <br>  - `XXD_HR_EMPLOYEE_INFO_V` <br>  - `XXD_PO_ORDERS_REJECTED`|
 
 <br>
 

From b5099d83aeeaf1bbda82596c942cfa01fc225b6a Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:23:12 +0300
Subject: [PATCH 108/126] Update "Packages Naming Standards"

---
 database-standards-guidelines/packages-standards/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/packages-standards/README.md b/database-standards-guidelines/packages-standards/README.md
index e3be809..cf623c2 100644
--- a/database-standards-guidelines/packages-standards/README.md
+++ b/database-standards-guidelines/packages-standards/README.md
@@ -25,7 +25,7 @@
 ## Packages Naming Standards
 
 - You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
-- You MUST place the new packages in the **APPS** schema.
+- You MUST place the new packages in the "**APPS**" schema.
 - The packages name `{object_name}` must be 27 characters or less for table handlers packages, and end with `PKG`.
 - The packages name `{object_name}` must be 27 characters or less for public packages, and end with `API`. 
 - The packages name `{object_name}` must be 27 characters or less for private packages, and end with `PVT`. 

From a8193df4fe1be3e38ae40a0b04e080a23551caaf Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:29:16 +0300
Subject: [PATCH 109/126] Add "Specific Database Object Types Standards"

---
 database-standards-guidelines/README.md | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 9a02227..756a24c 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -2,6 +2,7 @@
 
 - <a href="#general-syntax">**General Syntax**</a>
 - <a href="#general-standards">**General Standards**</a>
+- <a href="#general-standards">**Specific Database Object Types Standards**</a>
 
 <br>
 
@@ -62,13 +63,11 @@
 ```
 <br>
 
-## Database Custom Objects Standards by Type
-- **Database Custom Objects Standards**
-  - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/tables-standards">**Tables Standards**</a>
-  - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/sequences-standards">**Sequences Standards**</a>
-  - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/views-standards">**Views Standards**</a>
-  - <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/packages-standards">**Packages Standards**</a>
-- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/plsql-coding-standards">**Oracle PL/SQL Coding Standards**</a>
+## Specific Database Object Types Standards
+- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/tables-standards">**Tables Standards**</a>
+- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/sequences-standards">**Sequences Standards**</a>
+- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/views-standards">**Views Standards**</a>
+- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines/packages-standards">**Packages Standards**</a>
 
 
 <br>

From e1222ee80a97454df7ec79c532697aa4f022692c Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:30:29 +0300
Subject: [PATCH 110/126] Update "Specific Database Object Standards" link

Specific Database Object Types Standards
---
 database-standards-guidelines/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 756a24c..6972908 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -2,7 +2,7 @@
 
 - <a href="#general-syntax">**General Syntax**</a>
 - <a href="#general-standards">**General Standards**</a>
-- <a href="#general-standards">**Specific Database Object Types Standards**</a>
+- <a href="#specific-database-object-types-standards">**Specific Database Object Types Standards**</a>
 
 <br>
 

From 274c22b8f9227eba991d9cc5623e9cf0d41edc8e Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:34:13 +0300
Subject: [PATCH 111/126] Update "Appendix" content links

---
 database-standards-guidelines/appendix/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database-standards-guidelines/appendix/README.md b/database-standards-guidelines/appendix/README.md
index fd73849..3085f7a 100644
--- a/database-standards-guidelines/appendix/README.md
+++ b/database-standards-guidelines/appendix/README.md
@@ -1,3 +1,3 @@
 # Appendix
-- Naming Conventions Syntax Elements
-- Database Custom Objects Naming Conventions
+- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/blob/main/database-standards-guidelines/appendix/database-objects-naming-conventions.md">**Naming Conventions Syntax Elements**</a>
+- <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/blob/main/database-standards-guidelines/appendix/syntax-elements-description.md">**Database Custom Objects Naming Conventions**</a>

From 76e1d6e7dce570fe01aa5cb4d04e37fd1a4ae5cc Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:35:56 +0300
Subject: [PATCH 112/126] Remove "PL/SQL Objects Coding Standards"

---
 .../plsql-coding-standards/README.md                          | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/database-standards-guidelines/plsql-coding-standards/README.md b/database-standards-guidelines/plsql-coding-standards/README.md
index b241ffe..48dba33 100644
--- a/database-standards-guidelines/plsql-coding-standards/README.md
+++ b/database-standards-guidelines/plsql-coding-standards/README.md
@@ -38,7 +38,3 @@
 
 <br>
 
-## PL/SQL Objects Coding Standards
-- 
-
-<br>

From 095aed8ad41fca9b2a4988982e332c9a7050c04e Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:39:29 +0300
Subject: [PATCH 113/126] Update "Syntax"

---
 .../plsql-coding-standards/README.md                   | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/database-standards-guidelines/plsql-coding-standards/README.md b/database-standards-guidelines/plsql-coding-standards/README.md
index 48dba33..a4810b9 100644
--- a/database-standards-guidelines/plsql-coding-standards/README.md
+++ b/database-standards-guidelines/plsql-coding-standards/README.md
@@ -4,7 +4,7 @@
 
 ## Syntax 
 
-> {scope}{prefix}{separator}{identifier_name}{separator}{suffix}
+> {scope}{separator}[Optional {prefix}{separator}]{identifier_name}[Optional {separator}{suffix}]
 
 <br>
 
@@ -12,10 +12,10 @@
 
  | SEQ | Object Name       | Length | scope | Prefix | Suffix | Example           |
  | :-  | :----             | :-:    | :--   | :---   | :--    | :----             |
- | 1   | **Variables**     |        |       |        |        |                  |
- | 1.1 | Global Variable   |        | g     |    _   |        | g_enterprise_id   | 
- | 1.2 | Local Variable    |        | l     |    _   |        | l_customer_id     | 
- | 2   | **Constants**     |        |       |        |       |                  |
+ | 1   | **Variables**     |   -    |  -    |  -     | -      |  -               |
+ | 1.1 | Global Variable   |        | g     |        |        | g_enterprise_id   | 
+ | 1.2 | Local Variable    |        | l     |        |        | l_customer_id     | 
+ | 2   | **Constants**     | -      | -     |  -     | -      | -                 |
  | 2.1 | Global Constants  |        | g     |  c     |        | gc_max_discount   | 
  | 2.2 | Local Constants   |        | l     |  c     |        | lc_max_discount   | 
  | 3   | **Parameters**    |  -     |       |  -     |  -     |    -              |

From 46ce8ca95a315b780c1f43b052a74ffdcef8f531 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:42:33 +0300
Subject: [PATCH 114/126] Add "Oracle PL/SQL Coding Standards" contents

---
 .../plsql-coding-standards/README.md                       | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/database-standards-guidelines/plsql-coding-standards/README.md b/database-standards-guidelines/plsql-coding-standards/README.md
index a4810b9..5af11d1 100644
--- a/database-standards-guidelines/plsql-coding-standards/README.md
+++ b/database-standards-guidelines/plsql-coding-standards/README.md
@@ -1,7 +1,14 @@
 # Oracle PL/SQL Coding Standards
 
+
 <br>
 
+- <a href="#plsql-objects-naming-convention">**PL/SQL Objects Naming Convention**</a>
+- <a href="#plsql-objects-naming-standards">**PL/SQL Objects Naming Standards**</a>
+
+<br>
+
+
 ## Syntax 
 
 > {scope}{separator}[Optional {prefix}{separator}]{identifier_name}[Optional {separator}{suffix}]

From 9e00ca530d7db20886213d47d7e2ac7a958514f8 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:44:07 +0300
Subject: [PATCH 115/126] Add "Syntax" conent link

---
 database-standards-guidelines/plsql-coding-standards/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/database-standards-guidelines/plsql-coding-standards/README.md b/database-standards-guidelines/plsql-coding-standards/README.md
index 5af11d1..972e988 100644
--- a/database-standards-guidelines/plsql-coding-standards/README.md
+++ b/database-standards-guidelines/plsql-coding-standards/README.md
@@ -3,6 +3,7 @@
 
 <br>
 
+- <a href="#syntax">**Syntax**</a>
 - <a href="#plsql-objects-naming-convention">**PL/SQL Objects Naming Convention**</a>
 - <a href="#plsql-objects-naming-standards">**PL/SQL Objects Naming Standards**</a>
 

From d70a1f4798a62dade112c5dac99065ee6213dc2d Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:44:58 +0300
Subject: [PATCH 116/126] Remove "Naming Standards"

---
 .../plsql-coding-standards/README.md                       | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/database-standards-guidelines/plsql-coding-standards/README.md b/database-standards-guidelines/plsql-coding-standards/README.md
index 972e988..16ea505 100644
--- a/database-standards-guidelines/plsql-coding-standards/README.md
+++ b/database-standards-guidelines/plsql-coding-standards/README.md
@@ -5,7 +5,7 @@
 
 - <a href="#syntax">**Syntax**</a>
 - <a href="#plsql-objects-naming-convention">**PL/SQL Objects Naming Convention**</a>
-- <a href="#plsql-objects-naming-standards">**PL/SQL Objects Naming Standards**</a>
+- <a href="">**PL/SQL Objects Naming Standards**</a>
 
 <br>
 
@@ -41,8 +41,3 @@
  
  
 <br>
-
-## PL/SQL Objects Naming Standards
-
-<br>
-

From ba670ed04cd679d8f8c207fd735bc6006024d60e Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:45:36 +0300
Subject: [PATCH 117/126] Remove "PL/SQL Objects Naming Standards" link

---
 database-standards-guidelines/plsql-coding-standards/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/plsql-coding-standards/README.md b/database-standards-guidelines/plsql-coding-standards/README.md
index 16ea505..5d8e9d1 100644
--- a/database-standards-guidelines/plsql-coding-standards/README.md
+++ b/database-standards-guidelines/plsql-coding-standards/README.md
@@ -5,7 +5,7 @@
 
 - <a href="#syntax">**Syntax**</a>
 - <a href="#plsql-objects-naming-convention">**PL/SQL Objects Naming Convention**</a>
-- <a href="">**PL/SQL Objects Naming Standards**</a>
+- PL/SQL Objects Naming Standards
 
 <br>
 

From 563e13dcadc7ffab89dc07c19a2c3654a20979dd Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:46:52 +0300
Subject: [PATCH 118/126] Update incorrect "Example"

---
 database-standards-guidelines/sequences-standards/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/sequences-standards/README.md b/database-standards-guidelines/sequences-standards/README.md
index 55f95e1..654bb84 100644
--- a/database-standards-guidelines/sequences-standards/README.md
+++ b/database-standards-guidelines/sequences-standards/README.md
@@ -11,7 +11,7 @@
 
  | SEQ  | Object Name            | Length | Prefix | Suffix | Example |
  | :-:  | :----                  | :-:    | :---   | :---   | :----   |
- | 1    | Sequence               | 30     |  -     | SEQ    | `DOCUMENT_ID_SEQ` |
+ | 1    | Sequence               | 30     |  -     | SEQ    | `XXD_DOCUMENT_ID_SEQ` |
  
  
 <br>

From 614e9663c5b5a8faab9b1f48809672f6689f587a Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:55:52 +0300
Subject: [PATCH 119/126] Add "primary key" point in "Table Standards"

Add "primary key" point in "Table Naming Standards"
---
 database-standards-guidelines/tables-standards/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/database-standards-guidelines/tables-standards/README.md b/database-standards-guidelines/tables-standards/README.md
index a8cbdf5..0048e91 100644
--- a/database-standards-guidelines/tables-standards/README.md
+++ b/database-standards-guidelines/tables-standards/README.md
@@ -42,6 +42,7 @@
 - The table name `{object_name}` should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
 - You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the "**APPS**" schema.
 - You must create private synonyms for custom tables in "**APPS**" schema.
+- The table MUST include a primary key column and supply value from a specific sequence.
 - You should add special WHO columns to your tables.
 - You should add concurrent program WHO columns to your table.
 - You should add descriptive flexfield (DFF) attribute columns to your table.

From 85d6b951bd2ce5cacfc4ba2c5625660917e7eeeb Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 21:58:35 +0300
Subject: [PATCH 120/126] Update "primary key (PK)"

---
 database-standards-guidelines/tables-standards/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/tables-standards/README.md b/database-standards-guidelines/tables-standards/README.md
index 0048e91..548ea44 100644
--- a/database-standards-guidelines/tables-standards/README.md
+++ b/database-standards-guidelines/tables-standards/README.md
@@ -42,7 +42,7 @@
 - The table name `{object_name}` should be 20 characters or less. It can be longer, but you need to abbreviate it for the table handler package name, which must be 27 characters or less.
 - You must place the new tables in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the "**APPS**" schema.
 - You must create private synonyms for custom tables in "**APPS**" schema.
-- The table MUST include a primary key column and supply value from a specific sequence.
+- The table MUST include a primary key (PK) column and supply value from a specific sequence.
 - You should add special WHO columns to your tables.
 - You should add concurrent program WHO columns to your table.
 - You should add descriptive flexfield (DFF) attribute columns to your table.

From 03e798f0a0527e24672b7512cc9ac5fc25dafb10 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 22:01:37 +0300
Subject: [PATCH 121/126] Update "Contect" name and links

---
 .../tables-standards/README.md                 | 18 ++++++++----------
 1 file changed, 8 insertions(+), 10 deletions(-)

diff --git a/database-standards-guidelines/tables-standards/README.md b/database-standards-guidelines/tables-standards/README.md
index 548ea44..3589d08 100644
--- a/database-standards-guidelines/tables-standards/README.md
+++ b/database-standards-guidelines/tables-standards/README.md
@@ -2,14 +2,14 @@
 
 <br>
 
-- <a href="#table-naming-syntax">**Table Naming Syntax**</a>
-- <a href="#table-naming-convention">**Table Naming Convention**</a>
-- <a href="#table-naming-standards">**Table Naming Standards**</a>
-- <a href="#table-naming-examples">**Table Naming Examples**</a>
+- <a href="#naming-syntax">**Naming Syntax**</a>
+- <a href="#naming-convention">**Naming Convention**</a>
+- <a href="#standards">**Standards**</a>
+- <a href="#examples">**Examples**</a>
 
 <br>
 
-## Table Naming Syntax
+## Naming Syntax
 
 ##### Syntax 
 
@@ -21,11 +21,9 @@
 
 > {prefix}{separator}{app_short_name}{separator}{object_name}
 
-
-
 <br>
 
-## Table Naming Convention
+## Naming Convention
 
  | SEQ  | Object Name            | Length | Prefix | Suffix | Example |
  | :-:  | :----                  | :-:    | :---   | :---   | :----   |
@@ -35,7 +33,7 @@
  
 <br>
 
-## Table Naming Standards
+## Standards
 
 - You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
 - The table name `{object_name}` should be plural.
@@ -76,7 +74,7 @@
  
 <br>
 
-## Table Naming Examples
+## Examples
 
  | Better   | Bad        |
  | :---  | :---        |

From 8eee04e85bdfc1cab9923d1246864fc56dab6f6c Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 22:03:30 +0300
Subject: [PATCH 122/126] update Content name and links

---
 .../packages-standards/README.md                     | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/database-standards-guidelines/packages-standards/README.md b/database-standards-guidelines/packages-standards/README.md
index cf623c2..0dbcb69 100644
--- a/database-standards-guidelines/packages-standards/README.md
+++ b/database-standards-guidelines/packages-standards/README.md
@@ -1,12 +1,16 @@
 # Packages Standards
 
-- <a href="#packages-naming-convention">**Packages Naming Convention**</a>
-- <a href="#packages-naming-standards">**Packages Naming Standards**</a>
+<br>
+
+- Naming Syntax
+- <a href="#naming-convention">**Naming Convention**</a>
+- <a href="#standards">**Standards**</a>
+- Naming Syntax
 
 <br>
 
 
-## Packages Naming Convention
+## Naming Convention
 
 
  | SEQ  | Object Name              | Length | Prefix | Suffix | Example |
@@ -22,7 +26,7 @@
  
 <br>
 
-## Packages Naming Standards
+## Standards
 
 - You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
 - You MUST place the new packages in the "**APPS**" schema.

From 46fadd0a2f72afaa655b9e7c43426a89cc5e3c66 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 22:05:05 +0300
Subject: [PATCH 123/126] Update "Examples"

---
 database-standards-guidelines/packages-standards/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/database-standards-guidelines/packages-standards/README.md b/database-standards-guidelines/packages-standards/README.md
index 0dbcb69..694b92c 100644
--- a/database-standards-guidelines/packages-standards/README.md
+++ b/database-standards-guidelines/packages-standards/README.md
@@ -5,7 +5,7 @@
 - Naming Syntax
 - <a href="#naming-convention">**Naming Convention**</a>
 - <a href="#standards">**Standards**</a>
-- Naming Syntax
+- Examples
 
 <br>
 

From 4e0dd24e583750f60260909a2a75f68be02fd4a1 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 22:05:58 +0300
Subject: [PATCH 124/126] Update "Content" name and links

---
 .../sequences-standards/README.md                    | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/database-standards-guidelines/sequences-standards/README.md b/database-standards-guidelines/sequences-standards/README.md
index 654bb84..2b64871 100644
--- a/database-standards-guidelines/sequences-standards/README.md
+++ b/database-standards-guidelines/sequences-standards/README.md
@@ -1,11 +1,15 @@
 # Sequences Standards
-- <a href="#sequence-naming-convention">**Sequence Naming Convention**</a>
-- <a href="#sequence-naming-standards">**Sequence Naming Standards**</a>
 
+<br>
+
+- Naming Syntax
+- <a href="#naming-convention">**Naming Convention**</a>
+- <a href="#standards">**Standards**</a>
+- Examples
 
 <br>
 
-## Sequence Naming Convention
+## Naming Convention
 
 <br>
 
@@ -17,7 +21,7 @@
 <br>
 
 
-## Sequence Naming Standards
+## Standards
 - You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
 - The sequence name `{object_name}` should be 30 characters or less and end with `_SEQ`.
 - You must place the new sequence in the custom ORACLE schema, for example, "**XXD**", and grant privileges to the "**APPS**" schema.

From 75689b3155cd2f795d6a4c51ee1254eb31937e58 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 22:07:24 +0300
Subject: [PATCH 125/126] Update "Views Standards" content and links

---
 .../views-standards/README.md                 | 20 ++++++++-----------
 1 file changed, 8 insertions(+), 12 deletions(-)

diff --git a/database-standards-guidelines/views-standards/README.md b/database-standards-guidelines/views-standards/README.md
index efdfc33..6340458 100644
--- a/database-standards-guidelines/views-standards/README.md
+++ b/database-standards-guidelines/views-standards/README.md
@@ -2,23 +2,21 @@
 
 <br>
 
-- <a href="#views-naming-syntax">**Views Naming Syntax**</a>
-- <a href="#views-naming-convention">**Views Naming Convention**</a>
-- <a href="#views-naming-standards">**Views Naming Standards**</a>
-- <a href="#views-naming-examples">**Views Naming Examples**</a>
-
-
+- <a href="#naming-syntax">**Naming Syntax**</a>
+- <a href="#naming-convention">**Naming Convention**</a>
+- <a href="#standards">**Standards**</a>
+- <a href="#examples">**Examples**</a>
 
 <br>
 
-## Views Naming Syntax
+## Naming Syntax
 
 > {custom_schema}{separator}{app_short_name}{separator}[Optional {prefix}{separator}]{object_name}[Optional {separator}{criteria}][Optional {separator}{suffix}]
 
 
 <br>
 
-## Views Naming Convention
+## Naming Convention
 
  | SEQ  | Object Name            | Length | Prefix | Suffix | Example |
  | :-:  | :----                  | :-:    | :---:  | :---   | :----   |
@@ -27,7 +25,7 @@
   
 <br>
 
-## Views Naming Standards
+## Standards
 - You MUST follow database custom objects <a href="https://github.com/demasy/Oracle-EBS-Development-Guidelines/tree/main/database-standards-guidelines">**general standards**</a>.
 - The view name `{object_name}` should be 30 characters or less and end with "**V**" for view and "**VM**" for materialized views.
 - The first column your view should select is the ROWID for the root table, and the view should alias it to "**ROW_ID**".
@@ -35,7 +33,7 @@
 
 <br>
 
-## Views Naming Examples
+## Examples
 
 <br>
 
@@ -45,5 +43,3 @@
 
 <br>
 
-<br>
-

From c18b1a67e91ea496a82c391c724cec698ef86813 Mon Sep 17 00:00:00 2001
From: Ahmed El-Demasy <39886429+demasy@users.noreply.github.com>
Date: Fri, 16 Sep 2022 22:09:03 +0300
Subject: [PATCH 126/126] Add "Oracle PL/SQL Coding Standards" in content

Add "Oracle PL/SQL Coding Standards" in the content section
---
 database-standards-guidelines/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/database-standards-guidelines/README.md b/database-standards-guidelines/README.md
index 6972908..9c51830 100644
--- a/database-standards-guidelines/README.md
+++ b/database-standards-guidelines/README.md
@@ -3,6 +3,7 @@
 - <a href="#general-syntax">**General Syntax**</a>
 - <a href="#general-standards">**General Standards**</a>
 - <a href="#specific-database-object-types-standards">**Specific Database Object Types Standards**</a>
+- Oracle PL/SQL Coding Standards
 
 <br>