Billing Document Type

Definition
Controls processing of billing documents such as invoices, credit and debit memos as well as cancellation documents.

Use
Billing document type controls the entire billing document. You can use billing document types to deal with the different business transactions carried out during billing processing. The different billing document types available are listed in the following table: Billing Document Type F1 F2 F5 F8 FP CR L2 RE S1 S2 Name Delivery-related invoice Delivery-related invoice Pro forma invoice for sales order Pro forma invoice for delivery Interface Billing - POS system Credit memo Debit memo Credit memo for returns Cancellation invoice Cancellation credit memo

Specific functions can be defined for each billing document type. This is done using control elements that are specified in tables. The document types can be tailored to meet the requirements of your company. You can also define new billing document types, if those defined in the SAP standard system do not meet all your company requirements. The billing document type controls the following elements: The number range for the document number The billing type that can be used to cancel the billing document The transfer status of the billing document: o o o transferred to financial accounting blocked from transfer not transferred

The procedure for account assignment in Financial Accounting The allowed output for a business transaction and the procedure for output The partner functions allowed at header level The partner functions allowed at item level

In SD Customizing, you can change the billing types provided with the standard system in order to meet your individual function requirements. You can also create your own billing types.

Displaying the Billing Document and the Accounting Documents

1. Call up the transaction as follows: Menu Path Logistics Sales and Distribution Billing Information System Billing Documents List Billing Documents VF05

Transaction Code 2. Enter the following data: Field Payer Billing docs from To Selection criteria - All billing docs Europe 1410 Todays date Todays date Select

North America 3210 Todays date Todays date Select

Check that the relevant company code (Europe: 1000, North America: 3000) has been entered under Organizational Data. 3. Choose .

You now see both of the invoices created for this customer. To call up any of the documents, simply double-click on the relevant line. 4. Choose until the overview tree appears. 5. Call up the transaction as follows: Menu Path Accounting Financial Accounting Accounts Receivable Document Display FB03

Transaction Code 6. Enter the following data: Field Company code Fiscal year 7. Choose List. Europe 1000 Current year

North America 3000 Current year

8. Enter the following data: Field Reference number 9. Choose . Europe K-PI-200934 North America C-FE-0123000

You now see the two accounting documents that were generated from the billing documents. To display a document, double-click on it. 10. Choose until the overview tree appears.

Customer/Vendor Integration
Purpose
Customer/Vendor Integration for the business partner may be required if you want to use Financial Accounting (FI) and SAP Business Partner in parallel. In Financial Accounting (FI) for company external accounting, accounts receivable and accounts payable accounting is used as part of the Accounts Receivable (AR) andAccounts Payable (AP) subledgers to manage accounting data for all customers and vendors. Financial Accounting does not rely on the SAP Business Partner to manage the business partners, but uses its own customer/vendor master records, which are integrated in all accounting transactions, such as creating business transactions on accounts and processing posting data. Many SAP customers have been using Financial Accounting for a long time and are now increasingly using other applications, such as Loans Management (FS-CML) orSAP Treasury and Risk Management (TRM), which use the SAP Business Partner to manage business partners. These customers require

business partners that are managed as customers/vendors in Financial Accounting and as business partners in other applications, to exist synchronously. Business partner Adams is one of your companys customers. In the business partner he is managed under the number 4556, and in the customer master record under number 7894. If certain data, such as his address or bank details, changes, this data should be changed in both business partner management systems. You can use customer and vendor integration independent of each other. There are applications that use only customer integration, and others that also require vendor integration. Customer/vendor integration is intended as a one system/one client solution.

Prerequisites
You have matched Customizing for the SAP Business Partner to Customizing for the

customer/vendor accounts. In particular you have matched the required entry fields. You have to set all fields that are required entry fields in the customer/vendor account as required entry fields in the field selection control for your customer/vendor business partner roles. You can access the field selection control for the SAP Business Partner from Customizing for Cross-Application Components by choosing SAP Business Partner -> Business Partner -> Basic Settings -> Field Groupings -> Configure Field Attributes per BP Role . You can access the screen selection control for customer/vendor accounts from Customizing by choosing Financial Accounting (New) Accounts Receivable and Accounts Payable. You make settings for customer integration by choosing Customer Accounts Master Data Preparations for Creating Customer Master Data Define Account Groups with Screen Layout (Customers) Define Screen Layout per Company Code (Customers) Define Screen Layout per Activity (Customers) If you also require vendor integration, you make settings for vendor integration by choosing: Vendor Accounts Master Data Preparations for Creating Vendor Master Data Define Account Groups with Screen Layout (Vendors) Define Screen Layout per Company Code (Vendors) Define Screen Layout per Activity (Vendors) To make settings for Master Data Synchronization, you have executed the IMG activities relevant for your processes in Customizing for Cross-Application Components by choosing Master Data Synchronization Sychronization Control. For more information, see the documentation for the IMG activities. To make settings for Customer/Vendor Integration, you have made settings for all required IMG activities in Customizing for Cross-Application Components by choosing Master Data Synchronization Customer/Vendor Integration. For more information, see the documentation for the IMG activities.

Process flow
Customer/Vendor Integration is bidirectional. You can both process customer/vendor master records from business partner maintenance as well as populate data from customer/vendor processing to the business partner. You can assign only one customer/vendor to a business partner and vice versa (1:1 assignment). You can assign one customer and one vendor to a business partner simultaneously in a corresponding business partner role. Customer/Vendor Integration involves the following process phases:
...

1.

You process the business partner or customer/vendor. The system conducts an authorization check. If you make changes to a business partner or a customer/vendor for whom assignments already exist, then the system locks both the object in question and the object that it is linked to for other users until you save the objects. 2. Customer/Vendor Integration takes place in the background whilst the system processes master data. When you post the business partner the system posts all required fields in the customer/vendor in accordance with the information in the business partner, and when you post the customer/vendor, the system posts all required fields in the business partner. Technically speaking when you update the business partner, the system updates the corresponding customer/vendor at the same time and vice versa. You store a number of the assignments required for this in Customizing. The customer/vendor master record is linked to the business partner in accordance with the settings made for synchronization control and Customer/Vendor Integration in Customizing. You can generate a customer/vendor during business partner processing only if you have selected a customer business partner role category for which this is possible. If a customer/vendor master record is assigned to the business partner, then the system updates the customer/vendor data in the business partner at the same time, irrespective of role. Note the following limitation when processing in the direction from customer/vendor master record to business partner: If you change a master record in customer/vendor processing, then the system deletes the first name in the assigned business partner of the category Person. The system then writes both the first and last name of the customer to the last name field for the business partner. For more information about synchronization directions with corresponding processing scenarios, see Synchronization Directions with Processing Scenarios.

Result
When processing the business partner you have also updated the relevant data for the customer/vendor master record and vice versa. You can remove an existing link between a business partner and a customer/vendor only as part of the archiving process. +

IDOC TYPES
Purchase Requisition: PREQCR101 Purchase Order: ORDERS01 Post Goods Issue: MBGMCR01 / MBGMCR02 Goods Receipt: WMMBID02 Invoices: INVOIC01

IDoc Types for Inbound Messages (SD)

The following inbound EDI (Electronic Data Interchange) messages are available in the standard system.

EDI standard term Inquiry

Output type REQOTE

IDoc type ORDERS01 ORDERS02 ORDERS03 ORDERS04 ORDERS01 ORDERS02 ORDERS03 ORDERS04 ORDERS01 ORDERS02 ORDERS03 ORDERS04 ORDERS03 ORDERS04 DELFOR01 DELFOR01 GSVERF01 DESADV01

Sales order

ORDERS

Sales order change

ORDCHG

Delivery order Forecast delivery schedule Just-in-time delivery schedule Self billing procedure External agent delivery note

DELORD DELINS DELJIT GSVERF EDLNOT

For more information on IDoc types, refer to IDoc types for Outbound Messages (SD).

SAP continues to support the old user interface for processing sales documents. If you want to process inbound EDI messages using the old user interface, enter SDO in the Variant field in the partner profile. If this field is blank, inbound EDI messages are processed using the new interface. You must make the entries for each partner for each partner function and output type. For further information on partner profiles, see See also: EDI messages for forecast delivery schedules and just-in-time delivery schedules are explained in more detail in the documentation EDI (Electronic Data Interchange) for Outbound Deliveries. Inbound Processing Partner Profile.