Request you to go through EDI Output type part one first to get the feel of continuation.
Access Sequence
An access sequence defines a sequence in which business rules are checked for proposing an output type. A business rule is checked by comparing the values passed in the application data with the values defined in the condition records of the condition table. If a match occurs, a business rule is considered satisfied. After a business rule is satisfied, the output values from the condition record are used for the output type.
We give an access sequence a four−character name, usually a number. It has the following attributes.
To view the access sequence, select an application in transaction NACE, then click on the Access sequences button. To see the details of an access sequence, select it and then double−click on the Accesses folder in the Dialog Structure frame. figure below illustrates two business rules. Business rule 1 is based on Doc.Type/Sales Org./Customer. Business rule 2 is based on Sales Organization/Customer Number. Each business rule is, effectively, a set of fields defined in a condition table.
Each business rule can also have some preconditions, which are implemented in requirements. These preconditions are captured in the requirements. A requirement is implemented as an ABAP/4 program and assigned a number. You can view a list of requirements defined in the system by using transaction VOFM.
A requirement is optional, but if you prefer, you can specify it for each business rule used in an access sequence. The exclusive or inclusive strategy specifies whether the system should exit after the first match of the business rule against the condition records or should continue to process other business rules in the access sequence.
If we choose the exclusive strategy, the system exits on the first match. In the inclusive strategy, the system continues to validate the rest of the business rules. The reason for an inclusive strategy is to have an output type proposed multiple times. However, one of the attributes (partner function, partner number, or language) must be different. The system does not allow two output types to have identical values.
For example, you choose the inclusive strategy when you have to send a purchase order to your business partner via EDI and also to another SAP system via ALE. The output is the same, but the partners are different. An access sequence can define any number of business rules.
Related Posts
EDI Message control configuration and part two
Maintaining partner profiles in EDI
EDI in bound parameters over view
EDI outbound parameters view part one and Two
EDI partner profile configuration
SAP ABAP INTERVIEW ROUND ONE FAQ'S PART TWO
Access Sequence
An access sequence defines a sequence in which business rules are checked for proposing an output type. A business rule is checked by comparing the values passed in the application data with the values defined in the condition records of the condition table. If a match occurs, a business rule is considered satisfied. After a business rule is satisfied, the output values from the condition record are used for the output type.
We give an access sequence a four−character name, usually a number. It has the following attributes.
- A set of business rules or conditions ·
- A sequence in which the rules or conditions are checked ·
- A requirement that checks for business rules using ABAP programs ·
- An exclusive or inclusive strategy ·
To view the access sequence, select an application in transaction NACE, then click on the Access sequences button. To see the details of an access sequence, select it and then double−click on the Accesses folder in the Dialog Structure frame. figure below illustrates two business rules. Business rule 1 is based on Doc.Type/Sales Org./Customer. Business rule 2 is based on Sales Organization/Customer Number. Each business rule is, effectively, a set of fields defined in a condition table.
Each business rule can also have some preconditions, which are implemented in requirements. These preconditions are captured in the requirements. A requirement is implemented as an ABAP/4 program and assigned a number. You can view a list of requirements defined in the system by using transaction VOFM.A requirement is optional, but if you prefer, you can specify it for each business rule used in an access sequence. The exclusive or inclusive strategy specifies whether the system should exit after the first match of the business rule against the condition records or should continue to process other business rules in the access sequence.
If we choose the exclusive strategy, the system exits on the first match. In the inclusive strategy, the system continues to validate the rest of the business rules. The reason for an inclusive strategy is to have an output type proposed multiple times. However, one of the attributes (partner function, partner number, or language) must be different. The system does not allow two output types to have identical values.
For example, you choose the inclusive strategy when you have to send a purchase order to your business partner via EDI and also to another SAP system via ALE. The output is the same, but the partners are different. An access sequence can define any number of business rules.
Related Posts
EDI Message control configuration and part two
Maintaining partner profiles in EDI
EDI in bound parameters over view
EDI outbound parameters view part one and Two
EDI partner profile configuration
SAP ABAP INTERVIEW ROUND ONE FAQ'S PART TWO
No comments :
Post a Comment