Skip to Content
0

Access Sequence in Listing and Exclusion:

Dec 29, 2016 at 06:20 AM

133

avatar image
Former Member

I have two access sequences for listing

1. Cust/mat

2. Sales org/div/ product hierarchy

For a customer with first access sequence 4 materials are maintained. So apart from these 4 materials no other material should get picked right?

But while creating order I am able to add other materials also.

Is it because of the second access sequence? there are many condition records existing with respect to second access sequence wherein for the given sales org and div a set of product hierarchies are allowed.

Since the product hierarchy is allowed (for that combination of sales org and div) is it allowing all the materials (with respect to that prod. hierarchy) also?

Why the system is not considering the first listed materials with respect to the customer?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Veselina Peykova
Dec 29, 2016 at 06:45 AM
0

To understand the cause for the system behavior, as a first step, I suggest that your read sap note 863767 - FAQ: Listing/exclusion, answer 4 and check your settings for the procedure for listing/exclsuion in OV04.
I am not completely sure what is the exact logic, which you need to be implemented - if you did not want to have materials determined via the second access, why would you set it up in such way?
If you want for specific customers to use only level 1 and for all others - level 2, one options is to include customer group or some other field in the second access. In this case you can assign customer group A to the regular customers, but not to the 'special' ones, which use access 1, then maintain records for level 2 for customer group A. As an alternative, you can define a custom requirement for the access as explained in note 865302 - Listing/Exclusion: Defining own requirement and assign it to the second access. In any case, I suggest to choose some customer attribute instead of customer number when determining whether the second access needs to be used - it will make the maintenance a lot easier in the future.

Share
10 |10000 characters needed characters left characters exceeded