Capture Idoc numbers for outbound INVOIC02

Hi,
We have a requirement where we need to capture the idoc numbers before it is dispatched.
IDOCS are populated by FM IDOC_OUTPUT_INVOIC using process code SD09 for custom output type(EDI processing).
Our requirement is to capture these idoc numbers into a custom table which will be used for further custom processing. The user exits in the above FM are good for just for segment population.
What is the best approach to capture these idocs? Is there a user exit to capture these idocs?
Thanks,
Pratik

sorry wrong forum

Similar Messages

IDOC WMMBID02 for Outbound

Hi,
I am trying to configure an outbound IDOC for GI/ GR. I was told to use WMMBID02 for this, but it uses FM L_IDOC_INPUT_WMMBXY.
Has anyone tried to use IDOC WMMBID02 for outbound? I want to use this for a particular GI with Material Document as a parameter.
Thanks.
Kenny

Hi Ferry,
Thanks for the reply.
I cant seem to make this test program work. I just put the Mat Doc Num and the Year then ticked direct processing. It then shows "Check your entries".
Please help.
Thanks.
Kenny

Idoc numbers for a certain output in Sales Orders

I have more than hundred Sales Order
One EDI output was triggered (with a unique partner type) from each of these Sales Orders.
How to find idoc numbers for all these Sales Order for this particular output?
I tried WE09 giving Segment and field with value....two issues with this. first is it is not working for me...not records found.
Secondly It take one value at a time. I can't do this for every Sales Order
Is there any database table or something else to find these idocs?
Thanks a lot!

Hi,
if this special partner type is the partner type of the IDoc receiver, then you can search for relevant IDocs in transaction WE02.
If you need a partner type out of the sales order data, then it is stored in table EDID4 "IDoc Data Records".

How to fill data in to extended idoc segments for outbound program

Hi all,
I am new to this Community In the extension of Standard idoc INVOIC02 with some custom segments like zemail, zfax,,,,how to fill the data into both standard segments and custom segments for outbound idoc using exit EXIT_SAPLVEDF_002 of standard function module IDOC_OUTPUT_INVOIC...
i need some sample code
THANKS
PAVAN K

Hi all,
I am new to this Community In the extension of Standard idoc INVOIC02 with some custom segments like zemail, zfax,,,,how to fill the data into both standard segments and custom segments for outbound idoc using exit EXIT_SAPLVEDF_002 of standard function module IDOC_OUTPUT_INVOIC...
i need some sample code
THANKS
PAVAN K

IDOC no. for outbound JIT calls

Hi,
I need to extract idoc number for all outbound jit calls that I can view in Outbound JIT call monitor.Can anyone please tell me that which table is used to store the generated idoc no. for a particular call/component group in a call.
Thanks,
Gauri

Hello,
There is one transaction code BDM2 which is the link between the INBOUND IDOC and the OUTBOUND IDOC
I never used this transaction, but try
OR as an alternative
There is a Function module SREL_GET_NEXT_NEIGHBOR
Goto the Transaction code SE37 and give this FM
OBJECT-OBJKEY = <IDoc number, 16-digits>
OBJECT-OBJTYPE = 'IDOC'
MAX_HOPS = '99'
and execute
it will give the Outbound idocs for the inbound idocs
I hope this will solve your requirement.
regards,
santosh

Duplicate outbound Idoc created for outbound delivery

Hi Gurus,
We use decentralised whse system for goods movement.
For couple of outbound deliveries there are double idocs created (messge type SHP_OBDLV_SAVE_REPLICA).
I have no idea how the duplication taken plcae. Any body come accross this kind of issue .
Please help to reslove the issue .
Thanks in advance

Hi,
There is nothing in message control tab for outbound parameter(we20) and even there are multiple changes in delivery.
What we do is as soon as the delivery is created . Z trnx is executed which changes the dec whse status A(Relevent ) to B (distribution) simulteneously outbound Idoc is created and delivery details send to whse.
Normally there will be one outbound idoc per delivery , but in this case there are 2 (duplicate)

XI generates own IDOC numbers in outbound IDOC

Hello, The scenario we have is R/3 --> XI --> 3'rd party (via IDOC rcvr adapter) AND then SYSTAT back from the 3'rd party to R/3 via XI.
Example: R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number).
Accordingly, the 3'rd party responds back with a status IDOC, SYSTAT, containing IDOC 200 in the E1STATS ==>DOCNUM field.
This is now a problem since if XI submits the SYSTAT as received from the 3'rd party, it has 200 in the DOCNUM field and this fails in R/3 since there is no original IDOC with number 200.
This can be solved if XI is able to pass the original number 100 through to the 3'rd party system (since then when the 3'rd party responds it will send a SYSTAT with IDOCNUM as 100 back, which will setup correctly in R/3).
I have gone through the other pertinent posts and none of them have this specific problem / offer a solution. I'm hoping I have missed something as this seems to be a pretty basic requirement.
Thank you for the time.
Some additional details...
- 3'rd party is non SAP.
- In the IDOC rcvr adapter we have flags 'Apply Control Record Values from Payload', 'Take Sender from Payload' and 'Take Receiver from Payload' fields checked.
- We have not checked any flags in the Rcvr Agreement.
- We are not using BPM and do not have a way to correlate the inbound 200 with the original 100 that went out.

Bhishma,
Just clarrification for you...when you said..
"R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number)."
Here Idoc number 100 is outbound idoc from R/2 where as Idoc number 200 is inbound idoc...n they are totally different idocs..not same
I think there is work around...while mapping data from XI --> 3rd party assign / store outbound idoc in one of the unused field of inbound idoc...and while mapping back use this field to map it back...I think this will work.
Let us know the result.
Nilesh

IDoc type for Outbound Delivery

Hi All,
Can someone please tell me the IDoc type and message type to be used for creating the outbound delivery for an incoming IDoc? Also, I would like to know the function module.
Regards,
Raghav

Hi,
Message type is DESADV
Basic type is DELVRY01 to 03 (can check the latest version or supported version)
Function module : BORES_IDOC_INPUT_DESADV1 or IDOC_INPUT_DESADV1
This is used for creating outbound deliveries, shipping noticfication etc.
Regards
vk

How to trigger FIDCCP02 idoc for outbound vendor invoices?

Hi
1. How can i trigger the idoc FIDCCP02 for outbound processing? I am trying to use this idoc to send the vendor invoice data to another system.
2. How do i send existing data from sap to another system thru idocs?
pls give me the steps.
Regards
Sujai

Hi Sujai,
First you have to fill the your data into a table which is like the structure of EDIDD.Here you have to fill the all segmetns in the sequence which defined in the idoc type only other wise you will get error 26.
Then pass the control record data in the structure like EDIDC here you have to fill the sender,receiver,partner profile,idoc type message type like stuff.
Then pass these table and structure to the function module MASTER_IDOC_DISTRIBUTE.
Then idoc will created by above funciton module.
If you want pass data in xml format then you have to create xml port in we21 and pass this port name in the EDIDC structure.
Thanks,
radha.

Idoc extension not displayed - outbound / INVOIC02

Hi All,
I have created a Extension Idoc ZINV2 , Basic type INVOIC02.
I have added the segment YE1EDK01 ( with 2 custom fields ) under the segment E1EDK01. the message type is INOIC.
The Partner Type is KU and the partner number used is 7000001.
In the Outbound parameters : i have assigned
Partner function as PY
Message type is INVOIC.
Message function is US.
and I am assigning the Basic type and Extesnion type here properly.
The segment and the idoc extension are released.
In VF02 , in OUTPUT i am giving the Output type as YU10 for outout MEDIUM EDI.
The idoc is getting created without any problem. But the Extesnion type is not displayed in the idoc in WE02. the added segment YE1EDK01 is not displayed.
What could be the Problem , i am not able to sort out.
Kindly help me in solving this .
Should we need to do anything in WE57.
Kindly help in solving this problem.
Waiting for your replies.
Suki.R

Hi,
When you need to add an Idoc extension, it must be appended in INT_EDIDD itab, after the actual segment. hen only it will be picked in the Idoc.
Steps to add extension(Example)::
1. WE31 - Create A segment(ZETEST) with additional fields, that needs to be added.
2. WE20 - Create the Extension(ZORDERS) for the given Basic type.
        2.1    Now add the custom segment(ZETEST) as the child segment to the segment which you want to extend(e.g. E1EDK01)
        2.2    Define the minimum and maximum occurrence
3. Release the custom segment (ZETEST) and the Extension (ZORDERS).
4. WE82 - Assign Basic type to extension / messages
5. WE30 - Check and Transport IDoc extension
                 5.1 Give the Extension Name(ZORDERS)
                 5.2 In the menu Path : Development Object -- >Check (Ensure that there are no errors or warnings)
                 5.3 Now Transport: Path: Development -> Transport
6. WE20 - Now go to the Partner Profile and add the Extension(ZORDERS) in the Message control data and Save it.
7. Go to the Function module for processing the Idoc, and add the code for custom fields.
Eg Code:
clear: lt_dxvbep, lt_dxvbep[],
       ls_dxvbap,
       ls_ysd_tvpr,
       ls_aufk,
       ls_ze1edket,
       ls_edi_partner,
       ls_int_edidd.
if int_edidd-segnam = 'E1EDK01'.
do 1 times.
    check control_record_out-cimtyp = 'ZORDERS'.
    data: ls_pmt_vbak like vbak,
          ls_pmt_vbuk like vbuk,
          ls_e1edk01 like e1edk01,
          ls_ze1edk01 like ze1edk01,
          ls_nastflags like ysd_tvoutflags.
*/ Clear workarea
    clear: ls_pmt_int_edidd.
*/ Get data
    select single * into ls_pmt_vbak from vbak
    where vbeln = dxvbak-vbeln.
    select single * into ls_pmt_vbuk from vbuk
    where vbeln = dxvbak-vbeln.
*/ Get customizing
    select * up to 1 rows
    from ysd_tvoutflags into ls_nastflags
    where flagn = 'STA_PMT_DELETE_IDOC'
      and kappl = 'V1'.
    endselect.
*/ Set extended name
    ls_pmt_int_edidd-segnam = 'ZE1EDK01'.
*/ Set data for ZE1EDK01
    ls_ze1edk01-cmgst = ls_pmt_vbuk-cmgst.
*/ Move to EDIdata and append
    move ls_ze1edk01 to ls_pmt_int_edidd-sdata.
    append ls_pmt_int_edidd to int_edidd.
*/ Modify E1EDK01 with extra field
    loop at int_edidd where segnam = 'E1EDK01'.
      move int_edidd-sdata to ls_e1edk01.
      ls_e1edk01-lifsk = ls_pmt_vbak-lifsk.
      move ls_e1edk01 to int_edidd-sdata.
      modify int_edidd.
    endloop.
enddo.
Hope this helps........

IDoc - Wrongly Picking value for outbound.

Guru's
Once save the sales order, a out bound idoc will trigger and goto a non sap system.. till date its picking right values but now its not picking one number(that is year) <b>Voyage number</b> starts with year example 2007 is equal to 7 and other two digits is serial numabre.. 701, 702, etc....now its not picking 7, only taking 03, 04.. ...
any inputs...
Ramki

Debugging is the only option to find your problem.
Put breakpoint on segment which you are having problem. or user exit, if you have any.
If you are not familiar how to debug for outbound idocs do the following steps.
1) Cllick header-->output
2) Repeat output type
3) Select output type and click Further data and select dispatch time to 1(Send with periodic schedule job).
4) Save.
5) Go to Transaction WE15 or execute RSNAST00 program
6) Select your output type..input object key-->nothing but document number(eg..sales order number).
select output type and transmission medium.
7) Now cursor stop at your break point".
"Rewards point if usefull"
Thanks,
Narayan

FM for outbound payment idoc

Hi,
How do we find out the FM for outbound payment idoc?.Here are the details
Message type-PAYEXT
Idoc type-PEXR2002
Thanks,

This thread is was last replied more than a year ago, but I'll add a little just to contribute.
WE60 documentation for the IDocs don't really give much except field / segment
information, but don't talk about where the fields come from.
FI_EDI_PAYEXT_PEXR2001_OUT seems to be the right FM, not sure how it relates to IDoc type pexr2002 as 2001 is the older version, but perhaps it handles the difference somewhere inside.
As to where certain segment fields come from (i.e. the mapping to master data fields...) , I've been debugging and still in progress.
I have not been able to find any straight forward mapping, and my comments at the moment are:
For any particular segment field of PEXR2002, take a look at FM :
FI_EDI_PAYEXT_PEXR2001_OUT
to see how it populates the field. Chances are, the values come from the tables REGUH/REGUP/REGUV.
The payment run process as far as my knowledge is concerned is as follows:
1) Payroll Run -> Stores to table BT
2) Pre DME (e.g. trx PC00_M08_CDTA) picks data frm BT and creates payment data in REGUH / REGUP / and REGUV tables. This gives you an identification feature ID for the next step.
3) RFFOEDI2 changes status field in REGUH for particular payment data record based on ID from step 2.. this enables it to be picked up in the next step.
4) RFFOEDI1 converts the record in REGUH into an IDoc which can be processed in BD87.
I have debugged from step 4 backwards to step 3, i.e. I know that segment field X comes from REGUH field Y. Now I have to debug step 2 to find out how it populates REGUH field Y. If this comes directly from master data, then that makes life easier. But if this REGUH field Y comes from table BT of step 1, then perhaps I have to debug the payroll run somewhere. (Nightmare?
Anyway, if anyone knows better, please advise.

Outbound output type & Idoc type for MIRO (Invoice Posting)

Hi Gurus,
I have requirement like , I want to send the outbound IDoc to a external system containg the invoice detials after Saving in MIRO.
I am not able to find any output type & Idoc type for the same.
By going through varios threads , I found that there tell there is no Idoc type & output type for sending Idocs after MIRO.
Kindlt let me know, if it so, or how this req can be fullfiled by other ways.
Thanks
Amresh

Hi,
Create Custom Idoc type with required fields,custom output type and assign it to partner profiles.(If there is no std idoc type or output type)
Use Funtion module MASTER_IDOC_DISTRIBUTE to generate Idocs while saving MIRO, for this you need to find exit or implement implicit enhancement while saving MIRO.
Regards,
Ashok.

Automatic generation of Idoc for outbound delivery

Hi Experts,
I need to generate Idoc automatically for each outbound delivery created in VL01n. I just wanted to know that whether we need to asign output type for each delivery number manually or is there any automated process available to generate Idoc for all the outbound deleveries automatically. Could some one share the information regarding the above matter and other information if there is any.

Hi,
U wont manuallly assign the output type for every delivery u create.
There will be Customization part which will be done by Functional guys and they will do that configuration.
This will auotomaticcaly set the Output type, medium..
Ones the configuration is done u just need to create partner profiles ( port and rfc by Basis people) .
Rvert back if any issues,
regards,
Naveen

IDOC Type for Tcode CC01 and CC02 (Create / Change Change Numbers)

We are trying to integrate Change Master from a 3rd party system to SAP R/3 4.72.What is the IDOC Type for Tcode CC01 and CC02 (Create / Change Change Numbers)

Thanks...
We have looked at this IDOC Type. However we are not very sure how the components (Material/BOM etc.) will be mapped into E1AEEFM segment in the IDOC.

Capture Idoc numbers for outbound INVOIC02

Similar Messages

Maybe you are looking for