Menu
CR500 CRM MIDDLEWARE PDF - CR - Free ebook download as PDF File.pdf), Text File.txt) or read book online for free. CR SAP AG CR CRM Middleware Overview. 9 Mar I´d like to know if CR500 CRM MIDDLEWARE PDF.
CRM Middleware Demystifiedby Ned Falk, Senior Education Consultant, SAP AmericaCRM Middleware contains important functionality to help SAP CRM share data with other systems. Learn about the components involved with CRM Middleware and then see how it helps to transfer data between SAP CRM and R/3 or SAP ERP Central Component. Key ConceptCRM Middleware provides software to enable the transfer of data to and from SAP CRM. CRM Middleware is an integrated part of SAP CRM and links SAP CRM with another applicasystem, such as SAP ERP Central Component, or a non-SAP system.SAP CRM, SAP NetWeaver Business Intelligence (BI), and R/3 or SAP ERP Central Component (ECC) share master data about customers and orders.
CRM Middleware software, delivered standard with SAP CRM, facilitates these activities by ensuring that the data passes smoothly among the systems. However, I often find that people who take my classes are unfamiliar with how CRM Middleware works. Although it is impossible to discuss and describe CRM Middleware thoroughly in just one article, let me introduce you to the basic architecture of CRM Middleware. Then Ill walk you through the steps of using CRM Middleware to transfer data from R/3 to SAP CRM.
Finally, Ill show you the reverse steps of sending data from SAP CRM to R/3. In a future article, Illdelve more deeply into the configuration aspects of CRM Middleware. For those who want a refresher on the terms used when discussing CRM Middleware, refer to the sidebar, Before You Begin: CRM Middleware Terms.
The processes mentioned in this article apply to R/3 4.6 and later and mySAP CRM 4.0 and later.it passes between them and SAP CRM. CRM Middleware is the collection of software that links SAP CRM with its supporting applications, such as Interaction Center and Campaign Management. This collection is further grouped into separate software that links SAP CRM with one specific type of system (site).
The specific software for each purpose is called an adapter, which functions as a technology link between SAP CRM and the associated system (Figure 2 on the next page). For instance, the BW Adapter links SAP CRM data into the format and technical storage required to feed the data to SAP NetWeaver BI. The R/3 Adapter passes data between CRM and R/3 (ECC). Adapters are delivered functionality of the CRM Server. Although most adapters have names that disclose the system types they pass data between (for example, the R/3 Adapter), two of them might not be so obvious.
One is the CRM Adapter. This collection of software validates incoming data using the logic configured for each CRM application. This ensures that only valid data is written to the CRM system. The second is the External Interface Adapter (XIF), which is responsible for the communication between CRM and third-party systems (normally back-office systems).
It is designed to process incom-CRM Middleware ArchitectureAlthough CRM Middleware has support for generic technologies (specifically XML), nearly all companies leverage the SAP-specific technologies used to pass data between CRM and the other SAP software. Figure 1 shows which systems are typically involved in a CRM Middleware implementation and the kinds of dataFigure 1 The basic landscape and data involved with SAP CRMing and outgoing XML or IDoc messages.BUPAMAIN is for business partners and BUSTRANSACTIONMESSAGE is the mBDoc for sales orders.Sending Data from R/3 to SAP CRMBefore I get into the data flows, I should mention that you must make some technical settings to link the CRM system to your other systems. For example, you need to set up Remote Function Call (RFC) destinations with log-on information in SAP CRM and, in most cases, the target system. In addition, you must set up the tables delivered with the plug-in to tell R/3 which RFC destinations are active CRM systems that need R/3 information. Lets track what happens in two scenarios. First lets see what happens when you create a new sales order in R/3 and you want to transfer this information to SAP CRM.
Figure 3 depicts a simplified version of the seven steps in this flow. A user saves or updates an order in R/3. In many cases, you may maintain the orders in SAP CRM, but either direction is common and possible. The save triggers a Business Transaction Event (BTE). This takes the customer data and writes it into a flat generic structure BAPIMTCS. This structure consists of a very long field, which stores the order and customer data. SAP CRM uses queued RFC (qRFC) to write the BAPIMTCS structure to an outbound queue in R/3.
The structure containing the data is only sent to SAP CRM if there are available resources and a live connection exists. To accomplish this, CRM uses a qRFC to transfer the data to an outbound R/3 queue. The data then moves to an inbound queue in SAP CRM. The R/3 Adapter in CRM takes the BAPIMTCS structure from the inbound queue and converts it to a messaging BDoc (mBDoc). The mBDoc is a database object designed to hold a specific piece of data. For example,Step 5. The system uses different function modules to validate specific business data and save it in SAP CRM using the CRM Adapter.
If the data saves success-Figure 2 Adapters with CRM MiddlewareFigure 3 The track of a delta order that originates in R/3fully, then it is valid and the system calls the outbound flow. The outbound flow calls various services (software functions for a specific purpose).
The most important is the notification service, which uses the data maintained in the administration console to determine which sites need the data in the order. For example, if a mobile site needs the data, the system writes it to the Consolidated Database (CDB) for later replication to mobile employees. The system calls other adapters as needed. If other R/3 systems or thirdparty back ends need the data, the system calls the appropriate adapter software to accomplish the task. In most cases, the system also calls the BW Adapter as part of the outbound flow. The BW Adapters job is to take the data (in the format of a BDoc) and transfer it to a specialized outbound queue called the BW delta queue.
It transfers the data to a flat structure format that SAP NetWeaver BI can subsequently upload. The BW Adapter is called in most outbound flows no matter how the record originated. This means orders or customers starting in any system (in this example, R/3) are available for complex analysis in your SAP NetWeaver BI system.Sending Data from SAP CRM to R/3Now that Ive shown you the flow for delta processing from R/3 to SAP CRM, Ill describe the minor differences, at a high level, in the other direction.
Basically, instead of R/3 initiating the inbound flow, the system calls the CRM Adapter when you create or change a business object in SAP CRM. This process calls the outbound messaging flow and any applicable adapters. The R/3 Adapter, in outbound mode, is responsible for taking the BDoc structured data, mapping it to the BAPIMTCS structure, and sending it via qRFC to R/3. The plug-in software then executes a specific function module to parse the very long data field, which is in the structure that contains the business information, and write the record to the R/3 tables.
The previous section covers delta processing in both directions for business objects containing both master data and transaction data. However, you may be wondering about all the records existing in your R/3 system, which most likely have been around for a few years. This includes pricing condition records (discounts, surcharges, and general price information), and customizing settings that SAP CRM needs (Figure 4), masterNoteFor more information, you can attend SAP Educations CRM Middleware overview in course CR500 (CRM Middleware). You can read more about this course at www.sap.com/usa/ services/education/index.epx.NoteAccount groups are used in R/3 for number range assignment. To ensure that business partners created in SAP CRM have the same customer number when they get to R/3, SAP CRM needs the information about these account groups. This is an example of the need to transfer customizing data from R/3 to SAP CRM.Figure 4 Customizing adapter objects settings (transaction R3AC3)data, and transactions (e.g., orders). Initial loads handle this data when you first implement SAP CRM.
Initial load transactions are delivered as standard with SAP CRM. They use the settings in adapter objects to request or send data to and from CRM as a group.
These are the same adapter objects that contain mapping functions for the delta downloads referenced above. This is true with the exception of pricing and customizing loads, which are normally just from R/3 to SAP CRM. R/3 is normally the baseline for these settings, so data almost never flows from SAP CRM to R/3 for price conditions and customizing. Figure 4 shows the customizing adapter object that is responsible for mapping R/3 account groups to SAP CRM. Although the initial load flow for business objects (partners and transactions) is more complex, the adapter objects look pretty much the same. The flow for initial downloads for business, customizing, and condition objects all use transaction R3AS to initiate the transfer (Figure 5). However, the flow is less complicated for customizing objects, because they do not support delta processing and it is mostly an R/3 to SAP CRM transfer.
Notice that the data flow in Figure 6 (for customizing objects) does not involve BDocs, nor the inbound and outbound flows. In this case, R/3 and SAP CRM supply the function modules for extraction and mapping. These functions facilitate requesting, then the extraction and transfer, and subsequently storage of the data in SAP CRM. Start the initial download transaction R3AS for the desired customizing table. In this example, the source system is R/3 and the target system is SAP CRM. SAP CRM sends a qRFC telling R/3 to open up a table and see which function it should execute when it requests this objects data.Step 2. The plug-in determines that a generic extraction program for customizing data is necessary.
This program, combined with the parameters of the needed table, extracts the data and puts it into the BAPIMTCS structure. The R/3 Adapter writes the data into similar tables in SAP CRM. Note that the initial flow of business data is more complicated and involves BDocs and flows. It also goes in both directions.to synchronization. In this process, the CDB, which is CRMs main database, and R/3 (ECC) must be in sync. Although in a perfect world, the initial loads and delta mechanisms would keep everything in line, this is not the case. Therefore, SAP CRM allows you to request a refresh of the data from one system (with the correct data) to another system (the one with data problems).
Use transaction R3AR2 to define which sets of business data you want to refresh from one system to another (Figure 7). These requests flow in a similar way as initial loads but are designed to beSynchronization Between SystemsLet me mention two final important CRM Middleware features that are keyFigure 5 Start the initial transfer of business, customizing, and pricing data betweenSAP CRM and other systemsFigure 6 Data flow for customizing objects, such as moving account groups from R/3to SAP CRMBefore You Begin: CRM Middleware Termsabout it almost instantaneously. Although this is the goal and it normally happens, SAP CRM is loosely connected to its supporting systems via an SAP NetWeaver (not SAP CRMspecific) technology called queued Remote Function Call (qRFC). The data the system sends from SAP CRM goes to an outbound queue. The system then passes the data to the inbound queue on SAP ECC. Once there, SAP ECC picks it up and writes it to the database.
The reverse happens when data passes to SAP CRM. CRM Middleware adapters: Collection of software designed to interface SAP CRM with specific applications, such as SAP ECC, SAP NetWeaver BI, or external systems. They facilitate the exchange of both master data and transaction data to these systems. Consolidated Database (CDB): The mobile sales force needs to get information about just its customers and their orders.
The sales reps, however, often move from one organization to another. When this happens, they need to discard their old customers and orders and load the new batch. To make this possible, the customers and orders are not directly passed to mobile sites; rather, they are written to this special database. When the mobile force logs in, it syncs up to this database. Adapter objects: Objects that contain the settings necessary to exchange and map specific pieces of data between a source and target system, such as business partners between R/3 and SAP CRM.
These objects are further grouped into: Business objects (e.g., orders or business partners) Customizing objects (e.g., item categories or calendars) Condition objects (e.g., pricing, rebates, or surcharges) Administration console: Manages which sites get which data from SAP CRM. One major site is your ECC system. Other sites can be for linking to groupware (such as Microsoft Outlook).
They can also be mobile sites linked to mobile sale force personnel. Sites subscribe to selections of data from publications, which link back to SAP CRM business objects, such as orders or business partners (Figure 1). Initial and delta loads: Both master data (e.g., customers) and transaction data (e.g., orders) support delta processing, which means that they only send the new or changed records to and from SAP CRM. Customizing data and pricing information, in most cases, flow only from R/3 to SAP CRM.CRM BDoc: A data container for moving objects (orders/ master) data within CRM.
Messaging BDocs (mBDocs) are special BDocs used to move data between R/3 and SAP CRM (as well as other systems). R/3 (ECC) plug-in: A collection of software functions required to process requests for data from CRM or SAP NetWeaver BI systems. This collection of tables and functions resides on the R/3 system. Although it is called the plug-in, as of SAP ECC 6.0, it comes as part of the normal installation and does not need to be added later. Outbound and inbound interfaces are the parts of the plug-in software geared to either extracting the records from R/3 or writing them to R/3. Structure: An ABAP term for a collection of fields that the system processes and references together Messaging flow: BDocs have associated messaging flows that can be inbound or outbound flows. The flow is made up of one or more services (function modules) run in sequence, such as calling the Billing Engine or the BW Adapter or checking what sites are supposed to receive the data in the BDoc message.
Messaging queues (inbound and outbound): If you create a new customer or sales order in SAP CRM, ECC should knowFigure 1 SAP CRM uses data maintained by the Adminis-tration Console to determine who needs what CRM datatargeted refreshes of limited data while delta processing continues uninterrupted. The ability to first compare data sets between systems is contained within the refresh functionality. For example, does SAP CRM have the same customer data for Ned Falk as R/3? The Data Integrity Manager (transaction SDIMA) contains this ability. This functionality shows you the differences among data sets across systems. If one of the systems is out of whack, you can automatically execute a request to fix it, as discussed above. NFigure 7 A data request to fix bad data in one system (customer number 301101) byrefreshing it from the correct systemNed Falk is a senior education consultant at SAP.
In prior positions, he implemented many ERP solutions, most recently R/3. At SAP, he initially focused on logistics, but now he focuses on SAP NetWeaver BI and SAP CRM. He specializes in BI and CRM interfaces. He has been working with SAP products for more than 12 years. You may contact him via email at [email protected] or meet him in person when he teaches SAP NetWeaver BI from the Atlanta SAP office.
1 CU51 Order BOM CU51 Purpose Use this transaction to create Order BOM for any configured pump based on configuration Job Roles Engineering Prerequisites Material master record already exists Related Documents MM01/MM02/MM03 File Name: CU51 Order BOM Page: 1 of 14 2 Design: BOM design for configurable pumps consists of multilevel KMATS, with a fine line between Order entry and engineering. Based on configuration entered by order entry, engineering will perform CU51 transaction to enter any information required by engineering and will perform BOM explosion using existing super BOM and will perform any required additions or changes to the order specific bom and will save it as an order bom in the system To facilitate this functionality, BOM structure for Pentair is as below PUMPSYSTEM All configured pumps will be configured using Pumpsystem material and based on the configuration specific pump series will be exploded as sub item. Along with the pump series, other sub items such as Spare parts, Suction CANS, Discharge Elbows etc will also be exploded as subitems. If multiple configured items are exploded as subitems onto sales order, engineering will run the transaction for ever Sales Order/Line Item to make sure BOM is exploded according to the configuration and will make changes/additions based on requirements.
Configuration entered at pumpsystem can only be viewed in a sales order PUMPXXXX, SUCTIONCAN, DISCHARGEELBOW, SPAREPARTS etc Order entry will answer all information required to configure these products. Configuration entered at this level can be viewed in CU51 for reference purposes but cannot be changed. In order for engineering to make any necessary changes or answer any additional information that can only be entered and reviewed by engineering, a phantom engineering material has been included as part of BOM structure and super BOMs for all pump series will be maintained at this level PUMPXXXX or PUMPXXXXE This serves as an engineering material and configuration at this level can only be entered by engineering using CU51. Order entry will not get any view to this material from sales order during order configuration.
Typical information answered at this level are motor parameters, engineering calculations, special materials etc. Certain information is mandatory at this level based on pump series and engineering has to enter this information to make the configuration complete and have it released to production PRERELEASE: This material is part of PUMPXXXX and is a Phantom material. This level will be used to establish a prerelease BOM when required so that long lead items can be purchased while engineering/spec department work on the full BOM Note: CU51 for Pentair will always save order BOMs as result oriented Order BOMs.
Result Oriented Order BOM: In this scenario configuration result with manual changes are saved as an order BOM. Dependencies are not saved.
This means that the saved assemblies are smaller than if you save a copy of the super BOM. Exploding the BOM in interactive configuration triggers an update using the material BOM.
Dependencies are processed, which means that changes to characteristic values can result in a change to structure. New items that are created in material BOM are copied to result oriented order bom Prerequisites: Prerequisites for processing CU51 Sales order exists Configuration is complete with no inconsistencies Right configuration profile exists for the materials that will be part of CU51 File Name: CU51 Order BOM Page: 2 of 14. 3 Transaction: CU51 This transaction has to be performed for every sales order/item that requires engineering work. Typical ones include PUMPS, Elbows, CANs etc Once entered into CU51 trnsaction, initial screen will display configuration as below. It displays configuration entered by order entry (which is greyed out and cannot be changed) and also displays the configuration for engineering material, which is where all missing engineering information can be entered File Name: CU51 Order BOM Page: 3 of 14.
4 Double click on the level(left hand Side) that needs to be accessed and the VC relevant for that level will be displayed on the right hand side GREEN LIGHT Indicates that particular level has all information that s required YELLOW LIGHT Indicates that particular level requires certain information and that information need to be entered RED LIGHT Indicates that the particular level has inconsistent VC values and need to be fixed Ultimate goal is to have Green light at all levels File Name: CU51 Order BOM Page: 4 of 14. 6 BOM Design BOM design employs class items which are replaced by real materials from variant tables. 98% of the bom items for all pump models are determined based on above methodlogy Pre-Release: In certain scenarios, a pre-release BOM has to be established so that the long lead items can be purchased while engineering/spec department works on the full bom and release it to production Establising a Prerelease BOM can either be done from CU51 or using transaction CS61. Recommendation is to use CS61 as multiple materials can be entered at once in CS61 where as in CU51 one materials has to be entered at a time.
Please refer to Prerelease BPP for this process File Name: CU51 Order BOM Page: 6 of 14. 7 CU51: Reasons why a material cannot be determined: Material does not exist in SAP Material not classified with right class Material does not exist for a certain VC selection Object dependency used to replace the class item with material from table is not written with proper syntax Issue Resolution: Only to be done by VC modelers. Users without a modeler role will only be performing steps that invloves adding or deleting material manually, changing component quantites manually and flagging the BOM as prodcution relevant Material Does not exist in SAP: To be performed by Master data team or Pentair KC superuser Create the material in SAP Make sure the material is assigned the right class o Ex: FNSTUD. If the assumption is that stud material CP8808M F has to be determined from table and it failed because material does not exist in SAP o After material is created, assign the material to Class 300 FNSTUD. Class a specific material has to be assigned can be determined as below o Method1 - CU51 screen will display the class name that needs to be replaced with the material. That s the class material need to be classified with o Method2 Super BOM (CS03) will display the class used for studs as below. BOM item number can be known by double clicking the item on left hand side in CU51 screen CS03: Material: VTSHCOLUMNASSY PLANT: 1530 USAGE: 1 File Name: CU51 Order BOM Page: 7 of 14.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |