The condition table specifies the key fields for a business rule. If a business rule requires you to send EDI based on sales organization and customer, the key for the business rule is Sales Organization (VKORG) and Customer Number (KNDNR).
Thus, we formulate a business rule by specifying the fields that are to be used in decision making, as shown in figure below and we can get to this screen from the Access sequence by double−clicking on the Fields folder in the Dialog Structure frame.) You use this key to access the condition records for output values such as output medium, partner function, partner number, output language, and output time for the message.
If the standard condition tables supplied in the system do not meet your requirements, you can create new condition tables. We must derive the keys for condition tables from the field catalog, which is a subset of the communication structure. This added layer helps you to manage fields. We can select all the fields from the communication structure in our field catalog.
Condition Records
Condition records are inserted in the condition table. Condition records contain the actual data against which the business rules are checked to propose an output. In the figure below, customer number is used as a rule to propose the output. Here we can see that a condition record has two pieces.
1.Key values of the business rule by which a condition record is accessed. (In the figure , customer number is the key value.)
2·The output values of partner function and number, and output medium, timing, and language.
Condition records are considered master data and are maintained by customers. If we are using standard pieces of Message control, the only components we need to create are condition records and Message control parameters in the partner profile.
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
abap programming for mm module
Thus, we formulate a business rule by specifying the fields that are to be used in decision making, as shown in figure below and we can get to this screen from the Access sequence by double−clicking on the Fields folder in the Dialog Structure frame.) You use this key to access the condition records for output values such as output medium, partner function, partner number, output language, and output time for the message.
If the standard condition tables supplied in the system do not meet your requirements, you can create new condition tables. We must derive the keys for condition tables from the field catalog, which is a subset of the communication structure. This added layer helps you to manage fields. We can select all the fields from the communication structure in our field catalog.
Condition Records
Condition records are inserted in the condition table. Condition records contain the actual data against which the business rules are checked to propose an output. In the figure below, customer number is used as a rule to propose the output. Here we can see that a condition record has two pieces.
1.Key values of the business rule by which a condition record is accessed. (In the figure , customer number is the key value.)
2·The output values of partner function and number, and output medium, timing, and language.
Condition records are considered master data and are maintained by customers. If we are using standard pieces of Message control, the only components we need to create are condition records and Message control parameters in the partner profile.
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
abap programming for mm module
No comments :
Post a Comment