FSCM Billing Consolidator

Billing Consolidation ConnectorPDF download from SAP Help Portal:http://help.sap.com/erp2005_ehp_06/helpdata/en/48/bfe73ba1726744e10000000a421937/frameset.htm

Created on July 10, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

NoteThis PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SEand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and othercountries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 27

Table of content1 Billing Consolidation Connector1.1 SAP Billing Consolidation Connector: Config. in SAP Back-End Sys1.1.1 Business Process with Electronic Data Exchange1.1.2 Setup of Your System Landscape1.1.2.1 Creating Distribution Models1.1.2.2 Determining Directory for IDoc File1.1.2.3 Editing Partner Profiles1.1.3 Configuration of Archive1.1.3.1 Checking ArchiveLink Document Classes1.1.3.2 Checking ArchiveLink Document Types1.1.3.3 Defining Archives1.1.3.4 Linking Archive with Document Types1.1.3.5 Determining Type of Archive Access1.1.4 Configuration of Messages1.1.4.1 Messages to Create and Change Purchase Orders1.1.4.2 Messages to Create (Purchase) Order Confirmations1.1.4.3 Messages to Create Shipping Notifications1.1.4.4 Messages to Create Billing Documents1.1.4.5 Message Checks in Documents1.1.5 Customizing for Electronic Data Exchange1.1.5.1 Customizing Settings Required for Customer1.1.5.2 Customizing Settings Required for Vendor1.1.6 Master Data Enhancements1.1.7 Information for System Administrators1.1.7.1 Security Aspects When Accessing Temporary Files1.1.7.2 Setting Up Authorizations1.1.7.3 Configuration of Data Exchange with FTP1.1.7.4 Configuration of Transformation of XML Documents1.1.7.5 Configuration of Web Client (Polling)1.1.7.5.1 Creating Certificates1.1.7.5.2 Importing PSE Files1.1.7.5.3 Configuring Web Services1.1.7.5.4 Defining Logical Port Names1.1.7.5.5 Defining Basic Settings1.1.7.5.6 Registering Certificates of Service Providers1.1.7.5.7 Activating Services1.1.8 Technical Background Information (Tables and Programs)1.1.9 Error Analysis1.1.9.1 Problems with Incoming Messages1.1.9.2 Problems with Sending Messages1.1.10 Support In Event of Problems


Page 2 of 27

1 Billing Consolidation Connector

PurposeThis component links an SAP system with a service provider, and enables electronic processing of purchase orders or invoices, for example. This does awaywith the need for extensive and cumbersome paperwork. More advantages include:

By interconnecting a service provider (SP), you can make accessible a whole network of billers and recipients in the case of B2B or e-banking platforms inthe case of B2C by a single technical connection.

The SP ensures by data conversion that messages can be exchanged irrespective of the system environments of senders and receivers. The SP ensures by a digital signature that can be verified and archived that country-specific legal requirements for sales/value added tax are met.

Features EDX_SEND: Sending of messages to an SP. EDX_PROCESS: Processing of messages received from an SP. EDX_LINK: Linking of documents from messages with IDocs and other documents. EDX_LIST: Table display of incoming and outgoing messages.

1.1 SAP Billing Consolidation Connector: Config. in SAP Back-End System You use the connectors of the Billing Consolidation (FIN-FSCM-BC) component to connect a SAP system to the system of a service provider on which thiscomponent is running. The connectors provide the technical base for the electronic exchange of documents.

PrerequisitesThe connectors are available in your SAP system, but they are switched off in the standard delivery. To use the connectors, you have to activate the BillingConsolidation Connector (FIN_FSCM_BCONS_CON) business function. To do so, in the SAP Customizing Implementation Guide, choose the Customizing activityActivate Business Functions .

ProcessThe configuration comprises the following areas:

1. Setup of Your System Landscape2. Configuration of Archive3. Configuration of Messages4. Configuration of Electronic Data Exchange

The following area is relevant for system administrators:5. Information for System Administrators

1.1.1 Business Process with Electronic Data Exchange You can reproduce the business process described below step-by-step in the test system or live system. In the live system, you need to schedule the programsEDX_SEND, EDX_PROCESS, and EDX_LINK as background jobs.

NoteIf you only want to send certain documents, you can create the appropriate program variants. In live operation, we recommend creating a variant for eachdocument class for the sending program (EDX_SEND). For a better overview of the variants, we recommend using as the variant name the technical key of thedocument class together with a sequence number. For instance, you could assign the variant name ORD1 for sending purchase orders.

PrerequisitesThe system landscape is configured correctly. For more information, see Set Up of Your System Landscape.To check that the provider can be reached, you have accessed it with the Internet Explorer. Note that you must use the correct port.You have checked that the vendor has been entered in the customer's sales area data, and also that the customer has been entered in the vendor's purchasingdata. For more information, see Master Data Enhancements.


Page 3 of 27

ProcessThe business process runs as follows:

Process Step Transaction Transaction Code1 Customer places order ME21N Create purchase order.

EDX_SEND Send messages.

2 Vendor creates order and sends order confirmation EDX_PROCESS System processes table EDX_PARKand creates sales order.EDX_SEND System processes tableEDX_OUTBOUND and sends order confirmation.

3 Customer processes order confirmation EDX_PROCESS System processes table EDX_PARKand completes purchase order.EDX_LINK System adds attachment list to completepurchase order.

4 Vendor sends shipping notification and posts goods issue.When the order is due at the vendor's end, the deliveryprocess starts.

VL01N Vendor picks goods from warehouse andcreates outbound delivery.EDX_SEND System processes tableEDX_OUTBOUND and sends shipping notification.VL02N Vendor changes outbound delivery. Whenpicking is complete, vendor posts goods issue.

5 Customer receives shipping notification and posts goodsissue

EDX_PROCESS System processes table EDX_PARKand completes purchase order.EDX_LINK System adds attachment list to completeshipping notification on customer side.MIGO Customer posts goods receipt.

6 Vendor bills and sends billing documents VF01 Vendor creates billing documents.EDX_SEND System processes tableEDX_OUTBOUND and sends billing documents.

7 Customer receives billing documents EDX_PROCESS System processes table EDX_PARKand creates billing documents.EDX_LINK System adds attachment list to completebilling documents.

8 Monitor EDX_LIST Message overview displays messages andtheir statuses. For more information, see thedocumentation for program EDX_LIST.

ExampleThe figure below illustrates the above process for a B2B billing scenario.

1.1.2 Setup of Your System Landscape


Page 4 of 27

To distribute data between systems, you must set up the system landscape appropriately. In other words, you determine which systems exchange data. Then thesystem knows how to send and receive data.

Process1. You determine the systems involved.

Two systems are relevant for the Billing Consolidation Connector (FIN-FSCM-BC) component: the back-end system (sender) and the middleware(receiver). These two systems correspond to an SAP system and a client, and they must exist in the back-end system as logical systems. You namelogical systems in Customizing for SAP NetWeaver under Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems Define Logical Systems .

NoteThe names of the systems are automatically assigned by the system administrator. If you do not find your systems here, contact your systemadministrator.If you assign a logical system a new name, you must also assign it a client. You do this in the Customizing activity Assign Logical System to Client .

2. You connect the sender system with the receiver system.To connect the two systems, you must create a distribution model. In the distribution model, the relationships between logical systems and message typesare determined. Distribution models are used by the applications and the ALE layer to determine receivers and to control data distribution. You createdistribution models and the corresponding model views in Customizing for SAP NetWeaver under Application Server IDoc Interface / ApplicationLink Enabling (ALE) Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views . For more information, seeCreating Distribution Models and the documentation of the Customizing activity.

3. You define the directory to which the back-end system can write the XML IDoc file before it is sent. For more information, see Determining Directory for IDocFile.

4. You edit the partner profile. You have to include in the partner profile the partners (customers or vendors) with whom you communicate by means of IDocs.In the partner profile, you determine which message the system sends to the partner in which way, and how the system processes incoming messages.For more information, see Editing Partner Profiles.

5. To transfer the settings to the middleware, you generate the partner profile. You generate the partner profile in Customizing for SAP NetWeaver under Application Server IDoc Interface / Application Link Enabling (ALE) Modelling and Implementing Business Processes Partner Profiles GeneratePartner Profiles .

NoteThe process codes are already preconfigured in the standard delivery; you do not usually have to make any additional settings. You can recognize the processcodes by the their technical key EDX... . For a complete overview, see the following list of the transactions relevant for process codes:

BD51 Maintain Function Modules (Inbound)WE57 Assignment of Function Module to Application ObjectsWE42 Inbound Process CodeBD67 Function Modules for Inbound ALE-EDI

More InformationSAP Billing Consolidation Connector

1.1.2.1 Creating Distribution Models The distribution model controls the data exchange between the sender and receiver system. The distribution model consists of individual model views in which youcan define all the cross-system interrelated message flows of your organization. For more information, see Distribution Model.

Procedure1. Create a new model view with a single message type for each document. You do this in the Customizing activity Maintain Distribution Model and Distribute

Views . You access this activity in Customizing for SAP NetWeaver under Application Server IDoc Interface / Application Link Enabling (ALE) Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views .

2. Switch to the change mode.3. Create a new model view. To do this, choose the Create Model View pushbutton and enter EDX: Connector as the short text and EDX as the technical

name.4. Choose Continue .

Your new model view now appears in the list.5. Position your cursor on your new model view and create a separate message type for each document. The following table contains the relevant message

types:Model View EDX EDX EDX EDX EDXSender (ERP) xxxCLNTnnn xxxCLNTnnn xxxCLNTnnn xxxCLNTnnn xxxCLNTnnnReceiver (Middleware) xxxCLNTnnn xxxCLNTnnn xxxCLNTnnn xxxCLNTnnn xxxCLNTnnnMessage Type DESADV INVOIC ORDCHG ORDERS ORDRSP

6. Save your entries.7. Generate the partner profile for all message types. You do this by positioning the cursor on the message type of the EDX model view and choosing


Page 5 of 27

Environment Generate Partner Profiles .

More InformationSetup of Your System Landscape

1.1.2.2 Determining Directory for IDoc File The Billing Consolidation Connector (FIN-FSCM_BC-CON) component uses the IDoc Interface for the exchange of data. Ports are the prerequisite forcommunication through the IDoc interface. In the port definition, you determine the directory in which the system is to store the IDoc file. For more information aboutcreating XML ports, see Port Type XML File: Maintaining the Port Description.

ProcedureHere is an example of how to create the port for the Billing Consolidation Connector (FIN-FSCM-BC-CON) component.

1. Access the activity in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define Ports in IDocProcessing .

2. Select XML File und choose Port Create .3. Enter IDOCXML as the name of the port and the descriptive text EDX: Write IDoc As XML File .4. Choose Unicode as the XML format.5. On the Outbound file tab page, enter the name of the physical directory according to your company's specifications. Use a directory that can be written to

from the back-end system.

Example/usr/sap/???/SYS/global/access/Note that the last character must be a slash.

6. Enter the function module: EDI_PATH_CREATE_CLIENT_DOCNUM.7. Leave the field for the outbound file blank.8. Check if the port can be accessed correctly. To do so, choose the Access test pushbutton.


1.1.2.3 Editing Partner Profiles You need to create partner profiles so that the system knows to send messages to the middleware. For all outgoing messages, you require a partner profile withpartner type LS. You also require one of the following partner profiles for each incoming message:

For all incoming messages of a vendor, you require an entry under LI with the vendor number.For all outgoing messages of a customer, you require an entry under KU with the customer number.

For general information about editing partner profiles, see Defining Partners.

ProcedureYou edit partner profiles in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define Partner Profiles .Outgoing Messages (LS)

1. Select partner type LS and choose your middleware (for instance X7TCLNT100). To create new middleware, choose Partners Create .2. Create the outbound parameters in the Outbound parmtrs. box.3. Enter message type DESADV, INVOIC, ORDCHG, ORDERS, ORDRSP and SYNCH as the outbound parameters.4. Edit the outbound parameters (Outbound Options and Message Control) for all message types, regardless of whether the messages are sent to customers

or vendors.5. For the above message types, define the outbound options as in the table below. Doubleclick the required message type and choose the Outbound

Options tab page. For all message types, enter IDOCXML as the receiver port. See Determining Directory for IDoc File. Also choose output mode TransferIDoc Immed. for all message types.Outbound options for various message typesMessage Type Basic TypeDESADV DELVRY05

CautionCould also be DELVRY03 in older releases

INVOIC INVOIC02

ORDCHG ORDERS05


Page 6 of 27

CautionFor this message type, you must also activate the change messages

ORDERS ORDERS05

ORDRSP ORDERS05

SYNCH SYNCHRON

6. For the above message types, enter the information about message control as in the table below. Doubleclick the required message type and choose theMessage Control tab page. Choose Insert Row and enter the required values.

Message control for various message typesMessage Type Application Message Type Process CodeDESADV V2 ZEDX DELV

INVOIC V3 ZEDX SD09

ORDCHG

CautionFor this message type, you mustalso activate the change messages

EF ZEDX ME11

ORDERS EF ZEDX ME10

ORDRSP EF ZEDX SD10

SYNCH No entry No entry No entry

7. Save your entries.Incoming Messages from Vendor (LI)Under partner type LI, enter the number of the vendor from whom you expect to receive incoming messages. Under Inbound parmtrs., enter the incomingmessage type DESADV, INVOIC and ORDRSP. These are the three message types that you can receive from this vendor.For every vendor with which you wish to exchange data electronically, you must edit the partner profile as follows:

1. Access the activity in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define Partner Profiles .2. To create a partner profile for a vendor, select the partner type LI and choose Partners Create .3. Under Partner No., enter the vendor number (for instance L678), and under Partn.Type LI.4. Save your entries.

The system adds the vendor under partner type LI.5. Create the inbound parameters for the vendor according to the table below. To do this, select the vendor and enter the required inbound parameters.

NoteTo add another vendor, position the cursor on the vendor you have just created and choose Partners Create copy .

Inbound options for various message typesMessage Type Process Code CommentDESADV EDX_DELS Delivery: Shipping notification

INVOIC EDX_INVL or EDX_INVF INVL for invoices from Materials Management (MM) withpurchase order reference (for instance, goods purchasewith purchase order) or INVF for a pure FI invoice without apurchase order reference (for instance, an electricity bill).

ORDRSP EDX_ORDR or EDX_INVF Order confirmation

Incoming Messages from Customer (KU)Under partner type KU, enter the number of the customer from whom you expect to receive incoming messages. Under Inbound parmtrs., enter the incomingmessage type ORDERS and ORDCHG. These are the two message types that you can receive from this customer.For every customer with which you wish to exchange data electronically, you must edit the partner profile as follows:

1. Access the activity in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define Partner Profiles .2. To create a partner profile for a customer, select the partner type KU and choose Partners Create .3. Under Partner No., enter the partner number (for instance KU123), and under Partn.Type KU.4. Save your entries.

The system adds the customer under partner type KU.5. Create the inbound parameters for the customer according to the table below. To do this, select the customer and enter the required inbound parameters.

NoteTo add another customer, position the cursor on the customer you have just created and choose Partners Create copy .

Inbound options for various message typesMessage Type Process Code CommentORDERS EDX_ORDC Change of a purchase order


Page 7 of 27

ORDCHG EDX_ORDE Order confirmation

You now have to generate the partner profiles you have edited so that the system can transfer the configured settings to the middleware. You do this by executingtransaction BD82.


1.1.3 Configuration of Archive The Billing Consolidation Connector (FIN-FSCM-BC-CON) component uses archives for the following reasons:

Archives serve as storage locations for the PDF file of the document. The sending program retrieves the PDF file from the archive and sends it.The vendor (biller) uses the archive as a safe storage location for data that is returned by the service provider (signed files that the service provider hasforwarded to the customer, such as signed invoices), according to the auditing requirements.The customer uses the archive as a safe storage location for vendor data received by the service provider, according to auditing requirements.

PrerequisitesAn archive that can communicate with the ArchiveLink interface is available in the system.

ProcessYou must make several settings so that the Billing Consolidation Connector (FIN-FSCM-BC-CON) component uses the existing archive correctly. You mustcarry out the following steps:

1. Check that the required document classes are available in the system. For more information, see Checking ArchiveLink Document Classes.2. Check that the required document types are available in the system. For more information, see Checking ArchiveLink Document Types.3. Define the archive. For more information, see Defining Archive.4. Define how the system is to access the archive. For more information, see Determining Type of Archive Access.5. Link the archive to the document types that you use. For more information, see Linking Archive with Document Types.

1.1.3.1 Checking ArchiveLink Document Classes

Procedure1. Access the Customizing activity to check the ArchiveLink document classes. You do this in Customizing for SAP NetWeaver under Application Server

Basis Services ArchiveLink Basic Customizing Edit Document Classes .2. Check if the settings for the document classes you wish to transfer are correct. In the Billing Consolidation Connector (FIN-FSCM-BC-CON) component,

you can transfer the following document classes:Document Class Description MIME type of a Web objectBIN Binary data application/octet-stream

DOC MS Word Application application/msword

EDI EDIFACT text/plain

PDF Portable Document Format application/pdf

PDFS Signed PDF application/pkcs7-mime

PDFSIG Signature of PDF application/pkcs7-signature

PPT MS PowerPoint Application application/vnd.ms-powerpoint

TXT Text Format text/plain

XLS MS Excel Application application/vnd.ms-excel

XML Extensible markup language text/xml

XMLS Signed XML application/pkcs7-mime

XMLSIG Signature of XML application/pkcs7-signature

More InformationConfiguration of Archive

1.1.3.2 Checking ArchiveLink Document Types


Page 8 of 27

Procedure1. Access the Customizing activity to check the ArchiveLink document types. You do this in Customizing for SAP NetWeaver under Application

Server Basis Services ArchiveLink Customizing Outgoing Documents Edit Document Types .2. Check which of the standard document types you would like to use.

NoteThe technical key of the permitted document types starts with EDX.

The document types are part of the standard system. For a complete list of the document types relevant for the SAP Billing Consolidation Connector (FIN-FSCM-BC-CON) component, see the attachment to SAP Note 1555550.


1.1.3.3 Defining Archives Archives are mapped in the system by means of content repositories. Content repositories are logical units within your storage system. Your storage system maycontain multiple content repositories. We recommend that you create a single content repository for your EDX documents.

Procedure1. Access the Customizing activity to define content repositories. You do this in Customizing for SAP NetWeaver under Application Server Basis

Services ArchiveLink Basic Customizing Define Content Repositories .2. Use the content repository ED, if possible. Enter the settings according to the following table:

Field Contents CommentContent Repository ED Name of archiveDescription EDX: EBPP Billing Consolidation for EBPP Archive

Repos.Document Area ArchiveLink

Storage Type HTTP content serverProtocol EDX EDX for EDX documentsVersion No. 0046 Content Server version 4.6HTTP server hs2086.wdf.sap.corp or 10.26.24.44 Your server ID for the archivePort Number 1092HTTP Script ContentServer/ContentServer.dllTransfer Directory For instance D:\temp The system stores the files temporarily in this directoryPhysical Path For instance D:\temp

NoteThe No signature field must not be selected. Only then does the system archive the signed documents.

3. Choose Test connection to check that access functions correctly.

CautionIt is important to test the connection in all cases because faulty connections could cause errors that are difficult for the user to trace (see Step 10).

4. If the connection worked correctly, you can introduce the repository to the server. To do so, first send the certificate to the server. Choose Send certificate forthis.

5. Navigate to Content Server Administration by choosing CS Admin .6. Switch to change mode of the Content Server Administration.7. Activate the certificate you sent by selecting it on the Certificates tab page and choosing Release .8. Activate the Check Signature function by selecting the relevant field on the Detail tab page.9. Save your entries.

10. Check whether the Customizing settings for the content repository are correct. You do this by accessing the Overview tab page and checking whether agreen entry is visible for your repository.

NoteIf the connection does not work in the business process, the message overview displays the error that the PDF file could not be found. In this case, thesystem was not able to store the document in the archive as a PDF file. Note that the message in the document is highlighted green because the PDF filewas generated successfully but the file could not be stored because the connection failed.


Page 9 of 27


1.1.3.4 Linking Archive with Document Types You have to determine in which archive (content repository) the system is to store your PDF files.

Procedure1. Access the Customizing activity to link the content repositories. You do this in Customizing for SAP NetWeaver under Application Server Basis

Services ArchiveLink Basic Customizing Edit Links .2. For all the document types that you use, create entries for the following object types listed below. Enter the archive that you created as the content repository.

BKPFBUS2012BUS2015BUS2032BUS2081EKKOIDOCLIKPVBAKVBRK

NoteIn the standard delivery, all these object types are assigned to the content repository ED. To compare entries for these object types with theoriginal client (standard delivery), go to change mode and choose in the menu Utilities Comparison .If you encounter problems with the display of archived documents, read SAP Note 304541.


1.1.3.5 Determining Type of Archive Access You can control the communication between the SAP system and content repository by using document classes. To do this, you define protocols in which youdetermine for individual document types how the system is to handle an ArchiveLink function (in other words, which communication type does it use).

Procedure1. Call up the Customizing activity for processing protocols. You do this in Customizing for SAP NetWeaver under Application Server Basis Services

ArchiveLink Front End Communication Customizing Maintain Protocols .2. Create a new protocol with the following values:

Protocol: EDXVersion: 0046Description: Protocol for EDX

3. For every function, enter the communication type for all the document classes you use from the table below.Settings for Document ClassesFunction Communication TypeDisplay Archived Document ARCHIVELNK

Retrieval Frontend HTTP

Display Local File ARCHIVELNK

4. Save your entries.


1.1.4 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 allowa message to be automatically sent by post for certain documents (such as purchase orders, orders, or deliveries). The document information in the messages


Page 10 of 27

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 BillingConsolidation Connector (FIN-FSCM-BC-CON) component uses the electronic exchange of documents to store messages as IDoc files on the file system forsystem documents (purchase orders, orders, deliveries, or billing documents) to be sent by ALE, and also to archive them as PDF files.

FeaturesYou 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 theprocedure for the message. You must also include the new messages in the condition records. You use the condition records to determine the conditions underwhich 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. Forevery document, the system uses a message type of the relevant application (for instance, application EF for purchase orders).

Vendor Customer Message Type Application More InformationPurchase order ZEDX (for IDoc file) and ZPDF (for

PDF file)EF Messages to Create and Change

Purchase OrdersPurchase order change ZEDX (for IDoc file) and ZPDF (for

PDF file)EF Messages to Create and Change

Purchase OrdersOrder confirmation Confirmation of purchase order ZEDX (for IDoc file) and ZPDF (for

PDF file)V1 Messages to Create (Purchase)

Order ConfirmationsShipping notification ZEDX (for IDoc file) and ZPDF (for

PDF file)V2 Messages to Create Shipping

NotificationsBilling ZEDX (for IDoc file) and ZPDF (for

PDF file)V3 Messages to Create Billing

Documents

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) tocheck how the system automatically handled the messages. If you can only add data to the messages in the document manually, this indicates that themessages exist in the system but the condition records are not functioning correctly. The system should automatically add the messages to the document.

NoteYou 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 themessage 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 notspecified 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 storedin the archive as a DocumentSet message to the middleware. The middleware then sends the message on to the service provider.

ActivitiesYou configure messages in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define Conditions forMessage Control .Once you have configured your messages, check them in the document. For more information, see Message Checks in Documents.

More InformationSAP Billing Consolidation Connector: Configuration in SAP Back-End System

1.1.4.1 Messages to Create and Change Purchase Orders So that you can exchange the customer's purchase orders and purchase order changes electronically, you must copy the messages that were already used forpurchase orders and purchase order changes of the EF application and change the settings accordingly. To create and change purchase orders, the systemaccesses the same messages. Note, however, that you must copy the used messages twice so that they can be output twice (once as an IDoc file and again asa PDF file).

ProcessThe whole process comprises the following steps:

1. Copy the used messages in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define Conditions forMessage Control . You do this as follows:

1. Select the line EF - Purchase Order .2. Choose Output types .

The system displays the messages that are available for purchase orders.3. Switch to change mode.4. Select the output type NEU - Purchase order (or your previously used output type).5. Copy this output type and assign the new output type the short text ZEDX and the description Purchase Order (XML).


Page 11 of 27

6. To copy the output type, choose Enter and then Copy All .7. Save your entries.

2. Check the settings of the new output type ZEDX.Tab page General Data

The access sequence must have the vendor details at the end (for instance 0001).Access to Conditions and Multiple Issuing must be selected.

Tab page Default ValuesDispatch Time 4, Send immediately (when saving the application)Transmission Medium: A, Distribution (ALE)Partner Function VN

Tab pageTimeProgram for Output Timing: RSNASTEDFORM Routine: ALE_PROCESSING

3. Check your entries for the processing routine of the new output type ZEDX.1. Select the line with the new output type ZEDX.2. Doubleclick the entry Processing Routines .3. The following entries are displayed: Medium Distribution ALE , Program RSNASTED, and FORM Routine ALE_PROCESSING.

4. Add the new output type ZEDX to the message procedure that you use for purchase orders.1. You edit procedures for messages in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define

Conditions for Message Control .2. Select the line EF - Purchase Order .3. Choose Procedures .

The system displays the procedures that exist for purchase orders.4. Select the procedure RMBEF1 - Purchase Order.5. Doubleclick the Control folder in the left screen area.6. Add a row with your new output type ZEDX. Choose the step number in such a way that the new output type comes directly after the output type that

you used as a copy template. We recommend copying the template output type and then changing the step number in the copy and entering theoutput type ZEDX.

7. Save your entries.5. Create the condition records for the new output type ZEDX as follows:

1. You edit the condition records in Customizing for Financial Supply Chain Management under Billing Consolidation Environment DefineConditions for Message Control .

2. Select the row EF - Purchase Order .3. Choose Condition Records .

The system displays the condition records that are available for purchase orders.4. Doubleclick the output type ZEDX.5. Select the key combination where the vendor is positioned at the end of the key.6. On the next screen, make the entries for your vendor, for instance purchasing document type NB, purchasing organization EK22, and vendor L678.7. Choose Execute .8. In the next table, enter the vendor only and choose Enter .9. Check if the following values are defaulted: Role VN, Medium A, Date/Time 4

10. Enter in this way all the vendors that are to receive electronic messages.11. Save your entries.

6. To copy messages for storing purchase order information as a PDF file, you proceed in the same way. But in this case you create output type ZPDF. Thedifferences in the settings for output type ZEDX are explained below.

When you check the settings for output type ZEDX, there are differences on the Default Values tab page. The transmission medium here must be 1- Print Output. The Storage System tab page is only relevant for output type ZPDF. The following entries should be visible here: Storage ModeArchive Only, Document Type EDXORDPDF EDX: Archive Purchase Order (PDF)When you check the processing routine of the new output type ZPDF, the following entries must be visible: Medium Print Output, ProgramSAPFM06P with FORM Routine ENTRY_NEU with Form MEDRUCK and Type blank (no entry).When you check the condition records, proceed in the same way as for output type ZEDX. In this case, however, you can enter communication datafor your vendors. To do so, select a vendor and choose the Communication push button. In the next screen, enter the output device (for instance yoursystem printer LP01 ) and activate the Print Immediately option. Enter all the vendors that are to receive electronic messages and configure theappropriate communication option. Save your entries.

7. For the two new output types you have created, you must now determine the processes for which they can be used (for instance, new printout or printout ofchanges). You configure the fine control of output types in Customizing for Material Management under Purchasing Messages Output Control Message Types Define Message Types for Purchase Order . In this Customizing activity, choose the entry Fine-Tuned Control: Purchase Order and,

for message types ZEDX and ZPDF, enter operations 1 and 2 for each of the message types.

More InformationConfiguration of MessagesMessage Checks in Documents

1.1.4.2 Messages to Create (Purchase) Order Confirmations To be able to exchange the vendor's order confirmations or the customer's purchase order confirmations electronically, you must copy the output type BA00 thatwas already used of the V1 application and change the settings accordingly. Note that you must copy the used message type twice so that it can be output twice(once as an IDoc file and again as a PDF file).

Process


Page 12 of 27

The whole process comprises the following steps:1. Copy the used messages in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define Conditions for

Message Control . You do this as follows:1. Select the row V1 - Sales .2. Choose Output Types .

The system displays the messages that are available for the area of sales.3. Switch to change mode.4. Select the output type BA00 - Order Confirmation (or your previously used output type).5. Copy this output type and assign the new output type the short text ZEDX and the description Order Confirmation (XML).6. To copy the output type, choose Enter and then Copy All .7. Save your entries.


The access sequence must have the customer details at the end (for instance 0001).Access to Conditions and Multiple Issuing must be selected.

Tab page Default ValuesDispatch Time Send immediately (when saving the application)Transmission Medium: Distribution (ALE)Partner Function SP

Tab pageTimeOutput Timing Program: RSNASTEDFORM Routine: ALE_PROCESSING

3. Check your entries for the processing routine of the new output type ZEDX.1. Select the row with the new output type ZEDX.2. Doubleclick the entry Processing Routines .3. The following entries are displayed: Medium Distribution ALE , Program RSNASTED and FORM Routine ALE_PROCESSING.

4. Add the new output type ZEDX to the message procedure that you use for order confirmations.1. You edit procedures for messages in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define

Conditions for Message Control .2. Select the row V1 - Sales .3. Choose Procedures .

The system displays the procedures that exist for purchase orders.4. Select the procedure V10000 - Order Output5. Doubleclick the Control folder in the left screen area.6. Add a row with your new output type ZEDX. Choose the step number such that the new output type comes directly after the output type that you used

as a copy template. We recommend copying the template output type and then changing the step number in the copy and entering the output typeZEDX.

7. Save your entries.5. Create the condition records for the new output type ZEDX as follows:


2. Select the row V1 - Sales .3. Choose Condition Records .

The system displays the condition records that are available for the area of sales.4. Doubleclick the output type ZEDX.5. Select the key combination where the customer is positioned at the end of the key.6. On the next screen, make the entries for your customer, for instance Sales Organization VK22, Distribution Channel 01, Division 01, and Customer

KU234.7. Choose Execute .8. In the next table, enter the customer only and choose Enter .9. Check if the following values are defaulted: Role SP, Medium A, Date/Time 4

10. Enter in this way all the customers that are to receive electronic messages.11. Save your entries.

6. To copy messages for storing purchase order information as a PDF file, you proceed in the same way. But in this case you create output type ZPDF. Thedifferences in the settings for output type ZEDX are explained below.

When you check the settings for output type ZEDX, there are differences on the Default Values tab page. Here you must enter TransmissionMedium 1 - Print Output. The Storage System tab page is only relevant for output type ZPDF. You must make the following entries there: StorageMode Archive Only, Document Type EDXORSPDF EDX: Archive Purchase Order (PDF)When you check the processing routine of the new output type ZPDF, the following entries must be visible: Medium Print Output, ProgramRVADOR01 with FORM Routine ENTRY with Form RVORDER01 and Type blank (no entry).When you check the condition records, proceed in the same way as for output type ZEDX. In this case, however, you can enter communication datafor your customers. To do so, select a customer and choose the Communication push button. In the next screen, enter the output device (for instanceyour system printer LP01 ) and activate the Print Immediately option. Enter all the vendors that are to receive electronic messages and configure theappropriate communication option. Save your entries.


1.1.4.3 Messages to Create Shipping Notifications To be able to exchange the vendor's shipping notifications electronically, you must copy the previously used output type LAVA of the application V2 and changethe settings accordingly. Note that you must copy the used message type twice so that it can be output twice (once as an IDoc file and again as a PDF file).


Page 13 of 27



1. Select the row V2 - Shipping .2. Choose Output Types .

The system displays the messages that are available for the area of sales.3. Switch to change mode.4. Select the output type LAVA - Outg.ship.notifica. (or your previously used output type).5. Copy this output type and assign the new output type the short text ZEDX and the description Shipping Notification (XML).6. Save your entries.



Tab page Default ValuesDispatch Time Send immediately (when saving the application)Transmission Medium: Distribution (ALE)Partner Function SH


3. Check your entries for the processing routine of the new output type ZEDX.1. Select the row with the new output type ZEDX.2. Doubleclick the entry Processing Routines .3. The following entries are displayed: Medium Distribution ALE , Program RSNASTED, and FORM Routine ALE-PROCESSING.

4. Add the new output type ZEDX to the message procedure that you use for shipping notifications.1. You edit procedures for messages in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define

Conditions for Message Control .2. Select the row V2 - Shipping .3. Choose Procedures .

The system displays the procedures that exist for shipping.4. Select the procedure V10000 - Header Output.5. Doubleclick the Control folder in the left screen area.6. Add a row with your new output type ZEDX. Choose the step number such that the new output type comes directly after the output type that you used


7. Save your entries.5. For all customers that are to receive electronic shipping notifications, create the condition records ZEDX as follows:


2. Select the row V2 - Shipping .3. Choose Condition Records .

The system displays the condition records that are available for the area of sales.4. Doubleclick the output type ZEDX.5. On the next screen, enter the sales organization and all the customers that are to receive electronic messages.

ExampleThe customer data could look like this: Sales organization VK22, Customer KU234, Role SH, Medium A (Distribution ALE), Date/Time 4 (Sendimmediately).

6. Choose Execute .7. Save your entries.

6. To copy messages for storing shipping notification information as a PDF file, you proceed in the same way. But in this case you create output type ZPDF.The differences in the settings for output type ZEDX are explained below.

When you check the settings for output type ZEDX, there are differences on the Default Values tab page. Here you must enter TransmissionMedium 1 - Print Output. The Storage System tab page is only relevant for output type ZPDF. You must make the following entries there: StorageMode Archive Only, Document Type EDXASNPDF EDX: Shipping Notification (PDF).When you check the processing routine of the new output type ZPDF, the following entries must be visible: Medium Print Output, ProgramRVADDN01 with FORM Routine ENTRY with Form RVDELNOTE and Type blank (no entry). Note that the above parameters are only examplesfor print output; you can replace them with your own values.When you check the condition records, proceed in the same way as for output type ZEDX. In this case, however, you can enter communication datafor your customers. To do so, select a customer and choose the Communication push button. In the next screen, enter the output device (for instanceyour system printer LP01 ) and activate the Print Immediately option. Enter all the customers that are to receive electronic messages and configurethe appropriate communication option. Save your entries.


1.1.4.4 Messages to Create Billing DocumentsPUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 14 of 27

1.1.4.4 Messages to Create Billing Documents To be able to exchange billing documents electronically, you must copy the previously used output type RD00 of the application V3 and change the settingsaccordingly. Note that you must copy the used message type twice so that it can be output twice (once as an IDoc file and again as a PDF file).



1. Select the row V3 - Billing .2. Choose Output Types .

The system displays the messages that are available for the area of billing.3. Switch to change mode.4. Select the output type RD00 - Invoice (or your previously used output type).5. Copy this output type and assign the new output type the short text ZEDX and the description Invoice (XML).6. Save your entries.



Tab page Default ValuesDispatch Time Send immediately (when saving the application)Transmission Medium: Distribution (ALE)Partner Function BP


3. Check your entries for the processing routine of the new output type ZEDX.1. Select the row with the new output type ZEDX.2. Doubleclick the entry Processing Routines .3. The following entries are displayed: Medium Distribution ALE , Program RSNASTED, and FORM Routine ALE-PROCESSING.

4. Add the new output type ZEDX to the message procedure that you use for invoices.1. You edit procedures for messages in Customizing for Financial Supply Chain Management under Billing Consolidation Environment Define

Conditions for Message Control .2. Select the row V3 - Billing .3. Choose Procedures .

The system displays the procedures that exist for billing.4. Select the procedure V10000 - Header Output.5. Doubleclick the Control folder in the left screen area.6. Add a row with your new output type ZEDX. Choose the step number such that the new output type comes directly after the output type that you used


7. Save your entries.5. For all customers that are to receive electronic invoices, create the condition records ZEDX as follows:


2. Select the row V3 - Billing .3. Choose Condition Records .

The system displays the condition records that are available for the area of billing.4. Doubleclick the output type ZEDX.5. On the next screen, enter the sales organization and all the customers that are to receive electronic messages.

ExampleThe customer data could look like this: Sales organization VK22, Customer KU234, Role BP, Medium A (Distribution ALE), Date/Time 4 (Sendimmediately).

6. Choose Execute .7. Save your entries.

6. To copy messages for storing billing information as a PDF file, you proceed in the same way. But in this case you create output type ZPDF. The differencesin the settings for output type ZEDX are explained below.

When you check the settings for output type ZEDX, there are differences on the Default Values tab page. Here you must enter TransmissionMedium 1 - Print Output. The Storage System tab page is only relevant for output type ZPDF. You must make the following entries there: StorageMode Archive Only, Document Type EDXINVPDF EDX: Invoice (PDF).When you check the processing routine of the new output type ZPDF, the following entries must be visible: Medium Print Output, ProgramRVADIN01with FORM Routine ENTRY_ESR with Form RVINVOICE01 and Type blank (no entry). Note that the above parameters are onlyexamples for print output; you can replace them with your own values.When you check the condition records, proceed in the same way as for output type ZEDX. In this case, however, you can enter communication datafor your customers. To do so, select a customer and choose the Communication push button. In the next screen, enter the output device (for instanceyour system printer LP01 ) and activate the Print Immediately option. Enter all the customers that are to receive electronic messages and configurethe appropriate communication option. Save your entries.


Page 15 of 27


1.1.4.5 Message Checks in Documents To check that the electronic document exchange works correctly, you must be sure that the system landscape is configured correctly. But you should also checkwhether the system was able to process the messages in the document correctly. You must check the following two cases:

For the IDoc message: Was the system able to store the document as a file?For the archive message: Can the document be displayed from the archive?

PrerequisitesYou have set up your system landscape correctly. For more information, see Set Up of Your System Landscape.

ProcessCheck for IDoc MessageFirst generate and save a document, for instance a purchase order using transaction ME21N. Then display this document and navigate to the message screen.The message must be highlighted green. The processing log shows how the system processed the message. The following table gives you an example of how toprocess messages correctly:

ExampleProcessing Log for Message Type ZEDXLog MeaningObject 4500001984 Document number of purchase orderMessage type: New Was the message type processed?Processing log for program RSNASTED routine ALE_PROCESSING Was the ALE routine for IDocs really called the way it was configured?

IDoc 0000000000021353 was added and transferred to output Was the message generated and processed correctly?IDoc 0000000000021353 was written to file Was a file really written?

It is possible that although the system processed the message correctly it was still not able to write an IDoc file. This may be the case, for example, if theauthorization to write the IDoc file is missing. In this case, the message is highlighted green but the system cannot send the message subsequently because theIDoc is not available as a file in the SAP system. You should therefore check if the IDoc file is available in the file system and if it can be read from the SAPsystem.While setting up the system landscape, you determined to where the system is to write the IDoc file. See Determining Directory for IDoc File. In Customizing forBilling Consolidation , in the activity Define Basic Settings you defined the directory from which the system reads the IDoc file.

Display the existing SAP directories. To do so, use transaction AL11. You should see your configured directory in the results list. Click on the directory and sortthe content in descending order by date. If the system was able to process the message and write the IDoc file correctly, you see the entry in this list. In the detaildisplay, you see an XML IDoc.

NoteYou can only see the XML IDoc temporarily. After sending the message, the system expects to receive a confirmation of arrival, and it then deletes thistemporary XML IDoc.

Check for Archive MessageWhen you have completed the archive settings and checked that they work, you generate a document and check the ZPDF message in this document. Displaythe relevant document and navigate to the message screen. The message must be highlighted green. Since, in this case, there is no processing log, select themessage and choose Additional Details .Check that the message is not locked.

ExampleYou can release a locked purchase order with transaction ME29N. You can output a purchase order for which no output has been requested with transactionME9F.

To check whether the system can actually read and display the documents stored in the archive, choose transaction OAAD. After you have called the transaction,you can see how many documents have been stored, among other things. To display archive documents, choose Technical Search in the Documents screenarea. To restrict the number of hits, we recommend entering the current date as the selection criterion for the storage date.

1.1.5 Customizing for Electronic Data Exchange


Page 16 of 27

You need to configure the electronic data exchange (EDI) because the data that customers or vendors send does not always match the data structures in the targetsystem. The system must be able to interpret the incoming data correctly: The customer's material management system must interpret the vendor's datacorrectly, and the vendor's SD system must interpret the customer' data correctly. In the Customizing activities for the electronic data exchange, you determinehow the system handles incoming data.

More InformationCustomizing Settings Required for CustomerCustomizing Settings Required for Vendor

1.1.5.1 Customizing Settings Required for Customer Customizing settings are required on the customer side so that the customer's material management system can interpret and process the vendor's data correctly.

ProcessThe Customizing settings comprise the following steps:

1. Specify to which company code the system is to assign the vendor's incoming invoices. You must create an entry for each vendor from which you wish toreceive data; this is because the SAP system cannot process data without a company code.To do so, call transaction OBCA and enter the following data:

Partner Type LI - for vendor data.In the Partner Number field, enter the vendor number in the SAP system.In the Company Code Name in the Invoice field, enter how the vendor is identified in the IDoc file (for instance, by the customer number in theirsystem).Enter the company code to which you would like to post the vendor invoice.

ExamplePartner Type Partner Number Company Code Name in the Invoice Company CodeLI 789 0000000234 CC23

2. You determine how the system is to determine the tax code. Note that you may have to create multiple entries for each vendor since the system requires aunique assignment for each data constellation.To do so, call transaction OBCD and enter the following data:

Partner Type LI - for vendor data.In the Partner Number field, enter the vendor number in the SAP system.In the Tax Type field, enter the tax code of the vendor system.In the Tax Rate field, enter the tax rate transferred by the vendor.

NoteThe system settings determine whether a period or comma is used as the decimal separator.

In the Country field, enter the country from which the invoice originates. Note that you must enter country IDs from the vendor system.In the Sales Tax Code field, enter the tax code that the system is to use for this data constellation (for instance V0 or V1).

ExamplePartner Type Partner Number Tax Type Tax Rate Country Tax CodeLI 789 CH VO

LI 789 AO 0,0 CH VO

LI 789 A1 7,6 CH V1

LI 789 A1 7,600 CH V1

LI 789 VAT 7,6 CH V1

LI 789 VAT 7,600 CH V1

3. You determine the posting parameters for incoming invoices.Specify to which company code the system is to assign the vendor's incoming invoices. You must create an entry for each vendor from whom you wish toreceive data; this is because the SAP system cannot process data without this information.To do so, call transaction OBCE and enter the following data:

Partner Type LI - for vendor data.The Description field is automatically filled by the system.In the Partner Number field, enter the vendor number of the vendor in the SAP system.Enter the company code to which you would like to post the vendor invoice.

ExamplePartner Type Short Description Partner Number Company Code


Page 17 of 27

LI Vendor V789 CC23

Doubleclick the entry to display the screen where you determine the posting parameters. We recommend leaving these parameters blank initially and onlyfilling them when the need arises. After you have checked that the system posts the incoming invoices for a specific vendor correctly, you can simply copythe other vendors.

4. You check the current program parameters for electronic data exchange (EDI) in the logistics invoice verification. You do this in the Customizing activityEnter Program Parameters . You can call up this Customizing activity in Customizing for Materials Management under Logistics Invoice Verification EDI . In this Customizing activity, there are various options for processing documents. Note the field help for the various options.

RecommendationFor the Processing parameter, assign the value 4 ( Tolerances correspond to those for online processing ).

More InformationCustomizing for Electronic Data Exchange

1.1.5.2 Customizing Settings Required for Vendor Customizing settings are required on the vendor side so that the vendor's SD system can interpret and process the customer's data correctly.

ProcessThe Customizing settings comprise the following steps:

1. You determine the sales channel through which you would like to serve the customer. To do so, call transaction VOE2 and define the required data.

ExampleBelow is an example of the data you could define for a customer.

Field ValueCustomer 234Vendor Number 0000000789Sales Organization VK12Distribution Channel 01Division 0Sales Document Type TA (Standard Order)

2. If the customer only transmits their internal number, you must determine which ship-to party number the system should use. To do so, execute transactionVOE4. The table could then contain the following entries:Data for Table: Sales - EDI ConversionCustomer External Function External Partner Internal Number234 AG (Sold-To Party) 789 234234 WE (Goods Recipient) WK13 234

This table also determines which value the system writes in the LIFNR field of the IDoc file for this invoice.3. So that your system understands what your customer orders, you must define in the SAP system the number under which your customer stores your

products. To do so, execute transaction VD51. For more information, see Master Data Enhancements.


1.1.6 Master Data Enhancements To enable customers and vendors to exchange documents electronically with the Billing Consolidation Connector (FIN-FSCM-BC-CON) component, you mustenhance master data as described below.CustomerWhen a customer orders with a vendor, the customer has to enter the customer number used by the vendor for this customer in the customer's vendor masterrecord. The system can only determine the reference in the IDoc file correctly if the Billing Consolidation Connector (FIN-FSCM-BC-CON) component knows thenumber under which the vendor lists you as customer. Otherwise the system processes the IDoc file incorrectly and cannot generate the required document.To enter the customer number in the vendor master record, proceed as follows:

1. On the SAP Easy Access screen, choose Logistics Materials Management Purchasing Master Data Vendor Central Change .2. Enter the data required for the vendor, select the Purchasing data field and choose Enter .


Page 18 of 27

3. In the Sales data area, enter in the Acc. with Vendor field the customer number that the vendor uses for you.

NoteIf you are not able to see the Sales data area, the vendor was created in an account group that hides this area. In this case, you can either create thesame vendor as a new vendor with another account group or adjust the Customizing of the account groups in the vendor master records.

VendorIf a vendor delivers goods to a customer, the situation is mirrored. The vendor has to enter the vendor number used by the customer for this vendor in the customermaster record so that the system can process the data correctly.To enter the vendor number in the customer master record, proceed as follows:

1. On the SAP Easy Access screen, choose Logistics Materials Management Purchasing Master Data Subsequent Settlement CustomerRebate Arrangements Environment Customer Business Partner Customer Change Full .

2. Enter the data required for the customer, select the Sales Area Data field and choose Continue .3. In the Sales area, enter in the vendor number that the customer uses for you.

NoteIf you are not able to see the Sales data area, the customer was created in an account group that hides this area. In this case, you can either createthe same customer as a new customer with another account group or adjust the Customizing of the account groups in the customer master records.

4. On the Control Data tab page, also enter the vendor number in the Vendor field that the customer uses for you.MaterialCreate a customer-material info record so that the system recognizes the partner's material. To create a customer-material info record, call transaction VD51. Toensure that you have created the materials correctly, we recommend using the same materials that you use in the business process without electronic dataexchange.ConditionsYou must have configured the message correctly and you must also have created the master record of the message condition accordingly so that the system cangenerate the IDoc file and PDF file on saving a document. To edit the message condition, call transaction NACE and select condition records from your application.For more information, see Messages to Create and Change Purchase Orders and Messages to Create (Purchase) Order Confirmations.


1.1.7 Information for System Administrators The following section contains configuration instructions for system administrators. You will find the following descriptions here:

Security Aspects When Accessing Temporary FilesSetting Up AuthorizationsConfiguration of Data Exchange with FTPConfiguration of Transformation of XML DocumentsConfiguration of Web Client (Polling)

1.1.7.1 Security Aspects When Accessing Temporary Files The Billing Consolidation Connector (FIN-FSCM-BC-CON) component provides directories for temporary files in the system and uses them in the EDX_SETUPtable. You can view these directories with transaction AL11. For easy access to this data, these files should also be available through the Network File System(NFS) protocol.The use of such directories makes it possible for a malicious user to gain read or write access to any files on the application server, thus enabling them todisclose confidential information, corrupt data, or change the system behavior. To understand these problems and know how to avoid them, you must read SAPNote 1497003 and follow the instructions given.The software of the Billing Consolidation Connector (FIN-FSCM-BC-CON) component is already prepared for these extensions. However, to ensure the secureoperation of all functions, you must also read SAP Note 1508060 and follow the instructions given.

1.1.7.2 Setting Up Authorizations Users can only configure the Billing Consolidation Connector (FIN-FSCM-BC-CON) component and execute programs if they have been assigned theappropriate authorizations.Authorization object F_EDX_AUTH controls the assignment of authorizations. You can use this authorization object to control message processing for electronic dataexchange. When assigning authorizations, you can differentiate between company code, activity, and message type. For instance, with the activity authorizationyou can determine whether a user is allowed to execute or check messages. You can use the message type to determine whether a user is allowed to processmessages for purchase orders or messages for order confirmations.To assign authorization object F_EDX_AUTH to a user, proceed as follows:

1. Call transaction PFCG.2. Create single role SAP_EDX.3. Navigate to the Authorizations tab page and create an authorization profile for this role.


Page 19 of 27

3. Navigate to the Authorizations tab page and create an authorization profile for this role.4. Change the authorization data by manually adding authorization object F_EDX_AUTH.5. Edit the Company Code, Activity, and Message Type fields for authorization object F_EDX_AUTH.6. Save your entries and generate the role.7. To assign role SAP_EDX to the user, navigate to the User tab page, enter the user data, and save your entries.

PrerequisitesWe deliver authorization object F_EDX_AUTH as of the following enhancement packages (EHP):

EHP6 - from SP00EHP5 - from SP04EHP4 - from SP09

1.1.7.3 Configuration of Data Exchange with FTP You can use the Billing Consolidation Connector (FIN-FSCM-BC-CON) component to exchange electronic files by File Transfer Protocol (FTP).

PrerequisitesYou have implemented the instructions of SAP Notes 1497003 and 1508060.

ProcessThe system writes to the file system the DocumentSet messages that were created and reads the DocumentSet messages that were received there.

1. Configure the directory structure of the file system in Customizing for Financial Supply Chain Management under Billing Consolidation GeneralSettings Define Basic Settings .

2. Select the File System value for the middleware that is used.3. In the Directory for Outgoing Messages, enter the master directory for the outgoing DocumentSet-Messages.

NoteThe system creates the directory structure for outgoing DocumentSet messages from the following information:

Directory registered for outgoing messagesClient from the SAP systemYour own ID with the service providertoSend (fixed element)

An example of a directory structure for outgoing DocumentSet messages is as follows: d:\edx_work\502_41019658412654785\toSend

The FTP client reads the DocumentSet message from the toSend directory and passes it on to the service provider. After it has been successfully passedon to the service provider, the file must be deleted in this directory.

4. In the Directory for Incoming Messages, enter the master directory for the outgoing DocumentSet messages.

NoteThe system creates the directory structure for incoming DocumentSet messages the same way as for the directory structure for outgoing messages.However, the fixed element is toProcess in this case. An example of a directory structure for incoming DocumentSet messages is as follows:d:\edx_work\502_41019756324584569\toProcess

As soon as the system processes a new DocumentSet message, it moves it from the toProcess directory to the inProcess directory. It also enters alldocuments from the DocumentSet message in table EDX_PARK. Once this step is successfully completed, the system deletes the DocumentSet messagefrom the inProcess directory. If an error occurs, the system moves the file to the withError directory. You should therefore check this directory regularly formessages that the system cannot process. Once you have analyzed and corrected the error, you can process the message again by moving it to theinProcess directory.

1.1.7.4 Configuration of Transformation of XML Documents The Billing Consolidation Connector (FIN-FSCM-BC-CON) component functions internally with an XML IDoc structure. If the systems that exchange electronicdata use different XML structures, you need to determine how the SAP system is to convert the XML IDoc document into a differently structured XML document.The SAP XSLT Editor performs this transformation.To configure the transformation of XML documents, proceed as follows:

1. Familiarize yourself with the functions of the SAP XSLT Processor. Read the application help for the SAP XSLT Processor and Transformation Editor.2. Create an XSLT transformation for your structured XML document. You need to differentiate between outgoing and incoming documents.3. Create a separate XSLT transformation rule for each direction. However, you can group multiple message types in an XSLT transformation.4. To find your final version of the transformation in table EDX_BP_SP (outgoing message types) or EDX_TRANSF_IN (incoming message types), you must

enter the final version of the XSLT transformation in the repository.5. Configure the transformation you have created in Customizing for Financial Supply Chain Management under Billing Consolidation General Settings

Define Transformations for Incoming Messages .6. Check the transformation as follows:

Create a new DocumentSet message, for instance for a new purchase order or invoice.


Page 20 of 27

Receive a new DocumentSet message from an external source.

1.1.7.5 Configuration of Web Client (Polling) Customers who have no middleware, or customers who do not allow pushing of data, can use a Web client to connect to the Billing Consolidation (FIN-FSCM-BC) component. The Web client provides a direct connection to the service provider without any middleware, such as SAP NetWeaver PI. The Web client uses anSSL connection (HTTPS) and supports authentication through the user name and password or certificates. The connection mode is synchronous with the pulling ofdata. For sending, the programs for processing messages are the same as those used with middleware.

PrerequisitesYou need to have the SAP Cryptographic Library in order to have an SSL connection to your service provider.For more information about configuring AS ABAP for SSL support , see SAP library for the SAP ERP Central Component on the SAP Help Portal athttp://help.sap.com.You have specified whether the SSL connection should be created with authentication by means of user name and password or by certificates.For more information on creating certificates, see:

Creating CertificatesImporting PSE Files

FeaturesAfter you configure the Web client, you can use the following two reports:

The background program EDX_PULL pulls all messages at the service provider's end, which allows the system to exchange outgoing and incomingmessages directly with the service provider. For more information, see the program documentation.Transaction EDX_POLL calls a Web Dynpro ABAP application that displays a list of messages that meet your selection criteria. The list groups themessages according to their status, such as Ready for Download or Downloaded . The primary purpose of the list is to assist you in analyzing errors andin monitoring.You can download the messages individually or download the complete list of messages. You can display the properties of a DocumentSet message aswell as its contents. You can extract and save the individual documents of a message, for example the PDF or XML output of a message. You can alsochange the status of a message at the service provider.

ActivitiesTo configure the Web client, you have to make the following settings:

Configure the Web serviceDefine logical port namesDefine basic settingsRegister certificate of service providerActivate serviceSet up authorizations

To check the Web client, use transaction EDX_POLL. If you receive an error message, check the trace file of the Internet Communication Manager (ICM) intransaction SMICM. Then increase the trace level to 3 and execute transaction EDX_POLL again.

More InformationTechnical Background Information (Tables and Programs)

1.1.7.5.1 Creating Certificates To ensure security when you send DocumentSet messages, you must establish communication that is made secure using a certificate. If you want to create thecertificate using the SAP Trust Manager (transaction STRUST), use the following procedure. You must agree on the procedure with your service provider.

Procedure1. Call transaction STRUST.2. Choose Environment SSL Client Identities and create a new SSL client identity.

Make all necessary entries and choose a key length of 1024 or 2048.Create a certificate request and send the file to your Certification Authority (CA) for signing.Import the signed certificate answer to the SSL client identity.

3. Choose Certificate Database Execute and add your CA to the list of trusted CAs.4. Link the newly created CA with the certificate. To do so, choose Certificate Import and link the certificate file ( File tab) with the CA added to the

database ( Database tab).5. Send the certificate to your service provider so that your access authorization is set up.


Page 21 of 27

More InformationImporting PSE Files

1.1.7.5.2 Importing PSE Files To ensure security when you send DocumentSet messages, you must establish communication that is made secure using a certificate. If you did not create thecertificate using SAP Trust Manager (transaction STRUST), but instead you created a P12 file using another tool, follow the procedure below to convert the file to aPSE file and to import it.

PrerequisitesYou have converted the P12 file to a PSE file.For more information, see SAP Library for SAP NetWeaver on the SAP Help Portal at http://help.sap.com.

Procedure1. Copy the PSE file to your workstation.2. Call transaction STRUST.3. Choose Environment SSL Client Identities and create a new SSL client identity.4. Double-click the File in the list of PSE files and enter your PSE file.5. Choose PSE Save As SSL Client and your PSE file.6. Expand the newly created SSL client identity and double-click on the PSE file. If a password is required, it is the same as the password of the P12 file.7. Choose the Import Certificate pushbutton and enter the certificate of your service provider. Your service provider has to send you the certificate, or at least

inform you of a link for downloading the certificate.8. Choose the Add to Cert. List pushbutton.9. Save your entries and start the Internet Communication Manager (ICM) again.

More InformationCreating Certificates

1.1.7.5.3 Configuring Web Services For you to be able to use the Web service interface instead of middleware, you have to configure the Web service in SOA Manager. You can configure the Webservice manually or automatically. You have to choose manual configuration, if authentication is to take place using a user name and password. You have tochoose automatic configuration based on a WSDL file, if authentication is to take place using a certificate. Your Billing Consolidation service provider delivers theWSDL file.

Procedure1. Call transaction SOAMANAGER.2. Choose the Application and Scenario Communication tab.3. Choose Administration of Single Services .4. Enter the following search criteria:

Search For: Consumer_ProxySearch Argument: CO_EDX*Field: Internal name

5. Choose the Start pushbutton.6. Select the row containing the consumer proxy CO_EDX_WS_DWSPORT in the search results and choose Apply Selection .7. Choose the Configurations tab.8. Choose the Define Log. Port pushbutton.

A dialog box for general configuration settings appears.If you want authentication to take place using the user name and password, choose Manual Configuration .If you want authentication to take place using certificates, choose WSDL-Based Configuration . Access is by means of a file that is provided.

9. Enter a name and a description for the logical port.10. Choose the Copy Settings pushbutton.

The area Configuration for Logical Port appears:On the Consumer Security tab, enter how authentication is to take place.On the Transport Settings tab, change the settings listed below. For all other settings, copy the standard values.

URL Access Path /DWS/DWS

Host Name of Access URL Domain Name of Service ProviderPort Number of Access URL Port Number of Service Provider

If no port number is entered, use the standard value 443.Protocol Information of URL HTTPS

If you use an Internet proxy, also make the following settings:


Page 22 of 27

Name of Proxy Computer Proxy ComputerPort Number of Proxy Computer Proxy PortUser Name for Proxy Access User Name, If Authentication RequiredPassword of Proxy User Password, If Authentication Required

If you configure the port manually, enter the following SOAP actions on the Operation-Specific tab:Operation SOAP ActiongetShipmentList urn:#getShipmentListtakeDocumentSetMsgReply urn:#takeDocumentSetMsgReplytakeDocumentSetMsg urn:#takeDocumentSetMsgconfirmShipmentReceipt urn:#confirmShipmentReceiptgetShipmentContent urn:#getShipmentContenttakeShipment urn:#takeShipmentsetShipmentState urn:#setShipmentStategetDocumentSetDescription urn:#getDocumentSetDescription


1.1.7.5.4 Defining Logical Port Names You have to enter the name of the logical port that you created in SOA Manager in the Customizing settings for the Billing Consolidation (FIN-FSCM-BC)component.

Procedure1. You do this in the Customizing activity Define Logical Port Names .

You access this Customizing activity in Customizing for Financial Supply Chain Management under Billing Consolidation General Settings DefineLogical Port Names .

2. Create a new entry with with the ID of the service provider, a descriptive name for the service provider, and the name of the logical port that you created inSOA Manager.


More InformationDefining Web Services

1.1.7.5.5 Defining Basic Settings To be able to use the Web service interface for communication with your service provider rather than middleware, you must make Customizing settings for theBilling Consolidation (FIN-FSCM-BC) component.

Procedure1. You do this in the Customizing activity Define Basic Settings .

You access this Customizing activity in Customizing for Financial Supply Chain Management under Billing Consolidation General Settings DefineBasic Settings .

2. Choose Web Service as the middleware to be used.3. Save your entries.

1.1.7.5.6 Registering Certificates of Service Providers To ensure secure communication with your service provider, you must register the SSL certificate of the service provider on your SAP backend system. This isthe only means of enabling the Internet Communication Manager (ICM) to verify the certificate of the service provider.

Procedure1. Call transaction STRUST.2. Choose Certificate Database Execute .3. Add the Certification Authority (CA) to the list of trusted CAs.4. Link the certificate with the newly created SSL client identity or with the anonymous SSL client identity that you created for authentication using a user name

and password.


Page 23 of 27

More InformationCreating CertificatesImporting PSE Files

1.1.7.5.7 Activating Services To be able to use the Web client for communication with your service provider, you have to check if the service is activated.

Procedure1. Call transaction SICF.2. In the Filter for Call of ICF Hierarchy group box, enter the hierarchy category Service and the service path

/sap/bc/webdynpro/sap/edx_poll_appl.3. Choose the Execute pushbutton.4. To display the properties of the service, double-click on the service in the navigation tree.

1.1.8 Technical Background Information (Tables and Programs) Below is an overview of the various tables and programs in the Billing Consolidation Connector (FIN-FSCM-BC-CON) component that allow and supportelectronic data exchange (EDX).

EDX tables for operative dataTechnical Key Data Contained in TableEDX_INBOUND EDX: Inbound Messages (Processed Messages)

EDX_OUTBOUND EDX: Lock Objects for Outbound Messages

EDX_PARK EDX: Lock Objects for Received Messages

EDX_TRACE EDX: Trace

EDX programs for message processingTechnical Key FeaturesEDX_BALANCING EDX: Comparison of Ingoing and Outgoing Messages

EDX_LINK EDX: Link Documents to Document

EDX_LIST EDX: Overview of Inbound and Outbound Messages

EDX_PARK EDX: Park Incorrect Invoices

EDX_PROCESS EDX: Process Messages

EDX_PULL EDX: Get Messages

EDX_RUN EDX: Process All Messages

NoteTo process all messages for day-end closing, we recommend scheduling thisprogram as a job.

EDX_SEND EDX: Create and Send Messages

EDX_READ_FILES EDX: Read Messages from File System

To ensure data consistency, we recommend executing the above programs at regular intervals.Additionally, there is a range of programs that you can use in special situations:

EDX programs for exceptional situationsTechnical Key DescriptionEDX_DEL EDX: Delete Messages in Park Table

EDX_DUMP EDX: Save Objects from Non-Processable Messages

EDX_RESET EDX: Reset Message Status for Renewed Send Attempt

EDX_TRACE EDX: Display Trace Messages from Processing

1.1.9 Error Analysis The error overview (program EDX_LIST) displays all the outgoing and incoming messages in a period, together with their processing statuses.For guidance in analyzing and correcting errors, see the explanations and tips in the following documents:


Page 24 of 27

Problems with Sending MessagesProblems with Incoming Messages

1.1.9.1 Problems with Incoming Messages System does not automatically continue processing of incoming messageYou want the system to continue processing of the incoming message automatically, without you having to trigger this manually. To do this, you have to schedulethe program for processing IDocs (RBDAPP01) as a periodic job. For more information, see Error Analysis > IDoc not transferred to the application at receipt:IDoc-Status '64' . See SAP Note 399271.Problems with order confirmationsYou have received an order confirmation from the vendor as a message with the status Partially Processed . To change the status, you have selected themessage in the message overview, navigated to IDoc processing through the context menu (right mouse button) (transaction BD87), and attempted to post theIDoc again. The system displayed an error message explaining that the error occurred because the confirmation control key is missing. The problem is due to thefact that the system does not expect an order confirmation. In other words, the purchase order item does not require an order confirmation. Since the orderconfirmation was submitted without a request, no action is required from your side.If you still want to post the message, you must change the