cancel
Showing results for 
Search instead for 
Did you mean: 

PO partner check/validation

jasonm2
Contributor
0 Kudos

Hi GURUS,

Is there any user-exits or Badi's to help checking vendor partners when creating or changing a PO?

Right now an OA partner or PI partner from different main vendor VN can be assgined to a PO VN. For example, VN1 has OA1 and PI1 and VN2 has OA2 and PI2. When using VN1 to create a PO, we can assgin OA2 or PI2 to the PO, which is not allowed somehow because there is no relationship between VN1 and OA2 or PI2.

How to prevent this from happening? OSS notes maybe?

Thanks

JM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Jason,

Sorry are you saying you want to stop OA2 and PI2 from being used against VN1? The question was not clear.

Whether the partner is changeable or not is dependent on the config setting under Purchasing->Partner Determination->Partner Settings in Purchasing Documents->Define Partner Schemas. There is an indicator called 'No chnge' in the partner function setting. It determines if the partner can be changed or not.

And also, you don't have to set up a relationship between OA2 and VN1 in vendor master in order to use OA2 in the PO.

Phyllis.

jasonm2
Contributor
0 Kudos

Hello Phyllis,

Thanks for your reply.

From my understanding the indicator 'No chnge' in the partner function setting determines if the partner can be changed or not for the document. The main vendor VN is set to No Change, but other partners are not because the partners should be changeable under the main vendor. It is possible that the main vendor has multiple OA or PI partners.

At the time the PO is either checked for completeness or is saved, SAP performs the vendor partner determination. It is possible that the vendor partners have been manually changed to values that should not be possible since they have nothing to do with the main PO vendor. For example, OA2 can be used with VN1, which should be fixed. How to prevent this from happening?

We don't want to build relationship between VN1 and OA2. They belong to different vendors.

Thanks

JM

JL23
Active Contributor
0 Kudos

It is possible to check this in userexit, enhancement MM06E005

jasonm2
Contributor
0 Kudos

Do you mean "Role determination for release of purchasing documents"?

Thanks

JM

JL23
Active Contributor
0 Kudos

we used EXIT_SAPMM06E_012

jasonm2
Contributor
0 Kudos

What's the enhancement name of EXIT_SAPMM06E_012 if I use SMOD to view?

Thanks

JM

JL23
Active Contributor
0 Kudos

we spoke about MM06E005

jasonm2
Contributor
0 Kudos

EXIT_SAPMM06E_012 "Check Customer-Specific Data Before Saving"

Is this the one you are talking about?

JL23
Active Contributor
0 Kudos

yes.

jasonm2
Contributor
0 Kudos

Good, I'll let our developer try that exit.

Thanks

JM