SD Details

7/27/2019 SD Details

1/7

Billing Document Type

Definition

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

Use

Billing document type controls the entire billing document.

You can use billing document types to deal with the different business transactions carried out duringbilling processing.

The different billing document types available are listed in the following table:

Billing Document Type NameF1 Delivery-related invoice

F2 Delivery-related invoice

F5 Pro forma invoice for sales order

F8 Pro forma invoice for delivery

FP Interface

Billing - POS system

CR Credit memo

L2 Debit memo

RE Credit memo for returns

S1 Cancellation invoice

S2 Cancellation credit memo

Specific functions can be defined for each billing document type. This is done using control elements thatare 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 meetall 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 transferred to financial accounting

o blocked from transfer

o not transferred
http://help.sap.com/saphelp_46c/helpdata/en/dd/560eb0545a11d1a7020000e829fd11/frameset.htm


2/7

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 inorder to meet your individual function requirements. You can also create your own billingtypes.

Displaying the Billing Document and theAccounting Documents

1. Call up the transaction as follows:

Menu Path LogisticsSales and

DistributionBillingInformation

System Billing Documents List Billing

Documents

Transaction Code VF05

2. Enter the following data:

Field Europe North America

Payer 1410 3210

Billing docs from Todays date Todays date

To Todays date Todays date

Selection criteria - All billing docs Select Select

Check that the relevant company code (Europe: 1000, North America: 3000) has been enteredunderOrganizational Data.

3. Choose .
http://help.sap.com/saphelp_46c/helpdata/EN/e6/4a75599e0311d189b70000e829fbbd/frameset.htm


3/7

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 AccountingFinancial AccountingAccountsReceivableDocumentDisplay

Transaction Code FB03



Company code 1000 3000

Fiscal year Current year Current year

7. Choose List.



Reference number K-PI-200934 C-FE-0123000

9. Choose .

You now see the two accounting documents that were generated from the billing documents. Todisplay a document, double-click on it.

10. Choose until the overview tree appears.

Customer/Vendor Integration

PurposeCustomer/Vendor Integration for the business partner may be required if you want to use Financial

Accounting (FI) and SAP Business Partnerin parallel.

In Financial Accounting (FI) for company external accounting, accounts receivable and accounts payableaccounting is used as part of theAccounts Receivable (AR) andAccounts Payable (AP) subledgers tomanage accounting data for all customers and vendors. Financial Accountingdoes not rely on the SAPBusiness Partnerto 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 accountsand processing posting data.

Many SAP customers have been using Financial Accountingfor a long time and are now increasinglyusing other applications, such as Loans Management (FS-CML) orSAP Treasury and Risk Management(TRM), which use the SAP Business Partnerto manage business partners. These customers require
http://help.sap.com/saphelp_erp60_sp/helpdata/en/42/d433deccdf6bace10000000a1553f6/frameset.htm


4/7

business partners that are managed as customers/vendors in Financial Accountingand as businesspartners in other applications, to exist synchronously.

Business partnerAdams is one of your companys customers. In the business partner he ismanaged under the number4556, and in the customer master record under number7894. If

certain data, such as his address or bank details, changes, this data should be changed in bothbusiness partner management systems.

You can use customer and vendor integration independent of each other. There are applications that useonly customer integration, and others that also require vendor integration. Customer/vendor integration isintended as a one system/one client solution.

Prerequisites You have matched Customizing for the SAP Business Partnerto Customizing for the

customer/vendor accounts. In particular you have matched the required entry fields. You have toset all fields that are required entry fields in the customer/vendor account as required entry fields inthe field selection control for your customer/vendor business partner roles.

You can access the field selection control for the SAP Business Partnerfrom CustomizingforCross-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 DataPreparations 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 relevantfor your processes in Customizing forCross-Application Components by choosing Master Data

SynchronizationSychronization 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 IMGactivities in Customizing forCross-Application Components by choosing Master Data

Synchronization Customer/Vendor Integration.

For more information, see the documentation for the IMG activities.

Process flowCustomer/Vendor Integration is bidirectional. You can both process customer/vendor master records frombusiness partner maintenance as well as populate data from customer/vendor processing to the businesspartner.

You can assign only one customer/vendor to a business partner and vice versa (1:1 assignment). Youcan assign one customer and one vendor to a business partner simultaneously in a correspondingbusiness partner role.

Customer/Vendor Integration involves the following process phases:...


5/7

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 alreadyexist, then the system locks both the object in question and the object that it is linked to for otherusers until you save the objects.

2. Customer/Vendor Integration takes place in the background whilst the system processes masterdata. When you post the business partner the system posts all required fields in thecustomer/vendor in accordance with the information in the business partner, and when you post thecustomer/vendor, the system posts all required fields in the business partner. Technically speakingwhen you update the business partner, the system updates the corresponding customer/vendor atthe same time and vice versa. You store a number of the assignments required for this inCustomizing.

The customer/vendor master record is linked to the business partner in accordance with thesettings made for synchronization control and Customer/Vendor Integration in Customizing.

You can generate a customer/vendor during business partner processing only if you have selecteda customer business partner role category for which this is possible. If a customer/vendor masterrecord is assigned to the business partner, then the system updates the customer/vendor data inthe business partner at the same time, irrespective of role.

Note the following limitation when processing in the direction from customer/vendor master recordto business partner:

If you change a master record in customer/vendor processing, then the system deletes the firstname in the assigned business partner of the category Person. The system then writes both thefirst 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.

ResultWhen processing the business partner you have also updated the relevant data for the customer/vendormaster record and vice versa.

You can remove an existing link between a business partner and a customer/vendor only as part of thearchiving process.

+

IDOC TYPES

Purchase Requisition: PREQCR101

Purchase Order: ORDERS01

Post Goods Issue: MBGMCR01 / MBGMCR02

Goods Receipt: WMMBID02Invoices: INVOIC01

IDoc Types for Inbound Messages (SD)

The following inbound EDI (Electronic Data Interchange) messages are available in the standard system.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/1c/48de42a142f140e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/1c/48de42a142f140e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_45b/helpdata/EN/93/745280546011d1a7020000e829fd11/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/1c/48de42a142f140e10000000a1550b0/content.htm


6/7

EDI standard term Output type IDoc type

Inquiry REQOTE ORDERS01

ORDERS02

ORDERS03

ORDERS04

Sales order ORDERS ORDERS01

ORDERS02

ORDERS03

ORDERS04

Sales order change ORDCHG ORDERS01

ORDERS02

ORDERS03

ORDERS04

Delivery order DELORD ORDERS03

ORDERS04

Forecast delivery schedule DELINS DELFOR01

Just-in-time delivery schedule DELJIT DELFOR01

Self billing procedure GSVERF GSVERF01

External agent delivery note EDLNOT DESADV01

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 youwant to process inbound EDI messages using the old user interface, enter SDO inthe Variantfield in the partner profile. If this field is blank, inbound EDI messages areprocessed using the new interface. You must make the entries for each partner for eachpartner function and output type.

For further information on partner profiles, see Inbound Processing Partner Profile.

See also:

EDI messages for forecast delivery schedules and just-in-time delivery schedules are explained in moredetail in the documentation EDI (Electronic Data Interchange) for Outbound Deliveries.
http://help.sap.com/saphelp_45b/helpdata/EN/93/74528d546011d1a7020000e829fd11/content.htmhttp://help.sap.com/saphelp_45b/helpdata/EN/dc/6b80b543d711d1893e0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_45b/helpdata/EN/dc/6b80b543d711d1893e0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_45b/helpdata/EN/bd/1850fb98a911d194fc00a0c9306667/frameset.htmhttp://help.sap.com/saphelp_45b/helpdata/EN/bd/1850fb98a911d194fc00a0c9306667/frameset.htmhttp://help.sap.com/saphelp_45b/helpdata/EN/93/74528d546011d1a7020000e829fd11/content.htmhttp://help.sap.com/saphelp_45b/helpdata/EN/dc/6b80b543d711d1893e0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_45b/helpdata/EN/bd/1850fb98a911d194fc00a0c9306667/frameset.htm


7/7

SD Details

Documents

Transcript of SD Details