Mostrando las entradas con la etiqueta Tutorial. Mostrar todas las entradas
// // 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 ...
// // Escribe un comentario

Ampliar ayuda para MatchCode

En muchas ocasiones, las ayudas de busqueda estandar de Sap (Matchcode), a las que accedemos como ayuda para completar los valores de los campos pulsando la tecla de función F4, son insuficientes para nuestras necesidades o no tienen en cuenta cosas tan obvias como no incluir registros que tienen peticiones de borrado.
Para estas ocasiones, tenemos la posibilidad de definir nuestras propias ayudas de búsqueda (Z) e incluirlas como una ayuda adicional en las ayudas estandar. Las ayudas estandar suelen ser ayudas complejas que incluyen varias ayudas simples, que podemos ir seleccionando según nuestras necesidades (en la imagen, podeís ver las ayudas de búsqueda disponibles cuando estamos dando de alta datos maestros de cliente a través de la transacción XD01).

Como ejemplos de ayudas de búsqueda que habitualmente se van a tener que definir en el sistema, tenemos:
  • Administración de personal: búsqueda por el segundo apellido, ya que es muy frecuente empleados con los mismos apellidos, y este tipo de búsqueda no esta incluido en el estandar.
  • Datos maestros: ayudas de búsqueda que excluyan registros con petición de borrado. Esto puede aplicar a proveedores, clientes, materiales, etc.
  • Busqueda por otros criterios: en muchas ocasiones nos puede interesar buscar por otros criterios que no son estandar, campos de cliente u otros campos estandar que andan perdidos en los datos maestros pero por los que nos interesa realizar búsquedas.
  • Ayudas personalizadas: también podremos incluir ayudas que ataquen a tablas Z o a vistas de datos estandar y tablas de cliente. Por ejemplo, en un sistema con control de imputaciones por cuentas contables, incluir una ayuda de búsqueda que nos indique, por cuenta contable, donde podemos imputar (tirando de tablas de cliente).
Leer más ...
// // Escribe un comentario

Agregar texto en el logon de SAP

Me pareció interesantísimo el artículo para la consultoría SAP en general, saber como modificar el log-on de SAP.
Creo que es importante para dejarle información de contacto (tal como voy a pasar a explicar) en la pantalla de acceso de todos los usuarios finales de SAP en la empresa.

Yo recomiendo que lean atentamente nuestro tutorial, y después accedan al sistema (recomiendo en ingles), para hacer los cambios.

Paso por paso tenemos que hacer lo siguiente:

1. Entrar a SAP.
2. Ejecutar la transacción SE61.

Cambiar la siguiente configuración:

  • En “Document Class” ponemos “Generat Text”
  • El “Language” lo podemos cambiar, o no. Yo dejo English.
  • En “Name” ponemos ZLOGIN_SCREEN_INFO

Después de eso, hacemos clic en el botón “CHANGE”.

Agregar texto personalizado en Logon de SAP

3. Aquí tenemos que agregar la información que queremos que aparezca:

Agregar texto personalizado en Logon de SAP

4. Hacemos “CTRL+S” y Activamos con “CTRL+F12” cuando hayamos terminado.

5. Salimos de SAP (cerramos todo, podemos usar “/nex” y darle enter)

Cuando volvamos a querer loguearnos en SAP, veremos la información que pusimos así:

Agregar texto personalizado en Logon de SAP

Y eso es todo.

Espero que sepan aprovecharlo.

Saludos, ^Osw.



Imágenes y fuente de: FreeSapTutorial

Leer más ...
// // 2 comentarios

Dummy Profit Center Creation in SAP

To create the dummy profit center for the controlling area in SAP.
The dummy profit center is updated in data transfers whenever the object to which the data was originally posted (cost center, order, and so on) is not assigned to a profit center.
This ensures that the data in Profit Center Accounting is complete. The data can be sent later on the dummy profit center to the other profit centers using assessment or distribution.

The dummy profit center’s master record is created using this special transaction ( KE59 ). Normal SAP transaction to create normal profit center is KE01 transaction. To change or display it, use the normal profit center maintenance functions ( KE52KE53 transaction ).
The name of the dummy profit center is displayed in the controlling area settings for Profit Center Accounting.
Leer más ...
// // Escribe un comentario

How to Send a System Message

Imagine that you’re working configuring a certain SAP module, touching several tables and configuration spots. Sometimes it might happen that someone else is maintaining the same table that you need access. This standard Function Module could be useful in these cases, since you might not know an alternative way to contact the user locking the table or other SAP object. Since the system will display who is locking the table, you will know for whom to send the message.
Here’s how it goes.

Trying to access the table

When trying to maintain a certain table, the user will receive the following warning:

Sending a system message using a standard SAP function module

Once you’ve identified the user, access SE37 – assuming you have permission! In SE37 call SAP standard function module TH_POPUP.

<!--more>
Fill in the following input parameters:
- CLIENT: the system client on which you’re working on. If you don’t know this, take a look at the lower right status bar;
- USER: the user for which you want the message to be delivered;
- MESSAGE: the text message you want to deliver to the user;
- MESSAGE_LEN: allows you to define a message length. Leave it empty;
- CUT_BLANKS: allows you to specify if you want to trim existing spaces. Leave it empty.
To submit the message just hit “Execute (F8)”

What the user receives

When you click on “Execute (F8)”, the destination user receives the following message as a pop-up:

This is just a simple system tool that can help you in a day to day basis, working with SAP.


Reblogged from Saplab.org
Leer más ...
// // Escribe un comentario

Custom transaction for Report Painter

In many organizations, the usage of transaction GR55 has been removed from end users and the usage of custom transaction for Report Painter report is preferred.

These transactions need to be added to roles & also transported via the SAP Transport system and go through change control.

One mistake is to create Variant Transactions that add another layer of objects to maintain and transactions that are not easily accepted by the end user community:

image003

The user will then have to navigate past the selection screen where the report group is selected.

image004

Another common mistake is that users create the transaction code with the SAP-generated program name of the Report Painter report.

image005

The users usually runs the report and via the menu path system status identifies the SAP generated report name, such as GP4D9W908VD93NG59JGEC5C4HE3200 in the development system or in the productive system as GP4D9W908VD93NG59JGEC5C4HE3400. Both program names look identical except for the last 3 digits, which represent the client in which the report was generated.

Because you don’t have control over the SAP-generated program name, you run into problems when the user tries to execute the program and a short dump may occur or the system may tell the user that the program doesn’t exist.

The right approach is to create a Parameter Transaction, map this transaction to the necessary objects in SU24 so that you can make sure that you won’t run into any authorization issues when the user runs the reports.

To create a custom transaction, you need to use transaction SE93 in the development client where your program development & configuration takes place.

Enter a transaction with the naming convention that your organization has issued and select the ‘create’ button:

image006

Enter a short description (according to naming standards of your organization) and select the option ‘Transaction with parameters’:

image007

Enter transaction ‘START_REPORT’ as shown below (1) and select the ‘Skip Initial Screen) (2):

image008

In the lower section, enter Screen Field D_SREPOVARI-REPORTTYPE with the value RW for Report Writer and D_SREPOVARI-REPORT for your report name. If you should have extended a extended report name, you also can add this screen field with the appropriate value D_SREPOVARI-EXTDREPORT to the list of screen fields.

image009

After saving the transaction, the system asks you for a package & transport request. Follow the development standards & instructions from your organization.

Once you have created the transaction, you need to make sure that it will be fully functional from a SAP Security standpoint. Use transaction SU24 to map the object S_Program to the transaction you have just created. The authorization group is the name of the Library with the prefix of RW_. You can find out the library via the report group or by running a trace. (This is helpful if you did not create the report and don’t know what library the developer was using).

image010

If you want to run the authorization analysis via ST01, you can find out easily what the values for S_Program should be:

image011

Once you have identified the objects & values, you can then map the object to the transaction with transaction SU24:

image012

Add all objects needed to run this report (you can find out the objects via your trace analysis):

image013

Switch the indicator to check/maintain:

image014

Enter the values according to your findings

image015

Don’t forget to double-check the values. You may want to make selections regarding on how the user can run the report according to your company guidelines and development standards:

image016

When the SAP Security Administrator maps the newly created transaction to a role, the objects needed for this transaction will be automatically pulled into the role:

image017

Depending on your SAP Security setup, the values of the individual authorizations for Report Writer may be more granular or with access to a broader area.


Reblogged from home4sap.com

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

Manuales HR

Sap RH es Recursos Humanos, lo que en Ingles SAP denomina: ERP HCM (HR)

El curso de Gestión y administración en HCM I (THR10) es el primer módulo presencial de los cursos de formación SAP Consultant en HCM. Tras una
introducción inicial al módulo HCM, aprenderá las funciones más importantes de
las áreas de gestión del personal y de la estructura de la empresa. Se incluye
una explicación de los escenarios básicos, seguida de un ejercicio práctico en el
sistema. Con esta información, se cubren las áreas de Gestión de tiempos y Datos
maestros de HR. El curso se cierra con una explicación de las diferentes opciones
de evaluación dentro y fuera del sistema mySAP HCM.
El curso de Gestión THR12 II es el segundo curso del control de formación de
SAP Consultant (Consultoría SAP) en HR. En cuanto haya completado el curso
de e-learning sobre la visión general de Solution Manager, durante la primera
semana aprenderá sobre el cálculo de nóminas de forma más detallada. Durante
la segunda semana, aprenderá más sobre la gestión de la organización. Entonces
podrá editar su primer proyecto.
Los manuales HR en español están disponibles a través de este artículo:
Manuales SAP HR Español.

Más info sobre SAP HR



Otros artículos de interés SAP


Saludos!
Leer más ...