Delivery IDOC Split

Issue:
We could observe that the error coming in the Idoc XXX; are errors involving the financial postings that occur as a result of the inventory movement associated with a goods issue.
Error Message:
Maximum number of items in FI reached
The above error in IDOC is due to max. number of items for an FI Document(999) is exceeded.
As per my understanding, I think we have to split the delivery document into two parts and post to FI accordingly
As FI documents is getting posted through IDOC, how can I limit my IDOC to process just 50% of line items(How to split my Delivery though IDOC)

Refer below note:
Note 1353827 - AC interface: Document split in FI for goods movements
Regards
Sreenivas

Similar Messages

  • Outbound Delivery IDOC not updating values from MKPF for goods receipt

    hi all,
    I have a question say I am generating an outbound delivery IDOC. which  has fields Goods Issues & Goods Receipt date retrieve from MKPF(BUDAT).
    say when i post goods issues, MKPF is updated and  IDOC is gernerated with issues date taken from MKPF.
    and when i tried to goods receipt, MKPf is updated and IDOC is generated but no receipt date taken from MKPF. then i check in MKPF, date is there and then once again I triggered the IDOC, receipt date comes......so my doubt is the time issues say when IDOC is triggeres, no value in MKPF...but when i check the time it is 4 mins difference from the MKPF time and the IDOC time...
    and also 1 more thing for doing goods receipt, we do in different transaction and for good issue we do in Vl02n.
    so bit confused.
    kindly help

    True , but in BKPF only Issues date are stored not the receipt date say if the document type = WE.
    Please let me know is there any other options to fetch rather than MKPF.
    because at the time of IDOC generation, there is not entries in MKPF. I tried to do using WAIT UP TO 50 seconds , even that didnt work.
    Please guide me
    thanks

  • Inbound delivery idoc error in segment e1eld20

    we are receiving delivery idoc from the vendor, so this is delivery will be created as inbound delivery in our system, so in the segment E1EDL20 field VBELN(let say 'ABCD') is the outbound delivery number of the vendor ( i believe), but when is try to process this idoc it gives the error as 'delivery ABCD does not exist' ( it's obvious that the delivery 'ABCD'  will not be in our system because it's a vendor delivery number), can some body please let me know whats wrong with this E1EDL20-VBELN.
    Thanks,
    Kashif

    HI,ALL
    Thanks for your replies and documents.
      Now I find the problems lies in the error connection between R/3 and BW. IF the autoconfiguration is completelly correct , the table RSBASIDOC in both system should be added one record.But now when the source system is activated successfully ,the table in R/3 side has no entry while the BW side has one entry .juding from this ,there is no BW system connected to the R/3 ,which is proved when I fill the setup table for LO datasource an error message shows that there's no BW system is connected to the OLTP system.
      How can i figure this issue out ?If I want to do an automatic configuration ,what shall I do ?

  • How PO/Outbound delivery idoc can be triggered automatically once PO is created.

    Hi All,
    We have a requirement that we need to automate the process of generation of Purchase Order & Outbound Delivery Idocs as soon as they are created in using ME21N and VL02N standard tcodes.
    Currently we are using ZDID Output type as craeted in NACE and below WE20 Message Control Entries:
      For PO -
      Application             EF : Purchase Order
      Message Type:      ZDID : Direct Delivery PO
      Process Code       ME10 : ORDERS: Purchase order
    For OB -
    Application        V2 : Shipping
    Message Type:      ZLD0 : Delivery Note
    Process Code       DELV : Delivery DELVRY01: DESADV/CARNOT/WHSORD/SHPORD
    Also, BD64 entries are already maintained.
    As per current process, we manually go to ME23N/VL02N tcode->and execute output type which generates Idoc in we02.
    Can any one help me getting this automated urgently.
    Thanks
    neha verma

    Hi Neha,
    Use Change Pointers Concept for Both PO & Delivery Note.
    So that, as soon as a Create/Change/Delete activities happen on PO & Delivery Note, IDOCS will be triggered automatically.
    PO Change Pointers
    http://scn.sap.com/docs/DOC-45107
    Same setup for Delivery Note as well.
    -santosh.

  • IDoc Split to different IDocs!!!!!!!!URJENT

    Hi
    Is there any possibility to split the IDoc ?
    We have a scenario like - Header without any data - Segments with the data - trailer segment with the details of the segment count and parent idoc details.
    We received one Inbound IDoc with 20000 segments.
    While processing the IDoc, because of the huge data it is going to dump with low memory issue.
    Is there any possiblity to split the segments into seperate idocs...in WE19 we can cut down the segments and create seperate idoc but count is very high we are not able to identify the numbers count.
    Is there any other way we can process the IDoc splitting into different IDocs.
    VVR
    FICO Consultant

    Hi Vuppala,
    CAn you please help how u split the IDOC.
    I have ARTMAS IDOC and as there is huge data i need to split it.
    Can you please help
    Thanks,
    Akriti

  • Delivery IDOC not getting generated

    Hi All,
    I have created an outbound delivery IDOC. The process is that the idoc should be trigerred as soon as the delivery is created/changed or deleted. I am having an issue. The idoc is getting trigerred as soon as the delivery is getting created but not in the case of the delivery change.
    I am not able to get the probable reason for that. Please let me know the probable reasons for that and where can i check that.
    Regards,
    Sharadendu

    Hi Sharadendu,
    For this you have to use Change pointers concept.
    see the explanation below
    System will remeber every change for a table related to an IDOC. eg. if costcenters are changes. tables csck and cskt will change. Having a change pointer for IDOC type cosmas which reflects costcenters. Any change made by using the KS* transactions will now be recorded. Usinf the change pointers you can now generate IDOCS so that the changes are sent to the dependant systems.
    use bd50 to acivate change pointers, use bd21 to generate idocs, use bd64 to determine the distribution of those idocs.
    PLs. reward if useful.....
    cheers,
    Hema.

  • Delivery Idoc

    Hi,
    We have an issue while sending delivery Idoc of type DELVRY03. In segment E1ADRM1 for field STREET1 the laegth was 40. I am sending 21 Japanese(Kanji) character(2 bytes each) means it occupies 42 charcters but field STREET1 supported lengh of this field is 40. Therefore the last character is truncating and causing issues.
    Can anyone let me know how to extend the field length of STREET1 field in the above segment which was created by SAP or any other alternative solution to this problem.
    Appreciate your response.
    Regards,
    Cheritha

    Hi Cheritha,
    you have almost 2 options:
    1- use field STREET2
    2- extend the Idoc DELVRY03. Create an custom extension ZDELVRY03 and a custom segment ZE1ADRM1, with the field STREET as a 50.
    Regards.

  • Flat File to Delivery IDOC scenario

    Dear All,
    I am having one scenario in which I am having the flat file (.txt) of the Delivery Idoc and now I want to convert that flat file into a Delivery Idoc with the required data.
    Kindly suggest me some good blogs which gives the step by step process for doing this scenario.
    Warm Regards,
    N.Jain

    Hey Nishu,
    You have  to use File Content Conversion Paramters to acheive this.
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    You can Follow the following blogs
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
    /people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
    Or juz post your sender datatype structure some one might give u exact fcc params.
    Hope itz Helpfull.
    <b>Cheers,
    *Raj*
    *REWARD POINTS IF FOUND USEFULL*</b>

  • Problem with Delivery IDOC staus 51

    Hi all,
    I have problem with Delivery IDOC.
    An IDOC is sent from the logistics provider with reference to a manually created delivery, which creates another IDOC & another partial delivery.
    The second IDOC created then confirms the partial delivery created by the first IDOC.
    When IDOC try to confirm this delivery, it goes to status 51 with error " Delivery does not exist".
    In some case IDOC was correctly processed & confirmed the delivery.
    In some cases it went wrong.
    Any ideas regarding this?

    Hi Suneel,
    It seems there is timing issue between the first IDoc and second IDoc.
    When the first IDoc has not yet commit to DB then the second IDoc tries to process with reference to the first IDoc.
    Is there any that can distinguish between 1st and 2nd IDocs?
    In other word, can you post the second IDoc within minutes delay?
    Just my two cents.
    Regards,
    Ferry Lianto

  • Idoc split program

    hi,
    what is the use of idoc split program.in which scenario it will be used?
    Ganesh

    Spliting the idoc - suppose you have purchase order - when you create purchase order then it will create one idoc.
    some times requirement would be like - purchase order has many line items ,clients need each line item as one idoc ,here we need create multiple idoc for one order ( For this we need to change the logic with in function module)
    Reward Points if it is helpful
    Thanks
    Seshu

  • Stop generating delivery IDOC output (outbound IDOC)  if goods issued!

    How to stop generating delivery IDOC output (outbound IDOC)  if the delivery has been goods issued?! Any user exit or BADI for this?!
    Thanks

    We take a routine in output requirement! it's done!

  • Sales Order - Outbound Delivery IDoc scenario.

    Hi Friends,
    I have the below urgent requirement. I would be gratful, if someone suggest possible options.
    Scenario: This is related to Sales order to Billing scenario.
    We are creating Sales orders by using ORDERS05 Idoc. After the Real goods despatch happens at legacy system, we will be getting despatch feed (IDoc) for outbound delivery trigger. Here if all sales Order items are complete, the system is creating Outbound delivery by using this IDoc and then PGI will follow. This is Ideal scenario.
    Practically what happening is, our sales orders are created with few incomplete items (Ex: Net price missing) because they are created via ORDERS05 Idoc.( Manually, we can't create sales order with incomplete items, unless we force the system to do so). When the Out bound delivery IDoc triggered, it will pick up only completed items and creates partial delivery and becomes 53 status. Now the sales order is left out with open and incomplete items.
    Now our aim is how to make this outbound delivery IDoc fail, if this is not able to create delivery for all items?? (I mean, if the sales order items are incomplete, the delivery Idoc must fail. So later, if sales order becomes complete, this Idoc can be reprocessed again) How can we make this scenario possible??
    Expecting your thoughts and inputs.
    Regards,
    Kaleeswaran

    HI,
    I suggest you to think of similar solution as below.
    1.As your issue is at order (few items are incomplete with Pricing issue or some other issue), at sales order level while saving each sales order write the code in user exit_save_document_prepare to check if any items exists as incomplete. if yes then populate a delivery block in the sales document header.(you can use a new delivery block to distinguish the reason for the block)
    2. While creating delivery for the order through Idoc since the incomplete orders have a delivery block at the sales document header level SAP wont create delivery for the entire Order.
    3.Handling this delivery block at sales order header: when ever a sales order is popluated with this new delivery block triggere a workflow which will shoot a mail to your End user team or customer representative team. they will correct the issue in the order and remove the delivery block. if you dont want to go with a workflow then you need to incorporate a process to remove the delivery block in the sales order
    Thanks,
    Srini

  • Errors while posting Delivery Idoc

    Dear All,
    We are changing some segments of an Delivery Idoc. After changing, the system is creating an new Idoc with the values defined in the original Idoc and is changing the status of original Idoc from 30 to 32. Then again we are changing the status of Idoc to 30 with the help of function module  "IDOC_STATUS_WRITE_TO_DATABASE". Now, while submitting the original Idoc in WE14, a pop-up is coming with "1 Idoc Selected" but status is remaining 30 only. But since we have transferred this Idoc to the port so status should have changed to 03 which is not happening.
    Please suggest me a solution for this.
    Warm Regards,
    N.Jain

    hi
    What i think is that you have to reprocess the idoc. <b>Execute this program in se38.</b>
    RBDMANI2  : Reprocess Idocs manually
    RBDMANIN  : Posting of IDocs with Status 51
    RBDMOIND  : Outbound Idocs status 03->12
    <b>RSEOUT00  : For Processing 30 Status IDocs</b>
    RBDAPP01  : For Processing 64 Status IDocs
    RBDAGAIN : Reprocess Incorrect Outbound IDocs
    RBDAGAI2 : Reprocessing of IDocs after ALE Input Error
    <b>Reward points for useful ans.</b>
    Regards
    Aarti
    Message was edited by:
            Aarti Dhingra

  • User exit for delivery IDOC on save

    Hi,
    I have found some exists for delivery IDOC fun mod 'IDOC_OUTPUT_DELVRY'.
    when I am testing from WE19, the debugger is not triggiring.
    Pl suggest.
    Thanks,
    Krishna

    Hi,
    If you have the idoc no. get the partner details form it and go to we20 and put it there. and go to inbound parameters, and cleck on the message which your idoc belongs to. and go to the process code in it, and double click on it. where you can get the FM attached to it. put the break point there. opne your idoc from we19. click on the inbound FM. and place the FM. and click on debugger active check box and chose fore ground. it will take you to that FM. now debug that function module. in this process you may come across Exits you are looking for.
       Hope this will helps you.
    Regards
    Kiran

  • Inbound Delivery Idoc not update PIC and PGI with split batch.

    Dear Experts,
    Delivery outbound with split batch send to third party Warehouse to PIC and PGI from SAP, then receive the delivery inbound IDOC to update the PIC and PGI in SAP from third party. Basic Idoc DELIVERY03 it's works fine with out split batch, with split batch it's not updating PIC and PGI at the same time no error. Please advice on this
    E1EDL24-HIPOS = "HIGHER LEVEL ITEM NUMEBR"
    E1EDL24-HIEVW = "VALUE 1"
    E1EDL19-QALF = "BAS"
    Thanks and Regards,
    Thiru.

    Hi,
    You also have to create a segment with following data as well (for batches).
    E1EDL19-QUALF = "QUA".
    Cheers,

Maybe you are looking for