2

Click here to load reader

1910803 - LORD- Variant Determination for ERP Sales Documents in SAP CRM

Embed Size (px)

Citation preview

Page 1: 1910803 - LORD- Variant Determination for ERP Sales Documents in SAP CRM

8/9/2019 1910803 - LORD- Variant Determination for ERP Sales Documents in SAP CRM

http://slidepdf.com/reader/full/1910803-lord-variant-determination-for-erp-sales-documents-in-sap-crm 1/2

SAP Note 

Header Data

Symptom 

You use the LORD framework to create or change ERP sales documents in SAP CRM. In the sales documents, you use configurable materialsand you have activated the variant determination/replacement.

However, during the variant replacement, the system does not behave as expected. Examples of this are:

1. Even though the system does not find a variant in IPC, the system executes a variant replacement when you leave the IPC.2. In the IPC, you click "Accept" for one of the product variants found. Then, the system issues a message informing you that you have switched

to product variant X. Even so, the system does not transfer the product variant X to the sales document item when you leave the IPC. There,the system still displays the configurable material you have entered originally.

3. In the IPC, you do not click "Accept" for any of the product variants found. Even so, the system still executes a variant replacement when youleave the IPC; the sales document item now contains a product variant rather than the configurable material that was originally entered.

Other Terms 

Product variant, material variant, variant,variant determination, variant replacement, variant substitution, LORD

Reason and Prerequisites 

The "Accept" button displayed in the IPC beside the product variant found does not immediately trigger a variant replacement in this scenario.here, it only serves to transfer the evaluation of the selected variant to the evaluation of the configurable material. (For example, certaincharacteristics can be excluded from the variant determination so the system can still find variants even if the evaluation that has been executed forthe configurable material does not yet match the evaluation of the variant.)

The actual variant replacement is executed by the LORD framework in ERP in the background when you leave the IPC.

First, a variant determination is executed again based on the characteristic valuation performed in IPC. It is based on the ERP configurationmodel. If the system finds a variant, the variant replacement is executed in accordance with the item type Customizing set in ERP SD (Actionmaterial variant indicator, TVAP-LTYPA, for more detailed information, refer to, for example, SAP Note 901452).

However, here, the system behavior for ERP sales documents in SAP CRM differs in certain aspects from the system behavior in transactionsVA01 and VA02:

l

 As opposed to VA01/VA02, the user cannot process any dialog boxes for the selection of the variant in the LORD framework because theLORD processes are background processes. in other words, even when the setting "1 Note (only in Append)" and "3 Note (Append andchange)" are used, the user does not have the option of selecting whether a variant is to be replaced or not. If a variant exists, it isautomatically used for the substitution.

l  As opposed to transactions VA01/VA02, in ERP sales documents in SAP CRM, the configuration is only run in the background when an itemis first created. In other words, when you create the item, the system only only sets default values that may exist or characteristic valuesdetermined via dependencies. To store a characteristic valuation that differs from this norm, you have to explicitly call the configuration/theIPC for an existing item. However, this is a proposal for a change, therefore, the system does not execute a variant replacement with thesettings "1 Note (only in Append)" or "2 Replace configurable material (only in Append)" when the configuration is explicitly called after theitem is first created.

Solution 

The behavior described above is the standard behavior in accordance with the configuration models and Customizing settings maintained in the

systems.

The examples for unexpected system behavior listed under "Symptom" can be explained as follows:

1. The variant determination in IPC leads to a different result than the ERP variant determination. The reason for this is usually to be found ininconsistencies between the configuration models in CRM and ERP. In addition, such a symptom may occur, if the plant-specific variantswere maintained correctly for the ERP variant determination but no relevant cross-plant variants have been maintained for the variantdetermination in IPC. Therefore, check your configuration models and variants in ERP as well as in CRM and ensure that they are consistentin both systems. For more information, refer to the online documentation .

1910803 - LORD: Variant determination for ERP sales documents in SAP CRM  

Version  2 Validity: 10.09.2013 - active Language  English

Released On  10.09.2013 09:01:16

Release Status  Released for Customer

Component  SD-SLS-API SD API Interface, LORD

CRM-BTX-ERP CRM UI for ERP Sales Documents SD-SLS-GF-VA SD BOM, Variant processing

Priority  Recommendations / Additional Info

Category  Consulting

Other Components

Page 2: 1910803 - LORD- Variant Determination for ERP Sales Documents in SAP CRM

8/9/2019 1910803 - LORD- Variant Determination for ERP Sales Documents in SAP CRM

http://slidepdf.com/reader/full/1910803-lord-variant-determination-for-erp-sales-documents-in-sap-crm 2/2

 

2. This symptom may occur when you use the settings "1 Note (only in Append)" or "2 Replace configurable material (only in Append)". Ascalling the configuration/the IPC is a change process, the system does not execute a variant replacement, even if a variant exists for theevaluation that was performed.

3. You have chosen one of the settings "3 Note (Append and change)" or "4 Replace configurable material (Append and change)". With thesesettings. the system executes a variant determination in ERP in accordance with the characteristic valuation performed in IPC. If the systemfinds a variant during this process, it automatically replaces the configurable material with this variant.

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes 

1885434 Sales UI: Variant determination 

1236015 ERP Sales Documents in SAP CRM 

901452 Configuration & bill of material - Item category Customizing 

900732 Variant matching does not work