Mostrando las entradas con la etiqueta CRM. Mostrar todas las entradas
// //

SAP signature management de DocuSign

SAP gestiona documentos firmados digitalmente con DocuSign.

Permite que las personas dentro y fuera de su organización accedan electrónicamente, firmen y envíen documentos importantes a cualquier lugar, en cualquier momento y en cualquier dispositivo con la aplicación SAP Signature Management de DocuSign, una solución segura basada en estándares.

SAP e-signature management de DocuSign - Consultoria-SAP


Leer más ...
// // 4 comentarios

Descarga Directa SAP TCRM10 y TCRM20

SAP CRM TCRM10 TCRM20

SAP Customer Relationship Management (SAP CRM), los manuales oficiales (de instructor) en ingles, listos para descargar y darte todo el conocimiento sobre esta tecnología. SAP CRM está dentro de lo que sería un módulo funcional de SAP, procesos de negocios y aplicaciones.

Dejo el contenido de los manuales (TCRM10_EN_Col92_FV_Inst_Ltr.pdf y TCRM20_EN_Col92_FV_Inst_Ltr.pdf ) a continuación:

TCRM10 Contents

Course Overview  
Course Goals 
Course Objectives

Unit 1: Introduction to SAP CRM 
What is CRM 
SAP CRM Overview
Case Study  

Unit 2: Basics and Architecture 
Overview of SAP CRM Architecture 
Channel Architecture  
Introduction to the CRM WebClient User Interface 

Leer más ...
// // 1 comentario

Debug Customer / Vendor

Debug Customer/Vendor<->BP Synchronization

This blog shows the way for debugging Customer/Vendor<->BP synchronization process using the Class CVI_MAPPER as an entry point for the debugger.

Imagine that we are synchronizing Customer to BP. And we have a problem there: when we remove the bank data from the Customer, the change is not synchronized on the BP. So we have a synchronization issue, because our BP has incorrect data.

CVI_MAPPER is a class that allows us to stop the debugger on the mapping process between Customer and BP (This is also valid for all the synchronization types Customer<->BP or Vendor<->BP).

So we can open SE24 and Display the details of CVI_MAPPER class:

There we can see a lot of interesting methods we can use for stopping the debugger and check why our bank data is not removed on the BP…

For us the most important methods are the following ones:

MAP_BPS_TO_CUSTOMERS

MAP_BPS_TO_VENDORS

MAP_CUSTOMERS_TO_BPS

MAP_VENDORS_TO_BPS

On our example we will have a look to method MAP_CUSTOMERS_TO_BPS, and we will put a breakpoint on the following code:

On this code, the customer data is filled on <customers> variable and the BP data is returned on ls_partners variable.

So we start XD02 transaction and open our Customer:

Then we open the “Payment transactions” tab and remove the existing Bank Details:

We can proceed to the saving process:

The debugger will stop on our breakpoint:

We can press F5 to go inside this method to see if we can find where the mapping of the bank data is located:

We found one method named “map_customer_bankdetails”, where the system maps the customer bank data to the BP bank data. If we enter using F5 to the method and see that in the last line, the variable LS_BP_BANKDETAILS is returned.

We can see the content and see that the problem is that the bank details of the customer are not removed!! So the problem is on the class responsible to extract the data from memory to do the synchronization: CMD_EI_API_EXTRACT or VMD_EI_API_EXTRACT. We can search notes for those classes.

This method can be used also for other kind of issues, like errors on MDS_PPO2, if you want to see via coding why the error is got. Those errors are returned usually on these methods.

Ivan Martin Marra SAP support consultant CRM

Reblogged from SDN Sap Blogs.

Leer más ...