Cookbook Documentation for OB10 Invoicing

Interface
Document in Solution Manager (1)
Table of contents
1. GENERAL INFORMATION ........................................................................................................................... 3
2. SYSTEM ENVIRONMENT ............................................................................................................................. 3
2.1 INVOICE PROCESSING ....................................................................................................................................... 3
3. FREQUENTLY ASKED QUESTIONS .......................................................................................................... 5
3.1 HOW-TO: ADD A NEW BILL-TO TO AN EXISTING COMPANY OB10 ACCOUNT .................................................... 5
3.2 HOW-TO: ADD A NEW COMPANY OB10 ACCOUNT ........................................................................................... 7
4. TYPICAL INCIDENTS .................................................................................................................................... 9
5. ALARM REACTION PROCEDURES ........................................................................................................... 9
5.1 PI ALERTS ....................................................................................................................................................... 9
5.2 OB10 ALERTS ................................................................................................................................................. 9
6. WORKAROUNDS, TIPS AND TRICKS ...................................................................................................... 11
6.1 SEARCHING FOR OB10 MESSAGES IN PI ........................................................................................................ 11
7. PROBLEM ESCALATION STRATEGY ..................................................................................................... 11
8. KNOWN ERRORS ......................................................................................................................................... 11
9. FUTURE NEW RELEASES AND UPGRADES .......................................................................................... 11
Company IT
Company Version 1.0 -9/23/2019 Page 3 of 12
Document in Solution Manager (1)
1. General information
This is a cookbook for the OB10Invoicing scenario in PI.
2nd Level person is System Integration
He/she is responsible for all information in this document.
2. System Environment
This interface delivers invoices from SAP system LP1 to OB10, an invoicing network. OB10
handles the details of delivering the invoice electronically to the actual Company customer.
OB10
2.1 Invoice processing
Invoices created in LP1 are automatically sent to PI as INVOIC.INVOIC02 IDoc’s. No
mapping is performed in PI – the IDoc’s are just forwarded by PI to OB10.
Users can monitor sent invoices in the OB10 portal (https://portal.ob10.com). Portal
Administrators can create portal users and set alert receivers for invoices that fail at OB10.
Company IT
Company Version 1.0 -9/23/2019 Page 4 of 12
Document in Solution Manager (1)
2.1.1 Mapping
As mentioned, no mapping is done in PI. The interesting thing however is still from where OB10
picks the relevant information in the IDoc.
Delivered to
In general the values are taken from partner ZB (Sales Responsible) that can be found on item
line of the invoice (IDoc segment E1EDPA1. If partner ZB is not found then the value is taken
from the second E1EDPA1 which is normally ZC (Customer Service).
While setting up AAA844095539 (Company Deutschland GmbH) to AAA520400094 (Nestlé Deutschland
AG) in 2014 we specifically asked OB10 to map WE (ship-to) instead.
Original invoice number
Nestlé requires that original invoice number must be present in credit memos. OB10 take it from
here:
General Nestle information can be found here: www.tungsten-network.com/de/de/NestleDE/
For some reason it has been decided in the past that original invoice number should be taken
from a text element.
Company IT
Company Version 1.0 -9/23/2019 Page 5 of 12
Document in Solution Manager (1)
To streamline the process it might be worthwhile do use the same approach as for Nestlé.
3. Frequently Asked Questions
3.1 How-to: Add a new customer to an existing Company OB10 Account
Adding a new customer requires configuration on both the SAP ECC and the SAP PI side. An
overview of existing Company OB10 accounts can be found in chapter 7.
3.1.1 SAP ECC
Output condition, N&H Europe: Transaction VV31
In LP1, add the new Bill-to in transaction VV31 for output types ZB03, ZB06 and ZB07:
Output condition, IB: Transaction VV31
Same approach as US/CA – see below.
Output Condition, US/CA: Transaction VV31
USA and Canada are using output type RD00 instead of ZB03, ZB06 and ZB07. Note that RD00
output determination for these is based on Payer. Therefore, Payer is maintained in VV31 (still
Company IT
Company Version 1.0 -9/23/2019 Page 6 of 12
Document in Solution Manager (1)
with BP as the function – for some reason!?). It’s not clear why US/CA and N&H Europe are
using different approaches.
Account link, Europe: Transaction VOE4
OB10 has its own customer master – so-called OB10 accounts. AAA379239379 with the name
Nestlé Deutschland AG is an example. This account has a specific VAT no. (Europe only),
address, PO box etc. By comparing these values with our own in SAP we can find a unique link
between our customer number and the OB10 customer number. This linkage is required and can
be done in different ways. US and Canada do it in one way and Europe in another.
In LD2-600 table edpar is customized using transaction VOE4. The relevant Company Sold-to’s
(related to the before-mentioned Bill-to’s) are linked with the Customer’s corresponding OB10
account.
Account link, US/CA: Alias in OB10 portal
Table edpar is not used. Instead the alias concept in OB10 portal is used.
Partner profile: Europe, Transaction WE20
In LP1, create an entry in WE20 with the Bill-to in question.
Outbound parameters:
Partn.type KU Customer
Partn.funct. BP Bill-to party
Message type INVOIC
Message code FI
Basic type INVOIC02