Idoc generation for VL02N

Hi all
I need to create idoc from VL02N on goods issue....
I have one particular output type configured in nace . When that gets triggered i need to create the idoc by taking the outbound delivery number from VL02N and then fetching certain data.
I am confused as to how to approach for this.....Where do i need to write my code for idoc generation so that it can access the outbound delivery number and then do the rest of the processing

Hi,
Your custom function module needs to be defined as the same structure as below.
Local Interface:
*" IMPORTING
*"     REFERENCE(OBJECT) LIKE NAST STRUCTURE NAST
*"     REFERENCE(CONTROL_RECORD_IN) LIKE EDIDC STRUCTURE EDIDC
*" EXPORTING
*"     VALUE(OBJECT_TYPE) LIKE WFAS1-ASGTP
*"     VALUE(CONTROL_RECORD_OUT) LIKE EDIDC STRUCTURE EDIDC
*" TABLES
*"      INT_EDIDD STRUCTURE EDIDD
In function module add following code to get the delivery number.
move object-objky(10) to del_no.
You can see the function module definition of IDOC_OUTPUT_DELVRY which is related to standard outbound process code "DELV".
Regards
Vinod

Similar Messages

Idoc generation for message types

Hi All,
regarding IDOC generation....
how do we activate the message type so that every time the application data which is created or changed or deleted generates the idoc and send it to other system. If iam not using Chnage pointers technique then i would not be activating the message type in BD50. In such case ie if the message type is not present in BD50 list and if change pointers is not used to transfer that message type . How do we genrate the idoc for such message types.
Thanks
Avinash

Hi,
For ur scenario u need to go for change pointers method only.U have other options like distributing master data and transactional data..But i don't think anything otherthan change pointers is useful.
Regards,
Nagaraj

Single idoc generation for multiple sales orders

Hi,
Pls let me know how do we generate single idoc for multiple sales orders.
Its not collecting idoc. As we know we can generate an idoc for one sales order correspondingly
my requirement is to generate single idoc number for multiple sales orders.
Do we need to write a program.

Amar,
To understand take HRMD_A04 as example. Root segment has Maximum 9999999999 defined.
Segm.type E1PLOGI
Minimum number 1
Maximum number 9999999999
Parent segment
Hier.level 2
This means that this IDOC types has capability to hold multiple HR Master data objects. PFAL program creates this IDOC and it has facility to mention the Objects per process, check selection screen.
I checked for INVOICE01/02 its not possible there. Hope this clarifies.

IDOC filtering for VL02n

Hello all,
I am creating the Delivery03 type IDOC each type a delivery document is changed or created using message control technique. But I want to create the IDOC only for perticular value of the delivery type and shipping point. How can I achive this ? Is there any user exit or badi I can use to implement htis?
Thanks and regards,
Keith

Hi..There is no need of exit for this.
We can Acheive this by maintaining Filter Conditions in BD64.
Steps: in BD64
Double Click on the "Data filter Not Active" under the Message type of Delivery03 in your model View.
Create a Filter Group
Maintain these Conditions
Note: If there are no filter objects available for Delivery type or Shipping point we can maintain them in BD95. And then they will Appear in BD64.
let me know if there are any issues.
Reward if Helpful

PO Idoc Generation for vendor

hi,
we want to generate Idoc for PO when PO is Saved and post it on Staging server
we have maintain partner profile using TRN code we20.
when we are trying to put EDI in output profile in me22n than
i am getting below error.
Maintain outgoing EDI-connection data for partner 100088
Diagnosis
The system could not locate the EDI partner agreements (outbound) for partner 100088.
System response
You cannot use transmission medium 'EDI' with this partner.
Procedure
Maintain the EDI partner agreements for partner 100088. Make sure to create entries for output control as well as for outbound parameters.
thanks .

Hi MD,
Even after setting up the output type for PO and creating patner profiles and adding the message types ORDER and ORDCHG etc, when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model "
Could you suggest some solution?
Also what do you mean by maintaining output type condition records for the partner ?
Thanks in advance,
Shweta

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

Deactivate idoc generation for order when status is not completed

Hi Guru,
In CRMD_ORDER when sales order is created it will generate bdoc and for that bdoc idoc is going to create for every status , my requirement is to stop the creation of idoc if status is not completed please provide solution for that.
Regards,
Naveen.

Hi Naveen,
As u said u dont want to create idoc on the particular User status(i.e. Not Completed ), in this case u check for u r subcription setting in administration console (txn: SMOEAC) that in which statuses u r idoc get created in field crieteria value, maintain status operator (NE) Not Equal to Not Completed , u r idoc will not get created if u r user status in Not Completed
Regards,
DD's

Idoc generation for FI transactions

Dear ALL,
I want to trigger idoc for some of the FI transactions like FB60,FV60,F-47,F-43,F-63 . I want to trigger idoc when the document is posted .But i cannot find any options in this transacions to attach the output type.
Can any one suggest any option to trigger the idoc for this transactions when the document is posted.
Thanks & Regards,
Gopan

Hello,
As far as I know, FI Transactions do not use Message Control (Output Type) for sending FI IDocs. Instead, we can set up an ALE Distribution Model in Transaction BD64 with the Message Types and Idoc types of the respective FI Transactions to serve this purpose.
Make sure to maintain Outgoing Partner Profiles for the Message Type and IDoc Type and generate the Same in the Distribution Model.
Hope it was helpful.
Thanks and Regards,
Venkat Phani Prasad Konduri

IDOC Generation For Quantity Change in Sales Order.

Hi to all,
I have a very urgent Requirement,Please give correct solutions.
Requirement:
When a change is made in the quantity of the sales order line item,an idoc should be trigerred . I have done done all the configurations ,still no results.I am new to ABAP , GIve good solutions ,i will reward you.

Hi there,
Could you please explain step by step procedure of your req. coz it is not clear.
What is BoQ?
Customer gives raw material with out knowing the specification of sheet?
Thanx
Jess

Outbound IDOC generation

Hi Gurus,
There is a requirement for a customer to develop a custom program i.e. IDOC generation for the Manual payments (F-53 ) raised (As similar to the F110 Automatic payments ).... We are calling MASTER_IDOC_DISTRIBUTION function Module from which IDOC is getting generated but the data which needs to be distubted to XML file through Port configuration is not happening .
with the Automatic payments with same port configuration this is working fine.... so is that anythign we need to do in the custom program ...
Thanks for your help in advance
Thanks & Regards,
Ramamurthy

Hi Ramamurthy,
I'm assuming that the IDoc gets generated, i.e. you can see it in WE02. If not then you're probably missing the entry in the distribution model (BD64), so the function module creates a master IDoc, but no communication IDocs.
If you see the IDocs on the database, but they are not being sent, check if your custom program issues a COMMIT WORK. Alternatively you could also see if changing the partner profile from Send immediately to Send via background program and then sending the IDoc via RSEOUT00 makes a difference.
Cheers, harald

DTD generation for IDOC- XI- Web-Method(SOAP)

Hi All,
Our web method team wants DTD from XI to design there development.
I can provide XML structure but I do not know how to generate DTD file from XI.
Also I am trying to generate DTD following site : http://www.hitsw.com/xml_utilites/ But web-method team saying there is no Root node in above generated DTD.
Please guide me how to generate DTD from XI?
Regards

Bhavesh,
I am working on a MDM(FILE)-XI-IDOC interface. I need to have the IDOC structure for my file structure. I have exported XSD from the IDOC and created an external definition file and using it.
Otherwise, can I create a DTD file out of IDOC and import that into any data type? I created the DTD for the IDOC in WE60 and tried to import that into XI data type which is giving PARSER ERROR.
Do you have any idea how to create a DTD file from a XSD file as you mentioned in this message?
Thanks
Kalyan

IDOC filtering for VLO2N PGI interface

Hello everyone,
we have an outbound interface online. An idoc is generated on PGI in VL02N (Interface ART_DVT).
We have another outbound interface which generates an IDOC for deliveries (Interface ART_OUT).
Both these interfaces update a table in a third party system.
As per my current requirement, the PGI interface should be triggered only for deliveries for which ART_OUT has been triggered.
The ART_DVT interface is being triggered via message control NACE.
Message Type : DELINF
Basic Type : DELVRY05
Whenever ART_OUT is triggered, a z-table gets updated in SAP with the necessary details.
I think I can check here before triggering the ART_DVT interface if i could use an user-exit in VL02N.
Any help is appreciated.
Thanks in advance.
Regards,
Xineohpi

Can someone atleast tell me if there is an user-exit or badi using which i can restrict the PGI idoc generation based on some check or if the message control execution part can be restricted..
in dire need of help......
Regards,
Xineohpi

Inbound Idoc Generation

Hello All,
We have a ALE concept to transfer data between clients. We have made the settings and the process was fine. But on some days Inbound Idoc is not getting generated with respect to the outbound Idoc, and after some times once again system comes to normal state and the idoc generation is fine. How ever we dont have any root cause for the failure of Idoc generation. Could someone let me know where i can chk the info and what all the parammetres needs to be checked.
Note ; There are no issues in ALE ocnfig settings.

Hi ,
See the following code :
Program To Generate IDoc
*& Report ZZ_Program_To_Create_Idoc
report zz_program_to_create_idoc                     .
tables: ekko,ekpo.
selection-screen skip 3.
selection-screen begin of block b1 with frame title titl.
selection-screen skip.
select-options s_ebeln for ekko-ebeln.
selection-screen skip.
selection-screen end of block b1.
data: header_segment_name like edidd-segnam value 'Z1EKKO',
      item_segment_name like edidd-segnam value 'Z1EKPO',
      idoc_name like edidc-idoctp value 'Z19838IDOC1'.
data: header_segment_data like z1ekko,
      item_segment_data like z1ekpo.
data: control_record like edidc.
data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
data: i_communication like edidc occurs 0 with header line,
      i_data like edidd occurs 0 with header line.
data: begin of i_ekko occurs 0,
      ebeln like ekko-ebeln,
      aedat like ekko-aedat,
      bukrs like ekko-bukrs,
      bsart like ekko-bsart,
      lifnr like ekko-lifnr,
      end of i_ekko.
data: begin of i_ekpo occurs 0,
      ebelp like ekpo-ebelp,
      matnr like ekpo-matnr,
      menge like ekpo-menge,
      meins like ekpo-meins,
      netpr like ekpo-netpr,
      end of i_ekpo.
start-of-selection.
select ebeln aedat bukrs bsart lifnr from ekko
          into table i_ekko where ebeln in s_ebeln.
select ebelp
       matnr
       menge
       meins
       netpr
       from ekpo
       into table i_ekpo
       where ebeln in s_ebeln.
control_record-mestyp = messagetyp.
control_record-rcvprt = 'LS'.
control_record-idoctp = idoc_name.
control_record-rcvprn = '0MART800'.
loop at i_ekko.
header_segment_data-ebeln = i_ekko-ebeln.
header_segment_data-aedat = i_ekko-aedat.
header_segment_data-bukrs = i_ekko-bukrs.
header_segment_data-bsart = i_ekko-bsart.
header_segment_data-lifnr = i_ekko-lifnr.
i_data-segnam = header_segment_name.
i_data-sdata = header_segment_data.
append i_data.
select ebelp
       matnr
       menge
       meins
       netpr
       from ekpo
       into table i_ekpo
       where ebeln = i_ekko-ebeln.
loop at i_ekpo.
item_segment_data-ebelp = i_ekpo-ebelp.
item_segment_data-matnr = i_ekpo-matnr.
item_segment_data-menge = i_ekpo-menge.
item_segment_data-meins = i_ekpo-meins.
item_segment_data-netpr = i_ekpo-netpr.
i_data-segnam = item_segment_name.
i_data-sdata = item_segment_data.
append i_data.
endloop.
clear i_ekpo.
refresh i_ekpo.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control                  = control_record
OBJ_TYPE                             = ''
CHNUM                                = ''
tables
    communication_idoc_control           = i_communication
    master_idoc_data                     = i_data
exceptions
   error_in_idoc_control                = 1
   error_writing_idoc_status            = 2
   error_in_idoc_data                   = 3
   sending_logical_system_unknown       = 4
   others                               = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
         with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
loop at i_communication.
    write: 'IDOC GENERATED', i_communication-docnum.
endloop.
commit work.
endif.
initialization.
titl = 'ENTER THE PURCHASE ORDER NUMBER'.
Reward points if helpful.
Regards.
Srikanta Gope.

Any BADI returning the 'IDOC Status' during IDOC generation.

Hello All,
I need a BADI which is being called during any IDOC generation and which returns the 'IDOC Status' i.e. Pass/Fail etc.
So far I am able to find BADIs like 'IDOC_DATA_MAPPER' or ''IDOC_DATA_INSERT'' but such BADIs only return the IDOC document number.. they do not return any information on IDOC Status (the field Status field remains blank).
Can any one suggest some solution on this please.
Regards
Vikas Gupta

Hi Erik,
Thanks for your reply, though i was able to get the status from BADI IDOC_DATA_MAPPER itself (earlier there were some config issues...which were creating some problems) but thanks for letting me know about table EDIDS, it helped at places.
Regards
Vikas Gupta

F110 Idoc generation

hi Folks,
i want to generate an idoc PEXR2002 using transaction f110 ( automatic payment program)
Does anybody have any idea on how to do it. your inputs are valuable.
Regards,
Padma

hi Madhu,
thanx for your input. I checked all the settings. they are in place.
In the additional log I am getting following entries:
06-06-2008 12:36:51 payments by EDI / IDoc generation
06-06-2008 12:36:51 IDOcs were generated for the following entries
06-06-2008 12:36:51 Company code 3001 House bank AMX Payment method W
06-06-2008 12:36:51
06-06-2008 12:36:51 End of log
06-06-2008 12:36:52 Step 002 started (program SAPFPAYM_SCHEDULE, variant &0000000000019, user ID SACHIN)
06-06-2008 12:36:52 Step 003 started (program RFFOEDI1, variant &0000000000012, user ID SACHIN)
06-06-2008 12:36:52 Program RFFOEDI1: No records selected
06-06-2008 12:36:52 Job finished
Regards,
Padma

Idoc generation for VL02N

Similar Messages

Maybe you are looking for