Correct Function module Read CDPO CDHDR

HI ,
I need to read CDPO and CDHDR tables for change documents of class 'EINKBELEG'
I used fm CHANGEDOCUMENT_READ_HEADERS but it did not return correct records.The DB table contains 87 recs and FM returned 20 records.
Please suggest whether there is any one fm which can fetch both header and item ie cdhdr and cdpos in one call...
Also mention separate FM for reading CDHDR , CDPOS.
Regards,
Shital

Hi
Look this fm CHANGEDOCUMENT_READ_WITHOUT_ED
Maybe is helpful
Regards
Gregory

Similar Messages

BAPI or Functional Module Reads Profit Segment From PR

Hello, does anybody know about BAPI or Functional module to read profit segment, created in Purchase requisition?
Or another technic to get: PAOBJNR

Here is a solution which was useful to us:
Take paobjnr form ebkn, and then: CALL FUNCTION 'RKE_CONVERT_PAOBJNR_COPADATA' and just read exported table with fields inside the profit segment
+ 1 simple select for customer description for example J

Packing a Delivery via function modules or BAPI's

Does anyone know the correct function modules to call in order to pack an outbound delivery. The HU is already been entered into the delivery. I just need to pack all the items into this HU and PGI the delivery. I've tried the following function modules:
SD_DELIVERY_UPDATE_PACKING
V51P_FIND_HEADER
V51P_NEUE_HU_PRO
I'm not sure what I'm doing wrong but the delivery doesn't get packed. Anyone have a clue?
Thank you,

The problem resides in external unique number assignement for handling units:
in SPRO:
> Logistics - General
> Handling Unit Management
> External Identification
> Set Unique Number Assignment for HU Identification
Simply flag the checkbox and Save!
Without this flag BAPI's raise this info message (HUDIALOG 038). Even if it is an info message and the number is returned at the end the handling unit won't be created!
Just flag it!

In WE19 getting error Message as Function module missing

Hi Friends,
I need to debug the Inbound function module
so in WE19 i am providing the IDOC number and clicking on the Inbound function module then i am getting pop-up
i am able to select my function module name
and checking the Fore ground processing Radio button
for debugging
I am getting a Warring Message as
Interface or Function module <NAME> is Incorrect
Kindly suggest me
where the mistake might be
and how to correct IT
Thanks in Advance
Ganesh

Hi Ganesh,
I believe you are using a non IDOC function module, that's the reason you are getting that error.
Use the appropriate IDOC function module and then select the Debug check box and it will stop.
If you can provide me the IDOC message then I can help you by giving the correct Function Module.
Thanks,
Mahesh.

Function module not released

Hi,
I have a requirement where I need to insert/delete international versions of BP standard Address.(This is not the International Address Usage in the Address Overview tab. The international versions can be added by the international versions button in the Address tab.)
I was tryng to use the following function modules for the same:-
ADDR_VERSION_INSERT,
ADDR_VERSION_DELETE,
ADDR_SINGLE_SAVE.
I am able to do the verion insert/delete using these function modules but the problem is none of these function modules are released . I was trying to get the correct function modules by debugging the BP transaction and setting the breakpoint at the 'CALL FUNCTION' statement.Also I tried using the report program 'RS_ABAP_SOURCE_SCAN'.But none of them were successful. Also I am not able to get these information from the where-used list of the function modules.
Please let me know how to go about this.
Thanks,
Samrat.

it's not clear what is released, what is not released. If it's somewhere in the documentation, I consider it released, even though technically it is not released. See [sap library - working with the BAS|http://help.sap.com/saphelp_nw70/helpdata/EN/12/ad79815c5811d3b4ea006094192fe3/frameset.htm]. Even if not released, you may take the small risk to use it, just discuss with your project/maintenance teams.

Function module for version history

hi
with limited access to sap system, i'm unable to to complete a documentation by missing the reference on the function module to be used for reading the version history of a report or module pool/screen. kindly point on the correct function module to be used that would fetch the version history ?
PS: I'm aware of the table to be used i.e. vrsd. yet, i'm looking for function module
thkx.
Prabhu

Chk this fm.
SVRS_GET_VERSION_DIRECTORY_46 - you canl get the version and transport request details
CALL FUNCTION 'SVRS_GET_VERSION_DIRECTORY_46'
EXPORTING
destination = lw_dest(Destination client)
objname = lw_obj_name(object name)
objtype = lw_obj_type(Eg : 'PROG' for program)
TABLES
lversno_list = l_verno
version_list = l_verlist
EXCEPTIONS
no_entry = 1
communication_failure_ = 2
system_failure = 3
OTHERS = 4.

Transaction SU01 -- Function modules...

Hi Colleagues,
Can someone direct me to correct function modules to get all data whcih we see in transaction SU01.. ie LOGON DATA , CoMM data etc.
Regards
Anuj

Hi Anuj,
In SE80 look at the Function Modules under Function Group SUSR.
Reward points if this info was useful to you.
Cheers,
Sougata.

Replacement of Function module in ECC 6.0

Hello All,
The Function module 'NAMETAB_GET' is shown to be obsolete in ECC 6.0 .
Please suggest which of the function modules among 'DDIF_FIELDINFO_GET' and 'DDIF_NAMETAB_GET' can be used as a replacement for the same.
Also ,it would be helpful if the use of these function modules is mentioned.
Best Regards,
Lavanya.

use 'DDIF_NAMETAB_GET'
Functionality
This function module reads the runtime information (nametab) of a table or in general of any type of the ABAP Dictionary. However, the runtime information does not contain any text. You should use the function module DDIF_FIELDINFO_GET to read the runtime information including text (or to determine the domain for table fields).
The types of the ABAP Dictionary are divided into data elements, structured types and table types.
A structured type consists of a sequence of components that are each identified by a unique name. A type is defined for each of these components. In addition to the types of the ABAP Dictionary, you can also use the built-in types of the R/3 System (CHAR, NUMC,...) to define the types of the components.
All its components as well as the fields of its structured components are called the fields of a structured type. The name of a field no longer uniquely identifies it within a structured type. For example, a structured type S could have a structured component F, which itself has a component called F. In this case S would have two fields with the name F. For this reason, its long field name is used to identify a field within a structured type. The long field name is the same as the name of the components for the components of the structured type itself. For the fields of a structured component, the long field name is a concatenation of the name of this structured component, the separator '-' and the long field name of the field in the structured component.
A field whose type is defined by a data element or a built-in type is also called an elementary type. A structured type whose components are all defined as elementary types is called flat. All other structured types are called deep.
This module gets the runtime information for the type whose name is defined in the IMPORT parameter TABNAME. If there is no such type, the exception NOT_FOUND is triggered.
Caution: If the IMPORT parameter ALL_TYPES is not set, only flat structured types are taken into consideration. In this case the exception is also triggered if the specified type is a data element, deep structure or a table type.
If the IMPORT parameter LFIELDNAME is not initial, only structured types having a field with the long name defined by LFIELDNAME are taken into consideration. The exception NOT_FOUND is triggered for all other types.
The internal representation of the runtime object is returned in parameters X030L_WA and X031L_TAB. Depending on the type category, this information is then edited in the corresponding parameters (see documentation about the parameters).
Notes
1. If parameter LFIELDNAME is not initial, X031L_TAB nevertheless contains the description of all fields of the structured type. The decoded form is only determined for the specified field, and the result is copied to DFIES_WA instead of DFIES_TAB. Since decoding for all the fields often takes up most of the runtime for this module, you should set parameter LFIELDNAME if you only need information about one field of the structured type.
This module gets the runtime information about a type. This means that only the currently active version of the type is taken into consideration. If none exists, the exception NOT_FOUND is triggered.
The corresponding function module DDIF_<object type>_GET is used to read the actual definition of a type of the ABAP Dictionary.
Caution: These read modules are much less efficient than the modules for defining the runtime information. You should therefore only use them if the runtime information is not sufficient.
2. The documentation for IMPORT parameter GROUP_NAMES describes how to handle named includes.

Generic Data Extraction From SAP R/3 to BI server using Function Module

Hi,
I want step by step procedure for Generic Extraction from SAP R/3 application to BI application
using Functional module.
If any body have any Document or any PPT then please reply and post it in forum, i will give point for them.
Thanks & Regards
Subhasis Pan

please go thr this link
[SAP BI Generic Extraction Using a Function Module|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/s-u/sap%20bi%20generic%20extraction%20using%20a%20function%20module.pdf]
[Generic Data Extraction Using Function Module |Re: Generic Data Extraction Using Function Module;

How to write the exceptions in function module

dear all,
how to write the exceptions in function modules with example.
thanq
jyothi

Hi,
Raising Exceptions
There are two ABAP statements for raising exceptions. They can only be used in function modules:
RAISE except.
und
MESSAGE.....RAISING except.
The effect of these statements depends on whether the calling program handles the exception or not. The calling program handles an exception If the name of the except exception or OTHERS is specified after the EXCEPTION option of the CALL FUNCTION statement.
If the calling program does not handle the exception
· The RAISEstatement terminates the program and switches to debugging mode.
· The MESSAGE..... RAISING statement displays the specified message. Processing is continued in relation to the message type.
If the calling program handles the exception, both statements return control to the program. No values are transferred. The MESSAGE..... RAISING statement does not display a message. Instead, it fills the system fields sy-msgid, sy-msgty, sy-msgno , and SY-MSGV1 to SY-MSGV4.
Source Code of READ_SPFLI_INTO_TABLE
The entire source code of READ_SPFLI_INTO_TABLE looks like this:
FUNCTION read_spfli_into_table.
""Local Interface:
*" IMPORTING
*" VALUE(ID) LIKE SPFLI-CARRID DEFAULT 'LH '
*" EXPORTING
*" VALUE(ITAB) TYPE SPFLI_TAB
*" EXCEPTIONS
*" NOT_FOUND
SELECT * FROM spfli INTO TABLE itab WHERE carrid = id.
IF sy-subrc NE 0.
MESSAGE e007(at) RAISING not_found.
ENDIF.
ENDFUNCTION.
The function module reads all of the data from the database table SPFLI where the key field CARRID is equal to the import parameter ID and places the entries that it finds into the internal table spfli_tab. If it cannot find any entries, the exception NOT_FOUND is triggered with MESSAGE ... RAISING. Otherwise, the table is passed to the caller as an exporting parameter.
Calling READ_SPFLI_INTO_TABLE
The following program calls the function module READ_SPFLI_INTO_TABLE:
REPORT demo_mod_tech_fb_read_spfli.
PARAMETERS carrier TYPE s_carr_id.
DATA: jtab TYPE spfli_tab,
wa LIKE LINE OF jtab.
CALL FUNCTION 'READ_SPFLI_INTO_TABLE'
EXPORTING
id = carrier
IMPORTING
itab = jtab
EXCEPTIONS
not_found = 1
OTHERS = 2.
CASE sy-subrc.
WHEN 1.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno.
WHEN 2.
MESSAGE e702(at).
ENDCASE.
LOOP AT jtab INTO wa.
WRITE: / wa-carrid, wa-connid, wa-cityfrom, wa-cityto.
ENDLOOP.
The actual parameters carrier and jtab have the same data types as their corresponding interface parameters in the function module. The exception NOT_FOUND is handled in the program. It displays the same message that the function module would have displayed had it handled the error.
Or
just have to decide what exceptions u want and under what conditions.
then declarethese exeptions under the exceptions tab.
in the source code of ur function module.
if
like this u can code .
now when u call the function module in tme mainprogram.
if some error occurs and u have declared a exception for this then it will set sy-subrc = value u give inthe call of this fm.
in the fm u can program these sy-subrc values and trigger the code for ur exception.
Please reward if useful
Regards,
Ravi
Edited by: Ravikanth Alapati on Mar 27, 2008 9:36 AM

Can you call a function module from within a smartform?

I was told that yu can not call a function module from a smartform - that does not make sense to me because you can do tons of ABAP within a smartform.
Well - can you?
Thanks.
Scott

Yes, you can call function modules.

Is there a BAPI function module which reverses the sign of an integer

Hi Friends,
 Could u plz tell me a BAPI function module which can reverse the
sign of an integer ?
For example:
if i get the integer value in work area as <number> <sign> , i need to change it to <sign><number>.
i.e if i get the integer value in work area as "248-" ("-" indicates minus sign) to " -248 ".
i.e if i get the sign after the value , my requirement is to get the sign before the value.
The actual ABAP query is:
data: QTY_1 TYPE CHAR10,
 QTY_2 TYPE CHAR10,
 WA_DISTK_PORTLET-QUANTITY TYPE INT4.
QTY_1 = WA_DISTK_PORTLET-QUANTITY.
 SEARCH QTY_1 FOR '-'.
 IF SY-SUBRC = 0 AND SY-FDPOS <> 0.
 SPLIT QTY_1 AT '-' INTO QTY_1 QTY_2.
 CONDENSE QTY_1.
 CONCATENATE '-' QTY_1 INTO QTY_1.
 CONDENSE QTY_1.
 ELSE.
 CONDENSE QTY_1.
 ENDIF.
 CLEAR: WA_DISTK_PORTLET-QUANTITY.
 MOVE : QTY_1 TO WA_DISTK_PORTLET-QUANTITY.
when i move this QTY_1 to work area quantity field The sign is coming after the numeric value.
Note: There is no possibility to change the datatype of quantity field.
I have tried my level best with 'CLOI_PUT_SIGN_IN_FRONT' function module.
I will assign full points to the correct function module.

Hi Ram,
try this ang look into fields.
data: fields type table of SVAL with header line.
fields-tabname = 'MARA'. fields-fieldname = 'MATNR'. append fields.
fields-tabname = 'BKPF'. fields-fieldname = 'BUDAT'. append fields.
CALL FUNCTION 'POPUP_GET_VALUES'
EXPORTING
 POPUP_TITLE = 'Value Insert'
TABLES
 FIELDS = fields.
Regards, Dieter

Function module SD_SCHEDULING: delivery date calculation factory calendar

Hi,
When I create or change a sales order, system calculates the delivery time and date (ETDAT) using transit duration and factory calendar. Currently factory calendar says that transportation leaves every Monday, Wednesday and Friday. Unfortunately, function module SD_SCHEDULING calculates the delivery date using factory calendar dates, i.e. NOT using working dates.
Function module reads the factory calendar from table TVRO (Routes) and field SPFBK (Factory calendar key) in subroutine GET_CUSTOMIZING, and saves factory calendar id in CS_SCHEDDU-TRANSIT_FC. The calculation itself is done later in function module DATE_CONVERT_TO_FACTORYDATE.
For example, if transit duration is 3 working days, function module calculates the delivery date using Monday (first day), Wednesday (second day) and Friday (third day). Thus, the result is Friday, which is wrong. Result should be of course Wednesday (Monday first day, Tuesday second day and Wednesday third day).
I'd like to use working days instead of calendar days. I am planning to recalculate the delivery date in some user exit, but before I start coding, I'd like to hear your opinion: Is it possible to use working days instead of calendar days when calculating delivery date? (I believe it must be, since my case is very normal). If it is, I assume that this can be achieved with IMG, but how and where?
I am using SAP R/3 Enterprise.
Regards,
Jarmo Tuominen

Hi jarmo,
1. DATE_CHECK_WORKINGDAY
 Probably this FM may be useful to u.
2.
CALL FUNCTION 'DATE_CHECK_WORKINGDAY'
 EXPORTING
 date = d
 factory_calendar_id = '01'
 message_type = 'I'
 EXCEPTIONS
 date_after_range = 1
 date_before_range = 2
 date_invalid = 3
 date_no_workingday = 4
 factory_calendar_not_found = 5
 message_type_invalid = 6
 OTHERS = 7.
regards,
amit m.

Exceptions in function module.... for beginner......

Dear all experts,
I am new to ABAP.
Can anybody please tell, how to use the exceptions in function module ?
and if any exception happens, then how to link some messages to that exceptions?
I will also like to know, how to create those messages ?
Can anybody please illustrate with help of example, so that a beginner will be able to understand. ?
eg, i am adding two numbers in function module, and if any one passing number is negative, then i need to raise exception with message please do not enter -ve numbers for addition.
your help will be surely, rewarded with points.
waiting for reply.
Regards & Thanks
Vinay.

hi..
Raising Exceptions
There are two ABAP statements for raising exceptions. They can only be used in function modules:
RAISE <except>.
and
MESSAGE..... RAISING <except>.
The effect of these statements depends on whether the calling program handles the exception or not. If the name <except> of the exception or OTHERS occurs in the EXCEPTIONS addition of the CALL FUNCTION statement, the exception is handled by the calling program.
If the calling program does not handle the exception
The RAISE statement terminates the program and switches to debugging mode.
The MESSAGE ..... RAISING statement display the specified message. How the processing continues depends on the message type.
If the calling program handles the exception, both statements return control to the program. No values are transferred. The MESSAGE ..... RAISING statement does not display a message. Instead, it fills the system fields SY-MSGID, SY-MSGTY, SY-MSGNO, and SY-MSGV1 to SY-MSGV4.
Source Code of READ_SPFLI_INTO_TABLE
The entire source code of READ_SPFLI_INTO_TABLE looks like this:
FUNCTION READ_SPFLI_INTO_TABLE.
""Local interface:
*" IMPORTING
*" VALUE(ID) LIKE SPFLI-CARRID DEFAULT 'LH '
*" EXPORTING
*" VALUE(ITAB) TYPE SPFLI_TAB
*" EXCEPTIONS
*" NOT_FOUND
SELECT * FROM SPFLI INTO TABLE ITAB WHERE CARRID = ID.
IF SY-SUBRC NE 0.
 MESSAGE E007(AT) RAISING NOT_FOUND.
ENDIF.
ENDFUNCTION.
The function module reads all of the data from the database table SPFLI where the key field CARRID is equal to the import parameter ID and places the entries that it finds into the internal table SPFLI_TAB. If it cannot find any entries, the exception NOT_FOUND is triggered using MESSAGE...RAISING. Otherwise, the table is passed to the caller as an exporting parameter.
Also check these links
http://help.sap.com/search/highlightContent.jsp
http://help.sap.com/search/highlightContent.jsp
http://help.sap.com/search/highlightContent.jsp
regards,
veeresh

How to create EXCEPTION in function module

hi experts,
          how to create exeptions in function module i want step by step.
regards,
chaitu

hi,
Raising Exceptions
There are two ABAP statements for raising exceptions. They can only be used in function modules:
RAISE except.
und
MESSAGE.....RAISING except.
The effect of these statements depends on whether the calling program handles the exception or not. The calling program handles an exception If the name of the except exception or OTHERS is specified after the EXCEPTION option of the CALL FUNCTION statement.
If the calling program does not handle the exception
·         The RAISEstatement terminates the program and switches to debugging mode.
·         The MESSAGE..... RAISING statement displays the specified message. Processing is continued in relation to the message type.
If the calling program handles the exception, both statements return control to the program. No values are transferred. The MESSAGE..... RAISING statement does not display a message. Instead, it fills the system fields sy-msgid, sy-msgty, sy-msgno , and SY-MSGV1 to SY-MSGV4.
Source Code of READ_SPFLI_INTO_TABLE
The entire source code of READ_SPFLI_INTO_TABLE looks like this:
FUNCTION read_spfli_into_table.
""Local Interface:
*"       IMPORTING
*"             VALUE(ID) LIKE SPFLI-CARRID DEFAULT 'LH '
*"       EXPORTING
*"             VALUE(ITAB) TYPE SPFLI_TAB
*"       EXCEPTIONS
*"              NOT_FOUND
SELECT * FROM spfli INTO TABLE itab WHERE carrid = id.
IF sy-subrc NE 0.
    MESSAGE e007(at) RAISING not_found.
ENDIF.
ENDFUNCTION.
The function module reads all of the data from the database table SPFLI where the key field CARRID is equal to the import parameter ID and places the entries that it finds into the internal table spfli_tab. If it cannot find any entries, the exception NOT_FOUND is triggered with MESSAGE ... RAISING. Otherwise, the table is passed to the caller as an exporting parameter.
Calling READ_SPFLI_INTO_TABLE
The following program calls the function module READ_SPFLI_INTO_TABLE:
REPORT demo_mod_tech_fb_read_spfli.
PARAMETERS carrier TYPE s_carr_id.
DATA: jtab TYPE spfli_tab,
      wa   LIKE LINE OF jtab.
CALL FUNCTION 'READ_SPFLI_INTO_TABLE'
     EXPORTING
          id        = carrier
     IMPORTING
          itab      = jtab
     EXCEPTIONS
          not_found = 1
          OTHERS    = 2.
CASE sy-subrc.
WHEN 1.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno.
WHEN 2.
    MESSAGE e702(at).
ENDCASE.
LOOP AT jtab INTO wa.
WRITE: / wa-carrid, wa-connid, wa-cityfrom, wa-cityto.
ENDLOOP.
The actual parameters carrier and jtab have the same data types as their corresponding interface parameters in the function module. The exception NOT_FOUND is handled in the program. It displays the same message that the function module would have displayed had it handled the error.
Hope this is helps,Do reward.

Correct Function module Read CDPO CDHDR

Similar Messages

Maybe you are looking for