2008 Oct 12 7:27 AM
Dear All,
I have some doubt in bdc , i.e., while recording the t-code s_l9c_94000095 i have to set begda as 01.10.2008 and endda as 10.10.2008 and employement status as <> 0 for this how can i record..
I tried in IDES there is ok_code call as =pick so i can transfer the cursor position to <> options but in development there is no ok_code called as =pick so how can i solve this issue.,.,
WHEN 'CWEEK'.
IF us_self_field-tabindex = 1.
PERFORM bdc_dynpro USING 'AQZZ/SAPQUERY/H2STAFF_CHANGES2' '1000'.
PERFORM bdc_field USING 'BDC_CURSOR'
'PNPSTAT2-LOW'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OPTI'.
PERFORM bdc_field USING 'PNPTIMR6'
'X'.
PERFORM bdc_field USING 'PNPBEGDA'
'01.10.2008'.
PERFORM bdc_field USING 'PNPENDDA'
'01.10.2008'.
PERFORM bdc_field USING 'PNPSTAT2-LOW'
'0'.
PERFORM bdc_field USING '%ALV'
'X'.
PERFORM bdc_dynpro USING 'SAPLALDB' '0651'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OKAY'.
PERFORM bdc_dynpro USING 'SAPLALDB' '0651'.
PERFORM bdc_dynpro USING 'AQZZ/SAPQUERY/H2STAFF_CHANGES2' '1000'.
PERFORM bdc_field USING 'BDC_CURSOR'
'PNPSTAT2-LOW'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ONLI'.
PERFORM bdc_field USING '%ALV'
' '.
*perform bdc_dynpro using 'SAPLSLVC_FULLSCREEN' '1000'.
CALL TRANSACTION 'S_L9C_94000095' USING bdcdata MODE 'E' .
2008 Oct 12 12:17 PM
This is customization issue. Contact to functional guy and get same configuration in both the client then you will be able to execute same BDC program in both client.
Regards
Rajiv singh.
Dear All,
I have some doubt in bdc , i.e., while recording the t-code s_l9c_94000095 i have to set begda as 01.10.2008 and endda as 10.10.2008 and employement status as <> 0 for this how can i record..
I tried in IDES there is ok_code call as =pick so i can transfer the cursor position to <> options but in development there is no ok_code called as =pick so how can i solve this issue.,.,
WHEN 'CWEEK'.
IF us_self_field-tabindex = 1.
PERFORM bdc_dynpro USING 'AQZZ/SAPQUERY/H2STAFF_CHANGES2' '1000'.
PERFORM bdc_field USING 'BDC_CURSOR'
'PNPSTAT2-LOW'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OPTI'.
PERFORM bdc_field USING 'PNPTIMR6'
'X'.
PERFORM bdc_field USING 'PNPBEGDA'
'01.10.2008'.
PERFORM bdc_field USING 'PNPENDDA'
'01.10.2008'.
PERFORM bdc_field USING 'PNPSTAT2-LOW'
'0'.
PERFORM bdc_field USING '%ALV'
'X'.
PERFORM bdc_dynpro USING 'SAPLALDB' '0651'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OKAY'.
PERFORM bdc_dynpro USING 'SAPLALDB' '0651'.
PERFORM bdc_dynpro USING 'AQZZ/SAPQUERY/H2STAFF_CHANGES2' '1000'.
PERFORM bdc_field USING 'BDC_CURSOR'
'PNPSTAT2-LOW'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ONLI'.
PERFORM bdc_field USING '%ALV'
' '.
*perform bdc_dynpro using 'SAPLSLVC_FULLSCREEN' '1000'.
CALL TRANSACTION 'S_L9C_94000095' USING bdcdata MODE 'E' .
2008 Oct 12 12:17 PM
This is customization issue. Contact to functional guy and get same configuration in both the client then you will be able to execute same BDC program in both client.
Regards
Rajiv singh.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |