Generate IDOC FM IDOC_INPUT_*

Hello
I would like to ask what are the steps to generate the Idoc function module such as IDOC_INPUT_MBGMCR and IDOC_INPUT_DELVRY.
Thanks

Hi ,
these are the specific steps..
Inbound IDOC Development
Create Idoc segments (WE31)
Create Idoc (WE30)
Create message type (WE81)
Assign Message type to Idoc type (WE82)
Develop posting program.
Configure the function to handle one or more idocs in the same call (BD51)
Assign function module to Idoc and message type (WE57)
Create inbound process code (WE42)
Create RFC Destination in (SM59)
Create Port for RFC destinationr (WE21)
Add message type to inbound parameters for partner (WE20)
Regards,
Prabhudas

Similar Messages

How i need to write a logic to generate idoc for some of infotypes, when i change the single infotype

Hi experts,
I have an requirement , when I change any infotype record from pa30 or pa40, i.e
suppose I am changing the infotype 0002 in pa30 , the idoc only generated for that changed infotype only,
but I need it to generate the idoc for some other infotypes also I.e(0000,0002,t528t, 0016).
So please give me some help to generate idoc when I run a rbdmidoc(bd21).
Thanks in advance.
Venkat

yes, visible bounds is reading the non-visible masked objects too.
you're going to have to do it the hard way, loop through all your objects to get your bounds manually, and while you're at it, test for clipping masks and use the masking path instead.

File to IDOC:how do i relate inbound idoc with generated idoc in the R/3

hi experts;
can any body tell me how can i relate the IDOC number genrated in the PI with the generated IDoc number in the SAP R/3 system for file to IDOC scenario?
in SAP PI for tcade idx5, idoc no is:12002
but in SAP R/3 in tcode WE05, idoc no is:846915
how can i know a particular message (in SAP PI) created a particular idoc in the backend SAP R/3 System.
thanks in advance,
kumar

Hi Kumar
at the time of testing you have to note down a time at what ur file got picked up ok
then go to we05
-> give the date on CREATED ON field.
-> then in BASIC TYPE field select your particular IDOC CREMAS05 or whatever, see the TIME field that you have noted down at the time of testing, if that is matching means that is ur latest IDOC you have tested.
-> one more thing, tha last IDOC showing in the list means that is your latest IDOC you have tested.
Hope i have helped you, points plz
Warm Regards
Dheeraj Kumar

Not generating IDOC for payment Advice to Vendors

Hi,
IDOC was getting generated before one month but now SAP system has stopped generating IDOC for vendor Payment advice. This problem is with all the vendors.
After execution of t-c-ode F110, payment document is successfully created, but IDOC is not geenerated. There is no log about "IDOC not getting generated"
Checked Table REGUH, IDOC number is displayed as 0000000000000.
This was happening perfectly one month back.
There is no change in Vendor master data, IDOC number range is available.
There is no posting of IDOC in table DFKKTHP and checked Report REREMITADV for which there is no data.
Waiting for your valuable responses.
Regards
veleyudham

Hi,
First check certain customization:-
(1) FBZP setup for payment method at country level. Whether IDOC generation program is assigned or not.
(2) Then check the variant of RFFOEDI1 in the printout tab of F110. Is the selection creteria OK?
(3) Check the partner profile in WE20 for the bank.
Then run the program RFFOEDI1 in SE38 for your payment run and check the output.
You can also get this program debugged from you ABAPer to have root cause analysis.
Regards,
Gaurav

Payment program F110 not generating IDoc

Hi All
while running payment program F110 I get a sucess message IDocs generated for company code and payment method, In the payment log i see this infomation.
when i check these IDoc's in WE02 I can't find any of these IDoc's. It looks to me the program RFFOEDI1 with the variant I created is not getting executed in spite of the check box "Generate IDoc" being checked.
can any one suggest what would be wrong?
Thanks
Pranav

Hi All,
Thanks for the quick response. Following are the config made with forms;
In Paying company code setup:
    Form for payment adivce: F110_US_AVIS
    EDI accompanying sheet form: F110_EDI_01
In Payment method in company code:
    Form for payment medium : F110_EDI_01
    Next form : F110_US_DTA
I have checked with all other configuration and seems to be in place. Please let me know if these config regarding forms are correct.
When I run the program REFFOEDI1 with the variant I created these IDocs are getting generated. These are not getting generated when I run the payment program F110. I am missing some thing which is not triggering this program from payment program. Please let me know if you have any suggestion.
Thanks
Pranav

Message type for generating IDOC for SUBCONTRACTING PURCHASE ORDER

Hi All,
I have to generate IDOC for PO creation or change .
I am using IDOC_OUTPUT_ORDERS and IDOC_OUTPUT_ORDCHG.
The messagetype.idoctype I am using is ORDERS. ORDERS05 and ORDCHG. ORDERS05.
Now the confusion is regarding whether this message type will work in case of SUBCONTRACTING PURCHASE ORDER as well ?
As I have gone through some websites and came to know that I will have to use PORDCR1.PORDCR102 specially for subcontracting.
And programs we need to use is BUS2012_ICH_R3 instead of RSNASTED and Form Routine SEND_PORDCR1 instead of EDI_PROCESSING.
Purchase Order Collaboration scenario - Not generating IDOC in ECC
http://www.erpgenie.com/faq/edi_purchasing.htm on this site question no 8.
Subcontract PO IDOCs
I hope your experience will help me .
Please reply ASAP.
Edited by: uttam27 on Dec 4, 2011 1:47 PM

There is a generic function to create change pointers for all message typs - 'CHANGE_POINTERS_CREATE_DIRECT'. This is triggered only if you configure your message type to create change pointers from BD50.
Once you activate it do any change to orders you can see change pointer tables BDCPV filled. Then BD21 will read the changes and generated outbound idocs accordingly.

Generating idoc for Purchase orders - ORDERS05

Hi,
Can you please let me know how to generate idoc for Purchase orders - ORDERS05-manually, not by activating change pointers.

hi
i believe u wont have this functionality as it is a transcational data and the one way of doing it by configuring output types only.

Docnum of generated Idoc in File2Idoc scenario

Hi folks,
I have a file2Idoc scenario and I would like to see in PI the docnum of the Idoc generated in the target backend system.
In sxmb_moni I ve found an IdocOutbound entry in the soap header but that docnum does not exist in the target system (the Idoc is there but with a different docnum). Actually I dont know what docnum it is as I couldnt find it in the pi system as well.
Its easy to identify the Idoc by timestamp in our dev system however it is not an option in the prod system where we have 10000 msg an hour
So how can I find out in PI which Idoc has been created in the target system?
thx

Hi,
Go to idx5 transaction and check the idoc number for the respective message.
Please refer the below links
file to IDOC:how do i relate inbound idoc with generated idoc in the R/3
Monitoring the IDOC Adapter in XI/PI using IDX5
Regards,
Priyanka

Pls send step by step procedure to create generated idoc type in ECC 6.0

Hi
pls send me the step by step procedure In ECC 6.0 Version
1) To create generated idoc type
2) To extended idoc type
3) How we can add structure to custom segments
thanks in advance

hi,
check these likns...
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
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
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
regds,
paras

Extension of generated Idocs types

hello,
does anybody knows why I can not create extension of generated (means in table EDBAS-GENERATED = 'X') idocs?
I tried to extend idoc BATMAS03 on R/3 Ecc 6 and got message:
message e099(b1) with
'Action is not possible for generated idoctypes'
In former version of R/3 4.6C it was possible to extend such IDoc BATMAS02 (generated one) without any problems.
Of course I found in program MSED5F02 in routine CREATE_EXT_STRUCTURE new (in comparison to 4.6C) extra check which protects against extension of generated IDocs, but I want to get to know what was behind that decision or how to workaround that problem.
Thanks in advance,
Marcin

Hi,
User Exits are used to populate data in new segments added and to read them
back which provides extension to existing idocs.
IDOC EXTENSIONS
SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type. Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
First, determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save. Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
Pls reward helpful points.
Regards,
Ameet

Error when generating IDoc from MC document - workitem to all the SAP users

A workflow item with the subject of Error when generating IDoc from MC document is sent to all the SAP users' inbox. Is it possible to stop the generation of this work item? If that is not possible, can we limit sending the work item to a specific user/agent instead of all the users in the system?
It appears that these work item or error message are generated when one of the developers reopen the POs and add line items. Moreover, during that time the procurement team blocked the IDOCs from going out to the vendors when changing and resaving the POs. Therefore, we need stop the generation of error message/work item when the IDOCs generation blocked.

Please check Rule 70000141which is the default rule for this task. Inside this rule a FM is attcahed which is reading table EDO13 and EDPP1 where agent is retrieved Probably this table entries are not maintained. This Workflow is getting triggered from Message cOntrol I think.
Please check this link for
http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4aec8453d11d189430000e829fbbd/frameset.htm
<b>Reward points if useful and close thread if resolved</b>

Error when generating IDoc from MC document

Hi,
Our Workflow administrator is getting the following error in his inbox daily for a particular IDOC type.
Error when generating IDoc from MC document
Please let me know how to disable this message.
Regards
Elini.P

Hi experts,
i got the error msg when generating idoc from mc document
this error msg goes to all sap users inbox,how to resolve this problem
pl give me solutions
regards
kumar

Generating IDoc DDF structures for EDI mapping

Hello all,
I am looking for a way to generate IDoc DDF structures to use them in the EDI mapping in Gentran.
I was able to find one on ERPGenie.com (developed by Kevin Wilson) but it is only available for ECC 4.x. We are on ECC 6 and the program gives me an ABAP dump when I try to run it.
Does anyone have the fix for this code? Or perhaps another way to accomplish this task?
Actually, I am only interested in generating the MBGMCR02 IDoc
Thanks for your help
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 7, 2008 12:36 PM

It's been a long time since I have done any IDOC processing.
Go to SE37 and enter the function module IDOC_INPUT_ORDERS. Display the source code. Search for "CALL CUSTOMER". You should see several "CALL CUSTOMER-FUNCTION" lines. These are enhancements where you can manipulate the IDOC data. If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value. Double-clicking on the number in quotes will bring you to an "EXIT_" function module. A "ZX" INCLUDE program is referenced. If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it. The values passed into the function module are available in the INCLUDE.
Ideally, you should create a project in transaction CMOD that references the chosen enhancement. This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

How to extended Generated IDoc type of MRESCR01 (Material Reservation )

Hi Experts ,
My scenario : I am receiving Material reservation data from SAP PI team , There is some extra fields .
My approach 1 . I have to extended the basic idoc MRESCR01 , here is problem 'Action is not possible for generated IDoc types' .
I have seen many posts for the same but I did nt get proper post for the same .
and also how to create ALE -BAPI interface by using BDBG , Please help this scenario .
Thanks ,
Jay.

Solution : new Message Type (By reducing MATMAS)

Generate IDoc COND_A01

Hi all,
I need to generate an Idoc with type COND_A01. Does anyone have some insight on how can I do this?
Please note that I don't want to use WE19, because what I need to do is to get some "real" data from the system and check what values go into which fields.
Thks

Hi Bruno,
Welcome to SDN.
You may need to ask SD Functional folk to create new pricing report (t/code V/LA) with sending IDoc, message type and logical system paramaters available for input.
or you can copy an existing pricing report (t/code V/LD) into custom report/program and change below parameters to be displayed.
PARAMETERS sen_idoc(1) TYPE c *NO-DISPLAY.
PARAMETERS p_mestyp LIKE tbdme-mestyp *NO-DISPLAY.
PARAMETERS p_logsys LIKE tbdls-logsys *NO-DISPLAY.
Once the report is available for you then the next step is to configure ALE and partner profile in order to generate IDoc COND_A01 from the pricing report.
Hope this will help.
Regards,
Ferry Lianto

Generate IDOC FM IDOC_INPUT_*

Similar Messages

Maybe you are looking for