‎2007 Jul 20 9:41 AM
what is the use of function modules;
Changedocument_Read_Headers.
Changedocument_Read_Positions.
Reuse_Alv_Fieldcatalog_Merge
‎2007 Jul 20 9:46 AM
Hi,
<b>CHANGEDOCUMENT_READ_HEADERS</b>
The function module determines change document numbers with the respective header information for an object class. The determination can be limited by specifying various parameters
<b>CHANGEDOCUMENT_READ_POSITIONS</b>
The function module reads change document items and processes both the old and the new values according to their category. In some cases, the units and currencies are added on to the value fields. Additionally, the corresponding table header is determined.
<b>REUSE_ALV_FIELDCATALOG_MERGE</b>
It create field catalog from dictionary structure or internal table.
It supports the creation of the field catalog for the ALV function modules based either on a structure or table defined in the ABAP Data Dictionary, or a program-internal table.
The program-internal table must either be in a TOP Include or its Include must be specified explicitly in the interface.
The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:
Performance is affected since the code of the table definition must always be read and interpreted at runtime.
Dictionary references are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.
If the field catalog contains more than 90 fields, the first 90 fields are output in the list by default whereas the remaining fields are only available in the field selection.
If the field catalog is passed with values, they are merged with the 'automatically' found information.
Regards,
Padmam.
‎2007 Jul 20 9:44 AM
hI,
<b>Changedocument_Read_Headers :</b>
From FM Documentation,
Change document: Read change document header
Preliminary comment
This function module has been released.
The documentation is being revised so that it conforms to the requirements for released function modules.
Functionality
The function module determines change document numbers with the respective header information for an object class. The determination can be limited by specifying various parameters (see interface description).
The change documents are read from the database (default) or from an archive depending on the ARCHIV_HANDLE parameter.
Using the parameter LOCAL_TIME you can also specify whether the local time and date (referring to the time zone) or a system time and date (default) are transferred.
Example call:
DATA: OBJEKT LIKE CDHDR-OBJECTCLAS,
OBJEKTID LIKE CDHDR-OBJECTID,
AENDERER LIKE CDHDR-USERNAME,
DATUM LIKE CDHDR-UDATE,
ZEIT LIKE CDHDR-UTIME,
DATA: BEGIN OF ICDHDR OCCURS 50.
INCLUDE STRUCTURE CDHDR.
DATA: END OF ICDHDR.
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
EXPORTING OBJECTCLASS = OBJEKT
OBJECTID = OBJEKTID
USERNAME = AENDERER
TIME_OF_CHANGE = ZEIT
DATE_OF_CHANGE = DATUM
TABLES I_CDHDR = ICDHDR
EXCEPTIONS ...
<b>Changedocument_Read_Positions.</b>
Change document: Read change document items
Preliminary comment
This function module has been released.
The documentation is being revised so that it conforms to the requirements for released function modules.
The function module reads change document items and processes both the old and the new values according to their category. In some cases, the units and currencies are added on to the value fields. Additionally, the corresponding table header is determined.
The change document number is required as a minimum entry.
The program RSSCD100 uses this function module and can be regarded as a possible application
<b>Reuse_Alv_Fieldcatalog_Merge :</b>
Create field catalog from dictionary structure or internal table
Functionality
Supports the creation of the field catalog for the ALV function modules based either on a structure or table defined in the ABAP Data Dictionary, or a program-internal table.
The program-internal table must either be in a TOP Include or its Include must be specified explicitly in the interface.
The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:
Performance is affected since the code of the table definition must always be read and interpreted at runtime.
Dictionary references are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.
If the field catalog contains more than 90 fields, the first 90 fields are output in the list by default whereas the remaining fields are only available in the field selection.
If the field catalog is passed with values, they are merged with the 'automatically' found information
Thanks.
REWARD POINTS IF HELPFUL.
‎2007 Jul 20 9:45 AM
Hi
- Changedocument_Read_Headers.
Changedocument_Read_Positions.
They are to get the change documents (header and items data) and so to read the table CHDR and CDPOS
- Reuse_Alv_Fieldcatalog_Merge : to fill the catalog table (fieldcat) in order to the definition of the output table.
Max
‎2007 Jul 20 9:45 AM
Hi Tanuj,
The first twoo FM are related to the change documents and to get the data from table CDHDR and CDPOS.
The third one is to display header in the ALV output.
Regards,
Atish
‎2007 Jul 20 10:24 AM
‎2007 Jul 20 9:46 AM
for documentation on any function module just login to <b>www.se37.com</b>,
eneter you FM name and know it!
regards,
srinivas
<b>*reward for useful answers*</b>
‎2007 Jul 20 9:46 AM
Hi,
<b>CHANGEDOCUMENT_READ_HEADERS</b>
The function module determines change document numbers with the respective header information for an object class. The determination can be limited by specifying various parameters
<b>CHANGEDOCUMENT_READ_POSITIONS</b>
The function module reads change document items and processes both the old and the new values according to their category. In some cases, the units and currencies are added on to the value fields. Additionally, the corresponding table header is determined.
<b>REUSE_ALV_FIELDCATALOG_MERGE</b>
It create field catalog from dictionary structure or internal table.
It supports the creation of the field catalog for the ALV function modules based either on a structure or table defined in the ABAP Data Dictionary, or a program-internal table.
The program-internal table must either be in a TOP Include or its Include must be specified explicitly in the interface.
The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:
Performance is affected since the code of the table definition must always be read and interpreted at runtime.
Dictionary references are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.
If the field catalog contains more than 90 fields, the first 90 fields are output in the list by default whereas the remaining fields are only available in the field selection.
If the field catalog is passed with values, they are merged with the 'automatically' found information.
Regards,
Padmam.
‎2007 Jul 20 9:47 AM
<b>Reuse_Alv_Fieldcatalog_Merge</b> : is used to create field catalog autometically in a ALV display.
Supports the creation of the field catalog for the ALV function modules
based either on a structure or table defined in the ABAP Data
Dictionary, or a program-internal table.
The program-internal table must either be in a TOP Include or its
Include must be specified explicitly in the interface.
The variant based on a program-internal table should only be used for
rapid prototyping since the following restrictions apply:
o Performance is affected since the code of the table definition must
always be read and interpreted at runtime.
o Dictionary references are only considered if the keywords LIKE or
INCLUDE STRUCTURE (not TYPE) are used.
If the field catalog contains more than 90 fields, the first 90 fields
are output in the list by default whereas the remaining fields are only
available in the field selection.
If the field catalog is passed with values, they are merged with the
'automatically' found information.
<b>Changedocument_Read_Headers</b> :
The function module determines change document numbers with the
respective header information for an object class. The determination can
be limited by specifying various parameters (see interface description).
The change documents are read from the database (default) or from an
archive depending on the ARCHIV_HANDLE parameter.
Using the parameter LOCAL_TIME you can also specify whether the local
time and date (referring to the time zone) or a system time and date
(default) are transferred.
<b>
Changedocument_Read_Positions</b> : The function module reads change document items and processes both th
old and the new values according to their category. In some cases, th
units and currencies are added on to the value fields. Additionally,
corresponding table header is determined.
The change document number is required as a minimum entry.
The program RSSCD100 uses this function module and can be regarded as
possible application.