PI7.11 - IDOC processing in AAE available?

I know that they were going to get IDOC adapter reside in AAE so mapping/parsing/persistence would take place within AAE (without Integration Engine).
Does anyone know if this is available in PI now?  If so, which version?
Thanks!

IDOC adapter is not yet available in AAE with 7.11 version.
They are palnning to include in future versions.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/700058f0-b1a1-2a10-39a8-ab2627b87cfa?quicklink=index&overridelayout=true|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/700058f0-b1a1-2a10-39a8-ab2627b87cfa?quicklink=index&overridelayout=true]
Refer Page-1 of above link.

Similar Messages

  • Idoc processing best practices - use of RBDAPP01 and RBDMANI2

    We are having performance problems in the processing of inbound idocs.  The message type is SHPCON, and transaction volume is very high.  I am a functional consultant, not an ABAP developer, but will try my best to explain our current setup.
    1)     We have a number of message variants for the inbound SHPCON message, almost all of which are set to trigger immediately upon receipt under the Processing by Function Module setting.
    2)      For messages that fail to process on the first try, we have a batch job running frequently using RBDMANI2.
    We are having some instances of the RBDMANI2 almost every day which get stuck running for a very long period of time.  We frequently have multiple SHPCON idocs coming in containing the same material number, and frequently have idocs fail because the material in the idoc has become locked.  Once the stuck batch job is cancelled and the job starts running again normally, the materials unlock and the failed idocs begin processing.  The variant for the RBDMANI2 batch job is currently set with a packet size of 1 and without parallel processing enabled.
    I am trying to determine the best practice for processing inbound idocs such as this for maximum performance in a very high volume system.  I know that RBDAPP01 processes idocs in status 64 and 66, and RBDMANI2 is used to reprocess idocs in all statuses.  I have been told that setting the messages to trigger immediately in WE20 can result in poor performance.  So I am wondering if the best practice is to:
    1)     Set messages in WE20 to Trigger by background program
    2)     Have a batch job running RBDAPP01 to process inbound idocs waiting in status 64
    3)     Have a periodic batch job running RBDMANI2 to try and clean up any failed messages that can be processed
    I would be grateful if somebody more knowledgeable than myself on this can confirm the best practice for this process and comment on the correct packet size in the program variant and whether or not parallel processing is desirable.  Because of the material locking issue, I felt that parallel processing was not desirable and may actually increase the material locking problem.  I would welcome any comments.
    This appeared to be the correct area for this discussion based upon other discussions.  If this is not the correct area for this discussion, then I would be grateful if the moderator could re-assign this discussion to the correct area (if possible) or let me know the best place to post it.  Thank you for your help.

    Hi Bob,
    Not sure if there is an official best practice, but the note 1333417 - Performance problems when processing IDocs immediately does state that for the high volume the immediate processing is not a good option.
    I'm hoping that for SHPCON there is no dependency in the IDoc processing (i.e. it's not important if they're processed in the same sequence or not), otherwise it'd add another complexity level.
    In the past for the high volume IDoc processing we scheduled a background job with RBDAPP01 (with parallel processing) and RBDMANIN as a second step in the same job to re-process the IDocs with errors due to locking issues. RBDMANI2 has a parallel processing option, but it was not needed in our case (actually we specifically wouldn't want to parallel-process the errors to avoid running into a lock issue again). In short, your steps 1-3 are correct but 2 and 3 should rather be in the same job.
    Also I believe we had a designated server for the background jobs, which helped with the resource availability.
    As a side note, you might want to confirm that the performance issues are caused only by the high volume. An ABAPer or a Basis admin should be able to run a performance trace. There might be an inefficiency in the process that could be adding to the performance issue as well.
    Hope this helps.

  • IDOC process

    gud mrng,
    after creating the idoc function module,how are we writing the code?
    how are we using the standard idoc?

    Hi Priya ,
    Check this .....
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Reward if useful.
    Regards,
    Chitra

  • Statistics (overview) for Synchronous messages processed via AAE

    Hello,
    We are on PI 7.11
    Is there any way to get synchronous messages processed via AAE displayed on RWB Message Monitor Overview view?
    Maybe there is some parameter available similar to messaging.syncMessageRemover.removeBody for persisting payloads for sync messages.
    Thanks!
    Best Regards,
    Artsiom Anichenka

    Mark,
    But I think there is already (PI 7.11) a possibility to persist payloads for java-only sync messages. I was mentioning this parameter in my original post:
    messaging.syncMessageRemover.removeBody
    this parameter is true by default and if you set it to false payloads will not be deleted, but this is not our aim. We want payloads to be deleted from sync messages, but we also want to see those messages on RWB MessageMonitor for overview.
    For me this is somekind of frustrating that the overview page doesn't really give you overview of what is happening on your system, like what and how many messages where processed...
    So can you please specify what is really planned for 7.31. Did you meant that parameter I am mentioning above or we will really get sync java-only messages to overview?
    Best Regards,
    Artsiom Anichenka

  • Creation of rfilr ports in WE21 from LSMW IDOC Processing

    Hi,
    I am trying to defile a file port for INBOUND IDOC processing status in LSMW.
    Now when I go to create a file port in WE21, I give some dummy Physical directory name. But what should I give in
    Function module field and Outbound file field ? Is it compulsary to put something in these fields...
    Please help.....

    Hi,
    Function module field is used to define the path functionality of file generated.
    EDI_PATH_CREATE_CLIENT_DOCNUM is the recommned fucntion by SAP .
    Function is used to prevent unprocessed files being overwritten.Tihs function generates file directory path dynamically.
    Hope this helps.
    Thanks.
    Mark points if helpful.

  • IDOC process in QM

    Hi,
      Can any one help me to understand the use of IDOC Process in QM???
    In which scenarios we will use IDOC in QM. 

    Hi,
    May be this link will help you.
    http://scn.sap.com/thread/171671
    sandip

  • Basic doubts in ALE/IDOC processing

    Hi All,
    1.How are IDOC Type and Message Type related? Many to one or One to Many?
    2. what is the prominence of msg code and msg function in ALE outbound processing?
    3. During outbound processing what is the startegy followed by the ALE service layer to pick up the customer model?
       It would be great if any one can answer these questions in plain words rather than referring links. Reward guaranteed.

    Hi Ravi,
    1.Can'te we assign more than one IDOC to the same msg type if the IDOC's are of different versions?
    Yes we can. Doesn't SAP do that? For example, ORDERS01, ORDERS02 ... ORDERS05 are having the same message type ORDERS. You can also create your own IDoc type or extend the standard IDoc type.
    3. When we run a stand alone program to trigger IDOC processing the only mandatory field will be the message type, so how can the sending system identify the receiving system?
    You need to setup partner profile (t/code WE20) and distribution model (t/code BD64). Once this configuration are done, The system will populate automatically the IDoc Control Record for sender and recepient system information when the IDoc generated based partner profile setup.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Payment Processing Temporarily not available, try again later.

    Hey Guys,
    I might have a solution for the folks who are getting the error "Payment Processing Temporarily not available, try again later".
    If you have an active credit card and trying to purchase/register in the iTunes store this error pops up. On contacting support, they will tell you to check with the bank and they will also suggest an alternative solution for this(purchasing an iTunes Gift Card).
    My Perspective on the Problem:
    The bank or the service which Apple is using to process your card is not a 24hrs service. I am not aware if the same problem is being faced in US, Canada & UK. But seeing the previous discussions on this error, most of the Apple users in India and other countries are facing this. I reside in India and I have faced this problem.
    My Proposed Solution:
    Try registering your card after 9.30am GMT. I was trying to register my card all day long and as soon it was 3am IST, my card got processed and I was able to make purchase on iTunes. So, 3am IST is 9.30am GMT. 9.30am GMT must be the opening time for the day at the bank/service which apple uses to bill users. So, 8 hrs from 9.30am GMT should be the time you should try to use your card on iTunes.
    Apple should take care of this.

    I had this happen earlier this week - thought perhaps it was a Netflix problem.when it contined the next day, I looked for a reset button - there isn't one.  So, I just pulled one of the plugs out from the back of the Apple TV, waited a second and plugged it back in.  Worked like a charm and could now watch my movie.

  • Inbound idoc processing by workflow

    Hello,
    How can I find if an inbound IDoc has been processed via workflow ?
    following are details -
    1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
    2)manual re process in test system using WE19 has all four status records by login user ID.
    3)BD67 values for this process code was checked for the start events.
    4)I checked standard task 30200090 following oss note 325361
    5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020 
    I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
    thank you very much in advance,
    Bhakti

    Hello,
    How can I find if an inbound IDoc has been processed via workflow ?
    following are details -
    1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
    2)manual re process in test system using WE19 has all four status records by login user ID.
    3)BD67 values for this process code was checked for the start events.
    4)I checked standard task 30200090 following oss note 325361
    5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020 
    I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
    thank you very much in advance,
    Bhakti

  • Inbound Idoc processing issues - Partner Profiles - error status 56

    Hello All,
    I'm having a little difficulty posting an idoc coming from MDM.  It's a CREMDM04 xml coming from an MDM system.  It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs.  The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe).  I'm using nothing but standard mapping/material from the SAP Business Content for XI.  After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
    The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
    The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc.  How is the RCVPRN value being populated? 
    SOAP Header in IDocOutbound tag
      <SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
      <SAP:RCVPRN>[String Value]</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
    I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere.  Perhaps i'm just overlooking it?
    When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
    Any help is very much appreciated! :-D

    Hi Jason ,
    Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
    To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
    STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
    We need to do the following settings in XI
    1) Create an RFC Destination to the Receiving System in transaction code (SM59)
    a) Choose create
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client, user & Password details of Destination system
    h) Test the connection and remote logon.Both should be succesful
    2) Create Port Using Transaction Code IDX1
    a) Select Create New button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client
    d) Enter the RFC Destination created in XI towards R/3
    e) Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1
    SETTINGS IN SAP R/3
    We need to do the following settings in R/3
    Logon to Sap R/3 System
    1) Create an RFC Destination to XI in transaction code (SM59)
    a) Choose create
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client, user & Password details of Destination system
    h) Test the connection and remote logon.Both must be succesful
    2) Create communication Port for Idoc processing Using Transaction(We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile with Inbound Parameters (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang
    Then Save
    e) Select Partner no. and LS which were create above
    f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
    g) Select Message type
    h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
    I) save
    4) In Transaction SALE, Create Logical System
    a). Go to Basic Settings-> First Define logical systems
    and then assign logical systems
    b) Double click on Define the logical systems
    c) Give data for your Logicaal System and Name
    d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e) Assign the logical system name to the client
    do let me know if it helped
    Edited by: Tom  Jose on Feb 21, 2008 9:04 AM

  • Send mail to a specific user group when an Inbound Idoc processing fails

    I am using standard Message type DEBMAS, but the process code is customed (say ZDEBM as the function module is customed). Can you tell me what configurations are required to activate the error notification message to a user when the inbound idoc fails?

    hi,
    i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
    if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
    ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
    Workflow functions as follows:
    A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
    If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
    If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
    For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
    1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
    2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
    3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
    If an error occurs, the system determines:
    1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
    2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
    3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
    regards,
    pankaj singh

  • RBDAP001 causing a short dump when submitted in a FM for IDOC processing

    Hi All Gurus,
    I have a situation wherein I need to automate the processing of failed INBOUND IDOCS.
    So the status of failed IDOCS could be 51 or 64 or anything like that.
    I tried using statement 'SUBMIT RBDAP001 with......'. in a custom FM , however I got a short dump.
    When I debugged I realised that RBDAP001 pops up a screen with the final IDOC processing result which probably may be the cause of dump. Dump message is 'CNTL_ERROR'.
    <u>So is there a way how I can suppress this screen</u> <b>OR</b> <u>use any other function module to process these inbound Idocs.</u>
    Appreciate your advise on same.
    Thanks and Regards
    RK

    Hi Rajiv,
    Please use program RBDMANI2 to reprocess IDoc with status 51.
    Also check program RBDINPUT for reprocessing IDoc with other statuses.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • How to control IDOC processing in XI

    hi
    I have scenario where File --> XI --> IDOC
    Source structure
    Header           1...1
        Detail         0..unbounded
    Trailer             1..1
    For every detail i need to generate 1 doc
    My requirement is that i dont want to send all the IDOCs at one shot from XI.
    trfc connection should be open just once for all the IDOCs and not single IDOCs are posted.
    Is there any transaction from where i can control my IDOC processing.
    Need urgent help.
    Thanks ,
    Loveena

    Hi Loveena,
    in a scenario, for instance, where you send IDOCs of type LS (logical system):
    1. In the sender system, call transaction WE05 to display the outbound IDoc. The IDoc partner type of both receiver and sender is LS.
    2. On the Integration Server, call transaction SXMB_MONI (Integration Engine Monitoring Monitor for Processed XML Messages) to display the message.
    3. In the receiver system, call transaction WE05 to display the inbound IDoc.
    if it helpful reward points are appreciated

  • IDOC Acknowledgement is really available?

    Hi there.
    I need your help.
    In first, my scenario is as follow.
    R/3(IDOC) -> XI -> FILE(XML)
    I found the acknowledgement from XI to R/3 is automatically generated and send. But it is not proper structure so it is not recognized correctly in R/3.(status 51)
    error txt----
    IDoc: Invalid table name 'TPSDLS ' in inb. status via IDoc
        Message no. EA 863
    Diagnosis
        When processing the inbound IDoc 0000000008194949 with status records,
        the unauthorized name TPSDLS occurred in the field TABNAM.
    System Response
        IDoc processing terminated with an error.
    Procedure
        Only the name 'EDI_DS' or the name 'EDI_DS40' can be sent in the field
        TABNAM.
    cf. TPSDLS is Message Type.
    But in XI(SXMB_MONI), outbound message is as follow.
      </SAP:Ack>
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>100</SAP:MANDT>
      <SAP:DOCREL>640</SAP:DOCREL>
      <SAP:DOCNUM>0000000000000453</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>ALEAUD</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPAXP</SAP:SNDPOR>
      <SAP:SNDPRN>ADC_UPSTMS</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPNAQ</SAP:RCVPOR>
      <SAP:RCVPRN>LOG_150</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL>20060131223008</SAP:SERIAL>
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS>03</SAP:STATUS>
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>2006-02-01</SAP:CREDAT>
      <SAP:CRETIM>03:43:12</SAP:CRETIM>
      <SAP:ARCKEY>C758B94092FE11DAA9C9000E7FECFC0E</SAP:ARCKEY>
      </SAP:IDocOutbound>
    Already I applied OSS NOTE.899200.( It's a bit helpfull)
    Someone ask to use BPM, but I want to use this funtion first.
    Many thanks for your advice in advance.
    Billy

    Hi Naresh,
    the version is currently in Ramp-up.
    To get a sneak preview you can download the 2007 B pre-upgrade tool. The tool will create an additional sbo-common on your server which faciliates mock-upgrades of databases on the server.
    You don't even have to back up a db before subjecting it to the simulated upgrade.
    The thus upgraded database is not functional in the sense that you will not be able to add transactions, yet it will allow you to see all existing data & run reports.
    We highly recommend to run this pre-upgrade tool on all databases you are planning to upgrade to 2007 B to gauge the IRU impact. You can download the tool & find a multitude of information including a 'How-to-Guide' on the reconciliation landing page:
    Go to the 2007 B landing page & then access 'New Reconciliation Engine - Learn more'.
    All the best,
    Kerstin

  • Function module creation for IDOC processing...

    hi Experts,
                 i want to create a function module for idoc processing..
    message type: zashpmnt
    idoc type : shpmnt05
    plz tell me which standard FM is used... and tell me what changes i want to do in it....
    Tnx in Advance..

    Hello,
             If you are trying to process an Outbound IDoc for the SHIPMNT05 IDoc Type with an Extension, you can use the IDOC_OUTPUT_SHPMNT Function Module which is assigned to SHPM Process Code.
           In Addition, since you have an IDoc Extension, you are required to populate the Custom Segment / Fields. For this, there is a Customer Function / Exit called EXIT_SAPLV56K_002 which you can use it for adding your Custom Segments to the IDoc ZSHPMNT05.
           If you are writing code in this exit, make sure to create a Project in CMOD.
           Also, ensure that you've made the assignment in WE82 with the Message Type , IDoc Type & the Extension.
           For Inbound, if you would like to Create a Custom Function Module, you can follow the Naming Convention Z_IDOC_INPUT_SHPMNT for which you are required follow the below Steps.
    1. Register the FM as Inbound FM in BD51 T-Code.
    2. Assign the FM to IDoc Type & Extension in WE57.
    3. You'll need to Create a Custom Process Code in WE42 in which you are required to make add your FM.
    4. Maintain Partner Profiles in WE20.
    5. Have the Process Code Migrated to the Testing Environment as creation of Custom Process Code is a Customizing Activity and it requires a Customizing Request to be created / Migrated.
    6. Define the Parameters as defined in the Standard Inbound Function Modules such as IDOC_INPUT_ORDERS , IDOC_INPUT_DELVRY etc.
    Thanks and Regards,
    Venkat Phani Prasad K

Maybe you are looking for