Ansicht
Dokumentation
ERP_IPM_BACKEND_1: Integration of SD Product Sales with IPM (New) ( RELNSAP_APPL_605_EXTRCT )
CL_GUI_FRONTEND_SERVICES - Frontend Services BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Short text
ERP_IPM_BACKEND_1: Integration of SD Product Sales with IPM (New)
Use
As of SAP enhancement package 5 for SAP ERP 6.0, business function IPM, Industry-Independent Back End (ERP_IPM_BACKEND_1), billed values and quantities from Sales and Distribution (SD) product sales are used as the basis for calculating outgoing royalties in SAP Intellectual Property Management(IPM). The information required from the SD billing document is transferred to the IPM settlement data collector. This function has been available in a media system as of Release IS-Media 4.71 and is now also available in an ERP system, even if the business function set Media is not activated.
Effects on Existing Data
Effects on Data Transfer
During billing document creation, the information required is saved in the outgoing royalties (OR) data collector in ERP. When you start the initial data transfer for the IPMBEAPRDSLS object, data is transferred to the settlement data collector in IPM. If processing is successful, the system deletes data in the OR data collector so that the OR data collector only contains the data that has not yet been transferred. The qRFC monitor (outbound queue) in ERP, the qRFC monitor (inbound queue) in IPM, and the inbound flow for the IPM_BEA_BDC BDoc are used as monitors for the data transfer to IPM.
The following data for a billing document is transferred to the OR data collector as standard:
- Logical system
- Header and item number for the billing document
- Service creation date
- Intellectual property (IP)
- Time stamp
Effects on System Administration
- In ERP, activate the enterprise business function IPM, Industry-Independent Back End (ERP_IPM_BACKEND_1).
- In CRM, activate the business function Intellectual Property Management(CRM_IPM_1)
Effects on Customizing
Subscreen 2014 in the MGD1 function group must be incorporated in material master maintenance to determine the IP. The system determines the IP for the billing item from the IP recorded in the material master for the billing item.
If no entry has been made in the IP field in the material master, the system does not take into account the corresponding billing item during the calculation of outgoing royalties. This means that no data is transferred to the OR data collector.
To determine the following data, you must make the following IPM Customizing settings or perform a corresponding BAdI implementation. You must also make the corresponding settings in ERP to transfer the data required by the IPM System:
- Rights dimensions 1 to 6. You define the rules for rights dimensions for a billing item in Customizing
for Customer Relationship Management under Settings for Intellectual Property Management (IPM) ->
Define Attribute Mapping.
If this customizing is not sufficient, you can define in Customizing for Customer Relationship Management under Settings for Intellectual Property Management (IPM) -> BAdIs -> Mapping of Rights Attributes the rules in an implementation of this Business Add-In.
- A value or quantity with a currency or unit of measure for each billing item and data value. You determine the data values required in Customizing for Customer Relationship Management under Settings for Intellectual Property Management (IPM) -> BAdIs -> OR Data Collector Enhancements.
The sample implementation can be used as a template for your implementation: the data value /SD0 contains the net value, the /SD1 data value contains the billed quantity, the /PNP data value contains the net store price, and the /PGP data value contains the gross store price.
If you reverse a billing item, the system deletes the corresponding entries in the settlement data collector. It then transfers the billing item to the OR data collector with a deletion indicator.
When you save after creating, modifying, or deleting a billing document, output control transfers the billing document to the OR data collector.
SAP provides the IPMO output type, which controls the OR data collector. This output type is used in the V10000 message schema. To activate the OR data collector, you must create an output condition record for each billing type for which data is to be transferred to IPM. Do not create output condition records for billing types that are not to be transferred to IPM, such as invoice lists. This is because invoice lists are not usually used to calculate royalties. See links below:
Output Type IPMO: Sales and Distribution -> Basic Functions -> Output Control -> Output Determination -> Output Determination Using the Condition Technique -> Maintain Output Determination for Billing Documents -> Maintain Output Types
Output Determination Procedure V10000: Sales and Distribution -> Basic Functions -> Output Control -> Output Determination -> Output Determination Using the Condition Technique -> Maintain Output Determination for Billing Documents -> Maintain Output Determination Procedure
Create Output Condition Record: Choose the following path in the SAP Easy Access menu: Logistics -> Sales and Distribution -> Master Data -> Output -> Billing Document -> Create
Note:
- Credit memos must be transferred with negative values and quantities so that they are interpreted correctly.
- The data values used here must be defined in the IPM Customizing settings under Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management --> Basic Functions -> Pricing -> Define Data Values.
Further Information
For more information, see the main release note for business function IPM, Industry-Independent Back End and SAP Library under SAP Customer Relationship Management-> Components and Functions -> SAP CRM for Industries -> Media -> Intellectual Property Management.
Vendor Master (General Section) RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 7615 Date: 20240603 Time: 193826 sap01-206 ( 139 ms )
