Quick Tips
Please ensure you write capital letter for the fieldcatalog fieldname.
add 1 to l_count.
it_fieldcat-col_pos = l_count.
it_fieldcat-fieldname = 'NOSPOUSE'.
it_fieldcat-seltext_m = 'No of Spouse'.
* it_fieldcat-do_sum = 'X'.
append it_fieldcat.
clear it_fieldcat.
There are 8 bits in a byte. There is No Shortcut to be A Great ABAP Programmer and It's Applies to All.
Saturday, June 4, 2011
Monday, April 18, 2011
Macro without Logical Database Declaration
HR ABAP
INFOTYPES: 0000. "+badli 20110415
DATA it_pa0000 LIKE P0000 OCCURS 0. "+badli 20110415
"Begin add by badli 20110415
" to check record already exist or not.
RP-READ-INFOTYPE w_pyh002h-pernr 0000 it_pa0000 w_pyh002h-zactdat
'99991231' .
"Begin add by badli 20110415
" to check record already exist or not.
RP-READ-INFOTYPE w_pyh002h-pernr 0000 it_pa0000 w_pyh002h-zactdat
'99991231' .
Above record is used Macro RP-READ-INFOTYPE
Thursday, April 7, 2011
PERFORM dynpro format
Using BDC for HR.
Code Snippet
PERFORM dynpro USING 'X' 'SAPMP50A' '1000'.
FORM dynpro USING pa_dynbegin
pa_name
pa_value.
IF pa_dynbegin = 'X'.
CLEAR ta_bdcdata.
MOVE: pa_name TO ta_bdcdata-program,
pa_value TO ta_bdcdata-dynpro,
'X' TO ta_bdcdata-dynbegin.
APPEND ta_bdcdata.
ELSE.
CLEAR ta_bdcdata.
MOVE: pa_name TO ta_bdcdata-fnam,
pa_value TO ta_bdcdata-fval.
* CONDENSE ta_bdcdata-fval no-gaps.
APPEND ta_bdcdata.
ENDIF.
ENDFORM.
pa_name
pa_value.
IF pa_dynbegin = 'X'.
CLEAR ta_bdcdata.
MOVE: pa_name TO ta_bdcdata-program,
pa_value TO ta_bdcdata-dynpro,
'X' TO ta_bdcdata-dynbegin.
APPEND ta_bdcdata.
ELSE.
CLEAR ta_bdcdata.
MOVE: pa_name TO ta_bdcdata-fnam,
pa_value TO ta_bdcdata-fval.
* CONDENSE ta_bdcdata-fval no-gaps.
APPEND ta_bdcdata.
ENDIF.
ENDFORM.
Thursday, February 10, 2011
Difference Between Smart Forms and SAPscripts
The advantages of SAP Smart Forms as compared to SAPscript are:
- Minimum time required for form customizing
- Consistent use of graphical tools
- Separation of data retrieval and form logic
- No special scripting language
- Integration in Internet applications
- Migration of SAPscript forms and styles is supported
- SAPscript texts can be inserted into SAP Smart Forms
Tuesday, February 8, 2011
BDC Message Type Error
I suggest that you press F1 on MESSAGE. Btw, you already covered most of the message types.
To help you out a bit:
A(bort)
E(rror)
W(arning)
S(tatus)
I(nfo)
(e)X(it) (guess the E was already taken)
Indeed, MESSTAB is filled in the same order as a user would see them.
Since this is a BDC program I asume there is no user present to read your messages. Neither does he have the means to influence the program. So I guess you want to write the messages to a log. And I think you want to have plian text, not something like E123(AB). Fortunately SAP has provided us with some useful function modules like BAPI_MESSAGE_GET_DETAIL (set textformat to 'NON')
But there are tons of FM's that deal with messages. Also take a look at table T100; that is where all messages are stored.
If you want to write your messages to an application log, take a look at function group SLG0
To help you out a bit:
A(bort)
E(rror)
W(arning)
S(tatus)
I(nfo)
(e)X(it) (guess the E was already taken)
Indeed, MESSTAB is filled in the same order as a user would see them.
Since this is a BDC program I asume there is no user present to read your messages. Neither does he have the means to influence the program. So I guess you want to write the messages to a log. And I think you want to have plian text, not something like E123(AB). Fortunately SAP has provided us with some useful function modules like BAPI_MESSAGE_GET_DETAIL (set textformat to 'NON')
But there are tons of FM's that deal with messages. Also take a look at table T100; that is where all messages are stored.
If you want to write your messages to an application log, take a look at function group SLG0
source :
Monday, January 31, 2011
LUW_MODE
0 - no COMMIT WORK, no ROLLBACK WORK ==> has to do manually after the FM returns
1 - COMMIT will be done in one go by the FM if everything is OK, otherwise ROLLBACK
2 - COMMIT or ROLLBACK will be done on any single infotype (one by one)
3 - can be used for simulation
(DIALOG_MODE has to be '0', otherwise any of the above makes no sense)
1 - COMMIT will be done in one go by the FM if everything is OK, otherwise ROLLBACK
2 - COMMIT or ROLLBACK will be done on any single infotype (one by one)
3 - can be used for simulation
(DIALOG_MODE has to be '0', otherwise any of the above makes no sense)
Friday, December 10, 2010
Integer Type Variable - Sapscript Using Space
Hi Folks,
It seems in SAPScript it will not condense if printing integer type value ,
if need comma separated value e.g 6,000,000 moving the value to char type variable is not a good choice as it will remove the comma in after moving the value .
The trick is put condense character in the SAPscript for e.g
&v_credit_ringgit(C)&
it will condense any empty space even it is integer type value.
Subscribe to:
Posts (Atom)