IDOC Volume

Whether there is any program or any transaction is there to find out the number of IDOCS has been processed in a system for a stipulated period?
(We are sending PO to our suppliers and I want to determine the volume?)
2) The average lenght of an IDOC?
Thanks

<i>
Whether there is any program or any transaction is there to find out the number of IDOCS has been processed in a system for a stipulated period?
</i>
you can find it with the help of WE02 or WE05.
you have date range in selection screen
Regards
vijay

Similar Messages

  • Average segment size of iDoc?

    We want to integrate 2 systems by using iDoc across WAN. So far we know the iDoc volumes and average iDoc segments, for example 6000 SO iDoc/hour and 250 segments of each iDoc. My understanding is that we need to know the average iDoc segment size to performance network sizing.
    I know the size varies from case to case. But is there a BEST PRACTICE value we can use?
    TIA
    James

    Hi Jinquin,
    >>I happen to find something interesting at http://msg-ibexi.wikispaces.com/message/view/home/10780864, "Maximun size of IDOC segment is 1000 bytes", is it true?
    Yes
    SDATA contains segment data and it is 1000 character long check here
    http://help.sap.com/saphelp_47x200/helpdata/en/1a/0e3842539911d1898b0000e8322d00/content.htm
    Also see the last statement in the link
    http://help.sap.com/saphelp_nw04/Helpdata/EN/78/21740f51ce11d189570000e829fbbd/frameset.htm
    Regards
    suraj

  • Processing large volume of idocs using BPM Processing

    Hi,
    I have a scenario in which SAP R/3 sends large volume say 30,000 DEBMAS Idocs to XI. XI then sends data to 3 legacy systems using jdbc adapter.
    I created a BPM Process which waits for 4 hrs to collect all the idocs. This is what my BPM does:
    1. Wait for 4 hrs Collect the idocs
    2. For every idoc do a IDOC->JDBC Message transformation.
    3. Append to a Big List
    4. Loop at the Big list from step 4 and in the loop for
    5. Start counter from 0 and increment. Append to a Small List.
    6. if counter reaches 100 then send a Batch JDBC Message in send step.
    7. Reset counter after every send.
    8. Process remaining list i.e if there was an odd count of say 5300 idoc then the remaining 53 idocs will be sent in anther block.
    After sending 5000 idocs to above BPM following problems are there:
    1. I cannot read the workflow log as system does not respond.
    2. In the For Each loop which loops through the big list of say 5000 idocs only first pass of 100 was processed after that the workflow item is not moving ahead. It remains in the status as "STARTED" but I do not see further processing.
    Please tell me why certain Work Items are stuck is it becuase I have reached upper limit and is this the right approach? The Main BPM Process is also hanging from last 2 days.
    I have concerns about using BPM for processing such high volume of idocs in production. Please advice and thanks in advance.
    Regards
    Ashish

    Hi Ashish,
    Please read SAPs Checklist for proper usage of BPMs: http://help.sap.com/saphelp_nw04/helpdata/en/43/d92e428819da2ce10000000a1550b0/content.htm
    One point i'm wondering about is why do you send the IDocs out of R/3 one by one and don't use packaging there? From a performance stand point this is much better than a bpm.
    The SAP Checklist states the following:
    <i>"No Replacement for Mass Interfaces
    Check whether it would not be better to execute particular processing steps, for example, collecting messages, on the sender or receiver system.
    If you only want to collect the messages from one business system to forward them together to a second business system, you should do so by using a mass interface and not an integration process.
    If you want to split a message up into lots of individual messages, also use a mass interface instead of an integration process. A mass interface requires only a fraction of the back-end system and Integration-Server resources that an integration process would require to carry out the same task. "</i>
    Also you might want to have a look at the IDoc packaging capabilities within XI (available since SP14 i believe): http://help.sap.com/saphelp_nw04/helpdata/en/7a/00143f011f4b2ee10000000a114084/content.htm
    And here is Sravyas good blog about this topic: /people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
    If for whatever reason you can't or don't want to use the IDoc packets from R/3 or XI there are other points on which you can focus for optimizing your process:
    In the section "Using the Integration Server Efficiently" there is an overview on which steps are costly and which steps are not so costly in their resource consumption. Mappings are one of the steps that tend to consume a lot of resources and unless it is a multi mapping that can not be executed outside a BPM there is always the option to do the mapping in the interface determination either before or after the BPM. So i would sugges if your step 2 is not a multi mapping you should try to execute it before entering the BPM and just handle the JDBC Messages in the BPM.
    Wait steps are also costly steps, so reducing the time in your wait step could potentially lead to better performance. Or if possible you could omitt the wait step and just create a process that waits for 100 messages and then processes them.
    Regards
    Christine

  • IDoc Adapter configuration for very high volumes

    Hi PI Expert,
    I'd like to have some tips about Idoc Adapter configuration in case of very very hudge volumes in "file to Idoc scenario" (adressing ECC) : How to optimize Idoc transmission time PI -> ECC ?
    => parallelization PI -> ECC by using differents comm channel IDocs with differents RFC destinations ?.
    => some other technical parameters in adapter IDoc
    => ...
    Thanks a lot
    Best regard.
    Etienne

    Hi,
    for sure idoc bundling will greatly increase performance: https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2762. [original link is broken] [original link is broken] [original link is broken]
    If you are in 7.1 you can also leverage message packaging: http://help.sap.com/saphelp_nwpi71/helpdata/en/46/79e8e13872275ae10000000a11466f/frameset.htm
    Regards,
    Sergio

  • Split of a Large Volume Outbound Idoc

    Hi,
    anyone who can tell me how split of a large volume outbound idoc works?
    /Elvez

    Hi Elvez,
    One way to split your idoc is to group your idoc into different segments
    You can create segments and group your data logically.
    Go through the following link. It will give you good tips on IDOCs
         http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
      other helpful links are...
         ALE/ IDOC/ XML
         http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
         http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
         http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    Good luck ..Reward me for the same
    Thanks
    Ashok

  • Impact of High Volume of Idocs

    What are the Impacts of High volume of Idocs on the application and what could be the solutions to overcome those impacts.

    Hi,
    IF the high volume is on the inbound side then use the baground posting. If it is on the outbound then use the packet. Also it depends on what is the IDOC that is being sent or received and the business process. If you can send the data in a single IDOC or in a multiple IDOC. This is possible in case like HRMS.

  • IDoc to IDoc Scenario with High Volumes

    We have requirement to load around 2.4 million idocs using XI from source SAP to target SAP system in ~8 hours. It's a IDoc to IDoc scenario with simple mapping involved.
    I Have looked at various weblogs with the design optons such as BPM collect pattern, collect pattern using IDoc XML file and IDoc Packaging.
    I am looking for inputs from real time experiences on such scenarios...i.e performanace statstics, best practices to handle such scenarios, hardware, XI basis tuning etc...
    Please share any experiences on the same...
    Regrads
    Anand

    Thanks Michal and Chandra...
    Chandra,
    I have looked into the weblog mentioned( option 2 - collecting idocs using IDoc XML port).
    I undersatnd that performance would also depened on hardware,tuning, idoc size, mapping complexity etc, but just get a rough idea and to decide on the design I was looking for stats, approaches followed in other projects  and past experiences in such scenarios.
    Michal,
    I cannot avoid collection of idocs as sending idoc's individually from source to target will have performance problems.
    I can avoid BPM by using IDoc XML port collection ( option 2).
    2.4 million idocs in 8 hours would mean that XI needs to process 300K idocs per hour.  I guess I need to try option 2  and check the performance.
    Regards
    Anand

  • Working on LSMW using IDoc method for processing Open Sales Orders

    We are currently in middle of creation of a new instance of production for a different Business SBU. We are looking to utilise the LSMW tool using IDocs for uploading / transferring the open orders to the new box. If some one has worked on LSMW using IDocs, please get in touch and if you could share any documents on the process of utilising the LSMW tool using Idocs for any kind of conversions, it would be great. The following is a sample case.
    1. Each order will have multiple segments with different qualifiers under various segments.
    2. Multiple line items would be available under each order.
    Issues we are currently looking to solve :
    1. How do you manage to loop through the qualifiers during processing for the same segment.
    2. How do you prepare the tool to recognise the multiple line items of the same order.
    3. What kind of strategy needs to be used to create the input data file(s). Like, splitting the header and detail level information ?
    Note  : The volume of data we are looking at is somewhere around 40-60 thousand orders worldwide.
    Thanks in Advance.

    hI vikram check this link
    and reward points if helpful
    http://www.****************/Tutorials/LSMW/IDocMethod/IDocMethod1.htm
    http://www.jt77.com/system-dynamics/model-01395.html

  • EDI IDOC generation for interface with Vendor software help needed.

    EDI IDOC help needed.
    We are NOT an EDI shop, but have a project to output data to Sales Force.com
    Sales Force requests IDOC output - eg. 810 Outbound Invoice.
    We will need to do a historical load of Orders/Quotes/Invoices from the past 2 years.
    Is there a function module or series of FM's that are used to generate the E2EDKxxxxx type segments?
    I have been testing using the IDOC_OUTPUT_INVOIC and IDOC_OUTPUT_ORDRSP FM's, but they generate segments begining with E1EDKxxxxx.
    Basicall we have a report program that the user enteres in the date range of Order/Quotes/Invoices they wish to extract, the the program needs to output a flat file (.txt) on the server which is then picked up by Sales Force.com.
    Also, is there a way to have in the Partner Profile a generic Partner under the "Type KU" that can be used for all orders/invoices so I don't have to create a KU Partner Type for each and every Sold-To customer we have?
    I am very new to EDI so any help would be greatly appreciated.
    Thanks.
    Scott.

    Hi Scott,
    We will need to do a historical load of Orders/Quotes/Invoices from the past 2 years.
    I know it's very tempting to use an interface for such loads if you anyhow have to create one. However, often the volume alone speaks against interface usage for such scenarios.
    Is there a function module or series of FM's that are used to generate the E2EDKxxxxx type segments? I have been testing using the IDOC_OUTPUT_INVOIC and IDOC_OUTPUT_ORDRSP FM's, but they generate segments begining with E1EDKxxxxx.
    Well, the E2* segments basically reflect the external name of the IDoc segment, whereas the function modules you're referring to basically just create an internal version of the IDoc. Once the IDoc framework then passes the IDocs to the partner, the segment names usually (depends on how the IDocs are passed on) get converted to their external name. If there are multiple versions of a segment, then the version number will be appended to the segment name.
    Note that IDoc segment definitions are only partially stored in the data dictionary. If you want to see all versions you should always use transaction WE31 to look at segments. There you can also see for example for E1EDK01 the several versions and when you then use in SE37 function module SEGMENT_EXTERNAL_NAME_GET you will see what SAP produces as the external name for segment E1EDK01. This function module is basically the one that handles the segment name translations.
    Ignore the comments for subsystem, this is basically an option in SAP to possibly trigger further external tools (e.g. mapping etc.) for handling the outbound IDocs.
    Again, the funny thing is that via the WE30 transaction, if i put in INVOIC02 as the Obj. name and see the segments, i can see that E2EDK01 there is a version 005, but if i go to SE11 and put in E2EDK01005 structure line and i get a "not found". We just have up to E2EDK01002.
    In the old days SAP used to generate E1, E2 and E3* structures in the data dictionary (SE11). The E1* structure reflected the character type representation of an IDoc segment, whereas the other two (definition and documentation) contained actual references to data elements (e.g. if you used a quantity field). However, in newer releases those dictionary structures (E2* & E3*) are no longer generated, because they're superfluous (meta data defined via WE31 is sufficient).
    Cheers, harald

  • Inbound IDoc SHPCON - Batch update issue

    Hi all,
    I would like to use SHPCON.DELVRY03 idoc in order to update Outbound delivery document.
    Scope is :
    - picking
    - good issue
    - update batches
    - update serial numbers
    - update volume and weights
    We met issue on update batches a soon as one document item already has batch information before receiving IDoc.
    2 cases :
    - no batch spliting => High level item has already a linked batch (LIPS-POSNR = 000010 and LIPS-CHARG not empty.
    Is there a way to update batch information if external warehouse confirms another batch number ?
    - batch splitting => High level item has already 2 sublines POSNR = 900001 & 900002. Both has batch numbers.
    If I want to confirm it, I can send E1EDL19 with BAS qualifier but sublines are added...
    Must I delete existing sublines with E1EDL19 DEL ?
    Thanks a lot for your help.
    J.C.
    and to post good issue.
    All is OK except

    Hi,
    We are having same issue as of yours...
    i.e Updation of batch via IDOC to the delivery if delivery contains batch ...its not happening and also idoc not throwing any error
    Did you able to resolve this ?
    Thanks
    Rajesh

  • IDOCs issue in XI

    In our IDOC -> XI -> IDOC scenario, we are facing an issue when a large number (~4000) of IDOCs are sent to XI system at the same time.
    The source SAP system sends the IDOCs to the XI system using a system user. When a large volume of IDOCs are sent at the same time, this user takes up all the dialog processes in the XI system.
    The system eventually becomes slow and needs to be restarted.
    One message gets created per IDOC in XI. The mapping between source and target IDOCS is simple. There is no issue with small number of IDOCs.
    Request your suggetions/inputs in this case. Could we make the IDOC process to run in background in XI to avoid this situation?

    Have a look into this thread to know how to improve performance when large IDOCs are transferred:
    Processing of huge IDocs ...
    You can also opt for IDOC packaging : /people/michal.krawczyk2/blog/2007/12/02/xipi-sender-idoc-adapter-packaging
    Regards,
    Abhishek.

  • Flatfile idoc sender scenario

    Hi all,
    we try to implement a flat file-XI-IDoc scenario. We receive flat files with idoc structure
    In ID I used sender file adapter and a receiver idoc adapter
    I have to use the option "File Content Conversion" in the file adapter and do I have to reproduce the whole IDoc structure in the content conversion parameters
    and since i get structure/segment name ahead of each line how to i handle this
    please see below
    adapter content conversion parameters:
    EDI_DC40.fieldFixedLengths     10,3,16,4,2,1,1,1,1,30,30,30,3,3,1,6,6,10,2,2,10,21,70,10,2,2,10,21,70,8,6,14,14,14,70,20
    EDI_DC40.endSeparator     'nlu2019
    EDI_DC40.fieldNames     TABNAM,MANDT,DOCNUM,DOCREL,STATUS,DIRECT,OUTMOD,EXPRSS,TEST,IDOCTYP,CIMTYP,MESTYP,MESCOD,MESFCT,STD,STDVRS,STDMES,SNDPOR,
    SNDPRT,SNDPFC,SNDPRN,SNDSAD,SNDLAD,RCVPOR,RCVPRT,RCVPFC,RCVPRN,RCVSAD,RCVLAD,CREDAT,CRETIM,REFINT,REFGRP,REFMES,ARCKEY,SERIAL
    EDI_DC40.keyFieldValue     0
    EDI_DC40.keyFieldInStructure     ignore
    E1EDL20.fieldFixedLengths     10,4,4,2,4,3,25,3,28,6,2,17,15,3,15,3,5,35,4,20,10,35,35,8,6,3,1,1,1,1
    E1EDL20.endSeparator     'nl'
    E1EDL20.fieldNames     VBELN,VSTEL,VKORG,LSTEL,VKBUR,LGNUM,ABLAD,INCO1,INCO2,ROUTE,VSBED,BTGEW,NTGEW,GEWEI,VOLUM,VOLEH,ANZPK,BOLNR,TRATY,TRAID,XABLN,
    LIFEX,PARID,PODAT,POTIM,LOC_SEQ,HOLD,MAX_ERR_TYPE,LE_SCENARIO,RECIPIENT_CREATE
    E1EDL20.keyFieldValue     0
    E1EDL20.keyFieldInStructure     ignore
    E1EDL22.fieldFixedLengths     30,20,20,20,25,30,40,20,20
    E1EDL22.endSeparator     'nl'
    E1EDL22.fieldNames     VSTEL_BEZ,VKORG_BEZ,LSTEL_BEZ,VKBUR_BEZ,LGNUM_BEZ,INCO1_BEZ,ROUTE_BEZ,VSBED_BEZ,TRATY_BEZ
    E1EDL22.keyFieldValue     0
    E1EDL22.keyFieldInStructure     ignore
    sender file:
    EDI_DC40  3000000001870383062700 3014  DESADV01                                                    DESADV                              X004010856   SAPD7B    LS  SAPD7B                                                                                ZSHIPNOTIFLISP0000000018                                                                                20100513233418                                                                                20100513
    E2EDK07001                    300000000187038306200000100000001000LLF000030003                       6910689255                                                 FOBFREE ON BOARD                                                                                Y5 H502                     oluquilla Wh Domestic              MX00
    E2EDKA1003                    300000000187038306200000200000102
    E2EDK03                       300000000187038306200000300000102
    E2EDK08001                    3000000001870383062000004000000020006910689255                                                 FOBFREE ON BOARD                                                                                Y5 H502                     oluquilla Wh Domestic              MX00                                    BC
    E2EDS01                       3000000001870383062000005000004030011
    E2EDS01                       3000000001870383062000006000004030216.645             KGM
    E2EDS01                       3000000001870383062000007000004030226.646             KGM
    E2EDS01                       3000000001870383062000008000004030236.646             KGM
    E2EDS01                       30000000018703830620000090000040301400001
    the above examples are not complete (just an example) Any help is appreciated.
    Thanks,
    siddu.236atgmail.com

    but the scenario is bit complex, we have SNC involved, we have existing scenario of sender idocs initially built,
    later sender told, he can only send flatfile idoc  - Can you elobarate complete your exitsting scenario if possible do the necessary changes existing one reason is below...
    You should not approach the FCC becuase it's not mandatory all the segments are fields will come always order..IF Data segments field order changed then your FCC will not work properly...FCC always assume that you are getting correct order 100%. I mean field order....
    Regards,
    Venu.

  • IDOC creation from a flat file

    We currently receive a large volume of invoices from freight companies that move our product from point A to B.
    I will receive a file from the vendor with 10 fields.  The fields are BOL, shipdate, shipfrom_pt, shipto_pt, volume, rate, surcharge, total, invoice_no, invoice_dt.
    I may also get them to plug in the Vendor number on creation.
    Currently, our staff uses paper invoice with the BOL & shipdate to locate the PO in our system, then lookup the PO, and if the total in SAP matches to the total on the paper invoice, it is marked for payment (that is the short of it).
    We have eVision already in place which I use to build an iDOC for our Utility bills we receive.  But these occur once a month, whereas we may receive 50+ invoices from a freight vendor.
    Do I have enough information to create an iDOC in SAP, in which SAP will know how to locate and reconcile?  The invoic01 documentation is extensive and examples are nill.  Help on identifying the segments, fields and values necessary to generate an iDOC.
    The alternative is to import the file into SAP and write an ABAP pgm, with BAPI's to search and create the invoice.
    I wanted to go with iDOC as it is SAP's proprietary form for handling inbound records.
    Ralph

    Hi Ralph,
       In my opinion, you must have a PO Number for Invoice if you want to use standard functionality. You will probably need to create IDOC using an ABAP program which reads this file and search for PO based on the information available to you. I also notice that you are missing material number as well, how do you match the item number in the PO ?
       I don't see a way aroung without writing an ABAP program to handle this logic, but you can still use IDOC ( which comes with the standard processing logic and that is a big advantage ) so that you need to write only the PO matching logic.
      or if you are not inclined to write a separate program for uploading file into SAP and formatting IDOC, you can write your own process code (FM)for INVOICE01. Inside this process code (FM), you can put your PO matching logic and then call standard FM (process code). This is what I usually do.
    Cheers,
    Sanjeev
    Cheers,
    Sanjeev

  • Suggest a TABLE CONTAINING THESE IDOC segment FIELDS

    E1MBXYJ : Create Goods Movement from Non-SAP System: Item++
    Segment definition E2MBXYJ001 Released since Release 620 , Segment length: 0476
    For the following fields. Tell me a table which contains a majority or all of the below fields.
    PARGB : Trading partner's business area
    internal data type : CHAR
    Internal length : 000004 characters
    Position in segment : 001, Offset : 0063. external length : 000004
    PARBU : Clearing company code
    internal data type : CHAR
    Internal length : 000004 characters
    Position in segment : 002, Offset : 0067. external length : 000004
    CLASS : Class number
    internal data type : CHAR
    Internal length : 000018 characters
    Position in segment : 003, Offset : 0071. external length : 000018
    UMCLA : Class number
    internal data type : CHAR
    Internal length : 000018 characters
    Position in segment : 004, Offset : 0089. external length : 000018
    XCLAS : Checkbox
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 005, Offset : 0107. external length : 000001
    UMXCL : Checkbox
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 006, Offset : 0108. external length : 000001
    XNIBU : Checkbox
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 007, Offset : 0109. external length : 000001
    BDTER : Requirement Date for the Component
    internal data type : DATS
    Internal length : 000008 characters
    Position in segment : 008, Offset : 0110. external length : 000008
    TBBEL : Article doc. no. of transfer requirement to be cancelled
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 009, Offset : 0118. external length : 000010
    TBBPO : Article doc. item of transf.reqmnt item to be cancelled
    internal data type : NUMC
    Internal length : 000004 characters
    Position in segment : 010, Offset : 0128. external length : 000004
    TBBJR : Article doc. year of transfer requirement to be cancelled
    internal data type : NUMC
    Internal length : 000004 characters
    Position in segment : 011, Offset : 0132. external length : 000004
    OBJNR : Object number
    internal data type : CHAR
    Internal length : 000022 characters
    Position in segment : 012, Offset : 0136. external length : 000022
    AUTYP : Order category
    internal data type : NUMC
    Internal length : 000002 characters
    Position in segment : 013, Offset : 0158. external length : 000002
    QPLOA : Inspection Lot on Which the Usage Decision is Based
    internal data type : NUMC
    Internal length : 000012 characters
    Position in segment : 014, Offset : 0160. external length : 000012
    TBPKZ : Indicator: No Transfer Requirement Created
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 015, Offset : 0172. external length : 000001
    TAFKZ : Indicator: do not cal up automatic TO creation
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 016, Offset : 0173. external length : 000001
    KZEAR_OLD : Final Issue for This Reservation
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 017, Offset : 0174. external length : 000001
    RSART : Record type
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 018, Offset : 0175. external length : 000001
    PPRCTR : Partner Profit Center
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 019, Offset : 0176. external length : 000010
    XMEVO : Propose quantities
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 020, Offset : 0186. external length : 000001
    UMLGT : Storage Type
    internal data type : CHAR
    Internal length : 000003 characters
    Position in segment : 021, Offset : 0187. external length : 000003
    UMLGP : Storage Bin
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 022, Offset : 0190. external length : 000010
    MENGE : Quantity
    internal data type : QUAN
    Internal length : 000013 characters
    000003 decimal places, without sign
    Position in segment : 023, Offset : 0200. external length : 000015
    MEINS : Base Unit of Measure
    internal data type : UNIT
    Internal length : 000003 characters
    Position in segment : 024, Offset : 0215. external length : 000003
    FKBER : Functional Area
    internal data type : CHAR
    Internal length : 000004 characters
    Position in segment : 025, Offset : 0218. external length : 000004
    MHDAT : SLED/Best-Before Date or Date of Production
    internal data type : DATS
    Internal length : 000008 characters
    Position in segment : 026, Offset : 0222. external length : 000008
    BSSKZ : Special movement indicator for warehouse management
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 027, Offset : 0230. external length : 000001
    EXIDV : External Handling Unit Identification
    internal data type : CHAR
    Internal length : 000020 characters
    Position in segment : 028, Offset : 0231. external length : 000020
    BERKZ : Material Staging Indicator for Production Supply
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 029, Offset : 0251. external length : 000001
    PRVBE : Supply Area
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 030, Offset : 0252. external length : 000010
    KZECH : Determination of batch entry in the production/process order
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 031, Offset : 0262. external length : 000001
    UPTYP : Subitem Category, Purchasing Document
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 032, Offset : 0263. external length : 000001
    REFIX : Field defined as in SY-TABIX
    internal data type : INT4
    Internal length : 000010 characters
    Position in segment : 033, Offset : 0264. external length : 000011
    VLIEF_AVIS : Delivery
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 034, Offset : 0275. external length : 000010
    VBELP_AVIS : Delivery Item
    internal data type : NUMC
    Internal length : 000006 characters
    Position in segment : 035, Offset : 0285. external length : 000006
    XWAIT : Checkbox
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 036, Offset : 0291. external length : 000001
    XNOEQ : Checkbox
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 037, Offset : 0292. external length : 000001
    ILINR : IDoc line item number
    internal data type : NUMC
    Internal length : 000006 characters
    Position in segment : 038, Offset : 0293. external length : 000006
    VOLUM : Volume
    internal data type : QUAN
    Internal length : 000015 characters
    000003 decimal places, without sign
    Position in segment : 039, Offset : 0299. external length : 000017
    VOLEH : Volume unit
    internal data type : UNIT
    Internal length : 000003 characters
    Position in segment : 040, Offset : 0316. external length : 000003
    ANZL1 : Number of Storage Units to be Placed Into Storage
    internal data type : DEC
    Internal length : 000003 characters
    No decimal places, without sign
    Position in segment : 041, Offset : 0319. external length : 000004
    ANZL2 : Number of Storage Units to be Placed Into Storage
    internal data type : DEC
    Internal length : 000003 characters
    No decimal places, without sign
    Position in segment : 042, Offset : 0323. external length : 000004
    LMEN1 : Quantity per Storage Unit to be Placed into Stock in Alt.UoM
    internal data type : QUAN
    Internal length : 000013 characters
    000003 decimal places, without sign
    Position in segment : 043, Offset : 0327. external length : 000015
    LMEN2 : Quantity per Storage Unit to be Placed into Stock in Alt.UoM
    internal data type : QUAN
    Internal length : 000013 characters
    000003 decimal places, without sign
    Position in segment : 044, Offset : 0342. external length : 000015
    LETY1 : Storage Unit Type
    internal data type : CHAR
    Internal length : 000003 characters
    Position in segment : 045, Offset : 0357. external length : 000003
    LETY2 : Storage Unit Type
    internal data type : CHAR
    Internal length : 000003 characters
    Position in segment : 046, Offset : 0360. external length : 000003
    KZKUB : Indicator: Do not create posting change notice
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 047, Offset : 0363. external length : 000001
    UBTYP : Storage Type
    internal data type : CHAR
    Internal length : 000003 characters
    Position in segment : 048, Offset : 0364. external length : 000003
    UBLGP : Storage Bin
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 049, Offset : 0367. external length : 000010
    MBLNR : Number of Article Document
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 050, Offset : 0377. external length : 000010
    MBLPO : Item in Article Document
    internal data type : NUMC
    Internal length : 000004 characters
    Position in segment : 051, Offset : 0387. external length : 000004
    MJAHR : Article Document Year
    internal data type : NUMC
    Internal length : 000004 characters
    Position in segment : 052, Offset : 0391. external length : 000004
    URZEI : Original line in article document
    internal data type : NUMC
    Internal length : 000004 characters
    Position in segment : 053, Offset : 0395. external length : 000004
    GEBER : Fund
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 054, Offset : 0399. external length : 000010
    FISTL : Funds Center
    internal data type : CHAR
    Internal length : 000016 characters
    Position in segment : 055, Offset : 0409. external length : 000016
    KZBWS : Valuation of Special Stock
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 056, Offset : 0425. external length : 000001
    KDAUF_SD : Sales Order Number
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 057, Offset : 0426. external length : 000010
    KDPOS_SD : Item Number in Sales Order
    internal data type : NUMC
    Internal length : 000006 characters
    Position in segment : 058, Offset : 0436. external length : 000006
    XRERE : Reservation reading is mandatory
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 059, Offset : 0442. external length : 000001
    XSTOR : Reverse posting indicator
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 060, Offset : 0443. external length : 000001
    BRGEW : Gross weight
    internal data type : QUAN
    Internal length : 000015 characters
    000003 decimal places, without sign
    Position in segment : 061, Offset : 0444. external length : 000017
    GEWEI : Weight Unit
    internal data type : UNIT
    Internal length : 000003 characters
    Position in segment : 062, Offset : 0461. external length : 000003
    WM_KZBEW : Movement Indicator
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 063, Offset : 0464. external length : 000001
    WENUM : Goods Receipt Number
    internal data type : CHAR
    Internal length : 000010 characters
    Position in segment : 064, Offset : 0465. external length : 000010
    GEBEH : Lot Container
    internal data type : UNIT
    Internal length : 000003 characters
    Position in segment : 065, Offset : 0475. external length : 000003
    ANZGEB : QM - No. of Containers
    internal data type : QUAN
    Internal length : 000006 characters
    000003 decimal places, without sign
    Position in segment : 066, Offset : 0478. external length : 000009
    KANBA : Kanban Indicator
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 067, Offset : 0487. external length : 000001
    BSTMG : Goods receipt quantity in order unit
    internal data type : QUAN
    Internal length : 000013 characters
    000003 decimal places, without sign
    Position in segment : 068, Offset : 0488. external length : 000015
    FUNC_AREA_LONG : Functional Area
    internal data type : CHAR
    Internal length : 000016 characters
    Position in segment : 069, Offset : 0503. external length : 000016
    GRANT_NBR : Grant
    internal data type : CHAR
    Internal length : 000020 characters
    Position in segment : 070, Offset : 0519. external length : 000020

    see the tables MSEG, MKPF.
    REgards,
    Ravi

  • Mapping iDoc to EDIFACT: Segment Count

    Hi experts,
    I am mapping a DELVRY05 iDoc to an EDIFACT DESADV document. Everythings fine so far, but I'm encountering troubles with filling the EDIFACT UNT Segment with the number of segments in the generated message.
    I am using the OPI2 conversion module and so I get a nice xml structure for the EDIFACT message. Is there a way to count created xml nodes? I think this would solve my issue.
    Thanks for your answers!

    That is an example for the source idoc
    <?xml version="1.0" encoding="UTF-8"?>
    <DELVRY05>
       <IDOC BEGIN="1">
          <EDI_DC40 SEGMENT="1">
             <TABNAM>EDI_DC40</TABNAM>
             <MANDT>100</MANDT>
             <DOCNUM>0000000002603007</DOCNUM>
             <DOCREL>700</DOCREL>
             <STATUS>30</STATUS>
             <DIRECT>1</DIRECT>
             <OUTMOD>2</OUTMOD>
             <IDOCTYP>DELVRY05</IDOCTYP>
             <MESTYP>DESADV</MESTYP>
             <SNDPOR>SAPKTS</SNDPOR>
             <SNDPRT>LS</SNDPRT>
             <SNDPRN>KTS100</SNDPRN>
             <RCVPOR>A000000016</RCVPOR>
             <RCVPRT>KU</RCVPRT>
             <RCVPFC>WE</RCVPFC>
             <RCVPRN>0004088156</RCVPRN>
             <CREDAT>20101123</CREDAT>
             <CRETIM>115322</CRETIM>
             <SERIAL>20101123115321</SERIAL>
          </EDI_DC40>
          <E1EDL20 SEGMENT="1">
             <VBELN>0080775647</VBELN>
             <VSTEL>0132</VSTEL>
             <VKORG>0130</VKORG>
             <LGNUM>132</LGNUM>
             <INCO1>EXW</INCO1>
             <INCO2>Leonding</INCO2>
             <ROUTE>009999</ROUTE>
             <VSBED>25</VSBED>
             <BTGEW>0.500</BTGEW>
             <NTGEW>0.500</NTGEW>
             <GEWEI>KGM</GEWEI>
             <VOLUM>0.000</VOLUM>
             <ANZPK>00000</ANZPK>
             <PODAT>20101123</PODAT>
             <POTIM>115321</POTIM>
             <E1EDL22 SEGMENT="1">
                <VSTEL_BEZ>Neuson Ersatzt.Linz II</VSTEL_BEZ>
                <VKORG_BEZ>Neuson Linz</VKORG_BEZ>
                <LGNUM_BEZ>LVS Neuson Linz Ersat. II</LGNUM_BEZ>
                <INCO1_BEZ>Ab Werk</INCO1_BEZ>
                <ROUTE_BEZ>NK Linz</ROUTE_BEZ>
                <VSBED_BEZ>Spedition</VSBED_BEZ>
             </E1EDL22>
             <E1EDL21 SEGMENT="1">
                <LFART>LF</LFART>
                <EXPKZ>X</EXPKZ>
                <LIFSK>10</LIFSK>
                <LPRIO>00</LPRIO>
                <KDGRP>02</KDGRP>
                <TRAGR>0100</TRAGR>
                <TRSPG>03</TRSPG>
                <E1EDL23 SEGMENT="1">
                   <LFART_BEZ>Auslieferung</LFART_BEZ>
                   <LIFSK_BEZ>zu verpacken</LIFSK_BEZ>
                   <KDGRP_BEZ>Handel</KDGRP_BEZ>
                   <TRAGR_BEZ>Transportgr. NK</TRAGR_BEZ>
                </E1EDL23>
             </E1EDL21>
             <E1EDL18 SEGMENT="1">
                <QUALF>ORI</QUALF>
             </E1EDL18>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>AG</PARTNER_Q>
                <PARTNER_ID>0004088156</PARTNER_ID>
                <LANGUAGE>EN</LANGUAGE>
                <FORMOFADDR>Firma</FORMOFADDR>
                <NAME1>Caterpillar Ltd.</NAME1>
                <STREET1>Peckleton Lane</STREET1>
                <POSTL_COD1>LE9 9JT</POSTL_COD1>
                <CITY1>Leicester</CITY1>
                <TELEPHONE1>14558258-00</TELEPHONE1>
                <COUNTRY1>GB</COUNTRY1>
             </E1ADRM1>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>SP</PARTNER_Q>
                <PARTNER_ID>0006006873</PARTNER_ID>
                <LANGUAGE>DE</LANGUAGE>
                <NAME1>DHL Express</NAME1>
                <STREET1>BleibtreustraÃu0178e 2</STREET1>
                <POSTL_COD1>1110</POSTL_COD1>
                <CITY1>Wien</CITY1>
                <TELEPHONE1>1 76600-3286</TELEPHONE1>
                <TELEFAX>1 76600-3475</TELEFAX>
                <COUNTRY1>AT</COUNTRY1>
                <REGION>W</REGION>
             </E1ADRM1>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>WE</PARTNER_Q>
                <PARTNER_ID>0004088156</PARTNER_ID>
                <LANGUAGE>EN</LANGUAGE>
                <FORMOFADDR>Firma</FORMOFADDR>
                <NAME1>Caterpillar Ltd.</NAME1>
                <STREET1>Peckleton Lane</STREET1>
                <POSTL_COD1>LE9 9JT</POSTL_COD1>
                <CITY1>Leicester</CITY1>
                <TELEPHONE1>14558258-00</TELEPHONE1>
                <COUNTRY1>GB</COUNTRY1>
             </E1ADRM1>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>OSP</PARTNER_Q>
                <PARTNER_ID>0132</PARTNER_ID>
                <LANGUAGE>DE</LANGUAGE>
                <NAME1>Neuson Ersatzt. Linz II</NAME1>
                <COUNTRY1>AT</COUNTRY1>
             </E1ADRM1>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>OSO</PARTNER_Q>
                <PARTNER_ID>0130</PARTNER_ID>
                <LANGUAGE>DE</LANGUAGE>
                <COUNTRY1>AT</COUNTRY1>
             </E1ADRM1>
             <E1EDT13 SEGMENT="1">
                <QUALF>006</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>003</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>001</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>007</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>010</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>015</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDL33 SEGMENT="1">
                <ALAND>AT</ALAND>
                <EXPVZ>3</EXPVZ>
                <IEVER>3</IEVER>
                <E1EDL34 SEGMENT="1">
                   <EXPVZ_BEZ>StraÃu0178enverkehr</EXPVZ_BEZ>
                   <IEVER_BEZ>StraÃu0178enverkehr</IEVER_BEZ>
                </E1EDL34>
             </E1EDL33>
             <E1EDL28 SEGMENT="1">
                <ROUTE>009999</ROUTE>
                <ROUID>NK LINZ</ROUID>
                <DISTZ>0.000</DISTZ>
                <E1EDL29 SEGMENT="1">
                   <ROUTE_BEZ>NK Linz</ROUTE_BEZ>
                </E1EDL29>
             </E1EDL28>
             <E1EDL24 SEGMENT="1">
                <POSNR>000010</POSNR>
                <MATNR>000000001000248477</MATNR>
                <MATWA>000000001000003928</MATWA>
                <ARKTX>PNEUMATIC SPRING</ARKTX>
                <ORKTX>Gasfeder 350N/L185/Hub64</ORKTX>
                <SUGRD>0001</SUGRD>
                <MATKL>000040900</MATKL>
                <WERKS>0131</WERKS>
                <LGORT>E002</LGORT>
                <LFIMG>1.000</LFIMG>
                <VRKME>ST</VRKME>
                <LGMNG>1.000</LGMNG>
                <MEINS>ST</MEINS>
                <NTGEW>0.500</NTGEW>
                <BRGEW>0.500</BRGEW>
                <GEWEI>KGM</GEWEI>
                <VOLUM>0.000</VOLUM>
                <LADGR>0131</LADGR>
                <TRAGR>0100</TRAGR>
                <VKBUR>0131</VKBUR>
                <VTWEG>02</VTWEG>
                <SPART>01</SPART>
                <GRKOR>000</GRKOR>
                <POSEX>000000</POSEX>
                <VFDAT>00000000</VFDAT>
                <EXPIRY_DATE_EXT>0</EXPIRY_DATE_EXT>
                <VGBEL>0001416863</VGBEL>
                <VGPOS>000020</VGPOS>
                <ORMNG>         1.000</ORMNG>
                <EXPIRY_DATE_EXT_B>0</EXPIRY_DATE_EXT_B>
                <E1EDL25 SEGMENT="1">
                   <LGORT_BEZ>Ersatzteill. 02</LGORT_BEZ>
                   <LADGR_BEZ>Neuson Ersatzteile</LADGR_BEZ>
                   <TRAGR_BEZ>Transportgr. NK</TRAGR_BEZ>
                   <VKBUR_BEZ>Neuson Ersatzteile</VKBUR_BEZ>
                   <VTWEG_BEZ>NK Ersatzteile</VTWEG_BEZ>
                   <SPART_BEZ>Produktsparte 01</SPART_BEZ>
                </E1EDL25>
                <E1EDL26 SEGMENT="1">
                   <PSTYV>ZERS</PSTYV>
                   <MATKL>000040900</MATKL>
                   <PRODH>409</PRODH>
                   <UMVKZ>1</UMVKZ>
                   <UMVKN>1</UMVKN>
                   <UEBTO>0.0</UEBTO>
                   <UNTTO>0.0</UNTTO>
                   <E1EDL27 SEGMENT="1">
                      <PSTYV_BEZ>Normalpos Ersatzteil</PSTYV_BEZ>
                      <MATKL_BEZ>Gasfeder</MATKL_BEZ>
                      <PRODH_BEZ>Gasfeder</PRODH_BEZ>
                      <WERKS_BEZ>Wacker Neuson Linz GmbH ET</WERKS_BEZ>
                   </E1EDL27>
                </E1EDL26>
                <E1EDL35 SEGMENT="1">
                   <STAWN>83024900</STAWN>
                   <EXPRF>10000</EXPRF>
                   <EXART>1</EXART>
                   <HERKL>FR</HERKL>
                   <GRWRT>          0.00</GRWRT>
                   <E1EDL36 SEGMENT="1">
                      <STXT1>Beschläge und ähnliche Waren, aus</STXT1>
                      <STXT2>unedlen Metallen, für anderweit nicht</STXT2>
                      <STXT3>genannte Zwecke (ausg. Scharniere, Lauf-</STXT3>
                      <STXT4>rädchen oder -rollen und Baubeschläge)</STXT4>
                      <EXPRF_BEZ>Ausfuhr o. voran. zollr. Best.</EXPRF_BEZ>
                      <EXART_BEZ>Kauf/Verkauf</EXART_BEZ>
                      <HERKL_BEZ>Frankreich</HERKL_BEZ>
                   </E1EDL36>
                </E1EDL35>
                <E1EDL43 SEGMENT="1">
                   <QUALF>C</QUALF>
                   <BELNR>0001416863</BELNR>
                   <POSNR>000020</POSNR>
                   <DATUM>20101123</DATUM>
                </E1EDL43>
                <E1EDL41 SEGMENT="1">
                   <QUALI>001</QUALI>
                   <BSTNR>TEST FAH</BSTNR>
                   <BSTDT>20101123</BSTDT>
                </E1EDL41>
             </E1EDL24>
          </E1EDL20>
       </IDOC>
    </DELVRY05>
    and thats what for the moment is the output for the EDIFACT before OPI2 conversion module. UNT segment count is hardcoded set to 1.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:EDIFACTMessage xmlns:ns0="http://cbsgmbh.com/xi/EDIFACT/99A">
       <Header>
          <SenderID>Test_SenderSystem</SenderID>
          <ReceiverID>Test_ReceiverSystem</ReceiverID>
          <MessageType>EDIFACTMessage</MessageType>
       </Header>
       <ListOfDespatchAdvises>
          <DespatchAdvise>
             <HEADING>
                <UNH>
                   <UNH01>0000000002603007</UNH01>
                   <UNH02>
                      <S00901>DESADV</S00901>
                      <S00902>D</S00902>
                      <S00903>98B</S00903>
                      <S00904>UN</S00904>
                   </UNH02>
                </UNH>
                <BGM>
                   <BGM01>
                      <C00201>351</C00201>
                   </BGM01>
                   <BGM02>
                      <C10601>0000000002603007</C10601>
                   </BGM02>
                   <BGM03>9</BGM03>
                </BGM>
                <DTM>
                   <DTM01>
                      <C50701>11</C50701>
                      <C50702>00201011230000</C50702>
                   </DTM01>
                </DTM>
                <DTM>
                   <DTM01>
                      <C50701>132</C50701>
                      <C50702>00201011230000</C50702>
                   </DTM01>
                </DTM>
                <DTM>
                   <DTM01>
                      <C50701>137</C50701>
                      <C50702>00201011230000</C50702>
                   </DTM01>
                </DTM>
                <MEA>
                   <MEA01>PD</MEA01>
                   <MEA02>
                      <C50201>G</C50201>
                   </MEA02>
                   <MEA03>
                      <C17401>KGM</C17401>
                      <C17402>0.500</C17402>
                   </MEA03>
                </MEA>
                <MEA>
                   <MEA01>PD</MEA01>
                   <MEA02>
                      <C50201>N</C50201>
                   </MEA02>
                   <MEA03>
                      <C17401>KGM</C17401>
                      <C17402>0.500</C17402>
                   </MEA03>
                </MEA>
                <MEA>
                   <MEA01>PD</MEA01>
                   <MEA02>
                      <C50201>WT</C50201>
                   </MEA02>
                   <MEA03>
                      <C17401>KGM</C17401>
                      <C17402>0.500</C17402>
                   </MEA03>
                </MEA>
             </HEADING>
             <DETAIL>
                <CPS>
                   <CPS01>1</CPS01>
                   <CPS03>3</CPS03>
                </CPS>
                <SG16>
                   <LIN>
                      <LIN02>000010</LIN02>
                   </LIN>
                   <PIA>
                      <PIA01>1</PIA01>
                      <PIA02>
                         <C21201>0001416863</C21201>
                         <C21202>PO</C21202>
                      </PIA02>
                   </PIA>
                   <PIA>
                      <PIA01>1</PIA01>
                      <PIA02>
                         <C21201>000020</C21201>
                         <C21202>PL</C21202>
                      </PIA02>
                   </PIA>
                   <PIA>
                      <PIA01>1</PIA01>
                      <PIA02>
                         <C21201>TEST FAH</C21201>
                         <C21202>ON</C21202>
                      </PIA02>
                   </PIA>
                </SG16>
             </DETAIL>
             <SUMMARY>
                <UNT>
                   <UNT01>1</UNT01>
                   <UNT02>0000000002603007</UNT02>
                </UNT>
             </SUMMARY>
          </DespatchAdvise>
       </ListOfDespatchAdvises>
    </ns0:EDIFACTMessage>

Maybe you are looking for

  • How can I load data into table with SQL*LOADER

    how can I load data into table with SQL*LOADER when column data length more than 255 bytes? when column exceed 255 ,data can not be insert into table by SQL*LOADER CREATE TABLE A ( A VARCHAR2 ( 10 ) , B VARCHAR2 ( 10 ) , C VARCHAR2 ( 10 ) , E VARCHAR

  • Search for all user messages doesnot work now ?

    Hello SDNer's, I often search my own questions and posts entering the keywords in Search for all user messages. After our forum has been revamped this functionality seems not be working as it used to. When I enter the keywords and Enter it throws me

  • Check the date format

    Hi,   Can anybody tell me how to check the date format in BDC while updating.   The system date format is like mm/dd/yyyy. Check the dates format, in case of error return the following message “The date format should be YYYYMMDD”. Thanks......

  • Attaching document to smartform

    Hi Experts, I want to pick up the attachment from the service ticket and attach it to the smartform.This smartform is triggered through an action. I am enhancing the method CRM_SRVORDER_EXEC_SMART_FORM: I have read the attachment using cl_crm_documen

  • BPELConsole Authentication is not working. Can't log in to BPEL Console

    I have installed the SOA Suite 10.1.3.10 which I have downloaded from OTN. I have selected the Standard Install and the installation was successful. I can start the SOA Suite without any problem. I can access the Oracle Application Server 10g Release