SAP CRM Sales Order Administration

SAP CRM Sales order administration Solely sales orders which are full and without errors, and that wouldn't have a distribution lock, are routinely transferred from CRM Enterprise to SAP R/3.Through the creation of gross sales transactions within the Net shop in Internet Sales, the shop is used to create the sales order and the bodily document itself is stored in CRM Enterprise (as is the order achievement in OLTP). The status replace on the Web can solely be viewed after successful supply of the sales order. Sales orders that are created over the Web or within the Interaction Middle may be further processed in CRM.It will be created by approach of:
  1. Interplay Center Web Consumer; Interaction Middle Win Client
  2. Portal
  3. Web Sales (E-Commerce)
  4. SAP R/3
  5. Direct creation in CRM
  6. Cellular Gross sales (laptop computer)
  7. Handhelds
Sales orders with errors, in addition to orders for which an extended textual content was written in Internet Sales, should be processed in the locator by manner of the Worklist tab page. In sales transactions, you could also make modifications to gross sales orders if the transfer to OLTP-R/3 has already taken place (depending on standing and availability of the methods).The doc stream in CRM displays the replicated gross sales order, as properly as subsequent R/3 paperwork (for instance, supply, goods challenge).

If an change has to take place between CRM Enterprise and SAP R/three, there have to be a transaction type in CRM Enterprise with the same name as a gross sales document sort in SAP R/3. The identical merchandise categories should be maintained in both systems.Moreover, settings for number range and item quantity project have to be matched between CRM Enterprise and SAP R/3.You'll give you the chance to entry the relevant settings inside the IMG:
  1. CRM: Buyer Relationship Management ® Transactions ® Primary Settings ® Outline Transaction Types.
  2. R/3: Sales and Distribution ® Sales ® Sales Paperwork ® Gross sales Doc Header ® Outline Sales Document Types.
In order that the transfer between CRM Enterprise and SAP R/three can happen, gross sales transactions must fulfill the next conditions:
  1. The transaction incorporates not much less than one item. Header knowledge from enterprise transactions is not transferred alone.
  2. You have got saved the transaction and it doesn't comprise errors.
  3. You haven't set the Distribution Lock.

Transactions with errors will additionally be saved in CRM and can be found for additional processing.Switch to SAP R/3 is simply possible when gross sales transaction processing is complete. From the distribution status of the transaction within the CRM system, you may see whether the transaction is related for distribution and, in that case, whether or not it was successfully distributed to SAP R/3.You'll have the opportunity to test for successful supply into SAP R/3 by viewing the supply standing in the order in CRM.After successful billing, the related billing standing is ready and the document move is updated.You make the settings for the enterprise transaction varieties in three steps:
  1. Define transaction varieties: Here, you define necessary management attributes, such as the main business transaction kind, textual content willpower process, accomplice dedication procedure, standing profile, the organizational knowledge profile, and the number vary assignment.
  2. Assign business transaction category:A business transaction can be assigned to at least one or several business transaction categories. Only sure mixtures of enterprise transaction categories are possible. You choose the extra enterprise transaction classes depending on the main enterprise transaction.You have to maintain Customizing settings for the header stage for every business transaction class you've got assigned.
  3. Customizing at header level:Varied settings could be made here, depending on the business transaction category.

You make the settings for the item categories in three levels:

  1. Outline item classes :Right here, you define important control attributes, such as item object type, text determination procedure, companion willpower process, standing profile, motion profile, and the number range assignment.
  2. Assign enterprise transaction category :An item class could be assigned to a minimum of one or a quantity of business transaction categories. Only particular mixtures of business transaction categories are possible.It's worthwhile to preserve Customizing settings for merchandise level in the transaction for each enterprise transaction category you assign.
  3. Customizing at item degree:Right here, you may set, for example, whether the item is relevant for billing (billing is finished in SAP R/3), or whether pricing is lively or inactive.
You'll have the option to decide at item class stage (Customizing) whether or not or not an item is related for CRM Billing. It's additionally attainable to specify the sort of billing.The next eventualities can be found:

  1. Order-related billing The full order quantity is billed Used for instance for credit memo requests and billing request gadgets
  2. Supply-related billing:The delivered quantity is billed Used,for example, for sales orders with deliveries.Trace: The billing relevance of the corresponding SAP R/3 merchandise category should be Q or R.

Related Posts

SAP CRM Organizational management
SAP CRM Territory Management
EDI Tools for SAP
EDI performance factors
SAP ABAP EDI out bound process scenarios examples

No comments :

Post a Comment