Ansicht
Dokumentation

CRM_BILL_BADI_EXTDOC - Business Add-In: Read External Bills

CRM_BILL_BADI_EXTDOC - Business Add-In: Read External Bills

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used to read bill documents from external systems and to save them within the CRM database for billing documents.

The bill documents saved in this way can be selected in the standard transaction for billing documents for display purposes. Subsequent processes such as the creation of adjustment requests can also be initiated based on these.

Search process flow: When searching for bill documents, the external system is checked first. The search results are then augmented by CRM billing documents that were created within CRM. If the user now tries to display a certain external bill document, it is loaded from the external system, converted and finally saved in CRM. The complete bill document is then loaded from there and brought up for display. Once an external bill document is saved in CRM, there is no further reconciliation with its original document in the external source system. A possible change to the original document (due to cancellation, for example) is therefore not recognized in the current release.

The external system can be accessed by CRM using the RFC or XI interface, for example. The bill documents can be displayed in the CRM billing document format.

If the external system uses document numbers of up to 10 digits, a transfer of these external document numbers can take place. If not, the CRM billing document is given a unique number when the transfer takes place. The Customizing of the billing type should be appropriately set up in view of the number range.

The class CL_CRM_BEA_EXTERNAL_BILLDOC_SD contains an example implementation for the reading of SD billing documents from an SAP ECC system. Due to the limited interface of the SAP ECC system, only parts of the billing document are read here and transferred to CRM. However, this example very clearly shows the difference between the investigation of a restricted search result and that of a complete billing document, if the document should actually be saved in CRM. The mapping of control information used in R/3 (for example, billing type and item category) can either occur in the supplying R/3 or the receiving CRM system.

The class CL_IMP_BEA_EXT_BILL_DOC_XI is an example of a connection using the XI interface. The data here is also requested in two steps, whereas the mapping of the individual data fields takes place within the interface defined in XI.






General Data in Customer Master   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 2558 Date: 20240606 Time: 135652     sap01-206 ( 119 ms )