When Group Memberships are not being applied, I have noticed the following
1. The group already exists in Metadata, in that case you would need to use the User Synchronization process to updating existing users and groups, more information at the link here
2. The grpmems table contains memberships to groups that are not in the idgrps table. In that case, check idgrps and grpmems table to ensure that the Unique Key for the group matches a group in the idgrps table.
3. If you are getting the following error
ERROR: The method is not directed at a repository. (The Reposid parameter is blank.)
This problem occurs when the KEYID value an identity group (the default value is the distinguishedName for the group) is greater than 128 bytes. A workaround is to use DATA step logic to truncate the KEYID value for groups to 128 bytes within the canonical tables prior to running the MDUIMPLB macro.
For example, you can add the following steps immediately prior to the MDUIMPLB macro call, this is based on the importad.sas sample program:
Usage Note 40628: Automating the addition of users and groups to a SAS® Metadata Repository
data adir.grpmems; length grpkeyid $ 128; set adir.grpmems;
data adir.idgrps; length keyid $ 128; set adir.idgrps;
run;
... View more