Use of partner function and vendor sub-range?

13.Question: Use of partner function and vendor sub-range?

Answer: Partner function explains the role of partner, like one central vendor has many partners where few are OA/GS/PI- OA- where we use to order by sending output(Normally output will be sent to OA address), GS- the partner who carries out goods and supplies to plant from the vendor plant, PI- to which partner the billing should be done.

13.1 How do you create partner functions?

Answer: First we will define partner functions as per our company standards

Once we have partner functions, we will assign to Account group, now we will define a partner schema and assign to vendor account group to get displayed in vendor master.

Vendor Sub-range:

As we have business partner to maintain our business, they may have child companies as per there standards and once they have, we use from procure from child vendor to our local plant to decrease the costs and customs. 

`

In this case we can maintain the vendor sub-range to the central vendor like sub-range in purchasing and partner functions.

Purchasing is for allowing local currencies to pay to the vendor and partner functions is for maintaining OA and GS as local vendor (local vendor means company plant place).

What are the requirements to maintain sub-range?

We must do settings in vendor account group- vendor sub-range/Plant.

Assign partner schema in account group which we defined as per A/c group.

Ticket: User tried to add Z5 as partner to PO, where it shown error partner not allowed.

Resolution: First partner needs to be maintained for that document type as per the business approvers, then we can add it to account group upon approvals.

Level 3 ticket: Region in vendor master cannot be controlled by field settings:

Solution: Worked with ABAPer to maintain that field setting as mandatory by customizing the existing code.