AR Territory and Transaction Flexfield Setup - Future Considerations
Based on our current business requirements, we do not need anything more than a one segment FF for both the Transaction AND Territory FFs. It is not expected that we will ever need anything more than this for the business that we are currently implementing on our Global Instance. (note: we have an interface with Oracle PM that requires definition of the Transaction FF even though Autoinvoice accounting is 100% driven by our PM config)
HOWEVER, we may decide to use AR for other businesses on our global instance at a later date (in separate op units). Since the Transaction and Territoty FFs are global and can only have one definition per INSTANCE, we are struggling with how to provide flexibility for "potential" future implementations on the same instance.