/$sync --> Reiniciar la memoria interna
rsrz --> v_rsrzglobv
bd61 --> punteros ALE (check para subida delta)
domingo, 9 de octubre de 2011
Tables BW
Queries:RSRREPDIR, RSZELTDIR,RSZELTTXT
Workbooks: RSRWBINDEXT
RSTSODS
V_TBDLS
RSADMINA
RREX_VARIABLE_EXIT
ODS Request:
RSICCONT
RSMONICDP
RSODSACTUPDTYPE
RSODSACTREQ
Favoritos usuarios:
SMEN_BUFFC
Workbooks: RSRWBINDEXT
RSTSODS
V_TBDLS
RSADMINA
RREX_VARIABLE_EXIT
ODS Request:
RSICCONT
RSMONICDP
RSODSACTUPDTYPE
RSODSACTREQ
Favoritos usuarios:
SMEN_BUFFC
Botanita, Botana, SAP, BW, Ponte Carreira
ABAP: Tables
Módulos de funciones
DAYS_BETWEEN_TWO_DATES
GET_TAX_PERCENTAGE
RSAP_BIW_DISCONNECT
RSAR_ODS_API_DEL
L_MM_MATERIAL_READ
MB_SELECT_SD_SCHEDULED
MB_ABD_PURCHASE_ORDER
ME_READ_HISTORY
'UMC_TODO_SEND_EMAIL'
GET_TAX_PERCENTAGE
RSAP_BIW_DISCONNECT
RSAR_ODS_API_DEL
L_MM_MATERIAL_READ
MB_SELECT_SD_SCHEDULED
MB_ABD_PURCHASE_ORDER
ME_READ_HISTORY
'UMC_TODO_SEND_EMAIL'
Botanita, Botana, SAP, BW, Ponte Carreira
ABAP: Módulos de funciones
viernes, 2 de septiembre de 2011
Bisiesto
clear: mes, year, dia, yearmes.
year = COMM_STRUCTURE-CALMONTH(4).
year = year + 1.
mes = COMM_STRUCTURE-CALMONTH+4(2).
dia = COMM_STRUCTURE-CALDAY+6(2).
if mes eq '02'.
concatenate year mes into yearmes.
PERFORM CALCULATE_ULTIMO
USING yearmes
RECORD_NO
RECORD_ALL
SOURCE_SYSTEM
CHANGING RESULT
RETURNCODE.
else.
concatenate year mes dia into RESULT.
endif.
year = COMM_STRUCTURE-CALMONTH(4).
year = year + 1.
mes = COMM_STRUCTURE-CALMONTH+4(2).
dia = COMM_STRUCTURE-CALDAY+6(2).
if mes eq '02'.
concatenate year mes into yearmes.
PERFORM CALCULATE_ULTIMO
USING yearmes
RECORD_NO
RECORD_ALL
SOURCE_SYSTEM
CHANGING RESULT
RETURNCODE.
else.
concatenate year mes dia into RESULT.
endif.
Cuando se copia un mandante respecto a otro se pueden copiar:
Datos
Customizing
Usuarios
Todo lo que es workbench es independiente de mandante.
Si machacamos los usuarios, se borran todos los usuarios no coincidentes que estaban en mandante destino y no en el mandante origen
Si los roles de los usuarios eran diferentes se pierde todo lo que tenían en el mandante destino y pasan a tener todo lo que tenían en el mandante origen.
Datos
Customizing
Usuarios
Todo lo que es workbench es independiente de mandante.
Si machacamos los usuarios, se borran todos los usuarios no coincidentes que estaban en mandante destino y no en el mandante origen
Si los roles de los usuarios eran diferentes se pierde todo lo que tenían en el mandante destino y pasan a tener todo lo que tenían en el mandante origen.
Botanita, Botana, SAP, BW, Ponte Carreira
Copia de mandantes
viernes, 22 de julio de 2011
0HR_PY_1 extractor is not runnig with delta mode
Actually, there are difference when the 0HR_PY_1 extractor is run in
init/delta mode or FULL mode. Please refer to the information provided
from our developer:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In full mode, the status of this payroll records, which is maintained
for each payroll area in transaction PA03, is NOT considered at all.
This is different in init/delta runs. In this case, we the extractor
needs to decide, whether payroll results can be considered to be
final and are not being overwritten by new payroll runs for the
same period.
This means, as long as a certain payroll period is not closed for
a given payroll area, results which are already on the database
for this period are not getting extracted, as there is the
possibility, that they are getting overwritten again by
a payroll run for the same period.
Once the payroll period is closed in PA03, the results for that
period are considered to be final, and thus extraction will
extract them. You will need to check the status of the payroll
areas in PA03.
init/delta mode or FULL mode. Please refer to the information provided
from our developer:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In full mode, the status of this payroll records, which is maintained
for each payroll area in transaction PA03, is NOT considered at all.
This is different in init/delta runs. In this case, we the extractor
needs to decide, whether payroll results can be considered to be
final and are not being overwritten by new payroll runs for the
same period.
This means, as long as a certain payroll period is not closed for
a given payroll area, results which are already on the database
for this period are not getting extracted, as there is the
possibility, that they are getting overwritten again by
a payroll run for the same period.
Once the payroll period is closed in PA03, the results for that
period are considered to be final, and thus extraction will
extract them. You will need to check the status of the payroll
areas in PA03.
Botanita, Botana, SAP, BW, Ponte Carreira
HHRR
domingo, 15 de mayo de 2011
Note 1534315 - How to analyse Generic BI data extraction errors
Botanita, Botana, SAP, BW, Ponte Carreira
Truquis BW
Suscribirse a:
Entradas (Atom)