SAP ABAP IMG Activity _CUSPOR_FIS_INVDETL (BAdI: Determination of Invoice Details)
Hierarchy
FI-CA (Software Component) FI-CA
   FI-CA (Application Component) Contract Accounts Receivable and Payable
     FKKB (Package) Contract A/R & A/P: Central Objects
IMG Activity
ID _CUSPOR_FIS_INVDETL BAdI: Determination of Invoice Details  
Transaction Code S_KK4_74002734   (empty) 
Created on 20030901    
Customizing Attributes _CUSPOR_FIS_INVDETL   Determination of Invoice Details 
Customizing Activity _CUSPOR_FIS_INVDETL   Determination of Invoice Details 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FIS_INVOICEDETAIL    

Use

The Business Add-In (BAdI) FIS_INVOICEDETAIL is the interface for determining invoices.

SAP delivers the relevant BAdI implementation for the invoicing SAP components (for example, SD_INVOICEDETAIL for displaying billing documents from the ERP component Sales and Distribution (SD)). It also delivers an example implementation for the system access to an optical archive for determining invoice data via the SAP ArchiveLink interface. If you require further information, contact your SAP consultant.

Once event 1231 has been processed, the system creates an invoice overview that contains an invoice in the form of one or more items. When the Web user selects the invoice detail display, a new request for determining the detailed data is sent to Contract Accounts Receivable and Payable. During the creation of the invoice overview in event 1231, or subsequently in event 1235, for each invoice the invoicing application transfers information about the formats in which the invoice details can be delivered. The request to determine the invoice details is in one or more of the formats defined (see interface parameter I_INVOICE_FORMATS). In Contract Accounts Receivable and Payable, the system runs through all active BAdI implementations for the BAdI FIS_INVOICEDETAIL. Using the business partner number, invoice number (BOR key), language, and format request transmitted, the individual BAdI implementations first check their responsibility and where relevant, return the required invoice data in the required format as the result of the BAdI call.

In addition to the request to Contract Accounts Receivable and Payable to determine the invoice details, from the Web application you can also support, for example, a direct request to another Web server (see interface description of event 1231).

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030901 
SAP Release Created in 472