How To Create Vendor Invoice In Sap

Create Supplier Invoice

Definition

The new version of the Create Invoice Inbound V1 operation replaces the previous version Create Invoice Inbound operation (technical name InvoiceRequest_In). This document is related to business processes that store the incoming invoice as a document in the agency business application. It does not cover documents to be stored within the standard invoice verification.

Technical Data

Software Component Version	SAP_APPL 606
Release State	Released
Technical Name	`InvoiceRequest_In_V1`
Namespace	`http://sap.com/xi/APPL/Global2`
Application Component	MM-IV-GF-ES
Related Web Service Definition	Reporting Framework
Category	B2B
Direction	Inbound
Mode	Asynchronous
Idempotency	Not applicable
Change/Update Behavior	Reporting Framework

Business Context

From a business perspective, this operation supports the use cases Central Billing and Chargeback in Agency Business.

In the Central Billing process, a central agency takes over the responsibility of paying a supplier for goods that were ordered by customers. The goods delivery takes place directly from the supplier to the customer. So, the agency is only involved in the payment process, and earns a fee from the supplier and/or the customer for his or her service.

A special feature in agency business is the Chargeback process, where a wholesaler can request the difference between the price he or she paid for goods to the supplier, and the price he or she gets from the customer. This difference is based on a special contract between the supplier and the customer.

Related Operations

InvoiceConfirmation_Out to confirm the creation of an invoice.

InvoiceCancellationRequest_In to cancel an invoice.

InvoiceCancellationConfirmation_Out to confirm the cancellation of an invoice.

InvoiceRequest_In to create an invoice from the incoming request (previous version).

InvoiceRequest_Out_V1 to send an invoice to a business partner.

Features

You create an invoice using this service operation. On header level, the operation includes all relevant billing information, such as bill-from party and bill-to party, as well as the total amount of the invoice. Every item contains information about material, price, gross value, net value, and tax portion, for example. Once the operation has been processed successfully, a new invoice is created in the back-end system.

The invoice is considered to be an agency billing document (single settlement request) for Central Billing if it is sent to the agency, and the bill-to party and the product recipient party are not identical. Otherwise the invoice is interpreted as a standard invoice. A single settlement 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, such as a purchase order reference, does not have to exist in the system before the document 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.

For the Chargeback scenario, which creates an incoming Agency Business billing document of type Single Settlement Request, the basis is a special contract (condition contract) between a supplier and a customer to sell him or her goods at a lower price than the normal price. A wholesaler, who handles the orders for the customer, needs to pay the higher price to the supplier, and can request the difference from the supplier by sending an invoice for compensation. On the incoming side, this chargeback request is created as a single settlement request in the supplier system. This single settlement request has a reference to the condition contract between supplier and customer, realized with the new TradePriceSpecificationContractReference node on item level. In contrast to a standard incoming invoice, the supplier has the role of the bill-to party, and the wholesaler has the role of the bill-from party.

Note Note

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

End of the note.

To differentiate between chargeback invoice documents and other kinds of invoice documents in the back end, a new use case was introduced. When the TradePriceSpecificationContractReference node is filled, the use case for compensation management is set, and controls, for example, the mapping of the bill-to party and bill from-party.

Technical Features

The Agency Business adaptation in the previous service version was implemented in the software component EA-RETAIL. With the new service version, the adaptation of the agency business application is provided with software component SAP_APPL. Since the Central Billing process requires only the software component layer SAP_APPL, it is no longer necessary to install the EA-RETAIL component to run the Central Billing process with this service operation.

The Chargeback process, in contrast to the Central Billing process, requires the software components SAP_APPL and EA-GLTRADE due to the condition contract, but not the EA-RETAIL component. Therefore, a new inbound framework for the service implementation of invoices was developed, to dynamically handle the incoming invoice create request for the different business processes. The framework includes a configuration component, which loads important details for mapping and back-end application processing, depending on the use case. Therefore, the corresponding mapping and application processing classes for the Chargeback scenario are only loaded if software component EA-GLTRADE is installed. Otherwise, the Chargeback scenario is not supported.

In contrast to this, all mapping and application processing classes for the Central Billing scenario are provided in software component SAP_APPL.

Prerequisites

You must implement the application component Agency Business. To use the Chargeback scenario, you must also implement Compensation Management.

A payment type and a billing type for each use case in Agency Business needs to be defined.

A proxy mapping group must be defined in the Customizing, containing a default payment type and default organizational data such as a sales and purchase organization. Alternatively, the organizational data can be determined from referenced documents like the condition contract. This is already available in EhP5 for EA-RETAIL. In EhP6, this Customizing view is also available in SAP_APPL with the option 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 service operation uses forward error handling (FEH).

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

Error Category		Error Message
Value	Name	Message Class	Message Number	Message Text
DCE.ICE	Invalid Call Error	WZRE_PRX_MAPPING	010	BTDTypeCode has an initial value. Assign a valid value.
		WZRE_PRX_MAPPING	027	Item &1: no OriginInvoiceReference is maintained
		WZRE_PRX_MAPPING	028	Item &1: BTDTypeCode &2 or referenced document &3 is not supported
		WZRE_PRX_MAPPING	035	BTDItemTypeCode has an initial value. Assign a valid value
		WZRE_PRX_MAPPING	040	PriceSpecificationElementCategoryCode: &1 is not a valid value
		WZRE_PRX_MAPPING	055	Neither currency &1 nor &2 match the currency &3 of the document
DCE.VME	Value Mapping Error	WZRE_PRX_MAPPING	008	Codevalue &1 of BTDTypeCode is currently not supported
		WZRE_PRX_MAPPING	012	The & could not be mapped
		WZRE_PRX_MAPPING	025	Mapping &1 fails: text-id is not maintained (billing document type = &2)
		WZRE_PRX_MAPPING	026	Mapping &1 fails: text-id not maintained (item &2, billing doc type = &3)
		WZRE_PRX_MAPPING	029	Item &1: ExchangeRate could not be mapped successfully.
		WZRE_PRX_MAPPING	033	Item &1: The Product could not be mapped
		WZRE_PRX_MAPPING	036	Item &1: Codevalue &2 of BTDItemTypeCode is currently not supported.
		WZRE_PRX_MAPPING	037	Billing category &1 is currently not supported
DCE.ITE	Internal Term Error	WZRE_PRX_MAPPING	017	Neither currency &1 nor &2 are equal to local currency &3
		WZRE_PRX_MAPPING	021	No purchasing org. data relevant for agency business found for vendor &1

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

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

Error Category		Error Message
Value	Name	Message Class	Message Number	Message Text
PRE.AUE	Authorization Error	WS	034	&: no authorization for this in pur. org & pur. group & in sales area
		WS	072	No authorization to & billing document & (&)
		WS	073	No authorization to & billing document type & (&) in company code &
		WS	366	No authorization for documents for document type & (see long text)
		WS	367	No authorization for documents for org. units (see long text)
		WS	713	No authorization
PRE.TEE.LRE	Lock Request Error	WS	031	Document & is currently being processed
		MC	601	Object requested is currently locked by user &
		MC	602	The requested object is locked by another transaction
		MC	604	Own lock is no longer set for object requested
		WS	032	Document & cannot be blocked
		WS	830	Document & cannot be locked (process lock for invoicing party &)
		WS	832	Document &1 cannot be unlocked (process lock for payer &2)
		01	413	System lock administration error. Please notify your administrator
PRE	Processing Error	WS	203	Billing doc. category & not same & of bill. doc. type &
			204	No billing doc. type passed on
			266	No invoice recipient was transferred

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

Within the postprocessing office, the Create Invoice operation is related to the business process INVC007 of component CA-SOA-ESM-ERP-PUR.

Constraints and Integrity Conditions

The Invoice Create message for Chargeback process only supports the business object Single Settlement Request (BUS 2100002).

Notes on SAP Implementation

The generated proxy in the SAP ERP back-end system is the ABAP interface II_IVE_INVOICECRTRQ1, which is implemented in the class CL_IVE_INVOICECRTRQ1.

The following proxy data type is used in the SAP ERP system for the incoming request message: IVE_E_INVOICE_REQUEST.

A new inbound framework in SAP_APPL, package WZRE_XI_PROXY, which contains the class CL_WLF_INVC_IN_FRAMEWORK, is available. It is used for the reusable parts of all inbound service implementations for invoices concerning all use cases, and calls the use case-specific parts, such as inbound mapping, application processing, outbound mapping, and the proxy call of the confirmation message.

All use cases share the same mapping definition in the Service Mapping Tool (SMT); the mapping WLF_IVE_E_INVOICECRTRQ for inbound data mapping of the incoming request message, which is defined in software component SAP_APPL.

The concrete implementation of the inbound data mapping for the Central Billing scenario is performed in class CL_WLF_INVC_CRT_MAP_IN__B2B (use case = initial).

For the Chargeback scenario (use case = 20), the inbound data mapping is implemented in software component EA-GLTRADE, within class CL_WLF_INVC_CRT_MAP_IN_20_B2B, in package WCB_SE_XI_PROXY.

Both scenarios use the same application processing implementation in class CL_WLF_INVC_CRT_APPL_PROC___.

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

Enhancements

Business Add-Ins (BAdI)

WLF_SE_INVC_RQ_IN: The BAdI definition WLF_SE_INVC_RQ_IN (package WZRE_XI_PROXY) is available to handle customer enhancements. This external Business Add-In offers the BAdI interface IF_WLF_SE_INVC_RQ_IN with the operations INBOUND_PROCESSING, OUTBOUND_PROCESSING, and SKIP_CONFIRMATION:

The INBOUND_PROCESSING operation is called during the inbound data mapping, and can be used for enhancements related to the invoice request message. Import parameters are IVE_E_INVOICE_REQUEST, which contains the data from the invoice request message, and a message container CL_BS_SOA_MESSAGE_CONTAINER. The changing parameter is WLF_INVC_API_IN_SSR, corresponding to the API structure of single settlement request.
The OUTBOUND_PROCESSING operation is called during the outbound data mapping for the confirmation message, and can be used for enhancements related to the invoice request message. Import parameters are WLF_INVC_API_OUT, which contains the data from the back end, and a message container CL_BS_SOA_MESSAGE_CONTAINER. The changing parameter is IVE_E_INVOICE_CONFIRMATION.
The SKIP_CONFIRMATION operation is called during the initialization of the inbound process, and can be used to prevent the system sending a confirmation back to the service 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 WS-RM (Web Services Reliable Messaging) protocol, and there is no counterpart inbound operation available for the outgoing confirmation service operation.

In the EA-RETAIL software component, there is a default enhancement implementation WLF_SPOT_SE_AB_ENH_RT_IMPL, of the BAdI definition mentioned above. This implementation calls any implementation of the BAdI definition WLF_SE_INVOICEREQUEST_INT_ASYN, which was provided in the EA-RETAIL software component with enhancement package 4. Existing enhancement implementations on the customer side can be reused in the new service version, which avoids a double maintenance of enhancements via BAdI.

In addition, there are further BAdI definitions available in enhancement spot WLF_SPOT_SE_AB_ENH, to identify the plant, material number, internal vendor, and customer number.

Service Mapping Tool (Transaction SMT)

The service mapping tool (transaction SMT) was used to create the new and chargeback-specific mapping of an incoming invoice request to a single settlement request in the back end. It also offers another possibility to enhance the inbound mapping.

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

Mapping steps:

HEADER DATA: General mapping for header data
HEADER_ADDRESS_DATA: Mapping of address data on header level
HEADER_PARTY: Mapping of parties on header level
HEADER_PARTY_CMP: Mapping of parties on header level for Compensation Management
HEADER_TAX: Mapping of header taxes
HEADER_TEXTS: Mapping of header texts
ITEM_COND_MM: Mapping of conditions on item level concerning supplier
ITEM_COND_SD: Mapping of conditions on item level concerning customer
ITEM_DATA: General mapping for item data
ITEM_REF: Mapping of references on item level
ITEM_TAX: Mapping of item taxes
ITEM_ DESCR: Mapping of item descriptions