Wednesday, October 24, 2012
Saturday, October 6, 2012
Friday, September 21, 2012
Deactivate an enhancement set in the WebUI for testing purposes
Deactivate an enhancement set in the WebUI for testing purposes
2) From CRM7.0 SP3: note 1311966
User parameter WCF_IGNORE_ENHANCEMT to value 'A' in transaction SU3.
This will disable all customer enhancements in these areas:
o Enhancement Sets
o UI Configurations
o UI Personalizations
o Field labels in text repository
o Changes in Design Layer (design objects and assignments)
Keep in mind to remove this user parameter once you are done with the
analysis!!!!
Wednesday, September 19, 2012
Tax info replication from ECC to CRM for products
Pasted from <http://scn.sap.com/thread/1985450>
This error refers to tax customizing so you should check what assingments you have in R/3 and then replicated on CRM. You can use transaction CRM_TAXCUST_VALIDATE to check the tax errors both in customers and materials. Then, according to the missing entries you will see on the transaction I told, you should check in R/3 tables TSKM and TSTL (used for materials). In table TSTL you have all the customizing made on R/3 transaction OVK1 and in table TSKM you´ll find the customizing made on transaction OVK4. The entries made there for your country should be the same ones made in CRM. The customizing path is the following: SPRO>CRM>Basic Functions>Taxes>Basic Settings>Tax Types and Tax Groups>Assing Tax Groups to SAP ECC Tax Classifications (Products) Here you have to enter the combination of: COUNTRYTAX TYPETAX GROUPTAX SEQTAx CL (which you should be able to fullfill after checking the R/3 tables
Pasted from <http://scn.sap.com/thread/1985450>
Saturday, July 14, 2012
Thursday, June 21, 2012
FETCH and OPEN CURSOR Analysis
Wednesday, June 6, 2012
Recommended approaches of defaulting values for fields in ECC which doesn’t exist in CRM for customers.
Friday, April 6, 2012
Friday, March 23, 2012
Tuesday, February 7, 2012
Sunday, January 29, 2012
Thursday, January 26, 2012
Sunday, January 22, 2012
Wednesday, January 18, 2012
Tuesday, January 17, 2012
BADI CRM_ORDER_AUTH_CHECK
1. Authorization BADI CRM_ORDER_AUTH_CHECK->CRM_ORDER_ALTERN_AUTH_CHECK
This allows for skipping standard authorization checks
2. Std Check - Own document, user owns a role
3. Std Check - User assigned to same Org level of document
4. Std check - territory(if enabled in customizing)
5. Std check - Business object type (Eg. BUS2000111)
6. Std check - Process type
7. Std check - Sales/div channel
8. Authorization BADI CRM_ORDER_AUTH_CHECK->CRM_ORDER_ADD_AUTH_CHECK
This allows for additional checks if user has passed all std checks
Following the sequence 1 to 7, if any of the step OKs the user, the rest of the steps are skipped. The step 8 is still carried out if the user has passed. So, you may want to analyze your situation further. Maybe, you have to implement the BADI method mentioned in step 8 and do a further check based on user role. The CL_CRM_UI_PROFILE->Get_profile will give you the PFCG role.
Saturday, January 7, 2012
CRM Web UI Workflow Navigation to ERP Sales Orders
SAP Developer Network SAP Weblogs: CRM |
CRM Web UI Workflow Navigation to ERP Sales Orders Posted: 06 Jan 2012 12:11 PM PST |