ASSIGN_BASE_TOO_SHORT in DBPNPF03 (SAPDBPNP)
Hi,
I am getting Short Dump in this Program - ASSIGN_BASE_TOO_SHORT in DBPNPF03 (SAPDBPNP).
Kindly advise me what I have to do for this one. Is there any SAP Note available for this Dump. Also, I have checked the SAP Note. There is no SAP note specific to this Short Dump for this program.
Kindly check the SAP Message below.
<i>The source field must at least be as long as the structure.
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove the error.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ASSIGN_BASE_TOO_SHORT" " "
"SAPDBPNP" or "DBPNPF03"
"READ-INFOTYPE"</i>
Regards
Siva.
I am getting it too.
In SAPLHRMM...
Line 271: ASSIGN record TO <record> CASTING TYPE (tabname).
Still no solution to this?
Similar Messages
-
Dump in Zprogram using PNP logical database
shows the following error when I run a human resources program that uses logical database PNP.
ASSIGN_BASE_TOO_SHORT: The current ABAP program "SAPDBPNP" Had To Be terminated Because it has come across a statement Unfortunately That Can not Be Executed.
Anybody can help me understand why this problem occurs?You should have run a simple search on this before raISING YOUR OWN QUESTION. sEVERAL PEOPLE HAVE HAD the same or similar issue.
This thread quotes an oss note which might help you:
ASSIGN_BASE_TOO_SHORT in DBPNPF03 (SAPDBPNP) -
EREC - ASSIGN_BASE_TOO_SHORT error
Hi All,
At a client, they want to enlargen the data model of e-rec. This means adding fields to the standard SAP tables. For example HRP5125.
I created append structures to do this (best practice as far as I know). On activation, there are no problems.
I also enhanced the structure P5125 with the same fields. No error on activation.
Now, when i open the recruiter dashboard in the portal with all the query's (POWL), system tells me there is an error.
When I go to ST22 I get
ASSIGN_BASE_TOO_SHORT
in
RH_BASE_READ_INFTY_NNNN
Function Module
This happens on line
ASSIGN bnnnn TO <bnnnn_wa> CASTING TYPE (dbtab).
data declaration is
DATA : BEGIN OF bnnnn OCCURS 100.
INCLUDE STRUCTURE hrinnnn.
DATA : END OF bnnnn.
Does anyone know if I forgot something or how to solve it ?
ThxHey Jan,
You've mentioned that you enhanced both structure HRI51xx and P51xx, It's a bit confusing... The only structure you should change, is the CI_P51xx. The customer include is included in all others.
The dump ASSIGN_BASE_TO_SHORT means that the structure of the field symbol (dynamicaly defined in T77D-DBTAB), is bigger than the field structure (typed TABLE HRINNNN) .
HRINNNN is a generic structure which is composed of the key structure, the historic structure and the VDATA field which has a lenght of 1000 char. You may check how long is HRP5125, and if it's bigger than 1000chars you will get a dump. Did you add a string field ?
best regards
Hadrien -
Hi,
I'm calling HR_INFOTYPE_OPERATION and I'm getting a short dump with ASSIGN_BASE_TOO_SHORT error.
It's occuring on the line:
ASSIGN record TO <record> CASTING TYPE (tabname).
and it appears to be because the field symbol <record> is blank?
Can someone please explain what's going on and how I can sort this out?
Regards,
RobRuntime Error: ASSIGN_BASE_TOO_SHORT
Cause: The field symbol is structured and the field to be assigned is shorter than the structure.
refer the below link. Hope it helps.
Creation of record in 2001 using FM - HR_INFOTYPE_OPERATION -
HI EXPERTS!
CAN ANYBODY TELL ME HOW TO RESOLVE THIS RUNTIME ERROR ON EXECUTING TRANSACTION PC00_M40_CALC.
Runtime errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 07.08.2007 at 14:13:06
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"GET_SLAB_RATE" "(METHOD)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure
"GET_SLAB_RATE"
"(METHOD)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-04031: unable to allocate 4200 bytes of
shared memory ("shared pool","SELECT * FROM "T7INT1" WHERE...","library
cache","kkslpkp - literal info.")"
Internal call code.........: "[RSQL/FTCH/T7INT1 ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"CL_HRPAYIN_SLABRATES==========CP " or "CL_HRPAYIN_SLABRATES==========CM002 "
"GET_SLAB_RATE"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "hmsidev01"
Network address.......... "10.249.16.150"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "HMSIDEV01"
Database type............ "ORACLE"
Database name............ "DEV"
Database owner........... "SAPDEV"
Character set............ "English_United State"
SAP kernel............... "620"
Created on............... "Jun 13 2004 22:06:10"
Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
Database version......... "OCI_817_SHARE "
Patch level.............. "1511"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.."
SAP database version..... "620"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 100
User................ "IR1"
Language key........ "E"
Transaction......... "PC00_M40_CALC "
Program............. "CL_HRPAYIN_SLABRATES==========CP "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "CL_HRPAYIN_SLABRATES==========CP
" in "GET_SLAB_RATE".
The main program was "HINCALC0 ".
The termination occurred in line 12 of the source code of the (Include)
program "CL_HRPAYIN_SLABRATES==========CM002 "
of the source code of program "CL_HRPAYIN_SLABRATES==========CM002 " (when
calling the editor 120).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "GET_SLAB_RATE" "(METHOD)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "CL_HRPAYIN_SLABRATES==========CP ". Its source
code starts in line 1
of the (Include) program "CL_HRPAYIN_SLABRATES==========CM002 ".
Source code extract
000010 METHOD get_slab_rate .
000020
000030 DATA: wa_t7int1 TYPE t7int1,
000040 wa_t7int3 TYPE t7int3,
000050 slab_code TYPE t7int1-slcod.
000060 CLEAR: wa_t7int1 ,
000070 wa_t7int3 ,
000080 slab_code .
000090
000100
000110 * Select slab code from t7int1.
SELECT * FROM t7int1 INTO wa_t7int1
000130 WHERE sltyp = slab_type
000140 AND begda LT ref_date
000150 AND endda GE ref_date.
000160 MOVE wa_t7int1-slcod TO slab_code.
000170 ENDSELECT.
000180
000190 * Find out the rate for the salb code in which the income falls.
000200 SELECT * FROM t7int3 INTO wa_t7int3 WHERE slcod = slab_code ORDER BY
000210 hirge.
000220 IF wa_t7int3-hirge GE income.
000230 EXIT.
000240 ENDIF.
000250 ENDSELECT.
000260
000270 slab_rate = wa_t7int3-txval.
000280
000290
000300 ENDMETHOD.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 215
SY-TABIX 63 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 1 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM SY-TITLE Payroll Driver, India
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
16 METHOD GET_SLAB_RATE
CL_HRPAYIN_SLABRATES==========CP
CL_HRPAYIN_SLABRATES==========CM002 12
CL_HRPAYIN_SLABRATES
15 FORM STDDED03
HINCALC0
PCTAXIN0 564
14 FORM CALC_STANDARD_DEDUCTION
HINCALC0
PCTAXIN0 466
13 FORM FUINTAX
HINCALC0
PCTAXIN0 253
12 FORM AS-FUNKTION
HINCALC0
PCASFIN0 13
11 FORM ASLOOP
HINCALC0
RPCHRT09_ASLOOP 58
10 FORM MONATSABRECHNUNG
HINCALC0
RPCHRT09_MONATSABRECHNUNG 48
9 FORM RUECKRECHNUNG
HINCALC0
RPCHRT09_RUECKRECHNUNG 136
8 FORM MAIN
HINCALC0
RPCHRT09_MAIN 134
7 FORM %_GET_PERNR
HINCALC0
RPCHRT09 762
6 FORM FILL_INFOTYPE_TABLES_AND_PUT
SAPDBPNP
DBPNPF03 542
5 FORM PUTPERN
SAPDBPNP
DBPNPF03 470
4 FORM LOOP_AT_INDEX_AND_PUT
SAPDBPNP
DBPNPF01 996
3 FORM PUT_PERNR
SAPDBPNP
DBPNPF01 194
2 FORM %_ROOT
SAPDBPNP
SAPDBPNP 151
1 EVENT SYSTEM-EXIT
HINCALC0
20
Chosen variables
16 METHOD GET_SLAB_RATE
CL_HRPAYIN_SLABRATES==========CP
CL_HRPAYIN_SLABRATES==========CM002 12
SLAB_TYPE D
4
4
REF_DATE 20070331
33333333
20070331
INCOME ####Q#
00005991
0001153C
SLAB_RATE ########
00000000
0000000C
WA_T7INT1 0000000000000000
222233333333333333332
000000000000000000000
WA_T7INT3 ####### #######
222222000000022222220000000
000000000000C0000000000000C
SLAB_CODE
2222
0000
%_VIASELSCR #
0
4
<%_TABLE_T7INT1> ???
%_SPACE
2
0
SYST-REPID CL_HRPAYIN_SLABRATES==========CP
4454554544554445454533333333334522222222
3CF820199EF3C1221453DDDDDDDDDD3000000000
SY-XPROG SAPDBPNP
5454454522222222222222222222222222222222
310420E000000000000000000000000000000000
SY-REPID CL_HRPAYIN_SLABRATES==========CP
4454554544554445454533333333334522222222
3CF820199EF3C1221453DDDDDDDDDD3000000000
SY-XFORM %_ROOT
255445222222222222222222222222
5F2FF4000000000000000000000000
%_DUMMY$$
2222
0000
<%_TABLE_T7INT3> ???
15 FORM STDDED03
HINCALC0
PCTAXIN0 564
STD_DED_TAB Table[initial]
0000FFFD
0000FFFF
SY-TABIX 63
3000
F000
STD_PERCENT #####
00000
0000C
%_SPACE
2
0
SYST-REPID HINCALC0
4444444322222222222222222222222222222222
89E31C3000000000000000000000000000000000
SPACE
2
0
%_DUMMY$$
2222
0000
$ENDDATE 20070331
33333333
20070331
$PRE_DEDN_AMOUNT ####Q#
00005991
0001153C
$CALC_DEDN ########
00000000
0000000C
SY-REPID HINCALC0
4444444322222222222222222222222222222222
89E31C3000000000000000000000000000000000
SY ×#######?###?###########################
D000000030003000000000000000000000000000
70001000F000F000000000000000000000000000
... + 40 ###################################5###
0000000000000000000080000000000000003000
1000100010000000100040000000000000005000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000400000000000000000000000
... + 120 ################################%######
0000000000000000000000000000000020008000
000000000000000000000000000000005000E000
... + 160 ############XM## P############# E0 1
0000000000005400250000000000000222432223
0000700040008D00000020000C0000C000500001
... + 200 000 ####PNP 100
3332222222220000545222222222222222223332
00000000000000000E0000000000000000001000
... + 240 00
222223322222222
000000000000000
NO_OF_ROWS
2
0
SY-TFILL 63
3000
F000
14 FORM CALC_STANDARD_DEDUCTION
HINCALC0
PCTAXIN0 466
P0015[] Table IT_204[12x147]
F7D4DED48000C000000090000000FFFF00004500
871900998000C000C00030000000FFFF40000F00
... + 40
0000C020
20001E80
SW_AUFROLLUNG X
5
8
%BX03242_BLOCK_1000 Log
4662222222222222222222222222222222222222
CF70000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
SNAME 40INDED
33444442
409E4540
T559A-WTIME 000000
333333
000000
OGRT[] Table IT_299[0x53]
00000000C0002000000030000000FFFF0000E300
000000003000B100000050000000FFFF40000310
... + 40
1000C200
00001E00
ENDDATE 20070331
33333333
20070331
T596F-PGMNA HINCALC0
4444444322222222222222222222222222222222
89E31C3000000000000000000000000000000000
T596F-MODNA STDDED03
55444433
34445403
P_PRE_DEDUCTION_BALANCE ####Q#
00005991
0001153C
STANDARD_DEDUCTION ########
00000000
0000000C
P2006[] Table IT_460[37x168]
9ED40000E000C0002000A0000000FFFF00008500
877900006000C100500080000000FFFF40000600
... + 40
0000C020
20001E00
13 FORM FUINTAX
HINCALC0
PCTAXIN0 253
ANNUAL_IRREGULAR_INCOME ####3#%L
00003124
0000365C
%_SET_VOID_%_APP_%
222222222222222222222222222222
000000000000000000000000000000
ANNUAL_PERK ########
00000000
0000000C
SET_ODC
2
0
%_SET_ODC_%_APP_%
222222222222222222222222222222
000000000000000000000000000000
SET_REVR
2
0
P%2007 00000000 000000000000000000000
3333333322222222222333333333333333333333
0000000000000000000000000000000000000000
... + 40 000000 00
3333332222222222222222222222222222222233
0000000000000000000000000000000000000000
... + 80 0000000000 00###### ###### 00000000000
3333333333233000000200000022233333333333
000000000000000000C000000C00000000000000
... + 120 0000000000000000000000000
3333333333333333333333333222222222222222
0000000000000000000000000000000000000000
... + 160
222222222222
000000000000
PRE_DEDUCTION_BALANCE ####Q#
00005991
0001153C
OCRSN
2222
0000
APER-PAPER-PABRJ 2006
3333
2006
APER-IAPER-PABRJ 2007
3333
2007
SW_INTIM
2
0
APER-PAPER 200612
333333
200612
ANN_PTAX_AMT ########
00000000
0000000C
12 FORM AS-FUNKTION
HINCALC0
PCASFIN0 13
P0584 00000000 000000000000000000000
3333333322222222222333333333333333333333
0000000000000000000000000000000000000000
... + 40 000000 #
3333332222222222222222222222222222222220
0000000000000000000000000000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
00000C0000C0000C0000C0000C000000C000000C
... + 120 ####################################
0000000000000000000000000000000000002222
000000C000000C0000C0000C000000C0000C0000
... + 160 0000
22222222222333322222
00000000000000000000
ORGDIR 00000 0000000000000000 00 0
3333322222222333333333333333322332222223
0000000000000000000000000000000000000000
... + 40 0000000 0000000000000000000000000
3333333222222223333333333333333333333333
0000000000000000000000000000000000000000
... + 80 0000000000000 00000000
3333333333333223333333322222222222222222
0000000000000000000000000000000000000000
... + 120 00000000000000 000000000000000000000
3333333333333323333333333333333333332222
0000000000000000000000000000000000000000
RP-IMP-CD-SUBRC 0
0000
0000
CD-SUBRC 0
0000
0000
CD-INDEX 0
0000
0000
IT[] Table IT_490[63x53]
EFC47AC4F000E000300030000000FFFF00005100
0AB903399000A100F00050000000FFFF40000810
... + 40
2000C000
B0009E00
IT */418######### # ####################Q
2233300000000020222000000000000000000005
AF418000000000000000000000C0000000C00011
... + 40 #
9912222222222
53C0000000000
RGDIR_CA[] Table IT_383[0x156]
00003ED4E0007000000090000000FFFF0000C100
000086791000F1000000C0000000FFFF40000810
... + 40
4000C000
00001400
RGDIR_CA 00000 0000000000000000 00 0
3333322222222333333333333333322332222223
0000000000000000000000000000000000000000
... + 40 0000000 0000000000000000000000000
3333333222222223333333333333333333333333
0000000000000000000000000000000000000000
... + 80 0000000000000 00000000
3333333333333223333333322222222222222222
0000000000000000000000000000000000000000
... + 120 00000000000000 000000000000000000000
333333333333332333333333333333333333
000000000000000000000000000000000000
%%_DIR2[] Table IT_218[0x54]
000000009000D000000030000000FFFF0000D100
000000006000A000000060000000FFFF40008210
... + 40
6000C000
40001400
<%_TABLE_T599B> ???
PY_PM_CONTAINER 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 0
3222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
PNPSTATU-LOW
222
000
SET_LCW 010
333
010
11 FORM ASLOOP
HINCALC0
RPCHRT09_ASLOOP 58
P_WITH_LOG X
5
8
SW_EXPORT_ES
2
0
ASNUM 215
D000
7000
APER_NUMB 15
0000
F000
NEXT_AS_ENTRY 244
F000
4000
SW_REPETITION X
5
8
SW_P0005_CHANGED
2
0
PNPSACHZ
222222222
000000000
PTEXT[] Table IT_139[0x548]
0000CCC460008000000020000000FFFF00004300
00000D79C000B000000042000000FFFF40000500
... + 40
1000C200
00001400
SW_VOID
2
0
SCREEN %_17SNS0000177553_%_%_%_%_%_%_
2533545333333333352525252525252222222222
5F173E30000177553F5F5F5F5F5F5F0000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 SRI00001#00000 ####
2222222222222222222225543333303333320000
0000000000000000000003290000100000000000
SW_PROT
2
0
PNPSBMOD-LOW
2222
0000
PTEXT_LINES 0
0000
0000
10 FORM MONATSABRECHNUNG
HINCALC0
RPCHRT09_MONATSABRECHNUNG 48
CALC_CURRENCY INR
44522
9E200
SY-SUBRC 0
0000
0000
CALC_CURR_DEC 1380862210
0
2
TCURX-CURRDEC 0
0
0
PNPPERSK-LOW
22
00
PNPKOSTL
22222222222222222222222
00000000000000000000000
SL_BRUTTO
2
0
FC-SL_B_N
2
0
%_PNPSNAME_%_APP_% PNPSNAMEEE name can be sorted to
5455444444266662666266276776622222222276
0E03E1D5550E1D5031E02503F24540000000004F
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 @1FQMultiple selection@
2224345547676766276666766642222222222222
000016C1D5C490C5035C5349FE00000000000000
... + 120
222
000
APER-CALCD X
5
8
DT /AEA00200612 00000000########
24443333333322333333330000000022222
F1510020061200000000000000000C00000
DT[] Table IT_1916[4x35]
F8F40000E0007000000020000000FFFF0000E400
06090000A100C700400030000000FFFF40008610
... + 40
1000C220
00001E00
9 FORM RUECKRECHNUNG
HINCALC0
RPCHRT09_RUECKRECHNUNG 136
APER-PAYTY
2
0
SY-XPROG SAPDBPNP
5454454522222222222222222222222222222222
310420E000000000000000000000000000000000
PYCT 0<>
0000FFFF
0000FFFF
PNP-SW-AUTH-SKIPPED-RECORD 0
3
0
P0007[] Table IT_201[4x138]
CBC47DD48000C000000080000000FFFF00005400
80390F99500090004000A0000000FFFF40008B00
... + 40
0000C020
20001E80
PNPKOKRS[] Table IT_52[0x11]
0000000020003000000000000000FFFF04007200
00000000A00040000000B0000000FFFF44008700
... + 40
0000C000
A0001400
PNPBLCKT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
FC-NT_BEGIN 0
0000
0000
PNP-SW-IGNORELOCKEDRECORDS Y
5
9
FROM_DATE 00000000
33333333
00000000
%_SET_LCW_%_APP_%
222222222222222222222222222222
000000000000000000000000000000
8 FORM MAIN
HINCALC0
RPCHRT09_MAIN 134
%_PNPFKBER_%_APP_% PNPFKBERFunctional Area to
5454444547667666662476622222222222222276
0E06B25265E349FE1C012510000000000000004F
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 @1FQMultiple selection@
2224345547676766276666766642222222222222
000016C1D5C490C5035C5349FE00000000000000
... + 120
222
000
PERNR-PERNR 00003015
33333333
00003015
Table IT_235[0x178]
000045D4A000E0000000B0000000FFFF00003400
000080390000B000000020000000FFFF40008110
... + 40
1000C200
00001400
P0027[] Table IT_234[0x1851]
0000A4D49000E000000030000000FFFF0000DE00
00008F39F000A0000000B7000000FFFF40000610
... + 40
0000C200
80001E00
PNPENAME
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
INFTY[] Table IT_116[34x4]
8EC4000050007000200000000000FFFF0D008000
0E790000A0004000200040000000FFFF43000900
... + 40
2000C000
20001400
INFTY 0078
3333
0078
PNPBLCKP Payroll period
5677666276766622222222222222222222222222
0192FCC00529F400000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
SY-MSGNO 000
333
000
FC-PGM_TYP ABR
4452
1220
PY12W_MEM_ID_BUFFER T512W_BUFFER
533355454445
45127F256652
RSJOBINFO 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 ####
0000
0000
P0032 00000000 000000000000000000000
3333333322222222222333333333333333333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 #####
2222222222222222222222200000222222222222
000000000000000000000000000C000000000000
... + 120
2222222222222222222222222222222222222222
Hello,
strange, you have the same message in SQL Server forum, but we can see Oracle DB here:
SQL ERROR
Without developer traces it would be difficult to say. But it looks bad enough because of kernel 6.20 patch level 1511 (definitely dboraslib.dll has similar patch level) and Oracle 8.1.7 are out of support since years.
best regards -
Which Syntax is best to read an infotype using PNPCE LDB ?
Hi experts,
Which syntax is best to read an infotype when we use PNPCE LDB.
Thanks.
reddyHi Iredy,
if you need to read an infotype records of the particular employee, you can use Macro RP-READ-INFOTYPE (Parameters: PERNR, INFTY, BEGDA, ENDDA)
Macro definition you can find in table TRMAC.
For RP-READ-INFOTYPE is definition as follows:
RP-READ-INFOTYPE 001 ****************************************
RP-READ-INFOTYPE 002 * RP-READ-INFOTYPE *
RP-READ-INFOTYPE 003 ****************************************
RP-READ-INFOTYPE 004 * PARAMETERS: *
RP-READ-INFOTYPE 005 * PERNR REQUESTED PERSONALNUMBER*
RP-READ-INFOTYPE 006 * INFTY REQUESTED INFOTYPNUMBER *
RP-READ-INFOTYPE 007 * INFTY-TABLE OUTPUT-TABLE LIKE PNNNN*
RP-READ-INFOTYPE 008 * BEGDA REQUESTED INTERVAL-BEGIN*
RP-READ-INFOTYPE 009 * ENDDA REQUESTED INTERVAL-END *
RP-READ-INFOTYPE 010 ****************************************
RP-READ-INFOTYPE 011 *SET DEBUGGING INTERRUPT ON *
RP-READ-INFOTYPE 012 PERFORM READ-INFOTYPE(SAPDBPNP) *
RP-READ-INFOTYPE 013 TABLES &3 *
RP-READ-INFOTYPE 014 USING &1 '&2' &4 &5
RP-READ-INFOTYPE 015 *SET DEBUGGING INTERRUPT OFF *
It means that the macro is performing read-infotype which is defined in include DBPNPF03 of the SAPDBPNP. -
Creation of record in 2001 using FM - HR_INFOTYPE_OPERATION
Hi fellow ABAP,
I'm new to using HR_INFOTYPE_OPERATION, I want to make this one an alternative way to create record in IT 2001 instead of using Batch Input.. but it returns me error
Runtime Errors: ASSIGN_BASE_TOO_SHORT
Short text : Fehler in ASSIGN-Zuweisung im Programm "SAPLHRMM".
I ran HR_INFOTYPE_OPERATION at SE37 with these parameters:
INFTY = '2001'
NUMBER = '00001003'
SUBTYPE = '2250'
OBJECTID = ' '
LOCKINDICATOR = 'X'
VALIDITYEND = '06/02/2009'
VALIDITYBEGIN = '06/02/2009'
RECORDNUMBER = '000'
RECORD = '2001'
OPERATION = 'CREATE'
TCLAS = 'A'
DIALOG_MODE = '0'
NOCOMMIT = 'X'
VIEW_IDENTIFIER = ' '
SECONDARY_RECORD = ' '
is there something I missed? and how can I pass value for the creation of IT2001?
thanks so much in advance...Hi Dude,
Go through this code for 2002..
tables: pa0001, pa0171, pa0378.
DATA BEGIN OF i0378.
include structure p0378.
DATA END OF i0378.
DATA: START_DATE LIKE SY-DATUM.
DATA RETURN LIKE BAPIRETURN1.
selection-screen begin of block p1.
* This select option allows for testing on limited employees
* or for splitting the update into multiple runs.
SELECT-OPTIONS pernr for pa0001-pernr.
selection-screen end of block p1.
selection-screen skip.
selection-screen begin of block b1.
* The plan year date is normally the first day of the next year
PARAMETERS: py_date LIKE SY-DATUM.
* This date is the beginning of the enrollment period for managers
PARAMETERS: MGR_DATE LIKE SY-DATUM.
* This date is the beginning of the enrollment period for hourlys
PARAMETERS: HRLY_DATE LIKE SY-DATUM.
selection-screen end of block b1.
INITIALIZATION.
py_date = sy-datum.
py_date(4) = py_date(4) + 1.
py_date+4(4) = '0101'.
START-OF-SELECTION.
select * from pa0171
where pernr in pernr
and endda ge py_date
and begda le py_date.
* skip ineligible employees
if pa0171-bstat eq 'INEL'.
continue.
endif.
* determine start date of enrollment based on benefit group
if pa0171-bengr eq 'MNGR'.
start_date = mgr_date.
elseif pa0171-bengr eq 'HRLY'.
start_date = hrly_date.
else.
* ERROR HANDLING GOES HERE
continue.
endif.
* create IT0378 record for this person
clear i0378.
i0378-pernr = PA0171-pernr.
i0378-barea = PA0171-barea.
i0378-event = 'OPEN'.
i0378-begda = start_date.
i0378-infty = '0378'.
i0378-aedtm = sy-datum.
i0378-uname = sy-uname.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
INFTY = '0378'
NUMBER = i0378-pernr
SUBTYPE = 'OPEN'
VALIDITYBEGIN = i0378-begda
RECORD = i0378
OPERATION = 'INS'
IMPORTING
RETURN = return
EXCEPTIONS
OTHERS = 1.
if sy-subrc ne 0 or return-type ne ' '.
* ERROR HANDLING GOES HERE
endif.
ENDSELECT. -
Logical database PNP (Suppress message)
Hi,
we are having 1 report which is using logical database PNP
this is being shown in ALV
when the user runs the report the output is shown and after pressing BACK button the below lines are being shown
Personnel numbers skipped by the database driver
Reason 1: insufficient authorization, no. skipped personnel nos.:
this is being done by logical databse program SAPDBPNP
is there any way to supress this mesasge
thanking you in advance
regards
Sai easwarI belive this is not concurent employment why we need to use
PNPCE
Please be specific about your question
Regards -
Line item in PNP logical database
Hi All,
Can anyone tell me, what is the selection logic for PNP Logical database, suppose in one report we use PNP Logical database,
So when we put some date range, so in the output of report there are 2 fields, so during that date range 1 field occurs two time and other field 4 times, so how many line items would be displayed by that report.
Regards,
Kumarread documentation for report SAPDBPNP or SAPDBPNPCE.
-
HR - Supress Error messages at end of PNP Logical dB ABAP
It appears from the code for logical dB PNP that you can turn off the error messages that automatically print at the end of the program, but I don't see how to do it. Here's the SAP code in include DBPNPI01:
FORM end-processing.
CHECK sw_supress_write EQ no.
Can anyone tell me how to 'change' sw_supress_write?Try this code:
DATA:
BEGIN OF t_empty OCCURS 50,
pernr LIKE pernr-pernr,
END OF t_empty.
DATA:
temp1 TYPE i,
temp2 TYPE i,
temp3 TYPE i.
NODES: pernr.
START-OF-SELECTION.
PERFORM pnp_skipped_pernr(sapdbpnp)
TABLES t_empty
USING 'Y'
CHANGING temp1 temp2 temp3.
GET pernr.
* Do something here.
*FORM pnp_skipped_pernr
* TABLES locked_pernr_tab LIKE locked[] "out
* USING supress_reject_info LIKE sw_supress_write"in
* CHANGING auth_skipped_count LIKE auth-skip-count "out
* locked_skipped_count LIKE locked_pernr_count"out
* locked_occurs_param LIKE locked_ocp. "out
* locked_pernr_tab[] = locked[].
* sw_supress_write = supress_reject_info.
* auth_skipped_count = auth-skip-count.
* locked_skipped_count = locked_pernr_count.
* locked_occurs_param = locked_ocp.
*ENDFORM. "pnp_skipped_pern
Let us know how it goes. -
Personnel numbers skipped by the database driver
Hi,
we are having 1 report which is using logical database PNP
this is being shown in ALV
when the user runs the report the output is shown and after pressing BACK button the below lines are being shown
Personnel numbers skipped by the database driver
Reason 1: insufficient authorization, no. skipped personnel nos.:
this is being done by logical databse program SAPDBPNP
is there any way to supress this mesasge
thanking you in advance
regardsMay be you need
call your ALV in event
END-OF-SELECTION instead of in START-OF-SELECTION
otherwise
Use fm
call function 'LDB_PROCESS'
instead of using PNB in attributes of the program.
Please check the demo program DEMO_LOGICAL_DATABASE for how to use fm LDB_PROCESS thru call function.
a® -
Can I use logical databases in a WebDynpro ABAP program?
can I use logical databases in a WebDynpro ABAP program?
I need to build a WDA screen that is similar to the SAPDBPNP selection screen (user can find the personnel number based on several criteria, such as last_name/first_name of the employee). So it seems that the existing logical databases have already many nice features already built (like the selection screens, the logic behind the screens etc). So I was wondering if/how I can use them in my WDA application.Hello, Tiberiu.
You cannot use LDB directly within your WDA programa. BUT, you can fetch results from this LDB by using FM LDB_PROCESS. This function module can be called anytime from any kind of ABAP program. But you will still have to create the screen, as it only processes data, not screens.
Regards,
Andre
PS: Pls reward points if it helps. -
Can I use logical databases in a WebDynpro for ABAP program?
can I use logical databases in a WebDynpro ABAP program?
I need to build a WDA screen that is similar to the SAPDBPNP selection screen (user can find the personnel number based on several criteria, such as last_name/first_name of the employee). So it seems that the exisinting logical databases have already many nice features already built (like the selection screens, the logic behind the screens etc). So I was wondering if/how I can use them in my WDA application.Hi
Please let me also know the solution to this. I am a beginner to WebDynpro and want to know if I can make use of LDB's as we do in our normal HR programming do develop a WDA in HR.
Thanks and regards,
Uma. -
To improve the performance of the extractor
Hi Team,
Currently there is one dataload which is taking 48hours to extract data from R/3 System to BI. It is based on infoset query.
The extractor uses the standard LDB : PNP, The database driver for this LDB is SAPDBPNP.
The extractor is based on PA0008 infotype.
1 tricky part of this code is that the values are not stored in the PA0008 table, but these are dynamically calculated during the infoset extract.
Could you please provide some inputs in improving the performance.
Thanks in advance.
Sunil Kumar.Since its dynamically calculated during the infoset extract, obviously it would go longer time. Because it has to calculate those many times as the no.of PERNR (in IT8).
If possible try to move those calculations to Transfer / Update Rules level.
OR
If its a non-delta datasource, try to add more infopackages (with PERNR selections) to this datasource, run them in parallel in process chain. -
Dynamic internal table problem in FM - HR_INFOTYPE_OPERATIONS
Dear All,
I have a problem when I use a Dynamic internal table in FM - HR_INFOTYPE_OPERTATION..
Please suggest me on the way to overcome this problem..
We wanted to have a dynamic Program for Info type operations which can be used for any info types as we are changing only BEGDA and the related actions
So in my program I have the parameters to accept
P_BEGDA - 01.10.2007
P_INFTY - P0008
P_ACTIO - COPY
I am able to create a dynamic table based on the parameters P_INFTY and able to read it also using the FM - HR_READ_INFOTYPE
BUT when I pass the dynamic internal table to a FM - HR_INFOTYPE_OPERTATION I am getting a DUMP
The DUMP is at the below statement from FM - HR_INFOTYPE_OPERTATION
ASSIGN record TO <record> CASTING TYPE (tabname). "XDP UniCode
It gives the below possiblities
"ASSIGN_BASE_TOO_SHORT" C
"SAPLHRMM" or "LHRMMU03"
"HR_INFOTYPE_OPERATION"
But If I use the below internal table
Data : g_t_0008 like P0008 occurs 0 with header line.
And If I use the internal table g_t_0008 instead of dynamic tables then it works. So I strongly feel it's due to not having a header in the dynamic table below see below the sample code on how I am generating a dynamic internal table
field-symbols: <dyn_table> type standard table.
data: dy_table type ref to data,
dy_line type ref to data,
xfc type lvc_s_fcat,
ifc type lvc_t_fcat.
to get the srurcute
perform get_structure using l_f_table.
perform create_dynamic_itab .
assign dy_table->* to <dyn_table>.
perform get_data tables <dyn_table01>
using pernr-pernr p_infty.
below are the forms routine .
form get_structure using p_table.
data : idetails type abap_compdescr_tab,
xdetails type abap_compdescr.
data : ref_table_des type ref to cl_abap_structdescr.
clear : ifc[], dy_table.
Get the structure of the table.
ref_table_des ?=
cl_abap_typedescr=>describe_by_name( p_table ).
idetails[] = ref_table_des->components[].
loop at idetails into xdetails.
clear xfc.
xfc-fieldname = xdetails-name .
xfc-datatype = xdetails-type_kind.
xfc-inttype = xdetails-type_kind.
xfc-intlen = xdetails-length.
xfc-decimals = xdetails-decimals.
append xfc to ifc.
endloop.
endform.
form create_dynamic_itab.
Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
exporting
it_fieldcatalog = ifc
importing
ep_table = dy_table.
endform.
*& Form get_data
form get_data tables p_table
using p_pernr
p_infty.
clear : p_table, p_table[].
CALL FUNCTION 'HR_READ_INFOTYPE'
EXPORTING
PERNR = P_PERNR
INFTY = p_infty
BEGDA = p_datum
ENDDA = p_datum
TABLES
INFTY_TAB = p_table
EXCEPTIONS
INFTY_NOT_FOUND = 1
OTHERS = 2.
CHECK SY-SUBRC EQ 0.
IF lines( p_table ) GT 0.
*write :/'Record exist' , 'IT', p_infty.
clear p_table.
PERFORM hr_operation tables p_table
using g_t_t588d-actio g_t_t588d-INFTY
g_t_t588d-SUBTY.
else.
PERFORM append_status using g_t_itab-pernr p_infty ' '
'Error' 'No records'.
ENDIF.
endform. " get_data
form hr_operation tables p_table
using p_actio P_INFTY P_SUBTY.
data: l_f_return LIKE bapireturn1.
ASSIGN COMPONENT 'BEGDA' OF STRUCTURE p_table TO <l_field>.
<l_field> = p_begda.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = P_infty
number = G_T_ITAB-PERNR
subtype = P_subty
validityend = g_f_endda
validitybegin = P_datum
record = P_TABLE
operation = p_actio
IMPORTING
return = l_f_return.
IF sy-subrc NE 0.
ENDIF.
ENDFORM.try
using field symbol for a wrk area instead of Field symbol for a table
loop your inernal table (again a field symbol) assigning to <fs_wrkarea>
in loop call HR_INFO.._OP..
reward if helpful
Maybe you are looking for
-
My iphone 4 is no longer ringing.
The mute button on the side is not engaged. The settings all appear to be correct but I can only hear music or sound through ear buds. My phone only vibrates for everything else. Help!
-
Can't delete Preferences in CS 4 (Design Standard)
Haven't used Ilustrator in over a year (ill) and I can't add lettering to an historical photo design. Layers are locked, new layer started for lots of lettering to be added but I'm prevented from drawing the curved base lines I need to wrap the
-
can this model scan to word in an editable form? OCR installed to word
-
The icon wont enable and when I go to open it via "open file" some technical sentences come up that make no sense to me. I don't know what is wrong. Never had this problem before. Can you help?
-
Automatically add user to an OIM role using rule
Hi, I am using OIM11g and I have created a rule with condition Oragnizaion Name == testgroup I have attached this rule to an OIM Role testrole. but when I create user with organization as tesgroup, user is not attached to OIM Role testrole. thanks.