Hi Joel
Harinam has already covered a large bit. Just some thing to consider:
EAM access approval is using the same MSMP workflow as ARQ. It's good you are using request type 006. You will need an initiatior rule that includes the Request Type so you can split out =006 vs <>006. I'm not sure if you are using ARQ for general provisioning, however, catering for the request type now does future proof your solution a bit
As far as handling the next piece, it really depends on whether you have a single step approval that is common for both scenarios. If for example, both had to be approved by FF OWNER but only one has to be approved by the SUPPORT MANAGER, then you could have a Path that request type 006 goes to in the initiator rule and add a routing rule to check if the request has to go the a new path for the Support Manager.
Alternatively, you could hand both scenarios back in the Initiator Rule and check for Request Type, System and Function Areas (not quite sure how function area maps back to FFId). If certain FF Ids needed additional approval, I would then put a check on the FF Id and use a naming convention. In taking this option, you would have two results from BRF+ for FF and in the MSMP you would map each to a different path. One path would have single step approval and the other would have dual. You would need to manage this at line item level to include the system in the check. Harinam pretty much summarised this
There are a few documents in SCN explaining the BRF+ rules and MSMP overview that will help you. The key to getting it to work is to figure out how to design your process flow (i.e. do you split at the Initiator or do you use routing).
Regards
Colleen