SAP EDI outbound process with Message Control is dealt with purchase order in detail with example sap abap screen shots.
Purchase Order overview:
The purchase order transaction is a business document sent by a customer to a vendor to procure materials or services. This transaction set provides for customary and established business and industry practice relative to the placement of purchase orders for goods and services.
The Analysis Phase of edi outbound process with message control of purchase order:
The analysis phase consists of analyzing business requirements and comparing them with the standard functionality of SAP. It's useful to have a good understanding of the SAP business process because, in several cases, you can fill gaps by customizing the system. If gaps cannot be filled via customizing, you should explore the use of user exits to meet your business needs .
Identifying SAP purchase order Business Processes
Identify the SAP business process that supports the EDI transaction in which you are interested. Sometimes the lingo in SAP can be different from what you are accustomed to. The online help is very useful at this stage. You will have to identify the SAP transaction from which you can initiate the process.
For example, the purchase order transaction is part of the Materials Management module. The transaction is ME21 for creating new purchase orders. This information, although not tricky, helps you understand which business process will be used and at which stage you initiate the process.
For example, if you are going to send out an advance shipment notice transaction, you can carry it out at the time of creating a delivery or after a goods issue process. Thus, identifying a business process helps you understand your company's business rules.
Developing a Cross Reference Sheet and Performing a Gap Analysis
In the analysis phase, you identify the gaps between the SAP−provided functionality and your business needs. Customers develop a cross−reference spreadsheet that maps the IDoc data fields to the SAP data elements and the EDI standards. A template is provided for reference . This cross−reference list helps to identify gaps between your business needs and the standard system. Every company develops the cross−reference sheet in one form or another for each transaction.
Identifying Available User Exits in SAP :
As a result of the gap analysis, you discover gaps between your business needs and the standard SAP functionality. If the gaps cannot be filled using one of the customizing options, you can use one of the user exits. User exits allow you to add customized code formally to an existing SAP process. They have been provided at strategic points in the process and are supported during an upgrade. You can browse 1the list of user exits by using the CMOD/SMOD transactions.
The user exit for the outbound purchase order transaction is MM06E001. To view a list of all user exits and their purposes, execute transaction SMOD, enter the enhancement name MM06E001, click the Components button, and select Display.
Identifying the IDoc Type and Message Type of EDI :
Identify the IDoc type and the message type to support the process: ORDERS02 and ORDERS .
You might wonder why there are multiple IDocsORDERS01 through ORDERS05 . The last two digits represent the version. ORDERS05 is a newer version, which means that it still has all the segments of the original version, ORDERS01.
ORDERS02 and higher support configurable materials. Always use the latest version of an IDoc type unless you specifically need the older version. Each IDoc type is thoroughly documented. To look up the IDoc documentation, execute transaction WE60.
Identifying the Message Control Parameters
The next step is to identify the Message control parameters. For each application there is an application ID from which you can drill down to other components of the Message control. You must determine the application ID and output type used in the process.
Application ID: EF
Output Type: NEU
Identifying the Process Parameters
In this step you determine the process code for your IDoc type and message type combination. Execute transaction WE41 for a list of process codes available in the system. The process code for generating the ORDERS message using the ORDERS02 IDoc is ME10.
Identifying the Workflow Parameters In this step you identify the organizational object (user ID, position, workcenter, and so on) responsible for handling errors associated with this EDI transaction.
The set up process of edi outbound process with message control for purchase order will be discussed in the next post.
The next post deals with edi outbound process with message control for purchase order is continued here.
Related Posts:
ERP implementation process and its advantages
Cost Center actual line items in sap finance-report
EDI COMPLETE COURSE
Purchase Order overview:
The purchase order transaction is a business document sent by a customer to a vendor to procure materials or services. This transaction set provides for customary and established business and industry practice relative to the placement of purchase orders for goods and services.
The Analysis Phase of edi outbound process with message control of purchase order:
The analysis phase consists of analyzing business requirements and comparing them with the standard functionality of SAP. It's useful to have a good understanding of the SAP business process because, in several cases, you can fill gaps by customizing the system. If gaps cannot be filled via customizing, you should explore the use of user exits to meet your business needs .
Identifying SAP purchase order Business Processes
Identify the SAP business process that supports the EDI transaction in which you are interested. Sometimes the lingo in SAP can be different from what you are accustomed to. The online help is very useful at this stage. You will have to identify the SAP transaction from which you can initiate the process.
For example, the purchase order transaction is part of the Materials Management module. The transaction is ME21 for creating new purchase orders. This information, although not tricky, helps you understand which business process will be used and at which stage you initiate the process.
For example, if you are going to send out an advance shipment notice transaction, you can carry it out at the time of creating a delivery or after a goods issue process. Thus, identifying a business process helps you understand your company's business rules.
Developing a Cross Reference Sheet and Performing a Gap Analysis
In the analysis phase, you identify the gaps between the SAP−provided functionality and your business needs. Customers develop a cross−reference spreadsheet that maps the IDoc data fields to the SAP data elements and the EDI standards. A template is provided for reference . This cross−reference list helps to identify gaps between your business needs and the standard system. Every company develops the cross−reference sheet in one form or another for each transaction.
Identifying Available User Exits in SAP :
As a result of the gap analysis, you discover gaps between your business needs and the standard SAP functionality. If the gaps cannot be filled using one of the customizing options, you can use one of the user exits. User exits allow you to add customized code formally to an existing SAP process. They have been provided at strategic points in the process and are supported during an upgrade. You can browse 1the list of user exits by using the CMOD/SMOD transactions.
The user exit for the outbound purchase order transaction is MM06E001. To view a list of all user exits and their purposes, execute transaction SMOD, enter the enhancement name MM06E001, click the Components button, and select Display.
Identifying the IDoc Type and Message Type of EDI :
Identify the IDoc type and the message type to support the process: ORDERS02 and ORDERS .
You might wonder why there are multiple IDocsORDERS01 through ORDERS05 . The last two digits represent the version. ORDERS05 is a newer version, which means that it still has all the segments of the original version, ORDERS01.
ORDERS02 and higher support configurable materials. Always use the latest version of an IDoc type unless you specifically need the older version. Each IDoc type is thoroughly documented. To look up the IDoc documentation, execute transaction WE60.
Identifying the Message Control Parameters
The next step is to identify the Message control parameters. For each application there is an application ID from which you can drill down to other components of the Message control. You must determine the application ID and output type used in the process.
Application ID: EF
Output Type: NEU
Identifying the Process Parameters
In this step you determine the process code for your IDoc type and message type combination. Execute transaction WE41 for a list of process codes available in the system. The process code for generating the ORDERS message using the ORDERS02 IDoc is ME10.
Identifying the Workflow Parameters In this step you identify the organizational object (user ID, position, workcenter, and so on) responsible for handling errors associated with this EDI transaction.
The set up process of edi outbound process with message control for purchase order will be discussed in the next post.
The next post deals with edi outbound process with message control for purchase order is continued here.
Related Posts:
ERP implementation process and its advantages
Cost Center actual line items in sap finance-report
EDI COMPLETE COURSE
No comments :
Post a Comment