CRM Business Transactions in SAP

The concept of CRM Business Transactions in SAP has the meanings of a uniform construction for all business transactions.Different transaction varieties have the identical structure.A enterprise transaction can cover a quantity of business circumstances, for instance, sales order and business activity.There's a comparable interface for processing all sorts of business transactions. There is a strict break up between the consumer interface and the processing of transactions. Similar capabilities can be found in all types of business transactions.

Depending on the Leading Transaction Category (e.g. Alternative, Gross sales, Task, Business Exercise), a business transaction has a sure structure.Tasks have a construction that is composes only of one Header level. Alternatives have a structure that is composed of two ranges:
  1. Header knowledge
  2. Merchandise knowledge
  3. Sales transactions have a structure that's composed of three ranges:
  4. Header information
  5. Merchandise data
  6. Schedule strains
  7. There are not any schedule line categories out there inside SAP CRM Customizing.
Within the SAP CRM system, there should be a corresponding gross sales doc kind of the same ID in the SAP R/3 system. In SAP R/3 it is doable to have language-dependant ID’s for sales document sorts (e.g. OR = TA).The identical requirement (an identical ID’s) applies for merchandise categories, merchandise class teams, and merchandise category determination. SAP delivers commonplace settings.A business transaction may be assigned to one or more enterprise transaction classes (for instance, sales and exercise). Solely sure mixtures of enterprise transaction classes are potential, for instance, leading enterprise transactions. The enterprise transactions sales and activity are assigned to the transaction sort Telesales. If gross sales is main, the transaction is displayed as a sales transaction within the locator and not as an activity.

Management attributes (such as the main business transaction class, text willpower procedure, associate willpower process, standing profile, the organizational data profile and the number range assignment) may be defined at header level. Various settings can be made, depending on the business transaction category.

First you outline the overall settings, that are the identical attributes for all sorts of merchandise
categories like General knowledge: merchandise object sort, calculation of weights and quantity for freight and Profiles: textual content determination, accomplice determination, status profile, ATP profile, organizational information profile, action profile, BOM explosion, configuration data.

Next you outline the business context in which the item class is used. Settings differ depending on the assigned business transaction category (billing data, pricing data, or citation information). Actions do not have items. Customizing item categories and item class determination shouldn't be obligatory in this case.

The procedure for willpower of merchandise categories needs to be set up in the same way as within the SAP R/3 system. In every other case, problems can occur through the upload to SAP R/3. SAP delivers the commonest item classes for gross sales transactions (TAN, TAM, TAC and TAE) and the suitable determination. Other customized-made merchandise classes and their dedication should be arrange manually. No customizing obtain from SAP R/three is supported.

Examples for merchandise category willpower:

A normal merchandise (NORM) in a typical gross sales order (TA) will lead to item category TAN.A typical item (NORM) in a typical sales order (TA) that belongs to the next-level merchandise (handbook enter) will result in merchandise class TANN (free good), because the principle merchandise class is taken into account.

A typical item (NORM) in a regular gross sales order (TA) that belongs to the next-level item of item class TAN will lead to merchandise class TANN, once free items willpower takes place (item
category utilization is FREE).
  1. Not all capabilities are available in every transaction type.
  2. A collection of fundamental functions are:
  3. Partner Processing
  4. Pricing
  5. Incompleteness Verify
  6. Text Management
  7. Date Management
The following gross sales-specific functions are covered in additional detail in CR300 CRM Gross sales:
  1. Product substitution
  2. Free items
  3. Credit-check
  4. ATP-verify
As of SAP CRM 3.0, you probably can select a number of transaction documents in the locator, and create a followup document for all of them.Within the locator, you choose the transactions you wish to use as templates, then choose Create follow-up in the locator.The header data is copied from the first transaction in the hit list, the merchandise data from all transactions is collected on the Merchandise selection tab page.

Prerequisite: Related organizational knowledge within the source and target transactions ought to match.For processing follow-up documents, you could carry out three customizing steps:
  1. Copy management for transaction sorts
  2. Copy management for item categories
  3. Decide item category when copying
Customers with specific requirements for copying management can enhance the conditions in line with their wishes. You might have the choice of writing your own data switch routines utilizing BAdI (enterprise addin) methods. For creating copying routines, you can use the CRM_COPY_BADI.

You want copying management for processing observe-up documents.

  1. Copying control for transaction types is mandatory
  2. Copying management for item categories is mandatory while you wish to copy products (objects) right into a observe-up document.
  3. The „definition of item category determination when copying“ is optionally available and can be used underneath particular circumstances.
Copying control may be maintained in Customizing:
  1. SAP Implementation Guide
  2. Buyer Relationship Management
  3. Transactions
  4. Basic Settings
  5. Copying Control for Business Transactions
When processing comply with-up paperwork, the doc movement is updated.From the document move it is potential to navigate to linked business transactions. Additionally it is attainable to navigate to the SAP R/3 system (e.g. to the delivery document).

In SAPGUI doc movement

  1. the Detail View only reveals the quick preceding/succeeding paperwork
  2. the Overview exhibits all paperwork that are linked

In the Individuals-Centric UI tab pages are used to show the doc flow.Document move tab pages are available on header and merchandise level. Navigation to linked CRM business transactions is possible.

  1. In SAP CRM it is potential to take care of textual information for a quantity of objects, e.g. Business Partner
  2. Product
  3. Product Catalog
  4. Enterprise transaction (header and merchandise)
  5. Billing paperwork (header and merchandise)
  6. Texts could be maintained language-dependent
The definition of text determination is much like that of pricing. First you outline several textual content types.After that you define the supply texts of your textual content types inside access sequences; for instance, if no sales text is on the market, the system should show the basic text.According to what you are promoting scenario, you combine some text sorts in text determination procedures.These texts are routinely displayed in paperwork or may be entered.

Text objects and textual content sorts are defined in Customizing:
  1. SAP Implementation Information
  2. Customer Relationship Administration
  3. Primary Functions
  4. Textual content Management
  5. Define Text Objects and Textual content Sorts
  6. Textual content willpower procedures and entry sequences are defined in Customizing: SAP Implementation Information
  7. Buyer Relationship Management
  8. Fundamental Functions
  9. Text Administration
  10. Outline
  11. Text Determination Process
Content material Management is a function of the SAP Internet Software Server, which is utilized in SAP CRM in various areas, for instance, for business partner- and product master data. In the business transaction, the assorted Content material Management functions are available on header and item level.Integration with the ArchiveLink performance: In Customizing, you'll have the option to define which documentation for the appropriate business objects is linked to the Archive Link functions. To do this, in Customizing, select the Internet Utility Server ,SAP Net Utility Server , Foundation Services , ArchiveLink.

Additionally, you'll give you the chance to create ArchiveLink documents from Content Management.The exchange of Content Administration documents with CRM Mobile is possible. Usage of filter profiles means that you simply can specify which paperwork are to be transferred to the Mobile Client.

Functions for Content Management are on the Paperwork tab page.Special capabilities in SAP GUI: Sending paperwork: You can ship business partners documents linked to a enterprise transaction, for instance, by e-mail or fax.Creation of non-public- and customarily seen notes at doc degree

System status: Status that may be a status set by the system, which informs the consumer that the system has executed a particular business transaction on an object. You'll find a way to only influence this standing when you execute a business transaction that changes the system status.
?? Nevertheless, there are additionally some system statuses in CRM that the person can set or reset as he needs, for example, Do not distribute. These statuses are outlined in the CRMC_STATUS_PROC table.Standing that you set, that you would give you the chance to create as additional info to the present system status. You outline a consumer status in a Status Profile that's created in Customizing for business transactions. You probably can outline and activate as many person statuses as you wish. A standing profile can then be assigned to a transaction kind (header status) and/or merchandise category (merchandise status).

Person statuses let you prolong the control of business processes managed by the system status. You can set and delete person statuses manually throughout enterprise processes.The header status is impartial of the item status. One exception is the standing Completed. If all gadgets have the standing Accomplished, the header standing can also be set to Accomplished .Depending on the enterprise transaction there could be R/three Transfer and R/3 Status data available (e.g. in a sales order).Setting a consumer status can affect the system status.

In SAP GUI you'll have the opportunity to show a standing analysis. If you need to investigate an issue individually, and would like to know for instance why the system does not show a selected status for setting, you'll have the option to use the standing analysis to call up a technical analysis function.User statuses are outlined in standing procedures or standing profiles. In standing profiles you can do the following:
  1. Define the sequence in which user statuses could be activated
  2. Outline initial statuses
  3. Permit or prohibit sure business transactions
  4. You have to assign not much less than one object sort, reminiscent of CRM Order Header, to the status procedure.
You'll find a way to define a standing profile in Customizing: SAP Implementation Information You can make settings for the incompleteness test in enterprise transactions. You presumably can outline when a enterprise transaction ought to be thought-about incomplete in the system and what message kind the system should situation to the appliance log during information processing. You probably can prohibit the incompleteness examine to particular person transaction sorts and to particular person enterprise partners.

The scope of the examine can differ for every object. For example, the system checks completely different fields in a sales order than it checks in an opportunity.You may arrange incompleteness in Customizing.

To arrange the incompleteness examine, carry out these steps:
  1. Outline an incompleteness group for business transactions and items.
  2. Define an incompleteness verify for enterprise partners. In the business partner grasp knowledge, assign the required business companions to the incompleteness group within the Gross sales Area Knowledge on the Sales tab.
  3. Assign transaction varieties to the incompleteness groups. In the incompleteness check, the same conditions are valid for all transaction types with the same incompleteness group assigned.
  4. Assign item categories to the incompleteness groups. In the incompleteness check, the same circumstances are valid for all merchandise classes with the same incompleteness group assigned.
  5. Outline the incompleteness procedures which would possibly be valid for the various sub objects of a transaction, for instance, SALES for sales information or PRODUCT_I for product information at merchandise level. In an incompleteness procedure, you'll have the ability to group fields that you simply wish to test for completeness. If you don't enter knowledge in any of those fields in the business transaction, the transaction is taken into account incomplete. For every discipline in the process, you could also outline whether or not the message issued to the applying log during data processing needs to be a warning or an error message.
  6. Assign the incompleteness teams to the incompleteness procedures. This specifies the enterprise transactions during which checks are carried out. If you happen to assign an incompleteness group for business companions to an incompleteness procedure, the system carries out the check only for these enterprise partners to whom the incompleteness group was assigned. If you happen to create a transaction utilizing that transaction sort and enterprise associate, however, the incompleteness process is legitimate solely the business accomplice, that is, the system doesn't display a mixture of each procedures as incomplete.Only the fields from the incompleteness process for the business associate are displayed as incomplete.
In Customizing, you probably can deactivate the change doc replace for transaction types. Subsequently go to the details of a transaction kind and examine the flag No Change Documents. In SAP GUI you can display the change paperwork by selecting Extras ? Change Documents.Even transactions with errors will be saved in the SAP CRM system. As soon as saved, the transactions are obtainable for additional processing.Transfer to SAP R/3 is possible solely after the processing of the gross sales transaction is complete. From the distribution status of the transaction within the SAP CRM system, you presumably can see whether or not the transaction is related for distribution and, if that's the case, whether it was efficiently distributed to SAP R/3.You can verify for profitable supply into SAP R/3 by viewing the delivery status in the order in SAP CRM.After successful billing, the related billing status is set.

Related Posts

SAP CRM Business Transactions
SAP CRM marketing Management Campaign

No comments :

Post a Comment