Ansicht
Dokumentation

SAP Media: Title Reporting (New) ( RELNBW_352_BCT_ISM )

SAP Media: Title Reporting (New) ( RELNBW_352_BCT_ISM )

rdisp/max_wprun_time - Maximum work process run time   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

SAP Media: Title Reporting (New)

Use

Title Reporting has been included in the SAP Business Information Warehouse to provide a general view for analysing the different business areas in a media company (for example, publishers, the entertainment industry and marketing agencies).

The different areas are integrated by using an object common to them all, the title.

A title in a media company refers to a product or a group of products. The title is an object that unites the business processes involved in the creation and exploitation of the title so that they can be analyzed together, thus replacing the previous view of individual business processes in isolation. For example, this means the title can be used to connect different modules (such as Materials Management and Sales and Distribution) and other media components (such as Media Product Sales and Intellectual Property Management).

This general analysis of business processes is aimed primarily at costs and revenue using the Special Ledger (FI-SL) and Profitability Analysis (CO-PA). The Business Content for Title Reporting can only be used if the operating concern in CO-PA and the Special Ledger have been defined accordingly.

FI-SL and CO-PA are generating applications that are set up in the customer system. This means that it is not possible to provide all the objects that are usually supplied with Business Content. Some other Business Content elements must be added manually.

Effects on Existing Data

The following objects are provided with the Business Content:

  • Queries

  • Data targets: InfoCubes and ODS objects

  • Update rules (assignment of communication structure to data targets)

  • InfoSources (communication structures)

  • DataSources (R/3) and transfer structures (BW) for master data

  • InfoPackages for master data

  • Process chains for master data

You will need to make enhancements to the following existing Business Content objects:

  • Process chains of transaction data for FI-SL and CO-PA

The following objects are not delivered:

  • DataSources for transaction data (R/3) in FI-SL and CO-PA

  • Transfer structures for transaction data in FI-SL and CO-PA

  • Transfer rules (assignment of DataSource (transfer structure) to InfoSource (communication structure) for transaction data

  • InfoPackages for transaction data for generated DataSources

Scenarios for Title Reporting

A variety of scenarios are mapped for Title Reporting:

  • Profitability and sales analyses

  • Financial statement analyses and profit and loss analyses

  • License sales contract analyses

Profitability and Sales Analyses in Title Reporting

The complex interaction between all the business processes involved in the life cycle of a title and the operative components involved (Materials Management, Sales and Distribution, etc.) is mapped in the operating concern in CO-PA and enriched with title data. In addition to the title, the media issue (media product master) is of key importance to reporting in sales and distribution. The media issue can be used to carry out reporting for individual products sold (for example, books) and to valuate these.

Data Targets for the Profitability and Sales Analyses

  • InfoCube: CO-PA: Profitability analysis (0ME_TLC03)

  • InfoCube: CO-PA: Sales analysis (0ME_TLC04)

  • ODS: CO-PA: Line item (0METLDS04)

InfoSources and DataSources for Profitability and Sales Analyses

  • InfoSource: ISM: CO-PA Title Reporting (line items) (0ME_TTL_COPA_SI)

  • The DataSource for CO-PA line items must be generated manually.

A new improved delta-enabled DataSource has been developed for the media product master to integrate the R/3 title master data with the media issue, media product, and media product family. An extraction process now takes place using one DataSource instead of separate DataSources for the media issue, media product, and media product family, as was previously the case. The master records are distributed between the media issue, media product, and media product family and media title (material number) by means of an update in SAP BW, so that the data now only has to be extracted once.

The previous DataSources are no longer supported (no continued development and no transfer structures for the InfoSource), but still exist so that the objects remain compatible:

  • IS-M: Media issue (0ME_MED_ISS_ATTR)

  • IS-M: Media issue texts (0ME_MED_ISS_TEXT)

  • IS-M: Media product (0ME_MED_PRO_ATTR)

  • IS-M: Media product texts (0ME_MED_PRO_TEXT)

  • IS-M: Media product family (0ME_MED_FAM_ATTR)

  • IS-M: Media product family texts (0ME_MED_FAM_TEXT)

Instead, you should use the following DataSources:

  • IS-M: Media-specific material data (0ME_MATERIAL_ATTR)

  • Material text (0MATERIAL_TEXT)

Please see also the note 'IS-M: New BW extraction for media product and title mat.' (699306).

Financial Statement Analyses and Profit and Loss Analyses in Title Reporting

Financial statement analyses and profit and loss analyses (P&L) can be executed to line item level in Title Reporting based on the transaction figures from the Special Ledger (FI-SL). This can be done using hierarchies based on the financial statement and P&L structures that make a balance-dependent assignment of financial statement items in the financial statement/P&L structure.

Data Targets for Financial Statement Analyses and Profit and Loss Analyses

  • InfoCube: FI-SL: Transaction figures (0METL_C01)

  • Virtual InfoCube: FI-SL: Financial statement and P&L (0METLVC01)

  • ODS: FI-SL: Line item (0METLDS01)

InfoSources and DataSources for Financial Statement Analyses and Profit and Loss Analyses

  • InfoSource: ISM: FI-SL Title Reporting (line items) (0ME_TTL_FISL_SI)

  • InfoSource: ISM: FI-SL Title Reporting (totals records) (0ME_TTL_FISL_TT)

  • The DataSource for the FI-SL line items must be generated manually

  • The DataSource for the FI-SL totals records must be generated manually

License Sales Contract Analyses in Title Reporting

Key figures are calculated from the line item records in FI-SL and summarized at contract level and over time for the title analyses for the license sales contract in Intellectual Property Managements (IPM). You can specify in Customizing for SAP BW which accounts are to be summarized for which key figures for transformation from the account to the key figure model.

Data Targets for License Sales Contract Analyses

  • InfoCube: FI-SL: License sales contract analysis (0METL_C02)

  • InfoCube: FI-SL: License sales contract analysis (time-dependent) (0METL_C05)

  • ODS: FI-SL: Key figure model (0METLDS02)

  • ODS: FI-SL: Key figures calculated (0METLDS03)

InfoSources and DataSources for License Sales Contract Analyses

  • InfoSource: The InfoSource for the FI-SL line items 'ISM: FI-SL Title Reporting (line items)' (0ME_TTL_FISL_SI) is used

  • The DataSource for the FI-SL line items must be generated manually

Process Chains for Title Reporting

Process chains are available for controlling all loading processes. The process chains are used to initialize the delta procedure and to load the data in the delta procedure.

Process Chains for Title Reporting

  • CO-PA: Title Reporting - line items: load delta (0ME_TTL_COPA_DELTA_P02)

  • CO-PA: Title Reporting - line items: initial load (0ME_TTL_COPA_INIT_P02)

  • CO-PA: Title Reporting - line item scenario: load delta (0ME_TTL_COPA_DELTA_P01)

  • CO-PA: Title Reporting - line item scenario: initial load (0ME_TTL_COPA_INIT_P01)

  • FI-SL: License sales contract - integration: load delta (0ME_TTL_IPM_DELTA_P01)

  • FI-SL: License sales contract - integration: initial load (0ME_TTL_IPM_INIT_P01)

  • FI-SL: Title Reporting - line item: load delta (0ME_TTL_FISL_DELTA_P02)

  • FI-SL: Title Reporting - line item: initial load (0ME_TTL_FISL_INIT_P02)

  • FI-SL: Title Reporting - totals records - balance carryforward 000.yyyy (0ME_TTL_FISL_FULL_P02)

  • FI-SL: Title Reporting - line item scenario: load delta (0ME_TTL_FISL_DELTA_P01)

  • FI-SL: Title Reporting - line item scenario: initial load (0ME_TTL_FISL_INIT_P01)

  • FI-SL: Title Reporting - balance carryforward scenario: full upload (0ME_TTL_FISL_FULL_P01)

  • Hierarchy for financial statement/P&L structure (R/3): full upload (0ME_GLACEXT_HIER_FULL_P01)

  • Media product-business partner hierarchy (R/3): full upload (0ME_MED_ISS_BP_HIER_P01)

  • Media product hierarchy (R/3): Full Upload (0ME_MED_ISS_HIER_P01)

  • G/L account hierarchy (R/3): Full Upload (0ME_GLACOUN_HIER_FULL_P01)

  • Title hierarchy (CRM): Full Upload (0IPM_TITLE_HIER_FULL_P02)

  • Title - business partner hierarchy (CRM): Full Upload (0IPM_TITLE_HIER_FULL_P03)

  • Hierarchy for title - content category (CRM): Full Upload (0IPM_TITLE_HIER_FULL_P05)

  • Hierarchy for title - library (CRM) Full Upload (0IPM_TITLE_HIER_FULL_P04)

  • Integration: Material - media product (R/3): load delta (0ME_TTL_DELTA_P01)

  • Integration: Material - media product (R/3): initial load (0ME_TTL_INIT_P01)

  • Integration: Title (CRM and R/3): load delta (0ME_TTL_DELTA_P02)

  • Integration: Title (CRM and R/3): initial load (0ME_TTL_INIT_P02)

  • Integration: Title (material) - title (IP) (CRM): Full Upload (0ME_TTL_FULL_P01)

  • General master data (CRM): load delta (0ME_TTL_IO_DELTA_P01)

  • General master data (CRM): full upload (0ME_TTL_IO_FULL_P02)

  • General master data (CRM): initial load (0ME_TTL_IO_INIT_P01)

  • General master data (R/3): load delta (0ME_TTL_IO_DELTA_P02)

  • General master data (R/3): full upload (0ME_TTL_IO_FULL_P01)

  • General master data (R/3): initial load (0ME_TTL_IO_INIT_P02)

  • Master data attributes for media product (R/3): full upload (0ME_TTL_IO_FULL_P03)

  • Master data for media title (IP) (CRM): load delta (0ME_TTL_IO_DELTA_P03)

  • Master data for media title (IP) (CRM): initial load (0ME_TTL_IO_INIT_P03)






TXBHW - Original Tax Base Amount in Local Currency   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 15026 Date: 20240520 Time: 220046     sap01-206 ( 154 ms )