SAP ARIBA Integration Configuration_RDS

SAP ARIBA Integration Guide - SAPVITS
Full screenshot of SPRO with all extension-
Vintage IT Solutions http://www.sapvits.com

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
“Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.” P a g e 1 | 46
Framework Setting

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
1)
Define Credentials and End Points for Ariba Network

Use
In this Customizing activity, you can do the following:
You can specify the credentials that identify your company on Ariba Network, assigning a
password (shared secret) to the Ariba Network ID
You can assign end points to Ariba Network IDs and define passwords on end-point level.
Note:
Instead of using passwords, you can use certificates. If you want to do so, you must
maintain them in transaction STRUST. In this case, leave the Shared Secret field in
this Customizing table empty.
The Ariba Network ID is displayed to suppliers on Ariba Network. You can have one or several
IDs. For example, each company code or purchasing organization can have a separate ID. The
Network ID is transferred with each outbound cXML message and identifies your company as
the sender.
An Ariba Network ID can have one or multiple end points. An end point is a document routing
placeholder that ensures documents from Ariba Network are sent to the required destinations
(system).
Caution:
If you have enabled and defined end points for your buyer account on Ariba Network,
you must assign them here and define passwords or use certificates at end-point level.
If you want to use more than one end point for an Ariba Network ID within the same
system, you have to implement the outbound BAdI, method
ASSIGN_SENDER_ENDPOINT.
The credentials can be specified as follows:
A shared secret for each Ariba Network ID
The shared secret is transferred with each outbound cXML message and allows the message
to access Ariba Network.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
A shared secret for each end point

A certificate for each Ariba Network ID (in transaction STRUST)
A certificate for each end point (in transaction STRUST)
Requirements
You have received the Ariba Network ID and the shared secret from Ariba.
Activities
Specify Credentials Without Using End Points
1. Choose New Entries.
2. Enter the Ariba Network ID.
3. Specify a Shared Secret password. If required, you can change the shared secret at a later
point in time.
4. If you have a test account on Ariba Network (which means that your Network ID is not
published), select the Test Account checkbox. You can add the credentials of your live
account at a later point in time.
5. If you want to remove an existing Ariba Network ID, select it and choose Delete.
6. Save your entries.
Specify Credentials on End-Point Level
2. Enter the Ariba Network ID.
3. If you do not want the Network ID to be published on Ariba Network, select the Test
Account checkbox. You can add the credentials of your live account at a later point in time.
4. In the Enable End Points column, select Enable end points for authentication from the
dropdown list
5. Select the line in which you entered the Ariba Network ID and double-click End Points for
Ariba Network in the Dialog Structure in the left-hand screen area.
6. In the table End Points for Ariba Network, do the following:
a) Enter an SAP-Internal Key. You can freely define this key.
b) Enter the Ariba EndPointID which been defined on Ariba Network for the Ariba
Network ID you selected.
7. Save your entries.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
2)
Define Basic Message Settings

Use
In this Customizing activity, you specify which cXML message types you want to exchange with
Ariba Network. You can also select the internal mapping version that you want to use for the
mapping between the objects in the SAP Business Suite system and the corresponding cXML
messages. And you select the cXML version that you want to use for communicating with Ariba
Network.
You can set the indicator Send cXMLStatusUpdateRequest Message if you want to send a
technical message to Ariba Network after a cXML message has been successfully processed by
the SAP system. On Ariba Network, the sending status of the message then changes from "Sent"
to "Acknowledged". Note that the message type cXMLStatusUpdateRequest is only available for
incoming messages.
Activities
2. For each message type that you want to exchange, select the combination of the
application component from where the cXML messages are sent and the message type. Most
other fields are then filled automatically.
3. Select the cXML version that you use to exchange messages with Ariba Network.
4. Select the mapping version that corresponds to the cXML version. The mapping version
refers to the mapping of the dcXML to BAPI structures.
5. Indicate whether you want the status of the message transfer to be visible to your suppliers
on Ariba Network. Examples of possible statuses are "Sent", "Acknowledged", and "Failed".
Example
If you want to transfer purchase orders that can also contain items of type "service", use the
XML message type ORDR (direction "outbound") in mapping version V002 and cXML version
1.2.025 (or higher).

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
3)
Decide on Connectivity Type

Use
There are two ways of connecting your SAP system with Ariba Network:
Direct connectivity: You establish a system connection between your SAP system and Ariba
Network without using middleware.
Mediated connectivity: You establish a system connection using middleware between your
SAP system and Ariba Network
Depending on which connectivity type you use, you only have to make the settings under
Customizing structure node Direct Connectivity Settings or under Customizing structure node
Mediated Connectivity Settings.
4)
A)
Manage and Test Enterprise Services

Use
You can use the SOA Manager to configure Enterprise Services and Enterprise Service clients.
You open the SOA Manager in a browser window.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
For more information about the SOA Manager, see SAP Help Portal at
http://help.sap.com/netweaver -> SAP NetWeaver Process Integration -> SAP NetWeaver
Process Integration 7.1 Including Enhancement Package 1 -> Application Help -> SAP Library
-> SAP NetWeaver Process Integration Library -> Developer's Guide -> Providing,
Discovering and Consuming Services -> Providing Web Services -> Providing Web Services in
ABAP Applications -> Working with the SOA Manager.
Requirements
You have configured the Web Services Runtime. For more information, see SAP Help Portal at
http://help.sap.com/netweaver -> SAP NetWeaver Process Integration -> SAP NetWeaver
Process Integration 7.1 Including Enhancement Package 1 -> Application Help -> SAP Library
-> SAP NetWeaver Process Integration Library -> Configuration -> Configuration of SAP
NetWeaver Systems -> Process Integration (PI) -> Wizard-Based Configuration -> Configuring
the Web Services Runtime.
B)
Maintain Certificate
Use
In this Customizing activity, you use the trust manager (transaction STRUST) to specify the
authentication certificate that enables your company to access Ariba Network using a Secure
Sockets Layer (SSL) protocol.
For more information about the trust manager, start transaction STRUST and choose Help ->
Application Help.
Requirements
You have received your authentication certificate from Ariba.
Activities
1. In the navigation structure, click SSL client SSL Client (Anonymous).
2. Under Certificate, click the icon Import Certificate to upload the certificate file (format
*.cer) that you have received from Ariba.
3. Click Add to Certificate List. The certificate appears in the Certificate List.
4. Save your data.
C)

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
Schedule Polling Agent

Use
To transfer pending messages from Ariba Network, you have to use report Fetch cXML
messages for different message types from Ariba Network
(ARBFND_FETCH_CXML_MESSAGES_NEW). This report is frequently referred to as
Polling Agent. It is only relevant for direct connectivity. It has to be scheduled as a variant in
which you select all cXML message types that you wish to receive and process in your SAP
system.
D)
Define Settings for Polling Agent

Use
In this Customizing activity, you specify which message types you want to retrieve from Ariba
Network. To retrieve the messages, you use the polling agent. The polling agent is a report that
schedules the transfer of cXML messages from Ariba Network to your SAP system (report Fetch
cXML messages for different message types from Ariba Network,
ARBFND_FETCH_CXML_MESSAGES_NEW). You must schedule this report as a job.
Requirements
You have specified the Ariba Network ID under Define Credentials for Ariba Network.
If you want to use end points in polling, you have specified an SAP-internal key for the Ariba
end point ID in the same Customizing activity.
You have configured the enterprise services under Manage and Test Enterprise Services.
Activities
2. Enter your Ariba Network ID.
3. Enter the logical system that you are currently logged on to. This is where the cXML
messages will be received.
4. Select a type of cXML messages that you want to receive. If you require several message
types, create a new entry for each message type.
5. If you use end points in polling, specify the SAP-internal key that corresponds to the Ariba
end point ID.
6. If you expect messages with a high data volume, you can define a maximum number of
messages that are transferred with each response from Ariba Network. This helps to optimize
the performance. Note that a small number will increase the overall duration of message
collection.
7. Specify the name of the logical port that you have defined under Manage and Test
Enterprise Services.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
E)
Define bgRFC Supervisor Destination

Use
In this Customizing activity you define a supervisor destination for the background RFC
(bgRFC). You do this on the Define Supervisor Dest. tab in transaction bgRFC Configuration
(SBGRFCCONF). Using the supervisor destination, the system retrieves the configuration
settings for the bgRFC scheduler and starts or stops the schedulers as required on each
application server.
Requirements
Ensure that the following prerequisites are fulfilled:
In client 000 of your SAP system, you have created a bgRFC supervisor user (with the user
type Service) in transaction User Maintenance (SU01), for example user BGRFCSUPER.
You have assigned the Authorization Role for bgRFC Supervisor User
(SAP_BC_BGRFC_SUPERVISOR) to the user BGRFCSUPER.
In transaction Configuration of RFC Connections (SM59), you have created a bgRFC
supervisor destination, for example destination BGRFC_SUPERVISOR, with the
following settings:
On the Technical Settings tab, you have left the Target Host field empty. This has the
effect that the RFC connection is used within the system where you have created
it.
On the Special Options tab, you have specified the transfer protocol Classic with
tRFC.
Activities
Proceed as follows to configure the bgRFC supervisor destination:
1. In transaction SBGRFCCONF on the Define Supervisor Destination tab, specify the
supervisor destination that you have created.
2. Specify the user that you have created in transaction SU01.
3. On the Scheduler: App. Server tab, enter all application servers that exist in your system
landscape.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
4. On the Define Inbound Dest. tab, specify a destination name.

5. Save your settings.
For more information, see SAP Help Portal at http://help.sap.com/nw70 -> Application Help ->
Function-Oriented View -> SAP NetWeaver by Key Capability -> Application Platform by Key
Capability -> Platform-Wide Services -> Connectivity -> Components of SAP Communication
Technology -> Classical SAP Technologies (ABAP) -> RFC -> Queued Remote Function Call
(qRFC) -> bgRFC (Background Remote Function Call) -> bgRFC Configuration -> Creating a
Supervisor Destination and Creating Inbound Destinations.
5)
Integration Engine Administration

Use
In this Customizing activity, you make settings that enable the Integration Engine of SAP
NetWeaver Process Integration (SAP NetWeaver PI) to perform the exchange of messages
between your SAP systems and Ariba Network. Note that in the list of entries displayed, only
Integration Engine Configuration is relevant.
Requirements
Your SAP NetWeaver PI system has been set up and connected to all relevant SAP systems.
Activities
1. Under Configuration, double-click Integration Engine Configuration.
2. Verify whether the information displayed is correct. Otherwise, check the connectivity to
your PI system.
For more information, see Help -> Application Help.
6)
Map Unit of Measure Codes for cXML Messages

Use
The Customizing acitvities for the mapping of unit of measure codes are only relevant for the
integration of SAP ERP and SAP SRM with the Ariba Network.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
“Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.” P a g e 10 |
46
You can use these activities to map the ISO codes used in your SAP Business Suite system to the
unit of measure codes used in cXML messages, and the other way round. This is relevant if the
codes used in cXML do not match the ISO codes.
7)

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Notes on Implementation
Use
All Business Add-Ins (BAdIs) grouped under this structure node belong to the
enhancement spot ARBFND_INTEGRATION.
BAdI: Notification About Communication Errors

Use
The Business Add-In BAdI for Ariba Integration Foundation (ARBFND_INTEGRATION) with
the method Error Notification (NOTIFY_ABOUT_ERROR) is used in the SAP Business Suite
Integration Component for Ariba Network. You can use this BAdI to trigger actions if errors
have occurred during the communication between your SAP System and Ariba Network.
Example
You can find example implementation CL_EX_ARBFND_BADI_INTEGRATION in the BAdI
Builder on the Enhancement Spot Element Definitions tab in the Implementation Example
Classes section. This example implementation illustrates how you can send error notifications as
e-mails.
Application Specific Setting
1)

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Available Message Types

Use
For SAP ERP, the following cXML message types are available to be exchanged with Ariba
Network:
For Buyers
OrderRequest (outbound direction): For purchase orders and scheduling agreement releases
ConfirmationRequest (inbound direction): For purchase order confirmations
ShipNoticeRequest (inbound direction): For inbound deliveries
InvoiceDetailRequest (inbound direction): For invoices that are sent from the Ariba Network
CopyRequest.InvoiceDetailRequest (outbound direction): For invoices that have been created
in SAP ERP and that are replicated to Ariba Network.
These are, for example, invoices that have been created by the evaluated receipt settlement,
or invoices that have been manually created in SAP ERP.
StatusUpdateRequest (outbound direction): For example, for message processing results, or
for the invoice payment status
Two message types are used for the bidding process on Ariba Network:
QuoteRequest (outbound direction): Technical enablement for customer-specific
implementation provided
QuoteMessage (inbound direction): Technical enablement for customer-specific
Two message types for negotiations on discounts based on accounting documents:
PaymentProposal Request (outbound direction): To propose a payment to the vendor
that is prior to the due date
CopyRequest.PaymentProposalRequest (inbound direction): To send updated
payment proposal including discount rate and payment date in response to the
PaymentProposal Request .
PaymentRemittanceRequest (outbound direction): To send payment documents from
payment runs to Ariba Network
PaymentRemittanceStatusUpdateRequest (outbound direction): For reset and reversed
payment documents
ServiceEntryRequest (Inbound direction): To receive service entry sheets from suppliers via
Ariba Network
ReceiptRequest (outbound direction): This message type is used for sending goods receipts to
Ariba Network.
ProductActivityMessage (outbound direction): This message is used to send inventory and
forecast data for materials to Ariba Network.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
ReceiptRequest (inbound direction): Technical enablement for customer-specific

ComponentConsumptionRequest (inbound direction): For providing visibility on
manufacturing execution; applicable for subcontracting items in purchase orders.
For Vendors
OrderRequest (inbound direction): To create sales orders in SAP ERP on the basis of
purchase orders received from Ariba Network
ConfirmationRequest (outbound direction): For sales order confirmations
ShipNoticeRequest (outbound direction): For outbound deliveries
InvoiceDetailRequest (outbound direction): For invoices that are sent to the Ariba Network
PaymentRemittanceRequest (inbound direction): To receive remittance advices from Ariba
Network
2)
Assign Ariba Network ID to Company Code

Use
In this Customizing activity, you can assign the Network IDs that you have received for Ariba
Network to the company codes in your SAP ERP system. This enables Ariba Network to clearly
identify the sender of the cXML message.
Note that you can use the same Network ID for more than one company code. Similarly, you can
use several Network IDs for one company code. Normally, you assign one Network ID to one
company code. If you want to assign more than one Network IDs to a company code, you must
implement the Outbound Mapping BAdI to adapt the assignment of the Network ID to your
requirements. For more information, see the documentation of the Outbound Mapping BAdI.
Requirements
You have entered at least one Ariba Network ID under Define Credentials for Ariba Network.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
3)
Define Message Output Control

Use
In this Customizing activity, you can define how documents that have been created or changed in
SAP ERP are transferred to Ariba Network. This is relevant for the following documents:
Standard Output cXML Message

Document Application
Type Type
Purchase orders EF NEU ORDR
Scheduling Agreement Release (FRC) EL LPH1 ORDR
Scheduling Agreement Release (JIT) EL LPJ1 ORDR
Updates to service entry sheets ES NEU STAT
Invoices (evaluated receipt settlement) MR ERS6 CCINVC
Shipping notifications V2 LD00 SHIP
Billing documents (SD) V3 RD00 INVC
The activity consists of the following main steps:
1. You define the conditions under which documents are transferred from SAP ERP to Ariba
Network. You do this for a specific output type, using message control. Note that for
purchase orders, SAP recommends that you use the output type NEU that is delivered by
SAP.
For more information, see Define Conditions for Output Control.
2. Fine-tuning of output control:
For purchase orders: If you do not use the output type NEU for purchase orders, you
have to fine-tune the output control. See Fine-Tune Control of Purchase Order.
For service entry sheets: See Customizing for Materials Management under External
Services Management -> Messages -> Output Control for Service Entry Sheet.
For invoices: See Customizing for Materials Management under Logistics Invoice
Verification -> Message Determination.
For billing documents: See Customizing for Sales and Distribution under Basic
Functions -> Output Control -> Output Determination -> Output Determination
Using the Condition Technique -> Maintain Output Determination for Billing
Documents.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
3. You map the document type in SAP ERP to a document type on Ariba Network.
For more information, see Map Application and Output Type to cXML Message.
4. If you use scheduling agreement releases, you have to assign one of the following release
types to the output types that you use:
Forecast delivery schedule
JIT delivery schedule

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
4)
Define Document-Specific Message Customizing

Use
In this Customizing activity, you define whether you want to do the following:
Transfer Attachments with cXML Messages
Here you define whether you want to enable the transfer of attchments with your business
objects. You define this for inbound and for outbound messages. You can differentiate your
settings for each inbound and outbound message type that exists in the Ariba system. If you
want to enable the transfer, select Generic Object Services under Attachment Transfer. If you
do not make an entry, attachments are not transferred to AN, and incoming attachments are
not stored.
Note that only attachments stored in Generic Object Services are supported.
Attach the cXML Message Payload to Business Objects
You choose this if you want to store the cXML message payload from which the business
object originates. This setting is typically used for invoices.
5)

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Map Texts of SAP ERP and Ariba Network

Use
In this Customizing activity, you can map cXML comments to SAP ERP texts.
Define cXML Comment Types for Text Mapping
In this activity, you specify the cXML comment type IDs that you want to map to SAP ERP
texts. For example, you can specify the cXML comment type COMMENTS_TO_BUYER and a
text that explains the comment type.
Define Text Mapping for Inbound Messages
In this activity, you specify the mapping details for cXML messages that you receive from Ariba
Network. For more information, see the Activities section below.
Define Text Mapping for Outbound Messages
In this activity, you specify the mapping details for cXML messages that you send to Ariba
Network. For more information, see the Activities section below.
Requirements
Text types have been defined in the standard Customizing of SAP ERP.
Activities
Define Text Mapping for Inbound Messages
Proceed as follows:
2. Select a combination of cXML message type and cXML element ID. The columns for the
corresponding object type and object node in SAP ERP are then automatically filled.
3. Select the ID of a comment type that you want to map. You have the following options:
Use one of the comment type IDs you have specified under "Define cXML Comment
Types for Text Mapping".
Use the blank entry to map all cXML comments that have no comment type to a
specific SAP ERP text object and ID.
Use the wildcard (*) to map all cXML comments, independent of their comment type,
to a specific SAP ERP text object and ID.
4. Select a combination of SAP ERP text object and text ID to which you want to map the
cXML comments.
Define Text Mapping for Outbound Messages
You can explicitly define which texts existing in SAP ERP are transferred to Ariba Network. To
do this, proceed as follows:

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
2. Select a combination of the SAP ERP business object type and object node (header or
item). The columns for the corresponding cXML message type and element ID are then
automatically filled.
3. Select a combination of SAP ERP text object and text ID that you want to map to cXML.
4. If you want to map the text to a specific comment type on Ariba Network, enter the
corresponding comment type ID. If you do not enter a comment type ID, the text is
nevertheless included in the cXML message.
Example
Text Mapping for Inbound Messages
A shipping notification received from Ariba Network contains the comment type "Transport".
You can map this comment type to the text "ERP Transport Information" that you may have
defined for business objects of the object type "Inbound Delivery".

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
6)
Adapt Mapping of SAP ERP Incoterm to cXML "TransportTerms"

Use
In this Customizing activity, for each incoterm in your SAP ERP system you can define what
you want to transfer in the cXML element "TransportTerms" as the value and as the content for
the incoterm. You do this if the recipient of the cXML message expects the "TransportTerms" in
a specific way that differs from the standard.
This Customizing activity is optional.
Example
In your SAP ERP system, the incoterm "FOB" exists, and it has the description "Free on board".
By default, this incoterm is transferred to the Ariba Network in the cXML element
"TransportTerms" with the value "FOB" and the content "Free on board".
However, you want to transfer "Free on Board" as the value and "FOB" as the content.
To reflect this, select the incoterm "FOB" and make the corresponding entries in the columns
cXML 'TransportTerms' Value and cXML 'TransportTerms' Content.
7)
Decide Whether to Make Settings for Buyers or Vendors

Use
You can connect to Ariba Network as a buyer or as a supplier. As a buyer, you integrate business
objects from SAP ERP MM and FI. As a supplier you integrate business objects from SAP ERP
SD. Accordingly, make the settings under Customizing structure node Integration for Buyers or
the settings under Integration for Vendors.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
8)
A)
Enable Vendors for Ariba Network

Use
In this optional Customizing activity, you can invite vendors that have not yet subscribed to the
Ariba Network to do business with you through the Network.
Activities
1. Select New Entries.
2. Specify the ID that your vendor has in SAP ERP.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
3. Activate quick enablement. By doing this, you create an Ariba Network account on behalf
of the supplier. The system transfers the supplier's company information from the SAP ERP
system to Ariba Network as part of the cXML message. On the basis of this information, the
account is created.
B)
Activate Business Transaction Events to Trigger Messages

Use
In this Customizing activity, you can activate a set of Business Transaction Events (BTEs) to
record changes made to invoices in SAP ERP Financials. This applies both to MM invoices and
FI invoices. BTEs must be activated to record the creation of and changes to accounting
documents in FI.
For general information about BTEs, see the standard documentation.
Activities
To activate BTEs, select the checkbox Active for the given application indicator ARBERP.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
C)
Enable Further Outbound Message Types per Vendor

Use
In this Customizing activity, you allow the sending of message types that are not transferred via
output management. You enable a message type for selected suppliers on the Ariba Network by
specifying the company codes and the suppliers for which the enablement is valid.
The following additional message types are available:
CopyRequest.InvoiceDetailRequest
This message type is used for MM invoices and for FI invoices that have been created in
SAP ERP and that are replicated to Ariba Network. These are, for example, MM invoices
that have been created by the evaluated receipt settlement, or MM or FI invoices that have
been manually created in SAP ERP.
PaymentProposalRequest
This message type is used to start negotiations on discounts by proposing a payment to the
vendor that is prior to the due date.
PaymentRemittanceRequest
This message type is used to send information about the payment run.
ReceiptRequest
This message type is used for sending goods receipts to Ariba Network.
ProductActivityMessage
This message is used to send inventory and forecast data for materials to Ariba Network.
Requirements
You have specified that you want to exchange the above mentioned message types through the
Ariba Network under Define Basic Message Settings.
Activities

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
2. For the Vendor that you want to enable to receive an additional message type, specify the
vendor ID from SAP ERP.
3. Specify the cXML Message Type you want to enable.
4. Enter the Company Code for which you want to enable the additional message type for the
vendor specified under 2.
Note:
While you must specify a vendor, you can leave the Company Code column empty. In this case,
the message type is enabled for all company codes.
D)
Schedule Jobs for Outbound Messages

Use
In order to synchronize data between SAP ERP and Ariba Network via cXML messages, you
must schedule several reports as jobs. The reports then record the creation or status change of the
documents in SAP ERP and ensure that the sending of the corresponding cXML messages is
triggered.
Schedule the reports with the following selection option: <type of document affected> Since Last
Report Run. This means that the report determines the documents that have been created or
changed since the last report run and triggers sending of the corresponding cXML messages.
For situations where cXML messages are not transferred to Ariba Network, most reports offer
some reconciliation modes. They allow you to select specific documents again and resend the
corresponding cXML messages.
Standard settings
To enable the sending of the cXML messages, you must schedule the corresponding reports.
For messages transferring goods receipts to Ariba Network, schedule the following report:

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
ARBERP_BUS2017_EXTRACT_RCPT
For messages about status updates in SAP ERP of invoices created on Ariba Network,
schedule the following report:
ARBERP_BUS2081_EXTRACT_STS_UPD (with invoice origin Received from
Ariba Network)
For messages transferring MM CC invoices, schedule the following reports:
ARBERP_BUS2081_EXTRACT_CCINVC
ARBERP_BUS2081_EXTRACT_STS_UPD (with invoice origin Created by Buyer
in SAP ERP System)
For messages transferring FI CC invoices, schedule the following reports:
ARBERP_BKPF_EXTRACT_CCINVC
ARBERP_BKPF_EXTRACT_STS_UPD
For messages transferring accounting documents (relevant for discount management on
Ariba Network), schedule the following report:
ARBERP_BKPF_EXTRACT_PAYP
For messages transferring payment run information (relevant for payment remittances on
Ariba Network), schedule the following report:
ARBERP_FIOPAYAVIS_EXTRACT_PAYR
For more information about the processes themselves and about the cXML messages, see the
release note.
Activities
The following steps are required for all above mentioned reports:
1. Save a variant containing the selection parameters that you require.
2. Schedule this variant as a job.
E)
Define Mapping Settings for Shipping Notifications

Use
Shipping notifications can contain information about the carrier. In this Customizing activity,
you can map the carrier domains and IDs used by Ariba to the carrier IDs used in SAP ERP.
Note that, in SAP ERP, carriers have the business partner type Vendor.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
F)
Define Mapping Settings for Invoices

Use
In this Customizing activity, you can define the mapping of data that is relevant for Logistics
Invoice Verification. Using Logistics Invoice Verification is mandatory if you transfer invoices
between Ariba Network and SAP ERP.
Related Customizing
You can customize vendor-specific tolerances: vendor-specific tolerances.
Mapping Activities
Incoming Invoice: Map Tax Codes for Logistics Invoice Verification
In this activity, you map the tax categories and country-specific values that exist on Ariba
Network to the tax codes in your SAP ERP system. You can do this for each of your vendors.
As a prerequisite, tax categories must be configured for your Ariba Network account.
Incoming Invoice: Map Company Codes for Logistic Invoice Verification
In this activity, you map the company code in your SAP ERP system to a billTo name in the
incoming cXML message. You do this for each of your vendors.
Incoming Invoice: Enter Control Parameters for Logistics Invoice Verification
In this activity, you define the following information for incoming invoices that a vendor sends
to a specific company code:
Which types of invoices and credit memos you want to create in SAP ERP
How the system reacts if there are differences between the values received in cXML and the
values proposed by SAP ERP.
For more information, see the Activities section below.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Incoming Invoice: Map cXML Partner to SAP ERP Invoicing Party

In this activity, you can specify a different invoicing party for incoming cXML invoices. You do
this if you want to post an incoming invoice to a different vendor than the vendor in the purchase
order.
To determine the invoicing party, the system uses the name that is transferred in cXML tag
"InvoicePartner" (with role "from"), in combination with the technical sender of the cXML
message (identified by VendorID in "From" "Credential").
In the column Name of ERP Invoicing Party you have to specify the SAP ERP vendor ID that
you want to be set as the invoicing party.
If you want outgoing documents (such as CC invoices or payment remittances) and status
updates to be sent to the original vendor, select the Reverse Mapping checkbox.
This Customizing is optional. By default, the invoicing party is identical to the vendor in the
purchase order.
If you want to overrule the logic described above, you can use the BAdI method
INVC_INV_PARTY_DETERMINATION of the inbound mapping BAdI
(ARBERP_INBOUND_MAPPING).
CC Invoice: Map Tax Category for Ariba Network Invoice
In this activity, you map the tax code in your SAP ERP system to the tax category to be used in
the Ariba Network invoice. You can do this for each of your vendors. The mapping is valid both
for MM and for FI invoices.
As a prerequisite, tax categories must be configured for your Ariba Network account.
Activities
Incoming Invoice: Enter Control Parameters for Logistics Invoice Verification
To specify the control parameters necessary for Logistics Invoice Verification, proceed as
follows:
1. Select New Entries.
2. Specify a vendor from whom you receive invoices and credit memos.
3. Specify the company code that receives the invoices and credit memos.
4. Under Inv.doc, select the type of invoice that you want to create in SAP ERP for invoices
coming in from Ariba Network.
5. Under Cred.doc, select the type of credit memo that you want to create in SAP ERP for
credit memos coming in from Ariba Network.
6. Under Processing, define how the system reacts if there are differences between the values
received in cXML messages and the values proposed by SAP ERP. To do this, you must
specify one of the following processing types:
No error
The invoice document is posted using the invoice data. If it contains quantity or price
variances, the system blocks it for payment.
Unclarified error; park invoice

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
The invoice document is created as containing unclarified errors. It is saved with the
values proposed by the system and the values contained in the cXML invoice. You
have to manually process the parked invoice document later.
7. Define whether the material numbers and units of measure in the cXML invoice are
compared to those in the purchase order items. Note that the invoice cannot be posted if there
are variances.
8. Define whether the system additionally checks the invoice document for negative
variances, in other words, checks for variances in favor of the invoice recipient.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
G)
Define Mapping Settings for Payments

Use
In this Customizing activity, you map the payment methods that exist on Ariba Network to the
payment methods in your SAP ERP system.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
H)
Define Mapping Settings for Component Consumption Requests

Use
In this customizing activity is relevant for subcontracting items in purchase orders.
You must define the external confirmation category that will be used when processing
ComponentConsumptionRequest cXML messages to provide visibility on manufacturing
execution.
The confirmation category you define here will be part of the confirmation control key used for
subcontracting items in purchase orders.
Important:
In Customizing for Materials Management under Purchasing -> Confirmations -> Define
Internal Confirmation Categories, find out which confirmation category is assigned to the
internal confirmation category Order Acknowledgement.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
When defining the external confirmation category for manufacturing execution visibility, ensure
that the category you use is different from the confirmation category assigned to the internal
confirmation category Order Acknowledgement.
9) Integration for vendors.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
A)
Map cXML Partner Role to SAP ERP Partner Function

Use
In this Customizing activity, you can map Ariba partner type descriptions to SAP ERP Sales and
Distribution partner functions.
Requirements
You have maintained partner functions.
Example
cXML Partner Role Partner Function
Ship To AG
Bill To BP
Sold To RE
B)

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
a)
Map cXML Partner to SAP ERP SD Customer

Use
In this Customizing activity, you map the name of a partner in the cXML to a SAP Sales and
Distribution (SD) partner based on the partner function and Ariba Network ID.
Requirements
You have maintained partners and partner functions.
Example
cXML Part.Name Ariba NetworkID cXMLPartner Role Partner Name
Partner1 AN02000606130 S shipTo Cust12
b)
Map cXML Order Type to SAP ERP SD Document Settings

Use

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
In this Customizing activity, you can map Ariba order types to SAP ERP Sales and Distribution
(SD) order types for a customer.
When an error occurs during the creation of a sales order from the cXML, it applies a block
which is specified in the "Applicable Delivery Block" column.
Requirements
You have maintained customers in SD master data as well as SAP order types and delivery
blocks in the SD configuration in your SAP ERP system.
Example
Cust Cust. PO Type Ariba Sales Doc. Sales Doc.Ty. App. Del. Del. Block
. Name Network Ty. Descr. Block Desc.
1 Cust1 Regular TA 1
c)
Maintain Sales Area for SAP ERP SD Customer

Use
In this Customizing activity, you can map a customer to a sales area for the creation of a sales
order in your SAP ERP Sales and Distribution system.
Requirements
You have maintained customers and sales areas.
Example
Cust. Sales Sales Org. Distr. Channel Division
Cust. Distr. Ch. Division
Name Org. Name Name Name
Cus1 SAP AG 0001 01 01

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Cus2 SAP AG 0001 01 10
C)
Assign Shipping Point to Ariba Network ID

Use
In this Customizing activity, you can assign the Network IDs that you have received for Ariba
Network to the shipping points in your SAP system. This enables Ariba Network to clearly
identify your company as the sender of the cXML message and as the supplier of the goods or
materials.
Note that you can use the same Network ID for more than one shipping point.
Requirements
You have entered at least one Ariba Network ID under Define Credentials for Ariba Network.
D)

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Map cXML Partner to SAP ERP SD Customer in Payment Advice

Use
After a payment run has been executed in the customer's ERP system, the customer sends a
payment advice as a cXML message via the Ariba Network to your SAP system.
To enable your SAP system to receive payment advices from the Ariba Network, in this
Customizing activity you map the customer name (in the system, the customer is called
"partner"), the Ariba Network ID, and customer role in the cXML message to the name of the
customer in your SAP system.
After you have done this, you will receive payment advices sent by the customer via the Ariba
Network in your SAP system.
Example
cXML Partner Name Ariba Network ID cXML Partner Role Partner Partner Name
ABC AN12345 Payer ABC ABC
Here is what the table means:
cXML Partner Name = Customer in the cXML message, who sends the payment advice
Ariba Network ID = ID of the customer in the Ariba Network
cXML Partner Role = is always Payer
Partner = Customer Account No. in the SAP system
Partner Name = Customer Name in the SAP system
E)
a)

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Maintain Ariba Network ID for SAP ERP SD Customer

Use
In this Customizing activity, you maintain the Ariba Network ID for the Sales and Distribution
customer.
Additionally, you can define a default Bill To Address ID, which is used to route invoices
without order reference (Ariba Network non-PO invoices) by the customer.
Example
Customer Customer Name Ariba Network ID Default Bill To Address ID
Cust1 SAP AG AN02000225634 ERPCLNT001
b)
Map SAP ERP SD Tax Code to cXML Tax Category

Use
In this Customizing activity, you map the tax code in your SAP ERP Sales and Distribution
system to the tax category for the Ariba Network invoice.
The activity supports wild card logic which works as follows:
If a bill to party is maintained then the tax code from that record is used.
Otherwise the tax code is taken from the record where no bill to party is mentioned.
Requirements
You must configure countries, tax codes and tax categories.
Example

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Bill-to Party Customer Name Country Tax Code Tax Category in cXML
6 Cust 1 DE V1 VAT
Bill-to Party Customer Name Country Tax Code Tax Category in cXML
Cust 1 DE V1 VAT
10)
BAdI: Outbound Mapping

Use
This Business Add-In (BAdI) is used in the Suite Enablement for Ariba (BNS-ARI-SE-ERP)
component. You can use this BAdI to change the result from the mapping of outbound SAP ERP
documents to Ariba cXML messages. Outbound SAP ERP documents can be purchase orders or
invoice statuses, for example.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Methods Relevant for all Outbound cXML Message Types

DEFINE_CUST_SPEC_MAPPING
With this method, you can freely define your own mapping. You can analyze the outgoing
documents. You can implement a logic that decides, based on the results of the analysis, whether
a document should undergo the standard mapping or not. Set the parameter
cv_proceed_with_appl_proc for documents that should undergo the standard mapping.
ASSIGN_SENDER_ANID
You can overwrite the standard assignment of an Ariba Network ID (ANID) to the sender of an
outbound document. By default, the ANID is assigned on company code level. You can use this
BAdI, for example, to assign ANIDs on a lower level, such as the level of purchasing
organizations.
ASSIGN_SENDER_ENDPOINT
You must implement this method if you have assigned more than one end point to one Ariba
Network ID. In this case, use this method to define unique end points for outbound documents.
Method Relevant for all cXML Messages Sent by Output Control
NAST_OUTPUT_FILTER
You can implement additional filter criteria to decide whether a message should be sent to Ariba
Network
Methods Relevant for Specific Processes
Send Purchase Order to Ariba Network with cXML OrderRequest Message
Method MAP_BUS2012_TO_ORDR_OUT:
You can enrich or (partially) overwrite the cXML message after the standard mapping has been
performed.
Send Scheduling Agreement Release to Ariba Network with cXML OrderRequest Message
Method MAP_BUS2013002_TO_ORDR_OUT:
performed.
Replicate Incoming Invoice to Ariba Network (CC Invoice) with cXML CopyRequest.InvoiceDetailRequest
Message
Method INSERT_CCINVC_TRIGGER_5010:
Network. The filters influence the selection of documents sent by the following reports:
For MM invoices: report ARBERP_BUS2081_EXTRACT_CCINVC in the mode ERP-
Initiated Invoices Posted Since Last Report Run.
For FI invoices: report ARBERP_BKPF_EXTRACT_CCINVC in the mode Accounting
Documents Posted Since Last Report Run.
Method SELECT_BUS2081_CCINVC_OUT (Relevant for MM CC Invoices):
Network. The filters influence the selection of MM documents sent by report
ARBERP_BUS2081_EXTRACT_CCINVC in the reconciliation modes.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
Method SELECT_BKPF_CCINVC_OUT (Relevant for FI CC Invoices):

Network. The filters influence the selection of FI documents sent by report
ARBERP_BKPF_EXTRACT_CCINVC in the reconciliation modes.
Method MAP_BUS2081_TO_CCINVC_OUT (Relevant for MM CC Invoices):
performed.
Method MAP_BKPF_TO_CCINVC_OUT(Relevant for FI CC Invoices):
performed.
Method CCINVC_SELECT_NONPO_IV_LEVEL (Relevant for FI and for MM CC Invoices):
You can define whether you want to transfer a CC invoice as a header-level invoice or whether
you also transfer posting lines as invoice items.
Send Invoice Status to Ariba Network with cXML InvoiceStatusUpdateRequest Message
Method INSERT_INVC_STAT_TRIGGER_5010:
Network. The filters influence the selection of documents sent by report
ARBERP_BUS2081_EXTRACT_STS_UPD in the mode Invoices Created/Changed Since Last
Report Run.
Method SELECT_BUS2081_STAT_OUT (Relevant for MM CC Invoices):
Network. The filters influence the selection of MM documents sent by report
ARBERP_BUS2081_EXTRACT_STS_UPD in the reconciliation modes.
Method SELECT_BKPF_STAT_OUT (Relevant for FI CC Invoices):
Network. The filters influence the selection of FI documents sent by report
ARBERP_BKPF_EXTRACT_STS_UPD in the reconciliation modes.
Method GET_BUS2081_STAT_APPL_DATA:
You can select additional customer-specific documents to be sent with cXML
InvoiceStatusUpdateRequest messages.
Method MAP_BUS2081_TO_STAT_OUT (Relevant for MM CC Invoices):
performed.
Method MAP_BKPF_TO_STAT_OUT (Relevant for FI CC Invoices):
performed.
Send Account Document to Ariba Network (Discount Management) with cXML PaymentProposalRequest
Message
Method INSERT_PAYP_TRIGGER_5010:

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
ARBERP_BKPF_EXTRACT_PAYP in the mode Accounting Documents Posted Since Last
Report Run.
Method SELECT_BKPF_PAYP_OUT:
ARBERP_BKPF_EXTRACT_PAYP in the reconciliation modes.
Method MAP_BKPF_TO_PAYP_USE_NET_DAYS:
You can specify that payment should be effected on or after the due date without considering
discount from payment terms.
Method MAP_BKPF_TO_PAYP_OUT:
performed.
Send Payment Document from Payment Run to Ariba Network with cXML PaymentRemittanceRequest
Message
Method INSERT_PAYR_TRIGGER_RFFO:
ARBERP_FIOPAYAVIS_EXTRACT_PAYR in the mode Payment Documents Posted Since
Last Report Run.
Method SELECT_FIOPAYAVIS_TO_PAYR_OUT:
ARBERP_FIOPAYAVIS_EXTRACT_PAYR in the reconciliation modes.
Method MAP_FIOPAYAVIS_TO_PAYR_OUT:
performed.
Send Reset and Reversed Payment Document to Ariba Network with cXML
PaymentRemittanceStatusUpdateRequest Message
Method INSERT_PAYS_TRIGGER_5010:
ARBERP_FIOPAYAVIS_EXTRACT_PAYR in the mode Payment Documents Posted Since
Last Report Run.
Method SELECT_BKPF_TO_PAYS_OUT:
ARBERP_FIOPAYAVIS_EXTRACT_PAYR in the reconciliation modes.
Method MAP_BKPF_TO_PAYS_OUT:

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
performed.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the
Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Example
You can find an example implementation in the BAdI Builder on the Enhancement Spot Element
Definitions tab in the Implementation Example Classes section.
CL_EX_ARBERP_BADI_OUTBOUND_MAP
This is an example implementation for outbound purchase orders. It enriches the resulting
Ariba cXML message with information about purchasing groups and purchasing group texts
on header level, and with information about product types, product type texts, and customer
part numbers on item level.
See also
For information about implementing BAdIs as part of the enhancement framework, see SAP
Library for SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform.
Choose a release and then Application Help --> Function-Oriented View --> Application Server -
-> Application Server ABAP --> Application Development on AS ABAP --> ABAP Customer
Development --> Enhancement Framework.
BAdI: Inbound Mapping

Use
This Business Add-In (BAdI) is used in the Suite Enablement for Ariba (BNS-ARI-SE-ERP)
component. You can use this BAdI to change the mapping of Ariba cXML message elements to
SAP ERP application interface structures.
Inbound Ariba cXML messages can be order confirmation messages, ship notice messages, or
invoice messages, for example.
The following are possible use cases for this BAdI:
1. You want to freely define your own mapping.
2. You want to implement your own processing logic.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
3. Ariba cXML messages contain field types that are not considered in the standard mapping,
for example, if cXML messages have been enhanced with extrinsic elements. In this case,
you can use the BAdI to include additional fields into the mapping.
4. You want to map one or more cXML elements to ABAP fields different from those
assigned in the standard mapping. In this case, you can modify the standard mapping.
5. You want to perform additional functions, for example, an own attachment handling, after
the application interface processing. At this point in time, the business object is created, but
not yet persisted.
Note:
You must not trigger "Commit Work" within this BAdI.
6. For invoices, you want to change the standard company code determination, or the
standard tax code determination, or you want to define how multiple tax codes on header
level are to be assigned to the items.
For use cases 1 and 2, the method DEFINE_CUST_SPEC_PROCESSING is available. It is
called for all incoming cXML messages.
You can analyze the incoming messages. You can implement a logic that decides, based on the
results of the analysis, whether a message should undergo the standard mapping and processing
logic or not. Set the parameter cv_proceed_with_appl_proc for messages that should undergo the
standard mapping and processing logic.
If you want to define your own mapping, but you want to apply the standard processing logic to
call the application interface, you can use the parameter cv_skip_stmap_and_call_appl_if.
For use cases 3 and 4, the BAdI includes one method per document type. These methods are
called before the application interface is called (pre-methods), but after the standard mapping has
been performed:
MAP_SHIP_TO_BUS2015_IN_PRE
MAP_CONF_TO_BUS2012_IN_PRE
MAP_INVC_TO_BUS2081_IN_PRE
MAP_PAYP_TO_BKPF_IN_PRE
MAP_PAYR_TO_AVIK_IN_PRE
For use case 5, the BAdI contains one post-method per document type. Post methods are called
after the business object has been created. The following post-methods are available:
MAP_SHIP_TO_BUS2015_IN_POST
MAP_CONF_TO_BUS2012_IN_POST
MAP_INVC_TO_BUS2081_IN_POST
MAP_PAYP_TO_BKPF_IN_POST
MAP_PAYR_TO_AVIK_IN_POST
Three methods are available for the use cases described under 6. They are called during the
standard mapping and can be used specifically for invoices:
INVC_COMPANYCODE_DETERMINATION

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46
INVC_TAXCODE_DETERMINATION
INVC_ITM_TAXCODE_DETERMINATION
You can use this method for inbound invoice messages where more than one tax code is
assigned on header level. The method is called for each item that is mapped to the SAP ERP
interface structures and determines the correct tax code to be used for the item. You can use
this method only if no tax jurisdiction is active.
INVC_INV_PARTY_DETERMINATION
You can use this method for inbound invoice messages to define a deviating invoicing party.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the
Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
See also
For information about implementing BAdIs as part of the enhancement framework, see SAP
Library for SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform.
Choose a release and then Application Help --> Function-Oriented View --> Application Server
--> Application Server ABAP --> Application Development on AS ABAP --> ABAP Customer
Development --> Enhancement Framework.

IND: +91 992 284 8898|USA: +1 678 389 8898|UK: +44 141 416 8898
46

SAP ARIBA Integration Configuration_RDS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP ARIBA Integration Configuration_RDS

Uploaded by

Copyright:

Available Formats

SAP ARIBA Integration Guide - SAPVITS

Full screenshot of SPRO with all extension-

Vintage IT Solutions http://www.sapvits.com

Vintage IT Solutions http://www.sapvits.com

Define Credentials and End Points for Ariba Network

Vintage IT Solutions http://www.sapvits.com

A shared secret for each end point

Vintage IT Solutions http://www.sapvits.com

Define Basic Message Settings

Vintage IT Solutions http://www.sapvits.com

Decide on Connectivity Type

Manage and Test Enterprise Services

Vintage IT Solutions http://www.sapvits.com

Vintage IT Solutions http://www.sapvits.com

Schedule Polling Agent

Define Settings for Polling Agent

Vintage IT Solutions http://www.sapvits.com

Define bgRFC Supervisor Destination

Vintage IT Solutions http://www.sapvits.com

4. On the Define Inbound Dest. tab, specify a destination name.

Integration Engine Administration

Map Unit of Measure Codes for cXML Messages

Vintage IT Solutions http://www.sapvits.com

Vintage IT Solutions http://www.sapvits.com

BAdI: Notification About Communication Errors

Application Specific Setting

Vintage IT Solutions http://www.sapvits.com

Available Message Types

Vintage IT Solutions http://www.sapvits.com

ReceiptRequest (inbound direction): Technical enablement for customer-specific

Assign Ariba Network ID to Company Code

Vintage IT Solutions http://www.sapvits.com

Define Message Output Control

Standard Output cXML Message

Vintage IT Solutions http://www.sapvits.com

Vintage IT Solutions http://www.sapvits.com

Vintage IT Solutions http://www.sapvits.com

Define Document-Specific Message Customizing

Vintage IT Solutions http://www.sapvits.com

Map Texts of SAP ERP and Ariba Network

Vintage IT Solutions http://www.sapvits.com

Vintage IT Solutions http://www.sapvits.com

Adapt Mapping of SAP ERP Incoterm to cXML "TransportTerms"

Decide Whether to Make Settings for Buyers or Vendors

Vintage IT Solutions http://www.sapvits.com

Enable Vendors for Ariba Network

Vintage IT Solutions http://www.sapvits.com

Activate Business Transaction Events to Trigger Messages

Vintage IT Solutions http://www.sapvits.com

Enable Further Outbound Message Types per Vendor

Vintage IT Solutions http://www.sapvits.com

Schedule Jobs for Outbound Messages

Vintage IT Solutions http://www.sapvits.com

Define Mapping Settings for Shipping Notifications

Vintage IT Solutions http://www.sapvits.com

Define Mapping Settings for Invoices

Vintage IT Solutions http://www.sapvits.com

Incoming Invoice: Map cXML Partner to SAP ERP Invoicing Party

Vintage IT Solutions http://www.sapvits.com

Vintage IT Solutions http://www.sapvits.com

Vintage IT Solutions http://www.sapvits.com

Define Mapping Settings for Payments

Vintage IT Solutions http://www.sapvits.com

Define Mapping Settings for Component Consumption Requests