Today, people asked me how the role was transferred. I did this a long time ago. Because the role also needs to bring a profile, and then it is not a workbench request, but a customized request. So I keep it here, you can check it out for yourself. After all, after a long time, I will forget it. . . But after a glance, he came back.
BW's architecture is generally three-tier, development, testing, and production. Then we usually build a role in the development system, and then pass it to production after testing.
Article Directory
Create role/transfer role
PFCG creates a role. Generally, we build a single role, comp.role I forgot. 
Then come in and give the description and permissions. The creation of role can also be written in a large part, which is simplified here.
After the permissions are set, click the ball to generate a profile parameter file. 
The permissions document is there. Exit after saving.
Then we will transmit.
Go back to the PFCG page:
if only the current single role is uploaded:
directly click on the trolley to pass:
check the first two: generate profile and personalized data (I don’t know how to translate this), the
last user assignment is not selected, because of this Role is for different clients. The users of the development system and the production system are different. This user assignment cannot be selected, and it is impossible for every system user to be the same.
Click Execute, and the request interface will come out.
It is a customized request, and because the role is for the client, this request is not a workbench request, but a customized request.
If you create a request first, you must create a customizing request, and then fill it in here, if not, create a new one here. Then transfer.
If you have many roles to pass, then PFCG->Utilities->Mass transport
will fill in the names of the many roles you want to pass.
Note that personalization data should also be selected, and then the steps to fill in the request are the same.
