The outbound parameters define the characteristics of an outbound message to your business partner and how SAP transfers the IDocs to the subsystem. A record is created for every outbound message to a business partner.
The main Partner Profiles screen displays the outbound parameters as a table control (labeled Outbound Parmtrs) in the middle of the right frame .We can display, create, or delete the outbound parameters for individual messages by selecting a line on the table control and/or clicking one of the icons displayed just beneath it.
Table EDP13 stores the outbound attributes. In the Outbound Parameters view , We specify the message type and sets of parameters displayed under the Outbound Options, Message Control, Post−Processing: Permitted Agent, and EDI Standard tabs. The Telephony tab parameters are generally not relevant to EDI.
Attributes in the Outbound Parameters view of a partner profile are discussed below.
1.Partn. Number: The same values as specified in the General Parameters view. The system automatically copies the values from the general view when you maintain the Outbound Parameters view.
2.Partn. Type: The same values as specified in the General Parameters view. The system automatically copies the values from the general view.
3· Partn. Funct: In SAP a business partner can have multiple roles. The Partn. Funct. field describes the partner function being used for this message.
4· Message Type/Message Code/Message Function: These three fields together represent the SAP message type assigned to the EDI transaction being sent to a business partner. The Message Type field is derived from the EDIFACT messages, but a one−to−one equivalence is not guaranteed. The message type is independent of the ANSI X.12 or EDIFACT standards. The Message Code and Message Function fields are not commonly used.
Using the Message Code and Message Function fields, we can create a variation of the same message by assigning different values in these two fields.
5.Test: This flag indicates whether the system generates a test IDoc before generating an actual IDoc. This option is not available for all messages. It is available for certain FI−related messages, such as remittance advice and payment orders. It helps you verify the data contents before transmitting the actual message. This attribute is also a directive for the subsystem not to transmit these messages to the business partner.
The Test flag is part of the key. Therefore, you must create two entries (with and without the test flag) for your message type to generate a test IDoc and an actual IDoc.
The Outbound Options tab contains the outbound parameters defining the output port, the output mode, and the type of outbound IDoc used. The specific parameters are
1.Receiver Port: This field contains the port your outbound process will use.
2· Pack Size: This field is specific to ALE processes and is visible only when the port used in the partnerprofile is of type tRFC. This field defines the number of IDocs that are bundled in a packet for transmission to a partner system. The value in this field affects the performance of the system.(74.1)
Related Posts
EDI partner profile configuration
EDI inbound process
EDI Outbound process
COMMUNICATION PART FIVE
COMPUTE PART ONE
The main Partner Profiles screen displays the outbound parameters as a table control (labeled Outbound Parmtrs) in the middle of the right frame .We can display, create, or delete the outbound parameters for individual messages by selecting a line on the table control and/or clicking one of the icons displayed just beneath it.
Table EDP13 stores the outbound attributes. In the Outbound Parameters view , We specify the message type and sets of parameters displayed under the Outbound Options, Message Control, Post−Processing: Permitted Agent, and EDI Standard tabs. The Telephony tab parameters are generally not relevant to EDI.
Attributes in the Outbound Parameters view of a partner profile are discussed below.1.Partn. Number: The same values as specified in the General Parameters view. The system automatically copies the values from the general view when you maintain the Outbound Parameters view.
2.Partn. Type: The same values as specified in the General Parameters view. The system automatically copies the values from the general view.
3· Partn. Funct: In SAP a business partner can have multiple roles. The Partn. Funct. field describes the partner function being used for this message.
4· Message Type/Message Code/Message Function: These three fields together represent the SAP message type assigned to the EDI transaction being sent to a business partner. The Message Type field is derived from the EDIFACT messages, but a one−to−one equivalence is not guaranteed. The message type is independent of the ANSI X.12 or EDIFACT standards. The Message Code and Message Function fields are not commonly used.
Using the Message Code and Message Function fields, we can create a variation of the same message by assigning different values in these two fields.
5.Test: This flag indicates whether the system generates a test IDoc before generating an actual IDoc. This option is not available for all messages. It is available for certain FI−related messages, such as remittance advice and payment orders. It helps you verify the data contents before transmitting the actual message. This attribute is also a directive for the subsystem not to transmit these messages to the business partner.
The Test flag is part of the key. Therefore, you must create two entries (with and without the test flag) for your message type to generate a test IDoc and an actual IDoc.
The Outbound Options tab contains the outbound parameters defining the output port, the output mode, and the type of outbound IDoc used. The specific parameters are
1.Receiver Port: This field contains the port your outbound process will use.
2· Pack Size: This field is specific to ALE processes and is visible only when the port used in the partnerprofile is of type tRFC. This field defines the number of IDocs that are bundled in a packet for transmission to a partner system. The value in this field affects the performance of the system.(74.1)
Related Posts
EDI partner profile configuration
EDI inbound process
EDI Outbound process
COMMUNICATION PART FIVE
COMPUTE PART ONE
No comments :
Post a Comment