How To Fix AFX_WIZARDS116 - Primary key of the master table does not permit dynamic package formation

SAP Error Message - Details

• Message type: E = Error

• Message class: AFX_WIZARDS - Messages from AFX Wizards

• Message number: 116

• Message text: Primary key of the master table does not permit dynamic package formation

What causes this issue?

The system has generated a default entry for the global control of
archiving automatically.

System Response

When checking the default entry, the system found that the primary key
for the master application table is not a GUID. Therefore, dynamic
package formation is not possible.
The "Dynamic Package Formation Permitted" indicator will be set,
however, to prevent a deadlock scenario from occurring when maintaining
the global Customizing settings. In Customizing, you must either permit
dynamic package formation or implement and assign a package formation
procedure.
This also means that the system cannot generate any coding for dynamic
package formation in the other generation steps for the analysis and
write programs. Here you must make manual changes at a later time since
the generated program would not be able to run as it is now.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

You must either implement dynamic package formation or a package
formation procedure. Then you must maintain the global control of
archiving accordingly.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AFX_WIZARDS116 - Primary key of the master table does not permit dynamic package formation ?

  The SAP error message AFX_WIZARDS116 indicates that there is an issue with the primary key of the master table when trying to create a dynamic package. This error typically arises in the context of SAP Data Services or SAP BW when working with data models or transformations.
  
  Cause:
  The error occurs because the primary key of the master table does not meet the requirements for dynamic package formation. This can happen due to several reasons:
  
  Non-Unique Primary Key: The primary key defined in the master table may not be unique, which is essential for creating dynamic packages.
  Composite Keys: If the primary key is a composite key (i.e., made up of multiple columns), it may not be properly defined or may not allow for dynamic package formation.
  Data Type Mismatch: There may be a mismatch in data types between the primary key fields and the fields being used in the dynamic package.
  Missing Key Fields: Some