&TITLE&
Trigger Billing Document IN R/3

Purpose
This reports generates R/3 billing documents directly from CRMdocuments, without detouring through other R/3 documents.

Prerequisites
Perform the following activities in the CRM system:
Enter a system link for the billing document by performing Customizingin the IMG activity Define OLTP R/3Parameters
Then assign a logical system to the system name. To do so, use IMGactivity Convert Logical System in Application Tables in chapterConfiguring the Logical System.
Perform the following activities in R/3 OLTP Customizing:
Define the CRM order types for billing under Sales and Distribution-> Sales -> Sales Documents -> Sales Document Header -> Define SalesDocuemnt Types.
Maintain the partner determination for the sales docuemnt type underSales and Distribution -> Master Data -> Business Partners ->Customers -> Customer Hierarchy -> Configure Partner Determination forHierarchy Types by selecting Sales Document Header andassigning the sales document type to procedure with PartnerProcedure.
Define the billing document-relevant item categories from CRM underSales and Distribution -> Sales -> Sales Documents -> SalesDocument Item -> Define Item Categories.
Define a billing document type for billing under Sales andDistribution -> Billing -> Billing Documents -> Define Billing DocumentTypes.
Define the billing document-relevant CRM item categories underSales and Distribution -> Sales -> Sales Documents -> SalesDocument Item -> Define Item Categories. Please note that the itemcategories must exist for both the billing request items and the objectitems.
Maintain the assignment of the sales document type to the billingdocument type with the corresponding item categories under Salesand Distribution -> Billing -> Billing Documents -> Maintain CopyControl for Billing Documents -> Copy Control: Sales Document toBilling Document. You must not specify any copy conditions in thecopy control.
Define an account key under Sales and Distribution -> BasicFunctions -> Account Assignment/Costing -> Revenue AccountDetermination -> Define and Allocate Account Keys -> Define AccountKeys.
Assign this account key to a G/L account under Sales andDistribution -> Basic Functions -> Account Assignment/Costing ->Revenue Account Determination -> Assign G/L Accounts.
Define the billing document-relevant CRM condition types underSales and Distribution -> Basic Functions -> Pricing -> PricingControl -> Defien Condition Types.
Assign these conditions to the costing procedures that you want to usefor the billing document under Sales and Distribution -> BasicFunctions -> Pricing -> Pricing Control -> Define and Allocate CostingProcedures -> Costing Procedure.
Define a document procedure under Sales and Distribution -> BasicFunctions -> Pricing -> Pricing Control -> Define and Allocate CostingProcedures -> Define Document Procedure.
Assign the document procedure to the billing type under Sales andDistribution -> Basic Functions -> Pricing -> Pricing Control -> AssignCosting Procedures -> Assign Document Procedure to Billing DocumentTypes.
Maintain the assignment of the costing procedures to the documentprocedure under Sales and Distribution -> Basic Functions ->Pricing -> Pricing Control -> Assign Costing Procedures -> DefineCosting Procedure Determination.
For print output, assign an output procedure to your billing documenttype under Sales and Distribution -> Basic Functions -> OutputControl -> Output Determination -> Output Determination via ConditionTechnique -> Maintain Output Determination for Billing Documents ->Assign Output Procedure.
Define the transfer of texts from CRM under Sales and Distribution-> Basic Functions -> Text Control -> Define Text Types. In thismaintenance transaction, select text object Billing Document ->Item and then consecutively maintain the text types, textprocedures, and access sequences that you want to transfer from CRM;assign the text procedure to the item categories under TextProcedure Usage.
To define the products that you want to include in the billingdocuments, proceed as follows:
Maintain the financial products in the CRM system under Master Data-> Products -> Edit Products and send them to R/3 OLTP with Goto-> Send to OLTP.
Assign these products to a specific plant that you want to use for thebilling documents in R/3.
Maintain the physical products in R/3 and download them to the CRMsystem. Assign the physical products to the corresponding financialproducts in the CRM system (with Links in product maintenance).

Features

Selection
You can select the CRM order items for billing by document number,sold-to party, organizational data (sales organization, distributionchannel, division, unit for billing), billing creation date, due date,and billing period, as well as transaction category and movement type.The selection takes place using database table CRMD_ORDER_INDEX.
Note:
You can use the "Test Run" parameter to determine which document itemsin the report would be passed on for billing in the selection.
The selected CRM document items are passed on to the R/3 billing
document along with the corresponding conditions. After the billingdocuments have been created in R/3, the status of the items is set to"Billed" and a document flow for the billing document is written inCRM.
You can use the "Synchronous" parameter to control whether you want thereport to wait for the results of billing document creation (suitablefor online processing).
If you run several billing runs in parallel (at the same time), makesure that the same contracts are not processed in different billingruns. This means that have to use at least one of the two selectioncriteria "Transaction Number" or "Sold-To Party" in this case.

Output
The report lists the selected order items.
You can use the Log function to display the messages (online)generated during the transfer of documents to the R/3 System. In anycase, these messages are written to the application log and can bedisplayed using transaction SLG1 (selection with object CRM_LAM,subobject BILLING)