Professional Documents
Culture Documents
1.
2. Create PUPS PSB member - PUPS option 20. (type PSBBATCH, CMPG)
- you can copy the profile from an existing PSBBATCH member
- create it as a BA, it will create the BT when you assemble it
3. Checkout your PSB -- PUPS option 1
4. Create your PSB, in FCU@BLD.CMPG.TEST.PSB
5.
Submit your PSB to be assembled (just submit using the PUPS option 3 compile)
6. You will need to migrate the PUPS PSB (type PSBBATCH) member though each
environment (INTE, FRST, QA) This PUPS move is how the PSB will be gen'd for each
environment
7.
You will need to move the PSB to PROD at least 1 week prior to the time that you are
launching your program. It will move from FRST, but it does require a CMR.
If it is a new program and you can do it sooner, that is probably better, but the bottom
line is that the gen's are done on the weekend, so if you put in a new PSB on the same
day as your program (M-F), you will not be able to run it until after the weekend (unless
you can get Tech Support to "gen" it sooner)
2.
3. Submit your PSB to be assembled (just submit using the PUPS option 5 compile)
4. You will need to migrate the PUPS PSB (type PSBBATCH) member though each
environment (INTE, FRST, QA) This PUPS move is how the PSB will be gen'd for each
environment
5.
You will need to move the PSB to PROD at least 1 week prior to the time that you are
launching your program. It will move from FRST, but it does require a CMR.
If it is a new program and you can do it sooner, that is probably better, but the bottom
line is that the gen's are done on the weekend, so if you put in a new PSB on the same
day as your program (M-F), you will not be able to run it until after the weekend (unless
you can get Tech Support to "gen" it sooner)