Why there is need to define processing code (we41/we42) in Idocs?

Hi All,
  Why there is need to define the processing codes when we already have defined the processing function for the IDOC type & message type combinations via we57.

Hi,
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/content.htm
The inbound function module needs to be linked to the message type and the mess type needs to b linked to the appropriate process code at the partner oprofile level before  any scenario is enabled.
Regards,
Gayathri

Similar Messages

  • Why do we need to define RFC destination and user for material replication

    Dear Experts,
    why do we need to define RFC destination and user for material replication? Here we use crm middleware only for material replication. Could you please help me to understand it?
    regards,
    Ranjan

    Hello,
    As far as I know, you can use the same RFC destination already available in ECC to SRM to replicate materials.
    You can refer to note 720819.
    Regards,
    Ricardo

  • How to write processing code for the Inbound IDOC to the R/3 ??

    i m having a file -> XI-->R/3 scenario,
    IDOC is being sent from XI to R/3,
    can u guide to me to write a processing code for the Inbound IDOC to the R/3,
    since i m new to ABAP and ALE technology, can we provide me any blog for doing that.......or guide me....

    Hi Sudeep
    Simple File to Idoc scenarion blog
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
    Also see the blog
    <a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> by Ravikumar.
    Configuration of IDOC adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm
    Regards
    Santhosh
    *Reward points if useful*

  • Why dont we need process code for outbound master idoc?

    For inbound master idoc we need a process code (EX. matmas03-MATM) but for <b>outbound master idoc</b> why dont we need process code?can anybody clarify me on that.
    thanx in advance....

    plz clarify me on that...its urgent...

  • DELV process code triggers unwanted inbound idoc!

    Hi,
    I am creating a delvry03 idoc with message type shpord.The process code is DELV.I am sending the idoc from LS to KU.I maintained the outbound parameters in both receiving and sender systems.The outbound is creating perfect.However, there is an unwanted inbound idoc that is being created.All the inbound idocs getting created in this way is in error.I am not able to understand why the inbound idoc is getting created.
    I see DELV as both outbound and inbound process codes, but then i am not able to understnad why shpord message type is getting processed.I have not done the distribution model as the receiving system is customer.
    Could someone help me out in this weird scenario.Thanks

    Duplicate in ABAP General deleted.  Post in ONE forum only, please.
    matt

  • Process code or Fmodule  for Idoc type PREQCR101 and message type PREQCR1

    hi all,
           Iam unable to find the process code or function module for the idoc type PREQCR101 and message type PREQCR1 for inbound process.
    help from some one would be a lot appretiated.

    Hi,
    Go to transaction WE57 and you can find the processing FM and message type that are associcated to the IDOC type.
    For process code if it is Inbound check WE42 and outbound check WE41 transactions
    Regards
    Shiva

  • Why do I need to define these in std for my random access iterator???

    Hi guys,
    I have written my own iterator class, to support 1-d slices of 2-d matrices, 2-d slices of 3-d matrices, etc.
    At first I wrote the class as a bidirectional iterator, but then I needed to extend it to random access so that I could pass these iterators to std::sort etc. No problem, I thought, I just needed to add friend operators for "iterator-iterator" and "iterator+/-distance".
    So, I did that and tested the code with VS6 and various versions of g++, with no problems. Isn't STL great!
    But I had endless problems with Studio 10. It kept griping that various mostly-internal-looking template functions were not defined. The only way I could get it to work was to define these:
    #if (defined __SUNPRO_CC) && (__SUNPRO_CC <= 0x570)
    namespace std
         template<typename T>          // Sigh
         typename matrixit<T>::
         difference_type distance(const matrixit<T>& a, const matrixit<T>& b) {
              return b-a;
         template<typename T>           // WTF?
         T* __value_type(const matrixit<T>&) {
              return static_cast<T*>(0);
         template<typename T>           // WTF?
         typename matrixit<T>::
         difference_type* __distance_type(const matrixit<T>&) {
              return static_cast<typename matrixit<T>::difference_type*>(0);
         template<typename T>           // WTF?
         typename matrixit<T>::
         iterator_category __iterator_category(const matrixit<T>&) {
              return typename matrixit<T>::iterator_category();
    #endif
    Why do I have to do this, or am I missing something in my iterator class (eg, typedefs), or do I need to derive it from something? Here is what it looks like:
    template<typename T>
    class matrixit
    public:
         typedef T&                         reference;
         typedef T*                         pointer;
         typedef T                         value_type;
         typedef size_t                    size_type;
         typedef ptrdiff_t               difference_type;
         typedef std::random_access_iterator_tag iterator_category;
    Ta, Simon.

    Come on, it is not that hard to work around the limitations of Cstd. For what you show here, you can use:
    namespace std {
    template <class Iterator> struct iterator_traits
    typedef typename Iterator::value_type value_type;
    typedef typename Iterator::difference_type difference_type;
    typedef typename Iterator::pointer pointer;
    typedef typename Iterator::reference reference;
    typedef typename Iterator::iterator_category iterator_category;
    template <class T> struct iterator_traits<T*>
    typedef T value_type;
    typedef ptrdiff_t difference_type;
    typedef T* pointer;
    typedef T& reference;
    typedef random_access_iterator_tag iterator_category;
    template <class T> struct iterator_traits<const T*>
    typedef T value_type;
    typedef ptrdiff_t difference_type;
    typedef const T* pointer;
    typedef const T& reference;
    typedef random_access_iterator_tag iterator_category;
    template <class ForwardIterator>
    inline ptrdiff_t
    distance (ForwardIterator first, ForwardIterator last)
    ptrdiff_t n = 0;
    __distance(first, last, n,
    iterator_traits<ForwardIterator>::iterator_category());
    return n;
    template <class InputIterator, class T>
    inline typename iterator_traits<InputIterator>::difference_type
    count (InputIterator first, InputIterator last, const T& value)
    typename iterator_traits<InputIterator>::difference_type result;
    count(first,last,value,result);
    return result;
    template <class InputIterator, class Predicate>
    inline typename iterator_traits<InputIterator>::difference_type
    count_if (InputIterator first, InputIterator last, Predicate pred)
    typename iterator_traits<InputIterator>::difference_type result;
    count_if(first,last,pred,result);
    return result;
    template < class T >
    inline typename T::value_type*
    __value_type (const T&)
    { return (typename T::value_type*)(0); }
    template < class T >
    inline typename T::difference_type*
    __distance_type(const T&)
    { return (typename T::difference_type*)(0); }
    template < class T >
    inline typename T::iterator_category
    __iterator_category (const T&)
    typename T::iterator_category tmp;
    return tmp;
    } // namespace std
    For the missing constructor of vector with iterators, you can simply use std::copy with a back_insert_iterator.
    The hardest thing to work around is probably the missing conversion between std::pair of various types (for instance with various constness when you use std::map), but it can still be handled by always specifying the type of the pair instead of relying on std::make_pair.
    And if there is a thing you really don't know how to work around, you can always ask here...

  • Why there is need for upgradation

    Hi All,
    can some one help me out with why we need to go for SAP BW upgradation to SAP BI 7.0?
    Thanks,

    Hi Bazi,
    In BW 7.0 you have more tools to help you designing your data model. I would say also that, even though you have much more tools, the data flows have even become much more simple.
    In BW 7.0, to trigger data loads inside the BW system, you have DTPs. In BW 3.x, you had only InfoPackages. That is an advace, because in BW 7.0, you won't necessarily need a staging DSO. That is because you may load first to the DataSource via InfoPackages and then into the InfoProviders you want, via DTP. Check the following thread: [Re: Is it compulsory to create ODS in BW?|Re: Is it compulsory to create ODS in BW?]
    RSA1 is more well organized. There are more divisions and the searches are simpler.
    Instead of having the dataflow:
      DataSource -> Transfer Rule -> InfoSource -> Update Rule -> InfoProvider
    You may construct a much simpler flow:
      DataSource -> Transformation-> InfoProvider
    There is also the new Archiving functionality.
    There are many new features in BW 7.0 and it's really worth it.

  • Why do they need credit card security code to download load a free app

    I have the iBook app and have been notified of an update, when I selected install I was asked fro my credit card security number, which after the recent press were hundreds of apple members personnel details had been stolen this is a bit naughty until they prove they are trust worthy, I feel that as they already have the information from when I purchased the iPad and many other apps a free upgrade does not need such high security. Unless I'm wrong, please tell me why?

    I've missed the press reports about stolen details but I have heard of fraudulent purchases being made on accounts where the Apple ID & Password have become compromised. Not so long ago I found myself having to a one-time revalidation of my credit card and also tighten up my password. You might also be prompted for details if your credit card on file expires. I'm sure you would prefer that you and you alone got access to your account so I would suggest you perform the account validation and then remove your credit card from file - i.e. switch your payment method to none. You should be able to obtain free updates thereafter, at least until the next major tweak to security demands we all revalidate ourselves.
    (Actually, I think you might be asked for some additional info. each time you use a new device to try to access your account which again would be a positive anti-fraud strategy)
    tt2

  • Need help in creating process codes

    Hi All,
    I need to create some message type and assign it to some idoc type , and i need to create process code and inbound function module for this.
    Can some one please help me in this regard.
    Thanks ,
    Hem

    hi
    CATSDB CUSTOM IDOC TRANSFERMATION BETWEEN 2 DIFFERENT APPLICATION SERVERS
    For this scenario Client 800 of application server SAPADM is the Sender and client 800 of application server SAP-REMOTE is the Receiver
    1. Creating Logical Systems
    o       Login using 800 client
    o       Go to T. Code SALE
    o       Expand Sending and Receiving Systems
    o       Expand Logical Systems
    o       Click on Define Logical System
    o       Click on New Entries
    o       Create CATSSENDER, ECC Logical Systems
    o       Save and come back
    o       Assign the CATSSENDER Logical System to client 800 of Application Server SAPADMAssign the ECC Logical System to client 800 of Application Server SAP-REMOTE
    2. Creating the RFCs
    o       Go to T. Code SM59
    o       Expand R/3 Connections
    o       Enter RFC Name as CATSSENDER
    o       Connection Type as 3
    o       Language as EN
    o       Client as 800
    o       User as SAPUSER
    o       Password as YESV13
    o       Target host as SAPADM
    o       Click on Remote logon button to test the RFC
    o       Enter RFC Name as ECC
    o       Connection Type as 3
    o       Language as EN
    o       Client as 800
    o       User as SAPUSER               
    o       Password as YESV123
    o       Target host as SAPADM                                                                               
    o       Click on Remote logon button to test the RFC
    3. Creating the Message Type
    o       Go to T. Code WE81
    o       Click on change, continue
    o       Click on New Entries button
    o       Give message type as ZCATSTIME and description
    o       Save and back
    4. Creating the Segment
    o       Go to T. Code WE31
    o       Give segment name as ZSEGMENTTIME
    o       Enter Short Text
    o       Enter the Field Name and Data Element in the text boxes
    o       Save, continue,
    o       Click on Edit -> Set Release
    5. Creating the Basic IDOC Object
    o       Go to T. code WE30
    o       Give obj. name as ZTIMEIDOC
    o       Click on create
    o       Select create new radio button, give description and continue
    o       Select the IDOC obj name and click on create button
    o       Enter the segment name which is create earlier
    o       Select the check box if you want to make the segment mandatory
    o       Enter 1 in minimum number 99999 in maximum number, continue
    o       Save and backo       Click on Edit -> Set Release
    6. Creating Customer Distribution Model
    o       Go to T. Code BD64
    o       Click on change and Create model view button
    o       Enter the short text and Technical name as CATSSENDER
    o       Select the model and click on Add Message Type Button
    o       Give the Sender as CATSSENDER,
    o       Receiver as ECC,
    o       Message Type as ZCATSTIME
    o       Select the model view & click on Environment -> Generate Partner Profiles
    o       Select Transfer IDOC Immediately and Trigger Immediately radio buttons
    o       Click on Execute
    o       You should get a list in green color which means it executed successfully.
    o       Back to main screen, select the model view
    o       Click Edit->Model view->Distribute
    o       Click on continueo     
    You should get a list saying model view is distributed successfully.
    7. Checking the Port
    o       Go to T. Code WE21
    o       Expand Transactional RFC
    o       Find the port from the list which is created using BD64 for ECC (Receiving system) RFC Destination.
    8. Checking the Partner Profiles.
    o       Go to T. Code WE20
    o       Expand Partner Type LS
    o       Select the Partner profile ECC
    o       Double click on Message Type ZCATSTIME in Outbound parmtrs.
    o       Check Receiver Port is assigned correctlyo     
    Check the Basic type as your Basic IDOC object.
    9. Assigning the Message Type to Basic IDOC Object
    o       Go to T. Code WE82
    o       Click on Change & continue, New Entries button
    o       Give the Message type as ZCATSTIME
    o       Give Basic Type as ZTIMEIDOC
    o       Release as 4.6C
    o       Save and back10. Creating Inbound Function Module (Posting Program)
    o       Go to T. Code SE37
    o       Create a function Module ZCATSDB_TIMESHEET_SURESH
    o       Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.   
    o       Import Parameters
              P_WORKDATE                    LIKE               CATSDB-WORKDATE
              P_COUNTER                        LIKE               CATSDB-COUNTER
              P_LSTAR                               LIKE               CATSDB-LSTAR
    o       Export Parameters
    o       Tables 
                 S_PERNR                      LIKE           ZCATSPERNR
    [PERNR is select option parameters in ZCUSTOMIDOC report program so that it should be passed to function module ZCATSDB_TIMESHEET_SURESH in tables section. And also in tables section we used ZCATSPERNR, which is a global structure, which contains four fields as
    Ø     SIGN
    Ø     OPTION
    Ø     LOW
    Ø     HIGH]
    o       Exceptions
    o       Source Code
    FUNCTION zcatsdb_timesheet_suresh.
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(P_WORKDATE) LIKE  CATSDB-WORKDATE
    *"     VALUE(P_COUNTER) LIKE  CATSDB-COUNTER
    *"     VALUE(P_LSTAR) LIKE  CATSDB-LSTAR
    *"  TABLES
    *"      S_PERNR STRUCTURE  ZCATSPERNR
      TABLES: catsdb, edidc, edidd. " using structures of catsdb, edidc, edidd
      CONSTANTS: c_doctyp TYPE edidc-idoctp VALUE 'ZTIMEIDOC',  " idoc type
                 c_segnam TYPE edidd-segnam VALUE 'ZSEGMENTTIME',   "segment type
                 c_mestyp TYPE edidc-mestyp VALUE 'ZCATSTIME'.   " message type
    *001 comment begin
         creating internal tables with out header lines for catsdb, edidc, edidd and also
    -           work areas
    *001 comment end
      DATA: it_edidc  TYPE edidc OCCURS 0,    "  control internal table with out header line
            it_edidd  TYPE edidd OCCURS 0, " data internal table with out header line
            wa_catsdb TYPE it_catsdb1,  " work area for it_catsdb internal table
            wa_edidc  TYPE edidc,  " work area for it_edidc internal table
            wa_edidd  TYPE edidd,  " work area for it_edidd internal table
            wa_zsegmenttime TYPE zsegmenttime, " work area for zsegment internal table
            v_occmax  TYPE idocsyn-occmax,
            v_nbseg   TYPE i.
      CLEAR wa_catsdb. " clears work area of catsdb
      CLEAR wa_edidc.  " clears edidc work area
    *002  comment begin
    Save the message type and the basic IDoc type in the control segment.
    *002 comment end
      MOVE c_mestyp TO wa_edidc-mestyp. " assigning custom message type to edidc workarea
      MOVE c_doctyp TO wa_edidc-idoctp. " assigning custom idoc type to edidc workarea
    *003 comment begin
    Retrieve the maximum number of segments in the basic IDoc type.
    *003 comment end
      SELECT MIN( occmax ) FROM idocsyn INTO v_occmax WHERE idoctyp EQ c_doctyp AND segtyp EQ c_segnam.
    *004 comment begin
    Save the whole CATSDB table content in the IT_ZCATSDB internal table.
    *004 comment end
      SELECT pernr workdate lstar counter FROM catsdb INTO CORRESPONDING FIELDS OF TABLE it_catsdb WHERE pernr IN s_pernr AND workdate EQ p_workdate.
    *005 comment begin
    Create a data segment for each line of IT_ZCATSDB.
    *005 comment end
      IF sy-subrc EQ 0.
        LOOP AT it_catsdb INTO wa_catsdb WHERE pernr IN s_pernr.
          MOVE-CORRESPONDING wa_catsdb TO wa_zsegmenttime.
          CLEAR wa_edidd.
          MOVE c_segnam TO wa_edidd-segnam.
          MOVE wa_zsegmenttime TO wa_edidd-sdata.
          APPEND wa_edidd TO it_edidd.
          CLEAR wa_catsdb.
          CLEAR wa_zsegmenttime.
        ENDLOOP.
      ELSE.
        MESSAGE 'NO DATA FOUND FOR GIVEN SELECTION' TYPE 'I'.
      ENDIF.
    *006 comment begin
    Count the number of data segments.
    *006 comment end
      DESCRIBE TABLE it_edidd LINES v_nbseg.
    *007 comment begin
    If the number of data segments exceeds the maximum allowed number,then display an error message.
    *007 comment end
      IF v_nbseg GT v_occmax.
        MESSAGE  'IDOC ERROR Message' TYPE 'E000'.
      ENDIF.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' " for creating an catsdb idoc
      EXPORTING
      master_idoc_control = wa_edidc
    OBJ_TYPE = ''
    CHNUM = ''
      TABLES
      communication_idoc_control = it_edidc
      master_idoc_data = it_edidd
      EXCEPTIONS
      error_in_idoc_control = 1
      error_writing_idoc_status = 2
      error_in_idoc_data = 3
      sending_logical_system_unknown = 4
      OTHERS = 5
       IF sy-subrc <> 0.
         MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
         WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
       ENDIF.
    ENDFUNCTION.
    Save, check and activate
    111. Assigning the Inbound Function Module to Basic Type & Message Type
    o       Go to T. Code WE57
    o       Click on change, continue, continue and New Entries Button
    o       Enter the Module as ZCATSDB_TIMESHEET_SURESH Type as "F"
    o       Basic Type as ZTIMEIDOC
    o       Message Type as ZCATSTIME
    o       Direction as 2
    o       Save and back
    Now Login in 800 client of Application Server SAP-REMOTE
    12. Assigning the Inbound Function Module in ALE Table
    o       Go to T. Code BD51
    o       Click on continue, New Entries button
    o       Give the Inbound Function Module ZCATSDB_TIMESHEET_SURESH
    o       Give Input t. as 0 (zero)
    o       Save and back13. Creating Process Code
    o       Go to T. Code WE42
    o       Click on Change, New Entries Button
    o       Give Process Code name as ZCATSDB, give Description & Save
    o       Select Processing with ALE Services Radio button
    o       Select Processing by Function Module Radio button
    o       Click the ALE Table (arrow Icon) in Identification
    o       Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS
    o       Give maximum number of repeats 0
    o       Save and back, back
    o       Select the process code from the list & click on Logical Messages Icon
    o       Give the Message Type as ZCATSTIME
    o       Save & Back, Save & Back, Save & Back
    14. Changing the Customer Distribution model in receiving system
    o       Go to T. Code BD64
    o       Click on change and Create model view button
    o       Enter the short text and Technical name as CATSECC
    o       Select the model view & click on Environment -> Generate Partner Profiles
    o       Select Transfer IDOC Immediately and Trigger Immediately radio buttonso       Click on Execute You should get a list in green color which means it executed successfully.15. Assigning the Process Code to Message Type in Receiving System
    o       Go to T. Code WE20
    o       Expand Partner Type LS
    o       Select the Partner Profile CATSSENDER
    o       Double click on Message Type ZCATSTIME in Inbound parmtrs.
    o       Give the Process Code as ZCATSDB
    o       Click on Trigger Immediately Radio button
    o       Save & Back
    Save & Back
    16. Creating the Selection Program (Outbound Program)
    -         Login in client 800.
    -         Go to T. Code SE38
    -         Create a Report Program as ZCUSTOMIDOC with the following code
    REPORT ZCUSTOMIDOC
           NO STANDARD PAGE HEADING.
    TABLES:catsdb. " using structure of cats db table
    *000 comment begin
         this selection screen contains one select option and one parameter
    *000 comment end
    SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS pernr FOR catsdb-pernr.
    PARAMETER: workdate LIKE catsdb-workdate,
              LSTAR like catsdb-LSTAR,
              COUNTER like catsdb-counter.
    SELECTION-SCREEN: END OF BLOCK b1 .
    DATA: wa_val TYPE i.
    wa_val = pernr-high - pernr-low.
    *001 comment begin
          calling custom function module
    *001 comment end
    CALL FUNCTION 'ZCATSDB_TIMESHEET_SURESH'
      EXPORTING
        p_workdate = workdate " passing workdate parameter
        p_LSTAR = LSTAR
        p_counter = counter
      TABLES
        s_pernr    = pernr. " passing pernr select option
    IF sy-subrc EQ 0.
      MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' pernr-low ' AND ' pernr-high .
    MESSAGE i000(zaluri) WITH   'IDOCS CREATED FOR EMPLOYEES BETWEEN' PERNR-LOW 'TO' PERNR-HIGH.
    gives information message if idocs are created for given  employees
    ELSE.
      MESSAGE e000(zaluri) WITH 'NO IDOCS CREATED FOR EMPLOYEES' pernr-low  'TO' pernr-high. " gives error message
    " if idoc is not created
    17. Transferring the CATSDB records from sender Application Server SAPADM   to  receiver Application Server SAP-REMOTE
    -         Execute Report Program ZCUSTOMIDOC
    -         Give the Range of PERSONNEL NO'S, Date, Activity Type, Counter to Transfer
    -         Give Message Type as ZCATSTIME
    -         Give Receiver Logical system as ECC
    -         Execute
    -         You should get the IDOC Number
    -         Take the IDOC Number and go to T. Code WE05 & Execute
    -         In Outbox you can see the IDOC Status
    -         Select the status record in left side window
    -         Double click on the Status record in right side window-         You can see the Control Record, Data Record and Status Records for that IDOC
    If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully
    18. SENDING IDOCS FROM APPLICATION SERVER SAPADM
    TO APPLICATION SERVER SAP-REMOTE USING WEDI
    -         Go to T. Code WEDI & execute or T. Code WE19
    -         Give idoc number it is generated recently
    -         Continue & double click on segment to view data in segment
    -         Click on EDIDC to give port, partner no, message type, partner
    type of receiver. [For sender no need to give any port no leave it as
    blank]
    -         Click on Standard Outbound Processing button and click continue
    -         You will get a message as idocs successfully transferred
    Now Login in Receiver 800 client
    -         Go to T. Code WE05 & Execute
    -         You can see the status record in left side window
    -         If the status no is 53 and color is green, it means the IDOC is posted to Application successfully.
    -         You can see the Log Information by double clicking on the status record in right side window.
    -         Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC
    -         Now go to T. Code SE16
    -         Give the table name CATSDB & press F7
    -         See the contents of the table
    -         The table is updated with the catsdb records transferred from 800 client with our selection program.
    regards
    Nagesh.Paruchuri

  • Why do we need separate t.codes KB11N and KB41N for reposting costs & rev?

    Hi,
    Why do we need separate t.codes KB11N and KB41N for reposting costs and revenues? I noticed that i can still use one t.code KB11N to post both costs and revenues, hence why do we need a separate t.code KB41N for revenues?

    Hi,
    The BAPI for costs allows more options than the one for revenues. For example, via BAPI_ACC_PRIMARY_COSTS_POST  you can select sender Network, what you cannot do via BAPI_ACC_REVENUES_POST. The same is for 'cost object' as a receiver; you can do it only via BAPI for costs. In other aspects, the BAPI for costs could be used to repost revenues as well.
    Regards,
    Eli

  • Need elp to create the process code for inbound idoc !

    When I am creating a process code in WE42 and associating a
    function module then another screen comming while saving....but in that screen in the drop down list..i didnt find the function module....how to solve ?

    Hi,
    Use transaction BD51 to make the FM known as an inbound FM.
    Regards,
    John.

  • Purpose of Process code

    Hi what is purpose of Process Code
    I know there we add Msg type and Function module what is its function that function module will helps in getting the data
    and *what abt Msg type* and Process code there

    Hi,
    R/3 uses the method of logical process codes to detach the IDoc processing and the processing function module. They assign a logical name to the function instead of specifying the physical function name.
    Logical pointer to a processing method
    The IDoc functions are often used for a series of message type/IDoc type combination. It is necessary to replace the processing function by a different one. E.g. when you make a copy of a standard function to avoid modifying the standard.
    Easily replacing  the processing method
    The combination message type/IDoc will determine the logical processing code, which itself points to a function. If the function changes, only the definition of the processing codes will be changed and the new function will be immediately effective for all IDocs associated with the process code.
    For inbound processing codes you have to specify the method to use for the determination of the inbound function.
    After defining the processing code you have to assign it to one or several logical message types. This declaration is used to validate, if a message can be handled by the receiving system.
    The inbound processing code is assigned analogously. The processing code is a pointer to a function module which can handle the inbound request for the specified IDoc and message type.
    The definition of the processing code is identifying the handler routine and assigning a serious of processing options.
    Processing with ALE
    You need to click "Processing with ALE", if your function can be used via the ALE engine. This is the option you would usually choose. It allows processing via the ALE scenarios.
    Associate a function module with a process code
    Table TBD51 to define if visible BTCI is allowed
    For inbound processing you need to indicate whether the function will be capable of dialog processing. This is meant for those functions which process the inbound data via call transaction. Those functions can be replayed in visible batch input mode to check why the processing might have failed.
    WE41     Process code outbound creation
    WE42     Process code inbound
    Regds
    Sivaparvathi
    Please reward points if helpful............

  • All about Process codes

    Hi all,
    Iam doing IDOC( Stock Transfer)--XIFile Scenario.
    Q) For this Do we really need to mention the Process code at We20 --in Outbound Parameters side????
    Regards
    Suman

    Hi Suman
    Purpose of Process Codes
    Definition
    Another name for a specific process, for example function module or workflow. IDocs are read or written in this process.
    Use
    In the partner profiles, the processing is never addressed directly but rather always using a process code. You can therefore replace an old process with a new one for any number of partners by assigning the existing process code to the new process.
    Two types of process code are used in conjunction with the partner profiles:
    ·        Outbound Process Code - if you are using outbound processing under Message Control, the IDoc is generated in the IDoc Interface. The process code names the relevant function module.
    ·        Inbound Process Code - names the function module or workflow which reads the IDoc data and transfers the data to the application document.
    There are also the process codes for exception handling:
    ·        System Process Code - names the workflow which is triggered in inbound or outbound processing when an exception occurs.
    ·        Status Process Code - names the exception workflow which is triggered when an incorrect status is returned by the external system.
    These two types are configured centrally and not on a partner-specific basis and therefore do not have to be maintained when a new process is defined. They were introduced for the sake of completeness, so that each process in the IDoc Interface is addressed using a process code.
    Inbound Process Code
    Use
    The processing module (workflow or application function module) that reads the IDoc data and generates the corresponding documents is found using the inbound process code.
    You must edit the inbound process codes in the following cases:
    ?      You want to use a new process and need a new process code for it.
    ?      You want to assign different processing to process code X.
    ?      You want to switch the ALE services on or off (this is only possible if the processing module is a workflow module). Switching off the ALE services can improve performance (lower memory requirement).
    Features
    The inbound process codes are application-specific. IDoc Basis includes the process code ED08, which forwards inbound IDocs to distributed SAP systems (?Forward Inbound? function). This processing is defined by the workflow WS30000483.
    Activities
    ·         Determine the required process code from the corresponding partner profiles or by choosing SAP Menu ® Tools ® IDoc/ALE ®  Services ®Documentation ® Process Codes (WE64).
    ·         You choose SAP Menu ® Tools ® IDoc/ALE ® Development ® IDoc ® Inbound Processing ® Maintain Process Code (WE41).
    ·         To change an assignment or to make a new entry, choose .
    For more details on Process code kindly follow this link
    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    hope this will definitly solve your problem
    regards
    sandeep Sharma
    PS if helpful kindly reward points
    Edited by: sandeep sharma on Apr 15, 2008 1:32 PM

  • Why do I need ODBC ?

    Ok, I setup successfully an Oracle database and I can access it e.g. through SQLplus.
    Later I could access this database from inside a program like CSharp or Java.
    For that I could code:
    OracleConnection con = new OracleConnection(connectionstring);
    Into this connectionstring I can put all relevant information to access the DB like username, password, Databasename.
    So why do I need to define an ODBC source in menu
    Programs->Administrative Tools->Data Source (ODBC)
    Where do I find a good, quick and easy introduction to ODBC setup?
    Peter

    Just re-posting the reply I had when this was in the Database - General forum...
    Generally, you're not required to create a DSN, you can generally pass in whatever information you'd like in the connection string. Some third party tools prefer (or require) an ODBC DSN to connect rather than trying to build a driver-specific connection string for every driver out there. If you need to configure various non-default options in the ODBC driver, it's also useful to have that centralized rather than trying to keep those options straight in the connection string.
    User DSN's are visible to the current user, System DSN's are visible to all users on the system. Ignore file DSN's
    Was there a follow-up question you wanted to ask here?
    Justin

Maybe you are looking for