Configuration of Messages
The electronic exchange of documents works on the basis of messages. Messages contain document information; this can be controlled in such a way as to allow a message to be automatically sent by post for certain documents (such as purchase orders, orders, or deliveries). The document information in the messages can also be output electronically, as a fax or e-mail, or as a PDF document or IDoc file. Multiple messages can be sent and received in parallel. The Billing Consolidation Connector
(FIN-FSCM-BC-CON
) component uses the electronic exchange of documents to store messages as IDoc files on the file system for system documents (purchase orders, orders, deliveries, or billing documents) to be sent by ALE, and also to archive them as PDF files.
Features
You have to copy the messages that are used for every document twice, so that the system can output them twice (once as an IDoc file and again as a PDF file). In the configuration, you determine the access sequences so that the program defaults the messages, including the new ones. You do this by adjusting the procedure for the message. You must also include the new messages in the condition records. You use the condition records to determine the conditions under which the system is to trigger a message (for instance, always or only for specific customers or vendors).
In the Billing Consolidation Connector
(FIN-FSCM-BC-CON
) component, you can exchange messages between systems for the documents listed below. For every document, the system uses a message type of the relevant application (for instance, application EF for purchase orders).
Vendor |
Customer |
Message Type |
Application |
More Information |
|---|---|---|---|---|
Purchase order |
ZEDX (for IDoc file) and ZPDF (for PDF file) |
EF |
||
Purchase order change |
ZEDX (for IDoc file) and ZPDF (for PDF file) |
EF |
||
Order confirmation |
Confirmation of purchase order |
ZEDX (for IDoc file) and ZPDF (for PDF file) |
V1 |
|
Shipping notification |
ZEDX (for IDoc file) and ZPDF (for PDF file) |
V2 |
||
Billing |
ZEDX (for IDoc file) and ZPDF (for PDF file) |
V3 |
To check if the new message types function properly, proceed as follows: If you are a customer, create a purchase order. If you are a vendor, create an order, delivery, or billing document. Then display the document with the appropriate change transaction (such as transaction ME22N to change a purchase order) to check how the system automatically handled the messages. If you can only add data to the messages in the document manually, this indicates that the messages exist in the system but the condition records are not functioning correctly. The system should automatically add the messages to the document.
Note
You can only completely check whether the system handles the messages correctly once you have configured the system landscape and archive correctly. Message type ZEDX does not function properly without the settings for the system landscape because you have not specified to which logical system the message is to be sent as an IDoc using ALE. Message type ZPDF does not function properly without the settings for the archive because you have not specified how the PDF document is to be stored in the archive. For more information, see Setup of Your System Landscape and Configuration of Archive.
If the two messages function correctly, they can now be sent. The EDX_SEND
program sends the IDoc file stored in the file system and the related PDF file stored in the archive as a DocumentSet message to the middleware. The middleware then sends the message on to the service provider.
Activities
You configure messages in Customizing for Financial Supply Chain Management
under 
Billing Consolidation
Environment
Define Conditions for Message Control
.
Once you have configured your messages, check them in the document. For more information, see Message Checks in Documents.