1310727 - Account Assignment for CRM Documents With Sales Items

8/10/2019 1310727 - Account Assignment for CRM Documents With Sales Items

http://slidepdf.com/reader/full/1310727-account-assignment-for-crm-documents-with-sales-items 1/3

SAP Note

Header Data

Symptom

This note explains Controlling (CO) integration for sales items in CRM sales and service documentsthat are replicated in ERP.It first provides an overview of various scenarios, and then offers individual solutions for caseswhere the standard solution does not cover the customer requirements.

Replication scenarios:

1. In CRM, you create a sales document with sales items and replicate it to ERP, so that thedelivery for it takes place in ERP. The CRM Billing Engine is used for billing. The billingscenario is non-external billing; therefore it is located in CRM and not in ERP.

2. In CRM, you create a service document with a sales item. For this item, a sales anddistribution (SD) document is created in ERP for the delivery. At the time of replication,control is transferred to the sales adapter. As above, the CRM Billing Engine is used forbilling.

l In these cases, the assignment to an account assignment object does not take place in the ERPsales order, but using the CRM transaction, and so the CO manager is called from CRM. Here, CRMis the leading system with regard to account assignment, since billing takes place in CRM.

l The reason for this is that the CRM Billing Engine does not recognize the account assignmentdetermined in the ERP order, and cannot post any revenues to it. Therefore, when you use theBilling Engine, there can only be one account assignment, which is managed using the account

assignment manager (IAOM).

l For sales documents, a profitability segment (CO-PA) is generally provided as an accountassignment object.

l For sales items in the service document, however, other CO objects such as an internal order maybe provided, as long as "Service" is set as a BW/CO scenario in CRM Customizing and single-object controlling is set for the CRM service CO scenario in ERP CO Customizing.

3. In the "CRM External Billing" scenario for service documents with service items only, accountassignment is always performed by the CO manager.

4. Currently, in the case of intercompany billing, the account assignment for the delivery iscreated in the ERP sales order (ERP standard logic). This means that the account assignment forthe delivery is not managed by the account assignment manager, and consequently there is NOintegration into CO for intercompany billing of the CRM billing document. Therefore, accountassignment is always performed using ERP.

5. If account assignment is provided by the account assignment CO manager, the determination ofall data relevant to account assignment in the R/3 sales order is prevented to ensure dataconsistency. Therefore, for example, you cannot use Customizing to set the special stockindicator, the valuation of special stock, and so on.

6. The following fields are determined by the CO manager:

a) vbap-paobjnr Number for profitability segments (CO-PA)

b) vbap-aufnr Internal order number

c) vbap-prctr Profit center

d) vbap-gsber Business area

e) vbap-ps_psp_pnr Work breakdown structure element (WBS element)

7. The following fields are not supported by the CO manager, and are therefore deleted:

a) vbap Originating sales document

b) posnv Originating item

1310727 - Account assignment for CRM documents with sales items

Version 3 Validity: 13.08.2013 - active Language English

Released On 13.08.2013 09:56:28

Release Status Released for Customer

Component CRM-BTX-COI-SAL Controlling Integration Sales

CRM-BTX-COI-SRV Controlling Integration ServicePriority Recommendations / Additional Info

Category Consulting

Other Components



c) sobkz Special stock indicator

d) kzbws Valuation of special stock

e) kzvbr Consumption posting

Other Terms

CRM, Controlling (CO) integration, sobkz, sobkz, kzvbrCRM_CO_SLS_IAOM_SELECTFV45PFAP_VBAP_FUELLEN_IAOM

Reason and Prerequisites

This is a consulting note.

Solution

Solution options:

1. If you are using ERP billing but these fields are still deleted or changed by the IAOM COmanager for some sales items, you must set "External billing" as the billing relevance for theitem category in CRM Customizing for billing data.

2. The following event is entered in the table TPS31. It is called for documents with a salesitem that are created in CRM. You can use transaction SM30 to change this table. You can replacethe standard function module with one of your own. For example, you can copy the standard sourcecode into your own function module and change it so that the module returns the value "False"for ls_iaom_vbp-iaom_relevant. This prevents the COBL fields in the includeFV45PFAP_VBAP_FUELLEN_IAOM from being overwritten.

¡ Process 00503122

¡ Country (ISO code)

¡ Application ID BC-MID

¡ Function module CRM_CO_SLS_IAOM_SELECT

3. Modification to the source text

In the include FV45PFAP_VBAP_FUELLEN_IAOM, the COBL fields are assigned after the call to the COmanager interface......vbap-paobjnr = da_cobl-paobjnr.vbap-aufnr = da_cobl-aufnr.vbap-prctr = da_cobl-prctr.vbap-gsber = da_cobl-gsber.

vbap-ps_psp_pnr = da_cobl-ps_psp_pnr.vbap-vbelv = da_cobl-kdauf.vbap-posnv = da_cobl-kdpos.vbap-sobkz = da_cobl-sobkz.vbap-sobkz = da_cobl-kzbws.vbap-kzvbr = da_cobl-kzvbr.....If you do not want one of these fields to be overwritten, you must comment it out.Example for special stock indicator:vbap-sobkz = da_cobl-sobkz.replace with * vbap-sobkz = da_cobl-sobkz.

Validity

For the following solutions, if you make one of the following changes, it is importantto make sure that your process functions correctly after the change. These solutionoptions may cause the CRM Billing Engine to post the revenues to another CO object (CO-PA) as costs of CRM documents, for example. Therefore, it is important to make sure

that the data is posted consistently.

Note that these are individual solutions, and are therefore not contained in the standardSAP solution.



This document is not restricted to a software component or software component version