User checks - create Purchase orders /Contracts

[Former Member]

<u>Requirement</u>

Creation of the purchase orders/Contracts should be allowed or blocked based on some vendor (classification) characteristics.

Purchase orders and contracts can be created for materials and services. For each line item (material/service) in Purchase order, the vendor characteristics should be checked. Further, each service item can have multiple service line items and check should be performed for each of these service line items.

<u>Transaction codes</u>

ME21, ME22, ME23, ME21N, ME22N, ME23N, ME31k, ME32k, ME33K

<u> Options tried out</u>

1. The PROCESS_ITEM method in the BADI ME_PROCESS_PO_CUST can be used to check the item data. The checks can be performed in this method. But, this BADI works only for enjoy transactions - ME21N, ME22N and ME23N.

2. The user exit EXIT_SAPMM06E_013 in the enhancement MM06E005 can be used. This user exit will be triggered on press of save for Purchase orders and contracts. However, the checks need to be performed for all the service line items also. The service line item details are not available (accessible) in the user-exit EXIT_SAPMM06E_013.

3. The user exit EXIT_SAPMM06E_013 in the enhancement MM06E005 can be used. This user exit will be triggered on press of save for Purchase orders and contracts. To check the service line items EXIT_SAPLMLSP_031 can be used. But the user exit EXIT_SAPLMLSP_031 does not work for contracts ME31k, ME32k, and ME33k.

<b>Is there a method to get the service line item details into the user-exit EXIT_SAPMM06E_013 so that i can continue with option 2 mentioned above.

Please suggest any other method that will help solve this issue.</b>

Your help is highly appreciated.

regards,

prasad

[Former Member]

<u>Requirement</u>

Creation of the purchase orders/Contracts should be allowed or blocked based on some vendor (classification) characteristics.

Purchase orders and contracts can be created for materials and services. For each line item (material/service) in Purchase order, the vendor characteristics should be checked. Further, each service item can have multiple service line items and check should be performed for each of these service line items.

<u>Transaction codes</u>

ME21, ME22, ME23, ME21N, ME22N, ME23N, ME31k, ME32k, ME33K

<u> Options tried out</u>

1. The PROCESS_ITEM method in the BADI ME_PROCESS_PO_CUST can be used to check the item data. The checks can be performed in this method. But, this BADI works only for enjoy transactions - ME21N, ME22N and ME23N.

2. The user exit EXIT_SAPMM06E_013 in the enhancement MM06E005 can be used. This user exit will be triggered on press of save for Purchase orders and contracts. However, the checks need to be performed for all the service line items also. The service line item details are not available (accessible) in the user-exit EXIT_SAPMM06E_013.

3. The user exit EXIT_SAPMM06E_013 in the enhancement MM06E005 can be used. This user exit will be triggered on press of save for Purchase orders and contracts. To check the service line items EXIT_SAPLMLSP_031 can be used. But the user exit EXIT_SAPLMLSP_031 does not work for contracts ME31k, ME32k, and ME33k.

<b>Is there a method to get the service line item details into the user-exit EXIT_SAPMM06E_013 so that i can continue with option 2 mentioned above.

Please suggest any other method that will help solve this issue.</b>

Your help is highly appreciated.

regards,

prasad

[Former Member]

Hi Prasad,

I am not sure if such exit would be available however I can suggest an alternative which will work just in case you are working on ECC 6.

From this release onwards we have a new technique call Enahncement-options which allows us to enehance the standard functionality. Look for any Enhancement-option avaiable on clicking save button by putting a break-point at run time on all 'Enhancement' statements. If anyone exits which i am sure will then you can do an implementation for the same and implement the required functionality.

Hope this helps and revert for more clarifications if any.

<b>Always reward points to useful suggestion.</b>

regards,

Vikas