Usages of ‘Exclusive’ Indicator in SAP Access Sequence


Usages of ‘Exclusive’ Indication in SAP Access Sequence

What is an Exclusive Indicator in SAP Access Sequence?

Basic Understanding Pricing Condition Technique.

With an Exclusive indicator and how does the system behave?

Without an Exclusive Indicator and how does the system behave?

What is an Exclusive Indicator in SAP Access Sequence?

The exclusive flag is an indicator that instructs the condition technique whether it should stop searching condition records after finding the first successful records for a condition type within an access sequence.

Usages of ‘Exclusive’ Indicator in SAP Access Sequence

Basic Understanding Pricing Condition Technique in SAP SD.

  • When we create a sales order in SAP before entering any material code system determine the Pricing procedure at the header level. 

  • After filling the material code and quantity in that sales order, the system accesses that pricing procedure and checks each and every condition type whether any applicable condition value is available or not. 

  • To get the condition value system finds the Access Sequence of that condition type tries to read tables of that access sequence. 

  • Once it finds a condition record for any condition type, the condition technique works for subsequent or next condition type. 

aGFZNOpSd4prm0Kp0j86Mdo1I8MulLikSihfQoIB2zTHGe5e6GYRENIdjMWiFcFKop LE14EaXxD2qV1akrdHobgMs5GiiOvyHhMCuU3PQfkwDK7ZjQnru3dEWLIC2DKXjPcad

Te8lAJlvIf79Hd9 58WbvWGS66MW9zcoRtiDw Z pKSGCy3pM5ahd4rUjaRHfnLvaDRW3DOPo hYWw 5nFihccutgkiNZ8VthFbvnpYOLtjV8wCWrGDMQrJZuOI3RYzOCdem0Z k

After finding a successful record for PR00, the system tries to find the next condition type. 

FKvMoUWqgHyE6U2F5jIxHgrmsU3GE A3wFmbzzOJU5 FDl5dETcimeEaQSvC0T7MiR3FekcyqYm7z4ySqQ1G9BB Q0udAEp 4M VhJgexPzVZBvQ9exAWkZX 14U2t vgvydIzH

With an Exclusive indicator and how does the system behave?

Usages of ‘Exclusive’ Indicator in SAP Access Sequence

If the exclusive indicator is activated in the access sequence, the system will not consider subsequent remaining table 406, 304 records once it found a matched valid condition record from 305.

For condition type PR00 we have condition records for the below three condition tables. 

PxLi7TI7AY Eya5c3ySLVgwyNEJW7MW1Pt4TrVDvSK cQd8U6NvSQEA1ABz6LCbCL2ofXd aggX bN1C 2ULWwUF5sHrsYurm9QNu8il8WvgkivoA0a9pG kwz2LeKaFlPKhdB

Cl07YyhET3LzSfOFMyMOoUu9nCoRDogGfL TWH5xYywAiOcKfFoMqO0ENMnAT eMVJE6Eeg646 RXp6vEnWb5gGuoUily5W6Ptv9ZQtM jeSzmoM8Xh1TAaXWjcswBbRvcPY3wKI

You can see the system only displays the first condition table condition record value. 

7Jtkh4aSOSl1a6Cx2gIdKXGehyKxKs8LB SPMGPjxcKPBbQdcziRRFEp1J 0W FfI2nkjuZFbYNJ4MHIROVSr08MriOrGir6Vx YjkRZZDszoiH7WsuLeB dNoyy8qsHr9bo0you

You can see the system only consider the condition record value of the first condition table.

WE6cHeljfDro bDV1n ilzF753Td5dpXF2XGfGUblTenC5vXBT4DRxyJjgVf5KgkOBHtkS

But the condition technique did not access the next table condition record. 

j7xWmVUPW06eKmSiNGxjqt9Je8 TOkKaudO709KpinSPPr 2kBafbtEY1lZrGo0ti6Ej1w3b9251iMl F7 HuC33HLavVw3 k1oadIYeYloKh49DvTZAJOMsT7FsMVaErjWUrJNM

Without an Exclusive Indicator and how does the system behave?

ufcbLlI8Wj8zDFmOr1ouMLMol4kUS1CR2GrwhZ20riW9gmwfoecZksLjYV3CWKI8LCGTh6pv8jCRPpUbA5jFAwIjmR9qEvYQm0arTnI

Now against these tables remove or uncheck Exclusive Indicator. 

cQYXW5w9VapbGIYPYeCnedsMkC7mQBCcKV8KIeb wXHJultTbFhwWZl5cvLcSk gDWDAyfjyH2bDSlL1Y7k 2qjAIvks0swQSR5mSFwDj5ZCoGqNjmzrZsRXXsuB46YQpo3prfXJ

For this case, the condition technique will validate or check all tables against an exclusive indicator not activated of that access sequence even though successfully any condition record is already found. 

MkxIDBPfgWM8v3AfxMeJxmAXMZTdv9kgESM4pFp ZTqb2IIXcQf5XFpXWk 69jEIProyJf57jx53XNIoXrWdk Dxeg2vDSo8WZAdYih 2B 1BOgPEYNPvH091mptonEZs ElLBA0

you can see the PR00 condition get three values from the condition table of its access sequence.

In another case of Discount Access Sequence, Exclusive is unchecked against all tables. 

9KpeThsLl4Ku6HsayO6lDiN 5ClBQb6CahgBLauSMnod6UC7dr2WkHgHlcejcyAT6rJVz4gcZH4dulRu1opFRDEfCQMvoda vRvH9g8GURnfD g9mI0trrHE r58br4VXt4sAbty

For the K007 condition type, you can see it appears twice with different discount percentages. 

From the above example, we can see the exclusive check box in the access sequence plays a vital role to determine the valid most suitable condition record for any condition type and improve system performance. 

 

Details Vlog of this article:- Usages of Exclusive Indicator in SAP Access Sequence

 

 

Join Our SAP SD LinkedIn Group


Similar Posts

Leave a Reply

Your email address will not be published.