Functionality This method enables you to read the communication type (in the contextof data exchange processes>) of a message,in order to determine the type (XML, e-mail, and so on) and the targetaddress of the data exchange. If you want to send data to another market participant, an IDoc (in theformat defined in the dataexchange definition>) is created from that data by means of adata exchange process>. Thecommunication type is also defined in the data exchange definition. The data can then be sent using the SAP Business Connector for example.The IDoc is sent via the IDoc Customizing to the SAP Business Connectorwhere the BAPI then reads the communication type and the target addressfrom the data exchange definition. The SAP Business Connector can generate an XML file from an IDoc forexample, which you can then send by Internet to the appropriaterecipient.Example In order to send measured load shapes to suppliers, you define adata exchange process>: Distributor sends measured load shape to supplier> As distributor DIST1, you create a data exchange definition for thesupplier SUPP1 on the basis of this data exchange process: DIST1 sends the measured load shape to SUPP1 in MSCONS format on thelast day of every month. The message is sent to the e-mail addresslastgang@lief1.com. During execution of the data exchange process, an IDoc in MSCONS formatis generated. This is sent on to the SAP Business Connector using apartner profile>. The Business Connector uses this BAPI to read the data exchangedefinition and determine the communication type and the target address.Further information General Information on Data Exchange Processes > You can use this BAdI ISU_IDE_COMM_FORMAT> to fill outputparameter ExtensionOut>. You can then read data from and returndata to customer tables.Description This parameter contains the address data if a message is forwardedusing Application Link Enabling (communication type ALE>). the SAPALIAS> field contains the SAP aliasof the target system (which must be defined in the SAP BusinessConnector).Description The parameter contains the most important task data:
- Data exchange process>
- Third party service provider
>
- Own service provider>
- Due date
- Due time
Description The parameter contains the communication format >.Description Version of the communication format. You use this parameter to differentiate between to versions of the same format. For example:
- UTILMD in CSV Format VDEW 1.0
- UTILMD in CSV Format VDEW 2.0
Description The parameter contains the communication type >.Description The parameter contains the data exchange format>.Description The parameter contains the e-mail server data if a message is sent bye-mail (communication type EMAIL>. The corresponding e-mail addresses are contained in parametersEMAIL_FROM, EMAIL_TO, EMAIL_CC and EMAIL_BCC.Description The parameter contains the address data if a message is sent byFile Transfer Protocol> (communication type FTP>).Description The parameter contains the address data, if a message is sent byInternet> (communication type WWW>).Description This table contains the return messages from the method call. Value range If an error occurs, this structure contains the following information:
- Message category (Field TYPE>)
- Message code (Field CODE>)
- Message text (Field MESSAGE>)
If no errors occur, the structure is initial.Description XML dialect with which a message is sent. Description IDoc number>, for which the communication type isread. This is an obligatory> field.Description The parameter contains the e-mail addresses, to which the message issent as a Blind Complimentary Copy> (BCC)>.Description The parameter contains the e-mail addresses, to which the message issent as a Complimentary Copy> (CC)>.Description The parameter contains the e-mail address, from which the message issent. Description The parameter contains the e-mail addresses, to which the message issent.
|