One and multiple XLA table(s)
If there is only one XLA table in the BG, only the private XLA table needs the Access codes to be created by the craft (i.e., call pickup access code, source-BG access code, and destination access codes).
If there are multiple private XLA tables in a BG where an XLA table serves a CPU group member subscriber, each XLA table will need at least the call pickup access code to be created. The SIPQ EP(s) used for NW-wide group CPU could be assigned to the Common XLA table. In this case, the source and destination access codes do not need to be created in each private XLA table. But if EPs need to be assigned to private XLA table(s), then the private XLA table(s) need to include the source and destination access codes and their result (or point to the Common XLA table).
As an option, when the craft has provisioned a Common XLA table, the access codes may be created in the Common XLA table, but, the private XLA tables still need to point/access the Common table, either via a rule or with the actual access code value.
The source-BG access
is not needed, even if assigned, if both of the following are true:
no network-wide group CPUs exist in the BGParent topic: Access Code Routing Concept
Path Replacement -Access -Code -Routing is set to 'off'