Explanation
Reference Data Sets
You begin this part of your implementation by creating and assigning reference data to sets. Make changes carefully as changes to a particular set affect all business units or application components using that set. You can assign a separate set to each business unit for the typeofobject that is being shared. For example, assign separate sets for payment terms, transaction types, and sales methods to your business units.
Your enterprise can determine that certain aspects of your corporate policy can affect all business units. The remaining aspects are at the discretion of the business unit manager to implement. This allows your enterprise to balance autonomy and control for each business unit. For example, your enterprise holds business unit managers accountable for their profitand loss, but manages working capital requirements at a corporate level.
In such a case, you can let managers define their own sales methods, but define payment terms centrally. In this example:
Each business unit has its own reference data set for salesmethods.
One central reference data set for payment terms is assigned to all business units.
References:https://docs.oracle.com/cloud/latest/financialscs_gs/FAIGL/FAIGL1493157.htm#FAIGL94314

Explanation
If you do not enable Automatic Offsets, Payables records the invoice liability using the liability account on the invoice, which defaults from the supplier site. When you distribute invoice distributions across multiple balancing segments, the invoice will not balance by balancing segment. However, General Ledger can automatically create intercompany balancing entries when you post the invoice if you have enabled the Balance Intercompany Journals option for your set of books.
References:https://docs.oracle.com/cd/A60725_05/html/comnls/us/ap/autoff01.htm