Scribd
Upload
157 views3 pages

Zhr1000 BDC

This document contains instructions for generating data records with specific field formatting rules. It defines 4 rules for the data section: 1) Each field definition consists of 2 lines, with the first commenting the data element and second defining the field name and length. 2) Fields must be of type C. 3) Do not change the generated data section. 4) Field names can include an underscore and 3 numbers before the length in brackets. The document then provides an example data section generated according to these rules.

Uploaded by

Santosh Moharana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
157 views3 pages

Zhr1000 BDC

This document contains instructions for generating data records with specific field formatting rules. It defines 4 rules for the data section: 1) Each field definition consists of 2 lines, with the first commenting the data element and second defining the field name and length. 2) Fields must be of type C. 3) Do not change the generated data section. 4) Field names can include an underscore and 3 numbers before the length in brackets. The document then provides an example data section generated according to these rules.

Uploaded by

Santosh Moharana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

report ZHR1000

no standard page heading line-size 255.


include bdcrecx1.
parameters: dataset(132) lower case.
***
DO NOT CHANGE - the generated data section - DO NOT CHANGE
***
*
* If it is nessesary to change the data section use the rules:
* 1.) Each definition of a field exists of two lines
* 2.) The first line shows exactly the comment
*
'* data element: ' followed with the data element
*
which describes the field.
*
If you don't have a data element use the
*
comment without a data element name
* 3.) The second line shows the fieldname of the
*
structure, the fieldname must consist of
*
a fieldname and optional the character '_' and
*
three numbers and the field length in brackets
* 4.) Each field must be type C.
*
*** Generated data section with specific formatting - DO NOT CHANGE ***
data: begin of record,
* data element: PLVAR
PLVAR_001(002),
* data element: OTYPE
OTYPE_002(002),
* data element: STIMR6
TIMR6_005(001),
* data element: BEGDATUM
BEGDA_006(010),
* data element: ENDDATUM
ENDDA_007(010),
* data element:
MARKFELD_01_008(001),
* data element: SHORT_D
SHORT_011(012),
* data element: STEXT
STEXT_012(040),
* data element: SEARK
SEARK_019(012),
end of record.
*** End generated data section ***
* INTERNAL TABLE & WORK AREA DECLARATION
*DATA : T_BDCDATA TYPE STANDARD TABLE OF BDCDATA INITIAL SIZE 0 ,
*
W_BDCDATA TYPE BDCDATA ,
*
T_ITAB TYPE STANDARD TABLE OF TY_ITAB INITIAL SIZE 0 ,
*
W_ITAB TYPE TY_ITAB .
* LOCAL VARIABLE \
DATA : V_FILENAME TYPE LOCALFILE .
*&---------------------------------------------------------------------*
*& At Selection Screen on value-request
*&---------------------------------------------------------------------*
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FNAME .
* PERFORM GET_FILE .

start-of-selection.
perform open_dataset using dataset.
perform open_group.
do.
read dataset dataset into record.
if sy-subrc <> 0. exit. endif.
perform bdc_dynpro
perform bdc_field
perform bdc_field
perform bdc_field
perform bdc_field
perform bdc_dynpro
perform bdc_field
*perform bdc_field
*
*perform bdc_field
*
perform bdc_field
perform bdc_field
perform bdc_field
perform bdc_field
perform bdc_field
perform bdc_dynpro
perform bdc_field
perform bdc_field
*perform bdc_field
*
*perform bdc_field
*
perform bdc_field
perform bdc_field
perform bdc_dynpro
*perform bdc_field
*
perform bdc_field
*perform bdc_field
*
*perform bdc_field
*

using 'SAPMH5A0' '5000'.


using 'BDC_CURSOR'
'PPHDR-OTYPE'.
using 'BDC_OKCODE'
'/00'.
using 'PPHDR-PLVAR'
record-PLVAR_001.
using 'PPHDR-OTYPE'
record-OTYPE_002.
using 'SAPMH5A0' '5000'.
using 'BDC_OKCODE'
'=INSE'.
using 'PPHDR-PLVAR'
record-PLVAR_003.
using 'PPHDR-OTYPE'
record-OTYPE_004.
using 'BDC_CURSOR'
'TT_T777T-ITEXT(01)'.
using 'PM0D1-TIMR6'
record-TIMR6_005.
using 'PPHDR-BEGDA'
record-BEGDA_006.
using 'PPHDR-ENDDA'
record-ENDDA_007.
using 'MARKFELD(01)'
record-MARKFELD_01_008.
using 'MP100000' '2000'.
using 'BDC_CURSOR'
'P1000-STEXT'.
using 'BDC_OKCODE'
'/00'.
using 'P1000-BEGDA'
record-BEGDA_009.
using 'P1000-ENDDA'
record-ENDDA_010.
using 'P1000-SHORT'
record-SHORT_011.
using 'P1000-STEXT'
record-STEXT_012.
using 'MP100000' '2000'.
using 'BDC_CURSOR'
'P1000-BEGDA'.
using 'BDC_OKCODE'
'=UPD'.
using 'P1000-BEGDA'
record-BEGDA_013.
using 'P1000-ENDDA'
record-ENDDA_014.

*perform bdc_field
*
*perform bdc_field
*
perform bdc_dynpro
perform bdc_field

using 'P1000-SHORT'
record-SHORT_015.
using 'P1000-STEXT'
record-STEXT_016.
using 'SAPMH5A0' '5000'.
using 'BDC_OKCODE'
'=BACK'.
*perform bdc_field
using 'PPHDR-PLVAR'
*
record-PLVAR_017.
*perform bdc_field
using 'PPHDR-OTYPE'
*
record-OTYPE_018.
*perform bdc_field
using 'PM0D1-SEARK'
*
record-SEARK_019.
perform bdc_transaction using 'PP01'.
enddo.
perform close_group.
perform close_dataset using dataset.

You might also like