Please suggest about the MM;functional module.

Hi All,
Myself Megha, i am new in the SAP world and would like all you gurus to guide me with right path.I am an Engineer in IT with 2 years of work x in Network Aminstraton, As per my qualifications i am eligble for SAP technical module(Basis), but my personal intrest is in retail sector. So i want to go for MM module(Procurrement).
If you guys can suggest me about the technical difficulties and future prospectives, then it will be a great help.
THANKS
Megha Mittal

Hi..
to sum up MM .. and life cycle
MM Material Management
MM module allows the company to manage on time the
stocks, procurement, and purchase templates.
- Purchasing,
- Inventory Management
-      Consumption Based Planning
-      Logistics Invoice Verification
-      External Services Management
-      Evaluation
-      Supplier Workspace
-      Information systems
comming to procurement ..
Procurement starts with requirement which is triggered by MRP. Requirement can be Dependent Requirement (Sale Order, Production Order) or Independent Requirement (Stationery Requirement).
Procurement: Procurement just not involves procuring of material. When a Requirement Triggers, right from creation of Requisition to sending the Purchase order to vendor is taken care by Procurement. This involves creation of Requisition, approval of Requisition, creation of RFQ if needed, converting of Requisition to Purchase order, identifying medium to send PO to vendor, and PO monitoring.
1. Initial Screen    Dead Line Purch Org Purch Grp
2.Collective
3.Item Detail   Material Qty
4.VendorDetails
Few Transaction Code:
ME51n: Create PR
ME52n: Change PR
ME53n: Display PR
ME54n: Release PR individually
In a PO, materials or services can be procured for all the Plants attached to the Purch
   Org. for which PO is created
Standard PO, Subcontracting PO, Consignment PO, STO and Third Party PO are
      different types of PO and they are differentiated with Document Type.
Document Overview screen PO, displays different Purchasing documents like RFQ, PR,      other POs.
with regards,
hari kv

Similar Messages

I want to know about the POPUP_SHOW_INTTAB function module.

what are all the parameters that needs to be passed.

Hi there,
I've played around with this FM recently and tested it in a demo program. It is a bit complex to display the data of an internal table this way. You have many options to design your output. Perhaps you will get a better insight on the parameters by checking my demo-program.
Good luck.
REPORT zmd_oce_057.
TYPES: BEGIN OF ts_itab1,
         tdobject TYPE ttxid-tdobject,
         tdid   TYPE ttxid-tdid,
         tdtext TYPE ttxit-tdtext,
       END OF ts_itab1.
TYPES: tt_itab1 TYPE SORTED TABLE OF ts_itab1 WITH UNIQUE KEY tdobject tdid,
       tt_itab2 TYPE STANDARD TABLE OF ts_itab1.
TYPES: BEGIN OF ts_ttxit,
         tdobject TYPE ttxit-tdobject,
         tdid     TYPE ttxit-tdid,
         tdtext   TYPE ttxit-tdtext,
       END OF ts_ttxit.
TYPES: tt_ttxit TYPE SORTED TABLE OF ts_ttxit WITH UNIQUE KEY tdobject tdid.
TYPES: BEGIN OF ts_fldlst.
        INCLUDE STRUCTURE dd03p.
TYPES: END OF ts_fldlst.
TYPES: tt_fldlst TYPE STANDARD TABLE OF ts_fldlst.
DATA: gt_itab1   TYPE tt_itab1,
      gt_itab2   TYPE tt_itab2,
      gs_itab1   TYPE ts_itab1,
      gt_ttxit   TYPE tt_ttxit,
      gs_ttxit   TYPE ts_ttxit,
      gt_fldlst TYPE tt_fldlst,
      gs_fldlst TYPE ts_fldlst,
      gd_tabname TYPE dd03p-tabname,
      gd_index   TYPE i,
      gd_langu   TYPE t002-laiso.
SELECT tdobject tdid
FROM ttxid
INTO TABLE gt_itab1.
SELECT tdobject tdid tdtext
FROM ttxit
INTO TABLE gt_ttxit
WHERE tdspras = sy-langu.
LOOP AT gt_itab1
INTO gs_itab1.
    gd_index = sy-tabix.
    READ TABLE gt_ttxit
    INTO gs_ttxit
    WITH KEY tdobject = gs_itab1-tdobject
             tdid     = gs_itab1-tdid.
    gs_itab1-tdtext = gs_ttxit-tdtext.
    MODIFY gt_itab1
    FROM gs_itab1
    INDEX gd_index
    TRANSPORTING tdtext.
ENDLOOP.
Language according to ISO 639
CALL FUNCTION 'CONVERSION_EXIT_ISOLA_OUTPUT'
    EXPORTING
      input = sy-langu
    IMPORTING
      output = gd_langu.
mandatory fill 'FELDLISTE'
gs_fldlst-tabname    = 'gt_itab2'.
gs_fldlst-fieldname = 'TDOBJECT'.
gs_fldlst-ddlanguage = gd_langu.
gs_fldlst-position   = '1'.
gs_fldlst-rollname   = 'TDOBJECT'.
gs_fldlst-intlen     = 10.
APPEND gs_fldlst TO gt_fldlst.
gs_fldlst-tabname   = 'gt_itab2'.
gs_fldlst-fieldname = 'TDID'.
gs_fldlst-ddlanguage = gd_langu.
gs_fldlst-position   = '2'.
gs_fldlst-rollname   = 'TDID'.
gs_fldlst-intlen     = 4.
APPEND gs_fldlst TO gt_fldlst.
gs_fldlst-tabname   = 'gt_itab2'.
gs_fldlst-fieldname = 'TDTEXT'.
gs_fldlst-ddlanguage = gd_langu.
gs_fldlst-position   = '3'.
gs_fldlst-rollname   = 'TDTEXT'.
gs_fldlst-intlen     = 30.
APPEND gs_fldlst TO gt_fldlst.
non-standard tables cannot be passes with tables!
mandatory fill 'INTTAB'
gt_itab2[] = gt_itab1[].
mandatory fill 'TABNAME'
gd_tabname = 'Incompletion_log'.
CALL FUNCTION 'POPUP_SHOW_INTTAB'
    EXPORTING
     tabname   = gd_tabname
    TABLES
      feldliste = gt_fldlst
      inttab    = gt_itab2.

Could you please explain about the chain and end chain and module

hi experts
could you please explain about the chain and end chain and module keywords?

Hi Naresh,
Conditions for Multiple Screen Fields
To ensure that one or more PAI modules are only called when several screen fields meet a particular condition, you must combine the calls in the flow logic to form a processing chain. You define processing chains as follows:
CHAIN.
ENDCHAIN.
All flow logic statements between CHAIN and ENDCHAIN belong to a processing chain. The fields in the various FIELD statements are combined, and can be used in shared conditions.
CHAIN.
FIELD: <f1>, <f 2>,...
MODULE <mod1> ON CHAIN-INPUT|CHAIN-REQUEST.
FIELD: <g1>, <g 2>,...
MODULE <mod2> ON CHAIN-INPUT|CHAIN-REQUEST.
ENDCHAIN.
The additions ON CHAIN-INPUT and ON CHAIN-REQUEST work like the additions ON INPUT and ON REQUEST that you use for individual fields. The exception is that the module is called whenever at least one of the fields listed in a preceding FIELD statement within the chain meets the condition. So <mod1> is called when one of the fields <fi> meets the condition. <mod2> is called when one of the fields <f i> or <g i> meets the condition.
Within a processing chain, you can combine individual FIELD statements with a MODULE statement to set a condition for a single field within the chain:
CHAIN.
FIELD: <f1>, <f 2>,...
FIELD <f> MODULE <mod1> ON INPUT|REQUEST|*-INPUT
|CHAIN-INPUT|CHAIN-REQUEST.
MODULE <mod2> ON CHAIN-INPUT|CHAIN-REQUEST.
ENDCHAIN.
The module <mod1> is called when screen field <f> meets the specified condition for individual fields. <mod2> is called when one of the fields <fi> or <f> meets the condition. If you use the addition ON CHAIN-INPUT or ON CHAIN-REQUEST with FIELD <f>, the condition also applies to the entire chain and module <mod1> and <mod2> are both called.
In cases where you apply conditions to various combinations of screen fields, it is worth setting up a separate processing chain for each combination and calling different modules from within it.
The functions of the FIELD statement for controlling data transport also apply when you use processing chains. Within a processing chain, screen fields are not transported until the FIELD statement. Processing chains also have another function for the FIELDS statements that they contain. This is described in the section on validity checks.
Ex:
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CHAIN.
FIELD: INPUT1, INPUT2.
MODULE MODULE_1 ON CHAIN-INPUT.
FIELD INPUT3 MODULE MODULE_* ON *-INPUT.
MODULE MODULE_2 ON CHAIN-REQUEST.
ENDCHAIN.
FIELD INPUT1 MODULE C1 AT CURSOR-SELECTION.
CHAIN.
FIELD: INPUT2, INPUT3.
MODULE C2 AT CURSOR-SELECTION.
ENDCHAIN.
MODULE CURSOR AT CURSOR-SELECTION.
Regards,
Sunil

Doubts about some popular function modules?

Hi all,
I have doubts about these function modules (see in parenthesis)
ws_filename_get (to get the file name at ...?)
ws_query (to get file size and environment variables from the presentation server to the ...?)
upload and download (what are the new function modules used in place of these (I know they are obsolete now)
what is the Object oriented equivalents of these functions?
Thanks.
Charles.
++++++++++++++++++++++++++++++++++++

(1)What is the use of ws_filename_get? Please be specific in your answer, about where the file resides: application server, presentation server or the ABAP program.
It is simply providing an interface for the user to choose a filename which resides on the frontend PC(presentation server). As suggested already, this has been replaced with FILE_OPEN_DIALOG method of the class CL_GUI_FRONTEND_SERVICES.
2)What is the use of ws_query? Please be specific in your answer, about where the file resides: application server, presentation server or the ABAP program.
Again, already answered, this has been replace by multiple more specific methods of the same class mentioned above.
How can GUI_UPLOAD be a substitute of Upload? It is a substitute of WS_UPLOAD as upload is used to transfer data from presentation server to the ABAP program, whereas the other two are used to get it from presentation server to the application server.
They all transafer data from the presentation to your application. They are all interchangable(in a sense), but you should be using the GUI_UPLOAD method of the class CL_GUI_FRONTEND_SERVICES.
Regards
Rich Heilman

Need to know the standard function module/program in E recruitment

Hi All,
I need to know the standard function module/programm that defaults the 'Functional area' field in the posting page from the requisition page.
Early responce is greatly appreciated.
Thanks and best regards
Rajeev

Hi Masa,
Thanks for your reply.
We are using Assets with the integration of Project systems. We are now in 4.6C R/3 & SRM 5.0 system. And now R/3 upgrade and SRM upgrade going on smultaniously to ECC6.0 and SRM 7.0 respectively.
I would like to know any new functionality available in the latest upgrades and we have done lot of customization for Asset Procurement. And would like to go with Vanilla.
Can you please provide me some inputs about the Project (WBS element ) based Asset Procurement in SRM as standard.
Thanks and Regards,
Ramesh

Need to know the standard function module in E-Recruitment

Hi All,
I need to know the standard function module that defaults the value of 'Functional area' in 'Posting' from 'Requisition'.
Early response is greatly appreciated.
Thanks an best regards
Rajeev

Hi Masa,
Thanks for your reply.
We are using Assets with the integration of Project systems. We are now in 4.6C R/3 & SRM 5.0 system. And now R/3 upgrade and SRM upgrade going on smultaniously to ECC6.0 and SRM 7.0 respectively.
I would like to know any new functionality available in the latest upgrades and we have done lot of customization for Asset Procurement. And would like to go with Vanilla.
Can you please provide me some inputs about the Project (WBS element ) based Asset Procurement in SRM as standard.
Thanks and Regards,
Ramesh

Change the standard function module

The standard function module FI_DUPLICATE_INVOICE_CHECK will check whether an invoice/credit memo has already been posted where all of the following attributes match: Company code, vendor, currency, document date, reference number (If a reference number was entered in the current invoice/credit memo). If no reference number was entered in the current invoice/credit memo the system checks whether an invoice/credit memo has already been posted where all of the following attributes match: Company code, vendor, currency, document date, amount in document currency
my requirement is
The above functionality described in the short description doesnt provide for the need within AP to check on duplicate invoices. The functionality in FI differs from the functionaltiy provided in LIV and therefor needs to be aligned. The risk of posting duplicate invoice entry is eminent since the check is dependent on all parameters. For a good duplicate invoice number check we need FI to check on Vendor and invoice reference within the same fiscal year. To modify rules, copy FI_DUPLICATE_INVOICE_CHECK, modify the checks and then call the copied function module from FB60. The remaining field check in the standard function module should be deleted.
how to achive this. i didn't understand the requirement .Please give me any suggestion for this.

Hi ,
I think what you are saying is the functionality given in Logistics Invoice verification is not suitable for FI Invoice.
If I am correct , then there is a configuration setting in SPRO where you set check for duplicate invoice. It has just three checkboxes
a) Company code b) Reference number c) Invoice date
so I think this configuration setting will suffice your requirement.
Please let me know.
Amit

How to create the INBOUND Function Module for INBOUND IDOCs

Hi Friends,
Can any Suggest me How to proceed to Create an INBOUND Function Module for Processing the INBOUND IDOCS
which are recieved from XI Server ?
I am working in SAP-ISU
Here i will recieve the INBOUND IDOCs for the Meter Reading Orders.
We have a Standard INBOUND FUNCTION MODULE
IDOC_INPUT_ISU_MR_UPLOAD
which Uploads the Meter Reading Results.
I copied the Same function Module into ZIDOC_INPUT_
and working on it.
Can any one suggest me, whether i am going in correct way or not.
In IDOC_INPUT_ISU_MR_UPLOAD Inbound fun module,
BAPI_MTRREADDOC_UPLOAD is used to Update or Insert the Meter Reading Results,
My requirment is to Insert and Update the Meter Reading Orders which are Inbounded from XI.
Can I Use the Same BAPI
BAPI_MTRREADDOC_UPLOAD
to Update the below fields,
EABL-SERNR
EABL-ZWNUMMER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS
EABL-ADATTATS
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Kindly Suggest me,
Thanks in Advance,
Ganesh

Hello Ganesh
I think you are going completely astray with you z-function module for IDoc processing.
If you look at TABLES parameter METERREADINGRESULTS (type BAPIEABLU ) of BAPI_MTRREADDOC_UPLOAD you will find many of the requested fields already:
EABL-SERNR => BAPIEABLU-SERIALNO
EABL-ZWNUMMER =>REGISTER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS => ACTUALMRTIME
EABL-ADATTATS => ACTUALMRDATE
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Field EABL-ZMESSAGE appears to be custom field (at least I cannot find it on ECC 6.0). If this field was added using include CI_EABL then you probably can get these values into the BAPI using the EXTENSIONIN parameter.
Check routine CHECK_UPLOADRECORDS in the BAPI which allows two extension structures:
- BAPI_TE_EABL
- BAPI_TE_EOSB
Not surprisingly BAPI_TE_EABL contains the include CI_EABL.
Regards
Uwe

How to find the existing function module is used in another function module

Hi all,
I created a function module and the same one is called from another function module.
When I tried to find where the first function module is used using Where-used List , I am getting the message "function module not found in selected areas" .
Please guide me what is other method to find whether the function module is used in another one.
Thanks,
Vengal Rao.

hi,
Go to UTILITIES-> Update Navigation index.
or go to fucntion group and Generate the Funtion group once.
it will detect all fucntion modules under that function group.
regards,
Rama

How to find the Obsolete function module in ECC 6.0

Hi Guys,
How we can find the all obsolete function in ECC 6.0, is any T-code to finding the obsolete function modules, or any other way to find.
Could you please help me.
Thanks,
Gourisankar.

Hi Gouri,
If you are looking at determining whether a single FM is obsolete or not is by this method:
Go to FM in SE37 -> Goto Attributes Tab -> General Data section -> look above the Edit Lock field ... where SAP places the release status and date of the FM, if the FM is obsolete, the text Function Obsolete appears
This is one way of finding out one FM @ a time
However if you want to check on a mass scale, I dont have a SAP system here hence cant confirm, however, all FMs are stored in TFDIR database table. Please scroll through the fields of the DB table to check whether any field relates to release status or the like. If it does, then from SE16, you can put the value corresponding to "Obsolete" in the field and run to check all FMs.
Cheers,
Aditya

Regarding the Remote Function Module

hi,
Can any body can provide the brief information regarding the Remote Function Module.
1)How to create the remote function module
2)how it differ from the normal function module
3)any special features about this.
Thanks in advance

Hi
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm
check out the following link it might help you
http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf
Function Modules;
Check this matter.
Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.
You can create them from TCode SE37.
Go through the following doc:
Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.
Function Module Interfaces
The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:
Syntax
... [IMPORTING parameters]
[EXPORTING parameters]
[CHANGING parameters]
[TABLES table_parameters]
[{RAISING|EXCEPTIONS} exc1 exc2 ...]
The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with [CLASS-]METHODS. The additional option of defining table parameters using TABLES is obsolete.
Interface parameters
The interface parameters are defined on the relevant tab pages in the Function Builder.
IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.
EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.
CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.
TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.
Exceptions
The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.
The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.
The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.
Note
For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.
RFC is a technology which is used to access a functions (Modules) from
the remote systems.
If a function module is set as remote enabled which can be access from
the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.
A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".
But Normal function modules can not accessd from the remote system.
Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)
Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.
CALLING A FUNCTION MODULE:
1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"
--> Write the Corresponding FM name --> Hit Enter
2)The appropriate import ,export Parameters will be displayed in ur editor
3)Pass the Values Here.
Also check these links.
http://www.geocities.com/victorav15/sapr3/abapfun.html
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
See the following links:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
Reward points for useful Answers
Regards
Anji

Travel Display Form: Error while determining the form function module

Hi,
In Travel Reqeust (ECC6/ESS) when i click the Display Form after raising the Travel Request it shows the error
"Error while determining the form function module"
Can anyone have idea on this?
Regards,
Boobalan

Hi,
This error was due to Not supported platforms of ADS (Adobe Document services)
It was not supported on itanium64 bit processors.
Please check where the ADS is supported in service.sap.com/pam
You can use the ADS in the Non-Supported Server by linking it to Supported Platform Server using the SM59 link. This will make the ADS files to work.
Please refer the ADS Config Doc for details.
Hope you also solve this problem.
Regards,
Boobalan

Using the MSG_* Function Modules

Hello,
I want to use the MSG_* function modules (e.g. MSG_OPEN, MSG_ACTION ...) and the MAC_MSG_* macros in my own programs, but they are not documented. Are there any docs about it?
Regards
Stefan

Hi,
Check this link
http://wwwcs.uni-paderborn.de/cs/heiss/lehre/pg/intern/docs/bc_xbp_45.pdf
Also see Re: Read Application Log
Thanks & Regards,
Judith.

Purpose of all the below Function Modules?

Hi All,
What is the Purpose of all the below Function Modules?
CALL FUNCTION 'K_REPO_PCA_AUTHORITY_CHECK'
CALL FUNCTION 'K_PCA_RESP_AUTHORITY_CHECK'
CALL FUNCTION 'G_CURRENCY_FROM_CT_GET'
CALL FUNCTION 'GET_CURRENT_YEAR'
CALL FUNCTION 'BDC_OPEN_GROUP'
CALL FUNCTION 'BDC_INSERT'
CALL FUNCTION 'MESSAGE_TEXT_BUILD'
Akshitha.

Hi,,
G_Buffer_ReSET-->Deleting Buffer in Set Manager
G_SET_ENCRYPT_SETID-->Conversion of Combination of Characteristics in a Set ID
G_SET_GET_INFO-->Checks whether Set exists and Provides Information about Set
Reward IF useful

WHAT ARE THE UPDATED FUNCTION MODULES

Hi Friends,
Can anybody explain me about UPDATED FUNCTION MODULES (types of function modules)

Hi
Update Function Module
Unlike transactions and executable programs, dialog modules do not start a new SAP LUW. Calls to update-task function modules from a dialog module use the same update key as the ones in the calling program. The result is that calls to update function modules from a dialog module are executed only if a COMMIT WORK statement occurs in the calling program.
If you place a COMMIT WORK in a dialog module, it does commit changes to the database (for example, with UPDATE).However, it does not start the update task. The function modules are not actually executed until a COMMIT WORK statement occurs in the calling program.
If you use dialog modules, try to avoid including calls to update function modules in subroutines called with PERFORM ON COMMIT. In general, any occurrence of PERFORM ON COMMIT(with or without update-task function calls) in a dialog module can be problematic.
This is because dialog modules have their own roll area, which disappears when the module finishes. Consequently, all local data (including data used for parameter values when calling an update function module) disappears as soon as the commit in the main program is reached.
If you must use this method in a dialog module (i.e. include the call to an update-task function in a subroutine), you must ensure that the values of the actual parameters still exist when the update-task function actually runs. To do this, you can store the required values with EXPORT TO MEMORY and then import them back into the main program (IMPORT FROM MEMORY) before the COMMIT WORK statement
Creating Update Function Modules
To create a function module, you first need to start the Function Builder. Choose Tools ® ABAP Workbench, Function Builder. For more information about creating function modules, refer to the ABAP Workbench Tools documentation.
To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to one of the following values:
Update with immediate start
Set this option for high priority ("V1") functions that run in a shared (SAP LUW). These functions can be restarted by the update task in case of errors.
Update w. imm. start, no restart
Set this option for high priority ("V1") functions that run in a shared (SAP LUW). These functions may not be restarted by the update task.
Update with delayed start
Set this option for low priority ("V2") functions that run in their own update transactions. These functions can be restarted by the update task in case of errors.
To display the attributes screen in the Function Builder, choose Goto ® Administration.
Defining the Interface
Function modules that run in the update task have a limited interface:
Result parameters or exceptions are not allowed since update-task function modules cannot report on their results.
You must specify input parameters and tables with reference fields or reference structures defined in the ABAP Dictionary.
http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4daa79e11d1950f0000e82de14a/frameset.htm
Regards,
Harish

Please suggest about the MM;functional module.

Similar Messages

Maybe you are looking for