The standard system ships with a complete suite of Message control components for each application. We can use these components as is, or you can modify them to suit your needs. If the objective is to use the standard components, all we have to do is create condition records to enable the application to use Message control. To plan to build some of the components, such as a new condition table, we have to carry out some configuration steps.They are explained here below in detail.
Creating Condition Records
Creating condition records is specific to each application. We can reach the screen to create condition records via the application menu or by using transaction NACE.
The steps are
1.Execute NACE to display the various applications.
2.Choose the application in which you're interested, and click the Condition Records button.
3.Specify the output type for which you want to create the condition records.
4.Pick the business rule (condition table) for which you want to maintain the condition records.
5.Enter values for the key fields, and specify the output medium, output timing, partner number, and partner function for each record.
6.Save your entries.
Creating a New Condition Component
If the standard Message control functionality does not meet your requirements, we can build the necessary pieces in Message control. The process of that is explained here with an example.
An area presented here sends out an order response via EDI for customer group 01 and sales organization 3000. Standard components are used wherever appropriate. In the analysis of the standard system, output type BA01 is used for EDI output. It points to access sequence 0003, which lacks a business rule based on customer group and sales organization. Therefore, a new business rule will be created and added to an access sequence.
The customer group number is available on the header portion of the sales order. An analysis of the existing condition table shows that there is no condition table based on the customer group and sales organization combination. We reach the steps to build the components for the SD applications from the IMG under Logistics−General, Sales and Distribution, Basic Functions, Output Control or from the SAP standard menu under Logistics, Sales and Distribution, Master Data, Output. You can also access the steps via transaction VOK2.(94.2)
Accessing the Field Catalog
Transaction: V/86
Menu path: From transaction VOK2, choose SD Document, Sales Document, Condition Table, Field Catalog. We have to make sure that the Customer group field (KDGRP) is selected in the field catalog. If it is not, insert the entry in the field catalog.
Creating a Condition Table
Transaction: V/56
Menu path: From transaction VOK2, choose SD Document, Sales Document, Condition Table, Create and establish the key for your business rule in this step. For the scenario, the key fields are Customer group (KDGRP) and Sales organization (VKORG).
Creating an Access Sequence
Transaction: V/48
Menu path: From transaction VOK2, choose SD Document, Sales Document, Access Sequence.A new access sequence does not have to be created, because you can modify the existing access sequence 0003 being used in the condition type BA01. Because the access sequence can be used in several output types, you should build a new access sequence to avoid conflicts with other output types.
Creating an Output Type
Transaction: V/30
Menu path: From transaction VOK2, choose SD Document, Sales Document, Condition Type we can assign the new access sequence to BA01 (order response) or create a new output type. If a new output type is to be created, the best option is to copy BA01 as ZB01 (order response). Select BA01 and click the Copy icon.
Adding the Output Type to a Procedure
Transaction: V/32
Menu path: From transaction VOK2, choose SD Document, Sales Document, Output Determination Proc.
Assigning the Procedure at the Header Level
Transaction: V/43
Menu path: From transaction VOK2, choose SD Document, Sales Document, Assign, Header(96)
Related Posts
Working of message control part one and two
EDI Message control configuration and part two
Maintaining partner profiles in EDI
EDI in bound parameters over view
Control table in message control
SAP ABAP SAMPLE CODE FOR ALV LIST DISPLAY REPORT
SAP ABAP SAMPLE CODE FOR ALV LAYOUT DISPLAY REPORT
Creating Condition Records
Creating condition records is specific to each application. We can reach the screen to create condition records via the application menu or by using transaction NACE.
The steps are
1.Execute NACE to display the various applications.
2.Choose the application in which you're interested, and click the Condition Records button.
3.Specify the output type for which you want to create the condition records.
4.Pick the business rule (condition table) for which you want to maintain the condition records.
5.Enter values for the key fields, and specify the output medium, output timing, partner number, and partner function for each record.
6.Save your entries.
Creating a New Condition Component
If the standard Message control functionality does not meet your requirements, we can build the necessary pieces in Message control. The process of that is explained here with an example.
An area presented here sends out an order response via EDI for customer group 01 and sales organization 3000. Standard components are used wherever appropriate. In the analysis of the standard system, output type BA01 is used for EDI output. It points to access sequence 0003, which lacks a business rule based on customer group and sales organization. Therefore, a new business rule will be created and added to an access sequence.
The customer group number is available on the header portion of the sales order. An analysis of the existing condition table shows that there is no condition table based on the customer group and sales organization combination. We reach the steps to build the components for the SD applications from the IMG under Logistics−General, Sales and Distribution, Basic Functions, Output Control or from the SAP standard menu under Logistics, Sales and Distribution, Master Data, Output. You can also access the steps via transaction VOK2.(94.2)
Accessing the Field Catalog
Transaction: V/86
Menu path: From transaction VOK2, choose SD Document, Sales Document, Condition Table, Field Catalog. We have to make sure that the Customer group field (KDGRP) is selected in the field catalog. If it is not, insert the entry in the field catalog.
Creating a Condition Table
Transaction: V/56
Menu path: From transaction VOK2, choose SD Document, Sales Document, Condition Table, Create and establish the key for your business rule in this step. For the scenario, the key fields are Customer group (KDGRP) and Sales organization (VKORG).
Creating an Access Sequence
Transaction: V/48
Menu path: From transaction VOK2, choose SD Document, Sales Document, Access Sequence.A new access sequence does not have to be created, because you can modify the existing access sequence 0003 being used in the condition type BA01. Because the access sequence can be used in several output types, you should build a new access sequence to avoid conflicts with other output types.
Creating an Output Type
Transaction: V/30
Menu path: From transaction VOK2, choose SD Document, Sales Document, Condition Type we can assign the new access sequence to BA01 (order response) or create a new output type. If a new output type is to be created, the best option is to copy BA01 as ZB01 (order response). Select BA01 and click the Copy icon.
Adding the Output Type to a Procedure
Transaction: V/32
Menu path: From transaction VOK2, choose SD Document, Sales Document, Output Determination Proc.
Assigning the Procedure at the Header Level
Transaction: V/43
Menu path: From transaction VOK2, choose SD Document, Sales Document, Assign, Header(96)
Related Posts
Working of message control part one and two
EDI Message control configuration and part two
Maintaining partner profiles in EDI
EDI in bound parameters over view
Control table in message control
SAP ABAP SAMPLE CODE FOR ALV LIST DISPLAY REPORT
SAP ABAP SAMPLE CODE FOR ALV LAYOUT DISPLAY REPORT
No comments :
Post a Comment