Skip to Content
0

Why some access sequences have many same tables (Ex: PBU) - SAP SD - Pricing - Access sequence

Aug 03, 2017 at 07:20 AM

84

avatar image
Former Member

Hi,

Can any one help me to answer why some access sequences (Ex: PBU) have many same condition tables (AC: PBU have 73 table 146)? Why don't it use only 1?

When I use T-code VK11/12/13 to update the Condition, only 1 key combination show, even the AC have many condition tables.

I've tried to find the answer but it seems that there is no topic to explain about this.

Thanks,

Donald

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

5 Answers

Phanikumar Valiveti Aug 03, 2017 at 07:35 AM
0

Why access are needed in an access sequence is depends on the conditions of client requirement in getting valid condition record..

Please search in google with Condition technique concept in SAP SD-you can find ready made answers there..

***When I use T-code VK11/12/13 to update the Condition, only 1 key combination show, even the AC have many condition tables****

Can you paste some screen shots for the above for better clarity.

Phanikumar

Share
10 |10000 characters needed characters left characters exceeded
Dissanayake Sanath Aug 03, 2017 at 08:23 AM
0

Hi Donald,

In fact there is no need to have the same table entered as multiple entries in the Access Sequence. In your case, all the entries in the Access Sequence refer to the same (single) table which is "146 - Customer Hierarchy". Actually, you have only one key combination due to this single table. Pls get your consultant to remove multiple entries. If you need different key combinations, then he has to define Condition Tables for respective key combinations and add new tables into the Access Sequence as new entries, for example No 11 or 12 etc etc.

Hope this will clear your doubts.

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Dissanayake,

Thanks for your answer, but this is the standard condition type, I think it has some meaning. Some other condition type of Data determination in Access has the same structure: PBUD (has many tables 144 in the ASeq), PBP (has many tables 149).

Thanks,

Donald.

pbud.png (32.0 kB)
pbp.png (22.1 kB)
0

Hi Donald,

I still believe the same logic apply here as well. I do not see any reason to maintain the same Condition Table in an Access Sequence multiple times, because all these Condition Tables will lead to the same search strategy. For example in the Sequence PBUD, it will evaluate to Customer Hierarchy only.

Regards.

0
avatar image
Former Member Aug 03, 2017 at 07:41 AM
0

Hi Phanikumar,

The AC: PBU has many same condition tables: 146

access-sequence-pbu.png

When I use T-code VK11 to update the condition type: PBU (Access sequence: PBU), it has only 1 key combination

only-1-key-combination.png

My question is: Why the the Access sequence PBU has many same condition tables? what is the purpose? why does not it use only 1 condition table in the Access sequence.

Thanks in advance!

Donald.


Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Aug 04, 2017 at 02:51 AM
0

Dear all,

Can anyone help me to answer this question?

Thanks,

Donald.

Share
10 |10000 characters needed characters left characters exceeded
Rob Ariaans Aug 04, 2017 at 06:50 AM
0

Because the actual field assignment is different in each case.

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Dear Rob,

Can you give me an example?

Rob: Because the actual field assignment is different in each case.

Donald: Even the Access sequence have many condition tables but why when I update the condition record (T-code: VK11/12/13) it still have only 1 key combination.

Best regards,

Donald.

0