Supplier in Voice Processing

8/19/2019 Supplier in Voice Processing

1/89

SOA Documentation

Supplier Invoice Processing

CUSTOMER

Document Version: 7063 – May 29, 2012


2/89

(C) SAP AG Supplier Invoice Processing 2

Copyright

© Copyright 2012 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC,BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF,Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet aretrademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.


3/89


RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerryTorch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,

Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android aretrademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany andother countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks ofBusiness Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks ofCrossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying such

products and services, if any. Nothing herein should be construed as constituting anadditional warranty.


4/89



5/89


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screentitles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT Technical names of system objects. These include report names, programnames, transaction codes, table names, and key concepts of a programminglanguage when they are surrounded by body text, for example, SELECT andINCLUDE.

Exampl e t ext Output on the screen. This includes file and directory names and their paths,messages, names of variables and parameters, source text, and names of

installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace these words andcharacters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.


6/89


Table of Contents

Supplier Invoice Processing .................................................................................................. 7

Supplier Invoice ................................................................................................................. 8

Invoicing In ..................................................................................................................... 9

Cancel Supplier Invoice ............................................................................................10

Change Supplier Invoice ...........................................................................................15

Create Supplier Invoice .............................................................................................21

Maintain Supplier Invoice ..........................................................................................23

Release Supplier Invoice ..........................................................................................24

Invoicing Out ................................................................................................................ 26

Confirm Supplier Invoice ...........................................................................................27

Notify of Supplier Invoice .......................................................................................... 30

Notify of Supplier Invoice Contract Release ...............................................................35

Manage Supplier Invoice In .......................................................................................... 36


Read Supplier Invoice ...............................................................................................39

Query Supplier Invoice In ............................................................................................. 41

Find Supplier Invoice by Elements ............................................................................42

Supplier Invoicing In ..................................................................................................... 44

Cancel Supplier Invoice ............................................................................................45

Create Invoice .......................................................................................................... 49

Create Invoice V1 ..................................................................................................... 60


Maintain Supplier Invoice ..........................................................................................68

Supplier Invoicing Out ..................................................................................................76

Confirm Invoice ......................................................................................................... 77

Confirm Invoice Cancellation.....................................................................................83

Transportation Processing In ........................................................................................85

Cancel Supplier Invoice based on Supplier Freight Invoice Request Cancel Request 86

Maintain Supplier Invoice based on Supplier Freight Invoice Request Request .......... 87

Transportation Processing Out .....................................................................................88

Confirm Supplier Freight Invoice Request ................................................................. 89


7/89


Supplier Invoice Processing

The Supplier Invoice Processing handles business documents stating the recipient’s (usuallythe purchaser’s) obligation to pay the supplier for goods received or services rendered.

Technical DataEntity Type Process Component

Software Component Version ESM ERP 606

Technical Name [External] SupplierInvoiceProcessing

Namespace [External] http://sap.com/xi/ESM/ERP

Business Context and Use

The Supplier Invoice Processing process component enables the provision of applicationsthat a customer can use to create, change, cancel or release an invoice.

Notes on SAP Implementation

Prerequisites

To use the operations contained in this process component, you must run the SAP ERPMaterials Management (MM) application component.

Author izat ion

The XI user of the communication channel needs sufficient authorization to execute the actionfor the invoice. The authorization object, M_RECH_WRK, is checked. The Activity field mustcontain the value 01 (Authorization to create invoices in certain plants).


8/89


Supplier Invoice

A recipient’s (usually the purchaser’s) obligation to pay the supplier for goods received orservices rendered.

Technical Data

Entity Type Business Object


Technical Name [External] SupplierInvoice

Object Category Business Process Object


A customer is interested in creating a supplier invoice after sales and distribution. The

supplier invoice is a document that states the invoiced customer's obligations to the supplier.The supplier invoice includes information such as invoice amount, customer details, supplierdetails, and payment terms.


To be able to use the operations in this business object, you must have implemented theMaterials Management (MM) application component.


9/89


Invoicing In

Technical Data

Entity Type Service Interface

Category [External] SAP A2A

Direction [External] inbound


10/89


Cancel Supplier Invoice

To cancel an incoming supplier invoice.

Technical Data

Entity Type Service Operation

Software Component Version SAP APPL 6.06

Release State [External] released

Technical Name [External] InvoiceERPCancelRequest_In

Namespace [External] http://sap.com/xi/APPL/Global2

Application Component [External] MM-IV-GF-ES



Mode [External] asynchronous

Idempotency [External] not applicable

Change/Update Behavior [External] not applicable

P2P Communication Enabled [External] no


This inbound operation is used to cancel an incoming invoice.

Release State

Released.

Released With Restrictions

Not Applicable

Related Operations

I nvoi ceERPConf i r mat i on_Out to confirm the cancellation of an invoice.

I nvoi ceERPRequest _I n to create an incoming invoice.

Features

It is necessary to support the invoicing of agencies that deal with sources of energy like gas.Invoices are created by a partner, for example, and sent to the ERP system. These invoicesneed a reference to a trading contract that contains the relevant data such as organizationaldata, vendor/customer, quantities, and prices. Therefore, the create invoice message wasenhanced with a node called Tr adi ngOr der Ref erence, on item level. In the back end, anagency business billing document of type Single Settlement Request is created, and eachitem is assigned to the matching trading contract item. This trading contract must have usecase 13 (Trading Contract Settlement (Energy)). If not, the invoice or the single settlementrequest is not assigned.

If an invoice such as this needs to be canceled, the operation Cancel Request is used. For Agency Business, the following logic is implemented:


11/89


The first step is to check whether the single settlement request can be set to‘Completed’. If this is possible (that is, if there is no posting to account), then a noreversal document is created, and the confirmation message only contains theheader data of the canceled invoice with the single settlement ID in the componentBi l l ToI D, as well as in the component Cancel l edI nvoi ceI D.

If this is not possible because a posting to account has already been made, areversal document is created. The confirmation message contains header data anditem data, with the ID of the reversal document in the element.

Cancel l edI nvoi ceI D, and the ID of the canceled single settlement request in the elementBi l l ToI D, Cancel l at i onI nvoi ceI ndi cat or is also set to true.

Technical Features

This process requires the software layers SAP_APPL and EA-GLTRADE because the tradingorder is only available in EA-GLTRADE. A new inbound framework was implemented tohandle the single settlement request that results from the invoice message, with new mappingand a proxy call, as well as the trading order reference with use case 13. This inboundframework is only used with EhP6. In the first step, it is determined whether the incominginvoice is a standard invoice or an agency invoice. In correspondence with the proxy nameand the use case, the new mapping and application process for agency invoice is called.Without the EhP6 switch, the standard invoice processing is called.

Prerequisites

You must implement the application component Agency Business so that you can use theoperation

For the trading order references, the software layer EA-GLTRADE should be implemented.

Intergration

This inbound operation belongs to the Suppl i er I nvoi ci ngI n inbound service interface.

Error Handling

The Cancel Invoice message uses Forward Error Handling (FEH).

Error messages that occur during inbound data mapping SAP_APPL are assigned to thefollowing error categories (new message class):

Error Category Error Message

Value NameMessageClass

MessageNumber

Message Text

PRE.TEE

Temporaryerror

W_WLF_SE 009 BAdI &1 is not implemented. Atleast the default impl. must exist.

W_WLF_SE 011BAdI &1 has multipleimplementations.

W_WLF_SE 016Invoice &1 could not be canceled,no further information available.

Error messages that occur during mapping, but are not listed here, are assigned to the errorcategory DCE (determination and conversion error ) by default.

Error messages of the application are assigned to the following error categories:


Value Name Message Class Messag Message Text


12/89


eNumber

PRE.AUE Authorization Error

WS 034

&: no authorizationfor this in pur. org &pur. group & in salesarea

WS 072No authorization to& billing document &(&)

WS 073

No authorization to& billing documenttype & (&) incompany code &

WS 366

No authorization fordocuments fordocument type &(see long text)

WS 367No authorization fordocuments for org.units (see long text)

WS 713 No authorization

WB2_SE_INVC_AGENCY

001

You are notauthorized fortransactionWZR2/WZR3/WZR4

PRE.TEE.LRE

LockRequest

Error

WS 031Document & iscurrently being

processed

MC 601Object requested iscurrently locked byuser &

MC 602The requestedobject is locked byanother transaction

MC 604Own lock is nolonger set for objectrequested

Error messages that occur in the application, but are not listed here, are assigned to the errorcategory PRE (processing error ) by default.

Within the postprocessing office, the Cancel Invoice operation is related to the businessprocess INVC001 of component CA-SOA-ESM-ERP-PUR.

During the cancellation of an invoice with a Cancel Invoice message, there can be twospecific situations:

If the single settlement request that should be canceled by the Cancel Request message is already set to ‘Completed’, only a confirmation with the correspondingdata is sent out, without throwing an error message.

If a reversal document for the single settlement request that should be canceled

already exists, FEH is triggered with an error message of category Conflict, and onlythe action Discard is allowed in the postprocessing office.


13/89


Constraints

The invoice cancel request message only supports billing type Single Settlement Request (BUS 2100002).


Configuration

The generated proxy in the SAP ERP back-end system is the ABAP interfaceII_IVE_E_INVOICEERPCNCRQ, which is implemented in the classCL_IVE_E_INVOICEERPCNCRQ.

The proxy data type IVE_INVOICE_ERPCANCEL_REQUEST is used in the SAPERP system for the incoming request message.

A new inbound framework in SAP_APPL, package WZRE_XI_PROXY, whichcontains the class CL_WLF_INVC_IN_FRAMEWORK, is used for implementation ofthe specific inbound mapping, the proxy call, and the outbound mapping for theconfirmation message.

The implementation of the mapping steps is located in EA-GLTRADE, packageWB2_SE_XI_PROXY, class CL_WLF_INVC_CNC_MAP_IN_13_A2A.

The implementation of the application processing is located in EA-GLTRADE,package WB2_SE_XI_PROXY, class CL_WLF_INVC_CNC_APPL_PROC_13.

B2B and A2A related information: As an example, an SAP ERP back-end system and

a third-party system are involved in sending and receiving invoice request messages.

Enhancements

Business Add-Ins in SAP_APPL

WLF_SE_INVC_ERP_CNC_IN

The WLF_SE_INVC_ERP_CNC_IN (package WZRE_XI_PROXY) Business Add-In isavailable. This internal Business Add-In offers the BAdI interfaceIF_WLF_SE_INVC_ERP_CNC_IN with the operations INBOUND_PROCESSING andOUTBOUND_PROCESSING:

The INBOUND_PROCESSING operation is called during the inbound data mapping,and can be used for enhancements related to the invoice request message. Importparameters are IVE_INVC_ERPCANC_REQ_MSG, containing the data from theinvoice request message, and a message containerCL_BS_SOA_MESSAGE_CONTAINER. The changing parameter is

WLF_INVC_API_IN_SSR, corresponding to the API structure of single settlementrequest.

The OUTBOUND_PROCESSING operation is called during the outbound datamapping for the confirmation message, and can be used for enhancements related tothe invoice request message. Import parameters are WLF_INVC_API_OUT,containing the data from the back end, and a message containerCL_BS_SOA_MESSAGE_CONTAINER. The changing parameter isIVE_E_INVC_ERPCONF_MSG.

The SKIP_CONFIRMATION operation is called during the initialization of the inboundprocess, and can be used to prevent the system sending a confirmation back to theservice caller, if the changing parameter CV_SKIP_CONFIRMATION has the value

true. An implementation of this operation is needed if the request is executed on theWS-RM (Web Services Reliable Messaging) protocol, and there is no counterpartinbound operation available for the outgoing confirmation service operation.


14/89


WLF_SE_INVC_CANCEL_SWITCH

The WLF_SE_INVC_CANCEL_SWITCH (package WZRE_XI_PROXY) Business Add-In isavailable. This internal Business Add-In offers the BAdI interfaceIF_WLF_SE_INVC_CANCEL_SWITCH, with the operationSET_CANCELLATION_INDICATOR. This can be used by the customer to provide his or her

own logic for the cancellation of an invoice:

The INBOUND_PROCESSING operation has the import parameter KOMLFK, whichcontains the header data of an invoice and the exportWZRE_SSR_CANCEL_INDICATOR.

Service Mapping Tool (Transaction SMT)

The service mapping tool (transaction SMT) was used to create the new mapping of anincoming cancel invoice request. It offers another possibility to enhance the inbound mapping.

To enhance the mapping of the invoice request out message, select the applicationWLF_IVE_E_INVOICEERPCNCRQ as the entry point.

Mapping steps:

HEADER: General mapping for header data

More Information

For more information, see Supplier Invoice Processing [Page 1].


15/89


Change Supplier Invoice

To change the data in a supplier invoice.

Technical Data




Technical Name [External] InvoiceERPChangeRequest_In







Change/Update Behavior [External] Type3 [External]



The Change Supplier Invoice inbound operation is used to change the data in an invoice. Youcan only change parked and held invoices.

Parking means that a document has been entered and saved in the system, but no postingshave yet been performed. Parked documents can be changed using this inbound operation(for example, by adding or correcting data) as often as requested.

Related Operations

The Create Supplier Invoice [Page 37] operation enables the creation of anincoming invoice.

The Cancel Supplier Invoice [External] operation enables the cancellation of acreated invoice.

The Release Supplier Invoice [Page 24] operation enables the releasing of a createdinvoice for payment.

Features

The Change Supplier Invoice inbound operation changes the data in a parked or held supplierinvoice.

This inbound operation processes the following message type:

InvoiceERPChange Request

This inbound operation uses the following BAPIs:


16/89


BAPI_INCOMINGINVOICE_GETDETAIL

BAPI_INCOMINGINVOICE_CHANGE

Header Data

You must enter the following values:

BillToID: InvoiceID

TypeCode: You can select one of the following values:

o 004 – Invoice

o 005 – CreditMemo

Price: GrossAmount > CurrencyCode

The following values are optional:

ReconciliationPeriodCounterValue

CancellationInvoiceIndicator

AcceptanceStatusCode

Name

Score

BuyerParty

SellerParty

ServicePerformerParty

RequestorParty

Product Recepient Party

PayerParty

ManufacturerParty

CarrierParty

EmployeeResponsibleParty

ShipToLocation

ShipFromLocation

DeliveryTerms

Attachment

ConfirmedDescription

Note the following conditions and constraints:

BillToID: (ID of the incoming invoice). The first four characters are the fiscal year, andthe next ten are the document number.


17/89


Description: In the header text of the invoice, you can enter up to 50 characters.

BillFromParty: You can enter the following values:

o InternalID

o Addresso TaxID

BillToParty > BillToID: ID of the invoice recipient.

VendorParty: You can enter the following values:

o TaxID

o Address

CashDiscountTerms: You can enter the following values:

o Code

o BaslineDate

o MaximumCashDiscount > DaysValue

o MaximumCashDiscount > Percent

o NormalCashDiscount > DaysValue

o NormalCashDiscount > Percent

o FullPaymentDueDaysValue

PaymentForm: You can enter the following values:

o PaymentFormCode

DeliveryTerms: You can enter the following values:

o Incoterms > Classification Code

o Description

Price: You can enter the following value:

o GrossAmount > Currency Code

PayerParty: You can enter the following value:

o InternalID

ProductTax: You can enter the following values:

o TaxRate

o TaxRateTypeCode

o TaxAmount

o TaxBaseAmount

o TaxCode


18/89


When you enter the Item List Complete Transmission Indicator , the last image isexpected. The missing lines of the item-related tables are deleted in the database.

Item

You must enter the following values:

BillToID

TypeCode: You can select one of the following values:

o 002 – InvoiceItem

o 003 – CreditMemoItem

o 004 – DeliveryCostItem

o 005 – SubsequentDebitItem

o 006 – SubsequentCreditItem

o 007 – UnplannedDeliveryCost

The following values are optional:

HierarchyRelationship

DeliveryPeriod

Product

ProductCategory

BuyerParty

SellerParty


RequestorParty

ProductRecepientParty

ManufacturerParty

ShipToLocation

ShipFromLocation

DeliveryTerms

SalesOrderReference

DeliveryReference

PurchasingContractReference

SalesContractReference

BuyerProductCatalogueReference

SellerProductCatalogueReference


19/89


AttachmentFolder



Price: You can enter the following value:

o GrossAmount (Price Component > Rate > Base Measure, Price component >Rate > Base Measure Unit Code)

ProductTax: You can enter the following value:

o TypeCode

PurchaseOrderReference and all other references: You can enter the followingvalues:

o ID

o Item ID

OriginInvoiceReference: You can enter the following values:

o ID. The first four characters are the fiscal year, and the next ten are thedocument number.

o ItemID

ServiceAcknowledgementReference: You can enter the following values:

o ID

o ItemID

AccountingCodingBlockAssignment: You can enter the following values:

o ActionCode. You can enter one of the following values:

01 – Create

02 – Change

06 – No action

o OrdinalNumberValue (must be filled if action code = 02)

o Amount

o Quantity

o ProfitCentreID

o CostCentreID

o FundsManagmentCentreID

o ProjectReference (specify the Project Element Type Code .)

o InternalOrderID

o SalesOrderReference

o FundsManagementFunds


20/89


o FundsManagmentFunctionalAreaID

o GrantID

o AccountingBusinessAreaCode

AccountingCodingBlockAssignment > Account Determination Expense Group Code =G/L Account

VendorParty: You can enter the following value:

o InternalID

Description: For the description of the invoice item, you can enter up to 25 characters.

Message Types

Invoice ERP Change Request


Allowed values for UnitCodes can be taken from the table T006 column ISOCODE ( see alsoIMG > SAP NetWeaver > General settings > Check Units of Measurement > ISO codes).

Allowed values for CurrencyCodes can be taken from the table TCURC column ISOCD (>see also IMG > SAP NetWeaver > General settings > Check Currency Codes).

Allowed values for CountryCodes can be taken from the table T005.

Data is mapped from XI format to backend format using the Mapping Tool WufWuf(transaction wufwuf) under the name IVE_E_INVOICEERPCRTRC_IN

Enhancements

(BAdI) IV_SE_INVOICEERPCHGREQUEST_ASY is available for this operation.

Processing

Business Add-In (BAdI) IV_SE_INVOICEERPCHGREQUEST_ASY is available for thisoperation.

PrerequisitesSupplier Invoice ProcessingProcessing

Processing


PrerequisitesSupplier Invoice ProcessingProcessing

Prerequisites

Supplier Invoice ProcessingProcessing

For more information, see Supplier Invoice Processing [Page 1] .

Processing


More Information



21/89


Create Supplier Invoice

To create a supplier invoice.

Technical Data




Technical Name [External] InvoiceERPRequest_In










The Create Supplier Invoice inbound operation is used to create an incoming invoice.

Release State

Released.

Released with Restrictions

Not Applicable

Related Operations

to confirm the creation of an invoice.

Error Handling

The Create Invoice message uses Forward Error Handling (FEH).

Error messages that occur during mapping but are not listed here are assigned to the errorcategory DCE (Determination & Conversion Error) by default.

Message Types

InvoiceERPRequest


The generated proxy in the SAP ERP backend system is the ABAP interfaceII_IVE_E_INVOICEERPCRTRQ, which is implemented in the classCL_IVE_E_INVOICEERPCRTRQ.


22/89


The proxy data type IVE_E_INVOICE_ERP_REQUEST is used in the SAP ERP system forthe incoming request message.

B2B and A2A related information:

As an example, an SAP ERP backend system and a third-party system are involved in

sending and receiving invoice request messages.

More Information



23/89


Maintain Supplier Invoice

A request to create or change a supplier invoice.

Technical Data



Release State [External]

Technical Name [External] MaintainSupplierInvoice





P2P Communication Enabled [External] yes

Please note: This item is not available on your system. This may be because it is not part of

your license scope, or because it has not been installed.


24/89


Release Supplier Invoice

To release a supplier invoice for payment.

Technical Data




Technical Name [External] InvoiceERPReleaseRequest_In










The Release Supplier Invoice inbound operation is used to release an incoming invoice forpayment. Releasing an incoming invoice is neccesary if the invoice has been blocked forpayment within invoice verification (automatically or manually). Payment can be performedonce the invoice has been released.

Related Operations

The Create Supplier Invoice [Page 37] operation enables the creation of anincoming invoice.

The Change Supplier Invoice [Page 15] operation enables the alteration of a parkedinvoice.

The Cancel Supplier Invoice [External] operation enables the cancellation of anincoming supplier invoice.

Features

The Release Supplier Invoice inbound operation releases a blocked or held invoice forpayment.

This inbound operation processes the following message type:

InvoiceERPReleaseRequest

To release a blocked or held invoice you must enter the following values:

BillToID: ID of the invoice


25/89


InvoiceReleaseDiscountDateShiftIndicator


BillToID: (ID of the incoming invoice). The first four characters are the fiscal year, andthe next ten are the document number.

InvoiceReleaseDiscountDateShiftIndicator indicates that the cash discount days inthe invoice are moved to the vendor line item of the accounting document when yourelease the invoice.

The proxy implementation calls the CANC_REL of classCL_IVE_E_P2P_INVOIC_EXECUTE_IN. After the mapping and the BAdI are processed, theBAPI BAPI_INCOMINGINVOICE_RELEASE is called.

Message Types

Invoice ERP Release Request

Notes on SAP ImplementationEnhancements

Business Add-In (BAdI) IV_SE_INVOICEERPRELREQUEST_ASY is available for thisoperation.

More Information



26/89


Invoicing Out

Technical Data



Direction [External] outbound


27/89


Confirm Supplier Invoice

To confirm an invoice received from a supplier.

Technical Data




Technical Name [External] InvoiceERPConfirmation_Out









The new version of the Confirm Invoice outbound operation is used to confirm the creation,the change or the cancellation of an incoming invoice.

Within Agency Business solution, this Confirm Invoice operation is available also for agenciesthat deal with energies (power and gas). Other use cases than power and gas in AgencyBusiness are not yet supported. Also the former versions of this new operation do not support Agency Business at all.

Related Operations

InvoiceERPRequest_In_V1 to create or change an incoming invoice.

InvoiceERPCancelRequest_In to cancel an invoice.

InvoiceERPConfirmation_Out to be replaced by this new operation.

Features

Invoices are created or changed, for example by a partner solution and send to an ERPsystem. For energy settlement in Agency Business, these invoices need a reference to atrading contract that contains the quantities, delivery conditions and prices on a daily basis.Therefore, the invoice message was enhanced by a node TradingOrderReference on itemlevel.

After the successful creation or change (or cancellation), a positive confirmation is send outthat contains the invoice data of the single settlement request, which was created or changedby the request. If the creation, change or cancellation fails, a negative confirmation,containing the data of the request message, is send out. Therefore, the confirmation messagewas also enhanced by a node TradingOrderReference on item level.


28/89


Technical features: This process requires the software layers SAP_APPL and EA-GLTRADEbecause the trading order is only available in EA-GLTRADE.

Message Types

Invoice ERP Confirmation

Prerequisites

You must implement the application component Agency Business so that you can use theoperation.

For the trading order references, the software layer EA-GLTRADE, respectively the GlobalTrade Management component has to be implemented.

Integration

This outbound operation belongs to the Invoicing Out outbound service interface.

Error HandlingMapping errors of the confirmation message are caught before sending the message out.Errors that occurred when trying to send the message out and the state of the message areshown and can be analyzed by selecting the trace feature of the integration engine monitorvia transaction SXMB_MONI.

If a negative confirmation has to be sent out, the errors that occurred during the processing ofthe corresponding request messages are mapped to the log parameter of the confirmationmessage.

Prerequisites

For the trading order references, implement the software layer EA-GLTRADE.


The generated proxy in the SAP ERP back-end system is the ABAP interfaceCO_IVE_INVOICEERPCF1.

The following proxy data type is used in the SAP ERP system for the outgoing confirmationmessage: IVE_INVOICE_ERPCONFIRMATION_V1.

A new inbound framework in SAP_APPL, package WZRE_XI_PROXY containing the classCL_WLF_INVC_IN_FRAMEWORK is used to handle the incoming service request for AgencyBusiness documents. This framework controls the call of the concrete inbound mapping, theback end application function, the outbound mapping and the send out of the confirmation

message, as well as error handling capabilities.

The implementation of the mapping steps for inbound and outbound data mapping is locatedin EA-GLTRADE, package WB2_SE_XI_PROXY. The classCL_WLF_INVC_COCRT_MAP_O_13_A2A contains the outbound data mapping.

B2B and A2A related information: As an example, an SAP ERP back-end system and a third-party system, are involved to send and receive invoice request messages.

Enhancements

Business Add-Ins in SAP_APPL

WLF_SE_INVC_ERP_RQ_IN: The WLF_SE_INVC_ERP_RQ_IN (package

WZRE_XI_PROXY) Business Add-In is available. This external Business Add-In offers the


29/89


BAdI interface IF_WLF_SE_INVC_ERP_RQ_IN with the operationOUTBOUND_PROCESSING_V1:

The OUTBOUND_PROCESSING_V1 operation is called during the outbound data mappingfor the confirmation message and can be used for enhancements relating to the invoicerequest message. Import parameters are WLF_INVC_API_OUT, containing the data from the

back end and a message container CL_BS_SOA_MESSAGE_CONTAINER. Changingparameter is of type SAPPLCO_INVC_ERPCF1_MSG.

Service Mapping Tool (Transaction SMT)

The service mapping tool (transaction SMT) was used to create the new mapping of anincoming invoice request to a single settlement request in the back end. It offers anotherpossibility to enhance the outbound data mapping.

To enhance the mapping of the invoice request out message, the applicationWLF_IVE_E_INVOICEERPCO_V1 has to be selected as entry point.

Mapping steps:

HEADER DATA: General mapping for header data

HEADER_PARTY: Mapping of parties on header level

HEADER_ADDRESS_DATA: Mapping of address data on header level

HEADER_CANCELLATION_INFO: Provide header cancellation information

HEADER_ PRODUCT _TAX: Mapping of header taxes

HEADER_TEXTS: Mapping of header texts

ITEM_COND: Mapping of conditions on item level

ITEM_DATA: General mapping for item data

ITEM_REF: Mapping of references on item level

ITEM_ TEXTS: Mapping of item texts

ITEM_TAX: Mapping of item tax data


30/89


Notify of Suppl ier Invoice

To send a notification about the receipt of a supplier invoice.

Technical Data




Notes on Release State

Technical Name [External] InvoiceNotification_Out








P2P Communication Enabled [External] yes


The Notify of Supplier Invoice A2A outbound operation ( Supplier Invoice business object)serves as a response to the invoicing party when a supplier invoice is received (eventPOSTED for BOR object BUS2081). Event POSTED is triggered by service operation CreateInvoice [Page 49] , Create Supplier Invoice [Page 37] or by online postings of incominginvoices (e.g. transaction MIRO). The Notify of Supplier Invoice operation contains dataextracted from the Create Supplier Invoice [Page 37] operation. The message is sent as an A2A message.

Features

This outbound operation notifies the invoicing party about the receipt of a supplier invoice and

processes the following message type:

InvoiceNotification

This message is sent when an invoice is received (event POSTED for BOR object BUS2081).Event linkage must be activated to enable this. The message is sent as an A2A message.

Header Data

The message supplies the following values:

ID: ID of the customer invoice

BillToID: ID

TypeCode: Value 004 (Invoice) or 005 (CreditMemo)


31/89


TransactionDate

BillToParty > BillToID: ID of the invoice recipient.

BillFromParty > BillToID: ID of the invoicing party

CancellationInvoiceIndicator

AcceptanceStatusCode

The following values are not supplied:

ReconciliationPeriodCounterValue

DateTime

Name

Note


RequestorParty


VendorParty

PayeeParty

ManufacturerParty

CarrierParty

EmployeeResponsibleParty

DeliveryTerms

ProductTax

Attachment


ShipToLocation

ShipFromLocation


Bill From Party: The following values are supplied:

o InternalID

o BillToID

o TaxID

o Address

BillToID (ID of the incoming invoice). The first four characters are the fiscal year, andthe next ten are the document number.


32/89


CashDiscountTerms: The following values are supplied:

o Code

o BaslineDate

o MaximumCashDiscount > DaysValue

o MaximumCashDiscount > Percent

o NormalCashDiscount > DaysValue

o NormalCashDiscount > Percent

o FullPaymentDueDaysValue

PaymentForm: The following value is supplied:

o PaymentFormCode

Price: The following value is supplied:

o GrossAmount

PayeeParty: One of the following values is supplied:

o InternalID

o BillToID

Item

The following values are supplied:

ID – ItemID of the incoming invoice.

BillToID

TypeCode

The following values are not supplied:

HierarchyRelationship

DeliveryPeriod

Product

ProductCategory


RequestorParty


VendorParty

ManufacturerParty

ShipToLocation

ShipFromLocation


33/89


SalesOrderReference

PurchasingContractReference

SalesContractReference

BuyerProductCatalogueReference

SellerProductCatalogueReference

Attachment

Description



TypeCode: One of the following values is supplied:

o 002 – InvoiceItem

o 003 – CreditMemoItem

o 004 – DeliveryCostItem

o 005 – SubsequentDebitItem

o 006 – SubsequentCreditItem

o 007 – UnplannedDeliveryCost

Price: The following value is supplied:

o GrossAmount > CurrencyCode

Product Tax: The following value is supplied:

o TypeCode

Purchase Order Reference: The following value is supplied:

o ID

o ItemID

Origin Invoice Reference: The following value is supplied:

o ID. The first four characters are the fiscal year, and the next ten are thedocument number.

o ItemID

Service Acknowledgement Reference: The following values are supplied:

o ID

o ItemID

Accounting Coding Block Assignment: The following values are supplied:

o ActionCode


34/89


o OrdinalNumberValue

o Amount

o Quantity

o ProfitCentreID

o CostCentreID

o FundsManagmentCentreID

o ProjectReference (specify the ProjectElementTypeCode .)

o InternalOrderID

o SalesOrderReference

o FundsManagementFunds

o FundsManagmentFunctionalAreaID

o GrantID

o AccountingBusinessAreaCode

o AccountingCodingBlockAssignment > Account Determination Expense GroupCode = G/L Account

Description: The description of the invoice item can contain up to 50 characters.

Message Types

Invoice Notification

Prerequisites

Event linkage must be activated to enable this.


When the supplier (vendor) invoice is saved as posted (not parked), the event linkage (eventPOSTED for BOR object BUS2081) causes workflow to call the methodPROCESS_BY_WORKFLOW of the class CL_SE_IV_INVOICENOTIFICATION. The methodimports the document number and fiscal year of the invoice. Then the document is read,mapped out and the notification service is called within the same class. Event linkage must beactivated to enable this.

Data is mapped from backend format to XI format using the Mapping Tool WufWuf(transaction wufwuf) under the name IVE_E_INVOICE_NOTIFICATION_OUT.

Enhancements

Business Add-In (BAdI) IV_SE_INVOICENOTIFICATION_ASYN is available for this outboundoperation.

More Information



35/89


Notify of Suppl ier Invoice Contract Release

Technical Data




Technical Name [External]SupplierInvoiceSUITEContractReleaseNotification_Out


Application Component [External] MM-PUR-GF-ES





P2P Communication Enabled [External]

yes

Message Types

Supplier Invoice SUITE Contract Release Notification


36/89


Manage Supplier Invoice In

Technical Data


Category [External] A2X



37/89


Create Supplier Invoice

To create a supplier invoice.

Technical Data




Technical Name [External]SupplierInvoiceERPCreateRequestConfirmation_In



Web Service Definition (Back End) ECC_SUPLRINVCERPCRTRC


Mode [External] synchronous

Idempotency [External] no



true

Features

This service operation creates a supplier invoice in the back-end system. Once created asupplier invoice can be posted, parked, parked and completed, or entered and held. It ispossible to create a supplier invoice with reference to a purchase order, goods movement, orservice acknowledgement. Furthermore, it is possible to create a supplier invoice with G/Laccount lines and material lines.

Error Handling

The Log in the response message contains messages and errors.

Message Types

SupplierInvoiceERPCreateConfirmation_sync

SupplierInvoiceERPCreateRequest_sync

Constraints

The service operation does not support the following functions:

Supplier invoice with amount split

Supplier invoice for CpD supplier

Supplier invoice with alternative payee

Supplier invoice with both invoice and credit items


38/89



Configuration

The behavior of the service operation in general depends on the Customizing settingsfor Invoice Verification (MM-IV).

Allowed values for unit codes (for example Item-Quantity-unitCode) can be takenfrom the table T006 column ISOCODE. For more information see Customizing forSAP NetWeaver under General settings -> Check Units of Measurement -> ISOCodes.

Allowed values for currency codes (for example Item-PriceCalculation-NetAmount-currencyCode) can be taken from the table TCURC column ISOCD. For moreinformation, see Customizing for SAP NetWeaver -> General settings -> CheckCurrency Codes.

Enhancements

The Business Add-In (BAdI) IVE_SE_SUPLRINVCERPCRTRC is available for this service

operation.


39/89


Read Supplier Invoice

Query to and response from Supplier Invoice Processing [Page 1] to read a supplier invoice.

Technical Data




Technical Name [External] SupplierInvoiceERPByIDQueryResponse_In



Web Service Definition (Back End) ECC_SupplierInvoiceERPByIDQR





P2P Communication Enabled [External] true


An accounts payable clerk can use this inbound service operation to read the header anditem data of a supplier invoice.

Features

This inbound service operation returns exactly one supplier invoice based on the specifiedsupplier invoice ID and fiscal year, if one exists. This inbound service operation returns all theheader and item data of the supplier invoice.

To return a supplier invoice, the following information is required in theSupplierInvoiceERPByIDQuery_sync [External] message type:

The supplier invoice ID (SupplierInvoiceID element)

The fiscal year (Year element)

Error Handling

If errors occur, the process is terminated and the corresponding messages are sent back tothe user.

Message Types

SupplierInvoiceERPByIDQuery_sync

SupplierInvoiceERPByIDResponse_sync


40/89



This operation uses the BAPI "BAPI_INCOMINGINVOICE_GETDETAIL".

Technical Name: SupplierInvoiceERPByIDQueryResponse_In

Web Service Definition: ECC_SupplierInvoiceERPByIDQR.

Constraints

The output node SUPPLIER_INVOICE->PRICE_CALCULATION->EXCHANGE_RATE is notreturned.

Enhancements

The Business Add-In (BAdI) IVE_SE_SUPPLINVOIERPBYIDQR is available for thisoperation.

Enhancements

The Business Add-In (BAdI) IVE_SE_SUPPLINVOIERPBYIDQR is available for this

operation.


41/89


Query Suppl ier Invoice In

Technical Data


Category [External] A2X



42/89


Find Supplier Invoice by Elements

To send a query to and receive a response from Supplier Invoice Processing [Page 1] to findsupplier invoice.

Technical DataEntity Type Service Operation

Software Component Version ESA ECC-SE 605


Technical Name [External] SupplierInvoiceERPByElementsQueryResponse_In

Namespace [External] http://sap.com/xi/APPL/SE/Global

Application Component [External] MM-IV

Web Service Definition (Back End) ECC_SupplierInvoiceERPByELQR






true


An accounts payable clerk can use this inbound service operation to find supplier invoices byentering specific search criteria.

Features

This inbound service operation returns all the supplier invoices that meet the given searchcriteria. Only the header data of each found supplier invoice is returned for performancereasons. You do not have to specfiy selection values to use this operation, but forperformance reasons, it is recommended that you restrict the selection. You can restrictselection by:

Vendor party

Posting date

Document creation date

Completeness and validation status

Purchase order ID

You can limit the number of returned supplier invoices by entering a value in theQueryHitsMaximumNumberValue element in the ProcessingConditions data type. TheProcessingConditions data type also contains the LastReturnedObjectID element, whichallows you to return all found supplier invoices starting from a specific object ID. Thisobject ID has a special format to identify a supplier invoice (supplier invoice ID followed by thefiscal year) and is also returned in the ProcesingConditions data type of this operation. For


43/89


example, the first time you use this inbound service operation, you want to read the first 100supplier invoices. The next time you use it, you want to read the next 100 supplier invoicesonly. So, you take the value that was returned in the LastReturnedObjectID element from thefirst read and enter it in the LastReturnedObjectID element for the second read.

Error Handling

If errors occur, the process is terminated and the corresponding messages are sent back tothe user.

Message Types

SupplierInvoiceERPByElementsQuery_sync

SupplierInvoiceERPByElementsResponse_sync


This operation uses the BAPI "BAPI_INCOMINGINVOICE_GETLIST".

Technical Name: SupplierInvoiceERPByElementsQueryResponse_In

Web Service Definition: ECC_SupplierInvoiceERPByELQR.

Enhancements

The Business Add-In (BAdI) IVE_SE_SUPPLINVOICEERPBYELQR is available for thisoperation.


44/89


Supplier Invoicing In

The inbound service interface Invoicing In contains an operation that creates a supplierinvoice on the basis of legally binding requests for payment from the supplier for goodsdelivered or services rendered.

Technical Data


Category [External] B2B



45/89


Cancel Supplier Invoice

Request sent from the Customer Invoice Processing at Supplier process component to theSupplier Invoice Processing process component to cancel a supplier invoice during an

agency business process. Agency business processes are transactions between third parties

in which an enterprise offers the parties involved specific advantages or services (such asbrokerage, del credere business, centralized regulation transactions). The enterprise is notdirectly involved in the contract of the business partners, or plays only a supporting role.

Example:

A vendor sells goods or services to a customer. Both business partners and an agencyhave signed a contract stating that the agency will handle payment and that the agency willreceive commission for providing this service.

Technical Data


Software Component Version EA-RETAIL 606


Technical Name [External] InvoiceCancellationRequest_In

Namespace [External] http://sap.com/xi/EA-RETAIL/Global2

Application Component [External] LO-AB








In general, the Cancel Supplier Invoice inbound operation enables communication betweenan agency (using an SAP system) and a partner of the agency (using an external system). An

incoming invoice created externally by the partner is entered into the SAP system used by theagency and can also be cancelled externally.

This operation creates a request to cancel a supplier invoice during an agency businessprocess.

The operation allows you to cancel an agency invoice that has not yet been released toaccounting, so that no further follow-on documents are created.

Related Operations

The counterpart to this asynchronous inbound operation is the Confirm Invoice Cancellation outbound operation.

In case of error, the Confirm Invoice Cancellation operation sends a confirmation in which thedata of the InvoiceCancellationRequest message are directly forwarded to theInvoiceCancellationConfirmation message without converting the data.


46/89


Features

The service operation is used to cancel an agency invoice that has not yet been released toaccounting. The relevant agency invoice must have been created using the Create Invoice

service operation and must have been entered as single settlement request. A singlesettlement request is a settlement document in agency business used to enter a single

incoming invoice. The special feature of this document is that a preceding document does nothave to exist in the system before the document can be created, yet it can still be used tocreate follow-on documents.

The following is a list of elements that are either supported but with restrictions, or notsupported at all. This list is not exhaustive.

Invoice BillToID: attributes of this element are not considered

Invoice DateTime: optional attributes of this element are not evaluated

Invoice BillToParty and Invoice BillFromParty: The following elements are mapped:

o The internal partner number (supplier number or customer number) isinherited from the element BillToID of the relevant party. If this element isinitial, the internal partner number will be inherited from the elementInternalID. However, this only occurs if the attributes of the elementInternalID are initial.

o If a standard ID exists, this one is transferred, provided it is an ILN(International Location Number) or a GLN (Global Location Number). In thecase of ILNs/GLNs the attribute schemeAgencyID of the elementStandardID must have the value '9' (= GS1).If there are several standard IDsmeeting this condition, the first ID will be transferred.

o If neither the internal partner number nor an ILN can be determined, themethod GET_VENDOR or GET_CUSTOMER of BAdI

WLF_SE_PARTNER_FOR_BTDPARTY is called to determine at least one ofthese elements.

Error Handling

Forward Error Handling

The Cancel Supplier Invoice inbound operation supports Forward Error Handling .

Error messages occurring during data mapping are assigned to the following error categories:

PRE.TEE (Temporary Error):

o W_WLF_SE 009: BAdI &1 is not implemented. At least the default impl. mustexist

o W_WLF_SE 011: BAdI &1 has multiple implementations

DCE.VME (Value Mapping Error):

o W_WLF_SE 012: The & could not be mapped

DCE.KME (Key Mapping Error):

o W_WLF_SE 016: Invoice &1 could not be cancelled; no further informationavailable

DCE (Determination & Conversion Error):


47/89


o All other error messages not listed here are assigned to this error category bydefault

Error messages of the application are assigned to the following error categories:

PRE.AUE (Authorization Error):

o WS 034: &: No authorization for this in pur. org & pur. group & in sales area &

o WS 072: No authorization to & billing document & (&)

o WS 073: No authorization to & billing document type & (&) in company code

o WS 366: No authorization for documents for document type & (see long text)

o WS 367: No authorization for documents for org. units (see long text)

o WS 713: No authorization

PRE.TEE.LRE (Lock Request Error):

o WS 031: Document & is currently being processed

o MC 601: Object requested is currently locked by user &

o MC 602: The requested object is locked by another transaction

o MC 604: Own lock is no longer set for object requested

PRE (Processing Error):

o Error messages occurring in the application that are not listed here areassigned to this error category by default.

In case of error, the Confirm Invoice Cancellation service operation sends a confirmation inwhich the data of the InvoiceCancellationRequest message are directly forwarded to theInvoiceCancellationConfirmation message without converting the data.

Message Types

Invoice Cancellation Request


Data is mapped from XI format to backend format using the Service Mapping Tool (SMT).Mapping procedures are defined in Customizing for Cross-Application Components underProcesses and Tools for Enterprise Applications -> Enterprise Services -> Develop Enterprise

Services -> Create and Edit Mappings -> Create and edit Mappings . The mapping for theCancel Supplier Invoice service operation can be found under the nameCL_WLF_INVOICECNCRQ.

Configuration:

The application component EA-Retail must be activated.

Enhancements:

Enhancements:

The Business Add-In (BAdI) WLF_SE_INVCCNCREQ_ASYN, methodINBOUND_PROCESSING is available to enhance this service operation.

In addition, there are further BAdIs available to determine the internal supplier or customernumber.


48/89


All BAdIs provided in the services environment can be found in Customizing for Logistics - General under Agency Business -> Enterprise SOA -> Business Add-Ins for Enterprise SOA.


49/89


Create Invoice

To create an agency invoice. An agency invoice is created during an agency businessprocess or transaction involving a third party.

Technical DataEntity Type Service Operation



Technical Name [External] InvoiceRequest_In










The Create Invoice B2B inbound operation is used to create an incoming invoice. Anincoming invoice is a document from an invoicing party containing the payments to be madebased on business transactions (e.g. the purchasing of material or service items) performedin purchasing and inventory management. An incoming invoice can be an invoice or a creditmemo. An invoice contains various information, such as:

The invoicing party

The invoice reference number

The tax amount on the invoice items

The invoice reference enables you to clearly allocate the invoice to a business transaction. Ifsuch a reference exists, the system uses "knowledge" that it already has and proposes theappropriate values when verifying the invoice, for example:

Agreed terms of payment

Quantities to be invoiced

Amounts expected for each item

The Create Invoice B2B inbound operation is a request from the customer invoice processingat supplier process component to the supplier invoice processing process component tocreate an invoice, for example during an agency business process. Agency businessprocesses are transactions between third parties in which an enterprise offers the partyinvolved specific advantages or services (such as brokerage, del credere business,


50/89


centralized regulation transactions). The enterprise is not directly involved in the contract ofthe business partners, or plays only a supporting role.

The Create Invoice B2B inbound operation is similar to the create supplier invoice inboundoperation. One main difference is the coding block (account assignment) that comes with theCreate Supplier Invoice [Page 37] inbound operation. As the Create Invoice service is a B2B

operation, the internal account assignment information is not known to the service consumer.

Example

A supplier sells goods or services to a customer. Both business partners (supplier andbuyer) and an agency have signed a contract stating that the agency will handle payment andthat the agency will receive commission for providing this service. The supplier sends anInvoice Request message to the agency using the Create Invoice B2B inbound operation totrigger invoice creation.

Related Operations

The Confirm Invoice [Page 77] operation is used to inform the invoicing party about thecreation of an agency invoice.

A special feature in the Agency Business is the chargeback process, where a wholesaler canrequest the difference between the price he paid for goods to the supplier and the price hegets from the customer. This difference is based on a special contract between the supplierand the customer.

Related Operations

The Confirm Invoice [Page 77] operation is used to inform the invoicing party about thecreation of an agency invoice.

Features

You create an invoice using this service operation. On header level, the operation includes all

relevant billing information, such as invoicing party and bill-to party, as well as the totalamount of the invoice. Every item contains information about material, price, gross value, netvalue, and tax portion, for example. Once the operation has been processed successfully, anew invoice is created in the back-end system.

The invoice is considered to be an agency invoice (single settlement request) if it is sent tothe agency, and the bill-to party and the agency are not identical. Otherwise the invoice isinterpreted as a standard invoice. A single settlement request is a settlement document inagency business used to enter a single incoming invoice. The special feature of thisdocument is that a preceding document does not have to exist in the system before thedocument can be created, yet it can still be used to create follow-on documents.

If the CancellationInvoiceIndicator is set to true, a reversal invoice is created in the back end.

With the new release (EhP6), it was required to support the chargeback scenario, whichcreates an incoming Agency Business billing document of type Single Settlement Request.The basis of this chargeback scenario is a special contract (condition contract) between asupplier and a customer to sell him goods to a lower price than the normal price. Awholesaler, who handles the orders for the customer, needs to pay the higher price to thesupplier and can request the difference from the supplier by sending him a credit memo. Onthe incoming side, this credit memo is created as a single settlement request in the suppliersystem. This single settlement request has a reference to the condition contract betweensupplier and customer, realized with a new TradePriceSpecificationContractReference nodeon item level. In contrast to a standard incoming invoice, the supplier has the role of the bill toparty and the customer (wholesaler) the role of the bill from party.


51/89


The invoice notification message is also enhanced by references for trading orders,customer rebate agreements and supplier rebate agreements, but the currentimplementation does not support these references.

To differentiate in the back end between standard invoices and billing documents fromchargeback process, a new use case was introduced. When the EhP6 switch is on and theTradePriceSpecificationReference node is filled, the use case for compensation management

is set controls, for example the mapping of the bill to and bill from party.

Without the EhP6 switch, the differentiation between standard invoice and agencyinvoice via BAdI is working as implemented in EhP5.

Technical Features

The chargeback process, in contrast to other agency business processes, requires only the

software layers SAP_APPL and EA-GLTRADE and not the EA-RETAIL layer, where theimplementation of the InvoiceRequest. In is adapted for EhP5. Therefore, the relevant EA-RETAIL objects are down ported to SAP_APPL. A new inbound framework for the serviceimplementation objects was developed to handle the single settlement request resulting fromchargeback process with new mapping and proxy call as well as the already existingimplementation for Agency Business in EA-RETAIL. This inbound framework is only used withEhP6 for Agency Business documents when the use case is of value 20, but it handles alsothe use cases initial and 01 - 04. If a customer has already used SOA services for invoices in Agency Business, the old implementation is used as before.

The existing EA-RETAIL objects (mapping, implementation) support the delivered

EhP5 scope as before and are not replaced by the new implementation.

Within the proxy, the current switch is checked. It is also checked, if the invoice is a standardinvoice or related to Agency Business. If the EhP6 switch is not active, the implementationdone in EhP5 is called. With EhP6 switch, the new inbound framework is called.

The inbound framework includes the following steps (only for EhP6):

Check if a reference to a trade price specification contract is existing: if yes, the usecase for compensation management (chargeback process) and the BOR objectBUS2100002 is set as default.

Call of the inbound mapping for a single settlement request in chargeback process

Call of the corresponding application process

Call of the corresponding outbound mapping for the confirmation

Prerequisites

You must implement the application component Agency Business and CompensationManagement so that you can use the operation.

For all other Agency Business processes, the software layer EA-RETAIL should beimplemented.

A billing type for chargeback needs to be defined.

A mapping group shall be defined in the Customizing, containing a default payment type anddefault organizational data like sales and purchase organization. Alternatively, the


52/89


organizational data can be determined from the condition contract. This is already available inEhP5 for EA-RETAIL. In EhP6, this Customizing view is also available in SAP_APPL with thepossibility to migrate existing entries from EA-RETAIL to the new Customizing in SAP_APPL. After migration, the Customizing view in EA-RETAIL can no longer be used.

Integration

This inbound operation belongs to the Supplier Invoicing In inbound service interface.

Error Handling

The Create Invoice message uses forward error handling (FEH).

Error messages occurring during inbound data mapping EA-RETAIL are assigned tothe following error categories:


Value NameMessageClass

Message

Number

Message Text

PRE.TEE

Temporar y error

W_WLF_SE

006No entry in in table TMZR_PRX_GRP ismarked as default for invoices

W_WLF_SE

007No entry in table TMZR_PRX_GRP ismarked as default for credit memos

W_WLF_SE

009BAdI &1 is not implemented. At least thedefault impl. must exist

W_WLF_SE

011 BAdI &1 has multiple implementations

WS 003 Billing doc. type & does not exist

WS 037 Payment type & does not exist

MN 202Error reading company code data(internal error)

DCE.ICEInvalidCall Error

W_WLF_SE

010BTDTypeCode has an initial value. Assign a avalid value.

W_WLF_SE

027Item &1: no OriginInvoiceReference ismaintained

W_WLF_SE

028Item &1: BTDTypeCode &2 or referenceddocument &3 is not supported

W_WLF_SE 035

BTDItemTypeCode has an initial value. Assign a valid value

W_WLF_SE

040PriceSpecificationElementCategoryCode:&1 is not a valid value

W_WLF_SE

041KOAID &1 cannot be mapped toPriceSpecificationElementCategoryCode

W_WLF_SE

042PriceComponentInactivityReasonCode:&1 is not a valid value

W_WLF_SE

043PriceComponentFixationCode: &1 is nota valid value

W_WLF_SE 044

PriceComponentOriginCode: &1 is not avalid value


53/89


W_WLF_SE

045KINAK &1 cannot be mapped toPriceComponentInactivityReasonCode

W_WLF_SE

046KSTEU &1 cannot be mapped toPriceComponentFixationCode

W_WLF_SE 047

KHERK &1 cannot be mapped toPriceComponentOriginCode

W_WLF_SE

048PriceSpecificationBaseCode: &1 is not avalid value

W_WLF_SE

049Calculation type &1 cannot be convertedto PriceSpecificationBaseCode

W_WLF_SE

050ScaleAxisBaseCode: Value &1 (&2) is notsupported

W_WLF_SE

051ScaleAxisBaseCode: &1 is not a validvalue

W_WLF_SE 052

Scale basis indicator &1 cannot beconverted to ScaleAxisBaseCode

W_WLF_SE

053TimePointTypeCode must have value &1;current value: &2

W_WLF_SE

054Neither currency &1 nor &2 match thelocal currency &3 of the document

W_WLF_SE

055Neither currency &1 nor &2 match thecurrency &3 of the document

DCE.VME

ValueMappingError

W_WLF_SE

008Codevalue &1 of BTDTypeCode iscurrently not supported

W_WLF_SE

012 The & could not be mapped

W_WLF_SE

025Mapping &1 fails: text-id is not maintained(billing document type = &2)

W_WLF_SE

026Mapping &1 fails: text-id not maintained(item &2, billing doc type = &3)

W_WLF_SE

029Item &1: ExchangeRate could not bemapped successfully.

W_WLF_SE

030Item &1: Different currencies on headerand item level (&2, &3)

W_WLF_SE

031Item &1: Different exchange rates onheader and item level (&2, &3)

W_WLF_SE

032Item &1: Different dates on header anditem level (&2, &3)

W_WLF_SE

033Item &1: The Product could not bemapped

W_WLF_SE

034Cancellation: Item &1 and Item &2 havedifferent OriginInvoiceId's

W_WLF_SE

036Item &1: Codevalue &2 ofBTDItemTypeCode is currently not

supported.

W_WLF_S 037 Billing category &1 is currently not


54/89


E supported

DCE.KME

KeyMappingError

W_WLF_SE

015Comparison of BillToParty with owncompany identifiers could not be done

DCE.ITE

Internal

TermError

W_WLF_SE 017 Neither currency &1 nor &2 are equal tolocal currency &3

W_WLF_SE

018No sales organization found which isassigned to company code &1

W_WLF_SE

019No sales area which is relevant foragency business found for customer &1

W_WLF_SE

020No purchasing organization found havingcompany code &1 or an initial one

W_WLF_SE

021No purchasing org. data relevant foragency business found for vendor &1

Error messages occurring during inbound data mapping SAP_APPL are assigned tothe following error categories (new message class)


Value Name Message Class

MessageNumber

Message Text

DCE.ICE

InvalidCallError

WZRE_PRX_MAPPING

010BTDTypeCode has an initial value. Assign a avalid value.

WZRE_PRX_MAPPING

027 Item &1: no OriginInvoiceReferenceis maintained

WZRE_PRX_MAPPING

028Item &1: BTDTypeCode &2 orreferenced document &3 is notsupported

WZRE_PRX_MAPPING

035BTDItemTypeCode has an initialvalue. Assign a valid value

WZRE_PRX_MAPPING

040PriceSpecificationElementCategoryCode: &1 is not a valid value

WZRE_PRX_MAPPING

055Neither currency &1 nor &2 matchthe currency &3 of the document

DCE.VME

ValueMapping Error

WZRE_PRX_MAPPING

008Codevalue &1 of BTDTypeCode iscurrently not supported

WZRE_PRX_MAPPING

012 The & could not be mapped

WZRE_PRX_MAPPING

025Mapping &1 fails: text-id is notmaintained (billing document type =&2)

WZRE_PRX_MAPPING

026Mapping &1 fails: text-id notmaintained (item &2, billing doc type

= &3)

WZRE_PRX_MAPPI 029 Item &1: ExchangeRate could not be


55/89


NG mapped successfully.

WZRE_PRX_MAPPING

033Item &1: The Product could not bemapped

WZRE_PRX_MAPPI

NG

036Item &1: Codevalue &2 ofBTDItemTypeCode is currently not

supported.

WZRE_PRX_MAPPING

037Billing category &1 is currently notsupported

DCE.ITE

InternalTermError

WZRE_PRX_MAPPING

017Neither currency &1 nor &2 are equalto local currency &3

WZRE_PRX_MAPPING

021No purchasing org. data relevant foragency business found for vendor &1

Error messages which occur during mapping but which are not listed here are assigned to theerror category DCE (Determination & Conversion Error) by default.

Error messages o f the application are assigned to the following error categories:


Value Name Message ClassMessageNumber

Message Text

PRE.AUEPRE.AUE AuthorizationError

WS 034

&: no authorizationfor this in pur. org& pur. group & insales area

WS 072No authorizationto & billing

document & (&)

WS 073

No authorizationto & billingdocument type &(&) in companycode &

WS 366

No authorizationfor documents fordocument type &(see long text)

WS 367

No authorization

for documents fororg. units (seelong text)

WS 713 No authorization

WB2_SE_INVC_AGENCY

001You are notauthorized fortransaction &1

003

No authorizationto create agencydocument withbilling type &1

005 No authorizationto create agency


56/89


document with orgdata: &1 &2 &3

PRE.TEE.LRE

Lock RequestError

WS 031Document & iscurrently beingprocessed

MC 601Object requestedis currently lockedby user &

MC 602

The requestedobject is locked byanothertransaction

MC 604Own lock is nolonger set forobject requested

WS 032Document &

cannot be blocked

WS 830

Document &cannot be locked(process lock forinvoicing party &)

WS 832

Document &1cannot beunlocked (processlock for payer &2)

01 413

System lockadministration

error. Pleasenotify youradministrator

PREProcessingError

WS 203

Billing doc.category & notsame & of bill.doc. type &

204No billing doc.type passed on

266No invoicerecipient was

transferredError messages which occur in the application but which a

Supplier in Voice Processing

Documents

Transcript of Supplier in Voice Processing