cancel
Showing results for 
Search instead for 
Did you mean: 

Condition records picking twice in Purchase Order

160690
Explorer
0 Kudos

Dear All,

We have below requirement from Business.

  1. Security Service code (300252) with Particular Vendor (100133) system calculate Non-Deductible Process.
  2. Same Security Service code (300252) other than Vendor (100133) system should calculate Deductible process.

For Above requirement we have created below access sequence:  First one with vendor and second one with out vendor and for all Access sequence activated Exclude option.

  1. Region/PlntRegion/GST Class. /Activity/Plant/Tax Code/Supplier
  2. Region/PlntRegion/GST Class. /Activity/Plant/Tax Code.

In FV11-We Maintained JIIN- Condition record under Access sequence 1 with Vendor (1001)Combination and JIIG- Condition record maintained under Access sequence 2 (Without Vendor)

While creating the PO with Vendor (100133) system picking both condition records values JIIN and JIIG from access sequence 1 and 2. If Access sequence 1 satisfied then why system checking again another access sequence?  How to restrict this access sequence issue.

If we creating PO with Other than 100133 vendor system picking JIIG and this is working fine.

Pls guide me on this., Below screen shots for reference.

160690_0-1708600388882.png

160690_1-1708600443192.png

 

160690_2-1708600443198.png

 

 

160690_3-1708600443204.png

 

160690_4-1708600443212.png

 

160690_5-1708600443222.png

Regards,

Silver.

View Entire Topic
Prasoon
Active Contributor
0 Kudos

Hi,

It looks like the conditions are copied from last purchase order - you may check the following:

1. In the PO line item level, if info-record is present, please remove it manually and check whether the duplicate JIIG is appearing.

2. Check the OMFI settings and ensure that the copy from last PO is not maintained in the default values key. You need to assign the key in the user profile - parameter ID with parameter ID EVO and then test again. Note: you may also create a default value with blank key, so that the parameter assignment is not mandatory.

Prasoon_0-1708833476261.png

Prasoon_1-1708833530079.png

Regards,

 

160690
Explorer
0 Kudos
Hi Prasoon,