Using a GUID for custom tables?

Question

As far as I know, SAP CRM and HANA use a GUID to uniquely identify records instead of using classic incremental integers. Are there best practices or clear guidelines that cover their use?

Here are some factors that I have considered in favor of a GUID:

• Offline creation of objects. IIRC GUIDs are almost guaranteed to be unique in these situations, so merging or integrating disparate datasets is not a problem.
• Surrogate keys have excellent developmental benefits. Although incrementing integers is a form of a surrogate key, using different orders of numbers can impose a functional value on them.

And some scripts that prefer classic keys:

• Users require human-readable keys to identify entries in the system. This can be handled in GUID tables, also by specifying an external identifier with a readable value.
• Users want to use numerical sequences to identify different types of records, similar to sales or purchase documents. Although I really consider this poor design.

In which user development scenarios do you prefer the GUID over the classic keys?

Is it helpful to use common GUID usage for all tables ?

Answer 1

: , ( , ABAP, ). GUID . , , , GUID, , . , 255, 120, . GUID , . , , GUID - , / .

GUID , " ABAP ". GUID , . (, , , , GUID ). , , , GUID. - - , GUID () , .